WO2018201978A1

WO2018201978A1 - Interface call data processing method, apparatus, computer device and storage medium

Info

Publication number: WO2018201978A1
Application number: PCT/CN2018/084762
Authority: WO
Inventors: 陈林; 张国辉
Original assignee: 平安科技（深圳）有限公司
Priority date: 2017-05-04
Filing date: 2018-04-27
Publication date: 2018-11-08
Also published as: CN108255905A; CN108255905B

Abstract

An interface call data processing method, comprising: receiving an interface call request, and acquiring a target interface code in said interface call request; acquiring a target data format corresponding to the target interface code; performing corresponding format conversion on call parameters in said interface call request according to the acquired target data format; acquiring an interface address corresponding to the target interface code according to mapping between interface codes and interface addresses configured in an interface routing service; according to the interface address, allocating the format-converted call parameters to a corresponding target interface for call processing.

Description

Interface call data processing method, device, computer device and storage medium

Cross-reference to related applications

The present application claims to be filed on May 4, 2017, the Chinese Patent Office, the number of which is incorporated herein by reference. In this application.

Technical field

The present application relates to the field of computer technologies, and in particular, to an interface call data processing method, apparatus, computer device, and storage medium.

Background technique

Nowadays, single-platform systems include more and more types of services and functional modules, resulting in many types of interfaces in the same platform, and different calling methods vary in size. At present, the registration center is used as a third party to judge and forward the interface call request.

However, the inventor realized that the registration center usually needs to be established in the line of business dimension. Generally, a service line needs to establish a corresponding registration center, so that the entire system platform needs to spend more resources and costs to establish a registration center cluster. .

Summary of the invention

In accordance with various embodiments disclosed herein, an interface call data processing method, apparatus, computer apparatus, and non-transitory computer readable storage medium are provided.

An interface call data processing method, including:

Receiving an interface call request, and acquiring a target interface code in the interface call request;

Obtaining a target data format corresponding to the target interface encoding;

And correspondingly converting the calling parameter in the interface call request according to the obtained target data format;

Obtaining an interface address corresponding to the target interface code according to a mapping relationship between the interface code and the interface address set in the interface routing service; and

According to the interface address, the formatted call parameters are allocated to the corresponding target interface for calling processing.

An interface calls a data processing device, including:

An acquiring module, configured to receive an interface call request, obtain a target interface code in the interface call request, and obtain a target data format corresponding to the target interface code;

a format conversion module, configured to perform a corresponding format conversion on the calling parameter in the interface call request according to the obtained target data format;

An interface address mapping module, configured to obtain an interface address corresponding to the target interface code according to a mapping relationship between an interface code and an interface address set in the interface routing service; and

The processing module is configured to allocate the formatted call parameters to the corresponding target interface according to the interface address for calling processing.

A computer device comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to execute The following steps:

Obtaining a target data format corresponding to the target interface encoding;

One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause one or more processors to perform the steps of:

Obtaining a target data format corresponding to the target interface encoding;

Details of one or more embodiments of the present application are set forth in the accompanying drawings and description below. Other features, objects, and advantages of the invention will be apparent from the description and appended claims.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings to be used in the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present application, Those skilled in the art can also obtain other drawings based on these drawings without any creative work.

1 is an application environment diagram of an interface call data processing method in accordance with one or more embodiments.

2 is a block diagram of a computer device in accordance with one or more embodiments.

3 is a flow diagram of an interface call data processing method in accordance with one or more embodiments.

4 is a flow diagram of a callback step of returning data in accordance with one or more embodiments.

FIG. 5 is a flow diagram of a log file generation step in accordance with one or more embodiments.

6 is a flow diagram of a log file generation step in accordance with another or more embodiments.

7 is a block diagram of an interface call data processing apparatus in accordance with one or more embodiments.

8 is a block diagram of an interface call data processing apparatus in accordance with another or more embodiments.

9 is a block diagram of an interface call data processing apparatus in accordance with yet one or more embodiments.

detailed description

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting.

FIG. 1 is an application environment diagram of an interface call data processing method in an embodiment. Referring to FIG. 1, the application environment includes an interface 110 and a called platform 120 that are connected through a network. The interface invoking device 110 refers to a device that initiates an interface call request to request an interface in the called platform 120. The interface invoking device 110 can be either a terminal or a server. The called platform 120 refers to a platform system that provides an interface called by the interface calling device 110. For example, when the interface invoking device 110 needs to use a certain function in the called platform 120, an interface call request is sent to the called platform 120 to request to call the corresponding interface in the called platform 120 for implementing the function. It should be noted that the interface is not limited to being invoked by the called platform. It can be understood that the called platform 120 can also have the capability of calling interfaces of other devices or platforms.

Specifically, the called platform 120 receives the interface call request sent by the interface invoking device 110, obtains the target interface code in the interface call request, and obtains the target format corresponding to the target interface code; according to the acquired target format, the interface call request Call the parameters for the corresponding format conversion. The called platform 120 obtains the interface address corresponding to the target interface code according to the mapping relationship between the interface code and the interface address configured in the interface routing service. And according to the interface address, the formatted call parameters are allocated to the corresponding target interface in the called platform 120 for call processing.

2 is a schematic diagram showing the internal structure of a computer device in an embodiment. The computer device may be the called platform 120 in FIG. 1, and the called platform 120 may be implemented by a separate server or a server cluster composed of multiple physical servers. Referring to Figure 2, the computer device includes a processor, memory, and network interface coupled by a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium, an internal memory. A non-volatile storage medium of a computer device stores an operating system and computer readable instructions. The internal memory in the computer device provides an environment for the operation of the operating system and computer readable instructions in the non-volatile storage medium. The computer readable instructions, when executed by a processor, cause the processor to perform an interface call data processing method. The network interface is used to connect to the network for communication, such as receiving an interface call request.

It will be understood by those skilled in the art that the structure shown in FIG. 2 is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation of the computer device to which the solution of the present application is applied. The specific computer device may It includes more or fewer components than those shown in the figures, or some components are combined, or have different component arrangements.

As shown in FIG. 3, in one of the embodiments, an interface call data processing method is provided. This embodiment is mainly illustrated by the method applied to the called platform in FIG. 1 above. Referring to FIG. 3, the interface calling data processing method specifically includes the following steps:

S302. Receive an interface call request, and obtain a target interface code in the interface call request.

Specifically, the interface calling device sends an interface call request to the called platform when the interface of the called platform is to be called, and the interface call request includes the target interface code. The target interface is the interface that is requested to be called. The target interface encoding is used to uniquely identify the target interface.

In one of the embodiments, the target interface code in the interface call request may be one or more, that is, the called platform may receive calls to multiple interfaces in parallel.

S304. Obtain a target data format corresponding to the target interface code.

The target data format is a data format conforming to the interface specification of the interface corresponding to the target interface encoding.

In one embodiment, the correspondence between the interface code and the data format is pre-stored in the called platform, and the called platform acquires the target data format corresponding to the target interface code according to the correspondence.

S306. Perform the format conversion on the calling parameter in the interface call request according to the obtained target data format.

The call parameters are included in the interface call request. The call parameter refers to the parameter related to the interface call processing. It can be understood that the called interface can perform corresponding call processing according to the calling parameter to obtain data that the interface calls the device to call.

It can be understood that different interfaces may have different interface specifications. When the target interface needs to be called, the calling parameter in the interface call request needs to be converted according to the target data format corresponding to the target interface, that is, converted into a target. Interface specification data.

S308. Obtain an interface address corresponding to the target interface code according to the mapping relationship between the interface code and the interface address set in the interface routing service.

The interface routing service is set in the called platform. An interface routing service is a program that can be used to implement interface routing addressing. The interface route addressing function refers to the function of routing the address to the address of the corresponding interface according to the interface code. It can be understood that the interface routing service does not only have the interface routing address function, and the interface routing service can also have other functions.

Specifically, the mapping relationship between the interface code and the interface address is preset in the interface routing service. The interface code corresponds to the interface address mapping. The called platform acquires an interface address corresponding to the target interface code according to the mapping relationship. Interface address, used to find the corresponding interface in the called platform.

S310, according to the interface address, assigning the formatted call parameter to the corresponding target interface for calling processing.

Specifically, according to the interface address, the corresponding interface is found in the called platform, and the found interface is the target interface. The called platform allocates the formatted call parameters to the found target interface, and the target interface performs corresponding call processing according to the formatted call parameters.

The above interface invokes a data processing method, and by setting an interface routing service in the called platform itself, when receiving an interface call request, the mapping relationship between the interface code and the interface address set in the service may be directly obtained according to the interface reason, that is, the interface may be obtained. To the interface address with the target interface, the target interface can be found according to the interface address. Compared with the traditional method, the registration center needs to be specially set to make the interface call, which greatly reduces the cost of the interface call processing. In addition, according to the target data format corresponding to the target interface code, the call parameter in the interface call request is subjected to corresponding format conversion; and the call parameter transfer after the format transfer refers to the target interface corresponding to the interface address, thereby avoiding the The calling interface does not recognize the error caused by the data.

As shown in FIG. 4, in one embodiment, the method further includes a step of invoking data return, specifically including the following steps:

S402. Acquire an initial data format of a call parameter in an interface call request.

The initial data format of the call parameter in the interface call request refers to the data format of the call parameter in the interface call request before the format conversion according to the target format.

Specifically, the initial data format including the calling parameter in the interface call request may be, and the called platform may directly obtain the initial data format of the calling parameter included in the interface call request.

Alternatively, the called platform performs format analysis on the calling parameters before the format conversion to extract the corresponding format data, and obtains the corresponding initial data format according to the extracted format data combination.

In addition, a plurality of data format templates may be preset in the called platform, and the calling parameters before the format conversion are matched and analyzed with each data format template, and the data format template with the highest matching degree is used as the calling parameter before the format conversion. The initial data format.

It can be understood that step S402 is not limited to being performed after step S310, and step S402 can be performed after step S302 and any step before step S404.

S404: Perform format conversion on the data obtained after the call processing based on the initial data format.

Specifically, the called platform may perform call processing according to the call parameter converted by the format interface by the target interface, and obtain corresponding data after the call processing, and the data obtained by the call processing is data required by the interface calling device.

The called platform can perform corresponding format conversion on the data obtained after the call is processed according to the initial data format. It can be understood that the data converted according to the initial data format conforms to the data format requirements of the interface calling device.

S406, returning the format converted data.

Specifically, the called platform may return the format converted data directly to the interface calling device according to the data channel established between the two when the interface calling device sends the interface call request. The called platform can also return the format converted data to the interface calling device by other means. Here, the implementation manner of returning the format converted data to the interface calling device by the called platform is not limited, as long as the format converted data is returned to the interface calling device.

In the above embodiment, the initial data format of the calling parameter in the interface call request is automatically obtained, and after the called data is acquired, the data obtained after the processing is automatically converted according to the initial data format, and then returned, that is, The called platform end completes the conversion of the data format, and does not need to perform data format conversion on the interface calling device side, which reduces the requirement for the interface calling device, thereby improving the applicability of the called platform.

In one embodiment, the method further includes: invoking log information according to the interface routing service record interface; the recorded interface call log information includes call log information of any interface in the invoked platform.

The interface invokes log information, including interface call time information, interface information of the requested call, and returned data information. The interface calls time information, which may include the interface call start time and the time of returning the called data or the duration of the interface call. The interface information requested to be invoked may include the target interface encoding of the requested call. The returned data information returned may include information such as the size or format of the data being called.

Specifically, the interface routing service in the called platform has an interface call log information management function. The interface invokes the log information management function, which may include a record function for calling the log of the interface. In one embodiment, the interface call log information management function may further include an access authority verification function for the interface call log, a function of integrating the call log information, and a function of outputting the call log information to generate a corresponding log file.

Because the call to any interface in the called platform is to determine the interface address that has a mapping relationship with the target interface code through the interface routing service, the call processing of any interface in the called platform will be uniformly routed through the interface. service. Therefore, the interface routing service can uniformly record the interface call log information. The interface calls log information, which is the log information related to the interface call. The log information is called according to the interface recorded by the interface routing service, including the call log information of any interface in the called platform.

In the foregoing embodiment, the interface routing service uniformly records the interface call logs uniformly, and implements unified management of the call log information of the interface, thereby avoiding the independent management of the self-log information of the programs corresponding to the interfaces, and the interface call is caused. The log information is mixed with other massive log information without using the query of the log information for the interface. In addition, the program corresponding to each interface is also prevented from independently managing the interface call log information, and the interface call log information is too scattered, which is not conducive to the analysis of the interface call. The interface routing service uniformly records the interface call logs uniformly, which implements centralized management of the interface call log information, and improves the efficiency of query log information and interface call problem analysis.

As shown in FIG. 5, in one embodiment, the method further includes a log file generating step, which specifically includes the following steps:

S502. Acquire an interface call log file generation request.

The interface invokes a log file generation request for requesting the generation of an interface to call the relevant log file.

Specifically, the user (such as a technician) can perform an interface call log file generating operation on the terminal, and the terminal generates and sends a corresponding interface call log file generating request to the called platform in response to the operation. In one of the embodiments, the interface call log file generation request includes a user identifier, and the user identifier is used to uniquely identify a user who performs an interface call log file generation operation.

S504. Acquire a rights configuration file corresponding to the user identifier in the interface call log file generation request.

In one of the embodiments, the correspondence between the user identifier and the rights profile is preset in the called platform. A rights profile is a file that describes the operation rights information of the corresponding user.

The called platform obtains a rights configuration file corresponding to the user identifier in the interface call log file generation request according to the correspondence between the user identifier and the rights configuration file.

S506, parsing the rights configuration file, and obtaining corresponding authority information.

The permission information obtained by the called platform to resolve the permission configuration file may include permission information for accessing the log information of the interface, and may also include other operation authority information of the user. The permission information for accessing the log information of the interface may include operation permission information such as querying, filtering, or outputting the log information of the interface.

S508. When it is determined that the interface call log file generation permission is satisfied according to the permission information, the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and the corresponding log file is generated.

The interface calls the log file generation permission, which refers to the corresponding log information output and the permission to generate the log file.

Specifically, the called platform may determine, according to the permission information, whether the interface call log file generation authority is satisfied, and if yes, obtain log information corresponding to the interface call log file generation permission from the interface call log information recorded in the interface routing service, and output the log information. To generate the corresponding log file, if not, you can return the prompt message that the interface call log file generation request failed or not process.

The called platform determines whether the interface call log file generation permission is satisfied according to the permission information, and may determine whether the interface permission log file generation permission is included in the permission information. The log information corresponding to the interface call log file generation permission is an interface call log information that can be queried and outputted to generate a log file. It can be understood that the interface invokes the log file generation permission, which may be a log file generation permission for calling the log information of all the interfaces recorded in the interface call service, or may be a log file generation of the interface call log information recorded in the interface call service. Permissions.

In the above embodiment, by setting the permission information, the log file generation authority is generated, and when the interface call log file generation permission is satisfied, the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output. Generate the appropriate log file. Greatly improved security.

As shown in FIG. 6, in one embodiment, step S508 specifically includes the following steps:

S602. Acquire a user role corresponding to the user identifier according to the authority information.

The permission information is multi-level permission information, and the permission information may include role level rights, function level rights, data level rights, and operation level rights.

A role is the work or location of a user in an organization or task. The permissions for different roles can be different. For example, the head of the human resources department and the general manager of the human resources department are in different roles. Function level permission refers to the user's permission to use some functions. For example, the access interface call log belongs to a function permission. Data level permissions refer to the permissions of the data content that can be accessed. For example, you can access all interface call log information, which belongs to data level permissions. Operation level permissions refer to the operation rights to accessible data, such as output permissions, such as output, add, and delete.

Specifically, the authority information is controlled according to the following hierarchical relationship: role level level authority -> function level level authority -> data level level authority -> operation level level authority. That is, the role level authority is the top level authority management level, and the operation level authority is the lowest level authority management level. When the called platform obtains data and/or permission judgment according to the authority information, it may sequentially perform the hierarchical order of the role level authority->function level level authority->data level level authority->operation level level authority.

S604. When the user role has the function permission to access the interface call log, obtain the content access permission information of the interface call log corresponding to the user role.

The function permission of the access interface call log refers to the access function of the call log to the interface.

Specifically, the called platform determines, according to the permission information, whether the function level permission corresponding to the acquired user role includes the function permission of the access interface call log, and if yes, the user role has the function permission to access the interface call log.

When the user role has the function permission to access the interface call log, the called platform further obtains the content access authority information of the interface call log corresponding to the user role according to the permission information. The content access permission information of the interface call log refers to the access right (equivalent to the data level level authority) of the content of the interface call log, which is used to represent the accessible interface call log information.

S606. When the user role invokes log information on the accessible interface represented by the content access permission information, and has the log file generation permission, obtains an interface call log information that is represented by the content access permission information and corresponds to the log file generation authority. .

The called platform determines whether the user role has the log file generation permission for the accessible interface call log information represented by the content access authority information according to the permission information. Log file generation permission refers to the permission to output log information to the interface to generate log files (equivalent to operation level permissions). When the user role invokes the log information on the accessible interface represented by the content access permission information, and has the log file generation permission, the called platform acquires the interface call log represented by the content access permission information and corresponding to the log file generation authority. Information, that is, get the interface call log information that can be accessed and output.

It can be understood that the interface call log information that is represented by the obtained content access right information and corresponds to the log file generation authority may be the interface call log information corresponding to one or more interfaces in the called platform.

S608. Generate a corresponding log file according to the obtained interface call log information.

Specifically, the invoked platform may directly output the obtained interface call log information according to a log file generation format to generate a corresponding log file. In one embodiment, the invoked platform may sort the output of the acquired interface call log information by an interface dimension or by an occurrence timing of the interface call log information to generate a corresponding log file.

The called platform may also select the corresponding interface call log information to output the corresponding interface call log information according to the preset rule or other requirements in the interface call log generation request to generate a corresponding log file.

In the above embodiment, the multi-level authority information of the role level permission->function level authority->data level level authority->operation level level authority is refined, and the granularity of the authority control of the generation of the log file is refined, so that the authority management is more controlled. Effective, and thus improved security.

In one of the embodiments, the interface call log file generation request further includes a log information query condition. Step S608, comprising: querying corresponding log information from the acquired interface call log information according to the log information query condition; outputting the invoked interface call log information to generate an interface call log file.

The log information query condition refers to the filter condition for invoking log information on the interface. Specifically, when the user invokes the log file generation operation, the user can input the log information query condition in the terminal interface to obtain the interface call log information that meets the requirements. In the terminal interface, the user can input the log information query condition or manually input the customized log information query condition by selecting the method.

In the foregoing embodiment, the log information query condition further refines the query of the log information, improves the validity and flexibility of the log information query, and avoids the resources caused by the queried log information not meeting the user requirements. waste.

It should be understood that the various steps in the above-described flowcharts are sequentially displayed in accordance with the indication of the arrows, but these steps are not necessarily performed in the order indicated by the arrows. Except as explicitly stated herein, the execution of these steps is not strictly limited, and the steps may be performed in other orders. Moreover, at least some of the steps in the above flow chart may include a plurality of sub-steps or stages, which are not necessarily performed at the same time, but may be executed at different times, and these sub-steps or stages The order of execution is not necessarily performed sequentially, but may be performed alternately or alternately with at least a portion of other steps or sub-steps or stages of other steps.

As shown in FIG. 7, an interface call data processing apparatus 700 is provided. The apparatus includes an acquisition module 702, a format conversion module 704, an interface address mapping module 706, and a call processing module 708, where:

The obtaining module 702 is configured to receive an interface call request, obtain a target interface code in the interface call request, and obtain a target data format corresponding to the target interface code.

The format conversion module 704 is configured to perform corresponding format conversion on the calling parameter in the interface call request according to the acquired target data format;

The interface address mapping module 706 is configured to obtain an interface address corresponding to the target interface code according to the mapping relationship between the interface code and the interface address set in the interface routing service.

The calling processing module 708 is configured to allocate the formatted call parameters to the corresponding target interface according to the interface address for calling processing.

In one embodiment, the obtaining module 702 is further configured to obtain an initial data format of the calling parameter in the interface call request.

The format conversion module 704 is further configured to perform format conversion on the data obtained after the call processing based on the initial data format; and return the data obtained after the format conversion.

As shown in FIG. 8, in one embodiment, the apparatus 700 further includes:

The log information recording module 710 is configured to invoke log information according to the interface routing service record interface; the recorded interface call log information includes call log information of any interface in the called platform.

As shown in FIG. 9, in one embodiment, the obtaining module 702 is further configured to obtain an interface call log file generation request, and obtain a rights configuration file corresponding to the user identifier in the interface call log file generation request.

In this embodiment, the apparatus 700 further includes:

The permission information parsing module 712 is configured to parse the rights configuration file to obtain corresponding authority information.

The log file generating module 714 is configured to: when it is determined that the interface call log file generation permission is satisfied according to the permission information, obtain log information corresponding to the interface call log file generation authority information from the interface routing service, and output the corresponding log file.

In one embodiment, the log file generating module 714 is further configured to acquire a user role corresponding to the user identifier according to the rights information; and when the user role has the function permission of the access interface to invoke the log, obtain the interface call log corresponding to the user role. The content access permission information; when the user role invokes the log information on the accessible interface represented by the content access permission information, and has the log file generation permission, the content access permission information is represented, and the log file generation authority is corresponding. The interface invokes log information; the corresponding log file is generated according to the obtained interface call log information.

In one of the embodiments, the interface call log file generation request further includes a log information query condition. The log file generating module 714 is further configured to: according to the log information query condition, query the corresponding log information from the acquired interface call log information; output the query interface call log information, and generate an interface call log file.

For specific definitions of the interface call data processing apparatus, reference may be made to the definition of the interface call data processing method in the above, and details are not described herein again. Each of the modules in the above-described interface call data processing apparatus may be implemented in whole or in part by software, hardware, and combinations thereof. Each of the above modules may be embedded in or independent of the processor in the computer device, or may be stored in a memory in the computer device in a software form, so that the processor invokes the operations corresponding to the above modules.

In one embodiment, a computer apparatus is provided comprising a memory and one or more processors having stored therein computer readable instructions that, when executed by the processor, cause one or more processors The following steps are performed: receiving an interface call request, obtaining a target interface code in the interface call request, acquiring a target data format corresponding to the target interface code, and performing a format conversion on the call parameter in the interface call request according to the acquired target data format. According to the mapping relationship between the interface code and the interface address set in the interface routing service, the interface address corresponding to the target interface code is obtained; according to the interface address, the formatted call parameter is allocated to the corresponding target interface for calling processing.

In one embodiment, the computer readable instructions further cause the processor to: obtain an initial data format of the call parameters in the interface call request; format convert the data obtained after the call processing based on the initial data format; return format The data obtained after conversion.

In one of the embodiments, the computer readable instructions further cause the processor to perform the step of: invoking log information in accordance with an interface routing service record interface; the recorded interface call log information includes call log information for any of the interfaces in the invoked platform.

In one embodiment, the computer readable instructions further cause the processor to: obtain an interface call log file generation request; obtain a rights configuration file corresponding to the user identifier in the interface call log file generation request; and resolve the rights configuration file The corresponding permission information is obtained. When the permission to generate the interface call log file is determined according to the permission information, the log information corresponding to the interface call log generation authority information is obtained from the interface routing service and output, and the corresponding log file is generated.

In one embodiment, when the processor determines that the interface call log file generation permission is satisfied according to the authority information, the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and the corresponding information is generated. The log file includes: obtaining a user role corresponding to the user identifier according to the permission information; and obtaining the content access permission information of the interface call log corresponding to the user role when the user role has the function permission of the access interface to invoke the log; Invoking log information to the accessible interface represented by the content access permission information, and having the log file generation permission, acquiring the interface calling log information represented by the content access permission information and corresponding to the log file generating permission; Call the log information to generate the corresponding log file.

In one embodiment, the interface call log file generation request further includes a log information query condition; the processor performs a log file according to the acquired interface call log information, and includes: obtaining the corresponding log file according to the log information query condition. The interface calls the log information to query the corresponding log information; the queried interface calls the log information output, and generates an interface call log file.

In one of the embodiments, a storage medium storing computer readable instructions, when executed by one or more processors, causes one or more processors to perform the steps of: receiving an interface call Requesting, obtaining the target interface code in the interface call request; obtaining the target data format corresponding to the target interface code; performing the format conversion on the call parameter in the interface call request according to the acquired target data format; setting according to the interface routing service The mapping relationship between the interface code and the interface address obtains the interface address corresponding to the target interface code; according to the interface address, the format converted call parameter is allocated to the corresponding target interface for calling processing.

One of ordinary skill in the art can understand that all or part of the process of implementing the above embodiments can be completed by computer readable instructions, which can be stored in a non-volatile computer. The readable storage medium, which when executed, may include the flow of an embodiment of the methods as described above. Any reference to a memory, storage, database or other medium used in the various embodiments provided herein may include non-volatile and/or volatile memory. Non-volatile memory can include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of formats, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronization chain. Synchlink DRAM (SLDRAM), Memory Bus (Rambus) Direct RAM (RDRAM), Direct Memory Bus Dynamic RAM (DRDRAM), and Memory Bus Dynamic RAM (RDRAM).

The technical features of the above embodiments may be arbitrarily combined. For the sake of brevity of description, all possible combinations of the technical features in the above embodiments are not described. However, as long as there is no contradiction in the combination of these technical features, It is considered to be the range described in this specification.

The above embodiments are merely illustrative of several embodiments of the present application, and the description thereof is more specific and detailed, but is not to be construed as limiting the scope of the invention. It should be noted that a number of variations and modifications may be made by those skilled in the art without departing from the spirit and scope of the present application. Therefore, the scope of the invention should be determined by the appended claims.

Claims

An interface call data processing method, including:

Receiving an interface call request, and acquiring a target interface code in the interface call request;

Obtaining a target data format corresponding to the target interface encoding;

And correspondingly converting the calling parameter in the interface call request according to the obtained target data format;

Obtaining an interface address corresponding to the target interface code according to a mapping relationship between the interface code and the interface address set in the interface routing service; and

According to the interface address, the formatted call parameters are allocated to the corresponding target interface for calling processing.
The method of claim 1 further comprising:

Obtaining an initial data format of the calling parameter in the interface call request;

Performing format conversion on the data obtained after the call processing based on the initial data format; and

Returns the data obtained after the format conversion.
The method of claim 1 further comprising:

The log information is invoked according to the interface routing service record interface; the recorded call log information of the interface includes call log information of any interface in the called platform.
The method of claim 3, further comprising:

Obtain an interface call log file generation request;

Obtaining a rights configuration file corresponding to the user identifier in the interface call log file generation request;

Parsing the rights configuration file to obtain corresponding permission information; and

When it is determined that the interface call log file generation authority is satisfied according to the permission information, the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and a corresponding log file is generated.
The method according to claim 4, wherein, when it is determined that the interface call log file generation authority is satisfied according to the authority information, obtaining the permission information for generating the log file from the interface by the interface routing service Corresponding log information is output and generated, and corresponding log files are generated including:

Obtaining a user role corresponding to the user identifier according to the rights information;

When the user role has the function permission for accessing the interface call log, obtaining content access permission information of the interface call log corresponding to the user role;

When the user role invokes log information on an accessible interface represented by the content access right information, and has log file generation permission,

Obtaining an interface call log information that is represented by the content access authority information and that corresponds to the log file generation authority; and

Generating a corresponding log file according to the acquired interface call log information.
The method according to claim 5, wherein the interface call log file generation request further includes a log information query condition;

The generating the corresponding log file according to the acquired interface call log information includes:

Querying corresponding log information from the obtained log information of the interface according to the query condition of the log information; and

The queried interface calls log information output, and generates an interface call log file.
An interface calls a data processing device, including:

An acquiring module, configured to receive an interface call request, obtain a target interface code in the interface call request, and obtain a target data format corresponding to the target interface code;

a format conversion module, configured to perform a corresponding format conversion on the calling parameter in the interface call request according to the obtained target data format;

An interface address mapping module, configured to obtain an interface address corresponding to the target interface code according to a mapping relationship between an interface code and an interface address set in the interface routing service; and

The processing module is configured to allocate the formatted call parameters to the corresponding target interface according to the interface address for calling processing.
The apparatus according to claim 7, wherein the obtaining module is further configured to acquire an initial data format of a calling parameter in the interface call request; the format converting module is further configured to use the initial data format pair The data obtained after the processing is called for format conversion; the data obtained after the format conversion is returned.
The device according to claim 7, further comprising:

The log information recording module is configured to invoke log information according to the interface routing service record interface; the recorded interface call log information includes call log information of any interface in the called platform.
The device according to claim 9, wherein the obtaining module is further configured to: acquire an interface call log file generation request; and acquire a rights configuration file corresponding to the user identifier in the interface call log file generation request;

The device also includes:

a permission information parsing module, configured to parse the rights configuration file to obtain corresponding authority information; and

a log file generating module, configured to: when determining, according to the permission information, that the interface call log file generation permission is satisfied, obtaining log information corresponding to the interface call log file generation authority information from the interface routing service, and outputting, generating The corresponding log file.
The device according to claim 10, wherein the log file generating module is further configured to acquire a user role corresponding to the user identifier according to the rights information; and when the user role has a function of accessing an interface call log And obtaining the content access permission information of the interface call log corresponding to the user role; and when the user role invokes the log information on the accessible interface represented by the content access authority information, and has the log file generation permission And acquiring the interface call log information that is represented by the content access right information and corresponding to the log file generation authority; and generating a corresponding log file according to the acquired interface call log information.
The apparatus according to claim 11, wherein the interface call log file generation request further includes a log information query condition; the log file generation module is further configured to: according to the log information query condition, obtain the location The interface call log information is queried for the corresponding log information; the queried interface calls the log information output, and the interface calls the log file.
A computer device comprising a memory and one or more processors, the memory storing computer readable instructions, the computer readable instructions being executed by the processor, causing the one or more processors to execute Next steps:

Receiving an interface call request, and acquiring a target interface code in the interface call request;

Obtaining a target data format corresponding to the target interface encoding;

And correspondingly converting the calling parameter in the interface call request according to the obtained target data format;

Obtaining an interface address corresponding to the target interface code according to a mapping relationship between the interface code and the interface address set in the interface routing service; and

According to the interface address, the formatted call parameters are allocated to the corresponding target interface for calling processing.
The computer apparatus according to claim 13 wherein said computer readable instructions are further executed by said one or more processors to perform the following steps:

Obtaining an initial data format of the calling parameter in the interface call request;

Performing format conversion on the data obtained after the call processing based on the initial data format; and

Returns the data obtained after the format conversion.
The computer apparatus according to claim 13 wherein said computer readable instructions are further executed by said one or more processors to perform the following steps:

The log information is invoked according to the interface routing service record interface; the recorded call log information of the interface includes call log information of any interface in the called platform.
The computer apparatus according to claim 15, wherein said computer readable instructions are further executed by said one or more processors to perform the following steps:

Obtain an interface call log file generation request;

Obtaining a rights configuration file corresponding to the user identifier in the interface call log file generation request;

Parsing the rights configuration file to obtain corresponding permission information; and

When it is determined that the interface call log file generation authority is satisfied according to the permission information, the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and a corresponding log file is generated.
One or more non-transitory computer readable storage mediums storing computer readable instructions, when executed by one or more processors, cause the one or more processors to perform the following steps:

Receiving an interface call request, and acquiring a target interface code in the interface call request;

Obtaining a target data format corresponding to the target interface encoding;

And correspondingly converting the calling parameter in the interface call request according to the obtained target data format;

Obtaining an interface address corresponding to the target interface code according to a mapping relationship between the interface code and the interface address set in the interface routing service; and

According to the interface address, the formatted call parameters are allocated to the corresponding target interface for calling processing.
The storage medium of claim 17, wherein the computer readable instructions are further executed by the one or more processors to perform the following steps:

Obtaining an initial data format of the calling parameter in the interface call request;

Performing format conversion on the data obtained after the call processing based on the initial data format; and

Returns the data obtained after the format conversion.
The storage medium of claim 17, wherein the computer readable instructions are further executed by the one or more processors to perform the following steps:

The log information is invoked according to the interface routing service record interface; the recorded call log information of the interface includes call log information of any interface in the called platform.
The storage medium of claim 19, wherein the computer readable instructions, when executed by the one or more processors, further perform the following steps:

Obtain an interface call log file generation request;

Obtaining a rights configuration file corresponding to the user identifier in the interface call log file generation request;

Parsing the rights configuration file to obtain corresponding permission information; and

When it is determined that the interface call log file generation authority is satisfied according to the permission information, the log information corresponding to the interface call log file generation authority information is obtained from the interface routing service and output, and a corresponding log file is generated.