CN111064722B - Data sharing method for realizing protocol conversion of set in API mode - Google Patents
Data sharing method for realizing protocol conversion of set in API mode Download PDFInfo
- Publication number
- CN111064722B CN111064722B CN201911274971.4A CN201911274971A CN111064722B CN 111064722 B CN111064722 B CN 111064722B CN 201911274971 A CN201911274971 A CN 201911274971A CN 111064722 B CN111064722 B CN 111064722B
- Authority
- CN
- China
- Prior art keywords
- service
- api
- format
- plug
- conversion
- 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
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/252—Integrating or interfacing systems involving database management systems between a Database Management System and a front-end application
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- 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/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to a data sharing method for realizing protocol conversion by an API mode, which comprises the following steps: API service input; wherein, the input mode includes at least: rapidly importing RESTful through a Swagger document, or rapidly importing WebService through a WSDL document, or manually inputting API service; determining the type of the service to which the input API service belongs, and converting the format of the corresponding API service interface information from a second format which is not the first format into the first format; wherein the first format is RESTful format, and the second format is a format other than the first format; performing service joint debugging on the API service after interface information format conversion to ensure that the service is normally called after formal release; the service joint debugging mode at least comprises a correlation plug-in and a custom agent address; and after the service joint debugging, performing joint debugging test, and after the test is passed, performing service release. By the method and the device, the data sharing and integration problems of the cross-platform heterogeneous application system can be solved, and the requirements of users on data interaction and cooperative work of all departments can be met.
Description
Technical Field
The present invention relates to the field of data processing technologies, and in particular, to a data sharing method for implementing set protocol conversion in an API manner.
Background
The application of the big data technology is just started, and due attention is not paid yet in the practical application level. Some basic works are weak, and information barriers exist between departments and between areas. While big data involves complex data from different sources. In the absence of proper data governance, it is difficult to properly integrate data. Therefore, the unique function of the big data technology is played by opening information islands among departments and realizing the sharing and fusion of information resources.
In the current society, mass data are produced every day, but due to historical reasons, the data are difficult to collect due to different use types and different versions of databases. Meanwhile, users worry about problems of data confidentiality, data tamper resistance, network security and the like, and data acquisition is difficult and operation procedures are complicated. How to use the data properly is a problem that is annoying to many users.
If the method is carried out in the API mode, a complete API interface is provided for data sharing, users can share open data or services quickly with low cost and low risk only by simple operation, and the service capability intercommunication of cross-system and cross-protocol among a plurality of systems can be realized. The system is shared and opened in the form of API, unified management and organization are carried out on the service API, and fusion, remodeling and innovation of business capability between departments and areas are realized around the API. An API should be the best solution for data sharing, whether technically, commercially, or at the legal level, at present.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a data sharing method for implementing set protocol conversion in an API manner, aiming at the above-mentioned defects of the prior art.
The technical scheme adopted by the invention for solving the technical problems is as follows: a data sharing method for realizing set protocol conversion in an API mode is constructed, and the method comprises the following steps: API service input; wherein, the input mode at least includes: rapidly importing RESTful through a Swagger document, or rapidly importing WebService through a WSDL document, or manually inputting API service; determining the type of the input API service, and converting the interface information format of the corresponding API service from a second format which is not the first format into the first format; wherein the first format is a RESTful format, and the second format is a format other than the first format; performing service joint debugging on the API service after interface information format conversion to ensure that the service is normally called after formal release; the service joint debugging mode at least comprises a correlation plug-in and a custom agent address; and after the service joint debugging, performing joint debugging test, and after the test is passed, performing service release.
In the data sharing method for realizing set protocol conversion in the API mode, the service types of the API service comprise RESTful reverse proxy, webService-to-RESTful, data table-to-service and HTTP custom service;
when format conversion is carried out on the RESTful reverse proxy type API service, extracting a service name, a service description, a calling threshold value and overtime, selecting a proxy verification type and a downlink verification mode, and completing conversion after filling;
when the format conversion is carried out on the API service of the WebService to RESTful type, extracting a service name, a service description, a calling threshold value and overtime, selecting an agent verification type, filling in a WSDL URL, and completing the conversion after filling;
when the format conversion is carried out on the API service of the data table conversion service type, an RESTful API function is automatically generated according to data metadata information of a mainstream relational database, and the database of three types of MySQL, oracle and PostgreSQL is supported;
when the format conversion is carried out on the API service of the HTTP custom type, the service name, the service description, the calling threshold value and the overtime are extracted, the proxy verification type and the downlink verification mode are selected, and the conversion is completed after the proxy verification type and the downlink verification mode are filled.
The data sharing method for realizing the set protocol conversion in the API mode further comprises the step of auditing the input API service so as to determine whether the input API service meets the requirements.
In the data sharing method for realizing set protocol conversion in the API mode, in the step of service joint debugging, if a plug-in is associated, the plug-in is selected from a plug-in list, and interception parameter descriptions of an incoming direction and an outgoing direction are filled; and if the self-defined proxy address is carried out, filling the self-defined proxy address, releasing the service and starting the service joint debugging.
In the data sharing method for realizing protocol conversion by the API, the plug-in is a means for realizing the prepositive interception and the postpositive interception of the API service when the plug-in is associated, and the prepositive interception stage is used for operating the message before sending, including encryption, authentication and special field processing; the post interception stage is used for operating the received message, including decryption and desensitization of sensitive fields; through two listening processes, multiple scenes can be flexibly adapted.
In the data sharing method for implementing set protocol conversion in an API manner according to the present invention, the step of plug-in development includes:
downloading a template: downloading a plug-in template and making environment preparation work for plug-in development; wherein, the template is a maven project;
plug-in development: plug-in developers use development tools to program plug-ins according to requirements; wherein, the development tool types comprise Eclipse, intellij and IDEA;
plug-in deployment: uploading a kar packet generated by development and deploying the packet to a corresponding gateway;
the plug-in unit is used: associating corresponding plug-ins when entering the service;
and (3) plug-in test: and verifying whether the function of the plug-in is correct or not through the online test of the platform.
In the data sharing method for realizing set protocol conversion in the API mode, the calling conditions of the API service are displayed from different dimensions in the step of service issuing, including the issued service number, the issued application number, the total times of service calling and the times of success and failure, and API service calling track analysis is carried out.
Different from the prior art, the data sharing method for realizing protocol conversion by using the API mode provided by the invention comprises the following steps: API service input; wherein, the input mode at least includes: rapidly importing RESTful through a Swagger document, or rapidly importing WebService through a WSDL document, or manually inputting API service; determining the type of the service to which the input API service belongs, and converting the interface information format of the corresponding API service from a second format which is not the first format into the first format; wherein the first format is RESTful format, and the second format is a format other than the first format; performing service joint debugging on the API service after interface information format conversion to ensure that the service is normally called after formal release; the service joint debugging mode at least comprises a correlation plug-in and a custom proxy address; and after the service joint debugging, performing joint debugging test, and after the test is passed, performing service release. By the method and the device, the data sharing and integration problems of the cross-platform heterogeneous application system can be solved, and the requirements of users on data interaction and cooperative work of all departments can be met.
Drawings
The invention will be further described with reference to the accompanying drawings and examples, in which:
fig. 1 is a schematic flowchart of a data sharing method for implementing set protocol conversion in an API manner according to the present invention.
FIG. 2 is a logic diagram of an associated plug-in for implementing a data sharing method for set protocol conversion in an API manner according to the present invention.
Detailed Description
For a more clear understanding of the technical features, objects and effects of the present invention, embodiments of the present invention will now be described in detail with reference to the accompanying drawings.
As shown in fig. 1, a data sharing method for implementing set protocol conversion in an API manner according to the present invention includes the steps of:
s110: API service input; wherein, the input mode includes at least: and rapidly importing RESTful through a Swagger document, or rapidly importing WebService through a WSDL document, or manually inputting API service.
S120: determining the type of the service to which the input API service belongs, and converting the interface information format of the corresponding API service from a second format which is not the first format into the first format; wherein the first format is a RESTful format and the second format is a format other than the first format.
S130: performing service joint debugging on the API service after interface information format conversion to ensure that the service is normally called after formal release; the service joint debugging mode at least comprises a relevant plug-in and a custom agent address.
S140: and after the service joint debugging, performing joint debugging test, and after the test is passed, performing service release.
In the data sharing method for realizing set protocol conversion in the API mode, the service types of the API service comprise RESTful reverse proxy, webService-to-RESTful, data table-to-service and HTTP custom service;
when format conversion is carried out on the RESTful reverse proxy type API service, extracting a service name, a service description, a calling threshold value and overtime, selecting a proxy verification type and a downlink verification mode, and completing conversion after filling;
when the WebService converts the format of the RESTful API service, extracting the service name, the service description, the calling threshold value and the overtime, selecting the proxy verification type, filling in the WSDL URL, and completing the conversion after filling in;
when the format conversion is carried out on the API service of the data table conversion service type, an RESTful API function is automatically generated according to data element information of a mainstream relational database, and three types of databases of MySQL, oracle and PostgreSQL are supported;
when the format conversion is carried out on the API service of the HTTP custom type, the service name, the service description, the calling threshold value and the overtime are extracted, the proxy verification type and the downlink verification mode are selected, and the conversion is completed after the proxy verification type and the downlink verification mode are filled.
The data sharing method for realizing protocol conversion by the API also comprises a step of auditing the input API service so as to determine whether the input API service meets the requirement.
In the data sharing method for realizing the set protocol conversion in the API mode, in the step of service joint debugging, if a plug-in is associated, the plug-in is selected from a plug-in list, and interception parameter descriptions of an incoming direction and an outgoing direction are filled; and if the self-defined proxy address is carried out, filling the self-defined proxy address, releasing the service and starting the service joint debugging.
In the data sharing method for realizing protocol conversion by the API, the plug-in is a means for realizing the prepositive interception and the postpositive interception of the API service when the plug-in is associated, and the prepositive interception stage is used for operating the message before sending, including encryption, authentication and special field processing; the post interception stage is used for operating the received message, including decryption and desensitization of sensitive fields; through two listening processes, multiple scenes can be flexibly adapted. As shown in fig. 2.
In the data sharing method for implementing set protocol conversion in an API manner according to the present invention, the step of plug-in development includes:
downloading a template: downloading a plug-in template and making environment preparation work for plug-in development; wherein, the template is a maven project;
plug-in development: plug-in developers use development tools to program plug-ins according to requirements; wherein, the development tool types comprise Eclipse, intellij and IDEA;
plug-in deployment: uploading a kar packet generated by development and deploying the packet to a corresponding gateway;
the plug-in unit is used: associating corresponding plug-ins when entering the service;
and (3) plug-in test: and verifying whether the function of the plug-in is correct or not through the online test of the platform.
In the data sharing method for realizing set protocol conversion in the API mode, the calling conditions of the API service are displayed from different dimensions in the step of service issuing, including the issued service number, the issued application number, the total times of service calling and the times of success and failure, and API service calling track analysis is carried out.
The method is positioned as a lightweight API service bus, and focuses on performance, reliability, quick service access and quick application calling. The simple and easy-to-use B/S development platform is provided, the access of the service can be rapidly completed through the development platform, the service is presented in the form of a service directory after being input, and the subsequent service retrieval and subscription are facilitated. In order to simplify the complexity of calling the upper-layer application, RESTful API is uniformly used as an access protocol, and a user does not need to pay attention to the real protocol type of the background service and only needs to connect the next platform to realize the purpose of quickly developing the application program. The platform provides strong operation and maintenance and statistical analysis capability, and can provide data support for users from multiple dimensions.
The invention provides a data sharing platform with protocol conversion and service routing functions, provides a basic protocol conversion function, can access protocols including RESTful, soap, dubbo, JDBC and other popular protocols, and automatically converts to generate a RESTful interface after service entry. And provides a plug-in mechanism to assist in fulfilling some of the high level protocol conversion requirements. The plug-in mechanism supports hot loading, the API service bus service does not need to be restarted after the plug-in is deployed, and existing forwarding service cannot be influenced.
The API service bus has two interception stages in the forwarding process, wherein the preposed interception stage is used for carrying out some special operations on the message before sending, such as encryption, authentication, field special processing and the like; the post-interception stage can be used for performing some special operations on the received message, such as decryption, desensitization of sensitive fields and the like, and the two interception processes are adopted, so that a user can flexibly adapt to a plurality of scenes. The essence of the plug-in mechanism is the realization and registration of the two interception stages, and the user can realize the interception mechanism of the user through the plug-in so as to achieve the aim of adapting to the background service.
In the invention, the API is driven by the directory to exchange, the convergence of the API is provided in the form of a service directory, the API service issued by departments is displayed, other users can browse the API service according to the classification and the departments, and the search can also be carried out according to keywords, so that developers can conveniently and quickly obtain corresponding resources. The linkage of the service directory and the data sharing platform is supported, the exchange task is automatically generated according to the user requirements, the operation complexity is greatly reduced, and the usability is improved.
In the conventional exchange mode, if the exchange is performed in the API service mode, a data provider is required to develop a corresponding data API by itself, thereby bringing development cost. Through the data sharing platform, a user can automatically generate data API service only by specifying a data source and column information, an authentication mechanism is provided, and the labor cost is reduced.
Meanwhile, convenient API monitoring, alarming and analyzing functions are provided, a user can intuitively monitor calling conditions of API services, including time-consuming statistics, calling records and the like, calling track tracking and multidimensional analysis are provided periodically according to hours, days, months and years, and data support is provided for API optimization and redevelopment.
The invention takes the safety of the user service as a primary task and provides a plurality of effective mechanisms to ensure the safety of the user service. The data sharing platform provides indirect data access service externally in a RESTful API mode, the real address of the service is hidden, and the service opening risk is reduced; the service access identity authentication mechanism is provided, and the anti-counterfeiting and anti-replay functions are provided, so that illegal access to the service is prevented; a service application approval mechanism is provided to prevent unauthorized illegal access; and a service calling speed limiting mechanism is provided to resist high concurrent impact on the service.
The following detailed description illustrates:
during service development, scenes with special conversion requirements on an Http protocol, such as conversion from xml to json and field name conversion, are provided, the Http self-defining mode provides great flexibility for users, and the users can flexibly define Http conversion rules.
1. Planning transformation rules
The developer needs to have a plan before starting to enter the service, and must know clearly the transmission format of the real service, and the expected agent access mode.
Examples are: an Http service is used for adding students to a class, the original service performs data transmission in an xml mode, conversion is expected to be performed through a platform, the service is exposed in a json mode, and an API manual provided by the original service is as follows:
to meet the requirement, a developer first needs to clear the request parameters (including Http Query, http Header, http Body) of the original service, and then tries to plan the converted request parameters (including Http Query, http Header, http Body), which needs to ensure that information is not lost during the planning process, i.e., the parameters of the proxy interface can meet the original service requirement.
The planned API manuals are as follows:
2. defining proxy service interfaces
And inputting the proxy service interface according to a planned format through a page provided by the data sharing platform.
3. Defining Http request message conversion rules
The request message conversion rule is executed before the real service is called, and the platform repackages the request message according to the defined conversion rule (including Http Header, http Query, http Body).
The entry of the proxy service interface has in fact determined the conversion rules, where the system needs to be entered in the form of a configuration.
The conversion needs to be done according to the following rules:
the values of Http method, content-Type, accept-Type are all changed and fixed.
The Http Query parameter needs to be obtained from Http Body (json) in the request message, and the value thereof is variable.
The Http Body also needs to be obtained from Http Body (json) in the request message, and the value thereof is variable.
4. Defining Http response message conversion rule
The response message conversion rule is executed after the response message of the real service is received, and the platform repacks the response message according to the defined conversion rule, mainly the Http Body.
The Http Body needs to be obtained from Http Body (xml) in the response message, and the value thereof is variable.
Different from the prior art, the data sharing method for realizing protocol conversion by using the API mode provided by the invention comprises the following steps: API service input; wherein, the input mode at least includes: rapidly importing RESTful through a Swagger document, or rapidly importing WebService through a WSDL document, or manually inputting API service; determining the type of the service to which the input API service belongs, and converting the interface information format of the corresponding API service from a second format which is not the first format into the first format; wherein the first format is RESTful format, and the second format is a format other than the first format; performing service joint debugging on the API service after interface information format conversion to ensure that the service is normally called after formal release; the service joint debugging mode at least comprises a correlation plug-in and a custom agent address; and after the service joint debugging, performing joint debugging test, and after the test is passed, performing service release. By the method and the device, the data sharing and integration problems of the cross-platform heterogeneous application system can be solved, and the requirements of users on data interaction and cooperative work of all departments can be met.
While the present invention has been described with reference to the embodiments shown in the drawings, the present invention is not limited to the embodiments, which are illustrative and not restrictive, and it will be apparent to those skilled in the art that various changes and modifications can be made therein without departing from the spirit and scope of the invention as defined in the appended claims.
Claims (6)
1. A data sharing method for implementing set protocol conversion in an API manner, comprising the steps of:
API service input; wherein, the input mode at least includes: rapidly importing RESTful through a Swagger document, or rapidly importing WebService through a WSDL document, or manually inputting API service;
determining the type of the input API service, and converting the interface information format of the corresponding API service from a second format which is not the first format into the first format; wherein the first format is a RESTful format, and the second format is a format other than the first format;
performing service joint debugging on the API service after interface information format conversion to ensure that the service is normally called after formal release; the service joint debugging mode at least comprises a correlation plug-in and a custom agent address;
after the service joint debugging, performing joint debugging test, and after the test is passed, issuing the service;
the service types of the API service comprise RESTful reverse proxy, webService transfer RESTful, data form transfer service and HTTP custom service;
when format conversion is carried out on the RESTful reverse proxy type API service, extracting a service name, a service description, a calling threshold value and overtime, selecting a proxy verification type and a downlink verification mode, and completing conversion after filling;
when the WebService converts the format of the RESTful API service, extracting a service name, a service description, a calling threshold value and overtime, selecting an agent verification type, filling in a WSDL URL, and completing conversion after filling in;
when the format conversion is carried out on the API service of the data table conversion service type, an RESTful API function is automatically generated according to data metadata information of a mainstream relational database, and the database of three types of MySQL, oracle and PostgreSQL is supported;
when the format conversion is carried out on the API service of the HTTP custom type, the service name, the service description, the calling threshold value and the overtime are extracted, the proxy verification type and the downlink verification mode are selected, and the conversion is completed after the proxy verification type and the downlink verification mode are filled.
2. The data sharing method for API-style implementation of set protocol conversion according to claim 1, characterized in that it further comprises a step of auditing the entered API service to determine whether the entered API service meets the requirements after the step of API service entry.
3. The data sharing method for implementing set protocol conversion in API manner as claimed in claim 1, wherein in the step of performing service joint debugging, if a plug-in is associated, selecting a plug-in from a plug-in list, and filling in interception parameter descriptions of an incoming direction and an outgoing direction; and if the self-defined proxy address is carried out, filling the self-defined proxy address, releasing the service and starting the service joint debugging.
4. The method according to claim 3, wherein the plug-in is a means for implementing pre-interception and post-interception of API services when performing plug-in association, and the pre-interception stage is used to perform operations on the message before sending, including encryption, authentication, and special field processing; the post interception stage is used for operating the received message, including decryption and desensitization of sensitive fields; through two listening processes, multiple scenes can be flexibly adapted.
5. The method of claim 4, wherein the step of plug-in development comprises:
downloading a template: downloading a plug-in template and making environment preparation work for plug-in development; wherein, the template is a maven project;
plug-in development: plug-in developers use development tools to program plug-ins according to requirements; wherein, the development tool types comprise Eclipse, intellij and IDEA;
plug-in deployment: uploading a kar packet generated by development and deploying the packet to a corresponding gateway;
the plug-in unit is used: associating corresponding plug-ins when entering service;
and (3) plug-in test: and verifying whether the function of the plug-in is correct or not through the online test of the platform.
6. The data sharing method for realizing protocol conversion of a set in an API manner according to claim 1, wherein in the step of issuing the service, calling conditions of the API service are displayed from different dimensions, including the number of issued services, the number of issued applications, the total number of service calls and the number of successes and failures, and API service call trajectory analysis is performed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911274971.4A CN111064722B (en) | 2019-12-12 | 2019-12-12 | Data sharing method for realizing protocol conversion of set in API mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911274971.4A CN111064722B (en) | 2019-12-12 | 2019-12-12 | Data sharing method for realizing protocol conversion of set in API mode |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111064722A CN111064722A (en) | 2020-04-24 |
| CN111064722B true CN111064722B (en) | 2022-10-25 |
Family
ID=70298999
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911274971.4A Active CN111064722B (en) | 2019-12-12 | 2019-12-12 | Data sharing method for realizing protocol conversion of set in API mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111064722B (en) |
Families Citing this family (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111988171B (en) * | 2020-08-12 | 2022-05-17 | 北京大学 | Method, proxy server and system for calling SOAP Web service based on RESTful style request |
| CN112131017A (en) * | 2020-09-15 | 2020-12-25 | 北京值得买科技股份有限公司 | Interface design method for calendar service |
| CN111880839A (en) * | 2020-09-28 | 2020-11-03 | 珠海大横琴科技发展有限公司 | API processing method and device |
| CN113127081B (en) * | 2021-04-19 | 2023-09-15 | 浪潮金融信息技术有限公司 | Lightweight interactive method, system and medium for terminal |
| CN113596151A (en) * | 2021-07-28 | 2021-11-02 | 杭州数梦工场科技有限公司 | Plug-in management method and device, and data processing method and device |
| CN113938529A (en) * | 2021-08-30 | 2022-01-14 | 上海威派格智慧水务股份有限公司 | Multi-protocol conversion access system and method |
| CN113778492B (en) * | 2021-09-17 | 2023-11-10 | 中国移动通信集团陕西有限公司 | Method, device, equipment and storage medium for issuing capability API |
| CN116400986A (en) * | 2023-03-31 | 2023-07-07 | 杭州端点网络科技有限公司 | Device for unified data service of large data platform |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103839138A (en) * | 2014-03-08 | 2014-06-04 | 成都文昊科技有限公司 | System for supporting interaction of multiple heterogeneous systems |
| CN107948135A (en) * | 2017-10-31 | 2018-04-20 | 贵州白山云科技有限公司 | A kind of data processing method and device for supporting a variety of API protocols |
| CN107958052A (en) * | 2017-11-28 | 2018-04-24 | 广州启生信息技术有限公司 | A kind of access method and device of large scale network crawlers |
| CN108880887A (en) * | 2018-06-20 | 2018-11-23 | 山东大学 | Accompany and attend to robot cloud service system and method based on micro services |
| CN109460223A (en) * | 2018-11-14 | 2019-03-12 | 沈阳林科信息技术有限公司 | A kind of API gateway management system and its method |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103338206B (en) * | 2013-07-10 | 2017-06-27 | 中兴智能交通股份有限公司 | A kind of method and device that data exchange is realized based on data bus technology |
| US20180218368A1 (en) * | 2017-01-31 | 2018-08-02 | First Data Corporation | Data transformation engine |
| CN108429808B (en) * | 2018-03-13 | 2020-12-01 | 南京邮电大学 | Method and system for cross-platform resource interaction of Internet of things |
-
2019
- 2019-12-12 CN CN201911274971.4A patent/CN111064722B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103839138A (en) * | 2014-03-08 | 2014-06-04 | 成都文昊科技有限公司 | System for supporting interaction of multiple heterogeneous systems |
| CN107948135A (en) * | 2017-10-31 | 2018-04-20 | 贵州白山云科技有限公司 | A kind of data processing method and device for supporting a variety of API protocols |
| CN107958052A (en) * | 2017-11-28 | 2018-04-24 | 广州启生信息技术有限公司 | A kind of access method and device of large scale network crawlers |
| CN108880887A (en) * | 2018-06-20 | 2018-11-23 | 山东大学 | Accompany and attend to robot cloud service system and method based on micro services |
| CN109460223A (en) * | 2018-11-14 | 2019-03-12 | 沈阳林科信息技术有限公司 | A kind of API gateway management system and its method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111064722A (en) | 2020-04-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111064722B (en) | Data sharing method for realizing protocol conversion of set in API mode | |
| KR102514325B1 (en) | Model training system and method, storage medium | |
| JP2022000757A5 (en) | ||
| US6879979B2 (en) | Method to remotely query, safely measure, and securely communicate configuration information of a networked computational device | |
| CN112116438A (en) | Multi-channel payment integration method, platform, equipment and medium | |
| US5557742A (en) | Method and system for detecting intrusion into and misuse of a data processing system | |
| CN112632135A (en) | Big data platform | |
| US20200213331A1 (en) | Data service system | |
| CN110083391A (en) | Call request monitoring method, device, equipment and storage medium | |
| US20150169392A1 (en) | System and method for providing an application programming interface intermediary for hypertext transfer protocol web services | |
| CN101300546A (en) | Method and system for a programmable camera for configurable security and surveillance systems | |
| CN114329290B (en) | Capability open platform and authorized access method thereof | |
| CN112738138B (en) | Cloud security hosting method, device, equipment and storage medium | |
| CN109271807A (en) | The data safety processing method and system of database | |
| US20180316702A1 (en) | Detecting and mitigating leaked cloud authorization keys | |
| US11829411B2 (en) | Data recovery method and apparatus, electronic device, and storage medium | |
| CN112017007A (en) | User behavior data processing method and device, computer equipment and storage medium | |
| CN113947485A (en) | Block chain customizable system | |
| US11924284B1 (en) | Automated security, orchestration, automation, and response (SOAR) app generation based on application programming interface specification data | |
| CN116633725A (en) | All-channel access gateway | |
| CN116303713A (en) | Tropical crop germplasm resource tracing method based on blockchain and genomics | |
| Murínová | Application log analysis | |
| CN113094398B (en) | Data link tracking method based on block chain technology | |
| CN109412861B (en) | Method for establishing security association display of terminal network | |
| CN111324796A (en) | Domain name crawling method and device based on block chain and SDN edge computing network 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230802 Address after: 030006 Room 1803, No. 345 Changzhi Road, Taiyuan Xuefu Park, Comprehensive Reform Demonstration Zone, Taiyuan City, Shanxi Province Patentee after: Shanxi Cloud Era Government Cloud Technology Co.,Ltd. Address before: No. 345, Changzhi Road, Xuefu Park, Taiyuan City, Shanxi Province, 030000 Patentee before: Shanxi yunshidai Technology Co.,Ltd. |