Information processing device, update method, and program

Abstract

Provided are an information processing device, an information processing system, an update method, and a program capable of appropriately updating software even if a network function has a redundant configuration. An information processing device (1) includes: an information acquisition unit (2) that acquires, from a MANO execution device which uses network definition information including redundant configuration information, which is information about a redundant configuration of a network function, to perform instantiation of the network function and which executes MANO for the network function, the redundant configuration information included in the network definition information; and an update control unit (3) that proposes, on the basis of the redundant configuration information, an update sequence of a node for updating software on the node that executes processing for providing the network function.

Description

[Technical field]

[0001] The present disclosure relates to an information processing device, an information processing system, an update method, and a non-transitory computer-readable medium on which a program is stored. [Background technology]

[0002] When updating software, it is necessary to take into consideration the impact on the system. In this regard, Patent Document 1 discloses a method for performing software updates for multiple cloud gateways. In this method, the order of the cloud gateways is determined according to the risk of the connected automation solution, and the update is started from the cloud gateway with the lowest risk.

[0003] However, as the scale of the service expands, the number of servers (also called worker nodes or compute nodes) that host workloads continues to increase as the scale of the platform, i.e., private cloud, grows. As a result, the total number of servers in all data centers can reach hundreds or more. On the other hand, when updating a platform for security maintenance, software EOL (End Of Life), or new function introduction, it is necessary to consider the service continuity of VNFs (Virtual Network Functions) or NSs (Network Services), which are services composed of multiple VNFs. VNFs are deployed in a configuration with regional redundancy and intra-datacenter redundancy in any data center and worker node, but the deployment destination may be changed at any time by orchestration by MANO (Management and Orchestration). In order to update the platform software (i.e., the software of the worker nodes) while continuing the VNF service, the worker nodes used in the redundant configuration of NSs or VNFs must not be stopped at the same time. For this reason, it becomes difficult to determine the update order as the number of VNFs increases.

[0004] Note that a document related to this disclosure is Non-Patent Document 1. Non-Patent Document 1 discloses the specifications of a VNF Descriptor. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Special Publication No. 2020-502650 [Non-patent literature]

[0006] [Non-Patent Document 1] ETSI GS NFV-IFA 011 V4.1.1 (2020-11) "Network Functions Virtualization (NFV) Release 4; Management and Orchestration; VNF Descriptor and Packaging Specification", November 2020 Summary of the Invention [Problem to be solved by the invention]

[0007] In NFVI (Network Functions Virtualization Infrastructure), there are a large number of worker nodes. For this reason, it is very costly to manually calculate the update order for each software update, taking into account the information about the deployment destination of NS or VNF. Moreover, this must be done individually for all data centers, which invites work errors. Furthermore, the deployment destination may be changed arbitrarily by healing, scaling, etc., using MANO orchestration.

[0008] Here, for software updates of worker nodes, a centralized management type update method using a template or script and a control device can be considered in order to reduce costs and improve work quality. In this method, the necessary descriptions for the update are written in advance in the template or script, and the necessary files are deployed. This makes it possible to specify the order of any worker nodes, exclude specific nodes, and perform updates while suppressing orchestration by MANO. However, even with this technology, in order to perform updates that take into account the redundant configuration and service continuity of NS or VNF, it is necessary to conduct a survey in advance and manually make a detailed plan of when and how to update which worker nodes. Furthermore, since templates or scripts are created by specifying each worker node according to the plan, there is a possibility of human error, and it is not sufficient in terms of improving work quality.

[0009] Furthermore, the technology disclosed in the above-mentioned Patent Document 1 does not take into consideration the update of a system having a redundant configuration.

[0010] Therefore, one of the objectives that the embodiments disclosed in this specification aim to achieve is to provide an information processing device, an information processing system, an update method, and a program that can properly perform software updates even when the network function has a redundant configuration. [Means for solving the problem]

[0011] An information processing device according to a first aspect of the present disclosure includes: An information acquisition means for acquiring redundant configuration information included in network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about a redundant configuration of a network function, and executes MANO (Management and Orchestration) for the network function; an update control means for proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; has.

[0012] An information processing system according to a second aspect of the present disclosure includes: a MANO execution device that instantiates a network function using network definition information including redundant configuration information that is information about a redundant configuration of a network function and executes MANO for the network function; Information processing device Equipped with The information processing device includes: An information acquisition means for acquiring the redundant configuration information included in the network definition information from the MANO execution device; an update control means for proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; has.

[0013] In the update method according to the third aspect of the present disclosure, A MANO execution device performs instantiation of a network function using network definition information including redundant configuration information, which is information about a redundant configuration of a network function, and acquires the redundant configuration information included in the network definition information from a MANO execution device that performs MANO for the network function; An update order of the nodes that execute processes for providing the network function in updating software of the nodes is proposed based on the redundant configuration information.

[0014] A program according to the fourth aspect of the present disclosure includes: An information acquisition step of acquiring the redundant configuration information included in the network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information that is information about a redundant configuration of a network function and executes MANO for the network function; an update control step of proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; to be executed by the computer. Effect of the Invention

[0015] According to the present disclosure, it is possible to provide an information processing device, an information processing system, an update method, and a program that are capable of appropriately updating software even when the network function has a redundant configuration. [Brief description of the drawings]

[0016] [Figure 1] FIG. 1 is a block diagram showing an example of a configuration of an information processing device according to an overview of an embodiment. [Diagram 2] 1 is a block diagram illustrating an example of a configuration of an information processing system according to an embodiment. [Diagram 3] 11 is a table showing an example of redundant configuration information. [Figure 4] 11 is a table showing an example of redundant configuration information. [Diagram 5] FIG. 2 is a block diagram showing an example of a hardware configuration of a central control device according to an embodiment. [Figure 6] 10 is a flowchart showing an example of an operation flow of a central control device according to the embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0017] <Outline of the embodiment> Before describing the details of the embodiment, an overview of the embodiment will be described. Fig. 1 is a block diagram showing an example of a configuration of an information processing device 1 according to the embodiment. As shown in Fig. 1, the information processing device 1 has an information acquisition unit 2 and an update control unit 3.

[0018] The information acquisition unit 2 acquires redundant configuration information included in the network definition information from the MANO execution device. Here, the MANO execution device is a device that performs instantiation of a network function using network definition information including redundant configuration information that is information about the redundant configuration of the network function, and executes MANO for the network function. In addition, the network function is specifically, for example, a VNF, but may also be a CNF (Container Network Function).

[0019] The update control unit 3 proposes an update order for nodes in updating software of the nodes that execute processes for providing network functions, based on the redundant configuration information acquired by the information acquisition unit 2.

[0020] In this way, the information processing device 1 acquires information about the type of redundant configuration of the network functions, and proposes an update order based on the acquired information. This allows the operator (user) to grasp an appropriate update order that takes into account the redundant configuration. This allows node software to be updated appropriately even if the network functions have a redundant configuration. This makes it possible to suppress the impact on services and improve the quality of the update work.

[0021] <Details of the embodiment> Next, details of the embodiment will be described. FIG. 2 is a block diagram showing an example of a configuration of an information processing system 10 according to the embodiment. In the example shown in FIG. 2, the information processing system 10 includes data centers 200_1, 200_2, . . . , 200_N and a central control device 100. In the following description, when the data centers 200_1, 200_2, . . . , 200_N are mentioned without any particular distinction, they will be referred to as data center 200. Note that FIG. 2 illustrates a configuration related to the features of the present embodiment, and other configurations are omitted as appropriate.

[0022] The data center 200 is a facility that accommodates physical resources for VNFs, and includes a MANO 210, a management device 220, and an NFVI 230. The number of data centers 200 is arbitrary. That is, N is an integer equal to or greater than 1. However, when a redundant configuration using different data centers 200 is adopted, the number of data centers 200 is two or more. In this case, each data center 200 is located in a different geographical region.

[0023] The MANO 210 is a node having a VNF management unit 211 that provides management of hardware and software resources, as well as management and orchestration functions for VNFs. Specifically, the VNF management unit 211 includes an NFVO (Network Function Virtualization (NFV) Orchestrator), a VNFM (VNF Manager), and a VIM (Virtualized Infrastructure Manager). The NFVO manages the lifecycle (e.g., generation, monitoring, operation, deletion, etc.) of a network service composed of multiple VNFs, and is responsible for integrated operation management of the entire system. The VNFM is responsible for managing resource requirements required by the VNFs and lifecycle management of the VNFs. The VIM is responsible for operation management of physical resources and virtual resources.

[0024] Deployment of NS or VNF (i.e., NS / VNF Instantiation) is performed by MANO210, mainly using the VNF Descriptor defined in ETSI GS NFV-IFA 011. Note that, except for nested NS, deployment across NFVIs is not possible in units of NS or VNF.

[0025] MANO 210 is a node corresponding to the above-mentioned MANO execution device, and performs VNF instantiation using a VNF descriptor including redundant configuration information, which is information about the redundant configuration of the VNF. Specifically, in this embodiment, MANO 210 performs VNF instantiation (in other words, VNF deployment) using a VNF descriptor that is an extension of the VNF descriptor defined in ETSI GS NFV-IFA 011 so as to include redundant configuration information. Hereinafter, the VNF descriptor may be referred to as a VNFD. Details of the redundant configuration information will be described later.

[0026] The NFVI 230 is an infrastructure for providing VNFs, and includes a plurality of worker nodes 231. Note that the number of worker nodes included in the NFVI 230 may differ in each data center 200. The worker node 231 is a physical server, and executes various software for providing VNFs. The worker node 231 is a specific example of a node that executes processing for providing VNFs. In this embodiment, a technique for updating software of a platform, that is, software of the worker node 231, is described.

[0027] The management device 220 is a node for controlling the software update process in the data center 200, and includes an update execution unit 221. The update execution unit 221 executes the process required for updating the software. That is, the update execution unit 221 is a processing unit that performs the software update process of the worker node 231. The update execution unit 221 executes the software update process, for example, according to an instruction from an update control unit 102 of the central control device 100, which will be described later.

[0028] The central control device 100 corresponds to the information processing device 1 in FIG. 1, and is a device that manages the redundant configuration of the VNF for updating the software of the worker node 231. The central control device 100 is connected to the MANO 210 and the management device 220 of each data center 200 in a wired or wireless manner so as to be able to communicate with each other. The central control device 100 includes an information acquisition unit 101 and an update control unit 102. The information acquisition unit 101 corresponds to the information acquisition unit 2 in FIG. 1, and acquires redundant configuration information included in the VNFD from the MANO 210 of each data center 200. In addition, the update control unit 102 proposes an update order of the worker node 231 in updating the software of the worker node 231 based on the redundant configuration information. For example, the update control unit 102 proposes the order of the data centers 200 in which the worker node 231 is updated, and the update order of the worker node 231 in the data center 200.

[0029] Here, we consider how to grasp the redundant configuration. In the case of a redundant configuration within one NFVI, it is possible to infer to some extent from the parameter values ​​of "vdu", "autoScale", "vipCpd", and "deploymentFlavour" (hereafter referred to as DF), which are attributes defined in the VNFD. However, the exact redundant configuration in the NS / VNF application layer cannot be grasped with existing specifications.

[0030] In addition, when instantiating an NS or VNF across NFVIs to provide regional redundancy to the NS or VNF, the following three methods can be considered.

[0031] The first method (Method a) is a method that uses the DCN (Distributed Computes Nodes) function of OpenStack, a cloud infrastructure software, and deploys NSs or VNFs in multiple regions (multiple data centers) using a single VNFD. The second method (method b) is to deploy NSs or VNFs to NFVIs in independent regions (data centers), each using a separate VNFD. The third method (method c) is a method of deploying NS or VNF on an OpenStack Platform (OSP) for each independent region (data center) using a Nested Network Service Descriptor (NSD).

[0032] In the case of method a, since it is logically similar to the case of the redundant configuration within one NFVI described above, the redundant configuration cannot be grasped with the existing ETSI NFV specifications. In addition, in the case of method b, since there is no relationship between each VNFD, MANO recognizes each instantiated VNF as a different VNF. Therefore, in the case of method b, the redundant configuration cannot be grasped. Furthermore, in the case of method c, although it is possible to specify the NFVI to be deployed in units of NS, the information that those NSs are in a redundant configuration is not included in the NSD and VNFD, so in this case too, the redundant configuration cannot be grasped.

[0033] In contrast, in this embodiment, by using a VNF descriptor that is extended to include redundant configuration information, it is possible to grasp the redundant configuration in any of the above-mentioned cases.

[0034] In this embodiment, the redundant configuration information is information on whether or not a redundant configuration by the worker nodes 231 in the same data center 200 exists, and information on whether or not a redundant configuration by the worker nodes 231 in the data centers 200 in different regions exists. In addition, when it is not necessary to grasp the redundant configuration by the worker nodes 231 in the data centers 200 in different regions, the redundant configuration information may be only information on whether or not a redundant configuration by the worker nodes 231 in the same data center 200 exists. Similarly, when it is not necessary to grasp the redundant configuration by the worker nodes 231 in the same data center 200, the redundant configuration information may be only information on whether or not a redundant configuration by the worker nodes 231 in the data centers 200 in different regions exists.

[0035] Hereinafter, information on whether or not there is a redundant configuration by the worker nodes 231 in the same data center 200 will be specifically described. In this embodiment, in the VNFD, an attribute as shown in FIG. 3 is added to an information element for a VDU (Virtual Deployment Unit), thereby making it possible to grasp a redundant configuration in the data center 200 of a VNFC (VNF Component), which is a component of a VNF. That is, in this embodiment, in order to make it possible to detect whether or not the configuration is made redundant in one NFVI 230, an attribute value "redundantInstance" shown in FIG. 3 is added to the VNFD. Note that each VNFC used in the redundant configuration in the data center 200 uses the same VDU. The VDU is a basic component of the VNF, and corresponds to a VM having a network function.

[0036] The attribute value "redundantInstance" is an attribute value given to each VDU, and specifically, is an identifier indicating that the VNFC using the VDU has a redundant configuration. The attribute value "redundantInstance" takes a value of true or false, and when the value of the attribute value "redundantInstance" is true, the VNFC instantiated using the VDU is treated as having a 1+N redundant configuration. In other words, a VNFC using a VDU for which this attribute value is true has a redundant configuration and is deployed in the data center 200.

[0037] In this way, the redundant configuration information may be information included in the VNFD as an attribute value for each VDU, and may be an attribute value indicating whether or not the VNFC using the VDU is in a redundant configuration. In other words, such redundant configuration information may be used as information regarding whether or not a redundant configuration by the worker nodes 231 in the same data center 200 exists.

[0038] Next, information on whether or not there is a redundant configuration by worker nodes 231 of data centers 200 in different regions will be specifically described. In this embodiment, by adding an attribute as shown in FIG. 4 to an information element for a DF in a VNFD, it is possible to grasp a redundant configuration by different regions (data centers 200) realized by using a different VNFD. That is, in order to make it possible to detect whether or not redundancy of the configuration is performed by using data centers 200 in different regions, in this embodiment, attribute values ​​"geoRedundancy" and "geoRedundancyVNFdid" shown in FIG. 4 are added to the VNFD.

[0039] The attribute value "redundantInstance" is an attribute value given for each DF. That is, the attribute value "redundantInstance" is an attribute value given for each VNF. In addition, since an NS is composed of multiple VNFs, this attribute value exists for the number of VNFs that compose the NS. Specifically, this attribute value is an identifier indicating whether or not a regional redundant configuration exists between different NFVIs with a value of true or false. When the value is true, it indicates that such a redundant configuration exists, and an attribute value of "geoRedundancyVNFdid" is also provided.

[0040] The attribute value "geoRedundancyVNFdid" indicates an identifier of a VNFD used for instantiation to identify redundancy between different NFVIs. That is, the attribute value "geoRedundancyVNFdid" is an attribute value that identifies the corresponding VNFD. In other words, the attribute value "geoRedundancyVNFdid" makes it possible to identify which VNFs and which VNFs are in a redundant configuration.

[0041] In this way, the redundant configuration information may be information included in the VNFD as an attribute value for each VNF (DF), and may be an attribute value indicating whether or not a redundant configuration using a different NFVI exists for the VNF. If a redundant configuration using a different NFVI exists, the redundant configuration information may further include an identifier of a VNFD for instantiating another VNF that configures the redundant configuration. In other words, such redundant configuration information may be used as information regarding whether or not a redundant configuration by a worker node 231 of a data center 200 in a different region exists.

[0042] Although the attribute values ​​described above do not allow for understanding of redundant configurations on a VNFC basis, they do allow for understanding of redundant configurations on a VNF basis, making it possible to formulate an NFVI update plan that maintains service continuity.

[0043] The information acquisition unit 101 of the central control device 100 acquires the values ​​of the attributes shown in Fig. 3 and Fig. 4 from each MANO 210 when the MANO 210 instantiates a VNF using a VNFD. As a result, the information acquisition unit 101 acquires information for identifying a redundant configuration of an NS or a VNF within a data center 200 and between different data centers 200.

[0044] The update control unit 102 of the central control device 100 proposes an update order for the data centers 200 and the worker nodes 231 based on the information acquired by the information acquisition unit 101. That is, the update control unit 102 proposes which data center 200 to start updating and which worker node 231 in the data center 200 to be updated to start updating. Specifically, the update control unit 102 creates a plan for the update order and outputs the created plan. The output may be displayed on a display or may be transmitted to an arbitrary terminal communicably connected to the central control device 100. The update control unit 102 may create multiple plans and output multiple plans. The operator refers to the output plan and inputs an instruction to specify the update order to the central control device 100. This input is given to the central control device 100 by an arbitrary method. For example, this input may be made via an input device connected to the central control device 100 or may be made via any of the above-mentioned terminals. The instruction to specify the update order may be an instruction to approve the output plans, an instruction to select one of the plans, or an instruction to modify the proposed update plan.

[0045] Then, the update control unit 102 instructs the management device 220 of the data center 200 to be updated of the order of the worker nodes 231 to be updated according to the update plan (update order) determined by the input instructions. The update execution unit 221 of the management device 220 executes software update processing of the worker nodes 231 in order according to the instructions.

[0046] Here, the update order proposed by the update control unit 102 will be described. The update control unit 102 uses the following parameter N 1 and N 2 We may plan the update sequence according to, where N 1 indicates the number of data centers 200 that perform updates simultaneously. 2 indicates the number of worker nodes 231 that can be updated simultaneously. Note that updates may be performed sequentially, not completely in parallel, by multiple worker nodes 231. In other words, N 2 N can also be said to be the number of worker nodes 231 to be updated in parallel or sequential updates. 1 The value of N is set by, for example, the operator taking into consideration the risk of failure and the time available for updating. 2 The value of is set by the operator to a value equal to or less than the upper limit imposed by technical limitations, for example.

[0047] The update control unit 102 updates the parameter N 1 and N 2 The update control unit 102 proposes an update order that satisfies the following conditions while satisfying the constraints specified by the parameter N 1 and N 2 In addition, it is preferable that the update control unit 102 proposes an update order that satisfies all of the conditions shown below, but it may propose an update order that satisfies any combination of the conditions, or may propose an update order that satisfies any one of the conditions.

[0048] <Condition A> The update order is such that the data center 200 with the least number of deployed VNFCs is selected first, and the worker node 231 with the least number of deployed VNFCs is selected first. In this case, the update control unit 102 determines the order of the data centers 200 in which the worker nodes 231 are updated, based on the total number of VNFCs implemented by the worker nodes 231 in the data center 200. In other words, the update control unit 102 determines the update order of the worker nodes 231 in units of data centers 200, based on the total number of VNFCs implemented by the worker nodes 231 in the data center 200. In addition, in this case, the update control unit 102 determines the update order of the worker nodes 231, based on the number of VNFCs implemented by the worker nodes 231. This makes it possible to suppress the risk of update failure. Note that the number of deployed VNFCs is managed by the MANO 210, and when an update order is proposed to satisfy this condition, the information acquisition unit 101 acquires the number of VNFCs from the MANO 210.

[0049] <Condition B> Two or more data centers 200 in different regions that are configured in a redundant configuration are not subject to update at the same time. That is, in this case, the update control unit 102 proposes an update order in which the worker nodes 231 are not updated simultaneously in two or more data centers 200 used in a redundant configuration by the worker nodes 231 of the data centers 200 in different regions. That is, in this case, the update control unit 102 proposes an update order other than the update order in which the worker nodes 231 of such two or more data centers 200 are updated simultaneously. Note that in this case, the information acquisition unit 101 identifies the data center 200 in the redundant relationship by inquiring of the MANO 210 about the data center 200 in which the VNF instantiated by the VNFD specified in "geoRedundancyVNFdid" exists. In this way, it is possible to implement an update taking into account a regional redundant configuration.

[0050] <Condition C> Two or more worker nodes 231 that form a redundant configuration in the same data center 200 are not subject to update at the same time. That is, in this case, the update control unit 102 proposes an update order that does not simultaneously update two or more worker nodes 231 that are in a mutually redundant relationship and are used in a redundant configuration by the worker nodes 231 in the same data center 200. That is, in this case, the update control unit 102 proposes an update order other than the update order in which such two or more worker nodes 231 are updated simultaneously. Note that in this case, the information acquisition unit 101 identifies the worker node 231 in a redundant relationship by inquiring of the MANO 210 about the worker node 231 in which the VNFC deployed by using the VDU in which "redundantInstance" is true exists. In this way, it is possible to implement an update that takes into account the redundant configuration in the data center 200.

[0051] <Condition D> Data centers 200 in different regions that have a redundant configuration, that is, data centers 200 that are in a redundant relationship, are not consecutively targeted for update. That is, in this case, the update control unit 102 proposes an update order such that the redundant data center 200 does not become a data center where the worker node 231 is successively updated. That is, in this case, the update control unit 102 proposes an update order other than the update order such that the data center 200 becomes a data center where the worker node 231 is successively updated. This makes it possible to realize an update that takes into consideration the switching timing of the workload on the NS or VNF and the operation confirmation period after the switching. That is, it becomes possible to implement an update without impeding the handover of service provision during the update and the confirmation of the handover, which are performed between the redundant VNFs.

[0052] <Condition E> The worker nodes 231 that form a redundant configuration in the same data center 200, that is, the worker nodes 231 that are in a redundant relationship, are not subject to successive updates. That is, in this case, the update control unit 102 proposes an update order that does not continuously update worker nodes 231 that are in a redundant relationship. That is, in this case, the update control unit 102 proposes an update order other than the update order in which such worker nodes 231 are continuously updated. This makes it possible to realize an update that takes into consideration the timing of switching workloads on the NS or VNF and the operation confirmation period after switching, as in the case of condition D. In addition, it is possible to prevent workloads from being switched alternately and continuously.

[0053] Next, a description will be given of an example of a hardware configuration of the central control device 100. Fig. 5 is a block diagram showing an example of a hardware configuration of the central control device 100. The central control device 100 has, for example, a network interface 150, a memory 151, and a processor 152 as shown in Fig. 5.

[0054] The network interface 150 is used to communicate with other devices (eg, the MANO 210 and the management device 220). The network interface 150 may include, for example, a network interface card (NIC).

[0055] The memory 151 is configured, for example, by a combination of a volatile memory and a non-volatile memory. The memory 151 is used to store software (computer programs) including one or more instructions to be executed by the processor 152, and data required for processing.

[0056] The processor 152 reads out software (computer programs) from the memory 151 and executes them to perform processing of the central control device 100 .

[0057] The processor 152 may be, for example, a microprocessor, a microprocessor unit (MPU), a central processing unit (CPU), etc. The processor 152 may include multiple processors.

[0058] In this way, the central control device 100 functions as a computer. The MANO 210, the management device 220, and the worker node 231 may also be computers having the configuration shown in Fig. 5. In other words, the processing of the MANO 210, the management device 220, and the worker node 231 may be realized by a processor in each device reading and executing software (computer program) including one or more instructions stored in a memory.

[0059] The above-mentioned program can be stored and supplied to a computer using various types of non-transitory computer readable media. The non-transitory computer readable medium includes various types of tangible storage media. Examples of the non-transitory computer readable medium include magnetic recording media (e.g., flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (e.g., magneto-optical disks), CD-ROM (Read Only Memory), CD-R, CD-R / W, and semiconductor memory (e.g., mask ROM, PROM (Programmable ROM), EPROM (Erasable PROM), flash ROM, RAM (Random Access Memory)). The program may also be supplied to a computer by various types of transitory computer readable media. Examples of the transitory computer readable medium include electric signals, optical signals, and electromagnetic waves. The transitory computer readable medium can supply the program to a computer via a wired communication path such as an electric wire and an optical fiber, or via a wireless communication path.

[0060] Next, a description will be given of the flow of update control by the central control device 100. Fig. 6 is a flowchart showing an example of the flow of operation of the central control device 100. Below, the example operation will be described with reference to Fig. 6.

[0061] In step S 100 , the information acquisition unit 101 acquires redundant configuration information from the MANO 210 . Next, in step S101, the update control unit 102 proposes an update order based on the information acquired in step S100. Next, in step S102, the update control unit 102 receives an instruction to specify the update order from an operator (user) who has referred to the update order proposed in step S101. Next, in step S103, the update control unit 102 instructs the management device 220 to update the worker nodes 231 in accordance with the update order specified in step S102.

[0062] In this way, the central control device 100 acquires redundant configuration information and proposes an update order based on the acquired information. Therefore, even if the NS or VNF has a redundant configuration, the software of the worker node 231 can be appropriately updated.

[0063] Although the present invention has been described above with reference to the embodiment, the present invention is not limited to the above. Various modifications that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the scope of the invention.

[0064] For example, a warning may be issued when a VNF is instantiated with insufficient resources (e.g., CPU, RAM, storage, or NIC) to perform VNF Hardware Healing. The present invention is not limited to cases where a network function is used in a virtual machine, but may also be applicable to cases where a network function is used in a container.

[0065] A part or all of the above-described embodiments can be described as, but is not limited to, the following supplementary notes. (Appendix 1) An information acquisition means for acquiring redundant configuration information included in network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about a redundant configuration of a network function, and executes MANO (Management and Orchestration) for the network function; an update control means for proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; An information processing device having the above configuration. (Appendix 2) The redundant configuration information includes information as to whether or not a redundant configuration exists with the nodes in the same data center. 2. An information processing device according to claim 1. (Appendix 3) The redundant configuration information includes information as to whether or not a redundant configuration exists with the nodes of data centers in different regions. 3. The information processing device according to claim 1 or 2. (Appendix 4) The update control means proposes an update order that does not simultaneously update two or more of the nodes used in a redundant configuration by the nodes in the same data center. 3. An information processing device according to claim 2. (Appendix 5) The update control means proposes an update order that does not update the two or more nodes consecutively. 5. The information processing device according to claim 4. (Appendix 6) The update control means proposes an update order that prevents the nodes from being updated simultaneously in two or more data centers used in a redundant configuration with the nodes in data centers in different regions. 4. The information processing device according to claim 3. (Appendix 7) The update control means proposes an update order such that the two or more data centers do not become data centers in which the node updates are performed consecutively. 7. The information processing device according to claim 6. (Appendix 8) The update control means determines the order of the data centers in which the node is updated based on the total number of network function components implemented in the node in the data center. 8. An information processing device according to any one of claims 1 to 7. (Appendix 9) The update control means determines an update order for the nodes based on the number of network function components implemented in the nodes. 9. An information processing device according to any one of claims 1 to 8. (Appendix 10) a MANO execution device that instantiates a network function using network definition information including redundant configuration information that is information about a redundant configuration of a network function and executes MANO for the network function; Information processing device Equipped with The information processing device includes: An information acquisition means for acquiring the redundant configuration information included in the network definition information from the MANO execution device; an update control means for proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; An information processing system having the above configuration. (Appendix 11) The redundant configuration information includes information as to whether or not a redundant configuration exists with the nodes in the same data center. 11. The information processing system according to claim 10. (Appendix 12) The redundant configuration information includes information as to whether or not a redundant configuration exists with the nodes of data centers in different regions. 12. The information processing system according to claim 10 or 11. (Appendix 13) A MANO execution device performs instantiation of a network function using network definition information including redundant configuration information, which is information about a redundant configuration of a network function, and acquires the redundant configuration information included in the network definition information from a MANO execution device that performs MANO for the network function; and proposing an update order of the nodes for performing a process for providing the network function, in updating software of the nodes, based on the redundant configuration information. How to update. (Appendix 14) An information acquisition step of acquiring the redundant configuration information included in the network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information that is information about a redundant configuration of a network function and executes MANO for the network function; an update control step of proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; A non-transitory computer-readable medium on which a program for causing a computer to execute the program is stored. [Explanation of symbols]

[0066] 1. Information processing device 2 Information acquisition section 3 Update control section 10. Information Processing Systems 100 Central control unit 101 Information acquisition department 102 Update control section 150 Network Interface 151 Memory 152 processors 200 Data Centers 210 MANO 211 VNF Management Department 220 Management device 221 Update Execution Department 230 NFVI 231 worker nodes

Claims

1. an information acquiring means for acquiring redundant configuration information included in the network definition information from a MANO executing device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about a redundant configuration of the network function, and that implements MANO (Management and Orchestration) for the network function; an update control means for proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; having the redundant configuration information includes information as to whether or not a redundant configuration by the node in a data center in which the node is located exists; The update control means proposes an update order that prevents two or more of the nodes used in a redundant configuration by the nodes in the data center from being updated simultaneously and prevents the two or more nodes from being updated consecutively. Information processing device.

2. An information acquisition means for acquiring redundant configuration information included in network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about the redundant configuration of the network function, and that implements MANO (Management and Orchestration) for the network function; an update control means for proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; having The redundant configuration information includes information as to whether or not a redundant configuration exists using the nodes in data centers in different regions; The update control means proposes an update order such that the nodes are not updated simultaneously in two or more data centers used in a redundant configuration with the nodes in data centers in different regions, and such that the two or more data centers do not become data centers in which the nodes are updated consecutively. Information processing device.

3. An information acquisition means for acquiring redundant configuration information included in network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about a redundant configuration of a network function, and that implements MANO (Management and Orchestration) for the network function; an update control means for proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; having The update control means determines the order of the data centers in which the node is updated based on the total number of network function components implemented in the node in the data center. Information processing device.

4. A MANO executing device instantiates a network function using network definition information including redundant configuration information, which is information about a redundant configuration of a network function, and obtains the redundant configuration information included in the network definition information from a MANO executing device that implements MANO for the network function; proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; the redundant configuration information includes information as to whether or not a redundant configuration by the node in a data center in which the node is located exists; At the time of the proposal, an update order is proposed that does not simultaneously update two or more of the nodes used in a redundant configuration by the nodes in the data center, and that does not continuously update the two or more nodes. How to update.

5. A method for instantiating a network function using network definition information including redundant configuration information, which is information about a redundant configuration of a network function, and acquiring the redundant configuration information included in the network definition information from a MANO execution device that implements MANO for the network function; proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; The redundant configuration information includes information as to whether or not a redundant configuration exists using the nodes in data centers in different regions; At the time of the proposal, an update order is proposed in which the nodes are not updated simultaneously in two or more data centers used in a redundant configuration with the nodes in data centers in different regions, and the two or more data centers are not data centers in which the nodes are updated consecutively. How to update.

6. A MANO executing device instantiates a network function using network definition information including redundant configuration information, which is information about a redundant configuration of a network function, and obtains the redundant configuration information included in the network definition information from a MANO executing device that implements MANO for the network function; proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; In the proposal, an order of the data centers in which the updates of the nodes are to be performed is determined based on a total number of network function components implemented by the nodes in the data centers. How to update.

7. an information acquisition step of acquiring redundant configuration information included in network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about a redundant configuration of a network function, and that implements MANO for the network function; an update control step of proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; Run the following on your computer: the redundant configuration information includes information as to whether or not a redundant configuration by the node in a data center in which the node is located exists; In the update control step, an update order is proposed that does not simultaneously update two or more of the nodes used in a redundant configuration by the nodes in the data center, and that does not continuously update the two or more nodes. program.

8. An information acquisition step of acquiring redundant configuration information included in network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about a redundant configuration of a network function, and that implements MANO for the network function; an update control step of proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; Run the following on your computer: The redundant configuration information includes information as to whether or not a redundant configuration exists using the nodes in data centers in different regions; In the update control step, an update order is proposed in which the nodes are not updated simultaneously in two or more data centers used in a redundant configuration with the nodes in data centers in different regions, and the two or more data centers are not data centers in which the nodes are updated consecutively. program.

9. An information acquisition step of acquiring redundant configuration information included in network definition information from a MANO execution device that instantiates a network function using network definition information including redundant configuration information, the redundant configuration information being information about a redundant configuration of a network function, and that implements MANO for the network function; an update control step of proposing an update order of the nodes in updating software of the nodes that execute a process for providing the network function based on the redundant configuration information; Run the following on your computer: In the update control step, an order of the data centers in which the nodes are updated is determined based on a total number of network function components implemented in the nodes in the data center. program.

Images