CN112988273A - Calling method and interface management platform of heterogeneous system - Google Patents
Calling method and interface management platform of heterogeneous system Download PDFInfo
- Publication number
- CN112988273A CN112988273A CN202110313211.0A CN202110313211A CN112988273A CN 112988273 A CN112988273 A CN 112988273A CN 202110313211 A CN202110313211 A CN 202110313211A CN 112988273 A CN112988273 A CN 112988273A
- Authority
- CN
- China
- Prior art keywords
- interface
- calling
- management platform
- called
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000012545 processing Methods 0.000 claims description 17
- 238000012795 verification Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 11
- 238000011161 development Methods 0.000 abstract description 16
- 238000010586 diagram Methods 0.000 description 22
- 230000018109 developmental process Effects 0.000 description 14
- 230000008569 process Effects 0.000 description 14
- 230000006870 function Effects 0.000 description 12
- SPBWHPXCWJLQRU-FITJORAGSA-N 4-amino-8-[(2r,3r,4s,5r)-3,4-dihydroxy-5-(hydroxymethyl)oxolan-2-yl]-5-oxopyrido[2,3-d]pyrimidine-6-carboxamide Chemical compound C12=NC=NC(N)=C2C(=O)C(C(=O)N)=CN1[C@@H]1O[C@H](CO)[C@@H](O)[C@H]1O SPBWHPXCWJLQRU-FITJORAGSA-N 0.000 description 3
- 230000008901 benefit Effects 0.000 description 3
- 230000000670 limiting effect Effects 0.000 description 3
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000014509 gene expression Effects 0.000 description 2
- 230000000977 initiatory effect Effects 0.000 description 2
- 230000033772 system development Effects 0.000 description 2
- 239000003795 chemical substances by application Substances 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 239000003999 initiator Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003672 processing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/44—Program or device authentication
- G06F21/445—Program or device authentication by mutual authentication, e.g. between devices or programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
Abstract
The invention discloses a calling method and an interface management platform of a heterogeneous system, and relates to the technical field of computers. The calling method of the heterogeneous system comprises the following steps: the interface management platform acquires a calling request which is sent by a first system and is used for calling a called interface, wherein the called interface is an interface provided by a second system, the interface management platform stores interface information of the interface provided by the second system, and the calling request comprises an interface identifier and a calling parameter value of the called interface; the interface management platform inquires interface information corresponding to the interface identification; the interface management platform initiates the calling of the called interface to the second system according to the interface information and the calling parameter value; and the interface management platform returns the calling result corresponding to the calling parameter value to the first system. Therefore, each system does not need to independently develop and call logic for each system providing an interface, the development workload is reduced, and the development efficiency is improved.
Description
Technical Field
The invention relates to the technical field of computers, in particular to a method and a system for calling a heterogeneous system and an interface management platform.
Background
With the advent of the Web 2.0 era, the internet based on the Web environment is increasingly widely used. In the process of enterprise informatization, many applications are built on a Web platform, and therefore, a large number of Web application systems are appeared. Meanwhile, a large number of interfaces are required between companies and between teams to provide cooperation of various services.
In the related art, the two cooperating systems use the interface document as shared cooperation information, and usually use the interface document management platform to provide a sharing function. In the calling process between the systems, an external interface needs to be arranged between the two systems with the calling relationship so as to facilitate the calling of the other system.
Disclosure of Invention
The inventor analyzes the related technology and finds that, in the related technology, when one service platform needs to support multiple heterogeneous systems, the supported systems all need to independently develop external call logic of interfaces provided by the supported systems, which causes that each system needs to perform repeated work in the construction process of the service platform, and the development efficiency is low.
The embodiment of the invention aims to solve the technical problem that: how to improve the development efficiency of heterogeneous systems.
According to a first aspect of some embodiments of the present invention, there is provided a method for calling a heterogeneous system, including: the interface management platform acquires a calling request which is sent by a first system and is used for calling a called interface, wherein the called interface is an interface provided by a second system, the interface management platform stores interface information of the interface provided by the second system, and the calling request comprises an interface identifier and a calling parameter value of the called interface; the interface management platform inquires interface information corresponding to the interface identification; the interface management platform initiates the calling of the called interface to the second system according to the interface information and the calling parameter value; and the interface management platform returns the calling result corresponding to the calling parameter value to the first system.
In some embodiments, the calling method further comprises: the interface management platform acquires a certificate passing application request sent by a first system; and the interface management platform returns a pass card to the first system, wherein the pass card is used for identity authentication.
In some embodiments, the invocation request further includes a pass, and the invocation method further includes: and the interface management platform performs identity verification on the pass card in the calling request so as to initiate calling of the called interface under the condition that the identity verification is passed.
In some embodiments, the calling method further comprises: the interface management platform acquires a calling authority application which is sent by a first system and is applied to an interface provided by a second system; and the interface management platform allocates corresponding calling authority for the first system.
In some embodiments, the calling method further comprises: after obtaining the call request, the interface management platform determines whether the first system has the call authority to the called interface according to the interface identifier, so as to initiate the call to the called interface under the condition that the first system has the call authority.
In some embodiments, the calling method further comprises: the interface management platform receives an interface registration request sent by a second system, wherein the interface registration request comprises interface information; the interface management platform allocates interface identifiers for corresponding interfaces; the interface management platform stores the corresponding relation between the interface information and the interface identification.
In some embodiments, the interface information includes a domain name and a context.
According to a second aspect of some embodiments of the present invention, there is provided an interface management platform comprising: the interface management platform comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is configured to acquire a calling request which is sent by a first system and is used for calling a called interface, the called interface is an interface provided by a second system, the interface management platform stores interface information of the interface provided by the second system, and the calling request comprises an interface identifier and a calling parameter value of the called interface; the query module is configured to query the interface information corresponding to the interface identifier; the calling module is configured to initiate calling of the called interface to the second system according to the interface information and the calling parameter value; and the result returning module is configured to return the result of the call corresponding to the call parameter value to the first system.
In some embodiments, the interface management platform further comprises: the system comprises a certificate passing management module and a certificate passing management module, wherein the certificate passing management module is configured to acquire a certificate passing application request sent by a first system and return a certificate passing to the first system, and the certificate passing is used for identity verification.
In some embodiments, the invocation request further includes a pass, and the pass management module is further configured to authenticate the pass in the invocation request, such that the invocation module initiates the invocation of the invoked interface if the authentication passes.
In some embodiments, the interface management platform further comprises: and the authority management module is configured to acquire a calling authority application which is sent by the first system and is applied to an interface provided by the second system, and allocate corresponding calling authority to the first system.
In some embodiments, the authority management module is further configured to determine whether the first system has the calling authority for the called interface according to the interface identification after obtaining the calling request, so that the calling module initiates the calling for the called interface if the first system has the calling authority.
In some embodiments, the interface management platform further comprises: the registration module is configured to receive an interface registration request sent by the second system, wherein the interface registration request includes interface information, allocate an interface identifier to a corresponding interface, and store a corresponding relationship between the interface information and the interface identifier.
In some embodiments, the interface information includes a domain name and a context.
According to a third aspect of some embodiments of the present invention, there is provided an interface management platform comprising: a memory; and a processor coupled to the memory, the processor configured to execute a calling method of any one of the aforementioned heterogeneous systems based on instructions stored in the memory.
According to a fourth aspect of some embodiments of the present invention, there is provided a computer-readable storage medium on which a computer program is stored, wherein the program, when executed by a processor, implements any one of the aforementioned calling methods for a heterogeneous system.
Some embodiments of the above invention have the following advantages or benefits. When the heterogeneous system needs to call the interface, one direction initiating the call initiates a call request to the interface management platform, and the subsequent call processing logic is completed by the interface management platform in a unified way. Therefore, each system does not need to independently develop and call logic for each system providing an interface, the development workload is reduced, and the development efficiency is improved. In addition, the systems interact through the interface management platform, so that the independence between the systems is improved, and the coupling degree is reduced.
Other features of the present invention and advantages thereof will become apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 illustrates a flow diagram of a method for invoking a heterogeneous system in accordance with some embodiments of the present invention.
Fig. 2A exemplarily shows a calling model of an intersystem call in the related art.
FIG. 2B illustrates an exemplary invocation model for intersystem calls in the present invention.
FIG. 3 illustrates a flow diagram of a method of forensic processing according to some embodiments of the present invention.
Fig. 4 is a flowchart illustrating a method for invoking a heterogeneous system with an authentication process.
FIG. 5 illustrates a flow diagram of a rights application method according to some embodiments of the invention.
Fig. 6 is a flowchart illustrating a method for invoking a heterogeneous system with a rights verification process.
FIG. 7 illustrates a flow diagram of a system registration method according to some embodiments of the inventions.
FIG. 8 illustrates an architectural diagram of an interface management platform according to some embodiments of the invention.
FIG. 9 illustrates an architectural diagram of an interface management platform according to further embodiments of the present invention.
FIG. 10 illustrates an architectural diagram of an interface management platform according to further embodiments of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the invention, its application, or uses. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The relative arrangement of the components and steps, the numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless specifically stated otherwise.
Meanwhile, it should be understood that the sizes of the respective portions shown in the drawings are not drawn in an actual proportional relationship for the convenience of description.
Techniques, methods, and apparatus known to those of ordinary skill in the relevant art may not be discussed in detail but are intended to be part of the specification where appropriate.
In all examples shown and discussed herein, any particular value should be construed as merely illustrative, and not limiting. Thus, other examples of the exemplary embodiments may have different values.
It should be noted that: like reference numbers and letters refer to like items in the following figures, and thus, once an item is defined in one figure, further discussion thereof is not required in subsequent figures.
In order to improve the development efficiency, the interface management platform is upgraded to have the functions of storing and inquiring interface information, and can also act for each system to carry out interface calling so as to avoid each system from repeatedly developing calling logic. An embodiment of the calling method of the heterogeneous system of the present invention is described below with reference to fig. 1.
The descriptions of the "first system" and the "second system" in the embodiment of the present invention are only used for distinguishing the calling initiator and the called party in the calling process, and it may be any system accessing the interface management platform, and the expression does not have any limiting effect on the present invention.
FIG. 1 illustrates a flow diagram of a method for invoking a heterogeneous system in accordance with some embodiments of the present invention. As shown in fig. 1, the calling method of the heterogeneous system of the embodiment includes steps S102 to S108.
In step S102, the interface management platform obtains a call request for a called interface sent by the first system, where the called interface is an interface provided by the second system, the interface management platform stores interface information of the interface provided by the second system, and the call request includes an interface identifier and a call parameter value of the called interface.
The first system and the second system are any two systems registered to the interface management platform. In an embodiment, the second system is a callee for providing an interface to be called, and the first system calls an interface provided by the second system.
When the first system needs to call the interface of the second system, the request is not directly sent to the second system, but the call request is sent to the interface management platform. And subsequent calling processing logic is uniformly completed by the interface management platform. Therefore, each platform lightens the development work of calling logic and improves the development efficiency.
In some embodiments, the interface information includes a domain name and a context. For example, for interface "www.ABC.com/f 1/? The user ═ xxx > & time ═ xxx > "," www.ABC.com "is the domain name," f1 "is the context," user "and" time "are the parameters, and the equal sign after the parameters is used to fill in the corresponding parameter values. The interface information may also include more content, such as interface documents, and the like.
In some embodiments, the interface management platform assigns an interface identifier to the registered interface, and stores a correspondence between the interface information and the interface identifier. The developer of the first system can obtain the interface identification of the registered interface by inquiring the interface management platform.
In step S104, the interface management platform queries the interface information corresponding to the interface identifier.
In step S106, the interface management platform initiates a call to the called interface to the second system according to the interface information and the call parameter value.
For example, the second system provides an interface "www.ABC.com/f 1/? The interface with user ═ xxx > & time ═ xxx > "is identified as" api1 ", the first system initiates a call request to the interface platform, for example, comprising { api1, user ═ u 1", time ═ 111111 "}. After the interface management platform queries the corresponding interface according to the api1, the parameter value is filled in, and then a call request of www.ABC.com/f 1/? u1& time 111111 ".
In step S108, the interface management platform returns the result of the call corresponding to the call parameter value to the first system.
Through the embodiment, when the interfaces are required to be called between heterogeneous systems, the calling request is initiated to the interface management platform by the calling party, and the subsequent calling processing logic is completed by the interface management platform in a unified manner. Therefore, each system does not need to independently develop and call logic for each system providing an interface, the development workload is reduced, and the development efficiency is improved. In addition, the systems interact through the interface management platform, so that the independence between the systems is improved, and the coupling degree is reduced.
Fig. 2A exemplarily shows a calling model of an intersystem call in the related art. As shown in fig. 2A, in addition to the interface processing logic, system a and system B need to be additionally equipped with processing logic for credential management for identity authentication or processing logic for access authentication for authority control. This further increases the development effort.
In some embodiments of the present invention, the interface management platform integrates at least one of the identity authentication function and the authority control function, so that each system does not need to develop the function additionally. An intersystem call model of the present invention is shown in FIG. 2B. The interface management platform interacts with each system through the interface proxy service and has the functions of calling processing logic, accessing authority and managing token, so that the system A and the system B do not need to develop the three functions additionally.
An embodiment of the method of the present invention is described below with reference to fig. 3.
FIG. 3 illustrates a flow diagram of a method of forensic processing according to some embodiments of the present invention. As shown in fig. 3, the certification processing method of this embodiment includes S302 to S304.
In step S302, the interface management platform obtains a request for a pass-certificate application sent by the first system.
In step S304, the interface management platform returns a pass to the first system, where the pass is used for performing identity verification. The first system may attach a certificate when initiating the call request so that the interface management platform verifies its identity.
The pass is used for indicating the validity of the identity of the calling requester. In addition, the system can also have time-based information, and each system connected to the interface management platform can ensure that the obtained certificate is in the valid period, for example, by periodically applying for the certificate.
By the method of the embodiment, the interface management platform can uniformly distribute and manage the certificates of all the systems, and all the systems do not need to develop related logics, so that repeated development work is reduced, and development efficiency is improved.
Fig. 4 is a flowchart illustrating a method for invoking a heterogeneous system with an authentication process. As shown in fig. 4, the calling method of this embodiment includes steps S402 to S410.
In step S402, the interface management platform obtains a call request sent by the first system for a called interface, where the called interface is an interface provided by the second system, and the call request includes an interface identifier of the called interface, a call parameter value, and a credential of the first system.
In step S404, the interface management platform queries the interface information corresponding to the interface identifier.
In step S406, the interface management platform performs authentication on the pass card in the invocation request.
Step S406 may be performed before, after, or simultaneously with step S404.
In some embodiments, when step S406 is performed first, step S404 is not performed if the authentication fails.
In step S408, in case that the identity authentication is passed, the interface management platform initiates a call to the called interface to the second system according to the interface information and the call parameter value.
In step S410, the interface management platform returns the result of the call corresponding to the call parameter value to the first system.
Through the method of the embodiment, the interface management platform executes the authentication process of the calling requester. Therefore, the system of the called interface does not need to additionally develop identity authentication logic, and the system development efficiency is improved. Moreover, the safety is improved by carrying out identity authentication based on the pass card in the calling process.
An embodiment of the rights application method is described below with reference to fig. 5.
FIG. 5 illustrates a flow diagram of a rights application method according to some embodiments of the invention. As shown in fig. 5, the method for applying for a right of this embodiment includes steps S502 to S504.
In step S502, the interface management platform obtains a call authority application for an interface provided by the second system, which is sent by the first system.
In step S504, the interface management platform assigns a corresponding invocation authority to the first system.
Through the method of the embodiment, the interface management platform can uniformly manage the interface calling authority of each system, and each system does not need to develop related logic, so that repeated development work is reduced, and development efficiency is improved.
Fig. 6 is a flowchart illustrating a method for invoking a heterogeneous system with a rights verification process. As shown in fig. 6, the calling method of this embodiment includes steps S602 to S610.
In step S602, the interface management platform obtains a call request sent by the first system for a called interface, where the called interface is an interface provided by the second system, and the call request includes an interface identifier and a call parameter value of the called interface.
In step S604, the interface management platform queries the interface information corresponding to the interface identifier.
In step S606, the interface management platform determines whether the first system has the call authority for the called interface according to the interface identifier.
Step S606 may be performed before, after, or simultaneously with step S604.
In some embodiments, when step S606 is performed first, if the first system does not have the call authority for the called interface, step S604 is not performed.
In step S608, when the first system has the call authority, the interface management platform initiates a call to the called interface to the second system according to the interface information and the call parameter value.
In step S610, the interface management platform returns the result of the call corresponding to the call parameter value to the first system.
Through the method of the embodiment, the interface management platform executes the call authority verification process of the call requester. Therefore, the system of the called interface does not need to additionally develop the authority verification logic, and the system development efficiency is improved. And moreover, the safety is improved by carrying out authority verification in the calling process.
In some embodiments, the interface management platform opens registration functions for system access that require the functionality of the various embodiments described above. An embodiment of the system registration method of the present invention is described below with reference to fig. 7.
FIG. 7 illustrates a flow diagram of a system registration method according to some embodiments of the inventions. As shown in fig. 7, the system registration method of this embodiment includes steps S702 to S706.
In step S702, the interface management platform receives an interface registration request sent by the second system, where the interface registration request includes interface information.
In some embodiments, the system submits the interface document as interface information at registration time. An example of an interface document is as follows.
domain:www.api.com
url:/get
method:GET
And (3) participating in entities:
in step S704, the interface management platform assigns an interface identifier to the corresponding interface.
In step S706, the interface management platform stores the correspondence between the interface information and the interface identification.
Therefore, the system can complete the registration process when submitting the interface information. After the interface identifier is allocated, other systems can also obtain the interface identifier by querying the interface management platform and can initiate calling through the interface management platform.
An embodiment of the interface management platform of the present invention is described below with reference to fig. 8.
FIG. 8 illustrates an architectural diagram of an interface management platform according to some embodiments of the invention. As shown in fig. 8, the interface management platform 800 of this embodiment includes: the obtaining module 8100 is configured to obtain a call request sent by a first system for a called interface, where the called interface is an interface provided by a second system, the interface management platform stores interface information of the interface provided by the second system, and the call request includes an interface identifier and a call parameter value of the called interface; a query module 8200 configured to query interface information corresponding to the interface identifier; a calling module 8300 configured to initiate a call to the called interface to the second system according to the interface information and the calling parameter value; a result returning module 8400 configured to return the result of the call corresponding to the call parameter value to the first system.
In some embodiments, the acquisition module 8100 and the result return module 8400 are integrated as a calling agent for data interaction directly with the respective system.
In some embodiments, interface management platform 800 further comprises: the certification management module 8500 is configured to acquire a certification application request sent by the first system, and return a certification to the first system, where the certification is used for performing identity verification.
In some embodiments, the invocation request further includes a pass, and the pass management module 8500 is further configured to authenticate the pass in the invocation request, such that the invocation module 8300 initiates the invocation of the invoked interface if the authentication passes.
In some embodiments, interface management platform 800 further comprises: the authority management module 8600 is configured to obtain a calling authority application sent by the first system to the interface provided by the second system, and allocate corresponding calling authority to the first system.
In some embodiments, the rights management module 8600 is further configured to determine whether the first system has the right to call the called interface according to the interface identifier after obtaining the call request, so that the call module 8300 initiates a call to the called interface if the first system has the right to call.
In some embodiments, interface management platform 800 further comprises: a registering module 8700 configured to receive an interface registering request sent by the second system, where the interface registering request includes interface information, assign an interface identifier to a corresponding interface, and store a corresponding relationship between the interface information and the interface identifier.
In some embodiments, the interface information includes a domain name and a context.
FIG. 9 illustrates an architectural diagram of an interface management platform according to further embodiments of the present invention. As shown in fig. 9, the interface management platform 90 of this embodiment includes: a memory 910 and a processor 920 coupled to the memory 910, wherein the processor 920 is configured to execute a calling method of a heterogeneous system in any of the embodiments based on instructions stored in the memory 910.
FIG. 10 illustrates an architectural diagram of an interface management platform according to further embodiments of the present invention. As shown in fig. 10, the interface management platform 100 of this embodiment includes: the memory 1010 and the processor 1020 may further include an input/output interface 1030, a network interface 1040, a storage interface 1050, and the like. These interfaces 1030, 1040, 1050 and the memory 1010 and the processor 1020 may be connected via a bus 1060, for example. The input/output interface 1030 provides a connection interface for input/output devices such as a display, a mouse, a keyboard, and a touch screen. Network interface 1040 provides a connection interface for various networking devices. The storage interface 1050 provides a connection interface for external storage devices such as an SD card and a usb disk.
An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program is configured to implement a method for invoking any one of the aforementioned heterogeneous systems when executed by a processor.
As will be appreciated by one skilled in the art, embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable non-transitory storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like that fall within the spirit and principle of the present invention are intended to be included therein.
Claims (16)
1. A calling method of a heterogeneous system comprises the following steps:
the method comprises the steps that an interface management platform obtains a calling request which is sent by a first system and is used for calling an interface to be called, wherein the interface to be called is an interface provided by a second system, the interface management platform stores interface information of the interface provided by the second system, and the calling request comprises an interface identifier and a calling parameter value of the interface to be called;
the interface management platform inquires the interface information corresponding to the interface identifier;
the interface management platform initiates the calling of the called interface to the second system according to the interface information and the calling parameter value;
and the interface management platform returns the calling result corresponding to the calling parameter value to the first system.
2. The calling method of the heterogeneous system according to claim 1, further comprising:
the interface management platform acquires a certification application request sent by the first system;
and the interface management platform returns a pass card to the first system, wherein the pass card is used for identity authentication.
3. The calling method of the heterogeneous system according to claim 2, wherein the calling request further includes the pass, and the calling method further comprises:
and the interface management platform performs identity verification on the pass card in the calling request so as to initiate calling of the called interface under the condition that the identity verification is passed.
4. The calling method of the heterogeneous system according to claim 1, further comprising:
the interface management platform acquires a calling authority application which is sent by the first system and is applied to an interface provided by the second system;
and the interface management platform allocates corresponding calling authority to the first system.
5. The calling method of the heterogeneous system according to claim 4, further comprising:
after the calling request is obtained, the interface management platform determines whether the first system has the calling authority for the called interface according to the interface identifier, so that calling for the called interface is initiated under the condition that the first system has the calling authority.
6. The calling method of the heterogeneous system according to claim 1, further comprising:
the interface management platform receives an interface registration request sent by the second system, wherein the interface registration request comprises interface information;
the interface management platform allocates interface identifiers for corresponding interfaces;
and the interface management platform stores the corresponding relation between the interface information and the interface identification.
7. The calling method of the heterogeneous system according to any one of claims 1 to 6, wherein the interface information includes a domain name and a context.
8. An interface management platform, comprising:
the interface management platform comprises an acquisition module, a processing module and a processing module, wherein the acquisition module is configured to acquire a calling request which is sent by a first system and is used for calling a called interface, the called interface is an interface provided by a second system, the interface management platform stores interface information of the interface provided by the second system, and the calling request comprises an interface identifier and a calling parameter value of the called interface;
the query module is configured to query the interface information corresponding to the interface identifier;
the calling module is configured to initiate calling of the called interface to the second system according to the interface information and the calling parameter value;
and the result returning module is configured to return the result of the call corresponding to the call parameter value to the first system.
9. The interface management platform of claim 8, further comprising:
the system comprises a first system and a second system, wherein the first system is used for sending a certificate receiving request to the second system, and the second system is used for sending a certificate receiving request to the first system.
10. The interface management platform of claim 9, wherein the invocation request further includes the pass, and the pass management module is further configured to authenticate the pass in the invocation request, such that the invocation module initiates the invocation of the invoked interface if the authentication passes.
11. The interface management platform of claim 8, further comprising:
and the authority management module is configured to acquire a calling authority application which is sent by the first system and is applied to an interface provided by the second system, and allocate corresponding calling authority to the first system.
12. The interface management platform according to claim 11, wherein the permission management module is further configured to determine whether the first system has the permission to call the called interface according to the interface identifier after obtaining the call request, so that the call module initiates the call to the called interface if the first system has the permission to call.
13. The interface management platform of claim 8, further comprising:
the registration module is configured to receive an interface registration request sent by the second system, where the interface registration request includes interface information, assign an interface identifier to a corresponding interface, and store a correspondence between the interface information and the interface identifier.
14. The interface management platform according to any of claims 8-13, wherein the interface information includes a domain name and a context.
15. An interface management platform, comprising:
a memory; and
a processor coupled to the memory, the processor configured to execute the calling method of the heterogeneous system of any of claims 1-7 based on instructions stored in the memory.
16. A computer-readable storage medium, on which a computer program is stored, which when executed by a processor implements the calling method of the heterogeneous system of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110313211.0A CN112988273A (en) | 2021-03-24 | 2021-03-24 | Calling method and interface management platform of heterogeneous system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110313211.0A CN112988273A (en) | 2021-03-24 | 2021-03-24 | Calling method and interface management platform of heterogeneous system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112988273A true CN112988273A (en) | 2021-06-18 |
Family
ID=76334462
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110313211.0A Pending CN112988273A (en) | 2021-03-24 | 2021-03-24 | Calling method and interface management platform of heterogeneous system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112988273A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110032454A (en) * | 2018-01-12 | 2019-07-19 | 北京京东尚科信息技术有限公司 | Remote invocation method, system and relevant device and computer readable storage medium |
| CN112416597A (en) * | 2020-12-01 | 2021-02-26 | 太平金融科技服务（上海）有限公司 | System calling method and device, computer equipment and storage medium |
-
2021
- 2021-03-24 CN CN202110313211.0A patent/CN112988273A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110032454A (en) * | 2018-01-12 | 2019-07-19 | 北京京东尚科信息技术有限公司 | Remote invocation method, system and relevant device and computer readable storage medium |
| CN112416597A (en) * | 2020-12-01 | 2021-02-26 | 太平金融科技服务（上海）有限公司 | System calling method and device, computer equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10447684B2 (en) | Hosted application sandbox model | |
| AU2015364339B2 (en) | Multi-faceted compute instance identity | |
| EP3301881B1 (en) | Method, device and system for using and invoking oauth api | |
| EP3324293B1 (en) | Application managed service instances | |
| US7930701B2 (en) | JMS integration into an application server | |
| RU2598324C2 (en) | Means of controlling access to online service using conventional catalogue features | |
| US20100125612A1 (en) | Multi-tenancy using suite of authorization manager components | |
| WO2016197609A1 (en) | Method, device and system for managing user information about application | |
| CN110546979B (en) | Multi-level distributed access control between services and applications | |
| US9922181B2 (en) | Security model for network information service | |
| WO2018153353A1 (en) | Method, device, cloud computing system and computer system for implementing authentication/authorization | |
| CN110708335A (en) | Access authentication method and device and terminal equipment | |
| CN111062028B (en) | Authority management method and device, storage medium and electronic equipment | |
| WO2020001162A1 (en) | Container management method, apparatus, and device | |
| CN112311783A (en) | Authentication reverse proxy method and system | |
| KR20130077433A (en) | System and method for authority management in the mobile cloud service | |
| CN115544585A (en) | Method, equipment, device and storage medium for dynamically configuring secure memory | |
| CN105677693B (en) | Method and device for accessing database | |
| CN110619204A (en) | Invitation code generation method and device, terminal equipment and storage medium | |
| CN112988273A (en) | Calling method and interface management platform of heterogeneous system | |
| WO2023092316A1 (en) | Third-party service login method and apparatus, terminal device, and storage medium | |
| US8631480B2 (en) | Systems and methods for implementing security services | |
| CN114924783A (en) | Interface calling method, device, equipment and storage medium of application program | |
| CN112804069B (en) | Method, apparatus and computer readable storage medium for instantiating virtual network function | |
| WO2023134144A1 (en) | Method for processing cloud service in cloud system, and related apparatus |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |