WO2024041446A1 - 应用程序编程接口api间的参数适配方法及装置 - Google Patents

应用程序编程接口api间的参数适配方法及装置 Download PDF

Info

Publication number
WO2024041446A1
WO2024041446A1 PCT/CN2023/113574 CN2023113574W WO2024041446A1 WO 2024041446 A1 WO2024041446 A1 WO 2024041446A1 CN 2023113574 W CN2023113574 W CN 2023113574W WO 2024041446 A1 WO2024041446 A1 WO 2024041446A1
Authority
WO
WIPO (PCT)
Prior art keywords
api
parameter
parameters
function
adaptation
Prior art date
Application number
PCT/CN2023/113574
Other languages
English (en)
French (fr)
Inventor
陈然
杨鑫
蒲哲
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2024041446A1 publication Critical patent/WO2024041446A1/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/30—Creation or generation of source code
    • 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

Definitions

  • Embodiments of the present invention relate to the field of computer applications, and specifically to a method and device for parameter adaptation between application programming interfaces (APIs).
  • APIs application programming interfaces
  • API Application Programming Interface
  • orchestration refers to the business capabilities of each business component, using APIs as inseparable atomic services, arranging and combining execution sequences, and generating APIs with new service capabilities. Without prior agreement, the input and output parameters of different APIs often differ in structure and data content. Under the microservice architecture, each microservice component is developed independently by different teams, and this difference is further amplified. Between such heterogeneous APIs, API combination cannot be completed through simple connection relationships, and the interface parameters between APIs need to be adapted.
  • APIs in traditional industries involve professional industry knowledge.
  • software technology is relatively backward compared to the Internet software industry.
  • Technology iterations and updates are slow, and API heterogeneity is more obvious, forming a more complex API orchestration scenario. Parameter adaptation is more challenging.
  • Embodiments of the present invention provide a method and device for parameter adaptation between application programming interface APIs, so as to at least solve the problem in related technologies that parameter adaptation between APIs in complex orchestration scenarios cannot be solved easily and at low cost.
  • a parameter adaptation method between application programming interface APIs including: parsing the output parameters of the front-end API in API arrangement, putting the obtained output parameters into a parameter pool and passing them through Interface presentation; parsing the input parameters of the post-API in the API arrangement, and presenting the input parameters on the interface; selecting the target output that matches the input parameters of the post-API from the output parameters in the parameter pool parameters, or generate the target output parameters based on the output parameters, and map and associate the target output parameters with the input parameters of the post-API to realize the communication between the pre-API and the post-API.
  • Parameter adaptation including: parsing the output parameters of the front-end API in API arrangement, putting the obtained output parameters into a parameter pool and passing them through Interface presentation; parsing the input parameters of the post-API in the API arrangement, and presenting the input parameters on the interface; selecting the target output that matches the input parameters of the post-API from the output parameters in the parameter pool parameters, or generate the target output parameters based on the output parameters, and
  • an application programming interface parameter adaptation device including: a first parsing module configured to parse the output parameters of the pre-API in the API arrangement, and put the obtained output parameters into in the parameter pool and presented through the interface; the second parsing module is configured to parse the input parameters of the post-API in the API arrangement, and present the input parameters on the interface; the mapping adaptation module is configured to select from the parameter pool Select a target output parameter that matches the input parameter of the post-API from the output parameters, or generate the target output parameter based on the output parameter, and convert the The target output parameters are mapped and associated with the input parameters of the post-API to realize parameter adaptation between the pre-API and the post-API.
  • a computer-readable storage medium is also provided.
  • a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute any of the above methods when running. Steps in Examples.
  • an electronic device including a memory and a processor.
  • a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above. Steps in method embodiments.
  • Figure 1 is a hardware structure block diagram of a mobile terminal of a parameter adaptation method between APIs according to an embodiment of the present invention
  • Figure 2 is a flow chart of a parameter adaptation method between APIs according to an embodiment of the present invention
  • Figure 3 is a structural block diagram of a parameter adaptation device according to an embodiment of the present invention.
  • Figure 4 is a structural block diagram of a mapping adaptation module according to an embodiment of the present invention.
  • Figure 5 is a structural block diagram of a mapping adaptation module according to an embodiment of the present invention.
  • Figure 6 is a structural block diagram of a mapping adaptation module according to an embodiment of the present invention.
  • Figure 7 is a structural block diagram of a parameter adaptation device according to a scenario embodiment of the present invention.
  • Figure 8 is a schematic diagram of the display mode of available parameters according to a scenario embodiment of the present invention.
  • Figure 9 is a schematic diagram of parameter mapping relationships according to a scenario embodiment of the present invention.
  • Figure 10 is a schematic diagram of parameter mapping interface display according to a scenario embodiment of the present invention.
  • Figure 11 is a schematic diagram of built-in function conversion according to a scenario embodiment of the present invention.
  • Figure 12 is a schematic diagram of the built-in function processing interface display according to the scenario embodiment of the present invention.
  • Figure 13 is a schematic diagram of custom function conversion according to a scenario embodiment of the present invention.
  • Figure 14 is a schematic diagram of the custom function editing interface display according to the scenario embodiment of the present invention.
  • Figure 15 is a schematic diagram of the custom function processing interface display according to the scenario embodiment of the present invention.
  • Figure 16 is a schematic diagram of the customized function mapping interface display according to the scenario embodiment of the present invention.
  • Figure 17 is a schematic diagram of parameter mapping relationships according to a scenario embodiment of the present invention.
  • Figure 18 is a schematic diagram of a function processing interface display according to a scenario embodiment of the present invention.
  • Figure 19 is a flow chart for automatically recommending monthly rental packages according to a scenario embodiment of the present invention.
  • Figure 20 is a schematic diagram of interface parameter adaptation according to a scenario embodiment of the present invention.
  • Figure 21 is a schematic diagram of editing the minimum consumption analysis function according to the scenario embodiment of the present invention.
  • Figure 22 is a schematic diagram of editing the highest consumption analysis function according to the scenario embodiment of the present invention.
  • Figure 23 is a schematic diagram of the parameter adaptation interface according to the scenario embodiment of the present invention.
  • Figure 24 is a flow chart of automatic monthly assessment and evaluation of employees according to the scenario embodiment of the present invention.
  • Figure 25 is a schematic diagram of the custom assessment level calculation function interface according to the scenario embodiment of the present invention.
  • Figure 26 is a schematic diagram of the parameter mapping interface according to the scenario embodiment of the present invention.
  • Figure 27 is a schematic diagram of the splitting of the assessment level function according to the scenario embodiment of the present invention.
  • FIG. 1 is a hardware structure block diagram of a mobile terminal of a parameter adaptation method between APIs according to an embodiment of the present invention.
  • the mobile terminal may include one or more (only one is shown in Figure 1) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the above-mentioned mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions.
  • processors 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA
  • a memory 104 for storing data
  • the above-mentioned mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions.
  • the structure shown in Figure 1 is only illustrative, and it does not limit the structure of the above-mentioned mobile terminal.
  • the mobile terminal may also include more or fewer components than shown in FIG. 1 , or have a different configuration than shown in FIG. 1 .
  • the memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the parameter adaptation method between APIs in the embodiment of the present invention.
  • the processor 102 runs the computer program stored in the memory 104 , thereby executing various functional applications and data processing, that is, implementing the above method.
  • Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memory located remotely relative to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.
  • the transmission device 106 is used to receive or send data via a network.
  • Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal.
  • the transmission device 106 includes a network adapter (Network Interface Controller, NIC), which can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF) module, which is used to communicate with the Internet wirelessly.
  • RF Radio Frequency
  • FIG. 2 is a flow chart of a parameter adaptation method between APIs according to an embodiment of the present invention. As shown in Figure 2, the The process includes the following steps:
  • Step S202 parse the output parameters of the front-end API in the API arrangement, put the obtained output parameters into the parameter pool and present them through the interface;
  • Step S204 parse the input parameters of the post-API in the API arrangement, and present the input parameters on the interface
  • Step S206 Select a target output parameter that matches the input parameter of the post-API from the output parameters in the parameter pool, or generate a target output parameter based on the output parameter, and map the target output parameter to the input parameter of the post-API. Association to achieve parameter adaptation between the pre-API and the post-API.
  • the obtained output parameters are put into the parameter pool and presented through the interface; the input parameters of the post-API in API orchestration are parsed, and the input parameters are presented on the interface ; Select the target output parameters that match the input parameters of the post-API from the output parameters in the parameter pool, or generate the target output parameters based on the output parameters, and map and associate the target output parameters with the input parameters of the post-API,
  • generating the target output parameters based on the output parameters includes: using a built-in library function to perform function processing on the output parameters through an interface to generate the target output parameters.
  • the built-in library function before using the built-in library function to perform function processing on the output parameters to generate the target output parameters through the interface, it also includes: customizing the function logic through coding to generate a new function, and using the generated new function Stored as a built-in library function.
  • the target output parameters obtained by function processing of the built-in library function meet the parameter adaptation needs, there is no need to perform function processing with a custom function, that is, the current function can be judged before performing function processing. Can some built-in library functions meet the final parameter adaptation requirements? If so, there is no need to customize the function. If not, then customize the function. At the same time, if the steps of customizing the function are performed, the custom function will be used as a new function. Built-in library functions are stored together with the original built-in library functions to provide functions for subsequent parameter adaptation between APIs to continuously increase the number of built-in library functions, thereby reducing the number of custom functions and improving the efficiency of parameter adaptation.
  • mapping and associating the target output parameters with the input parameters of the post-API includes: mapping and associating the target output parameters with the input parameters of the post-API through a visual operation.
  • the method according to the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solutions of the embodiments of the present invention can be embodied in the form of software products in essence or in part that contribute to the existing technology.
  • the computer software products are stored in a storage medium (such as ROM/RAM, magnetic disc, optical disk), including several instructions to cause a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the embodiments of the present invention.
  • module may be a combination of software and/or hardware that implements a predetermined function.
  • apparatus described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
  • Figure 3 is a structural block diagram of a parameter adaptation device according to an embodiment of the present invention.
  • the parameter adaptation device 30 includes: a first parsing module 310, configured to parse the output parameters of the pre-API in API arrangement. , put the obtained output parameters into the parameter pool and present them through the interface; the second parsing module 320 is set to parse the input parameters of the post-API in the API arrangement, and present the input parameters on the interface; the mapping adaptation module 330 is set In order to select the target output parameters that are suitable for the input parameters of the post-API from the output parameters in the parameter pool, or generate the target output parameters based on the output parameters, and map and associate the target output parameters with the input parameters of the post-API, To achieve parameter adaptation between the pre-API and the post-API.
  • Figure 4 is a structural block diagram of a mapping adaptation module according to an embodiment of the present invention.
  • the mapping adaptation module 330 includes: a built-in function unit 410, which is configured to adopt Built-in library functions perform functional processing on output parameters to generate target output parameters.
  • Figure 5 is a structural block diagram of a mapping adaptation module according to an embodiment of the present invention.
  • the mapping adaptation module 330 also includes: customization
  • the function unit 510 is configured to customize the function logic through coding to generate a new function, and store the generated new function as a built-in library function.
  • Figure 6 is a structural block diagram of a mapping adaptation module according to an embodiment of the present invention.
  • the mapping adaptation module 330 also includes: a mapping unit 610, set to map and associate the target output parameters with the input parameters of the post-API through visual operations.
  • each of the above modules and units can be implemented through software or hardware. For the latter, you can It is implemented in the following manner, but is not limited to this: the above-mentioned modules and units are all located in the same processor; or, the above-mentioned modules and units are located in different processors in any combination.
  • Embodiments of the present invention also provide a computer-readable storage medium that stores a computer program, wherein the computer program is configured to execute the steps in any of the above method embodiments when running.
  • the above-mentioned computer-readable storage media may include but is not limited to: U disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), mobile hard disk, Various media such as magnetic disks or optical disks that can store computer programs.
  • An embodiment of the present invention also provides an electronic device, including a memory and a processor.
  • a computer program is stored in the memory, and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • modules, units or steps of the embodiments of the present invention can be implemented using general-purpose computing devices, and they can be concentrated on a single computing device, or distributed among multiple computing devices.
  • they may be implemented in program code executable by a computing device, so that they may be stored in a storage device and executed by the computing device, and in some cases, may be in a sequence different from that described here.
  • the steps shown or described are performed either by fabricating them separately into individual integrated circuit modules, or by fabricating a plurality of modules, units or steps among them into a single integrated circuit module.
  • embodiments of the present invention are not limited to any specific combination of hardware and software.
  • API is a bridge for information exchange between software components. It is an ability that provides applications and developers with access to a set of routines based on a piece of software or hardware without having to access the source code or understand the details of the internal working mechanism.
  • existing APIs cannot meet existing usage scenarios.
  • Using existing APIs to combine and innovate to generate APIs with new business capabilities is an effective means to quickly respond to changes in business needs. API orchestration The concept came into being.
  • API orchestrators write additional hard code or scripts. This method is non-intrusive to the original API, but has high requirements on the programming capabilities and business knowledge of API orchestrators. In addition, considering complex orchestration scenarios such as parameter transfer between multiple non-adjacent APIs and very complex API parameters, API orchestrators will face greater technical challenges.
  • API orchestrators do not need to write code or scripts for parameter adaptation between APIs. They only write configuration information.
  • the background program automatically generates a parameter adaptation service based on the configuration information and executes it automatically when the API is called.
  • This method does not require API orchestrators to write code, but it still requires learning and mastering a set of orchestration configuration information specifications. The learning cost is not low.
  • the orchestration information is in a plain text format, which has poor readability and is not conducive to error correction.
  • Interface drag and drop method Users directly drag and drop to select appropriate parameters from the front-end API and perform associated mapping with the back-end API. This method is easy to get started and has low learning costs, and is more suitable for orchestrators without programming foundation. However, this method has great limitations. It can only handle parameter adaptation in simple orchestration scenarios, and cannot handle complex adaptation scenarios involving complex logical operations, parameter type conversion, etc.
  • Embodiments of the present invention aim to provide an API parameter adaptation solution that is simple and easy to use, has low code development cost, and satisfies complex orchestration scenarios, solves difficult problems in the API orchestration field of traditional industries, and assists the digital transformation of traditional industries.
  • Custom functions Customize the function logic through coding, generate a new function, and persist the function as a library function to iteratively enhance the functions of the built-in library function;
  • the method or device of the embodiment of the present invention has the characteristics of simplicity and ease of use, low code development cost, ability to meet complex orchestration scenarios, high efficiency, and strong scalability.
  • FIG. 7 is a structural block diagram of a parameter adaptation device according to a scenario embodiment of the present invention. As shown in Figure 7, this scenario implements The parameter adaptation device in the example can be divided into three module parts, including: parameter adapter, script converter and execution engine.
  • the parameter adapter is the core content of the embodiment of the present invention. It includes a parameter pool, a parameter mapping unit, which is the mapping unit in the above embodiment, a built-in library function unit, which is the built-in function unit in the above embodiment, and a custom function unit, which is the above implementation. Custom function unit in the example.
  • the parameter pool is an abstract concept, which is introduced to better understand the subsequent data interaction between units.
  • the essence of the parameter pool is the set of available parameters in the parameter adaptation device.
  • the available parameters include all pre-APIs. Output parameters and their sub-parameters as well as parameters generated by built-in library function units.
  • the parameter adaptation device When the parameter adaptation device is running, it automatically parses all front-end API output parameters and their sub-parameters, and puts them into the parameter pool as available parameters for parameter mapping by the parameter mapping unit.
  • the parameter mapping unit is used to provide visual direct mapping of parameters between APIs. Users can map and associate the parameters available in the parameter pool with the input parameters or sub-parameters of the post-API through an interface.
  • Built-in library function unit is used to provide visual processing of library functions. Users can call the built-in library function of this device through the interface to process the available parameters in the parameter pool, generate new available parameters, which have the format and content expected by the user, and put them into the parameter pool.
  • Custom function units are used to supplement the built-in library function units.
  • the user manually writes the processing logic of the function, generates a new function, and stores it in the built-in library function. unit to achieve iterative enhancement of the device's parameter adaptation capabilities and at the same time achieve the separation effect of software technicians and ordinary API orchestrators.
  • the script converter is used to convert the above parameter adaptation information into an executable script in a specific language.
  • the execution engine executes each API in series according to the set execution order of each API, and calls the script generated by the script converter to realize the adaptation of API parameters between APIs.
  • the API orchestration process generally includes four steps: orchestrating the API call sequence, inter-API parameter adaptation, converting parameter adaptation scripts, and testing and releasing the API.
  • the above parameter adaptation device is used to perform parameter adaptation between APIs.
  • the process of parameter adaptation between APIs includes the following steps:
  • Step 1 Parse the front-end API output parameters.
  • Figure 8 is a schematic diagram of the display method of available parameters according to the scene embodiment of the present invention. As shown in Figure 8, in this embodiment, a tree-like The structure is presented, and this step is automatically completed by the device.
  • Step 2 parameters are mapped directly.
  • the parameter adaptation device automatically parses the post-API input parameters and presents them on the interface in a user-readable manner. In this embodiment, they can be presented in a tree-like structure.
  • the user maps and associates the available parameters in the parameter pool with the post-API input parameters through visual operation methods, such as dragging, dropping, clicking, connecting, etc.
  • Figure 9 is a schematic diagram of the parameter mapping relationship according to the scenario embodiment of the present invention.
  • Figure 10 is a schematic diagram of the parameter mapping interface display according to the scenario embodiment of the present invention.
  • the user can drag the API1-output parameter and sub-parameter A from the parameter pool on the left to the parameter processing area, and then directly connect through the The method connects the API1-output parameter and sub-parameter A to the sub-parameter H1 and sub-parameter H2 of the post-API input parameter respectively to complete the parameter mapping.
  • Step 3 visualize the built-in library functions.
  • FIG 11 is a schematic diagram of built-in function conversion according to a scenario embodiment of the present invention. As shown in Figure 11, sub-parameter 1 and sub-parameter 2 of the pre-API are converted through built-in functions, that is, visual built-in library functions are used to process the parameters. Parameter 2 is obtained, and parameter 2 is used as an available parameter and mapped with sub-parameter 7 of the post-API.
  • Figure 12 is a schematic diagram of the built-in function processing interface display according to the scenario embodiment of the present invention.
  • the user drags the sub-parameter B of the front API from the left to the parameter processing area, and then drags the built-in function 1 from the top Go to the parameter processing area, connect sub-parameter B to built-in function 1, connect built-in function 1 to sub-parameter J of the post-API input parameter, which means that sub-parameter B is processed by built-in function 1 to generate a new parameter and then input with the post-API
  • the sub-parameter J of the parameter is mapped and related, and the sub-parameter D is the same.
  • Step 4 customize the function.
  • the built-in library function module of the parameter adaptation device can provide built-in library functions that meet common scenarios, but inevitably there are scenarios that cannot be applied. Therefore, in this embodiment, the parameter adaptation device additionally provides the ability to customize functions as a built-in Supplementary library functions. Users can specify the types of function input values and return values through the interface, and then use the encoded method to write the execution logic of the function. The generated function is stored in the built-in library function unit and used as a built-in library function. Repeat step 3.
  • Figure 13 is a schematic diagram of custom function conversion according to the scenario embodiment of the present invention. As shown in Figure 13, sub-parameter 1 and sub-parameter 2 of the pre-API are converted through custom functions, that is, visual built-in library functions are used to convert the parameters. Function processing obtains parameter 2, which is used as an available parameter and is mapped with sub-parameter 7 of the post-API.
  • Figure 14 is a schematic display of the custom function editing interface according to the scenario embodiment of the present invention. As shown in Figure 14, the user can click on the custom function, and the function custom function interface appears; the user defines the function by selecting parameters from the parameter pool. input parameter data structure; specify the output data structure; implement function logic through coding.
  • Figure 15 is a schematic diagram of the custom function processing interface display according to the scenario embodiment of the present invention. As shown in Figure 15, after the user edits the custom function, the function appears in the built-in library function area; optionally, the parameter processing area automatically Generate the connection relationship between sub-parameter F, sub-parameter G and the comparison function; the user can also manually drag and drop other available parameters to connect to the comparison function.
  • Figure 16 is a schematic diagram of the custom function mapping interface display according to the scenario embodiment of the present invention. As shown in Figure 16, the user can connect the comparison function to the parameter L to complete the mapping relationship connection.
  • Step 5 Repeat steps 2, 3, and 4 according to the user's parameter adaptation goals to complete the adaptation of complex parameters between APIs.
  • Figure 17 is a schematic diagram of parameter mapping relationships according to a scenario embodiment of the present invention. As shown in Figure 17, users can use a combination of built-in library functions and custom functions to function on parameters, and then perform parameter mapping.
  • Figure 18 is a schematic diagram of the function processing interface display according to the scenario embodiment of the present invention. As shown in Figure 18, API1-output parameters and API2-output parameters are processed by the custom function 1, and then processed by the built-in function 2, and then combined with the sub-function Parameter A is processed together by custom function 2, and finally mapped and associated with the sub-parameter L of the post-API input parameter.
  • parameter adaptation between APIs in complex orchestration scenarios can be completed, and programming technicians can write custom functions suitable for the current API orchestration scenario, enrich visual built-in library functions, and iteratively enhance the parameter adaptation capabilities of this device. This makes it possible to accumulate adaptation capabilities and gradually reduce dependence on programming technicians.
  • a communication/network operator system hopes to use existing APIs and quickly launch a new function that automatically recommends monthly rental packages to users through the API orchestration platform.
  • the logic is to recommend the monthly rental package based on the user's minimum and maximum consumption in the past year. Rent a range of packages.
  • the existing APIs are:
  • API-001 queries the user's monthly consumption situation in the past year.
  • the input and output parameters are described as follows:
  • API-002 query system for packages that meet the monthly rent range.
  • the input and output are described as follows:
  • Step 1 Arrange the execution sequence of API-001 (query the user’s monthly consumption in the past year) and API-002 (query the packages in the system with a specified monthly rent range) in the API orchestration platform: Connect API-001 to the API -002.
  • Figure 19 is a flow chart for automatically recommending monthly rental packages according to a scenario embodiment of the present invention.
  • Step 2 Since the parameters between API-001 and API-002 do not match, the parameters cannot be transferred normally, and the device of the embodiment of the present invention is used to implement parameter adaptation of API-001 and API-002.
  • the specific process is as follows:
  • the parameter adaptation device automatically parses the output parameters and sub-parameters of the front-end API (API-001) into the parameter pool. After parsing, the following available parameters are available: consumption statistics in the past year (type: object array), user information (type : object), user level (type: number), Internet age (type: number), age (type: number);
  • the parameter mapping unit uses the parameter mapping unit to associate the minimum consumption mapping to the sub-section of the API-002 input parameter in an interface manner.
  • the parameter is the minimum monthly rent
  • the sub-parameter that associates the maximum consumption mapping to the input parameter of API-002 is the maximum monthly rent.
  • Step 3 The script converter converts the user's parameter adaptation operation information in the previous step into an executable script
  • Step 4 The API orchestration platform launches the new API
  • Step 5 The new API that automatically recommends monthly rental packages to users is online and provides services to the outside world.
  • the internal execution engine calls the executable script in step 3 to implement parameter adaptation of the API-001 and API-002 interfaces, ensuring that the parameters are normal during the call from API-001 to API-002. Passed so that the API functions normally.
  • Figure 20 is a schematic diagram of interface parameter adaptation according to a scenario embodiment of the present invention.
  • this scenario embodiment through the combined use of parameter mapping and built-in library function manipulation, visual adaptation of parameters between APIs is achieved in the API orchestration scenario. , and quickly launched new APIs through the API orchestration platform.
  • the API orchestration platform automatically recommends APIs for monthly rental packages to users, and only recommends monthly rental packages to users based on the user's minimum consumption and maximum consumption in the past year.
  • the logic of the API is optimized.
  • the optimization content is as follows: the new API for user recommendation of monthly rental packages can recommend monthly rental packages based on the user's level, Internet experience, age and other information, combined with consumption conditions.
  • Step 1 The company's coding technicians are responsible for writing two custom functions in the custom function unit of the device: the minimum consumption analysis function and the maximum consumption analysis function, and store them in the built-in library function unit.
  • Figure 21 is a schematic diagram for editing the minimum consumption analysis function according to the scenario embodiment of the present invention
  • Figure 22 is a schematic diagram for editing the maximum consumption analysis function according to the scenario embodiment of the present invention.
  • Step 2 The API orchestrator within the company is responsible for transforming the parameter adaptation through the interface operation provided by the parameter adaptation device.
  • the operation process is as follows:
  • the API orchestrator uses the parameter mapping unit of the parameter adaptation device to connect monthly consumption and user information to the customized minimum consumption analysis function and maximum consumption analysis function, and process the minimum consumption and maximum consumption parameters respectively, and the types are all numbers. ;
  • This scenario embodiment modifies the existing parameter adaptation results of the parameter adaptation device in scenario embodiment three.
  • the pre-operation process is shown in scenario embodiment three, which will not be described again here.
  • the subsequent steps are the same as steps 3, 4, and 5 in scenario embodiment 3.
  • the new user recommended monthly rental package API function is put online for use.
  • Figure 23 is a schematic diagram of the parameter adaptation interface according to the scenario embodiment of the present invention. As shown in Figure 23, the minimum consumption analysis function and the maximum consumption analysis function written by software technicians can be persisted into the device, enriching the built-in functions of the device. Library functions can be used in other API orchestration scenarios later.
  • the application scenario provided by the scenario embodiment is: a company's assessment system needs to provide an API that automatically conducts monthly assessments and evaluations for employees.
  • the internal logic is to conduct assessments based on multiple dimensions such as PTL scoring, project bonus points, APO scoring, and employees' job levels. Fill in the level.
  • the position level of a known employee can be queried through API-002 (query employee position information).
  • the input and output parameter descriptions are as follows:
  • employee assessment level setting can be completed through API-003 (setting employee assessment level).
  • API-003 setting employee assessment level
  • Step 1 Arrange the execution sequence of API-001, API-002 and API-003 in the API orchestration platform: connect API-002 to API-001, and then connect API-001 to API-003.
  • Step 2 It is analyzed that parameter adaptation is not required between API-002 and API-001, but parameter adaptation is required between API-001 and API-003.
  • Step 3 Use the parameter adaptation device to perform parameter adaptation between API-001 and API-003.
  • the specific control process is as follows:
  • API-001 output parameter
  • type object
  • employee name type: string
  • This function has code logic to calculate employee assessment grade through the four dimensions of employee position grade, PTL score, project bonus score and APO score, and stores it in the built-in library function. unit;
  • Step 4 The internal script converter converts the user's parameter adaptation operation information in the previous step into an executable script
  • Step 5 The API orchestration platform launches the new API. This part is not part of the embodiment of the present invention.
  • Step 6 The new employee assessment level automatically sets the API to provide external services.
  • the internal execution engine calls the executable script in step 4 to implement parameter adaptation between APIs, ensuring the normal transfer of parameters during the call from API-002 to API-001 to API-003. , making the API function normally.
  • Figure 25 is a schematic diagram of the custom assessment level calculation function interface according to the scenario embodiment of the present invention
  • Figure 26 is a schematic diagram of the parameter mapping interface according to the scenario embodiment of the present invention.
  • FIG. 27 is a schematic diagram of splitting the assessment level function according to the scenario embodiment of the present invention. As shown in Figure 27, a single assessment level function is split into multiple functions as follows:
  • Position score calculation function This function calculates the job grade score based on job information.
  • Additional score calculation function Configure the weights of project bonus points to obtain additional assessment points.
  • the parameter adaptation device is used to implement parameter adaptation between adjacent and non-adjacent APIs during API orchestration; it is demonstrated that the parameter mapping and automatic parameter adaptation devices are used in combination during API orchestration.
  • functions to implement parameter adaptation It also gives a best practice for parameter adaptation devices, that is, when customizing functions, write small and simple general functions as much as possible to facilitate subsequent reuse in other API orchestration processes.
  • the embodiments of the present invention disclose a parameter adaptation method between APIs and a parameter adaptation device used to implement parameter adaptation between APIs.
  • a parameter adaptation device used to implement parameter adaptation between APIs.
  • users can perform parameter adaptation between APIs through direct parameter mapping, visual built-in library functions, custom functions, and a combination of the above three methods.
  • Parameter direct mapping method description All pre-API output parameters and post-API input parameters are presented on the interface. In order to facilitate user viewing, it can be in the form of a tree structure. Users can map parameters between APIs through dragging, dropping, clicking, connecting or other interface operations to complete parameter adaptation;
  • the interface provides a detailed list of built-in library functions.
  • the list can include the name, description, input and output parameter details, usage help and other information of each built-in library function.
  • the interface will The built-in library function is presented in the form of , and the user processes the existing parameters with the built-in library function by dragging, dropping, clicking, selecting, etc., and obtains new parameters.
  • Available parameters include output (sub) parameters of the front-end API, parameters generated by other library functions, and parameters generated by custom functions.
  • Custom function method After the user selects the custom function method, he or she can select zero or more available parameters as input parameters through the interface, and specify the data format of the output parameters. Available parameters include output (sub) parameters of the front-end API, parameters generated by other library functions, and parameters generated by custom functions. Then write the function processing logic in the code editing area to finally generate new parameters. At the same time, the written function logic can be saved to the built-in function library to facilitate subsequent reuse.
  • the visual function library can be continuously enriched by writing custom functions. As the capabilities of the visual function library continue to improve, there are fewer and fewer cases where custom functions need to be written. In the end, general ability orchestration users can completely use the two visualization methods. (Direct parameter mapping and visual built-in library functions) to complete parameter adaptation between APIs. At the same time, by continuously combining and nesting built-in library functions and custom functions, sufficiently complex parameter conversion logic can be generated to cope with complex capability orchestration scenarios.
  • the parameter adaptation method and parameter adaptation device provided by the embodiments of the present invention focus on the API orchestration API inter-API parameter adaptation device, which uses a combination of direct parameter mapping, visual built-in library functions and custom functions described in the embodiments of the present invention to implement inter-API Parameter adaptation; and API orchestration API inter-API parameter adaptation device, which realizes the control process of iterative enhancement of device capabilities by writing custom functions to extend built-in library functions;
  • the embodiment of the present invention realizes input and output between APIs by directly writing parameter adaptation code/script and writing configuration information. Comparing parameter adaptation methods, the embodiment of the present invention mainly uses a visual parameter adaptation method, which is simple and easy to use, has low code development cost, and can efficiently solve parameter adaptation in complex orchestration scenarios; it is different from the existing method that relies entirely on drag and drop. Comparison of methods for completing capability orchestration parameter adaptation. Completely drag-and-drop cannot meet complex business scenarios. For example, parameter adaptation between interfaces relies on complex calculations or business-specific computing logic. It is not a complete parameter adaptation solution and has orchestration capabilities. Limitations of the scene. The embodiment of the present invention provides a low-code inter-API parameter adaptation device to meet the usage requirements of complex orchestration scenarios.
  • the parameter adaptation device of the embodiment of the present invention has an iterative enhancement mechanism: the functions generated by the custom function unit coding in the device can be persistently stored in the built-in library function unit, iteratively enhancing the processing capabilities of the built-in library function unit, and at the same time, this mechanism also achieves It has the effect of separating coding technicians from ordinary API orchestrators, and gradually reduces the dependence on coding technicians. Any industry that needs to use parameter adaptation can use this parameter adaptation device.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Stored Programmes (AREA)

Abstract

本发明实施例提供了一种应用程序编程接口API间的参数适配方法及装置，通过本发明实施例，解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；解析API编排中的后置API的输入参数，并在界面呈现所述输入参数；从参数池中的输出参数中选择与后置API的输入参数相适配的目标输出参数，或基于输出参数生成目标输出参数，并将目标输出参数与后置API的输入参数进行映射关联，以实现前置API与后置API间的参数适配，解决了相关技术中无法简单易用、低成本地解决复杂编排场景中API间的参数适配的问题，达到了提高API间的参数适配效率的效果。

Description

应用程序编程接口API间的参数适配方法及装置
相关申请的交叉引用
本申请基于2022年8月25日提交的发明名称为“应用程序编程接口API间的参数适配方法及装置”的中国专利申请CN202211026581.7，并且要求该专利申请的优先权，通过引用将其所公开的内容全部并入本申请。
技术领域
本发明实施例涉及计算机应用领域，具体而言，涉及一种应用程序编程接口API间的参数适配方法及装置。
背景技术
应用程序编程接口(Application Programming Interface，API)编排指的是各个业务组件的业务能力以API为不可拆分的原子服务，进行执行顺序的编排组合，生成具有新的服务能力的API。在未事先约定的情况下，不同的API的输入输出参数在结构和数据内容上往往存在差异。微服务架构下，各个微服务组件由不同的团队独立开发，这种差异性被进一步放大。这种异构的API之间，无法通过简单的连接关系来完成API组合，需要对API间接口参数进行适配处理。
当前，全行业数字化转型在不断加速。在面向行业数据化过程中，传统行业中逐渐涌现对现有API进行编排达到快速迭代新功能的需求。一般而言，传统行业中API涉及专业的行业知识，同时软件技术相对于互联网软件行业较为落后，技术迭代更新缓慢，API异构现象更为明显，构成了更为复杂的API编排场景，API间参数适配更具有挑战性。
现有的API间参数适配方案无法提供一种简单易用、代码开发成本低、满足复杂编排场景的API间参数适配方式。
发明内容
本发明实施例提供了一种应用程序编程接口API间的参数适配方法及装置，以至少解决相关技术中无法简单易用、低成本地解决复杂编排场景中API间的参数适配的问题。
根据本发明的一个实施例，提供了一种应用程序编程接口API间的参数适配方法，包括：解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；解析API编排中的后置API的输入参数，并在界面呈现所述输入参数；从所述参数池中的输出参数中选择与所述后置API的输入参数相适配的目标输出参数，或基于所述输出参数生成所述目标输出参数，并将所述目标输出参数与所述后置API的输入参数进行映射关联，以实现所述前置API与所述后置API间的参数适配。
根据本发明的另一个实施例，提供了一种应用程序编程接口参数适配装置，包括：第一解析模块，设置为解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；第二解析模块，设置为解析API编排中的后置API的输入参数，并在界面呈现所述输入参数；映射适配模块，设置为从所述参数池中的输出参数中选择与所述后置API的输入参数相适配的目标输出参数，或基于所述输出参数生成所述目标输出参数，并将所述 目标输出参数与所述后置API的输入参数进行映射关联，以实现所述前置API与所述后置API间的参数适配。
根据本发明的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
附图说明
图1是本发明实施例的一种API间的参数适配方法的移动终端的硬件结构框图；
图2是根据本发明实施例的API间的参数适配方法的流程图；
图3是根据本发明实施例的参数适配装置的结构框图；
图4是根据本发明实施例的映射适配模块的结构框图；
图5是根据本发明实施例的映射适配模块的结构框图；
图6是根据本发明实施例的映射适配模块的结构框图；
图7是根据本发明场景实施例的参数适配装置的结构框图；
图8是根据本发明场景实施例的可用参数的显示方式示意图；
图9是根据本发明场景实施例的参数映射关系示意图；
图10是根据本发明场景实施例的参数映射界面化显示示意图；
图11是根据本发明场景实施例的内置函数转换示意图；
图12是根据本发明场景实施例的内置函数处理界面化显示示意图；
图13是根据本发明场景实施例的自定义函数转换示意图；
图14是根据本发明场景实施例的自定义函数编辑界面化显示示意图；
图15是根据本发明场景实施例的自定义函数处理界面化显示示意图；
图16是根据本发明场景实施例的自定义函数映射界面化显示示意图；
图17是根据本发明场景实施例的参数映射关系示意图；
图18是根据本发明场景实施例的函数处理界面化显示示意图；
图19是根据本发明场景实施例的自动推荐月租套餐的流程图；
图20是根据本发明场景实施例的界面化参数适配示意图；
图21是根据本发明场景实施例的最低消费分析函数编辑示意图；
图22是根据本发明场景实施例的最高消费分析函数编辑示意图；
图23是根据本发明场景实施例的参数适配界面化示意图；
图24是根据本发明场景实施例的员工自动月考核评价的流程图；
图25是根据本发明场景实施例的自定义考核等级计算函数界面示意图；
图26是根据本发明场景实施例的参数映射界面示意图；
图27是根据本发明场景实施例的考核等级函数拆分示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明实施例。
需要说明的是，本发明实施例的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例中所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例，图1是本发明实施例的一种API间的参数适配方法的移动终端的硬件结构框图。如图1所示，移动终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置)和用于存储数据的存储器104，其中，上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本发明实施例中的API间的参数适配方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端的API间的参数适配方法，图2是根据本发明实施例的API间的参数适配方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；
步骤S204，解析API编排中的后置API的输入参数，并在界面呈现输入参数；
步骤S206，从参数池中的输出参数中选择与后置API的输入参数相适配的目标输出参数，或基于输出参数生成目标输出参数，并将目标输出参数与后置API的输入参数进行映射关联，以实现前置API与后置API间的参数适配。
通过上述步骤，通过解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；解析API编排中的后置API的输入参数，并在界面呈现输入参数；从参数池中的输出参数中选择与后置API的输入参数相适配的目标输出参数，或基于输出参数生成目标输出参数，并将目标输出参数与后置API的输入参数进行映射关联，以实现前置API与后置API间的参数适配，解决了相关技术中无法简单易用、低成本地解决复杂编排场景中API间的参数适配的问题，达到了提高API间的参数适配效率的效果。
在一个示例性实施例中，基于输出参数生成目标输出参数包括：通过界面化方式采用内置库函数对输出参数进行函数处理以生成目标输出参数。
在一个示例性实施例中，通过界面化方式采用内置库函数对输出参数进行函数处理以生成目标输出参数之前，还包括：通过编码方式自定义函数逻辑以生成新函数，并将生成的新函数作为内置库函数存储。
其中，在本实施例中，若内置库函数的函数处理得到的目标输出参数满足了参数适配需要，则不需要再进行自定义函数进行函数处理了，即在进行函数处理之前可以先判断现有的内置库函数能否满足最终的参数适配需求，如果满足则不需要自定义函数，如果不满足再自定义函数，同时，若进行了自定义函数的步骤，则自定义函数作为新的内置库函数与原有的内置库函数一同存储，为之后的API间的参数适配提供函数，以不断地提高内置库函数的数量，从而减少自定义函数的次数，提高参数适配的效率。
在一个示例性实施例中，将目标输出参数与后置API的输入参数进行映射关联，包括：通过可视化操作将目标输出参数与后置API的输入参数进行映射关联。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明实施例的各个实施例所述的方法。
在本实施例中还提供了一种参数适配装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图3是根据本发明实施例的参数适配装置的结构框图，如图3所示，该参数适配装置30包括：第一解析模块310，设置为解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；第二解析模块320，设置为解析API编排中的后置API的输入参数，并在界面呈现输入参数；映射适配模块330，设置为从参数池中的输出参数中选择与后置API的输入参数相适配的目标输出参数，或基于输出参数生成目标输出参数，并将目标输出参数与后置API的输入参数进行映射关联，以实现前置API与后置API间的参数适配。
在一个示例性实施例中，图4是根据本发明实施例的映射适配模块的结构框图，如图4所示，映射适配模块330包括：内置函数单元410，设置为通过界面化方式采用内置库函数对输出参数进行函数处理以生成目标输出参数。
在一个示例性实施例中，图5是根据本发明实施例的映射适配模块的结构框图，如图5所示，映射适配模块330除了包括图4中的单元外，还包括：自定义函数单元510，设置为通过编码方式自定义函数逻辑以生成新函数，并将生成的新函数作为内置库函数存储。
在一个示例性实施例中，图6是根据本发明实施例的映射适配模块的结构框图，如图6所示，映射适配模块330除了包括图5中的单元外，还包括：映射单元610，设置为通过可视化操作将目标输出参数与后置API的输入参数进行映射关联。
需要说明的是，上述各个模块、单元是可以通过软件或硬件来实现的，对于后者，可以 通过以下方式实现，但不限于此：上述模块、单元均位于同一处理器中；或者，上述各个模块、单元以任意组合的形式分别位于不同的处理器中。
本发明实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明实施例的各模块、单元或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块、单元或步骤制作成单个集成电路模块来实现。这样，本发明实施例不限制于任何特定的硬件和软件结合。
为了使得本领域的技术人员更好地理解本发明实施例的技术方案，下面结合具体的场景实施例对本发明实施例的技术方案进行阐述。
API是软件组件之间信息交互的桥梁，是一种提供应用程序与开发人员基于某软件或硬件得以访问一组例程的能力，而无需访问源码，或理解内部工作机制的细节。在业务需求快速变化的情况下，现有API不能满足现有的使用场景，利用现有的API进行组合创新生成具有新的业务能力的API是一种快速响应业务需求变化的有效手段，API编排的概念应运而生。
目前常见的API间的参数适配方式有三种：
1.编写额外的硬代码或是脚本。该方式对原API无侵入性，但对API编排人员的编程能力和业务知识具有较高要求。此外，考虑非相邻的多个API间参数传递、API参数非常复杂等复杂编排场景，API编排人员将面临更大的技术挑战。
2.编写配置信息的方式。API编排人员对于API间参数适配，不需要编写代码或是脚本，仅编写配置信息，后台程序自动根据该配置信息生成参数适配服务，在API调用时自动执行。该方式无需API编排人员编写代码，但仍然需要学习和掌握一套编排配置信息规范，学习成本也不低，同时编排信息为纯文字格式，可读性较差，也不利于纠错。
3.界面化拖拽的方式。用户直接通过拖拽的方式，从前置API中选择合适的参数与后置API进行关联映射，该方式上手容易，学习成本低，更适合没有编程基础的编排人员。但该方式具有很大的局限性，只能处理简单编排场景下的参数适配，不能处理涉及复杂逻辑运算、参数类型转换等复杂的适配场景。
综上，现有方案无法提供一种简单易用、代码开发成本低、满足复杂编排场景的API间 参数适配方式。基于上述的技术，能够在传统行业这样复杂的编排场景中胜任API编排任务的人员一定是通晓平台微服务能力并具备一定行业专业知识的跨领域技术人才。但考虑到用人成本等因素，多数传统企业中不会存在大量的这种人才，进行API编排的人员往往是该传统行业的普通从业人员，具备行业专业知识，但不会编程，或仅仅对编程有一定的概念。
本发明实施例旨在提供一种简单易用、代码开发成本低、满足复杂编排场景的API间参数适配方案，解决传统行业在API编排领域的难点问题，助力传统行业的数字化转型。
本发明实施例通过有机结合使用下述三种方式，提供了一套API编排中API间参数适配的完整解决方案：
1.参数直接映射。解析所有前置能力接口输出参数及其子参数，作为装置内的可用参数放入参数池，通过界面化方式(拖、拽、点击等)将参数池中可用参数与后置API的输入参数或其子参数进行映射；
2.可视化内置库函数。通过界面化方式使用内置库函数对参数池中可用参数进行处理转换，生成新的可用参数并放入参数池，供参数直接映射方式使用；
3.自定义函数。通过编码方式自定义函数逻辑，生成新的函数，并将该函数作为库函数持久化存储，迭代增强内置库函数功能；
本发明实施例的方法或者装置具有简单易用、代码开发成本低、满足复杂编排场景、高效率、可扩展性极强等特点。
场景实施例一
本场景实施例中提供了一种实现API间的参数适配方法的参数适配装置，图7是根据本发明场景实施例的参数适配装置的结构框图，如图7所示，本场景实施例中的参数适配装置可以分为三个模块部分，包括：参数适配器、脚本转换器和执行引擎。
参数适配器是本发明实施例的核心内容，其包含了参数池、参数映射单元即上述实施例中的映射单元、内置库函数单元即上述实施例中的内置函数单元、自定义函数单元即上述实施例中的自定义函数单元。
其中，参数池是一个抽象的概念，是为了更好地理解后续各单元间数据交互而引入，参数池的本质是该参数适配装置内可用参数的集合，可用参数包括了所有的前置API输出参数及其子参数以及内置库函数单元产生的参数。参数适配装置运行时，自动解析所有的前置API输出参数及其子参数，将其作为参数映射单元用于参数映射的可用参数放入参数池。
参数映射单元，用于提供可视化的API间参数直接映射功能。用户可以通过界面化的方式将参数池中可用参数与后置API的输入参数或其子参数进行映射关联。
内置库函数单元，用于提供可视化的库函数处理方式。用户可以通过界面化方式调用本装置内置的库函数来对参数池中可用参数进行处理，生成新的可用参数，该参数具有用户期望的格式和内容，并放入参数池。
自定义函数单元，用于是对内置库函数单元的补充，当内置库函数提供的功能无法满足参数处理转换需求时，由用户手工编写函数的处理逻辑，生成新的函数，并存储到内置库函数单元，实现本装置参数适配能力的迭代增强，同时达到软件技术人员与普通API编排人员的分离效果。
用户通过有机结合地使用参数映射单元、内置库函数单元和自定义函数单元提供的功能来应对各种复杂API编排场景下API间的参数适配。用户的所有操作都可以在本装置提供的 界面上完成，装置自动根据用户的界面操作后台生成相应的API间参数适配信息(包含参数映射单元的参数映射关系、使用的库函数等信息)。
脚本转换器用于将上述参数适配信息转换为特定语言的可执行脚本。API编排生成的新的API被调用时，执行引擎按照设置的各个API的执行顺序，串联执行各个API，并调用脚本转换器生成的脚本，实现API间API参数的适配。
场景实施例二
在API编排中引入场景实施例一中的参数适配装置之后，API编排的过程一般包括：编排API调用顺序、API间参数适配、转换参数适配脚本和测试发布API四个步骤。在本场景实施例中，利用上述参数适配装置进行API间参数适配，具体地，API间参数适配的过程包括以下步骤：
步骤1，解析前置API输出参数。
将所有前置API输出参数及其子参数解析为可用参数，并放入参数池中。在界面上，以一定的排列方式呈现参数池中所有可用参数，图8是根据本发明场景实施例的可用参数的显示方式示意图，如图8所示，在本实施例中可以用树状的结构进行呈现，此步骤由装置自动完成。
步骤2，参数直接映射。
在本实施例中，参数适配装置自动解析后置API输入参数，并在界面上以用户可读性强的方式呈现，在本实施例中可以用树状的结构进行呈现。用户通过可视化的操作方式，如拖、拽、点击、连线等方式将参数池中可用参数与后置API输入参数进行映射关联，图9是根据本发明场景实施例的参数映射关系示意图。图10是根据本发明场景实施例的参数映射界面化显示示意图，如图10所示，用户可以从左侧参数池中拖拽API1-输出参数和子参数A到参数处理区域，然后直接通过连线的方式将API1-输出参数和子参数A分别与后置API输入参数的子参数H1和子参数H2进行连接，完成参数映射。
步骤3，可视化内置库函数。
当存在API间参数无法简单的通过参数直接映射方式完成适配时，用户可以使用可视化的内置库函数对参数池中现有的可用参数进行函数处理，生成用户期望的新的可用参数，并放回参数池，然后重复步骤2，进行参数映射。图11是根据本发明场景实施例的内置函数转换示意图，如图11所示，将前置API的子参数1和子参数2通过内置函数转换，即利用了可视化的内置库函数对参数进行函数处理获得了参数2，参数2作为可用参数再与后置API的子参数7进行映射。
图12是根据本发明场景实施例的内置函数处理界面化显示示意图，如图12所示，用户从左侧拖拽前置API的子参数B到参数处理区域，然后从上方拖拽内置函数1到参数处理区域，连接子参数B到内置函数1，连接内置函数1到后置API输入参数的子参数J，即表示子参数B经过内置函数1处理后生成新的参数再与后置API输入参数的子参数J进行映射关联，子参数D同理。
步骤4，自定义函数。
参数适配装置的内置库函数模块可以提供满足常见场景的内置库函数，但无可避免存在不能适用的场景，因此，本实施例中参数适配装置额外提供自定义函数的能力，作为是内置库函数的补充。用户可以通过界面化的方式指定函数输入值和返回值的类型，然后以编码的 方式编写函数的执行逻辑。生成的函数被存储到内置库函数单元，作为内置库函数被使用。重复步骤3。图13是根据本发明场景实施例的自定义函数转换示意图，如图13所示，将前置API的子参数1和子参数2通过自定义函数转换，即利用了可视化的内置库函数对参数进行函数处理获得了参数2，参数2作为可用参数再与后置API的子参数7进行映射。
图14是根据本发明场景实施例的自定义函数编辑界面化显示示意图，如图14所示，用户可以点击自定义函数，出现函数自定义函数界面；用户通过从参数池中选择参数来定义函数的输入参数数据结构；指定输出数据结构；通过编码实现函数逻辑。
图15是根据本发明场景实施例的自定义函数处理界面化显示示意图，如图15所示，用户编辑好自定义函数后，该函数出现在内置库函数区域；可选的，参数处理区域自动生成子参数F、子参数G与比较函数的连接关系；用户也可以手动拖拽其他可用参数来连接到比较函数。
图16是根据本发明场景实施例的自定义函数映射界面化显示示意图，如图16所示，用户可以将比较函数连接到参数L，完成映射关系连接。
步骤5，按照用户的参数适配目标，反复执行步骤2、3、4，可以完成API间复杂参数的适配。
图17是根据本发明场景实施例的参数映射关系示意图，如图17所示，用户可以组合使用内置库函数、自定义函数对参数进行函数，之后进行参数映射。
图18是根据本发明场景实施例的函数处理界面化显示示意图，如图18所示，API1-输出参数和API2-输出参数经过自定义函数1处理后，然后经过内置函数2处理，再与子参数A一起经过自定义函数2处理，最后与后置API输入参数的子参数L进行映射关联。
通过上述步骤，可以完成复杂编排场景下API间的参数适配，并且编程技术人员编写适合当前API编排场景的自定义函数，丰富可视化内置库函数，从而迭代增强本装置的参数适配能力，这使得适配能力的积累成为可能，并逐步降低了对编程技术人员的依赖。
场景实施例三
在本场景实施例中给出具体的应用场景，对本发明实施例的技术方案进行阐述。某通信/网络运营商系统希望利用现有的API，通过API编排平台，快速上线自动给用户推荐月租套餐的新功能，其逻辑为根据用户近一年的最低消费和最高消费，推荐该月租范围内的套餐。
现有的API有：
API-001查询用户最近一年每月消费情况，输入输出参数描述如下：

还包括API-002查询系统中满足月租资费范围的套餐，输入输出描述如下：
通过API编排平台并在API编排平台中使用本发明实施例的参数适配装置进行API间参数适配，实现快速上线上述自动给用户推荐月租套餐的功能，实现步骤如下：
步骤1，在API编排平台中编排API-001(查询用户最近一年每月消费情况)和API-002(查询系统中指定月租资费范围的套餐)的执行顺序：将API-001连接到API-002。图19是根据本发明场景实施例的自动推荐月租套餐的流程图。
步骤2，由于API-001和API-002间的参数不匹配，参数无法正常传递，使用本发明实施例装置实现API-001和API-002的参数适配。具体过程如下所示：
2.1参数适配装置自动解析前置API(API-001)的输出参数及子参数到参数池，解析后有如下的可用参数：近一年消费情况统计(类型：对象数组)、用户信息(类型：对象)、用户等级(类型：数字)、网龄(类型：数字)、年龄(类型：数字)；
2.2使用内置库函数单元的数组转换函数，以界面化的方式对可用参数即近一年消费情况统计进行处理，得到新参数即每月消费(类型：数字型数组)；
2.3使用内置库函数单元的最小值函数和最大值函数，以界面化的方式对每月消费处理得到最低消费和最高消费参数，类型均为数字；
2.4使用参数映射单元，以界面化的方式将最低消费映射关联到API-002输入参数的子 参数即最低月租，将最高消费映射关联到API-002的输入参数的子参数即最高月租。
步骤3，脚本转换器将上一步骤中用户的参数适配操作信息转换为可执行脚本；
步骤4，API编排平台上线该新的API；
步骤5，新的自动给用户推荐月租套餐API上线并对外提供服务。该API被调用时，内执行引擎调用步骤3中的可执行脚本，实现API-001和API-002接口的参数适配，从来保障了从API-001到API-002的调用过程中参数的正常传递，使得API功能正常。
上述步骤3、4、5采用本领域的常规技术即可实现，这里不再展开描述。图20是根据本发明场景实施例的界面化参数适配示意图，在本场景实施例中，通过组合使用参数映射和内置库函数操控方式，在API编排场景中实现了API间参数的可视化适配，并通过API编排平台快速上线了新的API。
场景实施例四
场景实施例三中API编排平台自动给用户推荐月租套餐的API，仅依据用户近一年的最低消费和最高消费来给用户推荐月租套餐。在本场景实施例中对该API进行逻辑优化，优化内容如下：新的用户推荐月租套餐的API能够根据用户的等级、网龄、年龄等信息，再结合消费情况来推荐月租套餐。
为了实现上述优化，仅需要在API编排平台中使用本发明实施例提供的参数适配装置对(查询用户最近一年每月消费情况)和API-002(查询系统中指定月租资费范围的套餐)的参数适配进行改造，步骤如下：
步骤1，公司内编码技术人员负责在本装置的自定义函数单元内编写两个自定义函数：最低消费分析函数和最高消费分析函数，并存储到内置库函数单元。
图21是根据本发明场景实施例的最低消费分析函数编辑示意图，图22是根据本发明场景实施例的最高消费分析函数编辑示意图。
步骤2公司内API编排人员负责通过参数适配装置提供的界面化操作对参数适配进行改造，操作过程如下：
2.1API编排人员使用参数适配装置的参数映射单元，将每月消费和用户信息连接到自定义的最低消费分析函数和最高消费分析函数，分别处理得到最低消费和最高消费参数，类型均为数字；
2.2使用本发明实施例装置的参数映射单元，以界面化的方式将最低消费映射关联到API-002输入参数的子参数最低月租，将最高消费映射关联到后置API(API-002)的输入参数的子参数最高月租。
本场景实施例是对场景实施例三中参数适配装置已有的参数适配结果进行修改，前置操作过程见场景实施例三，这里不再赘述。以及后续步骤同场景实施例三中步骤3、4、5，新的用户推荐月租套餐API功能上线使用。
图23是根据本发明场景实施例的参数适配界面化示意图，如图23所示，软件技术人员编写的最低消费分析函数和最高消费分析函数可以持久化到本装置内，丰富本装置的内置库函数，后续可在其他的API编排场景中继续使用。
通过本场景实施例展示了组合使用参数直接映射、可视化内置库函数和自定义函数方式实现API编排中异构API间参数的适配；以及本发明实施例提供的参数适配装置自定义函数单元带来的适配能力迭代增强的能力，能够使得编码技术人员和API编排人员分离，逐步降 低对编码技术人员的依赖，最终达到零代码实现API编排下API间参数的适配。
场景实施例五
场景实施例提供的应用场景是：某公司考核系统中需要提供自动给员工进行月考核评价的API，内部逻辑为根据PTL打分、项目加分、APO打分、员工的岗位等级等多个维度进行考核等级填写。
已知PTL打分、项目加分、APO打分信息可以通过现有的API-001(查询员工的考核信息)进行查询，该API的输入输出参数描述如下所示：
已知员工的岗位等级可以通过API-002(查询员工的职位信息)查询，输入输出参数描述如下所示：
已知员工的考核等级设置可以通过API-003(设置员工考核等级)完成，输入输出参数描述如下：

现在通过API编排平台并在API编排平台中使用本发明实施例提供的参数适配装置进行API间参数适配，实现快速上线上述自动给员工进行月考核评价的API的功能，图24是根据本发明场景实施例的员工自动月考核评价的流程图，如图24所示，实现步骤如下：
步骤1，在API编排平台中编排API-001、API-002和API-003的执行顺序：将API-002连接到API-001，API-001再连接到API-003。
步骤2，分析出API-002与API-001之间不需要参数适配，API-001与API-003之间需要进行参数适配。
步骤3，使用参数适配装置，对API-001与API-003之间进行参数适配，具体操控过程如下：
3.1本装置自动解析前置API(API-001和API-002)的输出参数及子参数到参数池，解析后有如下的可用参数：API-001输出参数(类型：对象)、员工ID(类型：字符串)、员工姓名(类型：字符串)等；
3.2通过参数映射单元，将参数池中员工ID参数映射到后置API(API-003)的员工ID参数；
3.3通过自定义函数单元，编写考核等级计算函数，该函数具有通过员工的岗位等级、PTL打分、项目加分和APO打分这四个维度来计算员工考核等级的代码逻辑，并存储到内置库函数单元；
3.4通过内置库函数单元，选择自定义的考核等级计算函数，将参数池中岗位等级、PTL打分、APO打分、项目加分等参数进行处理，得到新的参数即考核等级；
3.5通过参数映射单元，将考核等级参数映射到后置API(API-003)的考核等级参数。
步骤4，内脚本转换器将上一步骤中用户的参数适配操作信息转换为可执行脚本；
步骤5，API编排平台上线该新的API，该部分不是本发明实施例内容；
步骤6，新的员工考核等级自动设置API对外提供服务。该API被调用时，内执行引擎调用步骤4中的可执行脚本，实现API间的参数适配，从来保障了从API-002到API-001再到API-003的调用过程中参数的正常传递，使得API功能正常。
图25是根据本发明场景实施例的自定义考核等级计算函数界面示意图，图26是根据本发明场景实施例的参数映射界面示意图。
在本实施例中给出一种更优的实践方法，软件技术人员编写自定义函数时，应该将逻辑复杂的大函数拆分为一个个小而简的函数，提高自定义函数的可复用性。图27是根据本发明场景实施例的考核等级函数拆分示意图，如图27所示，将单一的考核等级函数拆分为如下多个函数：
1.岗位分值计算函数。该函数根据岗位信息计算岗位等级分数。
2.人员打分汇总函数。将PTL打分和APO打分进行加权计算，得到考核者打分。
3.附加分值计算函数。将项目加分进行权重配置，得到附加考核分。
4.考核等级映射函数。将考核分值映射到对应的考核等级。
在本场景实施例中，演示了在API编排时通过参数适配装置实现相邻和非相邻间的API间参数适配；演示了在API编排时通过参数适配装置组合使用参数映射和自定义函数方式实现参数适配。并给出了参数适配装置的一种最佳实践，即自定义函数时，尽可能编写小而简的通用函数，便于后续在其他API编排过程中复用。
本发明实施例通过上述实施例，公开了一种API间的参数适配方法，以及用来实现API间的参数适配的参数适配装置。通过参数适配装置，用户可以通过参数直接映射、可视化内置库函数、自定义函数以及组合使用上述三种方式来进行API间参数适配。
参数直接映射方式描述：在界面上呈现所有前置API输出参数和后置API输入参数，为了方便用户查看，可以是一种树状的结构形式。用户可以通过拖、拽、点击、连线或者其他的界面操作将API间参数进行参数映射，完成参数的适配；
可视化内置库函数方式描述：界面提供详细的内置库函数列表，该列表可以包含各个内置库函数的名称、描述、输入输出参数详细信息、使用帮助等信息，用户选择内置库函数后，以界面化的形式呈现该内置库函数，用户通过拖、拽、点击、选择等方式将现有参数进行内置库函数处理，并得到新的参数。可用参数包含前置API的输出(子)参数、其他库函数生成的参数以及自定义函数生成的参数。
自定义函数方式描述：用户选择自定义函数方式后，可以通过界面化方式选择零个或多个可用参数作为输入参数，并指定输出参数的数据格式。可用参数包含前置API的输出(子)参数、其他库函数生成的参数以及自定义函数生成的参数。然后在代码编辑区域中编写函数处理逻辑从而最后生成新的参数。同时该编写的函数逻辑可以被保存到内置函数库中，方便后续的复用。
通过编写自定义函数可以不断丰富可视化函数库，随着可视化函数库能力的不断提升，需要编写自定义函数的情况越来越少，最终，一般的能力编排用户就可以完全通过可视化的两种方式(参数直接映射和可视化内置库函数)来完成API间参数适配。同时，通过不断组合嵌套使用内置库函数和自定义函数方式，可以产生足够复杂的参数转换逻辑，从而应对复杂的能力编排场景。
以上描述是本发明实施例公开的参数适配方法及参数适配装置的一种可能的界面呈现形式，但并非唯一的一种呈现形式，其他包含该类型的界面呈现形式也是本发明实施例的保护实现形式之一。比如，通过任何界面化的形式，组合使用参数直接映射和可视化内置库函数实现API编排API间参数适配；比如，通过任何界面化的形式，组合使用参数直接映射、可视化内置库函数以及自定义函数方式实现API编排API间参数适配；比如，通过任何界面化的形式，组合使用可视化内置库函数和自定义函数方式实现API编排API间参数适配。
本发明实施例提供的参数适配方法和参数适配装置，重点在于API编排API间参数适配装置，组合使用本发明实施例描述的参数直接映射、可视化内置库函数和自定义函数实现API间参数适配；以及API编排API间参数适配装置，通过编写自定义函数扩展内置库函数来实现装置能力迭代增强的操控过程；
本发明实施例与直接编写参数适配代码/脚本方式和编写配置信息实现API间输入输出 参数适配方法对比，本发明实施例以可视化的参数适配方式为主，简单易用、代码开发成本低、同时能高效解决复杂编排场景下的参数适配；与现有的完全依赖拖拽完成能力编排参数适配的方法对比。完全通过拖拽的方式，无法满足复杂业务场景，例如接口间的参数适配依赖于复杂计算，或依赖于业务专有运算逻辑的情况，不是一套完整的参数适配解决方案，具有编排使用场景的局限性。本发明实施例提供了低代码的API间参数适配装置，满足复杂编排场景使用需求，是一套能够解决复杂能力编排场景下接口间参数适配的完整解决方案，具有解决问题的完备性；本发明实施例的参数适配装置具有迭代增强机制：装置内自定义函数单元编码生成的函数可以持久化存储到内置库函数单元，迭代增强内置库函数单元的处理能力，同时这一机制还达到了编码技术人员与普通API编排人员分离的效果，并逐步降低对编码技术人员的依赖。任何行业需要使用到参数适配的情况，都可以使用本参数适配装置。
以上所述仅为本发明实施例的优选实施例而已，并不用于限制本发明实施例，对于本领域的技术人员来说，本发明实施例可以有各种更改和变化。凡在本发明实施例的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明实施例的保护范围之内。

Claims (10)

  1. 一种应用程序编程接口API间的参数适配方法，包括：
    解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；
    解析API编排中的后置API的输入参数，并在界面呈现所述输入参数；
    从所述参数池中的输出参数中选择与所述后置API的输入参数相适配的目标输出参数，或基于所述输出参数生成所述目标输出参数，并将所述目标输出参数与所述后置API的输入参数进行映射关联，以实现所述前置API与所述后置API间的参数适配。
  2. 根据权利要求1所述的方法，其中，所述基于输出参数生成所述目标输出参数包括：
    通过界面化方式采用内置库函数对所述输出参数进行函数处理以生成所述目标输出参数。
  3. 根据权利要求2所述的方法，其中，通过界面化方式采用内置库函数对所述输出参数进行函数处理以生成所述目标输出参数之前，还包括：
    通过编码方式自定义函数逻辑以生成新函数，并将生成的所述新函数作为内置库函数存储。
  4. 根据权利要求1所述的方法，其中，所述将目标输出参数与所述后置API的输入参数进行映射关联，包括：
    通过可视化操作将所述目标输出参数与所述后置API的输入参数进行映射关联。
  5. 一种应用程序编程接口参数适配装置，包括：
    第一解析模块，设置为解析API编排中的前置API的输出参数，将得到的输出参数放入参数池中并通过界面呈现；
    第二解析模块，设置为解析API编排中的后置API的输入参数，并在界面呈现所述输入参数；
    映射适配模块，设置为从所述参数池中的输出参数中选择与所述后置API的输入参数相适配的目标输出参数，或基于所述输出参数生成所述目标输出参数，并将所述目标输出参数与所述后置API的输入参数进行映射关联，以实现所述前置API与所述后置API间的参数适配。
  6. 根据权利要求5所述的装置，其中，所述映射适配模块，包括：
    内置函数单元，设置为通过界面化方式采用内置库函数对所述输出参数进行函数处理以生成所述目标输出参数。
  7. 根据权利要求5所述的装置，其中，所述映射适配模块，还包括：
    自定义函数单元，设置为通过编码方式自定义函数逻辑以生成新函数，并将生成的所述新函数作为内置库函数存储。
  8. 根据权利要求5所述的装置，其中，所述映射适配模块，还包括：
    映射单元，设置为通过可视化操作将所述目标输出参数与所述后置API的输入参数进行映射关联。
  9. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述权利要求1至4任一项所述的方法。
  10. 一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，所述处理器执行所述计算机程序时实现所述权利要求1至4任一项所述的方法。
PCT/CN2023/113574 2022-08-25 2023-08-17 应用程序编程接口api间的参数适配方法及装置 WO2024041446A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202211026581.7A CN117667031A (zh) 2022-08-25 2022-08-25 应用程序编程接口api间的参数适配方法及装置
CN202211026581.7 2022-08-25

Publications (1)

Publication Number Publication Date
WO2024041446A1 true WO2024041446A1 (zh) 2024-02-29

Family

ID=90012456

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/113574 WO2024041446A1 (zh) 2022-08-25 2023-08-17 应用程序编程接口api间的参数适配方法及装置

Country Status (2)

Country Link
CN (1) CN117667031A (zh)
WO (1) WO2024041446A1 (zh)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101034371A (zh) * 2006-03-09 2007-09-12 国际商业机器公司 用于测试方案的方法和装置
CN110688142A (zh) * 2019-10-10 2020-01-14 星环信息科技（上海）有限公司 应用程序编程接口的发布方法、设备及存储介质
US10540270B1 (en) * 2018-01-25 2020-01-21 Amazon Technologies, Inc. Representation-based automated software testing
CN110716738A (zh) * 2019-09-03 2020-01-21 无锡华云数据技术服务有限公司 数据处理方法、装置、云平台、电子设备及存储介质
CN110912724A (zh) * 2018-09-18 2020-03-24 亿阳信通股份有限公司 一种基于参数驱动的自动业务编排方法及装置
US20210216288A1 (en) * 2020-01-13 2021-07-15 Fujitsu Limited Api-based software development platform
CN114115841A (zh) * 2021-04-02 2022-03-01 北京沃东天骏信息技术有限公司 数据流接口动态编排方法、装置、设备、介质及程序产品

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101034371A (zh) * 2006-03-09 2007-09-12 国际商业机器公司 用于测试方案的方法和装置
US10540270B1 (en) * 2018-01-25 2020-01-21 Amazon Technologies, Inc. Representation-based automated software testing
CN110912724A (zh) * 2018-09-18 2020-03-24 亿阳信通股份有限公司 一种基于参数驱动的自动业务编排方法及装置
CN110716738A (zh) * 2019-09-03 2020-01-21 无锡华云数据技术服务有限公司 数据处理方法、装置、云平台、电子设备及存储介质
CN110688142A (zh) * 2019-10-10 2020-01-14 星环信息科技（上海）有限公司 应用程序编程接口的发布方法、设备及存储介质
US20210216288A1 (en) * 2020-01-13 2021-07-15 Fujitsu Limited Api-based software development platform
CN114115841A (zh) * 2021-04-02 2022-03-01 北京沃东天骏信息技术有限公司 数据流接口动态编排方法、装置、设备、介质及程序产品

Also Published As

Publication number Publication date
CN117667031A (zh) 2024-03-08

Similar Documents

Publication Publication Date Title
US11790904B2 (en) Voice application platform
US11615791B2 (en) Voice application platform
US20230154461A1 (en) Voice Application Platform
US10438264B1 (en) Artificial intelligence feature extraction service for products
CN107463601B (zh) 基于人工智能的对话理解系统构建方法、装置、设备及计算机可读存储介质
WO2016060547A1 (en) Emulating manual system of filing using electronic document and electronic file
US11437029B2 (en) Voice application platform
CN110309350B (zh) 背诵任务的处理方法、系统、装置、介质及电子设备
AU2018260876A1 (en) Real-time data input correction and facilitation of data entry at point of input
WO2022134583A1 (zh) 一种保险数据信息的生成方法、装置、服务器及存储介质
TW201923548A (zh) 產生對話式使用者介面的方法及系統
CN112199477A (zh) 对话管理方案和对话管理语料的构建方法
WO2024099457A1 (zh) 一种信息推荐方法、装置、存储介质及电子设备
Standridge et al. TESS—the extended simulation support system
CN107391119A (zh) 一种横竖屏实现方法及装置
CN107515866A (zh) 一种数据操作方法、装置和系统
AU2015331028A1 (en) Electronic processing system for electronic document and electronic file
CN107888989A (zh) 一种基于互联网直播的交互系统及方法
US20210124752A1 (en) System for Data Collection, Aggregation, Storage, Verification and Analytics with User Interface
WO2024041446A1 (zh) 应用程序编程接口api间的参数适配方法及装置
CN110222282A (zh) 数据处理方法、装置、服务器及存储介质
Chaganti et al. Amazon SimpleDB developer guide
CA3102093A1 (en) Voice application platform
US11651148B2 (en) Centralized and automated document generation and collection
CN115577085A (zh) 表格问答任务的处理方法及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23856536

Country of ref document: EP

Kind code of ref document: A1