CN112346794A

CN112346794A - Interface calling method, device, equipment and medium

Info

Publication number: CN112346794A
Application number: CN202011130202.XA
Authority: CN
Inventors: 骆聪
Original assignee: Shenzhen Dingsheng Computer Technology Co ltd
Current assignee: Shenzhen Lexin Information Service Co.,Ltd.
Priority date: 2020-10-21
Filing date: 2020-10-21
Publication date: 2021-02-09

Abstract

The embodiment of the invention discloses an interface calling method, an interface calling device, interface calling equipment and a storage medium, wherein the method comprises the following steps: when the service information is received, determining a target service executing party for executing the service information; determining a target executive party identifier corresponding to a target service executive party, and acquiring at least one target calling interface corresponding to the target service executive party from a pre-established configuration file based on the target executive party identifier; and sending the service information to the target service executing party based on the at least one target calling interface. According to the technical scheme, the interfaces to be called of all the service execution parties are uniformly configured in the generalized calling service, and the corresponding target calling interfaces are obtained from the configuration files, so that the technical problems that a large amount of time is spent on developing and testing program codes corresponding to the service execution parties aiming at different service execution parties, resources are wasted, labor cost is high are solved, and the technical effect of conveniently and efficiently processing service information is achieved.

Description

Interface calling method, device, equipment and medium

Technical Field

The embodiment of the invention relates to the technical field of computers, in particular to an interface calling method, device, equipment and medium.

Background

In the aspect of credit business, in order to avoid the problem that the business of credit and lenders is too concentrated and the risk is high, the common measure is to continuously access new sub credit and lenders.

At present, the business preparation and the accessed documents of different sub credit lenders are different, and at this time, the credit lenders need to develop and write program codes corresponding to different sub credit lenders and debug the program codes so that the credit lenders can send the received credit business to other self credit lenders. As shown in fig. 1, the service information receiving party includes at least one sub credit lender, where the sub credit lenders are a, B, and C, and the service information receiving party receives program codes corresponding to different sub credit lenders when it is required to determine the sub credit lenders, and sends the service information to the corresponding sub credit lenders after determining the sub credit lenders.

That is, once a credit side receives a new sub credit side, a new program code needs to be developed, and more manpower and material resources need to be jointly adjusted, tested and divided, so that the technical problems of high cost and low efficiency exist.

Disclosure of Invention

The invention provides an interface calling method, an interface calling device, equipment and a storage medium, which are used for reducing the coupling between a service information receiver and a service information executor so as to achieve the technical effect of quickly, conveniently and effectively processing service information.

In a first aspect, an embodiment of the present invention provides an interface calling method, where the method includes:

when receiving the service information, determining a target service executing party for executing the service information;

determining a target executive party identifier corresponding to the target service executive party, and acquiring at least one target calling interface corresponding to the target service executive party from a pre-established configuration file based on the target executive party identifier;

and sending the service information to the target service executing party based on the at least one target calling interface.

In a second aspect, an embodiment of the present invention further provides an interface invoking device, where the interface invoking device includes:

the service execution party determining module is used for determining a target service execution party for executing the service information when the service information is received;

the target calling interface determining module is used for determining a target executive party identifier corresponding to the target service executive party and acquiring at least one target calling interface corresponding to the target service executive party from a pre-established configuration file based on the target executive party identifier;

and the service information sending module is used for sending the service information to the target service executing party based on the at least one target calling interface.

In a third aspect, an embodiment of the present invention further provides an apparatus, where the apparatus includes:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement an interface call method as in any of the embodiments of the invention.

In a fourth aspect, the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform the interface call method according to any one of the embodiments of the present invention.

According to the technical scheme of the embodiment of the invention, the interface to be called of each service executive executing the service information and the method corresponding to the interface are stored in the configuration file of the service calling system, so that after the service information is received and the service executive corresponding to the service information is determined, the target calling interface corresponding to the service executive is obtained from the configuration file, the service information is sent to the service executive for processing based on the target calling interface, the technical problems of resource waste and high labor cost caused by the fact that corresponding programs need to be written for different service executors are avoided, the coupling between the service executive and the service information receiver is reduced, the service information is processed conveniently and efficiently, and the technical effect of cost is reduced.

Drawings

In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, a brief description is given below of the drawings used in describing the embodiments. It should be clear that the described figures are only views of some of the embodiments of the invention to be described, not all, and that for a person skilled in the art, other figures can be derived from these figures without inventive effort.

Fig. 1 is a schematic diagram of processing service information provided in the prior art;

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

fig. 3 is a schematic diagram of an interface calling method according to a second embodiment of the present invention;

fig. 4 is a schematic diagram of an interface calling method according to a second embodiment of the present invention;

fig. 5 is a schematic structural diagram of an interface invoking device according to a third embodiment of the present invention;

fig. 6 is a schematic structural diagram of an apparatus according to a third embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the accompanying drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting of the invention. It should be further noted that, for the convenience of description, only some of the structures related to the present invention are shown in the drawings, not all of the structures.

Example one

Fig. 2 is a schematic flow chart of an interface calling method according to a first embodiment of the present invention, where the technical solution of this embodiment is applicable to a situation where when a plurality of service information executing parties access services corresponding to service information receiving parties, development of service program codes corresponding to the service executing parties is not needed, that is, development workload of the service information receiving parties is reduced. The hardware may be an electronic device, such as a PC terminal or a mobile terminal.

As shown in fig. 2, the method of this embodiment includes:

and S110, when the service information is received, determining a target service executing party for executing the service information.

For clearly describing the technical solution of the embodiment of the present disclosure, before describing the technical solution of the embodiment of the present disclosure, it should be noted that the technical solution of the embodiment of the present disclosure may be executed by a service information receiving side. The service of the service information receiver can receive a plurality of service information executing parties at the same time, and the service information executing parties can be various sub lenders.

Wherein, the service information can be credit service initiated by other platforms or users. For example, if the user a needs to loan, the loan service corresponding to the user a may be used as the service information. After receiving the service information, the lender may determine a sub-lender executing the service information, and may use the sub-lender executing the service information as a target service executor.

S120, determining a target executive party identifier corresponding to the target service executive party, and acquiring at least one target calling interface corresponding to the target service executive party from a pre-established configuration file based on the target executive party identifier.

The target executive party identification is used for representing a service party executing the service information. After the target service executor is determined, a target executor identifier corresponding to the target service executor may be determined, so as to obtain an interface to be called corresponding to the target executor based on the target identifier. The configuration file is pre-established and is used for placing service interfaces and interface corresponding methods corresponding to all service executing parties. The target calling interface is an interface corresponding to the target service executing party. The number of the target calling interfaces is the same as that of the interfaces corresponding to the target service executing party.

It should be noted that the number of interfaces corresponding to different service executing parties may be the same or different, and accordingly, the specific content, i.e., the method, corresponding to the interfaces may be the same or different.

In this embodiment, before obtaining at least one target invocation interface corresponding to a target service executing party from a configuration file, the method further includes: acquiring an executive party identifier of each service executive party and an interface to be called of the service executive party, and establishing a mapping relation between the executive party identifier and the interface to be called; and determining an interface calling configuration file comprising all interfaces to be called according to the interfaces to be called of each service party executive party so as to acquire at least one target calling interface corresponding to the target service executive party from the configuration file.

Specifically, in order to obtain a target service interface corresponding to a target service executing party from a configuration file, an executing party identifier of the service executing party may be determined, interfaces to be called corresponding to the service executing parties may be determined, and a mapping relationship between the service executing party and the interfaces to be called may be established, so that after the target service executing party is determined, the interfaces to be called corresponding to the service executing party may be determined based on the mapping relationship. Meanwhile, after the interfaces to be called corresponding to the service execution parties are determined, the methods of the interfaces to be called can be stored in a configuration file. The configuration file comprises interfaces to be called corresponding to all service execution parties, but no repeated interfaces to be called exist, so that the advantage of the setting is that the technical problem of resource redundancy in the configuration file is avoided.

In this embodiment, the configuration file includes an interface corresponding to each service executing party and a method corresponding to the interface, where the method includes: and registering the configuration file into the generalized calling service so as to acquire a target calling interface corresponding to a target service execution party for executing the service information from the configuration file stored in the generalized service when the service information is received.

The generalization service is a service for uniformly calling each service execution party and a target calling interface corresponding to the service execution party. Or can be understood as a generalized program code, and a certain command behavior determines a target calling interface corresponding to a target service executive according to the service executive identifier of the target service executive; a command behavior obtains a target invocation interface from a configuration file.

In this embodiment, based on the target executor identifier, acquiring at least one target invocation interface corresponding to the target service executor from a pre-established configuration file includes: and determining a target interface to be called corresponding to the target executive identification based on the mapping relation, and acquiring at least one target calling interface corresponding to the target interface to be called from a pre-established configuration file.

Specifically, according to the mapping relationship table, an interface required by the target executor corresponding to the target execution identifier may be determined, and the interface determined at this time may be used as the target interface to be called. According to the determined target interface to be called, the target calling interface corresponding to the target interface to be called can be obtained from the configuration file, so that the service information is sent based on the target calling interface, and the target service executing party executes the service corresponding to the service information.

S130, based on at least one target calling interface, the service information is sent to a target service executing party.

Specifically, according to a target call interface corresponding to the target service executing party, the information received by the service information receiving party is sent to the target service executing party, so that the target service executing party executes the corresponding service information.

Example two

Fig. 3 is a schematic diagram of an interface calling method according to a second embodiment of the present invention. Based on the foregoing embodiment, it should be noted that the technical solution of this embodiment may unify the technical implementation of different service executing parties, that is, unify the request entry and exit of each service executing party, that is, obtain the configuration parameters in the configuration file according to the service information, that is, the interface to be called corresponding to the service executing party, and implement reduction of the development workload of the program code when the service executing party, that is, each credit-credit sub party, accesses. By using the technical implementation mode of generalization call, each sub credit and debit party is requested, namely, the sub credit and debit party is routed to each sub credit and debit party, namely, a service executing party through configuration, and service coupling between each sub credit and debit party and a credit party is avoided.

Referring to fig. 3, the service information receiver mainly receives all service information and determines a service executor that executes the service information. The standard process of each guarantee access service butt joint defines uniform parameters and return results by the standard process, namely, each service executive party butt joints the service information receiver. The unified standard service calls a generalized calling service, the generalized calling service acquires interfaces and methods configured on the configuration center by each guarantee access service, and remote calling is carried out in a generalized mode.

As shown in fig. 4, each service executing party may register an interface and a method corresponding to each service executing party in the generalized calling service, that is, store the interface and the method in the generalized calling configuration center, and when the service information receiving party receives the service information, may determine a target service executing party corresponding to the service information, determine a target executing party identifier of the target service executing party, and call the generalized calling service to obtain a target calling interface corresponding to the target executing party identifier in the configuration file. And after the target calling interface is successfully called, assembling the method and the parameters by the generalized calling service to carry out remote invoke generalized calling.

The technical scheme of the embodiment of the invention realizes a unified calling frame by uniformly connecting the inlets of all the service executing parties and realizing all service calling by pre-establishing the configuration file in a generalized calling mode, and realizes the coupling between the service information receiving party and the service information executing party by adopting the generalized calling service. That is, based on the configuration file predetermined in the generalized calling service, it can be realized that only the configuration file needs to be changed and the program code corresponding to the configuration file does not need to be re-developed if a new service executor is received, thereby improving the access efficiency of the new service executor.

EXAMPLE III

Fig. 5 is a schematic structural diagram of an interface invoking device according to a third embodiment of the present invention, where the interface invoking device includes: a service executor determining module 510, a target call interface determining module 520, and a service information transmitting module 530.

The service executor determining module 510 is configured to determine, when receiving service information, a target service executor that executes the service information; a target calling interface determining module 520, configured to determine a target executor identifier corresponding to the target service executor, and obtain, based on the target executor identifier, at least one target calling interface corresponding to the target service executor from a pre-established configuration file; a service information sending module 530, configured to send the service information to the target service executing party based on the at least one target call interface.

According to the technical scheme of the embodiment of the invention, the interface to be called of each service executive party for executing the service information and the method corresponding to the interface are stored in the configuration file of the service calling system, so that after the service information is received and the service executive party corresponding to the service information is determined, the target calling interface corresponding to the service executive party is obtained from the configuration file, the service information is sent to the service executive party based on the target calling interface and is processed, the technical problems of resource waste and high labor cost caused by the fact that corresponding programs need to be written for different service executive parties are avoided, the service information is conveniently and efficiently processed, and the technical effect of reducing the cost is achieved.

On the basis of the above technical solution, the apparatus further includes:

the mapping relation establishing module is used for acquiring an executive party identifier of each service executive party and an interface to be called of the service executive party and establishing a mapping relation between the executive party identifier and the interface to be called;

and the configuration file determining module is used for determining interface calling configuration files comprising all interfaces to be called according to the interfaces to be called of each service party executive party so as to acquire at least one target calling interface corresponding to the target service executive party from the configuration files.

On the basis of the above technical solution, the configuration file includes an interface corresponding to each service executing party and a method corresponding to the interface, and further includes:

and the configuration file storage module is used for registering the configuration file into the generalized calling service so as to obtain a target calling interface corresponding to a target service executive party executing the service information from the configuration file stored by the generalized service when the service information is received.

On the basis of the above technical solutions, the configuration file determining module further includes:

the interface to be called determining unit is used for determining a target interface to be called corresponding to the target executive party identifier based on the mapping relation;

and the target calling interface determining unit is used for acquiring at least one target calling interface corresponding to the target interface to be called from a pre-established configuration file.

On the basis of the above technical solutions, the service information sending module is further configured to: after the at least one target calling interface is determined, packaging the method and the parameters of the at least one target interface based on the generalized calling service to obtain packaging information; and sending the service information to a target service executing party based on the packaging information.

The interface calling device provided by the embodiment of the invention can execute the interface calling method provided by any embodiment of the invention, and has corresponding functional modules and beneficial effects of the execution method.

It should be noted that, the units and modules included in the apparatus are merely divided according to functional logic, but are not limited to the above division as long as the corresponding functions can be implemented; in addition, specific names of the functional units are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the embodiment of the invention.

Example four

Fig. 6 is a schematic structural diagram of an apparatus according to a fourth embodiment of the present invention. FIG. 6 illustrates a block diagram of an exemplary device 60 suitable for use in implementing embodiments of the present invention. The device 60 shown in fig. 6 is only an example and should not bring any limitation to the function and scope of use of the embodiments of the present invention.

As shown in FIG. 6, device 60 is embodied in a general purpose computing device. The components of the device 60 may include, but are not limited to: one or more processors or processing units 601, a system memory 602, and a bus 603 that couples various system components including the system memory 602 and the processing unit 601.

Bus 603 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, such architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, micro-channel architecture (MAC) bus, enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

Device 60 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by device 60 and includes both volatile and nonvolatile media, removable and non-removable media.

The system memory 602 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM)604 and/or cache memory 605. The device 60 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 606 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 6, commonly referred to as a "hard drive"). Although not shown in FIG. 6, a magnetic disk drive for reading from and writing to a removable, nonvolatile magnetic disk (e.g., a "floppy disk") and an optical disk drive for reading from or writing to a removable, nonvolatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to the bus 603 by one or more data media interfaces. Memory 602 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.

A program/utility 608 having a set (at least one) of program modules 607 may be stored, for example, in memory 602, such program modules 607 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which examples or some combination thereof may comprise an implementation of a network environment. The program modules 607 generally perform the functions and/or methods of the described embodiments of the invention.

Device 60 may also communicate with one or more external devices 609 (e.g., keyboard, pointing device, display 610, etc.), with one or more devices that enable a user to interact with device 60, and/or with any devices (e.g., network card, modem, etc.) that enable device 60 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 611. Also, device 60 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via network adapter 612. As shown, a network adapter 612 communicates with the other modules of device 60 via bus 603. It should be appreciated that although not shown in FIG. 6, other hardware and/or software modules may be used in conjunction with device 60, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

The processing unit 601 executes various functional applications and data processing, for example, implementing an interface calling method provided by an embodiment of the present invention, by running a program stored in the system memory 602.

EXAMPLE five

Fifth, an embodiment of the present invention further provides a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform an interface invocation method.

The method comprises the following steps:

Computer storage media for embodiments of the invention may employ any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the computer readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for embodiments of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).

It is to be noted that the foregoing is only illustrative of the preferred embodiments of the present invention and the technical principles employed. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, although the present invention has been described in greater detail by the above embodiments, the present invention is not limited to the above embodiments, and may include other equivalent embodiments without departing from the spirit of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An interface calling method, comprising:

2. The method of claim 1, further comprising:

acquiring an executive party identifier of each service executive party and an interface to be called of the service executive party, and establishing a mapping relation between the executive party identifier and the interface to be called;

and determining an interface calling configuration file comprising all interfaces to be called according to the interfaces to be called of each service party executive party so as to acquire at least one target calling interface corresponding to the target service executive party from the configuration file.

3. The method of claim 2, wherein the configuration file includes an interface corresponding to each service executing party, and the method corresponding to the interface further includes:

and registering the configuration file into a generalized calling service so as to obtain a target calling interface corresponding to a target service execution party executing the service information from the configuration file stored in the generalized service when the service information is received.

4. The method of claim 2, wherein the obtaining at least one target invocation interface corresponding to the target service executor from a pre-established configuration file based on the target executor identifier comprises:

determining a target interface to be called corresponding to the target executive party identification based on the mapping relation;

and acquiring at least one target calling interface corresponding to the target interface to be called from a pre-established configuration file.

5. The method of claim 1, wherein the sending the service information to the target service executing party based on the at least one target call interface comprises:

after the at least one target calling interface is determined, packaging the method and the parameters of the at least one target interface based on the generalized calling service to obtain packaging information;

and sending the service information to a target service executing party based on the packaging information.

6. An interface invocation apparatus, comprising:

7. The apparatus of claim 6, further comprising:

8. The apparatus of claim 7, wherein the configuration file includes an interface corresponding to each service executing party, and wherein the method corresponding to the interface further includes:

9. An apparatus, characterized in that the apparatus comprises:

one or more processors;

a storage device for storing one or more programs,

when executed by the one or more processors, cause the one or more processors to implement the interface call method as recited in any of claims 1-7.

10. A storage medium containing computer-executable instructions for performing the interface call method of any one of claims 1-7 when executed by a computer processor.