Openability management method and device of API management system, equipment and storage medium

Abstract

The invention relates to an opening capability management method and device of an API management system, equipment and a storage medium. The method comprises the following steps: receiving an API service request sent by a user side, wherein the API service request comprises a performance requirement of a target service; predicting a candidate API and / or a candidate API calling combination corresponding to the target service according to the performance requirement of the target service; and receiving selection indication information sent by the user side, determining a target API from the candidate APIs, and / or determining a target API call combination from the candidate API call combinations. Receiving an authorization application request which is sent by the user side and aims at the target API and / or the target API calling combination; and auditing the authorization application request, and authorizing the target API and / or the target API call combination under the condition that the authorization application request passes. Therefore, a flexible API capability subscription and authorization mechanism can be provided for users, and individual requirements of different users are met.

Description

Technical Field

[0001] This application relates to the field of computer technology, and in particular to an open capability management method, apparatus, computer device, computer-readable storage medium, and computer program product of an API management system. Background Technology

[0002] An Application Programming Interface (API) is a set of definitions, procedures, and protocols that enable communication between computer software. A primary function of an API is to provide a common set of functionalities. Programmers can reduce their programming workload by calling API functions to develop applications.

[0003] In modern software development, APIs play a crucial role, acting as bridges between different software components and facilitating system interoperability and modularity. However, as software systems become increasingly complex, API management faces numerous challenges. Existing API management systems lack flexible capability subscription and authorization mechanisms, failing to meet the personalized needs of different users. Summary of the Invention

[0004] Therefore, it is necessary to provide an open capability management method, device, computer equipment, computer-readable storage medium, and computer program product for an API management system that can provide a flexible capability subscription and authorization mechanism to meet the personalized needs of different users, in order to address the above-mentioned technical problems.

[0005] Firstly, this application provides an open capability management method for an API management system, applied to an API management system, the method comprising:

[0006] Receive API service requests sent by the user client, wherein the API service requests contain the performance requirements of the target service;

[0007] Based on the performance requirements of the target service, the trained prediction model predicts the candidate APIs and / or combinations of candidate API calls corresponding to the target service.

[0008] The system receives selection indication information sent by the user terminal. The selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations.

[0009] Receive the authorization request sent by the user terminal for the target API and / or the combination of the target API calls;

[0010] The authorization request is reviewed, and if the authorization request is approved, the target API and / or the target API call combination is authorized so that the user can perform the target business by calling the target API and / or the target API call combination.

[0011] In one embodiment, the performance requirements of the target business include at least one of the following: API parameter complexity requirements, API running speed requirements, API stability requirements, and API historical usage count requirements;

[0012] After predicting candidate APIs and / or combinations of candidate API calls for the target service based on the performance requirements of the target service using a trained prediction model, the method further includes:

[0013] Based on the weights of the target service performance requirements set by the user, determine the performance of each candidate API and / or each combination of candidate API calls;

[0014] The candidate APIs and / or combinations of candidate API calls are ranked according to performance.

[0015] In one embodiment, the review of the authorization request includes:

[0016] The authorization application request is reviewed using a pre-established review model;

[0017] If the target API and / or the combination of target API calls meet the preset calling criteria, the authorization request is deemed approved.

[0018] In one embodiment, after authorizing the target API and / or the combination of target API calls, the method further includes:

[0019] According to the predetermined testing strategy, the authorized target API and / or the combination of target API calls are tested based on the pre-generated test cases to obtain the corresponding test results;

[0020] If the test results do not meet expectations, generate risk assessment results and debugging suggestions based on the debugging data of the target API and / or the combination of the target API calls;

[0021] If the test results meet expectations, monitor the target API and / or the combination of target API calls.

[0022] In one embodiment, monitoring the target API and / or the combination of target API calls includes:

[0023] Traffic anomaly prediction model is used to monitor the traffic of the target API and / or the combination of target API calls, and to predict in real time whether traffic anomalies will occur in the target API and / or the combination of target API calls.

[0024] If abnormal traffic is predicted for the target API and / or the combination of target API calls, the number of requests that invoke the target API and / or the combination of target API calls shall be limited.

[0025] In one embodiment, the method further includes:

[0026] The system displays the service status of each API in real time, and provides API list query controls and call limit setting controls; the service status includes any one of the following: normal, performance degradation, and maintenance; the API list query control is used to provide query functionality for the API list; the call limit setting control is used to provide functionality for setting the call limit upper limit and / or call strategy;

[0027] If the service status indicates performance degradation, increase the request timeout period or enable local caching;

[0028] If the service status is "under maintenance", a service interruption notification will be sent to the user's client.

[0029] In one embodiment, the method further includes:

[0030] Receive the unsubscribe request sent by the user client;

[0031] Based on the unsubscribe request, the authorization for the target API and / or the target API call combination is revoked, and monitoring of the target API and / or the target API call combination is stopped.

[0032] Secondly, this application also provides an open capability management device for an API management system, applied to an API management system, the device comprising:

[0033] The receiving module is used to receive API service requests sent by the user terminal, wherein the API service requests contain the performance requirements of the target service.

[0034] The prediction module is used to predict candidate APIs and / or combinations of candidate API calls for the target service based on the performance requirements of the target service using a trained prediction model.

[0035] The receiving module is further configured to receive selection indication information sent by the user terminal, wherein the selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations;

[0036] The receiving module is also configured to receive an authorization request sent by the user terminal for the target API and / or the combination of the target API calls;

[0037] The review module is used to review the authorization application request and, if the authorization application request is approved, authorize the target API and / or the target API call combination so that the user terminal can execute the target business by calling the target API and / or the target API call combination.

[0038] Thirdly, this application also provides a computer device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0039] Receive API service requests sent by the user client, wherein the API service requests contain the performance requirements of the target service;

[0040] Based on the performance requirements of the target service, the trained prediction model predicts the candidate APIs and / or combinations of candidate API calls corresponding to the target service.

[0041] The system receives selection indication information sent by the user terminal. The selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations.

[0042] Receive the authorization request sent by the user terminal for the target API and / or the combination of the target API calls;

[0043] The authorization request is reviewed, and if the authorization request is approved, the target API and / or the target API call combination is authorized so that the user can perform the target business by calling the target API and / or the target API call combination.

[0044] Fourthly, this application also provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, performs the following steps:

[0045] Receive API service requests sent by the user client, wherein the API service requests contain the performance requirements of the target service;

[0046] Based on the performance requirements of the target service, the trained prediction model predicts the candidate APIs and / or combinations of candidate API calls corresponding to the target service.

[0047] The system receives selection indication information sent by the user terminal. The selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations.

[0048] Receive the authorization request sent by the user terminal for the target API and / or the combination of the target API calls;

[0049] The authorization request is reviewed, and if the authorization request is approved, the target API and / or the target API call combination is authorized so that the user can perform the target business by calling the target API and / or the target API call combination.

[0050] Fifthly, this application also provides a computer program product, including a computer program that, when executed by a processor, performs the following steps:

[0051] Receive API service requests sent by the user client, wherein the API service requests contain the performance requirements of the target service;

[0052] Based on the performance requirements of the target service, the trained prediction model predicts the candidate APIs and / or combinations of candidate API calls corresponding to the target service.

[0053] The system receives selection indication information sent by the user terminal. The selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations.

[0054] Receive the authorization request sent by the user terminal for the target API and / or the combination of the target API calls;

[0055] The authorization request is reviewed, and if the authorization request is approved, the target API and / or the target API call combination is authorized so that the user can perform the target business by calling the target API and / or the target API call combination.

[0056] The aforementioned API management system's open capability management method, apparatus, computer equipment, computer-readable storage medium, and computer program product receive API service requests sent by user clients, which contain the performance requirements of the target service. This allows the system to request API calls based on the actual needs of the user's service. A trained prediction model predicts candidate APIs and / or candidate API call combinations corresponding to the target service based on its performance requirements, thus predicting the APIs to be called and preventing users from requesting APIs that exceed system resources. The system receives selection instruction information sent by the user client, which is used to determine the target API corresponding to the target service from the candidate APIs, and / or the target API call combination corresponding to the target service from the candidate API call combinations. This allows users to select the most suitable target API and / or target API call combination, improving API usage efficiency. The system also receives authorization request requests from the user client for the target API and / or target API call combination; reviews the authorization request; and, if the authorization request is approved, authorizes the target API and / or target API call combination, enabling the user client to execute the target service by calling the target API and / or the target API call combination. This allows for a flexible API subscription and authorization mechanism to meet the personalized needs of different users. Attached Figure Description

[0057] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the drawings used in the description of the embodiments of this application or related technologies will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0058] Figure 1 This is an application environment diagram of the open capability management method of the API management system in one embodiment;

[0059] Figure 2 This is a flowchart illustrating the open capability management method of an API management system in one embodiment;

[0060] Figure 3 This is a flowchart illustrating the open capability management method of the API management system in another embodiment;

[0061] Figure 4 This is a flowchart illustrating the open capability management method of the API management system in yet another embodiment;

[0062] Figure 5This is a flowchart illustrating the open capability management method of the API management system in the fourth embodiment;

[0063] Figure 6 This is a flowchart illustrating the open capability management method of the API management system in the fifth embodiment;

[0064] Figure 7 This is a structural block diagram of the open capability management device of the API management system in one embodiment;

[0065] Figure 8 This is a structural block diagram of the open capability management device of the API management system in another embodiment;

[0066] Figure 9 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0067] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0068] It should be noted that the terms "first," "second," etc., used in this application can be used to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish the first element from the second element. The terms "comprising" and "having," and any variations thereof, used in this application, are intended to cover non-exclusive inclusion. The term "multiple" used in this application refers to two or more. The term "and / or" used in this application refers to one of the embodiments, or any combination of multiple embodiments.

[0069] The open capability management method of the API management system provided in this application embodiment can be applied to, for example... Figure 1In the application environment shown, client 102 communicates with server 104 via a network. The API management system can be integrated into server 104 or located on the cloud or other network servers. The API management system in server 104 receives API service requests sent by client 102, which contain performance requirements for the target service; it uses a trained prediction model to predict candidate APIs and / or candidate API call combinations corresponding to the target service based on the performance requirements; it receives selection instruction information sent by the client, which is used to determine the target API corresponding to the target service from the candidate APIs, and / or the target API call combination corresponding to the target service from the candidate API call combinations; it receives authorization request requests from the client for the target API and / or the target API call combination; it reviews the authorization request requests, and if the authorization request is approved, it authorizes the target API and / or the target API call combination, enabling the client to execute the target service by calling the target API and / or the target API call combination. The user terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, drones, low-altitude aircraft, IoT devices, and portable wearable devices. IoT devices can include smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, and projection equipment. Portable wearable devices can include smartwatches, smart bracelets, and head-mounted displays. Head-mounted displays can be virtual reality (VR) devices, augmented reality (AR) devices, and smart glasses. The server 104 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing cloud computing services.

[0070] Existing API management systems lack flexible capability subscription and authorization mechanisms. Specifically, users cannot selectively subscribe to and use specific API capabilities according to their needs, and there is a lack of granular management and control over API usage. This leads to the following problems: 1) Users may be forced to subscribe to unnecessary APIs, resulting in wasted resources; 2) The inability to effectively restrict and monitor API usage may lead to abuse; 3) The lack of unified management of API authorization increases security risks. These problems mainly stem from the fact that traditional API management systems often adopt a one-size-fits-all approach, failing to meet the personalized needs of different users and lacking a granular control mechanism for API usage.

[0071] To address the problems existing in the prior art, this application aims to provide an open capability management method for an API management system. This method manages multiple functions of the API management system through multiple models, ensuring the accuracy, timeliness, efficiency of debugging, and comprehensiveness and depth of testing. For example, it analyzes and monitors API calls to determine if API traffic is abnormal, thus deciding whether authorization is possible. Based on user business needs and a business needs prediction model, it obtains a list of API call combinations matching those needs. Then, based on the performance requirements of those needs, it selects and outputs the API call combination that best suits the business requirements, thereby improving the efficiency and accuracy of selecting the API combination corresponding to the business needs. Furthermore, it enables API management within the API management system, such as API list querying, API status display, API call volume limit setting, and API activation and deactivation operations, further improving the efficiency of API interface management.

[0072] In one exemplary embodiment, such as Figure 2 As shown, an open capability management method for an API management system is provided, which is applied to... Figure 1 Taking the server in the example, the explanation includes the following steps 201 to 205. Wherein:

[0073] Step 201: Receive API service requests sent by the user.

[0074] The user terminal can be any device used by the user, such as a mobile phone, laptop, computer, and various portable smart devices. The user terminal can interact with the API management system.

[0075] For example, users can browse available API capabilities through the API management system's interface, and then select and subscribe to the corresponding APIs according to their business needs. Optionally, the API management system can record subscription information and associate it with the user's application.

[0076] The API service request includes the performance requirements of the target business. This API service request is used to request the API management system to recommend candidate APIs and / or candidate API call combinations that correspond to the performance requirements of the target business.

[0077] Optionally, the combination of candidate API calls may include calls between multiple APIs.

[0078] For example, the performance requirements of the target business include at least one of the following: API parameter complexity requirements, API running speed requirements, API stability requirements, and API historical usage requirements.

[0079] Step 202: Based on the performance requirements of the target business, use the trained prediction model to predict the candidate APIs and / or combinations of candidate API calls corresponding to the target business.

[0080] In this embodiment, the business prediction and recommendation function of the API management system can be used. Through deep learning models, such as Convolutional Neural Networks (CNN) and Recurrent Neural Networks (RNN), the deep learning model can perform word segmentation on the business requirements, obtain the word segmentation results, and predict the API call content of the business request.

[0081] For example, the prediction module can train the prediction model by collecting historical business data from the database to obtain a better prediction model. During training, the neural network model can be trained using backpropagation with the cross-entropy loss function or the mean squared error (MSE) loss function, and the model parameters can be optimized using optimization algorithms. Step size decay and exponential decay can be used to improve the convergence speed of the model, finally obtaining a well-trained prediction model. In addition, users can also upload API services and / or combinations of API services corresponding to their previous business needs to further train the prediction model, which can better predict the required candidate APIs and / or combinations of candidate API calls.

[0082] Step 203: Receive selection instruction information sent by the user terminal.

[0083] The selection indication information is used to determine the target API corresponding to the target business from the candidate APIs, and / or to determine the target API call combination corresponding to the target business from the candidate API call combination.

[0084] In this embodiment, the API management system provides the predicted candidate APIs and / or candidate API call combinations to the user terminal, and the user can select the appropriate target API and / or target API call combination on the user terminal's display interface.

[0085] It should be understood that different candidate API call combinations include different APIs, and therefore each candidate API call combination has different performance. Based on the performance requirements of the target business, the API call combination that matches the performance requirements of the target business can be selected from the candidate API call combinations as the API call combination for the target business.

[0086] Step 204: Receive an authorization request from the user client for the target API and / or a combination of target API calls.

[0087] In this embodiment, after selecting a suitable target API and / or a combination of target API calls, the user can submit an authorization request to the API management system. The API management system administrator can review the authorization request for the target API and / or the combination of API calls. Optionally, the administrator can review the authorization request using an auditing model to determine whether the authorization request complies with the API calling standards; if it does, the authorization request is approved.

[0088] Step 205: Review the authorization request and, if the authorization request is approved, authorize the target API and / or the combination of target API calls.

[0089] In this embodiment, the administrator of the API management system can manage the approval process. For example, if a user's subscription application is included in the administrator's approval process, the API management system can call the API's authorization interface to authorize it after the administrator approves it.

[0090] For example, authorization requests can be reviewed using a pre-established review model; if the target API and / or the combination of target API calls meet the preset calling criteria, the authorization request is deemed approved.

[0091] It should be understood that authorization can be divided into two levels: capability authorization and API authorization. Capability authorization refers to the process when a user subscribes to a specific digital intelligence capability, while API authorization is the process when a user activates a specific API. Both types of authorization require interaction with the digital intelligence service.

[0092] In the open capability management method of the aforementioned API management system, API service requests sent by user clients are received. These requests contain the performance requirements of the target service, allowing API calls to be requested based on the actual needs of the user's business. A trained prediction model predicts candidate APIs and / or combinations of candidate API calls based on the performance requirements of the target service, thus predicting the APIs to be called and preventing users from requesting APIs that exceed system resources. Selection instructions sent by user clients are received, used to determine the target API and / or the target API call combination from the candidate APIs. This allows users to select the most suitable target API and / or target API call combination, improving API usage efficiency. Authorization requests for the target API and / or target API call combination are received from user clients. These requests are reviewed, and if approved, authorization is granted to the target API and / or target API call combination, enabling users to execute the target service by calling the target API and / or target API call combination. This provides a flexible API capability subscription and authorization mechanism to meet the personalized needs of different users.

[0093] In another exemplary embodiment, such as Figure 3 As shown, an open capability management method for an API management system is provided, which is applied to... Figure 1 Taking the server in the example, the explanation includes the following steps 301 to 307. Wherein:

[0094] Step 301: Receive API service requests sent by the user client.

[0095] The user end can be any device used by the user, such as mobile phones, laptops, computers, and various portable smart devices.

[0096] The API business requests contain the performance requirements of the target business.

[0097] Step 302: Based on the performance requirements of the target business, use the trained prediction model to predict the candidate APIs and / or combinations of candidate API calls corresponding to the target business.

[0098] For the specific implementation process and technical effects of steps 301-302 in this embodiment, please refer to [link to documentation]. Figure 2 The relevant descriptions of steps 201 to 202 in the method embodiment shown will not be repeated here.

[0099] Step 303: Based on the weights of the target business performance requirements set on the user side, determine the performance of each candidate API and / or each candidate API call combination.

[0100] In this embodiment, users can set weights for different types of performance requirements of the business based on actual conditions, calculate the performance of each candidate API and / or each candidate API call combination in the candidate API and / or candidate API call combination list according to the weights, and select the API and / or API call combination that meets the performance requirements as the API call combination of the target business.

[0101] Step 304: Sort the candidate APIs and / or combinations of candidate API calls according to performance.

[0102] In this embodiment, the candidate API and / or candidate API call combination list can also be sorted by performance, and the candidate API and / or candidate API call combination with the highest performance can be used as the API call combination for the target business.

[0103] Step 305: Receive selection instruction information sent by the user terminal.

[0104] The selection indication information is used to determine the target API corresponding to the target business from the candidate APIs, and / or to determine the target API call combination corresponding to the target business from the candidate API call combination.

[0105] Step 306: Receive an authorization request sent by the user client for the target API and / or a combination of target API calls.

[0106] Step 307: Review the authorization request and, if the authorization request is approved, authorize the target API and / or the combination of target API calls.

[0107] For the specific implementation process and technical effects of steps 305-307 in this embodiment, please refer to [link to documentation]. Figure 2 The relevant descriptions of steps 203 to 205 in the method embodiment shown will not be repeated here.

[0108] In yet another exemplary embodiment, such as Figure 4 As shown, an open capability management method for an API management system is provided, which is applied to... Figure 1 Taking the server in the example, the explanation includes the following steps 401 to 408. Wherein:

[0109] Step 401: Receive API service requests sent by the user client.

[0110] The user end can be any device used by the user, such as mobile phones, laptops, computers, and various portable smart devices.

[0111] The API business requests contain the performance requirements of the target business.

[0112] For example, the performance requirements of the target business include at least one of the following: API parameter complexity requirements, API running speed requirements, API stability requirements, and API historical usage requirements.

[0113] Step 402: Based on the performance requirements of the target business, use the trained prediction model to predict the candidate APIs and / or combinations of candidate API calls corresponding to the target business.

[0114] Step 403: Receive selection instruction information sent by the user terminal.

[0115] The selection indication information is used to determine the target API corresponding to the target business from the candidate APIs, and / or to determine the target API call combination corresponding to the target business from the candidate API call combination.

[0116] Step 404: Receive an authorization request sent by the user client for the target API and / or a combination of target API calls.

[0117] Step 405: Review the authorization request and, if the authorization request is approved, authorize the target API and / or the combination of target API calls.

[0118] For the specific implementation process and technical effects of steps 401 to 405 in this embodiment, please refer to [link to documentation]. Figure 2 The relevant descriptions of steps 201 to 205 in the method embodiment shown will not be repeated here.

[0119] Step 406: According to the predetermined testing strategy, test the authorized target API and / or the combination of target API calls based on the pre-generated test cases to obtain the corresponding test results.

[0120] In this embodiment, after obtaining authorization, the user can utilize the target API and / or a combination of target API calls to meet business requirements. Prior to this, API test cases can be generated in advance using a generative adversarial network-based test case generator, and executed according to a predetermined test strategy to obtain test results for the target API and / or the combination of target API calls.

[0121] Step 407: If the test results do not meet expectations, generate risk assessment results and debugging suggestions based on the debugging data of the target API and / or the combination of target API calls.

[0122] Step 408: If the test results meet expectations, monitor the target API and / or the combination of target API calls.

[0123] In this embodiment, the test results of the target API and / or the target API call combination are used to determine whether the target API and / or the target API call combination can achieve good results. If the test results do not meet expectations, a risk assessment result and debugging suggestions are generated based on the debugging data. If the test results meet expectations, the target API and / or the target API call combination can be monitored through the API management module.

[0124] In this embodiment, steps 407 and 408 are optional steps, and there is no restriction on the execution order.

[0125] For example, a traffic anomaly prediction model can be used to monitor the traffic of a target API and / or a combination of target API calls, and predict in real time whether traffic anomalies will occur in the target API and / or the combination of target API calls; if traffic anomalies are predicted to occur in the target API and / or the combination of target API calls, the number of requests that call the target API and / or the combination of target API calls can be limited.

[0126] Optionally, traffic monitoring of API call combinations can be performed using a traffic anomaly prediction model. Historical API traffic data can be trained using a regression model to obtain the traffic anomaly prediction model. This model can then predict in real time whether the requested target API and / or target API call combination will experience traffic anomalies. If the target API and / or target API call combination is predicted to experience traffic anomalies, the API management system will limit the number of requests that invoke that target API and / or target API call combination.

[0127] It should be understood that for traffic anomaly prediction models, statistical traffic flow corresponding to each time period can be used as the dependent variable to establish multiple regression models. These regression models mainly include linear regression equations. By establishing multiple regression equations and discovering the intrinsic relationship between the dependent and independent variables, a linear function of the dependent and independent variables is constructed for fitting. Multiple regression models are then screened based on the confidence level (R-squared) and root mean square error (RMSE) of each model. This mainly involves selecting regression equations with a confidence level (R-squared) > 0.5 and an RMSE < 0.08, thereby predicting future traffic data.

[0128] In the fourth exemplary embodiment, such as Figure 5 As shown, an open capability management method for an API management system is provided, which is applied to... Figure 1Taking the server in the example, the explanation includes the following steps 501 to 508. Wherein:

[0129] Step 501: Receive API service requests sent by the user client.

[0130] The user end can be any device used by the user, such as mobile phones, laptops, computers, and various portable smart devices.

[0131] The API business requests contain the performance requirements of the target business.

[0132] For example, the performance requirements of the target business include at least one of the following: API parameter complexity requirements, API running speed requirements, API stability requirements, and API historical usage requirements.

[0133] Step 502: Based on the performance requirements of the target business, use the trained prediction model to predict the candidate APIs and / or combinations of candidate API calls corresponding to the target business.

[0134] Step 503: Receive selection instruction information sent by the user terminal.

[0135] The selection indication information is used to determine the target API corresponding to the target business from the candidate APIs, and / or to determine the target API call combination corresponding to the target business from the candidate API call combination.

[0136] Step 504: Receive an authorization request sent by the user client for the target API and / or a combination of target API calls.

[0137] Step 505: Review the authorization request and, if the authorization request is approved, authorize the target API and / or the combination of target API calls.

[0138] For the specific implementation process and technical effects of steps 501 to 505 in this embodiment, please refer to [link to documentation]. Figure 2 The relevant descriptions of steps 201 to 205 in the method embodiment shown will not be repeated here.

[0139] Step 506: Display the service status of each API in real time, and provide API list query controls and call limit setting controls.

[0140] The service status includes any of the following: normal, performance degradation, and maintenance; the API list query control provides the function of querying the API list; the call limit setting control provides the function of setting the call limit limit and / or call strategy.

[0141] Step 507: If the service status is degraded, increase the request timeout or enable local caching.

[0142] Step 508: If the service status is under maintenance, send a service interruption notification to the user's client.

[0143] In this embodiment, step 506 can be executed before or after any of steps 501 to 505, and steps 507 and 508 are optional steps, so there is no restriction on the execution order.

[0144] In this embodiment, the API management system can provide functions such as API list query, status display, and call limit settings. Users can view detailed information about subscribed APIs, including service status and usage restrictions.

[0145] For example, by displaying the service status of each API in real time, users can quickly understand the API's availability, such as a weather forecast application subscribing to a meteorological data API. Through the API status display feature, application developers can view the API's status in real time, such as "normal," "performance degradation," or "under maintenance." If the status shows "performance degradation," developers can take proactive measures, such as increasing request timeouts or enabling local caching, to ensure the application's normal operation. Conversely, if the API status is "under maintenance," developers can promptly notify users of potential service interruptions, improving the user experience.

[0146] For example, the call limit settings control provides fine-grained control over API usage, helping to prevent API abuse and excessive resource consumption. For instance, free users might be limited to 1,000 calls per day, while paid users might be limited to 10,000 calls. With the API call limit feature, users can clearly see these limits and monitor their usage in real time. If a free user finds their call volume approaching the daily limit, they can choose to upgrade to a paid account for a higher limit or optimize their calling strategy to avoid exceeding the limit.

[0147] In the fifth exemplary embodiment, such as Figure 6 As shown, an open capability management method for an API management system is provided, which is applied to... Figure 1 Taking the server in the example, the explanation includes the following steps 601 to 607. Wherein:

[0148] Step 601: Receive API service requests sent by the user client.

[0149] The user end can be any device used by the user, such as mobile phones, laptops, computers, and various portable smart devices.

[0150] The API business requests contain the performance requirements of the target business.

[0151] For example, the performance requirements of the target business include at least one of the following: API parameter complexity requirements, API running speed requirements, API stability requirements, and API historical usage requirements.

[0152] Step 602: Based on the performance requirements of the target business, use the trained prediction model to predict the candidate APIs and / or combinations of candidate API calls corresponding to the target business.

[0153] Step 603: Receive selection instruction information sent by the user terminal.

[0154] The selection indication information is used to determine the target API corresponding to the target business from the candidate APIs, and / or to determine the target API call combination corresponding to the target business from the candidate API call combination.

[0155] Step 604: Receive an authorization request sent by the user client for the target API and / or a combination of target API calls.

[0156] Step 605: Review the authorization request and, if the authorization request is approved, authorize the target API and / or the combination of target API calls.

[0157] For the specific implementation process and technical effects of steps 601 to 605 in this embodiment, please refer to [link to documentation]. Figure 2 The relevant descriptions of steps 201 to 205 in the method embodiment shown will not be repeated here.

[0158] Step 606: Receive the unsubscribe request sent by the user.

[0159] Step 607: Based on the unsubscribe request, revoke the authorization of the target API and / or the target API call combination, and stop monitoring the target API and / or the target API call combination.

[0160] For example, users can choose to enable or unsubscribe from an API. Once enabled, the API management system will begin monitoring API usage; once unsubscribed, the relevant monitoring information will no longer be visible.

[0161] For example, an application subscribes to user authentication capabilities, which include three APIs: "Mobile Number Verification," "Email Verification," and "Social Media Account Verification." Initially, the application only enables the "Mobile Number Verification" API. As business grows, the application decides to add email registration functionality, at which point it can use the API enable function to activate the "Email Verification" API. Later, if the application decides to discontinue email registration, it can use the API cancel function to disable the "Email Verification" API while maintaining the normal operation of the other APIs. This flexibility allows the application to adjust its functionality according to actual needs and user preferences, while optimizing API usage costs.

[0162] For example, the API management system is applied to the above. Figures 2-6 The various method embodiments shown can be divided into the following functional modules: capability subscription module, application association module, approval process module, API management module, API activation module, usage and monitoring module, and unsubscription module.

[0163] Taking a user wanting to use the SMS sending function in their app as an example, the developer logs into the API management system, browses the list of available API capabilities, and then finds the "SMS Service" capability through the capability subscription module and applies for a subscription. The API management system prompts the developer to select the application to associate. The developer selects their "Online Store" application through the application association module. Through the approval process module, the developer's subscription application is added to the administrator's approval queue. After the administrator approves it, the API management system automatically calls the API authorization interface of the digital intelligence service to authorize the "SMS Service" capability for the developer's "Online Store" application. After successful authorization, the developer can view the specific API list under "SMS Service" in the API management system through the API management module, such as "Send SMS" and "Query SMS Status". They can see the service status and call limits of each API. If the developer decides to activate the "Send SMS" API, they interact with the digital intelligence service again through the API activation module to complete the authorization of that specific API. Through the usage and monitoring modules, the developer can use the "Send SMS" API in the "Online Store" application and can also view the API usage and status in real time in the system. Finally, if developers decide to discontinue using the SMS service, they can unsubscribe through the unsubscribe module in the API management system. The API management system will then automatically revoke the relevant API authorization and stop monitoring.

[0164] In summary, the method in this application can predict the API and / or API call combination corresponding to the performance requirements of the target business using a predictive model, and obtain the most suitable target API and / or target API call combination based on user selection or performance ranking, thereby improving the efficiency and accuracy of selecting the target API and / or target API call combination corresponding to the performance requirements of the target business. The API management system's auditors can use the audit prediction model to predict the target API and / or target API call combination and determine whether it can pass the audit, preventing users from requesting target APIs and / or target API call combinations that exceed system resources. Furthermore, the test results of the target API and / or target API call combination can be obtained through adversarial networks. If the test results meet expectations, the target API and / or target API call combination can be used, thereby improving API usage efficiency. In addition, users can use a traffic anomaly prediction model to monitor the traffic of the target API and / or target API call combination, improving the monitoring efficiency of the target API and / or target API call combination and reducing manual maintenance costs.

[0165] It should be understood that although the steps in the flowcharts of the above embodiments are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages in other steps. It is understood that the steps in different embodiments can be freely combined as needed, and all non-contradictory solutions formed by such combinations are within the scope of protection of this application.

[0166] Based on the same inventive concept, this application also provides an open capability management device for implementing the open capability management method of the API management system described above. The solution provided by this device is similar to the implementation described in the above method. Therefore, the specific limitations of one or more embodiments of the open capability management device for the API management system provided below can be found in the limitations of the open capability management method for the API management system described above, and will not be repeated here.

[0167] In one exemplary embodiment, such as Figure 7As shown, an open capability management device for an API management system is provided, comprising: a receiving module 701, a prediction module 702, and an approval module 703, wherein:

[0168] The receiving module 701 is used to receive API service requests sent by the user terminal. The API service requests contain the performance requirements of the target service.

[0169] Prediction module 702 is used to predict candidate APIs and / or combinations of candidate API calls for the target business based on the performance requirements of the target business using a trained prediction model.

[0170] The receiving module 701 is also used to receive selection indication information sent by the user terminal. The selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations.

[0171] The receiving module 701 is also used to receive an authorization request sent by the user terminal for the target API and / or the combination of target API calls;

[0172] The review module 703 is used to review authorization request requests and, if the authorization request is approved, authorize the target API and / or the combination of target API calls so that the client can execute the target business by calling the target API and / or the combination of target API calls.

[0173] For example, the performance requirements of the target business include at least one of the following: API parameter complexity requirements, API running speed requirements, API stability requirements, and API historical usage requirements.

[0174] In another exemplary embodiment, such as Figure 8 As shown, an open capability management device for an API management system is provided. Figure 7 Based on the device shown, it may further include: a determining module 704, used to determine the performance of each candidate API and / or each candidate API call combination based on the weights of various performance requirements of the target service set by the user terminal; and to sort the candidate APIs and / or candidate API call combinations according to performance.

[0175] For example, the review module 703 is specifically used to: review the authorization application request through a pre-established review model; and determine that the authorization application request is approved if the target API and / or the target API call combination meets the preset call criteria.

[0176] For example, it may also include: a test module 705, configured to test the authorized target API and / or target API call combination based on pre-generated test cases according to a predetermined test strategy, and obtain corresponding test results; if the test results do not meet expectations, generate risk assessment results and debugging suggestions based on the debugging data of the target API and / or target API call combination; if the test results meet expectations, monitor the target API and / or target API call combination.

[0177] For example, monitoring the target API and / or the target API call combination includes: monitoring the traffic of the target API and / or the target API call combination through a traffic anomaly prediction model, and predicting in real time whether the target API and / or the target API call combination will experience traffic anomalies; and limiting the number of requests that call the target API and / or the target API call combination when it is predicted that traffic anomalies will occur.

[0178] For example, it may also include: a display module 706, used to display the service status of each API in real time, and to provide an API list query control and a call limit setting control; the service status includes any one of: normal, performance degradation, and maintenance; the API list query control is used to provide query functionality for the API list; the call limit setting control is used to provide setting functionality for the call limit upper limit and / or call strategy; when the service status is performance degradation, the request timeout time is increased or local caching is enabled; when the service status is maintenance, a service interruption prompt is sent to the user.

[0179] For example, it may also include: a subscription cancellation module 707, configured to receive a cancellation request sent by the user; and, based on the cancellation request, cancel the authorization of the target API and / or the target API call combination, and stop monitoring the target API and / or the target API call combination.

[0180] The modules in the open capability management device of the aforementioned API management system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device in hardware form, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0181] In one exemplary embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 9As shown, the computer device includes a processor, memory, input / output interfaces, a communication interface, a display unit, and an input device. The processor, memory, and input / output interfaces are connected via a system bus, and the communication interface, display unit, and input device are also connected to the system bus via the input / output interfaces. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The input / output interfaces are used for exchanging information between the processor and external devices. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, Near Field Communication (NFC), or other technologies. When the computer program is executed by the processor, it implements an open capability management method for an API management system. The display unit is used to form a visually visible image and can be a display screen, a projection device, or a virtual reality imaging device. The display screen can be an LCD screen or an e-ink screen. The input device of the computer device can be a touch layer covering the display screen, or buttons, trackballs, or touchpads set on the casing of the computer device, or external keyboards, touchpads, or mice, etc.

[0182] Those skilled in the art will understand that Figure 9 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0183] In one exemplary embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0184] The system receives API service requests from the client, which include performance requirements for the target service. Based on these performance requirements, it uses a trained prediction model to predict candidate APIs and / or combinations of candidate API calls for the target service. It also receives selection instructions from the client to determine the target API from the candidate APIs and / or the target API call combination from the candidate API call combinations. Furthermore, it receives authorization requests from the client for the target API and / or the target API call combination. The system reviews these authorization requests and, if approved, authorizes the target API and / or the target API call combination, enabling the client to execute the target service by calling the target API and / or the target API call combination.

[0185] In one embodiment, the performance requirements of the target business include at least one of the following: API parameter complexity requirements, API execution speed requirements, API stability requirements, and API historical usage count requirements; the processor also performs the following steps when executing the computer program:

[0186] After predicting the candidate APIs and / or combinations of candidate API calls for the target business based on the performance requirements of the target business using a trained prediction model, the performance of each candidate API and / or combination of candidate API calls is determined based on the weights of the various performance requirements of the target business set by the user. The candidate APIs and / or combinations of candidate API calls are then ranked according to their performance.

[0187] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0188] The authorization request is reviewed using a pre-established review model; if the target API and / or the combination of target API calls meet the preset calling criteria, the authorization request is approved.

[0189] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0190] According to the predetermined testing strategy, the authorized target API and / or target API call combination are tested based on the pre-generated test cases to obtain the corresponding test results; if the test results do not meet expectations, risk assessment results and debugging suggestions are generated based on the debugging data of the target API and / or target API call combination; if the test results meet expectations, the target API and / or target API call combination are monitored.

[0191] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0192] Traffic anomaly prediction models are used to monitor the target API and / or the combination of target API calls, and to predict in real time whether traffic anomalies will occur in the target API and / or the combination of target API calls. If traffic anomalies are predicted in the target API and / or the combination of target API calls, the number of requests that call the target API and / or the combination of target API calls will be limited.

[0193] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0194] The system displays the service status of each API in real time, and provides API list query controls and call limit setting controls. Service status includes any of the following: normal, performance degradation, and maintenance. The API list query control provides query functionality for the API list. The call limit setting control provides the function to set the call limit limit and / or call strategy. When the service status is performance degradation, the system increases the request timeout time or enables local caching. When the service status is maintenance, the system sends a service interruption notification to the user.

[0195] In one embodiment, the processor, when executing a computer program, also performs the following steps:

[0196] Receive unsubscribe requests from the client; based on the unsubscribe requests, revoke authorization for the target API and / or the target API call combination, and stop monitoring the target API and / or the target API call combination.

[0197] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method steps of the various embodiments described above.

[0198] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the method steps of the various embodiments described above.

[0199] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of the relevant data must comply with relevant regulations.

[0200] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, artificial intelligence (AI) processors, etc., and are not limited to these.

[0201] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0202] The above embodiments are merely illustrative of several implementation methods of this application, and their descriptions are relatively specific and detailed. However, they should not be construed as limiting the scope of this application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A method for managing the open capabilities of an API management system, characterized in that, Applied to an API management system, the method includes: Receive API service requests sent by the user client, wherein the API service requests contain the performance requirements of the target service; Based on the performance requirements of the target service, the trained prediction model predicts the candidate APIs and / or combinations of candidate API calls corresponding to the target service. The system receives selection indication information sent by the user terminal. The selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations. Receive the authorization request sent by the user terminal for the target API and / or the combination of the target API calls; The authorization request is reviewed, and if the authorization request is approved, the target API and / or the target API call combination is authorized so that the user can perform the target business by calling the target API and / or the target API call combination.

2. The method according to claim 1, characterized in that, The performance requirements of the target business include at least one of the following: API parameter complexity requirements, API running speed requirements, API stability requirements, and API historical usage count requirements. After predicting candidate APIs and / or combinations of candidate API calls for the target service based on the performance requirements of the target service using a trained prediction model, the method further includes: Based on the weights of the target service performance requirements set by the user, determine the performance of each candidate API and / or each combination of candidate API calls; The candidate APIs and / or combinations of candidate API calls are ranked according to performance.

3. The method according to claim 1, characterized in that, The review of the authorization application request includes: The authorization application request is reviewed using a pre-established review model; If the target API and / or the combination of target API calls meet the preset calling criteria, the authorization request is deemed approved.

4. The method according to claim 1, characterized in that, After authorizing the target API and / or the combination of target API calls, the method further includes: According to the predetermined testing strategy, the authorized target API and / or the combination of target API calls are tested based on the pre-generated test cases to obtain the corresponding test results; If the test results do not meet expectations, generate risk assessment results and debugging suggestions based on the debugging data of the target API and / or the combination of the target API calls; If the test results meet expectations, monitor the target API and / or the combination of target API calls.

5. The method according to claim 4, characterized in that, Monitoring the target API and / or combinations of target API calls includes: Traffic anomaly prediction model is used to monitor the traffic of the target API and / or the combination of target API calls, and to predict in real time whether traffic anomalies will occur in the target API and / or the combination of target API calls. If abnormal traffic is predicted for the target API and / or the combination of target API calls, the number of requests that invoke the target API and / or the combination of target API calls shall be limited.

6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: The system displays the service status of each API in real time, and provides API list query controls and call limit setting controls; the service status includes any one of the following: normal, performance degradation, and maintenance; the API list query control is used to provide query functionality for the API list; the call limit setting control is used to provide functionality for setting the call limit upper limit and / or call strategy; If the service status indicates performance degradation, increase the request timeout or enable local caching; If the service status is "under maintenance", a service interruption notification will be sent to the client.

7. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive the unsubscribe request sent by the user client; Based on the unsubscribe request, the authorization for the target API and / or the target API call combination is revoked, and monitoring of the target API and / or the target API call combination is stopped.

8. An open capability management device for an API management system, characterized in that, The device, used in an API management system, includes: The receiving module is used to receive API service requests sent by the user terminal, wherein the API service requests contain the performance requirements of the target service. The prediction module is used to predict candidate APIs and / or combinations of candidate API calls for the target service based on the performance requirements of the target service using a trained prediction model. The receiving module is further configured to receive selection indication information sent by the user terminal, wherein the selection indication information is used to determine the target API corresponding to the target service from the candidate APIs, and / or to determine the target API call combination corresponding to the target service from the candidate API call combinations; The receiving module is also configured to receive an authorization request sent by the user terminal for the target API and / or the combination of the target API calls; The review module is used to review the authorization application request and, if the authorization application request is approved, authorize the target API and / or the target API call combination so that the user terminal can execute the target business by calling the target API and / or the target API call combination.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

Images