|
|
Register | About Us | Sponsor Channel Service (Korean Market) | Advertise | Contact Us | LinkedIn | Our Korean Site
|
|||
|
HQ: 201, Hanho Building 33, Nonhyeon-ro 64-gil, Gangnam-gu, Seoul, 06228, Rep. of KOREA Netmanias USA: 5214 36th Ave. NE Seattle, WA 98105 USA Netmanias was founded in year 2002, and provides in-depth analysis and overview of 4G & 5G mobile, IoT, SDN/NFV, Gigabit Internet and video streaming technologies as well as trends in the evolution of Korean operators’ networks and services Copyright ⓒ 2002-2023 NMC Consulting Group. All rights reserved. |
||||
It is very descriptive and interesting information about GTP. I was wondering if you have any idea about GTP load balancing. In which part of the GTP we can implement if we want to implement GTP load balancing.
kind regards,
Kibrom
please I really need the answer of this question.
Kibrom asked very intellectual question,any one have answer for it ?
If GTP sender assigns dynamically for their UDP source carrying GTP-U :
=> “Sender IP + UDP source port” could be a key for load balancing.
=> I saw some EPC vendors use this scheme for their internal load balancing.
If not,
=> “Combination of sender IP + GTP-U TEID” could be a key for load balancing
=> I also know some EPC vendors use only 2152 for their source port number for GTP-U
What about NIDD? Non IP Data Delivery? In this case in IOT where the UE does not support IP stack, How for example in (3) Uplink it works in this case, how the UE will determine through which EPS bearer it should send the packet ?
What about GTP-C tunnels? Does each UE have one such tunnel throughout its connection lifetime?