CN111459475A

CN111459475A - Interface calling method, interface docking configuration method, device, equipment and medium

Info

Publication number: CN111459475A
Application number: CN202010236962.2A
Authority: CN
Inventors: 张晓光; 吴运涛
Original assignee: Beijing Sankuai Online Technology Co Ltd
Current assignee: Beijing Sankuai Online Technology Co Ltd
Priority date: 2020-03-30
Filing date: 2020-03-30
Publication date: 2020-07-28
Anticipated expiration: 2040-03-30
Also published as: CN111459475B

Abstract

The application discloses an interface calling method, an interface butt joint configuration device, equipment and a medium, and belongs to the technical field of internet. The method comprises the following steps: acquiring a calling instruction aiming at a first interface in a first system; acquiring docking configuration information of a first interface; selecting n functional components from a pre-configured component library according to the docking configuration information; the n functional components are run to invoke the first interface. According to the technical scheme, the program codes for realizing the interface calling function are stored in the component library in the form of the pre-developed functional components, so that the multiplexing of the functional components can be realized when different interfaces are aimed at, repeated development work is not needed, and the time and labor cost of interface butt joint development work are saved.

Description

Interface calling method, interface docking configuration method, device, equipment and medium

Technical Field

The embodiment of the application relates to the technical field of internet, in particular to a method, a device, equipment and a medium for interface calling and interface docking configuration.

Background

Data interaction between different systems can be carried out through an interface. For example, the merchant system provides an interface to the shopping platform system that can be invoked, and the shopping platform system sends a relevant operation request to the merchant system by invoking the interface of the merchant system.

In the related technology, in order to realize the interface docking of the shopping platform system and the merchant system, firstly, a system specification of the merchant system needs to be obtained, and which interfaces of the merchant system need to be docked are determined; then, for each interface needing to be docked, the docking development work of the interface is completed by writing codes of the whole flow; after the writing of the docking codes of one interface is finished, writing of the docking codes of the next interface is carried out until the writing of the docking codes of all the interfaces is finished.

Disclosure of Invention

The embodiment of the application provides an interface calling method, an interface docking configuration device, equipment and a medium. The technical scheme is as follows:

in one aspect, an embodiment of the present application provides an interface calling method, where the method includes:

acquiring a calling instruction aiming at a first interface in a first system;

acquiring docking configuration information of the first interface, wherein the docking configuration information comprises component configuration information used for indicating n functional components used by a second system for docking the first interface, and n is a positive integer;

selecting n functional components from a pre-configured component library according to the docking configuration information;

and executing the n functional components to call the first interface.

In another aspect, an embodiment of the present application provides an interface docking configuration method, where the method includes:

displaying an interface docking configuration page, wherein the interface docking configuration page comprises a preconfigured component library;

acquiring selection instructions aiming at n functional components in the component library, wherein n is a positive integer;

generating docking configuration information for a first interface in a first system, the docking configuration information including component configuration information indicating the n functional components used by a second system to dock the first interface;

sending the docking configuration information to a server of the second system.

In another aspect, an embodiment of the present application provides an interface invoking device, where the interface invoking device includes:

the instruction acquisition module is used for acquiring a calling instruction aiming at a first interface in a first system;

an information obtaining module, configured to obtain docking configuration information of the first interface, where the docking configuration information includes component configuration information used to instruct a second system to dock n functional components used by the first interface, where n is a positive integer;

the component selection module is used for selecting n functional components from a pre-configured component library according to the docking configuration information;

and the interface calling module is used for operating the n functional components to call the first interface.

In another aspect, an embodiment of the present application provides an interface docking configuration apparatus, where the apparatus includes:

the page display module is used for displaying an interface docking configuration page, and the interface docking configuration page comprises a preconfigured component library;

the instruction acquisition module is used for acquiring selection instructions aiming at n functional components in the component library, wherein n is a positive integer;

an information generating module, configured to generate docking configuration information for a first interface in a first system, where the docking configuration information includes component configuration information indicating the n functional components used by a second system to dock the first interface;

and the information sending module is used for sending the docking configuration information to a server of the second system.

In a further aspect, an embodiment of the present application provides a computer device, where the computer device includes a processor and a memory, where the memory stores a computer program, and the computer program is loaded and executed by the processor to implement the interface calling method or the interface docking configuration method.

Optionally, the computer device is a server, a user terminal or a configuration terminal.

In a further aspect, the present application provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor of a computer device, implements the interface calling method described above.

In a further aspect, the present application provides a non-transitory computer-readable storage medium, on which a computer program is stored, where the computer program is executed by a processor of a configuration terminal to implement the interface docking configuration method.

In a further aspect, a computer program product is provided, which, when run on a computer device, causes the computer device to perform the above interface call method.

In a further aspect, a computer program product is provided, which, when running on a configuration terminal, causes the configuration terminal to execute the above interface docking configuration method.

The technical scheme provided by the embodiment of the application can bring the following beneficial effects:

when a first interface in a first system is called, acquiring n functional components used for calling the first interface from a pre-stored component library based on the docking configuration information of the first interface, and then operating the n functional components to call the first interface; in the embodiment of the application, the program codes for realizing the interface calling function are stored in the component library in the form of the pre-developed functional components, so that the multiplexing of the functional components can be realized when different interfaces are aimed at, repeated development work is not needed, and the time and labor cost of interface docking development work are saved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of an interface docking system provided by one embodiment of the present application;

FIG. 2 is a flow chart of an interface call method provided by an embodiment of the present application;

FIG. 3 is a flow chart of a method for interface invocation provided by another embodiment of the present application;

FIG. 4 is a diagram illustrating the flow of an interface invocation method;

FIG. 5 is a flowchart of a configuration method for interface docking according to an embodiment of the present application;

FIG. 6 illustrates a schematic diagram of an interface docking configuration page;

FIG. 7 illustrates a schematic diagram of another interface docking configuration page;

FIG. 8 is a schematic diagram illustrating an interface docking flow;

FIG. 9 is a block diagram of an interface invocation device provided by one embodiment of the present application;

FIG. 10 is a block diagram of an interface invocation device provided in another embodiment of the present application;

FIG. 11 is a block diagram of an interface docking configuration apparatus provided in one embodiment of the present application;

fig. 12 is a block diagram of a computer device according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Referring to fig. 1, a schematic diagram of an interface docking system according to an embodiment of the present application is shown. The interface docking system may include: a first system 10 and a second system 20.

There is a need for interfacing between the first system 10 and the second system 20. For example, there needs to be data interaction between the first system 10 and the second system 20. Taking the example of the second system 20 interfacing with the first system 10, the first system 10 may provide one or more interfaces to the second system 20, and the second system 10 requests the first system 10 to perform corresponding operations by calling the interfaces in the first system 10. The interfaces in the first system 10 may include one or more, and different interfaces may have different functions.

A first server 11 may be included in the first system 10. Alternatively, the interface in the first system 10 may be disposed in the first server 11, and the second system 20 may request the function provided by the first server 11 by calling the interface to perform data interaction with the first server 11. The first server 11 may be one server, a server cluster composed of a plurality of servers, or a cloud computing service center.

The second system 20 may include a user terminal 21 and a second server 22. The user terminal 21 may be an electronic device such as a mobile phone, a tablet computer, a game console, an electronic book reader, a multimedia player, a wearable device, a PC (personal computer), and the like. The user terminal 21 may have a client installed therein for running a target application, where the target application may be a shopping application, a social application, a payment application, a game application, and the like, and this is not limited in this embodiment of the present application. The second server 22 may be a server, a server cluster composed of a plurality of servers, or a cloud computing service center. The second server 22 may be a background server for the target application, and is used for providing background services for the client of the target application.

The user terminal 21 (e.g., a client of the target application) and/or the second server 22 may have a need for data interaction with the first system 10. Taking the user terminal 21 as an example, the user terminal 21 (e.g. a client of the target application) calls an interface in the first server 11 by sending an interface call request to the first server 11, and requests the first server 11 to perform a corresponding operation. Taking the second server 22 as an example, the second server 22 calls the interface in the first server 11 by sending an interface call request to the first server 11, and requests the first server 11 to perform a corresponding operation.

In one example, the target application may be a shopping application, and accordingly, the second system 20 is a shopping application system that includes a client and a backend server for the shopping application, and the first system 10 may be a merchant system, a payment system, an advertising system, and the like. The number of first systems 10 may be multiple, as may a number of different merchant systems.

Optionally, as shown in fig. 1, the interface docking system may further include a configuration terminal 30. The configuration terminal 30 is a terminal device for configuring docking configuration information of the above-described interface. Alternatively, the configuration terminal 30 is a PC (Personal Computer). In the embodiment of the present application, a configurator configures docking configuration information of the interface through an interface docking configuration page on the configuration terminal 30, and sends the docking configuration information to the second server 22, and further, the second server 22 stores the docking configuration information. The second server 22 may use the docking configuration information described above when invoking an interface in the first system 10.

Alternatively, the first system 10 and the second system 20 may communicate with each other via a network, and the configuration terminal 30 and the second server 22 may communicate with each other via a network.

Referring to fig. 2, a flowchart of an interface calling method according to an embodiment of the present application is shown. The method can be applied to the second system 20 of the interface docking system shown in fig. 1, for example, the execution subject of each step can be the user terminal 21 or the second server 22. For convenience of explanation, the following description will be given by taking only the second server 22 (hereinafter, simply referred to as "server") as an example. The method comprises the following steps (201-205):

step 201, a call instruction for a first interface in a first system is obtained.

The first system may be used to provide various required services to the second system, such as sending data to the second system, providing function calls to the second system and responding to operation requests by the second system, and so forth. Optionally, the first system refers to a system that establishes a docking relationship with a second system. It should be noted that the second system may establish a docking relationship with one or more of the first systems. For example, the second system is a background system corresponding to a shopping application, the number of the first systems may be multiple, the first systems include background systems corresponding to merchants respectively, a docking relationship is established between the second system and the first system, and the second system may acquire various data of the first system to display various commodities for a user and provide a commodity purchasing function for the user. For another example, the second system is a background system corresponding to a travel application, the first system may be a background system corresponding to a hotel, a background system corresponding to a tourist attraction, and a background system corresponding to a ticket seller, a docking relationship is established between the second system and the first system, and the second system may acquire data corresponding to the first system to show hotel rooms, attraction tickets, and tickets at various places to the user, and provide the user with functions of hotel ordering, ticket issuing, and ticket purchasing.

The first interface is used for providing data interaction functions for the first system and the second system. Optionally, the first interface is a certain docking interface between the first system and the second system. It should be noted that, for different types of the first interface, different data interaction functions may be provided between the first system and the second system, for example, when the first interface is an ordering interface, the first interface may transmit information such as a commodity model and a commodity remaining amount of the first system to the second system; when the first interface is a payment interface, the first interface may transmit price change information of the first system commodity to the second system, and may also transmit order information and payment success information to the first system, so that the first system may store the order information. It should be noted that, in practical applications, the data transmitted by the first interface may vary according to practical situations, and the function and type of the first interface are not limited in this application. Of course, after the first system and the second system establish a docking relationship, the number of the interfaces for performing data interaction may be one or more, which is not limited in the embodiment of the present application.

The calling instruction is used for calling the first interface, and the calling request comprises an interface address of the first interface. Optionally, the server may invoke the first interface through the call instruction to implement data interaction with the first system, for example, obtain data of the first system, where the data may be model data (commodity picture) or information data (commodity price, quantity).

In one possible embodiment, the call instruction may be triggered automatically. Optionally, the server may automatically generate the call instruction, and then the server calls the first interface according to the call generation instruction. Of course, the server may generate the call instruction at regular time intervals, and the server may call the first interface according to the call generation instruction. Optionally, after the server calls the first interface, the server may record and update the acquired data or the executed operation, for example, the server may update prices of goods in real time, or may record room information ordered by a hotel in real time.

In another possible embodiment, the above-mentioned call instruction may be generated by user triggering. Optionally, the user may trigger generation of the call instruction by clicking an operation control corresponding to the application program on the user terminal. For example, when the user opens the application program, the call instruction may be triggered to be generated, and then the first interface is called to obtain the data of the first system, so as to render the display page of the application program; for another example, when a user purchases a commodity and clicks a corresponding order placing button, the call instruction may be triggered to be generated, and then the first interface is called, so as to obtain data of the first system in real time, and order information corresponding to the commodity is displayed on a user interface, where the order information may include commodity price, commodity preference, commodity quantity, and the like.

Step 202, obtaining docking configuration information of the first interface.

The docking configuration information of the first interface is used for indicating the docking mode of the first interface, and comprises various pieces of configuration information for docking the first interface. Optionally, the docking configuration information includes component configuration information, where the component configuration information is used to indicate n functional components used by the second system to dock the first interface, and n is a positive integer. The functional component refers to a component that processes data of the second system or the first system. The server can call the first interface by running the n functional components to realize data interaction with the first system.

In this embodiment of the application, after acquiring the call instruction of the first interface, the server may acquire the docking configuration information of the first interface according to the call instruction. Optionally, the call instruction may include identification information of the first interface, such as an interface address of the first interface, and the server acquires the docking configuration information of the first interface according to the identification information of the first interface.

The docking configuration information is stored in the information base of the server in advance. Optionally, the information base stores a mapping relationship between the docking configuration information and the identification information of the interface, and the mapping relationship may be stored in the information base in a form of a list. After the server obtains the call instruction, the server may obtain, according to the identification information of the first interface in the call instruction, docking configuration information having a mapping relationship with the identification information from an information base, as the docking configuration information of the first interface.

Step 203, selecting n functional components from a pre-configured component library according to the docking configuration information.

The functional component is used for processing and operating data of the first system or the second system, and optionally, the functional component can be stored in a component library of the server in advance. The component library refers to a database or a storage medium provided in a server and used for storing various components, and the component library may include one or more functional components.

In this embodiment of the application, after obtaining the docking configuration information, the server may select n functional components from a preconfigured component library according to the docking configuration information, where the n functional components are functional components used by the second system when calling the first interface. Optionally, the n functional components may include at least one of: the system comprises a first log tracking component, a request data encryption component, a second log tracking component, a response data verification component and a response data decryption component.

The first log tracking component is configured to record request data and response data transmitted between the second system and the first interface. In a possible implementation manner, the server may detect whether the correspondence between the request data and the response data is correct in real time, for example, detect whether the response data obtained by the second system is the data requested to be obtained by the second system; or detecting whether the quantity of response data acquired by the second system is the same as the quantity of data acquired by the second data request, so as to determine whether the data transmission failure exists. In another possible embodiment, the server may store the request data and the response data recorded by the first log tracking component, so as to facilitate the user to use or detect the request data and the response data subsequently to determine whether the second system and the first interface are communicating normally.

In this embodiment of the present application, the request data encryption component is configured to determine an encryption manner corresponding to the request data according to a type of the request data sent to the first interface by the second system, such as an MD5 information Digest Algorithm (MD5 Message-Digest Algorithm) and a base 64. Optionally, to ensure security of data transmission, the second system may encrypt the request data according to the request data encryption component before sending the request data to the first interface. It should be noted that, when the second system sends the request data to the first interface, different types of request data may correspond to different encryption manners.

The second log tracking component is configured to record an operation condition of the second system after receiving the response data from the first interface, for example, the second log tracking component may record an operation path of the response data on the second system (e.g., the response data is converted from the a module to the B module, and finally stored in the C module). In a possible implementation manner, the server may determine whether the response data can normally operate in the second system in real time according to the operation condition of the response data; in another possible implementation, the server may store the operation condition of the response data recorded by the second log tracking component, so that the user may detect the operation condition later to determine whether the communication between the second system and the first interface is normal.

The response data verification component is used for verifying the response data received by the second system from the first interface. Optionally, the response data checking component is configured to check validity of the response data. In a possible implementation manner, after receiving the response data, the server may check the response data through a response data checking component to determine the validity of the response data, and ensure that the response data is not tampered with maliciously in the transmission process.

The response data decryption component is used for determining a decryption mode of the response data, and in the embodiment of the application, the response data decryption component is used for determining a decryption mode corresponding to the response data according to the type of the response data received by the second system from the first interface. Optionally, in order to ensure the security of data transmission, the response data received by the second system from the first system may be encrypted data, and the server may decrypt the decrypted data according to the response data decryption component after receiving the response data. It should be noted that, in response data acquired by the second system from the first interface, different response data may correspond to different encryption manners, and in a possible implementation, an encryption manner of request data sent by the second system to the first interface may correspond to a decryption manner of response data corresponding to the request data.

It should be noted that the above description of n functional components is only exemplary, and in practical applications, the number or type of the functional components may be changed according to practical situations. For example, a plurality of response data verification components may be stored in the component library, and when generating the docking configuration information, an appropriate response data verification component may be selected according to the type of the first system.

Step 204, running n functional components to call the first interface.

In this embodiment, after the server obtains the n functional components, the server may run the n functional components to call the first interface.

To sum up, in the technical solution provided in the embodiment of the present application, when a first interface in a first system is called, n functional components used for calling the first interface are obtained from a pre-stored component library based on docking configuration information of the first interface, and then the first interface can be called by operating the n functional components; in the embodiment of the application, the program codes for realizing the interface calling function are stored in the component library in the form of the pre-developed functional components, so that the multiplexing of the functional components can be realized when different interfaces are aimed at, repeated development work is not needed, and the time and labor cost of interface docking development work are saved.

While various functional components included in the docking configuration information are mainly described above, in an exemplary embodiment, as shown in table 1, at least one of the following items may also be included in the docking configuration information: request field configuration information, response field configuration information, protocol type configuration information, request data type configuration information, and response data type configuration information.

TABLE 1 docking configuration information

Request field configuration information	Field conversion mode of request data
		Response field configuration information	Field conversion mode of response data
Protocol type configuration information	Transmission protocols, e.g. http, webservice, etc
		Requesting data type configuration information	Data types, e.g. json, xml, etc
Responsive data type configuration information	Data types, e.g. json, xml, etc

The request field configuration information is used to determine the field conversion mode of the requested data. Optionally, the call instruction may include information of the requested data, where the information may be the requested data, or may be prompt information of a manner of acquiring the requested data, for example, the prompt information in the call instruction may be "user a purchases b", and further, according to the prompt information, the requested data generated by the server may be data for requesting various information of the product b. After obtaining the call request, the server may generate corresponding request data according to the call request, and convert the request data into data that can be directly recognized by the first system according to the request field configuration information. The data directly recognizable by the first system refers to data meeting storage or operation rules of the first system, and optionally, the first system may directly use the data after acquiring the directly recognizable data.

The response field configuration information is used to determine the field conversion mode of the response data. Alternatively, after acquiring the response data sent from the first interface to the second system, the server may convert the response data into data directly recognizable by the second system according to the response field configuration information. The data directly recognizable by the second system is data satisfying the storage or operation rule of the second system, and optionally, the second system may directly use the data after receiving the directly recognizable data.

The protocol type configuration information is used to indicate a data transmission protocol between the second system and the first interface. Optionally, data transmission between the second system and the first interface needs to follow a data transmission protocol corresponding to the protocol configuration information. Wherein the data transmission protocol may be determined by the first system.

The request data type configuration information is used for indicating the data format of the request data sent by the second system to the first interface. Optionally, when the server generates the request data according to the call instruction, the format of the request data may be determined by the request data type configuration information, and then the encryption mode of the request data is determined according to the format of the request data, that is, when the docking configuration is performed, the request data encryption component needs to correspond to the request data type configuration information.

The response data type configuration information is used to indicate a data format of response data transmitted by the first interface to the second system. Optionally, the server may determine the data format of the response data according to the configuration information of the response data, and further determine the decryption manner of the response data according to the data format of the response data, that is, when performing docking configuration, the response data decryption component needs to correspond to the configuration information of the type of the response data. Of course, the server may also detect whether the acquired response data is sent by the first interface according to the response data type configuration information.

It should be noted that, the above description about the docking configuration information is only exemplary, and in practical applications, various types of configuration information may be added or subtracted according to actual situations. For example, the request field configuration information and the response field configuration information are generated on the premise that data between the first system and the second system cannot be identified, and if the data between the first system and the second system can be directly identified, the request field configuration information and the response field configuration information do not need to be generated during docking configuration.

Referring to fig. 3, a flowchart of an interface calling method according to an embodiment of the present application is shown. The method can be applied to the second system 20 of the interface docking system shown in fig. 1, for example, the execution subject of each step can be the user terminal 21 or the second server 22, and the second server 22 (hereinafter, referred to as "server" for short) is used as an example for description, the method can include the following steps (301-305):

step 301, a call instruction for a first interface in a first system is obtained.

Step 302, obtaining docking configuration information of the first interface.

Step 303, selecting n functional components from a pre-configured component library according to the docking configuration information.

The steps 301-.

Step 304, determining the running sequence of the n functional components.

Optionally, after the server acquires the n functional components, the server may determine an operation sequence of the n functional components, and then operate the n functional components according to the operation sequence to perform data processing, where the data may be request data in the call instruction, or may be request data acquired according to prompt information in the call instruction, where the prompt information is a manner of acquiring the request data.

In a possible embodiment, the server may determine the running order of the n functional components through a preconfigured flow component. The process component may be a pre-configured functional component stored in the server, and optionally, the user may determine a general operation sequence corresponding to each component according to each component possibly included in the docking configuration information, and generate and store the process component in the server according to the general operation sequence. In a possible embodiment, a server stores a flow component, and after acquiring the n functional components, the server can directly determine the running order of the n functional components through the preconfigured flow component; in another possible implementation, a server has stored therein a plurality of process components that can be, optionally, the plurality of flow components may be stored in a flow component library, each flow component having different identification information, optionally, the call instruction or the docking configuration information includes identification information of the flow component corresponding to the first interface, and after the server acquires the call instruction or the docking configuration information, the server may determine an operation sequence of n functional components corresponding to the first interface, and of course, in other possible cases, the server stores the mapping relationship between the flow components and the interfaces, and after obtaining the call instruction or the docking configuration information, the process components having a mapping relationship with the first interface may be determined, and the operation sequence of the n functional components corresponding to the first interface may be further determined. Alternatively, in the case where a plurality of flow components are included in the flow component library, the user may update the flow component library with irregular data to add a new flow component or delete a flow component with low usage and duplicate functions.

In another possible implementation manner, the server may determine an operation order of the n functional components according to order configuration information included in the docking configuration information, where the order configuration information is used to indicate the operation order of the n functional components. Alternatively, after the above docking configuration information is generated, the running order of the n functional components in the docking configuration information may be specified. After the server obtains the docking configuration information, n functional components may be selected from a preconfigured component library according to the docking configuration information, and further, an operation order of the n functional components is determined according to order configuration information in the docking configuration information.

Step 305, the n functional components are run based on the run order to call the first interface.

In this embodiment, after determining the running order of the n functional components, the server may run the n functional components based on the running order to call the first interface.

Optionally, the step 305 includes the following steps:

1. generating request data corresponding to the first interface;

2. converting the request data into request data which can be identified by the first system according to the request field configuration information to obtain the converted request data;

3. at least one functional component in the n functional components is operated according to the operation sequence, and the converted request data is processed to obtain processed request data;

4. sending the processed request data to a first interface;

5. receiving response data from the first interface;

6. at least one functional assembly in the n functional assemblies is operated according to the operation sequence, and the response data is processed to obtain processed response data;

7. and converting the processed response data into response data which can be recognized by the second system according to the configuration information of the response field.

In this embodiment of the application, after the server obtains the call instruction, the server may generate request data corresponding to the first interface according to the call instruction, and further, convert the request data according to the request field configuration information to obtain converted request data, where the converted request data may be directly identified by the first system. And then, according to the determined running sequence, running at least one functional component in the n functional components, processing the converted request data to obtain processed request data, wherein the processed request data can be encrypted request data, and sending the processed request data to the first interface.

Correspondingly, the first system generates response data after processing the processed request data, and sends the response data to the second system through the first interface. After receiving the response data, the second system runs at least one functional component of the n functional components according to the running sequence, processes the response data to obtain processed response data, wherein the processed response data may be decrypted response data obtained after verification, and further, the server converts the processed response data into response data recognizable by the second system according to the configuration information of the response field.

Illustratively, the docking call method of the present application is briefly described with reference to fig. 4. After receiving the call instruction 40, the server may generate request data 41 according to the call instruction 40 and the request data type configuration information, further convert the request data 41 according to the request field configuration information 42 to obtain converted request data that can be directly identified by the first system, encrypt the converted request data according to the request data encryption component 43 to obtain encrypted request data, and send the encrypted request data to the first system according to the protocol type configuration information 44. Correspondingly, after generating response data according to the encrypted request data, the first system sends the response data to the second system according to the first interface, further, according to the running sequence, the server verifies the response data according to the response data verification component 45, if the response data passes the verification, according to the response data decryption component 46, the response data is decrypted to obtain the decrypted response data, and then according to the response field configuration information 47, the decrypted response data is processed to obtain the processed response data which can be directly identified by the second system. In addition, in the above processing of the request data and the response data, the processing of the request data or the response data can be tracked and recorded by the log tracking component 48, wherein the log tracking component 48 comprises a first log tracking component and a second log tracking component.

It should be noted that the above description of the operation sequence of each component indicates an exemplary one, and in practical applications, the operation sequence of each component may be adjusted according to actual situations, for example, the request data is encrypted before being converted, or the request data is converted before being encrypted.

In summary, in the technical solution provided in the embodiment of the present application, the functional components are run through the determined running sequence to call the first interface, so that successful call of the first interface is ensured, and normal data interaction between the first system and the second system is ensured.

In addition, the running sequence of the functional components is determined according to the preconfigured flow components, so that excessive time consumed in determining the running sequence of the functional components is avoided, the operation is simple and convenient, and the time is saved.

In addition, the operation sequence of the functional components is determined while the docking configuration information is generated, the degree of freedom and flexibility of the operation sequence of the components are guaranteed, different operation sequences are determined for different operation components, and the accuracy of the operation of the components is guaranteed.

In addition, the request data is converted to obtain the data which can be directly identified by the first system, so that the identification time of the first system after obtaining the data is reduced, the processing time of the first system on the data is shortened, and the data interaction rate of the first system and the second system is improved; when the first system and the second system carry out data interaction, the transmission data are encrypted, so that the safety of data transmission is improved, and the data are prevented from being maliciously tampered in the transmission process.

In addition, the interface docking configuration information comprises configuration information of various functional components, data configuration information and a transmission protocol, so that the content contained in the interface docking configuration information is comprehensive, the calling success rate of the first interface is improved when the first interface can be successfully called, and the data transmission between the first system and the second system can be smoothly carried out.

Referring to fig. 5, a flowchart of an interface docking configuration method according to an embodiment of the present application is shown. The method can be applied to the configuration terminal 30 of the interface docking system shown in fig. 1, for example, the execution subject of each step can be the configuration terminal 30. The method comprises the following steps (501-504):

step 501, displaying an interface docking configuration page.

The interface docking configuration page is used for configuring docking configuration information of the interface, and optionally, the interface docking configuration page includes a component library configured in advance, and in a possible implementation, the server divides the component library into a plurality of component libraries, such as a log tracking component library, a request data encryption component library, a response data verification component library, and a response data decryption component library, according to different functions of various functional components. Illustratively, referring to fig. 6 in combination, various pre-configured component libraries are included in the interface docking configuration page 60, wherein the component libraries are divided into a first component library, a second component library, a third component library, … and an nth component library according to different functions of the various components, and different functional components are included in different component libraries.

In this embodiment of the application, the configuration terminal may display the interface docking configuration page after acquiring the opening instruction of the interface docking configuration page. The opening instruction can be generated by triggering the icon of the configuration page through the user clicking the interface.

Step 502, acquiring selection instructions for n functional components in the component library.

The selection instruction is used for indicating a functional component used by the second system for interfacing the first interface. Optionally, the selection instruction may be generated by a user clicking or dragging a component in the component library. In this embodiment of the application, after the configuration terminal displays the interface docking configuration page, the configuration terminal may obtain a selection instruction for n functional components of the component library in the interface docking page.

Optionally, in this embodiment of the present application, the functional components may include at least one of the following:

the first log tracking component is used for recording request data and response data transmitted between the second system and the first interface;

the request data encryption component is used for determining an encryption mode corresponding to the request data according to the type of the request data sent to the first interface by the second system;

the second log tracking component is used for recording the running condition of the second system after receiving the response data from the first interface;

a response data verification component for verifying response data received by the second system from the first interface;

and the response data decryption component is used for determining a decryption mode corresponding to the response data according to the type of the response data received by the second system from the first interface.

Optionally, after the configuration terminal obtains the selection finger, the configuration terminal may display icons corresponding to the n functional components in the interface docking configuration page. Illustratively, with combined reference to FIG. 6, the user displays the icon 61 of the responsive data check component A1 in the interface docking configuration page by clicking on the responsive data check component A1 in the first component library.

Step 503, generating docking configuration information for a first interface in a first system.

The docking configuration information is used to indicate a docking manner of the first interface, and optionally, the docking configuration information includes component configuration information used to indicate n functional components used by the second system to dock the first interface. In this embodiment of the application, the configuration terminal may generate corresponding docking configuration information according to the selection instruction of the n functional components.

It should be noted that, in this embodiment of the present application, for example, to ensure successful docking between the second system and the first interface, the docking configuration information further includes at least one of the following:

request field configuration information, which is used for determining a field conversion mode of request data sent to the first interface by the second system;

response field configuration information used for determining a field conversion mode of response data received by the second system from the first interface;

protocol type configuration information for indicating a data transmission protocol between the second system and the first interface;

request data type configuration information used for indicating the data format of the request data sent to the first interface by the second system;

response data type configuration information used for indicating the data format of response data sent by the first interface to the second system;

and the sequence configuration information is used for indicating the running sequence of the n functional components.

Optionally, in order to ensure the visualization of the configuration information, the interface docking configuration page may further include at least one of the following: the device comprises a request field configuration module, a response field configuration module, a protocol type configuration module, a request data type configuration module and a response data type configuration module. In a possible embodiment, the running sequence of each component is determined by a flow component preconfigured at the server side, in which case, the running sequence of each component may be displayed in the docking configuration page.

Illustratively, referring collectively to fig. 6, a request field configuration module 62, a response field configuration module 63, a protocol type configuration module 64, a request data type configuration module 65, and a response data type configuration module 66 are included in the docking configuration page 60. The user can click a selection button of the request field configuration module 62 to display a request field configuration interface 67, and in the request field configuration page 67, the user can select a request field corresponding to the request data and a response field corresponding to the response data to generate the request field configuration information; the request field configuration information may be generated by manually inputting a request field corresponding to the request data and a response field corresponding to the response data. In addition, the configuration method of each other module and the configuration method type of the request field configuration module 62 are not described herein again. Additionally, arrow icons may also be included in the interface docking configuration page 60 to indicate the order of execution of the various components or modules. It should be noted that since the positions of the respective components or modules are fixed in fig. 6, if it is not necessary to configure a certain component or module, a "/0" may be input at the position of the component or module.

In another possible implementation, the operation sequence of each component is determined by sequence configuration information generated in a docking configuration process, in this case, the docking configuration page may store the various modules into a module library, and a user clicks or drags each module in the module library to configure each module, so as to generate configuration information corresponding to each module.

Illustratively, with reference to FIG. 7 in conjunction, a first component library, a second component library, a third component library, and a module library are included in the interface docking configuration page 70. The user can display the icons of all the components and modules in the interface butt joint configuration page by clicking the components and modules in the first component library, the second component library, the third component library and the module library, and realize the configuration of the module by clicking the module icon to generate corresponding configuration information. In addition, the user can determine the operation order of the respective components by dragging or clicking the arrow icon 71, and generate the order configuration icon.

Step 504, sending docking configuration information to a server of the second system.

Optionally, in this embodiment of the application, after the configuration terminal generates the docking configuration information, the configuration terminal may send the docking configuration information to a server of the second system. In a possible implementation manner, in the selection process of configuring each component of the terminal, the docking configuration information may be sent to the server in real time; in another possible implementation, the configuration terminal may send docking configuration information to the server after the configuration of each component is completed.

Correspondingly, the server receives the docking configuration information. Optionally, after acquiring the docking configuration information, the server stores the docking configuration information. In a possible implementation manner, the docking configuration information includes indication information of the first interface, and the server may directly store the docking configuration information after acquiring the docking configuration information. In another possible embodiment, the docking configuration information does not include the indication information of the first interface, and the server may store the docking relationship between the docking configuration information and the indication information of the first interface while storing the docking configuration information.

By way of example, referring to fig. 8 in combination, a brief description of the first interface docking in the present application is that: the user determines the function or type of the first interface through the interface specification 81, performs component configuration on the first interface on the interface docking configuration page 82, generates interface docking information, and then introduces the flow component 83 to complete the docking of the first interface when calling the first interface. It should be noted that, if there is another interface between the first system and the second system, the docking step of the first interface may be repeated to complete the docking.

To sum up, in the technical scheme provided by the embodiment of the application, when the interface is configured in a butt joint mode, the functional component is selected from the component library to be configured, and the situation that development work is completed by directly writing codes when the interface is configured in a butt joint mode is avoided.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 9, a block diagram of an interface invoking device according to an embodiment of the present application is shown. The device has the function of realizing the interface calling method, and the function can be realized by hardware or by hardware executing corresponding software. The device may be a second server or a user terminal, or may be provided in the second server or the user terminal. The apparatus 900 may include: an instruction obtaining module 910, an information obtaining module 920, a component selecting module 930, and an interface calling module 940.

The instruction obtaining module 910 is configured to obtain a call instruction for a first interface in a first system.

An information obtaining module 920, configured to obtain docking configuration information of the first interface, where the docking configuration information includes component configuration information used to instruct a second system to dock n functional components used by the first interface, where n is a positive integer.

A component selecting module 930, configured to select n functional components from a preconfigured component library according to the docking configuration information.

An interface calling module 940, configured to run the n functional components to call the first interface.

In an exemplary embodiment, as shown in fig. 10, the interface calling module 940 includes: a sequence determination unit 941 and a component execution unit 942.

An order determination unit 941, configured to determine an operation order of the n functional components.

A component executing unit 942 configured to execute the n functional components based on the execution order to call the first interface.

In an exemplary embodiment, the component execution unit 942 is configured to generate request data corresponding to the first interface; running at least one functional assembly in the n functional assemblies according to the running sequence, and processing the request data to obtain processed request data; sending the processed request data to the first interface; receiving response data from the first interface; and operating at least one functional assembly in the n functional assemblies according to the operation sequence, and processing the response data to obtain processed response data.

In an exemplary embodiment, the sequence determining unit 941 is configured to determine an operation sequence of the n functional components through a preconfigured flow component; or determining the running sequence of the n functional components according to sequence configuration information included in the docking configuration information, where the sequence configuration information is used to indicate the running sequence of the n functional components.

In an exemplary embodiment, the docking configuration information further includes request field configuration information and response field configuration information, the request field configuration information is used to determine a field conversion manner of the request data, and the response field configuration information is used to determine a field conversion manner of the response data.

The component running unit 942 is further configured to convert the request data into request data that can be recognized by the first system according to the request field configuration information, so as to obtain converted request data; wherein, the converted request data is processed by at least one functional component in the n functional components to obtain the processed request data; and converting the processed response data into response data which can be recognized by the second system according to the configuration information of the response field.

In an exemplary embodiment, the n functional components include at least one of:

a first log tracking component for recording request data and response data transmitted between the second system and the first interface;

the second log tracking component is used for recording the operation condition of the second system after receiving the response data from the first interface;

In an exemplary embodiment, the docking configuration information further comprises at least one of:

request data type configuration information, which is used for indicating the data format of the request data sent to the first interface by the second system;

and the response data type configuration information is used for indicating the data format of the response data sent by the first interface to the second system.

In an exemplary embodiment, as shown in fig. 10, the apparatus 900 further comprises: a configuration acquisition module 950 and an information storage module 960.

A configuration obtaining module 950, configured to obtain the docking configuration information.

An information storage module 960, configured to store the docking configuration information.

Referring to fig. 11, a block diagram of an interface docking configuration apparatus according to an embodiment of the present application is shown. The device has the function of realizing the interface docking configuration method, and the function can be realized by hardware or by hardware executing corresponding software. The device can be a configuration terminal or be arranged at the configuration terminal. The apparatus 1100 may include: a page display module 1110, an instruction acquisition module 1120, an information generation module 1130, and an information transmission module 1140.

The page display module 1110 is configured to display an interface docking configuration page, where the interface docking configuration page includes a preconfigured component library.

An instruction obtaining module 1120, configured to obtain a selection instruction for n functional components in the component library, where n is a positive integer.

An information generating module 1130, configured to generate docking configuration information for a first interface in a first system, where the docking configuration information includes component configuration information indicating the n functional components used by a second system to dock the first interface.

An information sending module 1140, configured to send the docking configuration information to a server of the second system.

In an exemplary embodiment, the docking configuration information further includes request field configuration information and response field configuration information; the request field configuration information is used for determining a field conversion mode of request data sent by the second system to the first interface, and the response field configuration information is used for determining a field conversion mode of response data received by the second system from the first interface.

response data type configuration information for indicating a data format of response data sent by the first interface to the second system;

To sum up, in the technical scheme provided by the embodiment of the present application, when the interface is configured in a butt joint manner, the functional component is selected from the component library to be configured, so that the development work is avoided by directly writing codes when the interface is configured in a butt joint manner, and thus, when different interfaces are targeted, the multiplexing of the functional component can be realized, repeated development work is not required, and the time and labor cost of the interface butt joint development work are saved.

It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

Referring to fig. 12, a block diagram of a computer device 1200 according to an embodiment of the present application is shown. The computer device may be the user terminal 21 or the second server 22 shown in fig. 1, and the user terminal 21 or the second server 22 may implement the interface calling method; alternatively, the computer device may be a configuration terminal 30, which may implement the interface docking configuration method described above. Specifically, the method comprises the following steps:

the computer apparatus 1200 includes a Processing Unit (e.g., a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an FPGA (Field Programmable gate array), etc.) 1201, a system Memory 1204 including a RAM (Random Access Memory) 1202 and a ROM (Read Only Memory) 1203, and a system bus 1205 connecting the system Memory 1204 and the Central Processing Unit 1201. The computer device 1200 also includes a basic I/O system (Input/Output) 1206 to facilitate information transfer between various devices within the computer device, and a mass storage device 1207 for storing an operating system 1213, application programs 1214, and other program modules 1212.

The basic input/output system 1206 includes a display 1208 for displaying information and an input device 1209, such as a mouse, keyboard, etc., for a user to input information. The display 1208 and the input device 1209 are connected to the central processing unit 1201 through the input/output controller 1210 connected to the system bus 1205. The basic input/output system 1206 may also include an input/output controller 1210 for receiving and processing input from a number of other devices, such as a keyboard, mouse, or electronic stylus. Similarly, input-output controller 1210 also provides output to a display screen, a printer, or other type of output device.

The mass storage device 1207 is connected to the central processing unit 1201 through a mass storage controller (not shown) connected to the system bus 1205. The mass storage device 1207 and its associated computer-readable media provide non-volatile storage for the computer device 1200. That is, the mass storage device 1207 may include a computer-readable medium (not shown) such as a hard disk or a CD-ROM (Compact disk Read-Only Memory) drive.

Without loss of generality, the computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes RAM, ROM, EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash Memory or other solid state Memory technology, CD-ROM, DVD (Digital Video Disc) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage media is not limited to the foregoing. The system memory 1204 and mass storage device 1207 described above may be collectively referred to as memory.

The computer device 1200 may also operate as a remote computer connected to a network via a network, such as the internet, in accordance with embodiments of the present application. That is, the computer device 1200 may connect to the network 1212 through a network interface unit 1211 coupled to the system bus 1205, or may connect to other types of networks or remote computer systems (not shown) using the network interface unit 1211.

The memory stores a computer program which is loaded by the processor and realizes the interface calling method of the server side or the interface docking configuration method of the configuration terminal side.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium having stored thereon a computer program which, when executed by a processor of a server, implements the above-described interface calling method; alternatively, the computer program is configured to be executed by a processor of the terminal to implement the interface docking configuration method.

Optionally, the computer-readable storage medium may include: a Read Only Memory (ROM), a Random Access Memory (RAM), a Solid State Drive (SSD), or an optical disc. The Random Access Memory may include a resistive Random Access Memory (ReRAM) and a Dynamic Random Access Memory (DRAM).

In an exemplary embodiment, there is also provided a computer program product for performing the above interface call method when the computer program product runs on a server; when the computer program product runs on a configuration terminal, the interface docking configuration method is executed.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In addition, the step numbers described herein only exemplarily show one possible execution sequence among the steps, and in some other embodiments, the steps may also be executed out of the numbering sequence, for example, two steps with different numbers are executed simultaneously, or two steps with different numbers are executed in a reverse order to the order shown in the figure, which is not limited by the embodiment of the present application.

The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. An interface calling method, comprising:

acquiring a calling instruction aiming at a first interface in a first system;

and executing the n functional components to call the first interface.

2. The method of claim 1, wherein said executing the n functional components to invoke the first interface comprises:

determining the running sequence of the n functional components;

and executing the n functional components based on the running sequence to call the first interface.

3. The method of claim 2, wherein said executing the n functional components to invoke the first interface based on the execution order comprises:

generating request data corresponding to the first interface;

running at least one functional assembly in the n functional assemblies according to the running sequence, and processing the request data to obtain processed request data;

sending the processed request data to the first interface;

receiving response data from the first interface;

and operating at least one functional assembly in the n functional assemblies according to the operation sequence, and processing the response data to obtain processed response data.

4. The method of claim 2, wherein said determining an order of execution of said n functional components comprises:

determining an operating sequence of the n functional components through a preconfigured process component;

alternatively, the first and second electrodes may be,

determining the running sequence of the n functional components according to sequence configuration information included in the docking configuration information, wherein the sequence configuration information is used for indicating the running sequence of the n functional components.

5. The method according to claim 2, wherein the docking configuration information further includes request field configuration information and response field configuration information, the request field configuration information is used for determining a field conversion mode of the request data, and the response field configuration information is used for determining a field conversion mode of the response data;

after the generating of the request data corresponding to the first interface, the method further includes:

converting the request data into request data which can be identified by the first system according to the request field configuration information to obtain the converted request data; wherein, the converted request data is processed by at least one functional component in the n functional components to obtain the processed request data;

after the operating at least one of the n functional components according to the operating sequence and processing the response data to obtain processed response data, the method further includes:

and converting the processed response data into response data which can be recognized by the second system according to the configuration information of the response field.

6. The method of claim 1, wherein the n functional components include at least one of:

7. The method of claim 1, wherein the docking configuration information further comprises at least one of:

8. The method according to any one of claims 1 to 7, wherein before the obtaining the docking configuration information of the first interface, the method further comprises:

acquiring the docking configuration information;

storing the docking configuration information.

9. An interface docking configuration method, the method comprising:

sending the docking configuration information to a server of the second system.

10. The method of claim 9, wherein the n functional components include at least one of:

11. The method of claim 9, wherein the docking configuration information further comprises request field configuration information and response field configuration information;

the request field configuration information is used for determining a field conversion mode of request data sent by the second system to the first interface, and the response field configuration information is used for determining a field conversion mode of response data received by the second system from the first interface.

12. The method according to any of claims 9 to 11, wherein the docking configuration information further comprises at least one of:

13. An interface invocation apparatus, characterized in that said apparatus comprises:

14. An interface docking configuration apparatus, the apparatus comprising:

15. A computer device comprising a processor and a memory, the memory having stored therein a computer program that is loaded and executed by the processor to implement the interface call method of any of claims 1 to 8 or to implement the interface docking configuration method of any of claims 9 to 12.

16. A non-transitory computer-readable storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the interface call method according to any one of claims 1 to 8, or implements the interface docking configuration method according to any one of claims 9 to 12.