Method and apparatus for processing a dialog building vehicle

Abstract

The embodiment of the present specification provides a method and device for processing a dialogue construction carrier, wherein the method for processing the dialogue construction carrier comprises the following steps: providing a graphical interface for generating a dialogue architecture, the dialogue architecture comprising a plurality of nodes and a relationship between the nodes; receiving a grouping request corresponding to one or at least two existing nodes with a relationship in the dialogue architecture displayed by the graphical interface; in response to the grouping request, extracting relationship information and configuration information of the corresponding existing nodes from the dialogue architecture; and generating a reusable node component by using the relationship information and the configuration information of the existing nodes, the node component being a dialogue construction carrier with a finer granularity than the dialogue architecture, which helps to improve the construction efficiency of the dialogue architecture.

Description

TECHNICAL FIELD

[0001] Embodiments of the present specification relate to the technical field of intelligent technology, and in particular, to a method for processing a dialogue construction carrier. Embodiments of the present specification also relate to an apparatus for processing a dialogue construction carrier, a computing device, and a computer-readable storage medium. BACKGROUND

[0002] A dialogue robot platform is a multi-turn dialogue system for developers. Through the dialogue robot platform, an artificial intelligence system that answers questions using natural language can be implemented. On the dialogue robot platform, a user who is a developer can design, build and publish a dialogue architecture of a dialogue robot through a graphical interface.

[0003] The dialogue architecture is a graphical multi-turn dialogue design tool used by the dialogue robot platform to model a process, which is built and continuously maintained by the developer. How to effectively improve the construction efficiency of the dialogue robot and simplify the operation of the developer is an urgent problem to be solved by the dialogue robot platform. SUMMARY

[0004] Therefore, embodiments of the present specification provide a method for processing a dialogue construction carrier. Embodiments of the present specification also relate to an apparatus for processing a dialogue construction carrier, a computing device, and a computer-readable storage medium to solve the technical defects existing in the prior art.

[0005] According to a first aspect of embodiments of the present specification, a method for processing a dialogue construction carrier is provided, including: providing a graphical interface for generating a dialogue architecture, the dialogue architecture including a plurality of nodes and inter-node relationships; receiving a grouping request corresponding to one or at least two existing nodes with relationships in the dialogue architecture displayed by the graphical interface; in response to the grouping request, extracting relationship information and configuration information of the corresponding existing nodes from the dialogue architecture; and generating a reusable node component using the relationship information and the configuration information of the existing nodes.

[0006] Optionally, the method further includes: receiving input of one or more nodes and inter-node relationships, and receiving input of configuration information of the nodes; and forming the dialogue architecture according to the received input of one or more nodes, inter-node relationships, and configuration information of the nodes.

[0007] Optionally, the method further includes: receiving a setting input corresponding to the reusable node component, the setting input being used to indicate a position of the node component in the dialogue architecture; and adding the node component in the dialogue architecture according to the position corresponding to the setting input.

[0008] Optionally, the method further comprises: in the graphical interface, marking a region where the node component is located in the dialogue architecture, and displaying a corresponding operation icon for the region, the operation icon being associated with an operation label, the operation label comprising one or more of a naming operation label, an ungrouping operation label, and a saving operation label; the naming operation label is used for triggering a node component renaming operation by a user; the ungrouping operation label is used for triggering an ungrouping operation of the node component by the user; and the saving operation label is used for triggering a saving operation of the node component by the user.

[0009] Optionally, the extracting the configuration information of the corresponding existing node from the dialogue architecture comprises: extracting the configuration information from the dialogue architecture layer by layer according to a hierarchy of dependency relationships between different configuration items of the existing node.

[0010] Optionally, the method further comprises: saving the node component to a component library, the component library being used for saving and providing reusable node components; and / or pushing a message sharing the node component to other users.

[0011] Optionally, the method further comprises: in response to receiving a reference operation on the node component, obtaining relationship information and configuration information of the referenced node component; and adding the relationship information and the configuration information of the referenced node component to the dialogue architecture displayed in the graphical interface.

[0012] Optionally, the obtaining the relationship information and the configuration information of the referenced node component in response to receiving the reference operation on the node component comprises: in response to receiving a reference operation on a node component in a component library displayed in the graphical interface, obtaining the relationship information and the configuration information of the referenced node component from the component library according to the reference operation, the component library being used for saving and providing reusable node components.

[0013] Optionally, the method further comprises: determining whether there is information in the information of the referenced node component that conflicts with original information of the dialogue architecture; and if there is, updating the information of the referenced node component and / or the original information of the dialogue architecture according to a preset conflict resolution strategy, or giving up referencing the node component.

[0014] Optionally, the determining whether there is information in the information of the referenced node component that conflicts with original information of the dialogue architecture comprises: layer by layer determining whether there is information in the configuration information of the referenced node component that conflicts with the original information of the dialogue architecture according to a hierarchy of dependency relationships between different configuration items of the referenced node component; and the method further comprises: if the updated configuration item has other configuration items that have a dependency relationship with the updated configuration item, updating the dependency relationship of the other configuration items with the updated configuration item accordingly.

[0015] Optionally, the preset conflict resolution strategy comprises: a cover strategy, which is used to replace original information with new information for the conflicting information; or an inheritance strategy, which is used to replace new information with original information for the conflicting information; or a merge strategy, which is used to merge the new information and the original information as the current used information for the conflicting information; or an update strategy, which is used to modify the new information according to a preset modification manner so that the new information does not conflict with the original information for the conflicting information.

[0016] Optionally, the update strategy is used when the conflicting information is key information of a node; and the merge strategy is used when the conflicting information is non-key information of a node.

[0017] According to a second aspect of the embodiments of the present specification, a device for processing a dialogue construction carrier is provided, comprising: an interface providing module configured to provide a graphical interface for generating a dialogue architecture, the dialogue architecture comprising a plurality of nodes and relationships between the nodes; a request receiving module configured to receive a grouping request corresponding to one or at least two existing nodes with relationships in the dialogue architecture displayed by the graphical interface; an information extracting module configured to extract relationship information and configuration information of the corresponding existing nodes from the dialogue architecture in response to the grouping request; and a component generating module configured to generate a reusable node component using the relationship information and the configuration information of the existing nodes.

[0018] According to a third aspect of the embodiments of the present specification, a computing device is provided, comprising: a memory and a processor; the memory is configured to store computer executable instructions, and the processor is configured to execute the computer executable instructions to: provide a graphical interface for generating a dialogue architecture, the dialogue architecture comprising a plurality of nodes and relationships between the nodes; receive a grouping request corresponding to one or at least two existing nodes with relationships in the dialogue architecture displayed by the graphical interface; extract relationship information and configuration information of the corresponding existing nodes from the dialogue architecture in response to the grouping request; and generate a reusable node component using the relationship information and the configuration information of the existing nodes.

[0019] According to a fourth aspect of the embodiments of the present specification, a computer readable storage medium is provided, which stores computer executable instructions, and the computer executable instructions are executed by a processor to implement the steps of the method for processing a dialogue construction carrier according to any of the embodiments of the present specification.

[0020] The embodiment of the present specification provides a method for processing a dialogue construction carrier. The method provides a graphical interface for generating a dialogue architecture, the dialogue architecture comprising a plurality of nodes and relationships between the nodes, receives a grouping request corresponding to one or at least two existing nodes with relationships in the dialogue architecture displayed in the graphical interface, extracts relationship information and configuration information of the corresponding existing nodes from the dialogue architecture in response to the grouping request, and generates a reusable node component using the relationship information and configuration information of the existing nodes. The method provides a new dialogue construction carrier for users to split node components in the graphical interface, so that users can conveniently and flexibly split the reusable node components by, for example, point selection, frame selection and the like. The node component has corresponding relationship information and configuration information, and is a dialogue construction carrier with finer granularity than the dialogue architecture, realizes the management of a segment of the dialogue architecture, and helps to improve the construction efficiency of the dialogue architecture. BRIEF DESCRIPTION OF DRAWINGS

[0021] Figure 1 is a flowchart of a method for processing a dialogue construction carrier provided by an embodiment of the present specification;

[0022] Figure 2a is a schematic diagram of a graphical interface provided by an embodiment of the present specification;

[0023] Figure 2b is a schematic diagram of a graphical interface provided by another embodiment of the present specification;

[0024] Figure 3 is a structural schematic diagram of a dialogue architecture provided by an embodiment of the present specification;

[0025] Figure 4 is a schematic diagram of a graphical interface provided by another embodiment of the present specification;

[0026] Figure 5 is a flowchart of a method for processing a dialogue construction carrier provided by another embodiment of the present specification;

[0027] Figure 6 is a structural schematic diagram of an apparatus for processing a dialogue construction carrier provided by an embodiment of the present specification;

[0028] Figure 7 is a structural schematic diagram of an apparatus for processing a dialogue construction carrier provided by another embodiment of the present specification;

[0029] Figure 8 is a conflict resolution flowchart provided by an embodiment of the present specification;

[0030] Figure 9is a structural block diagram of a computing device provided by an embodiment of the present specification. DETAILED DESCRIPTION

[0031] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present specification. However, the present specification can be practiced without the specific details, which are not described in the present specification, and it is understood that the scope of the present specification is not limited to the details of the description. In other instances, well-known methods associated with computing devices have not been described in detail in order to avoid unnecessarily obscuring the present specification.

[0032] The terminology used in one or more embodiments of the present specification is for the purpose of describing particular embodiments only and is not intended to be limiting of one or more embodiments of the present specification. As used in one or more embodiments of the present specification and the accompanying claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and / or "comprising," when used in one or more embodiments of the present specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0033] It is to be understood that the terms first, second, etc. can be employed in one or more embodiments of the present specification to describe various information, but these terms are not intended to limit the scope of one or more embodiments of the present specification. These terms are used only to distinguish one type of information from another type of information. For example, without departing from the scope of one or more embodiments of the present specification, first can be referred to as second, and similarly, second can be referred to as first. Depending on the context, the word "if' as used herein can be interpreted to mean "when" or "in response to determining."

[0034] First, the noun terms related to one or more embodiments of the present specification are explained.

[0035] Graphical interface: refers to a graphical display of the user interface. Compared with the text input type interface, in addition to reducing the cognitive and operational burden of the user, the graphical interface is more visually acceptable to new users, and the learning cost is greatly reduced.

[0036] Conversational robot platform: can be used to implement an artificial intelligence system using natural language to answer questions, for the design, construction and release of conversational robots. For example, the conversational robot platform can provide a graphical interface for conversational architecture design, which is a workbench where users can customize the conversational architecture. For example, users can configure and add different conversational architectures in the robot to make the robot have conversational capabilities in several fields such as e-commerce services, financial services, etc. For example, the conversational robot platform abstracts and refines concepts in the conversation, which can include at least three basic elements: entry (trigger), function (function), and response (reply). It can also make branch judgments based on the parameter values obtained during the slot filling process, such as name verification, reasonableness verification, etc.

[0037] Robots: Robots are virtual systems that simulate human conversation with users. Based on the conversational robot platform, users can create multiple robots. In each robot, different conversational architectures are configured and added to make the robot have conversational capabilities in several fields such as e-commerce services, financial services, etc.

[0038] Conversational architecture: is a graphical multi-turn conversation design tool used by the conversational robot platform to model service processes, which are built and continuously maintained by developer users. The conversational architecture includes multiple nodes and node relationships. For example, it can include a directed graph of multiple types of nodes and associated intent, entity, service, etc. configuration information. It is generally used to implement a specific conversation skill in a specific service field, such as an e-commerce domain robot that can be composed of order query, return, ticket booking, etc. For example, the conversational architecture can be implemented in an actual application scenario as shown in the conversation flow. Figure 2a

[0039] Node: as an atomic carrier of conversation content and configuration, used to implement a specific task of the conversational architecture. Depending on the associated configuration, the node has different functions. For example, a node associated with intent and entity can rely on natural language understanding (NLU) technology to analyze user language and trigger the next step of the system; a node associated with a service can call a third-party API to implement functions such as weather query; a node associated with a reply configuration can generate a system reply based on various information.

[0040] Node component: is a conversation segment generated by the relationship information and configuration information of one or more nodes in the conversational architecture. One or more nodes can be any node selected by the user in the conversational architecture. The node component can be used for reuse in the current or other arbitrary conversational architecture.

[0041] ​It can be understood that the dialog framework and the node component are data carriers of different concepts. Specifically, a robot is composed of one or more dialog frameworks, which are generally used to complete a service capability in a certain field. The dialog framework is a dialog framework program directly mounted on the robot to implement a skill, which is generally used to complete a specific skill in a certain field, such as credit card collection. The node component is a dialog construction carrier containing one or more nodes, which cannot be directly mounted on the robot and is used to carry a fragment of a dialog framework, for example, a fragment of a skill, such as sending a short message.

[0042] In the present specification, a method for processing a dialog construction carrier is provided, and the present specification also relates to an apparatus for processing a dialog construction carrier, a computing device, and a computer-readable storage medium, which are described in detail one by one in the following embodiments.

[0043] Figure 1 A flowchart of a method for processing a dialog construction carrier according to an embodiment of the present specification is shown, which includes steps 102 to 108.

[0044] Step 102: providing a graphical interface for generating a dialog framework, the dialog framework containing a plurality of nodes and inter-node relationships.

[0045] For example, input of one or more nodes and inter-node relationships can be received, and input of configuration information of the nodes can be received; and the dialog framework can be formed according to the received input of one or more nodes, inter-node relationships, and configuration information of the nodes.

[0046] Step 104: receiving a grouping request corresponding to one or at least two existing nodes with relationships in the dialog framework displayed in the graphical interface.

[0047] Step 106: in response to the grouping request, extracting relationship information and configuration information of the corresponding existing nodes from the dialog framework.

[0048] For example, a user can select one or at least two existing nodes with relationships in the dialog flow displayed in the graphical interface, and initiate a grouping request for the selected existing nodes. The implementation of the user selecting the nodes is not limited, for example, the graphical interface can provide a selection mode of clicking and / or framing the selected nodes.

[0049] In the clicking implementation, the graphical interface can provide an operation mode for the user to click to select any one or at least two existing nodes with relationships. The directed edges between the nodes as the relationship information can be selected by the user clicking, or can be automatically determined according to the directed edges between the nodes selected by the user in the dialog framework.

[0050] In the boxed embodiment, the graphical interface can provide a way for the user to box one or at least two existing nodes with relationship. For example, the boxed area can be determined according to the area that the user slides in the graphical interface using a mouse or touch screen. To facilitate user operation efficiency, the graphical interface can also provide a shortcut for boxing. For example, when the user holds down the shift key, the two points selected by the user in succession can be used as the two opposite corners of the box to quickly determine the boxed area. The user can box one or more places in a dialogue architecture, and a corresponding node component can be generated for each local boxed.

[0051] The relationship information, for example, includes information describing the topology between nodes, such as directed edges between nodes, predecessor nodes allowed by nodes, successor nodes, and the like.

[0052] The configuration information includes one or more configuration items and corresponding configuration contents for defining node functions. For example, the configuration information can include several configuration items such as intent, slot, entity, function, and reply. For example, the configuration information of a "user says" node can include configuration items of different intents, and the configuration items of different intents include different utterance contents. For example, in a certain travel application scenario, the intent associated with the user says type of node includes utterances such as "I want to check the flight" and "I want to check the CN11123 flight" containing slots. In this example, the slot represents the flight number slot. The entity in this example specifically represents the specific flight number "CN11123". For another example, in a certain weather application scenario, the intent associated with the user says type of node can include utterances such as "I want to check the weather". In this example, the slot can represent the city. The entity in this example specifically represents the specific city name such as "Beijing".

[0053] It can be understood that a node can have relationship information, and therefore the relationship information and configuration information of a node can be extracted to generate a node component. However, in some application scenarios, if the relationship information of a node is insufficient, for example, if it is detected that a node in the user-boxed area is not connected to other nodes by a directed edge, the extraction of the information of the node with insufficient relationship information can be abandoned, and the generated node component can not include the isolated node with insufficient relationship information.

[0054] To facilitate user operation, in this embodiment, the area of the node and edge selected by the user in the dialogue architecture can be displayed in a color different from other parts of the dialogue architecture. For example, as shown in FIG. 6, the user can select a node and a directed edge in the dialogue architecture, and the selected node and edge can be displayed in a color different from other parts of the dialogue architecture. Figure 2aThe graphical interface diagram 202 shows that the user selects the region 204. The nodes and edges in the region 204 are in a selected state and correspond to a color, which is visually distinguished from the nodes and edges not selected by the user. After the user selects the region, the interface displays a pop-up window 208. The pop-up window 208 displays a button of “grouping”, which is used to trigger a grouping request. When the user clicks the “grouping”, the corresponding grouping request is initiated. To facilitate the management of the node component, after the user clicks the “grouping”, a pop-up window 210 for the user to name the node component can be popped up. After the user names the node component, the user can click “save grouping” to save the grouping in the dialog architecture. In addition, the graphical interface 202 displays another button “copy”. The “copy” is used to copy the empty node of the same node type, relationship information, and configuration information. Details are not described herein. It should be noted that, Figure 2a The graphical interface diagram is only used to schematically illustrate the method provided by the embodiments of the present disclosure and does not limit the method. The graphical interface of the method provided by the embodiments of the present disclosure can present different display effects and interactive modes according to the needs of the implementation scenario.

[0055] Step 108: generating a reusable node component by using the relationship information and configuration information of the existing node.

[0056] For example, the node component is generated by using the relationship information and configuration information of the existing node. Figure 3 As shown in the structural diagram of the dialog architecture, when one or more regions in the dialog architecture are selected by the user, a node component can be generated for each region. For example, the node component 302 is generated for the “Group-1” region. The topology structure and associated configuration of all nodes in the “Group-1” region are contained in the node component 302.

[0057] For example, after the relationship information and configuration information of the selected node are extracted, the node component can be directly generated. For another example, before the generation, the extracted information can be displayed to the user according to the needs of the implementation scenario. At the same time, an editing mode for editing the information of the node component can be provided, so that the user can adjust the information as needed before generating the node component. In the case where the user does not need to adjust, the generation of the node component is further confirmed.

[0058] It is understood that nodes within a node component, relative to other nodes in the dialogue architecture, possess grouping information. Therefore, in the graphical interface, node components can be marked to facilitate user operations. For example, to facilitate user operations on node components, the method can also mark the area where the node component is located in the dialogue architecture within the graphical interface and display corresponding operation icons for that area. These operation icons are associated with operation labels, including one or more of the following: naming (e.g., renaming), ungrouping, and saving. Specifically, the naming operation label is used by the user to trigger the renaming operation of the node component; the ungrouping operation label is used by the user to trigger the ungrouping of the node component; and the saving operation label is used by the user to trigger the saving of the node component.

[0059] For example, if a user triggers the naming operation tab, the node component can be named after the user's input name; if the user triggers the ungrouping operation tab, the node component can be ungrouped in the dialog architecture and the label of the area where the node component is located can be removed from the graphical interface; if the user triggers the save operation tab, the node component can be saved in the system default or user-specified location. For example, if a user modifies the information of one or more nodes in a node component in the dialog architecture and wants to save the modified node component, they can trigger a rename operation on the modified node component and save the renamed node component. In this way, the reuse of previously generated and named node components is not affected, and a new node component can be obtained for reuse. As another example, if a user wants to add or delete nodes in the node components displayed in the dialog architecture, they can trigger an ungrouping operation, add or delete nodes, and then regroup them.

[0060] For example, after saving the group, such as Figure 2b The graphical interface diagram 212 shown depicts the "SMS Sending" node component, which is marked by a rectangle within the dialog structure. Furthermore, the interface displays operation icons 214 for the node component. When the user clicks an operation icon 214, a pop-up window 216 appears, listing four operation tabs: "Rename," "Ungroup," "Copy," and "Save to Component Library."

[0061] For example, after generating a reusable node component, a setting input corresponding to the reusable node component can be received. The setting input is used to indicate the position of the node component in the dialogue architecture. Based on the position corresponding to the setting input, a node component is added to the dialogue architecture.

[0062] As can be seen, since the method provides a graphical interface for generating a dialogue architecture including a plurality of nodes and inter-node relationships, receives a grouping request corresponding to one or at least two existing nodes with relationships in the dialogue architecture displayed by the graphical interface, extracts relationship information and configuration information of the nodes selected by the user from the dialogue architecture in response to the grouping request, and generates a reusable node component using the relationship information and configuration information of the existing nodes, it can be seen that the method provides the user with a new way of splitting node components in the graphical interface, which is a new dialogue construction carrier, so that the user can conveniently and flexibly split the reusable node component by, for example, a selection operation. The node component has corresponding relationship information and configuration information, and is a dialogue construction carrier with a finer granularity than the dialogue architecture, and the user does not need to set inter-node relationships and configuration information, which helps to improve the construction efficiency of the dialogue architecture. For example, in a complex actual application scenario, there is often a fragment that can be reused in the dialogue architecture, and the user initiates a grouping request for the selected nodes, thereby generating a dialogue construction carrier with a finer granularity than the dialogue architecture, i.e., a node component, thereby achieving more flexible knowledge management and reuse.

[0063] It should be noted that in actual applications, the actual display effect and other functions of the graphical interface can be set according to the needs of the implementation scenario, and the method provided in the embodiments of the present application does not limit this. For example, in the graphical interface, different colors of nodes can represent different node types, such as green representing user-said-type nodes and blue representing robot-reply-type nodes. For another example, when the user clicks on a node, the configuration information of the node can be displayed on the interface so that the user can edit the configuration information. For another example, the controls on the graphical interface can be displayed in an overlaid manner according to the current user needs. In addition, after the relationship information and configuration information of the node are extracted, the relevant information can be displayed for the user to confirm the generation of the node component, or the user can not be prompted, and the generation of the node component is considered to be confirmed by default. In order to make the dialogue architecture display a three-dimensional hierarchical effect, the connection lines between nodes can be adaptively deformed when the nodes are pulled. On the graphical interface, operation buttons such as "organize", "copy", and "paste" can also be provided for the dialogue architecture. For example, organize: can be used to adjust the layout display effect of the dialogue architecture; copy: can be used to copy a blank node of the same node type with empty relationship information and configuration information, which can be pasted in the current dialogue architecture. In addition, for the configuration items of "intent", "slot", "entity", and "function" of the node, the user can open the corresponding detail page to edit the information therein.

[0064] In actual applications, the configuration information of the node can include a plurality of different configuration items, and some configuration items are configured hierarchically by dependency. For example, as shown in FIG. 6, the configuration information of the node includes an intent configuration item, a slot configuration item, an entity configuration item, and a function configuration item. The intent configuration item includes a name, a description, and a type. The slot configuration item includes a name, a description, and a type. The entity configuration item includes a name, a description, and a type. The function configuration item includes a name, a description, and a type. Figure 4The configuration page of the "trip expense confirmation" node in the graphical interface diagram is shown, the node is directly associated with the intention configuration item "trip application intention", the content of the "trip application intention" configuration item includes a dependency on the slot parameter configuration item "type", and the content of the slot parameter configuration item "type" can further include a dependency on an entity configuration item such as "trip expense type". Therefore, in one or more embodiments of the present specification, the configuration information of the corresponding existing node extracted from the dialogue architecture includes: from the dialogue architecture, according to the hierarchy of the dependency relationship between different configuration items of the existing node, the configuration information is extracted layer by layer. In this embodiment, when extracting the configuration information, the configuration dependency analysis is performed layer by layer, and the hierarchical extraction of the configuration content is performed, which not only meets the needs of the dependency relationship between different configuration items in the configuration information, but also can completely extract the configuration information of the node, so that a node component with complete configuration information can be generated.

[0065] For example, the process of layer-by-layer extraction can be as follows: the content of the configuration item directly associated with the existing node is extracted from the dialogue architecture; the directly associated configuration item is taken as the current layer configuration item; it is judged whether there is a next layer configuration item with a dependency relationship in the content of the current layer configuration item in the dialogue architecture; if not, the extraction of the configuration information of the existing node is ended; if there is, the next layer configuration item dependent on the content of the current layer configuration item is extracted from the dialogue architecture, and the next layer configuration item is taken as the current layer configuration item, and the step of judging whether there is a next layer configuration item with a dependency relationship in the content of the current layer configuration item is re-entered.

[0066] It can be understood that the node component generated by the method provided in the embodiments of the present specification can be reused in the dialogue architecture from which the node component is extracted, or can be reused in other dialogue architectures. In order to facilitate reuse, in one or more embodiments of the present specification, the method can further save the node component to a component library, and the component library is used to save and provide reusable node components.

[0067] In another or more embodiments, in order to improve the reuse rate, the method further includes: pushing a message sharing the node component to other users. Wherein, the range of the node component pushed can be determined according to the implementation scenario. For example, a developer user generates a node component using a dialogue robot platform, and the dialogue robot platform can push the node component to other users within the enterprise of the developer. For another example, the dialogue robot platform generates a system-level node component, and the dialogue robot platform can push the node component to all system users.

[0068] The following describes the embodiments of the present specification in conjunction with the accompanying Figure 2a and the accompanying Figure 2bThe graphical interface diagram is shown. The method for processing a dialogue to construct a carrier provided in the specification is further described in the process of generating the node component "SMS delivery" by the user on the graphical interface in the ticket purchase process scenario. As shown in Figure 2a and Figure 2b As shown, the user's operation process on the graphical interface is as follows:

[0069] In the initiation of the grouping stage, as shown in Figure 2a The graphical interface diagram 202 shows that the user freely selects the region 204 in the dialogue architecture displayed on the graphical interface 202. The region 204 includes several nodes such as "train ticket purchase process query". When the user selects, the user clicks "grouping" on the pop-up window 208 to initiate a grouping request. According to the method for processing a dialogue to construct a carrier provided in the embodiment of the specification, the internal edges and configuration information of the selected nodes are extracted to form a subgraph for grouping to generate a node component. The graphical interface pops up a pop-up window 210 for the user to name the node component. In the pop-up window 210, the user can name the node component as "SMS delivery" and save the grouping in the dialogue architecture.

[0070] As shown in Figure 2b The graphical interface diagram 212 shows that after saving the node component "SMS delivery", the node component "SMS delivery" is marked by a rectangular frame in the dialogue architecture. In addition, the interface also displays the operation icon 214 for the node component "SMS delivery". When the user clicks the operation icon 214, a pop-up window 216 can be popped up, which lists four operation labels "rename", "ungroup", "copy", and "save to component library". If the user clicks "rename", an input box for inputting a new name is popped up, and the user can modify the component name of the "SMS delivery" node component.

[0071] As shown in Figure 2b As shown in the graphical interface diagram 212, when the user clicks "save to component library", the user can save the generated node component "SMS delivery" to the component library for sharing. For example, the user can also save the node component generated in the dialogue architecture to the component library through other ways such as dragging. In addition, as shown in the graphical interface diagram 212, the user can also be prompted on the interface to "click to add component to the canvas to complete the operation". When the user clicks the plus sign on the node component "SMS delivery", the corresponding "SMS delivery" node component can be added to the canvas. In addition, in order to facilitate the user to find the required node component, the graphical interface can also provide a query box for querying the node component. The user can input the keywords of the name, arbitrary configuration information, etc. of the node component to query the node component.

[0072] To facilitate the reusability of the node component, the graphical interface can also provide a trigger button for "importing component library" and "exporting component library". The method of the embodiment can save the node component selected by the user for importing into the component library in response to the user initiating an importing component request for the component library displayed by the graphical interface; and / or save the node component selected by the user for exporting from the component library to a user-specified location in response to the user initiating an exporting component request for the component library displayed by the graphical interface.

[0073] Next, a method for processing a dialogue construction carrier according to another embodiment of the present specification is described in detail. Figure 5 The reference process of the generated node component is described in detail. Figure 5 A flowchart of a method for processing a dialogue construction carrier according to another embodiment of the present specification is shown, including steps 502 to 512.

[0074] Step 502: providing a graphical interface for generating a dialogue architecture, the dialogue architecture containing a plurality of nodes and relationships between the nodes.

[0075] Step 504: receiving a grouping request corresponding to one or at least two existing nodes with relationships in the dialogue architecture displayed by the graphical interface.

[0076] Step 506: in response to the grouping request, extracting relationship information and configuration information of the corresponding existing nodes from the dialogue architecture.

[0077] Step 508: generating a reusable node component using the relationship information and configuration information of the existing nodes.

[0078] Step 510: in response to receiving a reference operation on the node component, obtaining the relationship information and configuration information of the referenced node component.

[0079] Step 512: adding the relationship information and configuration information of the referenced node component to the dialogue architecture displayed by the graphical interface.

[0080] For example, the method can also include receiving a setting input corresponding to the referenced node component, the setting input indicating the position of the referenced node component in the dialogue architecture. The adding of the relationship information and configuration information of the referenced node component to the dialogue architecture displayed by the graphical interface can include adding the referenced node component to the dialogue architecture according to the position corresponding to the setting input.

[0081] It should be noted that after adding the node component to the dialogue architecture, the user can also autonomously modify any one or more nodes in the node component in the graphical interface as needed. For example, as shown in Figure 2bAs shown in the graphical interface schematic diagram 218, after the user reuses the "short message sending" node component, according to the requirement of the flight ticket purchase process query, the user replaces the "train ticket purchase process query" node in the reused "short message sending" node component with the "flight ticket purchase process query" node.

[0082] Since the method, in response to receiving the reference operation on the node component, acquires the relationship information and the configuration information of the referenced node component, and adds the relationship information and the configuration information of the referenced node component to the dialogue architecture displayed in the graphical interface, it can be seen that the method provides the user with a new type of dialogue construction carrier, i.e., the reference node component, in the graphical interface, so that the user can conveniently add the node component with existing relationship information and configuration information through the reference operation, avoid setting the relationship between nodes and the configuration information for each node, reduce the user configuration cost, and improve the construction efficiency of the dialogue architecture.

[0083] The source of the node component described in the embodiment is not limited. For example, the node component can be saved in the component library, can be generated in the current dialogue architecture, or can be saved in any other location. In the embodiment of referencing the node component generated in the current dialogue architecture, the user can generate a customized node component from a fragment of a high-frequency dialogue architecture in an application scenario, and quickly reuse it, which has strong timeliness and solves the personalized long-tail demand of the user in a complex application scenario.

[0084] In the embodiment in which the node component is derived from the component library, the method of acquiring the relationship information and the configuration information of the referenced node component in response to receiving the reference operation on the node component includes: acquiring the relationship information and the configuration information of the referenced node component from the component library in response to receiving the reference operation on the node component in the graphical interface display, and the component library is used to save and provide reusable node components. In this embodiment, through the management function of the component library, the user can acquire node components with various dialogue fragment functions from the component library, thereby improving the dialogue construction efficiency.

[0085] In order to improve the reusability of the node component, in one or more embodiments of the present specification, the method can further include: in response to receiving an import component request initiated by the component library displayed in the graphical interface, saving the selected imported node component to the component library; and / or, in response to receiving an export component request initiated by the component library displayed in the graphical interface, saving the selected exported node component in the component library to a user-specified location.

[0086] It should be noted that the node component can be referenced in any dialogue architecture. The introduced information is new information relative to the dialogue architecture, which may conflict with the original information of the dialogue architecture. For example, assuming that a node component is referenced to the current dialogue architecture, the node component has an intent, and the current dialogue architecture also has an intent with the same name, but the key configuration contents of the two intents with the same name conflict. The name of the intent of the newly referenced node can be changed or the name of the original intent of the dialogue architecture can be changed to solve the conflict. After the conflict is solved, the referenced node component is imported. For another example, assuming that the entity dependent on the intent configuration of the referenced node does not exist in the original dialogue architecture. In order to ensure the normal function of the node component, a new entity can be inserted, and the content of the entity is the content of the new entity, so that the function of the node component can be realized.

[0087] It can be seen that when the node component is introduced, the corresponding conflict resolution strategy can be preset according to the implementation scene to update the information to solve the conflict. Specifically, the method can further include: judging whether the information of the referenced node component has information that conflicts with the original information of the dialogue architecture; if so, updating the information of the referenced node component and / or the original information of the dialogue architecture according to the preset conflict resolution strategy, or abandoning to reference the node component.

[0088] In addition, since the configuration items have complex hierarchical dependency relationships, the conflicting configuration items can be solved layer by layer. After solving the underlying configuration conflict, the dependency relationship between the configuration items in the hierarchy can also be updated. Specifically, the judgment of whether the information of the referenced node component has information that conflicts with the original information of the dialogue architecture includes: judging whether the configuration information of the referenced node component has information that conflicts with the original information of the dialogue architecture layer by layer according to the hierarchy of the dependency relationship between different configuration items of the referenced node component. The method further includes: if the updated configuration item has other configuration items that have a dependency relationship with it, updating the dependency relationship of the other configuration items to the updated configuration item accordingly. For example, after modifying the name of an entity of a node of a newly introduced node component, other configuration items in the upper layer that depend on the entity, such as "slot" configuration, need to modify the name of the entity to update the dependency relationship.

[0089] For example, when the node component is referenced, the conflict detection and resolution can be performed through the following four steps:

[0090] Step one: detecting content extraction, that is, extracting the content in the current node that needs to be detected for conflict. For example, extracting the node name and associated configuration of the node component detected currently, and extracting the node name and associated configuration of the node in the dialogue architecture that may have a conflict.

[0091] Step 2: Conflict detection, which involves checking whether there are any conflicts in the extracted content. Specifically, conflict judgment criteria can be preset based on the type of the current node and the usage rules in actual applications.

[0092] Step 3: Conflict resolution, which means that when a conflict exists, any conflict resolution strategy that matches the conflict from the preset conflict resolution strategies is used to resolve it.

[0093] For example, the preset conflict resolution strategy may include:

[0094] Overlay strategy, used to replace existing information with new information in response to conflicting information;

[0095] Inheritance strategy is used to replace new information with existing information when there is conflict.

[0096] The merging strategy is used to address conflicting information by merging newly added information with existing information and using it as the currently used information.

[0097] The update strategy is used to modify newly added information according to a preset modification method to ensure that it does not conflict with the original information in the case of conflicting information.

[0098] If you choose not to reference the node component, you can terminate this process.

[0099] To improve the efficiency of conflict detection and resolution, such as Figure 8 The conflict resolution flowchart shown first performs conflict detection on the critical information of the nodes. If the critical information does not conflict, then the complete configuration information of the nodes is checked. If critical information conflicts, an update strategy is used to resolve the conflict. If critical information does not conflict but non-critical information conflicts, a merge strategy is used. This two-stage conflict resolution strategy, addressing both critical and non-critical information, avoids redundant related data. Therefore, the update strategy can be used when the conflicting information is critical information of the node, such as the name of the node or intent. Critical information must be unique and cannot be duplicated; therefore, conflict resolution for this type of content generally uses an update strategy. Since nodes often rely on critical configuration information (such as intent names or unique identifiers) to form dependencies, when critical information is passively updated due to the conflict resolution strategy, the dependencies generally need to be modified synchronously according to step four mentioned below. The merge strategy can be used when the conflicting information is non-critical information of the node.

[0100] Step 4: Update dependencies.

[0101] It can be seen from the above embodiments that, by applying the method for processing the dialogue construction carrier provided in the embodiments of the present specification to the robot dialogue platform, the user can find the rule of assembling and splicing between dialogue architecture fragments, which can be the cornerstone of dialogue architecture construction, improve the user work efficiency, even help the user form the idea of constructing dialogue architecture, and is simple, efficient and easy to use, and can reduce the user configuration cost.

[0102] Corresponding to the method for processing the dialogue construction carrier, the present specification also provides an apparatus for processing the dialogue construction carrier, Figure 6 Fig. 1 shows a structural schematic diagram of an apparatus for processing the dialogue construction carrier provided in an embodiment of the present specification. As shown in the figure, Figure 6 the apparatus comprises an interface providing module 602, a request receiving module 604, an information extracting module 606 and a component generating module 608.

[0103] The interface providing module 602 can be configured to provide a graphical interface for generating a dialogue architecture, wherein the dialogue architecture comprises a plurality of nodes and the relationship between the nodes.

[0104] The request receiving module 604 can be configured to receive a grouping request of one or at least two existing nodes with relationship in the dialogue architecture displayed by the graphical interface.

[0105] The information extracting module 606 can be configured to extract the relationship information and configuration information of the corresponding existing nodes from the dialogue architecture in response to the grouping request.

[0106] The component generating module 608 can be configured to generate a reusable node component by using the relationship information and configuration information of the existing nodes.

[0107] As can be seen, the device provides a graphical interface for generating a dialogue architecture, receives a grouping request corresponding to one or at least two existing nodes with a relationship in the dialogue architecture displayed in the graphical interface, extracts relationship information and configuration information of the corresponding existing nodes from the dialogue architecture in response to the grouping request, and generates a reusable node component using the relationship information and configuration information of the existing nodes. As can be seen, the device provides a user with a way of splitting a node component, a new dialogue construction carrier in the graphical interface, so that the user can conveniently and flexibly split a reusable node component through, for example, a simple selection operation. The node component has corresponding relationship information and configuration information, and is a dialogue construction carrier with a finer granularity than the dialogue architecture. The user does not need to set the relationship and configuration information, which helps to improve the construction efficiency of the dialogue architecture. For example, in a complex actual application scenario, there is often a fragment of the dialogue architecture that can be reused. The user initiates a grouping request for the selected node, and a dialogue construction carrier with a finer granularity than the dialogue architecture, i.e., a node component, is generated, thereby realizing more flexible knowledge management and reuse.

[0108] Figure 7 A structural schematic diagram of a device for processing a dialogue construction carrier provided by another embodiment of the present specification is shown. As shown in Figure 7 The device can further include an information input module 620, which can be configured to receive input of one or more nodes and relationships between the nodes, and receive input of configuration information of the nodes. A dialogue forming module 622 can be configured to form a dialogue architecture according to the received input of one or more nodes, relationships between the nodes, and configuration information of the nodes.

[0109] To facilitate user operation of the node component, the device can further include a node component operation module 610, which can be configured to mark a region in the dialogue architecture where the node component is located in the graphical interface, and display a corresponding operation icon for the region. The operation icon is associated with an operation label, and the operation label includes one or more of a naming operation label, an ungrouping operation label, and a saving operation label. The naming operation label is used for user triggering of a node component renaming operation. The ungrouping operation label is used for user triggering of ungrouping of the node component. The saving operation label is used for user triggering of saving of the node component.

[0110] In actual applications, the configuration information of a node can include a plurality of different configuration items, and some configuration items are configured hierarchically by dependency relationships. Therefore, in one or more embodiments of the present specification, the information extraction module 606 can be configured to extract configuration information from the dialogue architecture according to the hierarchy of dependency relationships between different configuration items of the node selected by the user, layer by layer. In this embodiment, when extracting configuration information, configuration dependency analysis is performed layer by layer, and hierarchical extraction of configuration content is performed, which meets the needs of dependency relationships between different configuration items in configuration information and enables complete extraction of configuration information of a node, thereby enabling the generation of a node component with complete configuration information and reusability.

[0111] To improve the reusability, in one or more embodiments of the present specification, as shown in Figure 7 the apparatus can further include a component sharing module 612, which can be configured to save the node component to a component library, and / or push a message sharing the node component to other users, the component library being configured to save and provide reusable node components.

[0112] After generating the new dialogue construction carrier of a node component, the node component can also be referenced. Specifically, as shown in Figure 7 the apparatus can further include a response referencing module 630 and a component adding module 632.

[0113] The response referencing module 630 can be configured to acquire relationship information and configuration information of a referenced node component in response to a user performing a referencing operation of the node component in a graphical interface.

[0114] The component adding module 632 can be configured to add the relationship information and configuration information of the referenced node component to a dialogue architecture displayed in the graphical interface.

[0115] Since the apparatus acquires relationship information and configuration information of a referenced node component in response to a user performing a referencing operation of the node component in a graphical interface, and adds the relationship information and configuration information of the referenced node component to a dialogue architecture displayed in the graphical interface, it can be seen that the apparatus provides a user with an operation mode of referencing a new dialogue construction carrier of a node component in a graphical interface, so that the user can conveniently add a node component with existing relationship information and configuration information through a simple referencing operation, avoids the user from setting the structure of relationships between nodes and configuration information for each node, reduces the configuration cost of the user, and improves the construction efficiency of a dialogue architecture.

[0116] To facilitate the user to add the referenced node component to a desired position, in one embodiment, as shown in Figure 7As shown, the apparatus can further include a setting input receiving module 640, which can be configured to receive a setting input corresponding to the referenced node component, the setting input being used to indicate a position of the referenced node component in the dialogue architecture. Accordingly, the component adding module 632 can be configured to add the referenced node component in the dialogue architecture according to the position corresponding to the setting input.

[0117] The source of the node component described in the embodiment is not limited. For example, it can be a node component saved in a component library, a node component generated in a current dialogue architecture, or a node component saved in any other location. For example, in an implementation where the source of the node component is the component library, the response referencing module 630 can be configured to, in response to receiving a reference operation on a node component displayed in the graphical interface of the component library, obtain relationship information and configuration information of the referenced node component from the component library according to the reference operation, the component library being used to save and provide reusable node components.

[0118] In order to improve the reusability of the node component, as Figure 7 As shown, the apparatus can further include a component library operation module 650, which can be configured to, in response to receiving an import component request initiated by the component library displayed in the graphical interface, save the selected imported node component to the component library; and / or, in response to receiving an export component request initiated by the component library displayed in the graphical interface, save the selected exported node component in the component library to a specified location. The specified location can be specified by the user or be the system default.

[0119] It should be noted that the node component can be referenced in any dialogue architecture. When the dialogue architecture references the node component, the introduced information is new information relative to the dialogue architecture, which can conflict with the original information of the dialogue architecture. Therefore, when the node component is introduced, the corresponding conflict resolution strategy can be preset according to the implementation scenario to update the information to resolve the conflict. Specifically, as Figure 7 As shown, the apparatus further includes a conflict judgment module 660 and a conflict resolution module 662.

[0120] The conflict judgment module 660 can be configured to judge whether there is information in the information of the referenced node component that conflicts with the original information of the dialogue architecture.

[0121] The conflict resolution module 662 can be configured to, if the conflict judgment module 660 determines that there is, update the information of the referenced node component and / or the original information of the dialogue architecture according to the preset conflict resolution strategy, or give up referencing the node component.

[0122] In addition, since there is a complex hierarchical dependency relationship between the configuration items, the conflicting configuration items can be solved layer by layer. After solving the underlying configuration conflict, the dependency relationship between the configuration items in different layers can also be updated. For example, the conflict judgment module 660 can be configured to judge, layer by layer, whether there is information in the configuration information of the referenced node component that conflicts with the original information of the dialogue framework according to the hierarchy of the dependency relationship between different configuration items of the referenced node component. Accordingly, as shown in Figure 7 The device can also include a dependency updating module 664, which can be configured to update the dependency relationship of other configuration items to the updated configuration item if there are other configuration items that have a dependency relationship with the updated configuration item.

[0123] The preset conflict resolution strategy can include:

[0124] a coverage strategy, which is used to replace the original information with the newly added information for the conflicting information;

[0125] or

[0126] an inheritance strategy, which is used to replace the newly added information with the original information for the conflicting information;

[0127] or

[0128] a merging strategy, which is used to merge the newly added information and the original information as the currently used information for the conflicting information;

[0129] or

[0130] an updating strategy, which is used to modify the newly added information according to a preset modification manner so that it does not conflict with the original information for the conflicting information.

[0131] In order to improve the efficiency of conflict detection and conflict resolution, the key information of the node can be detected for conflict first, and then the complete configuration information of the node can be detected in the case that the key information does not conflict. In the case that the key information conflicts, the updating strategy is used to solve the conflict of the key information, and in the case that the key information does not conflict and the non-key information conflicts, the merging strategy is used to solve the conflict. Through the conflict resolution strategy in two stages of key information and non-key information, the associated data redundancy problem is avoided. Therefore, the updating strategy can be used when the conflicting information is the key information of the node. The merging strategy can be used when the conflicting information is the non-key information of the node.

[0132] The above is a schematic scheme of the device for constructing a reference dialogue carrier according to the embodiment. It should be noted that the technical scheme of the device for constructing a reference dialogue carrier is the same as the technical scheme of the method for constructing a reference dialogue carrier, and the details of the technical scheme of the device for constructing a reference dialogue carrier that are not described in detail can be referred to the description of the technical scheme of the method for constructing a reference dialogue carrier.

[0133] Figure 9 A structural block diagram of a computing device 900 according to one embodiment of the present specification is shown. The components of the computing device 900 include, but are not limited to, a memory 910 and a processor 920. The processor 920 is connected with the memory 910 through a bus 930, and a database 950 is used to save data.

[0134] The computing device 900 also includes an access device 940, which enables the computing device 900 to communicate via one or more networks 960. Examples of these networks include a public switched telephone network (PSTN), a local area network (LAN), a wide area network (WAN), a personal area network (PAN), or a combination of communication networks such as the Internet. The access device 940 can include one or more of any type of network interface (e.g., a network interface card (NIC)) such as an IEEE 802.8 wireless local area network (WLAN) wireless interface, a worldwide interoperability for microwave access (Wi-MAX) interface, an Ethernet interface, a universal serial bus (USB) interface, a cellular network interface, a Bluetooth interface, a near field communication (NFC) interface, and the like, wired or wireless.

[0135] In one embodiment of the present specification, the above-mentioned components of the computing device 900 and other components not shown in the above-mentioned components can be connected with each other, for example, through a bus. It should be understood that Figure 9 Figure 9 The structural block diagram of the computing device shown is only for the purpose of example, and is not a limitation on the scope of the present specification. Other components can be added or replaced as needed by those skilled in the art.

[0136] The computing device 900 can be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., a tablet computer, a personal digital assistant, a laptop computer, a notebook computer, a netbook, etc.), a mobile phone (e.g., a smartphone), a wearable computing device (e.g., a smartwatch, smart glasses, etc.), or other types of mobile devices, or a stationary computing device such as a desktop computer or a PC. The computing device 900 can also be a mobile or stationary server.

[0137] In one aspect, the processor 920 is configured to execute computer-executable instructions as follows:

[0138] ​In response to the user selecting a node in the dialog architecture displayed in the graphical interface and initiating a grouping request, relationship information and configuration information of the selected node are extracted from the dialog architecture, and a reusable node component is generated using the relationship information and the configuration information of the selected node.

[0139] The above is a schematic solution of the computing device of the embodiment. It should be noted that the technical solution of the computing device and the technical solution of the method for processing the dialog construction carrier belong to the same concept, and the details of the technical solution of the computing device that are not described in detail can be referred to the description of the technical solution of the method for processing the dialog construction carrier.

[0140] On the other hand, the processor 920 is configured to execute the following computer executable instructions:

[0141] In response to the user performing a reference operation of the node component in the graphical interface, relationship information and configuration information of the referenced node component are obtained, and the relationship information and the configuration information of the referenced node component are added to the dialog architecture displayed in the graphical interface.

[0142] The above is a schematic solution of the computing device of the embodiment. It should be noted that the technical solution of the computing device and the technical solution of the method for processing the dialog construction carrier belong to the same concept, and the details of the technical solution of the computing device that are not described in detail can be referred to the description of the technical solution of the method for processing the dialog construction carrier.

[0143] An embodiment of the present specification also provides a computer readable storage medium storing computer instructions.

[0144] On the other hand, the processor 920 is configured to execute the following computer executable instructions:

[0145] In response to the user selecting a node in the dialog architecture displayed in the graphical interface and initiating a grouping request, relationship information and configuration information of the selected node are extracted from the dialog architecture, and a reusable node component is generated using the relationship information and the configuration information of the selected node.

[0146] The above is a schematic solution of the computer readable storage medium of the embodiment. It should be noted that the technical solution of the storage medium and the technical solution of the method for generating the dialog construction carrier belong to the same concept, and the details of the technical solution of the storage medium that are not described in detail can be referred to the description of the technical solution of the method for generating the dialog construction carrier.

[0147] On the other hand, the processor 920 is configured to execute the following computer executable instructions:

[0148] In response to the user's referencing operation on the node component in the graphical interface, the relationship information and the configuration information of the referenced node component are acquired, and the relationship information and the configuration information of the referenced node component are added to the dialogue architecture displayed in the graphical interface.

[0149] The above is a schematic scheme of the computer readable storage medium of the embodiment. It should be noted that the technical scheme of the storage medium and the technical scheme of the reference dialogue construction carrier method described above belong to the same concept, and the details of the technical scheme of the storage medium which are not described in detail can be referred to the description of the technical scheme of the reference dialogue construction carrier method.

[0150] The above describes specific embodiments of the present specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different than the order in which they are recited in the embodiments and still achieve desirable results. In addition, the processes depicted in the figures do not necessarily require the particular order shown, or sequential order, to achieve the desired results. In certain implementations, multitasking and parallel processing can be advantageous or necessary.

[0151] The computer readable medium can include any entity or device capable of carrying the computer program code, recording medium, U disk, mobile hard disk, magnetic disk, optical disk, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium, etc. It should be noted that the content contained in the computer readable medium can be appropriately increased or decreased according to the requirements of legislation and patent practice in the jurisdiction, for example, in some jurisdictions, according to legislation and patent practice, the computer readable medium does not include electrical carrier signals and telecommunication signals.

[0152] It should be noted that for the foregoing method embodiments, in order to facilitate description, they are all expressed as a combination of a series of actions, but those skilled in the art should know that the embodiments of the present specification are not limited by the order of the described actions, because according to the embodiments of the present specification, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should know that the embodiments described in the specification all belong to preferred embodiments, and the actions and modules involved are not necessarily all necessary for the embodiments of the present specification.

[0153] In the above-described embodiments, the description of each embodiment focuses on different aspects, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

[0154] The preferred embodiments of the present specification disclosed above are only used to help explain the present specification. The alternative embodiments do not describe all the details and limit the present application to the specific embodiments described. Obviously, according to the content of the embodiments of the present specification, many modifications and changes can be made. The present specification selects and specifically describes these embodiments in order to better explain the principles and practical applications of the embodiments of the present specification, so that those skilled in the art can well understand and utilize the present specification. The present specification is limited only by the claims and their full scope and equivalents.

Claims

1. A method for processing a dialog construction carrier, comprising: providing a graphical interface for generating a dialog architecture, the dialog architecture comprising a plurality of nodes and inter-node relationships; receiving a grouping request corresponding to one or at least two existing nodes with relationships in the dialog architecture displayed by the graphical interface; in response to the grouping request, extracting relationship information and configuration information of the corresponding existing nodes from the dialog architecture, wherein the configuration information of the corresponding existing nodes is extracted from the dialog architecture layer by layer according to a hierarchy of dependency relationships between different configuration items of the existing nodes, the configuration information comprising one or more configuration items defining node functions and corresponding configuration contents of the configuration items, and the relationship information comprising information describing a topology between nodes; generating a reusable node component using the relationship information and the configuration information of the existing nodes. 2.The method of claim 1, further comprising: receiving input of one or more nodes and inter-node relationships and input of configuration information of the nodes; forming the dialog architecture according to the received input of one or more nodes, inter-node relationships, and configuration information of the nodes. 3.The method of claim 1, further comprising: in the graphical interface, marking an area in the dialog architecture where the node component is located, and displaying a corresponding operation icon for the area, the operation icon being associated with an operation label, the operation label comprising one or more of a naming operation label, an ungrouping operation label, and a saving operation label; the naming operation label is used for triggering a node component renaming operation by a user; the ungrouping operation label is used for triggering an ungrouping operation of the node component by a user; the saving operation label is used for triggering a saving operation of the node component by a user. 4.The method of claim 1, further comprising: saving the node component to a component library, the component library being used to save and provide reusable node components; and / or pushing a message sharing the node component to other users. 5.The method of claim 1, further comprising: in response to receiving a reference operation on the node component, obtaining relationship information and configuration information of the referenced node component; adding the relationship information and the configuration information of the referenced node component to the dialog architecture displayed by the graphical interface. receiving a setting input corresponding to the referenced node component, the setting input being used to indicate a position of the referenced node component in the dialog architecture; 6. The method of claim 5, further comprising: the adding the relationship information and the configuration information of the referenced node component to the dialog architecture displayed by the graphical interface comprises: adding the referenced node component to the dialog architecture according to the position corresponding to the setting input. 7.The method of claim 5, the obtaining the relationship information and the configuration information of the referenced node component in response to receiving the reference operation on the node component comprises: ​ In response to receiving a reference operation on a node component in a component library displayed in a graphical interface, relationship information and configuration information of the referenced node component are obtained from the component library according to the reference operation, the component library being configured to store and provide reusable node components.

8. The method of claim 5, further comprising: determining whether information of the referenced node component conflicts with original information of the dialogue framework; if so, updating the information of the referenced node component and / or the original information of the dialogue framework according to a preset conflict resolution policy, or discarding the reference to the node component.

9. The method of claim 8, wherein the determining whether the information of the referenced node component conflicts with the original information of the dialogue framework comprises: determining, according to a hierarchy of dependency relationships between different configuration items of the referenced node component, whether configuration information of the referenced node component conflicts with the original information of the dialogue framework; the method further comprising: if the updated configuration item has other configuration items that depend on it, updating the dependency relationships of the other configuration items to the updated configuration item accordingly.

10. The method of claim 8, wherein the preset conflict resolution policy comprises: an overriding strategy for replacing original information with newly added information for conflicting information; or, an inheritance strategy for replacing newly added information with original information for conflicting information; or, a merging strategy for merging newly added information with original information for conflicting information as current information; or, an updating strategy for modifying newly added information according to a preset modification manner so that it does not conflict with the original information.

11. The method of claim 10, wherein the updating strategy is used when the conflicting information is key information of a node; and the merging strategy is used when the conflicting information is non-key information of a node.

12. An apparatus for processing a dialogue construction carrier, comprising: an interface providing module configured to provide a graphical interface for generating a dialogue framework, the dialogue framework including a plurality of nodes and relationships between the nodes; a request receiving module configured to receive a grouping request corresponding to one or at least two existing nodes with relationships in the dialogue framework displayed in the graphical interface; an information extracting module configured to extract relationship information and configuration information of the corresponding existing nodes from the dialogue framework in response to the grouping request, wherein the configuration information of the corresponding existing nodes is extracted from the dialogue framework according to a hierarchy of dependency relationships between different configuration items of the existing nodes, and the configuration information includes one or more configuration items defining the functionality of the nodes and configuration content corresponding to the configuration items, and the relationship information includes information describing the topology between the nodes; a component generating module configured to generate a reusable node component using the relationship information and the configuration information of the existing nodes.

13. A computing device, comprising: a memory and a processor; ​ The memory is configured to store computer-executable instructions, and the processor is configured to execute the computer-executable instructions. A graphical interface is provided for generating a dialogue architecture, the dialogue architecture comprising a plurality of nodes and relationships between the nodes. A grouping request is received for one or at least two existing nodes with relationships in the dialogue architecture displayed by the graphical interface. In response to the grouping request, relationship information and configuration information of the corresponding existing nodes are extracted from the dialogue architecture, wherein the configuration information of the corresponding existing nodes is extracted from the dialogue architecture layer by layer according to a hierarchy of dependency relationships between different configuration items of the existing nodes, and the configuration information includes one or more configuration items defining the functions of the nodes and corresponding configuration contents, and the relationship information includes information describing the topology between the nodes. A reusable node component is generated using the relationship information and the configuration information of the existing nodes.

14. A computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the steps of the method for processing a dialogue construction carrier according to any one of claims 1 to 11.

Images