HOME
BLOG
SHOPPING
 
CATEGORIES
 
Business Technology
RFID
 
Comms Technology
Telco Data
Digital Convergence
Telco Path To Profitability
Network Technology
IP Layering
Cloud Computing
Convergence
IP Infrastructure
Intro To Voice Over IP
Telecoms Whitepapers
Telecoms Index
WiMax
 
Telco Profiles
New Zealand
Australia
 
Mobile Networks
Mobile Applications
Mobile OS
Mobile Advertising
Mobile Video
 
Media
Digital Interactive Media
Digital Music Downloads
Top10 Video Sharing Sites
Mobile Media Broadcast
Mobile Media Industry
 
Web Technologies
Web 2.0
Web 3.0 Semantic
Web 3 Collaboration
Web 4.0 Quality Content
Web - X
Mashups
SOA - Web Services
VoIP in Business
Web 2.0 Enterprises
 
Virtualization
Intro To Virtualization
Planning
Server Virtualization
Platform Virtualization
App. Virtualization
OS Virtualization
Virtual Desktop [VDI]
Microsoft Hyper-V
VMWare VDI
 
On-Demand / SaaS
About SaaS
Selling SaaS
SaaS Channel Models
SaaS Sales Models
Billing SaaS
 
Electricity
Smart Power
Inductive Power Transfer
 
Electronic Payment
E-Payment Systems
E-Payment Directory
Mobile Payment Systems
 
Other
Personal Technology
Oyco Comms Portals
Convergence Marketing
Home Technology
Car Technology
Boat Technology
 
NEWS UPDATES
Media Technology
Telco Industry Updates
News Index
 
OTHER RESOURCES
Convergence Search
Social Media Podcasts
Events
Sitemap
PROJECT LOGIN
 

Network Convergence IP/MPLS


In April 2005, the ATM Forum merged with the Frame Relay Forum and the MPLS Forum to form the the IP/MPLS Forum. The aim of this new Forum was converging the implementation of multi service packet technologies in the global networking communications industry by driving “ the global adoption of IP/MPLS-based technology, networks, services and solutions."
IP is network layer protocol over Ethernet /ATM/SONET/SDH/etc. Although IP has many advantages, it also has a few problems:

  • Lacked fast routing - routing at the IP level is complicated and slow for backbone routing that utilise fast switching protocols such as ATM or another layer 2 switching protocol.
  • Connection to ATM networks - ATM and IP integration solutions usually have an overhead of routing. IP is not designed for cell switching.
  • Lack of an integrated solution for quality of service and class of service handling – IP handles all traffic equally, but in real life, priority handling to support QoS for certain services is essential.

This lead ISPs to swap IP networks for ATM networks.

 

MPLS

MPLS [Multi Protocol Label Switching] solves the problems with IP networks and enables further services such as traffic engineering.

MPLS resides in the gap between the network layer and data link layer [layers 3 & 2 in the OSI model], adding a label [32 bits] of data, to support all these services. It allows:

  • Fast switching [only 32 bit processing
  • Multiple protocols to interconnect [the labels are the same for all protocols].
  • Traffic engineering - building label-unique routes, each with a different class of service and a different quality of service.

MPLS does not replace IP, it enhances it by providing an improved interface to data link switching fabrics and optical networks than defined over ATM.

More on MPLS

Today networks need to support high volumes of best effort data using file transfers, electronic mail, and Internet access.

Different classes of traffic c require different Quality of Service [QoS] - data, voice, and video. This QoS differentiation relies on the capabilities of the underlying network elements - the routers and switches that implement the protocols.

Traditional hop-by-hop processing at its technological limit did not support this requirement, thus a conceptual shift in the forwarding process was required.

By evolving the IP network architecture to prepare next generation networks, allows a smooth and cost controlled transition from the current environment.

Todays networks need to support:

  • Different classes of traffic with specific service characteristics guaranteed across the complete path through the network [and often across multiple autonomous systems].
  • Carrier-class, multi-customer IP infrastructures require robust networks that can manage resources more effectively.
  • Traffic Engineering

And, this means:

  • Bigger, faster, cheaper routers
  • Multilayer switching technology

Next: Benefits of IP Layering

Back To Top