CN112769687A - API gateway platform - Google Patents
API gateway platform Download PDFInfo
- Publication number
- CN112769687A CN112769687A CN202011436226.8A CN202011436226A CN112769687A CN 112769687 A CN112769687 A CN 112769687A CN 202011436226 A CN202011436226 A CN 202011436226A CN 112769687 A CN112769687 A CN 112769687A
- Authority
- CN
- China
- Prior art keywords
- component
- api
- access request
- api gateway
- gateway platform
- 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
- 238000012544 monitoring process Methods 0.000 claims description 18
- 238000006243 chemical reaction Methods 0.000 claims description 9
- 239000004973 liquid crystal related substance Substances 0.000 claims description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 52
- 238000010586 diagram Methods 0.000 description 6
- 238000000034 method Methods 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 4
- 238000013475 authorization Methods 0.000 description 3
- 238000012360 testing method Methods 0.000 description 3
- 230000005856 abnormality Effects 0.000 description 2
- 238000004891 communication Methods 0.000 description 2
- 230000007547 defect Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/66—Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/14—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic
- H04L63/1408—Network architectures or network communication protocols for network security for detecting or protecting against malicious traffic by monitoring network traffic
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention relates to an API gateway platform, which comprises a gateway device and a management center, wherein the management center is used for issuing a custom component related to the requirements of enterprise users; and the gateway device is used for acquiring the corresponding custom component from the management center after receiving an access request of a terminal user and if the corresponding functional component cannot be acquired from the cache according to the access request, loading the acquired custom component through a custom loader and executing the custom component. The technical scheme of the invention supports the user-defined component, can dynamically load and run in the gateway device, and can realize reloading configuration and running of the component under the condition of not interrupting the gateway service.
Description
Technical Field
The invention relates to the field of network communication, in particular to an API gateway platform.
Background
With the development of the overall trend of the API, each historical era faces different challenges, and the architecture changes, from the most primitive "transport protocol communication" to "simple interface integration" to "message middleware" to the present "standard REST", it can be seen that the development of the API tends to be more concise, integrated and normalized.
The API gateway is a uniform entrance provided for external access internal interface service on the system boundary, receives the request of the client, forwards the request to the corresponding back-end system service according to a certain strategy and route, processes the result returned by the back-end service end, and the like. That is, the API gateway is responsible for routing proxies, performance allocations, etc. for the entire API resource.
With the increasing functions of the on-line client, the number of the APIs to be called is increased, and the types of data transmitted by different clients are also different for the different types of clients, which relates to the problem of API gateway configuration and maintenance. The current common practice is as follows: the configuration of the API gateway is manually modified according to requirements, and the API gateway needs to be restarted after being modified every time, so that the existing API gateway configuration has the problem of difficult maintenance.
Disclosure of Invention
The technical problem to be solved by the invention is to provide an API gateway platform aiming at the defect that the configuration of an API gateway is difficult to maintain in the prior art.
The technical scheme adopted by the invention for solving the technical problems is as follows: an API gateway platform is constructed comprising a gateway device having a plurality of functional components, and further comprising a management center, and,
the management center is used for publishing a custom assembly related to the enterprise user requirement;
and the gateway device is used for acquiring the corresponding custom component from the management center after receiving an access request of a terminal user and if the corresponding functional component cannot be acquired from the cache according to the access request, loading the acquired custom component through a custom loader and executing the custom component.
Preferably, the management center is further configured to receive setting information for setting the functional component and the API by an enterprise user.
Preferably, the monitoring center is further included, the functional components include a logging component, and;
the log recording component is used for recording a monitoring log;
and the monitoring center is used for collecting the monitoring log of the gateway device, generating a corresponding report according to the monitoring log, and/or judging whether the abnormity occurs according to the monitoring log, and generating alarm information when the abnormity occurs.
Preferably, the functional components include:
the authentication component is used for authenticating the identity of the terminal user by adopting at least one of the following authentication modes after receiving the access request: token, Basic, IP address;
an authentication component: and after the identity authentication is passed, detecting whether the terminal user has the right to access the corresponding API.
Preferably, the functional components include:
and the flow control component is used for judging whether the number of times of the access requests in the preset time period exceeds a threshold value, and if so, intercepting the newly received access requests.
Preferably, the functional components include:
and the protocol conversion component is used for converting the access request according to the received access request.
Preferably, the functional components include:
and the routing component is used for routing the converted access request to the corresponding back-end micro service node.
Preferably, the functional components include:
and the overtime fusing component is used for preventing external access requests in a fusing mode when all back-end micro service nodes are in a busy state.
Preferably, the functional components include:
and the data cache component is used for judging whether the called API has a set cache after receiving the access request, and if so, directly extracting data from the cache and returning the data to the terminal user.
Preferably, the number of the gateway devices is multiple, and the API gateway platform is a distributed API gateway platform; furthermore, it is possible to provide a liquid crystal display device,
the management center is used for sending an updating message to each gateway device in the cluster after receiving the setting information;
and the gateway device is used for refreshing the corresponding functional component when receiving the updating message.
The technical scheme provided by the invention can support the user-defined component, can dynamically load and run in the gateway device, and can realize reloading configuration and running of the component under the condition of not interrupting the gateway service.
Drawings
In order to illustrate the embodiments of the invention more clearly, the drawings that are needed in the description of the embodiments will be briefly described below, it being apparent that the drawings in the following description are only some embodiments of the invention, and that other drawings may be derived from those drawings by a person skilled in the art without inventive effort. In the drawings:
FIG. 1 is a logical block diagram of a first embodiment of an API gateway platform of the present invention;
FIG. 2 is a logical structure diagram of a second embodiment of the API gateway platform of the present invention;
fig. 3 is a logical structure diagram of the third embodiment of the API gateway platform 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. 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.
Fig. 1 is a logic structure diagram of an API gateway platform according to a first embodiment of the present invention, where the API gateway platform includes: a gateway device 100 and a management center 200, wherein the gateway device 100 includes a plurality of functional components. Furthermore, the management center 200 is configured to issue a custom component related to the enterprise user requirement, and the gateway device 100 is configured to, after receiving the access request, if the corresponding functional component cannot be obtained from the cache according to the access request, obtain the corresponding custom component from the management center 200, load the obtained custom component through the custom class loader, and execute the custom component. .
Regarding the embodiment, it should be noted that, the Class in the JVM is uniquely identified by a Class loader and a fully qualified name, and a component is published in the form of a Jar package, but the entry Class names of multiple versions of the same component need to be kept unchanged, so that a custom Class loader is needed to implement hot plug and multi-version coexistence of the component. In a specific example, after receiving an access request (API call request), the gateway device fetches the API configured component list from the cache according to the request parameters, then obtains the class instance corresponding to the component from the cache one by one, and if the class instance is not found, tries to load the Jar package through the custom class loader, and initializes the component instance and the cache. In addition, the custom class loader may need to inherit to URLClassLoader directly, otherwise it must be specified that its parent class loader is the loader of the executor, otherwise the component cannot refer to other classes of the gateway.
Through the technical scheme of the embodiment, except built-in functional components of products in the gateway device, enterprise users can customize the components according to actual requirements, output the components into Jar packages and upload and release the Jar packages through the management center. After receiving the access request of the terminal user, the gateway device can acquire the corresponding custom component from the management center, and load and execute the custom component, so that the coexistence of hot plug and multi-version of the component is realized.
Further, in an optional embodiment, the management center 200 is further configured to receive setting information of the enterprise user for setting the functional components and APIs, for example, by providing a unified management interface, the user can set and maintain basic information of the components, APIs, and systems.
Fig. 2 is a logical structure diagram of an API gateway platform according to a second embodiment of the present invention, which differs from the embodiment shown in fig. 1 only in that the API gateway platform further includes a monitoring center 300, and functional components of the gateway device include a log recording component, which is used for recording monitoring logs, including an access log and a behavior log. The monitoring center 300 is configured to collect monitoring logs of the gateway device, generate a corresponding report according to the monitoring logs, and/or determine whether an abnormality occurs according to the monitoring logs, and generate warning information when the abnormality occurs, so as to implement performance monitoring of the system or provide for later query.
Fig. 3 is a logic structure diagram of a third embodiment of the API gateway platform of the present invention, where the API gateway platform of this embodiment includes: the gateway device 100 is responsible for accessing requests, scheduling, loading and executing components of terminal users, routing the requests to corresponding micro service nodes in a back-end service cluster, processing results returned by the back-end micro service nodes, and the like. The management center 200 provides a unified management interface for the user to set and maintain the API, the functional component, and the system basic information, and specifically includes: API management settings, API group management settings, flow control policy settings, document generation settings, protocol conversion settings, logging settings, cache settings, encryption/decryption settings, service management settings, alarm settings, etc. The monitoring center 300 is responsible for collecting monitoring logs, performing trend analysis, generating various operation and maintenance reports, automatically giving alarms and the like.
The gateway apparatus 100 includes functional components specifically including: authentication component 101, authentication component 102, flow control component 103, routing component 104, protocol conversion component 105, timeout fusing component 106, data caching component 107, service orchestration component 108, service registration/discovery component 109, load balancing component 110, version graying/publishing component 111, logging component 112. Wherein:
the authentication component 101 is configured to authenticate the identity of the end user after receiving the access request by using at least one of the following authentication methods: token, Basic, IP address. Only authenticated end users can further access the services exposed by the gateway. The authentication component 102 is configured to detect whether the end user has an authority to access the corresponding API after the identity authentication is passed, and forward the terminal user to a subsequent service only when the authentication is passed. Through the multi-dimensional authentication and authorization strategy, the security of data transmission can be ensured.
The flow control component 103 is configured to determine whether the number of times of the access request within a preset time period exceeds a threshold, and intercept a newly received access request if the number of times of the access request within the preset time period exceeds the threshold. Aiming at the defects that the back-end service pressure is high, the service breakdown is easy to occur and the normal experience of a user is influenced because the back-end service generally judges whether the flow is effective when partial invalid flow directly flows into the back-end service at present, the embodiment configures a flow threshold value in a gateway device, for example, the number of requests per second, minute and hour is limited, and when the flow exceeds the threshold value, a new request can be intercepted by the gateway to ensure that the back-end service can normally run.
The load balancing component 110 is configured to perform dynamic load balancing adjustment according to the load condition of the back-end micro service node. The timeout fusing component 106 is configured to block external access requests in the form of a fuse when all back-end microservice nodes are busy. In this embodiment, once a particular internal microservice instance is highly loaded and even unable to respond in a timely manner, the load balancing component 110 reduces or stops forwarding requests to that microservice instance via load balancing policies. When all microservice instances are not processed, the timeout fusing component 106 may also block external requests by fusing or throttling to ensure availability of the entire system.
The protocol conversion component 105 is configured to convert the access request based on the received access request. In this embodiment, since the gateway device is externally facing to a plurality of different user terminals, for example, Web, APP, third-party partners, and the like, the types of data transmitted by different terminals may be different. Therefore, the protocol conversion module 105 is required to have a data conversion function to convert data transmitted from different terminals into the same type for forwarding, so that the diversity of the requests is compatible, and the flexibility of the micro-service is ensured. In addition, since the gateway uniformly exposes the Rest service to the outside, and the backend microservices are diverse, developers also need to develop different protocol conversion components according to the interface types of the backend microservices nodes.
The routing component 104 is operative to route the translated access request to a corresponding back-end microservice node. In this embodiment, all requests are sent to the gateway device first, and then the routing component 104 routes the requests to different microservice nodes according to different requests, for example, according to paths or parameters. Furthermore, since the internal microservice nodes may also be changed, added or deleted as traffic is adjusted, the routing component 104 may work in conjunction with the service registration/discovery component 109 to ensure that external requests are forwarded to the most appropriate microservice node.
The data cache component 107 is configured to determine whether the called API has a set cache after receiving the access request, and if so, directly extract data from the cache and return the data to the end user. In this embodiment, for an API of which query type and data change is infrequent, appropriate cache setting may effectively reduce the pressure of a back-end microservice node, specifically, a manager may configure whether caching is required according to the characteristics of the API, and after receiving an access request, a gateway device may determine whether a cache is set for the API that needs to be called, and if the cache is set and the cache is not expired, extract data from the cache directly and return the data to an end user, and if the cache is expired, access the back-end microservice via the routing component 104, and then update the cache. By means of data caching of key contents such as the API, the functional components and the like, access to a Database (DB) can be reduced as much as possible when the gateway device runs, and meanwhile, due to the fact that disk IO is not written in the running process, the fact that the throughput of the gateway is influenced by the performance of the disk IO is avoided.
Further, in an optional embodiment, the number of the gateway devices is plural, and the API gateway platform is a distributed API gateway platform, and the architecture is characterized in that: the distributed cache is based on Redis, the database is based on MySQL, and the distributed configuration is based on Zookeeper. The management center 200 is configured to send an update message to each gateway device in the cluster after receiving the setting information; the gateway apparatus 100 is configured to refresh the corresponding functional component when receiving the update message. In this embodiment, after the management center performs configuration adjustment on the API or the functional component, the Zookeeper cluster data synchronization mechanism may be used to update the configuration information to each gateway device in time, specifically, the management center issues a message to the message center, and each gateway device refreshes the cache data after receiving the message. In addition, the gateway device may also register with the Zookeeper node at startup to passively update the configuration information.
In addition, the API gateway platform also has Docker container Hua support, mirror images such as split gateway devices, management services, third-party middleware dependence and the like, and is convenient for flexible capacity expansion.
The technical scheme of the embodiment has the following beneficial effects:
1. reducing complexity of back-end micro-service phase intermodulation chain
The back-end requirements are deployed in a micro-service mode, and part of requirements may relate to the identification of user rights. However, the existing method for restricting the permission to use the local function for authentication includes that push service and open source gallery all request the original back-end interface in the http protocol manner to acquire user information, and with more and more services called each other in the later period, too strong dependence between services and complicated dependence relationship between services also need to be maintained, so that the solution is obviously unwise. When other modules are updated each time, the call chain between the services needs to be concerned, so that the complexity of deploying and updating the services is improved. According to the scheme, authentication and authorization are carried out in the gateway device, and the gateway device is forwarded to the back-end micro service node after passing the authentication and authorization, so that the complexity of the back-end micro service phase intermodulation chain can be greatly reduced.
2. Reducing problems due to backend service updates
When a new technology or reconfiguration logic is used for a micro service, according to the existing architecture, the micro service can release the formal environment after the testing environment passes, but due to the difference between the formal environment and the testing environment, for example, the user behavior is unknown, and the traffic size and data are not uniform. Under these factors, although the testing environment passes, the formal environment may still bring about some unknown problems. According to the scheme, the protocol conversion component, the flow control component and the like are arranged in the gateway device, and the components can be configured and maintained through the management center, so that the problems caused by back-end service updating can be reduced.
3. Reducing maintenance API complexity
As the functions of the application are more and more, the number of APIs is more and more, and more APIs need to be maintained. According to the scheme, the API can be managed in the management center, and the complexity of maintaining the API is reduced.
4. Setting unified monitoring points
The monitoring API is required to be deployed according to a service implementation mode by self when the back-end micro-services are more and more, the existing monitoring mode is that the back-end services, the push services, the open source gallery and the like are separately deployed, each service is required to be monitored and displayed in the service by self, and the operation is more and more complex as the back-end services are more and more. According to the scheme, the monitoring center is uniformly arranged, and the monitoring request state and the processing time are monitored according to the business name.
5. Relieving backend service pressure
The method aims at the problem that in the existing mode, part of invalid traffic can directly flow into the back-end service, and whether the traffic is valid or not is judged by the back-end service, so that the pressure of the back-end service is increased, even the back-end service is broken down, and the normal experience of a user is influenced. According to the scheme, the flow control assembly, the overtime fusing assembly and the load balancing assembly are arranged in the gateway device to reduce the rear-end service pressure, and the user experience is improved.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the scope of the claims of the present invention.
Claims (10)
1. An API gateway platform, comprising a gateway device with a plurality of functional components, characterized by further comprising a management center, and,
the management center is used for publishing a custom assembly related to the enterprise user requirement;
and the gateway device is used for acquiring the corresponding custom component from the management center after receiving an access request of a terminal user and if the corresponding functional component cannot be acquired from the cache according to the access request, loading the acquired custom component through a custom loader and executing the custom component.
2. The API gateway platform of claim 1,
and the management center is also used for receiving the setting information of the enterprise user for setting the functional component and the API.
3. The API gateway platform of claim 1, further comprising a monitoring center, wherein the functional components include a logging component, and further;
the log recording component is used for recording a monitoring log;
and the monitoring center is used for collecting the monitoring log of the gateway device, generating a corresponding report according to the monitoring log, and/or judging whether the abnormity occurs according to the monitoring log, and generating alarm information when the abnormity occurs.
4. The API gateway platform of any of claims 1-3, wherein the functional component comprises:
the authentication component is used for authenticating the identity of the terminal user by adopting at least one of the following authentication modes after receiving the access request: token, Basic, IP address;
an authentication component: and after the identity authentication is passed, detecting whether the terminal user has the right to access the corresponding API.
5. The API gateway platform of any of claims 1-3, wherein the functional component comprises:
and the flow control component is used for judging whether the number of times of the access requests in the preset time period exceeds a threshold value, and if so, intercepting the newly received access requests.
6. The API gateway platform of any of claims 1-3, wherein the functional component comprises:
and the protocol conversion component is used for converting the access request according to the received access request.
7. The API gateway platform of any of claims 1-3, wherein the functional component comprises:
and the routing component is used for routing the converted access request to the corresponding back-end micro service node.
8. The API gateway platform of claim 7, wherein the functional components comprise:
and the overtime fusing component is used for preventing external access requests in a fusing mode when all back-end micro service nodes are in a busy state.
9. The API gateway platform of any of claims 1-3, wherein the functional component comprises:
and the data cache component is used for judging whether the called API has a set cache after receiving the access request, and if so, directly extracting data from the cache and returning the data to the terminal user.
10. The API gateway platform of claim 3, wherein the number of gateway devices is plural, and the API gateway platform is a distributed API gateway platform; furthermore, it is possible to provide a liquid crystal display device,
the management center is used for sending an updating message to each gateway device in the cluster after receiving the setting information;
and the gateway device is used for refreshing the corresponding functional component when receiving the updating message.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011436226.8A CN112769687A (en) | 2020-12-10 | 2020-12-10 | API gateway platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011436226.8A CN112769687A (en) | 2020-12-10 | 2020-12-10 | API gateway platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112769687A true CN112769687A (en) | 2021-05-07 |
Family
ID=75693476
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011436226.8A Pending CN112769687A (en) | 2020-12-10 | 2020-12-10 | API gateway platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112769687A (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113381942A (en) * | 2021-06-04 | 2021-09-10 | 深圳市智慧空间平台技术开发有限公司 | Method for realizing interface gateway |
| CN113726566A (en) * | 2021-08-25 | 2021-11-30 | 杭州数政科技有限公司 | Service gateway device |
| CN113765701A (en) * | 2021-08-02 | 2021-12-07 | 中企云链（北京）金融信息服务有限公司 | Gateway control method based on permanent memory cache |
| CN113923200A (en) * | 2021-10-12 | 2022-01-11 | 上海中通吉网络技术有限公司 | Method and device for realizing massive API gateway service |
| CN114978936A (en) * | 2022-05-24 | 2022-08-30 | 身边云(北京)信息服务有限公司 | Method, system and storage medium for upgrading shared service platform |
| CN115277863A (en) * | 2022-06-27 | 2022-11-01 | 中盈优创资讯科技有限公司 | Scheduling method of API (application program interface) route |
| CN116319811A (en) * | 2023-05-22 | 2023-06-23 | 来未来科技(浙江)有限公司 | Gateway routing system supporting multiprotocol conversion and service arrangement |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101616430A (en) * | 2009-07-28 | 2009-12-30 | 中兴通讯股份有限公司 | A kind of method and home gateway of managing family gateway software version |
| CN105844450A (en) * | 2011-12-08 | 2016-08-10 | 微软技术许可有限责任公司 | Techniques to manage remote events |
| CN109194760A (en) * | 2018-09-14 | 2019-01-11 | 深圳市佰仟金融服务有限公司 | Method for processing business, network system and server |
| CN109618347A (en) * | 2019-02-17 | 2019-04-12 | 中国—东盟信息港股份有限公司 | A kind of Intelligent gateway system of automation distribution service request |
| CN109672553A (en) * | 2018-10-23 | 2019-04-23 | 平安科技（深圳）有限公司 | Gateway Dynamic Configuration, system, computer equipment and storage medium |
| CN110417598A (en) * | 2019-07-30 | 2019-11-05 | 普信恒业科技发展（北京）有限公司 | The management method and component manager of gateway component |
-
2020
- 2020-12-10 CN CN202011436226.8A patent/CN112769687A/en active Pending
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101616430A (en) * | 2009-07-28 | 2009-12-30 | 中兴通讯股份有限公司 | A kind of method and home gateway of managing family gateway software version |
| CN105844450A (en) * | 2011-12-08 | 2016-08-10 | 微软技术许可有限责任公司 | Techniques to manage remote events |
| CN109194760A (en) * | 2018-09-14 | 2019-01-11 | 深圳市佰仟金融服务有限公司 | Method for processing business, network system and server |
| CN109672553A (en) * | 2018-10-23 | 2019-04-23 | 平安科技（深圳）有限公司 | Gateway Dynamic Configuration, system, computer equipment and storage medium |
| CN109618347A (en) * | 2019-02-17 | 2019-04-12 | 中国—东盟信息港股份有限公司 | A kind of Intelligent gateway system of automation distribution service request |
| CN110417598A (en) * | 2019-07-30 | 2019-11-05 | 普信恒业科技发展（北京）有限公司 | The management method and component manager of gateway component |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113381942A (en) * | 2021-06-04 | 2021-09-10 | 深圳市智慧空间平台技术开发有限公司 | Method for realizing interface gateway |
| CN113765701A (en) * | 2021-08-02 | 2021-12-07 | 中企云链（北京）金融信息服务有限公司 | Gateway control method based on permanent memory cache |
| CN113765701B (en) * | 2021-08-02 | 2024-02-20 | 中企云链（北京）金融信息服务有限公司 | Gateway control method based on permanent memory cache |
| CN113726566A (en) * | 2021-08-25 | 2021-11-30 | 杭州数政科技有限公司 | Service gateway device |
| CN113726566B (en) * | 2021-08-25 | 2024-03-26 | 杭州数政科技有限公司 | Service gateway device |
| CN113923200A (en) * | 2021-10-12 | 2022-01-11 | 上海中通吉网络技术有限公司 | Method and device for realizing massive API gateway service |
| CN114978936A (en) * | 2022-05-24 | 2022-08-30 | 身边云(北京)信息服务有限公司 | Method, system and storage medium for upgrading shared service platform |
| CN115277863A (en) * | 2022-06-27 | 2022-11-01 | 中盈优创资讯科技有限公司 | Scheduling method of API (application program interface) route |
| CN115277863B (en) * | 2022-06-27 | 2024-05-14 | 中盈优创资讯科技有限公司 | Scheduling method of API (application program interface) route |
| CN116319811A (en) * | 2023-05-22 | 2023-06-23 | 来未来科技(浙江)有限公司 | Gateway routing system supporting multiprotocol conversion and service arrangement |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112769687A (en) | API gateway platform | |
| US11632392B1 (en) | Distributed malware detection system and submission workflow thereof | |
| CN110971449A (en) | Service management and control system based on micro-service architecture | |
| CN111431740B (en) | Data transmission method, device, equipment and computer readable storage medium | |
| US10671721B1 (en) | Timeout management services | |
| US10785255B1 (en) | Cluster configuration within a scalable malware detection system | |
| US11303647B1 (en) | Synthetic request injection to disambiguate bypassed login events for cloud policy enforcement | |
| US11757944B2 (en) | Network intermediary with network request-response mechanism | |
| US8352998B1 (en) | Policy evaluation in controlled environment | |
| US11190550B1 (en) | Synthetic request injection to improve object security posture for cloud security enforcement | |
| US8239923B2 (en) | Controlling computer program extensions in a network device | |
| US10491632B1 (en) | Methods for reducing compliance violations in mobile application management environments and devices thereof | |
| US11831685B2 (en) | Application-specific data flow for synthetic request injection | |
| US11985168B2 (en) | Synthetic request injection for secure access service edge (SASE) cloud architecture | |
| US10601863B1 (en) | System and method for managing sensor enrollment | |
| CN112367321B (en) | Method for quickly constructing service call and middle station API gateway | |
| US11888902B2 (en) | Object metadata-based cloud policy enforcement using synthetic request injection | |
| US11336698B1 (en) | Synthetic request injection for cloud policy enforcement | |
| US11647052B2 (en) | Synthetic request injection to retrieve expired metadata for cloud policy enforcement | |
| US10798218B2 (en) | Environment isolation method and device | |
| CN112149105A (en) | Data processing system, method, related device and storage medium | |
| US11979384B2 (en) | Dynamic proxy response from application container | |
| CN113424157A (en) | Multi-dimensional periodic detection of IoT device behavior | |
| US20180131751A1 (en) | Distributed network diagnostics of enterprise devices utilizing device management | |
| CN111709023B (en) | Application isolation method and system based on trusted operating system |
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 | ||
| CB02 | Change of applicant information |
Address after: 518000 Room 201, building a, No. 1, Qianwan 1st Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (settled in Shenzhen Qianhai business secretary Co., Ltd.) Applicant after: Feisuanzhi Technology (Shenzhen) Co.,Ltd. Address before: 208e-10, port building, shipping center, No. 59, Linhai Avenue, Nanshan street, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong 518000 Applicant before: Qianhai feisuan Technology (Shenzhen) Co.,Ltd. |
|
| CB02 | Change of applicant information | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20210507 |
|
| RJ01 | Rejection of invention patent application after publication |