Method and apparatus for load balancing in dualized network core communication network

Abstract

An embodiment relates to an operation method related to load balancing of a first dualization process network function (NF) in a dualized network core communication network and, more specifically to, a method for load balancing in a dualized network core communication network, the method comprising the steps of: setting, by the first dualization process NF, a load balancing condition of a first node connected to a first core; checking, by the first dualization process NF, a dualized network index of the first core and a second core in a database; and determining, by the first dualization process NF, whether to perform load balancing on the basis of the dualized network index and the load balancing condition.

Description

Load balancing method and device in a redundant network core communication network

[0001] The following description relates to a load balancing method and device for a redundant process NF in a redundant network core communication network.

[0002] In wireless communication systems, various Radio Access Technologies (RATs) such as LTE, LTE-A, and WiFi are used, and 5G is included in this. The three major requirement areas of 5G include (1) the Enhanced Mobile Broadband (eMBB) area, (2) the Massive Machine Type Communication (mMTC) area, and (3) the Ultra-reliable and Low Latency Communications (URLLC) area. Some use cases may require multiple areas for optimization, while others may focus on only a single Key Performance Indicator (KPI). 5G supports these various use cases in a flexible and reliable manner.

[0003] eMBB goes far beyond basic mobile internet access, covering media and entertainment applications in rich interactive tasks, the cloud, or augmented reality. Data is one of the core drivers of 5G, and dedicated voice services may not be seen for the first time in the 5G era. In 5G, voice is expected to be processed simply as an application using the data connection provided by the communication system. The main causes for the increased traffic volume are the increase in content size and the growing number of applications requiring high data transfer rates. Streaming services (audio and video), interactive video, and mobile internet connectivity will become more widely used as more devices connect to the internet. Many of these applications require always-on connectivity to push real-time information and notifications to users. Cloud storage and applications are growing rapidly on mobile communication platforms, and this can be applied to both work and entertainment. Furthermore, cloud storage is a specific use case driving the growth of uplink data transfer rates. 5G is also used for remote work in the cloud, requiring much lower end-to-end latency to maintain an excellent user experience when haptic interfaces are used. Entertainment, for example, cloud gaming and video streaming, is another key factor increasing the demand for mobile broadband capabilities. Entertainment is essential on smartphones and tablets anywhere, including in highly mobile environments such as trains, cars, and airplanes. Other use cases include augmented reality for entertainment and information retrieval. Here, augmented reality requires very low latency and instantaneous data volumes.

[0004] Furthermore, one of the most anticipated use cases for 5G concerns mMTC, the ability to seamlessly connect embedded sensors across all fields. The number of potential IoT devices is projected to reach 20.4 billion by 2020. Industrial IoT is one of the areas where 5G plays a key role in enabling smart cities, asset tracking, smart utilities, agriculture, and security infrastructure.

[0005] URLLC includes new services that will transform industries through ultra-reliable / available low-latency links, such as remote control of critical infrastructure and self-driving vehicles. Levels of reliability and latency are essential for smart grid control, industrial automation, robotics, and drone control and coordination.

[0006] Next, we will examine several usage examples in more detail.

[0007] 5G can complement FTTH (fiber-to-the-home) and cable-based broadband (or DOCSIS) as a means of providing streams rated at hundreds of megabits per second to gigabits per second. These high speeds are required for virtual and augmented reality, as well as for delivering TV at resolutions of 4K and above (6K, 8K, and higher). VR (Virtual Reality) and AR ( Augmented Reality) applications include near-immersive sports matches. Certain applications may require special network configurations. For example, in the case of VR games, game companies may need to integrate core servers with the network operator's edge network servers to minimize latency.

[0008] The automotive sector is expected to become a significant new driving force for 5G, with numerous use cases for mobile communications within vehicles. For instance, passenger entertainment requires high-capacity and high-mobility mobile broadband. This is because future users expect high-quality connectivity regardless of their location or speed. Another application in the automotive sector is the augmented reality dashboard. This displays information overlaid onto what the driver is seeing through the windshield, allowing them to identify objects in the dark and providing the driver with information about the objects' distances and movements. In the future, wireless modules will enable communication between vehicles, information exchange between vehicles and supporting infrastructure, and information exchange between vehicles and other connected devices (e.g., devices accompanying pedestrians). Safety systems will allow drivers to drive more safely by guiding them to alternative courses of action, thereby reducing the risk of accidents. The next step will be remotely controlled or self-driven vehicles. This requires highly reliable and very fast communication between different self-driven vehicles and between vehicles and infrastructure. In the future, self-driving vehicles will perform all driving activities, allowing drivers to focus solely on traffic anomalies that the vehicle itself cannot identify. The technical requirements for self-driving vehicles demand ultra-low latency and ultra-high reliability to increase traffic safety to a level unattainable by humans.

[0009] Smart cities and smart homes, referred to as a smart society, will be embedded with high-density wireless sensor networks. Distributed networks of intelligent sensors will identify conditions for maintaining the cost-effective and energy-efficient maintenance of the city or home. A similar setup can be implemented for each household. Temperature sensors, window and heating controllers, burglar alarms, and home appliances are all wirelessly connected. Many of these sensors typically feature low data transfer rates, low power consumption, and low cost. However, for example, real-time HD video may be required for certain types of devices for surveillance.

[0010] The consumption and distribution of energy, including heat or gas, are becoming highly decentralized, requiring automated control of distributed sensor networks. Smart grids interconnect these sensors using digital information and communication technologies to collect information and act accordingly. Since this information may include the behavior of suppliers and consumers, smart grids can improve efficiency, reliability, economic viability, production sustainability, and the automated distribution of fuels such as electricity. A smart grid can also be viewed as another sensor network with low latency.

[0011] The health sector possesses numerous applications that can benefit from mobile communications. Communication systems can support telemedicine, providing clinical care from remote locations. This helps reduce distance barriers and improves access to medical services that are not consistently available in remote rural areas. It is also used to save lives during critical medical care and emergencies. Mobile communication-based wireless sensor networks can provide remote monitoring and sensors for parameters such as heart rate and blood pressure.

[0012] Wireless and mobile communications are becoming increasingly important in industrial applications. Wiring is expensive to install and maintain. Therefore, the potential to replace cables with reconfigurable wireless links presents an attractive opportunity in many industries. However, achieving this requires wireless connections to operate with latency, reliability, and capacity comparable to cables, while also simplifying their management. Low latency and a very low probability of error are new requirements that 5G needs to meet.

[0013] Logistics and freight tracking are important use cases for mobile communications that use location-based information systems to enable the tracking of inventory and packages anywhere. Use cases for logistics and freight tracking typically require low data rates but necessitate wide coverage and reliable location information.

[0014] A wireless communication system is a multiple access system that supports communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). Examples of multiple access systems include CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), SC-FDMA (single carrier frequency division multiple access), and MC-FDMA (multi carrier frequency division multiple access) systems.

[0015] Sidelink (SL) refers to a communication method in which User Equipment (UE) establishes a direct link to directly exchange voice or data between terminals without passing through a Base Station (BS). SL is being considered as a solution to address the burden on base stations caused by rapidly increasing data traffic.

[0016] V2X (vehicle-to-everything) refers to a communication technology that exchanges information with other vehicles, pedestrians, and infrastructure-equipped objects through wired or wireless communication. V2X can be classified into four types: V2V (vehicle-to-vehicle), V2I (vehicle-to-infrastructure), V2N (vehicle-to-network), and V2P (vehicle-to-pedestrian). V2X communication can be provided through PC5 interfaces and / or Uu interfaces.

[0017] Meanwhile, as more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing Radio Access Technology (RAT) is emerging. Accordingly, communication systems considering services or terminals sensitive to reliability and latency are being discussed; next-generation radio access technology that incorporates improved mobile broadband communication, Massive Machine Type Communication (MTC), and Ultra-Reliable and Low Latency Communication (URLC) can be referred to as new radio access technology (new RAT) or new radio (NR). Vehicle-to-everything (V2X) communication can also be supported in NR.

[0018] The present disclosure has as its technical problem a load balancing method and apparatus for a redundant process NF in a redundant network core communication network.

[0019] One embodiment is a load balancing method in a redundant network core communication network, wherein the method comprises a step in which the first redundant process NF (Network Function) in the redundant network core communication network sets a load balancing condition of a first node connected to a first core; a step in which the first redundant process NF checks a redundant network indicator of the first core and a second core in a database; and a step in which the first redundant process determines whether to perform load balancing based on the redundant network indicator and the load balancing condition.

[0020] One embodiment is a first redundancy process Network Function (NF) that performs load balancing-related operations in a redundancy network core communication network, comprising: at least one processor; and at least one computer memory that can be operably connected to the at least one processor and stores instructions that cause the at least one processor to perform operations when executed, wherein the operations include: the first redundancy process NF setting a load balancing condition of a first node connected to a first core; the first redundancy process NF checking a redundancy network indicator of the first core and a second core in a database; and the first redundancy process determining whether to perform load balancing based on the redundancy network indicator and the load balancing condition.

[0021] The above redundancy network metrics may include the number of Registered UEs, the total CPS (Connections Per Second) of incoming messages, the total UE throughput (GBR (Guaranteed Bit Rate) + non-GBR), the GBR throughput of all UEs, the number of PDU sessions of all UEs, and the number of QoS flows of all UEs.

[0022] The above first redundancy process NF can determine to perform the load balancing based on the fact that at least one indicator in a subset of the redundancy network indicators satisfies the load balancing condition.

[0023] A subset of the above redundancy network metrics may include total UE throughput (GBR + non-GBR) and the number of QoS flows of total UEs.

[0024] A subset of the above redundancy network metrics may include the number of Registered UEs, the number of PDU sessions of all UEs, and the number of QoS Flows of all UEs.

[0025] The setting of the above load balancing conditions may be one or more of the following.

[0026] 1) Number of Registered UEs > Maximum Number of Supported UEs - Buffer

[0027] 2) Total CPS of incoming messages > CORE supported maximum CPS - buffer

[0028] 3) Total UE throughput (GBR + non-GBR) > Cell throughput (GBR + non-GBR) - Buffer

[0029] 4) Total UE GBR throughput > Cell GBR throughput - Buffer

[0030] 5) Total number of UE PDU sessions > Maximum number of UE PDU sessions - Buffer

[0031] 6) Total number of QoS Flows for all UEs > Maximum UE QoS Flow

[0032] The first redundancy process NF, which has decided to perform the above load balancing, can check whether all cores including the second core satisfy the load balancing condition.

[0033] Based on the fact that all of the above cores satisfy the load balancing condition, the maximum threshold for traffic acceptance of all cores can be determined.

[0034] Based on the fact that the maximum threshold for traffic acceptance of all the above cores has been exceeded, the first redundancy process NF can send a Notify message to the AMF (Access and Mobility Management Function) instructing the RAN (Radio Access Network) not to route traffic.

[0035] The first core and the second core mentioned above may both be active.

[0036] The above redundancy network indicators may be recorded in the database in real-time or periodically.

[0037] The number of PDU sessions and QoS flows of all UEs mentioned above may be aggregated by UPF or 5QI and recorded in the database.

[0038] The above total UE throughput is recorded by accumulating it to the previous database record value, and the record may be based on a Time stamp, UPF identifier, uplink or downlink related Direction, and a format of GBR / Non-GBR Bytes.

[0039] According to one embodiment, network system efficiency can be increased through improved load balancing. Real-time monitoring of traffic and system anomalies for each node is possible through an external redundancy process, and network efficiency and accident prevention can be achieved by performing distributed network processing and control in advance when anomalies occur. Furthermore, not only simple traffic control but also dynamic network distribution and control can be executed proactively by utilizing various network indicators.

[0040] The drawings attached to this specification are intended to provide an understanding of the embodiment(s), to illustrate various embodiments, and to explain the principles together with the description in the specification.

[0041] Figure 1 shows a Non-Roaming 5G System Architecture.

[0042] Figure 2 shows the overall 5G NR architecture.

[0043] Figure 3 illustrates a redundant server network configuration.

[0044] Figure 4 illustrates an example of a basic active-active redundancy network related to an embodiment of the present invention.

[0045] Figure 5 is a diagram illustrating the problem of overload device registration in an active-active redundancy network.

[0046] FIGS. 6 and 7 are drawings for explaining load balancing according to an embodiment of the present invention.

[0047] FIG. 8 illustrates a redundant SW load balancing scenario according to one embodiment of the present invention.

[0048] FIG. 9 illustrates a redundant SW load balancing scenario according to one embodiment of the present invention.

[0049] FIG. 10 illustrates a redundant load balancing detailed signaling flow and an information acquisition flow for process threshold check according to one embodiment of the present invention.

[0050] FIG. 11 illustrates a detailed signaling flow for redundant load balancing according to one embodiment of the present invention.

[0051] In various embodiments of the present disclosure, “” and “” should be interpreted as indicating “and / or”. For example, “A / B” may mean “A and / or B”. Furthermore, “B” may mean “A and / or B”. Furthermore, “” may mean “at least one of A, B and / or C”. Furthermore, “B, C” may mean “at least one of A, B and / or C”.

[0052] In various embodiments of the present disclosure, “or” should be interpreted as indicating “and / or.” For example, “A or B” may include “only A,” “only B,” and / or “both A and B.” In other words, “or” should be interpreted as indicating “additionally or alternatively.”

[0053] The following technologies can be used in various wireless communication systems such as CDMA (code division multiple access), FDMA (frequency division multiple access), TDMA (time division multiple access), OFDMA (orthogonal frequency division multiple access), and SC-FDMA (single carrier frequency division multiple access). CDMA can be implemented using wireless technologies such as UTRA (universal terrestrial radio access) or CDMA2000. TDMA can be implemented using wireless technologies such as GSM (global system for mobile communications), GPRS (general packet radio service), and EDGE (enhanced data rates for GSM evolution). OFDMA can be implemented using wireless technologies such as IEEE (institute of electrical and electronics engineers) 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved UTRA). IEEE 802.16m is an evolution of IEEE 802.16e and provides backward compatibility with systems based on IEEE 802.16e. UTRA is part of UMTS (universal mobile telecommunications system). 3GPP (3rd generation partnership project) LTE (long term evolution) is part of E-UMTS (evolved UMTS) which uses E-UTRA (evolved-UMTS terrestrial radio access), employing OFDMA in the downlink and SC-FDMA in the uplink.LTE-A (advanced) is an evolution of 3GPP LTE.

[0054] 5G NR is a successor technology to LTE-A and is a new clean-slate type mobile communication system with characteristics such as high performance, low latency, and high availability. 5G NR can utilize all available spectrum resources, ranging from low frequency bands below 1 GHz to mid-frequency bands from 1 GHz to 10 GHz, and high frequency (millimeter wave) bands above 24 GHz.

[0055] For clarity of explanation, the description focuses on LTE-A or 5G NR, but the technical concept according to one embodiment of the present disclosure is not limited thereto.

[0056] Figure 1 illustrates the Non-Roaming 5G System Architecture disclosed in 3GPP TS 23.501. As illustrated, the 5G Core Network contains various Network Functions (NFs), such as Access and Mobility Management Function (AMF), User Plane Function (UPF), and Session Management Function (SMF). Network functions can be implemented as network elements on dedicated hardware, software instances running on dedicated hardware, or virtualized functions instantiated on a suitable platform. For example, they can run on cloud infrastructure.

[0057] Table 1 below discloses the NF of the 5G Core Network and the functions of the corresponding NF.

[0058] NF function AMF (Access and Mobility Management Function) Access and Mobility Management Function Termination of RAN CP interface (N2) Termination of NAS (N1), NAS encryption and integrity protection. Registration management. Connection management. Accessibility management. Mobility management. Legitimate blocking (for interfaces to AMF events and LI systems). Provides SM message transmission between UE and SMF. Transparent proxy for SM message routing. Access authentication and access authorization. Provides SMS message transmission between UE and SMSF. SEAF (Security Anchor Function). Interacting with the AUSF and UE, and receiving the intermediate key generated as a result of the UE authentication process; in the case of USIM-based authentication, the AMF retrieves security data from the AUSF. Functions for non-3GPP access networks: UPF (User Plane Function) - Anchor points for Intra- / Inter-RAT mobility (if applicable); External PDU session points for interconnections to data networks; Packet routing and forwarding; Packet inspection; User plane portion of policy rule enforcement (e.g., gating, redirection, traffic coordination); Legitimate blocking (UP collection); Traffic usage reporting; QoS handling for the user plane (e.g., UL / DL rate enforcement, Reflected QoS indication in DL); Uplink traffic validation (QoS flow mapping in SDF); Transport-level packet marking for uplink and downlink; Downlink packet buffering and triggering downlink data notifications; Sending and forwarding one or more "termination markers" to the source NG-RAN node. SMF (Session Management Function) - Session management function; UE IP address allocation and management; Selection and control of UP functions; Configuring traffic coordination in the UPF Route traffic to appropriate targets, enforce routing policies, and control parts of QoS. Notify downlink data.PCF (Policy Control Function): Supports an integrated policy framework for managing network behavior; provides policy rules to control plane functions for enforcement; accesses subscription information related to policy decisions in the UDR (Unified Data Repository). UDM (Unified Data Management): 3GPP AKA authentication credential generation; user identification processing; granting access rights based on subscription data (e.g., roaming restrictions); managing UE serving NF registration; supporting service / session continuity (e.g., maintaining SMF / DNN assignments for ongoing sessions); supporting MT-SMS delivery; legitimate blocking functions; subscription management; SMS management. AUSF (Authentication Server Function): Supports the AUSF (Authentication Server Function) specified by SA WG3. AF (Application Function): Application influence on traffic routing; interacts with the policy framework for controlling access policies to network exposure functions.

[0059] In addition, there are various reference points such as N2, N3, and N4 in network architecture, which refer to interfaces between different functions or nodes.

[0060]

[0061] Figure 2 illustrates the overall 5G NR architecture. A gNB node is a node that provides NR User Plane and Control Plane protocol terminations to the terminal (User equipment, UE) and is connected to the 5G core network (5GC) via an NG interface. An ng-eNB node is a node that provides Control Plane protocol terminations to the terminal and is connected to the 5GC via an NG interface. As shown, the terminal is connected to the air base station (gNB, or ng-eNB, is connected to the base station via an air interface).

[0062]

[0063] Figure 3 illustrates a basic redundant server network configuration. The basic redundant server network configuration is a structure in which the same Core Network (Core NW) redundancy is applied to Ran(gNB) #1 and two servers (#1, #2). At the Core SW layer, a network switch algorithm is operated based on the 3GPP NG-FLEX specification, and key NG-FLEX specifications can be referenced in 23.501 6.3.5, 23.501 5.19.3, 23.501 5.19.5, 23.501 5.21.2, 38.410, and 38.413.

[0064] The RAN and Core are connected via the NG-AP protocol and perform Control Plane communication through the NG-SETUP process. After the terminal boots up and connects to the RAN, the RAN simultaneously establishes NG-SETUP-based Control Plane connections with Core #1 and Core #2. At this time, the terminal connects to Core #1 immediately after booting, and an actual session is established between the terminal and Core #1 via the RAN. On the other hand, since the connection with Core #2 is established via the NG-AP protocol only up to the point of session connection, an actual traffic session has not yet been allocated.

[0065]

[0066] FIG. 4 illustrates an example of a basic Active-Active redundancy network related to an embodiment of the present invention. In FIG. 4, each device is connected to a RAN, and the RAN is connected to each CORE in a 1:1 manner. Each core is physically separated and has a separate band, and the redundancy network configuration may have two separate bands overlapping. Each device is connected to RAN#1 or RAN#2 according to a frequency acquisition algorithm.

[0067] If a network singularity is detected on the Core #1 side node, a signal can be generated and transmitted to the VRAN / device to perform a failover operation to distribute traffic to adjacent Cores. Devices receiving the redundancy control signal can no longer connect to the corresponding network and are prompted to transition to another network or register with the network.

[0068] Continuing, Fig. 5 is a diagram illustrating the problem of overloaded device registration in an Active-Active redundancy network. Referring to Fig. 5, since network registration is done randomly, each terminal / device cannot be registered at a certain ratio for each node. In other words, even if the number of devices increases, network registration does not occur in each RAN at a certain ratio. Therefore, as exemplified in Fig. 5, cases may occur where many devices are connected to Core #1, and in such cases, system overload and reduced efficiency occur in the network.

[0069] Therefore, various embodiments of the present invention related to load balancing in a redundant network core communication network are disclosed below to solve these problems. In the following description, the 'load balancing condition' may be a concept including a threshold. As described below, the load balancing condition may be a condition of any one network metric, but may mean a threshold of at least two network metrics. In addition, in the following description, the redundant process NF may be an NF independent of the existing NF, or it may be included in the existing NF.

[0070]

[0071] A method for load balancing operation of a first redundancy process (redundancy process #1) NF in a redundancy network core communication network according to an embodiment of the present invention may include the step of the first redundancy process NF setting a load balancing condition of a first node connected to a first core; the step of the first redundancy process NF checking a redundancy network indicator of the first core and a second core in a database; and the step of the first redundancy process determining whether to perform load balancing based on the redundancy network indicator and the load balancing condition. Both the first core and the second core are active.

[0072] The above redundancy network metrics may include the number of Registered UEs, the total CPS (Connections Per Second) of incoming messages, the total UE throughput (GBR (Guaranteed Bit Rate) + non-GBR), the GBR throughput of all UEs, the number of PDU sessions of all UEs, and the number of QoS flows of all UEs.

[0073] The setting of the above load balancing conditions may be one or more of the following.

[0074] 1) Number of Registered UEs > Maximum Number of Supported UEs - Buffer

[0075] 2) Total CPS of incoming messages > CORE supported maximum CPS - buffer

[0076] 3) Total UE throughput (GBR + non-GBR) > Cell throughput (GBR + non-GBR) - Buffer

[0077] 4) Total UE GBR throughput > Cell GBR throughput - Buffer

[0078] 5) Total number of UE PDU sessions > Maximum number of UE PDU sessions - Buffer

[0079] 6) Total number of QoS Flows for all UEs > Maximum number of QoS Flows for all UEs - Buffer

[0080]

[0081] In such a case, the first redundancy process NF may determine to perform the load balancing based on the fact that at least one indicator in a subset of the redundancy network indicators satisfies the load balancing condition.

[0082] For example, referring to FIG. 6, the first redundancy process NF can perform load balancing based on at least one indicator in a subset of the redundancy network indicators [total UE throughput (GBR (Guaranteed Bit Rate) + non-GBR), number of QoS Flows of the total UE] satisfying the corresponding load balancing conditions 3) and 6). That is, the subset of the redundancy network indicators includes the total UE throughput (GBR + non-GBR) and the number of QoS Flows of the total UE.

[0083] Specifically, the load balancing condition (threshold condition) is set to 3) maximum processing capacity of the cell (GBR + non-GBR throughput): 90%, and 6) maximum number of QoS Flows of the cell: 90, and it is determined whether at least one of the total UE throughput (GBR (Guaranteed Bit Rate) + non-GBR) or the total number of QoS Flows of the UE satisfies the condition.

[0084] The confirmed CORE#1 status is that the total throughput (GBR+non-GBR throughput) of Active (Traffic) UEs has reached 80% (Device #1, Device #2, Device #3), and the total number of QoS flows of Active (Traffic) UEs is 90. Additionally, the CORE#2 status is that the maximum cell throughput (GBR + non-GBR throughput) is 30%, and the total number of QoS flows of Active (Traffic) UEs is 40.

[0085] In this case, since CORE#1 has reached the cell maximum output (90%), condition 3) does not satisfy the threshold condition, but condition 6) has reached the threshold condition and satisfies the failover execution condition, so it is decided to perform load balancing.

[0086] In other words, load balancing is determined by considering the maximum processing capacity of the CORE#1 cell and the total number of QoS flows of the Active UEs. This takes into account that network load may occur when each device operates multiple network resources (QoS). Regarding load balancing, UEs attempting to register with CORE#1 are guided to register with CORE#2, and among the UEs currently being served on CORE#1, a redirect is attempted to CORE#2 considering their QoS priority.

[0087]

[0088] Figure 7 assumes that, regarding load balancing conditions 1) Number of Registered UEs > Number of Max Supported UEs - Buffer, 5) Number of PDU sessions of all UEs > Number of PDU sessions of max UEs - Buffer, and 6) Number of QoS Flows of all UEs > Number of QoS Flows of max UEs, threshold conditions are set as follows: Condition 1) Number of Max Supported UEs: 90, Condition 5) Total number of PDU sessions of UEs in the cell: 350, Condition 6) Total number of QoS Flows within PDUs of the cell: 1600. That is, a subset of the redundancy network indicators includes the number of Registered UEs, the number of PDU sessions of all UEs, and the number of QoS Flows of all UEs.

[0089] CORE#1 has a total number of actual connected UEs of 70, a total number of PDU sessions of total UEs of 350, and a total number of QoS Flows of 1440, and the status of CORE#2 is a maximum number of supported UEs of the cell of 40, a total number of PDU sessions of UEs of the cell of 160, and a total number of QoS Flows within the cell's PDUs of 640.

[0090] Here, although the maximum support conditions 1) and 6) of the CORE#1 cell have not reached the threshold, the number of PDU sessions in condition 5) has reached the threshold, so CORE#1 may become network-loaded. Therefore, in this case, a safe attempt to FAILOVER to CORE#2 is made.

[0091] In addition to the above examples, load balancing may be performed when at least one of load balancing conditions 1) and 3) is satisfied, or when at least one of 4), 5), and 6) is satisfied.

[0092]

[0093] FIG. 8 illustrates a redundant SW load balancing scenario according to an embodiment of the present invention in relation to the method described above.

[0094] Referring to FIG. 8, in S801, network metrics or data configured by default for each Core node are collected and stored in a DB. In S802, each redundancy process sets traffic conditions and thresholds for each node. Network metric information of all Cores is checked in real-time or periodically through the DB. In S803, the redundancy process within each node monitors the real-time traffic status of the node. In S804, if the traffic metric in the redundancy process within Node #1 approaches the threshold or various network anomalies are detected, a control signal is immediately transmitted to the corresponding CORE. This step may correspond to the examples of FIG. 6 and FIG. 7 described above.

[0095] Continuing, at S805, if necessary, the redundancy process can send a Notify message to the redundancy process of another node to inform it of its current status, and the redundancy process that receives the Notify can adjust its capacity. At S806, the corresponding CORE that received the control signal generates a signal to reduce the network load and transmits it to the VRAN / device. At S807, the device that received the redundancy control signal is no longer connected to the network and is prompted to transition to another network or register with the network.

[0096]

[0097] The first redundancy process NF, which has decided to perform the above load balancing, can check whether all cores including the second core satisfy the load balancing condition. This is an algorithm for exchanging each Core state and network information by communication between each redundancy process #1 / #2, which checks all Core Threshold states.

[0098] Based on the fact that the maximum threshold for traffic acceptance of all the above cores has been exceeded, the first redundancy process NF can send a Notify message to the AMF (Access and Mobility Management Function) instructing the RAN (Radio Access Network) not to route traffic.

[0099] Alternatively, based on the existence of certain cores that fall below the maximum threshold for traffic acceptance, the load balancing conditions of said certain cores may be temporarily modified. When the threshold is exceeded, the Capacity setting of the RAN may be changed via AMF Notify for RAN control. Traffic control through dynamic Threshold adjustment may temporarily increase traffic by 10% and restore the existing Threshold after a certain period of time.

[0100] In relation to this, FIG. 9 illustrates a redundant SW load balancing scenario according to one embodiment of the present invention.

[0101] Referring to Fig. 9, in S901, the first redundancy process NF checks the current Core service status. If the service is normal, it proceeds to the next step, and if the service is not available, it terminates the process.

[0102] In S902, key features (network metrics) for Core load balancing are collected.

[0103] In S903, it checks whether the major features (network metrics) within the current Core have exceeded the Major Threshold, and if they have, executes the logic for load balancing. Here, the major features (network metrics) include Registered UEs, CPS, UL / DL Throughput, and GBR Session Count, and the previously described items may also fall under this category. Furthermore, load balancing can be determined based on multiple combinations of features rather than a single condition. For example, if the number of Registered UEs exceeds the Threshold and the current UL / DL Throughput statistics indicate that additional traffic can be accommodated, traffic is accepted; conversely, if the GBR Session Count exceeds the Threshold, new sessions can be not allocated through capacity adjustment, even if there is still capacity available for Registered UEs.

[0104] In S904, check if the traffic capacity of all currently serving cores exceeds the threshold. If it does, logic for checking the threshold of all cores may be triggered. If the traffic capacity of all currently serving cores does not exceed the threshold, the AMF Notify logic may be called.

[0105] In S905, if the threshold of all serviced cores is exceeded and there are no replacement cores, the threshold status of all cores is checked to see if the threshold can be temporarily raised. If the core is in a maximum processing state where the threshold can no longer be raised, the capacity is set to 0 to prevent the RAN from routing traffic, and a Notify logic is called to the AMF to protect the corresponding core system. If the threshold can be temporarily raised, logic to accommodate it can be triggered on that core.

[0106] In S906, if a Core can temporarily raise the Threshold, the Threshold currently set on the Core can be temporarily raised by 10% to accommodate traffic, and then restored to the original Threshold after a certain period of time.

[0107] In S907, you can request a change in the Capacity setting of the RAN via AMF Notify to increase or decrease the proportion of traffic flowing into the corresponding Core. After load balancing, if the Core becomes capable of accommodating traffic after a certain period, the Capacity can be restored to its original state to resume service processing.

[0108]

[0109] In relation to the above description, the Core node state management and load balancing algorithm can apply load balancing differently depending on the state of the Core node when executing load balancing logic in the Core. Normally, the Core's Threshold is set to approximately 70% of the maximum processing capacity, and if an abnormal state persists, the processing capacity can be flexibly expanded or contracted within 10% to 30% of the Threshold.

[0110] By checking the status of the Cores through the redundancy process and verifying whether the traffic capacity of all Cores in service exceeds the Threshold, the status of Core #2 can be checked to see if load balancing logic operation is required on Core #1. If Core #2 can handle it, logic to load balance to Core #2 is called, and if Core #2 cannot handle new traffic, additional status check logic such as item 3 can be called.

[0111] If both Core #1 and #2 in service exceed their thresholds and there are no Cores available for load balancing, check if the threshold of Core #1 can be temporarily raised. If it is possible to temporarily raise the threshold, increase Core #1's threshold by a certain percentage (e.g., 10%) and proceed with message processing. If the other system (Core #2) also has a threshold of 100% and Core #1's threshold is 100%, do not process the message and discard it to protect the Core system, and trigger a Notify logic in the AMF to prevent the RAN from routing traffic.

[0112] If traffic below the threshold flows in for a preset period of time—that is, if load balancing is not operating—the threshold of the Core that had its threshold temporarily raised can be restored to its default value.

[0113]

[0114] In relation to the above description, the redundancy DB information generation / aggregation algorithm may follow the following procedure.

[0115] First, redundancy network metrics are generated and aggregated, where the redundancy network metrics may include the number of Registered UEs, CPS, number of UE sessions, number of QoS Flows, GBR Bytes, Threshold, average packet throughput, etc. Alternatively, as previously explained, the redundancy network metrics may include the number of Registered UEs, the total CPS (Connections Per Second) of incoming messages, the total UE throughput (GBR (Guaranteed Bit Rate) + non-GBR), the total UE GBR throughput, the total number of PDU sessions of UEs, and the total number of QoS Flows of UEs, and may consist of all or part of the examples above.

[0116] The number of Registered UEs and the CPS of incoming NGAP / NAS messages are aggregated and recorded in the DB. Redundancy network metrics may be recorded in the above database in real-time or periodically.

[0117] The number of connected PDU Sessions / QoS flows is aggregated by UPF and 5QI and recorded in the DB. That is, the number of PDU Sessions and QoS flows of all UEs are aggregated by UPF or 5QI and recorded in the database.

[0118] The total UE throughput mentioned above is accumulated and recorded in the previous database record value, and said record may be based on a time stamp, UPF identifier, uplink or downlink related direction, and a format of GBR / Non-GBR Bytes. That is, the volume of generated packets is accumulated in the previous DB record value and can be recorded in the DB in the following format.

[0119] - Time stamp

[0120] - UPF identifier (UPF#1 or UPF#2)

[0121] - Direction (uplink or downlink)

[0122] - GBR / Non-GBR Bytes (Values ​​increasing monotonically from 0 since UPF operation)

[0123] Subsequently, information for threshold checks can be obtained. The following information is periodically queried from the DB. Querying the DB can be performed using a Rest API format.

[0124] - Number of Registered UEs for each AMF, NGAP / NAS CPS.

[0125] - Number of QoS flows per PDU Session / 5QI for each UPF.

[0126] - Average packet throughput of each UPF: Calculate the average value by dividing the difference between the first and last byte values ​​of the time range to be queried by the time range.

[0127] Regarding the redundancy DB information generation / aggregation algorithm mentioned above, Figure 10 illustrates a detailed redundancy load balancing signaling flow and an information acquisition flow for checking process thresholds.

[0128] Referring to Figure 10, in S1001a to 1001b, each AMF (AMF #1, AMF #2) aggregates the number of Registered UEs and the CPS of incoming NGAP / NAS messages and records them in the DB.

[0129] In S1002a~1002b, each UPF (UPF #1, UPF #2) aggregates the number of connected PDU Session / QoS flows by UPF and 5QI and records them in the DB.

[0130] In S1003a~1003b, each UPF (UPF #1, UPF #2) accumulates the volume of the generated packet in the previous DB record value and records it in the DB in the format described above.

[0131] In S1004a, S1005a, 1004b, and 1005b, each redundancy process (Redundancy Process #1, Redundancy Process #2) obtains information for threshold checks. As previously described, it periodically queries the DB for the number of Registered UEs for each AMF, NGAP / NAS CPS, the number of QoS flows per PDU Session / 5QI for each UPF, and the average packet throughput for each UPF. The query to the DB is performed using a Rest API format.

[0132] In S1006a~1006b, the node status between redundancy processes can be notified as needed.

[0133]

[0134] Figure 11 illustrates a detailed signaling flow for redundant load balancing.

[0135] Referring to Fig. 11, UE#1 attempts to register with core#1. Ran#1 performs network registration with AMF / UPF#1 (S1101).

[0136] In S1102, network capability calculation and load balance control are performed between the redundancy process NF (Process #1) and DB, and the details are replaced by the description above.

[0137] Meanwhile, UE#2 may attempt network registration with core#2, and Ran#2 may perform network registration with AMF / UPF#2 (S1103). In this case, redundancy process #2 performs network capability calculation and load balance control.

[0138] The redundancy process NF (Process #1) sends a Load threshold exceeding notification to AMF #1 (S1104), and AMF #1 sends a network registration control signal to Ran #1. That is, since a threshold exceeding notification has occurred in core #1, Ran network registration control is performed, and the details are replaced by the above description.

[0139] Afterwards, when registering a new network, RAN / Core#2 is induced, and Ran#2 performs new UE Registration on core#2 (S1107).

[0140] The embodiments described above can be applied to a redundant network structure using a private 5G network (e.g., private 5G) in factories / hospitals, etc.

Claims

1. A method for load balancing operations of a first redundancy process NF (Network Function) in a redundancy network core communication network, The step of the first redundancy process NF setting a load balancing condition of a first node connected to a first core; The step of the first redundancy process NF checking the redundancy network indicators of the first core and the second core in the database; A step of determining whether to perform load balancing based on the first redundancy process, the redundancy network indicator, and the load balancing condition; A load balancing method in a redundant network core communication network including 2. In Paragraph 1, A load balancing method in a redundant network core communication network, wherein the above redundant network metrics include the number of Registered UEs, the total CPS (Connections Per Second) of incoming messages, the total UE throughput (GBR (Guaranteed Bit Rate) + non-GBR), the GBR throughput of all UEs, the number of PDU sessions of all UEs, and the number of QoS Flows of all UEs.

3. In Paragraph 2, A load balancing method in a redundant network core communication network, wherein the first redundancy process NF determines to perform the load balancing based on the fact that at least one indicator in a subset of the redundancy network indicators satisfies the load balancing condition.

4. In Paragraph 2, A load balancing method in a redundant network core communication network, wherein a subset of the above redundant network metrics includes total UE throughput (GBR + non-GBR) and the number of QoS flows of total UEs.

5. In Paragraph 2, A load balancing method in a redundant network core communication network, wherein a subset of the above redundant network indicators includes the number of Registered UEs, the number of PDU sessions of all UEs, and the number of QoS Flows of all UEs.

6. In Paragraph 2, A load balancing method in a redundant network core communication network, wherein the setting of the above load balancing conditions is one or more of the following. 1) Number of Registered UEs > Maximum Number of Supported UEs - Buffer 2) Total CPS of incoming messages > CORE supported maximum CPS - buffer 3) Total UE throughput (GBR + non-GBR) > Cell throughput (GBR + non-GBR) - Buffer 4) Total UE GBR throughput > Cell GBR throughput - Buffer 5) Total number of UE PDU sessions > Maximum number of UE PDU sessions - Buffer 6) Total number of QoS Flows for all UEs > Maximum UE QoS Flow 7. In Paragraph 2, A load balancing method in a redundant network core communication network, wherein the first redundancy process NF determined to perform the load balancing checks whether all cores including the second core satisfy the load balancing condition.

8. In Paragraph 7, A load balancing method in a redundant network core communication network that determines the maximum traffic acceptance threshold of all cores based on the fact that all cores satisfy load balancing conditions.

9. In Paragraph 8, A load balancing method in a redundant network core communication network, wherein, based on the fact that the maximum threshold for traffic acceptance of all cores is exceeded, the first redundant process NF sends a Notify message to the AMF (Access and Mobility Management Function) instructing the RAN (Radio Access Network) not to route traffic.

10. In Paragraph 1, A load balancing method in a redundant network core communication network in which both the first core and the second core are active.

11. In Paragraph 2, A load balancing method in a redundant network core communication network, wherein the above-mentioned redundant network indicators are recorded in the database in real-time or periodically.

12. In Paragraph 11, A load balancing method in a redundant network core communication network, wherein the number of PDU sessions of all UEs and QoS flows of all UEs are aggregated by UPF or 5QI and recorded in the database.

13. In Paragraph 11, A load balancing method in a redundant network core communication network, wherein the total UE throughput is accumulated and recorded in the previous database record value, and the record is based on a Time stamp, UPF identifier, uplink or downlink related Direction, and GBR / Non-GBR Bytes format.

14. In a first redundancy process NF (Network Function) that performs load balancing-related operations in a redundancy network core communication network, At least one processor; and It includes at least one computer memory that can be operably connected to the at least one processor and stores instructions that cause the at least one processor to perform operations when executed, and The above operations are, The step of the first redundancy process NF setting a load balancing condition of a first node connected to a first core; The step of the first redundancy process NF checking the redundancy network indicators of the first core and the second core in the database; A step of determining whether to perform load balancing based on the first redundancy process, the redundancy network indicator, and the load balancing condition; A first redundancy process NF including

Images