CN112988409A

CN112988409A - Interface calling method and device, computer equipment and storage medium

Info

Publication number: CN112988409A
Application number: CN201911307130.9A
Authority: CN
Inventors: 廖海龙
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2019-12-18
Filing date: 2019-12-18
Publication date: 2021-06-18
Anticipated expiration: 2039-12-18
Also published as: CN112988409B

Abstract

The embodiment of the application discloses an interface calling method and device, computer equipment and a storage medium. According to the method and the device, when the calling request information of the user is received, the legality of the calling request information can be checked in the service layer, and the calling request information is sent to the agent layer. And configuring a data object according to the calling request information in the proxy layer, calling a preset packaging plug-in according to the data object, acquiring an execution result of the preset packaging plug-in, and finally sending the execution result to a service layer for outputting. According to the scheme, the interface calling code is packaged into the plug-in which can be used for multiple times, so that the plug-in can be repeatedly used to adapt to different development environments, and the development efficiency can be improved.

Description

Interface calling method and device, computer equipment and storage medium

Technical Field

The embodiment of the application relates to the field of software development, in particular to an interface calling method and device, computer equipment and a storage medium.

Background

Remote Procedure Calls (RPCs) are basic functions of distributed services that transparently translate local solution calls into cross-machine calls based on a specific computer communication protocol. The remote procedure call is always a request sent by a client to a server, and the server executes a result according to the request and returns the result to the client, which may be referred to as a remote call hereinafter.

Remote invocation typically implements a transparent translation of the local approach to invocation across machines through calls to the interface. However, the conventional interface calling method generally includes the following steps: acquiring a proxy object requesting background service; assembling a request structure body object corresponding to the binary protocol; initiating an asynchronous request; and processing the calling exception and converting the calling exception into a json object. In the research and practice process of the prior art, the inventor of the embodiment of the application finds that the prior method exposes too many calling details, and meanwhile, the code does not separate interface logic and general logic, so that a large number of codes are repeatedly written in the calling process, the reusability of calling codes is poor, and the development efficiency is low.

Disclosure of Invention

The embodiment of the application provides an interface calling method and device, computer equipment and a storage medium.

In a first aspect, an embodiment of the present application provides an interface calling method, including:

receiving call request information of a user;

verifying the legality of the calling request information in a service layer;

sending the call request information to a proxy layer

Configuring a data object according to the calling request information in the proxy layer;

calling a preset packaging plug-in according to the data object;

acquiring an execution result of a preset packaging plug-in;

and sending the execution result to a service layer and outputting the execution result.

In one possible design, before the calling a predetermined package plug-in according to the data object, the method further includes:

determining the service type of the service to be processed according to the data object;

determining an interface to be called according to the service type;

acquiring a plurality of calling component templates according to the interface to be called;

and generating the preset packaging plug-in according to the calling component templates.

In one possible design, before the obtaining the plurality of calling component templates according to the interface to be called, the method further includes:

and constructing a calling component template according to the service type.

In one possible design, after the determining the service type of the service to be processed according to the data object, the method further includes:

judging whether the service type changes;

when the service type changes, determining the changed service type;

determining a calling component to be updated according to the changed service type;

and updating the calling component to be updated to a preset packaging plug-in.

In one possible design, the predetermined encapsulation plug-in is disposed at the proxy layer.

In one possible design, the configuring, at the proxy layer, a data object according to the call request information includes:

at the proxy layer, configuring a service name, a request structural body and a response structural body according to the calling request information;

and generating the data object according to the service name, the request structural body and the response structural body, wherein the data object is used for bearing data when the calling request information is requested or responded.

In one possible design, the calling a preset package plug-in according to the data object to obtain an execution result of the preset package plug-in includes:

assembling the packaged calling request information into a request structure body according to the data object and the preset packaging plug-in;

sending the request structure body to a server according to the preset packaging plug-in;

in the agent layer, according to the incidence relation between the service name and the telecommunication terminal service, calling an interface protocol service agent to the telecommunication terminal service;

acquiring a response structural body generated by the server based on the request structural body according to the preset packaging plug-in;

and analyzing the response structure according to the preset packaging plug-in, disassembling the response structure into a script object, and taking the script object as the execution result.

In one possible design, the method further includes:

and setting the service logic of each calling interface according to the service type in the service layer.

In one possible design, the execution result of the interface call is saved on a blockchain node.

In a second aspect, an embodiment of the present application further provides an interface calling apparatus, which has a function of implementing the interface calling method. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions, which may be software and/or hardware.

In one possible design, the interface calling device includes:

the input and output module is used for receiving the calling request information of a user;

the verification module is used for verifying the legality of the calling request information received by the input and output module in a service layer;

the input and output module is also used for sending the calling request information to an agent layer;

the processing module is used for configuring a data object according to the calling request information in the proxy layer; calling a preset packaging plug-in according to the data object; acquiring an execution result of a preset packaging plug-in through the input and output module; sending the execution result to a service layer through the input and output module and outputting the execution result;

in one possible design, before the calling a predetermined package plug-in according to the data object, the processing module is further configured to:

determining the service type of the service to be processed according to the data object; determining an interface to be called according to the service type of the service to be processed;

and generating the preset packaging plug-in according to the plurality of calling component templates.

In one possible design, before the obtaining, according to the interface to be called, a plurality of calling component templates, the processing module is further configured to:

and constructing a calling component template according to the service type.

In one possible design, after the determining the service type of the service to be processed according to the data object, the processing module is further configured to:

judging whether the service type changes;

when the service type changes, determining the changed service type;

and updating the calling component to be updated to a preset packaging plug-in.

In one possible design, the processing module is specifically configured to:

configuring a service name, a request structural body and a response structural body at the proxy layer according to the legal calling request information verified by the verification module;

and generating the data object according to the configured service name, the request structural body and the response structural body, wherein the data object is used for bearing data when the calling request information is requested or responded.

and generating a preset packaging plug-in according to the data object.

In one possible design, the processing module is specifically configured to:

In one possible design, the processing module is further configured to:

In a third aspect, an embodiment of the present application provides a computer device, which includes at least one connected transceiver, a memory and a processor, where the memory stores an application program, and the processor is configured to execute the application program in the memory to perform the method according to the first aspect.

In a fourth aspect, the present application provides a computer-readable storage medium storing a plurality of instructions, which are suitable for being loaded by a processor to execute the interface calling method in the above aspects.

Compared with the existing mechanism, when the calling request information of the user is received, the validity of the calling request information is verified through the service layer, and the calling request information is sent to the proxy layer. And configuring a data object according to the calling request information in the proxy layer, calling a preset packaging plug-in according to the data object, acquiring an execution result of the preset packaging plug-in, and finally sending the execution result to a service layer and outputting the execution result. According to the scheme, the interface calling code is packaged into the plug-in which the interface calling code can be used for multiple times, so that the calling details are packaged, the decoupling of general logic and interface logic is realized, the code redundancy is reduced, meanwhile, the plug-in can be reused to adapt to different development environments, and the development efficiency and the project code maintainability can be improved.

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. 1a is a schematic structural diagram of a hierarchical model in an interface calling method according to an embodiment of the present application;

FIG. 1b is a diagram illustrating a directory structure of a call interface in an embodiment of the present application;

fig. 2 is a flowchart of an interface calling method according to an embodiment of the present application;

fig. 3 is a schematic diagram illustrating that different service types generate a preset encapsulation plug-in an interface calling method according to an embodiment of the present application;

fig. 4 is a schematic diagram illustrating a preset package plugin generated when a service type is changed in an interface calling method according to an embodiment of the present application;

fig. 5 is a schematic diagram illustrating a preset encapsulation plugin generated when a service function is added in an interface calling method according to an embodiment of the present application;

fig. 6 is a schematic diagram illustrating a preset encapsulation plug-in generated when a service function is deleted in an interface calling method according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating a preset encapsulation plug-in generated when a service function is replaced in an interface calling method according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a block chain system to which a distributed system is applied in an interface calling method according to an embodiment of the present application

Fig. 9 is a schematic diagram of a block chain structure in an interface call method according to an embodiment of the present application

FIG. 10 is a schematic structural diagram of an interface invoking device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a computer device provided in an embodiment of the present application.

Detailed Description

The terms "first," "second," and the like in the description and in the claims of the embodiments of the application and in the drawings described above are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprise" and "have," and any variations thereof, are intended to cover non-exclusive inclusions, such that a process, method, system, article, or apparatus that comprises a list of steps or modules is not necessarily limited to those steps or modules expressly listed, but may include other steps or modules not expressly listed or inherent to such process, method, article, or apparatus, such that the division of modules presented in the present application is merely a logical division and may be implemented in a practical application in a different manner, such that multiple modules may be combined or integrated into another system or some features may be omitted or not implemented, and such that couplings or direct couplings or communicative connections shown or discussed may be through interfaces, indirect couplings or communicative connections between modules may be electrical or the like, the embodiments of the present application are not limited. Moreover, the modules or sub-modules described as separate components may or may not be physically separated, may or may not be physical modules, or may be distributed in a plurality of circuit modules, and some or all of the modules may be selected according to actual needs to achieve the purpose of the embodiments of the present application.

The embodiment of the application provides an interface calling method and device, computer equipment and a storage medium. The scheme can be applied to terminals such as smart phones and personal computers for calling background service interfaces, and the terminals in the embodiment of the application can be nodes of a block chain system. The following are detailed below.

Fig. 1a is a schematic structural diagram of a hierarchical model when a background service interface is called to obtain data in the embodiment of the present application. The layered model includes a calling interface, a service layer, a proxy layer, and a proxy service. The calling interface refers to a communication interface between the front-end platform and the background server, and can be used for receiving calling request information, and the behavior is usually triggered in a user interface component. The service layer mainly checks the validity of the parameters, and transmits legal common format parameters to the agent layer to obtain results. The agent layer defines an interface form (specifying an interface name and objects such as a request structure body/a response structure body of the interface), and completes interface parameter coding, response parameter decoding and exception handling through a preset packaging plug-in. The proxy service here refers to a service that receives call request information sent by a preset package plugin by a server and executes a call of a related service according to the call request information. Taking an example that a user accesses a third-party novel website, the hierarchical model shown in fig. 1a is applied to a transcoding reader to convert the third-party website into an access novel service. The transcoding reader can be constructed based on a hippy platform, and when the transcoding reader is used for accessing the novel service, the transcoding reader can be used for communicating with a background server side. Fig. 1b is a directory structure of a call interface used by the transcode reader.

In the existing mechanism, the interface calling method generally includes the following steps: acquiring a proxy object requesting background service; assembling a request structure body object corresponding to the binary protocol; initiating an asynchronous request; and processing the calling exception and converting the calling exception into a json object. This scheme exposes too many call details and does not encapsulate the call methods well. Meanwhile, in the prior art, the general service logic of the foreground and background communication interfaces is to realize the addition, deletion, modification and query of data, and the general logic is to make a communication link at the bottom layer, assemble a request structure of the interfaces, disassemble an interface response structure into a common object, perform exception handling and the like. However, the interface logic and the general logic are not separated in the existing mechanism, so that a large number of codes of the general logic are repeatedly written in the calling process to generate redundant codes, and the maintainability is poor.

In order to solve the above technical problem, the following scheme is adopted in the embodiment of the present application:

and separating the general logic from the service logic in a layered mode, setting the service logic of each calling interface according to the service type in the service layer, and paying attention to the service logic of the service layer. The general logic is extracted from the service layer and placed in the agent layer, so that the general logic can be prevented from being written repeatedly, and meanwhile, the general logic can be reused, and convenience is provided for business logic. Specifically, when call request information of a user is received, the validity of the call request information is checked in a service layer, and the call request information is sent to a proxy layer. And configuring a data object according to the calling request information in the proxy layer, calling a preset packaging plug-in according to the data object, acquiring an execution result of the preset packaging plug-in, and finally sending the execution result to a service layer for outputting. According to the scheme, the interface calling code is packaged into the plug-in which the interface calling code can be used for multiple times, so that the calling details are packaged, meanwhile, the plug-in can be reused to adapt to different development environments, and the development efficiency can be improved.

The embodiment of the application does not limit the implementation mode and the deployment mode of the plurality of hierarchical models.

In some embodiments, the relevant code for invoking the interface, service layer, proxy layer, and proxy service may be developed and then configured as a relatively independent hierarchy. In the process of the interface calling method, a calling interface is used for receiving calling request information, a service layer is used for checking the legality of the calling request information, a proxy layer is used for defining an interface form and acquiring an execution result, and proxy service is used for executing calling service contained in the calling request information.

As shown in fig. 2, after completing the deployment of the hierarchical model, a specific flow of the interface calling method in the embodiment of the present application may be as follows:

201. and receiving the calling request information of the user.

The call request message is generally triggered by a User through a User Interface (UI) component. In some embodiments, when the user is specific, the user may trigger an invoke request action at the user interface component, which is used to generate the invoke request information.

For example, a user accesses a novel reading web page, such as a red sleeve scented page, at a user interface of the mobile terminal. When the user clicks the collection button, the mobile terminal receives the calling request information through clicking. The received call request information comprises transcoding service, the server executes the transcoding service after receiving the call request information, converts the red sleeve perfuming page into a mobile terminal mode, and sends the red sleeve perfuming page to a service layer of the mobile terminal for outputting.

In some embodiments, the call request information may include an identification of the communication protocol, an application version number, a serialization manner, reserved bytes, a request Identification (ID), and the like.

In some embodiments, in order to reduce the influence of the server on the application terminal and the modification cost, a self-described serialization mode is selected in the data processing. For example, in the processing of the call request information, the service name, the method name, and the parameter type are used as attribute values of the java object, and then, serialization is performed by Hessian (binary serialization). For data that has a relationship to an attribute, for example, as the attribute value of a java object: and serializing data such as service names, method names, parameter types and the like. Therefore, the attribute values of the java objects are converted into binary streams in a self-descriptive serialization way.

For example, when a user browser page clicks to enter a microblog link, a request for invoking a microblog application is triggered at this time, the identifier of a communication protocol is 0xJ, which means that the communication protocol at this time is a data code (JCE) protocol, and the JCE protocol is a binary and custom protocol; the application version number is 01, and represents that the application version called by the current request is 01; the request identifier is fixed to be 01 and corresponds to the subsequent response information; the 02 field in the request message is called, and represents that the serialization way of the current request message is Hessian 02.

202. And verifying the legality of the calling request information in a service layer.

After receiving the call request information, the terminal verifies the information in the service layer to ensure that the received call request information is legal information, so that execution errors in a subsequent call flow are avoided. And when the verification result shows that the calling request information is illegal, the service layer generates calling error information on the user interface and receives the calling request information again. For example, the request ID in the invocation request message must contain only numbers, and the length of the request ID must conform to the protocol specification corresponding to the request ID. When the service layer checks and finds that the request ID contains characters except numbers, such as large/small-case letters, the checking result indicates that the calling request information is illegal calling request information, and the service layer generates calling error information to the user interface.

In some embodiments, the method further comprises:

By hierarchically isolating the service logic of the calling interface and the general logic, only the service logic needs to be concerned when software is developed, and the method is beneficial to project maintenance and interface development.

203. And sending the calling request information to a proxy layer.

Specifically, after the service layer checks the validity of the call request information, the call request information is sent to the proxy layer, so that the proxy layer executes subsequent operations according to the call request information.

For example, when a user clicks a music link on a microblog interface, a call request for starting a music application is triggered at the moment. The call request message will be verified by the service layer. And when the verification result shows that the calling request information is legal, the calling request information is sent to the proxy layer.

204. And configuring a data object according to the calling request information in the proxy layer.

And the data object is used for bearing data when the calling request information is requested or responded. The request structure is used for carrying data when requested, and the response structure is used for carrying data when responding. For example, when the access request is a request for acquiring a map of a southern mountain area, the server is triggered to call the corresponding service interface, and then call request information corresponding to the service interface is generated, parameters requested by a user for acquiring the map of the southern mountain area and data of the map of the southern mountain area to be returned to the user are carried in the response structure, and data such as a network address, a path field, a structure and the like required by the map of the southern mountain area are displayed.

In some embodiments, the data object is a json-formatted data object generated by the proxy layer, and is used for transmitting to the preset package plug-in, so as to initialize the preset package plug-in. The agent layer can pack the codes into independent files by generating the data objects in the json format, so that the codes are more convenient to debug and maintain, and the readability of the codes is improved. And after the calling request information is sent to the proxy layer, the proxy layer configures a data object according to the calling request information. Specifically, at the proxy layer, after receiving legal call request information, a service name, a request structure body and a response structure body are configured, and a data object in a json format is generated according to the configured service name, the request structure body and the response structure body. Because the data object is in the json format, the business data can be converted into the data in the json format through the data object in the json format and then returned to the terminal where the user is located.

For example, after receiving the call request information of the instant messaging tool for starting the map, the proxy layer configures a service name as the map according to the call request information, and configures a request structural body and a response structural body according to the call request information for starting the map. And finally, the agent layer generates a data object in json format corresponding to the start map.

205. And calling a preset packaging plug-in according to the data object.

The preset packaging plug-in is arranged on the proxy layer.

In some embodiments, the invoking a preset wrapper plug-in according to the data object includes:

For example, when the package plug-in is a wireless uni-protocol (WUP) plug-in, a WUP service proxy is called to a micro service Framework (TAF) service by a service name, and after data is acquired, a response structure is disassembled into a common js object. The intermediate result of this generic js object is available to the service layer via the WUP-proxy plug-in. The communication interface is based on the JCE protocol, which is the lowest part of the TAF framework. Each communication interface defines a request fabric and a response fabric based on the JCE protocol. The WUP service is called TAF service that a service provides a series of interfaces, a platform layer builds a WUP basic service, the incidence relation between the service name and the TAF service is set in the configuration of the WUP basic service, and the front end is proxied to the TAF service of the service through the service name and the WUP basic service. The TAF service is used for providing a service processing thread class so as to count various calling information reported by the service.

In other embodiments, before calling the preset package plug-in, the preset package plug-in should be generated according to the data object. Specifically, the proxy layer determines the service type of the service to be processed corresponding to the call request information according to the data object. After the service type of the service to be processed is obtained, determining a port to be called corresponding to the service type and a function corresponding to the port to be called according to the service type of the service to be processed. And the proxy layer acquires the calling component template according to the functions required by the interface to be called, and finally assembles the calling component templates to generate a preset packaging plug-in. Optionally, the calling component template is constructed in advance according to the service type.

Specifically, the calling component template pool can be constructed in advance according to the required functions corresponding to the service types. In the calling component template pool, different calling component templates, namely, a component A to a component H, are constructed corresponding to different functions. And acquiring components required to realize the service type according to different service types to be processed, and generating the components into a preset packaging plug-in.

For example, the correspondence between the service types and the component templates can be as shown in table 1 below.

TABLE 1

Referring to table 1, the following correspondence can be obtained: when the service type is service 1, the preset encapsulation plug-in corresponding to the service 1 comprises a component A, a component B, a component C and a component D, and the components are assembled to generate the preset encapsulation plug-in of the service 1; when the service type is service 2, the preset encapsulation plug-in corresponding to the service 2 comprises a component C, a component E, a component F and a component H, and the components are assembled to generate the preset encapsulation plug-in of the service 2.

In some embodiments, when the service type of the service to be processed changes, the preset encapsulation plug-in should change accordingly to adapt to the call requirement, which may be specifically expressed as: after determining the service type of the service to be processed according to the data object, judging the service type and confirming whether the service type changes. And when the service type is changed, determining the changed service type, and determining a calling component to be updated according to the changed service type. And finally updating the calling component to be updated into a preset packaging plug-in.

206. And acquiring an execution result of the preset packaging plug-in.

After the data object of which the proxy layer configuration is completed is obtained, the specific execution process of the preset encapsulation plug-in comprises the following steps: according to the data object, namely a request structure body, a response structure body and a service name of the proxy layer configuration interface, the call request information is packaged according to the generated json format data object, and the packaged call request information is assembled into a request structure body; and the assembled request structure body is proxied to the proxy service through the service name, finally, the response structure body sent after the data is obtained, namely the execution is finished is disassembled, and the final execution result is obtained and transmitted to the proxy layer. And the agent layer finally obtains the execution result of the preset packaging plug-in. Here, the proxy service may be understood as a service type included in the call request information executed by the server. The information transmission is based on a JCE protocol, and the JCE protocol is a self-defined protocol based on a binary system. The protocol is the bottom layer part of the framework, and each interface defines a request structural body and a response structural body to execute a calling process based on the JCE protocol.

207. And sending the execution result to a service layer and outputting the execution result.

And after the agent layer obtains the final execution result of the preset packaging plug-in, the agent layer sends the final execution result to the service layer and outputs the final execution result to obtain the final execution result.

For example, when the calling request information requests to start music, the mobile terminal sends the calling request information to a remote server through a preset packaging plug-in to obtain an execution result, and then the execution result is sent to a service layer. And the service layer outputs the final execution result after acquiring the final execution result, wherein the output result is the music application to be started finally.

In some embodiments, a schematic diagram of generating a preset encapsulation plug-in for different service types is shown in fig. 3. When the obtained service type is service 1, the components to be called corresponding to the service 1 comprise a component A, a component B, a component C and a component D, so that the component A, the component B, the component C and the component D are respectively obtained from a calling component template pool, and the preset packaging plug-in of the service 1 is assembled. When another service type is obtained and is service 2, the components needing to be called corresponding to the service 2 comprise a component E, a component F, a component H and a component C. Since component C is multiplexed for both service 1 and service 2 for component C in which the same function is implemented for two different service types, repeated development of code is reduced.

In some embodiments, when the service type is changed, if the function required to be implemented by the service is changed, the predetermined package plug-in for the service type may also be changed. As shown in fig. 4, the service type is service 1, and for the function to be implemented by service 1, the preset package plug-in of service 1 includes component a, component B, component C, and component D. When the service type is changed to service 3, the functions required for the service are changed at this time. For the functions to be implemented by the service 3, the components to be called are also changed. In order to ensure that calling of the original preset packaging plug-in is not influenced after the service type is changed into the service 3, the preset packaging plug-in is updated. Specifically, the service type is changed from service 1 to service 3, the function to be implemented by the changed service 3 is determined, and the changed component G, component F, component H, and component C are determined according to the function to be implemented by the service 3. And assembling the changed component G, component F, component H and component C into a preset packaging plug-in of the service 3. When the service type is changed to service 3, component C is multiplexed in the changed service 3, as compared to service 1.

In some embodiments, when a version changes, for example, when a service version deployed by a service layer is upgraded, functions that can be implemented before and after the upgrade for the same service type are different, and the specifically implemented function change may include addition of a function, deletion of a function, replacement of a function, and the like. Specifically, the service type is service 1, and the corresponding predetermined package plug-in includes component a, component B, component C, and component D. When the version is upgraded, three changes, namely addition, deletion or replacement, can occur to the functions required to be realized by the service 1.

1) When the function of service 1 is added, as shown in fig. 5.

When the service 1 is upgraded from the first version to the second version, a is a preset encapsulation plug-in of the service 1 of the first version, and b is a preset encapsulation plug-in of the service 1 of the second version. The service 1 adds a data processing function, and correspondingly adds a component with the data processing function in the preset packaging plug-in. For the first version of service 1, the components required for implementing the call function include component a, component B, component C, and component D. Because the service 1 of the second version is added with the data processing function, the original preset packaging plug-in is called for ensuring that the service 1 of the second version is not influenced by the addition of the data processing function part, and the service 1 can still normally call the preset packaging plug-in to update the preset packaging plug-in. Specifically, the function corresponding to the service 1 is changed, and a new data processing function can be realized. Determining a data processing function required to be realized by the upgraded service 1, determining a component E required to be added newly according to the realized data processing function, and assembling the newly added component E and an original preset packaging plug-in unit, thereby obtaining the preset packaging plug-in unit corresponding to the service 1 of the second version. The updated preset package plug-in comprises a component A, a component B, a component D, a component E and a component C. Compared with the service 1 before version upgrade, the service 1 after version upgrade is added with a component E. And adding the component E into the preset packaging plug-in of the service 1 to obtain the preset packaging plug-in of the service 1 after the version is upgraded.

2) When the function of service 1 is deleted, as shown in fig. 6.

When the service 1 is upgraded from the first version to the second version, a in fig. 6 is a preset package plug-in for the service 1 of the first version, and b is a preset package plug-in for the service 1 of the second version. The service 1 no longer needs to implement the voice function, and correspondingly deletes the component of the voice function in the preset package plug-in. Aiming at the service 1 of the first version, the components required for realizing the calling function comprise a component A, a component B, a component C and a component D, and because the service 1 of the second version deletes the voice function, the component C in the original preset package plug-in realizes the voice function. In order to ensure that the service 1 of the second version does not influence the calling of the original preset encapsulation plug-in due to the deletion of the voice function part, the service 1 can still normally call the preset encapsulation plug-in to update the plug-in. Specifically, the function corresponding to the service 1 changes, and the voice function is no longer realized. Determining the voice function deleted by the service 1 of the second version, determining a component C to be deleted according to the deleted voice function, and deleting the component C in the original preset packaging plug-in, thereby obtaining the preset packaging plug-in corresponding to the upgraded service 1. The upgraded preset package plug-in of the service 1 comprises a component A, a component B and a component D. The version upgraded service 1 deletes component C as compared to the version before upgrade. And deleting the component C from the preset packaging plug-in of the original service 1 to obtain the preset packaging plug-in of the service 1 with the upgraded version.

3) When replacing the function of service 1, as shown in fig. 7.

When the service 1 is upgraded from the first version to the second version, a in fig. 7 is a preset package plug-in for the service 1 in the first version, and b is a preset package plug-in for the service 1 in the second version. And improving the voice function of the service 1, and correspondingly replacing the components of the voice function in the preset packaging plug-in. Aiming at obligation 1 of the first version, components required for realizing calling function comprise a component A, a component B, a component C and a component D, and because the voice function of service 1 of the second version is improved, the component C in the original preset packaging plug-in realizes the voice function. In order to ensure that the upgraded service 1 does not influence the calling of the original preset package plug-in due to the improvement of the voice function part, the service 1 can still normally call the preset package plug-in to update the plug-in. Specifically, the function corresponding to the service 1 changes correspondingly, and the voice function in the original preset package plug-in is improved. Determining an improved voice function of the upgraded service 1, determining a component C to be replaced according to the improved voice function, and replacing the component C in the original preset package plug-in unit with a component E, so as to obtain the preset package plug-in unit corresponding to the upgraded service 1. The upgraded service 1 preset package plug-in includes a component a, a component B, a component D, and a component E. In the service 1 after version-up, the component C is replaced with the component E, compared to the service 1 before version-up. And replacing the component C in the original service 1 with the component E to obtain a preset packaging plug-in of the service 1 with the upgraded version.

Compared with the existing mechanism, when the calling request information of the user is received, the validity of the calling request information is checked in the service layer, and the calling request information is sent to the agent layer. And configuring a data object according to the calling request information in the proxy layer, calling a preset packaging plug-in according to the data object, acquiring an execution result of the preset packaging plug-in, and finally sending the execution result to a service layer for outputting. According to the scheme, the interface calling code is packaged into the plug-in which the interface calling code can be used for multiple times, so that the calling details are packaged, the decoupling of general logic and interface logic is realized, the code redundancy is reduced, meanwhile, the plug-in can be reused to adapt to different development environments, and the development efficiency and the project code maintainability can be improved.

The plurality of mobile terminals in the embodiment of the present application may form a system based on a communication protocol. The system related to the embodiment of the application can be a distributed system formed by connecting a client, a plurality of nodes (any form of computing equipment in an access network, such as a server and a user terminal) through a network communication mode.

Taking a distributed system as an example of a blockchain system, referring To fig. 8, fig. 8 is an optional structural schematic diagram of the distributed system 800 applied To the blockchain system provided in this embodiment of the present application, and is formed by a plurality of nodes (computing devices in any form in an access network, such as servers and user terminals) and clients, a Peer-To-Peer (P2P) network is formed between the nodes, and the P2P Protocol is an application layer Protocol operating on a Transmission Control Protocol (TCP) Protocol. In a distributed system, any machine, such as a server or a terminal, can join to become a node, and the node comprises a hardware layer, a middle layer, an operating system layer and an application layer.

Referring to the functions of each node in the blockchain system shown in fig. 8, the functions involved include:

1) routing, a basic function that a node has, is used to support communication between nodes.

Besides the routing function, the node may also have the following functions:

2) the application is used for being deployed in a block chain, realizing specific services according to actual service requirements, recording data related to the realization functions to form recording data, carrying a digital signature in the recording data to represent a source of task data, and sending the recording data to other nodes in the block chain system, so that the other nodes add the recording data to a temporary block when the source and integrity of the recording data are verified successfully.

For example, the services implemented by the application include:

2.1) a service layer for checking the validity of the call request information received from other nodes; when the check result is legal, sending the check result to other nodes in the block chain system; and generating error information when the verification result is illegal.

2.2) a proxy layer for configuring the service name, the request structure body and the response structure body, generating the data object and sending the generated data object to other nodes in the block chain system.

And 2.3) the preset packaging plug-in is used for assembling the received calling request information into a request structural body and sending the request structural body to the server, receiving a response structural body executed by the server and disassembling the response structural body to generate a json object, and acquiring the execution result of the final calling request.

3) And the block chain comprises a series of blocks (Bloc k) which are connected with each other according to the generated chronological order, new blocks cannot be removed once being added into the block chain, and the blocks record the record data submitted by the nodes in the block chain system.

Referring to fig. 9, fig. 9 is an optional schematic diagram of a Block Structure (Block Structure) provided in this embodiment, where each Block includes a hash value of a transaction record stored in the Block (hash value of the Block) and a hash value of a previous Block, and the blocks are connected by the hash value to form a Block chain. The block may include information such as a time stamp at the time of block generation. A block chain (Blockchain), which is essentially a decentralized database, is a string of data blocks associated by using cryptography, and each data block contains related information for verifying the validity (anti-counterfeiting) of the information and generating a next block.

Any technical feature mentioned in the embodiment corresponding to any one of fig. 1a to 7 is also applicable to the embodiment corresponding to fig. 10 and 11 in the present application, and the details of the subsequent similarities are not repeated.

The above describes an interface calling method in the embodiment of the present application, and a device for executing the interface calling method in the implementation of the present application is introduced below.

Referring to fig. 10, a schematic structural diagram of an interface calling apparatus shown in fig. 10 is shown, where the interface calling apparatus can be applied to front-end development and calling a background interface. The apparatus in the embodiment of the present application can implement the steps corresponding to the interface calling method executed in the embodiment corresponding to fig. 2. The functions realized by the device can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above functions, which may be software and/or hardware. The apparatus may include an input/output module 1001, a checking module 1002 and a processing module 1003, and the interface calling apparatus may perform the steps in the interface calling method as performed in the embodiment corresponding to fig. 2, as follows:

an input/output module 1001 configured to receive call request information of a user;

wherein the call request information is typically triggered by the user through a user interface component. Specifically, a user may trigger a call request behavior in a user interface component, where the call request behavior includes call request information, and the input/output module 1001 receives the call request information.

In some embodiments, the invocation request information may include an identification of the communication protocol, an application version number, a request identification, a serialization manner, reserved bytes, a request ID, and the like.

A checking module 1002, configured to check validity of the call request information received by the input/output module at a service layer;

after the verification module 1002 verifies the validity of the call request information received by the input/output module, the input/output module 1001 is further configured to send the call request information to the processing module 1003, so that the processing module 1003 executes subsequent operations according to the call request information.

And the processing module 1003 is configured to configure a data object according to the call request information. Specifically, after receiving the legitimate call request information verified by the verification module 1002, the processing module 1003 configures a service name, a request structure and a response structure, and generates a data object in json format according to the configured service name, request structure and response structure.

Before the calling of the preset package plug-in according to the data object, the processing module 1003 is further configured to generate the preset package plug-in according to the data object. Specifically, the processing module 1003 determines the service type of the service to be processed corresponding to the invocation request information according to the data object. After the service type of the service to be processed is obtained, determining an interface to be called according to the service type of the service to be processed, obtaining a plurality of calling component templates according to the interface to be called, and finally assembling the calling component templates to generate a preset packaging plug-in. The calling component template is constructed in advance according to the service type.

After the data object is configured, the processing module 1003 calls a preset encapsulation plug-in according to the data object; acquiring an execution result of a preset package plug-in through the input and output module 1001; and sending the execution result to a service layer through the input/output module 1001 and outputting the execution result.

In some embodiments, the processing module 1003 is further configured to construct a calling component template according to the service type before the obtaining of the multiple calling component templates according to the interface to be called.

Wherein, the specific execution process of the preset package plug-in includes: according to the data object, namely a request structure body, a response structure body and a service name of a configuration interface of the processing module 1003, packaging the calling request information according to the generated json format data object, and assembling the packaged calling request information into a request structure body; the assembled request structure is proxied to the proxy service through the service name, the response structure sent after the data is finally obtained, namely the execution is completed, the received response structure is disassembled, the final execution result is obtained, and the final execution result is transmitted to the processing module 1003. The processing module 1003 finally obtains an execution result of the preset package plug-in.

Compared with the existing mechanism, in the embodiment of the present application, the processing module 1003 logically extracts the predetermined package plug-in from the calling code. When receiving the call request information through the input/output module 1001, the processing module sends the call request information to the server through the preset package plug-in, and obtains a final execution result and outputs the final execution result through the input/output unit. According to the scheme, the interface calling codes are packaged into the plug-in capable of being used for multiple times, so that the calling details are packaged, the processing module 1003 can repeatedly use the packaged preset packaging plug-in, decoupling of general logic and interface logic is achieved, code redundancy is reduced, meanwhile, the plug-in can be repeatedly used to adapt to different development environments, and development efficiency and project code maintainability can be improved.

The interface calling device in the embodiment of the present application is described above from the perspective of the modular functional entity, and the interface calling device in the embodiment of the present application is described below from the perspective of hardware processing. The embodiment of the present application further provides a computer device, as shown in fig. 11, which shows a schematic structural diagram of a computer device designed by the present application, specifically:

fig. 11 is a schematic structural diagram of a computer device provided in an embodiment of the present application, which may have a relatively large difference due to different configurations or performances, and may include one or more processors 1103 (e.g., one or more central processing units) and a memory 1102 (e.g., one or more mass storage devices). Wherein memory 1102 may be transient or persistent. The program stored in memory 1102 may include one or more modules (not shown), each of which may include a sequence of instructions operating on a server. Still further, the processor 1103 may be arranged in communication with the memory 1102 to execute a series of instruction operations in the memory 1102 on the computer device.

The computer device may also include one or more input-output units 1101; although not shown, the computer device may also include one or more power supplies, one or more wired or wireless network interfaces, and/or one or more operating systems, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, etc., which are not described in detail herein. The steps performed by the computer device in the above embodiments may be based on the computer device structure shown in fig. 11. Specifically, in this embodiment, the processor 1103 in the computer device loads an executable file corresponding to a process of one or more application programs into the memory 1102 according to the following instructions, and the processor 1103 runs the application programs stored in the memory 1102, thereby implementing various functions as follows:

receiving call request information of a user through the input-output unit 1101; verifying the legality of the calling request information; configuring a data object according to the calling request information; calling a preset packaging plug-in according to the data object; acquiring an execution result of a preset packaging plug-in; the execution result is output through the input-output unit 1101.

It should be noted that, in the embodiment of the present application, the apparatus shown in fig. 10 may have the structure shown in fig. 11, an entity device corresponding to the input/output module 1001 in the embodiment of fig. 10 may be the input/output unit 1101, and an entity device corresponding to the verification module 1002 and the processing module 1003 in the embodiment of fig. 10 may be the processor 1103. The input/output unit 1101 and the processor 1103 can implement the same or similar functions of the input/output module 1001, the verification module 1002 and the processing module 1003 provided in the foregoing embodiment of the apparatus corresponding to the apparatus, and the memory 1102 stores a computer program that needs to be called when the processor executes the interface calling method.

In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.

It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the module described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the embodiments of the present application, it should be understood that the disclosed method, apparatus, and computer device may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is merely a logical division, and in actual implementation, there may be other divisions, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.

The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.

In addition, functional modules in the embodiments of the present application may be integrated into one processing module, or each module may exist alone physically, or two or more modules are integrated into one module. The integrated module can be realized in a hardware mode, and can also be realized in a software functional module mode. The integrated module, if implemented in the form of a software functional module and sold or used as a stand-alone product, may be stored in a computer readable storage medium.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.

The computer program product includes one or more computer instructions. The procedures or functions described in accordance with the embodiments of the present application are generated in whole or in part when the computer program is loaded and executed on a computer. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

The technical solutions provided by the embodiments of the present application are introduced in detail, and the principles and implementations of the embodiments of the present application are explained by applying specific examples in the embodiments of the present application, and the descriptions of the embodiments are only used to help understanding the method and core ideas of the embodiments of the present application; meanwhile, for a person skilled in the art, according to the idea of the embodiment of the present application, there may be a change in the specific implementation and application scope, and in summary, the content of the present specification should not be construed as a limitation to the embodiment of the present application.

Claims

1. An interface calling method, comprising:

receiving call request information of a user;

verifying the legality of the calling request information in a service layer;

sending the calling request information to a proxy layer;

calling a preset packaging plug-in according to the data object;

acquiring an execution result of the preset packaging plug-in;

and sending the execution result to the service layer and outputting the execution result.

2. The method of claim 1, wherein prior to said invoking a pre-defined wrapper plug-in from said data object, said method further comprises:

determining an interface to be called according to the service type;

and generating a preset packaging plug-in according to the calling component templates.

3. The method of claim 2, wherein prior to said obtaining a plurality of calling component templates from the interface to be called, the method further comprises:

and constructing a calling component template according to the service type.

4. The method of claim 2, wherein after the determining the traffic type of the traffic to be processed according to the data object, the method further comprises:

judging whether the service type changes;

when the service type changes, determining the changed service type;

and updating the calling component to be updated to a preset packaging plug-in.

5. The method according to any one of claims 1 to 4, wherein said configuring, at the proxy layer, a data object according to the call request information comprises:

6. The method according to claim 5, wherein the calling a predetermined package plug-in according to the data object to obtain the execution result of the predetermined package plug-in comprises:

assembling the calling request information into a request structure body according to the data object and the preset packaging plug-in;

7. The method of claim 1, further comprising:

8. The method of claim 1, wherein the result of the execution of the interface call is saved on a blockchain node.

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

the processing module is used for configuring a data object according to the calling request information in the proxy layer; calling a preset packaging plug-in according to the data object; acquiring an execution result of the preset packaging plug-in through the input and output module; and sending the execution result to a service layer through the input and output module and outputting the execution result.

10. A computer device comprising a transceiver, a memory, and a processor; the memory stores an application program, and the processor is configured to execute the application program in the memory to perform the operation of the interface calling method according to any one of claims 1 to 8.