Algorithm component packaging method and device, equipment and medium

Abstract

The invention provides an algorithm component packaging method and device, equipment and a medium. Comprising the steps of determining a corresponding business component in an MOM system based on a target business scene, and determining a system component corresponding to any business component in a preset system component library according to the preset system component library; determining service components which do not correspond to the system components in the service components as blank service components, and replacing the blank service components according to preset blank system components; packaging the system component according to a preset component interface standard to obtain an initial component, and performing information extraction on the initial component according to a preset interface information type to obtain a target component; determining a process canvas, and dragging the target component and a preset blank system component on the process canvas according to a vue framework in the MOM system to obtain a target process; therefore, the flexibility of the packaging efficiency of the algorithm component is improved.

Description

Technical Field

[0001] This application relates to the field of manufacturing operations management technology, and in particular to a method, apparatus, device and medium for packaging algorithm components. Background Technology

[0002] The field of modern intelligent manufacturing is a comprehensive industrial category that integrates advanced manufacturing technology, information technology, automation technology and intelligent technology. Its core is to reshape the traditional manufacturing model through digitalization, networking and intelligentization to achieve a comprehensive upgrade in production efficiency, quality and flexibility.

[0003] Existing process design methods typically use Manufacturing Execution Systems (MES) and Advanced Planning and Scheduling (APS) systems, usually embedding low-code applications in a hard-coded manner. In addition, most visual assembly platforms focus on building interfaces or data flows.

[0004] However, existing process design methods suffer from poor flexibility and adaptability of the encapsulated components. Summary of the Invention

[0005] This application provides a method, apparatus, device, and medium for encapsulating algorithm components, in order to solve the problem that existing process design methods have poor flexibility and adaptability of encapsulated components.

[0006] Firstly, this application provides a method for encapsulating algorithm components, the method comprising: Based on the target business scenario, determine the corresponding business components in the MOM system, and according to the preset system component library, determine the system component in the preset system component library that corresponds to any business component; Identify business components that do not correspond to system components as blank business components, and replace the blank business components according to the preset blank system components; According to the preset component interface standard, the system components are encapsulated to obtain the initial components, and according to the preset interface information type, information is extracted from the initial components to obtain the target components. Define the process canvas, and based on the Vue framework in the MOM system, drag and drop the target component and the preset blank system component on the process canvas to obtain the target process.

[0007] In some embodiments of this application, based on the target business scenario, the corresponding business component in the MOM system is determined, and according to a preset system component library, the system component corresponding to any business component in the preset system component library is determined, including: Identify each business component, and determine all system components based on the pre-set system component library; The system compares whether the business components and system components correspond, obtains the comparison results, and determines the system component that corresponds to any business component in the system components based on the comparison results.

[0008] In some embodiments of this application, system components are encapsulated according to a preset component interface standard to obtain an initial component, and information is extracted from the initial component according to a preset interface information type to obtain a target component, including: Determine the initial components, as well as the field information types, parameter information types, and data information types in the preset interface information types; Based on the field information type, parameter information type, and data information type, information is extracted from the initial component to obtain the corresponding target field information, target parameter information, and target data information in the initial component; Based on the target field information, target parameter information, and target data information, the initial component is standardized to obtain the target component.

[0009] In some embodiments of this application, a process canvas is determined, and based on the Vue framework in the MOM system, target components and preset blank system components are dragged and dropped on the process canvas to obtain the target process, including: Based on user feedback on the Vue framework, determine the process sequence corresponding to the target process, and determine the process nodes corresponding to each target component and the preset blank system component. Drag and drop process nodes according to the process sequence to obtain the target process corresponding to the process sequence.

[0010] In some embodiments of this application, after determining the process canvas and dragging and dropping the target component and a preset blank system component on the process canvas according to the Vue framework in the MOM system to obtain the target process, the method further includes: Based on the component functions of each preset blank system component, create the corresponding target system component; Replace the preset blank components according to the target system components.

[0011] In some embodiments of this application, after replacing a preset blank component according to the target system component, the method further includes: Add the target system component to the preset system component library.

[0012] In some embodiments of this application, after determining the process canvas and dragging and dropping the target component and a preset blank system component on the process canvas according to the Vue framework in the MOM system to obtain the target process, the method further includes: Determine the process sequence corresponding to the target process, as well as the process nodes corresponding to each target component and the component to be added; Generate and output the corresponding process configuration files based on the process sequence and process nodes.

[0013] Secondly, this application provides a packaging device for algorithm components, the device comprising: The component determination module is used to determine the corresponding business components in the MOM system based on the target business scenario, and to determine the system components in the preset system component library that correspond to any business component. The component replacement module is used to identify business components that do not correspond to system components as blank business components, and to replace blank business components according to preset blank system components; The information extraction module is used to encapsulate system components according to preset component interface standards to obtain initial components, and to extract information from the initial components according to preset interface information types to obtain target components. The drag-and-drop module is used to define the process canvas and, based on the Vue framework in the MOM system, drag and drop the target component and the preset blank system component on the process canvas to obtain the target process.

[0014] Thirdly, this application provides a computer device, including: a processor, and a memory communicatively connected to the processor; The memory stores the instructions that the computer executes; The processor executes computer execution instructions stored in memory to implement the method of this application.

[0015] Fourthly, this application provides a computer-readable storage medium storing program code, which, when executed by a processor, is used to implement the method of this application.

[0016] This application provides a method, apparatus, device, and medium for encapsulating algorithm components. Based on a target business scenario, the method determines the corresponding business component in the MOM system, and according to a preset system component library, determines the system component in the library corresponding to any business component. It identifies business components that do not correspond to any system component as blank business components and replaces these blank business components with preset blank system components. According to a preset component interface standard, the method encapsulates the system component to obtain an initial component, and extracts information from the initial component according to a preset interface information type to obtain the target component. Finally, it determines a process canvas and, using the Vue framework in the MOM system, drags and drops the target component and the preset blank system component onto the process canvas to obtain the target process.

[0017] In this way, by standardizing the encapsulation of algorithm components, abstracting and modeling parameters, and unifying the description of inputs and outputs, and by using visualization tools for logical assembly and process management, the algorithm service can be made pluggable, loosely coupled, and easily integrated. This improves the reusability of algorithm components in process design, reduces redundant development and maintenance costs, makes business process construction more intuitive and efficient, and enhances versatility and compatibility. Attached Figure Description

[0018] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0019] Figure 1 A flowchart illustrating an algorithm component encapsulation method provided in an embodiment of this application; Figure 2 A system architecture diagram of an algorithm component encapsulation method provided in this application embodiment; Figure 3 A schematic diagram of a tool for encapsulating an algorithm component according to an embodiment of this application; Figure 4 A schematic diagram of the structure of an algorithm component encapsulation device provided in an embodiment of this application; Figure 5 This is a structural block diagram of a device for performing a method for encapsulating an algorithm component according to an embodiment of this application. Detailed Implementation

[0020] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0021] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0022] Figure 1 This is a flowchart illustrating a method for encapsulating an algorithm component according to an embodiment of this application. Figure 1 As shown, the encapsulation method for this algorithm component may include the following steps: S110. Based on the target business scenario, determine the corresponding business components in the MOM system, and according to the preset system component library, determine the system component in the preset system component library that corresponds to any business component.

[0023] Among them, the MOM (Manufacturing Operations Management) system is a manufacturing operations management system, which is an integrated software platform focused on production site operations management. Its essence is to integrate the elements of people, machines, materials, methods, and environment in the entire manufacturing process through digital means, so as to realize the transparency, controllability and intelligence of the production process, and can be used for process design in operations management.

[0024] The target business scenario can be understood as the specific business scope, application context, and problem types covered by the MOM system in the actual manufacturing operation process. It is an application scenario that deeply integrates the system's technical capabilities (such as data acquisition, process control, resource scheduling, etc.) with the actual business needs of manufacturing enterprises; for example, it can include different scenarios such as production planning, material traceability, and quality management.

[0025] Business components can be understood as business algorithms corresponding to various business scenarios. Based on the characteristics of various business scenarios in the MOM system (such as production planning, material traceability, quality management, etc.), complex business logic is decomposed into highly cohesive and loosely coupled algorithm modules. In other words, business components are algorithm modules corresponding to business scenarios.

[0026] The preset system component library is a pre-defined system component library. System components can be understood as algorithm modules with actual functions.

[0027] Based on this, the business characteristics of each business scenario are determined through the MOM system, thereby determining the corresponding algorithms for different business characteristics, that is, determining the business components corresponding to the business scenarios. Then, according to the preset system component library, system components that can meet the business functions required by each business scenario in the MOM system are determined, that is, system components corresponding to the business components are determined from the preset system component library.

[0028] S120. Determine that the business components that do not correspond to the system components are blank business components, and replace the blank business components according to the preset blank system components.

[0029] Among them, the preset blank system component is a pre-set blank component that does not have any actual function. The blank system component can be a placeholder component in the MOM system. The placeholder component does not have actual business functions. During operation, it can output simulated data configured by the developers. The visualization tool supports exporting business components containing placeholder components and configuring them for use in the project. After the component development is completed, the algorithm component is submitted and released through the CI / CD process, thereby replacing the placeholder component that has no actual function and is only used to complete the process design.

[0030] Based on this, a pre-set system component library is used to identify the system components corresponding to the business components in the business scenario. Furthermore, it identifies the business components among all business components that do not correspond to the system components. Then, pre-set blank system components, i.e. placeholder components, are used to replace the non-corresponding business components, so as to achieve the normal design and export of the process. This allows the blank system components to be replaced after the algorithm components that can realize the business function are developed in the future.

[0031] S130. According to the preset component interface standard, the system component is encapsulated to obtain the initial component, and according to the preset interface information type, the initial component is extracted to obtain the target component.

[0032] Among them, the preset component interface standard is a pre-defined interface design specification. The interface design specification is a key criterion to ensure efficient interaction between different systems, modules or components. Through the standardization of interface definition, format, protocol and constraints, data interoperability, functional collaboration and system decoupling are achieved.

[0033] Encapsulation can be understood as breaking down a complex system into independent, reusable functional units, hiding internal implementation details, and exposing only necessary interfaces. This design method can improve code maintainability, reusability, and system stability. For example, scenarios such as production scheduling and equipment status monitoring can be abstracted into independent algorithm modules. Based on REST or WSDL specifications, technical descriptions of algorithm input and output parameters can be defined. The input parameters of a production scheduling algorithm include equipment status (JSON format) and order priority (enumeration type), and the output is a sequence of work processes with timestamps. For high-frequency algorithms in MOM (such as Material Requirements Planning (MRP) and production cycle calculation), the template method pattern can be used to define the algorithm skeleton, allowing subclasses to extend specific parameters or rules. The core logic of MRP (such as net requirements calculation) can be encapsulated as a template, and the hook method can be used to adapt to the inventory strategies of different enterprises.

[0034] The initial components are algorithmic components that encapsulate system components and have a unified interface specification. Algorithm components are encapsulated functional units within the system, containing algorithmic modules that perform specific computational logic. Each component provides a standardized interface, possessing reusability and composability; each algorithmic component must implement a unified interface standard. The encapsulation method supports input / output parameter definition and exception handling mechanisms. Component implementation can be a Java class, a Python function, or a containerized service. Algorithm components are designed based on predefined interface design specifications, including unique identifiers, interface version information, functional descriptions, and category attributes, to achieve unified management and invocation of different algorithm types.

[0035] The preset interface information type is the information type corresponding to the pre-defined component interface information. For example, it may include information types such as input / output fields, configurable parameters, and metadata information.

[0036] The target component is a standardized algorithm component that can be used in different production scenarios and business processes, thus improving reusability.

[0037] Based on this, system components are encapsulated through component interface standards, and the interface information type corresponding to the encapsulated initial component is determined, thereby identifying standardized target components so that the target components can be called in different scenarios and processes, improving the flexibility of process design and the reusability of algorithm construction.

[0038] S140. Determine the process canvas, and based on the Vue framework in the MOM system, drag and drop the target component and the preset blank system component on the process canvas to obtain the target process.

[0039] Among them, the process canvas is a tool that uses a graphical interface to intuitively display business processes, logical relationships, and data flow, and can transform abstract business processes into a visual "digital blueprint".

[0040] The Vue framework is a visual assembly tool based on Vue. Visual assembly tools enable the rapid construction of business processes by dragging, connecting, and configuring algorithmic components in a graphical way.

[0041] The target process is the process that meets the user's actual needs, obtained by dragging and dropping algorithm components.

[0042] Based on this, by defining the process canvas, the target components that can realize specific business functions and the blank system components used for placeholders are dragged and connected using the Vue-based visual assembly tool in the MOM system, thereby obtaining the target process, so as to realize the operation and management of business scenarios according to the target process.

[0043] Based on the feasible implementation of S110 described above, this application further provides the following steps: determining the corresponding business component in the MOM system based on the target business scenario, and determining the system component corresponding to any business component in the preset system component library according to the preset system component library, including: Identify each business component, and determine all system components based on the pre-set system component library; The system compares whether the business components and system components correspond, obtains the comparison results, and determines the system component that corresponds to any business component in the system components based on the comparison results.

[0044] Based on this, by identifying the business components corresponding to the business characteristics of each business scenario in the MOM system, and identifying the system components in the system component library that can realize different business functions, the business components and system components are compared to determine whether they have the corresponding business functions. If a system component can correspond to any one of the business components, it indicates that the system component can realize the business function corresponding to that business component. Subsequently, the process is designed based on the corresponding system component, so that the designed target process can realize the business functions required by the business scenario.

[0045] Based on the feasible implementation of S130 described above, this application further provides the following steps: encapsulating system components according to a preset component interface standard to obtain an initial component, and extracting information from the initial component according to a preset interface information type to obtain a target component, including the following steps: Determine the initial components, as well as the field information types, parameter information types, and data information types in the preset interface information types; Based on the field information type, parameter information type, and data information type, information is extracted from the initial component to obtain the corresponding target field information, target parameter information, and target data information in the initial component; Based on the target field information, target parameter information, and target data information, the initial component is standardized to obtain the target component.

[0046] Among them, the field information type is input and output field, the input and output definition includes data name, data type and format description, the target parameter information includes configurable parameters, the parameter description includes parameter name, type, default value and optional range, the target data information includes metadata information, the metadata description includes algorithm version, developer information, function summary, dependency relationship, etc.

[0047] Standardization refers to the process of standardizing components. This involves establishing unified rules, structures, and interfaces to transform algorithm modules into reusable and easily integrated standard units, thereby solving the problems of high coupling and poor adaptability of traditional algorithm modules.

[0048] Based on this, by determining the initial component and the preset input / output fields, configurable parameters and metadata, the corresponding data of the initial component is extracted, and the standardization processing of the initial component is realized to obtain the target component.

[0049] Based on the feasible implementation of S140 described above, this application further provides a method for determining a process canvas and, according to the Vue framework in the MOM system, dragging and dropping target components and preset blank system components on the process canvas to obtain a target process, including the following steps: Based on user feedback on the Vue framework, determine the process sequence corresponding to the target process, and determine the process nodes corresponding to each target component and the preset blank system component. Drag and drop process nodes according to the process sequence to obtain the target process corresponding to the process sequence.

[0050] Among them, the feedback operation refers to the user's feedback on the process sequence of each component. Users can add algorithm components to the business process canvas by dragging and dropping, and set the data flow relationship and calling order between algorithms by connecting lines or configuring the panel, so as to realize the intuitive assembly of multiple algorithm components.

[0051] Process nodes are draggable and configurable graphical units in visual assembly tools, used to build business algorithm processes.

[0052] Based on this, in practical applications, after the visual assembly tool is loaded, it will display nodes corresponding to business scenarios such as "data acquisition", "scheduling optimization" and "performance evaluation" in the component library on the left. These three algorithm nodes can be placed on the process canvas by dragging and dropping. According to the process order provided by the user, the connection is drawn to specify the output of "data acquisition" to the input of "scheduling optimization". At the same time, parameter values ​​(such as sampling rate, optimization target, etc.) can be specified for each algorithm node on the configuration panel.

[0053] Based on the feasible implementation of S140 described above, this application further provides the following steps after determining the process canvas and dragging the target component and a preset blank system component on the process canvas according to the Vue framework in the MOM system to obtain the target process: Based on the component functions of each preset blank system component, create the corresponding target system component; Replace the preset blank components according to the target system components.

[0054] Here, component function refers to the function corresponding to a blank system component in the process, and target system component refers to an algorithm component with the corresponding component function. In practical applications, if an algorithm component is missing during development, a placeholder component can be dragged and dropped to replace it. A blank system component can be used as a placeholder, and the component function requirements, inputs and outputs, etc., corresponding to the blank system component used for the placeholder can be determined. The placeholder component does not have actual business functions and outputs configured simulation data during operation. The visualization tool supports exporting business components containing placeholder components and configuring them for use in the project. After the component development is completed, the corresponding target algorithm component can be submitted and released through the CI / CD process to update the component. That is, the placeholder component in the project can be partially replaced with the developed algorithm component to complete the algorithm process function. This means that even if an algorithm component is missing, the visualization configuration of the algorithm process in the project does not need to wait for the algorithm component development to be completed. It can be carried out synchronously and automatically, improving development efficiency.

[0055] Based on the feasible implementation of S140 described above, this application further provides the following steps after replacing a preset blank component according to the target system component: Add the target system component to the preset system component library.

[0056] Based on this, after completing the development of algorithm components with component functions corresponding to blank system components, the updated algorithm components are added to the preset system component library so that in subsequent practical applications, the components corresponding to the business scenario can be determined based on the components in the system component library to complete the process design.

[0057] Based on the feasible implementation of S140 described above, this application further provides the following steps after determining the process canvas and dragging the target component and a preset blank system component on the process canvas according to the Vue framework in the MOM system to obtain the target process: Determine the process sequence corresponding to the target process, as well as the process nodes corresponding to each target component and the component to be added; Generate and output the corresponding process configuration files based on the process sequence and process nodes.

[0058] The process configuration file is an export of the algorithm process built by the user in the visualization tool, which generates a runnable configuration file or project code.

[0059] Based on this, by exporting the visual assembly results as a runnable configuration file or project code, the front-end interface and back-end services can be directly loaded and used, significantly shortening the development cycle and reducing the complexity of front-end and back-end integration.

[0060] Please refer to Figure 2 , Figure 2 A system architecture diagram of an algorithm component encapsulation method provided in this application embodiment; as shown. Figure 2 As shown, business algorithm modules are encapsulated into standard algorithm components with unified interfaces, enabling reuse across multiple business scenarios. Each algorithm component defines standard input / output, configurable parameters, and metadata information, and supports encapsulation in the form of JSON configuration files or executable code snippets. Using a Vue-based visual assembly tool, the encapsulated algorithm components are registered as draggable components and combined on a business process canvas. The assembled process is exported to generate runnable configuration or project code for integration by front-end and back-end development. The algorithm component registration platform acts as a bridge between algorithm components and the subsequent visual assembly tool. The platform manages the metadata of algorithm components (such as interfaces, versions, input / output specifications, etc.) and registers them in the system component library. It provides interfaces for component upload, verification, and registration, stores component metadata, runtime environment requirements, and dependency information, and can be integrated with DevOps systems to achieve CI / CD. The business execution engine is responsible for the deployment and operation of the process, binding and executing algorithm services with real business processes. It can dynamically schedule the execution order of algorithm components according to the process definition file, supporting multi-threaded concurrent execution. It provides transaction control and error compensation mechanisms, and supports runtime flowchart visualization and log tracking.

[0061] Please refer to Figure 3 , Figure 3 A schematic diagram of a tool for encapsulating an algorithm component provided in an embodiment of this application; as shown. Figure 3 As shown, the encapsulated algorithm components are registered and displayed as draggable components in the Vue-based visual assembly tool. The tool can identify the interface definition and metadata of the algorithm components and display them as graphical nodes in the component list on the canvas. Users can add algorithm components to the business process canvas by dragging and dropping, and set the data flow relationship and call order between algorithms through connections or configuration panels, realizing the intuitive assembly of multiple algorithm components.

[0062] In some embodiments of this application, based on the characteristics of the business domains corresponding to various business scenarios in the MOM system, complex business logic is decomposed into highly cohesive and loosely coupled algorithm modules according to the business functions corresponding to the determined business scenarios. Corresponding system components are determined, and the components are standardized and encapsulated based on predefined interface design specifications to form algorithm components with unified interface specifications. Standardized input and output fields, configurable parameters, and metadata information are defined for each algorithm component to obtain the target component. At the same time, business components that do not correspond to system components are determined, and blank components that can be used as placeholders are determined so that blank components can replace uncorresponding business components in the process design. By determining the process canvas and the Vue framework, the target component and the blank component are dragged and connected according to the process sequence to obtain the target process.

[0063] In this way, by uniformly encapsulating business algorithms into standardized algorithm components, algorithm modules can be easily reused in different production scenarios and business processes, reducing redundant development and maintenance costs. Combined with a Vue-based visual assembly tool, drag-and-drop assembly of algorithm components and process configuration are realized, making business process construction more intuitive and efficient. Complex logic can be assembled without manually writing underlying integration code. It supports exporting the visual assembly results as runnable configuration files or project code, which can be directly loaded and used by the front-end interface and back-end services, significantly shortening the development cycle and reducing the complexity of front-end and back-end integration. It improves the maintainability and adaptability of the system, as well as the reusability of algorithm modules, and improves the efficiency and simplicity of process design.

[0064] Figure 4 This is a schematic diagram of the structure of an algorithm component encapsulation device 400 provided in an embodiment of this application. Figure 4 As shown, the encapsulation device 400 for an algorithm component includes: a component determination module 410, a component replacement module 420, an information extraction module 430, and a drag-and-drop module 440; wherein: The component determination module 410 is used to determine the corresponding business components in the MOM system based on the target business scenario, and to determine the system components in the preset system component library that correspond to any business component. The component replacement module 420 is used to determine that a business component that does not correspond to a system component is a blank business component, and to replace the blank business component according to a preset blank system component; The information extraction module 430 is used to encapsulate system components according to preset component interface standards to obtain initial components, and to extract information from the initial components according to preset interface information types to obtain target components. The drag-and-drop module 440 is used to define the process canvas and, based on the Vue framework in the MOM system, drag and drop the target component and the preset blank system component on the process canvas to obtain the target process.

[0065] In this embodiment of the application, the component determination module 410 can also be specifically used for: Identify each business component, and determine all system components based on the pre-set system component library; The system compares whether the business components and system components correspond, obtains the comparison results, and determines the system component that corresponds to any business component in the system components based on the comparison results.

[0066] In this embodiment of the application, the information extraction module 430 can also be specifically used for: Determine the initial components, as well as the field information types, parameter information types, and data information types in the preset interface information types; Based on the field information type, parameter information type, and data information type, information is extracted from the initial component to obtain the corresponding target field information, target parameter information, and target data information in the initial component; Based on the target field information, target parameter information, and target data information, the initial component is standardized to obtain the target component.

[0067] In this embodiment of the application, the drag-and-drop module 440 can also be specifically used for: Based on user feedback on the Vue framework, determine the process sequence corresponding to the target process, and determine the process nodes corresponding to each target component and the preset blank system component. Drag and drop process nodes according to the process sequence to obtain the target process corresponding to the process sequence.

[0068] In this embodiment of the application, the encapsulation device 400 for an algorithm component can also be specifically used for: Based on the component functions of each preset blank system component, create the corresponding target system component; Replace the preset blank components according to the target system components.

[0069] In this embodiment of the application, the encapsulation device 400 for an algorithm component can also be specifically used for: Add the target system component to the preset system component library.

[0070] In this embodiment of the application, the encapsulation device 400 for an algorithm component can also be specifically used for: Determine the process sequence corresponding to the target process, as well as the process nodes corresponding to each target component and the component to be added; Generate and output the corresponding process configuration files based on the process sequence and process nodes.

[0071] Figure 5 This is a schematic diagram of the structure of a device for performing a packaging method for an algorithm component according to an embodiment of this application. Figure 5 As shown, the device 500 includes: The device 500 may include a processor 501 with one or more processing cores, a memory 502 with one or more computer-readable storage media, a communication component 503, and other components. The processor 501, memory 502, and communication component 503 are connected via a bus 504.

[0072] In the specific implementation process, at least one processor 501 executes computer execution instructions stored in memory 502, causing at least one processor 501 to execute the above-described encapsulation method of an algorithm component.

[0073] The specific implementation process of processor 501 can be found in the above method embodiments, and its implementation principle and technical effect are similar. It will not be repeated here.

[0074] Furthermore, the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. A general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.

[0075] The memory may include random access memory (RAM) and may also include non-volatile memory (NVM), such as at least one disk storage device.

[0076] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings are not limited to a single bus or a single type of bus.

[0077] In some embodiments, a computer program product is also provided, including a computer program or instructions that, when executed by a processor, implement the steps in the encapsulation method of any of the above-described algorithm components.

[0078] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0079] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0080] Therefore, embodiments of this application provide a computer-readable storage medium storing a plurality of program codes, which can be loaded by a processor to execute the steps in the encapsulation method of any algorithm component provided in embodiments of this application.

[0081] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0082] According to one aspect of this application, a computer program product or computer program is provided, the computer program product or computer program including computer instructions stored in a computer-readable storage medium.

[0083] Since the instructions stored in the storage medium can execute the steps in the encapsulation method of any algorithm component provided in the embodiments of this application, the beneficial effects that the encapsulation method of any algorithm component provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0084] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the appended claims.

[0085] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope.

Claims

1. A method for encapsulating algorithm components, characterized in that, The method includes: Based on the target business scenario, the corresponding business components in the MOM system are determined, and according to the preset system component library, the system component in the preset system component library corresponding to any of the business components is determined; The business components that do not correspond to the system components are identified as blank business components, and the blank business components are replaced according to the preset blank system components. According to the preset component interface standard, the system component is encapsulated to obtain an initial component, and according to the preset interface information type, information is extracted from the initial component to obtain the target component; Define the process canvas, and based on the Vue framework in the MOM system, drag and drop the target component and the preset blank system component on the process canvas to obtain the target process.

2. The method according to claim 1, characterized in that, The step of determining the corresponding business component in the MOM system based on the target business scenario, and determining the system component in the preset system component library corresponding to any of the business components, includes: Each of the aforementioned business components is determined, and all of the aforementioned system components are determined according to the preset system component library; The system component is compared with the business component to determine whether they correspond, and the comparison result is obtained. Based on the comparison result, the system component that corresponds to any of the business components is determined.

3. The method according to claim 1, characterized in that, The process of encapsulating the system components according to a preset component interface standard to obtain an initial component, and extracting information from the initial component according to a preset interface information type to obtain a target component, includes: Determine the initial component, as well as the field information type, parameter information type, and data information type in the preset interface information type; Based on the field information type, parameter information type, and data information type, information extraction is performed on the information in the initial component to obtain the target field information, target parameter information, and target data information corresponding to the initial component. Based on the target field information, target parameter information, and target data information, the initial component is standardized to obtain the target component.

4. The method according to claim 1, characterized in that, The process involves determining the process canvas and, based on the Vue framework in the MOM system, dragging and dropping the target component and the preset blank system component onto the process canvas to obtain the target process, including: Based on user feedback on the Vue framework, the process sequence corresponding to the target process is determined, and the process nodes corresponding to each target component and the preset blank system component are determined. According to the process sequence, the process nodes are dragged and dropped to obtain the target process corresponding to the process sequence.

5. The method according to claim 1, characterized in that, After determining the process canvas and, based on the Vue framework in the MOM system, dragging and dropping the target component and the preset blank system component on the process canvas to obtain the target process, the method further includes: Based on the component functions corresponding to each of the preset blank system components, create the corresponding target system components; The preset blank component is replaced according to the target system component.

6. The method according to claim 5, characterized in that, After replacing the preset blank component according to the target system component, the method further includes: Add the target system component to the preset system component library.

7. The method according to claim 1, characterized in that, After determining the process canvas and, based on the Vue framework in the MOM system, dragging and dropping the target component and the preset blank system component on the process canvas to obtain the target process, the method further includes: Determine the process sequence corresponding to the target process, and the process nodes corresponding to each target component and the component to be added; Based on the process sequence and the process nodes, generate and output the corresponding process configuration files.

8. A packaging device for an algorithm component, characterized in that, The device includes: The component determination module is used to determine the corresponding business component in the MOM system based on the target business scenario, and to determine the system component in the preset system component library that corresponds to any of the business components; The component replacement module is used to determine that a business component that does not correspond to the system component is a blank business component, and to replace the blank business component according to a preset blank system component; The information extraction module is used to encapsulate the system components according to the preset component interface standard to obtain an initial component, and to extract information from the initial component according to the preset interface information type to obtain a target component; The drag-and-drop module is used to define the process canvas and, based on the Vue framework in the MOM system, drag and drop the target component and the preset blank system component on the process canvas to obtain the target process.

9. A computer device, characterized in that, include: One or more processors; Memory; One or more programs, wherein the one or more programs are stored in memory and configured to be executed by one or more processors, the one or more programs being configured to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores program code that can be called by a processor to perform the method as described in any one of claims 1 to 7.

Images