JP7217076B2 - Resource pool management system and method - Google Patents

Description

The present invention relates generally to building systems that are used in providing application services.

For example, with the development of virtual computing resource provision services represented by cloud services and private virtual networks (VPNs), virtual instances on various types of physical devices have become available. A virtual system is constructed by combining a plurality of types of such virtual instances, and a form of providing application services over a wide area using this system is expanding. In constructing and operating such virtual systems, a multi-tenant configuration is generally assumed in which a plurality of virtual systems are constructed on a limited number of physical systems and operated independently. Each independently operated virtual system is required to have the functions and performance required by the application services that use it. For example, Patent Literatures 1 and 2 are known as prior arts for constructing such a virtual system.

Patent No. 5944870 Patent No. 6170237

Virtual systems are used for application services, such as information processing application services. For example, processing according to requests such as information processing requests or data search requests from distributed bases is executed on virtual computing resources existing in the cloud. An application service is a service provided by executing an application program in a virtual system, or in other words, a system combining an application program and a virtual system.

However, as user needs for application services diversify, information systems are required to continue to be sophisticated, and the virtual systems that support them need to incorporate virtual resources from various heterogeneous systems. is coming. Heterogeneous systems are, for example, mobile access systems and sensor nets for collecting and controlling information from various sensors. Even within a single mobile access system, methods are diversified. For example, there are mobile session control methods represented by LTE (Long Term Evolution) (registered trademark), and various methods of Low Power Wireless Access (LPWA). and WiFi etc. As for the sensor network, there are various methods depending on the sensor type, field and application. Furthermore, the implementation form of application services is also diversifying in various system configurations such as microservices and serverless.

Also, when a virtual system incorporates virtual resources from various heterogeneous systems as described above, those virtual resources are not necessarily managed by a single administrator. In this case, an ASP (Application Service Provider) must identify the administrator and issue a request for the virtual resource for each system in order to acquire virtual resources from the required heterogeneous systems.

In this way, with the response to diversifying user needs and the expansion of application areas in various industrial fields, the conditions required for virtual systems by each application service (for example, conditions related to function, performance, and service area) will be changed in the future. likely to become more and more complex.

A resource pool management system intervening between an ASP system and an ISP (Infrastructure Service Provider) system is constructed. The resource pool includes, as virtual resources, data indicating one or more requirements including one or more functions for realizing each of a plurality of individual infrastructures provided by a plurality of ISPs. A resource pool management system identifies from the resource pool two or more virtual resources having two or more requirements that are within an acceptable difference from two or more requirements required by an ASP system for execution of an application program; A virtual system, which is a logical connection of the two or more virtual resources and is used to execute the application service, is constructed.

According to the present invention, it consists of a plurality of virtual resources corresponding to a plurality of individual infrastructures with different requirements (e.g., functions) and administrators (an example of an ISP), and the difference from the conditions required by the ASP is within an allowable range. It is possible to quickly and efficiently construct a virtual system with requirements.

1 shows the configuration of an entire system including a resource pool management system according to a first embodiment; Some features of the resource pool management system are shown. A configuration example of a template store is shown. A configuration example of a virtual resource store is shown. Shows an example configuration store configuration. 3 shows the overall flow of processing including virtual system construction processing. 3 shows the flow of virtual system change processing. 4 shows the flow of fault handling processing. 2 shows an n-dimensional requirement vector as an example of expression of n individual requirements belonging to functionality requirements. An N-dimensional requirement vector is shown as an example of an expression of N individual requirements in which (Nn) individual requirements belonging to non-functional requirements are added to n individual requirements belonging to functional requirements. An example of an individual requirement vector for an individual infrastructure is shown. An example of a requirement vector of virtual system requirements of an EtoE virtual system is shown. An example of a difference between a requirement vector of calculation requirements and a requirement vector of requirements is shown. An example of a requirement vector of virtual system requirements of a virtual system having alternative virtual resources is shown.

In the following description, an "interface device" may be one or more interface devices. The one or more interface devices may be one or more of the same type of communication interface devices (for example, one or more NICs (Network Interface Cards)) or two or more different types of communication interface devices (for example, NICs and It may be an HBA (Host Bus Adapter).

Also, in the following description, "memory" may be one or more memory devices, typically a main memory device. At least one memory device in the memory may be a volatile memory device or a non-volatile memory device.

Also, in the following description, a "persistent storage device" is one or more persistent storage devices. A permanent storage device is typically a non-volatile storage device (for example, an auxiliary storage device), and specifically, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

Also, in the following description, "storage" may be at least memory of memory and persistent storage.

Also, in the following description, a "processor" is one or more processor devices. The at least one processor device is typically a microprocessor device such as a CPU (Central Processing Unit), but may be another type of processor device such as a GPU (Graphics Processing Unit). At least one processor device may be single-core or multi-core. At least one processor device may be a processor core. At least one processor device may be a broadly defined processor device such as a hardware circuit (for example, FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs part or all of processing.

In the following description, the expression "xxx store" may be used to describe information that produces an output for an input. A learning model such as a neural network that generates Thus, "xxx store" can be referred to as "xxx information". Also, in the following description, the configuration of each store is an example, and one store may be divided into two or more stores, or all or part of two or more stores may be one store. may

In addition, in the following description, the function may be described using the expression “kkk unit”, but the function may be realized by executing one or more computer programs by a processor, or may be realized by executing one or more computer programs. It may be realized by the above hardware circuits (FPGA or ASIC, for example). When a function is realized by executing a program by a processor, the defined processing is performed while appropriately using a storage device and/or an interface device, etc., so the function may be at least part of the processor. good. A process described with a function as the subject may be a process performed by a processor or a device having the processor. Programs may be installed from program sources. The program source may be, for example, a program distribution computer or a computer-readable recording medium (for example, a non-temporary recording medium). The description of each function is an example, and multiple functions may be combined into one function, or one function may be divided into multiple functions.

Also, in the following description, a "computer system" is a system that includes one or more physical computers. A physical computer may be a general purpose computer or a special purpose computer.

In the following description, common parts of reference numerals may be used when similar elements are not distinguished, and reference numerals may be used when similar elements are distinguished. For example, when ASP systems are not distinguished, they are referred to as "ASP system 301", and when ASP systems are distinguished, they are referred to as "ASP system 301A" and "ASP system 301B".

FIG. 1 shows a configuration example of an entire system including a resource pool management system according to Embodiment 1 of the present invention.

A resource pool management system 100 is constructed as a boundary layer between an ASP (Application Service Provider) layer 300 and an ISP (Infrastructure Service Provider) layer 200 . The resource pool management system 100 has a resource pool 110 and a system construction section 50 .

ASP layer 300 is a layer to which one or more ASP systems 301 belong. The ASP system 301 may be a system realized by executing predetermined software on a computer system, or an ASP computer system (for example, a personal computer). The ASP system 301 specifies to the resource pool management system 100 a plurality of conditions required for application services (execution of application programs). An ASP may be rephrased as a user.

The ISP layer 200 is a layer to which multiple ISP systems 221 belong. The ISP system 221 may be a system realized by executing predetermined software on a computer system, or an ISP computer system. The ISP system 221 registers data indicating one or more requirements (including one or more functions) for realizing the individual infrastructure 211 in the resource pool 110 as a virtual resource, or performs virtualization according to instructions from the system construction unit 50 . It controls the individual infrastructure 211 for system construction. In the example of FIG. 1, the ISP and the infrastructure are one-to-one, but this need not be the case. For example, one ISP may provide multiple types of infrastructure, or multiple ISPs may provide one individual infrastructure. Also, in the example of FIG. 1, the ISP system 221 and the individual infrastructure 211 are one-to-one, but this need not be the case.

The resource pool 110, for example, has a virtual resource store 111 and multiple managers 112 (eg, 112A-112E). Each management unit 112 may be included in the system construction unit 50, and the resource pool 110 may be the virtual resource store 111 itself. The system construction unit 50 has an ASP interface unit 130, a matching unit 121, a configuration control unit 122, and a virtual resource control unit 113, for example. The system construction unit 50 may manage the template store 124 and the configuration store 123 in the resource pool management system 100, for example. The resource pool management system 100 may be a computer system or a system realized by executing predetermined software on a computer system. A computer system, for example, has an interface device, a storage device, and a processor connected thereto. Each of virtual resource store 111, template store 124 and configuration store 123 are stored, for example, in a storage device. The management unit 112 and the system construction unit 50 are implemented, for example, by executing one or more programs on a processor.

The resource pool 110 stores data indicating one or more requirements including one or more functions for realizing each of the individual infrastructures 211 provided by the ISP systems 221 as virtual resources. Including as The system construction unit 50 establishes two or more virtual system requirements (an example of two or more conditions) required by the ASP system 301 for execution of the application program, and has two or more requirements whose difference is within an allowable range. A resource is identified from the resource pool 110, and a virtual system, which is a logical connection of the two or more virtual resources and is used to execute the application service, is constructed. In building a virtual system, the system construction unit 50 identifies an ISP system 221 that provides an individual infrastructure 211 corresponding to each of two or more virtual resources, and assigns the virtual infrastructure to the ISP system 221. It instructs the activation of the individual infrastructure resource corresponding to the resource (the part of the individual infrastructure 211 corresponding to the virtual resource).

According to this embodiment, a virtual system can be quickly created that is composed of a plurality of virtual resources corresponding to a plurality of individual infrastructures 211 with different requirements and ISPs, and has requirements that differ from the conditions requested by the ASP within an allowable range. and efficient construction.

An example of a detailed description of FIG. 1 is, for example, as follows.

As shown in FIG. 1, the resource pool management system 100 mediates between the ISP system 221 and the ASP system 301 to provide the ASP with a virtual system that combines requirements (functions) from the individual infrastructure 211. . Individual infrastructure 211 includes, for example, sensor net 211A, radio access network 211B, SD-WAN 211C, VPN (Virtual Private Network) 211D, and cloud 221E. Each of the ISP systems 221A to 221E corresponding to these individual infrastructures 211A to 211E, respectively, has functional requirements (for example, communication bandwidth of physical resources, functions and performance such as start points or end points) and non-functional requirements of the individual infrastructures 211. Data indicating the compatibility requirement (for example, redundancy) is registered in the virtual resource store 111 of the resource pool management system 100 as a virtual resource. Data indicating link functions 231 (for example, 231A to 231D) that connect the physical resources of each individual infrastructure 211 are also included in the virtual resource as one piece of connection information. ISP system 221 may at least manage virtualization and management of individual infrastructure 211 . For example, ISP system 221A virtualizes sensor net 211A (eg, network 2111, multiple sensors 2112 (eg, which may include at least one surveillance camera), and gateway 2113), and virtualized sensor net 211A. is registered in the virtual resource store 111 as a virtual resource. Also, for example, the ISP system 221E registers the virtual resource as the cloud 211E in the virtual resource store 111. FIG.

A virtual resource (data) registered in the virtual resource store 111 is managed by a management unit 112 (eg, server) according to its requirements (eg, function and performance). For example, as an example of the management unit 112, a connection management unit 112C that manages connection information (for example, a communication band, a start point or an end point, etc.), a redundant configuration management unit 112A that manages a redundant configuration, a user management unit that manages users (ASPs) 112E, a security management unit 112B that manages access policies and the like for each user, and a VM management unit 112D that manages VMs (Virtual Machines) on the cloud 211E. These management unit types (server types) may be configured according to the requirements of the virtual system or the functions of the connected individual infrastructure 211, etc., and are not limited to the exemplified types.

Also, the user management unit 112E has a function of managing access policies and the like corresponding to ASPs, but it does not necessarily correspond one-to-one. A single user may use multiple ASP instances.

On the other hand, the ASP system 301 requests the resource pool management system 100 via the ASP interface unit 130 for a virtual system having requirements (for example, functions and performance) corresponding to the required conditions (for example, functions and performance). do. For inputting conditions, the ASP system 301 uses a service template stored in the template store 124 of the resource pool management system 100 and provided via the ASP interface unit 130 . A service template is, for example, data prepared for each ASP type, and is a template of virtual system requirements. Communication between the resource pool management system 100 and the ASP system 301 is performed via the ASP interface section 130 .

Virtual system requirements (an example of two or more conditions) associated with a request from the ASP system 301 are verified for consistency by the matching unit 121, and divided into partial requirements (one or more is decomposed and expanded as an example of the condition of The management unit 112 to which the partial requirements have been expanded searches the virtual resource store 111 for virtual resources that can correspond to the expanded partial requirements, thereby matching them. As a result, virtual resources with requirements that match the partial requirements are identified.

The virtual resource matched with the partial requirement is determined by the matching unit 121 as a component of the virtual system and passed to the configuration control unit 122 . The configuration control unit 122 combines the matched virtual resources to configure a virtual system corresponding to the virtual system requirements from the ASP system 301, and controls the configuration and the virtual resources in the virtual system (in other words, individual infrastructures). 211) is registered in the configuration store 123. Based on the information registered in the configuration store 123, the virtual resource control unit 113 configures the individual infrastructures 211 for each of the two or more individual infrastructures 211 corresponding to the two or more virtual resources that make up the virtual system. The ISP system 221 to be managed is instructed to activate the virtual resource.

Two or more ISP systems 221 each instructed to activate a virtual resource respond to the instruction by allocating or activating the physical resource of the individual infrastructure 211 managed by the ISP system 221. , the deployment of the virtual system (eg, EtoE (end-to-end) virtual system) is completed. As a result, construction of the virtual system is completed. For example, in the configuration illustrated in FIG. 1, a virtual system is constructed in which data output from sensor 2112 in sensor net 211A (sensor 2112 connected to network 2111) is accommodated in VM 2152 in cloud 211E. The virtual system is used by ASPs that have requested the above virtual system requirements.

FIG. 2 shows some functions of the resource pool management system 100 .

An arrow 141 extending from the ISP system 221 to the resource pool management system 100 is either virtual resource registration or resource failure notification.

Virtual resource registration is registration of virtual resources. That is, virtual resources from the ISP system 221 of the individual infrastructure 211 are registered in the resource pool 110 . In FIG. 2, only the virtual resource registration from the ISP system 221A is indicated by reference numerals, but the other ISP system 221 also performs virtual resource registration in the same manner. Also, FIG. 2 shows a case where a plurality of individual infrastructures of the same type exist. The resource pool 110 logically reserves virtual resources as so-called usage rights on the virtual resource store 111 . In such resource holding, various forms are possible according to the provision form of the physical resources of the individual infrastructure 211 and the fluctuation of virtual system demand from the ASP. There may be a case where usage rights are reserved in the resource pool 110 in advance by predicting fluctuations in virtual system demand, or a virtual resource is registered in the resource pool 110 in a required time frame based on a reservation from an ASP.

A resource failure notification is a notification of a virtual resource failure corresponding to the individual infrastructure 211 . That is, when the individual infrastructure 211 fails, the ISP system 221 notifies the resource pool management system 100 of the failure of the virtual resource corresponding to the individual infrastructure 211 .

An arrow 142 extending from the ASP system 301 to the service template 1241 is either a virtual system construction request or a virtual system change request. The virtual system construction request may have virtual system requirements (requirements for the entire virtual system), and the virtual system change request may have post-change virtual system requirements (requirements for the entire virtual system after change), It may have a virtual system requirement part (changed requirement) corresponding to the changed part. A virtual system requirement may be a combination of a service template 1241 and conditions specified by an ASP.

The matching unit 121 of the system construction unit 50 has, for example, a decomposition unit 1210, a functionality conversion unit 1211, a functionality matching unit 1212, a non-functional conversion unit 1213, and a non-functional matching unit 1214.

A decomposing unit 1210 decomposes the virtual system requirements into functional requirements and non-functional requirements.

A functionality conversion unit 1211 converts functionality requirements into corresponding functionality virtual resource requirements. The functionality matching unit 1212 searches the virtual resource store 111 of the resource pool 110 for virtual resources having requirements that match the functionality virtual resource requirements, and delivers the extracted virtual resources to the configuration control unit 122 .

A non-functionality converter 1213 converts non-functional requirements into corresponding non-functional virtual resource requirements. The non-functional matching unit 1214 searches the virtual resource store 111 of the resource pool 110 for virtual resources having requirements that match the non-functional virtual resource requirements, and passes the extracted virtual resources to the configuration control unit 122 .

The configuration control unit 122 registers the virtual system configuration information corresponding to the virtual system construction request or the virtual system change request in the configuration store 123 by synthesizing (logically connecting) the passed virtual resources.

An arrow 144 extending from the resource pool management system 100 to the ISP system 221 is an activation instruction (for example, a resource reservation or resource change and activation instruction). Based on the information in the configuration store 123, the virtual resource control unit 113 gives an activation instruction to the ISP system 221 of the individual infrastructure 211 corresponding to the virtual resource as a component of the virtual system.

Arrows 145 extending from configuration controller 122 to ASP system 301 are deployment notifications, change notifications, or failure notifications.

Specifically, for example, when a virtual system is newly constructed, the configuration control unit 122 notifies the ASP system 301 that issued the virtual system construction request of the deployment of the virtual system (the virtual system deployment is completed). issue a notice indicating that It should be noted that, in this embodiment, "construction of a virtual system" includes configuration and deployment of a virtual system. The “virtual system configuration” may be extraction of two or more virtual resources corresponding to the virtual system requirements and creation of virtual system configuration information in which the two or more virtual resources are logically connected. "Deployment of virtual system" is to make the virtual system available by securing (or changing) resources and activating the link function, etc. by giving activation instructions to the ISP system 221 based on the virtual system configuration information. That is.

Further, for example, when the virtual system is changed, the configuration control unit 122 notifies the ASP system 301 that issued the virtual system change request of the change of the virtual system (notification indicating that the change of the virtual system has been completed). to be issued. The change of the virtual system may be a change of the entire virtual system or a part of the virtual system, and the virtual system is deployed even when the virtual system is changed.

Also, for example, when a resource failure notification is issued from the ISP system 221 , the virtual resource control unit 113 registers information specified from the resource failure notification in the configuration store 123 . When the configuration control unit 122 identifies the registered information from the configuration store 123, the configuration control unit 122 identifies an ASP that uses the virtual system containing the faulty virtual resource, and sends the information to the ASP system 301 of the ASP. , to send a fault notification.

FIG. 3 shows a configuration example of the template store 124. As shown in FIG.

The template store 124 has service templates for each ASP. A service template may exist for each virtual system type instead of or in addition to each ASP. A virtual system type may be defined by one or more attributes, such as the usage of the virtual system.

According to the example of FIG. 3, each column indicates the service template for the ASP corresponding to that column. A service template is a template of virtual system requirements. Virtual system requirements are divided into functional requirements and non-functional requirements. There may be multiple individual requirements (which may also be called "sub-requirements" or "partial requirements") for both functional and non-functional requirements. Individual requirements indicate functions or performance.

Each service template lists individual requirements that constitute the virtual system requirements requested by the ASP corresponding to the template. For example, according to the service template of the virtual system requirements requested by ASP1, an example is as follows.
- Virtual sensors are placed at sites (A, B, C, ..., N).
- The CPU performance, memory amount, and storage amount of VMs placed in the cloud are specified.
・The maximum communication bandwidth is 64 kb/s per sensor.
• Traffic characteristics are bursts of 256 kb per hour.
・The maximum number of simultaneously connected sensors is 10,000.
・Mobility is not required.
・There is a fully redundant configuration between the sensor and the VM.
・There will be no functional changes in the future.
・Even in the event of a failure, it is necessary to ensure the same level of operation as normal.
・Degraded operation is permitted in the event of a large-scale disaster.
・Transfer to alternate zone is necessary in case of cloud failure.
・Security measures are advanced.

At least some of the individual requirements indicated by such service templates can be set or changed by the ASP. The virtual system requirement itself indicated by the service template, or the virtual system requirement according to the combination of setting or change by the ASP and the service template, is the virtual system requirement associated with the virtual system construction request or the virtual system change request from the ASP system 301. be.

FIG. 4 shows a configuration example of the virtual resource store 111. As shown in FIG.

The virtual resource store 111 has virtual resources for each ISP. Virtual resources may exist for each individual infrastructure type instead of or in addition to each ISP.

According to the example of FIG. 4, each column indicates the virtual resource for the ISP corresponding to that column. In this example, virtual resource requirements (for example, functions) are listed for each ISP (for each individual infrastructure). In FIG. 4, for the sake of simplification of explanation, the description is for each individual infrastructure, but in reality, the description may be for each virtual resource instance that can be operated by the resource pool management system 100 . A virtual resource instance may be described with a service granularity such as a link between bases A and B or a VM in the cloud, or may be an entire sensor that spreads over a wide area or a network cut out from SD-WAN as a virtual resource instance. It can also be registered as Also, although not shown in FIG. 4, the requirements have attributes of functional requirements or non-functional requirements as in FIG.

FIG. 5 shows a configuration example of the configuration store 123 .

The configuration store 123 has virtual system configuration information for each virtual system. According to the example of FIG. 5, each column indicates virtual system configuration information (which may include connection information) for the virtual system corresponding to that column. For each virtual system, the virtual system configuration information may be an enumeration of virtual resources that make up the virtual system. The virtual resources listed here may actually be virtual resource instances exclusively or statistically available to the virtual system.

According to the store configurations shown in FIGS. 3 to 5, all of the virtual system requirements of service templates, the requirements of registered virtual resources, and the virtual system requirements of configured virtual systems are , specifically, all individual requirement items and a requirement value for each individual requirement item. For example, service templates, virtual resources, and virtual system configuration information may all have common N individual requirements (where N is an integer equal to or greater than 2). In this case, if the number of individual requirements belonging to functional requirements is n, the number of individual requirements belonging to non-functional requirements may be (Nn).

Also, the individual requirement items in the stores 111, 124 and 123 do not necessarily have to match. For example, the individual requirement item "end system specification" in the service template may correspond to a combination of the individual requirement items "end system function" and "end system location" in the virtual resource or virtual system configuration information.

Moreover, when there are virtual resources of the same type in a plurality of virtual systems, any of the following may be employed.
- The virtual resources of the same type are a plurality of virtual resources that are logically different by being logically (for example, temporally) distinguished. Each of the plurality of virtual resources is a dedicated resource of the virtual system containing the virtual resource.
- The virtual resource of the same type is treated as one virtual resource shared by a plurality of virtual systems.

FIG. 6 shows the overall flow of processing including virtual system construction processing.

<Virtual resource registration (S301, S311 and S312)>

The ISP system 221 registers virtual resources corresponding to the individual infrastructures 211 under the control of the ISP system 221 in the virtual resource store 111 . As an example, the following processing is performed.

The ISP system 221A virtualizes the physical resources of the sensor net 211A (S301A) and issues a request to the resource pool management system 100 to register the virtualized resources (that is, virtual resources) in the resource pool 110. FIG. Also, the ISP system 221B virtualizes the physical resources of the radio access network 211B (S301B), and sends a request to the resource pool management system 100 to register the virtualized resources (that is, virtual resources) in the resource pool 110. put out. Upon receiving such a request, the resource pool management system 100 secures virtual resources for each requested individual infrastructure (S311), and registers the secured virtual resources in the virtual resource store 111 ( S312).

<Preparation of Service Template (S321)>

A service template is registered in the template store 124 (S321).

<Virtual System Construction Processing (S331 to S344)>

The ASP system 301 generates virtual system requirements (S331), selects a service template that meets the requirements from the template store 124 (S332), and provides the virtual system requirements to the resource pool management system 100 based on the service template. Notify (S333). For example, at S331, some individual requirements of the virtual system requirements may be generated. In S332, the service template found using the generated individual requirement as a key may be selected. The virtual system requirements notified in S333 may be the virtual system requirements of the selected service template themselves, or the virtual system requirements as a combination of the virtual system requirements of the service template and the individual requirements generated by the ASP. .

The matching unit 121 of the resource pool management system 100 receives the requirement notification (virtual system requirement notification) and checks the syntax of the requirement notification (S334). If there is no inconsistency in the syntax, the matching unit 121 divides the virtual system requirements indicated by the requirement notification into individual requirements for individual infrastructures (S335). Based on the divided individual requirements, the matching unit 121 extracts the virtual resource from the virtual resource store 111 if there is a virtual resource having a requirement that matches the individual requirement for each individual infrastructure (S336). The matching unit 121 synthesizes (logically connects) the extracted virtual resources to calculate the virtual system requirements (for example, functions and performance) of the virtual system as a set of the extracted virtual resources. The difference between the (calculated virtual system requirements) and the required requirements (virtual system requirements indicated by the requirement notification) is calculated (S337). The matching unit 121 notifies the ASP system 301, which is the transmission source of the requirement notification, of the calculated difference, and the ASP system 301 receives the difference notification (notification indicating the difference between the calculation requirement and the request requirement) (S338). ). In S337, for example, both the calculation requirement and the requirement have common N individual requirement items, and the difference in the requirement value may be calculated for each of the N individual requirement items. The calculated difference (the difference indicated by the difference notification) may be a set (for example, a list) of N requirement value differences respectively corresponding to the N individual requirement items.

The user (ASP) of the ASP system 301 determines whether the difference indicated by the difference notification is acceptable (S339). If acceptable, the ASP system 301 issues a virtual system construction request to the resource pool management system 100 . If not acceptable, the process returns to S3301. In other words, the requirements change.

In the resource pool management system 100 that has received the virtual system construction request, the configuration control unit 122 generates virtual system configuration information for the virtual system having the computational requirements (virtual system requirements calculated in S337) (S341). The system configuration information is registered in the configuration store 123 (S342).

In the resource pool management system 100, based on the registered virtual system configuration information, the virtual resource control unit 113 controls the secured virtual resources for each ISP system 221 corresponding to the virtual resources constituting the virtual system having the computational requirements. is activated (S343).

The ISP system 221 that has received the instruction allocates physical resources corresponding to all or part of the reserved virtual resources in response to the instruction (S344). For example, ISP system 221A allocates physical resources for sensor net 211A (S344A). Also, for example, the ISP system 221B allocates physical resources for the radio access network 211B (S341B).

According to this embodiment, by logically combining virtual resources registered in the resource pool 110 from individual infrastructures, a virtual system (for example, an EtoE virtual system) can be constructed without directly operating individual infrastructures. is possible. Furthermore, since it is possible to coordinate the requirements of the implemented virtual system with the ASP requesting the virtual system, efficient use of the physical resources of each individual infrastructure is possible.

Any one of the following may be adopted in place of at least part of S338 to S340.
- For at least one ASP, a policy regarding an allowable difference is registered in the resource pool management system 100 in advance. If the difference calculated in S337 for the ASP corresponds to the allowable difference indicated by the policy, the system construction unit 50 generates virtual system configuration information without issuing a difference notification.
- For at least one ASP, a policy regarding acceptable differences is registered in advance in the ASP system 301 of the ASP. For the ASP, in S339, the ASP system 301 determines whether the difference indicated by the difference notification corresponds to the allowable difference indicated by the policy.

Securing the virtual resource in S311 may correspond to reserving to be a component of the virtual system. All or part of the secured virtual resources (for example, part of the performance of the virtual resources) is assigned to the virtual system. If a portion of the reserved virtual resource is allocated, the rest of the virtual resource remains reserved. For each virtual resource, information regarding reservation may be registered for each virtual resource in the virtual resource store 111, for example.

In calculating the virtual system requirements of a virtual system, logical connections between the virtual resources that make up the virtual system may be made. For example, a logical connection between virtual resources A and B may be defined as a connection between virtual resources and a connection direction, such as a connection from virtual resource A to virtual resource B. FIG. An EtoE virtual system is configured by logically connecting a plurality of virtual resources on a cascade.

An example of details of S343-S340 (that is, virtual system deployment) may be as follows. Take one virtual system as an example. The virtual resource control unit 113 identifies each virtual resource that configures the virtual system from the virtual system configuration information of the virtual system. For each identified virtual resource, the virtual resource control unit 113 identifies the ISP system 221 corresponding to the virtual resource (for example, the ISP system 221 corresponding to the virtual resource is identified by referring to the virtual resource store 111). specified), and issues an activation instruction for the virtual resource to the specified ISP system 221 . The instruction includes, for example, the required requirements (for example, function and performance) and which individual infrastructure and link function are to be used for connection (for example, the ISP system 221 corresponding to the linked individual infrastructure). Various parameters such as an IP address and contents of instructions to the IP system are associated. According to the instruction, the ISP system 221 activates the individual infrastructure. The deployment of the virtual system is completed when the ISP system 221 corresponding to each virtual resource that constitutes the virtual system performs activation in response to the above-described instruction to the ISP system 221. . An individual infrastructure part corresponding to the virtual resource is mapped to the virtual resource as a component of the virtual system.

FIG. 7 shows the flow of virtual system change processing.

The ASP system 301 activates the modification of the virtual system requirements of the virtual system in use (S431), and selects the selected service template for building the virtual system in use (S432). The ASP system 301 issues to the resource pool management system 100 a requirement change request for changing the virtual system requirements (virtual system requirements of the virtual system in use) based on the service template (S433). The requirement change request may include only the changed portion (individual requirement after change) of the virtual system requirements of the virtual system in use, or may include the entire virtual system requirements including the changed portion. Also, changes in virtual system requirements may be made without selecting a service template. Also, the virtual system requirements of the service template selected in constructing the virtual system in use may be updated to the changed virtual system requirements.

Upon receiving the requirement change request, the matching unit 121 of the resource pool management system 100 checks the syntax of the change content indicated by the requirement change request (S434). If there is no problem with the syntax, S435 to S444 similar to S335 to S344 are performed.

That is, the matching unit 121 divides the requirements indicated by the change content into requirements for individual infrastructures corresponding to the change content (S435), and extracts the virtual resource to be changed from the virtual resource store 111 for each individual infrastructure. (S436). The matching unit 121 calculates the difference between the calculation requirement, which is the virtual system requirement of the virtual system synthesized by the extracted virtual resources, and the requirement, which is the virtual system requirement corresponding to the requirement change request (S437), and A difference notification indicating the calculated difference is sent to the ASP system 301 that sent the request. The ASP system 301 receives the difference notification (S438). The ASP determines whether or not the difference indicated by the difference notification can be accepted (S439). If acceptable, ASP system 301 issues a virtual system change request to resource pool management system 100 . If not acceptable, the process returns to S431.

Upon receiving the virtual system change request, the configuration control unit 122 of the resource pool management system 100 generates (for example, changes) virtual system configuration information (S441) and registers the virtual system configuration information in the configuration store 123 (S442). Based on the registered virtual system configuration information, the virtual resource control unit 113 issues a change request for the corresponding virtual resource to the ISP system 221 of the individual infrastructure corresponding to the change location (S443).

The ISP system 221 that has received the virtual resource change request changes the allocation of physical resources based on the change request (S444). In the example of FIG. 7, since the change target is the radio access network 211B, a virtual resource change request is transmitted to the ISP system 221B. The details of specifying the ISP system 221 corresponding to the virtual resource to be changed and the request (instruction) to the ISP system 221 may be the same as in the virtual system construction process. For example, the virtual resource change request includes parameters such as post-change requirements (for example, performance), and the ISP system 221 changes allocation of physical resources based on the parameters.

According to the virtual system change processing, in response to a virtual system change request from the ASP system 301, it is possible to perform realization and to adjust the requirements by logically manipulating the virtual resources registered on the resource pool 110. Rapid virtual system changes are possible because there is no need to coordinate with individual infrastructures.

FIG. 8 shows the flow of failure handling processing.

Assume that an example of a failed individual infrastructure is radio access network 211B. In this case, the ISP system 221B issues a virtual resource failure notification to the resource pool management system 100 (S501).

The matching unit 121 of the resource pool management system 100 receives the notification (S502), and registers the failure of the virtual resource (virtual resource of the radio access network) specified from the notification in the virtual resource store 111, for example (S503). ). The matching unit 121 uses each management unit 112 to extract virtual systems, virtual resources, and ASPs (users) affected by the failure of the radio access network (S504). An example of an extracted virtual system is a virtual system containing virtual resources corresponding to a radio access network. The extracted virtual resource is a virtual resource logically connected to the virtual resource corresponding to the radio access network in the virtual system. An example of the extracted ASP is the ASP corresponding to the extracted virtual system (for example, the ASP corresponding to the service template selected in constructing the virtual system).

The matching unit 121 notifies the configuration control unit 122 of the ASP system 301 of the ASP extracted in S504 and the failure information including information on the extracted virtual system and virtual resource. The configuration control unit 122 issues a fault notification including the fault information to the ASP system 301 (S505).

The ASP system 301 that received the failure notification receives the failure notification (S506) and displays the failure information indicated by this failure notification. The ASP determines whether the difference between the requirements before and after the failure is acceptable based on the displayed failure information (S507). If acceptable, processing terminates (eg, awaits another failure notification). If unacceptable, the ASP system 301 changes the virtual system requirements (S508), selects a service template corresponding to the virtual system in use (S509), and sends a requirement change request to the resource pool management system 100. is issued (S510). S508 to S510 may be the same as S431 to S433. At least one of the following may be performed instead of at least part of S502 to S507.
If the requirement difference before and after the failure corresponds to the allowable difference indicated by the policy regarding the allowable difference, then S507:Y is automatically set; otherwise, S507:N is automatically set.
• At S504, alternative virtual resources for the failed virtual release may be extracted. A substitute virtual resource is a virtual resource whose requirements are within a certain range from the requirements of the failed virtual release. The failure information indicated by the failure notification includes information indicating a substitute virtual resource in addition to information indicating a virtual resource in which a failure has occurred. Therefore, the display of the failure information indicated by the failure notification is a proposal for the alternative virtual resource.

After the requirement change request is transmitted, S511 to S521 similar to S434 to S444 are performed.

According to the failure handling process, since the resource pool management system 100 centrally grasps the virtual systems that use the virtual resources registered from each individual infrastructure, the range of influence of individual infrastructure failures and alternative virtual Resource proposals can be realized quickly and efficiently. Even if the system construction unit 50 receives a failure notification from the ISP system 221, it may not issue the failure notification to the ASP system 301 in any of the following cases (specifically, for example, Between S503 and S504, it may be determined whether or not it is necessary to issue a failure notification to the ASP system, and S504 may be performed when the result of the determination is true).
- The notified failure falls under a pre-specified requirement that does not affect the failure (for example, one or more prescribed requirements belonging to the day function requirement).
- The difference in the virtual system requirements before and after the failure is within a predefined allowable range.

Example 2 will be described. At that time, the points of difference from the first embodiment will be mainly described, and the explanations of the points in common with the first embodiment will be omitted or simplified.

In this embodiment, the requirements, calculation requirements, and requirements of virtual resources are all represented by vectors. Therefore, it is expected that virtual systems can be constructed and changed more quickly and efficiently. The vectors may be pre-registered in at least one of stores 111, 124 and 123, or may be calculated each time processing is performed.

A virtual system requirement is composed of a plurality of individual requirements (see, for example, FIG. 3), and a requirement vector representing such a plurality of individual requirements is a multidimensional vector. Quantities in each dimension have different units of measure depending on requirements, and may take continuous numerical values or discrete characteristic values. FIG. 9A shows an n-dimensional requirement vector 801 as an example of representation of n individual requirements belonging to functionality requirements among virtual system requirements.

In the case of qualitative requirements such as non-functional requirements, the qualitative functions are also discretely quantified by a predetermined procedure. FIG. 9B is an example of representation of virtual system requirements composed of N individual requirements, which are n individual requirements belonging to functional requirements and (N−n) individual requirements belonging to non-functional requirements. Requirement vector 802 is shown. FIG. 9B shows an example in which a non-functional requirement (here, the presence or absence of doubling) is represented by a discrete numerical value of 1 or 0 and made an independent dimension of the requirement vector 802 . It is also possible to weight between dimensions considering various conditions in demand and supply of each functionality and functionality requirements. All of these are logically implemented in registering or synthesizing virtual resources in the resource pool 110 and do not directly affect the resource virtualization process for each individual infrastructure 211 .

The requirements (virtual system requirements requested from the ASP system) are divided into multiple individual requirements to multiple individual infrastructures. Specifically, for example, the matching unit 121 calculates an N-dimensional requirement vector as an expression of requirements, and divides the N-dimensional requirement vector into a plurality of individual requirement vectors corresponding to a plurality of individual infrastructures. FIG. 10 shows one individual requirement vector 70 corresponding to one individual infrastructure (“target individual infrastructure” in the description of FIG. 10). Individual requirement vector 70 is a composite vector. According to the example of FIG. 10, it is as follows.

Assume that the target individual infrastructure has physical resources such as nodes A through D and links 811A through 811E. Assume that virtual resources corresponding to these physical resources are registered in the resource pool 110 . Suppose that a virtual resource corresponding to a route from node A to node D is required according to the requirements. Here, as an example of a route from node A to node D, assume that a virtual resource corresponding to link 811A between node A and node B and a virtual resource corresponding to link 811D between node B and node D are extracted. . The virtual resource requirement corresponding to link 811A is represented by vector 821A, and the virtual resource requirement corresponding to link 811D is represented by vector 821D. In this case, the individual requirement vector 70 for the target individual infrastructure among the requirements is a composite vector of the vectors 821A and 821D. For example, when a failure occurs in node B, the combined vector of the vectors corresponding to the link 811B between node A and node C and the link 811E between node C and node D is the individual requirement vector 70 for the target individual infrastructure. may be assumed.

According to the example in Fig. 10, it is possible to treat a virtual system defined by various individual requirements, both functional and non-functional, as an object that can be managed and operated in an integrated manner as a synthesis of requirement vectors. Become. Also, for each individual infrastructure, it is possible to hide the virtual resource configuration corresponding to the individual infrastructure and handle the virtual resource as a single requirement vector corresponding to the individual infrastructure.

The system construction unit 50 executes the processing described with reference to FIG. 10 for the virtual resources registered for each individual infrastructure, so that each of the individual infrastructures 211A to 211E as illustrated in FIG. Individual requirement vectors 70A-70E are obtained. The system construction unit 50 obtains a vector 820 of EtoE virtual system requirements from the sensor 2112 to the VM 2152 by synthesizing the individual requirement vectors 70A to 70E.

However, it is not always possible to obtain a virtual system (virtual system composed of extracted virtual resources) having a computational requirement in which a vector that completely matches the requirement vector 820 can be obtained. According to the example of FIG. 12, the system construction unit 50 obtains a calculation requirement vector 830 by synthesizing individual requirement vectors 831A to 831E of the virtual resources extracted from the individual infrastructures 211A to 211E. Vector of computational requirements 830 may differ from vector of requirements 820 . In such a case, the system construction unit 50 calculates the difference 837 between the vectors 820 and 830 of both. An example of difference 837 is the vector difference between requirement vector 830 and requirement vector 820 . Alternatively, the relationship between vectors 820 and 830 could be used as a difference metric, eg a scalar product or a vector product could be employed.

According to the example of FIG. 12, it is possible to express the difference between the requirements and the calculation requirements (implementation specifications) by performing various operations between the requirement vectors defined as logical metrics of the virtual system. , so that the feasible virtual system requirements for the requested virtual system requirements can be easily communicated to the ASP.

The system construction unit 50 obtains the individual requirement vector 70 for each individual infrastructure by decomposing the requirement vector 820, and using the individual requirement vector 70 as a key, the difference from the individual requirement vector 70 is within a certain range. You may extract the virtual resource corresponding to the requirement which becomes a vector that fits within.

FIG. 13 shows an example of a virtual system implemented as a synthesis of requirement vectors in which some of the virtual resources provided by individual infrastructures are unavailable.

According to the example of FIG. 13, bypassing to the Internet 211X when the VPN 211D fails is proposed to the ASP using the virtual system including the virtual resource of the VPN 211D. The Internet 211X is also an example of individual infrastructure, and virtual resources of the Internet 211X are also registered in the virtual resource store 111. FIG.

In the example of FIG. 13, the virtual resource corresponding to the individual requirement vector 841D cannot be used due to the failure of the VPN 211D. virtual resources on the WAN 211C and virtual resources on the cloud 211E) are also unavailable in the EtoE virtual system.

In this case, the system construction unit 50 converts part of the requirement vector 840 (requirement vector as a representation of the virtual system requirements of the virtual system in use) partly composed of the individual requirement vectors 841C to 841E to the alternative virtual resource (Internet 211X ) and a requirement vector 841E' of the virtual resource of the cloud 211E connected to the Internet 211X. Then, the system construction unit 50 substitutes the combined vector for the requirement vectors 841C to 841E described above, and calculates the requirement vector of the virtual system requirements of the virtual system after the substitution.

According to the example of FIG. 13, the alternative means when a failure occurs in an individual infrastructure is set as an alternative requirement vector in the individual infrastructure, or an alternative requirement vector including individual infrastructures connected to the failed individual infrastructure. Since it can be defined, quick and efficient fault handling becomes possible.

The above is the description of the second embodiment. For example, regarding an EtoE virtual system, if there are p end systems, p requirement vectors may be generated, or a combined vector of p requirement vectors may be generated.

Examples 1 and 2 described above can be summarized, for example, as follows. It should be noted that the following summary may include matters not included in the above description.

The resource pool 110 includes, as virtual resources, data indicating one or more requirements for realizing each individual infrastructure 211 provided by a plurality of ISPs. The system construction unit 50 identifies from the resource pool 110 two or more virtual resources that serve as computational requirements whose difference from the required requirements is within an allowable range. The difference is zero if the requirements and calculation requirements (implementation requirements) match. The system construction unit 50 constructs a virtual system composed of the two or more virtual resources, and for each of the two or more virtual resources, an ISP system 221 of an ISP that provides an individual infrastructure corresponding to the virtual resource. and instructs the ISP system 221 to activate the individual infrastructure resource corresponding to the virtual resource.

Plurality of individual infrastructures 211 includes one or more networks (eg, sensor sets, radio access networks, etc.). In general, involving networks in two or more separate infrastructures for the provision of application services is more burdensome for ASPs (especially two or more ISPs provided by two or more ISPs for the provision of application services). However, since the network is managed as a resource pool, the burden on the ASP is reduced. For example, in order to connect the sensor 2112 of the sensor net 211A to the VM 2152 of the cloud 211E, the ASP has to place an order for inter-base connection to each of the ISPs of the radio access network 211B and the SD-WAN 211C. can be eliminated.

The network is a particularly big bottleneck in such cases, as the services that provide connectivity are geographically dependent. However, since networks are generally a so-called facility industry that requires a large amount of time and money to complete, they are expected to be used for a relatively long period of time, and there are many individual requirements, and it takes a relatively long time before they can be used. time consuming. On the other hand, application services generally have a shorter product life cycle than the network product life cycle, and are desired to be provided quickly when needed.

As in the first and second embodiments described above, multiple infrastructures corresponding to multiple virtual resources registered in the resource pool 110 include networks, so two or more infrastructures for providing application services are included. Rapid provision of application services is possible even if the network is contained in a separate infrastructure.

It should be noted that it is difficult for networks to define their requirements as clear functional requirements, unlike storage and CPU.

Therefore, regarding a network virtual resource, which is a virtual resource for a network, the data as the network virtual resource indicates multiple requirements, and the multiple requirements include one or more individual requirements belonging to the functional requirements, as well as non- Contains one or more individual requirements belonging to the functionality requirements.

Networks also have a particularly large number of individual requirements belonging to non-functional requirements and hence a large spectrum of requirements.

Therefore, the system construction unit 50 sets the requirement (consisting of M individual requirements) as an M-dimensional requirement vector and the calculation requirement (consisting of N individual requirements) as an N-dimensional requirement vector. Both M and N are integers of 2 or more. M=N or M≠N. The system construction unit 50 calculates a vector difference as a difference between the M-dimensional requirement vector and the N-dimensional requirement vector. If the vector difference (or the requirement difference list specified from the vector difference (list of requirement value differences for each requirement item) is within a predetermined range, or if approved by the ASP, the above-mentioned allowable It corresponds to the difference in the range.

For each domain (eg ISP or individual infrastructure) a multi-dimensional individual request vector is generated according to the number of requirements for that domain. In an EtoE virtual system, a composite vector of two or more individual requirement vectors is the requirement vector of the virtual system. Depending on the usage of virtual resources, it is often possible to configure a virtual system with computational requirements that differ from the requirements (computational requirements (implementation requirements) that are the requirement vector of the requirements and the requirement vector with the difference). However, if the difference is within the allowable range, the difference is allowed.

When receiving a request to change part of the conditions of the virtual system in use, the system construction unit 50 uses one or more individual requirement vectors corresponding to the part of the conditions after the change to change the conditions after the change. A requirement vector as an expression may be computed. If the difference between the calculated requirement vector and the requirement vector representing the requirement corresponding to the post-change condition is within an allowable range, the system construction unit 50 You may change the virtual resources involved in In this way, the virtual system configuration can be changed using the requirement vector. Note that the virtual system configuration change may be performed by a method other than the method using the requirement vector.

When the system construction unit 50 receives a notification of a failure of an individual infrastructure corresponding to at least one virtual resource among two or more virtual resources that configure the virtual system in use, the system construction unit 50 receives the notification of the failure of the individual infrastructure. Replacement virtual resources may be identified for one or more virtual resources (eg, virtual resources corresponding to individual failed infrastructures and virtual releases that are logically connected to the virtual resources). The system construction unit 50 selects a virtual resource having a requirement corresponding to an individual requirement vector whose difference from one or more individual requirement vectors corresponding to the requirements of one or more virtual resources affected by the failure is within an allowable range. Certain alternate virtual resources may be identified. The system construction unit 50 uses the individual requirement vector corresponding to the requirements of the alternative virtual resource to create the requirement vector of the virtual system in which the alternative virtual resource is adopted in place of one or more virtual resources affected by the failure. can be calculated. If the difference between the calculated requirement vector and the requirement vector representing the condition M is within an allowable range, the system construction unit 50 substitutes one or more virtual resources of the virtual system in use. You can replace it with a resource. In this way, the requirement vector can be used to identify alternative virtual resources and to replace virtual resources. The identification of the alternative virtual resource and the replacement of the virtual resource may be performed by a method other than the method using the requirement vector.

When the system construction unit 50 receives a notification of a failure of an individual infrastructure corresponding to at least one virtual resource among two or more virtual resources that configure the virtual system in use, the system construction unit 50 receives the notification of the failure of the individual infrastructure. One or more individual requirement vectors corresponding to the post-failure requirements of one or more virtual resources may be used to calculate a requirement vector of the post-failure virtual system requirements of the virtual system in use. If the difference between the calculated requirement vector and the requirement vector representing the condition M is within the allowable range, the system construction unit 50 may continue to use the virtual system in use. Using the requirement vector in this manner, the difference in virtual system requirements before and after the failure can be calculated. Note that the difference between the virtual system requirements before and after the failure may be obtained by a method other than the method using the requirement vector.

In the above description, the requirement vector of the virtual system requirements is calculated as a synthesis of the individual requirement vectors of the virtual resources registered for each individual infrastructure 211 . However, this method is not limited to building (or changing) a single virtual system, and can be applied even when building (or changing) a plurality of virtual systems at the same time. In that case, a total matching calculation such as synthesizing the difference between multiple requirement virtual system requirement vectors and the realization requirement vector, or synthesizing the requirement virtual system requirement vector itself and comparing the difference with the synthesis of the realization requirement vector is performed. It is possible. According to this method, allocation of realization virtual systems (virtual systems composed of extracted virtual resources) corresponding to a plurality of virtual system construction requests (or a plurality of virtual system change requests) can be performed efficiently over the entire resource pool. It is possible to execute it as a typical matching.

In the above description, virtual resource allocation (virtual system deployment) is performed with a virtual system construction request (or a virtual system change request) from the ASP system 301 as a trigger. Alternatively or in addition, however, the present invention can be similarly applied to a case where a virtual system demand from an ASP is predicted in advance and a virtual resource registered in a resource pool is reserved. Since virtual resource reservation based on such virtual system demand prediction can be logically realized on a resource pool, it is possible to quickly respond to a virtual system construction request (or virtual system change request) from an ASP, or to make a time reservation. It can also respond to a type virtual system construction request (or a virtual system change request). Furthermore, it is also possible to perform demand forecasting while looking at trends in virtual system construction requests (or virtual system change requests) from ASPs by performing calculations on virtually operable logical instances called requirement vectors. By combining such a demand forecast with the technique of the above-described embodiment for synthesizing a plurality of virtual system construction requests (or virtual system change requests), it is possible to ensure total demand forecast accuracy.

According to at least one embodiment, quickly and efficiently build multiple types of virtual systems consisting of multiple individual infrastructures with different functions and administrators so as to match the virtual system requirements requested by ASPs. becomes possible.

Also, according to at least one embodiment, a virtual system having the requirements (e.g., function, performance, or service area) demanded by an ASP can be created without requiring operations corresponding to each individual infrastructure (e.g., It is possible to build a virtual system quickly and easily without having to contact an ISP individually).

In addition, in configuring and operating an EtoE virtual system by interconnecting a wide variety of individual infrastructures, the ISP that operates the individual infrastructure must understand the virtual system requirements from individual ASPs and communicate with all constituent members. It frees you from the difficult task of aligning requirements with each other and allows you to focus on managing the individual infrastructures that you manage.

Although several embodiments have been described above, these are examples for explaining the present invention, and are not meant to limit the scope of the present invention only to these embodiments. The invention can also be implemented in various other forms.

100: Resource Pool Management System

Claims (18)

A resource pool that contains, as virtual resources, data indicating one or more requirements including one or more functions that realize each individual infrastructure for each of multiple individual infrastructures provided by multiple ISPs (Infrastructure Service Providers). and,
identifying from the resource pool two or more virtual resources having two or more requirements that are within an allowable range of difference from two or more requirements required by an ASP (Application Service Provider) system for execution of an application program; a system construction unit that constructs a virtual system that is a logical connection of the two or more virtual resources and that is a system used to execute the application program;
with
In building the virtual system, the system construction unit identifies, for each of the two or more virtual resources, an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and provides the ISP system with the Directs the activation of individual infrastructure resources corresponding to virtual resources,
the plurality of individual infrastructures includes one or more networks;
for each of one or more network virtual resources that are one or more virtual resources for the one or more networks;
The data as the network virtual resource indicates multiple requirements,
The multiple requirements include one or more requirements belonging to non-functional requirements in addition to one or more requirements belonging to functional requirements,
Resource pool management system. The two or more conditions are M conditions (M is an integer of 2 or more),
The system construction unit defines the M conditions as an M-dimensional requirement vector, and the N requirements corresponding to the M conditions as an N-dimensional requirement vector (N is an integer of 2 or more),
The difference is a vector difference as a difference between the M-dimensional requirement vector and the N-dimensional requirement vector,
The resource pool management system according to claim 1 . When the request for the condition M is received from the ASP system, the system construction unit calculates the vector difference and notifies the ASP system of the calculated vector difference,
the acceptable difference is a vector difference approved from the ASP system;
3. A resource pool management system according to claim 2 . The system construction unit sets, for each of the two or more virtual resources, a requirement corresponding to the condition M among the requirements of the virtual resource as an individual requirement vector,
The N-dimensional requirement vector is a composite vector of two or more individual requirement vectors respectively corresponding to the two or more virtual resources,
4. A resource pool management system according to claim 3 . When the system construction unit receives a request to change the conditions of a part of the virtual system in use,
calculating a requirement vector as an expression of the post-change conditions using one or more individual requirement vectors corresponding to some of the post-change conditions;
If the difference between the calculated requirement vector and the requirement vector representing the requirement corresponding to the post-change condition is within an allowable range, the virtual resource related to the post-change condition is selected from the virtual system in use. change,
5. A resource pool management system according to claim 4 . When the system construction unit receives a notification of a failure of an individual infrastructure corresponding to at least one virtual resource among two or more virtual resources that constitute the virtual system in use,
Identify an alternative virtual resource that is a virtual resource having requirements corresponding to individual requirement vectors whose difference from one or more individual requirement vectors corresponding to the requirements of one or more virtual resources affected by the failure is within an allowable range. death,
calculating a requirement vector of a virtual system in which the alternative virtual resource is adopted in place of one or more virtual resources affected by the failure, using an individual requirement vector corresponding to the requirements of the alternative virtual resource;
If the difference between the calculated requirement vector and the requirement vector as an expression of the condition of M is within an allowable range, the one or more virtual resources of the virtual system in use are assigned to the alternative virtual resource. replace,
5. A resource pool management system according to claim 4 . When the system construction unit receives a notification of a failure of an individual infrastructure corresponding to at least one virtual resource among two or more virtual resources that constitute the virtual system in use,
Using one or more individual requirement vectors corresponding to the post-failure requirements of one or more virtual resources affected by the failure, create a requirement vector of post-failure virtual system requirements of the virtual system in use. calculate,
if the difference between the calculated requirement vector and the requirement vector representing the condition of M is within an allowable range, continuing to use the virtual system in use;
5. A resource pool management system according to claim 4 . A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). and,
Identifying from the resource pool two or more virtual resources having two or more requirements within an allowable range of difference from two or more requirements required by an ASP (Application Service Provider) system for execution of an application program; a system construction unit that constructs a virtual system that is a logical connection of the two or more virtual resources and that is a system used to execute the application program;
with
In building the virtual system, the system construction unit identifies, for each of the two or more virtual resources, an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and provides the ISP system with the Directs the activation of individual infrastructure resources corresponding to virtual resources,
When the request for the two or more conditions is received from the ASP system, the system construction unit calculates the difference and notifies the ASP system of the calculated difference,
the acceptable difference is an approved difference from the ASP system;
Resource pool management system. A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). and,
Identifying from the resource pool two or more virtual resources having two or more requirements within an allowable range of difference from two or more requirements required by an ASP (Application Service Provider) system for execution of an application program; a system construction unit that constructs a virtual system that is a logical connection of the two or more virtual resources and that is a system used to execute the application program;
with
In building the virtual system, the system construction unit identifies, for each of the two or more virtual resources, an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and provides the ISP system with the Directs the activation of individual infrastructure resources corresponding to virtual resources,
When the system construction unit receives a request to change a part of the conditions of the virtual system in use, if the difference between the conditions after the change and the requirements corresponding to the conditions after the change is within an allowable range, changing a virtual resource related to the condition after the change in the virtual system in use;
The resource pool management system according to claim 1. A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). and,
Identifying from the resource pool two or more virtual resources having two or more requirements within an allowable range of difference from two or more requirements required by an ASP (Application Service Provider) system for execution of an application program; a system construction unit that constructs a virtual system that is a logical connection of the two or more virtual resources and that is a system used to execute the application program;
with
In building the virtual system, the system construction unit identifies, for each of the two or more virtual resources, an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and provides the ISP system with the Directs the activation of individual infrastructure resources corresponding to virtual resources,
When the system construction unit receives a notification of a failure of an individual infrastructure corresponding to at least one virtual resource among two or more virtual resources that constitute the virtual system in use,
identifying alternative virtual resources for one or more virtual resources affected by the failure;
If the difference between the requirements of the virtual system in which the alternative virtual resource is employed in place of the one or more virtual resources affected by the failure and the requirement vector as an expression of the two or more conditions is within an acceptable range. replacing the one or more virtual resources of the active virtual system with the alternate virtual resources;
Resource pool management system. A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). and,
Identifying from the resource pool two or more virtual resources having two or more requirements within an allowable range of difference from two or more requirements required by an ASP (Application Service Provider) system for execution of an application program; a system construction unit that constructs a virtual system that is a logical connection of the two or more virtual resources and that is a system used to execute the application program;
with
In building the virtual system, the system construction unit identifies, for each of the two or more virtual resources, an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and provides the ISP system with the Directs the activation of individual infrastructure resources corresponding to virtual resources,
When the system construction unit receives a notification of a failure of an individual infrastructure corresponding to at least one virtual resource among two or more virtual resources that constitute the virtual system in use,
calculating post-failure virtual system requirements of the in-service virtual system using the post-failure requirements of one or more virtual resources affected by the failure;
if the difference between the calculated virtual system requirements and the two or more conditions is within an allowable range, continuing to use the virtual system in use;
Resource pool management system. A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). and,
Identifying from the resource pool two or more virtual resources having two or more requirements within an allowable range of difference from two or more requirements required by an ASP (Application Service Provider) system for execution of an application program; a system construction unit that constructs a virtual system that is a logical connection of the two or more virtual resources and that is a system used to execute the application program;
with
In building the virtual system, the system construction unit identifies, for each of the two or more virtual resources, an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and provides the ISP system with the Directs the activation of individual infrastructure resources corresponding to virtual resources,
The system construction unit provides the ASP system with a service template corresponding to the input of the ASP system among a plurality of service templates each being a template of a plurality of conditions,
The two or more conditions required by the ASP system are conditions entered using the service template.
Resource pool management system. A resource pool management method performed by a resource pool management system, comprising:
A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). from, identifying two or more virtual resources having two or more requirements that are within an allowable difference from two or more requirements required by an ASP (Application Service Provider) system for execution of the application program;
constructing a virtual system, which is a system that is a logical connection of the two or more virtual resources and is used to execute the application program, and in constructing the virtual system, for each of the two or more virtual resources, identifying an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and instructing the ISP system to activate the individual infrastructure resource corresponding to the virtual resource;
has
the plurality of individual infrastructures includes one or more networks;
for each of one or more network virtual resources that is one or more virtual resources for the one or more networks;
The data as the network virtual resource indicates multiple requirements,
The multiple requirements include one or more requirements belonging to non-functional requirements in addition to one or more requirements belonging to functional requirements,
Resource pool management method. A resource pool management method performed by a resource pool management system, comprising:
A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). from, identifying two or more virtual resources having two or more requirements that are within an allowable difference from two or more requirements required by an ASP (Application Service Provider) system for execution of the application program;
constructing a virtual system, which is a system that is a logical connection of the two or more virtual resources and is used to execute the application program, and in constructing the virtual system, for each of the two or more virtual resources, identifying an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and instructing the ISP system to activate the individual infrastructure resource corresponding to the virtual resource;
has
further comprising the step of calculating the difference and notifying the calculated difference to the ASP system when a request for the two or more conditions is received from the ASP system;
the acceptable difference is an approved difference from the ASP system;
Resource pool management method. A resource pool management method performed by a resource pool management system, comprising:
A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). from, identifying two or more virtual resources having two or more requirements that are within an allowable difference from two or more requirements required by an ASP (Application Service Provider) system for execution of the application program;
constructing a virtual system, which is a system that is a logical connection of the two or more virtual resources and is used to execute the application program, and in constructing the virtual system, for each of the two or more virtual resources, identifying an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and instructing the ISP system to activate the individual infrastructure resource corresponding to the virtual resource;
has
When receiving a request to change some of the conditions of the virtual system in use, if the difference between the conditions after the change and the requirements corresponding to the conditions after the change is within the allowable range, the virtual system in use further comprising the step of changing the virtual resource associated with the changed condition of
Resource pool management method. A resource pool management method performed by a resource pool management system, comprising:
A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). from, identifying two or more virtual resources having two or more requirements that are within an allowable difference from two or more requirements required by an ASP (Application Service Provider) system for execution of the application program;
constructing a virtual system, which is a system that is a logical connection of the two or more virtual resources and is used to execute the application program, and in constructing the virtual system, for each of the two or more virtual resources, identifying an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and instructing the ISP system to activate the individual infrastructure resource corresponding to the virtual resource;
has
When receiving a notification of a failure of an individual infrastructure corresponding to at least one of the two or more virtual resources that make up the virtual system in use,
identifying alternative virtual resources for one or more virtual resources affected by the failure;
If the difference between the requirements of the virtual system in which the alternative virtual resource is employed in place of the one or more virtual resources affected by the failure and the requirement vector as an expression of the two or more conditions is within an acceptable range. and replacing the one or more virtual resources of the active virtual system with the alternate virtual resources.
Resource pool management method. A resource pool management method performed by a resource pool management system, comprising:
A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). from, identifying two or more virtual resources having two or more requirements that are within an allowable difference from two or more requirements required by an ASP (Application Service Provider) system for execution of the application program;
constructing a virtual system, which is a system that is a logical connection of the two or more virtual resources and is used to execute the application program, and in constructing the virtual system, for each of the two or more virtual resources, identifying an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and instructing the ISP system to activate the individual infrastructure resource corresponding to the virtual resource;
has
When receiving a notification of a failure of an individual infrastructure corresponding to at least one of the two or more virtual resources that make up the virtual system in use,
calculating post-failure virtual system requirements of the in-service virtual system using the post-failure requirements of one or more virtual resources affected by the failure;
further comprising continuing to use the virtual system in use if the difference between the calculated virtual system requirements and the two or more conditions is within an acceptable range;
Resource pool management method. A resource pool management method performed by a resource pool management system, comprising:
A resource pool containing, as virtual resources, data indicating one or more requirements including one or more functions for realizing each individual infrastructure provided by multiple ISPs (Infrastructure Service Providers). from, identifying two or more virtual resources having two or more requirements that are within an allowable difference from two or more requirements required by an ASP (Application Service Provider) system for execution of the application program;
constructing a virtual system, which is a system that is a logical connection of the two or more virtual resources and is used to execute the application program, and in constructing the virtual system, for each of the two or more virtual resources, identifying an ISP system of an ISP that provides an individual infrastructure corresponding to the virtual resource, and instructing the ISP system to activate the individual infrastructure resource corresponding to the virtual resource;
has
further comprising the step of providing the ASP system with a service template corresponding to the input of the ASP system among a plurality of service templates each being a template of a plurality of conditions;
The two or more conditions required by the ASP system are conditions entered using the service template.
Resource pool management method.

Images