A heterogeneous logic graph reasoning method, electronic device and storage medium

Abstract

This invention discloses a heterogeneous logic graph reasoning method, electronic device, and storage medium. The method includes the following steps: real-time acquisition of user design operations, including user-selected page component types and event types; generation of a design request parameter set as matching input conditions based on the design operations; calculation of matching degree for each heterogeneous logic graph in the heterogeneous logic graph resource library based on the design request parameter set, and sorting the heterogeneous logic graphs in descending order according to the matching degree calculation results, prioritizing the recommendation of heterogeneous logic graphs suitable for the current design scenario; and receiving the heterogeneous logic graph corresponding to the user's selected recommendation result. This invention proactively recommends the optimal logic solution, achieving intelligent and personalized design processes, shortening the logic configuration time for common business pages, and improving the logic reuse rate between components, significantly outperforming traditional low-code platforms.

Description

Technical Field

[0001] This invention relates to the field of heterogeneous logic graph construction, and more particularly to a heterogeneous logic graph reasoning method, electronic device, and storage medium. Background Technology

[0002] Current low-code development platforms and visual tools face significant efficiency bottlenecks and insufficient intelligence in the development of page components. Specifically, when developers configure common interface elements such as dropdown lists, data tables, tree controls, or forms, they need to perform repetitive operations such as data source connection, API parameter mapping, front-end rendering rule setting, and event callback binding for each component's initialization loading, dynamic rendering, and user interaction scenarios.

[0003] This fragmented development model not only leads to substantial duplication of configuration operations (over 80%), but also, due to the lack of cross-component logical abstraction mechanisms, requires the same business logic to be repeatedly implemented across different controls. More importantly, existing platform template libraries typically only provide static component templates, and their built-in flowchart automation functions are often limited to a single data loading pipeline (such as table pagination queries), failing to handle heterogeneous logic scenarios commonly encountered in real-world business scenarios, such as multi-component linkage (e.g., dropdown selection triggering table refresh) and complex event handling (e.g., linking tree menu updates after form submission).

[0004] Existing technical solutions suffer from three key shortcomings: First, the granularity of logical modeling is limited, failing to establish a unified logical description model encompassing the entire chain, including data acquisition, transformation, rendering, and event response. Second, intelligent recommendation capabilities are weak, lacking a semantic-based business logic graph matching mechanism, making it difficult for developers to quickly locate reusable logic modules. Third, adaptive adjustment capabilities are insufficient; when the recommendation logic differs from specific requirements, the platform often requires developers to completely reconfigure rather than providing a visual parameter correction path. These issues directly result in limited improvements in the development efficiency of complex business pages. Although some component templates and flowchart automation technologies exist in the current technology, they are mostly designed for single data loading processes and lack cross-component and cross-event general heterogeneous logic graph modeling and intelligent recommendation functions, failing to meet the needs of rapid matching and flexible adjustment of heterogeneous logic in complex page development.

[0005] Therefore, there is an urgent need to propose a component modeling and management method that supports heterogeneous logic diagram recommendation, custom adjustment, and continuous optimization of the resource library, so as to improve the automation, intelligence, and reuse efficiency of page development. Summary of the Invention

[0006] The purpose of this invention is to overcome the shortcomings of the prior art and provide a heterogeneous logic diagram reasoning method, electronic device and storage medium.

[0007] The objective of this invention is achieved through the following technical solution:

[0008] A first aspect of the present invention provides a heterogeneous logic diagram reasoning method for Manufacturing Operations Management (MOM), comprising the following steps:

[0009] Real-time collection of user design operations, including the user's selected page component types and event types;

[0010] The design operation generates a set of design request parameters as matching input conditions. The set of design request parameters includes component type parameters and event type parameters.

[0011] Based on the design request parameter set, a matching degree is calculated for each heterogeneous logic graph in the heterogeneous logic graph resource library. Based on the matching degree calculation results, the heterogeneous logic graphs are sorted in descending order, and the heterogeneous logic graphs that are suitable for the current design scenario are recommended first. The heterogeneous logic graph is a directed graph used to describe the logical execution flow of page components.

[0012] Receive the heterogeneous logic diagram corresponding to the recommended selection results selected by the user.

[0013] Furthermore, the page component types include drop-down lists, tables, trees, and forms, and the event types include page initialization, single click, double click, and refresh.

[0014] Furthermore, the elements of the heterogeneous logic diagram include:

[0015] Node information elements: node type, execution content;

[0016] Connection information elements: the execution order and dependencies between nodes;

[0017] Tag information elements: Adapted event tags and component type tags.

[0018] Furthermore, in the node information element, the node type includes:

[0019] Page logic flow nodes include a series of actions such as user interaction, data request, data processing, page rendering, and event response, and are bound to front-end JS operations and back-end interactive logic flow;

[0020] The middle platform service nodes extract common capabilities from services to form standardized, modular, and reusable services, which can be flexibly called by multiple front-end applications; the common capabilities include data processing, business processes, and general services.

[0021] A service node is a set of independently deployable and invoked software functional units encapsulated to fulfill a specific functional requirement. It can interact with other systems or other modules through API interfaces.

[0022] In a database, an entity node is mapped to a table, and the entity's attributes are mapped to the table's columns.

[0023] The executed content includes: SQL statements, API addresses, and JS function names.

[0024] Furthermore, the heterogeneous logic graph resource library includes: a unique graph number, a graph name, an adaptation tag, a graph structure, and a usage frequency; the adaptation tag includes event tags and component tags, the graph structure includes nodes and connections, and the usage frequency is dynamically updated.

[0025] Further, the step of calculating the matching degree for each heterogeneous logic diagram in the heterogeneous logic diagram resource library based on the design request parameter set includes:

[0026] Matching score = α × event tag similarity + β × component type similarity + γ × historical usage frequency normalized value matching score; α, β, and γ are weighting coefficients, satisfying α + β + γ = 1; where:

[0027] Event tag similarity: Compare the event type parameters in the design request parameter set with the event tags in the heterogeneous logic diagram. When there is a complete match, the event tag similarity is 1; when there is a partial match, the event tag similarity is 0.5; and when there is no match, the event tag similarity is 0.

[0028] Component type similarity: Compare the component type parameters in the design request parameter set with the component tags in the heterogeneous logic diagram. When there is a complete match, the component tag similarity is 1; when there is a partial match, the component tag similarity is 0.5; and when there is no match, the component tag similarity is 0.

[0029] Historical usage frequency normalization value: corresponds to the percentage of the heterogeneous logic graph used in historical recommendations, representing the universality and priority of the heterogeneous logic graph.

[0030] Furthermore, the method also includes:

[0031] Receive user edits and modifications to the heterogeneous logic diagram corresponding to the recommended selection results;

[0032] Save the modified heterogeneous logic diagram to the heterogeneous logic diagram resource library.

[0033] Furthermore, the editing modifications include:

[0034] Adding nodes includes adding new API data sources and adding new data rendering methods;

[0035] Delete node: Delete invalid or redundant steps;

[0036] Modify nodes: Adjust parameters including SQL statements, API addresses, and JS rendering functions;

[0037] Connection adjustment: Modify the execution order and dependencies between nodes.

[0038] A second aspect of the present invention provides an electronic device including a storage unit and a processing unit, wherein the storage unit stores computer instructions executable on the processing unit, and the processing unit executes the steps of a heterogeneous logic diagram reasoning method as described in the first aspect when executing the computer instructions.

[0039] A third aspect of the present invention provides a storage medium having computer instructions stored thereon, which, when executed, perform the steps of a heterogeneous logic diagram reasoning method as described in the first aspect.

[0040] The beneficial effects of this invention are:

[0041] In an exemplary embodiment of the present invention, the optimal logical diagram is automatically recommended through tag comparison, frequency priority, and intelligent sorting. By analyzing the component types and data flow characteristics in the current development environment, the optimal logical solution is proactively recommended, achieving intelligent and personalized design processes. This method can shorten the logic configuration time for common business pages and improve the logic reusability between components, significantly outperforming traditional low-code platforms. Attached Figure Description

[0042] Figure 1 This is a flowchart of a heterogeneous logic graph reasoning method provided in an exemplary embodiment of the present invention;

[0043] Figure 2 This is a schematic diagram of node types provided in an exemplary embodiment of the present invention;

[0044] Figure 3 A heterogeneous logic diagram for initializing a drop-down list provided in an exemplary embodiment of the present invention;

[0045] Figure 4 A heterogeneous logic diagram for initializing a table provided in an exemplary embodiment of the present invention;

[0046] Figure 5 A heterogeneous logic diagram for initializing a tree provided in an exemplary embodiment of the present invention;

[0047] Figure 6 This is a heterogeneous logic diagram for initializing a form provided in an exemplary embodiment of the present invention. Detailed Implementation

[0048] The technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0049] In the description of this invention, it should be noted that the directions or positional relationships indicated by terms such as "center," "upper," "lower," "left," "right," "vertical," "horizontal," "inner," and "outer" are based on the directions or positional relationships shown in the accompanying drawings and are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this invention. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance.

[0050] In the description of this invention, it should be noted that, unless otherwise explicitly specified and limited, the terms "installation," "connection," and "joining" should be interpreted broadly. For example, they can refer to fixed connections, detachable connections, or integral connections; they can refer to mechanical connections or electrical connections; they can refer to direct connections or indirect connections through an intermediate medium; and they can refer to the internal communication between two components. Those skilled in the art can understand the specific meaning of the above terms in this invention based on the specific circumstances.

[0051] Furthermore, the technical features involved in the different embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other.

[0052] In existing technologies, low-code platforms or visual development tools typically require users to repeatedly perform data source configuration, front-end rendering logic design, and event binding operations during the data loading, rendering, and event binding processes of page components (such as drop-down lists, tables, trees, forms, etc.). This results in a large amount of redundant work in the development process and a lack of efficient logic diagram recommendation and reuse mechanisms.

[0053] See Figure 1 , Figure 1 The flowchart illustrates a heterogeneous logic graph reasoning method provided in an exemplary embodiment of the present invention, for Manufacturing Operations Management (MOM), including the following steps:

[0054] S1: Real-time collection of user design operations, including the user's selected page component type and event type;

[0055] S2: Generate a set of design request parameters as matching input conditions based on the design operation. The set of design request parameters includes component type parameters and event type parameters.

[0056] S3: Based on the design request parameter set, calculate the matching degree for each heterogeneous logic graph in the heterogeneous logic graph resource library, and sort the heterogeneous logic graphs in descending order according to the matching degree calculation results, giving priority to recommending heterogeneous logic graphs that are suitable for the current design scenario; the heterogeneous logic graph is a directed graph used to describe the logical execution flow of page components.

[0057] S4: Receive the heterogeneous logic diagram corresponding to the recommended selection result selected by the user.

[0058] This exemplary embodiment aims to address the problems of repetitive page component configurations and difficulty in reusing logic diagrams in existing technologies. It provides a heterogeneous logic diagram reasoning method that, through tag matching and intelligent recommendation algorithms, achieves rapid matching, dynamic adjustment, and resource library reuse of heterogeneous logic diagrams, improving development efficiency and reducing error risks. Specifically, the user-selected design and matching logic matching process is as follows:

[0059] S1: Collection of User Design Actions: When a user designs on the MOM software design page, the system will collect the user's design operations in real time, mainly including:

[0060] The type of page component selected by the user (in an exemplary embodiment, such as a drop-down list, table, tree, form, etc.);

[0061] The event types configured by the user (in an exemplary embodiment, such as page initialization, click, double click, refresh, etc.).

[0062] In one exemplary embodiment, when designing a page, the user selects the "Table" component and sets a "Page Initialization" event for it.

[0063] S2: The system generates design request parameters in real time: The system will automatically generate a set of design request parameters based on the user's current design selections.

[0064] Component type parameters (in one exemplary embodiment, a table);

[0065] Event type parameter (in an exemplary embodiment, page initialization).

[0066] This parameter serves as a matching input condition for retrieving heterogeneous logic graph resource libraries.

[0067] S3: System matching process:

[0068] S31: Matching Formula Calculation: The system will calculate the matching degree for each heterogeneous logic diagram in the heterogeneous logic diagram resource library based on the design request parameters;

[0069] S32: Matching result sorting: The system sorts the heterogeneous logic diagrams in descending order based on the matching degree calculation results, and prioritizes recommending the logic diagram that is most suitable for the current design scenario.

[0070] S4: User Interaction: The system will display the recommended heterogeneous logic diagrams to the user in real time, and the user can: directly select the recommended heterogeneous logic diagram for quick configuration.

[0071] Therefore, as shown above, user-selected design (the selection of components and events, supporting the combination and recommendation of heterogeneous logic across components and events) serves as the input condition for the matching process. The system automatically recommends the optimal structural logic diagram through tag comparison, frequency priority, and intelligent sorting. By analyzing the component types and data flow characteristics in the current development environment, it proactively recommends the optimal logic solution, achieving intelligent and personalized design. This approach can shorten the logic configuration time for common business pages and improve the logic reusability between components, significantly outperforming traditional low-code platforms.

[0072] The following content will provide illustrative examples of the preferred solutions, starting with the definition and modeling of the page heterogeneous logic diagram:

[0073] More preferably, in an exemplary embodiment, the page component types include drop-down lists, tables, trees, and forms, and the event types include page initialization, single click, double click, and refresh.

[0074] Specifically, in this exemplary embodiment, based on the heterogeneous logic graph resource library and intelligent recommendation mechanism, it supports heterogeneous logic graph matching and reasoning in all scenarios such as page initialization, single click, and double click.

[0075] More preferably, in an exemplary embodiment, the elements of the heterogeneous logic diagram include:

[0076] Node information elements: node type, execution content;

[0077] Connection information elements: the execution order and dependencies between nodes;

[0078] Tag information elements: Adapted event tags and component type tags.

[0079] More preferably, in an exemplary embodiment, in the node information element, such as Figure 2 As shown, the node types include:

[0080] Page logic flow nodes ( Figure 2 (Left 1) includes a series of actions including user interaction, data request, data processing, page rendering, and event response, and is bound to the front-end JS operation and the back-end interactive logic flow;

[0081] Middle platform service node ( Figure 2(Left 2) Extract the common capabilities of the services to form standardized, modular, and reusable services for multiple front-end applications to call flexibly; the common capabilities include data processing, business processes, and general services;

[0082] Service node ( Figure 2 (Left 3) A set of independently deployable and callable software functional units encapsulated to achieve a certain functional requirement, which can interact with other systems or other modules through API interfaces;

[0083] Database entity node ( Figure 2 (Left 4) In the database, an entity is mapped to a table, and the entity's attributes are mapped to the table's columns.

[0084] The executed content includes: SQL statements, API addresses, and JS function names.

[0085] In such Figures 3-6 In the specific exemplary embodiments, heterogeneous logic diagrams for initializing drop-down lists, tables, trees, and forms are given respectively. Specifically:

[0086] The heterogeneous logic diagram for initializing the dropdown list is as follows: Figure 3 As shown, the node labels include: (1) Event label: page initialization; (2) Component label: drop-down list. Figure 3 The link nodes from beginning to end include, in sequence, the "Get Drop-down List Data Source" and "Render Drop-down List Data" nodes in the page logic flow node category; and the "Get Drop-down List Data Source" node in the page logic flow node category specifically includes the following sequentially connected nodes: "Drop-down List Data Population Service" in the service node category, "Drop-down List Data Source Access Service" in the middle platform service node category, and "Drop-down List Data Source Entity" in the database entity node category.

[0087] Table initialization heterogeneous logic diagram as follows Figure 4 As shown, the node labels include: (1) Event label: page initialization; (2) Component label: table. Figure 4 The link nodes from beginning to end include, in sequence, the "Get Table Data Source" and "Render Table Data" nodes of the page logic flow node category. The "Get Table Data Source" node of the page logic flow node category specifically includes the "Table Data Population Service" of the service node category, which is connected to the "Table Data Source Access Service" and "Table Data Source Assembly Service" of the middle platform service node category. The "Table Data Source Access Service" of the middle platform service node category is also connected to the "Table Data Source Entity 1" and "Table Data Source Entity 2" of the database entity node category.

[0088] Tree initialization heterogeneous logic diagram as follows Figure 5 As shown, the node labels include: (1) Event label: page initialization; (2) Component label: tree. Figure 5 The link nodes from beginning to end include, in sequence, the "Get Tree Data Source" and "Render Tree Structure Data" of the page logic flow node category; and the "Get Tree Data Source" of the page logic flow node category specifically includes: the "Tree Data Population Service" of the service node category, which is connected to the "Tree Data Source Access Service" and the "Tree Structure Data Construction Service" of the middle platform service node category. The "Tree Data Source Access Service" of the middle platform service node category is also connected to the "Tree Parent Node Data Source Entity" and the "Tree Child Node Data Source Entity" of the database entity node category.

[0089] The heterogeneous logic diagram for form initialization is as follows: Figure 6 As shown, the node labels include: (1) Event label: page initialization; (2) Component label: form. Figure 6 The link nodes from beginning to end include, in sequence, the "Get Form Data Source" node category, the "Render Form Structure Data" node category, and the "Render Form Structure Data" node category. The "Get Form Data Source" node category specifically includes, in sequence, the "Form Data Fill Service" node category, the "Form Data Source Access Service" node category, and the "Form Data Source Entity" node category.

[0090] Single-click and double-click events are used to construct heterogeneous logic diagrams in a similar process structure.

[0091] In summary, in the above exemplary embodiments, discrete component operations are abstracted into composable logical primitives, thereby improving the efficiency of visual development.

[0092] Secondly, the following exemplary implementation illustrates the construction of a heterogeneous logic graph resource library:

[0093] More preferably, in an exemplary embodiment, the heterogeneous logic graph resource library includes: a unique graph number, a graph name, an adaptation tag, a graph structure, and a usage frequency; the adaptation tag includes an event tag and a component tag, the graph structure includes nodes and connections, and the usage frequency is dynamically updated.

[0094] More preferably, in an exemplary embodiment, the resource library management supports: system-preset standard heterogeneous logic diagrams; user-defined addition, modification, and deletion of heterogeneous logic diagrams; and heterogeneous logic diagram version management and history (corresponding to the exemplary embodiment of subsequent operations).

[0095] The following exemplary implementations will then be used to describe recommendations for designing page processing logic in MOM software based on graph models:

[0096] More preferably, in an exemplary embodiment, the step of calculating the matching degree for each heterogeneous logic graph in the heterogeneous logic graph resource library based on the design request parameter set includes:

[0097] Matching score = α × event tag similarity + β × component type similarity + γ × historical usage frequency normalized value matching score; α, β, and γ are weighting coefficients, satisfying α + β + γ = 1; where:

[0098] Event tag similarity: Compare the event type parameters in the design request parameter set with the event tags in the heterogeneous logic diagram. When there is a complete match, the event tag similarity is 1; when there is a partial match, the event tag similarity is 0.5; and when there is no match, the event tag similarity is 0.

[0099] Component type similarity: Compare the component type parameters in the design request parameter set with the component tags in the heterogeneous logic diagram. When there is a complete match, the component tag similarity is 1; when there is a partial match, the component tag similarity is 0.5; and when there is no match, the component tag similarity is 0.

[0100] Historical usage frequency normalization value: corresponds to the percentage of the heterogeneous logic graph used in historical recommendations, representing the universality and priority of the heterogeneous logic graph.

[0101] Specifically, when a user designs a page, they select a component (such as a dropdown list) and configure events (such as page initialization, clicks, etc.), and the system collects event information. Then, matching and recommendation are performed as in this exemplary embodiment. Specifically, based on the component type and event type, the system calculates the matching degree in the heterogeneous logical graph resource library.

[0102] By analyzing the component types, data flow characteristics, and historical behavior patterns in the current development environment, the system proactively recommends the optimal logical solution.

[0103] The following exemplary implementations illustrate the visualization, editing, and custom construction of heterogeneous logic diagrams:

[0104] More preferably, in an exemplary embodiment, the method further includes:

[0105] Receive user edits and modifications to the heterogeneous logic diagram corresponding to the recommended selection results;

[0106] Save the modified heterogeneous logic diagram to the heterogeneous logic diagram resource library.

[0107] Specifically, in this exemplary embodiment, the user can double-click the recommended heterogeneous logic diagram to enter the diagram editing interface. In a preferred embodiment, the editing includes: adding nodes: including adding API data sources and adding data rendering methods; deleting nodes: deleting invalid or redundant steps; modifying nodes: adjusting parameters including SQL statements, API addresses, and JS rendering functions; and adjusting connections: modifying the execution order and dependencies between nodes.

[0108] After editing, you can save and version control the adjusted heterogeneous logic diagram: (1) Save it as a new heterogeneous logic diagram, and the system will automatically generate a new diagram ID and archive it into the resource library. (2) Overwrite the current heterogeneous logic diagram and automatically upgrade the version number. It also supports querying and rolling back the diagram version history.

[0109] In summary, this exemplary embodiment implements a visual logic orchestration interface, supports custom adjustments to the recommendation logic via drag-and-drop, and ensures that the modified logic graph can feed back into the resource library to form a continuously evolving closed loop.

[0110] More preferably, in an exemplary embodiment, the system can also dynamically update the usage frequency of heterogeneous logic diagrams, recording the usage frequency of each heterogeneous logic diagram: (1) The usage frequency is automatically incremented by one each time a user applies the heterogeneous logic diagram. (2) The usage frequency serves as an important reference for recommendation priority. By dynamically adjusting the recommendation ranking based on usage frequency, the system can learn on its own and prioritize recommending heterogeneous logic diagrams that are frequently used and fit the scenario.

[0111] Having the same inventive concept as the exemplary embodiments described above, another exemplary embodiment of the present invention provides an electronic device, including a storage unit and a processing unit, wherein the storage unit stores computer instructions executable on the processing unit, and the processing unit executes the computer instructions as follows: Figure 1 The steps of the heterogeneous logic graph reasoning method described above.

[0112] Electronic devices are manifested in the form of general-purpose computing devices. Components of electronic devices may include, but are not limited to: at least one processing unit, at least one storage unit, and a bus connecting different system components (including storage units and processing units).

[0113] The storage unit stores program code that can be executed by the processing unit, causing the processing unit to perform the steps described in the "Exemplary Methods" section above, based on various exemplary embodiments of the present invention. For example, the processing unit can perform actions such as... Figure 1 The method shown in the figure.

[0114] The storage unit may include readable media in the form of volatile storage units, such as random access memory (RAM) and / or cache storage units, and may further include read-only memory (ROM).

[0115] The storage unit may also include a program / utility having a set (at least one) of program modules, including but not limited to: an operating system, one or more application programs, other program modules, and program data, each or some combination of these examples may include an implementation of a network environment.

[0116] A bus can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus that uses any of the various bus structures.

[0117] The electronic device can also communicate with one or more external devices (e.g., keyboards, pointing devices, Bluetooth devices, etc.), one or more devices that enable a user to interact with the electronic device, and / or any device that enables the electronic device to communicate with one or more other computing devices (e.g., routers, modems, etc.). This communication can be performed via input / output (I / O) interfaces. Furthermore, the electronic device can communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter. The network adapter communicates with other modules of the electronic device via a bus. It should be understood that other hardware and / or software modules can be used in conjunction with the electronic device, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0118] Through the above description, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to this exemplary embodiment can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the method according to this exemplary embodiment.

[0119] Having the same inventive concept as the exemplary embodiments described above, another exemplary embodiment of the present invention provides a storage medium having computer instructions stored thereon, wherein the computer instructions, when executed, perform actions such as... Figure 1 The steps of the heterogeneous logic graph reasoning method described above.

[0120] Based on this understanding, the technical solution of this embodiment, or the part that contributes to the prior art, or part of the technical solution, can be embodied in the form of a software product (program product). The computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention.

[0121] The program product may employ any combination of one or more readable media. A readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0122] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, carrying readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium, capable of sending, propagating, or transmitting programs for use by or in conjunction with an instruction execution system, apparatus, or device.

[0123] The program code contained on the readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical fiber, RF, etc., or any suitable combination thereof.

[0124] Program code for performing the operations of this invention can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0125] Obviously, the above embodiments are merely illustrative examples for clear explanation and are not intended to limit the implementation. Those skilled in the art can make other variations or modifications based on the above description. It is neither necessary nor possible to exhaustively list all possible implementations. However, obvious variations or modifications derived therefrom are still within the scope of protection of this invention.

Claims

1. A heterogeneous logic diagram reasoning method for Manufacturing Operations Management (MOM), characterized in that: Includes the following steps: Real-time collection of user design operations, including the user's selected page component types and event types; The design operation generates a set of design request parameters as matching input conditions. The set of design request parameters includes component type parameters and event type parameters. Based on the design request parameter set, a matching degree is calculated for each heterogeneous logic graph in the heterogeneous logic graph resource library. Based on the matching degree calculation results, the heterogeneous logic graphs are sorted in descending order, and the heterogeneous logic graphs that are suitable for the current design scenario are recommended first. The heterogeneous logic graph is a directed graph used to describe the logical execution flow of page components. Receive the heterogeneous logic diagram corresponding to the user's recommended selection results; The step of calculating the matching degree for each heterogeneous logic diagram in the heterogeneous logic diagram resource library based on the design request parameter set includes: Matching degree = α × event tag similarity + β × component type similarity + γ × historical usage frequency normalized value matching degree; α, β, and γ are weight coefficients, satisfying α + β + γ = 1; where: Event tag similarity: Compare the event type parameters in the design request parameter set with the event tags in the heterogeneous logic diagram. When there is a complete match, the event tag similarity is 1; when there is a partial match, the event tag similarity is 0.5; and when there is no match, the event tag similarity is 0. Component type similarity: Compare the component type parameters in the design request parameter set with the component tags in the heterogeneous logic diagram. When there is a complete match, the component tag similarity is 1; when there is a partial match, the component tag similarity is 0.5; and when there is no match, the component tag similarity is 0. Historical usage frequency normalization value: corresponds to the percentage of the heterogeneous logic graph used in historical recommendations, representing the universality and priority of the heterogeneous logic graph.

2. The heterogeneous logic graph reasoning method according to claim 1, characterized in that: The page component types include drop-down lists, tables, trees, and forms, and the event types include page initialization, single click, double click, and refresh.

3. The heterogeneous logic graph reasoning method according to claim 1, characterized in that: The elements of the heterogeneous logic diagram include: Node information elements: node type, execution content; Connection information elements: the execution order and dependencies between nodes; Tag information elements: Adapted event tags and component type tags.

4. The heterogeneous logic graph reasoning method according to claim 3, characterized in that: In the node information element, the node type includes: Page logic flow nodes include a series of actions such as user interaction, data request, data processing, page rendering, and event response, and are bound to front-end JS operations and back-end interactive logic flow; The middle platform service nodes extract common capabilities from services to form standardized, modular, and reusable services, which can be flexibly called by multiple front-end applications; the common capabilities include data processing, business processes, and general services. A service node is a set of independently deployable and invoked software functional units encapsulated to fulfill a specific functional requirement. It can interact with other systems or other modules through API interfaces. In a database, an entity node is mapped to a table, and the entity's attributes are mapped to the table's columns. The executed content includes: SQL statements, API addresses, and JS function names.

5. The heterogeneous logic graph reasoning method according to claim 1, characterized in that: The heterogeneous logic graph resource library includes: a unique graph number, a graph name, an adaptation tag, a graph structure, and a usage frequency; the adaptation tag includes event tags and component tags, the graph structure includes nodes and connections, and the usage frequency is dynamically updated.

6. The heterogeneous logic graph reasoning method according to claim 1, characterized in that: The method further includes: Receive user edits and modifications to the heterogeneous logic diagram corresponding to the recommended selection results; Save the modified heterogeneous logic diagram to the heterogeneous logic diagram resource library.

7. The heterogeneous logic graph reasoning method according to claim 6, characterized in that: The editing modifications include: Adding nodes: This includes adding new API data sources and adding new data rendering methods; Delete node: Delete invalid or redundant steps; Modify nodes: Adjust parameters including SQL statements, API addresses, and JS rendering functions; Connection adjustment: Modify the execution order and dependencies between nodes.

8. An electronic device comprising a storage unit and a processing unit, wherein the storage unit stores computer instructions executable on the processing unit, characterized in that: When the processing unit executes the computer instructions, it performs the steps of a heterogeneous logic graph reasoning method as described in any one of claims 1 to 7.

9. A storage medium storing computer instructions thereon, characterized in that: When the computer instructions are executed, they perform the steps of a heterogeneous logic graph reasoning method as described in any one of claims 1 to 7.

Images