Benefits of Packet Based Transport Networks

Published by Darron Toy on

hi this is Rob Shore director of global technical sales fork orient in this video I want to take a look at is packet based transport network and some of the benefits those networks can provide in a previous video we looked at the difference between circuit based networks and packet based networks now there are some advantages circuit based networks can provide but this video is going to focus very specifically on the benefits that are provided by packet based networks which are actually fairly substantial and numerous now the three primary benefits that a packet based transport infrastructure will provide over a circuit based infrastructure start with transport efficiency so enabling a more efficient transport network itself on top of that one of the big benefits of packet based networks will provide is not just in the transport network but in all the devices connected to the transport network in particular for routers so as routers connect to the transport network packet based networks can significantly improve the efficiency of those router interfaces and finally there's an a variety of different things that packet networks can provide when offering business services in providing differentiation on those service offerings so let's get into it the first thing I want to look at is what are some of the limitations for circuit based networks that struggle with providing some of those benefits I mentioned on the previous graphic so the real primary issue with circuit based networks is this it's just what I call per port service based mapping what I mean by that is when you go into a circuit based transport node the only thing a circuit based transport device can do is take all the traffic that comes in on a single port and it has to take all of that track at every ounce of it and put it into a single container all the traffic from that port goes into a single container that container now can only have a single destination I can broadcast things but in general this container will have a single destination so essentially what I'm doing is creating a single physical port to a single individual destination okay so from a network perspective let's take a look at some of the challenges that causes in the network so let's say I have these services in a network I want to provide out to the edge of my network right let's say VPN services internet video services the idea now is like put a router here to aggregate those right so I want to try to create individual traffic flows for each destination the problem though is coming off of this router because my transport network needs separate physical interfaces per destination it's also going to force the router to have a separate physical interface for each destination because I can't hand Trent the transport network a circuit based transport network an aggregated interface because I can't break it apart so this is a big problem one of the issues with this of course is that you know traffic demands themselves are very bursty especially I'm combining internet VPN video trap the traffic goes up and down but because I have a single physical interface per destination I need a size that interface based on the peak requirements of my destination so I don't drop traffic right so beyond that it's not just the peak of the requirement of the destination it's actually the peak rounded-up so what do I mean rounded up what I mean is that if this destination over here requires six gig right the peak utilization peak requirements is six gig what kind of interface I'm going to buy on a by a 10 gig interface so I've taken the peak requirements and I've rounded it up to the nearest physical interface of ten gig and so essentially what I'm doing now is I'm building a network that's the sum of the peak requirements of every destination rounded up to the nearest physical interface so again you can think even you know if one interface here if I need six gig and I'm buying a 10 gig interface already I'm at 60 percent utilization 40% of my capacity of that port goes unutilized and really when you look at it what you end up with is is networks that are based on circuit based transport solutions that have an average utilization of less than 50% in some cases significantly less than 50% and again the key issue here is it's based on a transport network that's going to require a separate physical interface for each destination that I need to transmit traffic between and this is just in the core of the network this problem is actually even worse as I get to the edge of the network because now that I've aggregated this traffic right I've got a single aggregated handoff from the router that's all on this purple wave like going to this destination because that's on a single aggregated handoff right let's say it's 10 gig worth of traffic going to this destination because this transport this circuit based transport note at this destination it can't break up that 10-gig and if I have multiple edge devices which I typically do that I need to get that traffic between I actually need to buy another router at that intermediate location there and I'm going to hand this 10 gig interface off to that router which is going to be then going to break up the traffic into these different edge devices I need to get to so I need an additional router there to break up that traffic and now it gets even worse because if I have a edge part of my now we're going to have an access ring here that hits three different locations remember the handoffs from this router I need a separate physical interface for each one of these individual destinations and if this is a circuit based network I have to break that circuit into these individual different little pipes so now I'm creating a separate physical interface with separate pipes and again just like in the core of my network each of these pipes in each of these interfaces needs to be based on the peak requirements of each destination rounded up so again now end-to-end in my network I'm buying capacity on the transport network and router interfaces based on a sum of the peak requirements of every destination my network and on the edge of the network because I have less locations I'm sharing the bandwidth between this traffic is even more bursty than it is in the core leading to utilization levels of well below 30 percent meaning 70 percent of the stuff I buy at the edge of my network I'm not using I'm basically wasting 70 percent of what I buy at the edge of my network and this is the issue with circuit based networks and the whole idea the whole issue here all centers around this concept of requiring a separate physical interface for every end destination so packet networks overcome this challenge right packet networks overcome this challenge because I can look at the traffic inside this physical interface and I can do per flow based mapping so now as traffic comes in I can look at the labels on the overhead and again I use the word label what I mean read could be a VLAN MPLS TP MAC address or a variety different types of labels just using the generic term label but the idea is I can look at the labels of the incoming frames on this on this physical interface and I can steer that traffic to a variety of different destinations all from a single physical aggregated interface if though again if I look at this from the same overall network architecture delivering the same services right internet video business services now when that traffic comes in to my router the router can take all of these different services together for all of the different destinations and aggregate them all into a single physical interface and handle the transport network then the transport network can take that single physical interface and break it up to the different destinations as necessary so this will have a huge impact on the efficiency of my network in the number of router ports that I need right so even even if I don't over subscribe it right so if I still base the network based on a peak requirements of each destination just by what I call right sizing these pipes so in other words if I have three destinations here that each needs six gig if I had a circuit based network because I need separate physical interfaces I would by three ten gig interfaces for my three destinations with a packet base to network because I can aggregate those into a single interface I can still base it off the peak requirements so no oversubscription no real packet management on the transport network but because I can provide this aggregated handoff I can do that on two 10 gig interfaces right it's still a total of eighteen gig but I can do it on two ten gig interfaces so even with no oversubscription whatsoever right away you've just saved 30 percent of your router ports I can buy 30 percent fewer router ports just by right sizing my traffic so just that by itself can significantly improve the efficiency in the utilization of your network now if I want to get into oversubscription right or maybe you don't have 10 gig coming in and I might have 30 gig worth of bandwidth I need to provide I'm going to over subscribe and packet manage it with that you can get utilizations all the way up to about 85% pretty reliably of course there are additional additional things that need to be managed in network you got on the transport network you have to add prioritization and queuing and things like that now these are relatively easy to implement but it is one extra step but that will get you even more efficiency in the network and again where am I really saving the saving the money on this it's not so much in the transport network it's really most of the benefit is being achieved on the router by being able to buy fewer router interfaces and this is the whole idea is that the transport network a packet base transport network can provide more efficiency transport yes but also when the device is connected to the transport network and now this benefit that I got in the core of my network it's even more pronounced as I get to the edge of my network because we remember in the edge of the network of a circuit based network I needed to buy this router here because I needed something I could break up this aggregated interfaces aggregator traffic flow into the different edge devices I need to connect to but of course now that I have a packet based transport solution I don't need that router intermediate router anymore for that purpose I can still have a router there for providing certain kinds of services but I don't need to waste the resources on those routers just to break up these service flows I can do that directly on the transport device itself and now connect directly to my various edge devices and similarly now that at the very edge of my now we're going to access part because these are packet based rings first of all I can provide a single aggregated handoff to support all the traffic for these three destinations but because that's now a shared pipe I can provide much more flexible services at the edge there right I can use all of the bandwidth for any of these locations so I'll get a certain amount of additional efficiency just by right sizing the pipes right no oversubscription at all but just basing it on the right sizing of the amount of bandwidth required for each of those services and I get really up to from 30% on circuit based networks up to 60% utilization with packet based just based on right sizing but if I want to over subscribe this as well now I get up to 75% utilization on average at the edge of the network so again the ideas I can have a single 10 gig ring here but I can sell actually 10 gig of services to each one of these customers with the expectation that they're not all going to use it at once or I can sell them you know let's say each 3 gig of dedicated bandwidth and then additional 7 gig worth of burst bandwidth all right so again I can sell better more effective services for my end customer and I can generate more revenue using the same physical interfaces in my network so no extra cost in the network to provide that so again I look back on the real benefit that packet based transport network provides in terms of improving efficiency in the network it's less on the transport side and more on the devices connected to the transport network by enabling more in handoffs so I need fewer interfaces fewer handoffs from other devices or being aloft for more services with the same resources that I have and this is where a lot of network operators end up getting into problems because when they do their studies of what transport network we are going to choose you know we're going to go circuit or am I going to go packet a lot of times they can strain that study to just the transport network itself and they don't consider all of the benefits that a packet based transport solution will have on the device is connected to the transport network so again one of the things I want to highlight here and maybe expand when you when one does network studies is to make sure you are including not just the cost of the transport equipment itself but also include the cost of the devices connected to the transport network and I think in most cases you'll find a significant savings when building packet based transport networks now this is just on the efficiency side of things there's another significant benefit that packet based transport networks can provide and this is in being able to manage traffic flows a variety of different ways so looking at the core of the network one of the things I can do is right so I can prioritize this traffic based on flow so each one of these different services coming into my network the VPN the internet video they're all going to be marked differently and when those hit the transport network I can prioritize them differently so if I want to over subscribe in this part of my network my transport network can prioritize video over internet or a BGP ends over both so I can ensure I get a reliable services even with oversubscribed interfaces so the ideas I can get even additional efficiency by or for subscribing and then use traffic management to ensure I get the consistent service consistent performance for the services I need this is a big thing that circuit networks can't do because circuit networks they can't differentiate services on an individual port all the traffic on that one physical port is all handled the same way so if I want different levels of service I need to create different pipes different physical interfaces on my transport on my circuit based transport network with a packet network I can do that same thing but all from a single physical interface now on the core of the network there's some advantages although I do have routers there that can also do some of this prioritization so where I think it makes even more benefit or where packet networks provide even more benefit is that the edge the network where I'm providing business services now what I can do is I can provide differentiated services to my end customers all from the same single physical interface so first off I can use that prioritization concept the ability to prioritize different traffic flows on the same physical interface I can implement that for business services as well so I can provide a single physical interface and I can then prioritize those traffic's different services on that interface differently so let's say they've got you know basic internet surfing and some mission-critical traffic right I can prioritize those differently this again can enable me to sell differentiated services of that customer I can provide them more services for the same price enable me to beat some of my competition and winning that customer's business by by by saying hey here's a 10 gig interface I'm going to give you three gig of constant bitrate you know guarantee traffic and but like you can do the whole rest of it can be bursty traffic so again the ideas I can sell differentiated services more services with the same physical interface and that's just the prioritization of the services there's another big benefit that packet based transport networks can provide for business services not only could I prioritize that but because I'm looking at this traffic on a label by label basis I can actually steer that traffic in different directions from the same physical interface so if my customer says hey I've got a couple new locations hey great I bought this Internet service from you and that's all up and working great now I've got a couple new locations that I'm opening up and I want to get traffic to those locations you can actually provide connectivity from this one single physical interface at the already buying to these new locations simply by steering the frames destined for those locations through the network to those locations so again the idea is I can do all of this from a single physical interface handle traffic differently based on the type of traffic the customers transporting the different types of service they have on that single physical interface and get that traffic to different destinations all within the transport network itself and I can do this without having to back call this traffic all the way back to some centralized point in the network to break that traffic up and then send it back out again so again I can do things much more efficiently I can offer differentiated services to my customers and I can help grow with my customers as they need new types services a packet network can adapt much more readily and much more efficiently and much more quickly to meet those customers needs so this basically the three primary benefits that you get from packet based transport solutions over circuit based solutions we looked at transport efficiency this is the ability to right size pipes so I'm not buying bigger interfaces or bigger transport pipes that I need the ability to share the pipes just a single big giant pipe and all the traffic is shared in between it I don't have to designate little sections of that fixed bandwidth to different locations right so I can use my transport capacity more efficiently and perhaps even more importantly all the devices connected to the transport network those interfaces could be much more efficient right and typically by the way routers in particular these are some of the most expensive interfaces in the network so by building a packet based transport network I can actually save a quite a bit of money on my network just by using my router interfaces more effectively right we're not getting rid of routers we're not bypassing none of that but just by using those interfaces more efficiently you can save a huge amount of money even without doing any oversubscription on the transport network just by right sizing the pipes and of course if you do over subscribe I can add traffic management to the transport network and prioritization and queuing and I can get even more efficiencies out of my router network and finally of course is a service differentiation the ability to take a single physical interface from my end customer and provide different levels of service for difference of their types of traffic needs and a more easily and flexibly connect to more locations to add a more bursty traffic really they be more dynamic with the services I offer them this can help me not only beat my competition and win that customer but it can also help me grow and evolve those customer services over time right I can upsell them new services as their network demands change and their service needs change I can much easily much more easily sell new services to that customer so this is the concept right these are the key benefits of packet based transport networks and of course Corinth is very heavily invested in packet based transport solutions and we have a very broad suite of transport packet based transport solutions and if you're interested in hearing more about any of those solutions please come and visit us at at or check out some of our other videos on some of our packet based solutions or even one of our videos on a unique concept from Korena called universal transport solutions based on our M Terra platform so again if you have any questions or want any more information please visit us at Quarry Netcom that comes to the end of our video hope you enjoyed it and thanks for watching

Leave a Reply

Your email address will not be published. Required fields are marked *