Management system, management apparatus, and management method

Abstract

To improve compatibility between a network function to be deployed and a hardware infrastructure.SOLUTION: The management system includes an acquisition means for acquiring information for identifying a target virtualized network function, and a determination means for determining a target hardware infrastructure on which the target virtualized network function is deployed by referring to policy information including a policy of the virtualized network function for the hardware infrastructure.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a management system, a management device, and a management method. [Background technology]

[0002] In recent years, the use of container-based virtualization technology has become mainstream in building systems on networks. Accordingly, management technologies for the virtualization technology have also been developed. For example, Patent Document 1 discloses a technology related to an orchestrator in a network service management device that provides network services using resources included in a network function virtualization platform, which re-reserves alternative resources when a reserved resource fails to be secured. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2020-036105 Summary of the Invention [Problem to be solved by the invention]

[0004] In network function virtualization, requirements for the hardware infrastructure may differ depending on the network functions to be deployed. However, the technology of Patent Document 1 does not take such requirements into consideration, and therefore there may be cases where the deployed network functions are not compatible with the hardware infrastructure.

[0005] The present disclosure has been made in consideration of the above problems, and an exemplary purpose thereof is to provide a technology in network function virtualization technology that can improve compatibility between the network functions to be deployed and the hardware infrastructure. [Means for solving the problem]

[0006] A management system according to an exemplary aspect of the present disclosure includes an acquisition means for acquiring information identifying a target virtualized network function, and a determination means for determining a target hardware platform on which to deploy the target virtualized network function by referring to policy information including a policy for the virtualized network function for the hardware platform.

[0007] A management system according to an exemplary aspect of the present disclosure includes an acquisition means for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy for the virtualized network function for the hardware platform, and an execution means for executing a deployment process by referring to the information acquired by the acquisition means.

[0008] A management device according to an exemplary aspect of the present disclosure includes an acquisition means for acquiring information identifying a target virtualized network function, and a determination means for determining a target hardware platform on which to deploy the target virtualized network function by referring to policy information including a policy for the virtualized network function for the hardware platform.

[0009] A management device according to an exemplary aspect of the present disclosure includes an acquisition means for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy for the virtualized network function for the hardware platform, and an execution means for executing a deployment process by referring to the information acquired by the acquisition means.

[0010] A management method according to an exemplary aspect of the present disclosure includes one or more processors obtaining information identifying a target virtualized network function and determining a target hardware platform on which to deploy the target virtualized network function by referencing policy information including a policy for the virtualized network function relative to the hardware platform.

[0011] The information processing device according to each aspect of the present invention may be realized by a computer. In this case, the information processing device program that causes the computer to operate as each part (software element) of the information processing device to realize the information processing device on the computer, and the computer-readable recording medium on which the program is recorded, also fall within the scope of the present invention. [Effects of the Invention]

[0012] According to an exemplary aspect of the present disclosure, an exemplary effect is achieved in network function virtualization technology in that it is possible to improve compatibility between a network function to be deployed and a hardware platform. [Brief explanation of the drawings]

[0013] [Figure 1] 1 is a block diagram illustrating a configuration of a management system according to the present disclosure. [Figure 2] FIG. 1 is a flow diagram showing the flow of a management method according to the present disclosure. [Figure 3] FIG. 2 is a block diagram illustrating a configuration of a management device according to the present disclosure. [Figure 4] 1 is a block diagram illustrating a configuration of a management system according to the present disclosure. [Figure 5] FIG. 1 is a flow diagram showing the flow of a management method according to the present disclosure. [Figure 6] FIG. 2 is a block diagram illustrating a configuration of a management device according to the present disclosure. [Figure 7] 1 is a block diagram illustrating a configuration of a management system according to the present disclosure. [Figure 8] 1 is a block diagram illustrating a configuration of a management system according to the present disclosure. [Figure 9] FIG. 10 is a sequence diagram showing the flow of a management method according to the present disclosure. [Figure 10] FIG. 10 is a diagram for explaining processing by a management system according to the present disclosure. [Figure 11] FIG. 10 is a sequence diagram showing the flow of a management method according to the present disclosure. [Figure 12]FIG. 10 is a sequence diagram showing the flow of a management method according to the present disclosure. [Figure 13] FIG. 1 is a block diagram illustrating a configuration of a computer that functions as a network function according to the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

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

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

[0016] (Overview of Management System 1) First, an overview of a management system 1 according to this exemplary embodiment will be described. As an example, the management system 1 is a system that, in network function virtualization (NFV) technology, performs processing to determine a target hardware platform on which to deploy a target virtualized network function (VNF) by referring to policy information including a policy of the virtualized network function for the hardware platform.

[0017] As will be explained below, the management system 1 Obtain information identifying the target virtualized network function; Determine the target hardware platform on which to deploy the target virtualized network function by referring to policy information including the policy of the virtualized network function for the hardware platform. In the following description, a virtualized network function may be simply referred to as a VNF, and a network function may be simply referred to as an NF (Network Function). In this specification, "deploy" refers, for example, to "place," "deploy," or "construct" a target network function, etc. on a target hardware platform, and make the target network function, etc. available for use. The expression "deploying a virtualized network function" can also be expressed as "instantiation of a virtualized network function." This also applies to the exemplary embodiments described below.

[0018] (Configuration of management system 1) The configuration of a management system 1 according to this exemplary embodiment will be described with reference to Fig. 1. Fig. 1 is a block diagram showing the configuration of the management system 1. As shown in Fig. 1, the management system 1 includes an acquisition unit 11 and a determination unit 12. Here, as shown in Fig. 1, the acquisition unit 11 and the determination unit 12 are connected via a network N. The specific configuration of the network N does not limit this exemplary embodiment, but as an example, a wireless LAN (Local Area Network), a wired LAN, a WAN (Wide Area Network), a public line network, a mobile data communication network, or a combination of these networks can be used.

[0019] (Acquisition part 11) The acquisition unit 11 acquires information for identifying a target virtualized network function. As an example, the acquisition unit 11 acquires an identifier for identifying a virtualized network function. Here, the identifier may be referred to as a VNF identifier (Virtual Network Function ID) or a VNF instance identifier (Virtual Network Function Instance ID), for example.

[0020] As an example, the acquisition unit 11 can be configured to acquire the above identifier from a platform management device or platform management unit that manages the hardware platform in the management system 1, but this does not limit this exemplary embodiment.

[0021] (Decision Unit 12) The determination unit 12 determines the target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including the policy of the virtualized network function for the hardware platform. Here, the policy of the virtualized network function for the hardware platform refers to, for example, the requirements that the virtualized network function requires of the hardware platform. For example, the requirements may be: In the case of the first type of virtual network function, taking into consideration the availability of maintaining connections, it requires the use of multiple different communication ports, or requires the separation of virtual LANs for each sub-interface, In the case of Type 2 virtual network functions, the network requests the reservation of a certain communication bandwidth or the occupancy of a communication port so as not to affect data processing performance. There may be various requirements such as the above. The policy information is, for example, information configured by associating the requirements for each virtualized network function as described above with the type or identifier of the virtualized network function. The determination unit 12 or other means included in the management system 1 can acquire in advance requirements required by multiple virtualized network functions that are candidates for deployment, and create the policy information in advance using the acquired requirements.

[0022] As an example, the determination unit 12 Process 1: Identifying the target virtualized network function by referring to the identifier acquired by the acquisition unit 11; Process 2: Identifying the requirements associated with the identifier or the type of target virtualized network function; Process 3: Among the multiple hardware platforms managed by the management system 1, a hardware platform that satisfies the above requirements is determined as a target hardware platform on which the target virtualized network function is to be deployed. Here, in the above process 3, the determination unit 12 may be configured to refer to information on the specifications of each of the multiple hardware platforms managed by the management system 1, and compare the requirements with the specifications to identify a hardware platform that satisfies the requirements. However, this does not limit the present exemplary embodiment.

[0023] Further, as information for identifying the target hardware platform determined by the determination unit 12, - ID of the relevant hardware platform - Type of target hardware platform However, this does not limit the present exemplary embodiment. For example, the information specifying the target hardware platform determined by the determination unit 12 is supplied to an platform management device or platform management unit that manages the hardware platform in the management system 1, and is referenced in the process of deploying the target virtualized network function.

[0024] The above-mentioned "hardware platform" includes, as an example, at least one of a PC, a server, storage, a network, and various interfaces, but these examples do not limit this exemplary embodiment.

[0025] (Effects of Management System 1) As described above, in the management system 1, Obtain information identifying the target virtualized network function; Determine the target hardware platform on which to deploy the target virtualized network function by referring to policy information including the policy of the virtualized network function for the hardware platform. The following configuration is adopted.

[0026] In this way, the management system 1 references policy information including a policy for a virtualized network function for a hardware platform to determine a target hardware platform on which to deploy the target virtualized network function. Therefore, a hardware platform that is compatible with the target virtualized network function can be determined as the hardware platform on which the target virtualized network function is deployed. Therefore, the management system 1 configured as described above can improve the compatibility between a network function to be deployed and a hardware platform in network function virtualization technology.

[0027] (Flow of management method S1) Next, the flow of the management method S1 according to this exemplary embodiment will be described with reference to Fig. 2. Fig. 2 is a flow diagram showing the flow of the management method S1. As shown in Fig. 2, the management method S1 includes a process (step) S11 of acquiring information that identifies a target virtualized network function, and a process (step) S12 of referring to policy information to determine a target hardware platform on which to deploy the target virtualized network function.

[0028] (Step S11) In step S11, the acquisition unit 11 of the management system 1 acquires information for identifying a target virtualized network function. The specific processing by the acquisition unit 11 has been described above, and therefore a description thereof will be omitted here.

[0029] (Step S12) Next, in step S12, the determination unit 12 of the management system 1 refers to policy information including a policy of a virtualized network function for a hardware platform to determine a target hardware platform on which to deploy the target virtualized network function. The specific processing by the determination unit 12 has been described above, and therefore a description thereof will be omitted here.

[0030] (Effect of management method S1) As described above, in the management method S1, Obtain information identifying the target virtualized network function; Determine the target hardware platform on which to deploy the target virtualized network function by referring to policy information including the policy of the virtualized network function for the hardware platform. Therefore, the management method S1 has the same effect as the management system 1.

[0031] (Configuration of management device 100) Next, the configuration of the management device 100 according to this exemplary embodiment will be described with reference to Fig. 3. Fig. 3 is a block diagram showing the configuration of the management device 100. As shown in Fig. 3, the management device 100 includes an acquisition unit 11 and a determination unit 12.

[0032] (Acquisition part 11) The acquisition unit 11 acquires information for identifying a target virtualized network function. The specific processing by the acquisition unit 11 has been described above, and therefore a description thereof will be omitted here.

[0033] (Decision Unit 12) The determination unit 12 determines the target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including the policy of the virtualized network function for the hardware platform. The specific processing by the determination unit 12 has been described above, and therefore a description thereof will be omitted here.

[0034] (Effects of the management device 100) As described above, in the management device 100, Obtain information identifying the target virtualized network function; Determine the target hardware platform on which to deploy the target virtualized network function by referring to policy information including the policy of the virtualized network function for the hardware platform. Therefore, the management device 100 can achieve the same effects as the management system 1.

[0035] (Overview of Management System 2) Next, an overview of the management system 2 according to this exemplary embodiment will be described. As an example, in network function virtualization (NFV) technology, the management system 2 is a system that acquires information that specifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform, and executes a deployment process by referring to the acquired information.

[0036] As will be explained below, the management system 2 acquiring information specifying a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy for the virtualized network function for the hardware platform; Execute the deployment process by referencing the acquired information The following process is performed.

[0037] (Configuration of management system 2) The configuration of the management system 2 according to this exemplary embodiment will be described with reference to FIG. 4. FIG. 4 is a block diagram showing the configuration of the management system 2. As shown in FIG. 4, the management system 2 includes an acquisition unit 21 and an execution unit 22. Here, as shown in FIG. 1, the acquisition unit 21 and the execution unit 22 are connected via a network N. The specific configuration of the network N does not limit this exemplary embodiment, but as an example, a wireless local area network (LAN), a wired LAN, a wide area network (WAN), a public line network, a mobile data communication network, or a combination of these networks can be used. Note that the management system 2 may be implemented in cooperation with the management system 1, or may be configured to include at least some of the components included in the management system 1.

[0038] (Acquisition part 21) The acquisition unit 21 acquires information that identifies the hardware platform on which the target virtualized network function is to be deployed, and that is determined by referring to policy information that includes the policy of the virtualized network function for the hardware platform. As an example, the acquisition unit 21 acquires information for identifying the target hardware platform determined by the determination unit 12 described in the management system 1. For example, the acquisition unit 21 acquires the following as the information for identifying the target hardware platform: The ID of the applicable hardware platform, or - Type of target hardware platform The policy information has been explained in the management system 1, so a duplicate explanation will be omitted.

[0039] The information obtained by the obtaining unit 21 may be obtained as a response to an inquiry from the obtaining unit 21 to the determining unit 12. For example, the obtaining unit 21 may Requesting the determination unit 12 to provide information identifying the hardware platform on which the target virtualized network function is to be deployed; In response to such request, - The ID of the above target hardware platform, or -Type of hardware platform mentioned above However, this is not a limitation of the present exemplary embodiment.

[0040] (Executive Department 22) The execution unit 22 executes a deployment process by referring to the information acquired by the acquisition unit 21. More specifically, the execution unit 22 executes a deployment process by referring to the information acquired by the acquisition unit 21. - The ID of the above target hardware platform, or -Type of hardware platform mentioned above and the like, and executes a process of deploying the target virtualized network function to the hardware platform specified by the information.

[0041] (Effects of Management System 2) As described above, in the management system 2, Acquiring information that identifies a hardware platform on which the target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy for the virtualized network function for the hardware platform; Execute the deployment process by referencing the acquired information The following configuration is adopted.

[0042] In this way, the management system 2 executes the deployment process by referring to information that identifies the hardware platform on which the target virtualized network function is to be deployed, the information being determined by referring to policy information including the policy of the virtualized network function for the hardware platform. This allows the target virtualized network function to be deployed on a hardware platform that is compatible with the target virtualized network function. Therefore, the management system 1 configured as described above can improve the compatibility between the network function to be deployed and the hardware platform in network function virtualization technology.

[0043] (Flow of management method S2) Next, the flow of the management method S2 according to this exemplary embodiment will be described with reference to Fig. 5. Fig. 5 is a flow diagram showing the flow of the management method S2. As shown in Fig. 5, the management method S2 includes (step) S21 of acquiring information that identifies the determined hardware platform by referring to policy information, and (step) S22 of executing a deployment process by referring to the acquired information.

[0044] (Step S21) In step S21, the acquisition unit 21 of the management system 2 acquires information that identifies the hardware platform on which the target virtualized network function is to be deployed, and that is determined by referring to policy information including the policy of the virtualized network function for the hardware platform. The specific processing by the acquisition unit 21 has been described above, and therefore a description thereof will be omitted here.

[0045] (Step S22) Subsequently, in step S22, the execution unit 22 of the management system 2 executes a deployment process by referring to the information acquired by the acquisition unit 21. The specific process by the execution unit 22 has been described above, and therefore will not be described here.

[0046] (Effect of management method 2) As described above, in the management system 2, Acquiring information that identifies a hardware platform on which the target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy for the virtualized network function for the hardware platform; Execute the deployment process by referencing the acquired information Therefore, the management method S2 has the same effect as the management system 2.

[0047] (Configuration of management device 200) Next, the configuration of the management device 200 according to this exemplary embodiment will be described with reference to Fig. 6. Fig. 6 is a block diagram showing the configuration of the management device 200. As shown in Fig. 6, the management device 200 includes an acquisition unit 21 and an execution unit 22.

[0048] (Acquisition part 21) The acquisition unit 21 acquires information that identifies the hardware platform on which the target virtualized network function is to be deployed, and that is determined by referring to policy information including the policy of the virtualized network function for the hardware platform. The specific processing by the acquisition unit 21 has been described above, and therefore a description thereof will be omitted here.

[0049] (Executive Department 22) The execution unit 22 executes a deployment process by referring to the information acquired by the acquisition unit 21. The specific process performed by the execution unit 22 has been described above, and therefore a description thereof will be omitted here.

[0050] (Effects of the management device 200) As described above, in the management device 200, Acquiring information that identifies a hardware platform on which the target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy for the virtualized network function for the hardware platform; Execute the deployment process by referencing the acquired information Therefore, the management device 200 can achieve the same effects as the management system 2.

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

[0052] (Configuration of management system 1A) The configuration of a management system 1A according to this exemplary embodiment will be described with reference to FIG. 7. FIG. 4 is a block diagram showing the configuration of the management system 1A. As shown in FIG. 7, the management system 1A includes, as an example, a first management device 100A, a second management device 20, a first server 51, and a second server 52. Here, as shown in FIG. 7, the first management device 100A, the second management device 20, the first server 51, and the second server 52 are connected via a network N. The specific configuration of the network N does not limit this exemplary embodiment, but as an example, a wireless local area network (LAN), a wired LAN, a wide area network (WAN), a public line network, a mobile data communication network, or a combination of these networks can be used.

[0053] 7, the units included in the first management device 100A may be configured to be distributed among multiple physical servers. Similarly, the units included in the second management device 20 may be configured to be distributed among multiple physical servers. Furthermore, at least some of the units included in the first management device 100A may be configured to be included in the second management device 20, and at least some of the units included in the second management device 20 may be configured to be included in the first management device 100A.

[0054] (First management device 100A) 7, the first management device 100A includes an acquisition unit 11, a determination unit 12, an allocation unit 13, and a storage unit 14. Here, the acquisition unit 11 and the determination unit 12 have the same functions as the configurations described in exemplary embodiment 1. In the following, the description of the contents that have already been described may be omitted as appropriate.

[0055] (Acquisition part 11) The acquisition unit 11 acquires information for identifying a target virtualized network function. As an example, the acquisition unit 11 acquires an identifier for identifying a virtualized network function. Here, as described in the exemplary embodiment 1, the identifier may be referred to as a VNF identifier (Virtual Network Function ID) or a VNF instance identifier (Virtual Network Function Instance ID), for example.

[0056] As an example, the acquisition unit 11 can be configured to acquire the identifier from the infrastructure management unit 200A included in the second management device 20, but this does not limit the present exemplary embodiment.

[0057] (Decision Unit 12) The determination unit 12 determines a target hardware platform on which the target virtualized network function is to be deployed, by referring to policy information including a policy of the virtualized network function for the hardware platform. Here, the policy of the virtualized network function for the hardware platform refers to, for example, requirements that the virtualized network function requires of the hardware platform, as described in the exemplary embodiment 1. For example, the requirements may be: In the case of the first type of virtual network function, taking into consideration the availability of maintaining connections, it requires the use of multiple different communication ports, or requires the separation of virtual LANs for each sub-interface, In the case of Type 2 virtual network functions, the network requests the reservation of a certain communication bandwidth or the occupancy of a communication port so as not to affect data processing performance. More specifically, when the management system 1A is used as part of a mobile communication network, for example, as a core network that constitutes the mobile communication network, the above requirements are as follows: In the case of virtualized network functions for control systems, for example, in the case of virtualized network functions related to the C-Plane in the 5G standard, taking into account the availability of session maintenance, it is necessary to require the use of multiple different NIC (Network Interface Card) ports, or to separate virtual LANs for each sub-interface. In the case of virtualized network functions for user data processing, for example, virtualized network functions related to the U-Plane in the 5G standard, the network may request the reservation of a certain communication bandwidth or the exclusive use of a NIC port to prevent an impact on data processing performance. There can be a variety of requirements.

[0058] The policy information is information configured by associating the requirements for each virtualized network function as described above with the type or identifier of the virtualized network function. The determination unit 12, or the function management unit 230 or the infrastructure management unit 200A described below, can acquire or identify in advance the requirements required by multiple virtualized network functions that are candidates for deployment, and create the policy information in advance using the acquired or identified requirements.

[0059] As described in the first exemplary embodiment, the determination unit 12, for example, Process 1: Identifying the target virtualized network function by referring to the identifier acquired by the acquisition unit 11; Process 2: Identifying the requirements associated with the identifier or the type of target virtualized network function; Process 3: Among the multiple hardware platforms managed by the management system 1, a hardware platform that satisfies the above requirements is determined as a target hardware platform on which the target virtualized network function is to be deployed. Here, in the above process 3, the determination unit 12 performs the following process. Refer to information about the specifications of each of the multiple hardware platforms managed by the platform management unit 200A (described later), Identify the hardware platform that meets the above requirements by comparing them with the relevant specifications. However, this is not a limitation of the present exemplary embodiment.

[0060] Further, as information for identifying the target hardware platform determined by the determination unit 12, - ID of the relevant hardware platform - Type of target hardware platform However, this does not limit the present exemplary embodiment. For example, the information specifying the target hardware platform determined by the determination unit 12 is provided to a platform management unit 200A (described later) and is referenced in the process of deploying the target virtualized network function.

[0061] In this way, the determination unit 12 A hardware platform that satisfies the policy information regarding the target virtualized network function is determined as the target hardware platform. However, the process by the determination unit 12 is not limited to this. For example, the determination unit 12 performs the following process: If there is no hardware infrastructure that satisfies the policy information regarding the target virtualized network function, generating a virtual hardware element that satisfies the policy information. The following processing may be performed.

[0062] As an example, when there is no hardware platform that satisfies the policy information related to the target virtualized network function, the determination unit 12 determines, as a virtual hardware element that satisfies the policy information, Virtualized Function (VF) Sub-IF (Sub-Interface) The determination unit 12 may create a virtual IF as a Sub-IF that satisfies the requirements and associate it with the target virtualized network function. More specifically, when the policy information includes requirements related to a Sub-IF but no hardware infrastructure that satisfies the requirements exists, the determination unit 12 may create a virtual IF as a Sub-IF that satisfies the requirements and assign the created virtual IF to the target virtualized network function. Here, an example of the virtual IF assignment process is to assign a VLAN (Virtual Local Area Network) ID. By performing the above-mentioned process, the determination unit 12 can provide a more suitable infrastructure environment for the target virtualized network function.

[0063] (Allocation Unit 13) The allocation unit 13 executes a dynamic IP address allocation process as an IP address for the secondary network in the target virtualized network function. As an example, when some kind of failure occurs in the primary network in a certain virtualized network function, the allocation unit 13 executes a dynamic IP address allocation process as an IP address for the secondary network in the target virtualized network function that is newly started as a replacement for the virtualized network function. By the allocation unit 13 executing such a process, it is possible to prevent a situation from occurring in which the IP address for the secondary network assigned to a certain virtualized network function and the IP address for the secondary network in the target virtualized network function overlap.

[0064] (Storage unit 14) The storage unit 14 stores various data derived by the first management device 100A and various data referenced by the first management device 100A. The storage unit 14 may also be configured to store various data derived or referenced by other units included in the management system 1A. The above-mentioned policy information can be cited as an example of data stored in the storage unit 14. Details of the policy information have been described above, so a detailed description will be omitted here.

[0065] (Second management device 20) As shown in FIG. 7, the second management apparatus 20 includes an overall management unit 210, a function management unit 230, and an infrastructure management unit 200A.

[0066] (General Management Department 210) The overall management unit 210 performs overall management of the entire management system 1A. As an example of processing by the overall management unit 210, Management of one or more network functions included in the management system 1A and one or more hardware platforms included in the management system 1A As an example, the general management unit 210 may: By issuing instructions to the function management unit 230, the management system 1A manages one or more network functions included in the management system 1A, By issuing instructions to the platform management unit 200A, the management system 1A manages one or more hardware platforms included in the management system 1A.

[0067] The overall management unit 210 can be realized as an orchestrator in network function virtualization technology, for example, but this example does not limit the present exemplary embodiment. Also, the orchestrator may be called an NFV orchestrator (NFVO: Network Function Virtualization Orchestrator), for example, but this name does not limit the present exemplary embodiment.

[0068] (Infrastructure Management Unit 200A) The platform management unit 200A manages one or more hardware platforms included in the management system 1A. As an example, the platform management unit 200A: Acquires a deployment request from the function management unit 230 to deploy the target VNF; Determine the hardware infrastructure on which to deploy the target VNFs, Deploy the above target VNFs on the selected hardware platform. The following process is performed.

[0069] 8, the platform management unit 200A includes, as an example, an acquisition unit 21 and an execution unit 22. Here, the acquisition unit 21 and the execution unit 22 have the same functions as the configurations described in exemplary embodiment 1. In the following, the description of the contents that have already been described may be omitted as appropriate.

[0070] (Acquisition part 21) The acquisition unit 21 acquires information that identifies the hardware platform on which the target virtualized network function is to be deployed, and that is determined by referring to policy information that includes the policy of the virtualized network function for the hardware platform.

[0071] As an example, the acquisition unit 21 acquires information for identifying the target hardware platform determined by the determination unit 12 included in the first management device 100A. For example, the acquisition unit 21 acquires the following as the information for identifying the target hardware platform: The ID of the applicable hardware platform, or - Type of target hardware platform The policy information has been described above, so a duplicated explanation will be omitted.

[0072] The information obtained by the obtaining unit 21 may be obtained as a response to an inquiry from the obtaining unit 21 to the determining unit 12 included in the first management device 100A. For example, the obtaining unit 21 may Requesting the determination unit 12 to provide information identifying the hardware platform on which the target virtualized network function is to be deployed; In response to such request, - The ID of the above target hardware platform, or -Type of hardware platform mentioned above However, this is not a limitation of the present exemplary embodiment.

[0073] (Executive Department 22) The execution unit 22 executes a deployment process by referring to the information acquired by the acquisition unit 21. More specifically, the execution unit 22 executes a deployment process by referring to the information acquired by the acquisition unit 21. - The ID of the above target hardware platform, or -Type of hardware platform mentioned above and the like, and executes a process of deploying the target virtualized network function to the hardware platform specified by the information.

[0074] The execution unit 22: the target virtualized network function or one or more management units included in the target virtualized network function; one or more hardware elements included in the hardware infrastructure; The deployment process may be executed by further referencing correspondence information indicating the correspondence between the management unit 200A and the management system 1A. Here, the management unit 200A may be referred to as a POD (Profile Object Attachment), for example, but this term does not limit the present exemplary embodiment. The correspondence information may be an example of information referred to as a Network Attachment Definition (NAD), for example, but this term does not limit the present exemplary embodiment. The execution unit 22 may be configured to refer to the correspondence information provided by a storage unit of the infrastructure management unit 200A or another NF included in the management system 1A, for example, but this does not limit the present exemplary embodiment. The processing by the execution unit 22 will be described in more detail in the application example described below.

[0075] In this exemplary embodiment, the hardware infrastructure is referred to as CIS (Container Infrastructure Service) and the infrastructure management unit 200A is sometimes referred to as CISM (CIS Manager), but these terms do not limit this exemplary embodiment.

[0076] (Functional Management Department 230) The function management unit 230 manages one or more VNFs included in the management system 1A. Here, the VNFs included in the management system 1A include: VNFs deployed on the hardware infrastructure of management system 1A VNFs that are not yet deployed on the hardware infrastructure of management system 1A but are candidates for deployment The function management unit 230 includes, for example, - Determine the VNF to be deployed based on instructions from the user or information obtained from other VNFs, etc. Send a deployment request to the infrastructure management unit 200A to deploy the target VNF. The following process is performed.

[0077] As shown in FIG. 8, the function management unit 230 includes an inquiry unit 31 and a decision unit 32, for example.

[0078] (Inquiry Section 31) The inquiry unit 31 inquires whether a candidate IP address for the secondary network in the target virtualized network function is already in use. In the management system 1A, a VIM (Virtualized Infrastructure Manager) that controls the virtualized infrastructure is queried to determine whether or not a candidate IP address for the secondary network in the target virtualized network function is already in use. Obtain a response to the inquiry from the VIM.

[0079] (Decision unit 32) The determination unit 32 determines the IP address for the secondary network by referring to the response to the inquiry. The candidate for the IP address is not already in use On the other hand, if the response to the inquiry indicates that the IP address candidate is an IP address for the secondary network in the target virtualized network function, the determination unit 32 determines the IP address candidate as an IP address for the secondary network in the target virtualized network function. The candidate for the IP address is already in use If so, the determining unit 32 replaces the candidate for the IP address with another candidate, and then causes the querying unit 31 to make the query again.

[0080] The processing by the inquiry unit 31 and the determination unit 32 may be performed at the following timing, for example. That is, when some kind of failure occurs in the primary network of a certain virtualized network function, the inquiry unit 31 sets a candidate IP address for the secondary network of the target virtualized network function that is newly started as a replacement for the virtualized network function, and inquires of the VIM whether the candidate is already in use. If the candidate is not already in use, the determination unit 32 sets the candidate as the IP address for the secondary network.

[0081] By having the inquiry unit 31 and the determination unit 32 perform such processing, it is possible to prevent a situation in which an IP address for a secondary network assigned to a certain virtualized network function overlaps with an IP address for a secondary network in the target virtualized network function.

[0082] In this exemplary embodiment, the function management unit 230 may be referred to as a VNFM (Virtualized Network Function Manager), but this term does not limit this exemplary embodiment.

[0083] (First server 51, second server 52) The first server 51 and the second server 52 shown in Fig. 7 are an example of a hardware platform managed by the platform management unit 200A described above, and are also an example of the CIS described above. In the example shown in Fig. 7, the platform management unit 200A deploys VNF1, VNF2, ..., etc. on the first server 51, and deploys VNF3, ..., etc. on the second server 52.

[0084] <Application example> An application example of the management system according to this exemplary embodiment will be specifically described below with reference to Figures 8 to 12. In this application example, the functions of the management system 1B may be described using terms used in Kubernetes (registered trademark), but these terms do not limit this application example. Figure 8 is a block diagram showing the configuration of the management system 1B, which is an application example of the management system 1A according to this exemplary embodiment.

[0085] As shown in FIG. 8, the management system 1B ·NFVO(Network Function Virtualization Orchestrator) ·EMS(Element Management System) ·VIM(Virtualized Infrastructure Manager) ·CISM(Container Infrastructure Service Manager) ·VNFM(Virtualized Network Function Manager) · PaaS (Platform as a Service) ·CIM#1(Container Infrastructure Service #1) ·CIM#2(Container Infrastructure Service #2) It is equipped with:

[0086] Here, the NFVO is an example of the above-mentioned overall management unit 210, and therefore the NFVO may be written as NFVO210. Furthermore, the CISM is an example of the above-mentioned infrastructure management unit 200A, and therefore the CISM may be written as CISM200A. Furthermore, the VNFM is an example of the above-mentioned function management unit 230, and therefore the VNFM may be written as VNFM230.

[0087] Furthermore, PaaS provides a platform for the management system 1B, and as an example, provides applications, database functions, etc. Since PaaS is an example of the above-mentioned first management device 100A, PaaS is sometimes referred to as PaaS100A. CIS#1 and CIS#2 are examples of the above-mentioned first server 51 and second server 52, respectively.

[0088] The EMS manages various elements included in the management system 1B. As an example, the EMS manages IP addresses of the VNFs included in the management system 1B. More specifically, the EMS manages secondary IP addresses of the VNFs included in the management system 1B. The VIM controls the virtualized infrastructure in the management system 1A. For example, the VIM receiving a query from the VNFM as to whether a candidate IP address for a secondary network in the target virtualized network function is in use; Check whether the candidate has been used or not, - Send the confirmation result to the VNFM as a response to the above inquiry. The following process is performed.

[0089] (Processing flow example 1) FIG. 9 is a sequence diagram showing a first example of the flow of processing by the management system 1B.

[0090] (Step 5.1) First, in step 5.1, the NFVO requests the CISM to configure a secondary container cluster network. Here, the NFVO requests the CISM to configure a secondary container cluster network, for example. -Information that the IP address type is DHCP (Dynamic Host Configuration Protocol), and NetworkNodePolicy Here, the DHCP type IP address is an example of the dynamic IP address described above, and NetworkNodePolicy is an example of the policy information described above.

[0091] (Step 5.2) Next, in step 5.2, CISM requests the PaaS to generate an object containing NetworkNodePolicy. This object is sometimes called a NetworkNodePolicy object or the policy information mentioned above. Upon receiving the above request from CISM, the PaaS: Decide whether to create an object containing a NetworkNodePolicy, If you decide to create one, create an object containing the NetworkNodePolicy. Sends a response to the above request to CISM. Here, the response to the request includes the result (OK / NG) of the request. The NetworkNodePolicy generated by the PaaS is stored in the storage unit 14 described above, for example.

[0092] (Step 18.1) Next, in step 18.1, the VNFM requests the CISM to deploy the target VNF.

[0093] (Step 18.2) In step S18.2, the CISM receives the deployment request from the VNFM and queries the PaaS for the NetworkNodePolicy. Refer to the NetworkNodePolicy to determine the server suitable for deploying the target VNF, - Sends server information to CISM to identify the determined server The process in this step is an example of the process performed by the acquisition unit 11 and the determination unit 12 described above.

[0094] In addition, in this step, if there is no hardware infrastructure that satisfies the NetworkNodePolicy for the target VNF, the PaaS selects a virtual hardware element that satisfies the NetworkNodePolicy as follows: Virtualized Function (VF) Sub-IF (Sub-Interface) and so on, and associate it with the target VNF. More specifically, if the NetworkNodePolicy includes requirements related to a Sub-IF but no hardware infrastructure that satisfies the requirements exists, the PaaS may be configured to create a virtual IF as a Sub-IF that satisfies the requirements and assign the created virtual IF to the target VNF. Here, an example of the virtual IF assignment process is to assign a VLAN (Virtual Local Area Network) ID. By performing the above process, the PaaS can provide a more suitable infrastructure environment for the target virtualized network function.

[0095] (Step 18.3) In step 18.3, the CISM, having acquired the server information, determines the server indicated by the server information as the server for deploying the target VNF.

[0096] (Step 18.4) Then, in step 18.4, the CISM deploys the target VNF ​​to the determined server.

[0097] In addition, in the above steps 18.2 and 18.3, the PaaS and CISM may perform the following instead of or in addition to the above processes: In step 18.2, the PaaS provides the NetworkNodePolicy containing the policy for the target VNF ​​to the CISM. In step 18.3, CISM refers to the NetworkNodePolicy to determine the appropriate server for deploying the target VNF. The processes in steps 18.3 and 18.4 are examples of the processes performed by the acquisition unit 21 and the execution unit 22 described above.

[0098] (Step 18.5) In addition, the PaaS assigns a dynamic IP address to the VNF deployed by the CISM. This processing is an example of the processing performed by the assignment unit 13 described above.

[0099] (Example of deployment process referencing policy information) 10 is a diagram illustrating an example of the deployment process executed by the CISM in step 18.4, which refers to the NetworkNodePolicy and the NAD (Network Attachment Definition). NetworkNodePolicy:AAA, which is policy information for VNF#1 defined as Namespace:AAA; NAD-A, NAD-B, and NAD-C are NADs related to VNF#1 Refer to the following to deploy VNF#1. NetworkNodePolicy:AAA, which is policy information for VNF#2 defined as Namespace:BBB; NAD-D, NAD-E, which are NADs related to VNF#2 The deployment process of VNF#2 is performed by referring to the above. Here, NAD-A, NAD-B, NAD-C, NAD-D, and NAD-E are examples of the above-mentioned correspondence information. More specifically, in this example, each NAD is a file that defines the association between a Namespace and a type of NIC port (a port of a Network Interface Card). Here, the type of NIC port is SR-IOV (Single Root I / O Virtualization) VF (Virtualized Function) and Sub-IF, etc. In this example, specifically, NAD-A, NAD-B, and NAD-C are NADs related to Pod1, Pod2, and Pod3, respectively, provided by VNF#1, and NAD-D and NAD-E are NADs related to Pod4 and Pod5, respectively, provided by VNF#2.

[0100] In the example shown in FIG. 10, more specifically, NetworkNodePolicy: AAA is linked to NAD-A, NAD-B, and NAD-C. - In Rule 1, NAD-A and B (NADs used by Pod 2) use different NIC ports. However, they must use the same VLAN ID 1000. ·NetworkNodePoilicy: Linking BBB and NAD-E, - Regulation 2 stipulates that NAD-E (the NAD used by Pod 4) will occupy and use a certain NIC port (SR-IOV compatible).

[0101] As described above, the CISM refers to the policy information and the NAD to determine the correspondence between each POD and one or more hardware elements included in the hardware infrastructure (CIS), and executes the deployment process of the VNF including each POD based on the determination. Figure 10 also shows the result of the deployment process. As shown in Figure 10, Pod2 uses Port 3 of NIC#1 and Port 3 of NIC#2 based on rule 1 above. However, they use the same VLAN ID -1000. It has been shown that Pod 4 will occupy and use Port 2 of NIC#1 based on rule 2 above. It has been shown that:

[0102] 10, VNF#1 is a virtualized network function of a control system, more specifically, a virtualized network function related to the C-Plane in the 5G standard. In this case, taking into consideration availability related to session maintenance, it is preferable to request the use of multiple different NIC (Network Interface Card) ports or to request the separation of virtual LANs for each sub-interface.

[0103] 10, VNF#2 is a virtualized network function of a user data processing system, and is a virtualized network function related to the U-Plane in the 5G standard. In this case, it is preferable to request the reservation of a predetermined communication bandwidth in the network or the occupancy of a NIC port so as not to affect data processing performance.

[0104] 10, the CISM according to this example can deploy each VNF to suitably satisfy these requirements by referring to the NetworkNodePolicy and the NAD. Therefore, it is possible to suitably improve the compatibility between the network function to be deployed and the hardware infrastructure.

[0105] (Processing flow example 2) FIG. 11 is a sequence diagram showing a second example of the flow of processing by the management system 1B.

[0106] (Step 5-1) In step 5-1, the NFVO requests the CISM to configure a secondary container cluster network. The request includes the following information about the secondary container cluster network: IP address type: DHCP mode CIS interface name:XXX Secondary Network Name:XXX ·IP Address range:10.0.0.0 / 24 It includes various information such as:

[0107] (Step 5-2) In step 5-2, the CISM provides information about the secondary container cluster network to the PaaS. The information provided to the PaaS in this step may include at least some of the information that the CISM obtained from the NFVO in step 5-1. The information obtained by the PaaS in this step is, for example, referenced when generating the policy information described above.

[0108] (Step 17) In step 17, the VNFM performs the following in accordance with the information "Mapping to NFV data models": Inject the secondary network name, which is a parameter of NetworkAttachmentDefinition. This step is performed, for example, in accordance with 6.2.2.1 of ETSI GS NFV-SOL 018.

[0109] (Step 18-1) In step 18-1, the VNFM requests the CISM to generate VNF#1.

[0110] (Step 18-2) In step 18-2, the CISM requests the PaaS to allocate an IP address.

[0111] (Step 18-3) In step 18-3, the PaaS assigns an IP address to the VNF#1. The IP address is, for example, an IP address for the secondary network of the VNF#1. The IP address assigned in this step is a dynamic IP address.

[0112] (Step 18-4) In step 18-4, the PaaS notifies the VNFM of the IP address for the secondary network of VNF#1.

[0113] (Step 18-5) In step 18-5, the VNFM notifies the DMS of the IP address for the secondary network of VNF#1.

[0114] (Step 18-6) In step 18-6, the EMS provides VNF#2 with an IP address for the secondary network of VNF#1.

[0115] In the process flow according to this example, as described above, the PaaS dynamically allocates an IP address as an IP address for the secondary network of VNF#1. Therefore, when a failure occurs in the primary network of a certain VNF and the PaaS starts up the VNF#1 as an alternative to the VNF, the PaaS executes a dynamic IP address allocation process as an IP address for the secondary network of the VNF#1.

[0116] By performing the above-described processing, the PaaS can prevent a situation in which the secondary network IP address assigned to a certain VNF overlaps with the secondary network IP address of VNF#1, which is a replacement for that VNF.

[0117] (Processing flow example 3) FIG. 12 is a sequence diagram showing a third example of the flow of processing by the management system 1B.

[0118] (Step 17) In step 17, the VNFM performs the following in accordance with the information "Mapping to NFV data models": Inject the secondary network name, which is a parameter of NetworkAttachmentDefinition. This step is performed, for example, in accordance with 6.2.2.1 of ETSI GS NFV-SOL 018.

[0119] (Step 17-1) In step 17-1, the VNFM requests the VIM to check whether the IP address to be allocated is already in use.

[0120] (Step 17-2) In step 17-2, the VIM checks whether the IP address to be allocated is already in use.

[0121] (Step 17-3) In step 17-3, the VIM sends the confirmation result to the VNFM.

[0122] (Step 18) In step 18, the CISM is requested to create VNF#1 using an IP address that is to be allocated and that has been confirmed to be unused.

[0123] In the process flow according to this example, as described above, the VNFM: - Request VIM to check whether the IP address to be assigned is already in use, Request CISM to generate VNF#1 using an IP address that is confirmed to be unused. The following process is performed.

[0124] Therefore, when a failure occurs in the primary network of a certain VNF, in the case where the PaaS starts the above VNF#1 as a substitute for the VNF, -Confirm in advance whether the IP address to be allocated as the IP address for the secondary network of the above VNF#1 is already in use, Generate VNF#1 using an IP address that is confirmed to be unused. This process prevents the occurrence of a situation in which the secondary network IP address assigned to a certain VNF overlaps with the secondary network IP address of VNF#1, which is a replacement for that VNF.

[0125] (Advantages of processing related to application examples) The management system 1B that executes the above-described process performs instantiation as the deployment process to create a container-based VNF application, for example. - Deploying the system by referring to policy information and NAD. IP address assignment using DHCP or assignment of an IP address that is confirmed to be unused This has the advantage of automating the local health processing. It also has the advantage of simplifying data management because it eliminates the need to manage individual IP addresses and statically maps VNF information and server IF information.

[0126] [Software implementation example] Some or all of the functions of each component (particularly, the acquisition unit 11, the determination unit 12, the acquisition unit 21, and the execution unit 22) of the management systems 1, 1A, and 1B may be realized by hardware such as an integrated circuit (IC chip) (i.e., realized as an individual device), or by software (i.e., realized as an instance deployed individually or in a distributed manner on one or more devices (physical servers)).

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

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

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

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

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

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

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

[0134] (Appendix A1) an acquisition means for acquiring information identifying a target virtualized network function; a determining means for determining a target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including a policy of the virtualized network function for the hardware platform; A management system that includes:

[0135] (Appendix A2) The determining means determining a hardware platform that satisfies the policy information related to the target virtualized network function as the target hardware platform; If there is no hardware infrastructure that satisfies the policy information regarding the target virtualized network function, a virtual hardware element that satisfies the policy information is generated. The management system described in Appendix A1.

[0136] (Appendix A3) a deployment means for deploying the target virtualized network function on the hardware platform determined by the determination means; It also has The management system described in Appendix A2.

[0137] (Appendix A4) The network device further includes an allocation unit that executes a dynamic IP address allocation process as an IP address for a secondary network in the target virtualized network function. 1. The management system according to any one of Appendices A1 to A3.

[0138] (Appendix A5) an acquisition means for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform; an execution means for executing a deployment process by referring to the information acquired by the acquisition means; A management system that includes:

[0139] (Appendix A6) The execution means the target virtualized network function or one or more management units included in the target virtualized network function; One or more hardware elements included in the hardware infrastructure; and executes the deployment process by further referring to correspondence information indicating the correspondence between the The management system described in Appendix A5.

[0140] (Appendix A7) an inquiry means for inquiring whether a candidate IP address for a secondary network in the target virtualized network function is already in use; a determination means for determining an IP address for the secondary network by referring to a response to the inquiry; Further comprising a management system according to appendix A5 or A6.

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

[0142] (Appendix B1) an acquisition means for acquiring information identifying a target virtualized network function; a determining means for determining a target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including a policy of the virtualized network function for the hardware platform; A management device comprising:

[0143] (Appendix B2) The determining means determining a hardware platform that satisfies the policy information related to the target virtualized network function as the target hardware platform; If there is no hardware infrastructure that satisfies the policy information regarding the target virtualized network function, a virtual hardware element that satisfies the policy information is generated. 10. The management device according to claim 8, wherein the management device is a device for managing a plurality of

[0144] (Appendix B3) a deployment means for deploying the target virtualized network function on the hardware platform determined by the determination means; It also has 2. The management device according to claim B2.

[0145] (Appendix B4) The network device further includes an allocation unit that executes a dynamic IP address allocation process as an IP address for a secondary network in the target virtualized network function. 2. The management device according to claim 1, wherein the management device is a device for managing a plurality of data streams.

[0146] (Appendix B5) an acquisition means for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform; an execution means for executing a deployment process by referring to the information acquired by the acquisition means; A management device comprising:

[0147] (Appendix B6) The execution means the target virtualized network function or one or more management units included in the target virtualized network function; One or more hardware elements included in the hardware infrastructure; and executes the deployment process by further referring to correspondence information indicating the correspondence between the 2. The management device according to claim B5.

[0148] (Appendix B7) an inquiry means for inquiring whether a candidate IP address for a secondary network in the target virtualized network function is already in use; a determination means for determining an IP address for the secondary network by referring to a response to the inquiry; The management device according to Appendix B5 or B6 further comprises:

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

[0150] (Appendix C1) one or more processors obtaining information identifying a target virtualized network function; determining a target hardware platform on which to deploy the target virtualized network function by referring to policy information including a policy of the virtualized network function for the hardware platform; A management method that includes:

[0151] (Appendix C2) The determining step comprises: determining a hardware platform that satisfies the policy information related to the target virtualized network function as the target hardware platform; and generating a virtual hardware element that satisfies the policy information when a hardware infrastructure that satisfies the policy information regarding the target virtualized network function does not exist. Control method described in Appendix C1.

[0152] (Appendix C3) Deploying the target virtualized network function on the determined hardware infrastructure. It further includes Management method described in Appendix C2.

[0153] (Appendix C4) and performing a dynamic IP address allocation process as an IP address for a secondary network in the target virtualized network function. A management method according to any one of Appendices C1 to C3.

[0154] (Appendix C5) acquiring information specifying a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform; executing a deployment process by referring to the information acquired by the acquisition means; A management method that includes:

[0155] (Appendix C6) The performing the target virtualized network function or one or more management units included in the target virtualized network function; One or more hardware elements included in the hardware infrastructure; and executes the deployment process by further referring to correspondence information indicating the correspondence between the Control method described in Appendix C5.

[0156] (Appendix C7) inquiring whether a candidate IP address for a secondary network in the target virtualized network function is in use; determining an IP address for the secondary network by referring to a response to the inquiry; The method of claim 1, further comprising:

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

[0158] (Appendix D1) A program that causes a computer to function as a management system, The computer an acquisition means for acquiring information identifying a target virtualized network function; a determining means for determining a target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including a policy of the virtualized network function for the hardware platform; A program that functions as a

[0159] (Appendix D5) A program that causes a computer to function as a management system, The computer an acquisition means for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform; an execution means for executing a deployment process by referring to the information acquired by the acquisition means; A program that functions as a

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

[0161] (Appendix E1) at least one processor, an acquisition process for acquiring information identifying a target virtualized network function; a determination process of determining a target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including a policy of the virtualized network function for the hardware platform; A management device that executes the above.

[0162] (Appendix E5) at least one processor, an acquisition process for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform; an execution process that executes a deployment process by referring to the information acquired by the acquisition means; A management device that executes the above. [Explanation of symbols]

[0163] 1, 1A, 1B... Management System 11 ... Acquisition unit (acquisition means) 12. Determination unit (determination means) 21 ... Acquisition unit (acquisition means) 22 Execution unit (execution means, deployment means) 100A: First management device (PaaS) 20 Second management device 200A Infrastructure Management Department (CISM) 230 ··· Functionality Management Unit (VNFM)

Claims

1. an acquisition means for acquiring information identifying a target virtualized network function; a determining means for determining a target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including a policy of the virtualized network function for the hardware platform; A management system that includes:

2. The determining means determining a hardware platform that satisfies the policy information related to the target virtualized network function as the target hardware platform; If there is no hardware infrastructure that satisfies the policy information regarding the target virtualized network function, a virtual hardware element that satisfies the policy information is generated. The management system according to claim 1 .

3. a deployment means for deploying the target virtualized network function on the hardware platform determined by the determination means; It also has The management system according to claim 2 .

4. The network controller further includes an allocation unit that executes a dynamic IP address allocation process as an IP address for a secondary network in the target virtualized network function. The management system according to any one of claims 1 to 3.

5. an acquisition means for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform; an execution means for executing a deployment process by referring to the information acquired by the acquisition means; A management system that includes:

6. The execution means the target virtualized network function or one or more management units included in the target virtualized network function; One or more hardware elements included in the hardware infrastructure; and executes the deployment process by further referring to correspondence information indicating the correspondence between the The management system according to claim 5 .

7. an inquiry means for inquiring whether a candidate IP address for a secondary network in the target virtualized network function is already in use; a determination means for determining an IP address for the secondary network by referring to a response to the inquiry; The management system according to claim 5 or 6, further comprising:

8. an acquisition means for acquiring information identifying a target virtualized network function; a determining means for determining a target hardware platform on which the target virtualized network function is to be deployed by referring to policy information including a policy of the virtualized network function for the hardware platform; A management device comprising:

9. an acquisition means for acquiring information that identifies a hardware platform on which a target virtualized network function is to be deployed, the information being determined by referring to policy information including a policy of the virtualized network function for the hardware platform; an execution means for executing a deployment process by referring to the information acquired by the acquisition means; A management device comprising:

10. one or more processors obtaining information identifying a target virtualized network function; determining a target hardware platform on which to deploy the target virtualized network function by referring to policy information including a policy of the virtualized network function for the hardware platform; A management method that includes:

Images