Service module sending method and device, electronic equipment and storage medium

By receiving client requests on the server and selecting the target business module based on compatibility information, the omission and timeliness of the compatibility marking of the application module on different clients are solved, ensuring the compatibility and operation efficiency of the business module.

CN119002918APending Publication Date: 2024-11-22BEIJING WODONG TIANJUN INFORMATION TECH CO LTD +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310572012.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-19
Publication Date
2024-11-22

AI Technical Summary

Technical Problem

In the prior art, the compatibility marking of application modules is prone to omissions and timeliness problems, resulting in compatibility problems when running on different clients.

Method used

By receiving the client's module acquisition request on the server, the compatibility information of the service module to be compiled is determined, and the target service module is selected from multiple service modules to be compiled is selected based on the client identification and compatibility information, and the target service module is sent to the client. to ensure compatibility filtering and timeliness.

Benefits of technology

It effectively solves the problems of compatibility marking omissions and timeliness, ensures that business modules can run successfully on different clients, and improves the compatibility and operation efficiency of the application.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119002918A_ABST
    Figure CN119002918A_ABST
Patent Text Reader

Abstract

The invention provides a service module sending method and device, electronic equipment and a storage medium, and is applied to a server, the server comprises compatibility information, the compatibility information is used for describing operation conditions of a to-be-compiled service module on different clients, the method comprises the following steps: receiving a module acquisition request sent by the client, the module acquisition request comprises a client identifier and to-be-compiled module information requested by the client, a plurality of to-be-compiled service modules corresponding to the to-be-compiled module information are determined, a target service module is determined from the plurality of to-be-compiled service modules according to the client identifier and the compatibility information, and the target service module is sent to the client. According to the method and the device, the service module incompatible with the client can be filtered by using the compatibility information, the service module sent to the client can be ensured to run successfully, and the compatibility information is acquired in real time in the filtering process, so that the timeliness when the compatibility analysis is performed on the service module is effectively ensured.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to the field of computer technology, and in particular to a service module sending method, device, electronic device and storage medium. Background Art

[0002] Currently, applications provide services in the form of multiple clients. For different types and versions of clients, a construction method that only writes one set of code is usually adopted to respond to business-side needs. As a result, the compatibility of multiple modules of the same application on different clients varies. It is necessary to mark the compatibility of each module on different clients.

[0003] In the related art, the compatibility of modules is usually marked manually by technical personnel. The development process of multiple modules of an application is not directly related to the filtering process of incompatible modules. When the module is sent down by the server or rendered by the client, the incompatible modules are filtered.

[0004] In this way, manual marking is prone to omissions and timeliness issues such as untimely marking. Summary of the invention

[0005] The present disclosure aims to solve one of the technical problems in the related art at least to some extent.

[0006] To this end, the purpose of the present disclosure is to provide a service module sending method, device, electronic device, storage medium and computer program product.

[0007] The first aspect of the present disclosure provides a method for sending a business module, which is applied to a server, and the server includes: compatibility information, where the compatibility information is used to describe the running status of the business module to be compiled on different clients. The method includes: receiving a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier and the module information to be compiled requested by the client; determining multiple business modules to be compiled corresponding to the module information to be compiled; determining a target business module from the multiple business modules to be compiled according to the client identifier and the compatibility information; and sending the target business module to the client.

[0008] A second aspect of the present disclosure provides a method for acquiring a business module, which is applied to a client and includes: sending a module acquisition request to a server, wherein the module acquisition request includes: a client identifier and information about modules to be compiled requested by the client, and the information about modules to be compiled is used by the server to determine multiple business modules to be compiled corresponding to the information about modules to be compiled; and receiving a target business module sent by the server, wherein the target business module is determined by the server from multiple business modules to be compiled according to the client identifier and compatibility information.

[0009] The third aspect of the present disclosure proposes a compatibility information generation method, which is applied to a third-party device, including: obtaining type information and version information of at least one client; obtaining at least one business logic interface referenced by the business module to be compiled, wherein the business logic interface is used to implement the business logic of the business module to be compiled; generating compatibility information corresponding to the server based on the type information, version information and business logic interface, wherein the compatibility information is used to describe the running status of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client.

[0010] The fourth aspect of the present disclosure proposes a service module sending device, which is applied to a server, and the server includes: compatibility information, which is used to describe the running status of the service module to be compiled on different clients. The device includes: a first transmission module, which is used to receive a module acquisition request sent by the client, wherein the module acquisition request includes: a client identifier and the module information to be compiled requested by the client; a first determination module, which is used to determine multiple service modules to be compiled corresponding to the module information to be compiled; a second determination module, which is used to determine a target service module from multiple service modules to be compiled according to the client identifier and the compatibility information; and a second transmission module, which is used to send the target service module to the client.

[0011] The fifth aspect embodiment of the present disclosure proposes a business module acquisition device, including: a third transmission module, used to send a module acquisition request to a server, wherein the module acquisition request includes: a client identifier, information of the module to be compiled requested by the client, and the information of the module to be compiled is used by the server to determine multiple business modules to be compiled corresponding to the information of the module to be compiled; a fourth transmission module, used to receive a target business module sent by the server, wherein the target business module is determined by the server from multiple business modules to be compiled according to the client identifier and compatibility information.

[0012] The sixth aspect embodiment of the present disclosure proposes a compatibility information generating device, including: a first acquisition module, used to obtain type information and version information of at least one client; a second acquisition module, used to obtain at least one business logic interface referenced by the business module to be compiled, wherein the business logic interface is used to implement the business logic of the business module to be compiled; a generation module, used to generate compatibility information corresponding to the server according to the type information, version information and business logic interface, wherein the compatibility information is used to describe the running status of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client.

[0013] The seventh aspect embodiment of the present disclosure proposes an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the program, it implements the service module sending method proposed in the first aspect embodiment of the present disclosure, or implements the service module receiving method proposed in the second aspect embodiment of the present disclosure, or implements the compatibility information generating method proposed in the third aspect embodiment of the present disclosure.

[0014] The eighth aspect embodiment of the present disclosure proposes a non-temporary computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the service module sending method proposed in the first aspect embodiment of the present disclosure, or implements the service module receiving method proposed in the second aspect embodiment of the present disclosure, or implements the compatibility information generating method proposed in the third aspect embodiment of the present disclosure.

[0015] The ninth aspect embodiment of the present disclosure proposes a computer program product. When the instructions in the computer program product are executed by a processor, the service module sending method proposed in the first aspect embodiment of the present disclosure is executed, or the service module receiving method proposed in the second aspect embodiment of the present disclosure is executed, or the compatibility information generating method proposed in the third aspect embodiment of the present disclosure is executed.

[0016] The business module sending method, device, electronic device, storage medium and computer program product proposed in the embodiments of the present disclosure receive a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier, information of the module to be compiled requested by the client, determine multiple business modules to be compiled corresponding to the information of the module to be compiled, determine a target business module from the multiple business modules to be compiled according to the client identifier and compatibility information, send the target business module to the client, and use the compatibility information to filter out business modules that are incompatible with the client to ensure that the business modules sent to the client can run successfully. Since the compatibility information is obtained in real time during the filtering process, the timeliness of the compatibility analysis of the business modules is effectively guaranteed.

[0017] Additional aspects and advantages of the present disclosure will be given in part in the following description and in part will be obvious from the following description or learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and / or additional aspects and advantages of the present disclosure will become apparent and easily understood from the following description of the embodiments in conjunction with the accompanying drawings, in which:

[0019] Figure 1 It is a flowchart of a service module sending method proposed in an embodiment of the present disclosure;

[0020] Figure 2is a flowchart of a service module sending method proposed in another embodiment of the present disclosure;

[0021] Figure 3 is a flow chart of the server compatibility filtering process in an embodiment of the present disclosure;

[0022] Figure 4 is a flowchart of a method for acquiring a business module proposed in an embodiment of the present disclosure;

[0023] Figure 5 is a flowchart of a compatibility information generation method proposed in an embodiment of the present disclosure;

[0024] Figure 6 is a schematic diagram of the system compilation process in an embodiment of the present disclosure;

[0025] Figure 7 is a schematic diagram of interface references in the disclosed embodiment;

[0026] Figure 8 is a schematic diagram of the system design of the application program in the embodiment of the present disclosure;

[0027] Fig. 9 is a flowchart of a compatibility information generating method proposed in another embodiment of the present disclosure;

[0028] Fig.10 is a structural diagram of a service module sending device proposed in an embodiment of the present disclosure;

[0029] Fig.11 is a structural diagram of a service module sending device proposed in another embodiment of the present disclosure;

[0030] Fig.12 is a structural diagram of a service module acquisition device proposed in an embodiment of the present disclosure;

[0031] Fig.13 is a schematic diagram of the structure of a compatible information generating device proposed in an embodiment of the present disclosure;

[0032] Fig.14 is a schematic diagram of the structure of a compatible information generating device proposed in another embodiment of the present disclosure;

[0033] Fig.15 A block diagram of an exemplary electronic device suitable for implementing embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0034] Embodiments of the present disclosure are described in detail below, examples of which are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present disclosure, and are not to be construed as limitations of the present disclosure. On the contrary, the embodiments of the present disclosure include all changes, modifications, and equivalents that fall within the spirit and connotation of the appended claims.

[0035] Figure 1 It is a flowchart of a service module sending method proposed in an embodiment of the present disclosure.

[0036] It should be noted that the execution subject of the service module sending method of this embodiment is a service module sending device, which can be implemented by software and / or hardware, and can be configured in an electronic device, without limitation.

[0037] The embodiments of the present disclosure may be applied to a server, which includes compatibility information, where the compatibility information is used to describe the running conditions of the to-be-compiled service module on different clients.

[0038] Among them, the server side refers to the server side of the application developed by the developer. The server side stores multiple business modules to be compiled that may be used when the application implements business functions. Each business module to be compiled has corresponding compatibility information, and the compatibility information is used to describe the operation of the business module to be compiled on different clients.

[0039] Among them, the client refers to a program that corresponds to the server and provides local services to customers. It is generally installed on an ordinary client computer, or uses a built-in web browser and needs to cooperate with the server to run. The client can be, for example, an independently installed native application program that can run directly on the current operating system, a small program attached to a specific application, or a web page and website that can be directly accessed without installing a browser, or it can be a user terminal that can be used by any application, without any restriction.

[0040] like Figure 1 As shown, the business module sending method includes:

[0041] S101: receiving a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier and information about a module to be compiled requested by the client.

[0042] The module acquisition request refers to the request information sent by the client to the server for requesting to obtain the business module to be compiled. The module acquisition request includes: the client identifier and the module information to be compiled requested by the client.

[0043] The client identifier refers to a data identifier that can be used to uniquely identify the identity information of the client. The client type and client version number of the client can be obtained based on the client identifier.

[0044] The module information to be compiled refers to data information that can be used to describe the service module requested by the client. The module information to be compiled can be, for example, the module name or module identifier of the service module, and there is no limitation on this.

[0045] In the disclosed embodiment, when the client needs to use the business module to be compiled, the client can generate the module information to be compiled according to the business module to be compiled, and generate the corresponding interface acquisition request according to the module information to be compiled and the client identifier. The data interface request can be used as a module acquisition request, and the module acquisition request is initiated to the server, and then the server can receive the module acquisition request sent by the client.

[0046] S102: Determine a plurality of to-be-compiled service modules corresponding to the to-be-compiled module information.

[0047] Among them, the business module to be compiled refers to the business module that needs to be used when the application runs in the client. A business module to be compiled is an implementation unit of a business function. The multiple business modules to be compiled corresponding to the module information to be compiled are the business modules required by the client for this compilation.

[0048] After receiving the module acquisition request sent by the client, the embodiment of the present disclosure can determine multiple to-be-compiled business modules corresponding to the to-be-compiled module information.

[0049] In the disclosed embodiment, when determining multiple business modules to be compiled corresponding to the information of the module to be compiled, the server can analyze and process the information of the module to be compiled by querying the storage service to obtain a set of all business modules requested by the client, and use the obtained business module set as multiple business modules to be compiled corresponding to the information of the module to be compiled. When developing a business module, the developer can introduce other business modules to combine into a complex business function in addition to the business logic code of the module itself. It can determine all modules referenced by the business module to be compiled to obtain a module set, and then in the system compilation stage, an automated compilation tool (such as webpack) can be used to obtain all business module sets to be compiled from the system code, and the business modules to be compiled in the combination are traversed. The entire code composition of the business module to be compiled can be abstracted as a multi-branch tree. Starting from the root node of the tree, each child node of the tree is traversed. Each time a child node is traversed, the compatibility description DSL content of the child node is attempted to be obtained until the business module to be compiled corresponding to each child node is traversed and processed, and the traversal process is completed. The compatibility description DSL of all business modules to be compiled is used as compatibility information to generate compatibility information corresponding to each business model module to be compiled, and the compatibility information is saved to the server.

[0050] S103: Determine a target service module from a plurality of service modules to be compiled according to the client identifier and the compatibility information.

[0051] The target business module refers to a business module obtained by the server after compatibility filtering multiple business modules to be compiled requested by the client according to the client identifier and compatibility information. The target business module can be compatible and run on the corresponding client.

[0052] After receiving the module acquisition request sent by the client and determining multiple to-be-compiled business modules corresponding to the to-be-compiled module information, the disclosed embodiment can determine the target business module from the multiple to-be-compiled business modules according to the client identifier and the compatibility information.

[0053] In the disclosed embodiment, when determining a target business module from a plurality of business modules to be compiled based on a client identifier and compatibility information, the server may traverse the plurality of business modules to be compiled, and obtain the client type and corresponding version information of the client from a request header or request parameters of a received module acquisition request, determine whether the currently traversed business module to be compiled can be run in the client based on the client type and corresponding version information of the client, and the compatibility information of the business modules to be compiled stored in the server, and obtain a corresponding judgment result, perform judgment processing on each business module to be compiled one by one to obtain a judgment result corresponding to each business module to be compiled, and use the business module to be compiled for which the judgment result is that it can be run as the target business module, so as to determine the target business module from the plurality of business modules to be compiled based on the client identifier and the compatibility information.

[0054] Optionally, in some embodiments, when determining a target business module from multiple business modules to be compiled based on the client identification and compatibility information, the type information and version information of the client can be determined based on the client identification, and the target business module can be determined from the multiple business modules to be compiled based on the type information, version information, and compatibility information. Therefore, based on the type information and version information of the client and the compatibility information of the business modules to be compiled, a traversal analysis process can be performed to determine whether the business modules to be compiled can be compatible and run on the client, so as to obtain the business modules to be compiled that can run on the client as the target business modules, thereby achieving effective filtering processing of the compatibility of the business modules, and ensuring that the business modules received by the client can be compiled and run smoothly.

[0055] Among them, type information refers to data information that can describe the type of the client. The type of the client can be, for example, an independently installed native application that can run directly on the current operating system, a small program attached to a specific application, or a web page and website that can be run by a browser that can be directly accessed without installation, etc., or it can be a client type that can be run by any application, and there is no restriction on this.

[0056] In the embodiment of the present disclosure, when determining a target business module from multiple business modules to be compiled based on a client identifier and compatibility information, the client identifier may be first analyzed to determine the client type of the client to generate type information, determine the version of the client as version information, and perform a judgment process on whether multiple business modules to be compiled are compatible on the client based on the type information, version information, and compatibility information corresponding to the business modules to be compiled, so as to determine the target business module from the multiple business modules to be compiled, and obtain the compatibility description information (Domain Specific Description) of the currently traversed business module to be compiled from the compatibility information stored on the server. Language, DSL), and judge whether the client type of the client exists in the compatibility description DSL of the currently traversed business module to be compiled according to the type information of the client. If not, the business module to be compiled is not the target business module. If it exists, continue to judge whether the client version belongs to the range of values ​​corresponding to the key value of the corresponding end in the compatibility description DSL of the currently traversed business module to be compiled according to the version information of the client, wherein the key of the corresponding end in the compatibility description DSL is the client identifier, and the value corresponding to the key-value pair can be a Boolean type or an array. The Boolean type represents all version numbers corresponding to the client, which are all supported or not supported to run. Each item in the array type is an expression of a string type, and the expression represents a specific supported client version, which can be a specific version or a version range interval. If it belongs to the range of values ​​corresponding to the key value of the corresponding end in the compatibility description DSL, the business module to be compiled can be used as the target business module. If it does not belong to the range of values ​​corresponding to the key value of the corresponding end in the compatibility description DSL, the business module to be compiled is not the target business module. The above judgment process is performed on each business module to be compiled one by one to obtain the target business module among the multiple business modules to be compiled.

[0057] S104: Send the target service module to the client.

[0058] In the embodiment of the present disclosure, after determining the target service module from the multiple service modules to be compiled according to the client identifier and the compatibility information, the target service module can be sent to the client of the transmission module acquisition request.

[0059] In this embodiment, by receiving a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier, information of the module to be compiled requested by the client, a plurality of business modules to be compiled corresponding to the information of the module to be compiled are determined, a target business module is determined from the plurality of business modules to be compiled according to the client identifier and the compatibility information, and the target business module is sent to the client. The compatibility information can be used to filter out the business modules incompatible with the client, thereby ensuring that the business modules sent to the client can run successfully. Since the compatibility information is obtained in real time during the filtering process, the timeliness of the compatibility analysis of the business modules is effectively guaranteed.

[0060] Figure 2 It is a flowchart of a service module sending method proposed in another embodiment of the present disclosure.

[0061] The embodiments of the present disclosure may be applied to a server. For the description of the server, reference may be made to the above embodiments, which will not be repeated here.

[0062] like Figure 2 As shown, the business module sending method includes:

[0063] S201: receiving a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier and information about a module to be compiled requested by the client.

[0064] S202: Determine a plurality of to-be-compiled service modules corresponding to the to-be-compiled module information.

[0065] S203: Determine the type information and version information of the client according to the client identifier.

[0066] For the description of S201 to S203 , please refer to the above embodiments, which will not be repeated here.

[0067] S204: Determine whether each to-be-compiled service module can be run on the client according to the type information and the compatibility information, and obtain a first determination result.

[0068] The first determination result refers to data information that can describe whether all the to-be-compiled service modules requested by the client can be run on the client.

[0069] In the embodiment of the present disclosure, when determining whether each to-be-compiled business module can run on the client based on the type information and the compatibility information and obtaining a first determination result, the compatibility description DSL corresponding to each to-be-compiled business module can be first determined from the compatibility information, and then, based on the type information of the client, it is determined whether the client has the compatibility description DSL corresponding to the to-be-compiled business module. If so, it indicates that the to-be-compiled business module can run on the client of the corresponding type. If not, it indicates that the to-be-compiled business module cannot run on the client of the corresponding type, and the first result information is obtained. The first result information describes a set of to-be-compiled business modules that can run on the client of the corresponding type.

[0070] S205: Determine at least one first candidate service module from the plurality of service modules to be compiled according to the first determination result.

[0071] The candidate service module refers to a service module among multiple service modules to be compiled that can be run on a client of a type corresponding to the client that sends the module acquisition request.

[0072] In the embodiment of the present disclosure, after determining whether each to-be-compiled business module can run on the client according to the type information and the compatibility information, and obtaining the first determination result, at least one first candidate business module can be determined from the multiple to-be-compiled business modules according to the first determination result.

[0073] In the disclosed embodiment, when at least one first candidate business module is determined from multiple business modules to be compiled based on the first determination result, the first determination result can be analyzed and processed to obtain a set of business modules to be compiled that can be run on the client, and some of the business modules to be compiled that correspond to the set of business modules to be compiled among the multiple business modules to be compiled are used as first candidate business modules.

[0074] Optionally, in some embodiments, when at least one first candidate business module is determined from multiple business modules to be compiled based on the first determination result, if the first determination result indicates that the business module to be compiled can be run on the client, the business module to be compiled is used as the first candidate business module, so that the first candidate business module that can be run on the client can be determined from the multiple business modules to be compiled requested by the client based on the first determination result, thereby achieving preliminary filtering of the multiple business modules to be compiled, reducing the number of versions subsequently filtered according to the client version, and improving the filtering processing effect.

[0075] S206: Determine a target service module from at least one first candidate service module according to the version information and the compatibility information.

[0076] In the embodiment of the present disclosure, after determining at least one first candidate business module from multiple business modules to be compiled according to the first determination result, a target business module may be determined from the at least one first candidate business module according to version information and compatibility information.

[0077] In the disclosed embodiment, when determining a target business module from at least one first candidate business module based on version information and compatibility information, the compatibility description DSL corresponding to each first candidate business module can be obtained based on the compatibility information, and the version number corresponding to the client can be obtained based on the version information. Then, at least one first candidate business module can be processed to determine whether the version belongs to the range of values ​​corresponding to the key value of the corresponding end in the compatibility description DSL of the first candidate business module currently traversed. If so, the corresponding first candidate business module is taken as the target business module, and each first candidate business module is judged and processed one by one until all first candidate business modules are traversed and the target business module in the first candidate business modules is obtained.

[0078] Optionally, in some embodiments, when determining a target business module from at least one first candidate business module based on version information and compatibility information, it can be determined whether the first candidate business module can run on the client based on the version information and compatibility information to obtain a second determination result, and based on the second determination result, the target business module is determined from at least one first candidate business module, so that the first candidate business modules after preliminary filtering can be further screened based on the version information of the client, so that the filtering process is refined to the version number of the client, effectively improving the compatibility filtering process effect on the business module.

[0079] The second determination result refers to a data result describing whether each first candidate service module can be run on the client.

[0080] In the disclosed embodiment, when determining a target business module from at least one first candidate business module based on version information and compatibility information, the compatibility description DSL of the first candidate business module can be obtained from the compatibility information, and the version number of the client can be determined based on the version information. Then, it can be determined one by one whether the version number of the client is within the version number range described by the value of the key-value pair of the compatibility description DSL of each first candidate business module, and each first candidate business module is traversed and judged to obtain a data result of whether each first candidate business module can be run on the client as a second determination result. Then, based on the second determination result, a first candidate business module that can be run on the client can be determined from at least one first candidate business module as the target business module.

[0081] Optionally, in some embodiments, when determining a target business module from at least one first candidate business module according to the second determination result, if the second determination result indicates that the business module to be compiled can run on the client, the first candidate business module is used as the target business module.

[0082] In the disclosed embodiment, when determining the target business module from at least one first candidate business module based on the second determination result, the second determination result can be analyzed and processed. If the second determination result indicates that the business module to be compiled can run on the client, the first candidate business module is used as the target business module, and the judgment result of each first candidate business module in the second determination result is traversed and processed, and all first candidate business modules that can run on the client are used as target business modules.

[0083] For example, Figure 3 As shown, Figure 3 : is a flow chart of the server compatibility filtering process in the embodiment of the present disclosure. The life cycle of the software system of the application is generally: system design stage, system development stage, system compilation stage and system use stage. The process flow of the server completing the sending of the business module is the system use stage. The client initiates a data interface request (module acquisition request) to the server to request the required business module. The server receives the module acquisition request and processes the data according to the following steps. The server queries the storage service to obtain all the business modules to be compiled requested by the client, which is called a set S3. S3 is traversed. The following are the operation steps of a single traversal: obtain the business module to be compiled currently traversed, which is called M2. The client type and corresponding version information are obtained from the request header or request parameter of the module acquisition request sent by the client. It is determined whether the client type exists in the compatibility description DSL of M2. If it exists, it is further determined whether the client version belongs to the value range of the key-value pair of the corresponding end in the compatibility description DSL of M2. If it does not belong, the module is removed from S3. If it does not exist, the module is removed from S3. S3 after all filtering operations is completed is returned to the requesting client.

[0084] S207: Send the target service module to the client.

[0085] For the description of S207, please refer to the above embodiment, which will not be repeated here.

[0086] In this embodiment, by receiving a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier, information of a module to be compiled requested by the client, determining a plurality of business modules to be compiled corresponding to the information of the module to be compiled, determining a target business module from the plurality of business modules to be compiled according to the client identifier and the compatibility information, and sending the target business module to the client, the compatibility information can be used to filter the business modules incompatible with the client, and ensure that the business modules sent to the client can be successfully run. Since the compatibility information is obtained in real time during the filtering process, the timeliness of compatibility analysis of the business modules can be effectively guaranteed. When determining the target business module from the plurality of business modules to be compiled according to the client identifier and the compatibility information, the type information and version information of the client can be determined according to the client identifier, and the target business module can be determined from the plurality of business modules to be compiled according to the type information, the version information, and the compatibility information. Therefore, according to the type information and the version information of the client and the compatibility information of the business modules to be compiled, whether the business modules to be compiled can be compatible and run on the client can be traversed and analyzed, so as to obtain the business modules to be compiled that can be run on the client as the target business modules, so as to achieve effective filtering of the compatibility of the business modules, and ensure that the business modules received by the client can be compiled and run smoothly.

[0087] Figure 4 It is a flowchart of a method for acquiring a business module proposed in an embodiment of the present disclosure.

[0088] The embodiments of the present disclosure may be applied to a client.

[0089] Among them, the client refers to the program that provides local services to customers corresponding to the server. It is usually installed on an ordinary client or uses a built-in web browser and needs to cooperate with the server to run.

[0090] like Figure 4 As shown, the business module acquisition method includes:

[0091] S401: Send a module acquisition request to a server, wherein the module acquisition request includes: a client identifier and information of modules to be compiled requested by the client, and the information of modules to be compiled is used by the server to determine a plurality of business modules to be compiled corresponding to the information of modules to be compiled.

[0092] In the disclosed embodiment, when a client needs to request a required business module to be compiled, the client can generate business module information to be compiled according to the business module to be compiled that the client wants to use. The module information to be compiled is used by the server to determine multiple business modules to be compiled corresponding to the module information to be compiled, and then generate a module acquisition request according to its own client identifier and the module information to be compiled, and send the module acquisition request to the server.

[0093] S402: Receive a target service module sent by the server, wherein the target service module is determined by the server from a plurality of service modules to be compiled according to the client identifier and compatibility information.

[0094] In the embodiment of the present disclosure, after sending the module acquisition request to the server, the server can determine multiple to-be-compiled business modules corresponding to the to-be-compiled module information according to the module acquisition request, and then determine the multiple to-be-compiled business modules corresponding to the to-be-compiled module information, determine the target business module from the multiple to-be-compiled business modules according to the client identifier and the compatibility information, and send the target business module to the client, and the client receives the target business module sent by the server, the target business module is determined by the server from the multiple to-be-compiled business modules according to the client identifier and the compatibility information.

[0095] In this embodiment, a module acquisition request is sent to the server, wherein the module acquisition request includes: a client identifier, information about the module to be compiled requested by the client, the information about the module to be compiled is used by the server to determine multiple business modules to be compiled corresponding to the information about the module to be compiled, and a target business module sent by the server is received, wherein the target business module is determined by the server from multiple business modules to be compiled according to the client identifier and compatibility information. Since the target business module is obtained after filtering by the server according to the compatibility information, it can be ensured that the business module requested by the client can be compatible and run on the client, thereby ensuring the running effect of the application.

[0096] Figure 5 It is a flowchart of a compatibility information generating method proposed in an embodiment of the present disclosure.

[0097] The embodiments of the present disclosure may be applied to third-party devices.

[0098] Among them, third-party devices refer to development devices used by developers when developing software systems for applications.

[0099] like Figure 5 As shown, the compatibility information generating method includes:

[0100] S501: Obtain type information and version information of at least one client.

[0101] In an embodiment of the present disclosure, a developer may operate a third-party device to determine the type of client that a cross-terminal application expects to deploy, to obtain type information of at least one client, and to obtain version number ranges of clients that each type of client expects to deploy, to obtain version information of at least one client.

[0102] S502: Acquire at least one business logic interface referenced by the business module to be compiled, wherein the business logic interface is used to implement the business logic of the business module to be compiled.

[0103] In the embodiment of the present disclosure, when obtaining at least one business logic interface referenced by a business module to be compiled, an automated compilation tool (such as webpack) can be used to obtain a set of all business modules to be compiled from the system code during the system compilation phase, and the business modules to be compiled in the set are traversed. For example, Figure 6 As shown in sub-process 1, Figure 6 is a schematic diagram of the system compilation process in the embodiment of the present disclosure. The following are the steps of a single traversal operation: Get the module currently traversed, called M1. Each business module to be compiled is composed of its own business logic code, other reference modules, and other reference business logic interface APIs. At the same time, other reference modules can also reference more other modules or APIs, and other APIs can also reference more other APIs, such as Figure 6 As shown in sub-process 2, the entire module code composition can be abstracted as a multi-branch tree. Starting from the root node of the tree, each child node of the tree is traversed. Every time a child node is traversed, an attempt is made to obtain the compatibility description DSL content of the child node. If the acquisition is successful, the content is added to a new collection, which is called S2. The content in the S2 collection can be at least one business logic interface referenced by the business module to be compiled.

[0104] S501: Generate compatibility information corresponding to the server according to type information, version information and business logic interface, wherein the compatibility information is used to describe the operation of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client.

[0105] Among them, compatibility information refers to data information that can describe the running status of the business module to be compiled on different clients. The compatibility information can be used by the server to determine the target business module requested by the client. The compatibility information can include the compatibility description DSL of each business module to be compiled, and the compatibility information can be stored on the server.

[0106] The business logic interface refers to a data interface used to implement the business logic of the business module to be compiled. The business logic interface can be written in the code of the business module to be compiled itself, or it can be a business logic interface of other modules referenced by the business module to be compiled.

[0107] For example, Figure 7 As shown, Figure 7It is a schematic diagram of interface references in the public embodiments. The business logic interface API is an implementation unit of underlying basic functions. When developing the business logic interface API, developers can introduce other APIs to combine into a complex underlying API in addition to their own business logic code. The implementation of this unit includes specific implementation logic in various types of clients. The implementation logic of each client may be different. It also allows only some terminals to be implemented instead of all clients that are expected to be supported. At the same time, a DSL that describes the API compatibility is used to record the specific support status of the API on each terminal.

[0108] In the disclosed embodiment, when compatibility information corresponding to the server is generated according to type information, version information and business logic interface, system design and system development can be performed on the software system of the cross-end application, and it is determined what types of clients are included in all clients that the cross-end application expects to support, as well as the version range corresponding to each type of client, and then the design and development of the business modules to be compiled of the software system are performed. When the developers develop the business modules to be compiled, in addition to the business logic code of the module itself, they can also introduce other modules to be compiled to combine into a complex business function. Some business functions require the support of the underlying capabilities of the system, and this part must be exposed by introducing the system. It can be implemented through API instead of being implemented in the module by yourself. During the system compilation stage, an automated compilation tool (such as webpack) can be used to obtain a set of all business modules to be compiled from the system code, and the business modules to be compiled in the set can be traversed. The entire module code composition can be abstracted as a multi-branch tree. Starting from the root node of the tree, each child node of the tree is traversed. Every time a child node is traversed, try to obtain the compatibility description DSL content of the child node until all business modules to be compiled in the set are traversed and processed. The compatibility description DSL of all business modules to be compiled is obtained as compatibility information, and the compatibility information is saved to the server.

[0109] For example, Figure 8 As shown, Figure 8It is a schematic diagram of the system design of the application in the embodiment of the present disclosure. The developer performs abstract hierarchical design of the application from the system architecture level of the application, abstracting the business layer and the system layer. The business layer focuses on processing business logic and takes business modules as components. The system layer provides underlying capabilities to support the business layer and provides them to the business layer in the form of a standardized application programming interface (Application Programming Interface, API), wherein the API encapsulates the specific operation logic implementation for each end. The developer or software decision maker specifies what types of clients are included in all the clients that the cross-end application expects to support, as well as the version ranges of the corresponding types of clients, and marks each supported end with a unique KEY. For example, a browser client is marked with its KEY as client1, and a APP client is marked with its KEY as client3.

[0110] In the disclosed embodiment, when generating compatibility information corresponding to the server, the type information and version information of at least one client can be obtained, and all the clients that the cross-end application expects to support can include which types of clients to obtain the type information of the client, and the version range corresponding to each type of client can be used as the version information of the corresponding type of client, and then at least one business logic interface referenced by the business module to be compiled can be obtained, and then the compatibility information of each business module to be compiled can be generated according to the type information, version information and business logic interface, and each business module to be compiled and the business logic interface referenced by it can be traversed to determine whether the currently traversed business module to be compiled can be run on a client of the corresponding type and version number, and if it can be run, the type and number of the client are written into the compatibility description DSL of the business module to be compiled, and whether each business module to be compiled can be run on clients of each type and version to obtain the compatibility description DSL of each business module to be compiled, and the compatibility description DSL of all business modules to be compiled is used as the compatibility information of the business module to be compiled.

[0111] In this embodiment, by obtaining type information and version information of at least one client, at least one business logic interface referenced by the business module to be compiled is obtained, wherein the business logic interface is used to implement the business logic of the business module to be compiled, and compatibility information corresponding to the server is generated according to the type information, version information and business logic interface, wherein the compatibility information is used to describe the operation of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client, and the compatibility of the business module and its referenced interface and other business modules on different clients can be obtained by traversing the business module, and the corresponding compatibility information is generated and stored in the server. Since the compatibility information can be used to analyze the compatibility of the business module on the corresponding client when the client requests the business module from the server, the filtering effect of the business module can be effectively improved, and the compatibility information of the business module to be compiled and the business logic interface of its application are obtained one by one, so as to ensure the comprehensiveness of the compatibility information acquisition of the system business module, and ensure the comprehensiveness and accuracy of the compatibility filtering processing of the business module to be compiled requested by the client by the server when the application is running on each client.

[0112] Fig. 9 It is a flowchart of a compatibility information generating method proposed in another embodiment of the present disclosure.

[0113] The embodiments of the present disclosure may apply third-party devices. The explanation of the third-party devices can be found in the above embodiments and will not be repeated here.

[0114] like Fig. 9 As shown, the compatibility information generating method includes:

[0115] S901: Obtain type information and version information of at least one client.

[0116] S902: Acquire at least one business logic interface referenced by the business module to be compiled, wherein the business logic interface is used to implement the business logic of the business module to be compiled.

[0117] For the detailed description of S901 and S902 , please refer to the above embodiments and will not be repeated here.

[0118] S903: Determine whether each business logic interface supports running on the client corresponding to the type information and version information, and obtain running result information.

[0119] The operation result information is used to describe the operation status of each business logic interface on clients of various types and corresponding version numbers.

[0120] After obtaining the type information and version information of at least one client and obtaining at least one business logic interface referenced by the business module to be compiled, the embodiment of the present disclosure can determine whether each business logic interface supports running on the client corresponding to the type information and version information, and obtain running result information, such as Figure 6 As shown in sub-process 2, after obtaining the set S2, the set S2 can be traversed. Each time the traversal is performed, the compatibility description DSL of the current traversal API is called D. The content of D is a number of key-value pairs. The key-value pairs are extracted one by one. When each key-value pair is extracted, the value of the key-value pair is recorded in M_Data according to the KEY of the key-value pair. After the traversal of the set S2 is completed, the running status information of each business logic interface on the client of each type and the version number corresponding to each type can be obtained, and the running status information is used as the running result information.

[0121] S904: Determine the client version number of the client that supports the operation of all business logic interfaces according to the operation result information.

[0122] In the embodiment of the present disclosure, after determining whether each business logic interface supports running on the client corresponding to the type information and version information, and obtaining the running result information, the client version number of the client supporting the running of all business logic interfaces can be determined according to the running result information, such as Figure 6 As shown in sub-process 2 in the above, after the M_Data data is obtained, the M_Data data can be processed by taking each array as a dimension and performing an intersection operation on each item in the array. The intersection obtained from each array is the client version number of the client that supports the operation of all business logic interfaces.

[0123] S905: Generate a client identifier corresponding to the client according to the type information and the version information.

[0124] In the disclosed embodiment, a client identifier corresponding to each client may be generated according to the client type to which each client belongs and the version number information corresponding to the client, so as to uniquely identify the identity information of the client. The client identifier may be used to assist in generating compatibility information.

[0125] S906: Generate compatibility information according to the client identifier and the client version number.

[0126] In the embodiment of the present disclosure, after determining the client version number of the client supporting the operation of all business logic interfaces according to the operation result information, and generating a client identifier corresponding to the client according to the type information and version information, compatibility information can be generated according to the client identifier and the client version number.

[0127] When generating compatibility information according to the client identifier and the client version number, the disclosed embodiment may generate a corresponding key-value pair for the client identifier and the client version number, wherein the key of the key-value pair is the client identifier and the value of the key-value pair is the client version number.

[0128] Optionally, in some embodiments, when generating compatibility information based on the client identifier and the client version number, a key-value pair can be generated based on the client identifier and the client version number, wherein the key of the key-value pair is the client identifier and the value of the key-value pair is the client version number, and the key-value pair is used as the compatibility information.

[0129] For example, Figure 6 As shown in sub-process 3 in , assuming that there are three version number ranges in the client client3 array, the version number range of item 1 is greater than or equal to 1.0, the version number range of item 2 is greater than or equal to 2.0, and the version number range of item 3 is 2.0 and 3.0. The intersection of these three ranges is only 2.0 and 3.0, so at this time, the compatibility DSL of M1 for client3 can be obtained as {client3:["2.0","3.0"]}. When the M_Data data is processed, the complete compatibility description DSL of M1 is obtained. At this time, each module in S1 generates the compatibility description DSL corresponding to the module, and the compatibility DSL of all business modules to be compiled is used as compatibility information, and the module compatibility information is saved to the server.

[0130] In this embodiment, the full-process development and automatic filtering solution based on the concept of compatibility description DSL unifies the differences in the lower end of the cross-end rendering architecture in the API, and expresses cross-end compatibility using compatibility description DSL, so that module development is decoupled from cross-end compatibility. Module developers do not need to pay attention to compatibility issues, while automatically obtaining reliable and timely compatibility expressions. In the module usage scenario, the function of automatically identifying mismatches and filtering can be realized.

[0131] In this embodiment, by generating compatibility information corresponding to the server, wherein the compatibility information is used to describe the running status of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client, the business module and the interface referenced by the business module and the compatibility of other business modules on different clients can be obtained by traversing the business module, and the corresponding compatibility information is generated and stored in the server. Since the compatibility information can be used to analyze the compatibility of the business module on the corresponding client when the client requests the business module from the server, the filtering effect of the business module can be effectively improved. By obtaining the type information and version information of at least one client, at least one business logic interface referenced by the business module to be compiled is obtained, wherein the business logic interface is used to implement the business logic of the business module to be compiled, and the compatibility information of each business module to be compiled is generated according to the type information, version information and business logic interface, so that the compatibility information of the business module to be compiled and the business logic interface of its application can be obtained one by one, so as to ensure the comprehensiveness of the compatibility information acquisition of the system business module, and ensure the comprehensiveness and accuracy of the compatibility filtering processing of the business module to be compiled requested by the client by the server when the application is running on each client.

[0132] Fig.10 It is a structural diagram of a service module sending device proposed in an embodiment of the present disclosure.

[0133] The service module sending device 100 is applied to a server, and the server includes: compatibility information, and the compatibility information is used to describe the operation of the service module to be compiled on different clients. The device includes:

[0134] The first transmission module 1001 is used to receive a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier and information of a module to be compiled requested by the client;

[0135] A first determining module 1002, configured to determine a plurality of to-be-compiled service modules corresponding to the to-be-compiled module information;

[0136] A second determination module 1003, configured to determine a target service module from a plurality of service modules to be compiled according to the client identifier and the compatibility information;

[0137] The second transmission module 1004 is used to send the target service module to the client.

[0138] In some embodiments of the present disclosure, Fig.11 As shown, Fig.11 100 is a schematic diagram of the structure of a service module sending device proposed in another embodiment of the present disclosure, wherein the second determination module 1003 includes:

[0139] The first determination submodule 10031 is used to determine the type information and version information of the client according to the client identifier;

[0140] The second determining submodule 10032 is used to determine a target business module from a plurality of business modules to be compiled according to type information, version information, and compatibility information.

[0141] In some embodiments of the present disclosure, the second determining submodule 10032 is specifically configured to:

[0142] Determine whether each to-be-compiled business module can run on the client according to the type information and the compatibility information, and obtain a first determination result;

[0143] Determining at least one first candidate service module from a plurality of service modules to be compiled according to the first determination result;

[0144] A target service module is determined from at least one first candidate service module according to the version information and the compatibility information.

[0145] In some embodiments of the present disclosure, the second determining submodule 10032 is further configured to:

[0146] Determine whether the first candidate service module can be run on the client according to the version information and the compatibility information, and obtain a second determination result;

[0147] According to the second determination result, a target service module is determined from at least one first candidate service module.

[0148] In some embodiments of the present disclosure, the second determining submodule 10032 is further configured to:

[0149] If the first determination result indicates that the service module to be compiled can be run on the client, the service module to be compiled is used as a first candidate service module.

[0150] In some embodiments of the present disclosure, the second determining submodule 10032 is further configured to:

[0151] If the second determination result indicates that the to-be-compiled service module can be run on the client, the first candidate service module is used as the target service module.

[0152] With the above Figures 1 to 3 Corresponding to the service module sending method provided in the embodiment, the present disclosure also provides a service module sending device. Figures 1 to 3 The service module sending method provided in the embodiment corresponds to the service module sending method, so the implementation of the service module sending method is also applicable to the service module sending device provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.

[0153] In this embodiment, by receiving a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier, information of the module to be compiled requested by the client, a plurality of business modules to be compiled corresponding to the information of the module to be compiled are determined, a target business module is determined from the plurality of business modules to be compiled according to the client identifier and the compatibility information, and the target business module is sent to the client. The compatibility information can be used to filter out the business modules incompatible with the client, thereby ensuring that the business modules sent to the client can run successfully. Since the compatibility information is obtained in real time during the filtering process, the timeliness of the compatibility analysis of the business modules is effectively guaranteed.

[0154] Fig.12 This is a schematic diagram of the structure of a service module acquisition device proposed in an embodiment of the present disclosure.

[0155] The service module acquisition device 120 is applied to the client and includes:

[0156] The third transmission module 1201 is used to send a module acquisition request to the server, wherein the module acquisition request includes: a client identifier and information of the module to be compiled requested by the client, and the information of the module to be compiled is used by the server to determine a plurality of business modules to be compiled corresponding to the information of the module to be compiled;

[0157] The fourth transmission module 1202 is used to receive a target service module sent by the server, wherein the target service module is determined by the server from a plurality of service modules to be compiled according to the client identifier and compatibility information.

[0158] With the above Figure 4 Corresponding to the service module acquisition method provided in the embodiment, the present disclosure also provides a service module acquisition device. Figure 4 The business module acquisition method provided in the embodiment corresponds to the business module acquisition method, so the implementation of the business module acquisition method is also applicable to the business module acquisition device provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.

[0159] In this embodiment, a module acquisition request is sent to the server, wherein the module acquisition request includes: a client identifier, information about the module to be compiled requested by the client, the information about the module to be compiled is used by the server to determine multiple business modules to be compiled corresponding to the information about the module to be compiled, and a target business module sent by the server is received, wherein the target business module is determined by the server from multiple business modules to be compiled according to the client identifier and compatibility information. Since the target business module is obtained after filtering by the server according to the compatibility information, it can be ensured that the business module requested by the client can be compatible and run on the client, thereby ensuring the running effect of the application.

[0160] Fig.13 This is a schematic diagram of the structure of a compatibility information generating device proposed in an embodiment of the present disclosure.

[0161] The compatibility information generating device 130 is applied to a third-party device and includes:

[0162] The first acquisition module 1301 is used to acquire type information and version information of at least one client;

[0163] A second acquisition module 1302 is used to acquire at least one business logic interface referenced by the business module to be compiled, wherein the business logic interface is used to implement the business logic of the business module to be compiled;

[0164] Generation module 1303 is used to generate compatibility information corresponding to the server based on type information, version information and business logic interface, wherein the compatibility information is used to describe the operation of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client.

[0165] In some embodiments of the present disclosure, Fig.14 As shown, Fig.14 1 is a schematic diagram of the structure of a compatibility information generating device proposed in another embodiment of the present disclosure, wherein the generating module 1303 includes:

[0166] The first determination submodule 13031 is used to determine whether each business logic interface supports running on the client corresponding to the type information and version information, and obtain running result information;

[0167] The second determination submodule 13032 is used to determine the client version number of the client supporting the operation of all business logic interfaces according to the operation result information;

[0168] The first generating submodule 13033 is used to generate a client identifier corresponding to the client according to the type information and the version information;

[0169] The second generating submodule 13034 is used to generate compatibility information according to the client identifier and the client version number.

[0170] In some embodiments of the present disclosure, the second generation submodule 13034 is specifically used to:

[0171] Generate a key-value pair according to the client identifier and the client version number, wherein the key of the key-value pair is the client identifier and the value of the key-value pair is the client version number;

[0172] Takes key-value pairs as compatibility information.

[0173] With the above Figures 5 to 9 Corresponding to the service module acquisition method provided in the embodiment, the present disclosure also provides a service module acquisition device. Figures 5 to 9 The business module acquisition method provided in the embodiment corresponds to the business module acquisition method, so the implementation of the business module acquisition method is also applicable to the business module acquisition device provided in the embodiment of the present disclosure, and will not be described in detail in the embodiment of the present disclosure.

[0174] In this embodiment, compatibility information corresponding to the server is generated, wherein the compatibility information is used to describe the running status of the business module to be compiled on different clients. The compatibility information is used by the server to determine the target business module requested by the client. By traversing the business modules, the compatibility of the business modules and their referenced interfaces and other business modules on different clients can be obtained, and the corresponding compatibility information is generated and stored in the server. Since the compatibility information can be used to analyze the compatibility of the business module on the corresponding client when the client requests the business module from the server, the filtering effect of the business module can be effectively improved.

[0175] In order to implement the above-mentioned embodiments, the present disclosure also proposes a non-temporary computer-readable storage medium, on which a computer program is stored. When the program is executed by a processor, it implements the service module sending method proposed in the aforementioned embodiment of the present disclosure, or implements the service module sending method proposed in the aforementioned embodiment of the present disclosure, or implements the compatible information generating method proposed in the aforementioned embodiment of the present disclosure.

[0176] In order to implement the above-mentioned embodiments, the present disclosure also proposes a computer program product. When the instruction processor in the computer program product is executed, it executes the service module sending method proposed in the aforementioned embodiment of the present disclosure, or implements the service module sending method proposed in the aforementioned embodiment of the present disclosure, or implements the compatible information generating method proposed in the aforementioned embodiment of the present disclosure.

[0177] Fig.15 A block diagram of an exemplary electronic device suitable for implementing embodiments of the present disclosure is shown.

[0178] Fig.15 The electronic device 15 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0179] like Fig.15 As shown, the electronic device 15 is in the form of a general purpose computing device. The components of the electronic device 15 may include, but are not limited to: one or more processors or processing units 16, a memory 28, and a bus 18 connecting different system components (including the memory 28 and the processing unit 16).

[0180] The bus 18 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnection (PCI) bus.

[0181] The electronic device 15 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 15, including volatile and non-volatile media, removable and non-removable media.

[0182] The memory 28 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 30 and / or cache memory 32. The electronic device 15 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 34 may be used to read and write non-removable, non-volatile magnetic media ( Fig.15 Not shown, often called a "hard drive").

[0183] although Fig.15 Not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (e.g., a compact disc read only memory (hereinafter referred to as: CD-ROM), a digital versatile disc read only memory (hereinafter referred to as: DVD-ROM) or other optical media) may be provided. In these cases, each drive may be connected to the bus 18 via one or more data medium interfaces. The memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present disclosure.

[0184] A program / utility 40 having a set (at least one) of program modules 42 may be stored, for example, in the memory 28, such program modules 42 including but not limited to an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 42 generally perform the functions and / or methods of the embodiments described in the present disclosure.

[0185] The electronic device 15 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, etc.), may also communicate with one or more devices that enable the human body to interact with the electronic device 15, and / or communicate with any device that enables the electronic device 15 to communicate with one or more other computing devices (e.g., network card, modem, etc.). Such communication may be performed through an input / output (I / O) interface 22. In addition, the electronic device 15 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 20. As shown, the network adapter 20 communicates with other modules of the electronic device 15 through a bus 18. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 15, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0186] The processing unit 16 executes various functional applications and parameter information determination by running the program stored in the memory 28, such as implementing the service module sending method mentioned in the aforementioned embodiment, or implementing the service module sending method proposed in the aforementioned embodiment of the present disclosure, or implementing the compatible information generation method proposed in the aforementioned embodiment of the present disclosure.

[0187] It should be noted that, in the description of the present disclosure, the terms "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present disclosure, unless otherwise specified, the meaning of "plurality" is two or more.

[0188] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present disclosure includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.

[0189] It should be understood that the various parts of the present disclosure can be implemented in hardware, software, firmware or a combination thereof. In the above-mentioned embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0190] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0191] In addition, each functional unit in each embodiment of the present disclosure may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium.

[0192] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0193] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representation of the above terms does not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0194] Although the embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present disclosure. A person skilled in the art may change, modify, replace and vary the above embodiments within the scope of the present disclosure.

Claims

1. A method for sending a service module, It is characterized in that Applied to a server, the server includes: compatibility information, the compatibility information is used to describe the running conditions of the service module to be compiled on different clients, the method includes: Receiving a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier and information of a module to be compiled requested by the client; Determine a plurality of to-be-compiled service modules corresponding to the to-be-compiled module information; Determining a target service module from the multiple service modules to be compiled according to the client identifier and the compatibility information; The target service module is sent to the client.

2. The method according to claim 1, It is characterized in that The step of determining a target service module from the plurality of service modules to be compiled according to the client identifier and the compatibility information includes: Determining the type information and version information of the client according to the client identifier; A target service module is determined from the multiple service modules to be compiled according to the type information, the version information, and the compatibility information.

3. The method according to claim 2, It is characterized in that The determining a target business module from the multiple business modules to be compiled according to the type information, the version information, and the compatibility information includes: Determine, according to the type information and the compatibility information, whether each of the to-be-compiled service modules can be run on the client, to obtain a first determination result; Determining at least one first candidate service module from the plurality of service modules to be compiled according to the first determination result; The target service module is determined from the at least one first candidate service module according to the version information and the compatibility information.

4. The method according to claim 3, It is characterized in that The step of determining the target service module from the at least one first candidate service module according to the version information and the compatibility information includes: Determine, according to the version information and the compatibility information, whether the first candidate service module can be run on the client to obtain a second determination result; The target service module is determined from the at least one first candidate service module according to the second determination result.

5. The method according to claim 3, It is characterized in that The step of determining at least one first candidate service module from the plurality of service modules to be compiled according to the first determination result includes: If the first determination result indicates that the to-be-compiled service module can be run on the client, the to-be-compiled service module is used as the first candidate service module.

6. The method according to claim 4, It is characterized in that The step of determining the target service module from the at least one first candidate service module according to the second determination result includes: If the second determination result indicates that the to-be-compiled service module can be run on the client, the first candidate service module is used as the target service module.

7. A method for obtaining a business module, It is characterized in that Applied to a client, the method comprises: Sending a module acquisition request to the server, wherein the module acquisition request includes: a client identifier and information of the module to be compiled requested by the client, wherein the information of the module to be compiled is used by the server to determine a plurality of business modules to be compiled corresponding to the information of the module to be compiled; A target service module sent by the server is received, wherein the target service module is determined by the server from the multiple service modules to be compiled according to the client identifier and compatibility information.

8. A method for generating compatibility information, It is characterized in that Applied to a third-party device, the method includes: Obtain type information and version information of at least one client; Acquire at least one business logic interface referenced by the business module to be compiled, wherein the business logic interface is used to implement the business logic of the business module to be compiled; Compatibility information corresponding to the server is generated based on the type information, the version information and the business logic interface, wherein the compatibility information is used to describe the operation of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client.

9. The method according to claim 8, It is characterized in that The generating, according to the type information, the version information and the business logic interface, the compatibility information corresponding to the server includes: Determine whether each of the business logic interfaces supports running on the client corresponding to the type information and the version information, and obtain running result information; Determine, according to the operation result information, a client version number of the client that supports the operation of all the business logic interfaces; Generate a client identifier corresponding to the client according to the type information and the version information; The compatibility information is generated according to the client identifier and the client version number.

10. The method according to claim 9, It is characterized in that The generating the compatibility information according to the client identifier and the client version number includes: Generate a key-value pair according to the client identifier and the client version number, wherein the key of the key-value pair is the client identifier, and the value of the key-value pair is the client version number; The key-value pair is used as the compatibility information.

11. A service module sending device, It is characterized in that Applied to a server, the server includes: compatibility information, the compatibility information is used to describe the operation of the service module to be compiled on different clients, the device includes: A first transmission module is used to receive a module acquisition request sent by a client, wherein the module acquisition request includes: a client identifier and information of a module to be compiled requested by the client; A first determining module, used to determine a plurality of to-be-compiled service modules corresponding to the to-be-compiled module information; A second determination module, configured to determine a target service module from the plurality of service modules to be compiled according to the client identifier and the compatibility information; The second transmission module is used to send the target service module to the client.

12. A device for acquiring a business module, It is characterized in that Applied to a client, the device comprises: A third transmission module is used to send a module acquisition request to the server, wherein the module acquisition request includes: a client identifier and information about the module to be compiled requested by the client, and the information about the module to be compiled is used by the server to determine a plurality of service modules to be compiled corresponding to the information about the module to be compiled; The fourth transmission module is used to receive a target service module sent by the server, wherein the target service module is determined by the server from the multiple service modules to be compiled according to the client identifier and compatibility information.

13. A compatibility information generating device, It is characterized in that Applied to third-party equipment, the device comprises: A first acquisition module, used to acquire type information and version information of at least one client; A second acquisition module, used to acquire at least one business logic interface referenced by the business module to be compiled, wherein the business logic interface is used to implement the business logic of the business module to be compiled; A generation module is used to generate compatibility information corresponding to the server according to the type information, the version information and the business logic interface, wherein the compatibility information is used to describe the operation of the business module to be compiled on different clients, and the compatibility information is used by the server to determine the target business module requested by the client.

14. An electronic device, It is characterized in that include: at least one processor; as well as a memory communicatively connected to 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 so that the at least one processor can execute the service module sending method described in any one of claims 1-6, or execute the service module acquisition method described in claim 7, or execute the compatibility information generation method described in any one of claims 8-10.

15. A non-transitory computer-readable storage medium storing computer instructions, It is characterized in that in, The computer instructions are used to enable the computer to execute the service module sending method described in any one of claims 1-6, or the service module acquisition method described in claim 7, or the compatibility information generating method described in any one of claims 8-10.

16. A computer program product, It is characterized in that It includes a computer program, which, when executed by a processor, implements the steps of the service module sending method according to any one of claims 1-6, or implements the steps of the service module acquisition method according to claim 7, or executes the steps of the compatibility information generating method according to any one of claims 8-10.