Renewal assistance system, renewal assistance method, and renewal assistance program

Abstract

The present invention realizes a renewal assistance system that obtains suitable QoS during renewal of a system. The renewal assistance system comprises: an acquisition unit that acquires a second service requirement modified from a first service requirement; a design unit that designs a specific configuration after renewal of a target system by repeatedly executing a reification procedure for generating one or more abstract configurations or specific configurations with respect to the second service requirement by specifying and applying one or more corresponding reification rules to an abstract configuration; an evaluation unit that calculates an evaluation value indicating a degree of impact on QoS resulting from renewal of the target system using a QoS evaluation function and the state of each component included in a specific configuration designed by the design unit; and a determination unit whereby determination of whether to wait or execute renewal of the target system is performed using the evaluation value and load information regarding the load of the target system.

Description

Renewal support system, renewal support method, and renewal support program

[0001] The present disclosure relates to a renewal support system, a renewal support method, and a renewal support program.

[0002] Technologies for supporting computer system upgrades are known. One example of such a technology is described in Patent Document 1. In the load balancing control method described in Patent Document 1, a load balancing mechanism distributes requests received from client terminals among multiple server nodes so as to distribute the load on each server node, a configuration change mechanism calculates the amount of resources required when a configuration change is made to start or stop a service, the load balancing mechanism refers to a load management table and secures the calculated amount of resources for server nodes that require that amount, and then the configuration change mechanism executes the configuration change.

[0003] Furthermore, Patent Document 2 describes a system configuration derivation device that includes a storage unit that stores concretization rules that specify a method for concretizing abstract configuration information, which is information indicating the configuration of a system that includes undetermined parts, by determining the undetermined parts of the abstract configuration information, and a generation unit that generates system configuration information, which is information indicating the configuration of a system that does not include undetermined parts based on the configuration requirements, by concretizing the abstract configuration information included in the configuration requirements of the system using the stored concretization rules.

[0004] Furthermore, Patent Document 3 discloses a deployment device that easily applies a system configuration definition file created for a certain environment to system deployment in another environment. The component information storage unit of the deployment device stores component information including configuration information for each component constituting the system that is independent of the deployment tool, and a deployment process by the deployment tool for each combination of each component and each deployment tool that can be used to deploy the component. The component identification unit identifies a deployment process corresponding to a specified deployment tool for each component based on the component information. The order determination unit determines the execution order of the identified deployment processes based on the dependency relationships between the components. The deployment execution unit deploys multiple components by applying the identified deployment processes to the configuration information of the components and executing them in accordance with the execution order.

[0005] Japanese Patent Application Publication No. 2009-217373 International Publication No. 2019 / 216082 International Publication No. 2017 / 017937

[0006] In the technology described in Patent Document 1, when a system is updated, the QoS (Quality of Service) may be reduced depending on the status (normal operation, stopped, standby, etc.) of the components (servers, applications, etc.) included in the system. The same applies to the technologies described in Patent Documents 2 and 3.

[0007] The present disclosure has been made in view of the above problems, and an exemplary purpose thereof is to provide a technique for making QoS appropriate during system upgrade.

[0008] An exemplary aspect of the present disclosure provides a renewal support system including: an acquisition unit that acquires second service requirements that have been changed from first service requirements; a design unit that designs a concrete configuration of the target system after renewal by repeatedly executing a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referencing a plurality of concretization rules that define a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more corresponding concretization rules to the abstract configuration; and a status management unit that manages the status of each component included in the concrete configuration designed by the design unit. and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that the update of the target system will have from the state of each of the component parts; an evaluation means for calculating the evaluation value using the QoS evaluation function; a calculation means for calculating load information related to the load on the target system; and a determination means for determining whether to wait or execute the update of the target system using the evaluation value and the load information, wherein the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified by the design means.

[0009] An exemplary aspect of the present disclosure provides a renewal support method, comprising: an acquisition process in which at least one processor acquires second service requirements that have been changed from first service requirements; a design process in which the at least one processor repeatedly executes a concretization procedure on the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that define a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more corresponding concretization rules to the abstract configuration, thereby designing a concrete configuration of the target system after renewal; and a design process in which the at least one processor performs a concretization procedure on the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that define a method for concretizing an abstract configuration of the target system that provides a service, the design process generating one or more concrete configurations after renewal, the concrete configuration of the target system ... The design process includes an evaluation process that calculates an evaluation value using the state of components and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that updating the target system will have from the state of each component part; a calculation process in which the at least one processor calculates load information related to the load on the target system; and a determination process in which the at least one processor uses the evaluation value and the load information to determine whether to wait or execute updating the target system, wherein the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for a QoS evaluation function associated with the one or more instantiation rules identified in the design process.

[0010] An exemplary aspect of the present disclosure provides a renewal support program for causing a computer to function as a renewal support system, the program comprising: an acquisition unit for acquiring second service requirements that have been changed from first service requirements; a design unit for designing a post-renewal concrete configuration of the target system by repeatedly executing a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referencing a plurality of concretization rules that define a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more corresponding concretization rules to the abstract configuration; and a determining means for determining whether to wait or execute the update of the target system, using the evaluation value and the load information, and wherein the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified by the design means.

[0011] According to an exemplary aspect of the present disclosure, an exemplary effect is achieved in that a technique for optimizing QoS during system upgrade can be provided.

[0012] FIG. 1 is a block diagram showing a configuration of a renewal support system according to the present disclosure. FIG. 2 is a flow diagram showing the flow of a renewal support method according to the present disclosure. FIG. 3 is a block diagram showing the configuration of an information processing device according to the present disclosure. FIG. 4 is a diagram showing an example of a specific configuration designed by a design unit according to the present disclosure. FIG. 5 is a flow diagram showing an example of the flow of a renewal support method according to the present disclosure. FIG. 6 is a diagram showing a specific example of a QoS evaluation function according to the present disclosure. FIG. 7 is a diagram showing an example of a renewal procedure according to the present disclosure. FIG. 8 is a block diagram showing the configuration of a computer that functions as a renewal support system and an information processing device according to the present disclosure.

[0013] The following are examples of embodiments of the present invention. However, the present invention is not limited to the exemplary embodiments shown below, and various modifications are possible within the scope of the claims. For example, embodiments obtained by appropriately combining the technologies (part or all of the products or methods) employed in the exemplary embodiments shown below may also be included in the scope of the present invention. Furthermore, embodiments obtained by appropriately omitting some of the technologies employed in the exemplary embodiments shown below may also be included in the scope of the present invention. Furthermore, the effects mentioned in the exemplary embodiments shown below are examples of effects expected in the exemplary embodiments, and do not define the scope of the present invention. In other words, embodiments that do not exhibit the effects mentioned in the exemplary embodiments shown below may also be included in the scope of the present invention.

[0014] [First Exemplary Embodiment] A first exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. This exemplary embodiment is a basic form for each of the exemplary embodiments described below. Note that the scope of application of each technique employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technique employed in this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical obstacles arise. Furthermore, each technique shown in the drawings referenced to explain this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical obstacles arise.

[0015] (Configuration of the renewal support system) The configuration of the renewal support system 1 will be described with reference to Fig. 1. Fig. 1 is a block diagram showing the configuration of the renewal support system 1. As shown in Fig. 1, the renewal support system 1 includes an acquisition unit 11, a design unit 12, an evaluation unit 13, a calculation unit 14, and a determination unit 15.

[0016] The acquisition unit 11 acquires second service requirements that have been changed from the first service requirements. The design unit 12 has a function of executing a concretization procedure that references a plurality of concretization rules that define a method for concretizing an abstract configuration of a target system that provides a service, and identifies and applies one or more concretization rules corresponding to the abstract configuration to generate one or more abstract or concrete configurations, and designs a concrete configuration of the target system after the update by repeatedly executing the concretization procedure on the second service requirements acquired by the acquisition unit 11.

[0017] Here, an abstract configuration is a configuration that includes abstract elements. The abstract elements included in the abstract configuration need to be concretized according to the concretization rules. Concretizing an abstract configuration means concretizing the abstract elements included in the abstract configuration. Concretization rules prescribe a method for concretizing the abstract configuration of a target system. As an example, the concretization rules are composed of information representing the configuration of the part to be concretized and information representing the configuration after the target part has been concretized. A specific partial configuration expressed by information representing the configuration of the part to be concretized included in the abstract configuration is concretized into a configuration expressed by information representing the configuration after the target part has been concretized.

[0018] A concrete configuration is a configuration that does not include abstract elements. The design process is considered complete when a configuration is found in which all components are concreted.

[0019] The evaluation unit 13 calculates the evaluation value using the state of each component included in the specific configuration designed by the design unit 12 and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS (Quality of Service) of the target system due to the update from the state of each component. The QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified by the design unit 12. The calculation unit 14 calculates load information related to the load of the target system. The determination unit 15 determines whether to wait or execute the update of the target system using the evaluation value and the load information.

[0020] (Effects of the Renewal Support System) As described above, the renewal support system 1 includes the acquisition unit 11 that acquires second service requirements that have been changed from first service requirements, the design unit 12 that designs the concrete configuration of the target system after renewal by repeatedly executing a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing the abstract configuration of a target system for providing a service and identifying and applying one or more concretization rules corresponding to the abstract configuration, and the design unit 12 that determines the state of each component included in the concrete configuration designed by the design unit 12 and the state of each of the configurations. The system includes an evaluation unit 13 that calculates an evaluation value using a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that the renewal of the target system will have from the state of components, a calculation unit 14 that calculates load information related to the load on the target system, and a determination unit 15 that determines whether to wait or execute the renewal of the target system using the evaluation value and the load information, wherein the QoS evaluation function is configured to be derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified by the design unit 12. Therefore, the renewal support system 1 has the effect of being able to optimize QoS during system renewal.

[0021] (Flow of renewal support method) The flow of renewal support method S1 will be described with reference to Fig. 2. Fig. 2 is a flow diagram showing the flow of renewal support method S1. As shown in Fig. 2, renewal support method S1 includes an acquisition process S11, a design process S12, an evaluation process S13, a calculation process S14, and a determination process S15.

[0022] In an acquisition process S11, at least one processor acquires second service requirements that have been modified from the first service requirements. In a design process S12, the at least one processor repeatedly executes a concretization procedure for the second service requirements, which refers to a plurality of concretization rules that define a method for concretizing an abstract configuration of a target system providing a service, and identifies and applies one or more concretization rules corresponding to the abstract configuration to generate one or more abstract or concrete configurations, thereby designing a concrete configuration after the renewal of the target system. In an evaluation process S13, the at least one processor calculates an evaluation value using the status of each component included in the concrete configuration designed in the design process S12 and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS of the renewal of the target system from the status of each component. The QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a QoS evaluation function conversion rule associated with the one or more concretization rules identified in the design process S12. In a calculation process S14, the at least one processor calculates load information relating to the load of the target system. In a determination process S15, the at least one processor determines whether to wait for or execute the update of the target system using the evaluation value and the load information.

[0023] (Effects of the renewal support method) As described above, the renewal support method S1 includes an acquisition process S11 in which at least one processor acquires second service requirements that have been changed from first service requirements, a design process S12 in which the at least one processor repeatedly executes a concretization procedure for the second service requirements, in which the at least one processor references a plurality of concretization rules that define a method for concretizing an abstract configuration of a target system that provides a service, and identifies and applies one or more concretization rules corresponding to the abstract configuration to generate one or more abstract configurations or concrete configurations, thereby designing a concrete configuration of the target system after renewal, and a design process S12 in which the at least one processor determines the state of each component included in the concrete configuration designed in the design process S12 and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that the renewal of the target system will have from the state of each of the components, an evaluation process S13 for calculating the evaluation value using the evaluation function, a calculation process S14 in which the at least one processor calculates load information related to the load on the target system, and a determination process S15 in which the at least one processor determines whether to wait or execute the renewal of the target system using the evaluation value and the load information, wherein the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified in the evaluation process S13. Therefore, the renewal support method S1 has the effect of optimizing QoS during system renewal.

[0024] Second Exemplary Embodiment A second exemplary embodiment, which is an example of an embodiment of the present invention, will be described in detail with reference to the drawings. Components having the same functions as those described in the above exemplary embodiment will be denoted by the same reference numerals, and their description will be omitted as appropriate. The scope of application of each technique employed in this exemplary embodiment is not limited to this exemplary embodiment. That is, each technique employed in this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs. Furthermore, each technique shown in each drawing referenced to describe this exemplary embodiment can also be employed in other exemplary embodiments included in the present disclosure, to the extent that no particular technical hindrance occurs.

[0025] (Configuration of information processing device) The configuration of the information processing device 1A will be described with reference to Fig. 3. Fig. 3 is a block diagram showing the configuration of the information processing device 1A. The information processing device 1A is a device that updates an autonomously operated computer system. The information processing device 1A includes a control unit 10A, a storage unit 20A, a communication unit 30A, an input unit 40A, and an output unit 50A.

[0026] (Communication Unit) The communication unit 30A communicates with devices external to the information processing device 1A via a communication line. While the specific configuration of the communication line does not limit the present exemplary embodiment, examples of the communication line include a wireless local area network (LAN), a wired LAN, a wide area network (WAN), a public line network, a mobile data communication network, or a combination thereof. The communication unit 30A transmits data supplied from the control unit 10A to other devices, and supplies data received from other devices to the control unit 10A.

[0027] (Input Unit) The input unit 40A is configured to receive input to the information processing device 1A, and includes, for example, input devices such as a keyboard, a mouse, a touch panel, a camera, a microphone, etc. The input unit 40A may also be configured to receive data from the input devices via an interface such as a USB (Universal Serial Bus).

[0028] (Output Unit) The output unit 50A is a component for performing output from the information processing device 1A, and includes, for example, output devices such as a display, a printer, a touch panel, a speaker, etc. The output unit 50A may be configured to include, for example, an interface such as a USB, and to output data to the output device via the interface.

[0029] (Storage Unit) The storage unit 20A stores various types of information referenced by the control unit 10A. Examples of such information include a database 201 and system configuration information 202. The storage unit 20A is an example of a storage device according to the present disclosure.

[0030] (Database / System Configuration Information) The database 201 stores various data referenced for system renewal. The data is registered in the database 201 by, for example, the administrator of the target system to be renewed or the creator of the concretization rules, etc., described below. Examples of data registered in the database 201 include a plurality of concretization rules, conversion rules, and load information. The concretization rules prescribe a method for concretizing the abstract configuration of the system. The conversion rules prescribe a method for converting the system configuration into a QoS evaluation function, described below. Each of the multiple concretization rules is associated with a conversion rule that prescribes a method for converting the QoS evaluation function. The load information is information regarding the load of the target system. Each of the multiple concretization rules is associated with a type of load information. The system configuration information 202 is information indicating the configuration of the system to be operated.

[0031] 3, the control unit 10A includes an acquisition unit 11A, a design unit 12A, an evaluation unit 13A, a calculation unit 14A, a modification unit 15A, and a generation unit 16A. The acquisition unit 11A, the design unit 12A, the evaluation unit 13A, the calculation unit 14A, the modification unit 15A, and the generation unit 16A are examples of an acquisition means, a design means, an evaluation means, a calculation means, a determination means, and a generation means, respectively, according to the present disclosure.

[0032] (Acquisition Unit) The acquisition unit 11A acquires service requirements (an example of second service requirements) that have been changed from the first service requirements. For example, the acquisition unit 11A may acquire the service requirements by reading them from a storage location (which may be a storage device within the information processing device 1A or a storage device external to the information processing device 1A) designated by the user of the information processing device 1A. The acquisition unit 11A may also acquire the service requirements by receiving them from another device via the communication unit 30A. The acquisition unit 11A may also acquire the service requirements input to the input unit 40A.

[0033] (Service requirements / abstract configuration information) Service requirements are based on the requests of users of the target system, and include, for example, abstract configuration information that indicates the abstract configuration of the service after the update. Abstract configuration information expresses multiple abstract components and the relationships between the components. For example, the abstract configuration is expressed as a graph consisting of nodes and edges. A node represents the intention regarding any component. An edge represents the intention regarding the relationship between the components. Each node is assigned node type and attribute information. Each edge is assigned edge type and attribute information. When type and attribute information is assigned, the intention contained in the node or edge is expressed more specifically.

[0034] (Design Unit) The design unit 12A has the function of executing a concretization procedure to generate one or more abstract or concrete configurations by referring to a plurality of concretization rules and identifying and applying one or more concretization rules corresponding to an abstract configuration, and also designs the concrete configuration of the target system after renewal by repeatedly executing the concretization procedure on the service requirements acquired by the acquisition unit 11.

[0035] (Concretization Rules) As described above, concretization rules define a method for concretizing an abstract configuration of a system. As an example, the definition of a concretization rule is composed of information representing the configuration of a part to be concretized and information representing the configuration after the part is concretized. A specific partial configuration expressed by information representing the configuration of a part to be concretized, included in the abstract configuration, is rewritten into a configuration expressed by information representing the configuration after the part is concretized. The memory unit 20A stores a plurality of concretization rules corresponding to various abstract configurations.

[0036] (Example of Concretization) FIG. 4 is a diagram showing an example of a concrete configuration designed by the design unit 12A. In the example of FIG. 4, the service requirements acquired by the acquisition unit 11A include information indicating a service SV1. The design unit 12A designs an abstract configuration CF11 using a concretization rule corresponding to the service SV1 included in the abstract configuration CF1, among multiple concretization rules stored in the storage unit 20A. In addition to the service SV1, the abstract configuration CF11 includes an application AP1 and an application AP2 as components. An example of the concretization rule used here is the rule that "service SV1 is run by two applications."

[0037] The design unit 12A further designs an abstract configuration CF12 from the abstract configuration CF11 using a concretization rule corresponding to the partial configuration of the application AP1 included in the abstract configuration CF11, out of the multiple concretization rules stored in the storage unit 20A. The abstract configuration CF12 includes a server SV21 as a component in addition to the service SV1, the application AP1, and the application AP2. An example of the concretization rule used here is the rule that "the application is hosted on a server."

[0038] Furthermore, the design unit 12A further designs a concrete configuration CF13 from the abstract configuration CF12 using a concrete configuration rule corresponding to the partial configuration of the application AP2 included in the abstract configuration CF12, out of the multiple concrete configuration rules stored in the storage unit 20A. The concrete configuration CF13 includes a server SV22 as a component in addition to the service SV1, the application AP1, the application AP2, and the server SV21. An example of the concrete configuration rule used here is the rule that "the application is hosted on a server."

[0039] (Generation Unit - QoS Evaluation Function) The generation unit 16A generates a QoS evaluation function. The QoS evaluation function is a function that calculates an evaluation value for evaluating the influence on QoS from the state of each component included in the specific configuration designed by the design unit 12A. The QoS evaluation function F(V ｓｙｓ ) is a function on the state variables, and the state variables V ｓｙｓ is defined by the following equation (1), for example. Here, the state variable v[E:s] is defined by each component E of the system Sys and the state s of the component E. For example, the state variable v[E:s] is a binary variable that takes "1" when "the state of the component E is s" and "0" when "the state of the component E is not s". Examples of the state s include, but are not limited to, "normal operation," "stopped," and "standby."

[0040] More specifically, the QoS evaluation function F(V ｓｙｓ ) is expressed by the following equation (2), for example: where the system Sys is made up of n components E １ ~E ｎ and k １ ~k ｎ is the weighting coefficient corresponding to each component. F(V ｓｙｓ ) = k １ ×v[E １ : Normal]+k ２ ×v[E ２ : Normal] +...+k ｎ ×v[E ｎ : Normal] ...(2)

[0041] In one aspect, each of the multiple instantiation rules is associated with a conversion rule that specifies a method for converting the QoS evaluation function, and the generation unit 16A generates the QoS evaluation function using the conversion rule associated with one or more instantiation rules identified by the design unit 12A. In other words, the conversion rule indicates how the QoS evaluation function should be converted when the corresponding instantiation rule is applied to the system. The storage unit 20A stores the conversion rule in association with each instantiation rule.

[0042] In the example of FIG. 4, the QoS evaluation function corresponding to the abstract configuration CF1 is, for example, ｓｙｓ ) = v [service SV1: normal] ... (3) Then, the concrete rule "run service SV1 with two applications" for designing abstract configuration CF11 from abstract configuration CF1 is associated with a conversion rule "replace v [service SV1: normal] with 12 x v [application AP1: normal] + 13 x v [application AP2: normal]", and by applying this conversion rule to formula (3), the QoS evaluation function corresponding to abstract configuration CF11 is expressed as follows: F(V ｓｙｓ )=12×v[application AP1: normal]+13×v[application AP2: normal] (4) Here, "12" and "13" in the conversion rule are weighting coefficients, which are set in advance by the creator of the specific rule or the like and stored in the storage unit 20A.

[0043] Furthermore, the concretization rule "host the application on the server" for designing the abstract configuration CF12 from the abstract configuration CF11 is associated with a conversion rule "replace v [application: normal] with v [application: normal] × v [server: normal]", and by applying this conversion rule to equation (4), the QoS evaluation function corresponding to the abstract configuration CF12 is given by F(V ｓｙｓ )=12×v[application AP1: normal]×v[server SV21: normal]+13×v[application AP2: normal] (5)

[0044] The concretization rule "host the application on the server" for designing the concrete configuration CF13 from the abstract configuration CF12 is associated with a conversion rule "replace v [application: normal] with v [application: normal] × v [server: normal]." By applying this conversion rule to equation (5), the QoS evaluation function corresponding to the concrete configuration CF13 is given by F(V ｓｙｓ )=12×v[application AP1: normal]×v[server SV21: normal]+13×v[application AP2: normal]×v[server SV22: normal] (6)

[0045] The QoS evaluation functions shown in equations (4) to (6) can also be described as functions that multiply each component included in a specific configuration by a function that includes the state of each component as a variable and a weighting coefficient, and then multiply the function corresponding to the component having a serial relationship in the specific configuration by the function, and add the function corresponding to the component having a parallel relationship.

[0046] (Evaluation Unit) The evaluation unit 13A calculates an evaluation value indicating the degree of impact on QoS of the target system update based on the state of each component included in the specific configuration designed by the design unit 12A. More specifically, as an example, the evaluation unit 13A acquires the state of each component included in the configuration designed by the design unit 12A and calculates the degree of impact on QoS using the state of each component included in the specific configuration designed by the design unit 12A and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS from the state of each component. The QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a QoS evaluation function conversion rule associated with one or more instantiation rules identified by the design unit 12A.

[0047] (Calculation Unit / Load Information) The calculation unit 14A calculates load information related to the load of the target system. The load information includes, for example, information related to requests for services provided by the target system. The load information may also include a TAT (Turn Around Time), which indicates the time from when a processing request is sent to a system or the like until the processing is completed. The load information may also include information indicating the number of end users using the service.

[0048] The updating unit 15A updates the system step by step from the pre-update configuration to the post-update configuration based on the service requirements specified by the user. For example, the method described in Patent Document 3 can be used as the updating method.

[0049] Furthermore, the updating unit 15A manages the state of each component (constituent part) in the system during the updating, and determines whether to wait or execute the updating depending on the state of each component. More specifically, as an example, the updating unit 15A determines to wait for the system updating when the impact on QoS indicated by the evaluation value calculated by the evaluation unit 13A is greater than the allowable range determined by the load information calculated by the calculation unit 14A.

[0050] 5 is a flow diagram showing an example of the flow of the renewal support method according to the present disclosure. In step S101, the acquisition unit 11A acquires service requirements (second service requirements) that have been changed from the first service requirements. In step S102, the design unit 12A designs a specific configuration of the target system after renewal based on the concretization rules corresponding to the service requirements acquired in step S101.

[0051] In step S103, the generation unit 16A generates a QoS evaluation function using a conversion rule associated with one or more instantiation rules identified by the design unit 12A. More specifically, as an example, the generation unit 16A generates a QoS evaluation function corresponding to the specific configuration after updating designed by the design unit 12A. The QoS evaluation function is generated using the specific configuration generated by the design unit 12A in step S102.

[0052] A specific example of a QoS evaluation function is shown on the right side of Fig. 6. In the example on the right side of Fig. 6, the specific configuration CF13 after renewal includes a service SV1, an application AP1, a server SV21, an application AP2, and a server SV22. The generation unit 16A generates the following as the second QoS evaluation function corresponding to the specific configuration CF13 after renewal: 12 x v [application AP1: normal] x v [server SV21: normal] + 13 x v [application AP12 normal] x v [server SV22: normal]

[0053] In step S104, the evaluation unit 13A calculates an evaluation value indicating the degree of impact on QoS of the target system due to the update, based on the state of each component included in the specific configuration designed by the design unit 12 A. More specifically, the evaluation unit 13A calculates the evaluation value using a QoS evaluation function, as an example.

[0054] In step S105, the calculation unit 14A calculates load information. In addition, in step S106, the update unit 15A compares the evaluation value with a reference value and determines whether to wait or execute the update of the target system. As an example, the update unit 15A determines to wait for the update when the evaluation value is below the reference value, and determines to execute the update when the evaluation value is equal to or greater than the reference value. Note that, as an example, the update unit 15A may determine to wait for the update when the evaluation value is equal to or less than the reference value, and determine to execute the update when the evaluation value is greater than the reference value.

[0055] As an example, the updating unit 15A may determine the reference value using load information. For example, the updating unit 15A may use the reference value indicated by the load information calculated by the calculation unit 14A (i.e., the measured value of the current load) or the reference value calculated from the load information as the reference value to be compared with the evaluation value. As the reference value calculated from the load information, for example, a value obtained by subtracting a predetermined margin from the value indicated by the load information may be used as the reference value. As another example, the reference value may be a value obtained by adding a predetermined tolerance value to the value indicated by the load information. The margin and tolerance value may be values ​​that are preset by, for example, a system administrator or a creator of the instantiation rules, etc.

[0056] If the updating unit 15A is to wait for the system update (YES in step S106), the updating unit 15A proceeds to the processing of step S107. On the other hand, if the updating unit 15A is not to wait for the system update (NO in step S106), the updating unit 15A proceeds to the processing of step S108. In step S107, the updating unit 15A waits for the system update. On the other hand, in step S108, the updating unit 15A continues the system update.

[0057] In step S109, the updating unit 15A determines whether the system updating is complete. If the updating is complete (YES in step S109), the updating unit 15A ends the processing in Fig. 5. On the other hand, if the updating is not complete (NO in step S109), the updating unit 15A returns to the processing in step S104.

[0058] (Variations of Operation) As a variation of the above-described process, a configuration will be described in which the type of load information used to determine the reference value is determined based on one or more instantiation rules identified by the design unit 12A. In step S105, as an example, the calculation unit 14A may calculate the load information by referring to the type of load information associated with the one or more instantiation rules identified by the design unit 12A.

[0059] For example, the storage unit 20A may store a type of load information along with a conversion rule in association with each concatenation rule. Each concatenation rule may be associated with a type of load information related to the component added by the concatenation rule. For example, a concatenation rule such as "run service SV1 with two applications" may be associated with a type of load information related to the operation of the applications, and a concatenation rule such as "host the applications on a server" may be associated with a type of load information related to the operation of the server. The type of load information may be a value preset by, for example, the creator of the concatenation rule. This allows the evaluation value to be compared with an appropriate reference value in step S106.

[0060] As a variation of the above-described process, a configuration using both a first QoS evaluation function corresponding to the configuration before renewal and a second QoS evaluation function corresponding to the configuration after renewal will be described. In step S103, the generation unit 16A may generate a first QoS evaluation function corresponding to the configuration before renewal of the target system, and may also generate a second QoS evaluation function corresponding to the specific configuration after renewal designed by the design unit 12A. The first QoS evaluation function is generated using the system configuration information 202 stored in the storage unit 20A. The second QoS evaluation function is generated using the specific configuration generated by the design unit 12A in step S102.

[0061] The example on the left side of Fig. 6 is a specific example of the first QoS evaluation function, and the example on the right side of Fig. 6 is a specific example of the second QoS evaluation function. In the example on the left side of Fig. 6, the configuration CF5 before the renewal includes service SV5, application AP5, and server SV51 as components. In the example on the right side of Fig. 6, the specific configuration CF13 after the renewal includes service SV1, application AP1, server SV21, application AP2, and server SV22. The generation unit 16A may generate the following as the first QoS evaluation function corresponding to the configuration CF5 before the renewal: 18 x v [application AP5: normal] x v [server SV51: normal]. In addition, the generation unit 16A may generate the following as a second QoS evaluation function corresponding to the specific configuration CF13 after the update: 12×v[application AP1: normal]×v[server SV21: normal]+13×v[application AP12 normal]×v[server SV22: normal].

[0062] In step S104, the evaluation unit 13A may, for example, calculate a first evaluation value using the first QoS evaluation function and calculate a second evaluation value using the second QoS evaluation function.

[0063] In step S105, the updating unit 15A may, for example, use the first evaluation value and the second evaluation value to determine whether to wait or execute the updating. For example, the updating unit 15A may use the larger of the first evaluation value and the second evaluation value as the overall evaluation value, and may determine to wait for the updating when the overall evaluation value is lower than a reference value. Here, for example, the reference value may be a value based on the load information calculated by the calculation unit 14A. For example, the reference value may be a value set in advance by a system administrator, a creator of the instantiation rules, etc.

[0064] The updating unit 15A may perform the process of step S106 in each of a plurality of phases included in the updating of the target system. A phase refers to each process of updating the target system. FIG. 7 is a diagram showing an example of an updating procedure when updating the pre-update configuration CF5 of the target system shown in FIG. 6 to a specific configuration CF13. In the example of FIG. 7, the updating is performed in the order of phase F1, phase F2, phase F3, .... In other words, the updating of the target system includes a plurality of phases, and the updating unit 15A determines whether to wait for or execute the updating in each of the plurality of phases of the target system.

[0065] (Effects of Information Processing Device) When configuring a mechanism for autonomously operating a system, it is necessary to change the system configuration and settings depending on environmental factors, etc. However, system upgrades often involve passing through a state in which the QoS required by the system operator is not being achieved, and if the system upgrade is performed under the expected normal service usage conditions, a fatal malfunction may occur in the entire service. To avoid this problem and upgrade the system without setting a clear service downtime, the only option is to estimate the extent to which each operation (upgrade task) performed during the system upgrade will affect the QoS of the service and to upgrade under conditions in which the impact can be contained. However, it is difficult to estimate the impact of each upgrade task on the QoS from system configuration information alone.

[0066] In contrast, in the information processing device 1A according to the present disclosure, the design unit 12A designs the specific configuration of the system after renewal based on the service requirements input by the user, and by using information generated by the design unit 12A (such as conversion rules linked to the instantiation rules identified by the design unit 12A), it is possible to estimate the impact of each renewal task on QoS, which is difficult to estimate from the system configuration information alone. This makes it possible to proceed with the renewal of the system while preventing the QoS from becoming too low.

[0067] Furthermore, in the information processing device 1A, the updating unit 15A is configured to determine to wait for the updating if the impact on the QoS indicated by the evaluation value is greater than the allowable range determined by the load information. Therefore, according to the information processing device 1A, it is possible to obtain the effect that the system updating can be carried out so that the impact on the QoS falls within the allowable range.

[0068] Furthermore, the information processing device 1A is configured such that each of the multiple instantiation rules is associated with a conversion rule that defines a method for converting the QoS evaluation function, and the device is provided with a generation unit 16A that generates a QoS evaluation function using the conversion rule associated with the one or more instantiation rules identified by the design unit 12A. Calculating an evaluation value using a QoS evaluation function generated using the conversion rule associated with the instantiation rule identified by the design unit 12A provides the effect of enabling evaluation suited to the specific configuration after updating.

[0069] Furthermore, in the information processing device 1A, a type of load information is associated with each of the multiple concatenation rules, and the calculation unit 14A calculates the load information by referring to the type of load information associated with the one or more concatenation rules identified by the design unit 12A. The updating unit 15A makes a determination using the type of load information associated with the one or more concatenation rules identified by the design unit 12A, thereby achieving the effect of being able to make a determination appropriate for the concrete configuration after the renewal.

[0070] Furthermore, in the information processing device 1A, the storage unit 20A stores configuration information indicating the configuration of the target system, the generation unit 16A generates a first QoS evaluation function corresponding to the configuration of the target system before renewal and generates a second QoS evaluation function corresponding to the specific configuration after renewal designed by the design unit 12A, the evaluation unit 13A calculates a first evaluation value using the first QoS evaluation function and calculates a second evaluation value using the second QoS evaluation function, and the renewal unit 15A determines whether to wait for or execute the renewal using the first evaluation value and the second evaluation value. By making the determination taking into account both the configuration before renewal and the configuration after renewal, it is possible to obtain the effect of preventing a deterioration in QoS due to renewal.

[0071] In addition, the information processing device 1A employs a configuration in which the load information includes information regarding requests for services provided by the target system, so that the information processing device 1A can achieve the effect of proceeding with renewal while preventing a deterioration in QoS that is affected by service requests.

[0072] Furthermore, in the information processing device 1A, the QoS evaluation function is a function obtained by multiplying a function including the state of each component included in the specific configuration by a weighting coefficient, and multiplying this function by functions corresponding to components having a series relationship in the specific configuration, and adding functions corresponding to components having a parallel relationship. Therefore, according to the information processing device 1A, it is possible to evaluate the impact on QoS using a QoS evaluation function suitable for the specific configuration after the update.

[0073] Furthermore, in the information processing device 1A, the renewal of the target system includes multiple phases, and the renewal unit 15A is configured to determine whether to wait or execute the renewal in each of the multiple phases of the target system. Therefore, the information processing device 1A has the effect of being able to proceed with the renewal while optimizing the QoS in multiple phases.

[0074] [Example of implementation using software] Some or all of the functions of the renewal support system 1 and the information processing device 1A (hereinafter also referred to as "each of the above-mentioned devices") may be implemented using hardware such as an integrated circuit (IC chip), or may be implemented using software.

[0075] In the latter case, each of the above devices is realized by, for example, a computer that executes instructions of a program, which is software that realizes each function. An example of such a computer (hereinafter referred to as computer C) is shown in Figure 8. Figure 8 is a block diagram showing the hardware configuration of computer C that functions as each of the above devices.

[0076] The computer C includes at least one processor C1 and at least one memory C2. The memory C2 stores a program P for causing the computer C to function as each of the above-mentioned devices. In the computer C, the processor C1 reads and executes the program P from the memory C2, thereby realizing the functions of each of the above-mentioned devices.

[0077] The processor C1 may be, for example, a central processing unit (CPU), a graphics processing unit (GPU), a digital signal processor (DSP), a micro processing unit (MPU), a floating point number processing unit (FPU), a physics processing unit (PPU), a tensor processing unit (TPU), a quantum processor, a microcontroller, or a combination thereof. The memory C2 may be, for example, a flash memory, a hard disk drive (HDD), a solid state drive (SSD), or a combination thereof.

[0078] The computer C may further include a RAM (Random Access Memory) for expanding the program P during execution and for temporarily storing various data. The computer C may also include a communication interface for transmitting and receiving data to and from other devices. The computer C may also include an input / output interface for connecting input / output devices such as a keyboard, a mouse, a display, and a printer.

[0079] The program P can also be recorded on a non-transitory, tangible recording medium M that can be read by the computer C. Such a recording medium M can be, for example, a tape, a disk, a card, a semiconductor memory, or a programmable logic circuit. The computer C can acquire the program P via such a recording medium M. The program P can also be transmitted via a transmission medium. Such a transmission medium can be, for example, a communication network or broadcast waves. The computer C can also acquire the program P via such a transmission medium.

[0080] Furthermore, the functions of each of the devices may be realized by a single processor provided in a single computer, by multiple processors provided in a single computer working in cooperation, or by multiple processors provided in each of multiple computers working in cooperation. Furthermore, the programs for causing each of the devices to realize the functions may be stored in a single memory provided in a single computer, or may be distributed and stored in multiple memories provided in a single computer, or may be distributed and stored in multiple memories provided in each of multiple computers.

[0081] [Appendix A] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0082] (Appendix A1) The system comprises: an acquisition means for acquiring second service requirements modified from first service requirements; a design means for repeatedly executing a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby designing a concrete configuration after the renewal of the target system; an evaluation means for calculating an evaluation value using a state of each component included in the concrete configuration designed by the design means and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that renewal of the target system will have from the state of each component; a calculation means for calculating load information regarding the load of the target system; and a determination means for determining whether to wait or execute renewal of the target system using the evaluation value and the load information, wherein the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for a QoS evaluation function associated with the one or more concretization rules identified by the design means. Renewal support system.

[0083] (Supplementary Note A2) The renewal support system according to Supplementary Note A1, wherein the determining unit determines to wait for the renewal when the influence on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

[0084] (Appendix A3) The renewal support system according to Appendix A1 or A2, wherein each of the plurality of concretization rules is associated with a conversion rule that defines a method of converting the QoS evaluation function, and further comprising: a generation means that generates the QoS evaluation function using the conversion rule associated with the one or more concretization rules identified by the design means.

[0085] (Appendix A4) The renewal support system according to Appendix A3, wherein a type of the load information is associated with each of the plurality of concretization rules, and the calculation means calculates the load information by referring to the type of load information associated with the one or more concretization rules identified by the design means.

[0086] (Appendix A5) The renewal support system according to Appendix A3 or A4, wherein the generating means generates a first QoS evaluation function corresponding to the configuration of the target system before renewal, and generates a second QoS evaluation function corresponding to the specific configuration after renewal designed by the designing means; the evaluating means calculates a first evaluation value using the first QoS evaluation function, and calculates a second evaluation value using the second QoS evaluation function; and the determining means determines whether to wait for or execute the renewal, using the first evaluation value and the second evaluation value.

[0087] (Supplementary Note A6) The renewal support system according to any one of Supplementary Notes A1 to A5, wherein the load information includes information relating to a request for a service provided by the target system.

[0088] (Appendix A7) The renewal support system according to any one of Appendices A3 to A5, wherein the QoS evaluation function is a function obtained by multiplying a function including a state of each component included in the specific configuration as a variable by a weighting coefficient, and multiplying the function by a function corresponding to components having a series relationship in the specific configuration, and adding the function corresponding to components having a parallel relationship.

[0089] (Appendix A8) The update support system according to any one of Appendices A1 to A7, wherein the update of the target system includes a plurality of phases, and the determination means determines whether to wait for or execute the update in each of the plurality of phases of the target system.

[0090] [Appendix B] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0091] (Supplementary Note B1) The method includes: an acquisition process in which at least one processor acquires second service requirements that have been changed from first service requirements; a design process in which the at least one processor repeatedly executes a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby designing a concrete configuration after the renewal of the target system; an evaluation process in which the at least one processor calculates an evaluation value using a state of each component included in the concrete configuration designed by the design process and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that the renewal of the target system will have from the state of each component; a calculation process in which the at least one processor calculates load information regarding the load of the target system; and a determination process in which the at least one processor uses the evaluation value and the load information to determine whether to wait for or execute the renewal of the target system, a QoS evaluation function derived from a QoS evaluation function associated with the second service requirement and a conversion rule for a QoS evaluation function associated with the one or more instantiation rules identified in the design process.

[0092] (Supplementary Note B2) The renewal support method according to Supplementary Note B1, wherein in the determination process, the at least one processor determines to wait for the renewal if the impact on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

[0093] (Appendix B3) The renewal support method according to Appendix B1 or B2, wherein each of the plurality of concretization rules is associated with a conversion rule that defines a method for converting the QoS evaluation function, and the renewal support method further includes a generation process in which the at least one processor generates the QoS evaluation function using the conversion rule associated with the one or more concretization rules identified in the design process.

[0094] (Supplementary Note B4) The renewal support method according to Supplementary Note B3, wherein each of the plurality of concretization rules is associated with a type of the load information, and in the calculation process, the at least one processor calculates the load information by referring to the type of load information associated with the one or more concretization rules identified in the design process.

[0095] (Supplementary Note B5) The renewal support method described in Supplementary Note B3 or B4, wherein in the generation process, the at least one processor generates a first QoS evaluation function corresponding to the configuration of the target system before renewal, and generates a second QoS evaluation function corresponding to the specific configuration after renewal designed in the design process; in the evaluation process, the at least one processor calculates a first evaluation value using the first QoS evaluation function, and calculates a second evaluation value using the second QoS evaluation function; and in the determination process, the at least one processor determines whether to wait for or execute the renewal, using the first evaluation value and the second evaluation value.

[0096] (Supplementary Note B6) The renewal support method according to any one of Supplementary Notes B3 to B5, wherein the load information includes information relating to a request for a service provided by the target system.

[0097] (Appendix B7) The renewal support method according to any one of Appendices B3 to B5, wherein the QoS evaluation function is a function obtained by multiplying a function including the state of each component included in the specific configuration as a variable by a weighting coefficient, and multiplying the function by a function corresponding to components having a series relationship in the specific configuration, and adding the function corresponding to components having a parallel relationship.

[0098] (Appendix B8) The update support method described in any one of Appendices B1 to B7, wherein the update of the target system includes multiple phases, and in the determination process, the at least one processor determines whether to wait for or execute the update in each of the multiple phases of the target system.

[0099] [Appendix C] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0100] (Appendix C1) A program for causing a computer to function as an update support system, the program causing the computer to function as: an acquisition means for acquiring second service requirements that have been changed from first service requirements; a design means for repeatedly executing, for the second service requirements, a concretization procedure that generates one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby designing a concrete configuration after the update of the target system; an evaluation means for calculating an evaluation value using a state of each component part included in the concrete configuration designed by the design means and a QoS evaluation function for calculating an evaluation value that indicates the degree of impact on QoS that updating the target system will have from the state of each component part; a calculation means for calculating load information related to the load of the target system; and a determination means for determining whether to wait for or execute updating of the target system using the evaluation value and the load information, a renewal support program, wherein the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified by the design means.

[0101] (Supplementary Note C2) The renewal support program according to Supplementary Note C1, wherein the determining means determines to wait for the renewal when the influence on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

[0102] (Appendix C3) The renewal support program according to appendix C1 or C2, wherein each of the plurality of instantiation rules is associated with a conversion rule that specifies a method of converting the QoS evaluation function, and the computer is further made to function as a generation means that generates the QoS evaluation function using the conversion rule associated with the one or more instantiation rules identified by the design means.

[0103] (Appendix C4) The renewal support program according to Appendix C3, wherein each of the plurality of concretization rules is associated with a type of the load information, and the calculation means calculates the load information by referring to the type of load information associated with the one or more concretization rules identified by the design means.

[0104] (Appendix C5) The renewal support program according to Appendix C3 or C4, wherein the generation means generates a first QoS evaluation function corresponding to the configuration of the target system before renewal, and generates a second QoS evaluation function corresponding to the specific configuration after renewal designed by the design means; the evaluation means calculates a first evaluation value using the first QoS evaluation function, and calculates a second evaluation value using the second QoS evaluation function; and the determination means determines whether to wait for or execute the renewal using the first evaluation value and the second evaluation value.

[0105] (Supplementary Note C6) The renewal support program according to any one of Supplementary Notes C1 to C5, wherein the load information includes information relating to a request for a service provided by the target system.

[0106] (Appendix C7) The renewal support program according to any one of Appendices C3 to C5, wherein the QoS evaluation function is a function obtained by multiplying a function including a state of each component included in the specific configuration as a variable by a weighting coefficient, and multiplying the function by a function corresponding to components having a series relationship in the specific configuration, and adding the function corresponding to components having a parallel relationship.

[0107] (Appendix C8) The update support program according to any one of appendices C1 to C7, wherein the update of the target system includes a plurality of phases, and the determination means determines whether to wait for or execute the update in each of the plurality of phases of the target system.

[0108] [Appendix D] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0109] (Supplementary Note D1) A system including at least one processor, the at least one processor executing: an acquisition process for acquiring second service requirements that have been changed from first service requirements; a design process for designing a concrete configuration of the target system after updating by repeatedly executing, for the second service requirements, a concretization procedure that generates one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration; an evaluation process for calculating an evaluation value using a state of each component included in the concrete configuration designed in the design process and a QoS evaluation function for calculating an evaluation value that indicates the degree of impact on QoS that updating the target system will have from the state of each component; a calculation process for calculating load information related to the load of the target system; and a determination process for determining whether to wait for or execute updating the target system using the evaluation value and the load information, the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for a QoS evaluation function associated with the one or more instantiation rules identified in the design process.

[0110] The renewal support system may further include a memory, and the memory may store a program for causing the at least one processor to execute each of the processes.

[0111] (Supplementary Note D2) The renewal support system according to Supplementary Note D1, wherein in the determination process, the at least one processor determines to wait for the renewal if the impact on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

[0112] (Appendix D3) The renewal support system according to appendix D1 or D2, wherein each of the plurality of concretization rules is associated with a conversion rule that specifies a method of converting the QoS evaluation function, and the at least one processor further executes a generation process that generates the QoS evaluation function using the conversion rule associated with the one or more concretization rules identified in the design process.

[0113] (Appendix D4) The renewal support system according to Appendix D3, wherein each of the plurality of concretization rules is associated with a type of the load information, and in the calculation process, the at least one processor calculates the load information by referring to the type of load information associated with the one or more concretization rules identified in the design process.

[0114] (Appendix D5) The renewal support system described in Appendix D3 or D4, wherein in the generation process, the at least one processor generates a first QoS evaluation function corresponding to the configuration of the target system before renewal, and generates a second QoS evaluation function corresponding to the specific configuration after renewal designed in the design process; in the evaluation process, the at least one processor calculates a first evaluation value using the first QoS evaluation function, and calculates a second evaluation value using the second QoS evaluation function; and in the determination process, the at least one processor determines whether to wait for or execute the renewal, using the first evaluation value and the second evaluation value.

[0115] (Supplementary Note D6) The renewal support system according to any one of Supplementary Notes D1 to D5, wherein the load information includes information relating to a request for a service provided by the target system.

[0116] (Appendix D7) The renewal support system according to any one of Appendices D3 to D5, wherein the QoS evaluation function is a function obtained by multiplying a function including a state of each component included in the specific configuration as a variable by a weighting coefficient, and multiplying the function by a function corresponding to components having a series relationship in the specific configuration, and adding the function corresponding to components having a parallel relationship.

[0117] (Appendix D8) The update support system described in any one of Appendices D1 to D7, wherein the update of the target system includes multiple phases, and in the determination process, the at least one processor determines whether to wait for or execute the update in each of the multiple phases of the target system.

[0118] [Appendix E] This disclosure includes the techniques described in the following appendices. However, the present invention is not limited to the techniques described in the following appendices, and various modifications are possible within the scope of the claims.

[0119] (Appendix E1) A program for causing a computer to function as an update support system, the program causing the computer to execute: an acquisition process for acquiring second service requirements that have been changed from first service requirements; a design process for designing a concrete configuration of the target system after update by repeatedly executing, for the second service requirements, a concretization procedure that generates one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration; an evaluation process for calculating an evaluation value using a state of each component included in the concrete configuration designed in the design process and a QoS evaluation function for calculating an evaluation value that indicates the degree of impact on QoS that updating the target system will have from the state of each component; a calculation process for calculating load information related to the load of the target system; and a determination process for determining whether to wait for or execute updating the target system using the evaluation value and the load information, A non-transient recording medium on which a renewal support program is recorded, in which the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified by the design means.

[0120] REFERENCE SIGNS LIST 1 Renewal support system 1A Information processing device 11, 11A Acquisition unit 12, 12A Design unit 13, 13A Evaluation unit 14, 14A Calculation unit 15 Determination unit 15A Renewal unit 16A Generation unit

Claims

1. An acquisition means for acquiring second service requirements that have been changed from first service requirements; design means for designing a concrete configuration of the target system after updating by repeatedly executing a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration; evaluation means for calculating an evaluation value using the state of each component part included in the concrete configuration designed by the design means and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS (Quality of Service) that updating the target system will have from the state of each component part; calculation means for calculating load information regarding the load on the target system; and determination means for determining whether to wait for or execute updating the target system using the evaluation value and the load information, the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for a QoS evaluation function associated with the one or more instantiation rules identified by the design means.

2. The renewal support system according to claim 1, wherein the determining means determines to postpone the renewal when the impact on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

3. The renewal support system according to claim 1 or 2, wherein each of the plurality of instantiation rules is associated with a conversion rule that specifies a method for converting the QoS evaluation function, and further comprising a generation means that generates the QoS evaluation function using the conversion rule associated with the one or more instantiation rules identified by the design means.

4. The renewal support system according to claim 3, wherein each of the plurality of concretization rules is associated with a type of load information, and the calculation means calculates the load information by referring to the type of load information associated with the one or more concretization rules identified by the design means.

5. The renewal support system described in claim 3, wherein the generation means generates a first QoS evaluation function corresponding to the configuration of the target system before renewal, and generates a second QoS evaluation function corresponding to the specific configuration after renewal designed by the design means; the evaluation means calculates a first evaluation value using the first QoS evaluation function, and calculates a second evaluation value using the second QoS evaluation function; and the determination means determines whether to wait for or execute the renewal using the first evaluation value and the second evaluation value.

6. The upgrade support system according to claim 1 or 2, wherein the load information includes information regarding requests for services provided by the target system.

7. The renewal support system according to claim 3, wherein the QoS evaluation function is a function obtained by multiplying a function including the state of each component included in the specific configuration as a variable by a weighting coefficient, and multiplying the function by a function corresponding to components having a serial relationship in the specific configuration, and adding the function corresponding to components having a parallel relationship.

8. The upgrade support system according to claim 1 or 2, wherein the upgrade of the target system includes a plurality of phases, and the determination means determines whether to wait for or execute the upgrade in each of the plurality of phases of the target system.

9. A system comprising: an acquisition process in which at least one processor acquires second service requirements that have been modified from first service requirements; a design process in which the at least one processor repeatedly executes a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing an abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby designing a concrete configuration after the renewal of the target system; an evaluation process in which the at least one processor calculates an evaluation value using the state of each component included in the concrete configuration designed by the design process and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that the renewal of the target system will have from the state of each component; a calculation process in which the at least one processor calculates load information regarding the load of the target system; and a determination process in which the at least one processor uses the evaluation value and the load information to determine whether to wait for or execute the renewal of the target system, the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for a QoS evaluation function associated with the one or more instantiation rules identified in the design process.

10. A program for causing a computer to function as an update support system, the program causing the computer to function as: acquisition means for acquiring second service requirements that have been changed from first service requirements; design means for designing a concrete configuration of the target system after update by repeatedly executing a concretization procedure for the second service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that prescribe a method for concretizing the abstract configuration of a target system that provides a service, and identifying and applying one or more concretization rules corresponding to the abstract configuration; evaluation means for calculating an evaluation value using the state of each component part included in the concrete configuration designed by the design means and a QoS evaluation function for calculating an evaluation value indicating the degree of impact on QoS that updating the target system will have from the state of each component part; calculation means for calculating load information related to the load on the target system; and determination means for determining whether to wait for or execute updating the target system using the evaluation value and the load information, a renewal support program, wherein the QoS evaluation function is derived from a QoS evaluation function associated with the second service requirement and a conversion rule for the QoS evaluation function associated with the one or more instantiation rules identified by the design means.

Images