CN117555957A - Automatic adaptation and conversion method and system for API message format - Google Patents
Automatic adaptation and conversion method and system for API message format Download PDFInfo
- Publication number
- CN117555957A CN117555957A CN202410045232.2A CN202410045232A CN117555957A CN 117555957 A CN117555957 A CN 117555957A CN 202410045232 A CN202410045232 A CN 202410045232A CN 117555957 A CN117555957 A CN 117555957A
- Authority
- CN
- China
- Prior art keywords
- api
- format
- message
- original
- return message
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000006978 adaptation Effects 0.000 title claims abstract description 47
- 238000006243 chemical reaction Methods 0.000 title claims abstract description 45
- 238000013507 mapping Methods 0.000 claims abstract description 32
- 230000004044 response Effects 0.000 claims abstract description 18
- 238000004458 analytical method Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 5
- 239000002356 single layer Substances 0.000 claims description 3
- 238000012545 processing Methods 0.000 abstract description 3
- 238000004891 communication Methods 0.000 description 18
- 230000009466 transformation Effects 0.000 description 14
- 238000013519 translation Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 239000010410 layer Substances 0.000 description 3
- 238000010586 diagram Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000000007 visual effect Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 238000011426 transformation method Methods 0.000 description 1
Classifications
-
- 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
-
- 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)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
Abstract
The invention relates to the technical field of message processing, and provides an automatic adaptation and conversion method and system for an API message format, wherein the method comprises the following steps: constructing a built-in format library according to the API return message formats, and generating a corresponding mapping file for each return message format in the built-in format library; acquiring an interface resource of an original API through original API registration, calling the original API according to the acquired interface resource, and acquiring a return message of the original API; and matching the acquired return message of the original API with a built-in format library, and converting the successfully matched return message of the original API into a standard format message according to the corresponding mapping file. The automatic adaptation and conversion method and the system for the API message format can avoid the occurrence rate of registration errors of the API during registration, simultaneously avoid the problem that the message format is inconsistent with the actual returned message format, and improve the successful response rate of the API resource.
Description
Technical Field
The present invention relates to the field of message processing technologies, and in particular, to an API message format automatic adaptation and conversion method and system.
Background
The existing API resource registration tool needs to specify a fixed message format for each API, including an in-parameter and an out-parameter, especially the data format of the return message. And the format of the message that the API calls into and back from must be consistent with the format specified at registration, otherwise the API interface will fail when called. In most cases, the entry of the API interface is fixed, but the return message may change, especially the data body (data content part) in the return message, where the data body changes according to the data processing situation of the API interface back-end service, where the situation often occurs in the API opened by the data management tool such as the data center. When such an actual return message does not conform to the return message format configured at registration, the call and parsing of the API may be abnormal and cause call failure. At present, the existing API resource registration tool cannot adapt and convert the actual returned message of the API interface when the API interface is called, most of the current API call abnormality is caused by the inconsistency between the format of the returned message and the configuration when the API call is registered, and the situation is a difficult problem which cannot be solved by the existing API registration tool.
Therefore, how to provide an API message format adapting and converting method, avoiding the failure of calling an API interface, becomes a technical problem to be solved urgently.
Disclosure of Invention
In view of the above, the present invention aims to overcome the shortcomings of the prior art, and provide a method and a system for automatically adapting and converting an API message format.
According to a first aspect of the present invention, there is provided an automatic adaptation and conversion method for API message format, comprising:
constructing a built-in format library according to the API return message formats, and generating a corresponding mapping file for each return message format in the built-in format library;
acquiring an interface resource of an original API through original API registration, calling the original API according to the acquired interface resource, and acquiring a return message of the original API;
and matching the acquired return message of the original API with a built-in format library, and converting the successfully matched return message of the original API into a standard format message according to the corresponding mapping file.
Preferably, in the method for automatically adapting and converting an API message format of the present invention, generating a corresponding mapping file for each returned message format in a built-in format library includes: and configuring corresponding analysis conversion rules for each returned message format in the built-in format library, and generating a corresponding mapping file according to each configured analysis conversion rule.
Preferably, in the method for automatically adapting and converting an API message format of the present invention, obtaining an interface resource of an original API through original API registration, calling the original API according to the obtained interface resource, and obtaining a return message of the original API, including:
registering an original API, and configuring front-end request information and back-end service response information for the original API, wherein the front-end request information comprises a front-end request address, a front-end request protocol and front-end request parameters, and the back-end service response information comprises a back-end service address, a back-end service path, a back-end service request method and back-end service request parameters;
calling the original API according to the configured front-end request information, and acquiring a return message of the original API according to the configured back-end service response information.
Preferably, in the method for automatically adapting and converting an API message format of the present invention, calling the original API according to the configured front-end request information includes: and creating an API call request according to the front-end request address and the front-end request protocol, and calling the original API by a front-end request parameter transmitted into the created API call request.
Preferably, in the method for automatically adapting and converting an API message format of the present invention, the obtaining, according to the configured back-end service response information, a return message of the original API includes: and calling a back-end service address and a back-end service path in back-end service response information of the original API, and acquiring a return message of the original API according to a designated parameter value in a back-end service request parameter transmitted by a back-end service request method.
Preferably, in the automatic adapting and converting method of API message format of the present invention, the matching is performed between the obtained return message of the original API and the built-in format library, and the successfully matched return message of the original API is converted into the standard format message according to the corresponding mapping file, including: and matching the acquired return message of the original API with the return message in the built-in format library, and when the acquired return message of the original API is successfully matched with the built-in format library, analyzing the return message of the original API according to the corresponding mapping file, and recombining the analyzed return message according to the mapping relation in the mapping file to acquire the standard format message.
Preferably, in the automatic adaptation and conversion method of the format of the API message, the standard format message adopts a non-nested single-layer key value pair format and the data node is used for identifying the start and stop content.
Preferably, the method for automatically adapting and converting the format of the API message of the present invention further includes: when the obtained return message of the original API fails to match with the built-in format library, the data body in the return message of the original API is returned to the calling party in the form of a large character string.
According to a second aspect of the present invention, an automatic adaptation and conversion system for an API message format is provided, including an adaptation and conversion server, configured to construct a built-in format library according to an API return message format, and configure a corresponding parsing conversion rule for each return message in the built-in format library; acquiring an interface resource of an original API through original API registration, calling the original API according to the acquired interface resource, and acquiring a return message of the original API; and matching the acquired return message of the original API with a built-in format library, and converting the successfully matched return message of the original API into a standard format message according to an analysis conversion rule.
According to a third aspect of the present invention there is provided a computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of the first aspect of the present invention when executing the program.
According to the method and the system for automatically adapting and converting the API message format, the return message format is built in the built-in format library in advance according to the application scene, the corresponding analysis and conversion rule is configured for the built-in return message format, the corresponding mapping file is generated, registration errors caused by configuration of the return message format and the conversion rule when the API is registered are avoided, meanwhile, the problem that the message format is inconsistent with the actual return message format when the API is registered is also avoided, and the successful response rate of the API resource is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings that are needed in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a system for an automatic adaptation and conversion method for an API message format in accordance with an embodiment of the present application;
FIG. 2 is a flowchart illustrating a method for automatically adapting and converting an API message format according to an embodiment of the present invention;
FIG. 3 is a flowchart illustrating an exemplary scenario for an API message format auto-adaptation and conversion method according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of the apparatus provided by the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
It should be noted that, without conflict, the following embodiments and features in the embodiments may be combined with each other; and, based on the embodiments in this disclosure, all other embodiments that may be made by one of ordinary skill in the art without inventive effort are within the scope of the present disclosure.
It is noted that various aspects of the embodiments are described below within the scope of the following claims. It should be apparent that the aspects described herein may be embodied in a wide variety of forms and that any specific structure and/or function described herein is merely illustrative. Based on the present disclosure, one skilled in the art will appreciate that one aspect described herein may be implemented independently of any other aspect, and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented and/or a method practiced using any number of the aspects set forth herein. In addition, such apparatus may be implemented and/or such methods practiced using other structure and/or functionality in addition to one or more of the aspects set forth herein.
Fig. 1 illustrates an exemplary system suitable for an API message format auto-adaptation and conversion method in accordance with an embodiment of the present application. As shown in fig. 1, the system may include an adaptation and conversion server 101, a communication network 102, and/or one or more adaptation and conversion clients 103, an example of which is a plurality of adaptation and conversion clients 103 in fig. 1.
The adaptation and transformation server 101 may be any suitable server for storing information, data, programs, and/or any other suitable type of content. In some embodiments, the adaptation and transformation server 101 may perform appropriate functions. For example, in some embodiments, the adaptation and transformation server 101 may be used for automatic adaptation and transformation of API message formats. As an alternative example, in some embodiments, the adaptation and transformation server 101 may be used to implement automatic adaptation and transformation of API message formats by building a built-in format library and generating a mapping file. For example, the adaptation and conversion server 101 may be configured to construct a built-in format library according to the API return message formats, and generate a corresponding mapping file for each return message format in the built-in format library; acquiring an interface resource of an original API through original API registration, calling the original API according to the acquired interface resource, and acquiring a return message of the original API; and matching the acquired return message of the original API with a built-in format library, and converting the successfully matched return message of the original API into a standard format message according to the corresponding mapping file.
As another example, in some embodiments, the adaptation and transformation server 101 may send the API message format automatic adaptation and transformation method to the adaptation and transformation client 103 for use by the user, upon request of the adaptation and transformation client 103.
As an alternative example, in some embodiments, the adaptation and conversion client 103 is configured to provide a visual interface, where the visual interface is configured to receive a selection input operation for automatically adapting and converting an API message format, and is configured to obtain, in response to the selection input operation, an interface corresponding to an option selected by the selection input operation from the adaptation and conversion server 101 and display the interface, where at least information for automatically adapting and converting the API message format and operation options for the information for automatically adapting and converting the API message format are displayed.
In some embodiments, communication network 102 may be any suitable combination of one or more wired and/or wireless networks. For example, the communication network 102 can include any one or more of the following: the internet, an intranet, a Wide Area Network (WAN), a Local Area Network (LAN), a wireless network, a Digital Subscriber Line (DSL) network, a frame relay network, an Asynchronous Transfer Mode (ATM) network, a Virtual Private Network (VPN), and/or any other suitable communication network. The adaptation and transformation client 103 is capable of being connected to the communication network 102 via one or more communication links (e.g., communication link 104), which communication network 102 is capable of being linked to the adaptation and transformation server 101 via one or more communication links (e.g., communication link 105). The communication link may be any communication link suitable for transferring data between the adaptation and translation client 103 and the adaptation and translation server 101, such as a network link, a dial-up link, a wireless link, a hard-wired link, any other suitable communication link, or any suitable combination of such links.
Adaptation and translation clients 103 may include any one or more clients that present interfaces related to automatic adaptation and translation of API message formats in an appropriate form for use and operation by a user. In some embodiments, the adaptation and transformation client 103 may comprise any suitable type of device. For example, in some embodiments, the adaptation and transformation client 103 may comprise a mobile device, a tablet computer, a laptop computer, a desktop computer, and/or any other suitable type of client device.
Although the adaptation and translation server 101 is illustrated as one device, in some embodiments any suitable number of devices may be used to perform the functions performed by the adaptation and translation server 101. For example, in some embodiments, multiple devices may be used to implement the functions performed by the adaptation and transformation server 101. Alternatively, the functions of the adaptation and conversion server 101 may be implemented using cloud services.
Based on the above system, the embodiments of the present application provide an automatic adaptation and conversion method for API message formats, which is described in the following embodiments.
Referring to fig. 2, a flowchart illustrating steps of an API message format auto-adaptation and conversion method according to an embodiment of the present application is shown.
The automatic adaptation and conversion method for the API message format of the present embodiment may be executed at an adaptation and conversion server, and includes the following steps:
step S201: and constructing a built-in format library according to the API return message formats, and generating a corresponding mapping file for each return message format in the built-in format library.
As an example, the embodiment adds the corresponding API return message format to the built-in format library according to the requirements of the application scenario, where the built-in format library is the target format library for matching the subsequent return file format.
After the built-in format library is built, the embodiment also needs to stretch out the corresponding mapping file for each returned message format in the built-in format library. Optionally, in this embodiment, a corresponding parsing conversion rule is configured for each return message format in the built-in format library, and a corresponding mapping file is generated according to each configured parsing conversion rule, where the mapping file generated by the method in this embodiment is used to ensure that all the return messages can be converted into a unified standard format message.
Step S202: the method comprises the steps of acquiring interface resources of an original API through original API registration, calling the original API according to the acquired interface resources, and acquiring a return message of the original API.
As an example, the method of this embodiment obtains the interface resource of the original API as follows: registering an original API, and configuring front-end request information and back-end service response information for the original API, wherein the front-end request information comprises a front-end request address, a front-end request protocol and front-end request parameters, and the back-end service response information comprises a back-end service address, a back-end service path, a back-end service request method and back-end service request parameters.
After the original API registration and the acquisition of the interface resources of the original API are completed, the embodiment also needs to call the original API according to the configured front-end request information, and acquire the return message of the original API according to the configured back-end service response information. For example, in this embodiment, an API call request is created according to a front end request address and a front end request protocol, and the original API is called by an incoming front end request parameter in the created API call request; after calling an original API, the embodiment calls a back-end service address and a back-end service path in back-end service response information of the original API, and obtains a return message of the original API according to a designated parameter value in a back-end service request parameter transmitted by a back-end service request method.
Step S203: and matching the acquired return message of the original API with a built-in format library, and converting the successfully matched return message of the original API into a standard format message according to the corresponding mapping file.
Because the actual message is in a non-standard format, the method of the embodiment needs to analyze and reorganize the non-standard return message, and convert the non-standard return message into a message in a standard format. As an example, the method of this embodiment matches the obtained return message of the original API with the return message in the built-in format library, and when the obtained return message of the original API is successfully matched with the built-in format library, parses the return message of the original API according to the corresponding mapping file, and reassembles the parsed return message according to the mapping relation in the mapping file, so as to obtain the standard format message. For example, the embodiment can split the content behind the data node in the actual return message layer by layer until the content reaches the form of the key value pair (for example, "name" to "Zhang three") at the bottom layer, and then place the key value pairs into the data root node according to the standard format specified in the mapping file, so as to parse and reorganize the return message. It should be noted that, when the person skilled in the art parses and reassembles the return message according to the method of the embodiment, the person skilled in the art may also select a suitable manner to parse and reassemble the return message according to a specific application scenario, which is not limited in this embodiment. The standard format message obtained by the method of the embodiment adopts a non-nested single-layer key value pair format and uses the data node to identify the start and stop content.
In the method of this embodiment, the following steps are performed. When the obtained return message of the original API fails to match with the built-in format library, the data body in the return message of the original API is returned to the calling party in the form of a large character string.
The method for automatically adapting and converting the API message format of the present embodiment is described in detail below in an exemplary scenario. Referring to fig. 3, in order to solve the problem that the format of the API resource return message is uncertain, the method for automatically adapting and converting the API message format according to the embodiment is implemented in the following manner:
acquiring a return message of an original API through original API registration, carrying out message format identification and matching on the acquired return message, and converting the return message into a standard format message according to a corresponding analysis conversion rule when the acquired return message is successfully matched with a built-in message format in a built-in format library; and when the acquired return message fails to be matched with the built-in message format in the built-in format, returning the data body in the return message of the original API to the calling party in the form of a large character string.
According to the method, the return message format can be built in the built-in format library in advance according to the application scene, corresponding analysis and conversion rules are configured for the built-in return message format, a corresponding mapping file is generated, registration errors caused by configuration of the return message format and the conversion rules when the API is registered are avoided, meanwhile, the problem that the message format is inconsistent with the actual return message format when the API is registered is avoided, and the successful response rate of the API resource is improved.
As shown in FIG. 4, the present invention also provides an apparatus comprising a processor 310, a communication interface 320, a memory 330 for storing a processor executable computer program, and a communication bus 340. Wherein the processor 310, the communication interface 320 and the memory 330 perform communication with each other through the communication bus 340. The processor 310 implements the API message format auto-adaptation and conversion method described above by running an executable computer program.
The computer program in the memory 330 may be implemented in the form of software functional units and may be stored in a computer-readable storage medium when sold or used as a separate product. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The system embodiments described above are merely illustrative, in which elements illustrated as separate elements may or may not be physically separate, and elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected based on actual needs to achieve the purpose of the embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by means of software plus necessary general hardware platforms, or of course may be implemented by means of hardware. Based on such understanding, the foregoing technical solutions may be embodied essentially or in part in the form of a software product, which may be stored in a computer-readable storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to perform the various embodiments or methods of some parts of the embodiments.
The foregoing is merely illustrative of the present invention, and the present invention is not limited thereto, and any changes or substitutions easily contemplated by those skilled in the art within the scope of the present invention should be included in the present invention. Therefore, the protection scope of the invention is subject to the protection scope of the claims.
Claims (10)
1. An automatic adaptation and conversion method for an API message format, the method comprising:
constructing a built-in format library according to the API return message formats, and generating a corresponding mapping file for each return message format in the built-in format library;
acquiring an interface resource of an original API through original API registration, calling the original API according to the acquired interface resource, and acquiring a return message of the original API;
and matching the acquired return message of the original API with a built-in format library, and converting the successfully matched return message of the original API into a standard format message according to the corresponding mapping file.
2. The method for automatically adapting and converting an API message format according to claim 1, wherein generating a corresponding mapping file for each returned message format in a built-in format library comprises:
and configuring corresponding analysis conversion rules for each returned message format in the built-in format library, and generating a corresponding mapping file according to each configured analysis conversion rule.
3. The method for automatically adapting and converting an API message format according to claim 1, wherein obtaining an interface resource of an original API through an original API registration, calling the original API according to the obtained interface resource, and obtaining a return message of the original API, includes:
registering an original API, and configuring front-end request information and back-end service response information for the original API, wherein the front-end request information comprises a front-end request address, a front-end request protocol and front-end request parameters, and the back-end service response information comprises a back-end service address, a back-end service path, a back-end service request method and back-end service request parameters;
calling the original API according to the configured front-end request information, and acquiring a return message of the original API according to the configured back-end service response information.
4. The automatic adaptation and conversion method for API message format according to claim 3, characterized by calling said original API according to configured front-end request information, comprising:
and creating an API call request according to the front-end request address and the front-end request protocol, and calling the original API by a front-end request parameter transmitted into the created API call request.
5. The method for automatically adapting and converting an API message format according to claim 3, wherein obtaining a return message of said original API according to configured back-end service response information includes:
and calling a back-end service address and a back-end service path in back-end service response information of the original API, and acquiring a return message of the original API according to a designated parameter value in a back-end service request parameter transmitted by a back-end service request method.
6. The automatic adaptation and conversion method of API message format according to claim 1, wherein matching the obtained return message of the original API with the built-in format library, and converting the successfully matched return message of the original API into a standard format message according to the corresponding mapping file, includes:
and matching the acquired return message of the original API with the return message in the built-in format library, and when the acquired return message of the original API is successfully matched with the built-in format library, analyzing the return message of the original API according to the corresponding mapping file, and recombining the analyzed return message according to the mapping relation in the mapping file to acquire the standard format message.
7. The method for automatically adapting and converting the format of an API message according to claim 1, wherein the standard format message is formatted in a non-nested single-layer key-value pair format and the start-stop content is identified by the data node.
8. The method for automatically adapting and converting an API message format as recited in claim 1, further comprising: when the obtained return message of the original API fails to match with the built-in format library, the data body in the return message of the original API is returned to the calling party in the form of a large character string.
9. An automatic adaptation and conversion system for an API message format is characterized by comprising an adaptation and conversion server, wherein the adaptation and conversion server is used for constructing a built-in format library according to an API return message format and configuring corresponding analysis conversion rules for each return message in the built-in format library; acquiring an interface resource of an original API through original API registration, calling the original API according to the acquired interface resource, and acquiring a return message of the original API; and matching the acquired return message of the original API with a built-in format library, and converting the successfully matched return message of the original API into a standard format message according to an analysis conversion rule.
10. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the method of any of claims 1-8 when executing the program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410045232.2A CN117555957A (en) | 2024-01-12 | 2024-01-12 | Automatic adaptation and conversion method and system for API message format |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202410045232.2A CN117555957A (en) | 2024-01-12 | 2024-01-12 | Automatic adaptation and conversion method and system for API message format |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117555957A true CN117555957A (en) | 2024-02-13 |
Family
ID=89823689
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202410045232.2A Pending CN117555957A (en) | 2024-01-12 | 2024-01-12 | Automatic adaptation and conversion method and system for API message format |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117555957A (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546442A (en) * | 2012-03-09 | 2012-07-04 | 北京神州数码思特奇信息技术股份有限公司 | Communication protocol conversion technology |
| CN108667866A (en) * | 2017-03-29 | 2018-10-16 | 贵州白山云科技有限公司 | A kind of request processing method and device based on API intelligent adaptations |
| CN109951430A (en) * | 2017-12-21 | 2019-06-28 | 中移（杭州）信息技术有限公司 | A kind of data processing method and device |
| CN110266592A (en) * | 2019-06-21 | 2019-09-20 | Ut斯达康通讯有限公司 | The communication means and device of SRV6 network and IP MPLS network |
| CN110866169A (en) * | 2019-09-30 | 2020-03-06 | 北京瑞航核心科技有限公司 | Learning-based Internet of things entity message analysis method |
| CN111143094A (en) * | 2020-01-02 | 2020-05-12 | 上海卓易科技股份有限公司 | Information flow aggregation system and control method thereof |
| US10887415B1 (en) * | 2018-05-09 | 2021-01-05 | Architecture Technology Corporation | Common agnostic data exchange systems and methods |
| CN113190513A (en) * | 2021-05-14 | 2021-07-30 | 广联达科技股份有限公司 | Data integration system and method |
| CN116112557A (en) * | 2023-04-12 | 2023-05-12 | 万联易达物流科技有限公司 | Method and system for adapting multiple message formats based on determined data |
| CN117278622A (en) * | 2023-08-28 | 2023-12-22 | 招商银行股份有限公司 | Message format conversion method and device, terminal equipment and storage medium |
-
2024
- 2024-01-12 CN CN202410045232.2A patent/CN117555957A/en active Pending
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102546442A (en) * | 2012-03-09 | 2012-07-04 | 北京神州数码思特奇信息技术股份有限公司 | Communication protocol conversion technology |
| CN108667866A (en) * | 2017-03-29 | 2018-10-16 | 贵州白山云科技有限公司 | A kind of request processing method and device based on API intelligent adaptations |
| CN109951430A (en) * | 2017-12-21 | 2019-06-28 | 中移（杭州）信息技术有限公司 | A kind of data processing method and device |
| US10887415B1 (en) * | 2018-05-09 | 2021-01-05 | Architecture Technology Corporation | Common agnostic data exchange systems and methods |
| CN110266592A (en) * | 2019-06-21 | 2019-09-20 | Ut斯达康通讯有限公司 | The communication means and device of SRV6 network and IP MPLS network |
| CN110866169A (en) * | 2019-09-30 | 2020-03-06 | 北京瑞航核心科技有限公司 | Learning-based Internet of things entity message analysis method |
| CN111143094A (en) * | 2020-01-02 | 2020-05-12 | 上海卓易科技股份有限公司 | Information flow aggregation system and control method thereof |
| CN113190513A (en) * | 2021-05-14 | 2021-07-30 | 广联达科技股份有限公司 | Data integration system and method |
| CN116112557A (en) * | 2023-04-12 | 2023-05-12 | 万联易达物流科技有限公司 | Method and system for adapting multiple message formats based on determined data |
| CN117278622A (en) * | 2023-08-28 | 2023-12-22 | 招商银行股份有限公司 | Message format conversion method and device, terminal equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3748908B1 (en) | Method, system, network device, storage medium for creating a network slice | |
| US11425047B2 (en) | Traffic analysis method, common service traffic attribution method, and corresponding computer system | |
| US11395189B2 (en) | State machine handling at a proxy node in an Ethernet-based fronthaul network | |
| US20200327045A1 (en) | Test System and Test Method | |
| EP2863582B1 (en) | Scheduling a device batch reconfiguration event in a network | |
| US10693706B2 (en) | Method and apparatus of performing simultaneous multi-agent access for command execution through a single client | |
| CN102571947A (en) | Processing method proxy method, device and system | |
| US20220171011A1 (en) | Positioning method and device, server, storage medium and terminal | |
| CN100417088C (en) | Method for synchronization of fore-and-aft alarm | |
| CN112073923A (en) | Communication method, device, gateway and readable storage medium compatible with multiple operators | |
| CN110474814B (en) | Power local area network fault diagnosis method and device | |
| CN107517248B (en) | Network connection method and device based on SDK | |
| EP3018883B1 (en) | Login method and system for client unit | |
| CN113132218A (en) | Home gateway access method, device, system processor and storage medium | |
| CN117555957A (en) | Automatic adaptation and conversion method and system for API message format | |
| CN112202795A (en) | Data processing method, gateway equipment and medium | |
| CN115617611A (en) | Generation method and device of signaling flow chart, electronic equipment and storage medium | |
| CN115567604A (en) | Service calling method based on micro-service system and server | |
| CN111200512B (en) | Network connection disaster recovery method, terminal equipment, storage medium and electronic equipment | |
| US20150149606A1 (en) | Managed object manipulation | |
| CN110225507B (en) | Cell locking method for terminal equipment and terminal equipment | |
| CN117615043B (en) | Inter-service communication method and system on edge gateway | |
| CN114356371A (en) | Data processing method and device for system configuration | |
| CN117424887A (en) | Error code uploading method, system, terminal and storage medium | |
| CN110647411A (en) | Service request 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 |