Module interaction method, device and equipment and readable storage medium

Abstract

The invention relates to a module interaction method and device, equipment and a readable storage medium. The method is applied to a first module, and comprises the following steps: when a module interaction demand is triggered, accessing a preset interaction storage space, obtaining a target storage item, and then interacting with a second module through a target application program interface according to the target storage item. Wherein the target storage item corresponds to a target application program interface of the second module, and each storage item included in the preset interaction storage space corresponds to each application program interface of the second module. By adopting the method, when the second module needs to be updated and maintained, only the storage items corresponding to the application program interfaces of the second module in the preset interactive storage space need to be updated and maintained, and the first module does not need to be updated, so that the updating efficiency of the whole system is improved.

Description

Technical Field

[0001] The present application relates to the field of computer software technology, and in particular to a module interaction method, device, equipment and readable storage medium. Background Art

[0002] In a computer software system, there are usually multiple functional modules, and there are often a large number of logical interaction requirements between different functional modules.

[0003] At present, the interaction between different functional modules is mainly achieved by calling the application program interface provided by the functional module. For example, module A interacts with module B by directly calling the application program interface of module B. In this interaction mode, when a functional module needs to be updated or maintained during the operation of the software system, the functional module that interacts with it also needs to be updated, resulting in low update efficiency of the entire software system. Summary of the invention

[0004] Based on this, it is necessary to provide a module interaction method, device, equipment and readable storage medium that can improve the update efficiency of the software system in response to the above technical problems.

[0005] In a first aspect, the present application provides a module interaction method, which is applied to a first module and includes:

[0006] When the module interaction requirement is triggered, the preset interaction storage space is accessed to obtain the target storage item; the target storage item corresponds to the target application program interface of the second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module;

[0007] According to the target storage item, interact with the second module through the target application program interface.

[0008] In this embodiment, when the module interaction demand is triggered, the preset interactive storage space is accessed to obtain the target storage item, and then, according to the target storage item, the second module is interacted with through the target application interface. Among them, the target storage item corresponds to the target application interface of the second module, and each storage item included in the preset interactive storage space corresponds to each application interface of the second module. In this way, the first module interacts with the second module by accessing the target storage item in the preset interactive storage space, without directly interacting with the second module. When the second module needs to be updated and maintained, it only needs to update and maintain the storage items corresponding to each application interface of the second module in the preset interactive storage space, and the first module does not need to be updated, thereby improving the update efficiency of the entire system.

[0009] In one embodiment, the interacting with the second module through the target application program interface according to the target storage item includes:

[0010] Determining address information of the target application program interface according to the target storage item;

[0011] According to the address information, interact with the second module through the target application program interface.

[0012] In this embodiment, the address information of the target application program interface is determined through the target storage item, and then the target application program interface can be called through the address information, thereby realizing the interaction between the first module and the second module.

[0013] In one embodiment, obtaining the target storage item includes:

[0014] Matching the target application program interface with each storage item in the preset interactive storage space according to the target application program interface identifier; the storage item includes the identifier of the corresponding application program interface;

[0015] The storage item that is successfully matched is determined as the target storage item.

[0016] In this embodiment, the first module accesses the preset interactive storage space by subscription, and determines the target storage item by matching with each storage item in the storage necklace table.

[0017] In one embodiment, accessing a preset interaction storage space includes:

[0018] Calling an interactive registration file, and determining an access address of the preset interactive storage space according to the interactive registration file;

[0019] The preset interactive storage space is accessed according to the access address.

[0020] In this embodiment, by defining a preset interactive storage space, then calling the interactive registration file, and determining the access address of the preset interactive storage space, access to the preset interactive storage space can be achieved. The preset interactive storage space is independent of each module, thereby achieving decoupling between modules. When each module needs to be modified and maintained, it will not affect other modules, thereby improving the flexibility and scalability of the software system.

[0021] In a second aspect, the present application provides a module interaction method, which is applied to a second module and includes:

[0022] According to all the application program interfaces on the second module, generate storage items corresponding to the application program interfaces;

[0023] The storage items corresponding to each of the application program interfaces are published to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage items by accessing the preset interactive storage space when the module interaction requirement is triggered, and to interact with the second module through the target storage items.

[0024] In this embodiment, the second module generates a corresponding storage item for the external application program interface and publishes it to the preset interactive storage space for the first module to call. Each application program interface is stored in an independent storage item, thereby achieving the decoupling of the interaction between the first module and the second module. If an application program interface of the second module is updated and maintained, the first module does not need to be updated or recompiled, and the update efficiency is higher.

[0025] In one embodiment, the method further comprises:

[0026] Processing the target application program interface on the second module; the processing includes at least one of adding, modifying or deleting;

[0027] According to all the processed application program interfaces on the second module, each storage item in the preset interactive storage space is updated.

[0028] In this embodiment, when the target application interface in the second module is processed, it is only necessary to recompile the processed second module, and generate storage items according to each application interface and publish them to the preset interactive storage space. The first module does not need to be recompiled, thereby achieving decoupling of the codes between the modules.

[0029] In a third aspect, the present application further provides a module interaction device, which is applied to a first module and includes:

[0030] An acquisition module, used to access a preset interaction storage space and acquire a target storage item when a module interaction requirement is triggered; the target storage item corresponds to a target application program interface of the second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module;

[0031] An interaction module is used to interact with the second module through the target application program interface according to the target storage item.

[0032] In a fourth aspect, the present application further provides a module interaction device, which is applied to the second module and includes:

[0033] A generating module, used for generating storage items corresponding to each of the application program interfaces according to all the application program interfaces on the second module;

[0034] A publishing module is used to publish the storage items corresponding to each of the application program interfaces to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage items by accessing the preset interactive storage space when the module interaction demand is triggered, and to interact with the second module through the target storage items.

[0035] In a fifth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the module interaction method described in any one of the first aspect or the second aspect is implemented.

[0036] In a sixth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the module interaction method described in any one of the first aspect or the second aspect is implemented.

[0037] In a seventh aspect, the present application further provides a computer program product, comprising a computer program, which, when executed by a processor, implements the module interaction method described in any one of the first aspect or the second aspect.

[0038] The above-mentioned module interaction method, device, equipment and readable storage medium, the method is applied to the first module, including: when the module interaction demand is triggered, access the preset interaction storage space, obtain the target storage item, and then interact with the second module through the target application interface according to the target storage item. Among them, the target storage item corresponds to the target application interface of the second module, and each storage item included in the preset interaction storage space corresponds to each application interface of the second module. In this way, the first module can interact with the second module by accessing the target storage item in the preset interaction storage space without directly interacting with the second module. When the second module needs to be updated and maintained, it only needs to update and maintain the storage items corresponding to each application interface of the second module in the preset interaction storage space, and the first module does not need to be updated, thereby improving the update efficiency of the entire system. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0040] FIG1 is a schematic diagram of the structure of an existing module interaction method in one embodiment;

[0041] FIG2 is a schematic diagram of an application environment of a module interaction method in one embodiment;

[0042] FIG3 is a schematic diagram of a flow chart of a module interaction method in one embodiment;

[0043] FIG4 is a schematic flow chart of a module interaction method in another embodiment;

[0044] FIG5 is a schematic flow chart of a target storage item determination step in another embodiment;

[0045] FIG6 is a schematic flow chart of a preset interactive storage space access step in another embodiment;

[0046] FIG7 is a schematic diagram of the structure of a preset interactive storage space in one embodiment;

[0047] FIG8 is a schematic diagram of a process of storing item publishing steps in another embodiment;

[0048] FIG9 is a schematic diagram of a process of a storage item update step in another embodiment;

[0049] FIG10 is a schematic diagram of a flow chart of a module interaction method in another embodiment;

[0050] FIG11 is a structural block diagram of a module interaction device in one embodiment;

[0051] FIG12 is a structural block diagram of a module interaction device in another embodiment;

[0052] FIG. 13 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0053] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0054] At present, the process of interaction between different functional modules in a computer software system is mainly realized by calling the application program interface provided by the functional module. For example, see the module interaction structure diagram shown in Figure 1, in which module B realizes the interaction with module A by directly calling the application program interface of module A. In this interaction mode, when the software system is running, if module A needs to be updated or maintained, the functional modules interacting with it, such as module B, also need to be updated, resulting in low update efficiency of the entire software system. At the same time, all modules need to be initialized in sequence when the software system starts, so the startup process is long and the startup efficiency is low.

[0055] In view of this, the present application provides a module interaction method, whereby a first module can interact with a second module by accessing a target storage item in a preset interactive storage space without directly interacting with the second module; when the second module needs to be updated and maintained, only the storage items corresponding to the application program interfaces of the second module in the preset interactive storage space need to be updated and maintained, and the first module does not need to be updated, thereby improving the update efficiency of the entire system.

[0056] The application environment of the module interaction method provided in the present application is shown in the module interaction structure diagram shown in Figure 2, wherein module B interacts with module A through a preset interaction storage space.

[0057] In an exemplary embodiment, as shown in FIG3 , a module interaction method is provided, which is applied to the B module in FIG2 (corresponding to the first module in all the following embodiments, and the second module corresponds to the A module in FIG2 ), and the steps of the module interaction method include:

[0058] Step 301, when a module interaction requirement is triggered, access a preset interaction storage space to obtain a target storage item.

[0059] Among them, the target storage item corresponds to the target application interface of the second module, and each storage item included in the preset interactive storage space corresponds to each application interface of the second module. The target application interface can be the application interface that the first module needs to access when the module interaction demand is triggered. When the module interaction demand is triggered, that is, when the first module needs to interact with the second module, for example, the first module needs to call the target application interface in the second module to implement some functions. Optionally, the first module may be a module that needs to call the application interface of other modules, and does not specifically refer to a certain module. The second module may be a module that contains the application interface to be called by other modules, and does not specifically refer to a certain module. Module interaction requirements include any of the following requirements: call requests between modules, data processing requests between modules such as data read requests or data write requests, information transmission requests between modules, etc.

[0060] Optionally, the first module and the second module can be a terminal or a server, or a system including a terminal and a server, and the above module interaction method is implemented through the interaction between the terminal and the server. Optionally, the first module and the second module can also be functional modules in a software system; optionally, the first module and the second module can also be code modules in a software system. The following description takes the first module and the second module as functional modules or code modules in a software system as an example.

[0061] Optionally, if the first module directly calls the application program interface of the second module, when the second module needs to be updated and maintained, the first module also needs to be updated. Therefore, in order to decouple the first module and the second module, the first module interacts with the second module by accessing a preset interactive storage space. The preset interactive storage space can be a predefined storage space independent of the first module and the second module. Optionally, the preset interactive storage space includes multiple storage items, each storage item corresponds one-to-one to each application program interface of the second module, and each storage item is stored in the preset interactive storage space in the form of a linked list. Therefore, after obtaining the target storage item, the target application program interface corresponding to the target storage item can be called.

[0062] In an embodiment of the present application, when a module interaction demand is triggered, for example, when the first module receives a call or data processing request from other functional modules in the device, or for another example, when the first module receives a data processing request sent by a client outside the device, it is directed to the preset interactive storage space to search for the required storage item, that is, the target storage item. The specific search process may be: traversing all storage items in the preset interactive storage space in turn to search for the target storage item, or searching for the target storage item by matching the storage item type.

[0063] Step 302: interact with the second module through the target application program interface according to the target storage item.

[0064] Optionally, the target storage item may include interface information of the target application program interface, and the first module can call the target application program interface of the second module through the interface information in the target storage item to interact with the second module. The preset interactive storage space may also include storage items corresponding to the application program interfaces of other modules, and the first module can interact with other modules by determining the storage items corresponding to the application program interfaces in other modules that need to be called.

[0065] In an embodiment of the present application, after obtaining the target storage item, the first module may call the target application interface based on the interface information of the target application interface stored in the target storage item, for example, the interface information includes address information, and the first module may call the target application interface based on the address information of the target application. For example, the interface information may include name information, and the first module may call the target application interface based on the name of the target application to achieve interaction with the second module.

[0066] In the above embodiment, when the module interaction demand is triggered, the preset interactive storage space is accessed to obtain the target storage item, and then, according to the target storage item, the second module is interacted with through the target application interface. Among them, the target storage item corresponds to the target application interface of the second module, and each storage item included in the preset interactive storage space corresponds to each application interface of the second module. In this way, the first module interacts with the second module by accessing the target storage item in the preset interactive storage space, without directly interacting with the second module. When the second module needs to be updated and maintained, it only needs to update and maintain the storage items corresponding to each application interface of the second module in the preset interactive storage space, and the first module does not need to be updated, thereby improving the update efficiency of the entire system.

[0067] In one embodiment, the interaction process between the above step 302 and the second module is shown in FIG4 , and includes:

[0068] Step 401, determining address information of a target application program interface according to a target storage item.

[0069] Optionally, the storage item may be a structure data, which may include the address information of the application program interface, and the address information may be a function pointer of the application program interface, through which the address of the application program interface may be determined, thereby implementing the call to the application program interface. The storage item may also include metadata information of the application program interface, such as type information of the application program interface, identification information of the application program interface, keyword information of the application program interface, or parameter information of the application program interface.

[0070] Step 402: interact with the second module through the target application program interface according to the address information.

[0071] According to the address information of the target application program interface obtained from the target storage item, the first module can determine the address of the target application program interface through the address information, thereby directing the target application program interface in the second module to call and realize interaction with the second module.

[0072] In the above embodiment, the address information of the target application program interface is determined through the target storage item, and then the target application program interface can be called through the address information, thereby realizing the interaction between the first module and the second module.

[0073] In an optional embodiment of the present application, the first module may access the preset interactive storage space to obtain the target storage item by subscription, as shown in FIG5 , including:

[0074] Step 501, matching the target application program interface identifier with each storage item in the preset interactive storage space.

[0075] Among them, the storage item includes the identifier of the corresponding application program interface. Optionally, the identifier of the application program interface can be the function name of the application program interface, and the identifier of the application program interface in the software system is unique. The first module interacts with other modules by subscription, and the preset interactive storage space can include storage items published by other modules stored in the form of linked lists. The first module traverses the storage necklace table in the preset interactive storage space, matches the identifier of the target application program interface to be called with the identifier of the application program interface corresponding to each storage item one by one, and determines whether it is the storage item to be found.

[0076] Step 502: determine the successfully matched storage item as the target storage item.

[0077] If the identifier of the target API matches the identifier of the API in the storage item, the storage item is determined to be the target storage item, that is, the storage item corresponding to the target API to be called by the first module. The first module can call the target API according to the target storage item.

[0078] In the above embodiment, the first module accesses the preset interactive storage space by subscription, and determines the target storage item by matching with each storage item in the storage necklace table.

[0079] Optionally, before the first module accesses the preset interaction storage space, as shown in FIG6 , the following steps are included:

[0080] Step 601: call the interactive registration file, and determine the access address of the preset interactive storage space according to the interactive registration file.

[0081] Optionally, in order to enable the first module to access the preset interactive storage space, the first module needs to call an interactive registration file, which may be a file containing information about the preset interactive storage space. The interactive registration file is called in the first module, so that the access address of the preset interactive storage space can be determined, which is the specific address of the preset interactive storage space in the memory or code storage space.

[0082] In an embodiment of the present application, the preset interactive storage space may include three custom program segments, as shown in FIG7 , including SECTION_H, SECTION and SECTION_T, wherein SECTION_H is used to identify the starting position of the storage necklace table in the preset interactive storage space, and will be automatically registered in the module that calls the interactive registration file. The interactive storage segment with SECTION as the core is used to store the storage items published by each module in the form of a linked list. SECTION_T is used to identify the end position of the storage necklace table in the preset interactive storage space, and will be automatically registered in the module that calls the interactive registration file. The SECTION segment can be an independent program segment, which is independent of each module that needs to interact, and is convenient for memory management. By subscribing to the preset interactive storage space, module B can access the storage items published by module A and realize module interaction with module A.

[0083] Step 602: Access a preset interactive storage space according to the access address.

[0084] Optionally, after determining the access address, the first module may access a preset interactive storage space according to the access address, and match the target application program interface identifier with each storage item stored in the SECTION segment to further determine the target storage item.

[0085] In the above embodiment, by defining a preset interactive storage space, then calling the interactive registration file, and determining the access address of the preset interactive storage space, access to the preset interactive storage space can be achieved. The preset interactive storage space is independent of each module, thereby achieving decoupling between the modules. When each module needs to be modified and maintained, it will not affect other modules, thereby improving the flexibility and scalability of the software system.

[0086] In an exemplary embodiment, as shown in FIG8 , a module interaction method is provided, which is applied to the second module and includes the following steps:

[0087] Step 801: Generate storage items corresponding to each application program interface according to all application program interfaces on the second module.

[0088] In order for other modules to call the application program interface of the second module, the second module can encapsulate all external application program interfaces into corresponding storage items, for example, encapsulate all external application program interface function pointers and application program interface metadata information into a structure, and encapsulate an application program interface function pointer and metadata information into a structure. Optionally, the metadata information may include application program interface type information, application program interface identification information, application program interface keyword information, or application program interface parameter information, etc. Take a structure as a storage item, and obtain multiple storage items corresponding to multiple application program interfaces, that is, each application program interface is stored in an independent storage item.

[0089] Step 802: Publish the storage items corresponding to each application program interface to the preset interactive storage space.

[0090] The preset interactive storage space is used for the first module to obtain a target storage item by accessing the preset interactive storage space when a module interaction requirement is triggered, and to interact with the second module through the target storage item.

[0091] Optionally, the second module publishes the storage items corresponding to each generated application program interface to a preset interactive storage space, which can be easily called by the first module.

[0092] In the above embodiment, the second module generates a corresponding storage item for the external application program interface and publishes it to the preset interactive storage space for the first module to call. Each application program interface is stored in an independent storage item, thereby realizing the decoupling of the interaction between the first module and the second module. If an application program interface of the second module is updated and maintained, the first module does not need to be updated and recompiled, and the update efficiency is higher.

[0093] In an embodiment of the present application, as shown in FIG9 , the method further includes:

[0094] Step 901, processing the target application program interface on the second module.

[0095] The processing includes at least one of adding, modifying or deleting.

[0096] Step 902: Update each storage item in the preset interactive storage space according to all the processed application program interfaces on the second module.

[0097] Optionally, if a new target application interface is added, the second module is recompiled, and the target storage items corresponding to the target application interface are generated, and the storage items generated by the second module are published to the preset interactive storage space. If the target application interface is modified, the second module is recompiled after the target application interface is modified, and then the storage items are generated according to all the current external application interfaces of the second module, and published to the preset interactive storage center. If the target application interface is deleted, the second module is recompiled after the target application is deleted, and then the storage items are generated according to all the current external application interfaces of the second module, and published to the preset interactive storage center.

[0098] In the above embodiment, when the target application interface in the second module is processed, it is only necessary to recompile the processed second module, and generate storage items according to each application interface and publish them to the preset interactive storage space. The first module does not need to be recompiled, thereby achieving decoupling of the codes between the modules.

[0099] In an embodiment of the present application, please refer to FIG. 10 , which shows a flow chart of a module interaction method provided in an embodiment of the present application. The module interaction method includes the following steps:

[0100] Step 1001: The second module generates storage items corresponding to each application program interface according to all application program interfaces on the second module.

[0101] Step 1002: The second module publishes the storage items corresponding to each application program interface to a preset interactive storage space.

[0102] Step 1003: When a module interaction requirement is triggered, the first module accesses a preset interaction storage space.

[0103] Step 1004: The first module matches the target application program interface identifier with each storage item in the preset interactive storage space.

[0104] Step 1005: The first module determines the successfully matched storage item as the target storage item.

[0105] Step 1006: The first module determines address information of the target application program interface according to the target storage item.

[0106] Step 1007: The first module interacts with the second module through the target application program interface according to the address information.

[0107] In the above embodiment, the first module and the second module can realize the interaction between modules by publishing the storage items to the preset storage space and subscribing to the preset storage space. The first module and the second module are decoupled by the preset interactive storage space, and the module interaction method is more flexible.

[0108] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0109] Based on the same inventive concept, the embodiment of the present application also provides a module interaction device for implementing the module interaction method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in one or more module interaction device embodiments provided below can refer to the limitations on the module interaction method above, and will not be repeated here.

[0110] In an exemplary embodiment, as shown in FIG. 11 , a module interaction device 1100 is provided, which is applied to a first module and includes: an acquisition module 1101 and an interaction module 1102, wherein:

[0111] The acquisition module 1101 is used to access the preset interaction storage space and acquire the target storage item when the module interaction requirement is triggered; the target storage item corresponds to the target application program interface of the second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module;

[0112] The interaction module 1102 is used to interact with the second module through the target application program interface according to the target storage item.

[0113] In one embodiment, the interaction module 1102 is specifically configured to determine address information of the target application program interface according to the target storage item; and interact with the second module through the target application program interface according to the address information.

[0114] In one embodiment, the acquisition module 1101 is specifically used to match each storage item in the preset interactive storage space according to the identifier of the target application interface; the storage item includes the identifier of the corresponding application interface; and the storage item that is successfully matched is determined as the target storage item.

[0115] In one embodiment, the acquisition module 1101 is specifically used to call the interaction registration file, and determine the access address of the preset interaction storage space according to the interaction registration file; and access the preset interaction storage space according to the access address.

[0116] Each module in the above module interaction device can be implemented in whole or in part by software, hardware and a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0117] In an exemplary embodiment, as shown in FIG. 12 , a module interaction device 1200 is provided, which is applied to a first module and includes: a generation module 1201 and a publishing module 1202, wherein:

[0118] A generating module 1201, configured to generate storage items corresponding to all the application program interfaces on the second module;

[0119] The publishing module 1202 is used to publish the storage items corresponding to each of the application program interfaces to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage items by accessing the preset interactive storage space when the module interaction demand is triggered, and to interact with the second module through the target storage items.

[0120] In one embodiment, an update module is also included for processing the target application interface on the second module; the processing includes at least one of adding, modifying or deleting; and based on all the application interfaces on the second module after processing, each storage item in the preset interactive storage space is updated.

[0121] Each module in the above module interaction device can be implemented in whole or in part by software, hardware and a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0122] In an exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be shown in FIG13. The computer device includes a processor, a memory, an input / output interface, a communication interface, a display unit, and an input device. The processor, the memory, and the input / output interface are connected via a system bus, and the communication interface, the display unit, and the input device are connected to the system bus via the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner may be implemented through WIFI, a mobile cellular network, near field communication (NFC) or other technologies. When the computer program is executed by the processor, a module interaction method is implemented. The display unit of the computer device is used to form a visually visible picture, which may be a display screen, a projection device, or a virtual reality imaging device. The display screen can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad set on the computer device shell, or an external keyboard, touchpad or mouse.

[0123] Those skilled in the art will understand that the structure shown in FIG. 13 is merely a block diagram of a partial structure related to the scheme of the present application, and does not constitute a limitation on the computer device to which the scheme of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different arrangement of components.

[0124] In an exemplary embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the following steps when executing the computer program: when a module interaction requirement is triggered, access a preset interaction storage space to obtain a target storage item; the target storage item corresponds to a target application program interface of a second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module; and according to the target storage item, interact with the second module through the target application program interface.

[0125] In one embodiment, when the processor executes the computer program, the following steps are also implemented: according to the target storage item, the address information of the target application program interface is determined; according to the address information, the second module is interacted with through the target application program interface.

[0126] In one embodiment, when the processor executes the computer program, the following steps are also implemented: matching the target application interface with each storage item in the preset interactive storage space; including the identification of the corresponding application interface in the storage item; and determining the successfully matched storage item as the target storage item.

[0127] In one embodiment, when the processor executes the computer program, the following steps are further implemented: calling the interaction registration file, and determining the access address of the preset interaction storage space according to the interaction registration file; and accessing the preset interaction storage space according to the access address.

[0128] In one embodiment, the processor also implements the following steps when executing the computer program: generating storage items corresponding to each application interface based on all application interfaces on the second module; publishing the storage items corresponding to each application interface to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage item by accessing the preset interactive storage space when the module interaction demand is triggered, and interact with the second module through the target storage item.

[0129] In one embodiment, when the processor executes the computer program, it also implements the following steps: processing the target application interface on the second module; the processing includes at least one of adding, modifying or deleting; and updating each storage item in the preset interactive storage space based on all the application interfaces on the second module after processing.

[0130] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: when a module interaction requirement is triggered, a preset interaction storage space is accessed to obtain a target storage item; the target storage item corresponds to a target application program interface of the second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module; and according to the target storage item, interaction is performed with the second module through the target application program interface.

[0131] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: according to the target storage item, address information of the target application program interface is determined; according to the address information, interaction with the second module is performed through the target application program interface.

[0132] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: matching the target application interface identifier with each storage item in the preset interactive storage space; including the identifier of the corresponding application interface in the storage item; and determining the successfully matched storage item as the target storage item.

[0133] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: calling the interaction registration file, and determining the access address of the preset interaction storage space according to the interaction registration file; and accessing the preset interaction storage space according to the access address.

[0134] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: based on all the application program interfaces on the second module, storage items corresponding to each application program interface are generated; the storage items corresponding to each application program interface are published to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage item by accessing the preset interactive storage space when the module interaction demand is triggered, and to interact with the second module through the target storage item.

[0135] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: processing the target application interface on the second module; the processing includes at least one of adding, modifying or deleting; and updating each storage item in the preset interactive storage space based on all the application interfaces on the processed second module.

[0136] In one embodiment, a computer program product is provided, including a computer program, which implements the following steps when executed by a processor: when a module interaction requirement is triggered, access a preset interaction storage space to obtain a target storage item; the target storage item corresponds to a target application program interface of a second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module; and according to the target storage item, interact with the second module through the target application program interface.

[0137] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: according to the target storage item, address information of the target application program interface is determined; according to the address information, interaction with the second module is performed through the target application program interface.

[0138] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: matching the target application interface identifier with each storage item in the preset interactive storage space; including the identifier of the corresponding application interface in the storage item; and determining the successfully matched storage item as the target storage item.

[0139] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: calling the interaction registration file, and determining the access address of the preset interaction storage space according to the interaction registration file; and accessing the preset interaction storage space according to the access address.

[0140] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: based on all the application program interfaces on the second module, storage items corresponding to each application program interface are generated; the storage items corresponding to each application program interface are published to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage item by accessing the preset interactive storage space when the module interaction demand is triggered, and to interact with the second module through the target storage item.

[0141] In one embodiment, when the computer program is executed by the processor, the following steps are also implemented: processing the target application interface on the second module; the processing includes at least one of adding, modifying or deleting; and updating each storage item in the preset interactive storage space based on all the application interfaces on the processed second module.

[0142] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0143] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0144] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A module interaction method, characterized in that: The method is applied to the first module, and the method comprises: When the module interaction requirement is triggered, the preset interaction storage space is accessed to obtain the target storage item; the target storage item corresponds to the target application program interface of the second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module; According to the target storage item, interact with the second module through the target application program interface.

2. The method according to claim 1, characterized in that The interacting with the second module through the target application program interface according to the target storage item includes: Determining address information of the target application program interface according to the target storage item; According to the address information, interact with the second module through the target application program interface.

3. The method according to claim 1 or 2, characterized in that: The obtaining of the target storage item includes: Matching the target application program interface with each storage item in the preset interactive storage space according to the target application program interface identifier; the storage item includes the identifier of the corresponding application program interface; The storage item that is successfully matched is determined as the target storage item.

4. The method according to claim 1 or 2, characterized in that: The accessing the preset interaction storage space includes: Calling an interactive registration file, and determining an access address of the preset interactive storage space according to the interactive registration file; The preset interactive storage space is accessed according to the access address.

5. A module interaction method, characterized in that: The method is applied to the second module, and the method comprises: According to all the application program interfaces on the second module, generate storage items corresponding to the application program interfaces; The storage items corresponding to each of the application program interfaces are published to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage items by accessing the preset interactive storage space when the module interaction requirement is triggered, and to interact with the second module through the target storage items.

6. The method according to claim 5, characterized in that The method further comprises: Processing the target application program interface on the second module; the processing includes at least one of adding, modifying or deleting; According to all the processed application program interfaces on the second module, each storage item in the preset interactive storage space is updated.

7. A module interaction device, characterized in that: The device is applied to a first module, and comprises: An acquisition module, used to access a preset interaction storage space and acquire a target storage item when a module interaction requirement is triggered; the target storage item corresponds to a target application program interface of the second module; each storage item included in the preset interaction storage space corresponds to each application program interface of the second module; An interaction module is used to interact with the second module through the target application program interface according to the target storage item.

8. A module interaction device, characterized in that: The device is applied to the second module, and the device includes: A generating module, used for generating storage items corresponding to each of the application program interfaces according to all the application program interfaces on the second module; A publishing module is used to publish the storage items corresponding to each of the application program interfaces to a preset interactive storage space; the preset interactive storage space is used for the first module to obtain the target storage items by accessing the preset interactive storage space when the module interaction demand is triggered, and to interact with the second module through the target storage items.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images