KR20210007788A - Method and apparatus therefor for providing service high availability through gnb relocation - Google Patents

Abstract

The present disclosure relates to a communication technique for converging a 5G communication system for supporting a higher data rate after a 4G system with IoT technology, and a system thereof. The present disclosure can be applied to intelligent services (eg, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on 5G communication technology and IoT-related technology. A control signal processing method comprises the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

Description

Method for providing high availability service through GNB reallocation and device for it {METHOD AND APPARATUS THEREFOR FOR PROVIDING SERVICE HIGH AVAILABILITY THROUGH GNB RELOCATION}

The present invention provides high availability of a function that detects gNB-CU failures composed of virtualized network equipment (VNF) and restores normal by quickly relocating the gNB-CU to an adjacent gNB-CU in the event of a disaster such as an earthquake or a large power outage. (HA: High Availability) provision method and apparatus for this are provided. In addition, by configuring an HA Cluster Group, resources of the gNB-CU within the group are monitored, and the service is resumed to the gNB-CU where resources are available, thereby increasing resource utilization. That is, it is possible to save CAPEX (Capital Expenditure) and OPEX (Operation Expenditure) because the configuration of the standby side for failure and disaster recovery is unnecessary. Moreover, by storing data in real time outside, it is possible to provide the latest RPO (Recovery Point Object) during service recovery.

Efforts are being made to develop an improved 5G communication system or a pre-5G communication system in order to meet the increasing demand for wireless data traffic after the commercialization of 4G communication systems. For this reason, a 5G communication system or a pre-5G communication system is called a Beyond 4G Network communication system or an LTE system and a Post LTE system. In order to achieve a high data rate, the 5G communication system is being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Giga (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, in 5G communication systems, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, in order to improve the network of the system, in 5G communication system, advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation And other technologies are being developed. In addition, in the 5G system, advanced coding modulation (ACM) methods such as Hybrid FSK and QAM Modulation (FQAM) and SWSC (Sliding Window Superposition Coding), advanced access technologies such as Filter Bank Multi Carrier (FBMC), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) have been developed.

On the other hand, the Internet is evolving from a human-centered network in which humans generate and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection with cloud servers, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, machine to machine , M2M), and MTC (Machine Type Communication) technologies are being studied. In the IoT environment, intelligent IT (Internet Technology) services that create new value in human life by collecting and analyzing data generated from connected objects can be provided. IoT is the field of smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliance, advanced medical service, etc. through the convergence and combination of existing IT (information technology) technology and various industries. Can be applied to.

Accordingly, various attempts have been made to apply a 5G communication system to an IoT network. For example, technologies such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication) are implemented by techniques such as beamforming, MIMO, and array antenna, which are 5G communication technologies. will be. As the big data processing technology described above, a cloud radio access network (cloud RAN) is applied as an example of the convergence of 5G technology and IoT technology.

The service recovery function for network equipment can ensure service continuity after a disaster such as a severe failure, earthquake or large-scale power outage, which makes it impossible to service the network equipment or the data center where the network equipment is deployed. Some known prior art is a VNF that configures a standby side in preparation for a failure and waits, transfers the service in operation when a failure occurs, and resumes recovery, or transfers the service of the occurrence device when the orchestrator detects a failure in an NFV (Network Function Virtualization) environment. The service was restored by additional creation.

A problem of the above-described prior art is that unnecessary CAPEX (Capital Expenditure) and OPEX (Operation Expenditure) costs increase by waiting for resources on the standby side that are not serviced. In addition, service recovery through the creation of a Virtualized Network Function (VNF) in an NFV (Network Function Virtualization) environment has a problem in that the Recovery Time Object (RTO) increases due to an increase in the recovery time according to the additional creation.

The present invention for solving the above problem is a control signal processing method in a wireless communication system, the method comprising: receiving a first control signal transmitted from a base station; Processing the received first control signal; And transmitting a second control signal generated based on the processing to the base station.

The present invention was derived to solve the above-described problem, and its purpose is to make all the gNB-CUs to be operated in an active state, and to configure the HA Cluster Group by grouping the operated gNB-CUs and Data Centers into a cluster. It manages resources and provides a quick recovery service with the latest data before the failure without waiting for standby resources or creating additional resources by performing restoration to the adjacent gNB-CU where available resources have been identified when a failure occurs.

Another object of the present invention is to prepare for the occurrence of a single gNB-CU failure and a disaster such as an earthquake or a large power outage by not fixing the object to be restored. In other words, in the event of a single gNB-CU failure, the logical gNB is relocated to the adjacent gNB-CU in the Intra Data Center and restored, thereby minimizing the latency between the gNB-CU and the gNB-DU due to the change of the gNB-CU. In the event of a large-scale failure due to a large-scale failure, it is possible to recover to other adjacent data centers, thereby providing a recovery flexibility function.

According to the present invention, a failure or disaster event is detected in advance through a separate equipment (HAC) that monitors the status of the gNB-CU and Data Center in real time, and the logical gNBs are quickly relocated, and when a single gNB-CU failure occurs. In the following, logical gNBs can be relocated to gNB-CUs in the same data center, or first relocated to gNB-CUs in adjacent data centers to secure recovery flexibility without fixing the recovery target. In addition, even if a disaster occurs in which the data center becomes inoperable through the same mechanism, logical gNBs within the data center are distributed and relocated to adjacent data centers, so there is no need to wait for resources on the standby side. It is grouped into a cluster to enable management.

Accordingly, CAPEX (Capital Expenditure) is saved because there is no need to create unnecessary resources and wait, and OPEX (Operation Expenditure) savings as all gNB-CUs are operated in an active state, failure and disaster events are quickly detected and service resumed. Efficient high availability can be secured by shortening the RTO (Recover Time Objective).

1 is a diagram showing a configuration for supporting high availability through a gNB-CU and an HA controller in a data center according to an embodiment of the present invention.
2 is a diagram illustrating an HA Cluster Group and a management list of a gNB-CU in an HA controller according to an embodiment of the present invention.
3 is a diagram illustrating cell resource monitoring of a gNB-CU according to an embodiment of the present invention.
4 is a diagram illustrating failure detection of a gNB-CU according to an embodiment of the present invention.
5 is a diagram illustrating a recovery target selection algorithm according to an embodiment of the present invention.
6 is a diagram illustrating relocation of a logical gNB in an Intra Data-Center according to a single gNB-CU failure according to an embodiment of the present invention.
7 is a diagram illustrating relocation of a logical gNB in an Inter Data-Center according to a large-scale gNB-CU failure according to an embodiment of the present invention.
FIG. 8 is a diagram illustrating an original restoration algorithm according to normalization of a gNB-CU according to an embodiment of the present invention.
9 is a diagram illustrating relocation of an original logical gNB according to normalization of a gNB-CU according to an embodiment of the present invention.

In order to achieve the above-described object, the gNB-CU and data centers can be managed as a cluster as an HA cluster group, and a device for resource management and service recovery target designation of the gNB-CU can be configured.

The device configured for this can monitor the resources of the gNB-CU in real time, detect failure and large-scale disaster conditions through status monitoring, and designate a logical gNB recovery target using the resources of an adjacent operating gNB-CU.

The recovery target gNB-CU, which will transfer the failed gNB-CU's logical gNB, acquires the latest data of the failed gNB-CU from the external data base system and performs configuration data recovery, and based on the data, the adjacent peer You can resume the service by reconnecting with them.

Hereinafter, embodiments of the present invention will be described in detail with reference to the accompanying drawings.

In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the present invention pertains and are not directly related to the present invention will be omitted. This is to more clearly convey the gist of the present invention by omitting unnecessary description.

For the same reason, some components in the accompanying drawings are exaggerated, omitted, or schematically illustrated. In addition, the size of each component does not fully reflect the actual size. The same reference numerals are assigned to the same or corresponding components in each drawing.

Advantages and features of the present invention, and a method of achieving them will become apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present invention is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only these embodiments make the disclosure of the present invention complete, and are common knowledge in the technical field to which the present invention pertains. It is provided to completely inform the scope of the invention to those who have, and the invention is only defined by the scope of the claims. The same reference numerals refer to the same components throughout the specification.

In the following description, a term referring to a signal, a term referring to control information, a term referring to network entities, a term referring to a component of a device, and the like are exemplified for convenience of description. Accordingly, the present disclosure is not limited to terms to be described later, and other terms having an equivalent technical meaning may be used.

In addition, the present disclosure describes various embodiments using terms used in some standards (eg, ETSI), but this is only an example for description. Various embodiments of the present disclosure may be easily modified and applied to other communication systems.

Various embodiments of the present invention provide a device that detects a rapid failure or disaster event through a separate device that monitors the state of a gNB-CU and a data center in real time, and controls to quickly relocate Logical gNBs. In addition, it provides data operation continuity by providing equipment that recovers data after Logical gNBs are relocated.

1 shows the configuration of the gNB-CU 102 disposed in each Data Center 101 and the Logical gNB 103 service in the gNB-CU 102 according to some embodiments, and the configuration of each gNB-CU 102 It is a diagram showing the HA Controller (hereinafter referred to as HAC) 100, which is a device that monitors the state of the network and manages high availability (HA).

In the configuration shown in FIG. 1, only the components related to the present embodiment are shown. Therefore, those of ordinary skill in the technical field related to the present embodiment can see that other general-purpose components other than the components shown in FIG. 1 may be further included.

1 shows the configuration of the gNB-CU 102 disposed in the Data Center 101, the Logical gNB 103 configured therein, and the HAC 100 that manages the HA of the gNB-CU 102. Are doing. Referring to FIG. 1, the gNB-CU 102 may be disposed and operated in an active state, respectively, in the Data Center 101. That is, a separate resource of the standby state for HA is not required.

In addition, each of the Logical gNBs 103 configured in the gNB-CU 102 is implemented with one or more gNBs. gNB is a new base station that is a next generation NodeB that supports interworking with 5G New Radio technology and SA (Stand Alone) Core. Logical gNB 103 is a software implementation of this gNB to provide services. Refers to.

Therefore, the user operates all gNB-CUs 102 in an active state, and even if a failure occurs in the gNB-CU 102, the user needs to wait for Standby state resources by relocating the serviced Logical gNB 103 to the adjacent gNB-CU 102. Service recovery is performed without it.

According to an embodiment of the present invention, monitoring and HA management for each gNB-CU 102 is configured to be managed by the HAC 100.

FIG. 2 is a diagram illustrating a configuration of an HA Cluster Group 200 of a gNB-CU 102 and a Cell Resource Management Table T200 of the gNB-CU 102 according to the configuration.

The table T200 shown in FIG. 2 is illustrated only with components related to the present embodiment. Accordingly, the components shown in FIG. 2 may be included in another procedure related to the present embodiment.

The table (T200) of the contents shown in FIG. 2 includes elements for status monitoring and resource monitoring of the gNB-CUs 102.

The HA Cluster Group in the Table (T200) is a group of gNB-CUs 102 that the HAC 100 will manage HA, and it detects the status of the gNB-CU 102 in the group and identifies the recoverable targets through resource monitoring. It is an item to be managed.

The DC_ID of the table (T200) is an ID to identify the Data Center 101 in which the gNB-CU 102 is located. In the event of a gNB-CU 102 failure, the Intra DC is first selected for recovery. . In other words, by relocating the Logical gNB 103 to the gNB-CU 102 in the same Data Center 101 as the gNB-CU 102 in which the failure occurred, the distance between the gNB-CU 102 and the DU increases, so that the latency does not increase. This is an item to avoid.

The Cell Count of the Table (T200) means the Cell Count currently operating in the gNB-CU 102.

Specifically, the maximum number of cell operations per configuration of the gNB-CU 102 is defined. By managing the number of current cell operations relative to the maximum number of operations, it becomes an element that can determine whether the restoration gNB-CU 102 is possible.

The gNB Status of the Table (T200) is an element that checks the service status of the Logical gNB 103 in the gNB-CU 102.

3 is a diagram illustrating a process of interworking, state detection, and message delivery between the gNB-CU 102 and the HAC 100 according to some embodiments.

When the operator sets the gNB-CU 102 and the HAC 100 to be managed, the gNB-CU 102 proceeds with the HAC registration request 300 through the TCP Message, and the HAC 100 opens the HA management list. After configuration, the HAC registration response 310 is performed to the gNB-CU 102.

Receiving the response, the gNB-CU 102 transmits a Keep-Alive Message 320 to the HAC 100 including contents of its own logical gNB information, the number of cell operations, and service operation status.

HAC (100), receiving information from the gNB-CU (102) through the Keep-Alive Message (320) monitors the available cell resources (T300) in each gNB-CU (102).

Specifically, if the maximum number of cells available to the gNB-CU 102 is 2000 and the available cell resources (T300) are 1000, the gNB-CU 102 transfers 1000 cells and provides service. It becomes a possible resource.

For example, if a failure occurs while the number of cells of the gNB-CU 102 in service operation is 1200 and it is necessary to restore 1200 cells, relocate to the gNB-CU 102 with available cell resources to resume the service. do.

4 is a diagram illustrating a process of determining a logical gNB 103 relocation by monitoring a state of a gNB-CU 102 by the HAC 100 and detecting a failure according to a case according to some embodiments.

Specifically, the HAC 100 manages the current service state of the gNB-CU 102 through the Keep-Alive Message (S400) transmitted from the gNB-CU 102. At this time, the Keep-Alive Message (S400) If a failure occurs for a certain period of time and a number of times, it is detected as Keep-Alive Failure (S401), and the connection failure status is linked with the gNB-CU 102 to determine whether a simple path is disabled or the actual gNB-CU 102 is disabled. Whether or not the status is checked through another entity to be performed (S402).

Accordingly, the HAC 100 determines the failure of the gNB-CU 102 (S403), proceeds to logical gNB relocation to the gNB-CU 102 in the HA Cluster Group (S404), and ends the process (S405). Is done.

In addition, the Keep-Alive checks the service state of the Logical gNB received through the Keep-Alive Message when the service in the gNB-CU 102 is unavailable and recovery is required under normal circumstances (S406).

Through this process, a failure of the gNB-CU 102 is determined (S403), and the logical gNB 103 is relocated to the adjacent gNB-CU 102 (S404), and the process is terminated (S405).

5 is a diagram illustrating an algorithm for selecting the gNB-CU 102 to be restored after the gNB-CU 102 failure determination (S403) according to some embodiments.

Specifically, the gNB-CU 102 is determined to be a failure (S403) and the logical gNB 103 is relocated and restored. The gNB-CU 102 is placed in the same Data Center 101 as the gNB-CU 102 in which the failure occurred. The HAC 100 selects and restores the existing gNB-CU 102 to reduce latency between CU-DUs.

Accordingly, the HAC 100 is monitoring the cell resource status of each gNB-CU 102 disposed in the same Data Center 101 as the gNB-CU 102, and when a faulty gNB-CU 102 occurs , The gNB-CU 102 that can receive the corresponding gNB-CU 102 Cell is selected (S500) to proceed with the Logical gNB 103 Relocation (S404).

If there is no gNB-CU 102 for which cell resources are available in the same data center 101, the logical gNB 103 is relocated by selecting the gNB-CU 102 in another adjacent data center 101 (S501). Proceed (S404) to proceed.

Therefore, the HAC (100) must be monitoring the cell resources of the gNB-CU (102) of all the Data Center (101) composed of the HA Cluster, and in the cluster, the Logical gNB (103) to any gNB-CU (102). Make relocation possible.

FIG. 6 is a diagram illustrating a process of relocating the Logical gNB 103 by first selecting a recovery target in the Intra Data Center 101 according to the algorithm shown in FIG. 5.

Specifically, when a failure of the gNB-CU 102 occurs, the HAC 100 detects the failure of the gNB-CU 102 and assigns the logical gNBs 103-a in the gNB-CU 102 to the same Data Center (010). In order to accommodate the cell resources within the distributed relocation to the available adjacent gNB-CU (102).

The distributed and relocated Logical gNB (103-b) retrieves the existing data through the External Data Base System (104) and resumes the service.

7 is a case in which the gNB-CU 102 capable of accommodating cell resources in the Intra Data Center as a recovery target according to the process shown in FIG. 6 is not identified, or the entire Intra Data Center is converted to an inoperable state. At this time, it is a diagram showing a process of relocation of the logical gNB 103 by expanding the recovery target to the Inter Data Center.

Specifically, in the former case, a failure of the gNB-CU 102 occurs, and the HAC checks the gNB-CU 102 that can accommodate cell resources in the same data center as the corresponding gNB-CU 102 and then checks the gNB-CU If (102) is not confirmed, the recovery target is expanded to an adjacent Data Center (Inter Data Center) to confirm the gNB-CU 102 that can accommodate the cell. When the logical gNB is relocated to the gNB-CU 102 of the Inter Data Center, the existing data is imported through the External Data Base System 104 and the service is resumed.

In the latter case, when the Data Center falls into an inoperable state such as an earthquake or a massive power outage, HAC detects the disaster and connects the Logical gNBs 103 in the gNB-CU 102 operating in the Data Center to the Inter Data Center. Disperse and rearrange.

The distributed and relocated Logical gNBs 103 retrieve the existing data through the External Data Base System 104 and resume the service.

FIG. 8 is a diagram illustrating an algorithm to restore the gNB-CU 102 or the Data Center to the gNB-CU 102 that was operating before a failure, which is restored after a normal recovery (S800), according to some embodiments.

Specifically, if the gNB-CU 102 detects that the HAC is restored normally due to normal recovery (S800) and the original mode (AUTO/CONFIRM) is set to AUTO (S801), the gNB-CU 102 that was originally operated automatically ) To relocate the Logical gNBs 103 to the original (S803). If the original mode is set to CONFIRM (S802), if the operator performs CONFIRM, the logical gNBs 103 are relocated to the original gNB-CU 102 (S803). If the operator does not perform CONFIRM while the original mode is set to CONFIRM (S802), the service continues in the currently operating gNB-CU 102.

9 is a state in which the gNB-CU 102 failure occurs according to the process shown in FIGS. 6 and 7 and the Logical gNB 103 resumes and operates the distributed relocation service in the adjacent gNB-CU 102 or Data Center. , When the faulty gNB-CU 102 is restored to a state in which normal operation is possible, the HAC detects the normalization and distributes and rearranges the logical gNBs 103 in service operation, and the gNB-CU 102 that was originally operating The original clothes are relocated to improve operational convenience.

For the understanding of the present invention, reference numerals are given in preferred embodiments shown in the drawings, and specific terms are used to describe the embodiments of the present invention, but the present invention is not limited by specific terms, and the present invention May include all components commonly conceivable to those skilled in the art.

The present invention can be represented by functional block configurations and various processing steps. These functional blocks may be implemented with various numbers of hardware or/and software configurations that perform specific functions.

Similar to how the components of the present invention can be implemented with software programming or software elements, the present invention includes various algorithms implemented with a combination of data structures, processes, routines or other programming constructs, including C, C++ , Java, assembler, etc. may be implemented in a programming or scripting language. Functional aspects can be implemented with an algorithm running on one or more processors. In addition, the present invention may employ conventional techniques for electronic environment setting, signal processing, and/or data processing.

In the specification of the present invention (especially in the claims), the use of the term “above” and a reference term similar thereto may correspond to both the singular and the plural. In addition, when a range is described in the present invention, the invention to which an individual value falling within the range is applied (unless otherwise stated), and each individual value constituting the range is described in the detailed description of the invention. Same as Finally, unless explicitly stated or contradictory to the steps constituting the method according to the present invention, the steps may be performed in an appropriate order. The present invention is not necessarily limited according to the order of description of the steps. The use of all examples or illustrative terms (for example, etc.) in the present invention is merely for describing the present invention in detail, and the scope of the present invention is limited by the above examples or illustrative terms unless limited by the claims. It is not limited. In addition, those skilled in the art can recognize that various modifications, combinations, and changes may be configured according to design conditions and factors within the scope of the appended claims or their equivalents.

Claims (1)

In the control signal processing method in a wireless communication system,
Receiving a first control signal transmitted from a base station;
Processing the received first control signal; And
And transmitting a second control signal generated based on the processing to the base station.

Images