CN114189476B - Multi-element interface shunting calling method and terminal - Google Patents
Multi-element interface shunting calling method and terminal Download PDFInfo
- Publication number
- CN114189476B CN114189476B CN202210034933.7A CN202210034933A CN114189476B CN 114189476 B CN114189476 B CN 114189476B CN 202210034933 A CN202210034933 A CN 202210034933A CN 114189476 B CN114189476 B CN 114189476B
- Authority
- CN
- China
- Prior art keywords
- data
- interface
- access
- interfaces
- access interface
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 20
- 238000004590 computer program Methods 0.000 claims description 8
- 238000001914 filtration Methods 0.000 claims description 7
- 238000010079 rubber tapping Methods 0.000 claims 2
- 238000012545 processing Methods 0.000 abstract description 10
- 238000009825 accumulation Methods 0.000 description 12
- 238000011161 development Methods 0.000 description 5
- 230000000903 blocking effect Effects 0.000 description 4
- 230000006870 function Effects 0.000 description 4
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000000694 effects Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L47/00—Traffic control in data switching networks
- H04L47/10—Flow control; Congestion control
- H04L47/12—Avoiding congestion; Recovering from congestion
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a multi-element interface shunting calling method and a terminal, which are used for acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups; setting a corresponding access interface for each data interface group; receiving an access request of a data demander, wherein the access request comprises an identification field; determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data; returning the target data to a data requiring party; when the access interfaces are set, the invention can set different outgoing parameters for the same data interface group according to actual requirements so as to correspond to different access interfaces, and a data demand party calls different access interfaces according to different required data, so that the data is shunted, the phenomenon of interface blockage when the access quantity is overlarge is avoided to a certain extent, and the processing efficiency of the access requests when the access quantity is overlarge is improved.
Description
Technical Field
The present invention relates to the field of data communications, and in particular, to a method and a terminal for shunting and calling a multiple interface.
Background
When the existing data collector provides data for the demander, a single interface is generally adopted for access, namely a unified interface is set by taking protocols such as webservice, HTTP and the like as request protocols to enable the demander to access, specific business requests of the demander are identified by defining transaction code fields, and the requests of the demander are routed to different processing logics according to the transaction code fields; in the method, a collecting party provides a unified interface address to the outside, if a large number of interface calls occur, the great request pressure is provided for the entrance service of the collecting party, in the prior art, load balancing is generally adopted to relieve the access pressure, but only one interface is provided to the outside to call, different service requests cannot be managed and controlled respectively, and even if the access amount of a certain processing logic (service) is smaller, the possibility that the access amount of other services is too large to be limited is provided; and the fields of the incoming parameters and the outgoing parameters provided by the same interface are also unified, if the corresponding incoming parameters and outgoing parameters are required to be formulated according to different use scenes, the codes are required to be modified, and the real-time requirement cannot be met.
Disclosure of Invention
The technical problems to be solved by the invention are as follows: the multi-element interface shunting calling method and the terminal are provided, and the data request processing efficiency of a large number of multi-services is improved.
In order to solve the technical problems, the invention adopts a technical scheme that:
a multi-element interface shunting calling method comprises the following steps:
s1, acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups;
s2, setting a corresponding access interface for each data interface group;
s3, receiving an access request of a data requiring party, wherein the access request comprises an identification field;
s4, determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data;
s5, returning the target data to the data requiring party.
In order to solve the technical problems, the invention adopts another technical scheme that:
a multi-element interface shunting call terminal, comprising a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the following steps when executing the computer program:
s1, acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups;
s2, setting a corresponding access interface for each data interface group;
s3, receiving an access request of a data requiring party, wherein the access request comprises an identification field;
s4, determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data;
s5, returning the target data to the data requiring party.
The invention has the beneficial effects that: the data interfaces provided by the data collector are grouped according to preset access logic to obtain a data interface group, the corresponding access interfaces are set according to the data interface group, the data demander accesses according to the access interfaces, the interfaces provided by the demander do not need to be concerned, the incoming parameters and the outgoing parameters of the interfaces can be defined, different outgoing parameters can be set for the same data interface group according to actual requirements when the access interfaces are set, so that different access interfaces are corresponding to the same data interface group, the data demander calls different access interfaces according to the different required data, the data is shunted, the phenomenon of interface blocking when the access amount is overlarge is avoided to a certain extent, and the processing efficiency of the access requests is improved when the access interfaces are accessed in a large scale.
Drawings
FIG. 1 is a flow chart of steps of a multi-element interface shunting calling method according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a multi-element interface shunting call terminal according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating a process for dynamically determining access interface outgoing parameters according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of a parameter structure according to an embodiment of the present invention;
description of the reference numerals:
1. a multi-element interface shunting calling terminal; 2. a processor; 3. a memory.
Detailed Description
In order to describe the technical contents, the achieved objects and effects of the present invention in detail, the following description will be made with reference to the embodiments in conjunction with the accompanying drawings.
Referring to fig. 1 and 3, a multi-element interface shunting calling method includes the steps of:
s1, acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups;
s2, setting a corresponding access interface for each data interface group;
s3, receiving an access request of a data requiring party, wherein the access request comprises an identification field;
s4, determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data;
s5, returning the target data to the data requiring party.
From the above description, the beneficial effects of the invention are as follows: the data interfaces provided by the data collector are grouped according to preset access logic to obtain a data interface group, the corresponding access interfaces are set according to the data interface group, the data demander accesses according to the access interfaces, the interfaces provided by the demander do not need to be concerned, the incoming parameters and the outgoing parameters of the interfaces can be defined, different outgoing parameters can be set for the same data interface group according to actual requirements when the access interfaces are set, so that different access interfaces are corresponding to the same data interface group, the data demander calls different access interfaces according to the different required data, the data is shunted, the phenomenon of interface blocking when the access amount is overlarge is avoided to a certain extent, and the processing efficiency of the access requests is improved when the access interfaces are accessed in a large scale.
Further, the S2 specifically is:
s21, acquiring a first incoming parameter, a first outgoing parameter and a first transaction code of each data interface in the data interface group, and acquiring the data collector corresponding to the data interface group;
s22, setting a second incoming parameter of the access interface according to the first incoming parameter, setting a second outgoing parameter of the access interface according to the first outgoing parameter and a preset target data item, setting an interface number of the access interface according to the first transaction code, and marking the access interface according to the data collector;
s23, releasing the access interface to a unified API gateway.
As can be seen from the above description, the data interfaces in the data interface group are accessed by calling the access interfaces by determining the input parameters required by the corresponding access interfaces according to the input parameters of the data interface group; according to the data interface group and the preset target data item, setting the outgoing parameters of the access interface, the interface provided by the data collector by the data interface is more difficult to modify, and the data collector usually places the outgoing parameters containing a plurality of associated data in one interface in order to reduce the maintenance cost of the interface, not necessarily all the required data, and can accurately acquire the required data by filtering the data returned by the data interface by setting the outgoing parameters of the access interface.
Further, the step S4 specifically includes:
s41, determining the first access interface corresponding to the identification field, and acquiring an interface document of the first access interface;
s42, converting the access request according to the interface document to obtain an interface protocol and a data format;
s43, executing the first access interface according to the interface protocol and the data format to obtain return data;
s44, filtering the return data according to the second outgoing parameters to obtain target data.
According to the description, the interface protocol and the data format are obtained by converting the access request according to the interface document of the access interface, the access interface is called according to the interface protocol and the data format, the returned data is filtered through the second outgoing parameters of the access interface, the data requesting party does not need to consider which data gathering party's interface needs to be called and which data gathering party's interface is specifically called, the convenience of the data requesting party for requesting the data is improved, the data interfaces are assembled by the access interface, and the data processing efficiency is improved.
Further, the unified API gateway in S23 is Kong middleware.
From the above description, it can be seen that, using Kong as a unified API gateway, kong's own plug-in can save development time, and Kong's function is complete, reducing development difficulty.
Further, the step S5 specifically includes:
encrypting the target data, and sending the encrypted target data to a data requiring party.
As can be seen from the above description, the data is encrypted and then sent to the data demander, so that the security of the data in the transmission process is ensured.
A multi-element interface shunting call terminal, comprising a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the following steps when executing the computer program:
s1, acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups;
s2, setting a corresponding access interface for each data interface group;
s3, receiving an access request of a data requiring party, wherein the access request comprises an identification field;
s4, determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data;
s5, returning the target data to the data requiring party.
The invention has the beneficial effects that: the data interfaces provided by the data collector are grouped according to preset access logic to obtain a data interface group, the corresponding access interfaces are set according to the data interface group, the data demander accesses according to the access interfaces, the interfaces provided by the demander do not need to be concerned, the incoming parameters and the outgoing parameters of the interfaces can be defined, different outgoing parameters can be set for the same data interface group according to actual requirements when the access interfaces are set, so that different access interfaces are corresponding to the same data interface group, the data demander calls different access interfaces according to the different required data, the data is shunted, the phenomenon of interface blocking when the access amount is overlarge is avoided to a certain extent, and the processing efficiency of the access requests is improved when the access interfaces are accessed in a large scale.
Further, the S2 specifically is:
s21, acquiring a first incoming parameter, a first outgoing parameter and a first transaction code of each data interface in the data interface group, and acquiring the data collector corresponding to the data interface group;
s22, setting a second incoming parameter of the access interface according to the first incoming parameter, setting a second outgoing parameter of the access interface according to the first outgoing parameter and a preset target data item, setting an interface number of the access interface according to the first transaction code, and marking the access interface according to the data collector;
s23, releasing the access interface to a unified API gateway.
As can be seen from the above description, the data interfaces in the data interface group are accessed by calling the access interfaces by determining the input parameters required by the corresponding access interfaces according to the input parameters of the data interface group; according to the data interface group and the preset target data item, setting the outgoing parameters of the access interface, the interface provided by the data collector by the data interface is more difficult to modify, and the data collector usually places the outgoing parameters containing a plurality of associated data in one interface in order to reduce the maintenance cost of the interface, not necessarily all the required data, and can accurately acquire the required data by filtering the data returned by the data interface by setting the outgoing parameters of the access interface.
Further, the step S4 specifically includes:
s41, determining the first access interface corresponding to the identification field, and acquiring an interface document of the first access interface;
s42, converting the access request according to the interface document to obtain an interface protocol and a data format;
s43, executing the first access interface according to the interface protocol and the data format to obtain return data;
s44, filtering the return data according to the second outgoing parameters to obtain target data.
According to the description, the interface protocol and the data format are obtained by converting the access request according to the interface document of the access interface, the access interface is called according to the interface protocol and the data format, the returned data is filtered through the second outgoing parameters of the access interface, the data requesting party does not need to consider which data gathering party's interface needs to be called and which data gathering party's interface is specifically called, the convenience of the data requesting party for requesting the data is improved, the data interfaces are assembled by the access interface, and the data processing efficiency is improved.
Further, the unified API gateway in S23 is Kong middleware.
From the above description, it can be seen that, using Kong as a unified API gateway, kong's own plug-in can save development time, and Kong's function is complete, reducing development difficulty.
Further, the step S5 specifically includes:
encrypting the target data, and sending the encrypted target data to a data requiring party.
As can be seen from the above description, the data is encrypted and then sent to the data demander, so that the security of the data in the transmission process is ensured.
Referring to fig. 1, a first embodiment of the present invention is as follows:
a multi-element interface shunting calling method comprises the following steps:
s1, acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups;
s2, setting a corresponding access interface for each data interface group, specifically:
s21, acquiring a first incoming parameter, a first outgoing parameter and a first transaction code of each data interface in the data interface group, and acquiring the data collector corresponding to the data interface group;
s22, setting a second incoming parameter of the access interface according to the first incoming parameter, setting a second outgoing parameter of the access interface according to the first outgoing parameter and a preset target data item, setting an interface number of the access interface according to the first transaction code, and marking the access interface according to the data collector;
if the data collector has two interfaces of an accumulation fund list and an accumulation fund account, wherein the accumulation fund list interface needs to have an accumulation fund account as an incoming parameter, the accumulation fund account needs to be called firstly and then to acquire an outgoing parameter, the accumulation fund account interface needs to have an identity card number as an incoming parameter, an edge node performs coding development in advance according to the scene, when an access interface for inquiring the accumulation fund list is defined, only the input parameter needs to be defined as an identity card, after the edge node receives the identity card input parameter, the accumulation fund account interface is called preferentially, and the accumulation fund account is acquired and then the accumulation fund account interface is called again to acquire the accumulation fund list, wherein the identity card number is a unified external inquiry field;
s23, releasing the access interface to a unified API gateway;
in an alternative embodiment, the unified API gateway may be considered as an entry where the system communicates with the outside world, and logic to handle some non-business logic, such as rights verification, monitoring, caching, request routing, etc., may be performed at the gateway. The Kong gateway middleware is an open-source API management service, and the data flow platform realizes the management function of the API based on the middleware, such as the release or the off-shelf of the API; after receiving the request, the API gateway firstly checks the data authority through the data authentication service, backfills default parameters and values according to the forced rules, and then forwards the request to the edge node service for processing;
s3, receiving an access request of a data requiring party, wherein the access request comprises an identification field;
in an alternative embodiment, the unified API gateway is Kong middleware; the Kong gateway exposes an external API service interface (access interface), the demander calls the exposed access interface to send an access request, and after receiving the access request, the Kong gateway forwards the request to a data interface of the data collector and returns the data received from the data interface of the data collector to the demander;
s4, determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data, wherein the method specifically comprises the following steps:
s41, determining the first access interface corresponding to the identification field, and acquiring an interface document of the first access interface;
s42, converting the access request according to the interface document to obtain an interface protocol and a data format;
in an alternative embodiment, the interface protocol is webservice protocol, and the data format includes XML data format;
s43, executing the first access interface according to the interface protocol and the data format to obtain return data;
s44, filtering the return data according to the second outgoing parameters to obtain target data;
s5, returning the target data to a data demand party, specifically:
encrypting the target data, and sending the encrypted target data to a data requiring party.
The second embodiment of the invention is as follows:
a multiple interface split call method, which is different from the first embodiment in that:
the step S22 is specifically as follows:
the access interface is configured through the visual form:
basic information of the configuration access interface: the basic information comprises a calling address for calling an access interface, an access interface name, an access interface number, a data collector identifier and an edge node address matched with the data collector, wherein the access interface number corresponds to transaction codes of different data interfaces provided by the data collector;
each incoming parameter needs to be provided with an attribute, wherein the attribute comprises a parameter name, a parameter type, a parameter description, whether a filling item is necessary or not and a forcing rule, the forcing rule defines the parameter as a non-filling field, the parameter can be automatically calculated according to a preset forcing rule expression, and the parameter is not required to be transferred when the interface is called;
each outgoing parameter needs to be provided with an attribute, wherein the attribute comprises a parameter name, a parameter type, a parameter description and ciphertext data, the ciphertext data marks that the field is a real data field in the return result of the API of the access interface, and because the circulation platform data is transmitted in an encrypted mode, the field defines the plaintext structure of the ciphertext data in a JSON format, and meanwhile, the edge node filters redundant fields in the query result of the collector interface through the configuration;
in an alternative embodiment, referring to fig. 4, specific key values are:
{ "name": "cipherertext", "encrypted": "child Nodes" ({ "name": "ROOT", "built-in" is a false, "child Nodes": [ { "name": "BODY", "built-in" is a false, "child Nodes": [ { "name": "FILE_DATA", "built-in" is a false, "child Nodes": [ ], "required": true "," type ": a string", "d-script": the encoded pdf FILE of "base 64", "isDefault": false }, "required": a true "," type ": o-object", "isDefault": false }, "required": false "," type ": object", "device": false "," device ": device", "device": type "," device ": device }" is a encrypted "is a product }
Wherein, name represents field name, encrypted represents whether encryption, child represents child node, required represents whether filling is necessary, type represents field type, isdefaults represents whether default field can not be deleted, if child node is empty, it is indicated that this field has no child node;
if "file_data" indicates storage configuration FILE DATA, "encrypted" indicates that the storage configuration FILE DATA is not encrypted, "required" indicates that the item is a mandatory item, "type" indicates that the field type of the item is a character string, "description" indicates that the pdf FILE after encoding by base64 indicates that the description information of the item is: the pdf file after base64 encoding, "isDefault" means that the item has no default value;
ciphereText represents the encrypted original, ROOT, BODY represents the hierarchical structure of the returned DATA, and FILE_DATA represents the specific FILE.
Specifically, when the access interface is called, the data interface (such as an accumulation fund interface or a social security interface) of the corresponding data collector is determined through the transaction code, and different services (account information, payment flow and the like) are transmitted to different values so as to identify the called service and realize the dynamic generation of the API.
Specifically, the transaction code values correspond to different services, for example 2101 represents account information, 2120 represents payment flow.
Referring to fig. 2, a third embodiment of the present invention is as follows:
the multi-element interface shunting call terminal 1 comprises a processor 2, a memory 3 and a computer program which is stored in the memory 3 and can run on the processor 2, wherein the processor 2 realizes the steps in the first embodiment or the second embodiment when executing the computer program;
in an alternative embodiment, a multi-element interface offload call terminal is a combination of a data flow platform and an edge node; the access interfaces are simultaneously issued on the data circulation platform and the corresponding edge nodes, and the edge nodes correspond to the data collectors, namely the access interfaces are issued on the edge nodes corresponding to the data collectors where the corresponding data interfaces are located.
In summary, the invention provides a multi-element interface shunting calling method and a terminal, which integrate and formulate a plurality of data interfaces provided by a data collector to corresponding access interfaces, dynamically formulate outgoing parameters of the access interfaces according to different target return data to obtain a plurality of different access interfaces, and enable each access request with different target return data to access the data collector through the different access interfaces, thereby realizing shunting of the access requests and avoiding the problem of blocking the external interfaces; based on the method, the micro-service architecture can be utilized to monitor the specific API service according to the service request condition; the cloud server is utilized to dynamically expand requests with more loads, meanwhile, for a request with large quantity, a certain API service can be set by using a current limiting plug-in of a Kong gateway, only a few times can be called in a certain period of time, and the exceeding process is refused, so that the robustness of the system is further improved, the original system functions can be used without changing the system architecture of a data collector, and the data flow platform is used for converting the collector interface to provide unified and personalized services to the outside.
The foregoing description is only illustrative of the present invention and is not intended to limit the scope of the invention, and all equivalent changes made by the specification and drawings of the present invention, or direct or indirect application in the relevant art, are included in the scope of the present invention.
Claims (8)
1. A multi-element interface shunting calling method is characterized by comprising the following steps:
s1, acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups;
s2, setting a corresponding access interface for each data interface group;
s3, receiving an access request of a data requiring party, wherein the access request comprises an identification field;
s4, determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data;
s5, returning the target data to a data requiring party;
the step S2 is specifically as follows:
s21, acquiring a first incoming parameter, a first outgoing parameter and a first transaction code of each data interface in the data interface group, and acquiring the data collector corresponding to the data interface group;
s22, setting a second incoming parameter of the access interface according to the first incoming parameter, setting a second outgoing parameter of the access interface according to the first outgoing parameter and a preset target data item, setting an interface number of the access interface according to the first transaction code, and marking the access interface according to the data collector;
s23, releasing the access interface to a unified API gateway.
2. The multi-element interface shunting calling method according to claim 1, wherein the step S4 is specifically:
s41, determining the first access interface corresponding to the identification field, and acquiring an interface document of the first access interface;
s42, converting the access request according to the interface document to obtain an interface protocol and a data format;
s43, executing the first access interface according to the interface protocol and the data format to obtain return data;
s44, filtering the return data according to the second outgoing parameters to obtain target data.
3. The multi-component interface forking calling method of claim 1, wherein the unified API gateway in S23 is Kong middleware.
4. The multi-element interface shunting calling method according to claim 1, wherein the step S5 is specifically:
encrypting the target data, and sending the encrypted target data to a data requiring party.
5. A multi-element interface shunting call terminal, comprising a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor realizes the following steps when executing the computer program:
acquiring a plurality of data interfaces provided by a data collector, and grouping the data interfaces according to preset access logic to obtain a plurality of data interface groups;
s2, setting a corresponding access interface for each data interface group;
s3, receiving an access request of a data requiring party, wherein the access request comprises an identification field;
s4, determining a first access interface corresponding to the identification field, and executing the first access interface according to the identification field to obtain target data;
s5, returning the target data to a data requiring party;
the step S2 is specifically as follows:
s21, acquiring a first incoming parameter, a first outgoing parameter and a first transaction code of each data interface in the data interface group, and acquiring the data collector corresponding to the data interface group;
s22, setting a second incoming parameter of the access interface according to the first incoming parameter, setting a second outgoing parameter of the access interface according to the first outgoing parameter and a preset target data item, setting an interface number of the access interface according to the first transaction code, and marking the access interface according to the data collector;
s23, releasing the access interface to a unified API gateway.
6. The multi-component interface tapping and calling terminal according to claim 5, wherein the S4 specifically is:
s41, determining the first access interface corresponding to the identification field, and acquiring an interface document of the first access interface;
s42, converting the access request according to the interface document to obtain an interface protocol and a data format;
s43, executing the first access interface according to the interface protocol and the data format to obtain return data;
s44, filtering the return data according to the second outgoing parameters to obtain target data.
7. The multi-component interface forking call terminal of claim 5, wherein the unified API gateway in S23 is Kong middleware.
8. The multi-component interface tapping and calling terminal according to claim 5, wherein the S5 specifically is:
encrypting the target data, and sending the encrypted target data to a data requiring party.
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2021101044825 | 2021-01-26 | ||
| CN202110104482 | 2021-01-26 |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114189476A CN114189476A (en) | 2022-03-15 |
| CN114189476B true CN114189476B (en) | 2023-12-08 |
Family
ID=80606855
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210034933.7A Active CN114189476B (en) | 2021-01-26 | 2022-01-13 | Multi-element interface shunting calling method and terminal |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114189476B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114610414A (en) * | 2022-03-22 | 2022-06-10 | 未鲲(上海)科技服务有限公司 | Method and device for calling integration interface, computer equipment and storage medium |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1540932A (en) * | 2003-04-22 | 2004-10-27 | 华为技术有限公司 | Implementing Method for sending datagram type message from assigned port |
| CN101505235A (en) * | 2009-03-05 | 2009-08-12 | 华为技术有限公司 | Component loading method and apparatus |
| CN101924692A (en) * | 2009-06-09 | 2010-12-22 | 鸿富锦精密工业（深圳）有限公司 | Method for processing multicast message by router |
| CN101958838A (en) * | 2010-10-14 | 2011-01-26 | 联动优势科技有限公司 | Data access method and device |
| CN105553996A (en) * | 2015-12-23 | 2016-05-04 | 北京奇虎科技有限公司 | Method and device for processing data access request |
| CN108199975A (en) * | 2018-03-28 | 2018-06-22 | 新华三技术有限公司 | A kind of flow control methods and device |
| CN110515924A (en) * | 2019-08-15 | 2019-11-29 | 平安普惠企业管理有限公司 | Database manipulation logic verify method, apparatus, equipment and readable storage medium storing program for executing |
| CN111343181A (en) * | 2020-02-26 | 2020-06-26 | 中国邮政储蓄银行股份有限公司 | Message processing method and system, data pool and computer readable storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9319299B2 (en) * | 2008-01-25 | 2016-04-19 | Alcatel Lucent | Method and apparatus for link aggregation using links having different link speeds |
| US9626108B2 (en) * | 2014-09-16 | 2017-04-18 | Kove Ip, Llc | Dynamically provisionable and allocatable external memory |
-
2022
- 2022-01-13 CN CN202210034933.7A patent/CN114189476B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1540932A (en) * | 2003-04-22 | 2004-10-27 | 华为技术有限公司 | Implementing Method for sending datagram type message from assigned port |
| CN101505235A (en) * | 2009-03-05 | 2009-08-12 | 华为技术有限公司 | Component loading method and apparatus |
| CN101924692A (en) * | 2009-06-09 | 2010-12-22 | 鸿富锦精密工业（深圳）有限公司 | Method for processing multicast message by router |
| CN101958838A (en) * | 2010-10-14 | 2011-01-26 | 联动优势科技有限公司 | Data access method and device |
| CN105553996A (en) * | 2015-12-23 | 2016-05-04 | 北京奇虎科技有限公司 | Method and device for processing data access request |
| CN108199975A (en) * | 2018-03-28 | 2018-06-22 | 新华三技术有限公司 | A kind of flow control methods and device |
| CN110515924A (en) * | 2019-08-15 | 2019-11-29 | 平安普惠企业管理有限公司 | Database manipulation logic verify method, apparatus, equipment and readable storage medium storing program for executing |
| CN111343181A (en) * | 2020-02-26 | 2020-06-26 | 中国邮政储蓄银行股份有限公司 | Message processing method and system, data pool and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 基于.net的校园网格异构数据统一访问接口;王海燕;;计算机工程(第11期);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114189476A (en) | 2022-03-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11411897B2 (en) | Communication method and communication apparatus for message queue telemetry transport | |
| EP2445238B1 (en) | Method and system for providing user service data | |
| CN103716326A (en) | Resource access method and URG | |
| CN103095852A (en) | Cloud storage file sharing method based on two-dimensional code | |
| EP1388084A2 (en) | Counting and billing mechanism for web-services based on a soap-communication protocol | |
| CN104967650A (en) | Third-party e-commerce platform unified releasing method | |
| CN112055078B (en) | Data transmission method, device, computer equipment and storage medium | |
| CN104717647B (en) | Professional ability method for authenticating, equipment and system | |
| CN114567650B (en) | Data processing method and Internet of things platform system | |
| CN111427613B (en) | Application program interface API management method and device | |
| CN111988418B (en) | Data processing method, device, equipment and computer readable storage medium | |
| CN114189476B (en) | Multi-element interface shunting calling method and terminal | |
| CN103457802A (en) | Information transmission system and method | |
| CN1753569B (en) | System and method for treating mobile communication data business based on false code | |
| CN100452704C (en) | Method and method for issuing blog articles | |
| CN103179211A (en) | Cloud-computing-based data processing method and system of comprehensive operation support system | |
| CN108833500B (en) | Service calling method, service providing method, data transmission method and server | |
| CN113114678B (en) | Service execution method and device | |
| CN109525550B (en) | Data message processing method, device and system | |
| CN106656936B (en) | A kind of access control method, PRP entity, PDP entity and PEP entity | |
| CN114968617A (en) | API conversion system, access request processing method thereof, electronic device and medium | |
| CN114547214A (en) | Long-link data processing method, device and equipment | |
| CN110166502A (en) | Data capture method, service providing end, service use end and network functional entity | |
| CN114760602A (en) | Holographic communication method, device, system and computer readable storage medium | |
| CN114676205A (en) | Event information processing method and device |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |