Patent ID: 12250118

DESCRIPTION OF EMBODIMENTS

Hereinafter, an embodiment of the invention will be explained with reference to the attached drawings.

However, the following embodiment is an example and the invention should not be construed to be limited by these descriptions.

FIG.1is a block diagram illustrating the functional configuration of a 5G wireless communication system to which the present embodiment is applied.

FIG.1illustrates a base station100, a 5G core network (CN: Core Network)200, and a UE (User Equipment)300.

InFIG.1, the vDU103and vCU111are constructed on an NFVI (Network Function Virtualization Infrastructure) which is an upgrade target cluster.

The base station100, known as a gNB, includes a RU (Radio Unit), a DU (Distributed Unit), and a CU (Central Unit).

The RU, the CU, and the DU constitute a radio access network (RAN: Radio Access Network).

The CU is connected to the 5G core network (CN)200.

Here, the DU and CU are each constructed by virtualization as vDUs (virtualized Distributed Units) and vCUs (virtualized Central Units).

The vDU101, vDU102, vDU103, vDU104, and vDU105perform layer processes in radio communication, including at least a physical layer.

The vCU111and vCU112perform layer processes including a radio resource control (RRC: Radio Resource Control) layer at a level higher than the layers in which the vDU101, vDU102, vDU103, vDU104, and vDU105perform processes.

Further, the vCU111and vCU112can each connect multiple vDUs.

The vCU111is connected to the vDU101and vDU102.

The vCU112is connected to the vDU103, vDU104, and vDU105.

Moreover, each of the vDU101, vDU102, vDU103, vDU104, and vDU105are connected to one or more RUs (not shown).

That is, the base station100comprises the vCU111and vCU112, the vDU101, vDU102, vDU103, vDU104, and vDU105connected to the vCU111or vCU112, and one or more RUs connected to each of the vDU101, vDU102, vDU103, vDU104, and vDU105.

Each of the one or more RUs form one or more beams, for example, by beam forming and use one of the beams to establish a connection with the UE300.

As discussed above, the vDU103and the vCU111indicated inFIG.1are constructed on an NFVI which is the upgrade target cluster.

Here, the vDU103is communicatively connected not to the vCU111, but to the vCU112.

That is, the NFVI which is the upgrade target cluster comprises one or more vDUs and/or vCUs, but the vDU103and the vCU111are not a functional collection on the RAN.

However, the present disclosure is not limited thereto and the NFVI which is the upgrade target cluster may comprise one or more vDUs and/or vCUs wherein there is a functional collection therebetween.

The 5G core network200shown inFIG.1comprises a C plane210and a U plane220.

The C plane210comprises an AUSF (Authentication Server Function) unit211, a UDM (Unified Data Management) unit212, an NRF (NF Repository Function) unit213, an AMF (Access and Mobility Management Function) unit214, an SMF (Session Management Function) unit215, and a PCF (Policy Control Function) unit216.

The U plane220comprises a UPF (User Plane Function) unit221.

The UE300is a radio terminal served by the base station100.

FIG.2is a diagram illustrating a functional block in NFV reference architecture400in a virtualized network proposed under the ETSI (European Telecommunication Standards Institute) standards.

The NFVI (Network Function Virtualization Infrastructure) assembly410comprises one or more NFVIs.

Some of the multiple NFVIs are clusters that are upgrade targets.

The multiple NFVIs are virtualization infrastructure for VNFs420which virtualize and realize hardware resources of a physical machine (server) on a virtualized layer such as a hypervisor.

Examples of hardware resources of a physical machine (server) can include a computing function, a storage function, and a network function.

Virtualized computing, virtualized storage, and a virtualized network can be realized by the NFVI assembly410.

The NFVI assembly may also be referred to simply as NFVI.

The VNFs420are application software for network functions installed so as to operate on the NFVI assembly410.

The VNFs420will sometimes be referred to as virtual nodes.

The vDU101, vDU102, vDU103, vDU104, and vDU105, the vCU111and vCU112, the AUSF unit211, the UDM unit212, the NRF unit213, the AMF unit214, the SMF unit215, the PCF unit216, and the UPF unit221inFIG.1correspond to the VNFs inFIG.2.

The EMSs (Element Management Systems)430manage FCAPS (Fault, Configuration, Accounting, Performance, Security) regarding the VNFs420.

The NFV MANO (Management and Orchestration)440comprises the NFVO (NFV Orchestrator)441, the VNFM (VNF Manager)442, and the VIM443.

The NFVO441manages and orchestrates the NFVI assembly410and the VNFs420and realizes network service on the NFVI assembly410.

In greater detail, the NFVO441allocates resources to the VNFs420and manages the VNFs420.

The NVFO441performs autohealing (automatic fault reconfiguration), autoscaling, or life cycle management of the VNFs420.

The VNFM442manages the life cycles of the VNFs420and provides event notification.

Here, the managed life cycles are cycles that begin with generation, go through updates, queries, healing, and scaling, and end with termination.

The VIM443controls the NFVI assembly410via a virtualized layer.

The VIM443performs computing, storage, and network resource management, fault monitoring of the NFVI assembly410, which is the infrastructure on which the VNFs420are executed, and monitoring of resource information.

Further, inFIG.2, of the OSS/BSS450, OSS (Operations Support Systems) is a collective term for the systems necessary for a carrier, which is a communications provider, to construct and operate services.

Of the OSS/BSS450, BSS (Business Support Systems) is a collective term for information systems used by a carrier, which is a communications provider, for charging and billing usage fees, responding to customers, or the like.

FIG.3is a diagram for explaining the configuration of the vDU101.

InFIG.3, the vDU101is constructed in line with the NFV reference architecture400illustrated inFIG.2.

Further, while the vDU101is exemplified here, the vDU102, vDU103, vDU104, and vDU105also have the same configuration.

The DU functions in the base station100are defined as VNFs in the NFV reference architecture400.

Hereinafter, a DU defined as a VNF will be referred to as a VNF (vDU)1011.

The VNF (vDU)1011comprises four VNFCs (Virtualized Network Function Components), VNFC #1, VNFC #2, VNFC #3, and VNFC #4, but is not limited thereto and comprises one or more VNFCs.

The VNFC #1, VNFC #2, VNFC #3, and VNFC #4 by which the VNF (vDU)1011is constructed are virtualized components by which the vDU101is constructed.

In the NFV reference architecture400, the VNFC #1, VNFC #2, VNFC #3, and VNFC #4 are also referred to as virtual machines (VMs: Virtual Machines).

The maximum number of VNFCs that the VNF (vDU)1011comprises is determined in accordance with the size of a virtualized resource pool1012that can be allocated for construction of the VNF (vDU)1011.

In this case, the virtualized resource pool1012is a virtualized infrastructure for the VNF (vDU)1011, corresponding to the NFVI assembly410inFIG.2.

The VNFC #1, VNFC #2, VNFC #3, and VNFC #4, the virtualization components by which the VNF (vDU)1011is constructed, are installed in the virtualized resource pool1012.

A management system500according to the present embodiment will be explained premised uponFIG.1toFIG.3discussed above.

FIG.4is a diagram illustrating the management system500according to the present embodiment.

The management system500illustrated inFIG.4comprises the NFVI assembly410, a DB460, the OSS/BSS450, and the VIM443.

The DB460stores setting information for a target cluster which is an upgrade target.

An autodiscovery flag is included in this setting information.

The autodiscovery flag is information indicating whether or not autodeployment is to be performed.

Autodeployment is a process for reconstructing a VNF in a predetermined location.

Upon the VNF being in a down state and the autodiscovery flag being set to an on state, reconstruction of the VNF is performed by autodeployment.

The OSS/BSS450performs a work process as discussed below on the autodiscovery flag.

In cases in which a VNF for which the autodiscovery flag is set to on does not exist, the NFVI assembly410performs autodeployment of the nonexistent VNF.

The VIM443restores the setting information to the upgraded target cluster.

The work process of the OSS/BSS450is a process that, in cases in which the autodiscovery flag is in the on state when the target cluster is upgraded, sets the autodiscovery flag to an off state and sets the autodiscovery flag to the on state after the upgrade of the target cluster is complete.

Here, autodeployment is not performed if the autodiscovery flag is in the off state and autodeployment is performed if the autodiscovery flag is in the on state.

According to the management system500illustrated inFIG.4, automatic reconstruction when upgrading a cluster realized by virtualization infrastructure without performing manual reconstruction such as resetting and without providing another cluster for the VNF or a reserve NFVI is possible.

As discussed above, when the VNF is in a down state, the autodiscovery flag is set to the on state in order for autodeployment to be performed.

In general, when the VNF is not in the down state, but is in an operating state, the autodiscovery flag is set to the off state.

However, in the present disclosure, the autodiscovery flag is set to the off state when upgrading a target cluster.

That is, in the present disclosure, when upgrading the target cluster, the autodiscovery flag is set to a temporary off state regardless of the VNF not being in the operating state.

Thusly, in the present disclosure, autodeployment is suppressed by setting the autodiscovery flag to the temporary off state until the upgrade is complete.

In addition, in the present disclosure, autodeployment is executed by setting the autodiscovery flag to the on state after the upgrade of the target cluster is complete.

FIG.5is a flowchart illustrating the upgrade method for a cluster which is an upgrade target according to the present embodiment.

The VIM443performs information gathering for a target cluster (S1: information gathering for target cluster).

The VIM443obtains setting information via the S1 process.

Upgrade version information and deployment information are included in the setting information.

The upgrade version information includes both present version information for the cluster which is the upgrade target and version information to then be upgraded to.

The deployment information includes information used in the process for reconstructing the VNF and includes information on the location at which the VNF is reconstructed and the like.

The VIM443stores the setting information for the target cluster, which is the upgrade target, in the DB460(S2: backup). The autodiscovery flag in the backed-up setting information is in the on state at this point in time.

The OSS/BSS450performs a work process on the setting information including the autodiscovery flag (S3: DB work process). As discussed previously, the autodiscovery flag is thereby set to the off state after this work process.

The work process may be performed until the upgrade is complete.

The OSS/BSS450requests the upgrade of the target cluster, which is the upgrade target, of the VIM443.

The VIM443executes the upgrade of the target cluster included in the NFVI assembly410due to the request from the OSS/BSS450(S4: upgrade).

The VIM443determines whether or not the upgrade is complete (S5; completion determination) and, when the upgrade of all the target clusters is not complete, executes the upgrade on the target clusters in which the upgrade is not complete (S4).

The VIM443restores the work-processed setting information to the upgraded target cluster via the OSS/BSS450(S6: restore).

Thereafter, all the virtual machines are activated (S7: virtual machine activation).

FIG.6is a sequence diagram of the management system500according to the present embodiment.

First, the VIM443obtains the upgrade version information and deployment information from the OSS/BSS450.

Then the VIM443performs a backup to the DB460.

The OSS/BSS450performs a work process on the setting information including the autodiscovery flag.

However, as discussed above, the work process may be performed until the upgrade is complete.

The OSS/BSS450requests the VIM443to execute the upgrade.

The VIM443executes the upgrade.

After the upgrade is complete, the VIM443performs a restore to the upgraded target cluster.

Here, because the setting information of the autodiscovery flag being in the on state is restored, the autodiscovery flag is in the on state and autodeployment of applications to the NFVI assembly410is performed.

Therefore, automatic reconstruction of applications after the upgrade becomes possible.

FIG.7is a diagram illustrating a computer system600for implementing the NFVI assembly410.

The computer system600includes one or more processors610, one or more storage units620, and one or more communication units630.

The processor610operates in accordance with a program installed in the computer system600.

Examples of the processor610can include a CPU (Central Processing Unit) and an MPU (micro processing unit).

The storage unit620stores a program or the like to be executed by a processor610.

The program may be stored on a computer-readable non-transitory storage medium.

Examples of the storage unit620can include a ROM (Read Only Memory), a RAM (Random Access Memory), an SSD (Solid State Drive), and an HDD (Hard Disk Drive).

The communication unit630exchanges data outside the computer system600, for example, with the base station100or the 5G core network200.

Examples of the communication unit630can include communications interfaces such as an NIC (Network Interface Card) and a wireless LAN (Local Area Network) module.

SDN (Software-Defined Networking) may be installed.

(1) to (5) below are included in the above-explained present disclosure.

(1) A management system comprising: an NFVI which, when a VNF in which an autodiscovery flag included in setting information is set to on does not exist, performs autodeployment of the nonexistent VNF;a DB which stores setting information for a target cluster within the NFVI that is an upgrade target;an OSS which performs a work process on the autodiscovery flag included in the setting information for the target cluster stored in the DB; and a VIM which restores the work-processed setting information to the upgraded target cluster.

(2) The management system according to (1), wherein, in the work process of the OSS,when the autodiscovery flag is in an on state when upgrading the target cluster, the autodiscovery flag is set to an off state in which autodeployment is not performed, andafter completion of the upgrade of the target cluster, the autodiscovery flag is set to the on state in which autodeployment is performed.

(3) The management system according to (2), wherein the autodiscovery flag is put in the on state by restoring setting information of the on state.

(4) The management system according to (1), wherein the autodiscovery flag is information indicating whether or not autodeployment is to be performed on the VNF.

(5) An upgrade method for a cluster that constructs a RAN and is realized by virtualization infrastructure, comprising:storing setting information for a target cluster, which is an upgrade target, in a DB;performing a work process on an autodiscovery flag which is included in the setting information for the target cluster stored in the DB and indicates whether or not autodeployment is to be performed, andrestoring the setting information to the upgraded target cluster.

As explained above, according to the present embodiment, automatic reconstruction when upgrading a cluster realized by virtualization infrastructure without performing manual reconstruction such as resetting is possible by setting the autodiscovery flag to the off state in the period from initiation to completion of the upgrade and setting the autodiscovery flag to the on state after the upgrade is complete.

Examples constructed in accordance with NFV reference architecture were explained for the present embodiment, but the present disclosure is not limited thereby and may be applied to configurations in which container-type virtualization technology is applied.

In configurations in which container-type virtualization technology is applied, the virtualized components correspond to the VNFs, the management unit corresponds to the VIM, and the control unit corresponds to the OSS.

Further, the present disclosure is not limited to the embodiments discussed above and includes various modified examples in which constituent elements have been added, removed, or replaced with respect to the configurations discussed above.

The term “connect” used in the present disclosure means a logical connection for communication.

For example, “an RU connected to a DU” means the DU and the RU are logically connected such that communication therebetween is possible.

Accordingly, there is no need for the DU and the RU to be directly connected physically by a physical cable or the like and multiple apparatuses or radio communications may also be disposed between the DU and the RU.