Method and apparatus for providing cloud-based API service

The cloud-based API service method integrates AI-based services to reduce costs and enhance user convenience by leveraging common infrastructure, addressing the inefficiencies of individual service management and providing stable AI-based API services through a centralized architecture.

WO2024248439A1PCT designated stage expired Publication Date: 2024-12-05SAMSUNG SDS CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2024/007134
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-31
Filing Date
2024-05-27
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

The existing methods for providing AI-based API services are costly and inefficient, requiring significant time and resources for building GPU infrastructure and managing multiple services individually, leading to high development and operating costs, and lack stability and user convenience.

Method used

A cloud-based API service method that integrates multiple AI-based services, utilizing a centralized architecture to issue authentication keys, manage user permissions, and execute API services on GPU-based worker nodes, reducing costs and improving user convenience by leveraging common infrastructure and middleware in the control plane area.

Benefits of technology

This approach reduces server and management costs, enhances user satisfaction, and improves service quality by providing stable and flexible AI-based API services through integration with cloud products, while minimizing development and operation expenses.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure KR2024007134_05122024_PF_FP_ABST
    Figure KR2024007134_05122024_PF_FP_ABST
Patent Text Reader

Abstract

The present disclosure relates to a method for providing a cloud-based API service and a system therefor. A method for providing a cloud-based API service according to some embodiments of the present disclosure may comprise the steps of: issuing an authentication key corresponding to an application for some of a plurality of API services; performing authentication for a first user by using the issued authentication key in response to a call for a first API service of the first user; and executing the first API service on the basis of a result of the authentication.
Need to check novelty before this filing date? Find Prior Art

Description

Method and device for providing cloud-based API services

[0001] The present disclosure relates to a method and device for providing a cloud-based API service. More specifically, the present disclosure relates to a method for providing and managing multiple API services through a single, integrated cloud environment, and a system employing the method.

[0002] Multiple API services utilizing AI models can be provided to users. However, building an on-premise environment to provide multiple AI-based API services can require significant time for GPU (Graphics Processing Unit) infrastructure construction and ML (Machine Learning) model development. Furthermore, if each API service is provided individually rather than as a cloud-based, integrated API service, the costs of building and operating the service environment can increase.

[0003] Accordingly, a technology is required that can minimize the development and operating costs of AI-based API services, improve user convenience, and provide stable services to users.

[0004] The technical problem that the present disclosure seeks to solve is to provide a method and device that can provide a plurality of cloud-based API services to users in an integrated manner.

[0005] Another technical challenge that the present disclosure seeks to address is to provide a method and device that enables a cloud service provider to efficiently manage multiple AI-based API services provided to users.

[0006] Another technical challenge that the present disclosure seeks to address is to provide a method and device for providing an API service using an architecture designed to flexibly and stably provide deep learning model service resources in the control plane area of ​​a cloud service provider when calling an API.

[0007] 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.

[0008] A method for providing a cloud-based API service according to one embodiment of the present disclosure for solving the above technical problem may include a step of issuing an authentication key corresponding to an application for some API services among a plurality of API services, a step of performing authentication on a first user using the issued authentication key in response to a call to a first API service from a first user, and a step of executing the first API service based on a result of the authentication.

[0009] In one embodiment, the step of executing the first API service may include the step of obtaining analysis target data from linked storage and the step of executing the first API service to generate analysis results for the analysis target data.

[0010] In one embodiment, the plurality of API services may include an AI (Artificial Intelligence)-based character recognition service, an AI-based text analysis service, and an AI-based image analysis service.

[0011] In one embodiment, the step of executing the first API service may include the step of checking the first user's permission to use the first API service, and the step of executing the first API service only if the first user has permission to use the first API service.

[0012] In one embodiment, the plurality of API services may be data analysis services, and the first API service may be executed on a GPU (Graphic Processing Unit)-based worker node.

[0013] In one embodiment, the step of executing the first API service may include the steps of creating a job for the first API service and inserting it into a queue, retrieving the job from the queue and verifying the validity of the job, and processing the job if the job is valid.

[0014] In one embodiment, the validity of the job may be verified based on at least one of the extension name of the analysis target data file and the capacity of the analysis target data file.

[0015] In one embodiment, the first API service may be an asynchronous API service. Furthermore, the step of executing the first API service may include creating a job for the first API service, processing the created job, and, prior to processing the job, providing the job ID to the first user.

[0016] In one embodiment, the step of creating a job for the first API service and processing the created job may include the step of creating a job for the first API service and inserting it into a queue, the step of retrieving the job from the queue and verifying the validity of the job, and the step of processing the job if the job is valid.

[0017] In one embodiment, if the job is valid, the step of processing the job may include the steps of dividing the job into a plurality of tasks based on preset conditions, the step of verifying the validity of a first task among the plurality of tasks, the step of processing the first task if the first task is valid, and the step of repeating the verifying step and the processing step until all of the plurality of tasks are processed.

[0018] In one embodiment, the validity of the first task may be verified based on at least one of the extension name of the analysis target data file of the first task and the capacity of the analysis target data file of the first task.

[0019] In one embodiment, the method for providing a cloud-based API service may further include a step of uploading the processing result of the job to storage according to an option preset by the first user.

[0020] In one embodiment, the method may further include providing information on the status of a job to the first user in response to the first user's request for inquiring about the status of the job. In this case, the request for inquiring about the status of the job may include information on the ID of the job.

[0021] According to another embodiment of the present disclosure for solving the above technical problem, a method for providing a cloud-based API service may include the steps of receiving a call for a first API service from a first user input through a screen of a demo management console, checking the first user's usage authority for the first API service in response to the received call, and executing the first API service only when the first user has usage authority. In this case, the first API service may be an API service selected by the first user from among a plurality of API services, and the demo management console may provide an execution result for an API service selected by a specific user from among the plurality of API services on a trial basis.

[0022] According to another embodiment of the present disclosure for solving the above technical problem, a cloud-based API service providing system may include a processor and a memory storing instructions, wherein the instructions, when executed by the processor, cause the processor to perform an operation of issuing an authentication key corresponding to an application for some of a plurality of API (Application Programming Interface) services, an operation of performing authentication on a first user using the issued authentication key in response to a call to a first API service by a first user, and an operation of executing the first API service based on a result of the authentication.

[0023] In one embodiment, the operation of executing the first API service may include an operation of obtaining analysis target data from linked storage and an operation of executing the first API service to generate analysis results for the analysis target data.

[0024] According to this embodiment, server and management costs can be reduced by utilizing common infrastructure and middleware built in the control plane area of ​​a cloud service provider.

[0025] According to this embodiment, rather than an architecture that individually configures multiple API services, it is possible to design and utilize an architecture in which multiple API services are integrated and configured in a single area as a centralized SaaS (Software as a Service) service, thereby effectively reducing related costs.

[0026] According to this embodiment, user satisfaction and convenience can be improved by providing API services through linkage with various cloud products such as object storage and machine learning platforms.

[0027] According to this embodiment, when developing or operating various AI-based API services, service development and operation costs can be reduced by utilizing integrated resources.

[0028] FIG. 1 is an exemplary diagram of a configuration of a cloud-based API service providing system according to some embodiments of the present disclosure.

[0029] FIG. 2 is a flowchart illustrating a method for providing a cloud-based API service according to some embodiments of the present disclosure.

[0030] Figure 3 is an exemplary diagram for explaining some of the operations illustrated in Figure 2.

[0031] Figure 4 is an exemplary diagram for explaining some of the operations illustrated in Figure 3.

[0032] FIG. 5 and FIG. 6 are detailed flowcharts of a method for providing a synchronous API service according to one embodiment of the present disclosure.

[0033] Figure 7 is an exemplary diagram for explaining some of the operations illustrated in Figure 3.

[0034] Figure 8 is an exemplary diagram for explaining some of the operations illustrated in Figure 7.

[0035] FIG. 9 is a detailed flowchart of an asynchronous API service providing method according to one embodiment of the disclosure.

[0036] FIG. 10 is an exemplary diagram of the configuration of an API service providing system of a demo version according to one embodiment of the present disclosure.

[0037] FIG. 11 is a detailed flowchart of a method for providing an API service of a demo version according to one embodiment of the present disclosure.

[0038] FIG. 12 is a hardware configuration diagram of a cloud-based API service providing system according to some embodiments of the present disclosure.

[0039] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. The advantages and features of the present invention, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the attached drawings. However, the technical spirit of the present invention 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 spirit of the present invention and to fully inform those skilled in the art of the present invention of the scope of the present invention, and the technical spirit of the present invention is defined only by the scope of the claims.

[0040] In describing 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 invention, 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 diagram of a configuration of a cloud-based API service providing system according to some embodiments of the present disclosure.

[0046] As illustrated in FIG. 1, a cloud-based API service providing system according to some embodiments of the present disclosure may include a storage (30), a console module (100), an API service linkage module (200), an API service module (300), and an API database (DB) (400). In this case, the console module (100), the API service linkage module (200), the API service module (300), and the API database (DB) (400) may belong to one control plane.

[0047] For convenience of explanation, the API service described below will be assumed to refer to a service that analyzes data using an AI model. However, it should be noted that the API service according to some embodiments of the present disclosure is not limited to a data analysis service.

[0048] First, the console module (100) may include an API End point (110) that receives a data analysis request from a user's (i.e. developer's) terminal and requests user authentication with an API authentication module (210), an authentication / authorization management console (121) that can set and manage authentication or authorization for a user, an API application console (122) that can receive an application for one or more API services from a user's (i.e. administrator's) terminal, a demo management console (123) that can receive an application and execution request for a demo version of an API service from a user's terminal, and a usage inquiry console (124) that allows a user to inquire about the API service usage up to a specific point in time. In addition, the console module (100) may be implemented in the form of a WEB server.

[0049] Second, the API service linkage module (200) may include an API authentication module (210) that performs user authentication in conjunction with the API manager (310), a user management module (220) that checks user usage rights in conjunction with the API manager (310), and a logging / messaging queue (230) that records logs and messages during the operation of the cloud-based API service provision system. In addition, the API service linkage module (200) may be implemented in the form of a WAS (Web Application Server) server.

[0050] Third, the API service module (300) may include an API manager (310) that creates a job for the API service and an API execution engine (320) that processes the job created through the API manager (300) to execute the API service. At this time, the API manager (310) may include an API End point (311) that receives an API service execution request after user authentication and authorization check are completed, a job manager (312) that creates a job and a job ID, divides the job into tasks as needed, and manages the processing status of the job, a queue (313) in which the job or task is temporarily stored, and an API execution request module (314). In addition, the API manager (310) may be driven on a CPU (Central Processing Unit)-based worker node, and the API execution engine (320) may be driven on a GPU (Graphics Processing Unit)-based worker node. Furthermore, the API service module (300) can be implemented in the form of a WAS (Web Application Server) server.

[0051] Meanwhile, depending on the API service method (e.g., synchronous or asynchronous), the operations performed by the API manager (310) and the API execution engine (320) may differ in some respects. A detailed description thereof will be provided below with reference to FIGS. 2 to 9.

[0052] Finally, the API database (DB) (400) can store information about a job (e.g., job status information, job processing result information) in conjunction with the API service module (300). In addition, the API service providing system may include a storage (30) that is not part of the control plane to which the API database (400) belongs, but can store analysis data target files uploaded by users and execution results of asynchronous API services.

[0053] Meanwhile, users can refer to administrators who apply for API services and developers who request the execution of API services. However, users of cloud-based API services are not necessarily divided into administrators and developers. The same user can apply for an API service and request the execution of that service simultaneously.

[0054] Although not illustrated in FIG. 1, users (e.g., administrators, developers) can utilize cloud-based API services via multiple user terminals. In this case, a user terminal may refer to a computing device utilized by a user (e.g., administrators, developers) to request an API service via the console module (100) and to call an API service (e.g., data analysis service) to obtain analysis results for data. In other words, a user terminal may be implemented as various types of computing devices, such as a smartphone, desktop, or laptop, and may be implemented as any device. For an example of such a computing device, refer to FIG. 12.

[0055] Referring again to FIG. 1, a cloud-based API service provision process according to some embodiments of the present disclosure will now be outlined. First, a user (e.g., an administrator) can apply for a specific API service (e.g., a text analysis service) among multiple API services via the cloud management console module (120). At this time, the user (e.g., an administrator) can set the user's (e.g., developer's) usage rights for the applied service along with the application for the text analysis service. Accordingly, an authentication key can be issued to the user (e.g., developer) with the usage rights.

[0056] Thereafter, a user (i.e., a developer) can upload a data file requiring text analysis to storage (30) and request analysis of the data file by calling a text analysis API service. In response to the request, user authentication and user permissions can be checked through the API service linkage module (200), and when the authentication procedure is completed, the text analysis result for the data file can be provided to the user through the API service module (300). In this case, if the text analysis API service is an asynchronous API service, the text analysis result according to the execution of the API service can be stored in the storage.

[0057] Accordingly, cloud service providers can effectively reduce server and management costs by leveraging the common infrastructure and middleware built into the control plane. Furthermore, by providing multiple API services in a cloud-based manner rather than individually on-premise, service development and operational costs can be reduced. Furthermore, integration with various cloud products, including storage (e.g., object storage), can improve the quality of customer service and enhance user satisfaction and convenience.

[0058] The configuration and process of a cloud-based API service provision system according to some embodiments of the present disclosure have been described with reference to FIG. 1. Below, the specific process of providing a cloud-based API service will be described in detail with reference to FIGS. 2 through 9.

[0059] Meanwhile, the subject of the steps / operations illustrated in FIGS. 2 to 4 may mean one computing device or computing system that performs the functions of the multiple modules (100, 200, 300, 400) belonging to the control plane (20) illustrated in FIG. 1. In other words, the multiple modules (100, 200, 300, 400) belonging to the control plane (20) illustrated in FIG. 1 may be implemented by at least one computing device. For example, all functions of the multiple modules (100, 200, 300, 400) may be implemented in one computing device, or the multiple modules (100, 200, 300, 400) may be implemented in multiple computing devices each having different functions. More specifically, the function of the console module (100) may be implemented in a first computing device, and the functions of the API service linkage module (200) and the API service module (300) may be implemented in a second computing device.

[0060] A computing device can encompass any device equipped with computing capabilities. For an example of such a device, see FIG. 12. A computing device is a collection of interacting components (e.g., memory, processor, etc.), and thus may sometimes be referred to as a "computing system." Furthermore, a computing system may also refer to a collection of interacting computing devices.

[0061] Furthermore, the computing device may be, but is not limited to, a server (including VMs, Clouds, etc.), a desktop, a laptop, etc., and may include any type of device equipped with computing capabilities. An example of a computing device will be described with reference to FIG. 12.

[0062] First, a method for providing a synchronous API service will be described with reference to FIGS. 2 to 6.

[0063] Figure 2 is a flowchart illustrating a method for providing a cloud-based API service 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.

[0064] As illustrated in FIG. 2, a method for providing a cloud-based API service according to one embodiment of the present disclosure may begin with step S100 of issuing an authentication key corresponding to an application for some of a plurality of API services. At this time, the authentication key may be issued by the authentication / authorization management module (121) of the console module (120) illustrated in FIG. 1.

[0065] Additionally, the plurality of API services may be data analysis services, and more specifically, may include AI (Artificial Intelligence)-based character recognition services, AI-based text analysis services, and AI-based image analysis services. Furthermore, the plurality of API services may be services running on GPU (Graphics Processing Unit)-based worker nodes.

[0066] In step S200, in response to a call from a first user to a first API service, authentication of the first user may be performed using the issued authentication key. At this time, the authentication may be performed by the API authentication module (210) illustrated in FIG. 1.

[0067] In step S300, the first API service may be executed based on the result of the authentication. That is, if the authentication key received along with the call message for the first API service of the first user is determined to be valid, a job for the first API service may be created and processed, thereby providing the user with the execution result for the first API service. At this time, the first API service may be executed by the API manager (310) and API execution engine (320) illustrated in FIG. 1. Hereinafter, a specific process for executing the first API service will be described with reference to FIGS. 3 and 4.

[0068] FIG. 3 is an exemplary diagram illustrating some of the operations illustrated in FIG. 2. 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 necessary.

[0069] As illustrated in FIG. 3, step S300 of executing the first API service based on the result of the authentication through step S200 of performing user authentication for the first user using the issued authentication key may include step S310 of checking the first user's usage rights for the first API service, step S320 of obtaining analysis target data from linked storage, and step S330 of executing the first API service to generate an analysis result for the analysis target data.

[0070] In step S310, the user management module (220) may check whether the first user has permission to use the first API service. At this time, if the check indicates that the first user has permission to use the service, subsequent processes related to the execution of the first API service may proceed. However, if the first user does not have permission to use the service, subsequent processes related to the execution of the first API service may not proceed, and a notification message indicating that execution is not possible may be transmitted to the user's terminal.

[0071] If it is checked in step S310 that the first user has the usage right, step S320, in which analysis target data is acquired from the storage (30) linked with the API service module (300), and step S330, in which analysis results for the analysis target data acquired by executing the first API service are generated, may be sequentially performed. At this time, the analysis target data may be a data analysis target file (e.g., text or image file for analysis) uploaded to the storage in advance by the user. In addition, the storage may be an object storage (OBS) that stores data in units of objects.

[0072] Meanwhile, FIG. 3 illustrates that step S310 of checking the user's usage rights for the first API service, step S320 of obtaining analysis target data from linked storage, and step S330 of generating analysis results for the analysis target data by executing the first API service are performed sequentially, but the present invention is not limited to this example. That is, step S310 of checking the user's usage rights and steps of obtaining analysis target data from storage and generating analysis results for the analysis target data by executing the API service (i.e. steps S320 and S330) may be performed in parallel.

[0073] A detailed description of the multiple steps / actions illustrated in FIGS. 2 and 3 and each entity performing each step / action will be described later with reference to FIG. 5.

[0074] FIG. 4 is an exemplary diagram illustrating some of the operations illustrated in FIG. 3. 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 necessary.

[0075] As illustrated in FIG. 4, after it is checked that the user has usage rights, step S330 of executing the first API service to generate analysis results for the analysis target data may include step S331 of creating a job for the first API service and inserting it into a queue, step S332 of retrieving a job from the queue and verifying the validity of the retrieved job, and step S333 of processing the job if the job is verified to be valid. At this time, steps S331 to S333 illustrated in FIG. 4 may be performed by the API service module (300).

[0076] Meanwhile, the first API service may be a synchronous or asynchronous API service. Synchronous or asynchronous API services are pre-configured. Users (e.g., administrators) can check whether the API service they are requesting is synchronous or asynchronous when requesting the service. By selecting the desired method, users can request an API service that best suits their needs.

[0077] At this time, if the first API service is synchronous, the step of separating a job into tasks, which are sub-concepts of a job, may not be necessary. However, if the first API service is asynchronous, the step of separating a job into multiple tasks may be required. In addition, if the first API service is asynchronous, unlike in the case of the synchronous method, the execution result of the first API service may be stored in storage linked to the API service module. In other words, it should be noted that some of the steps / operations illustrated in Fig. 4 may be added or changed depending on the method of the first API service (i.e., synchronous / asynchronous).

[0078] A detailed description of the multiple steps / actions illustrated in Fig. 4 and each entity performing each step / action will be described later with reference to Fig. 6.

[0079] In summary, by providing users with integrated API services through a cloud environment, rather than individually, server and management costs can be reduced through the use of common infrastructure and middleware. Furthermore, when users call API services, services utilizing AI models can be provided flexibly and reliably within the cloud service provider's control plane.

[0080] Below, a specific process in which an API service is executed in response to a call to a synchronous API service is described in detail with reference to FIGS. 5 and 6.

[0081] FIGS. 5 and 6 are detailed flowcharts of a synchronous API service provision method according to one embodiment 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, or the order of some steps may be changed, as necessary. Furthermore, the respective steps / operations of the synchronous API service provision method illustrated in FIGS. 5 and 6 may be performed by components of the cloud-based API service provision system illustrated in FIG. 1.

[0082] As illustrated in FIG. 5, a method for providing a synchronous API service may begin at step S10, in which a user (10) applies for an API service on the terminal of the user (10) through an API service application console (122). At this time, the user (10) may be an administrator, and the API service application console (122) may be a module included in a cloud management console (120) belonging to a console module (100). Thereafter, at step S11, the API service application console (122) may, in response to the API service application of the user (10), transmit the result of the API service application to the terminal of the user (i.e., the administrator, 10). At this time, the result of the API service application may include details of the API service applied for by the user (i.e., the administrator, 10) and information on the usage rights of each user who can use the applied API service. In the following, we will explain assuming that the API service requested by the administrator includes the first API service (e.g., AI-based text analysis service), and that the developer calls the first API service to obtain text analysis results.

[0083] In response to an application for the first API service, the authentication / authorization management console (121) can generate an authentication key (step S12) and transmit the authentication key generation result to the user (i.e. developer, 10) (step S13). That is, when a call is made to the first API service by a specific user (i.e. developer) in the future, the authentication key required in the user authentication process can be issued to the user. Thereafter, the user (i.e. developer, 10) can upload the analysis target data file to the storage (30) (step S14), and the storage (30) can transmit the upload result to the terminal of the user (i.e. developer, 10). The analysis target data file uploaded to the storage (30) can be transmitted to the API manager (310) in response to a download request from the API service module (300) in the execution phase of the first API service in the future.

[0084] Thereafter, in step S21, a call signal for the first API service may be received from the terminal of the user (i.e., developer, 10). However, although FIG. 5 illustrates that the user calls the first API service after the analysis data file has been uploaded to the storage at the user's request, the illustrated order is not necessarily required. In other words, the analysis data file may be uploaded to the storage even after the user calls the first API service.

[0085] In response to a call signal for the first API service received from a terminal of a user (i.e., developer, 10), the API authentication module (220) can perform user authentication using an authentication key previously issued to the user through steps S12 and S13 (step S22). In addition, the user management module (220) can check the user's usage rights set in advance for the first API service (step S23), and can provide the first API service only to users who have the usage rights as a result of the check. Thereafter, the results of the authentication and authorization check can be logged through a logging / message queue (240), and the logging results can be transmitted to the user management module (220).

[0086] After the authentication and authorization check procedure for the user is completed, the user management module (220) can transmit a request signal for executing the first API service to the API service module (300), and the API service module (300) can request the download of the analysis target data file previously uploaded to the storage (30) (step S38), and in response to the request, the storage (30) can transmit the analysis target data file to the API service module (300) (step S29). The API service module (300) can process a job for the first API service generated using the analysis target data file, and transmit the job processing result to the terminal of the user (i.e., developer, 10) via the user management module (220). At this time, the job processing result can be logged through the logging / message queue (240), and the logging result can be transmitted to the user management module (220).

[0087] Meanwhile, step S51, in which the API service module (300) requests an upload of an analysis result data file generated as a result of job processing to storage (30), and step S52, in which the upload result is transmitted to the API service module (300) in response to the request, may not be performed in a synchronous API service providing process. In other words, steps S51 and S52 may be performed only in an asynchronous API service providing process.

[0088] Hereinafter, a series of processes performed in the API service module (300) in response to a first API service execution request in a synchronous manner will be described in detail with reference to FIG. 6. At this time, the API service module (300) may include an API manager (310) including an API End point (311), a job manager (312), a queue (313), and an API execution request module (314), and an API execution engine (320).

[0089] As illustrated in FIG. 6, in step S31, the API service module (300) may receive a first API service execution request signal from the user management module (220) belonging to the API service linkage module (200). More specifically, the first API service execution request signal may be received through the API End point (311) belonging to the API manager (310) included in the API service module (300). Thereafter, in step S32, the API End point (311) may transmit the first API service execution request signal to the job management module (312a). At this time, the job management module (312a) may create a job for the first API service and manage information related to the created job (e.g., job ID).

[0090] The job management module (312a) may request the job processing result storage module (312b) to create a job ID while creating a job for the first API service (step S33), and in response to the creation request, the job ID may be issued to the job management module (312a) (step S34). At this time, information about the created job and job ID may be stored in the API database (400) (step S35). Meanwhile, in an asynchronous API service, the job ID may be transmitted to the user's terminal, and the user may use the job ID to check the processing status of the job at any time, but in a synchronous API service, the job ID may not be transmitted to the user.

[0091] In addition, the job management module (312a) can insert a job into the queue (313) (step S36), and the API execution request module (314) can retrieve the job inserted into the queue (313) (step S37). At this time, the API execution request module (314) can request a download of an analysis target data file previously uploaded by the user to the storage (30) before processing the job retrieved from the queue (313) (step S38), and can receive the analysis target data file in response to the request (step S39). In addition, the API execution request module (314) can verify the validity of the job retrieved from the queue (313) before processing the job. At this time, the validity of the job can be verified based on at least one of the extension name of the downloaded analysis target data file and the capacity of the analysis target data file. For example, if the capacity of the analysis target data file exceeds a reference value, the job may be determined to be invalid and the job processing process may not proceed. Additionally, if the data file to be analyzed is not a text-based file (e.g., an image file), the job may be deemed invalid and may not be processed due to the different extensions of the data file to be analyzed. Meanwhile, a job created for the first API may be processed on a job-by-job basis, but may also be divided into multiple tasks corresponding to sub-units of the job and processed on a task-by-task basis. This will be described later with reference to Figure 9.

[0092] Accordingly, by first verifying the validity of a job before processing it and processing the job only if it is determined to be a valid job, computing resources and resources that would otherwise be wasted can be saved.

[0093] If the validity of the job is verified through step S40, the API execution request module (314) can transmit an execution request signal of the first API service to the API execution engine (320) (step S41), and the API execution engine (320) can transmit the execution result of the first API service to the API execution request module (step S42). Thereafter, if the processing of the job is completed, information on the processing result of the job can be updated through the job processing result storage module (312b) (step S43). In addition, in step S44, information on the status of the job can be updated through the job processing result storage module (312b) and stored in the API database (400), and in step S45, information on the processing result of the job can be stored in the API database (400).

[0094] Meanwhile, the job management module (312a) can continuously poll the status of the job corresponding to the job ID. More specifically, the job management module (312a) can transmit a check request signal for the status of the job (e.g., processing status) to the job processing result storage module (312b) (step S46), and as a result of the check, information about the status of the job can be transmitted (step S47). Thereafter, when the job management module (312a) receives information that the status of the job is a processing completion state, it can request the job processing result storage module (312b) to inquire about the processing result of the job, and the job processing result storage module (312b) can request an inquiry about the processing result of the job previously stored in the API database (400) through step S45 (step S48). In response to the above query request, the job processing result transmitted from the API database (400) can be finally transmitted to the terminal of the user (i.e. developer, 10) through the job processing result storage module (312b), the job management module (312a), and the API end point (311) (step S49).

[0095] In summary, cloud service providers can effectively reduce server and management costs by leveraging the common infrastructure and middleware built into the control plane. Furthermore, by providing multiple synchronous API services in a cloud-based manner rather than individually on-premise, service development and operational costs can be reduced. Furthermore, integration with various cloud products, including storage (e.g., object storage), can improve the quality of customer service and enhance user satisfaction and convenience.

[0096] Furthermore, when developing AI-based synchronous API services individually, it can address the issues of reduced development productivity due to overlapping functions and structures, as well as increased development and operational costs due to different architectures, development languages, middleware, databases, and other environments for each service. Furthermore, providing AI-based synchronous API services can reduce excessive operating and management costs, previously incurred due to inefficient utilization of GPU (Graphics Processing Unit) resources.

[0097] So far, a method for providing a synchronous API service according to an embodiment of the present disclosure has been described with reference to FIGS. 2 to 6. Hereinafter, a method for providing an asynchronous API service according to an embodiment of the present disclosure will be described with reference to FIGS. 7 to 9.

[0098] FIG. 7 is an exemplary diagram illustrating some of the operations illustrated in FIG. 3. 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 necessary.

[0099] As illustrated in FIG. 7, the step S300 of executing the first API service based on the result of the user authentication described above with reference to FIG. 1 may include a step S340 of creating a job for the first API service and providing a job ID to the first user before the step of processing it, a step S350 of creating a job for the first API service and inserting it into a queue, a step S360 of retrieving a job from the queue and verifying the validity of the job, and a step S370 of processing the job if the job is valid. In addition, the steps / operations illustrated in FIG. 7 may be performed by components included in the API service module (300).

[0100] At this time, the job ID is generated when a job is created for the first API service. Unlike synchronous API services, this information may be provided to the user. The user can then use the received job ID to query the processing results for the job corresponding to the job ID.

[0101] Meanwhile, detailed descriptions of steps S350 to S370 overlap with the content described above with reference to FIG. 4, and thus detailed descriptions of the overlapping content will be omitted. Below, a process for dividing a job into multiple tasks, which are sub-units of the job and processing them as task units, which is necessary for performing an asynchronous API service, will be described with reference to FIG. 8.

[0102] FIG. 8 is an exemplary diagram illustrating some of the operations illustrated in FIG. 7. 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 necessary.

[0103] As illustrated in FIG. 8, after the validity of a job is verified, step S370 of processing the job may include step S371 of dividing the job into a plurality of tasks based on conditions preset by the user, step S372 of verifying the validity of any one of the divided tasks, and step S373 of processing the task if the task is verified as valid. At this time, step S372 of verifying the validity of any one of the plurality of tasks and step S373 of processing the task if the task is valid may be repeatedly performed until all of the plurality of tasks are processed. That is, step S370 of processing the job may further include step S374 of determining whether all of the plurality of tasks have been processed, and if all of the plurality of tasks have not been processed, step S372 of verifying the validity of any one of the unprocessed tasks and step S373 of processing the task if the task to be verified is valid may be sequentially performed.

[0104] Meanwhile, the validity of the task may be verified based on at least one of the extension name of the analysis target data file corresponding to the task and the capacity of the analysis target data file. For example, if the capacity of the analysis target data file corresponding to the task exceeds a reference value, the task may be determined to be invalid and the job processing may not proceed. In addition, if the analysis target data file is not a text-based file (e.g., an image file), the task may be determined to be invalid and may not be processed because the extension name of the analysis target data file is different.

[0105] Below, the specific process by which an API service is executed in response to an asynchronous API service call is described in detail with reference to FIG. 9.

[0106] Figure 9 is a detailed flowchart of an asynchronous API service provision method according to one embodiment of the disclosure. However, this is merely a preferred embodiment for achieving the purpose of the present disclosure, and it is understood that some steps may be added or deleted, or the order of some steps may be changed, as needed.

[0107] In addition, the subject of each step / operation of the asynchronous API service providing method illustrated in FIG. 9 can be performed by the configurations of the cloud-based API service providing system illustrated in FIG. 1. Furthermore, FIG. 9 only illustrates a series of processes performed in the API service module (300) in response to an asynchronous first API service execution request, and does not illustrate a process of checking user authentication and usage rights in the API service linkage module (200) in response to an asynchronous API service request through a user's (i.e. administrator's) terminal and console module (100) and an API service call by a user (i.e. developer). However, since the content not illustrated in FIG. 9 is the same as the content illustrated in FIG. 5, a description of the overlapping content will be omitted below.

[0108] As illustrated in FIG. 9, in step S51, the API service module (300) may receive a first API service execution request signal from the user management module (220) belonging to the API service linkage module (200). More specifically, the first API service execution request signal may be received through the API End point (311) belonging to the API manager (310) included in the API service module (300). Thereafter, in step S52, the API End point (311) may transmit the first API service execution request signal to the job management module (312a). At this time, the job management module (312a) may create a job for the first API service and manage information related to the created job (e.g., job ID).

[0109] The job management module (312a) may request the job processing result storage module (312b) to create a job ID while creating a job for the first API service (step S53), and in response to the creation request, a job ID may be issued to the job management module (312a) (step S54). At this time, information about the created job and job ID may be stored in the API database (400) (step S55). Meanwhile, the job ID may be transmitted to the user's terminal (step S54-1), and the user may use the transmitted job ID to inquire about the processing status of the job.

[0110] In addition, the job management module (312a) can insert a job into the queue (313) (step S56), and the API execution request module (314) can retrieve the job inserted into the queue (313) (step S57). At this time, the API execution request module (314) can request a download of an analysis target data file previously uploaded by the user to the storage (30) before processing the job retrieved from the queue (313) (step S58), and can receive the analysis target data file in response to the request (step S59). In addition, the API execution request module (314) can verify the validity of the job before processing the job retrieved from the queue (313). At this time, the job can be separated into tasks, which are sub-units of the job (step S60-1), and the validity can be verified for each task (step S60-2). Since multiple tasks are sub-units of a job created by separating a job, the job processing process can be understood as a process in which multiple tasks are processed sequentially or simultaneously. Additionally, the job validation process can be understood as a process in which multiple tasks are processed sequentially or simultaneously, and both job validation and task validation may be performed.

[0111] Meanwhile, the validity of the job or task may be verified based on at least one of the extension name of the downloaded analysis target data file and the capacity of the analysis target data file. For example, if the capacity of the analysis target data file exceeds a reference value, the job or task may be determined to be invalid and the processing of the job or task may not proceed. In addition, if the analysis target data file is not a text-based file (e.g., an image file), the extension name of the analysis target data file may be different, and thus the job or task may be determined to be invalid and the job or task may not be processed.

[0112] Accordingly, by first verifying the validity of a job or task before processing it and only processing it if it is determined to be valid, unnecessary computing resources and resources can be saved. Furthermore, by double-checking the validity of both the job and the task, the reliability and accuracy of the verification can be improved.

[0113] If the validity of the task is verified through step S60-2, the API execution request module (314) can transmit an execution request signal of the first API service to the API execution engine (320) (step S61), and the API execution engine (320) can transfer the execution result of the first API service to the API execution request module (step S62). Thereafter, if processing for multiple tasks is completed (i.e., job processing is completed), information on the processing result of the job can be updated through the job processing result storage module (312b) (step S63). In addition, in step S64, information on the status of the job can be updated through the job processing result storage module (312b) and stored in the API database (400), and in step S65, information on the processing result of the job can be stored in the API database (400).

[0114] Thereafter, in step S51, the API service module (300) may request the storage (30) to upload the analysis result data file generated as a result of job processing. In addition, in step S52, the storage (30) may transmit the upload result to the API service module (300) in response to the request.

[0115] Meanwhile, the job management module (312a) can receive a result inquiry request signal for a job ID from a user (step S71), and can transmit a check request signal for the job status (e.g., processing status) to the job processing result storage module (312b), and the job processing result storage module (312b) can transmit a check request signal for the job status (e.g., processing status) to the API database (400) (step S72). As a result of the check, the job management module (312a) can receive information on the job status transmitted from the API database (400) via the job processing result storage module (312b) (step S73).

[0116] Thereafter, when the job management module (312a) receives information that the status of the job is processing completed, it can request the job processing result storage module (312b) to inquire about the job processing result, and the job processing result storage module (312b) can request the API database (400) to inquire about the job processing result stored in step S65 (step S74). In response to the inquiry request, the job processing result transmitted from the API database (400) can be finally transmitted to the terminal of the user (i.e., developer, 10) through the job processing result storage module (312b), the job management module (312a), and the API end point (311) (step S75).

[0117] In summary, cloud service providers can effectively reduce server and management costs by leveraging the common infrastructure and middleware built into the control plane. Furthermore, by providing multiple asynchronous API services in a cloud-based manner rather than individually on-premise, service development and operational costs can be reduced. Furthermore, integration with various cloud products, including storage (e.g., object storage), can improve the quality of customer service and enhance user satisfaction and convenience.

[0118] Furthermore, when developing AI-based asynchronous API services individually, it can address the issues of reduced development productivity due to overlapping functions and structures, as well as increased development and operational costs due to different architectures, development languages, middleware, databases, and other environments for each service. Furthermore, providing AI-based asynchronous API services can reduce excessive operating and management costs, previously incurred due to inefficient utilization of GPU (Graphics Processing Unit) resources.

[0119] So far, an asynchronous API service providing method according to an embodiment of the present disclosure has been described with reference to FIGS. 7 to 9. Hereinafter, a demo version of an API service providing method according to an embodiment of the present disclosure will be described with reference to FIGS. 10 and 11.

[0120] FIG. 10 is an exemplary diagram of the configuration of an API service providing system of a demo version according to one embodiment of the present disclosure.

[0121] The configuration of the API service provision system of the demo version illustrated in Fig. 10 is identical to the configuration of the cloud-based API service provision system described with reference to Fig. 1, so detailed descriptions of overlapping contents will be omitted, and below, the API service provision process of the demo version will be roughly described with reference to Fig. 10.

[0122] First, a user (e.g., an administrator) can apply for a specific API service (e.g., a text analysis service) among multiple API services through the cloud management console module (120). At this time, the user (e.g., an administrator) can set the user's (e.g., an developer's) usage rights for the applied service along with the application for the text analysis service.

[0123] Thereafter, the user can call the demo version of the API service through the demo management console (123) belonging to the cloud management console module (120). That is, the user can select a data file to be analyzed and request analysis of the selected file. In response to the request, the user authentication and user permissions can be checked through the API service linkage module (200), and when the authentication procedure is completed, the API service module (300) can be requested to execute the API service of the demo version. Thereafter, the text analysis result for the data file can be provided to the user through the API service module (300).

[0124] In summary, in the case of the API service of the demo version, the user can make a call to the API service through the screen of the demo management console (123) without going through the API end point (110) of the console module (100). At this time, there is no need to issue an authentication key for the API service to the user, and the data file to be analyzed may not be uploaded to the storage (30) linked to the control plane (20). The data file to be analyzed required in the process of providing the API service of the demo version may be transmitted to the API service module (300) by a method other than using the storage, and may be transmitted in the form of Base64Data, for example.

[0125] Below, the specific process by which the API service of the demo version is provided will be described in detail with reference to Fig. 11.

[0126] FIG. 11 is a detailed flowchart of a method for providing an API service of a demo version according to one embodiment of the present disclosure.

[0127] As illustrated in FIG. 11, the API service provision method of the demo version may start at step S80, in which a user (i.e., an administrator (10)) applies for an API service on the terminal of the user (10) through an API service application console (122). At this time, the user (10) may be an administrator, and the API service application console (122) may be a module included in a cloud management console (120) belonging to a console module (100). Thereafter, at step S81, the API service application console (122) may, in response to the API service application of the user (10), transmit the result of the API service application to the terminal of the user (i.e., the administrator, 10). At this time, the result of the API service application may include details of the API service applied for by the user (i.e., the administrator, 10) and information on the usage rights of each user who can use the applied API service. Additionally, the API service requested by the administrator may be the first API service, which is an AI-based text analysis service, and the user can obtain text analysis results by calling the demo version of the first API service.

[0128] A user (i.e., developer, 10) can select a data file to be analyzed and transmit it to the demo management console (123) before calling the API service of the demo version (step S82). Thereafter, in step S83, the user (i.e., developer, 10) can call the first API service of the demo version through the screen of the demo management console (123). However, although FIG. 11 illustrates that the user calls the first API service of the demo version after selecting the data file to be analyzed, it is of course not necessarily dependent on the order illustrated above.

[0129] In response to a call to the first API service of the demo version, the user management module (220) belonging to the API service linking module (200) can check the user's usage rights (step S84), and as a result of the check, only users with usage rights can be provided with the first API service of the demo version. Thereafter, the result of the above-mentioned authorization check can be logged via the logging / message queue (240) (step S85), and the logging result can be transmitted to the user management module (220) (step S86).

[0130] After the authorization check procedure for the user is completed, the user management module (220) can send a request signal for executing the first API service of the demo version to the API service module (300) (step S87), and the API service module (300) can process a job for the first API service of the demo version and transmit the job processing result to the user management module (220) (step S88). At this time, the job processing result can be logged through the logging / message queue (240) (step S89), and the logging result can be transmitted to the user management module (220) (step S90).

[0131] Thereafter, the user management module (220) can transmit the job processing result to the demo management console (123) (step S91), and the execution result of the demo version of the API service can be displayed on the user's terminal through the screen of the demo management console (123).

[0132] Heretofore, a cloud-based API service providing method and system according to some embodiments of the present disclosure have been described with reference to FIGS. 1 to 11. According to the cloud-based API service providing method according to some embodiments of the present disclosure, server and management costs can be reduced by utilizing common infrastructure and middleware built in the control plane area of ​​a cloud service provider, and service development and operation costs can be reduced by utilizing integrated resources when newly developing or operating various AI-based API services.

[0133] FIG. 12 is a hardware configuration diagram of a cloud-based API service providing system according to some embodiments of the present disclosure. The cloud-based API service providing system (1000) illustrated in FIG. 12 may include one or more processors (1100), a system bus (1600), a communication interface (1200), a memory (1400) for loading a computer program (1500) executed by the processor (1100), and a storage (1300) for storing the computer program (1500).

[0134] The processor (1100) controls the overall operation of each component of the cloud-based API service providing system (1000). The processor (1100) can perform operations on at least one application or program for executing methods / operations according to various embodiments of the present disclosure. The memory (1400) stores various data, commands, and / or information. The memory (1400) can load one or more computer programs (1500) from the storage (1300) to execute methods / operations according to various embodiments of the present disclosure. The system bus (1600) provides a communication function between components of the cloud-based API service providing system (1000). The communication interface (1200) supports Internet communication of the cloud-based API service providing system (1000). The storage (1300) can non-temporarily store one or more computer programs (1500). The computer program (1500) may include one or more instructions implementing methods / operations according to various embodiments of the present disclosure. When the computer program (1500) is loaded into the memory (1400), the processor (1100) may execute the one or more instructions to perform the methods / operations according to various embodiments of the present disclosure.

[0135] In some embodiments, the cloud-based API service providing system (1000) described with reference to FIG. 12 may be configured using one or more physical servers included in a server farm based on cloud technologies such as virtual machines. In this case, at least some of the components illustrated in FIG. 12, such as the processor (1100), memory (1400), and storage (1300), may be virtual hardware, and the communication interface (1200) may also be configured as a virtualized networking element such as a virtual switch.

[0136] Various embodiments of the present disclosure and effects according to the embodiments have been described with reference to FIGS. 1 through 12. The effects according to the technical concept of the present disclosure are not limited to the effects described above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.

[0137] The technical concepts of the present disclosure described so far can be implemented as computer-readable code on a computer-readable medium. The 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 other computing device, and thus used on the other computing device.

[0138] 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 results. In certain circumstances, multitasking and parallel processing may be advantageous. Although the 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 present invention can be implemented in other specific forms without changing the technical spirit 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 invention 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. In the method of providing a cloud-based API (Application Programming Interface) service, A step of issuing an authentication key corresponding to an application for some of the API services among multiple API services; In response to a call to the first API service of the first user, a step of performing authentication on the first user using the issued authentication key; and A step of executing the first API service based on the result of the authentication, How to provide cloud-based API services.

2. In paragraph 1, The step of executing the above first API service is: A step of acquiring analysis target data from linked storage; and A step of generating analysis results for the analysis target data by executing the first API service, How to provide cloud-based API services.

3. In paragraph 1, The above multiple API services are: Including AI (Artificial Intelligence) based character recognition service, AI based text analysis service and AI based image analysis service. How to provide cloud-based API services.

4. In paragraph 1, The step of executing the above first API service is: A step of checking the usage rights of the first user for the first API service; and A step of executing the first API service only when the first user has the usage permission, How to provide cloud-based API services.

5. In paragraph 1, The step of executing the above first API service is: A step of creating a job for the first API service and inserting it into a queue; A step of retrieving the job from the above queue and verifying the validity of the job; and If the above job is valid, a step of processing the job is included. How to provide cloud-based API services.

6. In paragraph 5, The validity of the above job is, Verification is based on at least one of the extension name of the data file to be analyzed and the capacity of the data file to be analyzed. How to provide cloud-based API services.

7. In paragraph 1, The above first API service is an asynchronous API service, The step of executing the above first API service is: A step of creating a job for the first API service and processing the created job; and a step of providing the ID of the job to the first user before processing the job; How to provide cloud-based API services.

8. In paragraph 7, The step of creating a job for the above first API service and processing the created job is as follows: A step of creating a job for the above first API service and inserting it into a queue; A step of retrieving the job from the above queue and verifying the validity of the job; and If the above job is valid, a step of processing the job is included. How to provide cloud-based API services.

9. In paragraph 8, If the above job is valid, the steps for processing the job are: A step of dividing the above-described catch into multiple tasks based on preset conditions; A step of verifying the validity of a first task, which is one of the plurality of tasks; If the first task is valid, a step of processing the first task; and A step of repeating the above verification step and the above processing step until all of the multiple tasks are processed, How to provide cloud-based API services.

10. In paragraph 9, The validity of the above first task is Verification is based on at least one of the extension name of the analysis target data file of the first task and the capacity of the analysis target data file of the first task. How to provide cloud-based API services.

11. In paragraph 10, Further comprising a step of uploading the processing result of the job to storage according to the options preset by the first user. How to provide cloud-based API services.

12. In paragraph 10, In response to the request for the job status inquiry of the first user, further comprising the step of providing information on the job status to the first user, The above job status inquiry request includes information about the job ID. How to provide cloud-based API services.

13. Processor; and Contains memory for storing commands, The above instruction, when executed by the processor, causes the processor to: An action of issuing an authentication key corresponding to an application for some of the multiple API (Application Programming Interface) services; In response to a call to the first API service of the first user, an operation of performing authentication on the first user using the issued authentication key; and To perform an operation of executing the first API service based on the result of the above authentication, Cloud-based API service provision system.

14. In paragraph 13, The action of executing the above first API service is: The act of acquiring analysis target data from linked storage; and Including an operation of generating an analysis result for the analysis target data by executing the first API service. Cloud-based API service provision system.

15. In paragraph 13, The above first API service is an asynchronous API service, The step of executing the above first API service is: A step of creating a job for the first API service and processing the created job; and a step of providing the ID of the job to the first user before processing the job; Cloud-based API service provision system.

16. In paragraph 15, The step of creating a job for the above first API service and processing the created job is as follows: A step of creating a job for the above first API service and inserting it into a queue; A step of retrieving the job from the above queue and verifying the validity of the job; and If the above job is valid, a step of processing the job is included. Cloud-based API service provision system.

17. In paragraph 16, If the above job is valid, the steps for processing the job are: A step of dividing the above-described catch into multiple tasks based on preset conditions; A step of verifying the validity of a first task among the plurality of tasks; If the first task is valid, a step of processing the first task; and A step of repeating the above verification step and the above processing step until all of the multiple tasks are processed, Cloud-based API service provision system.

18. In paragraph 17, The validity of the above first task is Verification is based on at least one of the extension name of the analysis target data file of the first task and the capacity of the analysis target data file of the first task. Cloud-based API service provision system.

Citation Information

Patent Citations

  • API providing system, authentication server, API providing method, and program

    JP2019164590A

  • System and method for job execution in conjunction with cloud storage

    KR1020150062198A

  • Artificial intelligence scalp image diagnostic analysis system using big data and product recommendation system using the same

    KR102271558B1

  • Gateway device for API integration processing with security function and operation method thereof

    KR102528717B1

  • KR20220081542A