Method and apparatus for dynamic and efficient load balancing in mobile communication network
A communication technique that integrates a 5 th generation (5G) communication system for supporting a higher data rate after a 4 th generation (4G) system with Internet of Things (IoT) technology, and a system thereof is provided. The disclosure can be applied to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, or the like) based on 5G communication technology and IoT-related technology. The disclosure discloses a dynamic and efficient load balancing method and apparatus.
1 . A method performed by a load balancer for multi-level load balancing with a plurality of protocols of layers in a communication system, the method comprising:
receiving service requests related to a network entity;
identifying a protocol corresponding to a service request based on classifying the service requests in accordance with a protocol type;
in a case that the protocol corresponds to a first protocol among the plurality of protocols, determining a first load balancing scheme at a first level for processing traffic related to the first protocol and selecting a first engine supporting the first protocol;
in a case that the protocol corresponds to a second protocol among the plurality of protocols, determining a second load balancing scheme at a second level for processing traffic related to the second protocol and selecting a second engine supporting the second protocol;
creating a load balancing instance including the first load balancing scheme and the first engine or including the second load balancing scheme and the second engine; and
performing load balancing on data packets related to the service requests in accordance with the load balancing instance.
2 . The method of claim 1 ,
wherein the first load balancing scheme corresponds to a load balancing at a kernel level with layer 4 (L4) processing and the first protocol comprises stream control transmission protocol (SCTP), and
wherein the second load balancing scheme corresponds to a load balancing at an application level with layer 7 (L7) processing and the second protocol comprises a hypertext transfer protocol (HTTP).
3 . The method of claim 1 ,
wherein the first engine and the second engine are included in an engine group configured to perform the load balancing by the load balancer, and
wherein the engine group comprises one or more of an envoy engine, an ipvsadm engine, an ngnix engine, a smart network interface card (NIC), or a field programmable gate array (FPGA) NIC.
4 . The method of claim 1 ,
wherein the plurality of protocols comprise two or more of layer 4 (L4) protocol, layer 7 (L7) protocol, stream control transmission protocol (SCTP), hypertext transfer protocol version 2 (HTTP2.0), general packet radio service tunneling protocol control (GTP-C), and GTP user (GTP-U), google remote procedure call (gRPC), or structured query language (SQL).
5 . The method of claim 1 ,
wherein each of the first engine and the second engine is configured of an engine chain including two or more engines, and
wherein a load balancing path of the engine chain is determined according to a priority of the two or more engines.
6 . A load balancer for performing multi-level load balancing with a plurality of protocols of layers in a communication system, the load balancer comprising:
memory storing instructions; and
at least one processor,
wherein the instructions, when executed by the at least one processor, cause the load balancer to:
receive service requests related to a network entity,
identify a protocol corresponding to a service request based on classifying the service requests in accordance with a protocol type,
in a case that the protocol corresponds to a first protocol among the plurality of protocols, determine a first load balancing scheme at a first level for processing traffic related to the first protocol and selecting a first engine supporting the first protocol,
in a case that the protocol corresponds to a second protocol among the plurality of protocols, determine a second load balancing scheme at a second level for processing traffic related to the second protocol and selecting a second engine supporting the second protocol,
create a load balancing instance including the first load balancing scheme and the first engine or including the second load balancing scheme and the second engine, and
perform load balancing on data packets related to the service requests in accordance with the load balancing instance.
7 . The load balancer of claim 6 ,
wherein the first load balancing scheme corresponds to a load balancing at a kernel level with layer 4 (L4) processing and the first protocol comprises stream control transmission protocol (SCTP), and
wherein the second load balancing scheme corresponds to a load balancing at an application level with layer 7 (L7) processing and the second protocol comprises a hypertext transfer protocol (HTTP).
8 . The load balancer of claim 6 ,
wherein the first engine and the second engine are included in an engine group configured to perform the load balancing by the load balancer, and
wherein the engine group comprises one or more of an envoy engine, an ipvsadm engine, an ngnix engine, a smart network interface card (NIC), or a field programmable gate array (FPGA) NIC.
9 . The load balancer of claim 6 ,
wherein the plurality of protocols comprise two or more of layer 4 (L4) protocol, layer 7 (L7) protocol, stream control transmission protocol (SCTP), hypertext transfer protocol version 2 (HTTP2.0), general packet radio service tunneling protocol control (GTP-C), and GTP user (GTP-U), google remote procedure call (gRPC), or structured query language (SQL).
10 . The load balancer of claim 6 ,
wherein each of the first engine and the second engine is configured of an engine chain including two or more engines, and
wherein a load balancing path of the engine chain is determined according to a priority of the two or more engines.
11 . The load balancer of claim 6 , wherein the instructions, when executed by the at least one processor, cause the load balancer to:
for the performing the load balancing on the data packets related to the service requests, allocate at least one first pod in the network entity for a first service and at least one second pod in the network entity for a second service.
12 . The load balancer of claim 6 , wherein the network entity includes at least one of a session management function (SMF) or an access and mobility management function (AMF).
13 . The method of claim 1 , wherein the performing the load balancing on the data packets related to the service requests comprises allocating at least one first pod in the network entity for a first service and at least one second pod in the network entity for a second service.
14 . The method of claim 1 , wherein the network entity includes at least one of a session management function (SMF) or an access and mobility management function (AMF).
15 . The method of claim 1 ,
wherein the first load balancing scheme or the second load balancing scheme is determined based on service level agreement (SLA), and quality of service (QOS) of a packet flow of the service request, and
wherein the first load balancing scheme or the second load balancing scheme corresponds to one of a plurality of load balancing schemes.
16 . The load balancer of claim 6 ,
wherein the first load balancing scheme or the second load balancing scheme is determined based on service level agreement (SLA), and quality of service (QOS) of a packet flow of the service request, and
wherein the first load balancing scheme or the second load balancing scheme corresponds to one of a plurality of load balancing schemes.