Update support system, update support method, and update support program

Abstract

The present invention realizes an update support system capable of optimizing a QoS during an update of a system. An update support system according to the present invention comprises: a design unit that designs an updated concrete configuration of a target system providing a service by repeatedly executing, with respect to a service requirement, a concretization procedure in which a plurality of concretization rules defining a method for concretizing an abstract configuration of the target system are referred to, and one or more of the concretization rules corresponding to the abstract configuration are specified and applied to generate one or more abstract configurations or concrete configurations, and generates an operation model of the target system corresponding to the updated concrete configuration; a generation unit that generates a QoS evaluation function for evaluating, when updating the abstract configuration of the target system to the concrete configuration designed by the design unit, a quality of service (QoS) of the configuration of the target system in the middle of the update; and a planning unit that plans, by using the operation model and the QoS evaluation function, an update procedure satisfying a QoS-based criterion.

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 the autonomous operation of computer systems are known. One example of a technology for supporting the autonomous operation of a computer system is the technology described in Patent Document 1. The system operation planning device described in Patent Document 1 determines an appropriate system configuration for a target system based on values ​​of variable factors within a predetermined range of variable factors, and extracts a procedure for changing the current system configuration to the appropriate system configuration.

[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] Furthermore, Patent Document 4 discloses a high-speed change planning system that can reduce the amount of calculation required to create a change plan for a large-scale system, the high-speed change planning system including a state machine group dividing unit that divides a state machine group consisting of one or more state machines into state machine groups, and a state machine group integrating unit that integrates the transition orders derived for each state machine group included in the divided state machine groups.

[0006] International Publication No. 2023 / 233451 International Publication No. 2019 / 216082 International Publication No. 2017 / 017937 Japanese Patent Application Laid-Open No. 2015-215886

[0007] In the technology described in Patent Document 1, when the system configuration after updating is predetermined, the QoS (Quality of Service) may be reduced during the system update 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 to 4.

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

[0009] An exemplary aspect of the present disclosure provides a renewal support system that includes: an acquisition means for acquiring service requirements indicating requirements for a changed service; a design means for repeatedly executing a concretization procedure on the 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 the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby designing a renewed concrete configuration of the target system and generating an operation model of the target system that corresponds to the renewed concrete configuration; a generation means for generating a QoS evaluation function for evaluating the QoS of the configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to the concrete configuration designed by the design means; and a planning means for planning a renewal procedure that satisfies QoS-based criteria, using the operation model and the QoS evaluation function.

[0010] An exemplary aspect of the present disclosure provides a renewal support method including: an acquisition process, performed by at least one processor, for acquiring service requirements indicating requirements for a changed service; a design process, performed by the at least one processor, for designing a renewed concrete configuration of the target system by repeatedly executing a concretization procedure on the 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 the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby generating one or more abstract or concrete configurations; a generation process, performed by the at least one processor, for generating a QoS evaluation function for evaluating the QoS of a configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to a concrete configuration designed by the design process; and a planning process, performed by the at least one processor, for planning a renewal procedure that satisfies a QoS-based criterion, using the operation model and the QoS evaluation function.

[0011] An exemplary aspect of the present disclosure is an update support program for causing a computer to function as an update support system, and causes the computer to function as: an acquisition means for acquiring service requirements indicating requirements for a changed service; a design means for designing an updated concrete configuration of the target system by repeatedly executing a concretization procedure on the service requirements, the concretization procedure generating one or more abstract or concrete configurations by referring to a plurality of concretization rules that specify a method for concretizing the abstract configuration of a target system that provides the service, and identifying and applying one or more concretization rules that correspond to the abstract configuration, thereby generating one or more abstract or concrete configurations; a generation means for generating a QoS evaluation function for evaluating the QoS of the configuration of the target system in the middle of updating when the abstract configuration of the target system is updated to the concrete configuration designed by the design means; and a planning means for planning an update procedure that satisfies QoS-based criteria, using the operation model and the QoS evaluation function.

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

[0013] 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 diagram showing an example of a configuration before renewal and an example of a renewed configuration of a target system according to the present disclosure. FIG. 6 is a diagram showing an example of a state before renewal and an example of a renewed state of each component included in a target system according to the present disclosure. FIG. 7 is a flow diagram showing an example of the flow of a renewal procedure planning method according to the present disclosure. FIG. 8 is a diagram showing a specific example of a state and an evaluation value of a target system according to the present disclosure. FIG. 9 is a diagram for explaining a specific example of a renewal procedure plan according to the present disclosure. FIG. 10 is a flow diagram showing an example of the flow of a renewal support method according to the present disclosure. FIG. 11 is a block diagram showing the configuration of a renewal support system and a computer functioning as an information processing device according to the present disclosure.

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

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

[0016] (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, a generation unit 13, and a planning unit 14.

[0017] The acquisition unit 11 acquires service requirements indicating the requirements of a changed service. The service is a service provided by a target system supported by the renewal support system 1. The target system provides the service so as to satisfy specified requirements. In response to a change in the service requirements, the renewal support system 1 determines a renewal procedure for renewing the target system so as to satisfy the changed service requirements. In detail, the design unit 12 refers to a plurality of reification rules that define a method for concretizing an abstract configuration of the target system that provides the service, and repeatedly executes a reification procedure on the service requirements to generate one or more abstract or concrete configurations by identifying and applying one or more corresponding reification rules to the abstract configuration, thereby designing a renewed concrete configuration of the target system and generating an operation model of the target system corresponding to the renewed concrete configuration.

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

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

[0020] The generation unit 13 generates a QoS evaluation function for evaluating the QoS (Quality of Service) of the target system configuration during the update process when updating the abstract configuration of the target system to a specific configuration designed by the design unit 12. The planning unit 14 uses the operation model and the QoS evaluation function to plan an update procedure that satisfies QoS-based criteria. The update procedure indicates the order of processing required to update the abstract configuration of the target system to a specific configuration. As an example, the update procedure includes multiple phases, and the state of one component changes in each phase.

[0021] (Effects of the Renewal Support System) As described above, the renewal support system 1 includes an acquisition unit 11 that acquires service requirements indicating requirements for a changed service, a design unit 12 that repeatedly executes a concretization procedure for the service requirements, the concretization procedure comprising: referring to a plurality of concretization rules that define a method for concretizing an abstract configuration of a target system that provides the service; identifying and applying one or more concretization rules corresponding to the abstract configuration to generate one or more abstract or concrete configurations; a generation unit 13 that generates a QoS evaluation function for evaluating the QoS of the target system configuration during the renewal when the abstract configuration of the target system is renewed to the concrete configuration designed by the design unit 12; and a planner 14 that uses the operation model and the QoS evaluation function to plan a renewal procedure that satisfies QoS-based criteria. Therefore, the renewal support system 1 has the effect of optimizing QoS during system renewal.

[0022] (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, a generation process S13, and a planning process S14.

[0023] In an acquisition process S11, at least one processor acquires service requirements indicating requirements for a changed service. In a design process S12, the at least one processor repeatedly executes a concretization procedure for the service requirements, which generates one or more abstract or concrete configurations by referring to a plurality of concretization rules that define a method for concretizing the abstract configuration of a target system providing the service and identifying and applying one or more corresponding concretization rules to the abstract configuration, thereby designing a revised concrete configuration of the target system and generating an operation model of the target system corresponding to the revised concrete configuration. In a generation process S13, the at least one processor generates a QoS evaluation function for evaluating the QoS of the target system configuration during the renewal process when the abstract configuration of the target system is renewed to the concrete configuration designed in the design process S12. In a planning process S14, the at least one processor uses the operation model and the QoS evaluation function to plan a renewal procedure that satisfies QoS-based criteria.

[0024] (Effects of Renewal Support Method) As described above, the renewal support method S1 employs a configuration including: an acquisition process S11 in which at least one processor acquires service requirements indicating requirements of a changed service; a design process S12 in which the at least one processor repeatedly executes a concretization procedure for the service requirements, in which the at least one processor refers to a plurality of concretization rules that prescribe a method of concretizing an abstract configuration of a target system that provides the 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 renewed concrete configuration of the target system and generating an operation model of the target system that corresponds to the renewed concrete configuration; a generation process S13 in which the at least one processor generates a QoS evaluation function for evaluating QoS of a configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to the concrete configuration designed by the design process S12; and a planning process S14 in which the at least one processor uses the operation model and the QoS evaluation function to plan a renewal procedure that satisfies a QoS-based standard. Therefore, the renewal support method S1 has the effect of making it possible to optimize QoS during system renewal.

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

[0026] (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.

[0027] (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.

[0028] (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).

[0029] (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.

[0030] (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.

[0031] (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.

[0032] 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, a generation unit 16A, and a planning unit 17A. The acquisition unit 11A, the design unit 12A, the evaluation unit 13A, the calculation unit 14A, the modification unit 15A, the generation unit 16A, and the planning unit 17A are examples of an acquisition means, a design means, an evaluation means, a calculation means, a determination means, a generation means, and a planning means, respectively, according to the present disclosure.

[0033] (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.

[0034] (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 updated service. 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.

[0035] (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.

[0036] (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.

[0037] (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."

[0038] 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."

[0039] 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."

[0040] The design unit 12A also generates an operation model of the target system corresponding to the updated specific configuration. The operation model is a model for searching for an update procedure for updating the abstract configuration of the target system to the specific configuration designed by the design unit 12A. As an example, the operation model has a tree structure with edges corresponding to each process required to update the target system to the specific configuration and nodes representing the state of components included in the target system's configuration. Each process required to update to the updated specific configuration is a process for changing the state of each component included in at least one of the specific configuration before and after the update from its pre-update state to its updated state. The update procedure designed by the design unit 12A will be described with reference to FIGS. 5 to 7. FIG. 5 illustrates an example of the target system's pre-update configuration and updated configuration. In FIG. 5, the pre-update configuration CF5 includes a service SV5, an application AP5, and a server SV51 as components. The updated specific configuration CF13 includes a service SV1, an application AP1, a server SV21, an application AP2, and a server SV22 as components.

[0041] 6 is a diagram showing an example of the pre-update and updated states of each component included in the target system when performing the update shown in FIG. 5 . State ST0 is the state of the component included in the target system before the update. State STe is the state of the component included in the target system after the update. In the pre-update state ST0, the state of app AP1 is "absent," the state of server SV21 is "absent," the state of app AP2 is "absent," the state of server SV22 is "absent," the state of app AP5 is "normal," and the state of server SV51 is "normal." On the other hand, in the updated state STe, the state of app AP1 is "normal," the state of server SV21 is "normal," the state of app AP2 is "normal," the state of server SV22 is "normal," the state of app AP5 is "absent," and the state of server SV51 is "absent."

[0042] In the example of Fig. 6, the design unit 12A generates an operation model for planning an update procedure in which the state of the target system transitions from state ST0 to state STe. Fig. 7 is a diagram illustrating an example of an operation model of the target system for which the design unit 12A plans an update procedure. In the example of Fig. 7, the design unit 12A generates an operation model in which the state of one component transitions in one phase. A phase refers to each process of updating the target system.

[0043] (Generation Unit - QoS Evaluation Function) The generation unit 16A in FIG. 3 generates a QoS evaluation function. The QoS evaluation function is a function that calculates an evaluation value for evaluating the impact on QoS from the state of each component included in the specific configuration designed by the design unit 12A. The QoS evaluation function is also used to evaluate the QoS of the target system configuration in the process of updating when updating the abstract configuration of the target system to 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." 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.

[0044] F (V ｓｙｓ ) = k １ ×v[E １ : Normal]+k ２ ×v[E ２ : Normal] +...+k ｎ ×v[E ｎ: Normal] ... (2) 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.

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

[0046] 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)

[0047] 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)

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

[0049] (Evaluation Unit) During the renewal of the target system, the evaluation unit 13A calculates an evaluation value indicating the degree of impact on QoS of the renewal of the target system 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 the degree of impact on QoS from the state of each component.

[0050] (Planning Unit) The planning unit 17A plans a renewal procedure that satisfies QoS-based criteria using the operation model generated by the design unit 12A and the QoS evaluation function generated by the generation unit 16A. As an example, the planning unit 17A plans the renewal procedure using QoS evaluation criteria. Here, the QoS evaluation criteria (QoS criteria) are a set of a QoS evaluation function and its lower limit value. As an example, the QoS evaluation criteria are: F １ (V ｓｙｓ ), L.B. １= 17. In this case, as an example, the planning unit 17A plans a renewal procedure that does not go through a system state in which the evaluation value indicating the degree of impact on QoS, calculated using the QoS evaluation function, falls below a predetermined lower limit. Here, the lower limit is a value that is set in advance by, for example, a system administrator or a creator of the instantiation rules, etc.

[0051] 5 and 6, the transient requirement corresponding to the configuration CF5 in FIG. 5 is, for example, 18×v[application AP5: normal]×v[server SV51: normal]≧10, and the transient requirement corresponding to the specific configuration CF13 is, for example, {12×v[application AP1: normal]×v[server SV21: normal]+13×[application AP2: normal]×v[server SV22: normal]}≧10.

[0052] (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.

[0053] (Upgrading Unit) The upgrading unit 15A upgrades the system step by step from the pre-upgrade configuration to the upgraded configuration based on the service requirements specified by the user. At this time, the upgrading unit 15A upgrades the system step by step according to the upgrade procedure planned by the planning unit 17A. For example, the method described in Patent Document 3 mentioned above can be used as the upgrading method.

[0054] Furthermore, the updating unit 15A determines whether to wait or execute the updating of the target system in each phase included in the updating procedure planned by the planning unit 17A, using the evaluation value and the load information in that phase. More specifically, as an example, the updating unit 15A manages the state of each component (constituent part) in the system during the updating, and determines to wait for the system updating if 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.

[0055] <Flow of Renewal Procedure Planning Method> Figure 8 is a flow diagram showing an example of the flow of the renewal procedure planning method according to the present disclosure. In step S201, the acquisition unit 11A acquires service requirements (second service requirements) that have been changed from the first service requirements. In step S202, the design unit 12A designs a renewed specific configuration of the target system based on the instantiation rules corresponding to the service requirements acquired in step S201, and generates an operation model corresponding to the renewed specific configuration.

[0056] In step S203, the generating unit 16A generates a QoS evaluation function for evaluating the QoS of the configuration of the target system that is in the process of being updated.

[0057] In step S204, the planner 17A uses the operation model and the QoS evaluation function to plan a renewal procedure that satisfies the QoS-based criteria. FIG. 9 is a diagram showing specific examples of the states and evaluation values ​​of the target system. The example in FIG. 9 shows the determination results of whether the transient requirement is met for each of states ST101 to ST104. In state ST101, the first evaluation value and the second evaluation value are both equal to or greater than the lower limit "10," so the transient requirement is met. On the other hand, in state ST102, the first evaluation value and the second evaluation value are both below the lower limit "10," so the transient requirement is violated. In state ST103, the first evaluation value is equal to or greater than the lower limit "10," so the transient requirement is met. In addition, in state ST104, the second evaluation value is equal to or greater than the lower limit "10," so the transient requirement is met.

[0058] 10 is a diagram illustrating a specific example of a planning process for a renewal procedure performed by the planning unit 17A. The planning unit 17A searches for a path from a pre-renewal state to a renewed state while avoiding a state of the target system that violates a transition requirement. As a method for searching for a path in a system renewal problem, for example, the method described in Patent Document 4 can be used.

[0059] 11 is a diagram showing an example of an updating procedure planned by the planning unit 17A, and 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. 11, updating is performed in the order of phase F1, phase F2, phase F3, and so on.

[0060] 12 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 indicating requirements for a changed service. In step S102, the design unit 12A designs a renewed specific configuration of the target system based on the concretization rules corresponding to the service requirements acquired in step S101.

[0061] In step S103, the generator 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 generator 16A generates a QoS evaluation function corresponding to the updated specific configuration 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.

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

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

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

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

[0066] 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. 12. 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.

[0067] (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.

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

[0069] As a variation of the above-described process, a configuration using both a first QoS evaluation function corresponding to the configuration before updating and a second QoS evaluation function corresponding to the updated configuration will be described. In step S103, the generation unit 16A may generate a first QoS evaluation function corresponding to the configuration of the target system before updating, and may also generate a second QoS evaluation function corresponding to the updated specific configuration 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.

[0070] 5 , the generation unit 16A may generate the following as a first QoS evaluation function corresponding to the pre-update configuration CF5: 18×v[application AP5: normal]×v[server SV51: normal]. The generation unit 16A may also generate the following as a second QoS evaluation function corresponding to the post-update specific configuration CF13: 12×v[application AP1: normal]×v[server SV21: normal]+13×v[application AP12: normal]×v[server SV22: normal].

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

[0072] In step S106, for example, the updating unit 15A may determine whether to wait or execute the update of the target system in each phase of the update procedure using the first evaluation value, the second evaluation value, and the load information in that phase. For example, the updating unit 15A may use the larger of the first evaluation value and the second evaluation value as an overall evaluation value, and determine to wait for the update if the overall evaluation value is below 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 preset by a system administrator, a creator of the instantiation rules, or the like. The updating unit 15A may perform the process of step S106 in each of multiple phases included in the update of the target system. In other words, the update of the target system includes multiple phases, and the updating unit 15A may determine whether to wait or execute the update in each of the multiple phases of the target system.

[0073] (Effects of Information Processing Device) When configuring a mechanism for autonomous system operation, 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, depending on the upgrade procedure, circumstances may arise in which the service must be completely stopped midway.

[0074] In contrast, in the information processing device 1A according to the present disclosure, the design unit 12A designs a specific updated configuration of the system based on service requirements input by the user, generates an operation model corresponding to the specific updated configuration, and uses the operation model and a QoS evaluation function to plan an update procedure in which an evaluation value indicating the degree of impact on QoS satisfies a QoS-based standard. By having the information processing device 1A update the target system according to the planned update procedure, it is possible to proceed with the update of the target system while preventing the QoS from becoming too low.

[0075] Furthermore, the information processing device 1A employs a configuration in which the planning unit 17A plans a renewal procedure that does not pass through a system state in which the evaluation value calculated using the QoS evaluation function falls below a predetermined lower limit. Therefore, the information processing device 1A has the effect of being able to proceed with renewal of the target system while preventing the evaluation value regarding the impact on QoS from becoming too low.

[0076] The information processing device 1A also includes a calculation unit 14A that calculates load information related to the load of the target system, and a renewal unit 15A that determines whether to wait or execute renewal of the target system in each phase included in the renewal procedure planned by the planning unit 17A, using the evaluation value and load information in that phase. Therefore, the information processing device 1A can prevent the QoS from becoming too low during renewal of the target system.

[0077] Furthermore, the information processing device 1A is configured such that the updating unit 15A determines to wait for updating of the target system if the impact on QoS indicated by the evaluation value is greater than the allowable range determined by the load information. Therefore, the information processing device 1A has the effect of being able to proceed with system updating so that the impact on QoS falls within the allowable range.

[0078] Furthermore, in the information processing device 1A, a conversion rule that defines a method for converting a QoS evaluation function is associated with each of the multiple instantiation rules, and the generation unit 16A generates a QoS evaluation function using the conversion rule associated with one or more instantiation rules specified by the design unit 12A. By calculating an evaluation value using a QoS evaluation function generated using the conversion rule associated with the instantiation rule specified by the design unit 12A, an effect is obtained in which an evaluation suitable for the updated specific configuration can be performed.

[0079] Furthermore, the information processing device 1A is configured such that each of the multiple concatenation rules is associated with a type of load information related to the load of the target system, and the information processing device 1A includes a calculation unit 14A that calculates the load information by referring to the type of load information associated with 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 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 updated specific configuration.

[0080] Furthermore, the information processing device 1A is further equipped with an evaluation unit 13A, in which a generation unit 16A generates a first QoS evaluation function corresponding to the configuration of the target system before the update and generates a second QoS evaluation function corresponding to the specific updated configuration designed by a design unit 12A, and calculates a first evaluation value using the first QoS evaluation function and a second evaluation value using the second QoS evaluation function, and the update unit 15A determines, in each phase included in the update procedure planned by a planning unit 17A, whether to wait for or execute the update of the target system using the first evaluation value, the second evaluation value, and the load information in that phase. By making the above determination taking into account both the configuration before the update and the updated configuration, it is possible to obtain the effect of preventing a deterioration in QoS due to the update.

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

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

[0083] 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 13. Figure 13 is a block diagram showing the hardware configuration of computer C that functions as each of the above devices.

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

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

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

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

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

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

[0090] (Appendix A1) A renewal support system comprising: an acquisition means for acquiring service requirements indicating requirements for a changed service; a design means for repeatedly executing a concretization procedure on the 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 of concretizing an abstract configuration of a target system that provides the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby designing a renewed concrete configuration of the target system and generating an operation model of the target system corresponding to the renewed concrete configuration; a generation means for generating a QoS evaluation function for evaluating QoS of a configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to the concrete configuration designed by the design means; and a planning means for planning a renewal procedure that satisfies a QoS-based standard, using the operation model and the QoS evaluation function.

[0091] (Appendix A2) The renewal support system according to Appendix A1, wherein the planning means plans a renewal procedure that does not go through a system state in which an evaluation value indicating a degree of impact on QoS, calculated using the QoS evaluation function, falls below a predetermined lower limit value.

[0092] (Appendix A3) The renewal support system according to Appendix A2, further comprising: a calculation means for calculating load information relating to the load of the target system; and a determination means for determining, in each phase included in the renewal procedure planned by the planning means, whether to wait or execute renewal of the target system, using the evaluation value and the load information in that phase.

[0093] (Supplementary Note A4) The renewal support system according to Supplementary Note A3, wherein the determining unit determines to put the renewal on hold when the influence on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

[0094] (Appendix A5) The renewal support system according to any one of Appendices A1 to A4, 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 generation means generates the QoS evaluation function using the conversion rule associated with the one or more concretization rules identified by the design means.

[0095] (Appendix A6) The renewal support system according to Appendix A5, wherein each of the plurality of concretization rules is associated with a type of load information relating to a load on the target system, and further comprising a calculation means that 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.

[0096] (Appendix A7) 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 renewed specific configuration designed by the designing means, and further comprises an evaluating means which calculates a first evaluation value using the first QoS evaluation function, and calculates a second evaluation value using the second QoS evaluation function, and wherein the determining means determines, in each phase included in the renewal procedure planned by the planning means, whether to wait for or execute the renewal of the target system, using the first evaluation value, the second evaluation value, and the load information in that phase.

[0097] (Supplementary Note A8) The renewal support system according to any one of Supplementary Notes A3, A4, and A7, wherein the load information includes information relating to a request for a service provided by the target system.

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

[0099] (Supplementary Note B1) A renewal support method including: an acquisition process, by at least one processor, to acquire service requirements indicating requirements for a changed service; a design process, by the at least one processor, to design a renewed concrete configuration of the target system by repeatedly executing a concretization procedure on the 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 the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby generating one or more abstract or concrete configurations; a generation process, by the at least one processor, to generate a QoS evaluation function for evaluating QoS of a configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to a concrete configuration designed by the design process; and a planning process, by the at least one processor, to plan a renewal procedure that satisfies a QoS-based standard, by using the operation model and the QoS evaluation function.

[0100] (Appendix B2) The renewal support method according to Appendix B1, wherein in the planning process, the at least one processor plans a renewal procedure that does not go through a system state in which an evaluation value indicating the degree of impact on QoS, calculated using the QoS evaluation function, falls below a predetermined lower limit value.

[0101] (Supplementary Note B3) The renewal support method according to Supplementary Note B2, further comprising: a calculation process in which the at least one processor calculates load information relating to the load of the target system; and a determination process in which the at least one processor determines, in each phase included in the renewal procedure planned in the planning process, whether to wait or execute the renewal of the target system, using the evaluation value and the load information in that phase.

[0102] (Supplementary Note B4) The renewal support method according to Supplementary Note B3, 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.

[0103] (Appendix B5) The renewal support method according to any one of Appendices B1 to B4, wherein each of the plurality of concretization rules is associated with a conversion rule that specifies a method for converting the QoS evaluation function, and in the generation process, 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.

[0104] (Appendix B6) The renewal support method according to Appendix B5, wherein each of the plurality of concretization rules is associated with a type of load information relating to the load of the target system, and the at least one processor further includes a calculation process for calculating the load information by referring to the type of load information associated with the one or more concretization rules identified in the design process.

[0105] (Supplementary Note B7) The renewal support method according to 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 renewed specific configuration designed in the design process; and further includes an evaluation process in which 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 or execute the renewal of the target system, in each phase included in the renewal procedure planned in the planning process, using the first evaluation value, the second evaluation value, and the load information in that phase.

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

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

[0108] (Supplementary Note 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 service requirements indicating requirements for a changed service; a design means for designing an updated concrete configuration of the target system by repeatedly executing a concretization procedure for the 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 the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby generating one or more abstract or concrete configurations; a generation means for generating a QoS evaluation function for evaluating the QoS of the configuration of the target system in the middle of updating when the abstract configuration of the target system is updated to the concrete configuration designed by the design means; and a planning means for planning an update procedure that satisfies a QoS-based standard, using the operation model and the QoS evaluation function.

[0109] (Appendix C2) The renewal support program according to Appendix C1, wherein the planning means plans a renewal procedure that does not go through a system state in which an evaluation value indicating the degree of impact on QoS, calculated using the QoS evaluation function, falls below a predetermined lower limit value.

[0110] (Appendix C3) The update support program according to Appendix C2, further causing the computer to function as: a calculation means for calculating load information relating to the load of the target system; and a determination means for determining, in each phase included in the update procedure planned by the planning means, whether to wait or execute the update of the target system using the evaluation value and the load information in that phase.

[0111] (Supplementary Note C4) The renewal support program according to Supplementary Note C3, wherein the determining means determines to put the renewal on hold when the influence on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

[0112] (Appendix C5) The renewal support program according to any one of Appendices C1 to C4, 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 generation means generates the QoS evaluation function using the conversion rule associated with the one or more concretization rules identified by the design means.

[0113] (Appendix C6) The renewal support program according to Appendix C5, wherein each of the plurality of concretization rules is associated with a type of load information relating to the load of the target system, and the computer is further made to function as a calculation means that 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.

[0114] (Appendix C7) The renewal support program according to Appendix C3 or C4, 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 renewed specific configuration designed by the designing means; the computer further functions as an evaluating means that 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, in each phase included in the renewal procedure planned by the planning means, whether to wait for or execute the renewal of the target system, using the first evaluation value, the second evaluation value, and the load information in that phase.

[0115] (Supplementary Note C8) The renewal support program according to any one of Supplementary Note C3, C4, and C7, wherein the load information includes information relating to a request for a service provided by the target system.

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

[0117] (Supplementary Note D1) A renewal support system comprising at least one processor, which executes: an acquisition process for acquiring service requirements indicating requirements for a changed service; a design process for designing a renewed concrete configuration of the target system by repeatedly executing a concretization procedure on the 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 the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby generating one or more abstract or concrete configurations; a generation process for generating a QoS evaluation function for evaluating QoS of a configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to a concrete configuration designed by the design process; and a planning process for planning a renewal procedure that satisfies a QoS-based standard by using the operation model and the QoS evaluation function.

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

[0119] (Appendix D2) The renewal support system described in Appendix D1, wherein in the planning process, the at least one processor plans a renewal procedure that does not go through a system state in which an evaluation value indicating the degree of impact on QoS, calculated using the QoS evaluation function, falls below a predetermined lower limit value.

[0120] (Appendix D3) The upgrade support system according to Appendix D2, wherein the at least one processor further executes a calculation process that calculates load information regarding the load of the target system, and a determination process that determines, in each phase included in the upgrade procedure planned in the planning process, whether to wait for or execute the upgrade of the target system using the evaluation value and the load information in that phase.

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

[0122] (Appendix D5) The renewal support system according to any one of Appendices D1 to D4, 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 in the generation process, 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.

[0123] (Appendix D6) The renewal support system according to Appendix D5, wherein each of the plurality of concretization rules is associated with a type of load information relating to the load of the target system, and the at least one processor further executes a calculation process to calculate the load information by referring to the type of load information associated with the one or more concretization rules identified in the design process.

[0124] (Appendix D7) The upgrade support system according to 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 upgrade, and generates a second QoS evaluation function corresponding to the upgraded specific configuration designed in the design process; the at least one processor further executes an evaluation process of calculating a first evaluation value using the first QoS evaluation function, and calculating a second evaluation value using the second QoS evaluation function; and in the determination process, the at least one processor determines whether to wait or execute the upgrade of the target system, in each phase included in the upgrade procedure planned in the planning process, using the first evaluation value, the second evaluation value, and the load information in that phase.

[0125] (Supplementary Note D8) The renewal support system according to any one of Supplementary Notes D3, 4, and 7, wherein the load information includes information relating to a request for a service provided by the target system.

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

[0127] (Appendix E1) A non-transitory recording medium having recorded thereon a program that causes a computer to function as an update support system, the program causing the computer to execute the following: an acquisition process that acquires service requirements that indicate requirements for a changed service; a design process that designs an updated concrete configuration of the target system by repeatedly executing a concretization procedure on the 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 the service, and identifying and applying one or more concretization rules that correspond to the abstract configuration, thereby generating one or more abstract or concrete configurations; a generation process that generates a QoS evaluation function for evaluating the QoS of the configuration of the target system in the middle of update when updating the abstract configuration of the target system to the concrete configuration designed by the design process; and a planning process that uses the operation model and the QoS evaluation function to plan an update procedure that satisfies QoS-based criteria.

[0128] 1 Renewal support system 1A Information processing device 11, 11A Acquisition unit 12, 12A Design unit 13, 13A Evaluation unit 14, 17A Determination unit 14A Calculation unit 15A Renewal unit 16A Generation unit 17A Planning unit

Claims

1. A renewal support system comprising: an acquisition means for acquiring service requirements indicating the requirements of a changed service; a design means for repeatedly executing a concretization procedure on the service requirements, which generates one or more abstract or concrete configurations by referencing a plurality of concretization rules that specify a method for concretizing the abstract configuration of a target system that provides the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby designing a renewed concrete configuration of the target system and generating an operation model of the target system that corresponds to the renewed concrete configuration; a generation means for generating a QoS evaluation function for evaluating the QoS (Quality of Service) of the configuration of the target system in the process of being renewed when the abstract configuration of the target system is renewed to the concrete configuration designed by the design means; and a planning means for planning a renewal procedure that satisfies QoS-based standards using the operation model and the QoS evaluation function.

2. The upgrade support system of claim 1, wherein the planning means plans an upgrade procedure that does not go through a system state in which the evaluation value indicating the degree of impact on QoS, calculated using the QoS evaluation function, falls below a predetermined lower limit value.

3. The upgrade support system according to claim 2, further comprising: a calculation means for calculating load information relating to the load of the target system; and a determination means for determining, in each phase included in the upgrade procedure planned by the planning means, whether to wait for or execute the upgrade of the target system using the evaluation value and the load information in that phase.

4. The renewal support system according to claim 3, wherein the determining means determines to put the renewal on hold if the impact on the QoS indicated by the evaluation value is greater than an allowable range determined by the load information.

5. A renewal support system as described in 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 the generation means generates the QoS evaluation function using the conversion rule associated with the one or more instantiation rules identified by the design means.

6. The renewal support system according to claim 5, wherein each of the plurality of concretization rules is associated with a type of load information relating to the load of the target system, and further comprising a calculation means for calculating the load information by referring to the type of load information associated with the one or more concretization rules identified by the design means.

7. The renewal support system according to claim 3, 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 renewed specific configuration designed by the designing means, and further comprises an evaluating means that 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, in each phase included in the renewal procedure planned by the planning means, whether to wait for or execute the renewal of the target system, using the first evaluation value, the second evaluation value, and the load information in that phase.

8. The upgrade support system according to claim 3, wherein the load information includes information regarding requests for services provided by the target system.

9. A renewal support method including: an acquisition process in which at least one processor acquires service requirements indicating requirements for a changed service; a design process in which the at least one processor repeatedly executes a concretization procedure on the service requirements, which generates one or more abstract or concrete configurations by referring to a plurality of concretization rules that specify a method for concretizing an abstract configuration of a target system that provides the service, and identifies and applies one or more concretization rules corresponding to the abstract configuration, thereby designing a renewed concrete configuration of the target system and generating an operation model of the target system corresponding to the renewed concrete configuration; a generation process in which the at least one processor generates a QoS evaluation function for evaluating the QoS of the configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to a concrete configuration designed by the design process; and a planning process in which the at least one processor uses the operation model and the QoS evaluation function to plan a renewal procedure that satisfies QoS-based criteria.

10. A renewal support program for causing a computer to function as a renewal support system, comprising: an acquisition means for acquiring service requirements indicating the requirements of a changed service; a design means for designing a renewed concrete configuration of the target system by repeatedly executing a concretization procedure for the service requirements, which generates one or more abstract or concrete configurations by referencing a plurality of concretization rules that specify a method for concretizing the abstract configuration of a target system that provides the service, and identifying and applying one or more concretization rules corresponding to the abstract configuration, thereby generating one or more abstract or concrete configurations; a generation means for generating a QoS evaluation function for evaluating the QoS of the configuration of the target system in the middle of renewal when the abstract configuration of the target system is renewed to the concrete configuration designed by the design means; and a planning means for planning a renewal procedure that satisfies QoS-based criteria using the operation model and the QoS evaluation function.

Images