An information updating method and device, a storage medium and an electronic device

Abstract

The application relates to an information updating method and device, a storage medium and an electronic equipment, and relates to the technical field of information updating.The application comprises the following steps: in the case that there is a semantic conflict between description information of at least two executable function files corresponding to an interactive intelligent agent, updating the description information according to semantic conflict information of the description information, so that there is no semantic conflict between the description information of the at least two target executable function files.Compared with the related art, the application can update the description information according to the semantic conflict information of the description information in the case that there is a semantic conflict between the description information of the at least two executable function files corresponding to the interactive intelligent agent, so that there is no semantic conflict between the description information of the at least two target executable function files, thereby improving the semantic matching accuracy of the description information.

Description

Technical Field

[0001] This application relates to the field of information updating technology, specifically to an information updating method, apparatus, storage medium, and electronic device. Background Technology

[0002] In related technologies, when an interactive intelligent agent corresponds to at least two executable function files, the description information of different function files is prone to semantic conflicts, resulting in low accuracy of executable function file invocation. Summary of the Invention

[0003] In view of this, this application provides an information updating method, apparatus, storage medium and electronic device, the main purpose of which is to improve the technical problem in the related art that the description information of different functional files is prone to semantic conflicts, resulting in low accuracy of executable functional file calls.

[0004] Firstly, this application provides an information updating method, including:

[0005] In the event of a semantic conflict between the description information of at least two executable function files corresponding to the interactive agent, the description information is updated based on the semantic conflict information of the description information so that there is no semantic conflict between the description information of the at least two target executable function files.

[0006] Optionally, the description information is the function description information corresponding to the executable function file, and the function description information includes information on the executable functions of the executable function file and information on the non-executable functions of the executable function file.

[0007] Optionally, the semantic conflict information is obtained based on the existence of semantic overlap or similar descriptive information between the descriptive information of at least two executable function files.

[0008] Optionally, the semantic conflict information includes at least one of the semantically overlapping or similar descriptive keywords, the attribution information of the semantically overlapping or similar descriptive keywords, and the severity of the semantic conflict, wherein the attribution information is used to indicate the executable function file to which the semantically overlapping or similar descriptive keywords belong.

[0009] Optionally, the executable function file is used by the terminal device to execute the target function, and the executable function file includes at least one of the function description information corresponding to the target function and the applicable scenario information of the target function.

[0010] Optionally, updating the description information based on the semantic conflict information of the description information includes: Based on the semantic conflict information of the description information, the semantic coverage of the description information is narrowed in order to update the description information.

[0011] Optionally, the step of narrowing the semantic coverage of the description information based on the semantic conflict information of the description information includes: Based on the semantic conflict information of the description information, the scope information corresponding to each executable function file is obtained. The scope information is at least one of the following: functional domain information used to determine the unprocessable functional file of the executable function file and functional execution boundary information of the executable function file. Based on the range information and the description information, the semantic coverage of the description information is narrowed.

[0012] Optionally, the step of narrowing the semantic coverage of the description information based on the semantic conflict information of the description information includes: Based on the semantic conflict information in the description information, obtain the target functional domain information that each executable functional file can process; Based on functional domain information other than the target functional domain information in the description information, the semantic coverage of the description information is narrowed.

[0013] Optionally, the method includes: Based on the semantic content and scene association information in the semantically overlapping or similar descriptive keywords, the attribution information of the semantically overlapping or similar descriptive keywords is determined, and the scene association information is the functional scene information adapted to the semantic content in the semantically overlapping or similar descriptive keywords.

[0014] Optionally, updating the description information includes: Determine the target baseline description information from the description information; Update the description information other than the target baseline description information.

[0015] Optionally, updating the description information based on the semantic conflict information of the description information includes: If the number of updates to the description information is not higher than the target update number threshold, the description information is updated based on the semantic conflict information of the description information.

[0016] Optionally, the method includes: Based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive intelligent agent, it is determined that there is a semantic conflict between the description information of at least two executable function files.

[0017] Optionally, determining a semantic conflict between the description information of at least two executable function files based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive intelligent agent includes: In response to a change in the configuration information of at least one executable function file, a semantic conflict is determined to exist between the description information of at least two executable function files based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive agent.

[0018] Optionally, the configuration information of the executable function files includes at least the quantity information of the executable function files and the description information of the executable function files.

[0019] Secondly, this application provides an information updating device, comprising: The update module is configured to update the description information based on the semantic conflict information of the description information when there is a semantic conflict between the description information of at least two executable function files corresponding to the interactive agent, so that there is no semantic conflict between the description information of the at least two target executable function files.

[0020] Thirdly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the information update method described in the first aspect.

[0021] Fourthly, this application provides an electronic device, including a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, wherein the processor executes the computer program to implement the information update method described in the first aspect.

[0022] Fifthly, this application provides a vehicle or robot, including the control device described in the second aspect, or the electronic device described in the fourth aspect.

[0023] By employing the above technical solutions, this application provides an information updating method, apparatus, storage medium, and electronic device, comprising: updating the description information according to the semantic conflict information of the description information when there is a semantic conflict between the description information of at least two executable functional files corresponding to an interactive intelligent agent, so as to eliminate the semantic conflict between the description information of the at least two target executable functional files. Compared with related technologies, this application can update the description information according to the semantic conflict information of the description information when there is a semantic conflict between the description information of at least two executable functional files corresponding to an interactive intelligent agent, so as to eliminate the semantic conflict between the description information of the at least two target executable functional files. This allows the application to update the description information through the semantic conflict information of at least two description information to eliminate the semantic conflict between the description information of different functional files, thereby improving the accuracy of executable functional file invocation.

[0024] The above description is only an overview of the technical solution of this application. In order to better understand the technical means of this application and to implement it in accordance with the contents of the specification, and to make the above and other objects, features and advantages of this application more obvious and understandable, the following are specific embodiments of this application. Attached Figure Description

[0025] The accompanying drawings, which are included to provide a further understanding of this disclosure and form part of this disclosure, illustrate exemplary embodiments of the present disclosure and are used to explain the disclosure, but do not constitute an undue limitation of the disclosure. In the drawings: Figure 1 A flowchart illustrating an information updating method provided in an embodiment of this disclosure is shown. Figure 2 A flowchart illustrating an information updating method provided in an embodiment of this disclosure is shown. Figure 3 A flowchart illustrating yet another information updating method provided in an embodiment of this disclosure is shown; Figure 4 A flowchart illustrating another information updating method provided in an embodiment of this disclosure is shown; Figure 5 A schematic diagram of the structure of an information updating device provided in an embodiment of this disclosure is shown; Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of this disclosure is shown. Detailed Implementation

[0026] To better understand the above-mentioned objectives, features, and advantages of this application, the solution of this application will be further described below. It should be noted that, unless otherwise specified, the embodiments and features described in these embodiments can be combined with each other.

[0027] To address the technical problem in related technologies where, when an interactive agent corresponds to at least two executable function files, semantic conflicts easily arise in the description information of different function files, leading to low accuracy in calling executable function files, this embodiment provides an information updating method, such as... Figure 1 As shown, the method includes: Step 101: If there is a semantic conflict between the description information of at least two executable function files corresponding to the interactive agent, update the description information according to the semantic conflict information of the description information so that there is no semantic conflict between the description information of at least two target executable function files.

[0028] It should be noted that the execution subject of the embodiments of this application can be a terminal device, wherein the terminal device can be a human-carrying terminal device, for example, the terminal device can include, but is not limited to, a vehicle, a human-carrying robot, a humanoid robot, etc.; wherein, when the terminal device is a vehicle, the vehicle can be a vehicle of different drive types, such as an electric vehicle, a fuel vehicle, etc.; the vehicle can also be a vehicle of different models, such as a sedan, a commercial vehicle, etc.

[0029] In some examples, the interactive agent can be an artificial intelligence entity with multifunctional collaborative interaction capabilities. For example, the interactive agent can include, but is not limited to, intelligent customer service robots, home AI agents, office digital employees, embedded interactive robots, and so on.

[0030] In some examples, each executable file corresponds to a description.

[0031] In some examples, executable function files are used by terminal devices to execute target functions based on user instructions.

[0032] In some examples, the descriptive information can be semantic text content such as the scope of functions and services corresponding to the executable function file, function execution rules, scenario adaptation boundaries, and capability and responsibility descriptions; for example, the scope of executable functions, the scope of non-responsive or non-executable functions, and the applicable scenarios of functions corresponding to each executable function file are all part of the descriptive information in this application, and will not be listed one by one here.

[0033] In some examples, semantic conflicts can be abnormal semantic situations such as overlapping semantic scope between different executable function files, similar function descriptions, contradictory division of responsibilities, and ambiguous instruction matching. For example, if at least two executable function files have similar function descriptions and overlap in their descriptions of the same business scenario, then the two descriptions are determined to have semantic conflicts.

[0034] In some examples, semantic conflict information may include information such as semantically overlapping or similar descriptive information, attribution information of semantically overlapping or similar descriptive information, and the severity of semantic conflict.

[0035] In some examples, updating description information can be an optimization process that adjusts semantics, narrows scope, supplements boundaries, and simplifies content for description information that has semantic conflicts. For example, if there are semantic overlaps and conflicts between the description information of at least two executable function files, the way to update the description information can include, but is not limited to, narrowing the semantic coverage of the description information of each executable function file, dividing the functional domain of the executable function file, supplementing the functional boundaries of the executable function file, and eliminating redundant and overlapping semantic content, etc., which will not be listed one by one here.

[0036] Optionally, the description information is the function description information corresponding to the executable function file. The function description information includes information on the executable functions of the executable function file and information on the non-executable functions of the executable function file.

[0037] In some examples, the information about the executable functions that the executable function file can perform may include, but is not limited to, the scope of the executable function file's functions and services, the types of instructions that the executable function file can respond to, the business permissions that the executable function file can handle, and the scenarios that the executable function file can adapt to, etc., without specific limitations here.

[0038] For example, based on the information of the executable functions of an executable function file, the types of tasks and service scenarios that the executable function file can handle can be determined according to the corresponding function content.

[0039] As an optional approach, the information of the executable functions in the embodiments of this application can be positive semantic information, such as including but not limited to regular question and answer processing, scene interaction response, etc. For example, if the executable function file is a weather query function file, the information of the executable functions of the weather query function file includes: being able to query the real-time weather of cities across the country, the weather forecast for the next 7 days, and being able to respond to instructions such as "What's the weather like today?" and "Will it get colder tomorrow?", etc., and will not be listed one by one here.

[0040] In some examples, the information about functions that the executable file cannot execute may include, but is not limited to, the functional areas that the executable file prohibits from responding to, scenarios that are beyond the capabilities of the executable file, business types that the executable file refuses to process, invalid triggering instructions of the executable file, etc., without being specifically limited here.

[0041] For example, based on information about functions that cannot be executed by an executable function file, the relevant business and scope of application that the executable function file cannot respond to or process can be determined according to the corresponding content.

[0042] As an optional approach, the functional areas that the executable file in this application embodiment cannot respond to may include, but are not limited to, refusing to respond to illegal content, blocking instructions unrelated to the current executable file's function, and not processing scenarios exceeding the functional boundaries of the current executable file. For example, taking the aforementioned weather query function file as an example, the information regarding the non-executable functions of the weather query function file includes: not processing non-weather-related tasks such as stock queries and express delivery tracking; not responding to irrelevant instructions such as "check today's stocks" or "where is my express delivery?"; and being unable to predict long-term weather forecasts exceeding 14 days. These will not be listed in detail here.

[0043] Optionally, semantic conflict information is obtained based on semantic overlap or similarity in the description information of at least two executable function files.

[0044] In some examples, semantic conflict information is obtained based on semantically overlapping description information between the description information of at least two executable function files. The semantically overlapping description information is that the description information of at least two executable function files has the same functional keywords, the same service scenario, or the same response rules. For example, when the description information of at least two executable function files includes functional keywords (weather query), it can be determined that there is semantically overlapping description information between the description information of at least two executable function files.

[0045] In some examples, semantic conflict information is obtained based on the existence of semantically similar descriptive information between the description information of at least two executable function files. The semantically similar descriptive information refers to the description information between different executable function files that is not completely overlapping in semantics, but is semantically similar, has blurred boundaries, and is likely to cause confusion in instruction matching. For example, when the functional keywords in the description information of one executable function file include daily questions and answers, and the functional keywords in the description information of another executable function file include answers to common sense questions, it can be determined that there is semantically similar descriptive information between the description information of at least two executable function files.

[0046] Optionally, the semantic conflict information includes at least one of semantically overlapping or similar descriptive keywords, attribution information of semantically overlapping or similar descriptive keywords, and the severity of the semantic conflict, wherein the attribution information is used to indicate the executable function file to which the semantically overlapping or similar descriptive keywords belong.

[0047] In the embodiments of this application, semantically overlapping or similar descriptive keywords may include, but are not limited to, repeated functional terms, similar-meaning business terms, common scenario keywords, shared instruction triggering terms, etc., between different executable function files, and are not specifically limited here. For example, the description information of the aforementioned weather query function file and life service function file may both contain descriptive keywords such as temperature and forecast. These repeated words are semantically overlapping descriptive keywords; the question-and-answer consultation function file contains descriptive keywords for answering questions, and the common sense service function file contains descriptive keywords for answering questions. These descriptive keywords with similar meanings are semantically similar descriptive keywords, and will not be listed one by one here.

[0048] In this embodiment, the attribution information is used to indicate the executable function file to which semantically overlapping or similar descriptive keywords belong. This can include determining which executable function file exclusively matches the semantically overlapping or similar descriptive keywords, prioritizing high-frequency business functions, determining the belonging executable function file based on scenario adaptation relationships, etc. For example, if the descriptive keyword "weather forecast" appears in two executable function files, the attribution information for "weather forecast" clearly indicates that the keyword belongs to a weather query executable function file, rather than a daily question-and-answer executable function file. Further examples are not provided here.

[0049] In the embodiments of this application, the severity of semantic conflicts may include, but is not limited to, mild semantic overlap, moderate boundary overlap, severe conflict of rights and responsibilities, etc. For example, the severity of semantic conflicts can be classified according to the number of overlapping descriptive keywords, the semantic interference range of descriptive keywords, and the probability of instruction matching errors, without specific limitations here. For example, when only a small number of common descriptive keywords overlap, it is determined to be a mild semantic conflict; when a large number of core functional descriptive keywords overlap, it is determined to be a moderate semantic conflict; and when the descriptive keywords of key businesses completely overlap and cannot be distinguished, it is determined to be a severe semantic conflict.

[0050] Compared with related technologies, this embodiment can improve the pertinence and accuracy of description information updates and optimizations by extracting semantically overlapping or similar descriptive keywords, the attribution information of semantically overlapping or similar descriptive keywords, and the severity of semantic conflicts, thereby improving the accuracy of executable function file calls.

[0051] Optionally, the executable function file is used by the terminal device to execute the target function. The executable function file includes at least one of the function description information corresponding to the target function and the applicable scenario information of the target function.

[0052] In some examples, the target function may include, but is not limited to, different business functions possessed by the interactive intelligent agent within the terminal device. For example, the target function may be a travel query function, an encyclopedia Q&A function, a weather query function, etc., and will not be listed one by one here.

[0053] As an optional approach, the target function may include multiple sub-functions. For example, the travel query function may include sub-functions such as route planning and weather query, without being specifically limited here.

[0054] In some examples, the function description information corresponding to the target function may include, but is not limited to, the target function execution rules, the function execution scope, the scope in which the function cannot be executed, etc. For example, if the target function is a weather query function, the function description information corresponding to the target function may include the time period that the weather query function can query, the region that can be queried, etc., without specific limitations here.

[0055] In some examples, the applicable scenario information for the target function refers to information such as the application environment, usage context, and business scenario to which the target function is adapted, which may include, but is not limited to, daily home scenarios, travel scenarios, in-vehicle interaction scenarios, nighttime use scenarios, consultation scenarios, etc.; no specific limitations are made here. If the target function is a travel query function, the applicable scenario information for the target function may include commuting planning, route query, travel weather reference, travel itinerary arrangement, etc.; if the target function is an encyclopedia Q&A function, the applicable scenario information for the target function may include knowledge consultation, common sense popularization, information query, daily question answering, etc., and will not be listed one by one here.

[0056] Optionally, when performing the action of "updating the description information based on semantic conflict information," the following methods may be used, but are not limited to: Based on the semantic conflict information of the description information, the semantic coverage of the description information is narrowed in order to update the description information.

[0057] In this application embodiment, the semantic coverage is the entire semantic content boundary that a single executable function file can cover, adapt to, or respond to; for example, if there is a semantic conflict between the description information of at least two executable function files, it is necessary to perform convergence and reduction processing on the semantic coverage of the description information of the executable function files.

[0058] For example, if there is a semantic conflict between the description information of only two executable function files, the semantic coverage of one of the description information can be reduced, or the semantic coverage of both description information can be reduced simultaneously. If there is a semantic conflict between the description information of three executable function files, the semantic coverage of at least one of the description information needs to be reduced, or the semantic coverage of both description information can be reduced simultaneously, and so on. No further examples will be given here.

[0059] For example, when the executable function file is a travel query function file and the semantic coverage of the corresponding description information includes, but is not limited to, route planning, weather reference, and ticketing information, it is necessary to reduce the semantic content that is repetitive or similar to other executable function files; for example, when there is a semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file, the semantic coverage of the description information of the encyclopedia Q&A function file can be reduced.

[0060] As an optional approach, semantic coverage reduction processing can include, but is not limited to, narrowing the boundaries of general broad semantic content, eliminating overlapping semantic content, and determining the specific functions of executable function files. For example, when the semantic coverage of descriptive information is too large and causes semantic conflicts, the semantic content of non-core functions of the current executable function file can be reduced. When the semantic boundaries of at least two executable function files are blurred and cause semantic conflicts, the specific semantic scope of each executable function file can be determined, and so on. No further examples will be given here.

[0061] As an alternative approach, the updated description information can be a description information with a narrowed semantic scope; for example, after the description information of the travel query function file is reduced to include redundant information-related semantic content, only description information related to routes, traffic conditions, and travel weather is retained; after the description information of the encyclopedia Q&A function file is reduced to include cross-border semantic content related to travel, only semantic content related to knowledge popularization and common sense answers is retained.

[0062] Optionally, when performing the step of "shrinking the semantic coverage of the description information based on semantic conflict information," the following methods can be used, but are not limited to them, such as... Figure 2 As shown, the method includes: Step 201: Based on the semantic conflict information of the description information, obtain the scope information corresponding to each executable function file. The scope information is at least one of the following: the functional domain information used to determine the unprocessable functional file and the functional execution boundary information of the executable function file.

[0063] In this embodiment of the application, the information on the functional domains that the executable functional file cannot process is used to determine the scope of the executable functional file that is prohibited from responding. The information on the functional domains that cannot be processed can be business domains that each executable functional file is not authorized to process, does not require a response to, or is unrelated to the current function.

[0064] For example, when the executable file is a travel query function file, the unprocessable functional domain information can be related to life encyclopedia knowledge answers and common sense Q&A; when the executable file is an encyclopedia Q&A function file, the unprocessable functional domain information can be related to travel tickets and stocks, and so on.

[0065] In this embodiment of the application, the function execution boundary information of the executable function file is used to determine the maximum service coverage of the executable function file.

[0066] For example, the function execution boundary information can be the maximum functional range and scenario upper limit that each executable function file can adapt to. For instance, in the case where there is a semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file, the description information of the travel query function file can be clearly defined to only cover the boundaries of travel-related businesses, and the description information of the encyclopedia Q&A function file can only cover the boundaries of knowledge popularization businesses. In this way, the functional ranges of the description information of the travel query function file and the description information of the encyclopedia Q&A function file that do not overlap or only partially overlap are divided.

[0067] Step 202: Based on the scope information and description information, narrow the semantic coverage of the description information.

[0068] In this embodiment of the application, based on the unprocessable functional domain information and / or functional execution boundary information in the scope information, the semantic content in the description information that exceeds the functional execution boundary, belongs to the unprocessable domain, or conflicts with other files is deleted or optimized, while retaining the semantic content exclusive to each executable functional file.

[0069] For example, based on the obtained scope information, the conflict semantic range can be reduced and the broad semantic boundaries can be tightened. For instance, if the description information of the travel query function file cannot process encyclopedia-related information, the common sense semantic content in the description information of the travel query function file can be reduced; if the description information of the encyclopedia Q&A function file cannot process travel navigation-related information, the road condition and route-related semantic content in the description information of the encyclopedia Q&A function file can be reduced, and so on. No further examples will be given here.

[0070] Compared with related technologies, this embodiment shrinks the semantic coverage of at least two descriptive information based on range information and description information, making the semantic coverage of the description information of each executable function file more accurate. This avoids confusion in the matching of interactive agent instructions and improves the accuracy of calling the executable function file corresponding to the interactive agent.

[0071] Optionally, when performing the step of "shrinking the semantic coverage of the description information based on semantic conflict information," the following methods can be used, but are not limited to them, such as... Figure 3 As shown, the method includes: Step 301: Based on the semantic conflict information in the description information, obtain the target functional domain information that each executable functional file can process; In this embodiment of the application, the target functional domain information is the primary processing functional domain information among the functional domain information that the executable functional file can process. The functional domain information other than the target functional domain information may include secondary processing functional domain information that the executable functional file can process and functional domain information that the executable functional file cannot process.

[0072] In this embodiment of the application, by obtaining the target functional domain information that each executable functional file can process, the main functional domain information that each executable functional file processes can be determined.

[0073] Step 302: Based on the functional domain information other than the target functional domain information in the description information, the semantic coverage of the description information is narrowed.

[0074] In this embodiment of the application, if there is a semantic conflict between the description information of at least two executable functional files, it is determined whether the semantic conflict information is the main processing functional domain information of each executable functional file. If not, the semantic coverage of at least two description information can be narrowed according to the functional domain information other than the target functional domain information in the description information.

[0075] For example, taking the semantic conflict between the description information of two executable functional files as an example, if the semantic conflict information is information in the main processing functional domain information of one executable functional file and information in the secondary processing functional domain information of the other executable functional file, then the semantic coverage of at least two description information can be narrowed based on the functional domain information other than the target functional domain information in the description information. That is, by removing the functional domain information other than the target functional domain information in the description information, the semantic coverage of at least two description information can be narrowed.

[0076] For example, in the case of a semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file, the description information of the travel query function file includes information such as route planning, travel weather, general knowledge, and train / ticket information. The corresponding target functional domain information is travel-related information, namely route planning, travel weather, general knowledge, and train / ticket information. In this case, general knowledge belongs to a functional domain information outside the target functional domain information. The semantic coverage of the description information of the travel query function file can be narrowed by removing the semantic content related to general knowledge. On the other hand, the description information of the encyclopedia Q&A function file includes information such as general knowledge, popular science knowledge, travel route reference, and cultural consultation. The corresponding target functional domain information is knowledge and popular science related information, namely general knowledge, popular science knowledge, and cultural consultation. In this case, travel route reference belongs to a functional domain information outside the target functional domain information. The semantic coverage of the description information of the encyclopedia Q&A function file can be narrowed by removing the semantic content related to travel route reference.

[0077] Compared with related technologies, this embodiment shrinks the semantic coverage of at least two description information by using functional domain information other than the target functional domain information in the description information. The semantic coverage of the shrunken description information mainly covers the target functional domain information of the current executable file and does not involve the target functional domain information of other executable files. This can avoid confusion in the matching of interactive agent instructions and thus improve the accuracy of the executable functional file call corresponding to the interactive agent.

[0078] Optionally, this embodiment may also employ the following method, but not limited thereto: determining semantic conflict information of at least two description information based on semantically overlapping or similar description keywords between description information of at least two executable functional files, and the attribution information of the description keywords.

[0079] In the embodiments of this application, semantically overlapping or similar descriptive keywords are keywords in the descriptive information that are semantically easily confused.

[0080] In this embodiment of the application, semantic conflict information of at least two descriptive information is determined by extracting the same or similar descriptive keywords from at least two descriptive information and then obtaining the executable function file to which the semantically overlapping or similar descriptive keywords belong.

[0081] In this embodiment of the application, semantic conflict information of at least two descriptions can also be determined based on semantic overlap or similarity of description keywords between descriptions of at least two executable functional files, the attribution information of the description keywords, and the severity of semantic conflict.

[0082] For example, both the description information of the travel query function file and the description information of the encyclopedia Q&A function file contain the descriptive keyword "weather," which is a semantically overlapping descriptive keyword. Based on the attribution information, it is determined that "weather" belongs to the travel query function file and not to the encyclopedia Q&A function file. Based on the descriptive keyword "weather" and the fact that "weather" belongs to the travel query function file, semantic conflict information between the description information of the travel query function file and the description information of the encyclopedia Q&A function file is generated.

[0083] In the embodiments of this application, if the overlapping keywords are uniquely assigned and have clear boundaries, the severity of the semantic conflict is low; if the similar keywords cannot be distinguished, the severity of the semantic conflict is high.

[0084] Optionally, before performing the step of "determining semantic conflict information between at least two pieces of description information based on semantically overlapping or similar description keywords between at least two executable function files, and the attribution information of the description keywords," the following methods may be used, but are not limited to: Based on the semantic content and scene association information in semantically overlapping or similar descriptive keywords, the attribution information of semantically overlapping or similar descriptive keywords is determined. The scene association information is the functional scene information that matches the semantic content in semantically overlapping or similar descriptive keywords.

[0085] In this embodiment of the application, the semantic content of semantically overlapping or similar descriptive keywords is the meaning represented by the descriptive keywords themselves, and the scenario association information is the functional scenario that the semantically overlapping or similar descriptive keywords adapt to or match; by combining the meaning of semantically overlapping or similar descriptive keywords and the adapted scenario of semantically overlapping or similar descriptive keywords, it can be determined which executable functional file the semantically overlapping or similar descriptive keywords should belong to.

[0086] For example, taking the aforementioned semantically overlapping or similar descriptive keywords as weather, the semantic content of these descriptive keywords is related to weather temperature, sunshine, rain, and snow, and the corresponding scenario-related information is travel planning, itinerary reference, and travel arrangement scenarios. Based on the semantic content of the descriptive keywords and the scenario-related information, it can be determined that the descriptive keyword weather belongs to the travel query function file, rather than the encyclopedia Q&A function file.

[0087] For example, taking the semantically overlapping or similar descriptive keyword "common sense" as an example, the semantic content of this descriptive keyword is popular science content and information related to answers to common sense questions. The corresponding scenario-related information is daily consultation, popular science knowledge, and question-answering scenarios. Based on the aforementioned semantic content and scenario-related information, it can be determined that the descriptive keyword "common sense" belongs to the encyclopedia question and answer function file, rather than the travel query function file. And so on, without further examples.

[0088] As an alternative approach, if the semantic content of a keyword highly matches a certain functional scenario, the keyword will be preferentially assigned to the executable function file corresponding to that scenario; for example, keywords such as route and traffic conditions point to a travel scenario, so they can be assigned to the travel query function file.

[0089] Optionally, when performing the "update at least two description pieces of information" operation, the following methods can be used, but are not limited to these: Figure 4 As shown, the method includes: Step 401: Determine the target baseline description information from the description information; In the embodiments of this application, the target benchmark description information is one of the description information. For example, when there is a semantic conflict between the description information of at least two executable function files, the description information of the executable function file with the highest application frequency can be determined as the target benchmark description information.

[0090] For example, when there is a semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file, the description information of the travel query function file with clear functional boundaries and higher calling priority can be determined as the target benchmark description information; or the description information of the encyclopedia Q&A function file with fixed division of responsibilities can be determined as the target benchmark description information, and so on. Examples will not be given here.

[0091] Step 402: Update the description information except for the target baseline description information.

[0092] In this embodiment of the application, the target baseline description information is used as a reference to update the remaining description information that has semantic conflicts, so as to avoid semantic conflicts with the target baseline description information.

[0093] For example, if the description information of the travel query function file is determined as the target baseline description information, then the semantic coverage of the description information of the travel query function file remains unchanged, and the description information of the encyclopedia Q&A function file is updated; if the description information of the encyclopedia Q&A function file is determined as the target baseline description information, then the semantic coverage of the description information of the encyclopedia Q&A function file remains unchanged, and the description information of the travel query function file is updated, thereby eliminating the semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file. Examples will not be given here.

[0094] In this embodiment of the application, if there is a semantic conflict between the description information of three executable functional files, a baseline description information is determined from the three description information, and the description information of the remaining two executable functional files is updated, and so on. Examples will not be listed here.

[0095] Optionally, when performing the action of "updating the description information based on semantic conflict information," the following methods may be used, but are not limited to: If the number of times the description information is updated does not exceed the target update number threshold, the description information is updated based on the semantic conflict information of the description information.

[0096] In this embodiment, the target update threshold is a pre-set upper limit for the maximum number of updates to restrict the repeated iterative adjustment of the description information, in order to avoid the infinite shrinkage of the semantic range of the description information, which would cause the executable file to malfunction.

[0097] In this embodiment of the application, if the number of times the description information is updated exceeds the target number of updates threshold, the updating of the description information is stopped.

[0098] For example, if the target update threshold is set to 3 times, the description information can continue to be updated when the update count is 1, 2, or 3 times.

[0099] As an optional approach, the target update count threshold can be set according to the importance of the executable function file and the complexity of the scenario. For example, a larger target update count threshold can be set for high-frequency executable function files, and a smaller target update count threshold can be set for low-frequency executable function files. This can ensure that semantic conflicts between the description information of executable function files are fully eliminated, and can also avoid repeated and invalid updates of description information.

[0100] Optionally, this embodiment may also employ the following methods, but not limited thereto: determining that there is a semantic conflict between the description information of at least two executable functional files based on the semantic similarity between the description information of at least two executable functional files corresponding to the interactive intelligent agent.

[0101] In this embodiment of the application, semantic similarity is used to measure the degree of semantic overlap or similarity between the description information of different executable function files. When the semantic similarity between the description information of two executable function files reaches a preset semantic similarity threshold, it can be determined that there is a semantic conflict between the two description information. The higher the semantic similarity, the higher the similarity between the two description information, and the greater the risk of instruction confusion and call disorder.

[0102] For example, if the description information of the travel query function file and the description information of the encyclopedia Q&A function file are compared and calculated, and the semantic similarity between the two is high and reaches the preset semantic similarity threshold, then it can be determined that there is a semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file; if the semantic similarity is low and does not reach the preset semantic similarity threshold, then it can be determined that there is no semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file.

[0103] As an optional approach, a semantic similarity threshold can be preset. When the semantic similarity between the description information of executable function files is higher than the preset semantic similarity threshold, conflicts are automatically identified. If the semantic similarity is lower than the preset semantic similarity threshold, it is determined that there is no semantic conflict between the description information of executable function files, and there is no need to update the description information.

[0104] Optionally, when determining a semantic conflict between the description information of at least two executable functional files based on the semantic similarity between their description information and the description information of the interactive intelligent agent, the following method may be used, but is not limited to: In response to a change in the configuration information of at least one executable function file, a semantic conflict is determined to exist between the description information of at least two executable function files based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive agent.

[0105] In this application embodiment, changes to the configuration information of executable function files may include, but are not limited to, modifications, additions, or deletions of relevant parameters such as function scope, service scenarios, descriptive keywords, and execution permissions in the description information of executable function files; and increases or decreases in the number of executable function files.

[0106] When the configuration information of any executable function file is changed, the semantic similarity between the description information of the executable function files needs to be recalculated. This will allow for the timely identification of newly added semantically overlapping or similar descriptive keywords and the determination of whether new semantic conflicts have occurred.

[0107] For example, before the description information is updated, the boundaries between the travel query function file and the encyclopedia Q&A function file are clear, and the semantic similarity is low, so there is no semantic conflict between the corresponding description information. When the configuration information of the travel query function file changes, such as adding content related to answers to common sense questions, the semantic similarity between the description information of the travel query function file and the description information of the encyclopedia Q&A function file is recalculated. If the similarity increases and reaches the preset semantic similarity threshold, it can be determined that there is a new semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file.

[0108] For example, before the description information is updated, the encyclopedia Q&A function file is only responsible for popular science knowledge queries, and there is no semantic conflict between the description information of other executable function files; when the configuration information of the encyclopedia Q&A function file is changed, and new description content related to travel conditions and itinerary references is added, the semantic similarity between the encyclopedia Q&A function file and the description information of the travel query function file increases and reaches the preset semantic similarity threshold, it can be determined that there is a new semantic conflict between the description information of the travel query function file and the description information of the encyclopedia Q&A function file, and so on, without further examples here.

[0109] As an optional approach, semantic similarity re-verification is automatically triggered whenever the configuration information of the executable function file changes, in order to avoid new semantic conflicts arising from changes in configuration information.

[0110] Optionally, the configuration information for executable function files may include at least the number of executable function files and their descriptions.

[0111] In this embodiment of the application, the number of executable function files includes the total number of executable function files currently mounted, enabled, or participating in collaborative operation of the interactive intelligent agent, the number of newly added executable function files, and the number of deleted executable function files.

[0112] In the embodiments of this application, the description information of the executable function file includes the description keywords, function adaptation scope, executable function domain, and non-executable function domain corresponding to each executable function file.

[0113] For example, the interactive intelligent agent is currently configured with two executable function files, namely a travel query function file and an encyclopedia Q&A function file. The total number of these files is the number of executable function files. The route planning description information and common sense answer description content corresponding to each of the two executable function files are the description information of the corresponding executable function files.

[0114] In some examples, embodiments of this application may include, but are not limited to, the following: Example 1: An information update method, comprising: when there is a semantic conflict between the description information of at least two executable function files corresponding to an interactive intelligent agent, updating the description information according to the semantic conflict information of the description information, so that there is no semantic conflict between the description information of at least two target executable function files.

[0115] Example 2: The description information is the function description information corresponding to the executable function file. The function description information includes information on the executable functions of the executable function file and information on the non-executable functions of the executable function file.

[0116] Example 3: Semantic conflict information is obtained based on the existence of semantic overlap or similar descriptive information between the descriptive information of at least two executable function files.

[0117] Example 4: Semantic conflict information includes at least one of semantically overlapping or similar descriptive keywords, attribution information of semantically overlapping or similar descriptive keywords, and the severity of semantic conflict. The attribution information is used to indicate the executable function file to which the semantically overlapping or similar descriptive keywords belong.

[0118] Example 5: An executable function file is used by a terminal device to execute a target function. The executable function file includes at least one of the following: function description information corresponding to the target function and applicable scenario information of the target function.

[0119] Example 6: Based on the semantic conflict information of the description information, the semantic coverage of the description information is narrowed in order to update the description information.

[0120] Example 7: Based on the semantic conflict information of the description information, obtain the scope information corresponding to each executable function file. The scope information is at least one of the functional domain information used to determine the unprocessable functional file and the functional execution boundary information of the executable function file. Based on the scope information and the description information, perform a shrinking process on the semantic coverage of the description information.

[0121] Example 8: Based on the semantic conflict information in the description information, obtain the target functional domain information that each executable functional file can process; based on the functional domain information other than the target functional domain information in the description information, perform semantic coverage reduction processing on the description information.

[0122] Example 9: Based on the semantic overlap or similarity of description keywords between the description information of at least two executable functional files, and the attribution information of the description keywords, determine the semantic conflict information of at least two description information.

[0123] Example 10: Based on the semantic content and scene association information in semantically overlapping or similar descriptive keywords, determine the attribution information of semantically overlapping or similar descriptive keywords. The scene association information is the functional scene information adapted to the semantic content in semantically overlapping or similar descriptive keywords.

[0124] Example 11: Determine the target reference description information from the description information; update the description information other than the target reference description information.

[0125] Example 12: When the number of times the description information is updated is not higher than the target number of times the description information is updated, the description information is updated based on the semantic conflict information of the description information.

[0126] Example 13: Based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive intelligent agent, determine that there is a semantic conflict between the description information of at least two executable function files.

[0127] Example 14: In response to a change in the configuration information of at least one executable function file, a semantic conflict is determined to exist between the description information of at least two executable function files based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive agent.

[0128] Example 15: The configuration information of executable function files includes at least the number of executable function files and the description information of the executable function files.

[0129] It should be noted that the information update method involved in the above embodiments may include at least one of embodiments 1 to 15. For example, embodiment 1 may be implemented as an independent embodiment, embodiment 1+2 may be implemented as an independent embodiment, embodiment 1+3 may be implemented as an independent embodiment, embodiment 1+2+3 may be implemented as an independent embodiment, embodiment 1+4 may be implemented as an independent embodiment, embodiment 1+2+4 may be implemented as an independent embodiment, embodiment 1+3+4 may be implemented as an independent embodiment, embodiment 1+2+3+4 may be implemented as an independent embodiment, embodiment 1+5 may be implemented as an independent embodiment, embodiment 1+2+5 may be implemented as an independent embodiment, embodiment 1+3+5 may be implemented as an independent embodiment, embodiment 1+2+3+5 may be implemented as an independent embodiment, and embodiment 1+3+4+5 may be implemented as an independent embodiment. Examples of implementations are as follows: Examples 1+2+3+4+5 can be implemented as independent embodiments; Examples 1+6 can be implemented as independent embodiments; Examples 1+2+6 can be implemented as independent embodiments; Examples 1+3+6 can be implemented as independent embodiments; Examples 1+3+4+6 can be implemented as independent embodiments; Examples 1+2+3+4+6 can be implemented as independent embodiments; Examples 1+2+4+5+6 can be implemented as independent embodiments; Examples 1+3+4+5+6 can be implemented as independent embodiments; Examples 1+2+3+4+5+6 can be implemented as independent embodiments; and so on. These examples are not exhaustive and will not be listed here.

[0130] Compared with related technologies, this embodiment can update the description information based on the semantic conflict information when there is a semantic conflict between the description information of at least two executable function files corresponding to the interactive intelligent agent, so that there is no semantic conflict between the description information of at least two target executable function files. This allows the application to update at least two description information through the semantic conflict information of at least two description information, thereby improving the elimination of semantic conflicts between the description information of different function files and improving the accuracy of executable function file invocation.

[0131] Furthermore, as Figure 1 , Figure 2 , Figure 3 and Figure 4 To provide a specific implementation of the method shown, this embodiment offers an information updating device, such as... Figure 5 As shown, the device includes: an update module 51.

[0132] The update module 51 is configured to update the description information based on the semantic conflict information of the description information when there is a semantic conflict between the description information of at least two executable function files corresponding to the interactive agent, so that there is no semantic conflict between the description information of at least two target executable function files.

[0133] In some examples of this embodiment, the description information is the function description information corresponding to the executable function file. The function description information includes information on the executable functions of the executable function file and information on the non-executable functions of the executable function file.

[0134] In some examples of this embodiment, semantic conflict information is obtained based on semantic overlap or similar descriptive information between at least two executable function files.

[0135] In some examples of this embodiment, semantic conflict information includes at least one of semantically overlapping or similar descriptive keywords, attribution information of semantically overlapping or similar descriptive keywords, and the severity of semantic conflict. The attribution information is used to indicate the executable function file to which the semantically overlapping or similar descriptive keywords belong.

[0136] In some examples of this embodiment, the executable function file is used by the terminal device to perform the target function. The executable function file includes at least one of the function description information corresponding to the target function and the applicable scenario information of the target function.

[0137] In some examples of this embodiment, the update module 51 is specifically configured to update the description information based on semantic conflict information, including: Based on the semantic conflict information of the description information, the semantic coverage of the description information is narrowed in order to update the description information.

[0138] In some examples of this embodiment, the update module 51 is specifically configured to shrink the semantic coverage of the description information based on the semantic conflict information of the description information, including: Based on the semantic conflict information of the description information, obtain the scope information corresponding to each executable function file. The scope information is at least one of the following: functional domain information used to determine the unprocessable functional file and functional execution boundary information of the executable function file. Based on the scope information and description information, the semantic coverage of the description information is narrowed.

[0139] In some examples of this embodiment, the update module 51 is specifically configured to shrink the semantic coverage of the description information based on the semantic conflict information of the description information, including: Based on the semantic conflict information in the description information, obtain the target functional domain information that each executable functional file can process; Based on functional domain information other than the target functional domain information in the description information, the semantic coverage of the description information is narrowed.

[0140] In some examples of this embodiment, the update module 51 is further configured to determine semantic conflict information of at least two description information based on semantically overlapping or similar description keywords between description information of at least two executable functional files, and the attribution information of the description keywords.

[0141] In some examples of this embodiment, the update module 51 is further configured to determine the attribution information of semantically overlapping or similar descriptive keywords based on the semantic content and scene association information in the semantically overlapping or similar descriptive keywords, wherein the scene association information is the functional scene information adapted to the semantic content in the semantically overlapping or similar descriptive keywords.

[0142] In some examples of this embodiment, the update module 51 is further configured to determine the target baseline description information from the description information; Update the description information except for the target baseline description information.

[0143] In some examples of this embodiment, the update module 51 is further configured to update the description information based on the semantic conflict information of the description information when the number of updates to the description information is not higher than the target update number threshold.

[0144] In some examples of this embodiment, the update module 51 is further configured to determine that there is a semantic conflict between the description information of at least two executable function files based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive agent.

[0145] In some examples of this embodiment, the update module 51 is further configured to, in response to a change in the configuration information of at least one executable function file, determine that there is a semantic conflict between the description information of at least two executable function files corresponding to the interactive agent, based on the semantic similarity between the description information of at least two executable function files.

[0146] In some examples of this embodiment, the configuration information of the executable function files includes at least the number of executable function files and the description information of the executable function files.

[0147] It should be noted that other corresponding descriptions of the functional units involved in the information updating device provided in this embodiment can be found in [reference]. Figure 1 , Figure 2 , Figure 3 and Figure 4 The corresponding descriptions in [the document] will not be repeated here.

[0148] Based on the above, Figure 1 , Figure 2 , Figure 3 and Figure 4 Accordingly, this embodiment also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the above-described method. Figure 1 and Figure 2 The method shown.

[0149] Based on this understanding, the technical solution of this application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as CD-ROM, USB flash drive, mobile hard drive, etc.) and includes several instructions to cause a computer device (such as personal computer, server, or network device, etc.) to execute the methods of various implementation scenarios of this application.

[0150] like Figure 6 The diagram shown is a hardware structure schematic of an electronic device according to the present invention, comprising: At least one processor 601; and, Memory 602 is communicatively connected to at least one processor 601; wherein, The memory 602 stores instructions that can be executed by at least one processor, which enables the at least one processor to perform the information update method as described above.

[0151] Figure 6 Take the 601 processor as an example.

[0152] The electronic device may also include an input device 603 and a display device 604.

[0153] The processor 601, memory 602, input device 603, and display device 604 can be connected via a bus or other means. Figure 6 Taking the example of a connection between China and Israel via a bus.

[0154] The memory 602, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions / modules corresponding to the information update method in the embodiments of this application, for example, Figure 1 and Figure 2 The method flow is shown. The processor 601 executes various functional applications and data processing by running non-volatile software programs, instructions, and modules stored in the memory 602, thereby implementing the information update method in the above embodiments.

[0155] The memory 602 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created according to the use of the information update method, etc. Furthermore, the memory 602 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 602 may optionally include memory remotely located relative to the processor 601, and these remote memories can be connected to the apparatus performing the information update method via a network. Examples of such networks include, but are not limited to, the Internet, intranets, local area networks, mobile communication networks, and combinations thereof.

[0156] The input device 603 can receive user clicks and generate signal inputs related to user settings and function control for information update methods. The display device 604 may include a display screen or other display device.

[0157] One or more modules are stored in memory 602, and when run by one or more processors 601, the information update method in any of the above method embodiments is executed.

[0158] Optionally, the aforementioned physical devices may also include a user interface, a network interface, a camera, radio frequency (RF) circuitry, sensors, audio circuitry, a Wi-Fi module, etc. The user interface may include a display screen, input units such as a keyboard, etc., and optional user interfaces may also include USB interfaces, card reader interfaces, etc. The network interface may optionally include standard wired interfaces, wireless interfaces (such as Wi-Fi interfaces), etc.

[0159] Those skilled in the art will understand that the physical device structure provided in this embodiment does not constitute a limitation on the physical device, and may include more or fewer components, or combine certain components, or have different component arrangements.

[0160] The storage medium may also include an operating system and a network communication module. The operating system is a program that manages the hardware and software resources of the aforementioned physical device, supporting the operation of information processing programs and other software and / or programs. The network communication module is used to enable communication between the various components within the storage medium, as well as communication with other hardware and software in the information processing physical device.

[0161] Through the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented using software plus necessary general-purpose hardware platforms, or it can be implemented using hardware. By applying the solution of this embodiment, compared with related technologies, this embodiment can control the state adjustment of the device in the target area and / or target location based on the user's interactive actions in the target area and / or target location of the terminal device, thereby adjusting the target device to the target state. This embodiment can achieve state control of the target device corresponding to the target area and / or target location through the user's interactive actions in the target area and / or target location, without relying on a central control device for adjustment, thus meeting the usage needs in different scenarios.

[0162] 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 term "comprising" or any other variations thereof is 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 one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0163] The above description is merely a specific embodiment of this disclosure, enabling those skilled in the art to understand or implement it. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not to be limited to the embodiments described herein, but is to be accorded the widest scope consistent with the principles and novel features claimed herein.

Claims

1. An information updating method, characterized in that, include: In the event of a semantic conflict between the description information of at least two executable function files corresponding to the interactive agent, the description information is updated based on the semantic conflict information of the description information so that there is no semantic conflict between the description information of the at least two target executable function files.

2. The method according to claim 1, characterized in that, The description information is the function description information corresponding to the executable function file. The function description information includes information on the executable functions of the executable function file and information on the non-executable functions of the executable function file.

3. The method according to claim 1 or 2, characterized in that, The semantic conflict information is obtained based on the existence of semantic overlap or similar descriptive information between at least two executable function files.

4. The method according to any one of claims 1-3, characterized in that, The semantic conflict information includes at least one of the following: semantically overlapping or similar descriptive keywords, attribution information of the semantically overlapping or similar descriptive keywords, and the severity of the semantic conflict. The attribution information is used to indicate the executable file to which the semantically overlapping or similar descriptive keywords belong.

5. The method according to any one of claims 1-4, characterized in that, The executable function file is used by the terminal device to execute the target function. The executable function file includes at least one of the function description information corresponding to the target function and the applicable scenario information of the target function.

6. The method according to any one of claims 1-5, characterized in that, The step of updating the description information based on the semantic conflict information of the description information includes: Based on the semantic conflict information of the description information, the semantic coverage of the description information is narrowed in order to update the description information.

7. The method according to claim 6, characterized in that, The step of narrowing the semantic coverage of the description information based on semantic conflict information includes: Based on the semantic conflict information of the description information, the scope information corresponding to each executable function file is obtained. The scope information is at least one of the following: functional domain information used to determine the unprocessable functional file of the executable function file and functional execution boundary information of the executable function file. Based on the range information and the description information, the semantic coverage of the description information is narrowed.

8. The method according to claim 7, characterized in that, The step of narrowing the semantic coverage of the description information based on semantic conflict information includes: Based on the semantic conflict information in the description information, obtain the target functional domain information that each executable functional file can process; Based on functional domain information other than the target functional domain information in the description information, the semantic coverage of the description information is narrowed.

9. The method according to any one of claims 1-8, characterized in that, The method includes: Based on the semantic content and scene association information in the semantically overlapping or similar descriptive keywords, the attribution information of the semantically overlapping or similar descriptive keywords is determined, and the scene association information is the functional scene information adapted to the semantic content in the semantically overlapping or similar descriptive keywords.

10. The method according to any one of claims 1-9, characterized in that, Updating the description information includes: Determine the target baseline description information from the description information; Update the description information other than the target baseline description information.

11. The method according to any one of claims 1-10, characterized in that, The step of updating the description information based on the semantic conflict information of the description information includes: If the number of updates to the description information is not higher than the target update number threshold, the description information is updated based on the semantic conflict information of the description information.

12. The method according to any one of claims 1-11, characterized in that, The method includes: Based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive intelligent agent, it is determined that there is a semantic conflict between the description information of at least two executable function files.

13. The method according to claim 12, characterized in that, The determination of semantic conflicts between the description information of at least two executable function files based on the semantic similarity between the description information of the interactive intelligent agent includes: In response to a change in the configuration information of at least one executable function file, a semantic conflict is determined to exist between the description information of at least two executable function files based on the semantic similarity between the description information of at least two executable function files corresponding to the interactive agent.

14. An information updating device, characterized in that, include: The update module is configured to update the description information based on the semantic conflict information of the description information when there is a semantic conflict between the description information of at least two executable function files corresponding to the interactive agent, so that there is no semantic conflict between the description information of the at least two target executable function files.

15. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of any one of claims 1 to 13.

16. An electronic device, characterized in that, The invention includes a storage medium, a processor, and a computer program stored on the storage medium and executable on the processor, characterized in that the processor, when executing the computer program, implements the method of any one of claims 1 to 13.

17. A vehicle or robot, characterized in that, include: The apparatus of claim 14, or the electronic device of claim 16.

Images