A module linking method, device and medium based on identification resolution
By assigning identification codes and interface definitions to industrial internet modules, user requirements are automatically parsed and module interfaces are adapted, solving the problems of low identification efficiency and unstable links in module connections, and achieving efficient and reliable module integration and business process management.
Patent Information
- Application Number
- CN202511340474.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-09-19
- Publication Date
- 2025-11-28
- Estimated Expiration
- 2045-09-19
AI Technical Summary
In the Industrial Internet, the lack of a unified and standardized identification and coding mechanism in the module linking process leads to low efficiency in module identification and discovery. Existing methods have limited parsing capabilities, making it difficult to support flexible and ever-changing business needs. Furthermore, the linking relationships between modules are unstable, resulting in high implementation costs, long cycles, and poor maintainability.
For each module, an industrial internet identifier code, input interface, and output interface are determined. User requirements are parsed through the identifier code to generate a module identifier sequence. Adaptation is performed according to the interface attributes to establish the link relationship between modules. The circuit breaker module is used to handle potential risks and realize automated adaptation and fault switching.
It achieves intelligent parsing and automated adaptation of module links, reducing development and debugging workload, improving module integration efficiency and system stability, and ensuring the traceability and reliability of business processes.
Smart Images

Figure CN120856758B_ABST
Abstract
Description
TECHNICAL FIELD
[0001] The present application relates to the technical field of digital information transmission, and in particular to a module linking method based on identification analysis, equipment and medium. BACKGROUND
[0002] In the field of industrial internet, a module generally refers to a software and hardware unit with specific functions, which can be independently deployed and reused, such as a data acquisition module, a processing module, a communication module, etc. Module linking refers to connecting and integrating these independent modules according to business logic, realizing the penetration of data flow, control flow or service flow, and thus combining into a complete system that can complete complex tasks. By combining modules with different functions as needed, it can quickly respond to business changes, reduce repeated development, reduce system integration and maintenance costs, and realize efficient collaboration and optimal allocation of resources in industrial applications.
[0003] Currently, in the process of realizing module linking, the following problems exist: first, for different modules, there is a lack of unified standard industrial internet identification coding mechanism, it is difficult to quickly and accurately obtain the input and output interface information and unique identity of the module, resulting in low efficiency of module identification and discovery; second, for the module linking requirements issued by the user, the existing method has limited analysis capability, mainly relying on manual or preset rules for module combination, which is difficult to support flexible and variable business requirements; third, after determining the target modules to be linked, due to the inconsistency of input and output interfaces between modules in terms of data structure, transmission protocol, etc., the system lacks effective automatic adaptation mechanism, it is difficult to establish stable and reliable inter-module linking relationship, and still needs a lot of manual development and conversion work, which has high implementation cost, long cycle and poor maintainability. SUMMARY
[0004] In order to solve the above problems, the present application provides a module linking method based on identification analysis, comprising:
[0005] For each module, determine the module linking information corresponding to the module; wherein the module linking information includes industrial internet identification coding, input interface and output interface;
[0006] Parse the module linking requirements sent by the user to determine the module identification sequence requested by the module linking requirements to link according to the industrial internet identification coding;
[0007] Obtain the target module linking information corresponding to each target module in the module identification sequence, and adapt each target module according to the input and output interfaces in the target module linking information to establish the linking relationship between the target modules.
[0008] In an implementation manner of the present application, the target modules are adapted according to the input interfaces and the output interfaces in the target module linkage information, and specifically comprising:
[0009] According to the module identification sequence, a request linkage order corresponding to the target modules is determined;
[0010] According to the request linkage order, a preceding target module and a following target module existing a linkage relationship in the target modules are determined in sequence;
[0011] According to the target module linkage information, a semantic similarity corresponding to the output interface and the input interface of the preceding target module and the following target module is determined, so as to adapt the target modules.
[0012] In an implementation manner of the present application, the semantic similarity between the input interface and the output interface of the preceding target module and the following target module is determined, so as to adapt the target modules, and specifically comprising:
[0013] The semantic similarity between the output interface of the preceding target module and the input interface of the following target module is calculated;
[0014] In the case that the semantic similarity is greater than a preset similarity, it is determined whether the output data type of the output interface and the input data type corresponding to the input interface are the same;
[0015] If yes, it is determined that the preceding target module and the following target module are adapted;
[0016] If no, the output data type of the output interface is converted into the input data type, so that the preceding target module and the following target module can be adapted.
[0017] In an implementation manner of the present application, before the linkage relationship between the target modules is established, the method further comprises:
[0018] Based on the module dependency relationship between the target modules, a risk value corresponding to a business process to which the target modules belong is determined;
[0019] In the case that the risk value is greater than a preset risk threshold, a risk target module in the business process is identified, and a fuse module is added in front of the risk target module, so as to realize the request cut-off of the risk target module through the fuse module.
[0020] In an implementation manner of the present application, based on the module dependency relationship between the target modules, a risk value corresponding to a business process to which the target modules belong is determined, and specifically comprising:
[0021] determine whether there is a circular dependency and a resource conflict between the target modules based on a module dependency relationship between the target modules, and if so, determine a number of loops and a conflict probability corresponding to the business process;
[0022] determine a historical average delay duration corresponding to a critical path in the business process, and determine a risk value corresponding to the business process to which the target modules belong according to the number of loops, the conflict probability and the historical average delay duration.
[0023] In an implementation manner of the present application, the risk value corresponding to the business process to which the target modules belong is determined according to the number of loops, the conflict probability and the historical average delay duration, and specifically includes:
[0024] determining a loop weight, a resource weight and a delay weight corresponding to the number of loops, the conflict probability and the historical average delay duration respectively;
[0025] performing weighted summation on the number of loops, the conflict probability and the historical average delay duration according to the loop weight, the resource weight and the delay weight to obtain the risk value corresponding to the business process to which the target modules belong.
[0026] In an implementation manner of the present application, before determining the semantic similarity corresponding to the output interface and the input interface corresponding to the front target module and the rear target module, the method further includes:
[0027] determining whether the output interface corresponding to the front target module contains a business process unique identifier;
[0028] if not, refusing to establish a link relationship between the front target module and the rear target module.
[0029] In an implementation manner of the present application, the link relationship between the target modules is established, and specifically includes:
[0030] establishing the link relationship between the target modules and obtaining a real-time module state corresponding to each target module;
[0031] in a case where it is determined according to the real-time module state that the target module is faulty, re-linking the target module, and if the number of retries is greater than a preset number, cutting off a request for the target module through the fuse module and switching a standby module corresponding to the target module for linking.
[0032] An embodiment of the present application provides a module linking device based on identification analysis, and the device includes:
[0033] at least one processor;
[0034] and a memory connected in communication with the at least one processor;
[0035] The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the module linking method based on identification resolution according to any one of the above.
[0036] The embodiment of the present application provides a nonvolatile computer storage medium, which stores computer executable instructions, and the computer executable instructions are configured as follows:
[0037] The module linking method based on identification resolution.
[0038] The module linking method based on identification resolution can bring the following beneficial effects:
[0039] By assigning the industrial internet identification code and the structured interface definition to each module, intelligent analysis of user linking requirements and module identification sequence generation are realized, module linking information is obtained through the module identification code, and then the input interface and the output interface of different target modules are matched according to the module linking information, the interface semantics can be automatically identified, the data format can be adapted and the module can be automatically linked, manual conversion code writing or manual configuration is not needed, and the development and debugging workload in the module integration process is significantly reduced. BRIEF DESCRIPTION OF DRAWINGS
[0040] The accompanying drawings, which are included to provide a further understanding of the application and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:
[0041] Figure 1 A flowchart of the module linking method based on identification resolution provided by the embodiment of the present application is shown in the figure.
[0042] Figure 2 A structural diagram of the module linking device based on identification resolution provided by the embodiment of the present application is shown in the figure. DETAILED DESCRIPTION
[0043] To make the objectives, technical solutions and advantages of the present application clearer, the technical solutions of the present application will be described below in conjunction with specific embodiments of the present application and corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the scope of protection of the present application.
[0044] The technical solutions provided by the embodiments of the present application are described in detail below with reference to the drawings.
[0045] As shown in the figure, the module linking method based on identification analysis provided by the embodiments of the present application comprises the following steps: Figure 1
[0046] S101: For each module, determine the module linking information corresponding to the module; wherein the module linking information comprises an industrial internet identification code, an input interface and an output interface.
[0047] The module linking system based on identification analysis provided by the embodiments of the present application mainly comprises a user interaction layer, a module management and analysis layer and a module execution layer. The user interaction layer is responsible for receiving the user's custom module linking requirements and feeding back the processing results to the user. This layer provides a friendly graphical interface or a simple command line interface to facilitate user operation. The module management and analysis layer is the core of the system, responsible for the management of module identification, identification analysis and the construction and management of module linking. It maintains a module information database, storing the identification, interface specification, function description and other module linking information of all modules. The module execution layer is responsible for the actual execution of the module's function, data transmission and interaction between different modules according to the link established by the module management and analysis layer, and completes the user-specified business process.
[0048] In the industrial internet, in order to realize the flexible construction and efficient collaboration of modular systems, first of all, the module linking information corresponding to each functional module needs to be clearly defined. Module linking information is the core data required in the integration and interoperation process of modules, mainly including industrial internet identification code, input interface and output interface. Among them, the industrial internet identification code is the unique identity of the module in the global scope, usually following international or industry standards, such as the VAA standard based on IPv6. VAA is an identification system authorized or recognized by international organizations and managed and maintained by China Information Technology Institute. Its purpose is to use smart contracts to realize the allocation and generation process of identification, and at the same time, to store data by means of decentralized distributed ledger or blockchain technology, in order to ensure the openness and transparency of information and traceability. The identification code includes the basic information of the module, such as module type, function description, version number, etc., to ensure that the module can be uniquely identified and accurately positioned. The input interface clearly specifies the data type, data structure and transmission protocol of the input data that the module can accept, as well as the traceable unique identifier inherited from the output module, such as a data processing module that may specify to accept JSON format data transmitted through HTTP protocol. The output interface clearly specifies the data type, data structure and transmission method of the module output, and also specifies that the unique identifier for the whole process must be included in the output to ensure the traceability and consistency of data in the cross-module transmission process.
[0049] The process of determining the module link information is essentially the process of standardizing encapsulation and registration of the modules. Before accessing the system, each module needs to register its identification code and interface metadata through the management platform. These information will be stored in the central or distributed module library, forming a module information library that can be dynamically queried and parsed.
[0050] S102: The module link requirement sent by the user is parsed to determine the module identification sequence requested by the module link requirement according to the industrial internet identification code.
[0051] The user inputs the custom module link requirement description through the front-end interactive interface. The description can be a graphical drag-and-drop operation or a text form of module combination instruction. After receiving the module link requirement sent by the user, the system will parse and convert the module link requirement. The core goal is to convert the user requirement into an ordered and executable module identification sequence according to the industrial internet identification code system, thereby providing clear input for subsequent module discovery, interface adaptation and link establishment.
[0052] The module link requirement sent by the user is usually expressed in the form of graphical drag-and-drop combination or natural language text instruction, such as "connect the output of data acquisition module A to data processing module B, and then transmit to visualization module C", which is a text form of module combination instruction. The system identifies each target module and its requested link order in the module link requirement through semantic understanding and structure parsing technology, and then extracts the corresponding industrial internet identification code of each target module. Finally, a structured module identification sequence is generated, which includes the industrial internet identification code of each target module and clearly lists the order of the target modules.
[0053] By automatically parsing the module link requirement, the complexity of manually configuring the module link by the user is significantly reduced, and the link error caused by non-uniform identification or non-existent modules is avoided. At the same time, by converting the vague user requirement into a standardized module identification sequence, a reliable foundation is laid for subsequent implementation of module interface automatic matching and dynamic link between modules, and the efficiency and flexibility of modular system construction are comprehensively improved.
[0054] S103: Obtain the target module link information corresponding to each target module in the module identification sequence, and adapt each target module according to the input interface and output interface in the target module link information to establish the link relationship between the target modules.
[0055] After generating the module identification sequence, the system further acquires target module link information corresponding to each target module in the module identification sequence, and performs automatic adaptation between modules according to the input interface attribute and the output interface attribute defined in the target module link information, to finally establish the link relationship between the target modules and construct the modular system.
[0056] In one embodiment, in the process of interface adaptation according to the target module link information, first, the request link order of each target module is determined according to the module identification sequence, so as to determine the sequence of data flow between modules. Then, each pair of modules with a link relationship is processed in turn according to the request link order, and is identified as a front target module (i.e. data sender) and a rear target module (i.e. data receiver) respectively.
[0057] In order to realize effective linking between modules, the detailed metadata of the output interface of the front target module and the input interface of the rear target module, including field name, data type, semantic description and structure constraint, etc., are further extracted according to the acquired target module link information. By performing semantic similarity calculation on the input interface and the output interface, whether the output content and the input content point to the same entity is determined to judge whether the front and rear adjacent target modules are adapted.
[0058] Specifically, in the module interface adaptation process, the core is to determine the semantic similarity between the output interface of the front target module and the input interface of the rear target module, and to perform corresponding adaptation operations based on the judgment. First, the semantic similarity between the output interface corresponding to the front target module and the input interface corresponding to the rear target module is calculated through a semantic mapping engine. The semantic similarity here refers to the semantic similarity between the output content and the input content of the interface. If the semantic similarity is greater than a preset similarity, it means that the output content of the front target module and the input content of the rear target module are consistent in semantics, for example, the output content of the front target module is customer ID, and the input content of the rear target module is user number, and the semantic similarity of customer ID and user number is high. After judging that the content of the input interface and the output interface has semantic similarity, it is further determined whether the data types are consistent.
[0059] If the output data type is exactly the same as the input data type, it is directly determined that the two modules are adaptable, and a lossless data link relationship between the target modules is established. If the data types are inconsistent, the system will automatically call the built-in type converter to perform format processing, converting the output data type of the output interface to the input data type required by the input interface, to ensure that the data meets the compatibility in the syntax level on the premise of semantic consistency. For example, the output of the pre-target module is in XML format, and the input of the post-target module requires JSON format, so the output content in XML format needs to be automatically converted to JSON format to realize the adaptation between the pre-target module and the post-target module.
[0060] The above module adaptation mechanism based on semantic similarity and data type significantly improves the automation and accuracy of module linking, avoiding false judgment of interface unusable due to literal mismatch, and solving the connection failure problem caused by type incompatibility.
[0061] It should be noted that when a complete modular system is formed by module linking and a business process is executed, each business process has a corresponding business process unique identifier, which is similar to a courier waybill number, used to ensure the traceability and consistency of business data in complex processes. Therefore, before establishing the link relationship between the target modules, it is necessary to determine whether the output interface corresponding to the pre-target module contains the business process unique identifier. If the business process unique identifier does not exist, the system will refuse to establish the link relationship between the current modules, and return an error message to the upper layer, prompting that the interface specification does not meet the traceability requirements. Through the above access control mechanism, it is ensured that all target modules participating in the link have traceability capability from the beginning of the business link construction, ensuring the reliability and maintainability of the industrial internet business link, and laying a necessary foundation for realizing full-process trusted traceability.
[0062] In one embodiment, before establishing the link relationship between the target modules, in order to ensure the stability and reliability of the link, it is necessary to identify and evaluate the potential risks existing in the business process. This process needs to be based on the module dependency relationship between the target modules to systematically analyze the complete business process composed of the target modules and quantify the overall risk value.
[0063] The calculation of the risk value comprehensively considers various factors, including but not limited to: whether there is a ring-shaped dependency between modules, whether there is resource competition (such as concurrent access to the same hardware resource), and the average delay duration in historical execution. The system quantifies the risk degree of the business process to which the target module belongs through a predefined risk calculation model, and obtains the corresponding risk value. If the calculated risk value exceeds the preset risk threshold, the key module that causes high risk, i.e., the risk target module, needs to be further located. In order to avoid the module from causing system avalanche or business death at runtime, instead of directly establishing the original link, a fuse module is automatically added in front of the risk target module. The fuse module will continuously monitor the state of the risk target module, and once an exception such as timeout or error rate soaring is detected, the fuse module will immediately temporarily cut off the subsequent request according to the preset strategy, thereby isolating the fault, preventing the risk from spreading along the call chain, and guaranteeing the overall stability and business continuity of the system.
[0064] In the calculation of the risk value corresponding to the business process, it is necessary to detect whether there is a circular dependency between the target modules, that is, whether there is a ring-shaped call relationship between the modules, for example, A->B->C->A forms a loop. Through loop scanning of the business process by a dependency graph traversal algorithm, the number of loops with the above circular dependency in the business process can be determined. At the same time, the resource conflict between multiple target modules needs to be quantitatively evaluated. By analyzing whether the resource requirements declared by the target modules to be executed in parallel in the same time period overlap, for example, if module A and module B are scheduled to run at the same time and both declare the need to exclusively access the same specific sensor, it is considered that they have a resource competition relationship. In the calculation of the conflict probability of the business process, it is necessary to determine whether the maximum total resource demand peak of the business process exceeds the total amount of corresponding resources currently available to the system. If it exceeds, the conflict probability is 1; if it does not exceed the total amount of resources, the resource adequacy ratio needs to be calculated according to the ratio between the total amount of available resources and the current maximum total resource demand peak. The lower the ratio, the higher the conflict probability. According to the preset mapping relationship between the resource adequacy ratio and the conflict probability, the conflict probability of the business process can be determined. In addition, the system traces back the historical running data to obtain the historical average delay duration of each target module on the critical path of the business process, so as to reflect its timeliness performance in past execution. The critical path refers to the execution sequence with the longest time consumption.
[0065] To comprehensively evaluate the risk of the business process based on the above multi-dimensional factors, weight coefficients corresponding to the number of loops, conflict probability and historical average delay duration need to be determined. The loop weight is used to adjust the contribution degree of the ring dependency to the overall risk, the resource weight represents the risk severity of the resource competition behavior, and the delay weight reflects the sensitivity of the system to the timing performance. Finally, by weighting and summing the number of loops, the conflict probability and the historical average delay duration through the loop weight, the resource weight and the delay weight, the risk value of the business process can be calculated. The risk value comprehensively reflects the health status of the business process in the three key aspects of structural rationality, resource competition and timing performance, and provides a decision basis for whether to introduce a fuse protection mechanism subsequently.
[0066] In an embodiment, in the process of establishing the link relationship between the target modules, the system will monitor the real-time module state of each target module to ensure the stability of the link. The real-time module state information includes the heartbeat signal, response delay, error log, resource utilization and other key operation indicators of the module. When a failure of a certain target module is detected according to the real-time module state monitoring, the link retry mechanism will be automatically triggered, and first attempt to re-establish the link with the target module and perform fault recovery operation.
[0067] If the number of retries exceeds the preset threshold, the module is determined to be in an unusable state. At this time, if the target module has previously set a fuse module, all request traffic sent to the faulty module needs to be immediately cut off through the previously preset fuse module to prevent fault propagation and avoid continuous consumption of system resources, while automatically switching to the standby module corresponding to the target module and re-establishing the link relationship, thereby realizing the rapid and seamless switching of the business. If the target module has not previously set a fuse module, the standby module of the target module can be directly enabled to switch the link. Through the closed-loop control of real-time state monitoring, intelligent retry and fuse switching, the continuous and stable operation of the modular system in the industrial internet environment is effectively guaranteed, the downtime is reduced, and the self-response capability to abnormal conditions is enhanced.
[0068] The above is a method embodiment of the present application. Based on the same idea, some embodiments of the present application also provide a device and a non-volatile computer storage medium corresponding to the above method.
[0069] Figure 2 A structure diagram of a module link device based on identification analysis is provided for the embodiments of the present application. As shown in Figure 2 , it includes:
[0070] at least one processor; and,
[0071] a memory communicatively connected to the at least one processor; wherein,
[0072] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to perform the method of any one of the above.
[0073] The embodiment of the present application provides a non-volatile computer storage medium, which stores computer executable instructions, and the computer executable instructions are configured to:
[0074] The method of any one of the above.
[0075] The embodiments of the present application are described in a progressive manner, and the same and similar parts of the embodiments can be referred to each other, and each embodiment mainly describes the difference from other embodiments. Especially, the device and medium embodiments are basically similar to the method embodiments, so the description is relatively simple, and the related parts can be referred to the part of the method embodiment.
[0076] The device and medium provided by the embodiment of the present application are one-to-one corresponding to the method, so the device and medium also have the similar beneficial technical effects of the method. Since the beneficial technical effects of the method have been described in detail above, the beneficial technical effects of the device and medium will not be described here.
[0077] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system, or a computer program product. Therefore, the present application can adopt a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program codes.
[0078] The present application is described with reference to flowcharts and / or block diagrams of the method, device (system), and computer program product according to the embodiments of the present application. It should be understood that each flow and / or block in the flowcharts and / or block diagrams, and the combination of the flows and / or blocks in the flowcharts and / or block diagrams can be implemented by computer program instructions. These computer program instructions can be provided to a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to produce a machine, so that the instructions executed by the computer or other programmable data processing devices produce a device that implements the functions specified in the flowcharts and / or block diagrams. Figure 1 The device that implements the functions specified in one flow or multiple flows and / or blocks Figure 1 The device that implements the functions specified in one flow or multiple flows and / or blocks
[0079] These computer program instructions can also be stored in a computer- readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instructions which implement the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.
[0080] These computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the Figure 1 function specified in the flow or flows and / or blocks Figure 1 of the block or blocks.
[0081] In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
[0082] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM) or Flash memory, etc. Memory is an example of computer-readable media.
[0083] Computer-readable media includes permanent and non-permanent, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD), or other optical storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to computing devices. According to the definition herein, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.
[0084] It is also to be noted that the terms "comprising", "including", and any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but can also include other elements not expressly listed or inherent to such process, method, article, or apparatus. An element proceeded by "comprises a... " does not, without more constraints, exclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the recited element.
[0085] The above description is only the preferred embodiment of the application, not intended to limit the application. Any modification, equivalent replacement and improvement made within the spirit and principle of the application shall fall within the scope of the claims of the application.
Claims
1. A module linking method based on identification resolution, characterized in that, The method comprises: For each module, determine the module link information corresponding to the module; wherein the module link information comprises an industrial internet identifier code, an input interface and an output interface; Parse the module link demand sent by the user to determine the module identifier sequence requested by the module link demand according to the industrial internet identifier code; Obtain the target module link information corresponding to each target module in the module identifier sequence, and adapt each target module according to the input interface and the output interface in the target module link information to establish the link relationship between the target modules; Adapting each target module according to the input interface and the output interface in the target module link information, specifically comprising: According to the module identifier sequence, determine the request link order corresponding to the target module; According to the request link order, determine the front target module and the rear target module in the target module which exist link relationship in turn; According to the target module link information, determine the semantic similarity corresponding to the output interface and the input interface of the front target module and the rear target module to adapt each target module; Determine the semantic similarity between the input interface and the output interface of the front target module and the rear target module to adapt each target module, specifically comprising: Calculate the semantic similarity between the output interface corresponding to the front target module and the input interface corresponding to the rear target module; the semantic similarity refers to the semantic similarity between the interface output content and the input content; If the semantic similarity is greater than a preset similarity, determine whether the output data type of the output interface and the input data type corresponding to the input interface are the same; If yes, determine that the front target module and the rear target module are adapted; If not, convert the output data type of the output interface into the input data type to enable the front target module and the rear target module to be adapted.
2. The method of claim 1, wherein, Before establishing the link relationship between the target modules, the method further comprises: Based on the module dependency relationship between the target modules, determine the risk value corresponding to the business process to which the target modules belong; If the risk value is greater than a preset risk threshold, identify the risk target module in the business process, and add a fuse module in front of the risk target module to achieve request cutting off of the risk target module through the fuse module.
3. The method of claim 2, wherein, Based on the module dependency relationship between the target modules, determine the risk value corresponding to the business process to which the target modules belong, specifically comprising: Based on the module dependency relationship between the target modules, determine whether there is a circular dependency and a resource conflict between the target modules, if yes, determine the number of loops and the conflict probability corresponding to the business process; Determine the historical average delay duration corresponding to the critical path in the business process, and determine the risk value corresponding to the business process to which the target modules belong according to the number of loops, the conflict probability and the historical average delay duration.
4. The method of claim 3, wherein, According to the loop quantity, the conflict probability and the historical average delay duration, a risk value corresponding to a business process to which the target module belongs is determined, and specifically includes: The loop quantity, the conflict probability and the historical average delay duration are respectively determined to correspond to loop weight, resource weight and delay weight; According to the loop weight, the resource weight and the delay weight, the loop quantity, the conflict probability and the historical average delay duration are weighted and summed to obtain the risk value corresponding to the business process to which the target module belongs.
5. The method of claim 1, wherein, Before determining the semantic similarity corresponding to the output interface and the input interface corresponding to the front target module and the rear target module, the method further includes: Determining whether the output interface corresponding to the front target module contains a business process unique identifier; If not, the linking relationship between the front target module and the rear target module is refused to be established.
6. The method of claim 2, wherein, The linking relationship between the target modules is established, and specifically includes: The linking relationship between the target modules is established, and the real-time module state corresponding to each target module is obtained; In the case that the target module is determined to be faulty according to the real-time module state, the target module is re-linked, and if the number of retries is greater than a preset number, the request of the target module is cut off by the fuse module, and the standby module corresponding to the target module is switched to be linked.
7. A module chaining device based on identification resolution, characterized by, The device includes: At least one processor; And a memory connected in communication with the at least one processor; Wherein, the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute a module linking method based on identification analysis according to any one of claims 1-6.
8. A non-transitory computer storage medium storing computer-executable instructions that, when executed, cause a computer to: The computer executable instructions are set as: A module linking method based on identification analysis according to any one of claims 1-6.
Citation Information
Patent Citations
Test data generation method and device
CN115658485A
BMT-based application module integration and data flow organization control method and system
CN118760512A