Method and device for creating plug-in, equipment and storage medium

By using the plugin creation template to obtain information input components on the plugin creation page, the problem of high barriers to plugin creation has been solved, enabling users to quickly create plugins that meet their needs and improving the flexibility and efficiency of plugin use.

CN119002874APending Publication Date: 2024-11-22BEIJING ZITIAO NETWORK TECH CO LTD +1

Patent Information

Application Number
CN202311088356.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-08-25
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In existing technologies, the barrier to entry for plugin creation is relatively high, and users cannot flexibly create plugins that meet their own needs.

Method used

It provides a plugin creation page, which allows users to obtain plugin creation information through the information input component in the plugin creation template, and publish target plugins based on this information. It supports the creation of various types of plugins, such as Q&A and document plugins.

Benefits of technology

Users can quickly and easily create plugins that meet their own needs, improving the efficiency of interaction with the digital assistant and the flexibility of plugin use.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119002874A_ABST
    Figure CN119002874A_ABST
Patent Text Reader

Abstract

According to the embodiment of the invention, a plug-in creating method and device, equipment and a storage medium are provided. The method comprises the steps that a creation page used for creating a target plug-in is provided, the creation page presents a plug-in creation template corresponding to the type of the target plug-in to be created, and the plug-in creation template comprises at least one information input component; plug-in creation information about the target plug-in is obtained at least through at least one information input component in the plug-in creation template; and publishing a target plug-in based on the plug-in creation information, the published target plug-in being selectable for interaction of the user with the digital assistant. In this way, by means of the template, the user can conveniently and quickly complete the creation of the plug-in, and then the user can efficiently complete diversified operations by means of the plug-in in the interaction process with the digital assistant.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to methods, apparatuses, devices, and computer-readable storage media for creating plug-ins. Background Art

[0002] With the development of information technology, various terminal devices can provide various services to people in work and life. For example, applications that provide services can be deployed in terminal devices. Terminal devices or applications can provide users with digital assistant functions to assist users in using terminal devices or applications. Users can use plug-ins to complete various operations during the interaction with digital assistants. How to create plug-ins that meet user needs conveniently and quickly is a technical issue to be explored at present. Summary of the invention

[0003] In a first aspect of the present disclosure, a method for creating a plug-in is provided. The method includes: providing a creation page for creating a target plug-in, wherein the creation page presents a plug-in creation template corresponding to the type of the target plug-in to be created, and the plug-in creation template includes at least one information input component; obtaining plug-in creation information about the target plug-in via at least one information input component in the plug-in creation template; and publishing the target plug-in based on the plug-in creation information, and the published target plug-in can be selected for interaction between a user and a digital assistant.

[0004] In a second aspect of the present disclosure, a device for creating a plug-in is provided. The device includes: a page providing module, configured to provide a creation page for creating a target plug-in, wherein the creation page presents a plug-in creation template corresponding to the type of the target plug-in to be created, and the plug-in creation template includes at least one information input component; an information acquisition module, configured to obtain plug-in creation information about the target plug-in via at least one information input component in the plug-in creation template; and a plug-in publishing module, configured to publish the target plug-in based on the plug-in creation information, and the published target plug-in can be selected for user interaction with a digital assistant.

[0005] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect.

[0006] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.

[0007] It should be understood that the content described in this section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0009] Figure 1 A schematic diagram showing an example environment in which embodiments of the present disclosure can be implemented;

[0010] FIG. 2A to FIG. 2C A schematic diagram showing an example interface for initiating a plug-in creation request according to some embodiments of the present disclosure;

[0011] Figure 3A and Figure 3B A schematic diagram showing an example page of a creation page of a plug-in according to some embodiments of the present disclosure;

[0012] FIG. 4A to FIG. 4B A schematic diagram showing an example page of a publishing page of a plug-in according to some embodiments of the present disclosure;

[0013] Figure 5 A flowchart showing a process for creating a plug-in according to some embodiments of the present disclosure is shown;

[0014] Figure 6 A block diagram showing an apparatus for creating a plug-in according to some embodiments of the present disclosure; and

[0015] Figure 7 A block diagram of an electronic device is shown in which one or more embodiments of the present disclosure may be implemented. DETAILED DESCRIPTION

[0016] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0017] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may also be included below.

[0018] Herein, unless explicitly stated, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.

[0019] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.

[0020] It is understandable that before using the technical solutions disclosed in the various embodiments of the present disclosure, the types, scopes of use, usage scenarios, etc. of the information involved in the present disclosure should be informed to relevant users and their authorization should be obtained in an appropriate manner in accordance with relevant laws and regulations. The relevant users may include any type of right holders, such as individuals, enterprises, and groups.

[0021] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly prompt the relevant user that the operation requested to be performed will require obtaining and using the information of the relevant user, so that the relevant user can independently choose whether to provide information to software or hardware such as an electronic device, application, server or storage medium that executes the operation of the technical solution of the present disclosure based on the prompt message.

[0022] As an optional but non-limiting implementation, in response to receiving an active request from a relevant user, a prompt message is sent to the relevant user, for example, in the form of a pop-up window, in which the prompt message may be presented in text form. In addition, the pop-up window may also carry a selection control for the user to select "agree" or "disagree" to provide information to the electronic device.

[0023] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that meet relevant laws and regulations may also be applied to the implementation of the present disclosure.

[0024] Figure 1 A schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented is shown. In the example environment 100, an application 120 is installed in a terminal device 110. A user 140 can interact with the application 120 via the terminal device 110 and / or an attached device of the terminal device 110.

[0025] In some embodiments, the application 120 can be downloaded and installed on the terminal device 110. In some embodiments, the application 120 can also be accessed through other means, such as through a web page. Figure 1 In the environment 100, if the application 120 is started, the terminal device 110 can present the interface 150 of the application 120. The interface 150 may include various user interfaces that the application 120 can provide. The interface 150 is sometimes also referred to as a client interface.

[0026] Application 120 includes, but is not limited to, one or more of the following: chat application (also known as instant messaging application), document application, audio and video conferencing application, email application, task application, objectives and key results (OKR) application, and the like. Application 120 supports the use of plug-ins. Such plug-ins include, but are not limited to, one or more of the following: search plug-in, contact plug-in, message plug-in, document plug-in, table plug-in, email plug-in, calendar plug-in, schedule plug-in, task plug-in, and the like. In some embodiments, application 120 may include a multi-functional collaboration platform, such as an office collaboration platform (also known as an office suite) that can provide integration of various types of applications or components to facilitate people's office work, communication and other activities. In the multi-functional collaboration platform, people can start different applications or components as needed to complete corresponding information processing, sharing, communication, etc.

[0027] In some embodiments, the terminal device 110 communicates with the server 130 to provide services for the application 120. The terminal device 110 may be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the terminal device 110 may also support any type of interface for the user (such as a "wearable" circuit, etc.). The application 130 may be a computing system / server of various types that can provide computing power, including but not limited to a mainframe, an edge computing node, a computing device in a cloud environment, and the like.

[0028] It should be understood that the structure and function of the various elements in the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.

[0029] As briefly mentioned above, digital assistants can assist users in using terminal devices or applications. Some applications can provide integrated functions of different plug-ins. In addition to being able to have free conversations with digital assistants, users can also use natural language instructions to enable digital assistants to use different plug-ins to complete some more complex business-related operations related to the application, such as creating documents, inviting schedules, creating tasks, etc. Traditional plug-ins often require relevant professionals (such as the backend programmers of the application) to create. This will make the threshold for plug-in creation higher, and users cannot flexibly create plug-ins based on their own needs.

[0030] According to some embodiments of the present disclosure, an improved scheme for creating plug-ins is proposed. In an embodiment of the present disclosure, a creation page for creating a target plug-in is provided in the interaction window between the user and the digital assistant. A plug-in creation template is presented in the creation page. The plug-in creation information of the plug-in is obtained through at least one information input component in the plug-in creation template, and the plug-in is published based on the plug-in creation information. It can enable users to complete the creation of plug-ins conveniently and quickly, which helps users to efficiently complete various operations with the help of plug-ins during the interaction process with the digital assistant.

[0031] Some example embodiments of the present disclosure will be described in detail below with reference to examples of the accompanying drawings.

[0032] As described above, in an embodiment of the present disclosure, a digital assistant is used to interact with a user. An interaction window between a user and a digital assistant may be presented in a client interface. The interaction window between a user and a digital assistant may include a conversation window, in which the interaction between the user and the digital assistant may be presented in the form of a conversation message. Alternatively or additionally, the interaction window between a user and a digital assistant may also include other types of windows, such as a window in a floating window mode, in which a user may trigger the digital assistant to perform a corresponding operation by inputting instructions, selecting shortcut instructions, and the like. As an intelligent assistant, a digital assistant has intelligent dialogue and information processing capabilities. In the interaction window, a user inputs an interactive message, and the digital assistant provides a reply message in response to the user input. The client interface for providing a digital assistant may correspond to a single-function application or a multi-function collaboration platform, such as an office suite or other collaboration platform capable of integrating multiple components.

[0033] In some embodiments, multiple interaction modes between the user and the digital assistant can be provided, and the multiple interaction modes can be flexibly switched. When a certain interaction mode is triggered, the corresponding interaction area is presented to facilitate the interaction between the user and the digital assistant. The user interacts with the digital assistant in different ways in different interaction modes, so that it can be flexibly adapted to the interaction needs in different application scenarios.

[0034] In some embodiments, the digital assistant can be included in the current user's contact list in the office suite as a user's contact, or included in the information flow of the chat component. In some embodiments, the user has a corresponding relationship with the digital assistant. For example, the first digital assistant corresponds to the first user, the second digital assistant corresponds to the second user, and so on. In some embodiments, the first digital assistant can correspond uniquely to the first user, the second digital assistant can correspond uniquely to the second user, and so on. That is, the first digital assistant of the first user can be specific to or exclusive to the first user. For example, in the process of the first digital assistant providing assistance or service to the first user, the first digital assistant can use its historical interaction information with the first user, the data authorized by the first user that it can access, and the current interaction context with the first user. If the first user is an individual or an individual, the first digital assistant can be regarded as a personal digital assistant. It can be understood that in the disclosed embodiments, the first digital assistant is based on the authorized access to the data to which the permission is granted by the first user. It should be understood that "uniquely corresponding" or similar expressions in the present disclosure are not intended to limit the first digital assistant to be updated accordingly based on the interaction process between the first user and the first digital assistant.

[0035] In some embodiments, it is possible to provide information processing services specific to the user based on the historical interaction information between the user and the digital assistant and / or the data range specific to the user. In some embodiments, the historical interaction information of the user interacting with the digital assistant in multiple interaction modes can be stored in association with the user. In this way, in one interaction mode (any one or a specified one of the interaction modes) among the multiple interaction modes, the digital assistant can provide services to the user based on the historical interaction information stored in association with the user.

[0036] The digital assistant can be called or awakened by an appropriate means (e.g., shortcut keys, buttons, or voice) to present an interaction window with the user. In some embodiments, the digital assistant can be included in the current user's contact list in the application, or included in the information flow of the chat application as a contact of the user. By selecting the digital assistant, the interaction window with the digital assistant can be opened. The interaction window may include interface elements for information interaction, such as input boxes, message lists, message bubbles, and so on. In other embodiments, the digital assistant can be awakened through an entry control or menu provided in the page, or by inputting a preset instruction. In some embodiments described below, for ease of discussion, the interaction window between the user and the digital assistant is mainly illustrated as a conversation window.

[0037] FIG. 2A to FIG. 2CA schematic diagram of an example client interface 201 for initiating a plug-in creation request according to some embodiments of the present disclosure is shown. The client interface 201 may be implemented at the terminal device 110. Figure 1 describe FIG. 2A to FIG. 2C .

[0038] In some embodiments, in response to a user (e.g., user 140) waking up a digital assistant through a preset operation (e.g., selecting a digital assistant from a contact list), the terminal device 110 may display a session window (also referred to as a main session window) in which the user interacts with the digital assistant and a plug-in selection control. Through such a plug-in selection control, the user may select a plug-in to be used in the main session window.

[0039] In some embodiments, Figure 2A As shown, the main conversation window between the digital assistant (shown as "XX Assistant" in the figure) and the user is presented in area 210 of interface 201. The digital assistant can be regarded as one of the user's contacts and is presented in the information flow of the instant messaging application. The instant messaging application is presented in area 230 of interface 201, and the information flow is presented in area 220 of interface 201. The user selects the digital assistant in the instant messaging application to enter the main conversation window. The main conversation window includes a plug-in selection control 212. The user can select a plug-in to be used in the conversation window by clicking the plug-in selection control 212.

[0040] In some embodiments, the terminal device 110 responds to the user's preset operation (such as triggering a preset control, inputting a preset instruction or voice wake-up, etc.) to wake up the digital assistant in a page (such as a page for browsing a document), and displays a sub-session window for the user to interact with the digital assistant. Such a sub-session window includes a plug-in selection control. Through such a plug-in selection control, the user can select and use a plug-in in the sub-session window.

[0041] In some embodiments, in response to detecting a selection operation (e.g., a click operation) on the plug-in selection control 212, the terminal device 110 may present a plug-in selection panel 214. The plug-in selection panel 214 presents at least one pre-stored, created plug-in (e.g., Figure 2A In some embodiments, the plug-in selection panel 214 also presents a plug-in viewing control 216. In response to detecting a selection operation on the plug-in viewing control 216, the terminal device 110 presents all plug-ins included in the terminal device 110.

[0042] In some embodiments, in response to detecting a selection operation on the plug-in viewing control 216, the terminal device 110 may also present a plug-in setting page in the interface 201. For example, Figure 2BAs shown, in response to detecting Figure 2A In the plug-in view control 216 of the selection operation, the terminal device 110 can also present the plug-in setting page 240 in the interface 201. Figure 2B In the example, the plug-in setting page 240 is presented on the upper side of the interface 201 and is included in the interface 201. In other embodiments, it can be arranged in other ways as needed. For example, it can be switched from presenting the interface 201 to presenting the plug-in setting page 240.

[0043] In some embodiments, the plug-in setting page 240 provides a plug-in search function for searching for plug-ins from existing plug-ins. Figure 2B As shown, the plug-in setting page 240 includes a search box 242. The user can enter at least a portion of the name of the plug-in to be searched in the search box 242. In some embodiments, the plug-in setting page 240 can present search results in association with the search box 242. For example, if the user input received in the search box 242 is "search", the plug-in setting page 240 can present search results in association with the search box 242, such as "search plug-ins", "search contacts", "search documents", "search forms", etc. Additionally or alternatively, the plug-in selection panel provides a fuzzy search function.

[0044] In some embodiments, the plug-in setting page 240 further includes a control 243 and a control 244. For example, in response to detecting a selection operation on the control 243, the terminal device 110 may present all stored plug-ins (for example, a first group of plug-ins) in the plug-in setting page 240. Figure 2B As shown, in response to detecting a selection operation on control 243, the terminal device 110 presents all stored plug-ins such as plug-in 1, plug-in 2, plug-in 3, etc. at "existing plug-ins". All the plug-ins here can be created by the user himself, or they can be shared with the user after being created by other users for use by the user. For example, the terminal device 110 can present only the plug-ins created by the current user himself (for example, it can be called the second group of plug-ins) in the plug-in setting page 240 in response to detecting a selection operation on control 244. It can be understood that the first group of plug-ins includes the second group of plug-ins, and the number of plug-ins included in the first group of plug-ins should be greater than or equal to the number of plug-ins included in the second group of plug-ins. In some embodiments, in response to the plug-in setting page 240 being presented, the terminal device 110 can present the first group of plug-ins corresponding to the control 243 by default, and switch to presenting the second group of plug-ins when detecting a selection operation on the control 244.

[0045] In some embodiments, the plug-in setting page 240 also includes a plug-in creation area 245. The plug-in creation area 245 can be used to present a text description instructing the user to create a plug-in. A plug-in creation control 246 can also be presented in the plug-in creation area 245. The terminal device 110 can, for example, present a plug-in creation page in response to detecting a selection operation on the plug-in creation control 246. In some embodiments, before presenting the plug-in creation page, the terminal device 110 can also present a type selection page for selecting a plug-in type for the plug-in to be created in response to detecting a selection operation on the plug-in creation control 246. Exemplary, as Figure 2B as well as Figure 2C As shown, the terminal device 110 may present a type selection page 250 in response to detecting a selection operation on the plug-in creation control 246. Figure 2C In the description, only the type selection page 250 is presented on the upper side of the interface 201 and is included in the interface 201 as an example. In other embodiments, other arrangements may be performed as needed.

[0046] like Figure 2C As shown, the type selection page 250 includes multiple type selection areas corresponding to different plug-in types. In some embodiments, considering that intelligent question and answer is a fairly common demand scenario for users, in terms of implementation, the process of knowledge question and answer is composed of two key parts: search vector recall and model generation of answers, and the links of different scenarios are highly reusable. In view of this, it is necessary to use the question and answer plug-in as an application scenario in the digital assistant plug-in creation process, lower the threshold for question and answer configuration, and allow users to quickly create one or more question and answer plug-ins to be put into daily use. Therefore, in some embodiments, the type selection page 250 includes at least a selection area 252 corresponding to the question and answer plug-in template and a creation control 253 for creating a plug-in corresponding to the question and answer plug-in template. In addition to question and answer plug-ins, other plug-in types may include, for example, but are not limited to document plug-ins, custom plug-ins, mail plug-ins, search plug-ins, and the like.

[0047] As an example, in Figure 2CIn the example, the multiple type selection areas included in the type selection page 250 may include a selection area 252 corresponding to a question-and-answer plug-in template, a selection area 254 corresponding to a document plug-in template, and a selection area 256 corresponding to a custom plug-in. It can be understood that the type selection page 250 may also include more areas corresponding to other template types, which is not limited in this space. Each area includes a creation control associated with the corresponding plug-in type. For example, area 252 includes a corresponding creation control 253 for creating a plug-in corresponding to a question-and-answer plug-in template; area 254 includes a creation control 255 for creating a plug-in corresponding to a document plug-in template; area 256 includes a creation control 257 for flexible user customization, and so on.

[0048] In some embodiments, in response to detecting a selection operation on a create control in a window corresponding to any type, the terminal device 110 determines that a plug-in creation request for the plug-in of the type is received, and then based on the plug-in creation request, provides a creation page for creating the plug-in. Figure 2C The terminal device 110 detects the selection operation of the create control 253 in the middle, determines that a plug-in creation request for creating a question-and-answer plug-in is received, and then provides a creation page for creating a question-and-answer plug-in. Figure 2C The terminal device 110 detects the selection operation of the create control 255 in the document class plug-in, determines that a plug-in creation request for creating a document class plug-in is received, and then provides a creation page for creating a document class plug-in. Figure 2C The selection operation of the create control 257 determines that a plug-in creation request indicating the creation of a custom plug-in is received, and then provides a creation page for creating the custom plug-in.

[0049] It should be understood that FIG. 2A to FIG. 2C An example interface for initiating a plug-in creation request, including initiating a template-based plug-in creation request, is shown. In a specific application, any interface interaction method can be designed as needed, or a plug-in creation entry can be provided in any other appropriate page to facilitate users to initiate plug-in creation requests.

[0050] In an embodiment of the present disclosure, one or more types of plug-in creation templates are provided to facilitate users to create plug-ins more efficiently. If a user requests to create a plug-in according to a specific type of plug-in creation template, the creation page for creating the plug-in includes a plug-in creation template corresponding to the type of plug-in to be created. The plug-in creation template includes at least one information input component. In some embodiments, the plug-in creation template here is determined based on the template information corresponding to the type. The template information here at least indicates at least one information input component required to create a plug-in of the type. Thus, the user can determine the corresponding template information based on the type of plug-in he or she wishes to create, and then determine the creation page containing the corresponding plug-in creation template.

[0051] In some embodiments, depending on the type of plug-in to be created, the information input component provided by the corresponding plug-in creation template may include a list of tools that can be selected under that type. Generally, a plug-in can be understood as a collection of functions, and a "tool" in a plug-in can be understood as a unit function or atomic function in a plug-in. With the help of multiple tools, a plug-in can ultimately be used to process a class of tasks that the user expects. For example, a plug-in for processing documents may include: a document creation tool for creating new documents; a search tool for performing searches in documents; a formula generation tool for generating and inserting formulas in documents, and so on.

[0052] When chatting with the digital assistant, the user can choose to use the question-and-answer plug-in to enable the digital assistant to answer the user's questions. In some embodiments, a plug-in creation template corresponding to the question-and-answer plug-in can be provided. For the question-and-answer plug-in, one of the required tools includes a data set.

[0053] The data set here may include, for example, the data required for the user to expect the digital assistant to be able to answer questions. For example, for employees in an enterprise, the data set in the question-and-answer plug-in may include information on various aspects of the enterprise's internal rules and regulations, operating procedures, business precipitation, etc. The data set can be in any format, including offline documents, online documents, knowledge spaces, FAQ documents, documents in various formats (such as PDF, word, PPT, etc.), etc. Traditionally, when employees need to understand these corporate knowledge for work reasons or other transactional reasons (for example, want to know how to connect a certain internal business, how to apply for leave, how to submit a reimbursement form, etc.), employees often need to find information through different channels, or ask relevant colleagues layer by layer. This way of obtaining information takes a lot of time for the questioner to find information and summarize answers, and it also takes time and energy for the answerer to answer a large number of repetitive questions. To solve such problems, in an embodiment of the present disclosure, corresponding knowledge information can be provided to the digital assistant, for example, a data set containing this knowledge information can be provided to the digital assistant. These data sets are used to generate question-and-answer plug-ins for digital assistants. As a result, users can directly ask the digital assistant all kinds of questions they want to ask, and the digital assistant can use question-and-answer plug-ins to give users answers based on the knowledge information included in the data set, which can greatly improve the efficiency of the question-and-answer scenario. In addition, when creating a question-and-answer plug-in, users do not need to pay attention to other technical details. They only need to provide basic information (that is, plug-in creation information) through the plug-in creation template, which can make the process of configuring a question-and-answer plug-in templated and zero-code, allowing users to get started at a very low cost and quickly build a personalized question-and-answer plug-in for use in the digital assistant.

[0054] In some embodiments, for the plug-in creation template corresponding to the question-and-answer plug-in, in addition to the user-configurable data set, the plug-in creation template can also be pre-configured with the question-and-answer processing capability information required to provide the question-and-answer function. Such question-and-answer processing capability information and the user-configured data set together constitute the plug-in creation information for creating the user's question-and-answer plug-in. For example, the question-and-answer processing capability may include the ability to index data sets, the ability to understand user questions, and the ability to search for answers corresponding to questions from data sets. In this way, after the user inputs one or more data sets through the plug-in creation template, these data sets are indexed into the knowledge base of the question-and-answer plug-in. The created question-and-answer plug-in can search for answers corresponding to questions within the scope of the knowledge base.

[0055] It should be understood that, in addition to question-and-answer plug-ins, corresponding plug-in creation templates can also be provided for other types of plug-ins according to the creation needs of specific types of plug-ins. Different information input components can be provided in the plug-in creation template according to the plug-in type, so that users can complete the code writing of the entire plug-in or the tools in the plug-in without going through a complicated programming process, so that various types of plug-ins that meet their own needs can be simply and conveniently defined. In some embodiments, depending on the specific type, the plug-in creation template can also be pre-configured with the plug-in processing capability information required by the corresponding type of plug-in to indicate the plug-in processing capability commonly required by the plug-in of this type. The plug-in processing capability information can be built into the plug-in creation template, without the need for special input and configuration by the user. The plug-in processing capability information pre-configured in the plug-in creation template, combined with the information input by the user, constitutes the plug-in creation information for creating a user-customized plug-in.

[0056] In some embodiments, in order to distinguish multiple plug-ins, no matter which plug-in type the creation page corresponds to, the plug-in creation template may include at least one of an information input component (also referred to as a second information input component) for inputting identification information (such as a text identifier and / or an image identifier) ​​of the plug-in and an information input component (also referred to as a third information input component) for inputting description text of the plug-in. The terminal device 110 may obtain plug-in creation information about the plug-in to be created via at least one information input component in the plug-in creation template.

[0057] Figure 3A and Figure 3B A schematic diagram of an example page of a create page of a plug-in according to some embodiments of the present disclosure is shown. In some embodiments, in response to detecting a create control associated with a question-and-answer plug-in (e.g. Figure 2C The terminal device 110 may present the following Figure 3A The creation page 301 shown contains a plug-in creation template for creating a question-and-answer plug-in. In some embodiments, in response to detecting a creation control (e.g., Figure 2C The terminal device 110 may present the following Figure 3B The creation page 302 shown contains a plug-in creation template for creating a non-question-and-answer type plug-in.

[0058] like Figure 3A as well as Figure 3BAs shown, both the creation page 301 and the creation page 302 include an information input component 310 for inputting an image identifier (e.g., an icon) of the plug-in, an information input component 320 for inputting a text identifier (e.g., a name) of the plug-in, and an information input component 330 for inputting a description text. The information input component 310 and the information input component 320 are both information input components for inputting identification information of the plug-in. The terminal device 110 can obtain the icon of the plug-in via the information input component 310, obtain the name of the plug-in via the information input component 320, and obtain the introduction text of the plug-in via the information input component 330. In some embodiments, for the image identifier of the plug-in, the terminal device 110 only supports the acquisition of images in a specified format through the information input component 310. For example, the terminal device 110 only supports the acquisition of images in PNG format through the information input component 310. In this case, the user can click on a text such as "image format requirements" to view the format requirements for the image identifier. The terminal device 110 can present a description text indicating the format requirements in response to detecting a click operation on the "image format requirements".

[0059] In some embodiments, the creation page 301 and the creation page 302 may also include an effect presentation area 340 for presenting preview information of the plug-in. The preview effect of the plug-in to be created may be presented in the effect presentation area 340. In some embodiments, the creation page 301 and the creation page 302 may also include an information input component for determining permission information of the plug-in. Such permission information may, for example, indicate the range of users who can use the plug-in. Exemplarily, if the terminal device 110 obtains identification information corresponding to user A (e.g., the name of user A) via such an information input component, the terminal device 110 may determine that user A can use the plug-in.

[0060] In some embodiments, Figure 3A As shown, in the case where the plug-in to be created is a question-and-answer plug-in, the creation page 301 may also include an information input component 350 (also referred to as a first information input component) for specifying one or more data sets corresponding to the question-and-answer plug-in. Such an information input component 350 may include, for example, a first part for inputting the type of one or more data sets and a second part for inputting the source of one or more data sets. Figure 3AAs shown, the information input component 350 includes an input entry 352 for inputting a data set type and an input entry 354 for inputting a data set source. The data set type here can be, for example, web, wiki, etc., and the data set source here can be, for example, an access address to such a data set. In some embodiments, such input entry 352 and input entry 354 can be used to receive at least one type of data set and at least one data set source corresponding to at least one type of data set. Alternatively or additionally, in some embodiments, such input entry 352 and input entry 354 can also be used only to receive one type of data set and the data set source corresponding to the data set. In this case, one input entry 352 and one input entry 354 can be regarded as a group, and the information input component 350 can include multiple groups of such input entries to obtain multiple types of data sets and data set sources corresponding to multiple types of data sets. In some embodiments, the information input component 350 also includes a data set addition control 356. For example, the terminal device 110 can obtain a data set determined by the information input in the input entry 352 and the input entry 354 in response to detecting the selection operation of the data set addition control 356. It can be understood that the specific question and answer capabilities of the corresponding question and answer plug-in created are different for different acquired data sets.

[0061] In some embodiments, Figure 3BAs shown, in the case where the plug-in to be created is a non-question-and-answer plug-in, the creation page 302 may also include an information input component 360 for specifying one or more tools corresponding to the non-question-and-answer plug-in. The information input component 360 includes a search box 362. The terminal device 110 can search for multiple tools based on the user input obtained in the search box 362. The information input component 360 may also include a tool creation control 364. The terminal device 110 may present a creation page for creating a new tool in response to detecting a selection operation on the tool creation control 364. The information input component 360 may present multiple pre-acquired tools, which may also be used for pre-creation, or shared with users after being created by other users for use by users. These multiple tools may be presented in the information input component 360 in the form of a tool list. The tool list presents the tool name, tool description and operation corresponding to each tool. The operation here may include, for example, an edit operation and a delete operation. The tool list of the information input component 360 may include, for example, controls corresponding to the operation, such as "edit control" and "delete control". The terminal device 110 may perform a corresponding operation on a tool in response to detecting a selection operation on a certain control. For example, the terminal device 110 may determine to perform an edit operation on tool one in response to detecting a selection operation on an edit control of tool one. In some embodiments, the terminal device 110 may present a corresponding page for performing an operation. For example, an edit page for performing an edit operation on a tool may be performed.

[0062] The terminal device 110 can publish a plug-in based on the plug-in creation information, and the published plug-in can be selected for user interaction with the digital assistant. FIG. 4A to FIG. 4B A schematic diagram of an example publishing page 401 of a plug-in according to some embodiments of the present disclosure is shown. In some embodiments, in response to obtaining the plug-in creation information of the plug-in in the creation page, the terminal device 110 can present a publishing page 401 for publishing the plug-in. An input entry 410 for inputting version information is presented in the publishing page 401. In some embodiments, the version number of the latest version of the plug-in can be directly presented in the input entry 410. The version number here can be determined by the terminal device 110 itself, or it can be manually entered by the user. In some embodiments, the terminal device 110 can also present a control "historical version" associated with the input entry on the publishing page. In response to detecting a click operation on the "historical version", the terminal device 110 can present the historical version information associated with the plug-in to be published.

[0063] In some embodiments, the publishing page 401 further includes a permission editing control 420. The terminal device 110 can determine the user range that can use the plug-in based on the user input obtained at the permission editing control 420, that is, determine at least one user that can use the plug-in. The at least one user here includes at least the current user who created the plug-in.

[0064] In some embodiments, when the created plug-in is for private use, that is, only used by the user who created the plug-in, only the user information associated with the current user is presented in the publishing page 401. Figure 4A As shown, if the current user is user A, the terminal device 110 only presents the user information of user A (e.g., user A's avatar, name, etc.) associated with the permission editing control 420. In some embodiments, when the created plug-in is used for public use, that is, used by the user who created the plug-in and at least one other user, the publishing page 401 may also present the user information associated with all users who can use the plug-in. For example, Figure 4B As shown, if the current user is user A, and the plug-in created by user A is open to all users in the department where user A is located, the terminal device 110 can present the user information of user A (such as user A's avatar, name, etc.) and the department information of the department where user A is located (such as department name) in association with the permission editing control 420. It can be understood that in addition to presenting the department information, in some embodiments, the terminal device 110 can also present the user information of user A and the user information of all users in the department where user A is located in association with the permission editing control 420. In this case, the digital assistant can make different replies to different questioners based on the authority of the questioner. For example, in the case of two question-and-answer plug-ins including plug-in A and plug-in B, if user A only has the authority of plug-in A and user B only has the authority of plug-in B, the digital assistant will use plug-in A to reply to user A and plug-in B to reply to user B. Even if user A and user B ask the same question to the digital assistant, the digital assistant can also reply to the two differently because the plug-ins with which they have authority are different.

[0065] In some embodiments, the plug-in created by the user can be made public to other users. In some embodiments, the plug-in to be published by the user needs to be approved before it can be published. In this case, the terminal device 110 can publish the plug-in in response to the approval of the plug-in creation information. In some embodiments, in order to allow the user to intuitively obtain the current review status of the plug-in (for example, whether it has passed the review), such as Figure 4A as well as Figure 4B As shown, the publishing page 401 may also include an audit information presentation area 430. In the case where the created plug-in is for private use, the audit information presentation area 430 may present the following information: Figure 4A The text prompt shown here is used to remind the user that such a plug-in does not need to be reviewed by others and can be directly published. In the case where the created plug-in is used for public use, the review information presentation area 430 can present the following Figure 4B The audit information shown. The audit information here can indicate the auditor who audited the plug-in (the auditor here includes other users or machines, models, digital assistants, etc.), as well as the current audit node. The terminal device 110 can present prompt information to the user in response to the end of the audit. For example, the prompt information can be presented to the user through voice, vibration, text, etc. The terminal device 110 then responds to detecting a publishing operation indicating the release of the plug-in (such as a touch operation such as clicking on the release control, or a non-touch operation such as a voice command or a gesture command), determines that a publishing instruction for the plug-in has been received, and then publishes the plug-in.

[0066] In summary, according to various embodiments of the present disclosure, a creation page for creating a target plug-in is provided in the interaction window between the user and the digital assistant. A plug-in creation template is presented in the creation page. The plug-in creation information of the plug-in is obtained through at least one information input component in the plug-in creation template, and the plug-in is published based on the plug-in creation information. With the help of the template, users can complete the creation of the plug-in conveniently and quickly, which helps users to efficiently complete various operations with the help of the plug-in during the interaction with the digital assistant.

[0067] It should be understood that some embodiments of the present disclosure are described above in conjunction with the specific examples in the drawings, but these specific examples do not limit the scope of the embodiments of the present disclosure. The described embodiments can also be implemented in various other variations.

[0068] Figure 5 FIG. 5 is a flowchart of a process 500 for creating a plug-in according to some embodiments of the present disclosure. The process 500 may be implemented at the terminal device 110. For ease of discussion, reference will be made to FIG. Figure 1 The process 500 is described in the environment 100.

[0069] In block 510 , the terminal device 110 provides a creation page for creating a target plug-in, wherein the creation page presents a plug-in creation template corresponding to the type of the target plug-in to be created, and the plug-in creation template includes at least one information input component.

[0070] In block 520 , the terminal device 110 obtains plug-in creation information about the target plug-in via at least one information input component in the plug-in creation template.

[0071] In box 530, the terminal device 110 publishes a target plug-in based on the plug-in creation information, and the published target plug-in can be selected for user interaction with the digital assistant.

[0072] In some embodiments, providing a creation page for creating a target plug-in includes: receiving a plug-in creation request indicating a type of plug-in to be created; and providing a creation page for creating the target plug-in based on the plug-in creation request.

[0073] In some embodiments, the plug-in creation template is determined based on template information corresponding to the type, the template information at least indicating at least one information input component required for creating the plug-in of the type.

[0074] In some embodiments, the type corresponding to the target plug-in is a question-and-answer plug-in, and the plug-in creation template includes at least: a first information input component for specifying one or more data sets corresponding to the question-and-answer plug-in.

[0075] In some embodiments, the first information input component includes at least: a first part for inputting the type of one or more data sets; and a second part for inputting the source of one or more data sets.

[0076] In some embodiments, the plug-in creation template also includes at least one of the following: a second information input component for inputting identification information of the target plug-in, the identification information including a text identifier and / or an image identifier; and a third information input component for inputting description text of the target plug-in.

[0077] In some embodiments, the plug-in creation information further includes permission information, and the permission information at least indicates a range of users who can use the target plug-in.

[0078] In some embodiments, publishing the target plug-in based on the plug-in creation information includes: in response to a review of the plug-in creation information being passed, publishing the target plug-in.

[0079] Figure 6 A schematic structural block diagram of an apparatus 600 for creating a plug-in according to some embodiments of the present disclosure is shown. The apparatus 600 may be implemented as or included in a terminal device 110. Each module / component in the apparatus 600 may be implemented by hardware, software, firmware, or any combination thereof.

[0080] The device 600 includes a page providing module 610, which is configured to provide a creation page for creating a target plug-in, wherein the creation page presents a plug-in creation template corresponding to the type of the target plug-in to be created, and the plug-in creation template includes at least one information input component. The device 600 also includes an information acquisition module 620, which is configured to obtain plug-in creation information about the target plug-in via at least one information input component in the plug-in creation template. The device 600 also includes a plug-in publishing module 630, which is configured to publish the target plug-in based on the plug-in creation information, and the published target plug-in can be selected for user interaction with the digital assistant.

[0081] In some embodiments, the page providing module 610 includes: a creation request receiving module, configured to receive a plug-in creation request, the plug-in creation request indicating the type of plug-in to be created; and a creation page providing module, configured to provide a creation page for creating a target plug-in based on the plug-in creation request.

[0082] In some embodiments, the plug-in creation template is determined based on template information corresponding to the type, the template information at least indicating at least one information input component required for creating the plug-in of the type.

[0083] In some embodiments, the type corresponding to the target plug-in is a question-and-answer plug-in, and the plug-in creation template includes at least: a first information input component for specifying one or more data sets corresponding to the question-and-answer plug-in.

[0084] In some embodiments, the first information input component includes at least: a first part for inputting the type of one or more data sets; and a second part for inputting the source of one or more data sets.

[0085] In some embodiments, the plug-in creation template also includes at least one of the following: a second information input component for inputting identification information of the target plug-in, the identification information including a text identifier and / or an image identifier; and a third information input component for inputting description text of the target plug-in.

[0086] In some embodiments, the plug-in creation information further includes permission information, and the permission information at least indicates a range of users who can use the target plug-in.

[0087] In some embodiments, the plug-in publishing module 630 includes: a publishing module configured to publish a target plug-in in response to the plug-in creation information being reviewed and approved.

[0088] The units and / or modules included in the device 600 can be implemented in various ways, including software, hardware, firmware, or any combination thereof. In some embodiments, one or more units and / or modules can be implemented using software and / or firmware, such as machine executable instructions stored on a storage medium. In addition to or as an alternative to machine executable instructions, some or all of the units and / or modules in the device 600 can be implemented at least in part by one or more hardware logic components. As an example and not limitation, exemplary types of hardware logic components that can be used include field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0089] It should be understood that one or more steps in the above method can be performed by a suitable electronic device or a combination of electronic devices. Such an electronic device or a combination of electronic devices may include, for example, Figure 1 The server 130, the terminal device 110 and / or the combination of the server 130 and the terminal device 110.

[0090] Figure 7 1 shows a block diagram of an electronic device 700 in which one or more embodiments of the present disclosure may be implemented. It should be understood that Figure 7 The electronic device 700 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Figure 7 The electronic device 700 shown can be used to implement Figure 1 terminal device 110.

[0091] like Figure 7 As shown, the electronic device 700 is in the form of a general electronic device. The components of the electronic device 700 may include, but are not limited to, one or more processors or processing units 710, a memory 720, a storage device 730, one or more communication units 740, one or more input devices 750, and one or more output devices 760. The processing unit 710 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 720. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 700.

[0092] The electronic device 700 typically includes a plurality of computer storage media. Such media can be any available media accessible to the electronic device 700, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 720 can be a volatile memory (e.g., register, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory) or some combination thereof. The storage device 730 can be a removable or non-removable medium, and can include a machine-readable medium, such as a flash drive, a disk, or any other medium, which can be used to store information and / or data and can be accessed within the electronic device 700.

[0093] The electronic device 700 may further include additional removable / non-removable, volatile / non-volatile storage media. Figure 7 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. The memory 720 may include a computer program product 725 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.

[0094] The communication unit 740 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 700 can be implemented with a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 700 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0095] The input device 750 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 760 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 700 may also communicate with one or more external devices (not shown) through the communication unit 740 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 700, or communicate with any device that allows the electronic device 700 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0096] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0097] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0098] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0099] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0100] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0101] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.

Claims

1. A method for creating a plug-in, comprising: Providing a creation page for creating a target plug-in, wherein the creation page presents a plug-in creation template corresponding to the type of the target plug-in to be created, and the plug-in creation template includes at least one information input component; Obtaining plug-in creation information about the target plug-in at least via the at least one information input component in the plug-in creation template; as well as The target plug-in is published based on the plug-in creation information, and the published target plug-in can be selected for user interaction with the digital assistant.

2. The method according to claim 1, wherein providing a creation page for creating a target plug-in comprises: receiving a plug-in creation request, the plug-in creation request indicating a type of plug-in to be created; as well as Based on the plug-in creation request, the creation page for creating the target plug-in is provided. 3 . The method according to claim 1 , wherein the plug-in creation template is determined based on template information corresponding to the type, the template information at least indicating at least one information input component required for creating a plug-in of the type.

4. The method according to claim 1, wherein the type corresponding to the target plug-in is a question-and-answer plug-in, and the plug-in creation template at least includes: The first information input component is used to specify one or more data sets corresponding to the question-and-answer plug-in.

5. The method according to claim 4, wherein the first information input component comprises at least: The first part is used to input the type of the one or more data sets; as well as The second part is used to input the source of the one or more data sets.

6. The method according to claim 1, wherein the plug-in creation template further comprises at least one of the following: A second information input component, used to input identification information of the target plug-in, wherein the identification information includes a text identification and / or an image identification; The third information input component is used to input the description text of the target plug-in. 7 . The method according to claim 1 , wherein the plug-in creation information further includes permission information, the permission information at least indicating a range of users who can use the target plug-in.

8. The method according to claim 1, wherein the plug-in creation information further comprises: The plug-in processing capability information pre-configured for the plug-in creation template corresponds to the type of the target plug-in.

9. The method according to claim 1, wherein publishing the target plug-in based on the plug-in creation information comprises: In response to the plug-in creation information being reviewed and approved, the target plug-in is released.

10. A device for creating a plug-in, comprising: A page providing module is configured to provide a creation page for creating a target plug-in, wherein the creation page presents a plug-in creation template corresponding to the type of the target plug-in to be created, and the plug-in creation template includes at least one information input component; an information acquisition module, configured to acquire plug-in creation information about the target plug-in at least via the at least one information input component in the plug-in creation template; as well as A plug-in publishing module is configured to publish the target plug-in based on the plug-in creation information, and the published target plug-in can be selected for user interaction with the digital assistant.

11. An electronic device, comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to perform the method according to any one of claims 1 to 9 when executed by the at least one processing unit.

12. A computer-readable storage medium having a computer program stored thereon, wherein the computer program can be executed by a processor to implement the method according to any one of claims 1 to 9.

Citation Information

Patent Citations

  • Prompt method and system for personal assistant information in instant messaging (IM)

    CN102347911A

  • Embedded programs and interfaces for chat conversations

    CN110945840A

  • Data processing method, device and equipment and readable storage medium

    CN111680147A

  • Customer service robot question and answer data creation method and device and computer equipment

    CN111753075A

  • Skill packet data processing method and device, computer equipment and storage medium

    CN112882769A

Cited By

  • Support structure for vehicle

    CN122603085A