Dynamic tool integration method and device for large language model using web assembly

Abstract

A dynamic tool integration method for a large language model using a web assembly, according to one feature of the present disclosure, comprises: a step for receiving an input of a user question; a step for selecting an operating tool on the basis of the user question; a step for downloading an operating tool which can operate in a web assembly environment; a step for executing the operating tool in a web assembly runtime environment of a pocket framework; and a step for generating an interactive answer to the user question on the basis of an execution result of the operating tool and providing the answer to the user.

Description

Method and device for dynamic tool integration of large-scale language models using WebAssembly

[0001] The present disclosure relates to a method for integrating and executing external tools in a Large Language Model (LLM), and in particular to a technique for more efficiently integrating and securely executing dynamic tools by utilizing a Web Assembly-based execution environment.

[0002] Large-scale language models are widely used in AI agent systems capable of automating various tasks based on natural language processing and command generation capabilities.

[0003] Previously, research focused on methods that performed tasks using only large-scale language models. However, recently, in order to implement more accurate and diverse tasks, attempts are being made to handle more complex and varied operations by enabling large-scale language models to interact with external databases or tools.

[0004] On the other hand, there are various limitations to integrating external tools using such existing large-scale language models. Specifically, to integrate an external tool with a specific AI framework, the tool must be dependent on that framework. For this reason, there are limitations, such as the necessity of development specifically for tool integration.

[0005] Therefore, there is a growing need to integrate external tools more seamlessly, independently of the environment of large-scale language models.

[0006] One embodiment of the present disclosure provides a dynamic tool integration technology for a large-scale language model using WebAssembly, which enables more efficient and secure integration of external tools in a large-scale language model system.

[0007] One embodiment of the present disclosure aims to provide a dynamic tool integration technology for large-scale language models utilizing WebAssembly, which can simplify and standardize the tool integration process regardless of the framework by using WebAssembly.

[0008] One embodiment of the present disclosure aims to provide a dynamic tool integration technology for a large-scale language model utilizing WebAssembly, which can provide a consistent execution experience by integrating tools implemented in various programming languages ​​into a WebAssembly environment.

[0009] The problems that the present disclosure aims to solve are not limited to those described above, and problems not mentioned will be clearly understood by those skilled in the art from the present specification and the accompanying drawings.

[0010] One feature of the present disclosure proposes a method for dynamic tool integration of a large-scale language model using WebAssembly. The method for dynamic tool integration of a large-scale language model using WebAssembly comprises: receiving a user question; selecting an operating tool based on the user question; downloading an operating tool executable in a WebAssembly environment; executing the operating tool in a WebAssembly runtime environment of a Pocket Framework; and generating an interactive response to the user question and providing it to the user based on the execution result of the operating tool.

[0011] The step of selecting a driving tool based on the above user question may include: generating a query prompt for selecting a tool related to the user question; providing the query prompt to a large-scale language model; and selecting a driving tool based on the answer of the large-scale language model.

[0012] The step of generating a query prompt for selecting a tool related to the above user question may include: generating a command requesting a tool search based on the above user question; and generating the query prompt including the above user question and the above command.

[0013] The step of downloading a driving tool that can be run in the above web assembly environment may include: a step of having web assembly tool information that can be run in the web assembly; a step of identifying the driving tool in the web assembly tool information; and a step of downloading the driving tool using the web assembly tool information.

[0014] The above web assembly tool information may include a list of web assembly tools that can be run in web assembly; and download links for the web assembly tools.

[0015] The step of executing the driving tool in the web assembly runtime environment of the pocket framework may include: executing a browser in the pocket framework; and executing the driving tool through the browser.

[0016] The step of generating and providing an interactive answer to the user's question based on the execution result of the above-described driving tool may include: generating an answer prompt including the execution result of the above-described driving tool and the user's question; and providing the user's question and the answer prompt to a large-scale language model.

[0017] The step of generating and providing an interactive answer to the user's question based on the execution result of the above-described driving tool may include: receiving an interactive answer to the user's question generated from the above-described large-scale language model; and providing an answer to the user's question based on the interactive answer.

[0018] Another feature of the present disclosure proposes a dynamic tool integration device for a large-scale language model utilizing WebAssembly. The dynamic tool integration device for a large-scale language model utilizing WebAssembly includes at least one processor; and a memory for storing instructions. When the instructions are executed individually or collectively by the at least one processor, the processor is configured to perform the following operations: receiving a user question; selecting an operating tool based on the user question; downloading an operating tool executable in a WebAssembly environment; executing the operating tool in a WebAssembly runtime environment of a pocket framework; and generating an interactive answer to the user question based on the execution result of the operating tool and providing it to the user.

[0019] The means for solving the problem of the present disclosure are not limited to the means for solving the problem described above, and means for solving the problem not mentioned will be clearly understood by those skilled in the art to which the present disclosure belongs from the present specification and the attached drawings.

[0020] According to the embodiments, in particular, by utilizing a Web Assembly-based isolated execution environment to integrally manage tools developed in various languages ​​and automating the process of adding and executing dynamic tools, it provides the effect of increasing work efficiency and enhancing security.

[0021] According to the embodiments, the effect of providing a tool integration process regardless of the framework by using WebAssembly is provided without the need for separate development depending on the type of framework, etc.

[0022] According to the embodiments, the effect of enhancing security by running an external tool in a secure execution environment of a web assembly is provided.

[0023] The effects according to the present disclosure are not limited to the effects described above, and unmentioned effects will be clearly understood by those skilled in the art from the present specification and the accompanying drawings.

[0024] The above-mentioned problems, other problems, features, and advantages of the present disclosure will become more apparent to those skilled in the art by describing exemplary embodiments of the present disclosure in detail with reference to the accompanying drawings.

[0025] FIG. 1 is a drawing illustrating a dynamic tool linkage device for a large-scale language model utilizing Web Assembly according to one embodiment of the present disclosure.

[0026] FIG. 2 is a diagram illustrating the operation of a dynamic tool linkage device for a large-scale language model utilizing Web Assembly according to one embodiment of the present disclosure.

[0027] FIG. 3 is a flowchart illustrating a method for dynamic tool integration of a large-scale language model using Web Assembly according to one embodiment of the present disclosure.

[0028] FIG. 4 is a flowchart illustrating a method for selecting a driving tool based on a user's question according to one embodiment of the present disclosure.

[0029] FIG. 5 is a flowchart illustrating a method for downloading a driving tool in a web assembly environment according to one embodiment of the present disclosure.

[0030] FIG. 6 is a flowchart illustrating a method for providing an interactive response based on the execution result of a driving tool according to one embodiment of the present disclosure.

[0031] FIG. 7 is a flowchart illustrating a scenario of a dynamic tool linkage method for a large-scale language model using Web Assembly according to an embodiment of the present disclosure.

[0032] FIG. 8 is a flowchart illustrating a method for generating a Web Assembly-based driving tool based on an alternative tool according to one embodiment of the present disclosure.

[0033] Specific structural or functional descriptions of embodiments according to the concept of the present disclosure disclosed herein are provided merely for the purpose of explaining embodiments according to the concept of the present disclosure, and embodiments according to the concept of the present disclosure may be implemented in various forms and are not limited to the embodiments described herein.

[0034] Embodiments according to the concept of the present disclosure may be subject to various modifications and may take various forms; therefore, embodiments are illustrated in the drawings and described in detail in this specification. However, this is not intended to limit the embodiments according to the concept of the present disclosure to specific disclosed forms, and includes modifications, equivalents, or substitutions that fall within the spirit and scope of the present disclosure.

[0035] Terms such as "first" or "second" may be used to describe various components, but said components shall not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of rights according to the concept of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component.

[0036] When it is stated that one component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. Conversely, when it is stated that one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between. Expressions describing the relationships between components, such as "between," "exactly between," or "directly adjacent to," should be interpreted in the same way.

[0037] The terms used herein are used merely to describe specific embodiments and are not intended to limit the disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this specification, terms such as “comprising” or “having” are intended to specify the existence of the described features, numbers, steps, actions, components, parts, or combinations thereof, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0038] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this specification.

[0039] In this specification, the term "processor" may refer to hardware capable of performing functions and operations according to each name described in this specification, computer program code capable of performing specific functions and operations, or an electronic recording medium loaded with computer program code capable of performing specific functions and operations.

[0040] In other words, the term "processor" may mean a functional and / or structural combination of hardware for carrying out the technical concept of the present disclosure and / or software for driving said hardware.

[0041] Hereinafter, embodiments will be described in detail with reference to the attached drawings. However, the scope of the patent application is not limited or restricted by these embodiments. Identical reference numerals in each drawing denote identical components.

[0042] FIG. 1 is a drawing illustrating a dynamic tool linkage device for a large-scale language model utilizing Web Assembly according to one embodiment of the present disclosure.

[0043] Referring to FIG. 1, a dynamic tool linkage device (100, hereinafter abbreviated as ‘dynamic tool linkage device’) of a large-scale language model utilizing Web Assembly may include a processor (110) and memory (120).

[0044] Although not illustrated, the dynamic tool linkage device (100) may further include a communication module for being communicated to a large-scale language model (200) and a user terminal (300) via wireless or wired communication. The communication module may include communication circuitry.

[0045] The dynamic tool integration device (100) may be implemented as a service server, but is not limited thereto. For example, the dynamic tool integration device (100) may be provided as an independent server or an independent physical device connected to a separate service server that provides artificial intelligence services.

[0046] Existing LLM systems often depend on specific languages ​​or platforms when integrating tools, and suffer from security and dependency issues when executing external tools. In one embodiment of the present disclosure, a dynamic tool integration device (100) capable of integrating external tools more efficiently and safely is proposed to overcome these limitations.

[0047] The dynamic tool linkage device (100) can execute the tool based on Web Assembly, thereby minimizing language restrictions and executing code in an isolated environment.

[0048] The dynamic tool integration device (100) provides a Web Assembly-based tool runtime development environment, and thus can simplify the tool integration process regardless of the framework by utilizing Web Assembly.

[0049] The dynamic tool integration device (100) can overcome language constraints by integrating tools implemented in various programming languages ​​into a web assembly to provide a consistent execution experience.

[0050] The dynamic tool linkage device (100) can increase security by running even untrusted tools in a secure environment of the web assembly and can ensure an isolated environment.

[0051] The dynamic tool linkage device (100) can expand the possibility of implementing AGI (Artificial General Intelligence) by automatically searching for, installing, or executing a suitable tool dynamically when necessary.

[0052] The dynamic tool linkage device (100) includes a processor (110) and a memory (120).

[0053] The processor (110) may include, as an example, at least one of a microprocessor, a central processing unit, a processor core, a multi-core processor, a multiprocessor, an ASIC (Application-Specific Integrated Circuit), or an FPGA (Field Programmable Gate Array), but is not limited thereto.

[0054] Memory (120) can store instructions (or programs) executable by the processor (110). Memory (120) may include volatile memory or non-volatile memory.

[0055] Volatile memory can be implemented as DRAM (dynamic random access memory), SRAM (static random access memory), T-RAM (thyristor RAM), Z-RAM (zero capacitor RAM), or TTRAM (Twin Transistor RAM).

[0056] Non-volatile memory can be implemented as EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, MRAM (Magnetic RAM), Spin-Transfer Torque (STT)-MRAM, Conductive Bridging RAM (CBRAM), FeRAM (Ferroelectric RAM), PRAM (Phase change RAM), Resistive RAM (RRAM), Nanotube RRAM, Polymer RAM (PoRAM), Nano Floating Gate Memory (NFGM), holographic memory, Molecular Electronic Memory Device, or Insulator Resistance Change Memory.

[0057] FIG. 2 is a diagram illustrating the operation of a dynamic tool linkage device for a large-scale language model utilizing Web Assembly according to one embodiment of the present disclosure.

[0058] The dynamic tool integration device (100) includes a pocket framework (130) that runs on the dynamic tool integration device (100). The pocket framework (130) may also be referred to as a pocket SDK.

[0059] The pocket framework (130) may be a software development kit (SDK) that provides a WebAssembly (Wasm)-based execution environment and can dynamically link and manage various tools in a WebAssembly-based execution environment.

[0060] The WebAssembly environment of the Pocket Framework (130) provides an isolated execution environment. That is, each tool is executed independently during each WebAssembly runtime, thereby improving security and performance.

[0061] The pocket framework (130) can dynamically acquire a driving tool from an external source and inject it into a WebAssembly environment to execute it. That is, the pocket framework (130) includes a dynamic tool injection function, and through this, it can provide a function to automatically search for a suitable tool from an open source repository—e.g., GitHub—and execute it whenever a tool is needed.

[0062] The pocket framework (130) can store and manage tool manifests containing metadata files for each tool. The pocket framework (130) can automatically handle tool management and tool execution settings based on the tool manifests.

[0063] For example, the tool directory may contain a manifest file that specifies input data in a JSON schema. The manifest file may define authentication requirements for external open source repositories and WebAssembly file paths.

[0064] Hereinafter, an external tool used to process a user's question is referred to as a driving tool. For example, a large-scale language model (200) can determine a driving tool corresponding to a user's question.

[0065] The pocket framework (130) can obtain a driving tool from an external open source repository, automatically install the driving tool, and run the driving tool in a WebAssembly environment. For example, the pocket framework (130) can download the WebAssembly bytecode of the tool, and the installed tool can be registered so that it can be used in the LLM Workflow Framework.

[0066] The pocket framework (130) can perform a tool execution process for executing the driving tool. For example, the pocket framework (130) can verify the authentication information required for the execution of the tool and provide a suitable authentication / authorization method (Token, OAuth2, etc.) to the user. After authentication, the pocket framework (130) can execute the driving tool in a browser environment—e.g., a headless mode browser—and execute an HTML file containing WebAssembly code. Input data can be passed to the driving tool after the LLM validates it according to the JSON schema defined in the manifest, and the execution result can be provided to the LLM Workflow as standard output.

[0067] The pocket framework (130) may include a dynamic tool injection system. The dynamic tool injection system performs the process of automatically searching for, installing, and executing a driving tool. For dynamic tool injection, the pocket framework (130) can automatically search for and install a tool. For example, if a driving tool is not currently available, the pocket framework (130) can search for a suitable tool from an open source platform, install the found tool, and then dynamically integrate it into the LLM Workflow. The installed driving tool runs in the WebAssembly runtime environment and can be integrated into the existing workflow.

[0068] Hereinafter, with reference to FIGS. 3 to 8, various embodiments of a dynamic tool linkage method performed in a dynamic tool linkage device (100) will be described.

[0069] FIG. 3 is a flowchart illustrating a method for dynamic tool integration of a large-scale language model using Web Assembly according to one embodiment of the present disclosure.

[0070] When the dynamic tool linkage device (100) receives a user question (S310), it can select a driving tool based on the user question (S320).

[0071] In one embodiment, the dynamic tool linkage device (100) can select the necessary driving tool according to a user question using a large-scale language model (200). This embodiment will be described in more detail below with reference to FIG. 4.

[0072] When a driving tool is selected, the dynamic tool linkage device (100) can download a driving tool that can be driven in a web assembly environment (S330).

[0073] The dynamic tool linkage device (100) can execute a driving tool in the web assembly runtime environment of the pocket framework (S340).

[0074] For example, a dynamic tool linkage device (100) can run a browser in a pocket framework and run a tool in a web assembly runtime environment through the run browser.

[0075] The dynamic tool linkage device (100) can generate an interactive answer to a user's question and provide it to the user based on the execution result of the driving tool through the above process (S350).

[0076] In one embodiment, the dynamic tool linkage device (100) can generate an interactive answer to a user question based on the result of a driving tool using a large-scale language model (200). This embodiment will be described in more detail below with reference to FIG. 6.

[0077] FIG. 4 is a flowchart illustrating a method for selecting a driving tool based on a user's question according to one embodiment of the present disclosure.

[0078] Referring to FIG. 4, the dynamic tool linkage device (100) can generate a query prompt for selecting a driving tool related to a user question (S410).

[0079] The query prompt is a prompt provided as a query to a large-scale language model (200), and is a prompt for selecting necessary tools from user questions using the large-scale language model (200).

[0080] In one embodiment, to generate a query prompt, the dynamic tool integration device (100) may generate a command requesting a tool search based on a user question. Subsequently, the dynamic tool integration device (100) may generate a query prompt including the user question and the command. For example, the dynamic tool integration device (100) may generate a command such as "Check the user question and select an operating tool to perform the user question." The dynamic tool integration device (100) may generate a query prompt including the user question and the above command.

[0081] The dynamic tool linkage device (100) provides a query prompt to the large-scale language model (200) (S420), and can select a driving tool based on the answer from the large-scale language model (200) (S430).

[0082] FIG. 5 is a flowchart illustrating a method for downloading a driving tool in a web assembly environment according to one embodiment of the present disclosure.

[0083] Referring to FIG. 5, the dynamic tool linkage device (100) may have web assembly tool information that can be driven in a web assembly (S510). The dynamic tool linkage device (100) may identify the driving tool in the web assembly tool information (S520) and download the driving tool using the web assembly tool information (S530).

[0084] Here, the web assembly tool information may include a list of web assembly tools that can be run in web assembly and download links for the web assembly tools.

[0085] That is, in the example illustrated in FIG. 5, an example is illustrated in which Web Assembly tool information, which is information about a tool running in a Web Assembly environment, is built in advance or obtained from an external source, and then a tool running is obtained using this Web Assembly tool information.

[0086] Meanwhile, there may be no driving tool in the Web Assembly tool information, and in such cases, an embodiment that generates a driving tool based on an alternative tool, such as the embodiment shown in FIG. 8, may be used.

[0087] FIG. 6 is a flowchart illustrating a method for providing an interactive response based on the execution result of a driving tool according to one embodiment of the present disclosure.

[0088] Referring to FIG. 6, the dynamic tool linkage device (100) can generate an answer prompt including the execution result of the driving tool and a user question (S610).

[0089] For example, when a tool execution plan comes from a large-scale language model (200), the dynamic tool integration device (100) can perform the operation of finding a tool corresponding to the tool execution plan and actually executing it.

[0090] The dynamic tool linkage device (100) provides an answer prompt to a large-scale language model (S620) and can receive an interactive answer generated from the large-scale language model (S630).

[0091] The dynamic tool linkage device (100) can provide an interactive response to the user terminal (300) (S640).

[0092] FIG. 7 is a flowchart illustrating a scenario of a dynamic tool integration method for a large-scale language model utilizing WebAssembly according to an embodiment of the present disclosure. An example of a dynamic tool integration method is described with reference to FIG. 7.

[0093] The user terminal (300) can provide a user question to the dynamic tool linkage device (100) (S701). As an example of a user question, the explanation assumes the case where "What is the information on the fastest flight tickets to the US?" is provided.

[0094] The dynamic tool linkage device (100) can generate a query prompt to determine what tool is needed based on a user question (S702). For example, the dynamic tool linkage device (100) can generate a query prompt including a command "Select the necessary driving tool based on the user question" and the user question, and query the large-scale language model (200) with the query prompt.

[0095] The large-scale language model (200) can provide a response to a query prompt to the dynamic tool linkage device (100) (S703). As an example of a response, the answer "I need an flight lookup tool" may be provided.

[0096] The dynamic tool linkage device (100) can perform a process to select an flight search tool and run the flight search tool as a driving tool. Specifically, the dynamic tool linkage device (100) can run a browser to build a Web Assembly runtime environment (S704), and after obtaining the flight search tool, run the flight search tool as a driving tool in the browser's Web Assembly runtime environment (S705).

[0097] The dynamic tool integration device (100) can generate an answer prompt to generate an interactive answer based on the results of the driving tool using a large-scale language model (200) (S706). For example, the dynamic tool integration device (100) can generate an answer prompt saying "Generate an interactive answer to the user's question based on the flight search results" and query the flight search results, which are the execution results of the dynamic tool, and the user's question into the large-scale language model (200).

[0098] The large-scale language model (200) can provide a response to the answer prompt to the dynamic tool linkage device (100) (S707). As an example of a response, the answer "The fastest flight ticket to the United States is OZ737 on February 7 at 13:00" may be provided.

[0099] The dynamic tool integration device (100) can provide a conversational answer to a user question to a user terminal (300) based on a conversational answer provided in a large-scale language model (200) (S708). For example, the dynamic tool integration device (100) can provide the user terminal (300) with the answer, "The fastest flight ticket to the United States is OZ737 on February 7 at 13:00."

[0100] FIG. 8 is a flowchart illustrating a method for generating a Web Assembly-based driving tool based on an alternative tool according to one embodiment of the present disclosure.

[0101] An embodiment illustrated in FIG. 8 relates to a method for generating a web assembly-based driving tool when a web assembly-based driving tool is not found.

[0102] The dynamic tool linkage device (100) can search for whether there is a tool suitable for responding to a user's query by utilizing an open source repository such as Github (S810).

[0103] If the tool is built as a web assembly, the dynamic tool linkage device (100) can execute the tool using the file (S820).

[0104] Meanwhile, if the tool is not built into a web assembly, the dynamic tool linkage device (100) attempts to build it into a web assembly (S830), and if the build is successfully performed, the tool can be executed using the built web assembly file (S840).

[0105] In another embodiment, the dynamic tool linkage device (100) can search for whether a driving tool exists for a tool running in a web assembly environment. For example, it can search for whether a tool corresponding to the driving tool exists using the web assembly tool information described above.

[0106] The dynamic tool linkage device (100) can search for whether there is a tool corresponding to the driving tool in the second driving environment if there is no tool in the web assembly environment.

[0107] For example, if a WebAssembly-based tool is not found, the dynamic tool linkage device (100) can search for a replacement tool by targeting a tool that is executable in a different execution environment other than WebAssembly, such as a native library or another execution environment, as a search range to find a replacement tool.

[0108] The dynamic tool linkage device (100) can download the tool as a replacement tool when the tool is found in the second operating environment. For example, in FIG. 7, if an flight lookup tool that can be operated in the C environment is found, the dynamic tool linkage device (100) can secure the flight lookup tool as a replacement tool.

[0109] The dynamic tool linkage device (100) can generate a driving tool by dynamically compiling an alternative tool into a web assembly.

[0110] For example, the dynamic tool integration device (100) can dynamically compile an alternative tool, an flight lookup tool that can be run in a C environment, into WebAssembly. If necessary, the dynamic tool integration device (100) can automatically convert the code at runtime to generate a runnable tool that can be executed in a WebAssembly environment. To this end, the dynamic tool integration device (100) can perform automated code conversion processing. For automatic code conversion, the dynamic tool integration device (100) can search for libraries in open source projects or external repositories to convert the alternative tool in a C environment into a dynamic tool in a WebAssembly environment.

[0111] This embodiment ensures system flexibility by enabling the creation of a driving tool based on an alternative tool in various execution environments even when there is no driving tool in the web assembly environment. Additionally, since the dynamic tool linkage device (100) automatically converts the code and creates an execution environment, the user can conveniently perform tasks without needing to configure them directly.

[0112] The device described above may be implemented as a hardware component, a software component, and / or a combination of a hardware component and a software component. For example, the device and components described in the embodiments may be implemented using one or more general-purpose or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing unit may execute an operating system (OS) and one or more software applications executed on said operating system. Additionally, the processing unit may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing unit may be described as being used as a single unit, but those skilled in the art will understand that the processing unit may include multiple processing elements and / or multiple types of processing elements. For example, the processing unit may include multiple processors or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are also possible.

[0113] Software may include computer programs, code, instructions, or a combination of one or more of these, and may configure a processing unit to operate as desired or command the processing unit independently or collectively. Software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium, computer device, or transmitted signal wave so as to be interpreted by the processing unit or to provide instructions or data to the processing unit. Software may be distributed over networked computer systems and may be stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.

[0114] The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., either alone or in combination. The program instructions recorded on the medium may be those specifically designed and configured for the embodiment, or may be those known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware device may be configured to operate as one or more software modules to perform the operation of the embodiment, and vice versa.

[0115] Although the embodiments have been described above with reference to limited examples and drawings, those skilled in the art can make various modifications and variations from the description above. For example, suitable results can be achieved even if the described techniques are performed in a different order than described, and / or the components of the described system, structure, device, circuit, etc. are combined or assembled in a form different from described, or replaced or substituted by other components or equivalents.

[0116] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims set forth below.

[0117] The method and device for dynamic tool integration of a large-scale language model utilizing WebAssembly as described above can be applied to the field of artificial intelligence services utilizing large-scale language models.

Claims

1. Step of receiving user questions; A step of selecting a driving tool based on the above user question; A step of downloading the above-mentioned driving tool that can be run in a Web Assembly environment; A step of executing the above-mentioned driving tool in the Web Assembly runtime environment of the Pocket Framework; and A step comprising generating an interactive answer to the user's question and providing it to the user based on the execution result of the above-mentioned driving tool; Method for dynamic tool integration of large-scale language models using WebAssembly.

2. In Paragraph 1, The step of selecting a driving tool based on the above user question is, A step of generating a query prompt for selecting the driving tool related to the above user question; The step of providing the above query prompt to a large-scale language model; and A step of selecting the driving tool based on the answer of the large-scale language model; comprising Method for dynamic tool integration of large-scale language models using WebAssembly.

3. In Paragraph 2, The step of generating a query prompt for selecting the driving tool related to the above user question is, A step of generating a command to request a tool search based on the above user question; and A step of generating the query prompt including the user question and the command; Method for dynamic tool integration of large-scale language models using WebAssembly.

4. In Paragraph 2, The step of downloading the driving tool that can be run in the above web assembly environment is, A step of providing web assembly tool information executable in a web assembly; and A step of verifying the driving tool in the above web assembly tool information; and A step of downloading the driving tool using the above web assembly tool information; comprising Method for dynamic tool integration of large-scale language models using WebAssembly.

5. In Paragraph 4, The above web assembly tool information A list of web assembly tools that can be run on the above web assembly; and A download link for the above Web Assembly tool; including, Method for dynamic tool integration of large-scale language models using WebAssembly.

6. In Paragraph 1, The step of executing the driving tool in the web assembly runtime environment of the above pocket framework is: Step of running a browser in the above pocket framework; and A step of executing the driving tool through the browser; comprising Method for dynamic tool integration of large-scale language models using WebAssembly.

7. In Paragraph 1, The step of generating and providing an interactive answer to the user's question based on the execution result of the above-mentioned driving tool is: A step of generating an answer prompt including the execution result of the above-mentioned driving tool and the above-mentioned user question; and The step of providing the above answer prompt to the above large-scale language model; comprising, Method for dynamic tool integration of large-scale language models using WebAssembly.

8. In Paragraph 7, The step of generating and providing an interactive answer to the user's question based on the execution result of the above-mentioned driving tool is: A step of receiving an interactive answer to the user question generated from the above-mentioned large-scale language model; and A step of providing an answer to the user question based on the above interactive answer; comprising Method for dynamic tool integration of large-scale language models using WebAssembly.

9. At least one processor; and It includes memory for storing instructions, When the above instructions are executed individually or collectively by the at least one processor, the processor: Action of receiving user questions; The action of selecting a driving tool based on the above user question; The action of downloading the above-mentioned driving tool that can be run in a Web Assembly environment; The operation of executing the above-mentioned driving tool in the web assembly runtime environment of the Pocket Framework; and Based on the execution result of the above-mentioned driving tool, the operation of generating an interactive answer to the above-mentioned user question and providing it to the user; is performed. Dynamic tool integration device for large-scale language models using WebAssembly.

10. Instructions that cause a computer to execute the method according to claim 1, Non-transient computer-readable recording medium.

Images