Cloud-based API service provision system, and method thereof
The cloud-based API service system addresses response delays by separating control and data planes, enabling efficient API execution and improving user satisfaction through independent scaling and integration of AI-based APIs.
Patent Information
- Application Number
- PCT/KR2024/007292
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-31
- Filing Date
- 2024-05-29
- Publication Date
- 2024-12-05
AI Technical Summary
Cloud-based API service systems face response delays and deteriorated service quality due to increased traffic, as operation and processing functions are combined on a single plane, leading to decreased user satisfaction.
Implementing a cloud-based API service system with a separation of control and data planes, where authentication and management functions are handled by the control plane, and API execution is performed by the data plane, utilizing a cloud management console, API manager, and API execution engine, allowing for efficient processing of API calls without going through the control plane.
This separation of functions prevents response delays even with increased traffic, improving service quality and user satisfaction by ensuring that processing functions can scale independently, and integrating AI-based APIs enhances user experience.
Smart Images

Figure KR2024007292_05122024_PF_FP_ABST
Abstract
Description
Cloud-based API service provision system and method thereof
[0001] The present disclosure relates to a cloud-based API (Application Programming Interface) service providing system and method thereof.
[0002] As cloud technology becomes more widespread, systems (or platforms) offering cloud-based API (Application Programming Interface) services are emerging. These systems offer APIs for services difficult for general users to implement (e.g., those requiring high development complexity or significant development costs) and generate significant revenue through billing based on factors such as the number of API calls.
[0003] However, in systems like the above, the cloud-based API service's operational (or control / management) functions (e.g., authentication, authorization, metering / billing, etc.) and API call processing functions are typically implemented on a single plane (e.g., the same network). In this case, as API call-related traffic (load) increases, response delays occur across the entire system, inevitably degrading service quality and user satisfaction.
[0004] The technical problem to be solved through some embodiments of the present disclosure is to provide a system capable of providing a high-quality API (Application Programming Interface) service based on a cloud and a method performed in the system.
[0005] The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art of the present disclosure from the description below.
[0006] According to some embodiments of the present disclosure for solving the above-described technical problem, a cloud-based API service providing system may include a cloud management console that issues authentication information for an application API among a plurality of APIs (Application Programming Interfaces), wherein the cloud management console is a module belonging to a control plane, an API manager that receives a call message for a specific API including authentication information from a user's terminal, performs authentication using the authentication information of the call message, and requests execution of the specific API based on a result of the authentication, wherein the call message is received by the API manager belonging to a data plane without going through the control plane, and an API execution engine that generates an execution result for the specific API in response to a request from the API manager.
[0007] In some embodiments, the plurality of APIs may include APIs for AI-based character recognition, AI-based text analysis, and AI-based image analysis functions.
[0008] In some embodiments, the specific API is an API for data analysis functionality, and the API execution engine may be run on a GPU (Graphics Processing Unit)-based worker node.
[0009] In some embodiments, the control plane further includes an API authentication module, and the API manager can perform the authentication in conjunction with the API authentication module.
[0010] In some embodiments, the control plane further includes a user management module, and the API manager may check the user's usage rights for the specific API in conjunction with the user management module, and request execution of the specific API based on the check result.
[0011] In some embodiments, the specific API is an API for a data analysis function, and the API manager can download analysis data from storage and transmit the analysis data to the API execution engine.
[0012] In some embodiments, the API manager may include an API authentication linkage module that performs the authentication in conjunction with the control plane, a job manager that creates a job for the specific API based on the call message and inserts it into a queue, and an API execution request module that fetches the job from the queue and requests the API execution engine to execute the specific API.
[0013] In some embodiments, the job manager may include a job management module that creates a job for the specific API and issues an ID of the job, and a job status check module that checks the processing status of the job in a polling manner using the ID of the job.
[0014] In some embodiments, the job management module receives an execution result for the specific API from the API execution request module, stores the result in a database, and updates the processing status of the job to a completed status, and the job status check module obtains the execution result from the database when the processing status of the job is a completed status, and transmits the execution result to the user's terminal.
[0015] In some embodiments, the API manager may include an API authentication linkage module that performs the authentication in conjunction with the control plane, a job manager that creates a job for the specific API based on the call message, and an API execution request module that divides the job into task units according to preset criteria and requests the API execution engine to execute the specific API in task units.
[0016] In some embodiments, the specific API is an API for a data analysis function, and the API execution request module verifies the job based on at least one of the size, extension, and file name of the analysis data file, and if the job is valid, the job can be separated into task units and processed.
[0017] In some embodiments, the specific API is an API for a data analysis function, and the API execution request module can divide the job into task units based on the number of files or pages of analysis data.
[0018] In some embodiments, the API manager includes an API authentication linkage module that performs the authentication in conjunction with the control plane, a job manager that creates a job for the specific API based on the call message, and an API execution request module that requests the API execution engine to execute the specific API to process the job, and the job manager can transmit the ID of the job to the user's terminal before the job is processed if the specific API is an asynchronous API.
[0019] In some embodiments, the job manager may receive an execution result for the specific API from the API execution request module and upload the execution result to a storage accessible to the user's terminal.
[0020] In some embodiments, the API authentication linkage module receives a query request including the job ID and authentication information for the specific API, authenticates the requester using the authentication information of the query request, and, if the requester is authenticated, provides the requester with a query result for the job ID, and the query result may include processing status information for the job or an execution result for the specific API.
[0021] In some embodiments, the cloud management console includes a demo management console that provides a demonstration of an execution result for an API selected by a specific user from among the plurality of APIs, and the demo management console requests the API manager to obtain an execution result for the selected API, and the API manager may be configured not to request authentication information for the API requested from the demo management console.
[0022] A method for providing a cloud-based API service according to some embodiments of the present disclosure for solving the above-described technical problem is a method performed by at least one computing device, the method including the steps of: receiving a call message for a specific API (Application Programming Interface) from a user's terminal without going through a control plane to which a cloud management console belongs, wherein the call message includes authentication information and the authentication information is issued by the cloud management console; performing authentication on the user using the authentication information of the call message, wherein the authentication is performed in conjunction with an API authentication module belonging to the control plane; obtaining an execution result for the specific API through an API execution engine when the authentication is successfully performed; and providing the execution result to the user's terminal.
[0023] According to some embodiments of the present disclosure for solving the above-described technical problem, a computer program may be stored in a computer-readable recording medium to execute the steps of: receiving a call message for a specific API (Application Programming Interface) from a user's terminal without going through a control plane to which a cloud management console belongs, wherein the call message includes authentication information and the authentication information is issued by the cloud management console; performing authentication on the user using the authentication information of the call message, wherein the authentication is performed in conjunction with an API authentication module belonging to the control plane; obtaining an execution result for the specific API through an API execution engine when the authentication is successfully performed; and providing the execution result to the user's terminal.
[0024] According to some embodiments of the present disclosure, the operation (or control / management) functions (e.g., authentication, authorization, metering / billing, etc.) of a cloud-based API (Application Programming Interface) service and the processing functions for API calls can be implemented on different planes. In this case, even if the traffic (load) related to service operation or the traffic (load) related to API calls increases, there is no response delay for the overall functions of the system, resulting in improved service quality and user satisfaction. Furthermore, by increasing the resources of the data plane responsible for processing API calls, the issue of response delay for API calls can be easily resolved.
[0025] In addition, by integrating and providing various APIs related to AI (Artificial Intelligence)-based data analysis functions (e.g., character recognition, text analysis, image analysis, etc.) that are difficult for general users to develop, user satisfaction with API services can be further improved.
[0026] Additionally, by providing demo services for various APIs, users' choice regarding API services can be guaranteed, thereby further improving user satisfaction.
[0027] The effects according to the technical idea of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.
[0028] FIG. 1 is an exemplary configuration diagram schematically illustrating a cloud-based API (Application Programming Interface) service providing system and its operating environment according to some embodiments of the present disclosure.
[0029] FIG. 2 is an exemplary block diagram illustrating a functional separation structure of a cloud-based API service providing system according to some embodiments of the present disclosure.
[0030] FIGS. 3 and 4 are exemplary block diagrams for explaining in more detail the configuration and operation of a cloud-based API service providing system according to some embodiments of the present disclosure.
[0031] FIG. 5 illustrates the overall flow of an API service providing method performed in a cloud-based API service providing system according to some embodiments of the present disclosure.
[0032] FIG. 6 is an exemplary flowchart illustrating a service application processing process in a cloud-based API service providing system according to some embodiments of the present disclosure.
[0033] FIG. 7 and FIG. 8 are exemplary flowcharts illustrating a synchronous API call processing process in a cloud-based API service providing system according to some embodiments of the present disclosure.
[0034] FIG. 9 is an exemplary flowchart illustrating a job status check process in a cloud-based API service providing system according to some embodiments of the present disclosure.
[0035] FIG. 10 and FIG. 11 are exemplary flowcharts illustrating an asynchronous API call processing process in a cloud-based API service providing system according to some embodiments of the present disclosure.
[0036] FIG. 12 is an exemplary flowchart illustrating a job information retrieval process in a cloud-based API service providing system according to some embodiments of the present disclosure.
[0037] FIG. 13 illustrates the overall flow of a process in which an API demo service is provided in a cloud-based API service providing system according to some embodiments of the present disclosure.
[0038] FIG. 14 illustrates an exemplary computing device that can implement a cloud-based API service providing system according to some embodiments of the present disclosure.
[0039] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the attached drawings. The advantages and features of the present disclosure, and methods for achieving them, will become clear with reference to the embodiments described in detail below together with the attached drawings. However, the technical idea of the present disclosure is not limited to the following embodiments and may be implemented in various different forms. The following embodiments are provided only to complete the technical idea of the present disclosure and to fully inform those skilled in the art of the present disclosure of the scope of the present disclosure, and the technical idea of the present disclosure is defined only by the scope of the claims.
[0040] In describing various embodiments of the present disclosure, if it is determined that a detailed description of a related known configuration or function may obscure the gist of the present disclosure, the detailed description will be omitted.
[0041] Unless otherwise defined, the terms (including technical and scientific terms) used in the following examples may be used with meanings commonly understood by those of ordinary skill in the art to which this disclosure pertains; however, this may vary depending on the intentions of engineers working in the relevant field, precedents, the emergence of new technologies, etc. The terminology used in this disclosure is for the purpose of describing the embodiments and is not intended to limit the scope of this disclosure.
[0042] In the following examples, singular expressions include plural concepts unless the context clearly specifies that they are singular. Furthermore, plural expressions include singular concepts unless the context clearly specifies that they are plural.
[0043] In addition, terms such as first, second, A, B, (a), (b), etc. used in the following embodiments are only used to distinguish certain components from other components, and the nature, order, or sequence of the components are not limited by the terms.
[0044] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0045] FIG. 1 is an exemplary configuration diagram schematically illustrating a cloud-based API (Application Programming Interface) service providing system (10) and its operating environment according to some embodiments of the present disclosure. In the drawings below FIG. 1, the cloud-based API service providing system (10) is depicted as an 'API service providing system.'
[0046] As illustrated in FIG. 1, the cloud-based API service providing system (10) is a cloud-based computing system (or platform) that can provide API services to multiple user terminals (11-1 to 11-N). For example, the cloud-based API service providing system (10) can provide users with APIs related to various AI (Artificial Intelligence)-based data analysis functions that are difficult for users to develop in an integrated manner. Examples of such functions may include character recognition, text analysis, image analysis, translation, STT (Speech-To-Text), etc., but the scope of the present disclosure is not limited thereto. In some cases, the cloud-based API service providing system (10) can also provide users with APIs related to non-AI-based data analysis functions (or other functions, e.g., functions that require a lot of computing resources). The detailed configuration and operation of the cloud-based API service providing system (10) will be described in detail with reference to the drawings in FIG. 2 and below.
[0047] Hereinafter, for convenience of explanation, the cloud-based API service provision system (10) will be abbreviated as the "service provision system." In addition, the reference number "11" will be used in all cases where it refers to any user terminal (e.g., 11-1, 11-2) or collectively refers to all user terminals (11-1 to 11-N).
[0048] The service provision system (10) described above may be implemented with at least one computing device. For example, the first function of the service provision system (10) may be implemented on a first computing device, and the second function may be implemented on a second computing device. Alternatively, specific functions of the service provision system (10) may be implemented on multiple computing devices.
[0049] A computing device may include any device equipped with computing capabilities. For an example of such a device, see FIG. 14. Since a computing device is a collection of interacting components (e.g., memory, processor, etc.), it may sometimes be referred to as a "computing system." Of course, the term "computing system" can also encompass the concept of a collection of interacting computing devices.
[0050] A user terminal (11) may refer to a user terminal that utilizes the API service of the service provision system (10). The user terminal (11) may be implemented using any device. Users may be, for example, developers, administrators (e.g., development administrators who apply for API services and set API usage rights for developers), etc.; however, the scope of the present disclosure is not limited thereto.
[0051] As illustrated in Fig. 1, a user terminal (11) and a service provision system (10) can communicate via a network. Here, the network can be implemented as any type of wired / wireless network, such as a local area network (LAN), a wide area network (WAN), a mobile radio communication network, or Wibro (Wireless Broadband Internet).
[0052] So far, with reference to FIG. 1, a service provision system (10) and its operating environment according to some embodiments of the present disclosure have been briefly described. Hereinafter, the functional separation structure, detailed configuration, and operation of the service provision system (10) will be described in more detail with reference to FIGS. 2 to 4.
[0053] FIG. 2 is an exemplary drawing for explaining the functional separation structure of a service providing system (10) according to some embodiments of the present disclosure.
[0054] As illustrated in FIG. 2, the functions of the service provision system (10) can be implemented separately on the control plane (21) and the data plane (22). In this case, even if service operation-related traffic (i.e., control traffic) or API call-related traffic (i.e., data traffic) increases, no response delay occurs for the overall functions of the service provision system (10). In addition, by increasing the resources of the data plane (22) (e.g., computing resources, network bandwidth, etc.), the problem of response delay due to an increase in API call-related traffic (load) can be easily resolved.
[0055] Specifically, the service provision system (10) may be configured to include a cloud management console (23), a common operation module (24), an API service manager (25), and an API execution engine (26). Here, the cloud management console (23) and the common operation module (24) are modules responsible for the operation (or control / management) function of a cloud-based API service, and the API service manager (25) and the API execution engine (26) are modules responsible for the processing function for API calls. Accordingly, the cloud management console (23) and the common operation module (24) may be implemented to belong to the control plane (21), and the API service manager (25) and the API execution engine (26) may be implemented to belong to the data plane (22). For example, the cloud management console (23) and the common operation module (24) may be implemented on a first network, and the API service manager (25) and the API execution engine (26) may be implemented on a second network that is distinct from the first network (e.g., a network having a larger bandwidth than the first network). By doing so, traffic of different characteristics can be naturally separated into different planes (or networks), and as a result, the overall response speed of the service provision system (10) can be greatly improved.
[0056] Meanwhile, as illustrated, the API service manager (25) belonging to the data plane (22) may be operated on a CPU (Central Processing Unit) worker node, and the API execution engine (26) may be operated on a GPU (Graphics Processing Unit) worker node. For example, if the API execution engine (26) is an engine that executes an API related to AI-based data analysis functions (e.g., character recognition, text analysis, image analysis, etc.), the API execution engine (26) may be operated on a GPU worker node. By doing so, the response speed for API calls may be significantly improved. The worker node may be a virtual machine or a physical machine.
[0057] In some embodiments, an auto-scaling function may be performed based on the resource usage (or the amount of API call-related traffic (load)) of worker nodes (e.g., CPU worker nodes, GPU worker nodes). For example, if the resource usage of GPU worker nodes on which the API execution engine (26) is running is greater than a threshold, the service providing system (10) may increase the number of GPU worker nodes (scale-out), and conversely, may decrease the number of GPU worker nodes (scale-in).
[0058] For reference, the common operation module (24) may be a general term for various modules required for the operation of a cloud-based API service, and the API execution engine (26) may be a general term for engines required for the execution of various APIs.
[0059] Hereinafter, the detailed configuration and operation of the service provision system (10) will be described in more detail with reference to FIGS. 3 and 4. FIG. 3 is a block diagram showing in more detail the modules (i.e., components) of the service provision system (10) belonging to the control plane (21), and FIG. 4 is a block diagram showing in more detail the modules (i.e., components) of the service provision system (10) belonging to the data plane (22).
[0060] As illustrated in FIG. 3, the cloud management console (23) may be configured to include an authentication management console (31), an authorization management console (32), a service management console (33), and a demo management console (34). However, in some cases, the cloud management console (23) may further include other management modules.
[0061] The authentication management console (31) may refer to a module responsible for authentication management functions. For example, the authentication management console (31) may provide (issue) authentication information for API calls at the user's request. Authentication information may be, for example, an authentication key or token, but the scope of the present disclosure is not limited thereto. Below, the explanation will continue assuming that the authentication management console (31) issues an "authentication key."
[0062] Next, the permission management console (32) may refer to a module responsible for permission management functions. For example, the permission management console (32) may provide a function for setting users' API usage rights, number of calls, usage time, etc. For example, an administrator (i.e., a development manager) can set policies such as developers' API usage rights, number of uses, usage time, etc. through the permission management console (32).
[0063] Next, the service management console (33) may refer to a module responsible for service management functions. For example, the service management console (33) may provide users with a function to apply for API services. For example, an administrator (i.e., a development manager) may apply for APIs to be used by developers through the service management console (33). In some cases, a system administrator may also create and provide an API product composed of multiple APIs through the service management console (33) (e.g., providing a single API product by bundling several related APIs).
[0064] Next, the demo management console (34) may refer to a module responsible for demo management functions. For example, the demo management console (34) may provide a demo service for an API selected by a user (i.e., a service that provides a demonstration of the execution results of the selected API). The demo service provision process will be described later with reference to FIG. 13. In some cases, the system administrator may also select and configure a demo API from among multiple APIs through the demo management console (34).
[0065] For reference, the cloud management console (23) described above is a front-end module that provides an interface with a user (e.g., developer, development manager) or system administrator, and may be implemented, for example, via a web server (i.e., management functions are provided via a web interface). However, the scope of the present disclosure is not limited thereto.
[0066] Below, the common operation module (24) will be described.
[0067] As illustrated, the API authentication module (35), the user management module (35), the logging module (37), and the metering / billing module (38) may be included in the category of the common operation module (24). However, the scope of the present disclosure is not limited thereto, and the category of the common operation module (24) may further include various modules necessary for the operation of a cloud-based API service.
[0068] The API authentication module (35) may refer to a module responsible for the authentication function for the called API. For example, the API authentication module (35) may identify (verify) the user of the called API using an authentication key included in the API call message. However, the scope of the present disclosure is not limited thereto.
[0069] Next, the user management module (35) may refer to a module responsible for integrated management functions for user information. For example, the user management module (35) may manage user account authentication information (e.g., ID, password, etc.), application API (or API product) information, authority information, project information, etc. In addition, the user rights module (35) may perform user account authentication, authority check, etc. (i.e., perform an IAM (Identity Access Management) function) based on the exemplified information. However, the scope of the present disclosure is not limited thereto.
[0070] Next, the logging module (37) may refer to a module responsible for logging functions. The logging module (37) may log various operations of the service provision system (10). For example, the logging module (37) may log API call information for which API (user) authentication and user authorization checks have been successfully completed. The log information thus generated may be utilized by the metering / billing module (38) to calculate service costs.
[0071] Next, the metering / billing module (38) may refer to a module responsible for metering and billing functions for the called API. For example, the metering / billing module (38) may measure the number of API calls by user, project, etc. (e.g., measuring based on log information) and calculate service costs (e.g., cost per user, cost per project, etc.) based on the number of API calls. However, the scope of the present disclosure is not limited thereto, and any metering and billing method may be used.
[0072] For reference, the above-described common operation module (24) is a back-end module that provides common operation functions of a cloud-based API service in conjunction with a cloud management console (23) and / or an API service manager (25), and may be implemented, for example, via a web application server. However, the scope of the present disclosure is not limited thereto.
[0073] Below, modules belonging to the data plane (22) will be described with reference to FIG. 4.
[0074] As illustrated in FIG. 4, the API service manager (25) belonging to the data plane (22) can be configured to include an API authentication linkage module (41), an API endpoint (42, endpoint), a job manager (43), and an API execution request module (46).
[0075] The API authentication linkage module (41) may refer to a module responsible for the authentication function for the called API and the linkage function with the control plane (21). For example, the API authentication linkage module (41) may receive an API call message from a user terminal (11) and perform authentication (i.e., user authentication) for the called API using the authentication key of the API call message. At this time, the API authentication linkage module (41) may perform such authentication by linking with the API authentication module (35) of the control plane (21). In addition, the API authentication linkage module (41) may also check the user's authority by linking with the user management module (36) of the control plane (21). An API call message for which user authentication and authority check have been successfully completed may be transmitted to the API endpoint (42).
[0076] Next, the API endpoint (42, endpoint) may refer to an end point that receives an API call message. The API endpoint (42) may initiate a process for generating a response to the API call message (i.e., a process for generating an execution result for the called API) by requesting the job manager (43) to create a job. For this, please refer to the description of the drawings below in FIG. 6. Those skilled in the art will likely already be familiar with the meaning of an API endpoint, and therefore, a description thereof will be omitted.
[0077] Next, the job manager (43) may refer to a module responsible for job management functions. Here, a job may refer to a work unit within the service provision system (10) for processing API calls. For example, the job manager (43) may be responsible for functions such as job creation, job ID issuance, and job status checking.
[0078] As illustrated, in some embodiments, the job manager (43) may be configured to include a job management module (44) and a job status check module (45). The job management module (44) may create a job and issue a job ID, and the job status check module (45) may check the status of the job through polling. For detailed operations of the job management module (44) and the job status check module (45), please refer to the descriptions of the drawings below FIG. 6.
[0079] Next, the API execution request module (46) may refer to a module responsible for requesting the execution of a called API. For example, the API execution request module (46) may request the API execution engine (26) to execute the API of a job for job processing. In some cases, the API execution request module (46) may divide the job into task units and request the execution of the API for each task. For this purpose, please refer to the descriptions of the drawings below FIG. 6.
[0080] Next, the API execution engine (26) may refer to a module that generates the execution result of the called API. As illustrated in FIG. 4, when the service providing system (10) provides APIs related to AI-based character recognition, text analysis, and image analysis, the category of the API execution engine (26) may include a character recognition API execution engine (47), a text analysis API execution engine (48), and an image analysis API execution engine (49). However, the scope of the present disclosure is not limited thereto. Hereinafter, the description will continue assuming that the service providing system (10) provides an API as exemplified (i.e., an AI-based data analysis API).
[0081] For reference, the components of the service provision system (10) illustrated in FIGS. 2 to 4 represent functionally distinct functional elements, and multiple components may be implemented in a form in which they are integrated with each other in an actual physical environment, or a specific functional element may be implemented in a form in which it is separated into multiple sub-functional elements.
[0082] So far, the functional separation structure, detailed configuration, and operation of the service provision system (10) have been described in detail with reference to FIGS. 2 to 4. Hereinafter, the method of providing API services in the service provision system (10) will be described in more detail with reference to FIGS. 5 to 13.
[0083] Figure 5 illustrates the overall flow of an API service provision method performed in a service provision system (10) according to some embodiments of the present disclosure. Figure 5 assumes that an administrator (i.e., a development administrator) applies for an API service and a developer calls the API. However, in some cases, the administrator and developer may be the same user.
[0084] As illustrated in FIG. 5, the cloud management console (23) can receive API service requests from administrators (i.e., administrator terminals) and set usage policies for the same (see ①). For example, the administrator can request APIs, API products, etc. for use by developers through the service management console (33). In addition, the administrator can set policies such as developer (or project) usage rights, usage frequency (i.e., number of calls possible), usage time, etc. for the requested API (or API product) through the permission management console (32).
[0085] Next, the cloud management console (23) can issue an authentication key for the API in response to a request from a developer (i.e., the developer's terminal) (see ②).
[0086] Next, the developer can upload analysis data (e.g., analysis file) to accessible storage (51, e.g., OBS (Object-Based Storage)) (see ③). For reference, FIG. 5 assumes that the API service manager (25) obtains analysis data through storage (51), but the scope of the present disclosure is not limited thereto. For example, the API service manager (25) may directly receive analysis data from the developer or may obtain analysis data in another way.
[0087] Next, the API service manager (25) can receive an API call message containing an authentication key from the developer (see ④). Then, the API service manager (25) can perform user authentication and authorization checks in conjunction with the common operation module (24) of the control plane (21) (see ⑤). If this process is successfully completed, subsequent steps can be performed.
[0088] Next, the API service manager (25) can download analysis data from storage (51) and execute the called API through the API execution engine (26) (see ⑥, ⑦). Then, the API service manager (25) can provide the execution result of the called API to the developer (see ⑧).
[0089] Below, the detailed processes of the API service provision method will be described in more detail with reference to the drawings in FIG. 6 and below. In the drawings in FIG. 6 and others, developers and administrators are collectively referred to as "users" without distinction.
[0090] Figure 6 is an exemplary flowchart illustrating a service application process in a service provision system (10) according to some embodiments of the present disclosure. However, this is merely a preferred embodiment for achieving the purpose of the present disclosure, and it is to be understood that some steps may be added or deleted as needed.
[0091] As illustrated in FIG. 6, the service application process may begin at step S61, where the cloud management console (23) receives an application for an API service from a user terminal (11). For example, an administrator may access the service management console (33) through his or her terminal (11) and apply for an API, API product, etc. to be used. As described above, the administrator may also set policies, such as the developer's (or project's) usage rights, usage frequency, usage time, etc. for the applied API (or API product) through the permission management console (32). Such setting (policy) information may be transmitted to the user management module (36) and used for permission checking, etc.
[0092] In step S62, the service management console (33) can transmit (send) the application result of the API service (e.g., success, failure, application details, etc.) to the user terminal (11).
[0093] In step S63, the authentication management console (31) may receive a request (i.e., a request message) for issuing an authentication key for a specific API from a user terminal (11). For example, a developer may access the authentication management console (31) through his / her terminal (11) and request issuance of an authentication key for a specific API among the application APIs.
[0094] In step S64, the authentication management console (31) can transmit (send) the authentication key issuance result (e.g., success, failure, authentication key, etc.) to the user terminal (11). The authentication management console (31) can issue an authentication key for a specific API through the API authentication module (35) or can issue an authentication key independently. In either case, the authentication key and user information can be transmitted to the API authentication module (35) and used to authenticate the called API.
[0095] So far, the service application process according to some embodiments of the present disclosure has been described with reference to FIG. 6. Below, the process of processing API calls in the service provision system (10) will be described in detail with reference to FIGS. 7 to 12.
[0096] First, the synchronous API call processing process will be described with reference to FIGS. 7 to 9.
[0097] Figures 7 and 8 are exemplary flowcharts illustrating a synchronous API call processing process in a service provision system (10) according to some embodiments of the present disclosure. However, this is merely a preferred embodiment for achieving the objectives of the present disclosure, and it is to be understood that some steps may be added or deleted as needed. The following description will be provided with reference to Figures 7 and 8.
[0098] In step S71, analysis data can be uploaded to storage (51). For example, the developer can upload the analysis data to storage (51, eg, OBS) before calling the API.
[0099] In step S72, the API manager (25) belonging to the data plane (22) can receive an API call message (i.e., a call message for a specific API) from the user terminal (11). In other words, the API call message can be directly transmitted to the API manager (25) without passing through the control plane (21). In this case, the response speed for API calls can be further improved, and as a result, user satisfaction with the API service can be significantly improved.
[0100] The API call message may include, for example, a previously issued authentication key, API information (e.g., API URL, API parameter values, etc.). However, the scope of the present disclosure is not limited thereto.
[0101] In step S73, the API manager (25) may perform user authentication in conjunction with the API authentication module (35) belonging to the control plane (21). For example, the API manager (25) may identify the user who called the API using the authentication key included in the API call message. If the authentication key is valid and the user is successfully identified, subsequent steps may be performed.
[0102] More specifically, as illustrated in FIG. 8, the API authentication linkage module (41) may receive an API call message and perform user authentication in conjunction with the API authentication module (35) (S72 and S73). For example, the API authentication linkage module (41) may transmit an authentication key to the API authentication module (35) and receive a user authentication result (e.g., success, failure, information on the identified user (e.g., ID), etc.) from the API authentication module (35). However, the scope of the present disclosure is not limited thereto. The specific user authentication method may be changed at any time.
[0103] In step S74, the API manager (25) can check the user's authority by linking with the user management module (36) belonging to the control plane (21). If the authority check is successfully performed, subsequent steps can be continuously performed.
[0104] More specifically, as illustrated in FIG. 8, the API authentication linkage module (41) may perform an authorization check in conjunction with the user management module (36) (S74). For example, the API authentication linkage module (41) may transmit the user's identification information (e.g., ID) to the user management module (36) and receive an authorization check result (e.g., success, failure, etc.) from the user management module (36). However, the scope of the present disclosure is not limited thereto, and the specific authorization check method may be changed at any time. In some cases, the API authentication linkage module (41) may further receive the user's storage information (e.g., the user's upload location allocated on the storage (51)), project information, etc. from the user management module (36).
[0105] In step S75, the API manager (25) can perform preparations for execution of the called API.
[0106] More specifically, as illustrated in FIG. 8, an API call message can be transmitted to the API endpoint (42) (S81). Then, the API endpoint (42) can initiate API execution preparation by requesting job creation for the called API (S82). Next, the job manager (43) can create a job for the called API in response to the request (S83-1). In addition, the job manager (43) can store information about the created job in the database (81) and insert the created job into the queue (82) (S83-2, S83-3). For further details on the detailed operation of the job manager (43), please refer to the description of FIG. 9.
[0107] Job information may include, for example, information about the called API (e.g., API URL, API parameter values, etc.), user information (e.g., user ID, affiliated project, etc.), storage information (e.g., upload location of analysis data), etc. However, the scope of the present disclosure is not limited thereto.
[0108] In step S76, the API manager (25) can download analysis data from storage (51).
[0109] More specifically, as illustrated in FIG. 8, the API execution request module (46) can retrieve a job from the queue (82) (S84) and download analysis data associated with the job from the storage (51) (S76).
[0110] In some embodiments, the API execution request module (46) may perform job verification based on analysis data. For example, the API execution request module (46) may verify the job based on at least one of the size, extension, and file name of the analysis data file. As a more specific example, the API execution request module (46) may determine that the job is invalid if the size of the analysis data file is greater than or equal to a threshold, the extension does not conform to a predefined rule (e.g., if the extension is not included in the predefined extension list, if the called API is a text analysis API but the extension points to an image file), or the file name does not conform to a predefined rule (e.g., the length is greater than or equal to a threshold, etc.). If the job is verified as valid, the API execution request module (46) may continue to perform subsequent steps (e.g., if the job is valid, the job is divided into task units).
[0111] Additionally, in some embodiments, the API execution request module (46) may divide the work into task units based on preset criteria (S85). For example, the API execution request module (46) may divide the work into multiple tasks based on the number of files or pages of the analysis data (e.g., one file or page corresponds to one task) and request API execution on a task-by-task basis (e.g., API execution requests are repeated on a task-by-task basis). By doing so, API calls can be processed more quickly.
[0112] In steps S77 and S78, the API manager (25) may request the API execution engine (26) to execute the call API and receive the API execution result. The API execution result may mean a job processing result.
[0113] More specifically, as illustrated in FIG. 8, the API execution request module (46) may request the execution of the called API to the API execution engine (26) (S77). At this time, the API execution request module (46) may transmit the downloaded analysis data to the API execution engine (26). Then, the API execution engine (26) may execute the called API on the analysis data. For example, if the called API is an API related to a character recognition function, the API execution engine (26) may perform character recognition on the analysis data (e.g., document image). As another example, if the called API is an API related to a text analysis function (e.g., sentiment analysis, named entity recognition, etc.), the API execution engine (26) may perform text analysis on the analysis data (e.g., document text). As another example, if the called API is an API related to an image analysis function (e.g., object detection, etc.), the API execution engine (26) may perform image analysis on the analysis data (e.g., image).
[0114] If the job is divided into task units, the API execution request module (46) can request execution of the API called in task units (S77). For example, if the analysis data is a document image consisting of multiple pages and one page is created as one task, the API execution request module (46) can request execution of the API for the first page of the document image and then request execution of the API again for the second page of the document image.
[0115] In some cases, the API execution request module (46) may perform task verification and request API execution only for verified tasks. The method for verifying tasks may be any method.
[0116] In step S79, the API manager (25) may transmit the execution result of the calling API (i.e., the job processing result) to the user terminal (11). In some cases, the API manager (25) may upload the API execution result to storage (51) and notify the user terminal (11) of an execution completion message.
[0117] More specifically, as illustrated in FIG. 8, the job manager (43) can receive the execution result of the API called from the API execution request module (46) and update job information (S86, S87). For example, the job manager (43) can store the execution result of the called API in the DB (81) and update the processing status of the job to a completed state. Next, the job manager (43) can transmit the execution result of the called API to the user terminal (11) through the API endpoint (42) and the API authentication linkage module (41) (S88, S89, S79).
[0118] Below, the detailed operation of the job manager (43) will be described in more detail with reference to Fig. 9.
[0119] As illustrated in Fig. 9, the job manager (43) may be configured to include a job status check module (44) and a job management module (45), and the job management module (45) may create a job for the called API and issue a job ID (S91, S92). In addition, the job management module (45) may transmit the job ID to the job status check module (44) (S93).
[0120] The job status check module (44) can check the status of a job being processed in a polling manner (S94-1 to S94-K). For example, the job status check module (44) can periodically check the processing status of a job through the job management module (45). In other words, the job status check module (44) can send the job ID to the job management module (45) and request an inquiry of the job processing status. Then, the job management module (45) can use the job ID to inquire the processing status of the corresponding job in the DB (81) and transmit the inquiry result to the job status check module (44).
[0121] When the job management module (45) updates the processing status of the job to a completed status, the processing status of the job can be checked as a completed status (see S87, S94-K), and then the job status check module (44) can obtain the called API execution result (i.e., the processing result of the job) by querying the database (81) with the job ID through the job management module (45) (S95), and the job status check module (44) can transmit the query result to the user terminal (11) through the API endpoint (42) (S88, S89, S79).
[0122] Heretofore, the synchronous API processing process in the service provision system (10) according to some embodiments of the present disclosure has been described with reference to FIGS. 7 to 9. As described above, API call messages can be delivered to the API manager (25) belonging to the data plane without passing through the control plane. In this case, even if the traffic (load) related to API calls increases, no response delay occurs for the overall functions of the system, and as a result, service quality and user satisfaction can be improved. Furthermore, by increasing the resources of the data plane responsible for processing API calls, the problem of response delay for API calls can be easily resolved.
[0123] Additionally, by integrating and providing various APIs related to AI-based data analysis functions (e.g., character recognition, text analysis, image analysis, etc.) that are difficult for general users to develop, user satisfaction with API services can be further improved.
[0124] Hereinafter, an asynchronous API processing process according to some embodiments of the present disclosure will be described with reference to FIGS. 10 to 12. However, for clarity of the present disclosure, descriptions of content overlapping with the aforementioned synchronous API processing process will be omitted.
[0125] Figures 10 and 11 are exemplary flowcharts illustrating an asynchronous API call processing process in a service provision system (10) according to some embodiments of the present disclosure. However, this is merely a preferred embodiment for achieving the objectives of the present disclosure, and it is understood that some steps may be added or deleted as needed. The following description will be provided with reference to Figures 10 and 11.
[0126] In step S101, analysis data can be uploaded to storage (51).
[0127] In step S102, the API manager (25) can receive an API call message from the user terminal (11).
[0128] In step S103, the API manager (25) can perform user authentication for the called API in conjunction with the API authentication module (35).
[0129] In step S104, the API manager (25) can check the user's authority for the called API in conjunction with the user management module (35).
[0130] In steps S105 and S106, the API manager (25) can perform execution preparation of the called API and transmit the job ID to the user terminal (11) before execution of the called API is initiated (or before execution is completed).
[0131] More specifically, as illustrated in FIG. 11, the job manager (43) can create a job for the called API in response to a job creation request from the API endpoint (42) and issue a job ID (S111, S112, S113-1). In addition, the job manager (43) can store information about the created job in a database (81) and insert the job into a queue (82). Next, the job manager (43) can transmit the job ID to the user terminal (11) through the API endpoint (42) and the API authentication linkage module (41) before the job is processed (S114-1, S114-2, S106). The job ID can be used by the user terminal (11) to inquire job information (e.g., job processing status, job processing result), and for this, refer to the description of FIG. 12.
[0132] In step S107, the API manager (25) can download analysis data from storage (51).
[0133] More specifically, as illustrated in FIG. 11, the API execution request module (46) can retrieve a job from the queue (82) (S115) and download analysis data associated with the job from the storage (51) (S107).
[0134] In steps S108-1 and S108-2, the API manager (25) can execute the called API through the API execution engine (26).
[0135] For example, as illustrated in FIG. 11, the API execution request module (46) can divide the job brought in by task unit (S116) and request execution of the API (i.e., the called API) for the job by task unit (S108-1). Next, the API execution request module (46) can receive the execution result of the called API from the API execution engine (26) and transmit it to the job manager (43) (S108-2, S117). Then, the job manager (43) can store the execution result of the called API in the database (81) and update the processing status of the job to a completed status (S118).
[0136] In step S109, the API manager (25) can upload the execution result of the called API to storage (51). This upload service is provided for asynchronous APIs, and may be selectively provided based on the user's selection or may be provided by default.
[0137] In some cases, the API manager (25) may notify the user terminal (11) of an execution completion message after uploading the execution result of the called API to storage (51).
[0138] Below, the job information retrieval process using the job ID will be further explained with reference to Fig. 12.
[0139] As shown in Fig. 12, the user terminal (11) can use the received job ID to search job information (e.g., processing status, processing result, etc.).
[0140] Specifically, in step S121, the API manager (25) can receive a query request (i.e., a request message) including a job ID and an authentication key of a specific API (i.e., an asynchronous API) from the user terminal (11). For example, the API authentication linkage module (41) can receive such a query request from the user terminal (11).
[0141] In step S122, the API manager (25) may perform user authentication in conjunction with the API authentication module (35). For example, the API authentication linkage module (41) may perform user (i.e., query requester) authentication based on an authentication key through the API authentication module (35). If authentication is successfully performed, subsequent steps may be continuously performed.
[0142] In steps S123 and S124, the API manager (25) can query the database (81) with the job ID and transmit the query result to the user terminal (11). The query result may be, for example, job processing status information, job processing result (i.e., API execution result), etc., but is not limited thereto.
[0143] More specifically, the API authentication linkage module (41) transmits a query request message to the job manager (43), and the job manager (43) can query the database (81) using the job ID included in the query request message. Then, the job manager (43) can transmit the query result to the user terminal (11) through the API authentication linkage module (41).
[0144] The asynchronous API call processing process in the service provision system (10) according to some embodiments of the present disclosure has been described with reference to FIGS. 10 to 12. As described above, by providing users with an asynchronous API in addition to a synchronous API, user satisfaction with the API service can be further enhanced.
[0145] Below, the process of providing an API demo service in the service provision system (10) will be described with reference to FIG. 13.
[0146] Figure 13 illustrates the overall flow of the process by which the API demo service is provided. Figure 13 assumes that the user is a developer.
[0147] As illustrated in FIG. 13, the cloud management console (23) can receive a demo service request from a developer (i.e., the developer's terminal) (see ①). More specifically, the demo management console (34) can receive a demo service request including a demo API and analysis data selected by the developer.
[0148] Next, the demo API can be executed by the cloud management console (23) sending a call message for the demo API to the API manager (25) (see ②). More specifically, the demo management console (34) can obtain the execution result for the demo API by sending a call message for the demo API to the API endpoint (42) (i.e., requesting execution of the demo API). Here, it can be understood that the reason the demo management console (34) sends the demo API call message to the API endpoint (42) is because procedures such as user authentication and authorization check are omitted for the demo API. That is, the API manager (25) can be configured not to request authentication information for the API requested (called) from the demo management console (34) (note that a general API call message is transmitted to the API authentication linkage module (41)). For details of the API execution process, refer to the descriptions of FIGS. 5 to 12.
[0149] Next, the cloud management console (23) can provide the developer with the execution results for the demo API. That is, the demo management console (34) can provide the developer with the execution results for the demo API (e.g., the execution results are displayed on the screen of the developer terminal).
[0150] Meanwhile, although not clearly shown in Figure 13, if an administrator (i.e., a development administrator) applies for a specific API (or API product), a demo service may be provided for the applied API (or API product).
[0151] The process of providing an API demo service in the service provision system (10) has been described with reference to FIG. 13. As described above, by providing demo services for various APIs, users' choice regarding API services can be guaranteed, thereby further enhancing user satisfaction.
[0152] Hereinafter, an exemplary computing device (140) capable of implementing the above-described service provision system (10) will be described with reference to FIG. 14.
[0153] Figure 14 is an exemplary hardware configuration diagram showing a computing device (140).
[0154] As illustrated in FIG. 14, a computing device (140) may include one or more processors (141), a bus (143), a communication interface (144), a memory (142) for loading a computer program (146) executed by the processor (141), and a storage (145) for storing the computer program (146). However, only components related to the embodiment of the present disclosure are illustrated in FIG. 14. Therefore, a person skilled in the art to which the present disclosure pertains will appreciate that other general components may be included in addition to the components illustrated in FIG. 14. That is, the computing device (140) may further include various components in addition to the components illustrated in FIG. 14. In addition, in some cases, the computing device (140) may be configured in a form in which some of the components illustrated in FIG. 14 are omitted. Hereinafter, each component of the computing device (140) will be described.
[0155] The processor (141) can control the overall operation of each component of the computing device (140). The processor (141) can be configured to include at least one of a CPU (Central Processing Unit), an MPU (Micro Processor Unit), an MCU (Micro Controller Unit), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or any other type of processor well known in the art of the present disclosure. In addition, the processor (141) can perform operations for at least one application or program for executing operations / methods according to embodiments of the present disclosure. The computing device (140) can include one or more processors.
[0156] Next, the memory (142) can store various data, commands, and / or information. The memory (142) can load a computer program (146) from the storage (145) to execute operations / methods according to embodiments of the present disclosure. The memory (142) may be implemented as a volatile memory such as RAM, but the technical scope of the present disclosure is not limited thereto.
[0157] Next, the bus (143) can provide a communication function between components of the computing device (140). The bus (143) can be implemented as various types of buses such as an address bus, a data bus, and a control bus.
[0158] Next, the communication interface (144) can support wired and wireless Internet communication of the computing device (140). Furthermore, the communication interface (144) can also support various communication methods other than Internet communication. To this end, the communication interface (144) can be configured to include a communication module well known in the technical field of the present disclosure.
[0159] Next, the storage (145) can non-temporarily store one or more computer programs (146). The storage (145) can be configured to include non-volatile memory such as Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), flash memory, a hard disk, a removable disk, or any form of computer-readable recording medium well known in the art to which the present disclosure pertains.
[0160] Next, the computer program (146) may include instructions that cause the processor (141) to perform operations / methods according to various embodiments of the present disclosure when loaded into the memory (142). That is, the processor (141) may perform operations / methods according to various embodiments of the present disclosure by executing the instructions loaded into the memory (142).
[0161] For example, the computer program (146) may include instructions for performing an action of receiving a call message for a specific API from a user's terminal without going through a control plane to which a cloud management console (23) belongs, an action of performing authentication on the user using authentication information of the call message, an action of obtaining an execution result for the specific API through an API execution engine (26) when the authentication is successfully performed, and an action of providing the obtained execution result to the user's terminal (11).
[0162] As another example, the computer program (146) may include instructions to perform at least some of the operations / steps described with reference to FIGS. 1 through 13.
[0163] In the above examples, a service providing system (10) according to some embodiments of the present disclosure can be implemented through a computing device (140).
[0164] Meanwhile, in some embodiments, the computing device (140) illustrated in FIG. 14 may refer to a virtual machine implemented based on cloud technology. For example, the computing device (140) may be a virtual machine operating on one or more physical servers included in a server farm. In this case, at least some of the processor (141), memory (142), and storage (145) illustrated in FIG. 14 may be virtual hardware, and the communication interface (144) may also be implemented as a virtualized networking element, such as a virtual switch.
[0165] So far, with reference to FIG. 14, an exemplary computing device (140) capable of implementing a service providing system (10) according to some embodiments of the present disclosure has been described.
[0166] Various embodiments of the present disclosure and effects according to the embodiments have been described with reference to FIGS. 1 through 14 so far. The effects according to the technical concept of the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.
[0167] Furthermore, even though the above embodiments have described multiple components as being combined or operating in combination, the technical concept of the present disclosure is not necessarily limited to these embodiments. That is, within the scope of the technical concept of the present disclosure, all of the components may be selectively combined and operated one or more times.
[0168] The technical concepts of the present disclosure described so far can be implemented as computer-readable code on a computer-readable recording medium. A computer program recorded on the computer-readable recording medium can be transmitted to another computing device via a network such as the Internet, installed on the device, and used therein.
[0169] Although the operations are depicted in a specific order in the drawings, it should not be understood that the operations must be performed in the specific order depicted, or in a sequential order, or that all depicted operations must be performed to achieve the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Although various embodiments of the present disclosure have been described above with reference to the attached drawings, those skilled in the art to which the present disclosure pertains will understand that the technical concepts of the present disclosure can be implemented in other specific forms without changing the technical concepts or essential characteristics thereof. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included in the scope of the technical ideas defined by the present disclosure.
Claims
1. A cloud management console that issues authentication information for an application API among multiple APIs (Application Programming Interfaces) - the cloud management console is a module belonging to the control plane -; An API manager that receives a call message for a specific API including authentication information from a user's terminal, performs authentication using the authentication information of the call message, and requests execution of the specific API based on the result of the authentication, wherein the call message is received by the API manager belonging to the data plane without passing through the control plane; and Including an API execution engine that generates an execution result for the specific API in response to a request from the API manager. Cloud-based API service provision system.
2. In paragraph 1, The above multiple APIs include APIs related to AI (Artificial Intelligence)-based character recognition, AI-based text analysis, and AI-based image analysis functions. The above specific API is an API for data analysis functions, The above API execution engine runs on GPU (Graphic Processing Unit) based worker nodes. The above API manager, Download analytics data from storage, Sending the above analysis data to the API execution engine, Cloud-based API service provision system.
3. In paragraph 1, Further including an API authentication module belonging to the above control plane, The above API manager performs the above authentication in conjunction with the above API authentication module. Cloud-based API service provision system.
4. In paragraph 1, Further comprising a user management module belonging to the above control plane, The above API manager, Check the user's usage rights for the specific API by linking with the user management module. Requesting execution of the specific API based on the above check result, Cloud-based API service provision system.
5. In paragraph 1, The above API manager, An API authentication linkage module that performs the authentication in conjunction with the above control plane; A job manager that creates a job for the specific API based on the above call message and inserts it into a queue; and An API execution request module that retrieves the job from the queue and requests the API execution engine to execute the specific API, Cloud-based API service provision system.
6. In paragraph 5, The above job manager, A job management module that creates a job for the above-mentioned specific API and issues an ID for the job; and Including a job status check module that checks the processing status of the job by polling using the ID of the job. Cloud-based API service provision system.
7. In paragraph 6, The above job management module, Receive the execution result for the specific API from the API execution request module and store it in the database, Update the processing status of the above job to completed, The above job status check module is, If the processing status of the above job is complete, the execution result is obtained from the database, Transmitting the above execution result to the user's terminal, Cloud-based API service provision system.
8. In paragraph 1, The above API manager, An API authentication linkage module that performs the authentication in conjunction with the above control plane; A job manager that creates a job for the specific API based on the call message; and An API execution request module that separates the above-described tasks into units according to preset criteria and requests the API execution engine to execute the specific API in units of the tasks. Cloud-based API service provision system.
9. In paragraph 8, The above specific API is an API for data analysis functions, The above API execution request module is: Verifies the job based on at least one of the size, extension, and file name of the analysis data file, If the above job is valid, the job is processed by dividing it into task units. Cloud-based API service provision system.
10. In paragraph 8, The above specific API is an API for data analysis functions, The above API execution request module is: Separating the job into task units based on the number of files or pages of the analysis data, Cloud-based API service provision system.
11. In paragraph 1, The above API manager, An API authentication linkage module that performs the authentication in conjunction with the above control plane; A job manager that creates a job for the specific API based on the call message; and Including an API execution request module that requests the API execution engine to execute the specific API to process the above job, The above job manager, If the above specific API is an asynchronous API, the ID of the job is transmitted to the user's terminal before the job is processed. Cloud-based API service provision system.
12. In paragraph 11, The above job manager, Receive the execution result for the specific API from the API execution request module, Uploading the above execution result to a storage accessible to the user's terminal, Cloud-based API service provision system.
13. In paragraph 11, The above API authentication linkage module is: Receive a query request including the ID of the above job and authentication information for the above specific API, The requester is authenticated using the authentication information of the above inquiry request, If the above requester is authenticated, the result of the inquiry for the above job ID is provided to the above requester, The above query result includes processing status information of the job or execution result for the specific API. Cloud-based API service provision system.
14. In paragraph 1, The above cloud management console includes a demo management console that provides a demonstration of execution results for an API selected by a specific user from among the above multiple APIs. The above demo management console requests the API manager to obtain the execution results for the selected API, The above API manager is configured not to request authentication information for APIs requested from the above demo management console. Cloud-based API service provision system.
15. A method performed by at least one computing device, A step of receiving a call message for a specific API (Application Programming Interface) from a user's terminal without going through a control plane to which a cloud management console belongs, wherein the call message includes authentication information and the authentication information is issued by the cloud management console; A step of performing authentication on the user using the authentication information of the above call message, wherein the authentication is performed in conjunction with an API authentication module belonging to the control plane; If the above authentication is successfully performed, a step of obtaining an execution result for the specific API through the API execution engine; and Including a step of providing the execution result to the user's terminal, How to provide cloud-based API services.
16. In paragraph 15, The above cloud management console issues authentication information for multiple APIs including the above specific API, The above multiple APIs include APIs related to AI (Artificial Intelligence)-based character recognition, AI-based text analysis, and AI-based image analysis functions. The above specific API is an API for data analysis functions, The above API execution engine runs on a GPU (Graphic Processing Unit) based worker node. How to provide cloud-based API services.
17. Combined with a computing device, A step of receiving a call message for a specific API (Application Programming Interface) from a user's terminal without going through a control plane to which a cloud management console belongs, wherein the call message includes authentication information and the authentication information is issued by the cloud management console; A step of performing authentication on the user using the authentication information of the above call message, wherein the authentication is performed in conjunction with an API authentication module belonging to the control plane; If the above authentication is successfully performed, a step of obtaining an execution result for the specific API through the API execution engine; and In order to execute the step of providing the above execution result to the user's terminal, stored in a computer-readable recording medium, Computer program.
Citation Information
Patent Citations
Application programming interfaces for data parallel computing on multiple processors
KR1020110019775A
Tail gate of vehicle
KR1020230055192A
Method for controlling of accelerating edge platform network and electronic device using the same
KR102217114B1
SERVICE AND APIs FOR REMOTE VOLUME-BASED BLOCK STORAGE
US20190082012A1
KR20210116005A
