CN114598750A - Data request processing method and device and storage medium - Google Patents

Abstract

The invention discloses a data request processing method, device and storage medium, which relate to the technical field of data processing, and can unify interface specifications during remote data invocation. The specific scheme includes: obtaining a data call request, which is used to request target data of the target service; analyzing the data call request to obtain the data call address, call method name and business parameters of the target service included in the data call request; The first mapping relationship between the address and the interface determines the target interface corresponding to the data calling address; based on the second mapping relationship between interfaces, method names, and methods, the calling method corresponding to the target interface is determined; The format is converted into the second format, and target interface parameters are generated; the target interface parameters are sent to the service server through the target interface; the target data sent by the service server is received; and the target data is converted from the second format to the first format.

Description

A data request processing method, device and storage medium

technical field

The present invention relates to the technical field of data processing, and in particular, to a data request processing method, device and storage medium.

Background technique

The business server has multiple interfaces, and each interface can correspond to a service. Usually, the services in the business server are called internally. Therefore, when the data calling device needs to call a service in the business server, it is necessary to write a templated application layer code for the interface corresponding to each service, and the data calling device requests Both the parameters and the response parameters of the business server need to be customized, which is not conducive to the unified interface specification.

SUMMARY OF THE INVENTION

The present invention provides a data request processing method, device and storage medium, which can unify interface specifications during remote data invocation.

To achieve the above object, the present invention adopts the following technical solutions:

In a first aspect, the present invention provides a data request processing method, the method comprising:

Get the data call request, the data call request is used to request the target data of the target business;

Analyze the data calling request to obtain the data calling address, calling method name and business parameters of the target business included in the data calling request;

Determine the target interface corresponding to the data calling address based on the first mapping relationship between the calling address and the interface;

Determine the calling method corresponding to the target interface based on the interface, the method name, and the second mapping relationship between the methods;

Convert business parameters and calling methods from the first format to the second format, and generate target interface parameters;

Send the target interface parameters to the service server through the target interface;

Receive the target data sent by the business server;

Convert the target data from the second format to the first format.

With the data request processing method provided by the present invention, when the gateway receives the data invocation request sent by the data invocation device, it processes the data invocation request to obtain target interface parameters. Then, the gateway sends the target interface parameters to the service server, and receives the target data sent by the service server. Finally, the gateway converts the target data from the second format to the first format, so that the data invoking device can identify the target data and obtain the data to be invoked. Compared with the prior art, when the gateway needs to call a service in the business server, it needs to write a templated application layer code for the interface corresponding to each service, and the request parameters of the gateway and the response parameters of the business server need to be customized. , the data request processing method provided by the present invention can unify the interface specification during the calling process. Moreover, the gateway can provide customizable parameter conversion, which improves the convenience and security of interface management.

In a possible implementation manner, after parsing the data invocation request, the identity identifier included in the data invocation request is also obtained;

Based on the identity identifier and the pre-stored authentication policy, determine whether the account indicated by the identity identifier has the right to call data;

Based on the first mapping relationship between the calling address and the interface, determine the target interface corresponding to the data calling address, including:

In the case where it is determined that the account indicated by the identity identifier has the right to call data, the target interface is determined based on the first mapping relationship.

In a possible implementation manner, the above data request processing method further includes:

Send subscription information to the registration server;

The first mapping relationship and the second mapping relationship sent by the registration server are received.

In a second aspect, the present invention provides a data request processing method, which is applied to a service server, and the method includes:

Obtain the identified preset interface, and the preset interface is used to call the target data of the target service;

Send a preset interface and method information corresponding to the preset interface to the registration server, where the method information includes a calling address corresponding to the preset interface, and at least one method name and method corresponding to the preset interface.

In a third aspect, the present invention provides a data request processing device, the data request processing device comprising:

The obtaining unit is used to obtain the data calling request, and the data calling request is used to request the target data of the target service;

a parsing unit, configured to parse the invocation request acquired by the acquiring unit, and obtain the data invocation address, invocation method name and business parameters of the target business included in the data invocation request;

The determining unit is used to determine the target interface corresponding to the data invocation address obtained by the parsing unit based on the first mapping relationship between the data call address and the interface, and based on the second mapping relationship between the interface, the method name and the method, determine the corresponding target interface method of calling;

a generating unit, configured to convert the business parameters obtained by the parsing unit and the calling method obtained by the determining unit from the first format to the second format, and generate target interface parameters;

The acquiring unit is also used to send the target interface parameters to the service server through the target interface, and receive the target data sent by the service server;

The generating unit is further configured to convert the target data acquired by the acquiring unit from the second format to the first format.

In a possible implementation manner, after the parsing unit parses the data calling request, it also obtains the identity identifier included in the data calling request;

The determining unit is further configured to determine whether the account indicated by the identity identifier has the data calling authority based on the identity identifier and the pre-stored authentication strategy;

Determine the unit, specifically for:

In the case where it is determined that the account indicated by the identity identifier has the right to call data, the target interface is determined based on the first mapping relationship.

In a possible implementation manner, the acquiring unit is further configured to send subscription information to the registration server, and receive the first mapping relationship and the second mapping relationship sent by the registration server.

In a fourth aspect, the present invention provides a data request processing device, the data request processing device comprising:

an acquisition unit, configured to acquire the identified preset interface, and the preset interface is used to invoke the target data of the target service;

The sending unit is configured to send the preset interface and method information corresponding to the preset interface to the registration server, where the method information includes a calling address corresponding to the preset interface, and at least one method name and method corresponding to the preset interface.

In a fifth aspect, the present invention provides a data request processing apparatus, the data request processing apparatus comprising: a processor and a memory. The memory is used to store computer program code including computer instructions. When the processor executes the computer instructions, the data request processing apparatus executes the data request processing method as described in the first aspect and any possible implementation manner thereof, or executes the data request processing method as described in the second aspect.

In a sixth aspect, the present invention provides a computer-readable storage medium on which computer instructions are stored, and when the computer instructions are executed on the data request processing apparatus, the data request processing apparatus executes the first aspect or the possibility of the first aspect. The data request processing method of any one of the implementation manners, or execute the data request processing method described in the second aspect.

Description of drawings

1 is a schematic structural diagram of a data request processing system provided by an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a computing device according to an embodiment of the present invention;

3 is one of the schematic flowcharts of a data request processing method provided by an embodiment of the present invention;

4 is a second schematic flowchart of a data request processing method provided by an embodiment of the present invention;

5 is a third schematic flowchart of a data request processing method provided by an embodiment of the present invention;

6 is one of the schematic structural diagrams of a data request processing apparatus provided by an embodiment of the present invention;

FIG. 7 is a second schematic structural diagram of an apparatus for processing a data request provided by an embodiment of the present invention.

Detailed ways

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, but not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as indicating or implying relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may expressly or implicitly include one or more of that feature. In the description of the embodiments of the present disclosure, unless otherwise specified, "plurality" means two or more. Additionally, the use of "based on" or "according to" is meant to be open and inclusive, since a process, step, calculation or other action "based on" or "depending on" one or more of the stated conditions or values may in practice be based on additional condition or exceed the stated value.

In order to unify interface specifications during remote data invocation, embodiments of the present invention provide a data request processing method, device, and storage medium. When the gateway receives the data invocation request sent by the data invocation device, it obtains the target interface parameters by processing the data invocation request. Then, the gateway sends the target interface parameters to the service server, receives the target data sent by the service server, and converts the target data from the second format to the first format, so that the data calling device can identify the target data and obtain the data to be called. .

The data request processing method provided by the embodiment of the present invention can be applied to a data request processing system. FIG. 1 shows a structure of the data request processing system. As shown in FIG. 1 , the data request processing system may include: a data calling device 11 , a gateway 12 , a registration server 13 and a service server 14 . The data calling device 11 establishes a connection with the gateway 12 through wired communication or wireless communication. The gateway 12, the registration server 13, and the service server 14 establish connections through wired communication or wireless communication.

The data invocation device 11 is configured to send a data invocation request to the gateway 12, where the data invocation request is used for requesting target data, and receives target data in a first format sent by the gateway 12.

Exemplarily, the data calling device 11 may be a gateway such as a smart phone, a tablet computer, or a desktop computer.

The gateway 12 is configured to parse the received data invocation request to obtain the data invocation address, invocation method name and service parameters. The gateway 12 is further configured to determine the target interface corresponding to the data invocation address based on the first mapping relationship between the data invocation address and the interface, and determine the invocation method corresponding to the target interface based on the second mapping relationship between interfaces, method names and methods. The gateway 12 is also used to convert the service parameters and the calling method from the first format to the second format, generate target interface parameters, and send the target interface parameters to the service server through the target interface, after receiving the target data sent by the service server, Convert the target data from the second format to the first format. The gateway 12 is further configured to send the target data whose data format is the first format to the data calling device 11 .

The registration server 13 is configured to receive the identification interface sent by the service server 14 and the method information corresponding to the identification interface, and generate the first mapping relationship and the second mapping relationship according to the identification interface and the method information corresponding to the identification interface.

The service server 14 is configured to provide the gateway 12 with the target data whose data format is the second format. The service server 14 is further configured to send the identification interface and method information corresponding to the identification interface to the registration server.

The basic hardware structures of the above-mentioned data calling device 11 , gateway 12 , registration server 13 and service server 14 are similar, and all include the elements included in the computing device shown in FIG. 2 . Taking the computing device shown in FIG. 2 as an example below, the hardware structures of the data calling device, the gateway, the registration server and the service server are introduced.

As shown in FIG. 2 , the computing device may include: a processor 21 , a memory 22 , a communication interface 23 and a bus 24 . The processor 21 , the memory 22 and the communication interface 23 can be connected through a communication bus 24 .

The processor 21 is the control center of the computing device, and may be one processor 21 or a general term for multiple processing elements. For example, the processor 21 may be a general-purpose central processing unit (central processing unit, CPU), or may be other general-purpose processors 21 or the like. The general-purpose processor 21 may be a microprocessor 21 or any conventional processor 21 or the like.

As an embodiment, the processor 21 may include one or more CPUs, for example, CPU0 and CPU1 shown in FIG. 2 .

The memory 22 may be a read-only memory 22 (ROM) or other type of static storage device that can store static information and instructions, a random access memory 22 (RAM) or a device that can store information and instructions. Other types of dynamic storage devices can also be electrically erasable programmable read-only memory 22 (electrically erasable programmable read-only memory, EEPROM), magnetic disk storage media or other magnetic storage devices, or can be used to carry or store instructions or The desired program code in the form of a data structure and any other medium that can be accessed by a computer, but not limited thereto.

In a possible implementation manner, the memory 22 may exist independently of the processor 21, and the memory 22 may be connected to the processor 21 through a bus 24 for storing instructions or program codes. When the processor 21 calls and executes the instructions or program codes stored in the memory 22, the data request processing method provided by the following embodiments of the present invention can be implemented.

In another possible implementation manner, the memory 22 may also be integrated with the processor 21 .

The communication interface 23 is used for connecting the computing device with other devices through a communication network, the communication network may be Ethernet, radio access network (RAN), wireless local area network (WLAN) and the like. The communication interface 23 may include a receiving unit for receiving data, and a transmitting unit for transmitting data.

The bus 24 may be an Industry Standard Architecture (ISA) bus 24, a Peripheral Component Interconnect (PCI) bus 24 or an Extended Industry Standard Architecture (EISA) bus 24 or the like. The bus 24 can be divided into an address bus 24, a data bus 24, a control bus 24, and the like. For ease of presentation, only one thick line is shown in FIG. 2, but it does not mean that there is only one bus 24 or one type of bus 24.

It should be pointed out that the structure shown in FIG. 2 does not constitute a limitation on the computing device. In addition to the components shown in FIG. 2 , the computing device may include more or less components than those shown in the figure, or combine certain components. some components, or a different arrangement of components.

The data request processing method provided by the embodiments of the present invention will be described below with reference to the accompanying drawings.

As shown in FIG. 3 , the data request processing method provided by the embodiment of the present invention includes the following steps 301 to 308 .

301. The gateway obtains a data invocation request, where the data invocation request is used to request target data of a target service.

In one scenario, when the user invokes the target data of the target service in the service server through the data invocation device, the data invocation device makes a data invocation request to the gateway, and the data invocation request is used to request the target data of the target service. Exemplarily, the data call request may be an http request.

302. The gateway parses the data invocation request, and obtains the data invocation address, invocation method name, and service parameters of the target service included in the data invocation request.

Optionally, after the gateway receives the data invocation request sent by the data invocation device, it adopts the preset parsing rules to parse the data invocation request to obtain the data invocation address, invocation method name and target service information included in the data invocation request. business parameters. The service parameters of the target service are parameters necessary for the target data invoked by the data invoking device.

Illustratively, take the data calling request as an http request as an example. After receiving the http request sent by the data calling device, the gateway parses the http request to obtain a Uniform Resource Locator (URL) of the http request. The gateway is further configured to perform path matching according to the URL of the http request, and determine the data invocation address, invocation method name and service parameters of the target service included in the http request.

For example, an operation and maintenance application is installed in the data calling device, and the target business is to call the operation and maintenance data of the operation and maintenance device in November. When the operation and maintenance personnel want to call the operation and maintenance data of the operation and maintenance equipment for the whole month of November, the operation and maintenance personnel send an http request to the gateway to call the operation and maintenance data of November through the data calling equipment. The http request for calling the operation and maintenance data in November includes the data calling address, the calling method name, and business parameters such as the date. After receiving the http request, the gateway parses and processes the http request, and determines the data calling address, calling method name, date and other business parameters.

Optionally, after parsing the data invocation request, the identity identifier included in the data invocation request can also be obtained. Based on the identity and the pre-stored authentication policy, the gateway determines whether the account indicated by the identity has the right to call data. The gateway will proceed with the following steps only if it is determined that the account logged in by the data calling device has the right to call the target data.

303. The gateway determines a target interface corresponding to the data invocation address based on the first mapping relationship between the invocation address and the interface.

Optionally, in the case that the gateway determines that the account indicated by the identity identifier has the right to call data, the target interface is determined based on the first mapping relationship. The data invocation address corresponds to the interface in the service server one by one. After the gateway determines the data invocation address, it will determine the target interface corresponding to the data invocation address according to the first mapping relationship between the invocation address and the interface. The target interface is the interface corresponding to the business server when the target data is called.

304. The gateway determines the calling method corresponding to the target interface based on the interface, the method name, and the second mapping relationship among the methods.

Optionally, an interface can include multiple methods, and a method has a name. After the gateway determines the name of the calling method, it will determine the calling method corresponding to the target interface according to the second mapping relationship between the interface, the method name, and the method.

305. The gateway converts the service parameters and the calling method from the first format to the second format, and generates target interface parameters.

Optionally, since the data format of the data used by the data invoking device is the first format, the data format of the data used by the service server is the second format. Therefore, after the gateway determines the corresponding target interface when calling the above target data and the calling method corresponding to the target interface, it needs to convert the business parameters and calling method from the first format to the second format that the business server can recognize, and generate the target interface. interface parameters.

306. The gateway sends the target interface parameter to the service server through the target interface.

307. The gateway receives the target data sent by the service server.

308. The gateway converts the target data from the second format to the first format.

The data format of the target data received by the gateway is the second data format. In order for the data calling device to recognize the target data, the gateway also needs to convert the target data from the second format to the first format.

With the data request processing method provided by the present invention, when the gateway receives the data invocation request sent by the data invocation device, it processes the data invocation request to obtain target interface parameters. Then, the gateway sends the target interface parameters to the service server, receives the target data sent by the service server, and converts the target data from the second format to the first format, so that the data calling device can obtain the data to be called. Compared with the prior art, when the gateway needs to call a service in the business server, it needs to write a templated application layer code for the interface corresponding to each service, and the request parameters of the gateway and the response parameters of the business server need to be customized. , can unify the interface specification. Moreover, the gateway can provide customizable parameter conversion, which improves the convenience and security of interface management.

With reference to FIG. 3 , as shown in FIG. 4 , the data request processing method provided by the embodiment of the present invention may further include the following steps 401 and 402 .

401. The gateway sends subscription information to the registration server.

402. The gateway receives the first mapping relationship and the second mapping relationship sent by the registration server.

Optionally, when the gateway starts, it will actively send subscription information to the registration server. After receiving the subscription information, the registration server sends to the gateway the first mapping relationship between the calling address and the interface, and the second mapping relationship between the interface, the method name, and the method. After receiving the first mapping relationship and the second mapping relationship, the gateway adopts a caching strategy to cache the two. When the first mapping relationship and the second mapping relationship in the registration server are changed, the registration server will actively send the change information to the gateway.

With reference to FIG. 4 , as shown in FIG. 5 , the data request processing method provided by the embodiment of the present invention may further include the following steps 501 and 502 .

501. The service server acquires the identified preset interface. The preset interface is used to call target data of the target service.

502. The service server sends a preset interface and method information corresponding to the preset interface to the registration server. The method information includes the calling address corresponding to the preset interface, and at least one method name and method corresponding to the preset interface.

Optionally, after the service server is started, it automatically scans the interfaces that need to be exposed when the data calling device calls data, and the specific method information corresponding to the interfaces that need to be exposed. After the business server determines the interface to be exposed, it identifies the interface to be exposed by annotating the implementation class on the interface to be exposed, and obtains the identified preset interface, which is used to call the target service's target data. After the business server generates the identification interface, it sends the preset interface and the method information corresponding to the preset interface to the registration server, so that the interface in the business server can be automatically exposed and discovered by the registration server, and the interface in the business server can be avoided. Duplicate ID.

Optionally, after acquiring the preset interface and the method information corresponding to the preset interface, the registration server generates the first mapping relationship and the second mapping relationship according to the preset interface and the method information corresponding to the preset interface.

The solutions provided by the embodiments of the present invention are described above mainly from the perspective of a data request processing apparatus. It can be understood that, in order to realize the above-mentioned functions, the data request processing apparatus includes corresponding hardware structures and/or software modules for executing each function. Those skilled in the art should easily realize that the present invention can be implemented in hardware or a combination of hardware and computer software in conjunction with the algorithm steps of the examples described in the embodiments disclosed herein. Whether a function is performed by hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each particular application, but such implementations should not be considered beyond the scope of the present invention.

FIG. 6 shows a schematic diagram of a possible composition of the data request processing apparatus 600 involved in the above embodiment. As shown in FIG. 6 , the data request processing apparatus 600 may include: an acquiring unit 601 , a parsing unit 602 , and a determining unit 603 and generating unit 604 .

The obtaining unit 601 is configured to obtain a data calling request, and the data calling request is used to request target data of a target service. The parsing unit 602 is configured to parse the data invocation request acquired by the acquiring unit, and obtain the data invocation address, invocation method name and service parameters of the target service included in the data invocation request. The determining unit 603 is configured to determine, based on the first mapping relationship between the calling address and the interface, the target interface corresponding to the data calling address obtained by the parsing unit, and based on the second mapping relationship between the interface, the method name and the method, determine the corresponding target interface method of calling. The generating unit 604 is configured to convert the service parameters obtained by the parsing unit and the calling method obtained by the determining unit from the first format to the second format to generate target interface parameters. The obtaining unit 601 is further configured to send target interface parameters to the service server through the target interface, and receive target data sent by the service server. The generating unit 604 is further configured to convert the target data acquired by the acquiring unit from the second format to the first format.

After the parsing unit 602 parses the data invocation request, the identity identifier included in the data invocation request can also be obtained.

Optionally, the determining unit 603 is further configured to determine, based on the identity identifier and a pre-stored authentication policy, whether the account indicated by the identity identifier has the right to call data.

Optionally, the determining unit 603 is specifically configured to:

In the case where it is determined that the account indicated by the identity identifier has the right to call data, the target interface is determined based on the first mapping relationship.

Optionally, the obtaining unit 601 is further configured to send subscription information to the registration server, and receive the first mapping relationship and the second mapping relationship sent by the registration server.

FIG. 7 shows a possible schematic composition diagram of the data request processing apparatus involved in the above embodiment. As shown in FIG. 7 , the data request processing apparatus 700 may include: an obtaining unit 701 and a sending unit 702 .

Wherein, the obtaining unit 701 is configured to obtain the identified preset interface, and the preset interface is used to invoke the target data of the target service. The sending unit 702 is configured to send a preset interface and method information corresponding to the preset interface to the registration server, where the method information includes a calling address corresponding to the preset interface, and at least one method name and method corresponding to the preset interface.

Of course, the data request processing apparatus provided by the embodiment of the present invention includes but is not limited to the above-mentioned modules.

In actual implementation, the acquiring unit, the parsing unit, the determining unit, the generating unit and the sending unit may be implemented by the processor 21 shown in FIG. 2 calling program codes in the memory 22 . For the specific execution process, reference may be made to the description of the data request processing method shown in FIG. 3 to FIG. 6 , which will not be repeated here.

Another embodiment of the present invention further provides a computer-readable storage medium, where computer instructions are stored in the computer-readable storage medium, and when the computer instructions are executed on the data request processing apparatus, the data request processing apparatus is made to execute the above method embodiments Each step performed by the data request processing apparatus in the method flow shown.

Another embodiment of the present invention further provides a chip system, which is applied to a data request processing apparatus. The chip system includes one or more interface circuits and one or more processors 21 . The interface circuit and the processor 21 are interconnected by wires. The interface circuit is adapted to receive signals from the memory 22 of the data request processing device, and send the signals to the processor 21 , the signals comprising computer instructions stored in the memory 22 . When the processor 21 executes the computer instructions, the data request processing apparatus executes each step performed by the data request processing apparatus in the method flow shown in the above method embodiments.

In another embodiment of the present invention, a computer program product is also provided, the computer program product includes instructions, when the instructions are executed on the data request processing apparatus, the data request processing apparatus is caused to execute the method flow shown in the above method embodiments Each step performed by the data request processing device in

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can 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 computer-executable instructions are loaded and executed on a computer, the processes or functions according to embodiments of the present invention result in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. Computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center over a wire (e.g. coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) means to another website site, computer, server or data center. Computer-readable storage media can be any available media that can be accessed by a computer or data storage devices including one or more servers, data centers, etc., that can be integrated with the media. Useful media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto, and any changes or substitutions within the technical scope disclosed by the present invention should be covered within the protection scope of the present invention. . Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims (10)

1. A method for processing a data request, comprising:

acquiring a data calling request, wherein the data calling request is used for requesting target data of a target service;

analyzing the data calling request to obtain a data calling address, a calling method name and service parameters of the target service, wherein the data calling address, the calling method name and the service parameters of the target service are included in the data calling request;

determining a target interface corresponding to the data calling address based on a first mapping relation between the calling address and the interface;

determining a calling method corresponding to the target interface based on a second mapping relation among the interfaces, the method names and the methods;

converting the service parameters and the calling method from a first format to a second format to generate target interface parameters;

sending the target interface parameter to a service server through the target interface;

receiving the target data sent by the service server;

converting the target data from the second format to the first format.

2. The data request processing method according to claim 1, wherein after the data call request is parsed, an identity included in the data call request is also obtained;

determining whether the account indicated by the identity mark has data calling authority or not based on the identity mark and a pre-stored identity authentication strategy;

the determining a target interface corresponding to the data call address based on the first mapping relationship between the call address and the interface includes:

and under the condition that the account indicated by the identity identification is determined to have data calling authority, determining the target interface based on the first mapping relation.

3. The data request processing method according to claim 1 or 2, wherein the data request processing method further comprises:

sending subscription information to a registration server;

and receiving the first mapping relation and the second mapping relation sent by the registration server.

4. A method for processing a data request, comprising:

acquiring an identified preset interface, wherein the preset interface is used for calling target data of a target service;

and sending the preset interface and method information corresponding to the preset interface to a registration server, wherein the method information comprises a calling address corresponding to the preset interface and at least one method name and method corresponding to the preset interface.

5. A data request processing apparatus, comprising:

the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a data calling request which is used for requesting target data of a target service;

the analysis unit is used for analyzing the data calling request acquired by the acquisition unit to obtain a data calling address, a calling method name and a service parameter of the target service, wherein the data calling address, the calling method name and the service parameter are included in the data calling request;

the determining unit is used for determining a target interface corresponding to the data calling address obtained by the analyzing unit based on a first mapping relation between the calling address and the interface, and determining a calling method corresponding to the target interface based on a second mapping relation among the interface, the method name and the method;

a generating unit, configured to convert the service parameter obtained by the analyzing unit and the calling method obtained by the determining unit from a first format to a second format, and generate a target interface parameter;

the acquiring unit is further configured to send the target interface parameter to a service server through the target interface, and receive the target data sent by the service server;

the generating unit is further configured to convert the target data acquired by the acquiring unit from the second format to the first format.

6. The apparatus according to claim 5, wherein after the parsing unit parses the data call request, an identity included in the data call request is also obtained;

the determining unit is further configured to determine whether an account indicated by the identity identifier has a data call authority or not based on the identity identifier and a pre-stored identity authentication policy;

the determining unit is specifically configured to:

and under the condition that the account indicated by the identity identification is determined to have data calling authority, determining the target interface based on the first mapping relation.

7. The apparatus according to claim 5 or 6, wherein the obtaining unit is further configured to send subscription information to a registration server, and receive the first mapping relationship and the second mapping relationship sent by the registration server.

8. A data request processing apparatus, comprising:

the system comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring a marked preset interface, and the preset interface is used for calling target data of a target service;

and the sending unit is used for sending the preset interface and the method information corresponding to the preset interface to a registration server, wherein the method information comprises a calling address corresponding to the preset interface and at least one method name and method corresponding to the preset interface.

9. A data request processing apparatus, characterized in that the data request processing apparatus comprises: a processor and a memory; the memory for storing computer program code, the computer program code comprising computer instructions; when the processor executes the computer instructions, the data request processing apparatus performs the data request processing method according to any one of claims 1 to 3, or performs the data request processing method according to claim 4.

10. A computer-readable storage medium, comprising computer instructions which, when run on a data request processing apparatus, cause the data request processing apparatus to perform the data request processing method of any one of claims 1-3, or perform the data request processing method of claim 4.

Images