JP2020140415A - Resource pool management system and method - Google Patents

Abstract

To quickly and efficiently construct a virtual system composed of multiple virtual resources corresponding to multiple individual infrastructures with different requirements and ISPs (Infrastructure Service Providers).SOLUTION: A resource pool management system 100 is arranged between an Application Service Provider (ASP) and an ISP in which a resource pool includes data as a virtual resource indicating one or more requirements including one or more functions to realize each of a plurality of individual infrastructures provided by a plurality of ISPs. The resource pool management system identifies two or more virtual resources from the resource pool on which a difference between two or more conditions required by the ASP for the execution of an application program is in an allowable range, and constructs a virtual system that is a logical connection between the two or more virtual resources to be used for the execution of application services.SELECTED DRAWING: Figure 1

Description

The present invention generally relates to the construction of a system used in the provision of application services.

For example, with the development of virtual computing resource providing services such as 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 such a plurality of types of virtual instances, and an application service provision form in a wide area using the virtual system is expanding. In the construction and operation of such a virtual system, a multi-tenant form in which a plurality of virtual systems are constructed on a limited number of physical systems and operated independently is generally assumed. Each independently operated virtual system is required to have the functions and performance required by the application service that uses it. Prior arts for constructing such a virtual system include, for example, Patent Documents 1 and 2.

Patent No. 5944870 Patent No. 6170237

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

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. It's coming. Heterogeneous systems are, for example, mobile access systems and sensor nets for collecting and controlling information from various sensors. Even if it is limited to one mobile access system, the methods are diversified. For example, the mobile session control method represented by LTE (Long Term Evolution) (registered trademark) and various methods of Low Power Wireless Access (LPWA) And WiFi etc. There are various methods for the sensor net depending on the sensor type, field and application. Furthermore, application service implementation forms are also diversifying in various system configurations such as microservices and serverless computing.

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

In this way, the conditions required by each application service for virtual systems (for example, conditions related to functions, performance, and service areas) will be met in the future in response to diversifying user needs and expansion of application areas in various industrial fields. It is expected to become more and more complicated.

A resource pool management system that intervenes between the ASP system and the ISP (Infrastructure Service Provider) system is constructed. The resource pool contains data indicating one or more requirements including one or more functions for realizing the individual infrastructure for each of the plurality of individual infrastructures provided by the plurality of ISPs as virtual resources. The resource pool management system identifies from the resource pool two or more virtual resources that have two or more requirements within which the difference from the two or more conditions required by the ASP system for the execution of the application program is acceptable. Build a virtual system that is a logical connection of the two or more virtual resources and is used to execute application services.

According to the present invention, it is composed of a plurality of virtual resources corresponding to a plurality of individual infrastructures having different requirements (for example, functions) and an administrator (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 build a virtual system with requirements.

The configuration of the entire system including the resource pool management system according to the first embodiment is shown. Shows some functions of the resource pool management system. An example of configuring the template store is shown. An example of configuring a virtual resource store is shown. A configuration example of the configuration store is shown. The flow of the entire process including the virtual system construction process is shown. The flow of virtual system change processing is shown. The flow of failure handling processing is shown. An n-dimensional requirement vector is shown as an example of the representation of n individual requirements belonging to the functional requirement. An N-dimensional requirement vector is shown as an example of the representation of the individual requirements of N, which is the sum of the individual requirements of n belonging to the functional requirements and the individual requirements of (Nn) belonging to the non-functional requirements. An example of the individual requirement vector of the individual infrastructure is shown. An example of the requirement vector of the virtual system requirement of the EtoE virtual system is shown. An example of the difference between the requirement vector of the calculation requirement and the requirement vector of the requirement requirement is shown. An example of the requirement vector of the virtual system requirement of the virtual system having the alternative virtual resource is shown.

In the following description, the "interface device" may be one or more interface devices. The one or more interface devices may be one or more similar 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). It may be HBA (Host Bus Adapter).

Further, in the following description, the "memory" is one or more memory devices, and may be 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.

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

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

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 processor device in a broad sense such as a hardware circuit (for example, FPGA (Field-Programmable Gate Array) or ASIC (Application Specific Integrated Circuit)) that performs a part or all of the processing.

Further, in the following description, information that can be obtained as an output for an input may be described by an expression such as "xxx store", but the information may be data having any structure and may be an output for an input. It may be a learning model such as a neural network that generates. Therefore, the "xxx store" can be referred to as "xxx information". Further, 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 a part of two or more stores may be one store. You may.

Further, in the following description, the function may be described by the expression of "kkk part", but the function may be realized by executing one or more computer programs by the processor, or one. It may be realized by the above hardware circuit (for example, FPGA or ASIC). When a function is realized by executing a program by a processor, the specified processing is appropriately performed by using a storage device and / or an interface device, so that the function may be at least a part of the processor. Good. The process described with the function as the subject may be a process performed by a processor or a device having the processor. The program may be installed from the program source. The program source may be, for example, a program distribution computer or a computer-readable recording medium (eg, a non-temporary recording medium). The description of each function is an example, and a plurality of functions may be combined into one function, or one function may be divided into a plurality of functions.

Further, in the following description, a "computer system" is a system including one or more physical computers. The physical computer may be a general-purpose computer or a dedicated computer.

Further, in the following description, the common part of the reference codes may be used when the same type of elements are not distinguished, and the reference code may be used when the same type of elements are distinguished. For example, when the ASP system is not distinguished, it may be referred to as "ASP system 301", and when the ASP system is distinguished, it may be referred to as "ASP system 301A" or "ASP system 301B".

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

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

The 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 in the computer system, or an ASP computer system (for example, a personal computer). The ASP system 301 specifies a plurality of conditions required for the application service (execution of the application program) to the resource pool management system 100. ASP may be paraphrased as a user.

The ISP layer 200 is a layer to which a plurality of ISP systems 221 belong. The ISP system 221 may be a system realized by executing predetermined software in the 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 as a virtual resource in the resource pool 110, or virtualizes according to an instruction 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 it may not be limited to that. For example, one ISP may provide a plurality of types of infrastructure, or a plurality of ISPs may provide one individual infrastructure. Further, in the example of FIG. 1, the ISP system 221 and the individual infrastructure 211 are one-to-one, but it may not be limited thereto.

The resource pool 110 has, for example, a virtual resource store 111 and a plurality of management units 112 (for example, 112A to 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 includes, for example, an ASP interface unit 130, a matching unit 121, a configuration control unit 122, and a virtual resource control unit 113. 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 the computer system. A computer system has, for example, an interface device, a storage device, and a processor connected to them. Each of the virtual resource store 111, the template store 124, and the configuration store 123 is stored in, for example, a storage device. The management unit 112 and the system construction unit 50 are realized, for example, by executing one or more programs on the processor.

The resource pool 110 provides data indicating one or more requirements including one or more functions for realizing the individual infrastructure 211 for each of the plurality of individual infrastructures 211 provided by the plurality of ISP systems 221. Include as. The system construction unit 50 has two or more virtual systems having two or more requirements whose difference from the virtual system requirements (an example of two or more conditions) required by the ASP system 301 for execution of the application program is within an allowable range. A resource is specified from the resource pool 110, and a virtual system that is a logical connection between the two or more virtual resources and is used for executing an application service is constructed. In the construction of the virtual system, the system construction unit 50 identifies the ISP system 221 that provides the individual infrastructure 211 corresponding to the virtual resource for each of the two or more virtual resources, and the ISP system 221 is provided with the virtual system. Instructs 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 composed of a plurality of virtual resources corresponding to a plurality of individual infrastructures 211 having different requirements and ISPs and having a requirement that the difference from the conditions required by the ASP is within an allowable range can be quickly established. And it becomes possible to construct efficiently.

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

As shown in FIG. 1, the resource pool management system 100 provides an ASP with a virtual system that combines requirements (functions) from the individual infrastructure 211 by mediating between the ISP system 221 and the ASP system 301. .. Examples of the individual infrastructure 211 include a sensor net 211A, a radio access network 211B, SD-WAN211C, a VPN (Virtual Private Network) 211D, and a cloud 221E. Each of the ISP systems 221A to 221E corresponding to these individual infrastructures 211A to 211E has functional requirements (for example, functions and performances such as communication bandwidth and start point or end point of physical resources) and non-functions of the individual infrastructure 211. Data indicating the sex requirement (for example, redundancy) is registered as a virtual resource in the virtual resource store 111 of the resource pool management system 100. Data indicating the link function 231 (for example, 231A to 231D) for connecting the physical resources of each individual infrastructure 211 is also included in the virtual resource as one of the connection information. The ISP system 221 may manage at least one of the virtualization and management of the individual infrastructure 211. For example, the ISP system 221A virtualizes the sensor net 211A (eg, network 2111, multiple sensors 2112 (which may include at least one surveillance camera), and gateway 2113) and virtualizes the sensor net 211A. The virtual resource as is registered in the virtual resource store 111. Further, for example, the ISP system 221E registers the virtual resource as the cloud 211E in the virtual resource store 111.

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

Further, the user management unit 112E is a function of managing an access policy or the like corresponding to the ASP, but the two are not necessarily associated with each other on a one-to-one basis. One user may use multiple ASP instances.

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

The virtual system requirements (an example of two or more conditions) associated with the request from the ASP system 301 are verified for consistency by the matching unit 121, and partial requirements (one or more) are applied to the plurality of management units 112A to 112E. It is decomposed and expanded as an example of the condition of). The management unit 112 in which the partial requirements are expanded matches the virtual resources corresponding to the expanded partial requirements by searching the virtual resource store 111. As a result, virtual resources with requirements that match the partial requirements are identified.

The virtual resource matched to 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 form a virtual system corresponding to the virtual system requirements from the ASP system 301, and configures the virtual system and the virtual resources in the virtual system (in other words, individual infrastructures). The connection information and the like indicating the logical connection between 211) are registered in the configuration store 123. Based on the information registered in the configuration store 123, the virtual resource control unit 113 sets the individual infrastructure 211 for each of the two or more individual infrastructures 211 corresponding to the two or more virtual resources constituting the virtual system. Instructs the managed ISP system 221 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 resources of the individual infrastructure 211 managed by the ISP system 221. , Virtual system deployment (eg, EtoE (end-to-end) virtual system) is complete. As a result, the construction of the virtual system is completed. For example, in the configuration illustrated in FIG. 1, a virtual system is constructed in which the data output from the sensor 2112 (sensor 2112 connected to the network 2111) in the sensor net 211A is housed in the VM2152 in the cloud 211E. The virtual system is utilized by the ASP that requested the virtual system requirements described above.

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

The 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, the 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 shown, but the virtual resource registration is also performed for the other ISP system 221 in the same manner. Further, FIG. 2 shows a case where a plurality of individual infrastructures of the same type exist. The resource pool 110 logically reserves the virtual resource on the virtual resource store 111 as a so-called usage right. In such resource retention, there may be various forms in response to the provision form of the physical resources of the individual infrastructure 211 and the fluctuation of the virtual system demand from the ASP. There may be a case where the usage right is reserved in the resource pool 110 in advance by predicting the fluctuation of the virtual system demand, or a virtual resource is registered in the resource pool 110 in the required time frame based on the reservation from the ASP.

The resource failure notification is a notification of a virtual resource failure corresponding to the individual infrastructure 211. That is, the failure of the virtual resource corresponding to the individual infrastructure 211 is notified from the ISP system 221 to the resource pool management system 100 due to the failure of the individual infrastructure 211.

The 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 a virtual system requirement (requirement for the entire virtual system), and the virtual system change request may have a virtual system requirement after the change (requirement for the entire virtual system after the change). It may have a virtual system requirement part (requirement after change) corresponding to the changed part. The virtual system requirement may be a combination of the service template 1241 and the conditions specified by the ASP.

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

The decomposition unit 1210 decomposes the virtual system requirements into functional requirements and non-functional requirements.

The functionality transforming unit 1211 transforms the functionality requirements into the 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 passes the extracted virtual resources to the configuration control unit 122.

The non-functional conversion unit 1213 converts the non-functional requirements into the 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.

The arrow 144 extending from the resource pool management system 100 to the ISP system 221 is an activation instruction (for example, an instruction for securing a resource or changing a resource and activating). Based on the information in the configuration store 123, the virtual resource control unit 113 issues 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 the configuration control unit 122 to the 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 deployment of the virtual system is completed). Notification) will be issued. In this embodiment, "construction of virtual system" includes configuration and deployment of virtual system. The "virtual system configuration" may be performed by extracting two or more virtual resources corresponding to the virtual system requirements and creating virtual system configuration information in which the two or more virtual resources are logically connected. In "virtual system deployment", the virtual system becomes available by securing (or changing) resources and activating the link function by instructing the ISP system 221 to activate 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 is completed). Is issued. Note that the virtual system may be changed in whole or in part, and the virtual system is deployed even if the virtual system is changed.

Further, for example, when a resource failure notification is issued from the ISP system 221, the virtual resource control unit 113 registers the 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 a virtual system containing a virtual resource with a failure, and the ASP system 301 of the ASP is used. , Send a failure notification.

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

The template store 124 has a service template for each ASP. Service templates may exist for each virtual system type in place of or in addition to each ASP. The virtual system type may be defined by one or more attributes such as the purpose of the virtual system.

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

Each service template enumerates the individual requirements that make up the virtual system requirements required by the ASP corresponding to the template. For example, according to the service template of the virtual system requirement required by ASP1, the following is an example.
-Virtual sensors are placed at bases (A, B, C, ..., N).
-The CPU performance, memory amount, and storage amount of VMs placed in the cloud are specified.
-The maximum communication band is 64 kb / s per sensor.
-Traffic characteristics are transmitted in bursts of 256 kb per hour.
-The maximum number of simultaneous connection sensors is 10,000.
・ Mobility is not required.
-There is a complete redundancy between the sensor and the VM.
-No functional changes will be made in the future.
-It is necessary to ensure the same operation as usual even in the event of a failure.
・ Degenerate operation is permitted in the event of a large-scale disaster.
・ In case of cloud failure, it is necessary to transfer to an alternative zone.
・ 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 that follows the combination of the 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. is there.

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

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

According to the example of FIG. 4, each column shows a virtual resource for the ISP corresponding to the column. In this example, the requirements (for example, functions) of virtual resources are listed for each ISP (for each individual infrastructure). In FIG. 4, although the description is summarized in individual infrastructures for the sake of simplicity, it may actually be described for each virtual resource instance that can be operated by the resource pool management system 100. The virtual resource instance may be described by the service particle size such as the link between the bases AB and the VM of the cloud, or the entire sensor spread over a wide area or the network cut out from the SD-WAN as the virtual resource instance. It is also possible to register as. Further, 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 shows virtual system configuration information (which may include connection information) about the virtual system corresponding to the column. For each virtual system, the virtual system configuration information may be an enumeration of virtual resources constituting the virtual system. The virtual resources listed here may be virtual resource instances that are actually occupied or statistically available to the virtual system.

According to the store configuration shown in FIGS. 3 to 5, the virtual system requirements of the service template, the requirements of the registered virtual resources, and the virtual system requirements of the configured virtual system are all virtual system requirements. It may have all the individual requirements that can constitute the above, specifically, all the individual requirement items and the requirement value for each individual requirement item. For example, all of the service template, virtual resource, and virtual system configuration information may have a common individual requirement of N (N is an integer of 2 or more). In this case, assuming that the number of individual requirements belonging to the functional requirements is n, the number of individual requirements belonging to the non-functional requirements may be (Nn).

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

Further, when a plurality of virtual systems have virtual resources of the same type, any of the following may be adopted.
-The virtual resources of the same type are regarded as a plurality of logically different virtual resources by being logically (for example, temporally) distinguished. Each of the plurality of virtual resources is a dedicated resource of the virtual system including the virtual resource.
-The virtual resource of the same type is regarded as one virtual resource shared by a plurality of virtual systems.

FIG. 6 shows the flow of the entire process including the virtual system construction process.

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

The ISP system 221 registers the virtual resource corresponding to the individual infrastructure 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. Further, the ISP system 221B virtualizes the physical resources of the radio access network 211B (S301B), and requests the resource pool management system 100 to register the virtualized resources (that is, virtual resources) in the resource pool 110. put out. In the resource pool management system 100 that receives such a request, a virtual resource is secured for each individual infrastructure requested (S311), and the secured virtual resource is registered in the virtual resource store 111 (). S312).

<Preparation of service template (S321)>

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

<Virtual system construction process (S331-S344)>

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

The matching unit 121 of the resource pool management system 100 receives a requirement notification (notification of virtual system requirements) and confirms the syntax of the requirement notification (S334). If there is no inconsistency in the syntax, the matching unit 121 divides the virtual system requirement 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 matching the individual requirement for each individual infrastructure (S336). The matching unit 121 calculates the virtual system requirements (for example, function and performance) of the virtual system as a set of the extracted virtual resources by synthesizing (logically connecting) the extracted virtual resources, and the calculation requirements. The difference between (calculated virtual system requirement) and requirement requirement (virtual system requirement indicated by the above requirement notification) is calculated (S337). The matching unit 121 notifies the calculated difference to the ASP system 301 that is the transmission source of the requirement notification, and the ASP system 301 receives the difference notification (notification indicating the difference between the calculation requirement and the requirement requirement) (S338). ). In S337, for example, both the calculation requirement and the requirement requirement have a common N individual requirement item, and the difference between the requirement values may be calculated for each of the N individual requirement items. The calculated difference (difference indicated by the difference notification) may be a set (for example, a list) of N requirement value differences corresponding to each N individual requirement item.

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 unacceptable, processing returns to S3301. That is, the requirements are changed.

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 of a virtual system having a calculation requirement (virtual system requirement calculated in S337) (S341), and the virtual system concerned. The system configuration information is registered in the configuration store 123 (S342).

In the resource pool management system 100, the virtual resource control unit 113 allocates virtual resources for each ISP system 221 corresponding to the virtual resources constituting the virtual system having calculation requirements based on the registered virtual system configuration information. Is instructed to activate (S343).

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

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

Any of the following may be adopted in place of at least a part of S338 to S340.
-For at least one ASP, a policy regarding acceptable differences 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. Regarding the ASP, in S339, the ASP system 301 determines whether or not the difference indicated by the difference notification corresponds to the allowable difference indicated by the policy.

In S311 the securing of virtual resources may correspond to the reservation of being a component of the virtual system. All or part of the reserved virtual resources (for example, some of the performance of the virtual resources) are allocated to the virtual system. If some of the reserved virtual resources are allocated, the rest of the virtual resources remain reserved. For each virtual resource, information regarding allocation may be registered for each virtual resource in, for example, the virtual resource store 111.

In calculating the virtual system requirements of a virtual system, logical connections may be made between the virtual resources that are the components of the virtual system. For example, the logical connection between the virtual resources A and B may define the connection and the connection direction between the virtual resources, such as the connection from the virtual resource A to the virtual resource B. An EtoE virtual system is constructed by logically connecting a plurality of virtual resources in a cascade.

A detailed example of S343 to S340 (that is, deployment of a virtual system) may be as follows. Take one virtual system as an example. The virtual resource control unit 113 identifies each virtual resource constituting 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, by referring to the virtual resource store 111, the ISP system 221 corresponding to the virtual resource is specified. Specified), and issues an activation instruction for the virtual resource to the specified ISP system 221. The instructions indicate, for example, the required requirements (eg, functionality and performance) and which individual infrastructure to connect with (eg, the ISP system 221 for the linked individual infrastructure). Various parameters such as the IP address and the content of the instruction to the IP system) are associated with each other. In response to the instruction, the ISP system 221 activates the individual infrastructure. For each virtual resource that constitutes the virtual system, the ISP system 221 corresponding to the virtual resource activates in response to the above-mentioned instruction to the ISP system 221 to complete the deployment of the virtual system. .. The individual infrastructure part corresponding to the virtual resource is mapped to the virtual resource as a component of the virtual system.

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

The ASP system 301 activates the change of virtual system requirements of the virtual system in use (S431) and selects the service template selected for constructing the virtual system in use (S432). The ASP system 301 issues a requirement change request, which is a change request of the virtual system requirement (virtual system requirement of the virtual system in use) based on the service template, to the resource pool management system 100 (S433). The requirement change request may include only the changed part (individual requirement after the change) of the virtual system requirements of the virtual system in use, or may include the entire virtual system requirement including the changed part. Also, changes to virtual system requirements may be made without selecting a service template. In addition, the virtual system requirements of the service template selected in the construction of 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 confirms the syntax of the change content indicated by the requirement change request (S434). If there is no problem with the syntax, S435-S444 similar to S335-S344 is performed.

That is, the matching unit 121 divides the requirements indicated by the changed contents into the requirements for the individual infrastructure corresponding to the changed contents (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 resource, and the requirement requirement, which is the virtual system requirement corresponding to the requirement change request (S437), and changes the requirement. A difference notification indicating the calculated difference is transmitted to the ASP system 301 that is the source of the request. The ASP system 301 receives the difference notification (S438). The ASP determines whether or not the difference indicated by the difference notification is acceptable (S439). If acceptable, the ASP system 301 issues a virtual system change request to the resource pool management system 100. If unacceptable, the process returns to S431.

The configuration control unit 122 of the resource pool management system 100 that has received the virtual system change request 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 changed part (S443).

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

According to the virtual system change process, in response to the virtual system change request from the ASP system 301, it is possible to realize or adjust the requirements by logically operating the virtual resources registered in the resource pool 110, and each ASP system 301 can adjust the requirements. Since there is no need to coordinate with individual infrastructure individually, rapid virtual system changes are possible.

FIG. 8 shows a flow of fault handling processing.

It is assumed that an example of the individual infrastructure in which a failure has occurred is the 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 a failure of the virtual resource (virtual resource of the radio access network) specified from the notification in, for example, the virtual resource store 111 (S503). ). The matching unit 121 extracts virtual systems, virtual resources, and ASPs (users) affected by the failure of the radio access network by using each management unit 112 (S504). An example of the extracted virtual system is a virtual system including virtual resources corresponding to a wireless access network. The extracted virtual resource is a virtual resource that is logically connected to the virtual resource corresponding to the wireless access network in the virtual system. An example of the extracted ASP is an ASP corresponding to the extracted virtual system (for example, an ASP corresponding to the service template selected in the construction of 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 about the extracted virtual system and virtual resource. The configuration control unit 122 issues a failure notification including the failure information to the ASP system 301 (S505).

Upon receiving the failure notification, the ASP system 301 receives the failure notification (S506) and displays the failure information indicated by the failure notification. Based on the displayed failure information, the ASP determines whether the difference between the requirements before and after the failure is acceptable (S507). If acceptable, the process ends (for example, waiting for another failure notification). If unacceptable, the ASP system 301 changes the virtual system requirements (S508), selects the service template corresponding to the virtual system in use (S509), and makes a requirement change request to the resource pool management system 100. Issuance (S510). S508 to S510 may be the same as S431 to S433. Further, instead of at least a part of S502 to S507, at least one of the following may be performed.
-If the requirement difference before and after the failure corresponds to the allowable difference indicated by the policy regarding the allowable difference, S507: Y may be automatically set, and if not, S507: N may be automatically set.
-In S504, an alternative virtual resource of the failed virtual release may be extracted. An alternative virtual resource is a virtual resource that has a requirement that the difference from the requirement of the failed virtual release falls within a certain range. The failure information indicated by the failure notification includes information indicating an alternative virtual resource in addition to information indicating the virtual resource in which the failure has occurred. Therefore, the display of the failure information indicated by the failure notification is a proposal for an alternative virtual resource.

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

According to the failure response process, since the resource pool management system 100 centrally grasps the virtual system using the virtual resource registered from each individual infrastructure, the spread range of the individual infrastructure failure and the alternative virtual system. Resource proposals can be realized quickly and efficiently. Even if the system construction unit 50 receives a failure notification from the ISP system 221, the system construction unit 50 may not issue the failure notification to the ASP system 301 if any of the following applies (specifically, for example, for example. It may be determined between S503 and S504 whether or not it is necessary to issue a failure notification to the ASP system, and if the result of the determination is true, S504 may be performed).
-The notified failure corresponds to a pre-specified requirement that does not affect the failure (for example, one or more predetermined requirements belonging to the daily functional requirements).
-The difference between the virtual system requirements before and after the failure is within the predetermined tolerance.

The second embodiment will be described. At that time, the differences from the first embodiment will be mainly described, and the common points with the first embodiment will be omitted or simplified.

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

The virtual system requirement is composed of a plurality of individual requirements (see, for example, FIG. 3), and the requirement vector as a representation of the plurality of individual requirements is a multidimensional vector. The unit of measurement of the quantity in each dimension differs depending on the requirements, and it may take a continuous numerical value or a discrete characteristic value. FIG. 9A shows an n-dimensional requirement vector 801 as an example of the representation of n individual requirements belonging to the functional requirements of the virtual system requirements.

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

The requirements (virtual system requirements requested by the ASP system) are divided into multiple individual requirements for multiple individual infrastructures. Specifically, for example, the matching unit 121 calculates an N-dimensional requirement vector as an expression of a requirement requirement, 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). The individual requirement vector 70 is a composite vector. According to the example of FIG. 10, it is as follows.

It is assumed that the target individual infrastructure has physical resources such as nodes A to D and links 811A to 811E. It is assumed that virtual resources corresponding to these physical resources are registered in the resource pool 110. According to the requirements, it is assumed that a virtual resource corresponding to the route from node A to node D is required. Here, as an example of the route from node A to node D, it is assumed that the virtual resource corresponding to the link 811A between the node A and the node B and the virtual resource corresponding to the link 811D between the node B and the node D are extracted. .. The requirement of the virtual resource corresponding to the link 811A is represented by the vector 821A, and the requirement of the virtual resource corresponding to the link 811D is represented by the vector 821D. In this case, the individual requirement vector 70 for the target individual infrastructure among the required requirements is a composite vector of the vector 821A and the vector 821D. For example, when a failure occurs in node B, the composite 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 target individual requirement vector 70 for the individual infrastructure. May be.

According to the example of FIG. 10, it is possible to handle a virtual system defined by various individual requirements, both functional requirements and non-functional requirements, as an object that can be managed and operated in an integrated manner as a synthesis of requirement vectors. Become. In addition, 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, and as illustrated in FIG. 11, each of the individual infrastructures 211A to 211E is performed. The individual requirement vectors 70A-70E are obtained. The system construction unit 50 obtains the requirement vector 820 of the EtoE virtual system from the sensor 2112 to the VM2152 by synthesizing the individual requirement vectors 70A to 70E.

However, it is not always possible to obtain a virtual system (a virtual system composed of extracted virtual resources) having a calculation requirement that a vector that exactly matches the vector 820 of the requirement requirement is obtained. According to the example of FIG. 12, the system construction unit 50 obtains the calculation requirement vector 830 by synthesizing the individual requirement vectors 831A to 831E of the virtual resources extracted for the individual infrastructures 211A to 211E, respectively. The calculation requirement vector 830 may differ from the requirement requirement vector 820. In such a case, the system construction unit 50 calculates the difference 837 between the two vectors 820 and 830. As an example of the difference 837, there is a vector difference between the requirement vector 830 and the requirement vector 820. Alternatively, it is conceivable to use the relationship between the vectors 820 and 830 as a metric of the difference, and for example, a scalar product or a vector product may be adopted.

According to the example of FIG. 12, it is possible to express the difference between the requirement requirement and the calculation requirement (realization specification) by performing various operations between the requirement vectors defined as the logical metric of the virtual system. Therefore, the feasible virtual system requirements for the requested virtual system requirements can be easily transmitted to the ASP.

The system construction unit 50 acquires the individual requirement vector 70 for each individual infrastructure by decomposing the requirement vector 820, and the difference from the individual requirement vector 70 is within a certain range using the individual requirement vector 70 as a key. Virtual resources corresponding to the requirements that are vectors that fit within may be extracted.

FIG. 13 shows an example of a virtual system realized as a synthesis of requirement vectors when virtual resources by some individual infrastructures become unavailable.

According to the example of FIG. 13, it is proposed to the ASP using the virtual system including the virtual resource of the VPN211D to bypass to the Internet 211X when the VPN211D becomes a failure. It is assumed that the Internet 211X is also an example of an individual infrastructure, and the virtual resources of the Internet 211X are also registered in the virtual resource store 111.

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, and the virtual resource corresponding to the individual requirement vectors 841C and 841E before and after the individual requirement vector 841D (SD- The virtual resource on the WAN211C and the virtual resource on the cloud 211E) are also unavailable in the EtoE virtual system.

In this case, the system construction unit 50 uses a part of the requirement vector 840 (requirement vector as an expression of the virtual system requirement of the virtual system in use) including the individual requirement vectors 841C to 841E as a substitute virtual resource (Internet 211X). It is configured as a composite vector of the requirement vector 841X of the virtual resource corresponding to) and the requirement vector 841E'of the virtual resource of the cloud 211E connected to the Internet 211X. Then, the system construction unit 50 substitutes the composite vector for the above-mentioned requirement vectors 841C to 841E, and calculates the requirement vector of the virtual system requirement of the virtual system after the substitution.

According to the example of FIG. 13, the alternative means in the event of a failure in the individual infrastructure is defined as an alternative requirement vector in the individual infrastructure or an alternative requirement vector including the individual infrastructure connected to the individual infrastructure in the failure. Since it can be defined, quick and efficient troubleshooting is possible.

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

The above Examples 1 and 2 can be summarized as follows, for example. The following summary may include matters not described above.

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

The plurality of individual infrastructures 211 include one or more networks (eg, sensor sets, radio access networks, etc.). In general, the inclusion of a network in two or more separate infrastructures for the provision of application services is even more burdensome for the ASP (especially two or more provided by two or more ISPs for the provision of application services). (When the requirements of the network are required), but since it is managed as a resource pool including the network, the burden on the ASP is reduced. For example, in order to connect the sensor 2112 of the sensor net 211A to the VM2152 of the cloud 211E, the ASP bears the burden of placing an order for inter-site connection to each of a plurality of ISPs such as the ISP of the radio access network 211B and the ISP of the SD-WAN211C. It can be eliminated.

Since the services that provide connectivity depend on geographical conditions, the network becomes a major bottleneck, especially in such cases. However, since networks are generally a so-called equipment industry that takes a lot of time and money to complete, they are desired to be used for a relatively long period of time, and it is relatively long until they become available with many individual requirements. take time. On the other hand, application services generally have a shorter product life cycle than the product life cycle of a network, and it is desired that they be provided promptly when needed.

As in Examples 1 and 2 above, since the plurality of infrastructures corresponding to the plurality of virtual resources registered in the resource pool 110 include the network, two or more for providing the application service. Even if the individual infrastructure includes a network, application services can be provided quickly.

It should be noted that it is difficult for a network to define requirements as clear functional requirements such as storage and CPU.

Therefore, regarding the network virtual resource which is a virtual resource for the network, the data as the network virtual resource shows a plurality of requirements, and the plurality of requirements are not in addition to one or more individual requirements belonging to the functional requirements. Includes one or more individual requirements that belong to functional requirements.

Networks also have a large spectrum of requirements, especially due to the large number of individual requirements that belong to non-functional requirements.

Therefore, the system construction unit 50 sets the requirement requirement (composed of M individual requirements) as the M-dimensional requirement vector and the calculation requirement (consisting of N individual requirements) as the 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 (list of requirement value differences for each requirement item) specified from the vector difference is within the predetermined range, or if it is approved by the ASP, the above-mentioned tolerance is allowed. Corresponds to the difference in the range.

For each domain (eg, ISP or individual infrastructure), a multidimensional individual request vector is generated according to the number of requirements for that domain. In the EtoE virtual system, the composite vector of two or more individual requirement vectors is the requirement vector of the virtual system. Depending on the usage status of virtual resources, it is often possible to configure a virtual system with calculation requirements that differ from the requirement requirements (calculation requirements (realization requirements) that are the requirement vector of the requirement requirement and the requirement vector that differs from the requirement vector). It is conceivable, but if the difference is within the permissible range, the difference is permissible.

When the system construction unit 50 receives a request to change some conditions of the virtual system in use, the system construction unit 50 uses one or more individual requirement vectors corresponding to some of the changed conditions to change the changed conditions. The requirement vector as an expression may be calculated. If the difference between the calculated requirement vector and the requirement vector as an expression of the requirement corresponding to the changed condition is within an allowable range, the system construction unit 50 will use the changed condition of the virtual system in use. You may change the virtual resources involved in. In this way, the virtual system configuration can be changed using the requirement vector. The virtual system configuration change may be performed by a method different from 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 of the two or more virtual resources constituting the virtual system in use, the system construction unit 50 is affected by the failure. Alternate virtual resources for one or more virtual resources (eg, virtual resources corresponding to a failed individual infrastructure and virtual releases that are logically connected to the virtual resource) may be identified. The system construction unit 50 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. You may identify an alternative virtual resource. The system construction unit 50 uses the individual requirement vector corresponding to the requirement of the alternative virtual resource, and uses 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. May be calculated. If the difference between the calculated requirement vector and the requirement vector as an expression of 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. It may be replaced with a resource. In this way, the requirement vector can be used to specify the alternative virtual resource and replace the virtual resource. It should be noted that the identification of the alternative virtual resource and the replacement of the virtual resource may be performed by a method different from 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 of two or more virtual resources constituting the virtual system in use, the system construction unit 50 is affected by the failure. The requirement vector of the post-failure virtual system requirement of the virtual system in use may be calculated using one or more individual requirement vectors corresponding to the post-failure requirement of one or more virtual resources. The system construction unit 50 may continue to use the virtual system in use as long as the difference between the calculated requirement vector and the requirement vector as an expression of the condition M is within an allowable range. In this way, the difference between the virtual system requirements before and after the failure can be calculated using the requirement vector. The difference between the virtual system requirements before and after the failure may be performed by a method different from the method using the requirement vector.

In the above description, the requirement vector of the virtual system requirement is calculated as a synthesis of the individual requirement vector of the virtual resource registered for each individual infrastructure 211. However, this method is not limited to the construction (or modification) of a single virtual system, and is applicable even when the construction (or modification) of a plurality of virtual systems is performed at the same time. In that case, total matching calculation such as synthesizing the difference between a plurality of required virtual system requirement vectors and the realization requirement vector, or synthesizing the required virtual system requirement vector itself and comparing the difference with the synthesizing of the realization requirement vector is performed. It is possible to do. According to this method, the efficiency of allocating realized virtual systems (virtual systems composed of extracted virtual resources) corresponding to multiple virtual system construction requests (or multiple virtual system change requests) across the resource pool. It is possible to execute as a matching.

Further, in the above description, the virtual resource allocation (deployment of the virtual system) is performed triggered by the virtual system construction request (or the virtual system change request) from the ASP system 301. However, instead or in addition, the same applies to the case where the virtual system demand from the ASP is predicted in advance and the virtual resource registered in the resource pool is reserved. Since virtual resource reservation based on such virtual system demand forecast can be logically realized on the resource pool, it is possible to quickly respond to a virtual system construction request (or virtual system change request) from ASP, or time reservation. It can also respond to type virtual system construction requests (or virtual system change requests). Furthermore, it is possible to forecast the demand while observing the trend of the virtual system construction request (or virtual system change request) from the ASP by calculating the requirement vector, which is a virtually operable logical instance. Such demand forecasting can ensure the accuracy of total demand forecasting by combining with the method of the above-described embodiment that synthesizes a plurality of virtual system construction requests (or virtual system change requests).

According to at least one embodiment, multiple types of virtual systems consisting of multiple individual infrastructures with different functions and administrators are quickly and efficiently constructed to meet the virtual system requirements required by the ASP. Is possible.

Also, according to at least one embodiment, a virtual system with the requirements required by an ASP (eg, functionality, performance or service area) does not need to be operated for each individual infrastructure (eg, for example). It is possible to build a virtual system quickly and easily without having to contact the ISP individually).

In addition, when configuring and operating an EtoE virtual system by interconnecting a wide variety of individual infrastructures, the ISP that operates the individual infrastructure understands the virtual system requirements from the individual ASPs and communicates with all the members. You will be freed from the difficult task of aligning requirements with each other, and you will be able to focus on managing the individual infrastructure that you manage.

Although some examples have been described above, these are examples for explaining the present invention, and the scope of the present invention is not limited to these examples. The present invention can also be implemented in various other forms.

100: Resource pool management system

Claims (15)

A resource pool that contains data indicating one or more requirements including one or more functions that realize the individual infrastructure for each of the multiple individual infrastructures provided by multiple ISPs (Infrastructure Service Providers) as virtual resources. When,
Regarding the execution of the application program, two or more virtual resources with two or more requirements whose difference from the two or more conditions required by the ASP (Application Service Provider) system are within the allowable range are specified from the resource pool. It is equipped with a system construction unit that constructs a virtual system that is a logical connection of the two or more virtual resources and is a system used for executing the application program.
In the construction of the virtual system, the system construction unit identifies the ISP system of the ISP that provides the individual infrastructure corresponding to the virtual resource for each of the two or more virtual resources, and applies the ISP system to the ISP system. Instruct the activation of individual infrastructure resources corresponding to virtual resources,
Resource pool management system. The plurality of individual infrastructures include one or more networks.
The resource pool management system according to claim 1. With respect to each of one or more network virtual resources, which is one or more virtual resources for the one or more networks.
The data as the network virtual resource shows multiple requirements and
The plurality of requirements include one or more requirements belonging to non-functional requirements in addition to one or more requirements belonging to functional requirements.
The resource pool management system according to claim 2. The two or more conditions are M conditions (M is an integer of 2 or more).
The system construction unit sets the M condition as an M-dimensional requirement vector, and sets the N requirement corresponding to the M condition 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 3. When the system construction unit receives the request for the condition M from the ASP system, the system construction unit calculates the vector difference and notifies the calculated vector difference to the ASP system.
The difference within the permissible range is a vector difference approved by the ASP system.
The resource pool management system according to claim 4. For each of the two or more virtual resources, the system construction unit sets the requirements corresponding to the condition M among the requirements of the virtual resources as individual requirement vectors.
The N-dimensional requirement vector is a composite vector of two or more individual requirement vectors corresponding to the two or more virtual resources.
The resource pool management system according to claim 5. When the system construction unit receives a request to change some conditions of the virtual system in use,
Calculate the requirement vector as an expression of the changed condition using one or more individual requirement vectors corresponding to some of the changed conditions.
If the difference between the calculated requirement vector and the requirement vector as an expression of the requirement corresponding to the changed condition is within the allowable range, the virtual resource related to the changed condition among the virtual systems in use is selected. change,
The resource pool management system according to claim 6. When the system construction unit receives a notification of failure of an individual infrastructure corresponding to at least one of two or more virtual resources constituting the virtual system in use, the system construction unit receives a notification of failure of the individual infrastructure corresponding to at least one virtual resource.
Identify alternative virtual resources that are virtual resources with requirements corresponding to the 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 acceptable. And
Using the individual requirement vector corresponding to the requirement of the alternative virtual resource, the requirement vector of the virtual system in which the alternative virtual resource is adopted instead of one or more virtual resources affected by the failure is calculated.
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 can be used as the alternative virtual resource. Replace,
The resource pool management system according to claim 6. When the system construction unit receives a notification of failure of an individual infrastructure corresponding to at least one of two or more virtual resources constituting the virtual system in use, the system construction unit receives a notification of failure of the individual infrastructure corresponding to at least one virtual resource.
Using one or more individual requirement vectors corresponding to the post-failure requirements of one or more virtual resources affected by the failure, the requirement vector of the post-failure virtual system requirements of the virtual system in use Calculate and
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 use of the virtual system in use is continued.
The resource pool management system according to claim 6. When the system construction unit receives the request for the condition M from the ASP system, the system construction unit calculates the difference and notifies the ASP system of the calculated difference.
The difference within the permissible range is the difference approved by the ASP system.
The resource pool management system according to claim 1. When the system construction unit receives a request to change some conditions of the virtual system in use, if the difference between the changed conditions and the requirements corresponding to the changed conditions is within an allowable range. Of the virtual systems in use, the virtual resources related to the changed conditions are changed.
The resource pool management system according to claim 1. When the system construction unit receives a notification of failure of an individual infrastructure corresponding to at least one of two or more virtual resources constituting the virtual system in use, the system construction unit receives a notification of failure of the individual infrastructure corresponding to at least one virtual resource.
Identify alternative virtual resources for one or more virtual resources affected by the failure
If the difference between the requirement of the virtual system in which the alternative virtual resource is adopted in place of one or more virtual resources affected by the failure and the requirement vector as an expression of the two or more conditions is within the allowable range. , Replacing the one or more virtual resources of the virtual system in use with the alternative virtual resource.
The resource pool management system according to claim 1. When the system construction unit receives a notification of failure of an individual infrastructure corresponding to at least one of two or more virtual resources constituting the virtual system in use, the system construction unit receives a notification of failure of the individual infrastructure corresponding to at least one virtual resource.
Using the post-failure requirements of one or more virtual resources affected by the failure, the post-failure virtual system requirements of the virtual system in use are calculated.
If the difference between the calculated virtual system requirement and the two or more conditions is within the permissible range, the use of the virtual system in use is continued.
The resource pool management system according to claim 1. 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 of which is a template of a plurality of conditions.
The two or more conditions requested by the ASP system are the conditions input using the service template.
The resource pool management system according to claim 1. For each of the multiple individual infrastructures provided by multiple ISPs (Infrastructure Service Providers), data indicating one or more requirements including one or more functions to realize the individual infrastructure is sent to the resource pool as a virtual resource. Accepting registration,
Regarding the execution of the application program, two or more virtual resources with two or more requirements whose difference from the two or more conditions required by the ASP (Application Service Provider) system are within the allowable range are specified from the resource pool.
A virtual system, which is a logical connection between the two or more virtual resources and is used for executing the application program, is configured.
For each of the two or more virtual resources that make up the virtual system, identify the ISP system of the ISP that provides the individual infrastructure corresponding to the virtual resource, and give the ISP system the individual infrastructure corresponding to the virtual resource. Instruct to activate the structure resource,
Resource pool management method.