Management system, management device, and management method

Abstract

The purpose of the present invention is to provide a management system, a management device, a management method, and a non-transitory computer-readable medium that can perform mapping of a virtual network across domains. The management system includes a management unit (11) that manages multiple data centers (12) included in a first area, a management unit (21) that manages multiple data centers (22) included in a second area, and a management unit (110) that selects a data center candidate in which a first virtual node is deployed and a data center candidate in which a second virtual node is deployed on the basis of inter-data-center communication performance information. The management unit (11) identifies a data center (12) in which the first virtual node is deployed on the basis of the candidate in which the first virtual node is deployed, and the management unit (21) identifies a data center in which the second virtual node is deployed on the basis of the candidate in which the second virtual node is deployed.

Description

[Technical Field]

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

[0002] Currently, virtualization of the devices that make up the core network is being considered, and in the future, in preparation for the spread of 5G (5th Generation) networks, it is expected that the virtualization of RAN components will be further promoted in the Open Radio Access Network (O-RAN) Alliance.

[0003] Patent Document 1 discloses the configuration of a resource allocation system that maps a virtual network to a physical infrastructure so as to satisfy the reliability expected for the service and achieve optimal utilization of reliable resources. [Prior art documents] [Patent documents]

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

[0005] The resource allocation system disclosed in Patent Document 1 maps virtual networks to all hardware that constitutes the physical infrastructure in accordance with a specific management policy. Therefore, if the physical infrastructure is divided into multiple management domains, the resource allocation system may not be able to map virtual networks that span the domains.

[0006] In view of the above-mentioned problems, an object of the present disclosure is to provide a management system, a management device, and a management method that are capable of mapping a virtual network across domains. [Means for solving the problem]

[0007] A management system according to a first aspect of the present disclosure includes a first management means for managing a plurality of first data centers included in a first area; a second management means for managing a plurality of second data centers included in a second area different from the first area; and a third management means for selecting, based on communication performance information between the first data center and the second data center, a candidate data center for deploying a first virtual node from among the plurality of first data centers and a candidate data center for deploying a second virtual node from among the plurality of second data centers. The first management means identifies the first data center for deploying the first virtual node based on the candidate data center for deploying the first virtual node, and the second management means identifies the second data center for deploying the second virtual node based on the candidate data center for deploying the second virtual node.

[0008] A management device according to a second aspect of the present disclosure includes a selection unit that selects, from among a plurality of first data centers, at least one first data center that is a candidate for deploying a first virtual node and at least one second data center that is a candidate for deploying a second virtual node, based on communication performance information between a plurality of first data centers included in a first area and a plurality of second data centers included in a second area different from the first area; and a communication unit that transmits information about the at least one first data center that is a candidate for deploying the first virtual node to a first management means that manages the plurality of first data centers, and transmits information about the at least one second data center that is a candidate for deploying the second virtual node to a second management means that manages the plurality of second data centers.

[0009] A management method according to a third aspect of the present disclosure includes selecting, based on communication performance information between a plurality of first data centers included in a first area and a plurality of second data centers included in a second area different from the first area, at least one first data center from among the plurality of first data centers that is a candidate for deploying a first virtual node and at least one second data center from among the plurality of second data centers that is a candidate for deploying a second virtual node; identifying the first data center to deploy the first virtual node from the at least one first data center selected as a candidate based on the communication performance information; and identifying the second data center to deploy the second virtual node from the at least one second data center selected as a candidate based on the communication performance information. [Effects of the Invention]

[0010] The present disclosure makes it possible to provide a management system, a management device, and a management method that are capable of mapping a virtual network across domains. [Brief explanation of the drawings]

[0011] [Figure 1] FIG. 1 is a configuration diagram of a management system according to a first embodiment. [Figure 2] FIG. 2 is a configuration diagram of a management device according to the first embodiment. [Figure 3] FIG. 2 is a configuration diagram of a management device according to the first embodiment. [Figure 4] FIG. 10 is a diagram illustrating a flow of a process for identifying a data center in which a virtual node is to be deployed in the management system according to the first embodiment. [Figure 5] FIG. 10 is a configuration diagram of a management system according to a second embodiment. [Figure 6] FIG. 10 is a configuration diagram of a virtualization management system according to a second embodiment. [Figure 7] FIG. 10 is a configuration diagram of an Edge Orchestrator according to a second embodiment. [Figure 8] FIG. 10 is a configuration diagram of an E2E Orchestrator according to a second embodiment. [Figure 9] FIG. 10 is a diagram illustrating the collection of performance information according to the second embodiment. [Figure 10] FIG. 10 is a diagram showing a flow of management processing of performance information according to the second embodiment; [Figure 11] FIG. 10 is a diagram showing a flow of management processing of an environmental situation according to the second embodiment. [Figure 12] FIG. 10 is a diagram illustrating a flow of a process for extracting a pair of data centers that are candidates for deploying a virtual node according to the second embodiment. [Figure 13] FIG. 10 is a diagram illustrating a flow of a process for determining a data center in which a virtual node is to be deployed according to the second embodiment. [Figure 14] FIG. 2 is a configuration diagram of an Orchestrator according to each embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] (Embodiment 1) Hereinafter, embodiments of the present invention will be described with reference to the drawings. An example of the configuration of a management system according to the first embodiment will be described with reference to FIG. 1. The management system of FIG. 1 includes a management unit 11 that manages multiple data centers (DCs) 12 included in an area 10. Furthermore, the management system of FIG. 1 includes a management unit 21 that manages multiple data centers 22 included in an area 20. Furthermore, the management system of FIG. 1 includes a management unit 110. The management unit 110 communicates with the management unit 11 and the management unit 21. Area 20 manages a data center 22 included in an area different from area 10. For example, area 10 and area 20 may each be an area based on a city or an area based on a prefecture, or area 10 may be an area based on a city and area 20 may be an area based on a prefecture that includes multiple cities. In other words, area 10 and area 20 do not need to include overlapping areas, or part of area 10 may overlap with area 20, or all of area 10 may be included in area 20. Furthermore, an area may be referred to as a domain or a cloud.

[0013] 1 shows that the management means 11 is located within the area 10, but the management means 11 may be located outside the area 10 and manage a plurality of data centers 12 located within the area 10. Similarly, the management means 21 may be located outside the area 20 and manage a plurality of data centers 22 located within the area 20.

[0014] The management means 11, the management means 21, and the management means 110 may be computer devices in which processing is performed by a processor executing a program stored in a memory. For example, the management means 11 may be a single computer device or a single server device. Alternatively, the management means 11 may be a group of computer devices in which multiple computer devices operate in cooperation with each other, or a group of server devices in which multiple server devices operate in cooperation with each other. The management means 110 and the management means 21 may have the same configuration as the management means 11. Alternatively, the management means 11 may be a software resource included in a management system or a management server that manages the entire network, and assigned to manage multiple data centers 12 present in the area 10. The management means 21 may be a software resource included in a management system or a management server that manages the entire network, and assigned to manage multiple data centers 22 present in the area 20. The management means 110 may be a software resource included in a management system or a management server that manages the entire network.

[0015] The data center 12 and the data center 22 may be computer devices in which processing is performed by a processor executing a program stored in a memory. The data center 12 and the data center 22 may perform various functions by installing software. Each of the data center 12 and the data center 22 may be a single computer device or a group of computer devices in which multiple computer devices operate in cooperation with each other. Each of the data center 12 and the data center 22 may be a single server device or a group of server devices.

[0016] The management means 110 may manage performance information related to data centers. The performance information may be referred to as communication performance information. For example, the performance information may be the transmission rate or communication bandwidth of data transmitted between data centers in the same area, or the transmission rate or communication bandwidth of data transmitted between a data center 12 and a data center 22. The performance information may also be the time required for data to reach another data center 12 or data center 22 from one data center 12, data fluctuation, etc. The time required for data to reach another data center 12 or data center 22 from one data center 12 may be referred to as transmission time or delay time. The performance information may also be statistical information, for example, the average, of the time required for multiple pieces of data to reach another data center 12 or data center 22 from one data center 12. The management means 110 may collect performance information from the management means 11 and the management means 21 and further analyze it. Furthermore, the management means 110 may, for example, send a message to the management means 11 and the data center 12 instructing them to transmit measurement data and measure performance information. Up to this point, an example has been described in which the data center 12 is the data sender, but the same applies when the data center 22 is the data sender.

[0017] The management means 110 selects at least one data center 12 as a candidate for deploying a virtual node based on performance information between data centers belonging to different areas, i.e., data center 12 and data center 22. Furthermore, the management means 110 selects at least one data center 22 as a candidate for deploying a virtual node based on performance information about the data center 12 and data center 22. The management means 110 notifies the management means 11 of information about the data center 12 selected as a candidate for deploying a virtual node, and notifies the data center 12 of information about the data center 22 selected as a candidate for deploying a virtual node.

[0018] The management unit 110 may also specify an area, such as area 10 or area 20, in which to deploy a virtual node depending on the function of the virtual node to be deployed. Furthermore, the management unit 110 may specify an area in which to deploy a virtual node depending on the function and service requirements of the virtual node to be deployed. For example, a transmission time or a delay time may be defined as a service requirement.

[0019] The management means 11 may, for example, manage the environmental conditions of a plurality of data centers 12. The environmental conditions may, for example, be the failure frequency of each data center 12, or the amount of power consumption of each data center 12. The management means 11 may collect at least one of the failure frequency and the amount of power consumption from each data center 12, and further analyze it.

[0020] Furthermore, the management means 11 may manage what virtual nodes are currently allocated in each data center 12 in order to identify the data center 12 to which the virtual nodes should be allocated. "Allocate" may be another way of saying "deploy." The management means 11 may also manage available software resource space in each data center 12. A virtual node may be, for example, a virtualized network function. A virtual node may include all the functions of a physical node, or may include some of the functions of a physical node.

[0021] Like the management means 11 , the management means 21 may also manage the environmental conditions relating to a plurality of data centers 22 and information required to allocate virtual nodes to the data centers 22 .

[0022] The management means 11 identifies a data center 12 in which to deploy the virtual node from at least one data center 12 selected as a candidate based on performance information between each data center 12 and each data center 22. Identifying may be rephrased as determining.

[0023] Furthermore, the management means 21 also identifies a data center 22 in which to deploy the virtual node from at least one data center 22 selected as a candidate based on performance information between each data center 12 and each data center 22.

[0024] The candidate data centers 12 and 22 selected based on the performance information may be, for example, the data centers 12 and 22 whose performance information satisfies predetermined requirements. The data centers 12 and 22 whose performance information satisfies predetermined requirements may be, for example, the data centers 12 and 22 that achieve a transmission time shorter than a predetermined time.

[0025] The performance information between each data center 12 and each data center 22 may be generated, for example, by the management means 11 instructing each data center 12 to transmit measurement data to each data center 22. The management means 11 may generate the performance information from the transmission results of the measurement data obtained from each data center 12, and the management means 21 may generate the performance information from the reception results of the measurement data obtained from each data center 22. The management means 11 and the data center 12 transmit the generated performance information to the management means 110.

[0026] The performance information between each data center 12 and each data center 22 may be generated by the management means 110 instructing the data center 12 or the data center 22 to transmit measurement data via the management means 11 and the management means 21. Alternatively, the performance information between each data center 12 and each data center 22 may be generated by the data centers periodically transmitting measurement data without receiving an instruction from the management means 110.

[0027] For example, the management means 110 may select at least one pair of data centers in which the transmission time of measurement data is shorter than a predetermined time from among a plurality of pairs each combining one of a plurality of data centers 12 with one of a plurality of data centers 22. In this case, the management means 110 may identify one data center from among the data centers included in the selected pair, and deploy a virtual node in the identified data center 12. The management means 21 may identify a data center in which to deploy the virtual node from among the notified pairs of data centers 22.

[0028] Here, an example of the configuration of the management means 11 will be described using Fig. 2. Here, an example will be described in which the management means 11 is configured as a single device, namely, a management device 15. The management device 15 includes a DC management unit 16 and an identification unit 17. The DC management unit 16 manages a plurality of data centers 12. For example, the DC management unit 16 manages the environmental conditions related to the plurality of data centers 12 and information required for allocating virtual nodes to the data centers 12. The identification unit 17 identifies the data center 12 in which to deploy the virtual node from at least one data center 12 selected as a candidate based on performance information between each data center 12 and each data center 22. Like the management means 11, the management means 21 is also configured by devices similar to the management device 15.

[0029] Next, an example configuration of the management means 110 will be described using FIG. 3. Here, an example will be described in which the management means 110 is configured as a single device, that is, a management device 150. The management device 150 has a selection unit 160 and a communication unit 170. The selection unit 160 selects at least one data center that is a candidate for deploying a virtual node for each of areas 10 and 20, based on performance information between the data centers. The communication unit 170 transmits information about at least one data center 12 that is a candidate for deploying a virtual node to the management means 11, and transmits information about at least one data center 22 that is a candidate for deploying a virtual node to the management means 21.

[0030] Next, the flow of processing in the management system to identify a data center in which to deploy a virtual node will be described with reference to Figure 4. First, the management means 110 selects a data center as a candidate for deploying a virtual node based on performance information (S1). Specifically, the management means 110 selects at least one data center 12 as a candidate for deploying a virtual node from among a plurality of data centers 12 included in the area 10. Furthermore, the management means 110 selects at least one data center 22 as a candidate for deploying a virtual node from among a plurality of data centers 22 included in the area 20.

[0031] Next, the management means 110 notifies the management means 11 of the data center 12 that is a candidate for deploying the virtual node (S2). Next, the management means 110 notifies the management means 21 of the data center 22 that is a candidate for deploying the virtual node (S3). The management means 110 may execute steps S2 and S3 at substantially the same time, or may execute step S2 after step S3.

[0032] Next, the management means 11 identifies a data center 12 in which to deploy the virtual node from among at least one data center 12 that is a candidate for deploying the virtual node (S4). Similarly to the management means 11, the management means 21 also identifies a data center 22 in which to deploy the virtual node from among at least one data center 22 that is a candidate for deploying the virtual node (S5).

[0033] As described above, the management system in Fig. 1 includes management means 11 that manages multiple data centers included in area 10, and management means 21 that manages multiple data centers included in area 20. Management means 11 deploys virtual nodes to data center 12 in area 10, and management means 21 deploys virtual nodes to data center 22 in area 20. This allows, for example, management means that manage each area to deploy virtual nodes to multiple data centers that belong to different areas, making it possible to deploy virtual nodes across areas.

[0034] (Embodiment 2) Next, a configuration example of a management system according to the second embodiment will be described with reference to FIG. 5. The management system in FIG. 5 includes Edge Cloud 30, Edge Cloud 31, Regional Cloud 40, Regional Cloud 41, Core Cloud 50, and Cell sites 60 to 62. Edge Cloud 30, Edge Cloud 31, Regional Cloud 40, Regional Cloud 41, and Core Cloud 50 correspond to Area 10 and Area 20 in FIG. 1. FIG. 5 illustrates an example in which Area 10 and Area 20 in FIG. 1 have a hierarchical structure. Cell sites 60 to 62 may be, for example, communication areas managed by base stations used for mobile communications. The base stations may be referred to as, for example, eNBs (evolved Node Bs) or gNBs. The base stations may also be referred to as NRs or NR entities. The numbers of Edge Clouds, Regional Clouds, Core Clouds, and Cell sites are not limited to those shown in FIG. 5.

[0035] Edge Clouds 30 and 31 relay data transmitted between cell sites. For example, Edge Cloud 30 transmits data received from cell site 60 to cell site 61 or cell site 62. Alternatively, Edge Cloud 30 transmits data received from cell site 60 to Regional Cloud 40 to be relayed to a cell site under Edge Cloud 31. Edge Cloud 30 and Edge Cloud 31 may be provided, for example, for each specific region. Edge Clouds 30 and 41 accommodate devices (for example, DU (RAN Distributed Unit) or CU (RAN Control / Centralized Unit)) connected to a large number of cell sites (radio devices (RU: Remote Radio Unit) of base stations).

[0036] The Regional Clouds 40 and 41 relay data transmitted between the Edge Cloud 30, the Edge Cloud 31, and other Edge Clouds. The Core Cloud 50 relays data transmitted between the Regional Cloud 40, the Regional Cloud 41, and other Regional Clouds. The Regional Clouds 40 and 41 are the next connection sites for the Edge Clouds. Depending on the slice requirements, CUs corresponding to DUs deployed in the Edge Clouds are deployed in the Regional Clouds. The Core Cloud 50 is the next connection site for the Regional Clouds. The Core Cloud generally accommodates core network applications such as 5GC (5th Generation Core) and EPC (Evolved Packet Core). The placement of functions deployed in the Edge Cloud, Regional Cloud, and Core Cloud may differ depending on the vendor.

[0037] The Regional Cloud 40 is a higher-level cloud of the Edge Cloud 30 and the Edge Cloud 31, and the Core Cloud 50 may be referred to as a higher-level cloud of the Regional Cloud 40 and the Regional Cloud 41. A higher-level cloud may also be referred to as a higher-level domain. Furthermore, the Regional Cloud 40 and the Regional Cloud 41 are lower-level clouds of the Core Cloud 50, and the Edge Cloud 30 and the Edge Cloud 31 may also be referred to as lower-level clouds of the Regional Cloud 40 and the Regional Cloud 41. A lower-level cloud may also be referred to as a lower-level domain. When transmitting data to a data center of a cloud or domain different from the respective cloud or domain, the Edge Cloud 30, the Edge Cloud 31, the Regional Cloud 40, and the Regional Cloud 41 transmit the data to the higher-level cloud or the higher-level domain. In other words, the higher-level cloud relays communications between the lower clouds.

[0038] Next, a virtualization management system for constructing a virtualization system will be described with reference to FIG. 6. The virtualization management system in FIG. 6 includes an Edge Orchestrator 35, a MANO (Management and Orchestration) 36, a Regional Orchestrator 45, a MANO 46, a Core Orchestrator 55, and an E2E Orchestrator 70. The E2E Orchestrator 70 corresponds to the management means 110 in FIG. 1. The Edge Orchestrator 35, the Regional Orchestrator 45, and the Core Orchestrator 55 correspond to the management means 11 and the management means 21 in FIG. 1. The Edge Orchestrators 35, 45, and 55, the MANOs 36, 46, and 56, and the E2E Orchestrator 70 may be computer devices that operate by a processor executing a program stored in a memory. Alternatively, the Edge Orchestrators 35, 45, and 55, the MANOs 36, 46, and 56, and the E2E Orchestrator 70 may be a group of computer devices.

[0039] In order to optimize the dynamic deployment of network functions, the MANO 36 builds a virtualization system using, for example, multiple data centers included in the Edge Cloud 30. The Edge Orchestrator 35 manages the Edge Cloud 30 and performs analysis related to the Edge Cloud 30. The Regional Orchestrator 45, the MANO 46, the Core Orchestrator 55, and the MANO 56 also perform functions and processes similar to those of the Edge Orchestrator 35 and the MANO 36. Although the Edge Cloud 31 and the Regional Cloud 41 are omitted from FIG. 6, it is assumed that an Edge Orchestrator and a MANO are also associated with the Edge Cloud 31, and that a Regional Orchestrator and a MANO are also associated with the Regional Cloud 41.

[0040] In FIG. 6, the Edge Orchestrator 35 and the MANO 36 are shown as different devices or components. However, for example, the Edge Orchestrator 35 may be a component that constitutes the MANO 36. For example, the MANO 36 may include the Edge Orchestrator 35, a Virtual Network Function Manager (VNFM), and a Virtualized Infrastructure Manager (VIM). The VIM is responsible for operational management of the physical resources of the data center included in the Edge Cloud 30 and the virtual resources on the data center. The VNFM manages the resource requirements required by the VNFs and manages the lifecycle of the VNFs. The VNFs are a group of virtualized network functions that run on the NFVI. The Network Functions Virtualization Infrastructure (NFVI) is a platform for treating physical resources such as storage as virtual resources. The NFVI is included in the data center. A system including the Edge Orchestrator 35 and the MANO 36 may be referred to as an NFV architecture.

[0041] The E2E Orchestrator 70 collects and analyzes data necessary for deploying VNFs across clouds or domains. The data necessary for deploying VNFs may be, for example, performance information between data centers.

[0042] The virtualization management system of FIG. 6 deploys, for example, RAN (Radio Access Network) components across clouds. The RAN components include RUs (Remote Radio Units), DUs (RAN Distributed Units), and CUs (RAN Control / Centralized Units). The RUs process radio frequency signals. The RUs are mainly deployed in cell sites 60 to 62. The RUs may be configured, for example, with antennas. The clouds to which the DUs and CUs are deployed are determined according to service requirements or slice requirements (hereinafter referred to as service requirements). Furthermore, for VNFs other than the DUs and CUs, the clouds to which they are deployed are determined according to slice requirements, the functions of the VNFs, and requirements required for the VNFs.

[0043] The DU and CU are devices or functional blocks that perform baseband processing. The CU is a device that connects to a core network device, and the DU is located between the RU and the CU. The CU mainly processes packet data, etc., while the DU processes data at a lower layer than the CU.

[0044] For example, the service requirements are defined as eMBB (enhanced Mobile Broadband), URLLC (Ultra Reliable and Low Latency Communications), and mMTC (massive Machine Type Communication). For example, when executing a service that satisfies URLLC, which has the strictest latency requirements, the CU and DU may be deployed in Edge Cloud 30 and Edge Cloud 31. This shortens the transmission distance between the CU and DU, thereby reducing the latency time related to data transmission. When executing a service that satisfies eMBB, which specifies a high-speed, large-capacity communication service, the DU may be deployed in Edge Cloud 30 and Edge Cloud 31, and the CU may be deployed in Regional Cloud 40 and Regional Cloud 41. When executing a service that satisfies mMTC, which specifies a communication service between a large number of simultaneously connected terminals, the DU may be deployed in Edge Cloud 30 and Edge Cloud 31, and the CU may be deployed in Core Cloud 50. Specifically, the CU may be deployed farther from the Edge Cloud in order of the service's strictest latency requirements. Similarly to the CU, the DU may be flexibly deployed in the Edge Cloud 30, the Regional Cloud 40, and the Core Cloud 50 according to service requirements.

[0045] Furthermore, when the DU and CU are deployed as virtual nodes or virtual machines in the Edge Cloud, Regional Cloud, and Core Cloud, the DU and CU may be referred to as vDU and vCU.

[0046] Next, a configuration example of the Edge Orchestrator 35 will be described with reference to Fig. 7. Note that the Regional Orchestrator 45 and the Core Orchestrator 55 have the same configuration as the Edge Orchestrator 35, so detailed configuration examples of the Regional Orchestrator 45 and the Core Orchestrator 55 will not be described here.

[0047] The Edge Orchestrator 35 includes a Network Slice Subnet Management Function (NSSMF) 37 and a Management Data Analytics Function (MDAF) 38. The NSSMF 37 and the MDAF 38 may be referred to as an NSSMF entity 37 and an MDAF entity 38, for example.

[0048] The NSSMF 37 collects and manages information such as fault information and power consumption as the environmental status of the data centers included in the target cloud. The NSSMF 37 may also be referred to as a management unit. The target cloud may be, for example, the Edge Cloud 30. The target cloud managed by the NSSMF 37 may also be referred to as a network subnet slice. A network subnet slice is created by further dividing a network slice.

[0049] For example, the NSSMF 37 may collect and manage environmental conditions for each data center. Fault information may be divided into, for example, software and hardware fault information. A fault alarm indicating a software fault in a data center may be transmitted from the data center to the NSSMF via an EMS (Element Management System), for example. The EMS manages, for example, VNFs. The EMS may manage, for example, one data center, a data center included in one cloud, or each data center included in multiple clouds. Furthermore, a fault alarm indicating a hardware fault in the data center and power consumption may be transmitted to the NSSMF via a VIM.

[0050] The MDAF 38 may analyze the environmental conditions collected by the NSSMF 37 and identify or select the data center with the best environmental conditions from among candidate data centers for deploying a vCU or vDU. The MDAF 38 may be referred to as an identification unit. The candidate data centers may be notified by the E2E Orchestrator 70, which will be described later. For example, the number of fault alarms with a severity indicating the level of the fault (Minor) or higher or the number of physical faults may be used as the environmental conditions. Alternatively, the daily power consumption rate in the data center, the frequency of power outages per week, the duration of power outages, the average heat generation per day of servers or storage, the average power consumption or heat generation per rack per day, etc. may be used as the environmental conditions. At least one of the information listed above may be used as the environmental conditions. For example, if the MDAF 38 uses at least one criterion of the number of fault alarms, the number of physical faults, and information related to power as the environmental conditions, it may score the environmental conditions for each criterion and use the total score as the value of the environmental conditions. For example, the fewer the number of fault alarms and the fewer the number of physical faults, the higher the score may be. The smaller the value of the information regarding power, the higher the score may be. The total of the environmental conditions indicates that the higher the score, the better the quality, and the MDAF 38 may identify data centers with high scores.

[0051] The physical failure may include, for example, a power outage of a server due to a power shortage, or a network failure due to a fault in an optical fiber cable, etc. The power consumption rate may be a value obtained by dividing the total amount of power supplied by the amount of power consumed and multiplying the result by 100.

[0052] Next, a configuration example of the E2E Orchestrator 70 will be described with reference to Fig. 8. The E2E Orchestrator 70 has a Communication Service Management Function (CSMF) 71, a Network Slice Management Function (NSMF) 72, and an MDAF 73. The CSMF 71 and the NSMF 72 may also be referred to as the CSMF entity 71 and the NSMF entity 72.

[0053] The CSMF 71 manages communication services. For example, the CSMF 71 may manage data transmitted as a user plane. Furthermore, the CSMF 71 receives a deployment request for a vCU and a vDU from an operator who operates the E2E Orchestrator 70. Specifically, the CSMF 71 receives the deployment request from the operator via an input interface such as a touch panel, a keyboard, or a microphone. The deployment request may include information regarding service requirements. The information regarding service requirements indicates eMBB, URLLC, or mMTC, and may further include a transmission time of data between the vCU and the vDU.

[0054] The NSMF 72 collects and manages performance information between data centers across multiple clouds. Here, the performance information collected by the NSMF 72 will be described with reference to FIG. 9. FIG. 9 shows that the Cell site 60 includes multiple RUs, including RU_1 to RU_4. The numbers 1 to 4 are identification information for identifying the RUs. Furthermore, it shows that the Edge Cloud 30 includes multiple DCs, including DCs (Data Centers) E1 to DC_E4, the Regional Cloud 40 includes multiple DCs, including DC_R1 to DC_R3, and the Core Cloud 50 includes multiple DCs, including DC_C1 and DC_C2. E1 to E4, R1 to R3, and C1 to C2 are identification information for identifying the DCs, respectively.

[0055] For example, the NSMF 72 collects information regarding data transmission times on transmission paths between DC_E1 and each DC included in the Regional Cloud 40. The NSMF 72 may collect data transmission times for all combinations of each DC included in the Edge Cloud 30 and each DC included in the Regional Cloud 40. Alternatively, the NSMF 72 may collect data transmission times for some of all combinations of each DC included in the Edge Cloud 30 and each DC included in the Regional Cloud 40.

[0056] Similarly, the NSMF 72 may collect data transmission times between the Regional Cloud 40 and the Core Cloud 50, between a DC included in the Regional Cloud 40 and a DC included in the Core Cloud 50. Furthermore, the NSMF 72 may collect data transmission times between each RU included in the Cell site 60 and each DC included in the Edge Cloud 30.

[0057] For example, the NSMF 72 may determine a DC to which measurement data is to be sent and a DC that is the destination of the measurement data, and instruct the DC that sent the measurement data to send the measurement data. Furthermore, the NSMF 72 may collect information regarding the transmission time of the measurement data from the DC that received the measurement data. For example, the DC that sent the measurement data may set the transmission time in the measurement data, and the DC that received the measurement data may identify the time at which the measurement data was received. The DC that received the measurement data may identify the transmission time of the measurement data by subtracting the time set in the measurement data from the time at which the measurement data was received.

[0058] The MDAF 73 analyzes performance information collected by the NSMF 72, such as information related to transmission time, to identify a data center that satisfies the service requirements. For example, when executing a service that satisfies eMBB, which specifies a high-speed, large-capacity communication service, it is assumed that the DU is deployed in the Edge Cloud 30 and the CU is deployed in the Regional Cloud 40. Furthermore, it is assumed that the eMBB service requirements stipulate that the transmission time for data transmission between the vCU and the vDU is, for example, 1 msec (millisecond). In this case, the MDAF 73 extracts a pair of data centers where the transmission time for measurement data between the data center included in the Edge Cloud 30 and the data center included in the Regional Cloud 40 is 1 msec or less. The MDAF 73 may extract multiple pairs. In other words, the MDAF 73 extracts candidate data centers for deploying the vCU and the vDU.

[0059] The MDAF 73 transmits the identification information of the candidate data centers to the Edge Orchestrator 35 and the Regional Orchestrator 45 of the Edge Cloud and the Regional Cloud that have the data centers included in the extracted pair.

[0060] Next, the flow of the performance information management process will be described with reference to Fig. 10. First, the EMS transmits performance information related to the data centers it manages to the NSMF 72 (S11). The EMS transmits performance information between data centers to the NSMF 72. The performance information between data centers may be, for example, the transmission time of measurement data transmitted between data centers. The performance information also includes information identifying the data center that transmitted the measurement data and the data center that is the destination of the measurement data.

[0061] For example, the EMS may receive the measurement data, acquire performance information from a data center that has identified the transmission time, and transmit the acquired performance information to the NSMF 72. Also, while Fig. 10 shows one EMS notifying the NSMF 72 of performance information, multiple EMSs may transmit performance information to the NSMF 72.

[0062] The EMS may also transmit performance information to the NSMF 72 in response to a request message received from the NSMF 72. Furthermore, when the EMS receives a request message from the NSMF 72 requesting performance information between specific data centers, the EMS having the performance information between the specified specific data centers may respond to the NSMF 72 with the performance information.

[0063] Next, the MDAF 73 transmits a performance information request message to the NSMF 72 in order to obtain performance information from the NSMF 72 (S12). Next, the NSMF 72 transmits a performance information response message including the performance information to the MDAF 73 in order to transmit the performance information to the MDAF 73 (S13). The MDAF 73 may periodically transmit the performance information request message and obtain the performance information from the NSMF 72. Alternatively, the MDAF 73 may transmit the performance information request message at any timing and obtain the performance information from the NSMF 72.

[0064] Next, the MDAF 73 updates the learning model it manages using the acquired performance information (S14). The learning model is used to output candidates for data centers in which to deploy the virtual nodes. For example, when the type of cloud in which to deploy the virtual nodes is input, the learning model may output at least one candidate for a pair of data centers in which to deploy the virtual nodes. The type of cloud may be information that identifies, for example, an Edge Cloud, a Regional Cloud, or a Core Cloud. The learning model outputs candidate pairs of data centers using the performance information. For example, the learning model extracts candidate pairs of data centers that satisfy the transmission time requirements included in the service requirements.

[0065] Next, the flow of the environmental status management process will be described with reference to Fig. 11. First, the VNF transmits a software environmental status notification message to the NSSMF 37 via the EMS to notify the NSSMF 37 of the environmental status related to software (SW) (S21). The environmental status related to software includes, for example, software fault information. The VNF is, for example, a function of a virtual node deployed in a data center in the Edge Cloud 30. The VNF notifies the NSSMF 37 included in the Edge Orchestrator 35 that manages the Edge Cloud 30 of the environmental status related to the software.

[0066] Next, the NFVI transmits a hardware environment status notification to the NSSMF 37 via the VIM to notify the NSSMF 37 of the environment status related to hardware (HW) (S22). The environment status related to hardware includes hardware fault information and power information. The NFVI is deployed in a data center in the Edge Cloud 30 and is a platform for treating physical resources such as storage as virtual resources. The NFVI notifies the NSSMF 37, which is included in the Edge Orchestrator 35 that manages the Edge Cloud 30, of the environment status related to hardware.

[0067] When the VNF and the NFVI detect a fault or the like, they transmit the environmental status to the NSSMF 37. Therefore, the order of steps S21 and S22 may be reversed from the order shown in FIG.

[0068] Next, the MDAF 38 transmits an environmental status request message to the NSSMF 37 to acquire the environmental status from the NSSMF 37 (S23). Next, the NSSMF 37 transmits an environmental status response message including the environmental status to the MDAF 38 to transmit performance information to the MDAF 38 (S24). The MDAF 38 may periodically transmit the environmental status request message to acquire the environmental status from the NSSMF 37. Alternatively, the NSSMF 37 may transmit the environmental status request message at any timing to acquire the environmental status from the NSSMF 37.

[0069] Next, the MDAF 38 uses the acquired environmental conditions to update the learning model that it manages (S25). The learning model is used to output a data center in which to deploy the virtual node from among candidate data centers. For example, when candidate data centers in which to deploy the virtual node are input, the learning model may output a data center in which to deploy the virtual node. The learning model identifies a data center using the environmental conditions. For example, the learning model identifies an optimal data center according to criteria related to the environmental conditions. The optimal data center may be, for example, the data center with the highest availability or reliability.

[0070] Next, the flow of the process of extracting a pair of data centers that are candidates for deploying a virtual node will be described with reference to Fig. 12. First, the CSMF 71 receives a virtual node deployment request from an operator who operates the E2E Orchestrator 70 (S31). For example, the deployment request may include information on the area in which the service is provided and the service requirements. For example, assume that the service requirements specify eMBB and that the transmission time between the vCU and the vDU is 1 msec or less.

[0071] Next, the CSMF 71 transmits to the NSMF 72 a configuration notification message including configuration information indicating the area in which the service is provided and the configuration of the deployment of the vCU and vDU that satisfies the specified service requirements (S32). For example, it is assumed that each of eMBB, URLCC, and mMTC, and the cloud type in which the vCU and vDU are deployed, are predetermined. For example, if eMBB is specified, it may be determined that the vDU is deployed in an Edge Cloud and the vCU is deployed in a Regional Cloud. In this case, because eMBB is specified as a service requirement, the CSMF 71 transmits to the NSMF 72 a configuration notification message indicating that the vDU is deployed in an Edge Cloud and the vCU is deployed in a Regional Cloud.

[0072] Next, the NSMF 72 sends a DC query notification message including the service area and the deployment configuration of the virtual node to the MDAF 73 (S33). The MDAF 73 extracts pairs of data centers in which the virtual nodes, i.e., the vCU and vDU, are deployed (S34). For example, the MDAF 73 may determine the Edge Cloud closest to the service area. In this case, the MDAF 73 extracts candidate data center pairs using the transmission time between the data center included in the determined Edge Cloud and the data centers included in each of multiple Regional Clouds. The MDAF 73 extracts candidate data center pairs using the learning model described in FIG. 10.

[0073] Next, the MDAF 73 sends a DC response message including information about the candidate data center pair to the NSMF 72 (S35).

[0074] Next, the flow of the process of determining the data center in which to deploy the virtual node will be described with reference to Fig. 13. Here, it is assumed that information on the pair of data centers that are candidates for deploying the virtual node, as described in Fig. 12, has been notified to the NSMF 72.

[0075] First, the NSMF 72 transmits a candidate DC notification message including information about a data center that is a candidate for deploying a virtual node to the NSSMF 37 (S41). Specifically, the NSMF 72 notifies the NSSMF 37 of information about at least one data center included in the Edge Cloud 30, among the data centers included in a pair of data centers that are candidates for deploying a virtual node. Also, FIG. 13 shows that the NSMF 72 transmits a candidate DC notification message to the NSSMF 37. However, in reality, the NSMF 72 also notifies the NSSMF included in the Regional Orchestrator of the Regional Cloud of information about at least one data center included in the Regional Cloud.

[0076] Next, the NSSMF 37 transmits a DC inquiry message including information about candidate data centers in which to deploy the virtual node to the MDAF 38 in order to acquire information about the data center in which to deploy the virtual node (S42).

[0077] Next, the MDAF 38 determines a data center in which to deploy the virtual node from among the candidate data centers (S43). Specifically, the MDAF 38 determines a data center from among the candidate data centers using the environmental conditions of each data center. The MDAF 38 determines a data center in which to deploy the virtual node using the learning model described in FIG. 11.

[0078] Next, the MDAF 38 transmits a DC response message including information about the determined data center to the NSSMF 37 (S44). Next, the NSSMF 37 transmits a virtual node setting instruction message including information about the determined data center to the MANO 36 to set a virtual node in the determined data center (S45). The MANO 36 sets a VNF, which is a vDU, in the data center included in the virtual node setting instruction message. In addition, the MANO associated with the Regional Orchestrator also sets a VNF, which is a vCU, in the data center determined by the Regional Orchestrator.

[0079] As described above, the E2E Orchestrator 70 extracts candidate data centers across clouds for deploying virtual nodes based on the data transmission time between clouds. Furthermore, the Edge Cloud 30, Regional Cloud 40, and Core Cloud 50 determine the data center in which to deploy the virtual nodes from the candidate data centers notified by the E2E Orchestrator 70 based on the environmental conditions. This enables deployment of virtual nodes across clouds. Furthermore, by determining the data center based on performance information and environmental conditions, it is possible to determine the data center that meets the service requirements. Furthermore, by each of the Edge Orchestrator 35, Regional Orchestrator 45, and Core Orchestrator 55 identifying or determining the data center in which to deploy the virtual nodes, the processing load can be distributed. In other words, the processing load on each of the Edge Orchestrator 35, Regional Orchestrator 45, and Core Orchestrator 55 can be reduced compared to when one Orchestrator identifies all data centers in which to deploy virtual nodes.

[0080] (Modification of the second embodiment) A modified example of the process for identifying a data center in which a virtual node is to be deployed will be described. In the second embodiment, an example was described in which the Edge Orchestrator and the Regional Orchestrator each identify a data center in which a virtual node is to be deployed according to the environmental situation. In the following modified example, it will be described that the E2E Orchestrator 70 identifies a data center in which a virtual node is to be deployed, and the Edge Orchestrator and the Regional Orchestrator 45 deploy the virtual node in the data center identified by the E2E Orchestrator 70.

[0081] The MDAF 38 included in the Edge Orchestrator 35 may prioritize the multiple data center candidates notified by the NSMF 72 based on the environmental conditions. Furthermore, the Edge Orchestrator 35 transmits information indicating the ranking set for each of the multiple data center candidates to the NSMF 72. Similarly, the MDAF included in the Regional Orchestrator 45 may prioritize the multiple data center candidates notified by the NSMF 72 based on the environmental conditions. Furthermore, the Regional Orchestrator 45 transmits information indicating the ranking set for each of the multiple data center candidates to the NSMF 72.

[0082] The NSMF 72 transmits to the MDAF 73 information indicating the rankings set for the plurality of data center candidates received from the Edge Orchestrator 35 and the Regional Orchestrator 45 .

[0083] The MDAF 73 identifies one of the multiple pairs of a data center included in the Edge Cloud 30 and a data center included in the Regional Cloud 40 extracted in step S34 of Fig. 12. For example, the MDAF 73 may identify a pair of data centers that can be expected to have high availability when environmental conditions are taken into consideration, even though the transmission time will be longer than other pairs. Alternatively, the MDAF 73 may identify a pair of data centers that can be expected to have short transmission time, but have shorter availability when environmental conditions are taken into consideration, than other pairs.

[0084] The MDAF 73 may output the identified data center pair to the NSMF 72, and the NSMF 72 may transmit identification information of the identified data center to the NSSMF 37 included in the Edge Orchestrator 35 and the NSSMF included in the Regional Orchestrator 45.

[0085] As described above, the E2E Orchestrator 70 can determine, for each pair of data centers extracted using the performance information, the data center in which the vDU is to be deployed in the Edge Cloud 30 and the data center in which the vCU is to be deployed in the Regional Cloud 40.

[0086] For example, when the Orchestrator of each cloud identifies a data center to deploy a virtual node based on the environmental conditions, the identified data center may differ from the pair of data centers extracted in MDAF 73. In this case, the performance information between the identified data centers may not satisfy the service requirements.

[0087] In this variant, MDAF73 takes into account the ranking set based on the environmental conditions and further identifies data centers on a pair-by-pair basis extracted based on performance information, thereby reducing the possibility of identifying a data center that does not meet the service requirements.

[0088] 14 is a block diagram showing an example configuration of an Edge Orchestrator 35, a Regional Orchestrator 45, a Core Orchestrator 55, and an E2E Orchestrator 70 (hereinafter referred to as the Edge Orchestrator 35, etc.). Referring to FIG. 14, the Edge Orchestrator 35, etc. includes a network interface 1201, a processor 1202, and a memory 1203. The network interface 1201 may be used to communicate with other network nodes. The network interface 1201 may include, for example, a network interface card (NIC) that complies with the IEEE 802.3 series.

[0089] The processor 1202 reads and executes software (computer programs) from the memory 1203 to perform the processing of the Edge Orchestrator 35 and the like described using flowcharts in the above-described embodiments. The processor 1202 may be, for example, a microprocessor, an MPU, or a CPU. The processor 1202 may include multiple processors.

[0090] The memory 1203 is configured by a combination of volatile memory and non-volatile memory. The memory 1203 may include storage located remotely from the processor 1202. In this case, the processor 1202 may access the memory 1203 via an I / O (Input / Output) interface (not shown).

[0091] 14, the memory 1203 is used to store software modules. The processor 1202 reads and executes these software modules from the memory 1203, thereby performing the processing of the Edge Orchestrator 35 and the like described in the above embodiment.

[0092] As described with reference to FIG. 14, each of the processors included in the Edge Orchestrator 35 or the like in the above-described embodiment executes one or more programs including a group of instructions for causing a computer to execute the algorithm described with reference to the drawings.

[0093] In the above examples, the program includes instructions (or software code) that, when loaded into a computer, cause the computer to perform one or more functions described in the embodiments. The program may be stored on a non-transitory computer-readable medium or a tangible storage medium. By way of example and not limitation, computer-readable medium or tangible storage medium includes random-access memory (RAM), read-only memory (ROM), flash memory, solid-state drive (SSD) or other memory technology, CD-ROM, digital versatile disc (DVD), Blu-ray® disc or other optical disk storage, magnetic cassette, magnetic tape, magnetic disk storage or other magnetic storage device. The program may also be transmitted on a transitory computer-readable medium or communication medium. By way of example and not limitation, transitory computer-readable medium or communication medium includes electrical, optical, acoustic, or other forms of propagated signals.

[0094] The present disclosure is not limited to the above-described embodiment, and can be modified as appropriate within the scope of the present disclosure.

[0095] A part or all of the above-described embodiments can be described as, but not limited to, the following supplementary notes. (Appendix 1) a first management means for managing a plurality of first data centers included in a first area; a second management means for managing a plurality of second data centers included in a second area having a range different from the first area; and a third management means for selecting, based on communication performance information between the first data center and the second data center, a candidate data center for deploying a first virtual node from among the plurality of first data centers and a candidate data center for deploying a second virtual node from among the plurality of second data centers. The first management means Identifying the first data center in which to deploy the first virtual node based on the candidates for deploying the first virtual node; The second management means and a management system that identifies the second data center in which to deploy the second virtual node based on the candidate for deployment of the second virtual node. (Appendix 2) The communication performance information 2. The management system of claim 1, wherein the time is a transmission time of data transmitted between each of the first data centers and each of the second data centers. (Appendix 3) The first management means Identifying the first data center in which to deploy the first virtual node based on environmental conditions in the plurality of first data centers; The second management means 3. The management system according to claim 1, wherein the second data center in which the second virtual node is to be deployed is identified based on environmental conditions in the second data centers. (Appendix 4) The environmental conditions are: 4. The management system of claim 3, wherein the management system indicates a failure frequency or power consumption at each of the first data centers or each of the second data centers. (Appendix 5) The third management means 5. The management system according to claim 1, wherein an area in which the first virtual node and the second virtual node are to be deployed is identified according to the functions of the first virtual node and the second virtual node. (Appendix 6) the first virtual node is a DU (Distributed Unit) that performs baseband processing, 6. The management system according to any one of appendixes 1 to 5, wherein the second virtual node is a CU (Central Unit) that processes data in a layer higher than a layer handled by the DU. (Appendix 7) a selection unit that selects, based on communication performance information between a plurality of first data centers included in a first area and a plurality of second data centers included in a second area different from the first area, at least one of the first data centers as a candidate for deploying a first virtual node, and at least one of the second data centers as a candidate for deploying a second virtual node, from the plurality of second data centers; a communication unit that transmits, to a first management means that manages a plurality of the first data centers, information about at least one of the first data centers that is a candidate for deploying the first virtual node, and that transmits, to a second management means that manages a plurality of the second data centers, information about at least one of the second data centers that is a candidate for deploying the second virtual node. (Appendix 8) The communication performance information 8. The management device according to claim 7, wherein the time is a transmission time of data transmitted between each of the first data centers and each of the second data centers. (Appendix 9) The selection unit 9. The management device according to claim 7, wherein the management device identifies an area in which to deploy the first virtual node and the second virtual node according to functions of the first virtual node and the second virtual node. (Appendix 10) the first virtual node is a DU (Distributed Unit) that performs baseband processing, The management device according to any one of Supplementary notes 7 to 9, wherein the second virtual node is a CU (Central Unit) that processes data in a layer higher than a layer handled by the DU. (Appendix 11) selecting at least one first data center from among the first data centers that is a candidate for deploying a first virtual node, and at least one second data center from among the second data centers that is a candidate for deploying a second virtual node, based on communication performance information between a plurality of first data centers included in a first area and a plurality of second data centers included in a second area that is different from the first area; identifying the first data center in which to deploy the first virtual node from among at least one of the first data centers selected as a candidate based on the communication performance information; a management method for identifying the second data center in which the second virtual node is to be deployed from among at least one second data center selected as a candidate based on the communication performance information; (Appendix 12) The communication performance information 12. The management method according to claim 11, wherein the time is the transmission time of data transmitted between each of the first data centers and each of the second data centers. (Appendix 13) When identifying the first data center, Identifying the first data center in which to deploy the first virtual node based on environmental conditions in the plurality of first data centers; When identifying the second data center, The management method according to claim 11 or 12, further comprising identifying the second data center in which to deploy the second virtual node based on environmental conditions in the second data centers. (Appendix 14) The environmental conditions are: 14. The management method of claim 13, further comprising indicating a failure frequency or power consumption in each of the first data centers or each of the second data centers. (Appendix 15) 15. The management method according to any one of appendixes 11 to 14, wherein, when selecting the first data center and the second data center, an area in which the first virtual node and the second virtual node are to be deployed is identified according to functions of the first virtual node and the second virtual node. (Appendix 16) the first virtual node is a DU (Distributed Unit) that performs baseband processing, The management method according to any one of Supplementary Notes 11 to 15, wherein the second virtual node is a CU (Central Unit) that processes data in a layer higher than the layer handled by the DU. (Appendix 17) selecting at least one first data center from among the first data centers that is a candidate for deploying a first virtual node, and at least one second data center from among the second data centers that is a candidate for deploying a second virtual node, based on communication performance information between a plurality of first data centers included in a first area and a plurality of second data centers included in a second area that is different from the first area; A management method comprising: transmitting information about at least one first data center that is a candidate for deploying the first virtual node to a first management means that manages a plurality of the first data centers; and transmitting information about at least one second data center that is a candidate for deploying the second virtual node to a second management means that manages a plurality of the second data centers. (Appendix 18) The communication performance information 18. The management method of claim 17, wherein the time is a transmission time of data transmitted between each of the first data centers and each of the second data centers. (Appendix 19) When selecting the first data center and the second data center, 19. The management method according to any one of appendix 17 or 18, wherein an area in which the virtual node is to be deployed is identified according to the function of the virtual node. (Appendix 20) the first virtual node is a DU (Distributed Unit) that performs baseband processing, The management method according to any one of Supplementary Notes 17 to 19, wherein the second virtual node is a CU (Central Unit) that processes data in a layer higher than the layer handled by the DU.

[0096] The present invention is not limited to the above-described embodiment, and can be modified as appropriate within the scope of the invention. [Explanation of symbols]

[0097] 10 Area 11 Control measures 12 Data Centers 15 Management device 16 DC Management Department 17 Specific section 20 Area 21 Control measures 22 Data Center 30 Edge Cloud 31 Edge Cloud 35 Edge Orchestrator 36 MANO 37 NSSMF 38 MDAF 40 Regional Cloud 41 Regional Cloud 45 Regional Orchestrator 46 MANO 50 Core Cloud 55 Core Orchestrator 56 MANO 60 Cell sites 61 Cell sites 62 Cell sites 70 E2E Orchestrator 71 CSMF 72 NSMF 73 MDAF 110 Control measures 150 Management device 160 Selection Section 170 Communications Department

Claims

1. a first management means for managing a plurality of first data centers included in a first area; a second management means for managing a plurality of second data centers included in a second area having a range different from the first area; and a third management means for selecting, based on communication performance information between the first data center and the second data center, a candidate data center for deploying a first virtual node from among the plurality of first data centers and a candidate data center for deploying a second virtual node from among the plurality of second data centers. The first management means Identifying the first data center in which to deploy the first virtual node based on the candidates for deploying the first virtual node; The second management means and a management system that identifies the second data center in which to deploy the second virtual node based on the candidate for deployment of the second virtual node.

2. The communication performance information The management system according to claim 1 , wherein the time is a transmission time of data transmitted between each of the first data centers and each of the second data centers.

3. The first management means Identifying the first data center in which to deploy the first virtual node based on environmental conditions in the plurality of first data centers; The second management means The management system according to claim 1 , further comprising: identifying the second data center in which to deploy the second virtual node based on environmental conditions in a plurality of the second data centers.

4. The environmental conditions are: The management system according to claim 3 , further comprising: a management system that indicates a failure frequency or a power consumption in each of the first data centers or each of the second data centers.

5. The third management means 5. The management system according to claim 1, further comprising: specifying an area in which the first virtual node and the second virtual node are to be deployed in accordance with functions of the first virtual node and the second virtual node.

6. the first virtual node is a DU (Distributed Unit) that performs baseband processing, The management system according to claim 1 , wherein the second virtual node is a CU (Central Unit) that processes data in a layer higher than a layer handled by the DU.

7. a selection unit that selects, based on communication performance information between a plurality of first data centers included in a first area and a plurality of second data centers included in a second area different from the first area, at least one first data center that is a candidate for deploying a first virtual node from among the plurality of first data centers and at least one second data center that is a candidate for deploying a second virtual node from among the plurality of second data centers; a communication unit that transmits, to a first management means that manages a plurality of the first data centers, information about at least one of the first data centers that is a candidate for deploying the first virtual node, and that transmits, to a second management means that manages a plurality of the second data centers, information about at least one of the second data centers that is a candidate for deploying the second virtual node.

8. The communication performance information The management device according to claim 7 , wherein the time is a transmission time of data transmitted between each of the first data centers and each of the second data centers.

9. The selection unit The management device according to claim 7 , wherein an area in which the first virtual node and the second virtual node are to be deployed is identified in accordance with functions of the first virtual node and the second virtual node.

10. A management device, selecting at least one first data center from among the first data centers that is a candidate for deploying a first virtual node, and at least one second data center from among the second data centers that is a candidate for deploying a second virtual node, based on communication performance information between a plurality of first data centers included in a first area and a plurality of second data centers included in a second area that is different from the first area; A management method comprising: transmitting, to a first management means that manages a plurality of the first data centers, information about at least one of the first data centers that is a candidate for deploying the first virtual node; and transmitting, to a second management means that manages a plurality of the second data centers, information about at least one of the second data centers that is a candidate for deploying the second virtual node.

Images