CN113381866A

CN113381866A - Service calling method, device, equipment and storage medium based on gateway

Info

Publication number: CN113381866A
Application number: CN202010115998.5A
Authority: CN
Inventors: 张凡; 陈喆
Original assignee: Beijing Tongbang Zhuoyi Technology Co ltd
Current assignee: Beijing Tongbang Zhuoyi Technology Co ltd
Priority date: 2020-02-25
Filing date: 2020-02-25
Publication date: 2021-09-10
Anticipated expiration: 2040-02-25
Also published as: CN113381866B

Abstract

The application provides a gateway-based service calling method, device, equipment and storage medium, and relates to the technical field of computers. The method comprises the steps of receiving a service calling request which is sent by a target application and requests to call a target interface service, determining the target interface service and parameter information of the target interface service according to the service calling request and user configuration data which are loaded in advance, and calling the target interface service according to the parameter information of the target interface service. According to the technical scheme, the relevant parameters of the target interface service can be obtained by using the pre-loaded user configuration data, the gateway does not need to be restarted, the problem that the user cannot use the gateway due to shutdown of the gateway is avoided, and the use experience of the user is improved.

Description

Service calling method, device, equipment and storage medium based on gateway

Technical Field

The present application relates to the field of computer technologies, and in particular, to a method, an apparatus, a device, and a storage medium for calling a service based on a gateway.

Background

At present, the novel micro-service three-layer system architecture in the internet industry comprises: a service layer, a business logic bus layer and a gateway layer. The service layer realizes a certain vertical module service, the service logic bus layer realizes service combination, and the gateway layer needs to execute protocol conversion aiming at different communication protocols existing in each application scene so as to realize data information acquisition.

In the prior art, a gateway layer performs protocol conversion by using a Remote Procedure Call (RPC) technology, so that a computer can request a service from a Remote computer program through a network without knowing an underlying network technology on the premise that the gateway layer holds a next-end transmission object.

However, when the gateway layer executes protocol conversion each time, it is necessary to hold a transmission object of the next end, so that when a new interface accesses the gateway layer, it is necessary to implement protocol conversion and message mapping of the corresponding interface in the form of writing codes, and update the data of the gateway by restarting the gateway, which has a problem that the user cannot access due to shutdown of the gateway.

Disclosure of Invention

The application provides a service calling method, device, equipment and storage medium based on a gateway, which aim to solve the problem that a user cannot access the existing gateway due to the fact that the gateway needs to be shut down in a protocol conversion process.

In a first aspect, a method for calling a service based on a gateway provided by the present application includes:

acquiring a service calling request sent by a target application, wherein the service calling request is used for requesting to call a target interface service;

determining the target interface service and the parameter information of the target interface service according to the service calling request and the pre-loaded user configuration data;

and calling the target interface service according to the parameter information of the target interface service.

In this embodiment, the pre-loaded user configuration data is utilized to obtain the relevant parameters of the target interface service, and the gateway does not need to be restarted, so that the problem that the user cannot use the gateway due to shutdown of the gateway is avoided, and the use experience of the user is improved.

In a possible design of the first aspect, before the obtaining a service invocation request issued by a target application, the method further includes:

obtaining configuration parameters for the target interface service, the configuration parameters being determined by the type of the target interface service;

configuring the gateway based on the configuration parameters;

and acquiring the user configuration data loaded when the gateway runs.

In this embodiment, before receiving the service invocation request, the configuration information of the target interface service is acquired and the gateway is configured, so that the implementation possibility is provided for subsequently executing the invocation of the target interface service.

In the foregoing possible design of the first aspect, the obtaining the configuration parameter for the target interface service includes:

acquiring an interface service transmission packet imported in a preset mode;

determining an analysis mode of the interface service transmission packet according to the preset mode;

and analyzing the interface service transmission packet by utilizing the analysis mode to obtain the configuration parameters aiming at the target interface service.

In this embodiment, through the configuration interface, the configuration information of the target interface service required by the gateway is written into the gateway of the electronic device in a configuration form, so that hot deployment of the target interface service is realized when the gateway runs.

Optionally, the preset mode is one of the following modes: an Excel import mode, an interface configuration mode and a jar package import mode.

As an example, if the preset manner is an Excel import manner, the obtaining an interface service transport packet imported by the preset manner includes:

determining a pre-configured Excel template, wherein the Excel template comprises: the target interface serves a plurality of configuration items of the corresponding interface;

acquiring the interface service transmission packet through a lead-in interface on a configuration interface, wherein the interface service transmission packet is obtained by updating field information of a fixed position in the Excel template by a user according to a plurality of configuration items of the target interface service;

the analyzing the interface service transmission packet by using the analysis mode to obtain the configuration parameters aiming at the target interface service comprises the following steps:

and acquiring configuration parameters aiming at the target interface service from the interface service transmission package according to the field information of the fixed position in the Excel template.

In the embodiment, the interface service transmission packet is acquired in the Excel import mode and analyzed in the corresponding analysis mode, so that the acquisition of the configuration parameters is realized, and the implementation mode is simple and easy to realize.

As another example, if the preset mode is an interface configuration mode, the acquiring an interface service transmission packet imported in the preset mode includes:

acquiring an interface service transmission packet imported by a user through operation on a configuration interface, wherein the operation on the configuration interface comprises the following steps: configuring or modifying configuration parameters of the target service interface;

and acquiring configuration parameters aiming at the target interface service from the configuration interface.

According to the embodiment, the configuration parameters of the target interface service are acquired through the configuration interface importing mode, and the configuration interface is directly operated, so that the implementation is easy, and the importing efficiency is improved.

As another example, if the preset mode is a jar packet import mode, the obtaining an interface service transmission packet imported by the preset mode includes:

acquiring the interface service transmission packet generated by a provider to which the target interface service belongs through a configuration interface, wherein the interface service transmission packet comprises a transmission object with a custom note, the custom note is positioned at a specific position of the transmission object, and the custom note is used for explaining a field or a class in the transmission object;

and acquiring configuration parameters aiming at the target interface service according to the custom annotation and a Java reflection mechanism.

In the embodiment, the transmission parameters can be uploaded to the management platform in a mode of adding custom annotations to the transmission parameters, so that uploading of the configuration parameters can be realized, and a foundation is laid for obtaining user configuration data by loading in the subsequent gateway operation.

As another example, the obtaining of the interface service transport packet imported in the preset manner includes:

and acquiring the interface service transmission packet from the registration center of the target interface service.

In another possible design of the first aspect, before the configuring the gateway based on the configuration parameter, the method further includes:

and checking the configuration parameters, and determining that the configuration parameters pass the check.

The configuration parameters are verified, and the gateway is configured by the verified configuration parameters, so that the accuracy of the gateway for providing the service can be improved.

In a second aspect, the present application provides a gateway-based service invocation apparatus, including: the system comprises an acquisition module, a processing module and a calling module;

the acquisition module is used for acquiring a service calling request sent by a target application, and the service calling request is used for requesting to call a target interface service;

the processing module is used for determining the target interface service and the parameter information of the target interface service according to the service calling request and the user configuration data loaded in advance;

the calling module is used for calling the target interface service according to the parameter information of the target interface service.

In a possible design of the second aspect, the obtaining module is further configured to obtain a configuration parameter for the target interface service before obtaining a service call request issued by a target application, where the configuration parameter is determined by a type of the target interface service;

the processing module is further configured to configure the gateway based on the configuration parameter;

the obtaining module is further configured to obtain the user configuration data loaded during the gateway operation.

In the above possible design of the second aspect, the obtaining module includes: an acquisition unit and a processing unit;

the acquisition unit is used for acquiring the interface service transmission packet imported in a preset mode;

and the processing unit is used for determining an analysis mode of the interface service transmission packet according to the preset mode, and analyzing the interface service transmission packet by using the analysis mode to obtain the configuration parameters aiming at the target interface service.

As an example, if the preset manner is an Excel import manner, the obtaining unit is specifically configured to:

the processing unit is specifically configured to obtain configuration parameters for the target interface service from the interface service transport packet according to the field information of the fixed position in the Excel template.

As another example, if the preset mode is an interface configuration mode, the obtaining unit is specifically configured to obtain an interface service transmission packet imported by a user through an operation performed on a configuration interface, where the operation performed on the configuration interface includes: configuring or modifying configuration parameters of the target service interface;

the processing unit is specifically configured to acquire, from the configuration interface, configuration parameters for the target interface service.

As another example, if the preset manner is a jar packet import manner, the obtaining unit is specifically configured to obtain, through a configuration interface, the interface service transmission packet generated by a provider to which the target interface service belongs, where the interface service transmission packet includes a transmission object with a custom annotation, the custom annotation is located at a specific position of the transmission object, and the custom annotation is used to interpret a field or a class in the transmission object;

the processing unit is specifically configured to obtain configuration parameters for the target interface service according to the custom annotation and a reflection mechanism of Java.

As another example, the obtaining unit is specifically configured to obtain the interface service transport packet from a registry of the target interface service.

In another possible design of the second aspect, the processing module is further configured to check the configuration parameter before configuring the gateway based on the configuration parameter, and determine that the configuration parameter passes the check.

The apparatus provided in the second aspect of the present application may be configured to perform the method provided in the first aspect, and the implementation principle and the technical effect are similar, which are not described herein again.

In a third aspect, embodiments of the present application further provide an electronic device, which includes a processor, a memory, and a computer program stored in the memory and executable on the processor, and the processor executes the computer program to implement the method according to the first aspect and possible designs.

In a fourth aspect, embodiments of the present application further provide a computer-readable storage medium, in which computer instructions are stored, and when the computer instructions are executed on a computer, the computer is caused to execute the method according to the first aspect and each possible design.

According to the gateway-based service calling method, device, equipment and storage medium provided by the embodiment of the application, when a service calling request which is sent by a target application and requests to call a target interface service is received, the target interface service and the parameter information of the target interface service are determined according to the service calling request and user configuration data which are loaded in advance, and then the target interface service is called according to the parameter information of the target interface service. According to the technical scheme, the relevant parameters of the target interface service can be obtained by using the pre-loaded user configuration data, the gateway does not need to be restarted, the problem that the user cannot use the gateway due to shutdown of the gateway is avoided, and the use experience of the user is improved.

Drawings

Fig. 1 is a schematic view of an application scenario of a gateway-based service invocation method according to an embodiment of the present application;

fig. 2 is a schematic flowchart of a first embodiment of a gateway-based service invocation method provided in the embodiment of the present application;

fig. 3 is a schematic flowchart of a second embodiment of a gateway-based service invocation method provided in the embodiment of the present application;

fig. 4 is a schematic flowchart of a third embodiment of a gateway-based service invocation method provided in the embodiment of the present application;

FIG. 5 is a schematic diagram of an interface service transport package obtained by an Excel import mode;

FIG. 6 is a schematic diagram of obtaining an interface service transport packet by interface configuration;

fig. 7 is a schematic structural diagram of an embodiment of a gateway-based service invocation apparatus according to an embodiment of the present application;

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

Detailed Description

In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.

Before the technical solution of the present application is introduced, the terms referred to in the embodiments of the present application are explained first:

(1) RPC protocol: remote Procedure Call (RPC) protocol, a protocol that requests services from Remote computer programs over a network without knowledge of the underlying network technology;

(2) protocol conversion: protocol conversion refers to a process of converting a standard or protocol between one device or system cluster into a protocol suitable for another device or system, in order to enable interoperation between different protocols;

(3) jar package: JAR (Java ARchive) is a platform-independent file format that can synthesize multiple files into one file;

(4) JAVA reflection: the JAVA reflection mechanism is that in a running state, all the attributes and methods of any class can be known; for any object, any method and attribute of the object can be called; this function of dynamically acquiring information and dynamically invoking object methods is referred to as the reflection mechanism of the java language.

(5) The registration center: the registry can be said to be an "address book" in the micro-service architecture, and records the mapping relationship between services and service addresses. In a distributed architecture, services are registered, and when the services need to call other services, the addresses of the services are found and called.

(6) Thermal deployment: hot deployment is the upgrading of software while an application is running, without requiring the application to be restarted.

Before the technical solution of the present application is described below, an application scenario of the technical solution of the present application is first described. Fig. 1 is a schematic view of an application scenario of a gateway-based service invocation method according to an embodiment of the present application. Referring to fig. 1, the application scenario includes: a Uniform Resource Locator (URL) distributor, a gateway cluster (including a synchronous gateway 1 to a synchronous gateway n), an Application Programming Interface (API) gateway console, an API configuration library, a registry, and an internal service system.

The URL distributor is used for receiving a service calling request sent by an external application and distributing the service calling request to one synchronous gateway in the gateway cluster. Optionally, the external application communicates with the URL distributor via a hypertext transfer protocol secure (HTTPS) protocol.

For example, in the application scenario shown in fig. 1, each synchronization gateway in the gateway cluster may have functions of synchronization API transceiving, API security verification, protocol conversion, fuse throttling, error control, and the like. Optionally, each synchronization gateway and the internal service system may communicate in any one of JFS, Dubbo, or hypertext transfer protocol (HTTP). Wherein, JFS and Dubbo are both Java-based high-performance RPC distributed service-oriented frameworks (SOAs).

Referring to fig. 1, the gateway cluster is further connected to a registration center, where the registration center is configured to receive registration request information sent by the gateway cluster and record a mapping relationship between a service and a service address. Optionally, the registry further provides functions such as authorization, monitoring, load balancing, caching, request deployment and management, and dynamic response processing. The registry is used for managing service addresses, defining services, selecting services and executing service policies.

Optionally, the API gateway console is connected to the gateway cluster and the API configuration library, and the API gateway console is configured to manage and control information of the synchronous gateway in the gateway cluster. The API configuration library is used for storing relevant information of the interface service.

It should be noted that fig. 1 is only a schematic diagram of an application scenario provided by an embodiment of the present application, and a positional relationship between components shown in fig. 1 does not constitute any limitation. The execution main body of this embodiment may be an electronic device, which is specifically a server, and may also be a processing platform at a back end. The specific implementation of the electronic device may be determined according to actual situations, and will not be described herein.

At this stage, the micro service architecture is a framework that a single application is developed as a suite of many small services. The small services are built around business functions, each service can be written by different programming languages and uses different data storage technologies, and independent deployment is realized by means of an automatic deployment mechanism.

Optionally, the micro service architecture may include three layers of architectures, such as a service layer, a service logic bus layer, and a gateway layer. The gateway layer is the part with the minimum dependence on the service, even can completely not depend on the service, and only needs to concentrate on some technical characteristics of the gateway, such as the forbidden level, the login state verification, the authority verification, the protocol forwarding, the protocol conversion and the like.

In practical application, the gateway layer may further perform protocol conversion for different communication protocols existing in each application scenario to achieve data information acquisition. In the prior art, a gateway layer executes protocol conversion through an RPC technology, but the gateway layer needs to hold a next-end transmission object, and at this time, protocol conversion and message mapping of a corresponding interface are usually realized in a form of writing codes, which results in that the gateway needs to be updated in a way of restarting the gateway, and problems of shutdown of the gateway, incapability of accessing by a user, and poor user experience exist.

In view of the above problems, an embodiment of the present application provides a gateway-based service invoking method, which, when receiving a service invoking request sent by a target application and requesting to invoke a target interface service, determines the target interface service and parameter information of the target interface service according to the service invoking request and pre-loaded user configuration data, and further invokes the target interface service according to the parameter information of the target interface service. According to the technical scheme, the relevant parameters of the target interface service can be obtained by using the pre-loaded user configuration data, the gateway does not need to be restarted, the problem that the user cannot use the gateway due to shutdown of the gateway is avoided, and the use experience of the user is improved.

The overall thought of the embodiment of the application is as follows: and carrying out interface and parameter configuration through a configured interface, loading user configuration data in real time when the gateway runs, and calling the back-end RPC service in a generalized calling mode. The method replaces the traditional method that the code needs to be modified to increase the back-end service transmission object after the gateway adds the new interface in the prior art, and writes the data needed by the gateway in a configuration form without restarting the gateway. In addition, when the internal interface is output externally, developers can directly output externally through simple configuration, the time for outputting a new interface externally is greatly shortened, and the user experience is improved.

The technical solution of the present application will be described in detail below with reference to specific examples.

It should be noted that the following specific embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

Fig. 2 is a schematic flowchart of a first embodiment of a gateway-based service invocation method provided in the embodiment of the present application. As shown in fig. 2, the method may include the steps of:

s201, obtaining a service calling request sent by a target application, wherein the service calling request is used for requesting to call a target interface service.

In the embodiment of the application, when an external target application needs to call a target interface service, the external target application may send a service call request to an electronic device with a gateway, so that the electronic device determines the target interface service requested to be called by the target application according to the obtained service call request.

Optionally, in order to enable the electronic device to determine the target application and the target interface service timely and accurately based on the received service invocation request, the service invocation request may include: an identification of the target application and an identification of the target interface service. It can be understood that the service invocation request is not limited to include the identifier of the target application and the identifier of the target interface service, and in an actual application, it may also include other contents, which are not described herein again.

S202, determining the target interface service and the parameter information of the target interface service according to the service calling request and the pre-loaded user configuration data.

Optionally, in an embodiment of the present application, the electronic device may store pre-loaded user configuration data. For example, the user configuration data may be loaded and stored in a cache of the electronic device when the gateway is running, and the user configuration data includes related parameter information of the target interface service. Therefore, when the electronic device obtains a service call request of an external application, the electronic device may determine the target interface service from the pre-loaded user configuration data, and match parameter information of the target interface service, that is, parameter information required for executing the target interface service call.

Optionally, the process of preloading the user configuration data may be explained by using the embodiment shown in fig. 3, which is not described herein again.

Specifically, in S202, the electronic device obtains feature information included in the service invocation request, where the feature information is information capable of indicating a target interface service, and the feature information may specifically be a target interface name and/or a destination address in the service invocation request, where the target interface name and the destination address are related to a protocol type of a target application. After the characteristic information is obtained, the characteristic information is independently matched with user configuration data loaded in advance in the gateway, and whether the configuration information containing the characteristic information exists is checked. And if the characteristic information is successfully matched with the user configuration data of one service, determining the service corresponding to the successfully matched user configuration data as the target interface service, and further acquiring the parameter information for executing the target interface service.

S203, calling the target interface service according to the parameter information of the target interface service.

In this embodiment, after the electronic device obtains the parameter information of the target interface service, the electronic device may execute the calling of the target interface service based on the parameter information of the target interface service, thereby implementing the calling of the target interface service on the premise of not closing the gateway.

According to the service calling method based on the gateway provided by the embodiment of the application, when a received service calling request for calling the target interface service is received, the target interface service and the parameter information of the target interface service can be determined by combining with the pre-loaded user configuration data, and the calling of the target interface service is executed. According to the technical scheme, the relevant parameters of the target interface service can be obtained by utilizing the pre-loaded user configuration data, the target interface service at the rear end is called in a generalized calling mode, the gateway does not need to be restarted, the problem that the user cannot use the gateway due to shutdown of the gateway is avoided, and the use experience of the user is improved.

Exemplarily, on the basis of the above embodiments, fig. 3 is a schematic flowchart of a second embodiment of a gateway-based service invocation method provided in the embodiment of the present application. As shown in fig. 3, in this embodiment, before the foregoing S201, the method may further include the following steps:

s301, obtaining the configuration parameters aiming at the target interface service, wherein the configuration parameters are determined by the type of the target interface service.

In the embodiment of the present application, before the electronic device obtains the service invocation request from the external target application, it needs to determine the user configuration data that has loaded the target interface service. Specifically, the electronic device first obtains configuration parameters for the target interface service, and the specific configuration parameters need to be determined according to the type of the target interface service.

For example, when the target interface service is a bank account management service, the configuration parameters include parameters of account, amount, profit, and the like. When the target interface service is a health management service, the configuration parameters include: weight, height, age, body fat percentage and the like. The number and content of configuration parameters are different for different interface services, and the embodiment of the present application does not limit the number and content.

For a specific implementation of this step, reference may be made to the following description of the embodiment shown in fig. 4, which is not described herein again.

S302, configuring the gateway based on the configuration parameters.

In the embodiment of the application, after the electronic device acquires the configuration parameters for the target interface service, the configuration parameters can be used for configuring the gateway, so that when the gateway runs, the parameter information required for executing the target interface service can be generated based on the configuration parameters.

And S303, acquiring the user configuration data loaded when the gateway runs.

For example, when the electronic device configures the gateway based on the acquired configuration parameters, so that the gateway adds a target interface service, when the gateway is running, the gateway may convert the configuration parameters into user configuration information of the target interface service, and load the user configuration information into the electronic device, for example, a cache of the electronic device.

In this embodiment, the fact that the gateway does not need to be restarted is a result of loading the user configuration data in real time, because the configuration information of the newly added interface service is already loaded in the cache, and the user configuration data in the cache can be directly utilized subsequently, the gateway does not need to be restarted, and the user experience is improved.

Optionally, in an embodiment of the present application, as shown in fig. 3, before the step S302, the method may further include the following steps:

s304, verifying the configuration parameters and determining that the configuration parameters pass the verification.

In the embodiment of the present application, in order to improve the accuracy of the target interface service, the acquired configuration parameters need to be checked. Optionally, the configuration parameter may be checked according to some attribute information of the configuration parameter.

For example, for the age of the configuration parameter, it is statistically found that there is no person over 200 years old, and thus, if there is a parameter with an age of 210 years in the configuration parameter, it indicates that the parameter is obviously not normal, and it is determined that the configuration parameter cannot pass the verification. Alternatively, it may be eliminated.

In this embodiment, the gateway is configured by using the verified configuration parameters, so that the accuracy of providing the service by the gateway can be improved, and the user experience is also improved.

According to the service calling method based on the gateway, the configuration parameters aiming at the target interface service are obtained, the gateway is configured based on the configuration parameters, and finally the user configuration data loaded when the gateway runs are obtained. According to the technical scheme, before the service calling request is received, the configuration information of the target interface service is obtained and the gateway is configured, so that the realization possibility is provided for the follow-up execution of the calling of the target interface service.

Exemplarily, on the basis of the above embodiments, fig. 4 is a schematic flowchart of a third embodiment of a gateway-based service invocation method provided in the embodiment of the present application. Referring to fig. 4, S301 may be implemented by:

s401, obtaining an interface service transmission packet imported in a preset mode.

In the embodiment of the application, the external application may write the configuration parameters into excel, or perform parameter configuration on the configuration interface, or perform configuration in a jar packet import manner, and generate the interface service transmission packets respectively. The specific configuration mode of the interface service transmission packet may be determined according to an actual scenario, and is not described herein again.

Optionally, the specific configuration parameter included in the interface service transmission packet corresponding to each interface service may be determined according to the type of the interface service, which is not limited in this embodiment of the present application.

For example, in this embodiment, the preset manner may be one of the following manners: an Excel import mode, an interface configuration mode and a jar package import mode.

As an example, if the preset manner is an Excel import manner, the step S401 may be implemented by the following steps: firstly, determining a pre-configured Excel template, wherein the Excel template comprises the following components: and acquiring an interface service transmission packet through the import interface on the configuration interface, wherein the interface service transmission packet is obtained by updating the field information of the fixed position in the Excel template according to the plurality of configuration items of the target interface service by a user.

Specifically, a user downloads an Excel template for parameter configuration through a configuration interface, fills transmission parameters of interfaces corresponding to the interface services according to requirements, and then imports an interface service transmission package generated based on the Excel template into the corresponding interface through an import interface on the configuration interface.

For example, table 1 shows a plurality of configuration items included in an Excel template. Referring to table 1, the relevant configuration items of the interface corresponding to the target interface service are as follows:

interface description	Credit line inquiry of credit platform
		Interface service type	Jsf
Interface name	0009
		Interface Chinese name	User's limit inquiry interface
External request interface address	10.222.10.84；8112/mapi/dubhe/1/quotainfo
		http internal request address
Service interface name	Support.quota.facade.DubheQuotaQueryFacade
		Service alias	QuotaQuery
Registration center address	i.jsf.comqweq
		Interface method name	Queryquotainfo
Full package name of request header	Com.api.modle.commonRequest
		Request object body package name	Com.support.quota.request.QuotaQueryinfoReqDto
Full package name of response header	Com.api.modle.OutResponse
		Responsive object body package name	Com.support.quota.response.QuotaQueryinfoRespDto

It should be understood that the configuration items given above are only an exemplary illustration, and the type, name and number of the configuration items can be determined according to practical situations, and the embodiment of the present application is not limited thereto.

Optionally, table 2 shows information of the request-service parameter in the Excel template shown in table 1. Referring to table 2, the information of the request-service parameter is as follows:

table 3 shows information of response-service parameters in the Excel template shown in table 1. Referring to table 3, the information of the response-service parameter is as follows:

optionally, fig. 5 is a schematic diagram of obtaining an interface service transport packet through an Excel import mode. Referring to fig. 5, the configuration interface of the electronic device has an option of querying the application interface through the application code and/or the application name, and also has an option of adding an application interface. The options for the existing application interfaces may include an application code added, an application name, an operation (options of editing, deleting, detailing, adding an interface, data authority management, and the like), an import interface (which may include a plurality of interfaces with different transmission rates), and the like.

In the embodiment of the present application, specific content and detailed information about an application interface may be determined according to an actual scene, and are not described herein again.

As another example, when the preset mode is an interface configuration mode, the step S401 may be implemented by the following steps: acquiring an interface service transmission packet imported by a user through operation on a configuration interface, wherein the operation on the configuration interface may include: configuring or modifying configuration parameters of the target service interface.

Fig. 6 is a schematic diagram illustrating an interface service transport packet obtained by an interface configuration method. Referring to fig. 6, a user may directly configure and modify configuration parameters of an interface corresponding to an interface service through a configuration interface. Specifically, the configuration parameters may include request parameters and response parameters. Wherein, the processing for the request parameter may include: parameter name, parameter Chinese name, service field code, data type, parameter type, mandatory item, default data, operation, etc.

In addition, as shown in fig. 6, the configuration interface may further include options of adding a sibling column, saving, and the like. The specific operation can be determined according to actual conditions, and is not described herein again.

As another example, if the preset mode is jar package import mode, the step S401 may be implemented by: and acquiring an interface service transmission packet generated by a provider to which the target interface service belongs through a configuration interface.

The interface service transmission packet comprises a transmission object with a custom note, wherein the custom note is positioned at a specific position of the transmission object and is used for explaining fields or classes in the transmission object.

Specifically, the service provider may introduce a custom annotation to the gateway, that is, annotate a field or class at a specific position in the transport object, process the transport object with the annotation into a jar packet, and upload the jar packet to the electronic device through the configuration interface. Correspondingly, the gateway in the electronic equipment can acquire the interface service transmission package by downloading the jar package.

Illustratively, the custom annotation of the transport object is as follows:

@InterfaceInfoutil(

InterfaceName is defined as "Credit application result query interface + 002",

interfaceCode＝”epp_gateway_trade_system_101”,

isRootNode＝true

)

public class entirtouttest{

private String status；

private String errorCode；

private String errorMesssage；

private String responseCode；

……

in addition, in the embodiment of the application, the electronic device may obtain the imported interface service transmission packet through the excel, the interface configuration, and the jar packet, and if the gateway is communicated with the registry of the backend service, the electronic device may further obtain the upload interface service transmission packet from the registry.

Thus, this S401 can also be realized by: and acquiring the interface service transmission packet from the registration center of the target interface service.

As can be seen from the above analysis, in the embodiment of the present application, the interface service transmission packet may be obtained in any one of multiple manners, such as an excel import manner, an interface configuration manner, a jar package import manner, and extraction from a registration center, and as to which manner is specifically adopted, which manner may be determined according to an actual situation, which is not described herein again.

S402, determining the analysis mode of the interface service transmission packet according to the preset mode.

In this embodiment, the electronic device may obtain the interface service transmission packet according to a plurality of preset manners, and since different preset manners correspond to different analysis manners, the electronic device may determine, according to the preset manners, manners for analyzing the interface service transmission packet, that is, different analysis manners.

And S403, analyzing the oral service transmission packet by using the analysis mode to obtain the configuration parameters for the target interface service.

In this embodiment, the gateway in the electronic device may identify an import manner of the interface service transport packet, and analyze the imported interface service transport packet by using a corresponding analysis manner to obtain the configuration parameter for the target interface service.

It can be understood that, for different import and parsing manners, the interface service transport packet will be finally converted into the same set of user configuration data for the target interface service, but the import manner is different, the data source is different, and the conversion logic (parsing manner) is different.

Optionally, on the basis of S401, when the preset mode is an Excel import mode, S403 may be implemented by the following steps: and acquiring configuration parameters aiming at the target interface service from the interface service transmission package according to the field information of the fixed position in the Excel template.

Specifically, when the interface service transport package is acquired in an Excel import mode, a fixed position can be determined according to a label because the data at each position in each Excel has one label; therefore, the electronic equipment can determine to acquire the configuration parameters for the target interface service according to the field information of the fixed position in the Excel template.

Optionally, when the preset mode is an interface configuration mode, the step S403 may be implemented by: and acquiring the configuration parameters aiming at the target interface service from the configuration interface. Specifically, the electronic device may directly obtain the configuration parameters for the target interface service from the configuration interface of the operation.

When the preset mode is a jar packet import mode, the S403 may be implemented by the following steps: and acquiring configuration parameters aiming at the target interface service according to the custom annotation and a Java reflection mechanism.

Specifically, since the Java reflection mechanism refers to a function of dynamically acquiring information and dynamically invoking an object method, and since the custom annotation is an explanation of an interface corresponding to the target interface service, the configuration parameters for the target interface service can be acquired from jar based on the custom annotation and the Java reflection mechanism in the jar package.

According to the service calling method based on the gateway provided by the embodiment of the application, the interface service transmission packet imported in a preset mode is obtained, the analysis mode of the interface service transmission packet is determined according to the preset mode, and the oral service transmission packet is analyzed by using the analysis mode to obtain the configuration parameters aiming at the target interface service. According to the technical scheme, the configuration information of the target interface service required by the gateway is written into the gateway of the electronic equipment in a configuration form through the configuration interface, so that hot deployment of the target interface service is realized when the gateway runs. In addition, developers can directly output user configuration data of the internal interface service to the outside through simple configuration, so that the output time is greatly shortened, and the output efficiency is improved.

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.

Fig. 7 is a schematic structural diagram of an embodiment of a gateway-based service invocation apparatus according to an embodiment of the present application. As described with reference to fig. 7, the apparatus may include: an obtaining module 701, a processing module 702 and a calling module 703.

The obtaining module 701 is configured to obtain a service invocation request sent by a target application, where the service invocation request is used to request to invoke a target interface service;

the processing module 702 is configured to determine the target interface service and parameter information of the target interface service according to the service invocation request and the preloaded user configuration data;

the calling module 703 is configured to call the target interface service according to the parameter information of the target interface service.

For example, in a possible design of the present application, the obtaining module 701 is further configured to obtain a configuration parameter for the target interface service before obtaining a service call request issued by a target application, where the configuration parameter is determined by a type of the target interface service;

the processing module 702 is further configured to configure the gateway based on the configuration parameters;

the obtaining module 701 is further configured to obtain the user configuration data loaded during the running of the gateway.

For example, in another possible design of the present application, the obtaining module 701 includes: an acquisition unit and a processing unit;

the acquisition unit is used for acquiring an interface service transmission packet imported in a preset mode;

the processing unit is configured to determine an analysis mode of the interface service transmission packet according to the preset mode, and analyze the interface service transmission packet by using the analysis mode to obtain a configuration parameter for the target interface service.

In an embodiment of the present application, the preset mode is one of the following modes: an Excel import mode, an interface configuration mode and a jar package import mode.

the processing unit is specifically configured to acquire configuration parameters for the target interface service from the configuration interface.

For example, in another possible design of the present application, the obtaining module 701 is specifically configured to obtain the interface service transport packet from a registry of the target interface service.

For example, in another possible design of the present application, the processing module 702 is further configured to check the configuration parameter before configuring the gateway based on the configuration parameter, and determine that the configuration parameter passes the check.

The apparatus provided in the embodiment of the present application may be used to execute the method in the embodiments shown in fig. 2 to fig. 4, and the implementation principle and the technical effect are similar, which are not described herein again.

It should be noted that the division of the modules of the above apparatus is only a logical division, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the determining module may be a processing element separately set up, or may be implemented by being integrated in a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and the function of the determining module is called and executed by a processing element of the apparatus. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when some of the above modules are implemented in the form of a processing element scheduler code, the processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor that can call program code. As another example, these modules may be integrated together, implemented in the form of a system-on-a-chip (SOC).

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. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. 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 can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the 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.

Fig. 8 is a schematic structural diagram of an embodiment of an electronic device provided in the embodiment of the present application. As shown in fig. 8, the electronic device may include: the system comprises a processor 81, a memory 82, a communication interface 83 and a system bus 84, wherein the memory 82 and the communication interface 83 are connected with the processor 81 through the system bus 84 and complete mutual communication, the memory 82 is used for storing computer execution instructions, the communication interface 83 is used for communicating with other devices, and the processor 81 implements the scheme of the embodiment shown in fig. 2 to 4 when executing the computer program.

Optionally, in an embodiment of the present application, the electronic device may further include a configuration interface 85, and the configuration interface 85 may be used for importing the configuration parameters.

In fig. 8, the processor 81 may be a general-purpose processor including a central processing unit CPU, a Network Processor (NP), and the like; but also a digital signal processor DSP, an application specific integrated circuit ASIC, a field programmable gate array FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components.

The memory 82 may comprise Random Access Memory (RAM), read-only memory (RAM), and non-volatile memory (non-volatile memory), such as at least one disk memory.

The communication interface 83 is used to enable communication between the database access device and other devices (e.g., clients, read-write libraries, and read-only libraries).

The system bus 84 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The system bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of illustration, only one thick line is shown, but this does not mean that there is only one bus or one type of bus.

Optionally, an embodiment of the present application further provides a computer-readable storage medium, where computer instructions are stored, and when the computer instructions are executed on a computer, the computer is caused to execute the method according to the embodiment shown in fig. 2 to 4.

Optionally, an embodiment of the present application further provides a chip for executing the instruction, where the chip is configured to execute the method in the embodiment shown in fig. 2 to 4.

Embodiments of the present application further provide a program product, where the program product includes a computer program, where the computer program is stored in a computer-readable storage medium, and the computer program can be read by at least one processor from the computer-readable storage medium, and the at least one processor can implement the method in the embodiments shown in fig. 2 to fig. 4 when executing the computer program.

In the present application, "at least one" means one or more, "a plurality" 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, wherein A and B can be singular or plural. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship; in the formula, the character "/" indicates that the preceding and following related objects are in a relationship of "division". "at least one of the following" or similar expressions refer to any combination of these items, including any combination of the singular or plural items. For example, at least one (one) of a, b, or c, may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or multiple.

It is to be understood that the various numerical references referred to in the embodiments of the present application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of the present application. In the embodiment of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiment of the present application.

Finally, it should be noted that: the above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some or all of the technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A gateway-based service invocation method is characterized by comprising the following steps:

2. The method of claim 1, wherein prior to said obtaining the service invocation request issued by the target application, the method further comprises:

configuring the gateway based on the configuration parameters;

and acquiring the user configuration data loaded when the gateway runs.

3. The method of claim 2, wherein obtaining configuration parameters for the target interface service comprises:

acquiring an interface service transmission packet imported in a preset mode;

4. The method according to claim 3, wherein if the preset mode is an Excel import mode, the obtaining an interface service transport packet imported in the preset mode includes:

5. The method according to claim 3, wherein if the preset mode is an interface configuration mode, the obtaining of the interface service transport packet imported in the preset mode includes:

6. The method according to claim 3, wherein if the predetermined manner is a jar packet import manner, the obtaining an interface service transport packet imported by the predetermined manner includes:

7. The method according to claim 3, wherein the obtaining the interface service transport packet imported by the predetermined method comprises:

8. A gateway-based service invocation apparatus, comprising: the system comprises an acquisition module, a processing module and a calling module;

9. An electronic device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the method according to any of the claims 1-7 when executing the program.

10. A computer-readable storage medium having stored thereon computer instructions which, when executed on a computer, cause the computer to perform the method of any one of claims 1-7.