View Single Post
Old 06-11-2010, 14:24   #12
Ignitionnet
Inactive
 
Join Date: Jun 2008
Location: Leeds, West Yorkshire
Age: 47
Posts: 13,995
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Ignitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny starsIgnitionnet has a pair of shiny stars
Re: an idea for VM on traffic management

Quote:
Originally Posted by Chrysalis View Post
Now for my 2nd idea. Probably much more complex than the first.

VM create virtual docsis interface ran in software.

So a real doscis3 upstream and downstream 4 channels bonded on each so 4xdocsis2 72mbit upstream port. Plus 4 down ports for 200+mbit downstream.

Within this 200mbit down and 72mbit upstream up capacity create virtual docsis interfaces that customers connect to, these virtual interfaces been smaller. This software would allow fine tuning where specific customers connect so although the same hard connection limitations exist (individual customers cannot be moved) they can be moved around to different virtual ports, and as such VM can do things like seperate serial users in an area from normal users.. This sort of thing is becoming more common in server hosting where a physical hardware kit will host many virtual servers.

The virtual docsis can be 1.x, 2.x or 3.x so to maintain compatability with customer equipment.
It's not complicated particularly but it's a duplication of existing DOCSIS capabilities. Virgin could produce bad boy pipes right now if they chose to without messing with the DOCSIS segementation or reducing the bandwidth available to other customers.
Ignitionnet is offline   Reply With Quote