Why Teams call analytics are critical to your entire business
Analyzing and optimizing mpls technology at Reliance Jio
1. Analyzing and Optimizing
MPLS Technology at RJIL
Internal Mentor: External Mentor: Presented By :
Prof. Sameer Prabhu Mr. Saurabh Srivastava Tushar Saxena
J040
2. Organizational Profile
• RJIL- Upcoming provider of mobile telephony, broadband
services, and digital services in India.
• Formerly Infotel Broadband Services Limited, to provide
4G services on a pan-India level (LTE technology)
• Spectrum in 1800 MHz (across 14 circles) and 2300 MHz
(across 22 circles) capable of offering fourth generation
(4G) wireless services.
• Plans to provide seamless 4G services using FDD-LTE on
1800 MHz and TDD-LTE on 2300 MHz through an
integrated ecosystem.
4. Why MPLS?
• Real-time and multimedia applications have grown
enormously during the last few years.
• Require guaranteed bandwidth in a packet switched
networks.
• MPLS networks cater to these requirements without
compromising scalability.
6. • LER- Insertion of labels before transmission between the
MPLS network.
• LSR- performs label operation and packet forwarding
through the MPLS enabled network.
• Packets Travel across the MPLS enabled network via
specific route -“Label Switched Path (LSP)”.
• This path is unidirectional and is defined between ingress
edge routers to an egress edge router.
• In bidirectional communication, return traffic does not
necessarily take the same path as original traffic.
7. • FEC- includes a cluster of packets of a specific application
forwarded in its switch path over the same pathway
(with same forwarding treatment).
• Every packet of a particular class hold same service
requirement.
• Data traffic is assigned a new FEC.
• Independent LSP assignment is necessary for each
direction.
8. Traditional Routing
• Every router in a network might need full Internet
Routing information.
• Destination- based routing lookups are needed in every
router.
• Consumes more memory, increases the overall time for
routing and decision making for path selection.
9.
10. MPLS Forwarding
• MPLS Core routers swap labels and forward
packets according to simple label lookups.
• MPLS Edge routers also perform a routing table
lookup and have the capability to add or remove
a label.
11.
12. MPLS Control Plane
• Responsible for collecting and propagating the
information that will be used later to forward incoming
packets.
• Routing protocols (OSPF, EIGRP and BGP) and label
distribution protocols are parts of control plane.
• The Routing Information (data)Base (RIB) and Label
Information Base (LIB) are processed in software and
used to populate FIB(forwarding information base)
13.
14. Forwarding Plane
• The Forwarding Information Base (FIB) is built from the
information in the RIB and is used to forward incoming
unlabeled IP packets.
• The egress can be IP packets or labeled packets.
• LFIB is used to forward incoming labeled packets to the
egress interface
• The result can be a labeled packet (label swapping) or
normal IP packet (label disposition).
15.
16. Features of MPLS
• A forwarding mechanism in which packets are forwarded
according to labels
• Decreases forwarding overhead on core routers
• Supports multiple services, including: Unicast and
multicast routing, VPN, TE, QoS, AToM
• Can support forwarding of non-IP protocol.
• MPLS label correspond to destination networks
(equivalent to traditional IP forwarding).
17. MPLS Header Format
• Each label stack entry contains four fields:
• A 20-bit label value. A label with the value of 1 represents the
router alert label
• A 3-bit Traffic Class field for QoS (quality of service) priority and
ECN (Explicit Congestion Notification).
• A 1-bit bottom of stack flag. If this is set, it signifies that the
current label is the last in the stack.
• An 8-bit TTL (time to live) field.
19. • Customers connect to service provider via IP
• Service provider enables any-to-any connectivity
between sites belonging to the same VPN.
• Service uses virtual routers to isolate customer routing
information.
• Customers can use any addressing inside their VPN
20. • MPLS-based VPNs are created in Layer 3 based on the
peer model, makes them more scalable and easier to
build and manage than conventional VPNs.
• Benefits of Peer-to-Peer Model:
• Peer-to-Peer VPN guarantees optimum routing
between customer sites.
• Easier to provision an additional VPN.
• Only Sites provisioned, not links between them
22. Optimization Strategy - SDN
• OpenFlow Protocol- Fundamental for building SDN
solutions.
• Is dynamic, agile and cost effective.
• Appropriate for high- bandwidth, dynamic user
requirements.
• Decouples network control and Forwarding functions-
Directly Programmable
24. Benefits of SDN over MPLS-VPN
• Directly programmable
• Agile
• Centrally managed
• Programmatically configured
• Open standards-based and vendor-neutral
CSR – Cell Site Router, AG- Aggregation , OLT- Optical Line Terminal , Reliance Jio uses IPv6 which is implemented at the internet layer. The Internet Control Message Protocol (ICMP) is primarily used for error and diagnostic functions.
The control plane is the component to a router that focuses on how that one individual box interacts with its neighbors with state exchange.
These MPLS-labeled packets are switched after a label lookup/switch instead of a lookup into the IP table. As mentioned above, when MPLS was conceived, label lookup and label switching were faster than a routing table or RIB (Routing Information Base) lookup because they could take place directly within the switched fabric and not the CPU.
Reliability can become a factor depending upon the service provider that you choose. If the VPN utilizes the Internet it is important to work with a provider that can guarantee minimal downtime.
The design and security implementation for a virtual private network can be complex. This means that it requires a professional with a high level of understanding for the best type of VPN configuration and some of the security issues that can occur when using a VPN.
If it happens to be necessary to create additional infrastructure the solutions can become incompatible and cause technical issues if you use a different product vendor than you used for the current infrastructure. On the other side of the coin and depending upon the product vendor you use, working with the same vendor can sometimes increase the cost of deploying additional infrastructure
SDN Applications are programs that explicitly, directly, and programmatically communicate their network requirements and desired network behavior to the SDN Controller via a northbound interface (NBI)
The SDN Controller is a logically centralized entity in charge of (i) translating the requirements from the SDN Application layer down to the SDN Datapaths and (ii) providing the SDN Applications with an abstract view of the network (which may include statistics and events
The SDN Datapath is a logical network device that exposes visibility and uncontested control over its advertised forwarding and data processing capabilities.
The SDN CDPI is the interface defined between an SDN Controller and an SDN Datapath, which provides at least (i) programmatic control of all forwarding operations, (ii) capabilities advertisement, (iii) statistics reporting, and (iv) event notification
SDN NBIs are interfaces between SDN Applications and SDN Controllers and typically provide abstract network views and enable direct expression of network behavior and requirements
1. Network control is directly programmable because it is decoupled from forwarding functions.
2. Abstracting control from forwarding lets administrators dynamically adjust network-wide traffic flow to meet changing needs.
3. Network intelligence is (logically) centralized in software-based SDN controllers that maintain a global view of the network, which appears to applications as single logical switch.
4. lets network managers configure, manage, secure, and optimize network resources very quickly via dynamic, automated SDN programs, which they can write themselves because the programs do not depend on proprietary software
5. implemented through open standards, SDN simplifies network design and operation because instructions are provided by SDN controllers instead of multiple, vendor-specific devices and protocols.