VPNv4 route control for LTE X2 SON using import route maps and outbound route filtering

Abstract

In an embodiment, a network device automatically creates a more optimal route entry for inter-base station traffic to be transmitted between a local base station and a remote base station. The network device automatically discovers a remote IP address of the remote base station used for inter-base station traffic based upon traffic transmitted by the local base station destined to the network device or traffic transmitted between the local and remote base stations. In response, the network device inserts an entry into a route import map representing the remote IP address, and based upon determining that a route from a route update message matches this entry, installs the more optimal route entry into the routing table. This route provides a shorter path to the remote base station through the backhaul network compared to a less optimal route through a mobile core network previously used for the inter-base station traffic.

Description

technical field [0001] Embodiments of the present invention relate to the field of networking, and more specifically, network topology discovery and automatic creation of network routes between base stations for inter-base station traffic. Background technique [0002] The 3rd Generation Partnership Project (3GPP) defines standards and technical specifications called Long Term Evolution (LTE) for 3G mobile systems. In contrast to the circuit-switched configuration employed by previous cellular communication networks, LTE was designed to support packet-switched services, providing seamless Internet Protocol (IP) between a user equipment (UE) device and one or more packet data networks (PDNs). ) connectivity without interference during end-user geographic movement. [0003] While the term "LTE" includes the evolution of Universal Mobile Telecommunications System (UMTS) Radio Access to Evolved UTRAN (E-UTRAN), there are also non-radio aspects under the term "System Architectur...

AI Technical Summary

Problems solved by technology

However, a given eNodeB may typically have around 20-30 neighboring eNodeBs at a time, each of these neighboring eNodeBs will require a route configured for each of its neighbors, requiring a huge and error-prone configuration and also costly A large amount of routing state to maintain in the network

Furthermore, since the number of eNodeBs in the network tends to fluctuate with network expansion, reconfiguration and maintenance, there is thus a huge administrative overhead for maintaining such static routes

Images