Telco heavyweights pass packets in NFV demo

NFV gets more open

NTT, NEC, Hitachi, Alcatel-Lucent, Cisco, and ALAXALA have put together a key test of interoperability in the network function virtualisation (NFV) world.

They've shown that the NFV concept of “service chaining” – putting together virtualised services by directing traffic through the addresses of services rather than (say) hardware – not only works, but can work on a cross-vendor basis.

The release itself is pretty dry, so The Reg's networks desk is going to take a shot at explaining why it matters.

Service Chaining

The first step in NFV is to take a function – the firewall is a handy example – and abstract it from particular hardware. Instead it becomes a software running on a virtual machine (VM) that can be spun up and down on-demand.

Service chaining describes the next step in the operation: creating more complex services by “chaining” different virtual network functions (VNFs) together – with different service chains able to be built for different customers.

While vendors would love to keep their customers closeted in a single environment, that's not really feasible – which is why standards organisations like ETSI and the IETF have been working on interoperability.

In the current six-vendor demo, which will be shown off in public later this week at the NTT Musashino R&D Center at that company's 2015 R&D forum, the collaborators demonstrated packet delivery to the appropriate virtual network service, in the correct order.

This involved the six vendors preparing various components of service chaining (Classifier, Service Function Forwarder, Service Function Chaining Proxy, and Controller) and getting them to interoperate.

The NEC canned statement describes the roles of each of these as follows:

  • Classifier – Determines what service is to be applied to a flow, and attaches the appropriate tag. In the interop test, a network service header (currently being standardised in the ITEF) was used as the tag.
  • Service Function Forwarder (SFF) – reads the tag to decide which service function is the destination for a particular packet.
  • SFC Proxy – this provides legacy integration for “pre-NFV” network services. Since (for example) a legacy firewall won't know what to do with the SFC header, it strips it off if a packet is being sent to a legacy service.
  • Controller – manages the Classifier and SFF, and updates the relevant tables.
Multivendor NFV service chaining demo

What multi-vendor NFV service chaining looks like, apparently. Image: NEC

In the service chain shown in the image above, video destined for a mobile device needs to be a bit thinner than a laptop browser.

In the service chaining model, all that's needed to add video optimisation to the chain is the appropriate tag. So if it all works as described on the box, NFV plus service chaining provides both flexibility and automation.

Since telcos won't rip out today's non-virtual equipment while it's still got economic life in front of it, the ability to use NFV proxies to integrate existing kit is also important. Demonstrating multi-vendor interop in a way that also offers a phased introduction of virtualised kit is a big step towards getting telcos to implement the emerging NFV technologies. ®

Broader topics

Narrower topics

Other stories you might like

  • World’s smallest remote-controlled robots are smaller than a flea
    So small, you can't feel it crawl

    Video Robot boffins have revealed they've created a half-millimeter wide remote-controlled walking robot that resembles a crab, and hope it will one day perform tasks in tiny crevices.

    In a paper published in the journal Science Robotics , the boffins said they had in mind applications like minimally invasive surgery or manipulation of cells or tissue in biological research.

    With a round tick-like body and 10 protruding legs, the smaller-than-a-flea robot crab can bend, twist, crawl, walk, turn and even jump. The machines can move at an average speed of half their body length per second - a huge challenge at such a small scale, said the boffins.

    Continue reading
  • IBM-powered Mayflower robo-ship once again tries to cross Atlantic
    Whaddayaknow? It's made it more than halfway to America

    The autonomous Mayflower ship is making another attempt at a transatlantic journey from the UK to the US, after engineers hauled the vessel to port and fixed a technical glitch. 

    Built by ProMare, a non-profit organization focused on marine research, and IBM, the Mayflower set sail on April 28, beginning its over 3,000-mile voyage across the Atlantic Ocean. But after less than two weeks, the crewless ship broke down and was brought back to port in Horta in the Azores, 850 miles off the coast of Portugal, for engineers to inspect.

    With no humans onboard, the Mayflower Autonomous Ship (MAS) can only rely on its numerous cameras, sensors, equipment controllers, and various bits of hardware running machine-learning algorithms to survive. The computer-vision software helps it navigate through choppy waters and avoid objects that may be in its path.

    Continue reading
  • Revealed: The semi-secret list of techs Beijing really really wishes it didn't have to import
    I think we can all agree that China is not alone in wishing it had an alternative to Microsoft Windows

    China has identified "chokepoints" that leave it dependent on foreign countries for key technologies, and the US-based Center for Security and Emerging Technology (CSET) claims to have translated and published key document that name the technologies about which Beijing is most worried.

    CSET considered 35 articles published in Science and Technology Daily from April until July 2018. Each story detailed a different “chokepoint” or tech import dependency that China faces. The pieces are complete with insights from Chinese academics, industry insiders and other experts.

    CSET said the items, which offer a rare admission of economic and technological vulnerability , have hitherto “largely unnoticed in the non-Chinese speaking world.”

    Continue reading

Biting the hand that feeds IT © 1998–2022