JP7006408B2 - Usage fee determination program, usage fee determination method, and information processing equipment - Google Patents

Description

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

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

Special Table 2016-529597

By the way, the usage fee paid by the user who uses the above-mentioned system to the system provider is often determined based on the Service Level Agreement (SLA) which guarantees the quality of service. For example, if 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 in an individual operation performed by the user instead of stopping the operation of the entire system, it is not covered by the SLA warranty. Therefore, whether or not the usage fee is reduced is determined individually due to the cause of the error, separately from the SLA. For example, if such a temporary error is caused by the user of the system, the usage fee will not be reduced.

Therefore, in one aspect, it is an object of the present invention to provide a usage fee determination program, a usage fee determination method, and an information processing apparatus capable of determining a usage fee excluding errors caused by the user side of the system.

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

It is possible to determine the usage fee excluding the error 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 is 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 influence degree management table. FIG. 7 is a flowchart showing an example of the operation of the API management server. FIG. 8A is 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 is an example of a billing management screen.

Hereinafter, a mode 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 device, and an administrator terminal 300. In FIG. 1, a personal computer (PC) is shown as an example of a user terminal 100 and an administrator terminal 300. Instead of the PC, a smart device such as a smartphone or a tablet terminal may be used as the user terminal 100 or the administrator terminal 300.

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, the third service providing server 230, and the like. The cloud service providing system ST can be realized by deploying the API management server 200, the first service providing server 210, the third service providing server 230, and the like in a data center or the like and connecting them to each other. The API management server 200 may be called an API endpoint or the like. On the other hand, the first service providing server 210, the third service providing server 230, and the like may be referred to as a 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 the communication network NW. The communication network NW includes, for example, the Internet. Therefore, both the user terminal 100 and the administrator terminal 300 can connect to the API management server 200 by 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. Further, the control device 130 transmits the information input from the input device 110 to the API management server 200, and receives the information transmitted from the API management server 200. When the control device 130 receives the information, the control device 130 controls the display content of the display device 120 based on the received information. Since the administrator terminal 300 basically has the same configuration and function as the user terminal 100, the description thereof will be omitted.

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

Therefore, the control device 130 controls the display content of the display device 120 based on the response message. As a result, the display device 120 displays various contents according to the response message. The user determines the success or failure of the service requested to the cloud service providing system ST based on the content displayed on the display device 120. For example, if an error occurs due to an improper operation such as a setting error of the user himself / herself, the user requests the service from the cloud service providing system ST again. On the other hand, if an error occurs due to an appropriate operation that is not the user's own inappropriate operation, the user performs recovery processing as necessary. Specifically, the user performs a process of deleting unnecessary information generated in the process of the service provided by the cloud service providing system ST and remaining in the system as a recovery process.

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

FIG. 2 is an example of the hardware configuration of the API management server 200. Since the user terminal 100 and the administrator terminal 300 described above have basically the same hardware configuration as the API management server 200, the description thereof will be omitted. Further, since the above-mentioned first service providing server 210, third service providing server 230, and the like have basically the same hardware configuration as the API management server 200, the description thereof will be 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 / F200F, an output I / F200G, an input / output I / F200H, and a drive device 200I, if 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. The input device 710 includes, for example, a keyboard and a mouse. The above-mentioned input device 110 is basically the same as the input device 710. A display device 720 is connected to the output I / F 200G. The display device 720 includes, for example, 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 200H 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, for example, a display port.

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

In the RAM 200B described above, the program stored in the ROM 200C or the HDD 200E is temporarily stored by the CPU 200A. The program recorded on the portable recording medium 740 is temporarily stored in the RAM 200B by the CPU 200A. When the CPU 200A executes the stored program, the CPU 200A realizes various functions described later and also executes various processes described later. The program may be adapted to the flowchart described later.

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

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 included in the user terminal 100, the API management server 200 included in the cloud service providing system ST, the first service providing server 210, the second service providing server 220, and the third service providing server It represents the functional configuration of 230. 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 degree management table T4. Since the administrator terminal 300 basically has the same functional configuration as the user terminal 100, the description thereof will be omitted.

First, the control device 130 will be described. As shown 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-mentioned input I / F200F, output I / F200G, and network I / F200D, respectively. The control unit 134 can be realized by, for example, the CPU 200A and the RAM 200B described above.

The input unit 131 receives the information output from the input device 110. For example, when the user specifies the method, Uniform Resource Locator (URL, unified resource location specifier) and request body described later, and causes the cloud service providing system ST to execute the API, the input device 110 is operated. 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 the control by the control unit 134. As a result, 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-mentioned request message based on the 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 the 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 the response message transmitted from the API management server 200 and outputs it 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 above-mentioned network I / F200D. 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. Further, 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 the request message transmitted from the user terminal 100. The communication unit 201 transmits the received request message to any one 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 message 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, when the request message corresponding to the response message is transmitted from the user terminal 100, the communication unit 201 transmits the response message to 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 the error information described later to the first service providing server 210.

The processing unit 202 analyzes the request message and the 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 the service request processing. Although the details will be described later, the service request processing 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. It is a process to send a request message to one of the servers. On the other hand, when the response message is analyzed, the processing unit 202 specifies the status code included in the response message.

The processing unit 202 has a specific status code (specifically, a specific error code (specifically, 400s) excluding an error code (specifically, 400s) indicating an error caused by the user of the cloud service providing system ST. When a 500 series) is detected, error information is generated. This error information includes a combination of the API name included in the request message corresponding to the response message containing the specific error code and the specific error code. That is, when the processing unit 202 detects 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 the 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 the error information, the communication unit 201 transmits the received error information to the first service providing server 210. Therefore, the processing unit 202 manages the 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 billing 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.

Each communication unit 211,221,231 can be realized by the above-mentioned network I / F200D. The billing 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 the communication between the second service providing server 220 and the API management server 200. The communication unit 231 controls the communication between the third service providing server 230 and the API management server 200. For example, the communication units 211,221,231 all receive the request message transmitted from the API management server 200 and transmit the response message. For example, the communication unit 211 receives the error information transmitted from the API management server 200.

The billing service providing unit 212 provides APIs related to billing and contracts as a service. More specifically, the billing service providing unit 212 manages information on the usage fee imposed on the call of various APIs provided by the cloud service providing system ST by the first storage unit 213. Further, the billing service providing unit 212 manages the contract information regarding the contract between the provider and the user of the cloud service providing system ST by the first storage unit 213. In addition, when the communication unit 211 receives the 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 the 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 above-mentioned error information. Specifically, as shown in FIG. 4A, the first storage unit 213 stores contract information regarding the 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. Further, as shown in FIG. 4B, the first storage unit 213 stores the base contract information that defines the relationship between the contract type and the fixed monthly charge. The base contract information is managed by the base contract management table T2.

Further, as shown in FIG. 5, the first storage unit 213 stores error information. The error information is managed by the 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. Includes. Each of the error information is identified by an error ID.

Further, as shown in FIG. 6, the first storage unit 213 stores the influence degree information. The impact level information is managed by the impact level management table T4. The impact information includes the API name, the specific error code, the impact defined by the combination of the API name and the specific error code, and the error message as components. The error message may be excluded from the components. The degree of influence indicates the degree of burden on the user due to an error corresponding 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-mentioned deletion process, so a relatively small degree has an impact. To be registered in. On the other hand, since the method name "create" is a method for generating resources, when an error occurs, the user is required to perform the above-mentioned deletion process, so a relatively large degree is registered as the degree of influence. .. Each of such impact information is identified by a discount ID.

In addition, as shown in FIG. 4C, the first storage unit 213 stores discount information. The discount information is information on the discount rate applied when discounting the usage fee before discount. The discount information is managed by the discount rate management table T5. The discount information includes the total value of the degree of influence and the discount rate as components. The correspondence between the total value of the degree of influence and the discount rate is predetermined. For example, when the total value of the degree of influence is relatively large, a relatively large discount rate is registered. On the contrary, when the total value of the influence degree is relatively small, a relatively small discount rate is registered.

Further, as shown in FIG. 4D, the first storage unit 213 stores the usage fee information. The usage fee information is information about the usage fee charged to the user. The usage fee information is managed by the usage fee management table T6. Each of the usage fee information is identified by the monthly ID. In particular, the user is charged the post-discounted charge to which the discount rate is applied to the pre-discounted charge representing the pre-discounted usage charge. 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 by the error information on the user.

In the present embodiment, the first storage unit 213 stores various information, but the contract information may be stored in another storage unit (not shown) different from the first storage unit 213. Further, the contract information, the base contract information, the influence degree information, and the discount information may be stored in the first storage unit 213 in advance. On the other hand, the error information and the 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 a service. More specifically, the API that allows the user to define the network connectivity and address allocation in the cloud CL is provided as a service. For example, the network service providing unit 222 creates a virtual network infrastructure such as a network, a switch, a subnet, and a router based on a request message received by the communication unit 221 and manages it by the second storage unit 223. Then, the network service providing unit 222 provides the virtual network infrastructure to the device (for example, CPU, memory, etc.) 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 a service, and the third storage unit 233 manages the device. For example, the compute service provider 232 uses the hypervisor API to create and terminate a virtual machine instance.

Subsequently, 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 is 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. Each time the API management server 200 receives a request message, the API management server 200 executes a process according to the flowchart shown in FIG. Similarly, each time the third service providing server 230 receives the request message, the third service providing server 230 executes the process 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, each time the request message is received, the process according to the flowchart shown in FIG. 9 is executed.

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 shown in FIG. 8A, the processing unit 202 analyzes the request line, which is the first line of the request message RQ. The processing unit 202 may analyze the request header starting from the second line of the request message RQ and the request body following the request header.

When the processing in step S102 is completed, the processing unit 202 then executes the service request processing (step S103). Here, the above-mentioned request line includes a method name (create in FIG. 8A) and a 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. As a result, 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 specifies the second service providing server 220.

Moving to FIG. 9, when the communication unit 231 receives the request message RQ, the compute service providing unit 232 executes processing according to the method name described in the request line of the request message RQ and the resource name of the URL (step S201). .. In the present 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 creates the 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 the 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 shown in FIG. 8B, the processing unit 202 analyzes the status line, which is the first line of the response message RP. The processing unit 202 may analyze the response header starting from the second line of the response message RP and the 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 a response message RP without executing the subsequent processes of steps S107 and S108 (step S109). .. That is, when the status code is in the 200s, the processing unit 202 determines that the processing 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, when the processing unit 202 determines that the status code is not in the 200s (step S106: NO), it then determines whether or not the status code is in the 400s (step S107). When the processing unit 202 determines that the status code is in the 400s (step S107: YES), the communication unit 201 executes the process of step S109 without executing the subsequent process of step S108. That is, when the status code is in the 400s, an error has occurred in the processing 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 responds. 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 series (step S107: NO), the processing unit 202 manages the error information (step S108). That is, the processing unit 202 determines that the status code is in the 500s, and manages the error information. Specifically, the processing unit 202 acquires the service name and the resource name included in the method name and the URL described in the request line of the request message RQ, respectively, and generates the API name. Further, the processing unit 202 acquires the status code included in the status line of the response message RP, the date and time included as the error occurrence date and time in the response header, and the error message and contract ID included in the response body as response information. Then, the processing unit 202 generates error information including the API name and the response information, assigns 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 the 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. As a result, the control device 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 day such as the end of the month or the closing date of the usage fee billing period. The API management server 200 may cause the first service providing server 210 to execute the process according to the flowchart shown in FIG.

When, for example, the above-mentioned specific day is detected by the calendar function, the processing unit 202 starts loop processing as shown in FIG. 10 (step S301). When the processing unit 202 starts the loop processing, the subsequent processing is executed for the number of contracts. When the loop processing 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 specified contract ID from the error codes stored in the first storage unit 213, and counts the extracted error codes daily regardless of the type. do. As a result, the number of daily error information occurrences is specified regardless of the type of error code. Then, when the processing unit 202 detects the error occurrence frequent occurrence date when the counted value becomes equal to or more than the threshold value, the error occurrence frequent occurrence date and the SLA guarantee target date are compared.

When the processing in step S302 is completed, the processing unit 202 identifies the error information that is not subject to the discount (step S303). For example, as a result of comparing the error occurrence frequent occurrence date and the SLA guarantee target date, the processing unit 202 does not apply the discount to the error information of the error occurrence frequent occurrence date when the error occurrence frequent occurrence date corresponds to the SLA guarantee target date. Identify as error information. This avoids double application of discounts. The processing unit 202 excludes the error information that is not subject to the discount from the subsequent processing targets.

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

When the processing of step S304 is completed, the processing unit 202 then calculates the total value of the specified influence degree (step S305), and determines the 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 error information in which the combination of the error code and the API name is common, the degree of influence associated with the combination may be tripled. Then, the processing unit 202 may calculate the total value by adding the tripled influence degree to the influence degree associated with the other combination. Further, when the processing unit 202 determines the discount rate, the processing unit 202 may refer to the discount information (see FIG. 4C) stored in the first storage unit 213.

When the processing in step S306 is completed, the processing unit 202 calculates the 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 identifies the contract ID. Specify a fixed monthly fee according to. Next, the processing unit 202 specifies pay-as-you-go billing according to the number of API calls and the usage time of the cloud service providing system ST. The number of API calls and the usage time may be managed by the processing unit 202 by the first storage unit 213. Then, the processing unit 202 calculates the pre-discount charge which is the sum of the specified fixed monthly charge and the pay-as-you-go charge.

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

FIG. 11 is an example of a billing management screen. The administrator terminal 300 displays the billing management screen based on the operation by the administrator who manages the cloud service providing system ST. For example, when the administrator performs an operation to display the billing management screen to the administrator terminal 300, the administrator terminal 300 sends 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 the 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 billing service providing unit 212 executes a process 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 billing 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 contains a status code in the 200s, the communication unit 201 transmits the response message RP to the administrator terminal 300. As a result, the administrator terminal 300 displays a billing management screen including usage fee information and the like. As shown in FIG. 11, when the administrator inputs the billing target date and presses the execution button BT with the pointer PT, the same processing as the above-described processing is performed, and the administrator terminal The 300 displays a billing management screen including usage fee information according to the billing target date.

As described above, according to the present embodiment, the API management server 200 includes a 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, the processing unit 202 responds to the response message RP including the specific error when it detects a specific error excluding the error caused by the user side of the cloud service providing system from the response message RP. Request message Manages the combination of the request content included in the RQ and a specific error. Based on this combination, the processing unit 202 identifies the degree of impact indicating the degree of burden that the user is affected by a specific error, and the cloud service providing system ST is determined according to the number of errors and the degree of impact of the specific error. Determine the usage fee for. As a result, it is possible to determine the usage fee excluding the error caused by the user side of the system. As a result, even if the temporary error is not caused by the user of the cloud service provision system ST, the provider of the cloud service provision system ST is requested by the user to reduce the usage fee separately from the SLA. You don't have to.

Although the preferred embodiments of the present invention have been described in detail above, the present invention is not limited to the specific embodiments of the present invention, and various modifications are made within the scope of the gist of the present invention described in the claims.・ Can be changed. For example, in the above-described embodiment, the error code is used as an example, but since the error code and the error message correspond to each other, the error message may be used instead of the error code.

Further, in the above-described embodiment, the first service providing server 210, the second service providing server 220, and the third service providing server 230 are the components of the cloud service providing system ST, but the first service providing server 210 and the first service providing server 210 are used. 2 At least one of the 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.

Further, 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, another type of API may be used between the user terminal 100 and the API management server 200, and a REST type 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.

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

The following additional notes will be further disclosed with respect to the above explanation.
(Appendix 1) As a result of analyzing the response to the request sent from the terminal of the user who uses the system and analyzing the response, a specific error excluding the error caused by the user side of the system is obtained from the response. When detected, the combination of the request content included in the request corresponding to the response including the specific error and the specific error is managed, and the user is affected by the specific error based on the combination. A usage fee determination program that causes a computer to execute a process that specifies the degree of influence representing the degree of the above and determines the usage fee of the system according to the number of errors of the specific error and the degree of impact.
(Appendix 2) In the above-mentioned processing, the total value of the degree of influence is calculated based on the number of errors, and the discount rate according to the calculated total value is determined and determined based on a predetermined correspondence table. The usage fee determination program according to Appendix 1, wherein the usage fee of the system is determined based on the discount rate and the usage fee of the system before discount.
(Appendix 3) The process counts the number of errors on a daily basis, and when an error frequent occurrence date in which the counted value exceeds the threshold value is detected, the error frequent occurrence date and the quality of the service provided by the system are guaranteed. The usage fee according to Appendix 2, characterized in that, when the error frequency date corresponds to the target day, the application of the discount rate to the pre-discounted usage fee of the system is excluded. Decision program.
(Appendix 4) The content of the request is a combination of the name of the service provided by the system, the name of the method used in the API, and the name of the resource. Usage fee determination program described in.
(Appendix 5) As a result of analyzing the response to the request sent from the terminal of the user who uses the system and analyzing the response, a specific error excluding the error caused by the user side of the system is obtained from the response. When detected, the combination of the request content included in the request corresponding to the response including the specific error and the specific error is managed, and the user is affected by the specific error based on the combination. A method of determining a usage fee in which a computer executes a process, in which the degree of influence representing the degree of the above is specified, and the usage fee of the system is determined according to the number of errors of the specific error and the degree of impact.
(Appendix 6) As a result of analyzing the response to the request sent from the terminal of the user who uses the system and analyzing the response, a specific error excluding the error caused by the user side of the system is obtained from the response. When detected, the combination of the request content included in the request corresponding to the response including the specific error and the specific error is managed, and the user is affected by the specific error based on the combination. Information processing characterized by having a processing unit for executing processing, which specifies the degree of influence representing the degree of the above and determines the usage fee of the system according to the number of errors of the specific error and the degree of influence. Device.
(Appendix 7) The processing unit calculates the total value of the degree of influence based on the number of errors, and determines and determines the discount rate according to the calculated total value based on a predetermined correspondence table. The information processing apparatus according to Appendix 6, wherein the usage fee of the system is determined based on the discount rate and the usage fee of the system before discount.
(Appendix 8) The processing unit counts the number of errors on a daily basis, and when it detects an error-prone date when the counted value exceeds the threshold value, it guarantees the error-prone date and the quality of the service provided by the system. The information described in Appendix 7, characterized in that, when the error frequency date corresponds to the target date, the application of the discount rate to the pre-discount usage fee of the system is excluded from the comparison with the target date. Processing device.
(Appendix 9) The content of the request is a combination of the name of the service provided by the system, the name of the method used in the API, and the name of the resource. The information processing device described in.

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

Claims (6)

It analyzes the response to the request sent from the terminal of the user who uses the system, and analyzes it.
As a result of analyzing the response, when a specific error excluding the error caused by the user side of the system is detected from the response, the request content included in the request corresponding to the response including the specific error and the specification are specified. Manage error combinations and
Based on the combination, the degree of influence indicating the degree of burden on the user due to 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. In the process, the total value of the degree of influence is calculated based on the number of errors, the discount rate according to the calculated total value is determined based on a predetermined correspondence table, and the determined discount rate and the said The usage fee of the system is determined based on the usage fee of the system before discount.
The usage fee determination program according to claim 1. The process counts the number of errors on a daily basis, and when an error frequency date in which the counted value exceeds the threshold value is detected, the error frequency date is compared with the target date for guaranteeing the quality of the service provided by the system. However, if the error frequency date corresponds to the target date, the application of the discount rate to the pre-discounted usage fee of the system is excluded.
The usage fee determination program according to claim 2, characterized in that. The request content is a combination of the name of the service provided by the system, the name of the method used in the API, and the name of the resource.
The usage fee determination program according to any one of claims 1 to 3, characterized in that. It analyzes the response to the request sent from the terminal of the user who uses the system, and analyzes it.
As a result of analyzing the response, when a specific error excluding the error caused by the user side of the system is detected from the response, the request content included in the request corresponding to the response including the specific error and the specification are specified. Manage error combinations and
Based on the combination, the degree of influence indicating the degree of burden on the user due to 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.
How to determine the usage fee for the computer to perform the process. It analyzes the response to the request sent from the terminal of the user who uses the system, and analyzes it.
As a result of analyzing the response, when a specific error excluding the error caused by the user side of the system is detected from the response, the request content included in the request corresponding to the response including the specific error and the specification are specified. Manage error combinations and
Based on the combination, the degree of influence indicating the degree of burden on the user due to 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 device characterized by having a processing unit that executes processing.

Images