Configuration file generation method and device, equipment, storage medium and program product

Abstract

The invention discloses a configuration file generation method and device, equipment, a storage medium and a program product, and the method comprises the steps: receiving a configuration task which comprises configuration intention information; determining a target configuration scene and execution parameters based on the configuration intention information; the execution parameters comprise at least one of an execution object, an execution action, a dialogue scene and an intention corresponding to the dialogue scene; calling at least one corresponding basic template file from a preset template library based on the target configuration scene; the basic template file comprises a dialogue scene template file, an instruction template file and an intention-instruction mapping template file; and filling corresponding fields of the basic template file with the execution parameters, and determining a target configuration file. According to the method, the problems of high development threshold, long period, difficult maintenance, inflexible configuration and the like in the prior art can be solved, and efficient and accurate generation of the configuration file is realized.

Description

Technical Field

[0001] This application relates to the field of voice interaction technology, and in particular to a configuration file generation method, apparatus, device, computer storage medium, and computer program product. Background Technology

[0002] With the rapid development of smart cockpit technology, the control functions of voice assistants are constantly being added, increasing the complexity of voice dialogue system development. Traditional voice dialogue system development methods require developers to write complex code from scratch for different functional requirements. This not only demands high levels of professional skill from developers, resulting in a high development threshold, but also leads to long development cycles and difficulty in quickly responding to iterative functional needs. Furthermore, the fragmented code writing approach increases the difficulty of subsequent system maintenance and upgrades, hindering the long-term stable operation of the system.

[0003] To address the aforementioned issues, existing technologies employ template-based approaches to simplify the development process. However, existing template-based solutions suffer from problems such as limited template types, unclear configuration logic, and a lack of standardized parameter filling. This makes it difficult to efficiently and accurately generate configuration files, failing to meet the needs of rapid development and flexible configuration of voice dialogue systems in scenarios such as smart cockpits. Consequently, it directly impacts the overall performance and user experience of the voice dialogue system.

[0004] Therefore, there is an urgent need for a configuration file generation method that can lower the development threshold, shorten the development cycle, facilitate maintenance, and provide flexible, efficient, and accurate configuration to adapt to the rapid iteration needs of voice dialogue systems. Summary of the Invention

[0005] This application provides a configuration file generation method, apparatus, device, computer storage medium, and computer program product, which can solve the problems of high development threshold, long cycle, difficult maintenance, and inflexible configuration in the prior art, and realize efficient and accurate generation of configuration files.

[0006] In a first aspect, embodiments of this application provide a configuration file generation method, including: Receive a configuration task, the configuration task including configuration intent information; Based on the configuration intent information, the target configuration scenario and execution parameters are determined; the execution parameters include at least one of the following: execution object, execution action, dialogue scenario, and intent corresponding to the dialogue scenario; Based on the target configuration scenario, at least one corresponding basic template file is called from the preset template library; the basic template file includes: dialogue scenario template file, instruction template file, and intent-instruction mapping template file; The execution parameters are filled into the corresponding fields of the base template file to determine the target configuration file.

[0007] In some possible implementations, the step of filling the execution parameters into the corresponding fields of the base template file to determine the target configuration file includes: The dialogue scenario is filled into the dialogue scenario field of the dialogue scenario template file, and the intent is filled into the intent field of the dialogue scenario template file to obtain the first configuration file; The execution object and / or execution action are filled into the instruction execution data field of the instruction template file to obtain the second configuration file; A mapping relationship is established between the intent and the instruction identifier in the instruction template file in the intent-instruction mapping template file to obtain a third configuration file; The target configuration file is determined based on the first configuration file, the second configuration file, and the third configuration file.

[0008] In some possible implementations, the step of calling at least one corresponding basic template file from a pre-set template library based on the target configuration scenario includes: When the target configuration scenario is to add a voice dialogue function, the dialogue scenario template file, the instruction template file, and the intent-instruction mapping template file are called from the preset template library; When the target configuration scenario involves modifying existing functional parameters, the instruction template file is called from the preset template library; When the target configuration scenario involves adding a new intent mapping relationship, the intent-instruction mapping template file is called from the preset template library.

[0009] In some possible implementations, the step of filling the dialogue scene into the dialogue scene field of the dialogue scene template file and filling the intent into the intent field of the dialogue scene template file to obtain a first configuration file includes: Check if the dialogue scenario exists in the dialogue scenario template file; If the dialogue scenario exists in the dialogue scenario template file, the template file corresponding to the dialogue scenario shall be used as the first configuration file. If the dialogue scenario does not exist in the dialogue scenario template file, a new dialogue scenario is created, and the intent is filled into the intent field of the new dialogue scenario to obtain the first configuration file.

[0010] In some possible implementations, the instruction execution data field includes: an object field and an action field; The step of filling the execution object and / or execution action into the instruction execution data field of the instruction template file to obtain the second configuration file includes: The execution object is populated into the object field, and the execution action is populated into the action field to obtain the second configuration file.

[0011] In some possible implementations, after determining the target configuration file, the following is also included: The target configuration file is subjected to a configuration consistency check, which includes checking whether the reference relationship between the dialogue scenario template file, the instruction template file, and the intent-instruction mapping template file is correct. If the verification passes, the target configuration file will be loaded into the configuration management module of the voice dialogue system; If the verification fails, a configuration error report will be generated and output to prompt the user to make corrections.

[0012] Among the possible implementations are: Receive voice information input by the user, the voice information being used to describe the vehicle function requirements to be executed; The control intent is extracted from the speech information using a natural language understanding model; Based on the control intent and the third configuration file in the target configuration file, obtain the instruction identifier corresponding to the control intent; Based on the control intent and the first configuration file in the target configuration file, determine the dialogue scenario corresponding to the control intent and the intent corresponding to the dialogue scenario. In the dialogue scenario, based on the instruction identifier and the second configuration file in the target configuration file, instruction execution data corresponding to the instruction identifier is obtained; Based on the instruction execution data, control instructions for executing the control intent are generated.

[0013] In some possible implementations, after extracting the control intent from the speech information using a natural language understanding model, the method further includes: The vehicle functional requirement type is determined based on the control intent; Based on the vehicle functional requirement type, determine at least one target configuration field corresponding to the vehicle functional requirement type; Based on the target configuration field, query the target configuration file to see if there is a current configuration file that matches the target configuration field; If a configuration file matching the target configuration field exists in the target configuration file, a control instruction for executing the control intent is generated based on the configuration file; If no configuration file matching the target configuration field exists in the target configuration file, the target configuration file is updated based on the target configuration field to generate a target configuration file matching the target configuration field.

[0014] Secondly, embodiments of this application provide a configuration file generation apparatus, the apparatus comprising: A receiving module is used to receive a configuration task, wherein the configuration task includes configuration intent information; The determination module is used to determine the target configuration scenario and execution parameters based on the configuration intent information; the execution parameters include at least one of the following: execution object, execution action, dialogue scenario, and intent corresponding to the dialogue scenario; The calling module is used to call at least one corresponding basic template file from a preset template library based on the target configuration scenario; the basic template files include: dialogue scenario template files, instruction template files, and intent-instruction mapping template files; The fill module is used to fill the execution parameters into the corresponding fields of the base template file to determine the target configuration file.

[0015] Thirdly, embodiments of this application provide a configuration file generation device, the device comprising: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the configuration file generation method as described in the first aspect above.

[0016] Fourthly, embodiments of this application provide a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the configuration file generation method described in the first aspect above.

[0017] Fifthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, enable the electronic device to perform the configuration file generation method as described in the first aspect above.

[0018] In this embodiment, after receiving the configuration task, the target configuration scenario and execution parameters corresponding to the configuration intent information in the configuration task are used. Then, based on the target configuration scenario, three types of basic template files—dialogue scenarios, commands, and intent-command mappings—are called from a pre-set template library, and the execution parameters are filled into the corresponding fields of the basic template files, thereby generating the target configuration file. On one hand, this method uses configuration intent information as its core, directly determining the target configuration scenario and execution parameters. The execution parameters cover key elements such as the execution object, execution action, dialogue scenario, and corresponding intent, ensuring that the configuration direction highly matches user needs. Simultaneously, calling template files based on scenario differences avoids loading redundant templates, reduces invalid configuration steps, and significantly improves configuration accuracy. On the other hand, by using dialogue scenario template files (RuleDialogModel.json), command template files (CommandModel.json), and intent-command mapping template files (IntentCmdMappingModel.json), the configuration process is transformed into a standardized configuration of intent analysis, template invocation, and parameter filling. This effectively replaces the traditional complex code writing mode, allowing non-professional developers to participate in configuration and significantly lowering the development threshold of voice dialogue systems. Furthermore, the template files can be flexibly selected based on the target configuration scenario, improving configuration flexibility. In addition, by centralizing dialogue configuration in file templates, it facilitates later maintenance and upgrades, improving the accuracy and stability of the configuration. Attached Figure Description

[0019] The features, advantages, and technical effects of exemplary embodiments of this application will now be described with reference to the accompanying drawings.

[0020] Figure 1 A flowchart illustrating a configuration file generation method provided in one embodiment of this application; Figure 2 This is a flowchart of an embodiment S104 of this application; Figure 3 This is a schematic diagram of the structure of a configuration file generation apparatus provided in one embodiment of this application; Figure 4 This is a schematic diagram of the structure of a configuration file generation device provided in one embodiment of this application. Detailed Implementation

[0021] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0022] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0023] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0024] With the rapid development of smart cockpit technology, the control functions of voice assistants are constantly being added, increasing the complexity of voice dialogue system development. Traditional voice dialogue system development methods require developers to write complex code from scratch for different functional requirements. This not only demands high levels of professional skill from developers, resulting in a high development threshold, but also leads to long development cycles and difficulty in quickly responding to iterative functional needs. Furthermore, the fragmented code writing approach increases the difficulty of subsequent system maintenance and upgrades, hindering the long-term stable operation of the system.

[0025] To address the aforementioned issues, existing technologies employ template-based approaches to simplify the development process. However, existing template-based solutions suffer from problems such as limited template types, unclear configuration logic, and a lack of standardized parameter filling. This makes it difficult to efficiently and accurately generate configuration files, failing to meet the needs of rapid development and flexible configuration of voice dialogue systems in scenarios such as smart cockpits. Consequently, it directly impacts the overall performance and user experience of the voice dialogue system.

[0026] To address the problems in the prior art, embodiments of this application provide a configuration file generation method, apparatus, device, computer storage medium, and computer program product.

[0027] The configuration file generation method provided in the embodiments of this application will be described below.

[0028] Figure 1 A flowchart illustrating a configuration file generation method according to an embodiment of this application is shown. The method includes the following steps: S101, Receive configuration task, the configuration task includes configuration intent information.

[0029] In S101, the configuration intent information can be audio information transmitted by the user through the voice input device to clarify the requirements of the voice dialogue function to be configured, or it can be text information. It is the source of requirements for the subsequent configuration process and directly determines the configuration direction and goal.

[0030] For example, users can input configuration intent information through voice input devices (such as microphones in smart cockpits, voice input modules on mobile phones, etc.). For example, configuration intent information could be "configure voice control function for opening car windows", "modify execution parameters for switching seat massage modes", "add intent mapping relationship for air conditioning temperature adjustment", etc.

[0031] S102, based on the configuration intent information, determine the target configuration scenario and execution parameters.

[0032] In S102, once the configuration intent information is clear, the corresponding target configuration scenario and execution parameters can be determined. The target configuration scenario may include adding a voice dialogue function, modifying existing function parameters, or adding intent mapping relationships; the execution parameters include at least one of the following: execution object, execution action, dialogue scenario, and intent corresponding to the dialogue scenario.

[0033] For example, if the configuration intent information is "Add window opening control intent", then the target configuration scenario is to add a voice dialogue function. The execution parameters include the execution object "window", the execution action "open", the dialogue scenario "WindowDialog", and the intents corresponding to the dialogue scenario are "WindowOn" and "WindowOff". If the configuration intent information is "Modify seat massage mode switching parameters intent", then the target configuration scenario is to modify existing function parameters. The execution parameters include the execution object "seat massage mode", the execution action "switch", and the dialogue scenario "NextSeatMassageModeSet_Rox". If the configuration intent information is "Add air conditioning temperature adjustment mapping intent", then the target configuration scenario is to add an intent mapping relationship. The execution parameters include the dialogue scenario "AirConditionerTemperatureAdjust" and the command identifier "sys.car.air.temp".

[0034] S103, based on the target configuration scenario, call at least one corresponding basic template file from the preset template library.

[0035] In S103, the template library is a database that stores various standardized basic template files. These basic template files are predefined configuration file prototypes with fixed formats and fields, including dialogue scenario template files (such as RuleDialogModel.json), command template files (CommandModel.json), and intent-command mapping template files (such as IntentCmdMappingModel.json). Depending on the target configuration scenario, the corresponding basic template file can be called.

[0036] S104. Fill the execution parameters into the corresponding fields of the base template file to determine the target configuration file.

[0037] In S104, the corresponding field is a preset location in the basic template file used to store specific execution parameters. The target configuration file is a complete configuration file formed after parameter filling and can be directly used in the voice dialogue system. It is the final result of the configuration process.

[0038] In practice, the execution parameters can be filled into the corresponding positions one by one according to the field definition of the basic template file: the dialogue scenario is filled into the dialogue scenario field of the dialogue scenario template file, the intent is filled into the intent field of the dialogue scenario template file, the execution object and execution action are filled into the instruction execution data field of the instruction template file, the association between the dialogue scenario and the instruction identifier is established in the intent-instruction mapping template file, and after filling is completed, they are integrated to form the target configuration file to ensure that the file can be directly adapted to the voice dialogue system.

[0039] In this embodiment, after receiving voice information describing the user's voice dialogue function requirements, the configuration intent, corresponding target configuration scenario, and execution parameters are determined through intent recognition. Then, based on the target configuration scenario, three types of basic template files—dialogue scenario, command, and intent-command mapping—are called from a pre-set template library, and execution parameters are filled into the corresponding fields of the basic template files to generate the target configuration file. On one hand, this method uses configuration intent information as its core, directly determining the target configuration scenario and execution parameters. The execution parameters cover key elements such as the execution object, execution action, dialogue scenario, and corresponding intent, ensuring that the configuration direction highly matches the user's needs. Simultaneously, calling template files based on scenario differences avoids loading redundant templates, reduces invalid configuration steps, and significantly improves configuration accuracy. On the other hand, by using dialogue scenario template files (RuleDialogModel.json), command template files (CommandModel.json), and intent-command mapping template files (IntentCmdMappingModel.json), the configuration process is transformed into a standardized configuration of intent analysis, template invocation, and parameter filling. This effectively replaces the traditional complex code writing mode, allowing non-professional developers to participate in configuration and significantly lowering the development threshold of voice dialogue systems. Furthermore, the template files can be flexibly selected based on the target configuration scenario, improving configuration flexibility. In addition, by centralizing dialogue configuration in file templates, it facilitates later maintenance and upgrades, improving the accuracy and stability of the configuration.

[0040] In some embodiments, such as Figure 2 As shown, S104 may include: S1041, populate the dialogue scene into the dialogue scene field of the dialogue scene template file, and populate the intent into the intent field of the dialogue scene template file to obtain the first configuration file.

[0041] A dialogue scenario is a standardized identifier for user configuration requirements, used to uniquely correspond to a voice dialogue function configuration; a dialogue scenario template file is a basic template used to define dialogue scenarios and the responsive intents of that dialogue scenario, and the intent field is a specific area specifically used to store the names of the responsive configuration intents; the first configuration file is a configuration file that has the correspondence between dialogue scenarios and responsive intents after the configuration intent names have been filled in.

[0042] For example, a dialogue scenario template file is used to configure a dialogue scenario and the names of intents that the dialogue scenario can accept. It includes dialogue scenario fields (such as the "WindowDialog" field) and intent fields (such as the "allowed" field).

[0043] In practice, the system can check if the dialogue scenario exists in the dialogue scenario template file. For example, for the configuration intent "WindowOn (Open the window)", it checks if the dialogue scenario RuleDialogModel.json file contains the dialogue scenario "WindowDialog (Window Dialog Box)". If the corresponding dialogue scenario exists in the template file, the template file is used as the first configuration file. If the corresponding dialogue scenario does not exist in the template file, a new dialogue scenario is created, and the intent is populated into the intent field of the new dialogue scenario. For example, if the "WindowDialog (Window Dialog Box)" dialogue scenario does not exist, it is created, and "WindowOn (Open the window)" is populated into its "allowed" field. Through these steps, the first configuration file (i.e., the populated dialogue scenario template file) is obtained.

[0044] Through the scene detection process, on the one hand, it avoids multiple duplicate dialogue scenarios for the same intent, ensuring a one-to-one correspondence between dialogue scenarios and intents. This prevents confusion in intent recognition caused by scene redundancy and improves the system's accuracy in responding to user voice commands. On the other hand, for configuration intents without corresponding dialogue scenarios, it supports creating new dialogue scenarios and populating them, meeting the configuration requirements of adding new voice dialogue functions. For existing corresponding scenarios, it directly adds intents to adapt to extended function scenarios without reconstructing the entire dialogue scenario template structure, adapting to different types of configuration requirements. Furthermore, this process eliminates the need for developers to manually check for the existence of dialogue scenarios; the system automatically completes the detection and adaptation operations, reducing manual intervention and avoiding configuration errors caused by human judgment mistakes. It also eliminates the tedious step of repeatedly creating dialogue scenarios, further shortening the configuration cycle and improving configuration efficiency.

[0045] S1042, fill the execution object and / or execution action into the instruction execution data field of the instruction template file to obtain the second configuration file.

[0046] The execution object is the target of the voice control function, and the execution action is the specific operation to be performed; the instruction template file is the basic template used to define the instruction name, instruction identifier and the data required for instruction execution, and the instruction execution data field is the area that stores the core execution data such as the execution object and execution action; the second configuration file is the configuration file with complete instruction execution logic after the execution data is filled in.

[0047] For example, the instruction execution data fields include an object field and an action field. When filling the instruction execution data fields of the instruction template file with the execution object and / or execution action to obtain the second configuration file, specifically, the execution object can be filled into the object field, and the execution action can be filled into the action field to obtain the second configuration file.

[0048] In practice, the instruction template file is used to configure the instruction name, instruction identifier (such as functionCode), and instruction execution data. The instruction execution data fields include an object field (such as "object") and an action field (such as "action"). The execution object is filled into the object field, and the execution action is filled into the action field. For example, for the execution object "window" and the execution action "open", in the CommandModel.json file, the instruction name field is filled with "WindowControl", the instruction identifier field is filled with "sys.car.crl", the object field is filled with "window", and the action field is filled with "open", resulting in the second configuration file (i.e., the filled instruction template file).

[0049] S1043, Establish the mapping relationship between intents and instruction identifiers in the intent-instruction mapping template file to obtain the third configuration file.

[0050] The intent-command mapping template file is the basic template used to associate the dialogue scenario template file and the command template file, and is responsible for establishing the correspondence between the configured intent and the executed command. The command identifier is the specific information in the command template file used to uniquely identify a command. The mapping relationship is the correspondence between the configured intent name and the command identifier, which is used to quickly match and execute commands after intent recognition. The third configuration file is the configuration file with the intent-command association logic after the mapping relationship is established.

[0051] In practice, the intent-command mapping template file is used to associate the dialogue scenario template file and the command template file. By establishing a mapping between configured intents and command identifiers, the voice dialogue system can match the corresponding execution command based on the user's input intent. For example, in the IntentCmdMappingModel.json file, the matching rule name is defined as "OpenWindowRule", the dialogue matching condition is set to "WindowDialog", the intent matching condition is set to "WindowOn", and the target command identifier is set to "sys.car.crl", thereby establishing a mapping relationship between "WindowOn" and "sys.car.crl" to obtain the third configuration file (i.e., the populated intent-command mapping template file).

[0052] S1044, Based on the first configuration file, the second configuration file, and the third configuration file, determine the target configuration file.

[0053] The target configuration file is a complete configuration result that integrates the first, second, and third configuration files. It contains all the core configuration information, such as dialogue scenario definition, command execution data, and intent-command mapping relationship. Together, they constitute the complete voice dialogue function configuration logic, which can be directly loaded into the voice dialogue system and support the function operation, ensuring that the voice dialogue system can accurately execute the corresponding operation according to the voice command input by the user.

[0054] On the one hand, by focusing on binding intents with dialogue scenarios in the dialogue scenario template files, the scope of intents that the system can respond to is clearly defined; the instruction template files focus on the standardized configuration of execution data, providing a clear basis for function execution; and the intent-instruction mapping template files build a bridge between the two, ensuring that the corresponding instruction can be accurately matched after intent recognition. The three have clear division of labor and a closed logical loop, avoiding configuration confusion and association failure. On the other hand, the categorized filling mode does not require a complete reconstruction of the template files, but only requires supplementing or modifying parameters for the corresponding fields, reducing invalid operations; at the same time, the standardized field filling requirements and mapping rules reduce the error rate of manual configuration, avoiding the voice dialogue system from failing to respond normally due to incorrect parameter filling or disordered association, ensuring the reliability of configuration results, and meeting the core requirement that the quality of template files directly affects system performance. Furthermore, when adding or modifying functions, only the relevant fields of the corresponding template files need to be adjusted, without changing the overall configuration architecture, adapting to the iterative needs of the continuously added voice functions of the intelligent cockpit; the independent configuration characteristics of the three types of template files also provide convenient conditions for subsequent function upgrades and multi-scenario adaptation (such as voice interaction needs in different regions), without having to repeatedly build the basic configuration framework. In addition, by distributing configuration information into three types of files according to functional modules, the corresponding configuration module can be quickly located when troubleshooting and optimizing functions, without having to search through complex overall files. The unified integration logic makes the target configuration file structure clear, which makes it easier for developers to understand the configuration relationships, reduces maintenance costs, and supports the system to quickly load configurations and run stably.

[0055] In some embodiments, when calling at least one corresponding basic template file from a pre-set template library based on a target configuration scenario, the target configuration scenario can be determined first, and the corresponding basic template file can be selected based on the type of the target configuration scenario. Target configuration scenarios may include adding voice dialogue functionality, modifying existing function parameters, adding intent mapping relationships, etc.

[0056] The new voice dialogue function refers to adding a completely new voice control feature to the voice dialogue system. This function has no historical configuration records and requires complete configuration logic support. The basic template files are dialogue scenario template files, command template files, and intent-command mapping template files, which together constitute the complete configuration framework for the new function.

[0057] In practice, once the system determines that the target configuration scenario is the addition of a voice dialogue function, it automatically retrieves all three types of basic template files from the pre-set template library. The dialogue scenario template file is used to define the dialogue scenario and responsive intents of the new function; the instruction template file is used to configure the execution data and instruction identifiers of the new function; and the intent-instruction mapping template file is used to establish the relationship between the two, ensuring a closed loop throughout the entire process from intent recognition to instruction execution for the new function.

[0058] Modifying existing function parameters refers to adjusting the execution parameters of existing voice dialogue functions in the system, without changing the dialogue scenario definition or intent-command mapping relationship. The command template file stores the core execution data of the function and is the key carrier for parameter modification.

[0059] In practice, when the target configuration scenario involves modifying existing functional parameters, the system only calls the instruction template file from the template library. Developers do not need to manipulate the other two types of templates; they can directly modify the execution object, execution action, and other related parameters in the instruction template file to complete the parameter update of existing functions, avoiding redundant operations on unrelated templates and improving configuration efficiency.

[0060] Adding a new intent mapping relationship refers to establishing an association between a new intent and its corresponding instruction based on existing dialogue scenarios and instructions, without needing to add new dialogue scenarios or modify instruction parameters. The intent-instruction mapping template file is the dedicated carrier for implementing this association.

[0061] In practice, once the system identifies a new intent mapping relationship in the target configuration scenario, it only calls the intent-command mapping template file. Developers define new matching rules in this file, associating the new intent of the existing dialogue scenario with the corresponding command identifier, thus completing the new intent-command association configuration. This simplifies the configuration process as there is no need to modify the dialogue scenario template or command template.

[0062] On the one hand, when adding new voice dialogue functions, all three types of template files are called to ensure complete configuration logic support; when modifying existing function parameters, only the instruction template file is called, and when adding intent mapping relationships, only the intent-instruction mapping template file is called, avoiding the loading and operation of irrelevant templates, eliminating redundant configuration steps, shortening the configuration cycle, and meeting the needs of rapid iteration of intelligent cockpit voice functions. At the same time, template calls in different scenarios are all centered around core configuration requirements. When adding new functions, the three types of templates work together to build a complete link from intent recognition to instruction execution. When modifying parameters and adding mappings, the focus is on key templates, avoiding configuration logic loss or confusion caused by improper template calls, and ensuring that the voice dialogue system can accurately respond to configuration requirements. On the other hand, developers do not need to manually select the required templates. The system automatically matches and calls them according to the scenario, reducing the cost of manual judgment and selection, especially friendly to non-professional developers; at the same time, targeted calls avoid accidental operation of irrelevant templates, reduce the risk of configuration errors, and improve the configuration success rate. Meanwhile, when adapting to different configuration scenarios such as adding new features, modifying parameters, and adding mappings, there is no need to reconstruct the template library or adjust the overall configuration architecture, supporting rapid expansion and iterative upgrades of voice dialogue functions. Furthermore, the standardized logic for template calls facilitates subsequent adaptation to personalized voice interaction needs across multiple vehicle models and regions, improving the solution's versatility. Moreover, by categorizing templates by scenario, the usage scenarios of various template files are clearly defined, allowing for quick location of associated templates for corresponding configuration scenarios during later maintenance, avoiding chaotic use of template files, reducing maintenance difficulty, and ensuring the standardization and cleanliness of the template library.

[0063] To ensure the validity and availability of the target configuration file, after determining the target configuration file, it is also necessary to add configuration consistency verification and subsequent loading or error correction processes.

[0064] As an example, configuration consistency checks can be performed on the target configuration file. Configuration consistency checks include checking whether the reference relationships between the dialogue scenario template file, the instruction template file, and the intent-instruction mapping template file are correct.

[0065] For example, configuration consistency verification is a process of checking whether the association logic between the three types of basic template files in the target configuration file is accurate. The reference relationship refers to the corresponding association established through key information between the dialogue scenario template file, the instruction template file, and the intent-instruction mapping template file, which is the core of ensuring the consistency between intent recognition and instruction execution.

[0066] In practice, the system automatically initiates a verification process, focusing on checking the reference relationships among the three types of template files. For example, it checks whether the dialogue name referenced in the intent-instruction mapping template file exists in the dialogue scenario template file, whether the referenced instruction identifier exists in the instruction template file, and whether the intent name in the dialogue scenario template file matches the intent name in the mapping file.

[0067] If the verification passes, it means that the configuration logic of the target configuration file is correct. It is then loaded into the configuration management module of the voice dialogue system to make the configuration effective. The voice dialogue system can then respond to the user's voice commands based on the configuration file.

[0068] The configuration management module is the core unit in the voice dialogue system responsible for receiving, storing, and retrieving configuration files. It is used to manage various functional configurations and support the system in responding to user commands according to the configuration logic.

[0069] When the verification results show that the reference relationships of the three types of template files are correct and the configuration logic is error-free, the system automatically triggers the loading process. The target configuration file is transmitted to the configuration management module in a format supported by the voice dialogue system. After receiving the file, the module completes storage and registration, enabling the functional logic in the configuration file to take effect. The voice dialogue system can then recognize the user's intent and execute the corresponding commands based on the configuration file.

[0070] If the validation fails, it indicates that there are problems such as incorrect references or missing fields in the configuration file. A configuration error report will be generated and output. The error report will clearly indicate the error type and location, such as "The instruction identifier 'sys.car.window' referenced in the intent-instruction mapping template file does not exist in the instruction template file" or "The 'allowed' field in the dialogue scenario template file is missing the configuration intent name 'WindowOff'", to prompt the user to correct the error.

[0071] After determining the target configuration file, adding configuration consistency verification and subsequent loading or error correction processes can ensure the validity and availability of the target configuration file. On the one hand, the quality of the template file directly affects the performance of the voice dialogue system. Verification can identify configuration logic vulnerabilities in advance, avoid invalid configurations being loaded into the system and causing functional failures, and provide users with clear error guidance to ensure that the configuration file can accurately support the normal operation of the voice dialogue function, meeting the stable and reliable usage requirements of the intelligent cockpit voice system.

[0072] In this embodiment of the application, after determining the target configuration file, a process from receiving user vehicle function voice requests to generating control commands can be constructed based on the generated target configuration file.

[0073] First, the system receives voice input from the user, which describes the vehicle function requirement to be executed. For example, this voice input may be audio information entered by the user via a voice interaction device, describing the vehicle function requirement to be executed, and serves as the input source to trigger vehicle function control.

[0074] In practice, users can input voice messages describing their vehicle's functional needs using in-vehicle microphones or other voice input devices. The system receives this voice information through an audio acquisition module, performs preprocessing such as noise reduction and decoding on the audio data to ensure that the voice information is clear and identifiable, providing high-quality raw data for subsequent intent extraction.

[0075] Then, the control intent in the speech information can be extracted using a natural language understanding model.

[0076] For example, a natural language understanding model is an algorithmic model with speech semantic parsing capabilities, which can extract the core needs from speech information; control intent is the specific functional needs that the user expresses through voice and wants the vehicle to perform, which is the key to connecting voice input and function execution.

[0077] In practice, a natural language understanding model is invoked to perform semantic analysis on the preprocessed speech information. The model extracts key entities and operational commands from the speech, such as identifying the functional target and specific operational actions from the speech content. The extracted information is then matched with a pre-set vehicle function intent database to accurately determine the user's control intent.

[0078] Then, based on the control intent and the third configuration file in the target configuration file, the instruction identifier corresponding to the control intent is obtained.

[0079] For example, the first configuration file is a configuration file formed by filling parameters into the dialogue scenario template file, which is used to store the correspondence between dialogue scenarios and responsive intents; the dialogue scenario is an interaction scenario classification corresponding to vehicle functions, which is used to define the response range of control intents.

[0080] In practice, the system loads the first configuration file and, based on the determined control intent, retrieves the associated data of dialogue scenarios and intents stored in the file. It matches the dialogue scenario corresponding to the control intent and simultaneously confirms the range of responsive intents within that dialogue scenario, ensuring that the control intent is within the response range of the dialogue scenario and avoiding invalid intent matching.

[0081] Subsequently, in this dialogue scenario, instruction execution data is obtained based on the instruction identifier and the second configuration file.

[0082] For example, the second configuration file is a configuration file formed by filling parameters into the instruction template file, which stores the correspondence between instruction identifiers and instruction execution data; the instruction execution data are the core parameters required to execute vehicle functions, including the execution object and execution action, etc.

[0083] In practice, within the defined dialogue scenario, the system retrieves the second configuration file. Based on the acquired instruction identifier, it searches the file for the corresponding instruction execution data, extracting key information such as the execution object and execution action to ensure that the data can support the accurate execution of vehicle functions.

[0084] Finally, based on the instruction execution data, control instructions are generated to execute the control intent.

[0085] For example, control commands are operation commands generated by the system based on command execution data, which can be recognized and executed by the vehicle control system, and are the direct basis for driving the vehicle to complete functional actions.

[0086] In practice, the system integrates the extracted instruction execution data and, according to the instruction format requirements of the vehicle control system, transforms the execution object and execution action into standardized control instructions. The generated control instructions are transmitted to the corresponding functional control module of the vehicle, and the drive module executes the corresponding operation to respond to the user's voice requests.

[0087] On the one hand, the system extracts control intentions through a natural language understanding model, matches command identifiers with a third configuration file, locks the dialogue scenario based on the first configuration file, and obtains command execution data through a second configuration file, forming a closed-loop logic of "intent recognition - scenario matching - command extraction." This process ensures that user voice requests are accurately translated into executable vehicle control commands, avoiding misjudgment of intent or mismatch of commands, and significantly improving the response accuracy of voice control. On the other hand, with the target configuration file as the core basis, the three types of sub-files each perform their own functions and are logically closely related, making the voice control process standardized and regulated. The confirmation step of the dialogue scenario limits the scope of intent response and eliminates interference from invalid intents; the accurate matching of command identifiers and execution data ensures the effectiveness of control commands, reduces vehicle function execution failures, and improves the operational stability of the voice interaction system.

[0088] To achieve accurate matching between voice control intent and configuration file, and to support dynamic iteration of configuration file, in some embodiments, after extracting the control intent from the voice information through a natural language understanding model, the type of vehicle function requirement can also be determined based on the control intent.

[0089] For example, vehicle function requirement type is a vehicle function category divided according to control intent, covering common vehicle functions such as window control, seat adjustment, and air conditioning control, and is the core classification basis for distinguishing different voice control needs.

[0090] In practice, the system receives the extracted control intent and compares it with a pre-defined library of vehicle function requirement types. Based on the execution object and action contained in the control intent, it determines the type of function requirement it belongs to. For example, if the control intent contains information related to windows and opening them, it is determined to be a window control requirement.

[0091] Subsequently, based on the vehicle functional requirement type, at least one target configuration field corresponding to the vehicle functional requirement type is determined.

[0092] For example, the target configuration field is a configuration data field corresponding to a specific vehicle function requirement type. It is the core data carrier in the configuration file that supports the operation of this type of function. Different function requirement types correspond to different target configuration fields.

[0093] In practice, the system retrieves a pre-defined association library of functional requirement types and configuration fields, and extracts the corresponding target configuration fields based on the identified vehicle functional requirement types. For example, window control requirements correspond to object and action fields, while seat adjustment requirements correspond to object, position, and mode fields, ensuring that the extracted target configuration fields fully cover the control requirements of that type of function.

[0094] Next, based on the target configuration field, a query is performed in the target configuration file to see if a current configuration file matching the target configuration field exists. For example, the current configuration file is a file already stored in the target configuration file that contains various functional configuration data.

[0095] In practice, the system initiates a configuration file query program, using the target configuration fields as search criteria to traverse and query the target configuration files. It checks whether a file containing all the target configuration fields exists in the target configuration files, and verifies whether the field data matches the requirements of the control intent.

[0096] If a configuration file matching the target configuration fields exists in the target configuration file, the system extracts the instruction execution data from that configuration file. Following the instruction format specifications of the vehicle control system, the instruction execution data is converted into standardized control instructions. The generated control instructions are directly transmitted to the corresponding vehicle function control module, and the drive module executes the corresponding operation.

[0097] If no matching configuration file exists in the target configuration file set, the system automatically triggers a configuration file update process. Based on the identified target configuration fields, the corresponding field data is added to generate a new configuration file. The newly generated configuration file is then integrated into the target configuration file set, completing the target configuration file update. The updated target configuration file can be directly used to generate control commands for the current control intent, while also providing configuration support for subsequent similar functional requirements.

[0098] On one hand, by determining the type of vehicle function requirement through control intent, the system further narrows down the target configuration fields and uses these as search criteria to query matching configuration files. This process, through multi-level filtering, narrows down the matching range of configuration files, avoids invalid searches, and ensures that the generated control commands highly match user needs, significantly reducing the error rate of function execution due to configuration mismatch. On the other hand, for scenarios where there is no matching configuration file, the system can automatically update the target configuration file based on the target configuration fields to generate a new adapted configuration. This feature allows for rapid adaptation to newly added vehicle function voice control requirements without manual intervention to reconstruct the configuration architecture, meeting the needs of continuous iteration of smart cockpit functions and improving the system's scalability and flexibility.

[0099] The following example, "Configuring the voice control function for opening car windows," details the configuration file generation process: First, receive the configuration task, which includes the configuration intent information of "configure the voice control function for opening the car window"; Subsequently, based on this configuration intent information, the target configuration scenario is determined to be the addition of a voice dialogue function, the execution parameters are the execution object "car window", the execution action "open", the dialogue scenario is "car window", and the configuration intent is "WindowOn". Next, the dialog scene template file (RuleDialogModel.json), command template file (CommandModel.json), and intent-command mapping template file (IntentCmdMappingModel.json) are retrieved from the template library. In the RuleDialogModel.json file, if the "WindowDialog" dialog scene is detected, the template file corresponding to that dialog scene is used as the first configuration file. In the CommandModel.json file, the command name field is filled with "WindowControl", the command identifier field with "sys.car.crl", the object field with "car window", and the action field with "open", resulting in the second configuration file. In the IntentCmdMappingModel.json file, a mapping relationship is established between "WindowOn" and "sys.car.crl", resulting in the third configuration file. After verifying the consistency of the three configuration files and confirming the correct referencing relationships, the final "open car window" configuration file is loaded into the configuration management module of the voice dialogue system, completing the configuration of the "open car window" voice control function.

[0100] In this embodiment, after receiving the configuration task, the target configuration scenario and execution parameters corresponding to the configuration intent information in the configuration task are used. Then, based on the target configuration scenario, three types of basic template files—dialogue scenarios, commands, and intent-command mappings—are called from a pre-set template library, and the execution parameters are filled into the corresponding fields of the basic template files, thereby generating the target configuration file. On one hand, this method uses configuration intent information as its core, directly determining the target configuration scenario and execution parameters. The execution parameters cover key elements such as the execution object, execution action, dialogue scenario, and corresponding intent, ensuring that the configuration direction highly matches user needs. Simultaneously, calling template files based on scenario differences avoids loading redundant templates, reduces invalid configuration steps, and significantly improves configuration accuracy. On the other hand, by using dialogue scenario template files (RuleDialogModel.json), command template files (CommandModel.json), and intent-command mapping template files (IntentCmdMappingModel.json), the configuration process is transformed into a standardized configuration of intent analysis, template invocation, and parameter filling. This effectively replaces the traditional complex code writing mode, allowing non-professional developers to participate in configuration and significantly lowering the development threshold of voice dialogue systems. Furthermore, the template files can be flexibly selected based on the target configuration scenario, improving configuration flexibility. In addition, by centralizing dialogue configuration in file templates, it facilitates later maintenance and upgrades, improving the accuracy and stability of the configuration.

[0101] Based on the configuration file generation method provided in the above embodiment, this application also provides a configuration file generation apparatus, as described in the following embodiments.

[0102] First see Figure 3 The configuration file generation apparatus 300 provided in this application embodiment includes: The receiving module 301 is used to receive a configuration task, which includes configuration intent information. The determination module 302 is used to determine the target configuration scenario and execution parameters based on the configuration intent information; the execution parameters include at least one of the following: execution object, execution action, dialogue scenario, and intent corresponding to the dialogue scenario; Module 303 is used to call at least one basic template file from a pre-set template library based on the target configuration scenario; the basic template files include: dialogue scenario template file, instruction template file, and intent-instruction mapping template file; The fill module 304 is used to fill the execution parameters into the corresponding fields of the base template file to determine the target configuration file.

[0103] In some possible implementations, fill module 304 is also used for: The dialogue scenario is populated into the dialogue scenario field of the dialogue scenario template file, and the intent is populated into the intent field of the dialogue scenario template file to obtain the first configuration file; Fill the execution object and / or execution action into the instruction execution data field of the instruction template file to obtain the second configuration file; The intention-instruction mapping template file establishes a mapping relationship between intentions and instruction identifiers in the instruction template file, resulting in a third configuration file; The target configuration file is determined based on the first configuration file, the second configuration file, and the third configuration file.

[0104] In some possible implementations, calling module 303 is also used for: When the target configuration scenario is to add a voice dialogue function, the dialogue scenario template file, command template file, and intent-command mapping template file are called from the preset template library; When the target configuration scenario involves modifying existing functional parameters, the instruction template file is called from the preset template library; When the target configuration scenario involves adding a new intent mapping relationship, the intent-instruction mapping template file is called from the preset template library.

[0105] In some possible implementations, fill module 304 is also used for: Check if a dialogue scenario exists in the dialogue scenario template file; If a dialogue scenario exists in the dialogue scenario template file, the template file corresponding to the dialogue scenario will be used as the first configuration file. If no dialogue scenario exists in the dialogue scenario template file, a new dialogue scenario is created, and the intent is populated into the intent field of the new dialogue scenario to obtain the first configuration file.

[0106] In some possible implementations, the instruction execution data fields include: object fields and action fields; Fill module 304 is also used for: The second configuration file is obtained by populating the execution object into the object field and the execution action into the action field.

[0107] In some possible implementations, after the target configuration file is determined, the configuration file generation device 300 further includes: a verification module; The verification module is used to verify the configuration consistency of the target configuration file. The configuration consistency verification includes checking whether the reference relationship between the dialogue scenario template file, the instruction template file, and the intent-instruction mapping template file is correct. If the verification passes, the target configuration file will be loaded into the configuration management module of the voice dialogue system; If the verification fails, a configuration error report will be generated and output to prompt the user to make corrections.

[0108] In some possible implementations, after determining the target configuration file, the receiving module 301 is further configured to: Receive voice information input from the user, which describes the vehicle function requirements to be executed; Extracting control intent from speech information using natural language understanding models; Based on the control intent and the third configuration file in the target configuration file, obtain the instruction identifier corresponding to the control intent; Based on the control intent and the first configuration file in the target configuration file, determine the dialogue scenario corresponding to the control intent and the intent corresponding to the dialogue scenario. In the dialogue scenario, based on the instruction identifier and the second configuration file in the target configuration file, the instruction execution data corresponding to the instruction identifier is obtained; Based on the instruction execution data, control instructions are generated to execute the control intent.

[0109] After extracting the control intent from the speech information using a natural language understanding model, the determination module 302 is further used for: Determine the type of vehicle functional requirements based on control intent; Based on the vehicle functional requirement type, determine at least one target configuration field corresponding to the vehicle functional requirement type; Based on the target configuration field, query the target configuration file to see if there is a current configuration file that matches the target configuration field; If a configuration file matching the target configuration field exists in the target configuration file, control instructions for executing the control intent are generated based on the configuration file. If no matching target configuration file exists in the target configuration file, update the target configuration file based on the target configuration field to generate a target configuration file that matches the target configuration field.

[0110] The various modules of the configuration file generation device provided in this application embodiment can achieve Figure 1 It provides functionality for each step of the configuration file generation method and achieves the corresponding technical effects. For the sake of brevity, it will not be elaborated here.

[0111] Based on the above configuration file generation method, this application embodiment also provides a configuration file generation device 400, such as... Figure 4 As shown, the configuration file generation device 400 includes a processor 401 and a memory 402 storing computer program instructions; when the processor 401 executes the computer program instructions, it implements the configuration file generation method described above.

[0112] Based on the above configuration file generation method, this application embodiment also provides a computer-readable storage medium storing computer program instructions, which, when executed by a processor, implement the configuration file generation method described above.

[0113] Based on the above configuration file generation method, this application embodiment also provides a computer program product, wherein when the instructions in the computer program product are executed by the processor of an electronic device, the electronic device is able to execute the configuration file generation method as described above.

[0114] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0115] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0116] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A method for generating a configuration file, characterized in that, include: Receive a configuration task, the configuration task including configuration intent information; Based on the configuration intent information, the target configuration scenario and execution parameters are determined; The execution parameters include at least one of the following: execution object, execution action, dialogue scenario, and intent corresponding to the dialogue scenario; Based on the target configuration scenario, at least one corresponding basic template file is called from the preset template library; The basic template files include: dialogue scenario template files, instruction template files, and intent-instruction mapping template files; The execution parameters are filled into the corresponding fields of the base template file to determine the target configuration file.

2. The method according to claim 1, characterized in that, The step of filling the execution parameters into the corresponding fields of the basic template file to determine the target configuration file includes: The dialogue scenario is filled into the dialogue scenario field of the dialogue scenario template file, and the intent is filled into the intent field of the dialogue scenario template file to obtain the first configuration file; The execution object and / or execution action are filled into the instruction execution data field of the instruction template file to obtain the second configuration file; A mapping relationship is established between the intent and the instruction identifier in the instruction template file in the intent-instruction mapping template file to obtain a third configuration file; The target configuration file is determined based on the first configuration file, the second configuration file, and the third configuration file.

3. The method according to claim 2, characterized in that, The step of calling at least one corresponding basic template file from a pre-set template library based on the target configuration scenario includes: When the target configuration scenario is to add a voice dialogue function, the dialogue scenario template file, the instruction template file, and the intent-instruction mapping template file are called from the preset template library; When the target configuration scenario involves modifying existing functional parameters, the instruction template file is called from the preset template library; When the target configuration scenario involves adding a new intent mapping relationship, the intent-instruction mapping template file is called from the preset template library.

4. The method according to claim 2, characterized in that, The step of filling the dialogue scene into the dialogue scene field of the dialogue scene template file and filling the intent into the intent field of the dialogue scene template file to obtain the first configuration file includes: Check if the dialogue scenario exists in the dialogue scenario template file; If the dialogue scenario exists in the dialogue scenario template file, the template file corresponding to the dialogue scenario shall be used as the first configuration file. If the dialogue scenario does not exist in the dialogue scenario template file, a new dialogue scenario is created, and the intent is filled into the intent field of the new dialogue scenario to obtain the first configuration file.

5. The method according to claim 2, characterized in that, The instruction execution data fields include: an object field and an action field; The step of filling the execution object and / or execution action into the instruction execution data field of the instruction template file to obtain the second configuration file includes: The execution object is populated into the object field, and the execution action is populated into the action field to obtain the second configuration file.

6. The method according to any one of claims 1-5, characterized in that, After determining the target configuration file, the following is also included: The target configuration file is subjected to a configuration consistency check, which includes checking whether the reference relationship between the dialogue scenario template file, the instruction template file, and the intent-instruction mapping template file is correct. If the verification passes, the target configuration file will be loaded into the configuration management module of the voice dialogue system; If the verification fails, a configuration error report will be generated and output to prompt the user to make corrections.

7. The method according to claim 2, characterized in that, After determining the target configuration file, the method further includes: Receive voice information input by the user, the voice information being used to describe the vehicle function requirements to be executed; The control intent is extracted from the speech information using a natural language understanding model; Based on the control intent and the third configuration file in the target configuration file, obtain the instruction identifier corresponding to the control intent; Based on the control intent and the first configuration file in the target configuration file, determine the dialogue scenario corresponding to the control intent and the intent corresponding to the dialogue scenario. In the dialogue scenario, based on the instruction identifier and the second configuration file in the target configuration file, instruction execution data corresponding to the instruction identifier is obtained; Based on the instruction execution data, control instructions for executing the control intent are generated.

8. The method according to claim 7, characterized in that, After extracting the control intent from the speech information using a natural language understanding model, the method further includes: The vehicle functional requirement type is determined based on the control intent; Based on the vehicle functional requirement type, determine at least one target configuration field corresponding to the vehicle functional requirement type; Based on the target configuration field, query the target configuration file to see if there is a current configuration file that matches the target configuration field; If a configuration file matching the target configuration field exists in the target configuration file, a control instruction for executing the control intent is generated based on the configuration file; If no configuration file matching the target configuration field exists in the target configuration file, the target configuration file is updated based on the target configuration field to generate a target configuration file matching the target configuration field.

9. A configuration file generation apparatus, characterized in that, The device includes: A receiving module is used to receive a configuration task, wherein the configuration task includes configuration intent information; The determination module is used to determine the target configuration scenario and execution parameters based on the configuration intent information; the execution parameters include at least one of the following: execution object, execution action, dialogue scenario, and intent corresponding to the dialogue scenario; The calling module is used to call at least one corresponding basic template file from a preset template library based on the target configuration scenario; the basic template files include: dialogue scenario template files, instruction template files, and intent-instruction mapping template files; The fill module is used to fill the execution parameters into the corresponding fields of the base template file to determine the target configuration file.

10. A configuration file generation device, characterized in that, The device includes: a processor and a memory storing computer program instructions; the processor, when executing the computer program instructions, implements the configuration file generation method as described in any one of claims 1-8.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the configuration file generation method as described in any one of claims 1-8.

12. A computer program product, characterized in that, When the instructions in the computer program product are executed by the processor of the electronic device, the electronic device is able to perform the configuration file generation method as described in any one of claims 1-8.

Images