KR20220060988A - Method and apparatus of hybrid virtualization for cloud base station - Google Patents

Abstract

A hybrid virtualization technology for a cloud base station is disclosed. A method of operating a cloud base station comprising a central node and a distribution node in a communication system, the method comprising: virtualizing, by a hypervisor of the central node, network functions of a central unit of the central node in a hypervisor manner; virtualizing, by the container engine of the distribution node, network functions of the distribution unit of the distribution node in a container manner; establishing a first link between the central unit and the distribution unit to exchange real-time data; and exchanging virtualization control data by establishing a second link between the hypervisor and the container engine.

Description

Hybrid virtualization method and apparatus for cloud base station

The present invention relates to a hybrid virtualization technology for a cloud base station, and more particularly, to a hybrid virtualization technology for a cloud base station so that the characteristics of a central node and a distribution node are well reflected in a cloud base station in which the functions of the base station are divided and operated will be.

4G (4th Generation) communication system (e.g., LTE (Long Term Evolution) communication system, LTE-A (Advanced) communication system) for the processing of rapidly increasing wireless data after the commercialization of the frequency band of the 4G communication system ( For example, a 5th generation (5G) communication system (eg, NR (New Radio) communication system) is being considered. The 5G communication system may support enhanced Mobile BroadBand (eMBB), Ultra-Reliable and Low Latency Communication (URLLC), and Massive Machine Type Communication (mMTC).

Such a 5G communication system may pursue a variety of services based on advanced network functions, and may have a strategy to accommodate various services using a single virtualized infrastructure for network efficiency. That is, the 5G communication system uses a virtualization technique called network slicing to create a number of logically isolated networks using one physical network so that each network can have different characteristics. there is.

For service integrity, such network slicing can be done end-to-end. And, for this, most network functions of the base station may be operated based on virtualization. On the other hand, the base station may have many real-time processing elements, and may be based on a large number of small processing devices because it directly deals with the user through wireless. In addition, since the base station is placed in the field, failure may occur frequently depending on the environment. Therefore, a virtualization method that well supports the characteristics of such a base station may be required.

It is an object of the present invention to solve the above problems, in detail, a hybrid virtualization method and apparatus for a cloud base station so that the characteristics of a central node and a distribution node are well reflected in a cloud base station in which the functions of the base station are divided and operated is to provide

A hybrid virtualization method for a cloud base station according to a first embodiment of the present invention for achieving the above object is an operating method of a cloud base station comprising a central node and a distribution node in a communication system, wherein the hypervisor of the central node is the virtualizing network functions of a central unit of the central node in a hypervisor manner; virtualizing, by the container engine of the distribution node, network functions of the distribution unit of the distribution node in a container manner; establishing a first link between the central unit and the distribution unit to exchange real-time data; and establishing a second link between the hypervisor and the container engine to exchange virtualization control data.

According to the present invention, it is possible to maximize isolation and flexibility due to the use of virtual resources by virtualizing a central node that can include a small number of real-time network functions in a hypervisor method.

In addition, according to the present invention, it is possible to guarantee real-time processing due to actual resource use by virtualizing distribution nodes, which can include many real-time network functions, based on containers.

In addition, according to the present invention, it is possible to manage a small scale and a large number of hosts with low cost and high efficiency by virtualizing distribution nodes in a container manner, and to quickly cope with a failure situation.

In addition, according to the present invention, the connection link can be constructed by dividing it into two types: a real-time link and a general link.

In addition, according to the present invention, virtualization control can be performed using a general link, and a connection between network functions can be performed using a real-time link so that real-time performance is not deteriorated due to function separation.

1 is a conceptual diagram illustrating a first embodiment of a communication system.
2 is a block diagram illustrating a first embodiment of communication nodes constituting a communication system.
3 is a conceptual diagram illustrating a first embodiment of a cloud base station.
4 is a conceptual diagram illustrating a second embodiment of a cloud base station.
5 is a conceptual diagram illustrating a third embodiment of a cloud base station.
6 is a block diagram illustrating a first embodiment of a hybrid virtualization device for a cloud base station.
7 is a block diagram illustrating a second embodiment of a hybrid virtualization device for a cloud base station.
8 is a flowchart illustrating a first embodiment of a hybrid virtualization method for a cloud base station.
9 is a block diagram illustrating a first method of a communication structure for virtualization control between a hypervisor and a container.
10 is a block diagram illustrating a second method of a communication structure for virtualization control between a hypervisor and a container.
11 is a block diagram illustrating a third method of a communication structure for virtualization control between a hypervisor and a container.

Since the present invention can have various changes and can have various embodiments, specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present invention to specific embodiments, and it should be understood to include all modifications, equivalents and substitutes included in the spirit and scope of the present invention.

Terms such as first, second, etc. may be used to describe various elements, but the elements should not be limited by the terms. The above terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, a first component may be referred to as a second component, and similarly, a second component may also be referred to as a first component. and/or includes a combination of a plurality of related listed items or any of a plurality of related listed items.

When an element is referred to as being “connected” or “connected” to another element, it is understood that it may be directly connected or connected to the other element, but other elements may exist in between. it should be On the other hand, when it is said that a certain element is "directly connected" or "directly connected" to another element, it should be understood that the other element does not exist in the middle.

The terms used in the present application are only used to describe specific embodiments, and are not intended to limit the present invention. The singular expression includes the plural expression unless the context clearly dictates otherwise. In the present application, terms such as “comprise” or “have” are intended to designate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, but one or more other features It should be understood that this does not preclude the existence or addition of numbers, steps, operations, components, parts, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical and scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in a commonly used dictionary should be interpreted as having a meaning consistent with the meaning in the context of the related art, and should not be interpreted in an ideal or excessively formal meaning unless explicitly defined in the present application. does not

Hereinafter, preferred embodiments of the present invention will be described in more detail with reference to the accompanying drawings. In describing the present invention, in order to facilitate the overall understanding, the same reference numerals are used for the same components in the drawings, and duplicate descriptions of the same components are omitted.

1 is a conceptual diagram illustrating a first embodiment of a communication system.

1, the communication system 100 is a plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Here, the communication system may be referred to as a “communication network”. Each of the plurality of communication nodes may support at least one communication protocol. For example, each of the plurality of communication nodes may include a code division multiple access (CDMA)-based communication protocol, a wideband CDMA (WCDMA)-based communication protocol, a time division multiple access (TDMA)-based communication protocol, and a frequency division multiple (FDMA)-based communication protocol. access) based communication protocol, OFDM (orthogonal frequency division multiplexing) based communication protocol, OFDMA (orthogonal frequency division multiple access) based communication protocol, SC (single carrier)-FDMA based communication protocol, NOMA (non-orthogonal multiple) access)-based communication protocol, space division multiple access (SDMA)-based communication protocol, etc. may be supported. Each of the plurality of communication nodes may have the following structure.

2 is a block diagram showing a first embodiment of a communication node constituting a communication system.

Referring to FIG. 2 , the communication node 200 may include at least one processor 210 , a memory 220 , and a transceiver 230 connected to a network to perform communication. In addition, the communication node 200 may further include an input interface device 240 , an output interface device 250 , a storage device 260 , and the like. Each of the components included in the communication node 200 may be connected by a bus 270 to communicate with each other. However, each of the components included in the communication node 200 may not be connected to the common bus 270 but to the processor 210 through an individual interface or an individual bus. For example, the processor 210 may be connected to at least one of the memory 220 , the transceiver 230 , the input interface device 240 , the output interface device 250 , and the storage device 260 through a dedicated interface. .

The processor 210 may execute a program command stored in at least one of the memory 220 and the storage device 260 . The processor 210 may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which methods according to embodiments of the present invention are performed. Each of the memory 220 and the storage device 260 may be configured as at least one of a volatile storage medium and a non-volatile storage medium. For example, the memory 220 may be configured as at least one of a read only memory (ROM) and a random access memory (RAM).

Referring back to FIG. 1 , the communication system 100 includes a plurality of base stations 110-1, 110-2, 110-3, 120-1, 120-2, and a plurality of terminals. (130-1, 130-2, 130-3, 130-4, 130-5, 130-6). Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may form a macro cell. Each of the fourth base station 120-1 and the fifth base station 120-2 may form a small cell. The fourth base station 120-1, the third terminal 130-3, and the fourth terminal 130-4 may belong to the coverage of the first base station 110-1. The second terminal 130-2, the fourth terminal 130-4, and the fifth terminal 130-5 may belong to the coverage of the second base station 110-2. The fifth base station 120-2, the fourth terminal 130-4, the fifth terminal 130-5, and the sixth terminal 130-6 may belong within the coverage of the third base station 110-3. . The first terminal 130-1 may belong to the coverage of the fourth base station 120-1. The sixth terminal 130-6 may belong to the coverage of the fifth base station 120-2.

Here, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, 120-2 is a NodeB (NodeB), an advanced NodeB (evolved NodeB), a BTS (base transceiver station), A radio base station, a radio transceiver, an access point, an access node, a road side unit (RSU), a digital unit (DU), a cloud digital unit (CDU) , a radio remote head (RRH), a radio unit (RU), a transmission point (TP), a transmission and reception point (TRP), a relay node, and the like. Each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 is an access terminal, a mobile terminal, a station, It may be referred to as a subscriber station, a mobile station, a portable subscriber station, user equipment (UE), a node, a device, and the like.

A plurality of communication nodes (110-1, 110-2, 110-3, 120-1, 120-2, 130-1, 130-2, 130-3, 130-4, 130-5, 130-6) Each may support cellular (cellular) communication (eg, long term evolution (LTE), LTE-A (advanced), etc. defined in the 3rd generation partnership project (3GPP) standard). Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may operate in different frequency bands or may operate in the same frequency band. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to each other through an ideal backhaul or a non-ideal backhaul, and the ideal backhaul Alternatively, information may be exchanged with each other through a non-ideal backhaul. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may be connected to a core network (not shown) through an ideal backhaul or a non-ideal backhaul. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits a signal received from the core network to the corresponding terminals 130-1, 130-2, 130-3, 130 -4, 130-5, 130-6), and a signal received from the corresponding terminal (130-1, 130-2, 130-3, 130-4, 130-5, 130-6) is transmitted to the core network can be sent to

Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 may support OFDMA-based downlink (DL) transmission, and SC-FDMA-based uplink (uplink, UL) transmission may be supported. In addition, each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 transmits multiple input multiple output (MIMO) (eg, single user (SU)-MIMO, MU (multi user)-MIMO, massive MIMO, etc.), coordinated multipoint (CoMP) transmission, carrier aggregation transmission, transmission in an unlicensed band, device to device, D2D ) communication (or Proximity services (ProSe), etc.), etc. Here, each of the plurality of terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6 is a base station. (110-1, 110-2, 110-3, 120-1, 120-2) and corresponding operation, by the base station (110-1, 110-2, 110-3, 120-1, 120-2) Supported actions can be performed.

For example, the second base station 110-2 may transmit a signal to the fourth terminal 130-4 based on the SU-MIMO method, and the fourth terminal 130-4 may transmit a signal based on the SU-MIMO method. A signal may be received from the second base station 110 - 2 . Alternatively, the second base station 110 - 2 may transmit a signal to the fourth terminal 130 - 4 and the fifth terminal 130 - 5 based on the MU-MIMO scheme, and the fourth terminal 130 - 4 . and each of the fifth terminals 130 - 5 may receive a signal from the second base station 110 - 2 by the MU-MIMO method. Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 may transmit a signal to the fourth terminal 130-4 based on the CoMP scheme, and the fourth The terminal 130-4 may receive signals from the first base station 110-1, the second base station 110-2, and the third base station 110-3 by the CoMP method. Each of the plurality of base stations 110-1, 110-2, 110-3, 120-1, and 120-2 includes the terminals 130-1, 130-2, 130-3, 130-4, 130-5, 130-6) and a signal may be transmitted/received based on the CA method. Each of the first base station 110-1, the second base station 110-2, and the third base station 110-3 coordinates D2D communication between the fourth terminal 130-4 and the fifth terminal 130-5. (coordination), each of the fourth terminal 130-4 and the fifth terminal 130-5 is D2D communication by the coordination of each of the second base station 110-2 and the third base station 110-3 can be performed.

On the other hand, in such a communication system, the 5G communication system can pursue a variety of services based on an advanced network function, and can have a strategy to accommodate various services using a single virtualized infrastructure for network efficiency. . That is, the 5G communication system can use a virtualization technique called network slicing to create a plurality of logically isolated networks using one physical network so that each network can have different characteristics. The traditional method of virtualizing a network may be a method to abstract real resources into virtual resources by placing a middleware layer called a hypervisor on the host operating system. In this hypervisor method, only virtual resources are Virtual machines (VMs) with an independent guest operating system (guest OS) used may exist on the top, and in a hypervisor method, an application program may perform a unique network function within the virtual machine.

The second method of virtualizing the network may be a method of sharing the kernel of the host operating system in the guest program without putting a virtual machine equipped with a separate operating system thereon. In this method, called the container method, virtual resources may not be used, and real resources of the host may be used together. In this container method, a control program called a container engine is placed for an isolation effect, and a process ID, a network device and address, a runtime library, an operating system configuration file, etc. can be independently operated differently from the host operating system.

Meanwhile, in the hypervisor method, since the host operating system and the guest operating system are completely separated by the hypervisor, isolation can be greatly guaranteed. However, since virtual machines above the hypervisor use virtual resources abstracted through the hypervisor, performance may be degraded compared to actual resource usage. In particular, input/output device resources may result in an increase in latency. Such an increase in latency may act as an obstacle in virtualizing a network function such as a base station including a number of real-time functions. In addition, in the hypervisor method, it may take a lot of time and money to prepare a new virtual machine due to an independent guest operating system operation.

Next, in the container method, an application program may not use a virtual resource, and since it uses an actual resource, performance degradation may not occur due to the use of the virtual resource. In addition, the container method can ensure isolation and portability because identifier mapping is performed by the container engine. However, the container method cannot guarantee complete isolation because the host operating system kernel is shared by guest applications, which may affect each other between the host and the guest or between the guest and the guest. However, in the container method, the time and cost for preparing a new container may be significantly smaller than that of the hypervisor.

Meanwhile, the cloud base station may be a method of disposing and operating a base station by dividing the base station function into a central node function and a distributed node function. Here, the central node may be integrated, may mean a centralized common area, and may be an area independent of an area where radio signals are generated by radio frequency (RF) and antennas. In addition, the distribution node may be a region related to an action of a mobile communication user receiving a service using a terminal. Communication can be performed between the central node and the distribution node using a connection means called a front haul. Functional division of the cloud base station may exist in various ways depending on the performance of the fronthaul, the capabilities of the performing nodes, the environment of the distribution node, and the like. The execution node of the central node may be referred to as a central unit (CU), and the execution node of the distribution node may be referred to as a distributed unit (DU). The distribution unit may be further divided into a remote access unit (RAU) and a remote radio unit (RRU). The cloud base station may have a characteristic that the real-time property may be lowered toward the central node, and the real-time property may be increased toward the distribution node.

The fronthaul is a network that connects separated layers, and various interface types are defined by various standardization organizations. IF1 (interface 1), nFAPI (network functional application platform interface), IF4.5, IF5, etc. can be used a lot. IF1 may be an interface connecting upper splitting points. nFAPI, IF5, IF4.5 may be interfaces for connecting lower split points. nFAPI, IF5, and IF4.5 may require real-time performance in terms of bandwidth or latency. In particular, nFAPI can satisfy very strict latency requirements because it performs a function of connecting between the MAC (medium access control) layer and the PHY (physical) layer, respectively. In addition, IF4.5 and IF5 perform the function of connecting the upper PHY(PHY-H) and the lower PHY(PHY), respectively, so very strict latency requirements can be satisfied.

3 is a conceptual diagram illustrating a first embodiment of a cloud base station.

Referring to FIG. 3 , the cloud base station may include a central unit 310 and a distribution unit 320 . The central unit 310 may include a general packet radio service (GPRS) tunneling protocol (GTP) layer 311, a packet data convergence protocol (PDCP) layer 312, and a radio resource control (RRC) layer 313. . In addition, the distribution unit 320 may include a radio link control (RLC) layer 321 , a MAC layer 322 , a PHY layer 323 , and an RF layer 324 . The central unit 310 and the distribution unit 320 may be connected using an IF1 interface.

4 is a conceptual diagram illustrating a second embodiment of a cloud base station.

Referring to FIG. 4 , the cloud base station may include a central unit 410 and a distribution unit 420 . The central unit 410 may include a GTP layer 411 , a PDCP layer 412 , an RRC layer 413 , an RLC layer 414 , a MAC layer 415 , and a PHY-H layer 416 . In addition, the distribution unit 420 may include a PHY layer 421 and an RF layer 422 . The central unit 410 and the distribution unit 420 can be connected using one interface in IF4.5, IF5 and nFAPI interfaces. Here, the PHY-H layer 421 indicated by a solid line may mean that if the PHY layer can be divided into upper and lower parts, the upper may be the PHY-H layer, and the lower may be the PHY layer. In addition, if the PHY-H layer 421 is indicated by a solid line, if the PHY layer is not divided into upper and lower parts, it may mean that there may be no PHY-H layer and only the PHY layer may exist.

5 is a conceptual diagram illustrating a third embodiment of a cloud base station.

Referring to FIG. 5 , the cloud base station may include a central unit 510 , a remote access unit 520 , and a remote wireless unit 530 . The central unit 510 may include a GTP layer 511 , a PDCP layer 512 , and an RRC layer 513 . In addition, the remote access unit 520 may include an RLC layer 521 , a MAC layer 522 , and a PHY-H layer 523 . Here, the PHY-H layer 523 indicated by a solid line may mean that if the PHY layer can be divided into upper and lower parts, the upper may be the PHY-H layer, and the lower may be the PHY layer. In addition, the PHY-H layer 523 indicated by a solid line may mean that if the PHY layer is not divided into upper and lower parts, there may be no PHY-H layer and only the PHY layer may exist. Next, the remote wireless unit 530 may include a PHY layer 531 and an RF layer 532 . The central unit 510 and the remote access unit 520 may be connected using an IF1 interface. In addition, the remote access unit 520 and the remote wireless unit 530 may connect using one interface in IF4.5, IF5 and nFAPI interfaces.

Meanwhile, a conventional method for virtualizing a cloud base station may be a method of operating a central unit in a hypervisor manner. Since the central unit is composed of a virtual network function (VNF), which is a network function that does not require strict real-time processing, virtualization can be easy. However, since a distribution unit, a remote access unit, and a remote wireless unit are composed of a physical network function (PNF), which is a network function that requires strict real-time processing, virtualization that satisfies the real-time requirement may be difficult to proceed. Network slicing that realizes service diversity and network flexibility can be based on virtualization of constituting network functions, and the higher the level of virtualization, the more complete network slicing can be. Accordingly, there may exist a requirement to virtualize the network functions in the distribution unit, remote access unit, and remote wireless unit classified as PNFs as much as possible.

A method of virtualizing network functions in a distribution unit, remote access unit, and remote radio unit in a hypervisor manner, as in the case of a central unit, may have several issues. First, performing a function based on a virtual machine using a virtual resource may cause performance degradation due to overhead. If the latency increases or becomes irregular in the same place as the input/output device, real-time execution may not be possible. Second, distribution nodes such as distribution units, remote access units, and remote radio units are systems with small processing capacity, and hypervisors and heavy virtualization techniques may be inefficient in terms of cost or performance. Third, since there will be multiple distribution nodes, an efficient virtualization management device to manage them may be required. Fourth, a virtualization technique that can quickly respond to the failure of the network function of the distribution node may be required.

For service integrity, network slicing can be done user-to-user. And, for this, most network functions of the base station may be operated based on virtualization. The base station has many real-time processing elements, and because it directly deals with users through wireless, it can be based on a number of small processing units. In addition, the base station may have a characteristic that failure may occur frequently depending on the environment as it is disposed in the field. Therefore, the 5G NR communication system may require a virtualization method that well supports the characteristics of such a base station.

6 is a block diagram illustrating a first embodiment of a hybrid virtualization device for a cloud base station.

Referring to FIG. 6 , a hybrid virtualization apparatus for a cloud base station may include a first host 610 virtualized by a hypervisor method as a central node and a second host 620 virtualized by a container method as a distribution node. Here, the first host 610 may include a central unit 611 and a hypervisor 612 for virtualizing network functions of the central unit 611 in a hypervisor manner. In addition, the second host 620 may include a distribution unit 621 and a container engine 622 for virtualizing network functions of the distribution unit 621 in a container manner.

As such, a hybrid virtualization device for a cloud base station may virtualize a central node in a hypervisor method and virtualize a distribution node in a container method. Network functions of the central unit 611 of the first host 610 may be performed by the virtualized hypervisor 612 . Network functions of the distribution unit 621 of the second host 620 may be performed in the virtualized container engine 622 . The first host 610 and the second host 620 may establish a first link 631 and a second link 632 . The first link 631 may be established between the hypervisor 612 and the container engine 622 , and may be mainly used for controlling a virtualization method between the hypervisor 612 and the container engine 622 . The second link 632 may be established between the central unit 611 and the distribution unit 621 , and may be mainly used for real-time data exchange between the central unit 611 and the distribution unit 621 . The first link 631 does not have to satisfy high bandwidth or strict latency requirements, but the second link 632 may satisfy high bandwidth or strict latency requirements depending on the nature of network functions to be connected. If a network function to be connected does not require high bandwidth or strict latency between PDCP-RLC, for example, the first link 631 may be used.

7 is a block diagram illustrating a second embodiment of a hybrid virtualization device for a cloud base station.

Referring to FIG. 7 , a hybrid virtualization device for a cloud base station includes a first host 710 virtualized by a hypervisor method as a central node, a second host 720 virtualized by a container method as a distribution node, and a container method as a distribution node. may include a virtualized third host 730 . Here, the first host 710 may include a central unit 711 and a hypervisor 712 for virtualizing network functions of the central unit 711 in a hypervisor manner. In addition, the second host 720 may include a remote access unit 721 and a first container engine 722 for virtualizing network functions of the remote access unit 721 in a container manner. Next, the third host 730 may include a remote wireless unit 731 and a second container engine 732 for virtualizing network functions of the remote wireless unit 731 in a container manner.

As such, a hybrid virtualization device for a cloud base station may virtualize a central node in a hypervisor method and virtualize a distribution node in a container method. Network functions of the central unit 711 of the first host 710 may be performed in the virtualized hypervisor 712 . In addition, network functions of the remote access unit 721 of the second host 720 may be performed in the virtualized first container engine 722 . In addition, network functions of the remote wireless unit 731 of the third host 730 may be performed in the virtualized second container engine 732 . The first host 710 and the second host 720 may establish a first link 731 and a second link 732 . The first link 731 may be established between the hypervisor 712 and the first container engine 722 , and may be mainly used for controlling a virtualization method between the hypervisor 712 and the first container engine 722 . . The second link 732 may be established between the central unit 711 and the remote access unit 721 , and may be mainly used for real-time data exchange between the central unit 711 and the remote access unit 721 . Next, the second host 720 and the third host 730 may establish a third link 733 and a fourth link 734 . The third link 733 may be established between the first container engine 722 and the second container engine 732 , and for controlling a virtualization method between the first container engine 722 and the second container engine 732 . can be mainly used. The fourth link 734 may be established between the remote access unit 721 and the remote wireless unit 731 , and may be mainly used for real-time data exchange between the remote access unit 721 and the remote wireless unit 731 . Here, the first link 631 and the third link 633 do not have to satisfy high bandwidth or strict latency requirements, but the second link 632 and the fourth link 634 have characteristics of network functions to be connected. As a result, high bandwidth or stringent latency requirements can be satisfied. If the network function to be connected does not require high bandwidth or strict latency between PDCP-RLC, for example, the first link 731 may be used.

As such, the hybrid virtualization device for the cloud base station can maximize isolation and flexibility due to the use of virtual resources by virtualizing the central node, which can include a small number of real-time network functions, in a hypervisor method. On the other hand, a hybrid virtualization device for a cloud base station can guarantee real-time processing due to actual resource use by virtualizing distribution nodes that can include many real-time network functions based on a container, and can manage small-scale and multiple hosts. It can be managed with low cost and high efficiency, and it can respond quickly to failure situations. In addition, the hybrid virtualization device for the cloud base station can be constructed by dividing the connection link into two types of a real-time link and a general link. Accordingly, the hybrid virtualization device for the cloud base station may perform virtualization control using a general link, and may perform a connection between network functions using a real-time link so that real-time performance is not deteriorated due to function separation.

8 is a flowchart illustrating a first embodiment of a hybrid virtualization method for a cloud base station.

Referring to FIG. 8 , in the hybrid virtualization method for the cloud base station, the hypervisor of the cloud base station may virtualize network functions of the central unit of the central node in a hypervisor manner ( S801 ). In addition, the container engine of the cloud base station may virtualize network functions of the distribution unit of the distribution node in a container manner ( S802 ). Thereafter, the central unit and the distribution unit of the cloud base station may establish a first link to exchange real-time data ( S803 ). In addition, the hypervisor of the cloud base station and the container engine may connect the second link to exchange virtualization control data (S804).

9, 10 and 11 are block diagrams illustrating (for all embodiments) three alternative methods of communication architecture for virtualization control between a hypervisor and a container.

9 is a block diagram illustrating a first method of a communication structure for virtualization control between a hypervisor and a container.

Referring to FIG. 9 , the communication structure for virtualization control between the hypervisor and the container includes a central unit 911, a hypervisor 912, a virtual container engine 913 and a virtual container engine operating on top of the hypervisor 912 ( 913) can be implemented as one host 910 including a gateway 914 operated at the top. Here, the virtual container engine 913 may correspond to the container engine of the distribution node. Accordingly, the virtual container engine 913 may receive a virtualization control signal from the container engine of the distribution node. Meanwhile, the gateway 914 may relay a virtualization control signal between the two virtualization methods by allowing access to both the hypervisor 912 and the virtual container engine 913 . If necessary, the gateway 914 may relay non-real-time protocol data between the central unit 911 and the distribution nodes.

10 is a block diagram illustrating a second method of a communication structure for virtualization control between a hypervisor and a container.

Referring to FIG. 10 , a communication structure for virtualization control between a hypervisor and a container includes a first host 1010 including a central unit 1011 and a hypervisor 1012, a virtual container engine 1021, and a virtual container engine ( 1021) may include a second host 1020 including a gateway 1022 operating at the top. Here, the virtual container engine 1022 may correspond to the container engine of the distribution node. Accordingly, the virtual container engine 1022 may receive a virtualization control signal from the container engine of the distribution node. Meanwhile, the gateway 1022 may relay a virtualization control signal between the two virtualization methods by allowing access to both the hypervisor 1012 and the virtual container engine 1021 . If necessary, the gateway 1022 may relay non-real-time protocol data between the central unit 1011 and the distribution nodes.

11 is a block diagram illustrating a third method of a communication structure for virtualization control between a hypervisor and a container.

Referring to FIG. 11 , the communication structure for virtualization control between the hypervisor and the container is a hypervisor 1111 , a virtual container engine 1112 operated on the top of the hypervisor 1111 , and a virtual container engine 1112 operated on the top It can be implemented with one host 1110 including the central unit 1113 . Here, the virtual container engine 1112 may correspond to the container engine of the distribution node. Accordingly, the virtual container engine 1112 may receive a virtualization control signal from the container engine of the distribution node. Meanwhile, control signals for virtualization between the hypervisor 1111 and the virtual container engine 1112 may be exchanged in the form of inter-layer messages. Communication of non-real-time protocol data between the central unit 1113 and the distribution nodes can be exchanged through the container network because the central unit 1113 operates on a container basis.

The methods according to the present invention may be implemented in the form of program instructions that can be executed by various computer means and recorded in a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, and the like, alone or in combination. The program instructions recorded on the computer-readable medium may be specially designed and configured for the present invention, or may be known and available to those skilled in the art of computer software. Examples of computer-readable media may include hardware devices specially configured to store and execute program instructions, such as ROM, RAM, flash memory, and the like. Examples of program instructions may include not only machine language codes such as those generated by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware device described above may be configured to operate as at least one software module to perform the operations of the present invention, and vice versa.

In addition, the above-described method or apparatus may be implemented by combining all or part of its configuration or function, or may be implemented separately.

Although the above has been described with reference to preferred embodiments of the present invention, those skilled in the art can variously modify and change the present invention within the scope without departing from the spirit and scope of the present invention as set forth in the claims below. You will understand that it can be done.

Claims (1)

A method of operating a cloud base station comprising a central node and a distribution node in a communication system, the method comprising:
virtualizing, by the hypervisor of the central node, network functions of the central unit of the central node in a hypervisor manner;
virtualizing, by the container engine of the distribution node, network functions of the distribution unit of the distribution node in a container manner;
establishing a first link between the central unit and the distribution unit to exchange real-time data; and
The method of operating a cloud base station, comprising the step of establishing a second link between the hypervisor and the container engine to exchange virtualization control data.

Images