CN114598750B - Data request processing method, device and storage medium - Google Patents

Abstract

The invention discloses a data request processing method, a data request processing device and a storage medium, relates to the technical field of data processing, and can unify interface specifications during remote data call. The specific scheme comprises the following steps: acquiring a data call request, wherein the data call request is used for requesting target data of a target service; analyzing the data call request to obtain a data call address, a call method name and a service parameter of a target service, wherein the data call address, the call method name and the service parameter are included in the data call request; determining a target interface corresponding to the data call address based on a first mapping relation between the call 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 business parameters and the calling method from a first format to a second format to generate target interface parameters; sending target interface parameters to a service server through a target interface; receiving target data sent by a service server; 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 field of data processing technology, 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, so when the data calling device needs to call a service in the business server, it is necessary to write boilerplate application layer code for the interface corresponding to each service, and the request of the data calling device Both the parameters and the response parameters of the business server need to be customized, which is not conducive to unified interface specifications.

Contents of the invention

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

In order to achieve the above objects, the present invention adopts the following technical solutions:

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

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

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

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

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

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

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

Receive target data sent by the business server;

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

Using the data request processing method provided by the present invention, when the gateway receives the data calling request sent by the data calling device, the target interface parameters are obtained by processing the data calling request. Then, the gateway sends the target interface parameters to the business server and receives the target data sent by the business server. Finally, the gateway 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 that needs to be called. Compared with the existing technology, when the gateway needs to call a service in the business server, it needs to write boilerplate 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 specifications during the calling process. Moreover, the gateway can provide customized parameter conversion, which improves the convenience and security of interface management.

In a possible implementation, after parsing the data calling request, the identity identifier included in the data calling 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 data call permission;

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

When it is determined that the account indicated by the identity identifier has the data calling authority, the target interface is determined based on the first mapping relationship.

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

Send subscription information to the registration server;

Receive the first mapping relationship and the second mapping relationship sent by the registration server.

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

Obtain the identified default interface, which is used to call the target data of the target business;

Send a preset interface and method information corresponding to the preset interface to the registration server. 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, which includes:

The acquisition unit is used to obtain the data call request, and the data call request is used to request the target data of the target business;

The parsing unit is used to parse the call request obtained by the acquisition unit, and obtain the data call address, call method name and business parameters of the target business included in the data call request;

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

The generation unit is used to convert the business parameters obtained by the parsing unit and the calling method obtained by the determination unit from the first format to the second format, and generate the target interface parameters;

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

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

In a possible implementation, after the above parsing unit parses the data call request, it also obtains the identity included in the data call request;

The determination unit is also used to determine whether the account indicated by the identity identifier has data calling permission based on the identity identifier and the pre-stored authentication policy;

Determine the unit, specifically used for:

When it is determined that the account indicated by the identity identifier has the data calling authority, the target interface is determined based on the first mapping relationship.

In a possible implementation, the acquisition unit is also 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, which includes:

The acquisition unit is used to obtain the identified preset interface, and the preset interface is used to call the target data of the target business;

A sending unit, configured to send a preset interface and method information corresponding to the preset interface to the registration server. 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 device, which includes: a processor and a memory. Memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the data request processing device performs the data request processing method as described in the first aspect and any possible implementation thereof, or performs 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. When the computer instructions are run on a data request processing device, the data request processing device performs the first aspect or the possibility of the first aspect. implement any one of the data request processing methods, or execute the data request processing method as described in the second aspect.

Description of the drawings

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

Figure 2 is a schematic structural diagram of a computing device provided by an embodiment of the present invention;

Figure 3 is one of the flow diagrams of the data request processing method provided by the embodiment of the present invention;

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

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

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

Figure 7 is a second structural schematic diagram of a data request processing device 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 some of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without making creative efforts fall within the scope of protection of the present invention.

Hereinafter, the terms “first” and “second” are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the quantity of indicated technical features. Therefore, features defined as "first" and "second" may explicitly or implicitly include one or more of these features. In the description of the embodiments of the present disclosure, unless otherwise specified, "plurality" means two or more. In addition, 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 "according to" one or more stated conditions or values may in practice be based on additional condition or exceeds 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 calling request sent by the data calling device, it processes the data calling request to obtain the target interface parameters. Then, the gateway sends the target interface parameters to the business server, receives the target data sent by the business 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 that needs 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. Figure 1 shows a structure of the data request processing system. As shown in Figure 1, the data request processing system may include: data calling device 11, gateway 12, registration server 13 and business server 14. The data calling device 11 establishes a connection with the gateway 12 through wired communication or wireless communication. Connections are established between the gateway 12, the registration server 13, and the business server 14 through wired communication or wireless communication.

The data calling device 11 is used to send a data calling request to the gateway 12. The data calling request is used to request target data and receive the target data sent by the gateway 12 in a first format.

For example, the data calling device 11 may be a gateway such as a smartphone, a tablet computer, or a desktop computer.

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

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

The business server 14 is configured to provide target data in the second format to the gateway 12 . The business server 14 is also used 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 business server 14 are similar, and all include elements included in the computing device shown in Figure 2. The following takes the computing device shown in Figure 2 as an example to introduce the hardware structure of the data calling device, gateway, registration server and business server.

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 may 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 collective name for multiple processing elements. For example, the processor 21 may be a general-purpose central processing unit (CPU) or other general-purpose processor 21 or the like. The general 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, such as 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 (random access memory, RAM) or a ROM that can store information and instructions. Other types of dynamic storage devices may also be electrically erasable programmable read-only memory 22 (EEPROM), disk storage media or other magnetic storage devices, or may be used to carry or store instructions or Without limitation, any other medium that represents the desired program code in the form of a data structure and can be accessed by a computer.

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

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

The communication interface 23 is used to connect the computing device to other devices through a communication network. The communication network may be Ethernet, a radio access network (radio access network, RAN), wireless local area networks (WLAN), etc. 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 (Industry Standard Architecture, ISA) bus 24, a Peripheral Component Interconnect (PCI) bus 24 or an Extended Industry Standard Architecture (Extended Industry Standard Architecture, EISA) bus 24, etc. The bus 24 can be divided into an address bus 24, a data bus 24, a control bus 24, etc. For ease of presentation, only one thick line is used in FIG. 2 , but this does not mean that there is only one bus 24 or one type of bus 24 .

It should be noted that the structure shown in Figure 2 does not constitute a limitation of the computing device. In addition to the components shown in Figure 2, the computing device may include more or less components than shown in the figure, or a combination of certain components. components, or different component arrangements.

The data request processing method provided by the embodiment of the present invention is described below with reference to the accompanying drawings.

As shown in Figure 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 call request, which is used to request target data of the target business.

In one scenario, when the user calls the target data of the target service in the service server through the data calling device, the data calling device makes a data calling request to the gateway, and the data calling request is used to request the target data of the target service. For example, the data calling request can be an http request.

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

Optionally, when the gateway receives the data calling request sent by the data calling device, it uses the preset parsing rules to parse the data calling request to obtain the data calling address, calling method name and target business included in the data calling request. business parameters. Among them, the service parameters of the target service are necessary parameters for the target data called by the data calling device.

As an example, take the data invocation request as an http request. When the gateway receives the http request sent by the data calling device, it parses the http request and obtains the Uniform Resource Locator (Uniform ResourceLocator, URL) of the http request. The gateway is also used to perform path matching based on the URL of the http request, and determine the data calling address, calling method name and business parameters of the target business included in the http request.

For example, the data calling device has an operation and maintenance application installed, and the target business is to retrieve 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 entire month of November, the operation and maintenance personnel send an http request to the gateway through the data calling device to call the operation and maintenance data of November. The http request for calling the operation and maintenance data in November includes the data calling address, calling method name, and date and other business parameters. After receiving the http request, the gateway parses the http request and determines the data calling address, calling method name, date and other business parameters.

Optionally, after parsing the data calling request, the identity included in the data calling 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 data call permission. Only if it is determined that the account logged in to the data calling device has the permission to call the target data, the gateway will continue to perform the following steps.

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

Optionally, when the gateway determines that the account indicated by the identity identifier has the data calling authority, the target interface is determined based on the first mapping relationship. The data calling address corresponds to the interface in the business server one-to-one. When the gateway determines the data calling address, it will determine the target interface corresponding to the data calling address based on the first mapping relationship between the calling address and the interface. The target interface is the interface corresponding to the business server when calling target data.

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

Optionally, an interface can contain multiple methods, each method having a name. After the gateway determines the calling method name, it will determine the calling method corresponding to the target interface based on the second mapping relationship between the interface, method name, and method.

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

Optionally, since the data format used by the data calling device is the first format, the data format used by the business server is the second format. Therefore, when the gateway determines the target interface corresponding to 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 can be recognized by the business server, and generate the target interface parameters.

306. The gateway sends the target interface parameters to the business server through the target interface.

307. The gateway receives the target data sent by the business 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.

Using the data request processing method provided by the present invention, when the gateway receives the data calling request sent by the data calling device, the target interface parameters are obtained by processing the data calling request. Then, the gateway sends the target interface parameters to the business server, receives the target data sent by the business server, and converts the target data from the second format to the first format, so that the data calling device can obtain the data that needs to be called. Compared with the existing technology, when the gateway needs to call a service in the business server, it needs to write boilerplate 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 interface specifications. Moreover, the gateway can provide customized parameter conversion, which improves the convenience and security of interface management.

In conjunction with Figure 3, as shown in Figure 4, the data request processing method provided by the embodiment of the present invention may also 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 the first mapping relationship between the calling address and the interface, and the second mapping relationship between the interface, method name, and method to the gateway. 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 change, the registration server will actively send the change information to the gateway.

In conjunction with Figure 4, as shown in Figure 5, the data request processing method provided by the embodiment of the present invention may also include the following steps 501 and 502.

501. The business server obtains the identified default interface. Among them, the preset interface is used to call the target data of the target business.

502. The business server sends the preset interface and the method information corresponding to the preset interface to the registration server. 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.

Optionally, after the business 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. When the business server determines the interfaces that need to be exposed, it identifies the interfaces that need to be exposed by annotating the interfaces that need to be exposed, and obtains the identified preset interfaces. The preset interfaces are used to call the target business. 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. This allows the interface in the business server to be automatically exposed and discovered by the registration server, and avoids modification of the interface in the business server. Duplicate identification.

Optionally, after the registration server obtains the preset interface and the method information corresponding to the preset interface, it generates the above-mentioned first mapping relationship and the second mapping relationship based on the preset interface and the method information corresponding to the preset interface.

The above mainly introduces the solution provided by the embodiment of the present invention from the perspective of the data request processing device. It can be understood that, in order to implement the above functions, the data request processing device includes hardware structures and/or software modules corresponding to each function. Those skilled in the art will readily appreciate that, in conjunction with the algorithm steps of each example described in the embodiments disclosed herein, the present invention can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the 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 specific application, but such implementations should not be considered to be beyond the scope of the present invention.

Figure 6 shows a possible composition diagram of the data request processing device 600 involved in the above embodiment. As shown in Figure 6, the data request processing device 600 may include: an acquisition unit 601, an analysis unit 602, and a determination unit 603 and generation unit 604.

Among them, the obtaining unit 601 is used to obtain a data calling request, and the data calling request is used to request target data of the target service. The parsing unit 602 is configured to parse the data calling request obtained by the acquisition unit, and obtain the data calling address, calling method name and business parameters of the target service included in the data calling request. The determining unit 603 is configured to determine the target interface corresponding to the data calling address obtained by the parsing unit based on the first mapping relationship between the calling address and the interface, and determine the corresponding target interface based on the second mapping relationship between the interface, method name, and method. calling method. 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, and generate target interface parameters. The acquisition unit 601 is also used to send target interface parameters to the business server through the target interface, and receive target data sent by the business server. The generating unit 604 is also used to convert the target data acquired by the acquiring unit from the second format to the first format.

After the above parsing unit 602 parses the data calling request, it can also obtain the identity included in the data calling request.

Optionally, the determining unit 603 is also configured to determine whether the account indicated by the identity identifier has data calling permission based on the identity identifier and the pre-stored identity verification policy.

Optional, determining unit 603 is specifically used for:

When it is determined that the account indicated by the identity identifier has the data calling authority, the target interface is determined based on the first mapping relationship.

Optionally, the acquisition unit 601 is also 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.

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

Among them, the obtaining unit 701 is used to obtain the identified preset interface, and the preset interface is used to call 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. 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 device provided by the embodiment of the present invention includes but is not limited to the above modules.

In actual implementation, the acquisition unit, analysis unit, determination unit, generation unit and sending unit can be implemented by the processor 21 shown in Figure 2 calling the program code in the memory 22. For its specific execution process, please refer to the description of the data request processing method shown in Figures 3 to 6, and will not be described again here.

Another embodiment of the present invention also provides a computer-readable storage medium. Computer instructions are stored in the computer-readable storage medium. When the computer instructions are run on the data request processing device, the data request processing device executes the above method embodiment. Each step performed by the data request processing device in the method flow shown.

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

In another embodiment of the present invention, a computer program product is also provided. The computer program product includes instructions. When the instructions are run on a data request processing device, the data request processing device executes the method flow shown in the above method embodiment. Each step performed by the data request processing device.

In the above 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 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 computer execution instructions are loaded and executed on a computer, processes or functions according to embodiments of the present invention are generated 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, e.g., computer instructions may be transmitted from a website, computer, server or data center via a wired link (e.g. Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means to transmit to another website, computer, server or data center. Computer-readable storage media can be any available media that can be accessed by a computer or include one or more data storage devices such as servers and data centers that can be integrated with the media. Available media may be magnetic media (eg, floppy disk, hard disk, magnetic tape), optical media (eg, DVD), or semiconductor media (eg, solid state disk (SSD)), etc.

The above are only specific embodiments of the present invention, but the protection scope of the present invention is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present invention should be covered by the protection scope of the present invention. . Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims (9)

1. A data request processing method, characterized by including: Obtain a data call request, which is used to request target data of the target business; Parse the data calling request to obtain the data calling address, calling method name and business parameters of the target service included in the data calling request; Based on the first mapping relationship between the calling address and the interface, determine the target interface corresponding to the data calling address; Based on the second mapping relationship between the interface, the method name, and the method, determine the calling method corresponding to the target interface; Convert the service parameters and the calling method from the first format to the second format, and generate target interface parameters; Send the target interface parameters to the business server through the target interface; Receive the target data sent by the business server; converting the target data from the second format to the first format; Wherein, after parsing the data calling request, the identity included in the data calling request is also obtained; Based on the identity identifier and the pre-stored identity verification policy, determine whether the account indicated by the identity identifier has data calling authority; Determining the target interface corresponding to the data calling address based on the first mapping relationship between the calling address and the interface includes: When it is determined that the account indicated by the identity identifier has data calling authority, the target interface is determined based on the first mapping relationship. 2. The data request processing method according to claim 1, characterized in that the data request processing method further includes: Send subscription information to the registration server; Receive the first mapping relationship and the second mapping relationship sent by the registration server. 3. A data request processing method, characterized by including: Obtain the identified preset interface, which is used to call the target data of the target service; Send the 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. method. 4. A data request processing device, characterized in that it includes: An acquisition unit, used to acquire a data call request, where the data call request is used to request target data of a target service; A parsing unit, configured to parse the data calling request obtained by the obtaining unit, and obtain the data calling address, calling method name and business parameters of the target service included in the data calling request; The determining unit is configured to determine the target interface corresponding to the data calling address obtained by the parsing unit based on the first mapping relationship between the calling address and the interface, and determine the target interface based on the second mapping relationship between the interface, method name, and method. The calling method corresponding to the target interface; A generating unit, 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, and generate target interface parameters; The acquisition unit is also configured to send the target interface parameters to the business server through the target interface, and receive the target data sent by the business server; The generating unit is also configured to convert the target data obtained by the obtaining unit from the second format to the first format. 5. The data request processing device according to claim 4, characterized in that, after the parsing unit parses the data call request, the identity identifier included in the data call request is also obtained; The determination unit is also configured to determine whether the account indicated by the identity identifier has data calling authority based on the identity identifier and a pre-stored identity verification policy; The determining unit is specifically configured to: determine the target interface based on the first mapping relationship when it is determined that the account indicated by the identity identifier has data calling authority. 6. The data request processing device according to claim 4 or 5, characterized in that the obtaining unit is further configured to send subscription information to a registration server, and receive the first mapping relationship and the sum of the first mapping relationship sent by the registration server. the second mapping relationship. 7. A data request processing device, characterized in that it includes: An acquisition unit, configured to acquire the identified preset interface, which is used to call the target data of the target service; A sending unit, configured to send the preset interface and method information corresponding to the preset interface to the registration server. The method information includes a calling address corresponding to the preset interface, and at least A method name and method. 8. A data request processing device, characterized in that the data request processing device includes: a processor and a memory; the memory is used to store computer program code, and the computer program code includes computer instructions; when the processor When executing the computer instructions, the data request processing device executes the data request processing method as described in any one of claims 1-2, or executes the data request processing method as claimed in claim 3. 9. A computer-readable storage medium, characterized in that it includes computer instructions, and when the computer instructions are run on a data request processing device, the data request processing device causes the data request processing device to execute any one of claims 1-2. The data request processing method described in claim 3, or the data request processing method described in claim 3.