JP2019160130A - Usage fee determining program, usage fee determining method, and information processing device - Google Patents

Abstract

To provide a usage fee determining program with which it is possible to determine a usage fee when an error, except errors attributable to the user of a system, is detected.SOLUTION: The usage fee determining program causes a computer to execute the process of: analyzing a response to a request transmitted from the terminal of a user using a system; when a specific error, except errors attributable to the user of the system, is detected from the response as the result of analysis, managing a combination of the request content included in the request that corresponds to the response that includes the specific error and the specific error; specifying, on the basis of the combination, the degree of influence that represents the degree of burden by which the user is affected due to the specific error; and determining the usage fee of the system in accordance with the number of specific errors and the degree of influence.SELECTED DRAWING: Figure 7

Description

  This case relates to a usage fee determination program, a usage fee determination method, and an information processing apparatus.

  Systems that provide services such as access to shared storage (eg, database systems) and / or computing resources to clients are known (see, for example, Patent Document 1).

JP-T-2006-529597

  By the way, in many cases, the usage fee paid to the system provider by the user using the system described above is determined based on a Service Level Agreement (SLA) that guarantees the quality of service. For example, when the operation of the entire system is stopped, the usage fee may be reduced based on the SLA.

  On the other hand, if a temporary failure (hereinafter referred to as an error) occurs for an individual operation performed by the user instead of stopping the operation of the entire system, this is not covered by the SLA guarantee. For this reason, whether or not the usage fee is reduced is individually determined due to the cause of the error separately from the SLA. For example, when such a temporary error is caused by the system user, the usage fee is not reduced.

  In view of this, an object of one aspect is to provide a usage fee determination program, a usage fee determination method, and an information processing apparatus that can determine a usage fee that excludes errors caused by the user side of the system.

  In one embodiment, the usage fee determination program analyzes a response to a request transmitted from a terminal of a user who uses the system, and as a result of analyzing the response, the usage fee determination program results from the response to the user side of the system. When a specific error excluding an error is detected, the request content included in the request according to the response including the specific error and the combination of the specific error are managed, and based on the combination, the specific error A degree of influence representing the degree of burden affected by the user is specified, and the computer is caused to execute a process of determining a usage fee for the system according to the number of errors of the specific error and the degree of influence.

  It is possible to determine a usage fee that excludes errors caused by the user side of the system.

FIG. 1 is a diagram for explaining an example of a usage fee determination system. FIG. 2 shows an example of the hardware configuration of the API management server. FIG. 3 is an example of a block diagram of the usage fee determination system. FIG. 4A is an example of a contract management table. FIG. 4B is an example of the base contract management table. FIG. 4C is an example of a discount rate management table. FIG. 4D is an example of a usage fee management table. FIG. 5 is an example of an error information management table. FIG. 6 is an example of the impact management table. FIG. 7 is a flowchart showing an example of the operation of the API management server. FIG. 8A shows an example of a request message. FIG. 8B is an example of a response message. FIG. 9 is a flowchart showing an example of the operation of the third service providing server. FIG. 10 is a flowchart showing another example of the operation of the API management server. FIG. 11 shows an example of a charge management screen.

  Hereinafter, an embodiment for carrying out this case will be described with reference to the drawings.

  FIG. 1 is a diagram for explaining an example of the usage fee determination system SYS. The usage fee determination system SYS includes a user terminal 100, an application programming interface (API) management server 200 as an information processing apparatus, and an administrator terminal 300. In FIG. 1, a personal computer (PC) is shown as an example of the user terminal 100 and the administrator terminal 300. A smart device such as a smartphone or a tablet terminal may be used as the user terminal 100 or the administrator terminal 300 instead of the PC.

  The API management server 200 is deployed on the cloud CL. More specifically, the API management server 200 is deployed in the data center together with the first service providing server 210 and the third service providing server 230. The API management server 200, the first service providing server 210, the third service providing server 230, and the like are deployed in a data center or the like and connected to each other, whereby the cloud service providing system ST can be realized. The API management server 200 may be called an API end point. On the other hand, the first service providing server 210, the third service providing server 230, and the like may be referred to as back-end secure or a back-end system.

  The user terminal 100, the API management server 200, and the administrator terminal 300 are connected to each other via a communication network NW. An example of the communication network NW is the Internet. Therefore, both the user terminal 100 and the administrator terminal 300 can connect to the API management server 200 using the communication network NW.

  The user terminal 100 includes an input device 110, a display device 120, and a control device 130. Both the input device 110 and the display device 120 are connected to the control device 130. The control device 130 controls the display content of the display device 120 based on the information input from the input device 110. In addition, the control device 130 transmits information input from the input device 110 to the API management server 200 and receives information transmitted from the API management server 200. When receiving the information, the control device 130 controls the display content of the display device 120 based on the received information. Note that the administrator terminal 300 basically has the same configuration and functions as the user terminal 100, and thus description thereof is omitted.

  Here, as the information transmitted by the control device 130 described above, there is a request message in an API (REST-API) in REpresentational State Transfer (REST) format. The request message is information requesting various API calls (calls) managed by the cloud service providing system ST. On the other hand, information received by the control device 130 includes a response message in REST-API. The response message is information indicating a response to the request message.

  Therefore, the control device 130 controls the display content of the display device 120 based on the response message. Thereby, the display device 120 displays various contents according to the response message. Based on the content displayed on the display device 120, the user determines whether the service requested by the cloud service providing system ST is successful. For example, when an error has occurred due to an inappropriate operation such as a setting error of the user himself, the user requests a service from the cloud service providing system ST again. On the other hand, if an error has occurred due to an appropriate operation that is not an inappropriate operation of the user, the user performs a recovery process as necessary. Specifically, the user deletes unnecessary information generated in the course of the service provided by the cloud service providing system ST and remaining in the system as a recovery process.

  Details of the user terminal 100, the API management server 200, the first service providing server 210, and the like will be described below.

  FIG. 2 shows an example of the hardware configuration of the API management server 200. The user terminal 100 and the administrator terminal 300 described above have basically the same hardware configuration as that of the API management server 200, and thus the description thereof is omitted. Further, the first service providing server 210 and the third service providing server 230 described above have basically the same hardware configuration as the API management server 200, and thus the description thereof is omitted. As shown in FIG. 2, the API management server 200 includes at least a central processing unit (CPU) 200A, a random access memory (RAM) 200B, a read only memory (ROM) 200C, and a network I / F (interface) 200D. . The API management server 200 may include at least one of a hard disk drive (HDD) 200E, an input I / F 200F, an output I / F 200G, an input / output I / F 200H, and a drive device 200I as necessary. The CPU 200A to the drive device 200I are connected to each other by an internal bus 200J. That is, the API management server 200 can be realized by a computer.

  An input device 710 is connected to the input I / F 200F. Examples of the input device 710 include a keyboard and a mouse. The input device 110 described above is basically the same as the input device 710. A display device 720 is connected to the output I / F 200G. An example of the display device 720 is a liquid crystal display. The display device 120 described above is basically the same as the display device 720. A semiconductor memory 730 is connected to the input / output I / F 200H. Examples of the semiconductor memory 730 include a universal serial bus (USB) memory and a flash memory. The input / output I / F 200 </ b> H reads programs and data stored in the semiconductor memory 730. The input I / F 200F and the input / output I / F 200H include, for example, a USB port. The output I / F 200G includes a display port, for example.

  A portable recording medium 740 is inserted into the drive device 200I. Examples of the portable recording medium 740 include a removable disk such as a Compact Disc (CD) -ROM and a Digital Versatile Disc (DVD). The drive device 200I reads a program and data recorded on the portable recording medium 740. The network I / F 200D includes, for example, a LAN port. The network I / F 200D is connected to the communication network NW described above.

  In the above-described RAM 200B, a program stored in the ROM 200C or the HDD 200E is temporarily stored by the CPU 200A. In the RAM 200B, the program recorded on the portable recording medium 740 is temporarily stored by the CPU 200A. When the stored program is executed by the CPU 200A, the CPU 200A realizes various functions described later and executes various processes described later. In addition, what is necessary is just to make a program according to the flowchart mentioned later.

  Next, the function of the usage fee determination system SYS will be described with reference to FIGS.

  FIG. 3 is an example of a block diagram of the usage fee determination system SYS. In particular, in FIG. 3, the control device 130 provided in the user terminal 100, the API management server 200, the first service providing server 210, the second service providing server 220, and the third service providing server included in the cloud service providing system ST. 230 shows a functional configuration. FIG. 4A is an example of the contract management table T1. FIG. 4B is an example of the base contract management table T2. FIG. 4C is an example of the discount rate management table T5. FIG. 4D is an example of the usage fee management table T6. FIG. 5 is an example of the error information management table T3. FIG. 6 is an example of the influence management table T4. The administrator terminal 300 basically has the same functional configuration as that of the user terminal 100, and thus the description thereof is omitted.

  First, the control device 130 will be described. As illustrated in FIG. 3, the control device 130 includes an input unit 131, a display unit 132, a communication unit 133, and a control unit 134. The input unit 131, the display unit 132, and the communication unit 133 can be realized by the above-described input I / F 200F, output I / F 200G, and network I / F 200D, respectively. The control unit 134 can be realized by the above-described CPU 200A and RAM 200B, for example.

  The input unit 131 receives information output from the input device 110. For example, when the user designates a method, Uniform Resource Locator (URL, uniform resource locator) and request body, which will be described later, and performs an operation for the cloud service providing system ST to execute the API, on the input device 110, The input unit 131 receives information corresponding to the operation from the input device 110. The display unit 132 displays various contents on the display device 120 based on control by the control unit 134. Thereby, the display device 120 displays various contents.

  The control unit 134 controls the entire operation of the user terminal 100. For example, the control unit 134 generates the above-described request message based on information received by the input unit 131. When the control unit 134 generates a request message, the control unit 134 outputs the generated request message to the communication unit 133. Further, the control unit 134 controls the display unit 132 based on the response message output from the communication unit 133. The communication unit 133 controls communication between the control device 130 and the API management server 200. For example, the communication unit 133 transmits the request message output from the control unit 134 to the API management server 200. For example, the communication unit 133 receives a response message transmitted from the API management server 200 and outputs the response message to the control unit 134.

  Next, the API management server 200 will be described. As shown in FIG. 3, the API management server 200 includes a communication unit 201 and a processing unit 202. The communication unit 201 can be realized by the network I / F 200D described above. The processing unit 202 can be realized by the CPU 200A and the RAM 200B described above.

  The communication unit 201 controls communication between the API management server 200, the user terminal 100, and the administrator terminal 300. The communication unit 201 controls communication between the API management server 200 and the first service providing server 210, the second service providing server 220, and the third service providing server 230. Specifically, the communication unit 201 receives a request message transmitted from the user terminal 100. The communication unit 201 transmits the received request message to any of the first service providing server 210, the second service providing server 220, and the third service providing server 230.

  The communication unit 201 receives the response messages transmitted from the first service providing server 210, the second service providing server 220, and the third service providing server 230. The communication unit 201 transmits a response message to the user terminal 100 or the administrator terminal 300. More specifically, the communication unit 201 transmits a response message to the user terminal 100 when a request message corresponding to the response message is transmitted from the user terminal 100. On the other hand, when the request message corresponding to the response message is transmitted from the administrator terminal 300, the communication unit 201 transmits the response message to the administrator terminal 300. In addition, the communication unit 201 transmits error information described later to the first service providing server 210.

  The processing unit 202 analyzes the request message and response message received by the communication unit 201. The processing unit 202 executes various processes according to the analysis result. When the request message is analyzed, the processing unit 202 executes a service request process. Although details will be described later, the service request process specifies one of the first service providing server 210, the second service providing server 220, and the third service providing server 230 according to the analysis result, and specifies the communication unit 201. This is a process for sending a request message to any of the above. On the other hand, when the response message is analyzed, the processing unit 202 identifies the status code included in the response message.

  The processing unit 202 specifies a specific error code (specifically, the specific status code represents a specific error excluding an error code (specifically 400s) indicating an error caused by the user side of the cloud service providing system ST) Error information is generated. This error information includes a combination of the API name included in the request message corresponding to the response message including the specific error code and the specific error code. That is, when detecting a specific error code representing an error caused by the provider side of the cloud service providing system ST, the processing unit 202 generates error information including a combination of the API name and the specific code. When the processing unit 202 generates error information, the processing unit 202 outputs the generated error information to the communication unit 201. As described above, when the communication unit 201 receives error information, the communication unit 201 transmits the received error information to the first service providing server 210. Therefore, the processing unit 202 manages error information from the first service providing server 210.

  Next, the first service providing server 210, the second service providing server 220, and the third service providing server 230 will be described. As shown in FIG. 3, the first service providing server 210 includes a communication unit 211, a charging service providing unit 212, and a first storage unit 213. The second service providing server 220 includes a communication unit 221, a network service providing unit 222, and a second storage unit 223. The third service providing server 230 includes a communication unit 231, a compute service providing unit 232, and a third storage unit 233.

  Note that each of the communication units 211, 211, and 231 can be realized by the network I / F 200D described above. The accounting service providing unit 212, the network service providing unit 222, and the compute service providing unit 232 can be realized by the CPU 200A and the RAM 200B described above. The first storage unit 213, the second storage unit 223, and the third storage unit 233 can be realized by the HDD 200E described above.

  The communication unit 211 controls communication between the first service providing server 210 and the API management server 200. Similarly, the communication unit 221 controls communication between the second service providing server 220 and the API management server 200. The communication unit 231 controls communication between the third service providing server 230 and the API management server 200. For example, each of the communication units 211, 221, and 231 receives a request message transmitted from the API management server 200 or transmits a response message. For example, the communication unit 211 receives error information transmitted from the API management server 200.

  The billing service providing unit 212 provides API related to billing and contract as a service. More specifically, the billing service providing unit 212 manages, with the first storage unit 213, information related to usage charges imposed on various API calls provided by the cloud service providing system ST. Further, the billing service providing unit 212 manages contract information related to the contract between the provider and the user of the cloud service providing system ST by using the first storage unit 213. In addition, when the communication unit 211 receives error information, the billing service providing unit 212 stores the received error information in the first storage unit 213. When the communication unit 211 receives a request message, the billing service providing unit 212 executes processing according to the request content included in the received request message.

  Here, the first storage unit 213 stores various types of information including the error information described above. Specifically, as illustrated in FIG. 4A, the first storage unit 213 stores contract information regarding a contract between the provider and the user of the cloud service providing system ST. The contract information is managed by the contract management table T1. As shown in FIG. 4B, the first storage unit 213 stores base contract information that defines the relationship between the contract type and the fixed monthly fee. The base contract information is managed by the base contract management table T2.

  As shown in FIG. 5, the first storage unit 213 stores error information. Error information is managed by an error information management table T3. In particular, the error information includes a specific error code represented by the 500 series, an error message corresponding to the error code, an API name defined by the request content included in the request message, an error occurrence date and time, a contract ID, and the like as components. Contains. Each piece of error information is identified by an error ID.

  Further, as illustrated in FIG. 6, the first storage unit 213 stores the influence degree information. The influence degree information is managed by the influence degree management table T4. The influence degree information includes an API name, a specific error code, an influence degree defined by a combination of the API name and the specific error code, and an error message as constituent elements. Note that error messages may be excluded from the components. The degree of influence represents the degree of burden that a user is affected by an error according to a specific error code.

  For example, since the method name “get” belonging to the API name is a method that refers to a resource, even if an error occurs, the user does not have to perform the above-described deletion process. Registered in On the other hand, since the method name “create” is a method for generating a resource, if an error occurs, the user is required to perform the above-described deletion process, so a relatively large degree is registered as an influence degree. . Each of such impact information is identified by a discount ID.

  In addition, as shown in FIG.4 (c), the 1st memory | storage part 213 memorize | stores discount information. Discount information is information relating to a discount rate applied when discounting a usage fee before discount. Discount information is managed by a discount rate management table T5. Discount information includes the total value of the impact and the discount rate as components. The correspondence relationship between the total value of the influence levels and the discount rate is determined in advance. For example, when the total value of the influence degree is relatively large, a relatively large discount rate is registered. Conversely, when the total value of the influence levels is relatively small, a relatively small discount rate is registered.

  Moreover, as shown in FIG.4 (d), the 1st memory | storage part 213 memorize | stores usage fee information. The usage fee information is information relating to the usage fee charged to the user. The usage fee information is managed by the usage fee management table T6. Each usage fee information is identified by a monthly ID. In particular, the user is charged with a discounted fee obtained by applying a discount rate to the pre-discount fee that represents the pre-discount usage fee. In this way, the usage fee charged to the user is reduced based on the number of error information and the degree of influence of the burden caused to the user by the error information.

  In the present embodiment, the first storage unit 213 stores various types of information, but the contract information may be stored in another storage unit (not shown) different from the first storage unit 213. Contract information, base contract information, influence information, and discount information may be stored in the first storage unit 213 in advance. On the other hand, error information and usage fee information are dynamically stored in the first storage unit 213 by the billing service providing unit 212.

  Returning to FIG. 3, the network service providing unit 222 provides various APIs related to the network as services. More specifically, an API that allows a user to define network connectivity and address assignment in the cloud CL is provided as a service. For example, the network service providing unit 222 generates a virtual network infrastructure such as a network, a switch, a subnet, and a router based on the request message received by the communication unit 221 and manages it by the second storage unit 223. The network service providing unit 222 provides the virtual network infrastructure to devices (for example, a CPU and a memory) managed by the compute service providing unit 232. On the other hand, the compute service providing unit 232 provides various APIs related to the virtual machine as services, and manages the device by the third storage unit 233. For example, the compute service providing unit 232 generates a virtual machine instance using the hypervisor API and ends the process.

  Next, the operation of the usage fee determination system SYS will be described.

  FIG. 7 is a flowchart showing an example of the operation of the API management server 200. FIG. 8A shows an example of the request message RQ. FIG. 8B is an example of the response message RP. FIG. 9 is a flowchart showing an example of the operation of the third service providing server 230. The API management server 200 executes processing according to the flowchart shown in FIG. 7 every time a request message is received. Similarly, every time the third service providing server 230 receives a request message, the third service providing server 230 executes processing according to the flowchart shown in FIG. Even when the first service providing server 210 and the second service providing server 220 receive the request message, the process according to the flowchart shown in FIG. 9 is executed each time the request message is received.

  First, as shown in FIG. 7, when the communication unit 201 of the API management server 200 receives the request message RQ (step S101), the processing unit 202 analyzes the request message RQ received by the communication unit 201 (step S102). Specifically, as illustrated in FIG. 8A, the processing unit 202 analyzes the request line that is the first line of the request message RQ. The processing unit 202 may analyze a request header starting from the second line of the request message RQ and a request body following the request header.

  When the process of step S102 is completed, the processing unit 202 then executes a service request process (step S103). Here, the request line described above includes the method name (create in FIG. 8A) and the URL as request contents. In particular, the URL includes a service name (compute in FIG. 8A) and a resource name (server in FIG. 8A). Therefore, in the present embodiment, the processing unit 202 identifies the third service providing server 230 based on the service name of the URL, and causes the communication unit 201 to transmit the request message RQ to the third service providing server 230. Thereby, the communication unit 201 transmits the request message RQ to the third service providing server 230. If network is included in the service name of the URL, the processing unit 202 identifies the second service providing server 220.

  9, when the communication unit 231 receives the request message RQ, the compute service providing unit 232 executes processing according to the method name and the URL resource name described in the request line of the request message RQ (step S201). . In this embodiment, since create is described in the method name and server is described in the resource name of the URL, the compute service providing unit 232 generates a virtual server as a resource.

  When the process of step S201 is completed, the compute service providing unit 232 updates the third storage unit 233 (step S202) and generates a response message RP (step S203). When the process of step S203 is completed, the communication unit 231 transmits a response message RP to the API management server 200 (step S204).

  Returning to FIG. 7, when the communication unit 201 of the API management server 200 receives the response message RP (step S104), the processing unit 202 analyzes the response message RP (step S105). Specifically, as illustrated in FIG. 8B, the processing unit 202 analyzes the status line that is the first line of the response message RP. The processing unit 202 may analyze a response header starting from the second line of the response message RP and a response body following the response header.

  Here, the processing unit 202 determines whether or not the status code included in the status line is in the 200s (step S106). When the processing unit 202 determines that the status code is in the 200s (step S106: YES), the communication unit 201 transmits the response message RP without executing the subsequent steps S107 and S108 (step S109). . That is, when the status code is in the 200s, the processing unit 202 determines that the process of step S201 executed by the compute service providing unit 242 is successful, and the communication unit 201 transmits the response message RP to the user terminal 100.

  On the other hand, if the processing unit 202 determines that the status code is not in the 200 range (step S106: NO), it then determines whether the status code is in the 400 range (step S107). When the processing unit 202 determines that the status code is in the 400 range (step S107: YES), the communication unit 201 executes the process of step S109 without executing the process of the subsequent step S108. That is, when the status code is in the 400 range, an error has occurred in the process of step S201 executed by the compute service providing unit 232, but the processing unit 202 determines that the error is caused by the user, and the communication unit 201 returns a response. The message RP is transmitted to the user terminal 100.

  On the other hand, when the processing unit 202 determines that the status code is not in the 400 range (step S107: NO), it manages error information (step S108). That is, the processing unit 202 determines that the status code is in the 500s and manages error information. Specifically, the processing unit 202 acquires the service name and resource name included in the method name and URL described in the request line of the request message RQ, and generates an API name. Further, the processing unit 202 acquires, as response information, the status code included in the status line of the response message RP, the date / time included as the error occurrence date / time in the response header, and the error message and contract ID included in the response body. Then, the processing unit 202 generates error information including an API name and response information, adds an error ID to the error information, and outputs the error information to the communication unit 201. The communication unit 201 transmits the error information output from the processing unit 202 to the first service providing server 210. That is, the processing unit 202 manages error information by the first service providing server 210.

  When the process of step S108 is completed, the communication unit 201 executes the process of step S109. That is, the communication unit 201 transmits the response message RP to the user terminal 100. Thereby, the control apparatus 130 of the user terminal 100 receives the response message RP.

  FIG. 10 is a flowchart showing another example of the operation of the API management server 200. The API management server 200 executes processing according to the flowchart shown in FIG. 10 on a specific date such as the end of the month or the deadline of the usage fee billing period. The API management server 200 may cause the first service providing server 210 to execute processing according to the flowchart shown in FIG.

  For example, when the processing unit 202 detects the above-described specific date by the calendar function, the processing unit 202 starts a loop process as illustrated in FIG. 10 (step S301). When the processing unit 202 starts loop processing, the subsequent processing is executed over the number of contracts. When the loop process is started, first, the processing unit 202 identifies one of the contract IDs, and compares the SLA guarantee target date with the error occurrence date (step S302). More specifically, the processing unit 202 extracts a plurality of types of error codes corresponding to the identified contract ID from the error codes stored in the first storage unit 213, and counts the extracted error codes every day regardless of the type. To do. As a result, the number of occurrences of daily error information is specified regardless of the type of error code. If the processing unit 202 detects a frequent occurrence date of the error whose counted value is equal to or greater than the threshold, the processing unit 202 compares the frequent occurrence date of the error with the SLA guarantee target date.

  When the process of step S302 is completed, the processing unit 202 identifies error information that is not subject to discount application (step S303). For example, when the processing unit 202 compares the error frequent occurrence date and the SLA guaranteed date, if the error frequent occurrence date corresponds to the SLA guaranteed date, the error information on the frequent error occurrence date is not subject to the discount application. Specify as error information. This avoids double application of discounts. The processing unit 202 excludes error information that is not subject to discount application from subsequent processing targets.

  When the process of step S303 is completed, the processing unit 202 then specifies the influence degree (step S304). More specifically, the processing unit 202 specifies the degree of influence corresponding to the combination of the API name and the error code for each of the remaining error information excluding error information that is not subject to discount application. The processing unit 202 may refer to the influence degree information (see FIG. 6) stored in the first storage unit 213 when specifying the influence degree.

  When the process of step S304 is completed, the processing unit 202 then calculates the total value of the specified influence degree (step S305), and determines a discount rate according to the calculated total value (step S306). The processing unit 202 uses the number of errors in the error information when calculating the total value. For example, when there are three pieces of error information having a common combination of error code and API name, the degree of influence associated with the combination may be tripled. Then, the processing unit 202 may calculate the total value by adding the degree of influence multiplied by three to the degree of influence associated with another combination. Further, when determining the discount rate, the processing unit 202 may refer to discount information (see FIG. 4C) stored in the first storage unit 213.

  When the process of step S306 is completed, the processing unit 202 calculates a pre-discount charge (step S307). More specifically, the processing unit 202 first refers to the contract information (see FIG. 4A) and the base contract information (see FIG. 4B) stored in the first storage unit 213, and specifies the identified contract ID. Identify fixed monthly charges according to Next, the processing unit 202 specifies a metered charge according to the number of API calls and the usage time of the cloud service providing system ST. Note that the processing unit 202 may manage the number of API calls and usage time by the first storage unit 213. Then, the processing unit 202 calculates a pre-discount charge that is the sum of the specified fixed monthly charge and the metered charge.

  When the process of step S307 is completed, the processing unit 202 calculates a discounted fee (step S308). More specifically, the processing unit 202 calculates a discounted fee by applying the discount rate determined in the process of step S306 to the pre-discount fee calculated in the process of step S307. When calculating the discounted fee, the processing unit 202 stores usage fee information (see FIG. 4D) including the discounted fee in the first storage unit 213. When the processing unit 202 stores the usage fee information, the processing unit 202 specifies another contract ID different from the specified contract ID, and repeats the processing of steps S302 to S308. When the processing unit 202 stores the usage fee information for all the contract IDs, the processing unit 202 ends the loop processing (step S309) and ends the usage fee billing process.

  FIG. 11 shows an example of a charge management screen. The administrator terminal 300 displays a billing management screen based on an operation by an administrator who manages the cloud service providing system ST. For example, when the administrator performs an operation for displaying the charge management screen on the administrator terminal 300, the administrator terminal 300 transmits a request message RQ corresponding to the operation to the API management server 200. When the communication unit 201 of the API management server 200 receives the request message RQ transmitted from the administrator terminal 300, the processing unit 202 analyzes the request line. In the present embodiment, as a result of the analysis, the communication unit 201 transmits a request message RQ to the first service providing server 210.

  When the communication unit 211 of the first service providing server 210 receives the request message RQ, the charging service providing unit 212 executes processing according to the request content described in the request line of the request message RQ. For example, if get is described as the method name of the request line, the charging service providing unit 212 acquires usage fee information and the like from the first storage unit 213, and the communication unit 211 acquires the usage fee acquired by the charging service providing unit 212. A response message RP including information and the like is transmitted to the API management server 200.

  The communication unit 201 of the API management server 200 receives the response message RP transmitted from the first service providing server 210. When the communication unit 201 receives the response message RP, the processing unit 202 analyzes the status line. As a result of the analysis, if the status line includes status codes in the 200s, the communication unit 201 transmits a response message RP to the administrator terminal 300. As a result, the administrator terminal 300 displays a billing management screen including usage fee information. As shown in FIG. 11, when the administrator inputs the billing year and month and performs an operation of pressing the execution button BT with the pointer PT, the same processing as described above is performed, and the administrator terminal 300 displays a billing management screen including usage fee information according to the billing year and month.

  As described above, according to the present embodiment, the API management server 200 includes the processing unit 202. The processing unit 202 analyzes the response message RP for the request message RQ transmitted from the user terminal 100 of the user who uses the cloud service providing system ST. As a result of analyzing the response message RP, when the processing unit 202 detects a specific error from the response message RP excluding an error caused by the user of the cloud service providing system, the processing unit 202 responds to the response message RP including the specific error. The request content included in the request message RQ and a combination of specific errors are managed. Based on this combination, the processing unit 202 identifies the degree of influence that represents the degree of burden that the user is affected by a specific error, and the cloud service providing system ST depends on the number of errors and the degree of influence of the specific error. Determine usage fees. This makes it possible to determine a usage fee that excludes errors caused by the user side of the system. As a result, even if a temporary error is not caused by the user side of the cloud service providing system ST, the provider of the cloud service providing system ST is requested by the user to reduce the usage fee separately from the SLA. No need to

  The preferred embodiments of the present invention have been described in detail above, but the present invention is not limited to the specific embodiments according to the present invention, and various modifications are possible within the scope of the gist of the present invention described in the claims.・ Change is possible. For example, in the above-described embodiment, an error code is used as an example. However, since the error code corresponds to the error message, an error message may be used instead of the error code.

  In the embodiment described above, the first service providing server 210, the second service providing server 220, and the third service providing server 230 are components of the cloud service providing system ST. At least one of the second service providing server 220 and the third service providing server 230 may be excluded from the components of the cloud service providing system ST. In this case, at least one of the first service providing server 210, the second service providing server 220, and the third service providing server 230 may be connected to the communication network NW.

  Furthermore, in the above-described embodiment, the REST format has been described as an example of the API format, but another format different from the REST format may be used. For example, an API in another format may be used between the user terminal 100 and the API management server 200, and an REST API may be used between the API management server 200 and the first service providing server 210. In this case, the API management server 200 executes API format conversion.

  Furthermore, in the above-described embodiment, the description of a request message is used in order to avoid confusion with a request line or a request header, but the request message may be simply referred to as a request. The response message is the same as the request message.

In addition, the following additional notes are disclosed regarding the above description.
(Supplementary note 1) As a result of analyzing a response to a request transmitted from a terminal of a user who uses the system and analyzing the response, a specific error excluding an error caused by the user side of the system is obtained from the response. If detected, the request content included in the request corresponding to the response including the specific error and the combination of the specific error are managed, and the user is affected by the specific error based on the combination A usage fee determination program for causing a computer to execute a process of identifying an influence level representing the degree of the error and determining a usage fee for the system according to the number of errors of the specific error and the influence level.
(Additional remark 2) The said process calculates the total value of the said influence degree based on the said error number, determines the discount rate according to the calculated said total value based on the predetermined correspondence table, and determined the said The usage fee determination program according to appendix 1, wherein the usage fee for the system is determined based on a discount rate and a usage fee before discounting the system.
(Supplementary Note 3) The process counts the number of errors every day, and when an error frequent occurrence date in which the counted value is equal to or greater than a threshold is detected, the error frequent occurrence date and an object for guaranteeing the quality of service provided by the system The usage fee according to appendix 2, wherein the application of the discount rate to the usage fee before discounting of the system is excluded when the error occurrence date corresponds to the target date. Decision program.
(Additional remark 4) The said request content is a combination of the name of the service which the said system provides, the name of the method used by API, and the name of a resource, Any one of Additional remark 1 to 3 characterized by the above-mentioned. Usage fee determination program as described in.
(Supplementary Note 5) As a result of analyzing a response to a request transmitted from a terminal of a user who uses the system, and analyzing the response, a specific error excluding an error caused by the user side of the system is obtained from the response. If detected, the request content included in the request corresponding to the response including the specific error and the combination of the specific error are managed, and the user is affected by the specific error based on the combination A usage fee determination method in which a computer executes a process of specifying an influence level representing the degree of the error and determining a usage fee of the system according to the number of errors of the specific error and the influence level.
(Appendix 6) As a result of analyzing a response to a request transmitted from a terminal of a user who uses the system and analyzing the response, a specific error excluding an error caused by the user side of the system is obtained from the response. If detected, the request content included in the request corresponding to the response including the specific error and the combination of the specific error are managed, and the user is affected by the specific error based on the combination An information processing system comprising: a processing unit that identifies a degree of influence representing a degree of the error and determines a usage fee for the system according to the number of errors of the specific error and the degree of influence. apparatus.
(Additional remark 7) The said process part calculated the total value of the said influence degree based on the said error number, and determined the discount rate according to the calculated said total value based on the predetermined correspondence table, and determined The information processing apparatus according to appendix 6, wherein the system usage fee is determined based on the discount rate and the usage fee before discounting the system.
(Supplementary Note 8) The processing unit counts the number of errors every day, and when an error frequent occurrence date in which the counted value is equal to or greater than a threshold value is detected, the error frequent occurrence date and the quality of service provided by the system are guaranteed. The information according to appendix 7, wherein comparison with a target date is performed, and when the error occurrence date corresponds to the target date, the application of the discount rate to the usage fee before discounting of the system is excluded. Processing equipment.
(Additional remark 9) The said request content is a combination of the name of the service which the said system provides, the name of the method used by API, and the name of a resource, Any one of additional remark 6 to 8 characterized by the above-mentioned. The information processing apparatus described in 1.

SYS usage fee determination system ST cloud service providing system 100 user terminal 200 API management server 201 communication unit 202 processing unit 300 administrator terminal

Claims (6)

Analyze the response to the request sent from the terminal of the user who uses the system,
As a result of analyzing the response, when a specific error is detected from the response excluding an error caused by a user of the system, the request content included in the request corresponding to the response including the specific error and the specific Manage combinations of errors,
Based on the combination, an impact level representing the degree of burden that the user is affected by the specific error is specified,
The usage fee of the system is determined according to the number of errors of the specific error and the degree of influence.
A usage fee determination program that causes a computer to execute processing. The process calculates a total value of the degree of influence based on the number of errors, determines a discount rate according to the calculated total value based on a predetermined correspondence table, and determines the discount rate and the determined discount rate Determining the usage fee of the system based on the usage fee before discounting the system;
The use fee determining program according to claim 1, wherein: The process counts the number of errors for each day, and when an error occurrence day with a counted value equal to or greater than a threshold value is detected, the error occurrence day is compared with a target day for guaranteeing the quality of service provided by the system. And, when the error occurrence date corresponds to the target date, excluding application of the discount rate to the usage fee before discounting the system,
The use fee determining program according to claim 2, wherein: The request content is a combination of the name of a service provided by the system, the name of a method used in the API, and the name of a resource.
The usage fee determination program according to any one of claims 1 to 3, wherein the usage fee is determined. Analyze the response to the request sent from the terminal of the user who uses the system,
As a result of analyzing the response, when a specific error is detected from the response excluding an error caused by a user of the system, the request content included in the request corresponding to the response including the specific error and the specific Manage combinations of errors,
Based on the combination, an impact level representing the degree of burden that the user is affected by the specific error is specified,
The usage fee of the system is determined according to the number of errors of the specific error and the degree of influence.
A usage fee determination method in which processing is executed by a computer. Analyze the response to the request sent from the terminal of the user who uses the system,
As a result of analyzing the response, when a specific error is detected from the response excluding an error caused by a user of the system, the request content included in the request corresponding to the response including the specific error and the specific Manage combinations of errors,
Based on the combination, an impact level representing the degree of burden that the user is affected by the specific error is specified,
The usage fee of the system is determined according to the number of errors of the specific error and the degree of influence.
An information processing apparatus having a processing unit for executing processing.

Images