HackMD
Transport Learning Docs
- Table of Content
Networking Basics
Virtual Local Area Networks (VLANs)
- The image was uploaded to a note which you don't have access to
- The note which the image was originally uploaded to has been deleted
VLANs Functions
- Break up physical switches into virtual “mini switches“
- Extend the virtual “mini switch” to multiple physical switches
VLANs allow your logical topology to be unconstrained by your physical topology.
Port Types
- Access Ports / Untagged Ports: Ports which carry traffic for only one VLAN.
- Trunk Ports / Tagged Ports: Ports which carry traffic for multiple VLANs.
- All frames traversing a Trunk port must be “tagged” so the receiving switch knows what VLAN to associate that traffic to.
Address Resolution Protocols (ARP)
ARPs Functions
- Break up physical switches into virtual “mini switches“
- Extend the virtual “mini switch” to multiple physical switches
VLANs allow your logical topology to be unconstrained by your physical topology.
Access Control List (ACL)
ACL Functions
- Break up physical switches into virtual “mini switches“
- Extend the virtual “mini switch” to multiple physical switches
VLANs allow your logical topology to be unconstrained by your physical topology.
Network Address Translation (NAT)
ACL Functions
- Break up physical switches into virtual “mini switches“
- Extend the virtual “mini switch” to multiple physical switches
VLANs allow your logical topology to be unconstrained by your physical topology.
Virtual Private Networking (VPN) & Tunneling
ACL Functions
- Break up physical switches into virtual “mini switches“
- Extend the virtual “mini switch” to multiple physical switches
VLANs allow your logical topology to be unconstrained by your physical topology.
High Level Tx & IP Architecture
Transport and IP Network Architecture
General overview of transport and IP network architecture and main transport technologies to be implemented in the network. In addition, the particularities of the IP network are examined.
Transport Network Overview
In a mobile environment, the transport network interconnects disparate networks, including the RAN, data centers, and external networks. Figure 3 displays the architecture of a typical transport network.
- The image was uploaded to a note which you don't have access to
- The note which the image was originally uploaded to has been deleted
Mobile networks are ubiquitous and support a mix of traffic types originating from and terminating to mobile devices. All this traffic must be conveyed between the mobile cellular base stations through the transport network up to the mobile core.
For this reason, different segments exist on the transport network that for most of NaaS operators can be classified as: last-mile and aggregation level. Additionally, there might exist a connection provided by a third-party network, which can provide the last mile or aggregation. The network segments are mostly defined by the technology and topology used within it. The key network segment characteristics are:
-
The last-mile and aggregation segments provide the connectivity to the eNodeB at the cell sites and are predominantly based on three chain topologies built with microwave radios and fiber optic links.
-
Optionally, a third-party network can be used to transport traffic to the mobile core. A typical method to implement this scenario is presented when the NaaS operator doesnt have network infrastructure in the geographical zone. In nearly all cases, the third-party network is an IP/MPLS network.
Figure 4 displays the structure of the transport network.
- The image was uploaded to a note which you don't have access to
- The note which the image was originally uploaded to has been deleted
The structure displayed in Figure 4 considers different physical technologies and topologies. Moving left to right, the last-mile connects a demarcation device, usually deployed at the cell site, to a first stage of traffic grooming and concentration. The aggregation network, in turn, further aggregates traffic, adapts any technology change and provides the hand-over point to a higher level of aggregation network.
The term physical connectivity is used to represent any technology that can be used to connect nodes. Common physical connectivity includes fiber optic, microwave, and satellite links. In addition, on top of the physical layer a networking layer is implemented that embraces all the possible logical architectures needed to steer LTE traffic and applications.
IP Network Overview
On top of the physical media, the connectivity required by LTE can be realized by using different service types. All these traffic types are forwarded from the last-mile through the aggregation tiers to the core.
The most common implementation scenario including last-mile/aggregation and third-party network segments is displayed in Figure 6:
Figure 6 Transport network scenario based on carrier Ethernet with L3VPNs
- The image was uploaded to a note which you don't have access to
- The note which the image was originally uploaded to has been deleted
The scenarios presented in Figure 6 have been defined only on top of Ethernet (IEEE 802.3), as its the dominant layer 2 technology. The use of Ethernet interfaces has also been assumed for all base station and mobile core nodes.
In the third-party network segment, an IP/MPLS-based transport is used to implement a L3 VPN on top of Ethernet. Using a L3 VPN permits the NaaS operators nodes to communicate privately over the third-party network, even though it routes through multiple third-party elements. Detail on this implementation is out of scope for this module, as that is a service provided by the third-party network.
Transport Technology Overview
The implementation of 4G LTE imposes some requirements on transport networks, such as more network capacity and latency reduction. These requirements are better served through terrestrial technologies (fiber optic and microwave). But in rural areas this becomes a challenge because satellite transport is usually the only feasible technology. For this reason, the transport network infrastructure is an essential component of the NaaS operator network.
An overview of commonly used technologies in the transport network is presented in the following subsections.
-
Fiber Optic Technology
Fiber optic is the mainstay wired transport in mobile operator networks whenever its available because of its significant, inherent bandwidth carrying capability. Additionally, several additional techniques can be used to offset any bandwidth constraints and essentially render the fiber assets future-proof.
While fiber optic has tremendous operational capacity, its main limitation is the cost and logistics of deployment. Moreover, it can take several months to provision each cell site with fiber optic transport.
-
Microwave Technology
Most operators rely heavily on microwave transport solutions in the 5 GHz 80 GHz bands (frequencies above 15GHz are not generally feasible in rural environments). Microwave is a low-cost option for mobile transport, as it can be deployed in a matter of days and support a range of up to several tens of kilometers.
The main limitation of microwave links is the requirement of line of sight (LOS) between transmitter and receiver. This represents an important constraint for its implementation, especially in rural areas due to steep conditions in the terrain. In addition, in many cases microwave requires a license to operate. In high frequencies, microwave links are subject to atmospheric effects or rain fade, which can attenuate the signal and limit its range.
-
Satellite Technology
Satellite technology is deployed in fringe network areas, usually in rural scenarios in emerging markets. Furthermore, satellite technology can be deployed as a temporary measure as an operator waits for regulatory microwave licenses to be approved. Satellite coverage is determined by satellite footprint and location-specific geographical and meteorological conditions.
The cost of satellite terminal equipment located at the base station is in line with microwave equipment. However, the OPEX burden generated by the satellite service fee can impact on the business case.
Functional & Operational Requirements
As stated in section 2.1.1, each eNB requires connectivity to the core elements and additionally for network management and potential synchronization. The subsequent sections describe the different planes that must be supported by the transport network.
Transport User Plane
The user plane (U-plane) in the LTE transport network consists of the S1-U plane used to transport user data between the eNodeB and the S and P-GW using a general radio service tunneling protocol user (GTP-U). It also includes the X2-U plane used to provide connection to neighbor eNodeBs.
The protocol stack required to support the user plane is shown in Figure 7.
Transport Control Plane
The control plane (C-plane) in the LTE transport network is comprised of the S1-MME traffic used to transfer signaling information between the eNodeB and MME. This information is used for S1 bearer management, mobility, and security handling, as well as for application signaling messages between the user equipment (UE) and MME. It also includes the X2-C plane used to provide connection to neighboring eNodeBs.
The protocol stack required to support the control plane is shown in Figure 8.
Transport Management Plane
The management plane (M-plane) in the LTE transport network is the interface between the eNodeB and the O&M system. The M-plane consists of all data required to manage and monitor the status of the network elements. The volume of this traffic has to be considered during the capacity analysis and the frequency to collect these data.
The protocol stack required to support the management plane is shown in Figure 9.
Transport Synchronization Plane
The synchronization plane (S-plane) in the LTE transport network is important to ensure proper functionality of the eNodeBs. The two types of synchronization methods for a mobile network are phase/time and frequency. More detail on the synchronization requirements is in Section 4.7.
However, the implementation of this plane can be optional if its decoupled from the transport network by using GNSS (global navigation satellite system) solutions at the eNB.
Transport and IP Architecture Design Considerations
ON PROGRESS..
Tx Network Design
Tx Network HLD
ON PROGRESS
- HLD Fundamentals
- Functions & Methodologies
- E2E Process Flow
Tx Network LLD
ON PROGRESS
- LLD Fundamentals
- Functions & Methodologies
- E2E Process Flow
IP Transport on TIP
Legend:
- Kuning = Fiber Optic Connection
- Biru = Switch-2 to Router Connection
- Hitam = Switch-1 to Router or General Connection
Room 2 - Transport Section
Ada 2 router dan 2 switch. Merk dari setiap router adalah Cisco ASR, dimana fungsi dari keduanya adalah sebagai internet gateway. Sedangkan untuk switch bermerk Cisco Nexus 9000.
Router memiliki 3 interface diantaranya:
- Gi/0/0
- TenGi/0/0
- TenGi/0/1
Switch-1 memiliki 7 interface diantaranya:
- Ethernet1/1
- Ethernet1/6
- Ethernet1/43 (Dipakai AP HFCL - OpenWifi)
- Ethernet1/45
- Ethernet1/46
- Ethernet1/47
- Ethernet1/48
Switch-2 memiliki 6 interface diantaranya:
- Ethernet1/1
- Ethernet1/6
- Ethernet1/45
- Ethernet1/46
- Ethernet1/47
- Ethernet1/48
Memiliki 15 Konfigurasi Trunk.
Room 1 - Core Section
Open Netra, standing for Open Network Training, is a comprehensive solution designed to facilitate the training, simulation, and management of 5G networks. The primary functionalities of Open Netra include E2E (End-to-End) 5G dashboard simulation and RAN (Radio Access Network) monitoring & configuration. The entire infrastructure is built on a foundation of virtualized network functions, specifically implemented as OpenAirInterface containers, orchestrated and managed by Kubernetes.
Room 3 - RAN Section
Open Netra, standing for Open Network Training, is a comprehensive solution designed to facilitate the training, simulation, and management of 5G networks. The primary functionalities of Open Netra include E2E (End-to-End) 5G dashboard simulation and RAN (Radio Access Network) monitoring & configuration. The entire infrastructure is built on a foundation of virtualized network functions, specifically implemented as OpenAirInterface containers, orchestrated and managed by Kubernetes.
Question
- Why using /25 CIDR for TIP Datacenter?
Radio Frequency Planning
As a VNF 5G Implementation Division on Kubernetes, I design and deploy high-performance OpenAirInterface (OAI) 5G use cases. I optimize network performance, ensure security integration, and collaborate on defining use cases. My focus is on automation for efficient seamless deployment 5G integration in Kubernetes environments.
