Network Protocol Virtualization

Last updated

Network Protocol Virtualization or Network Protocol Stack Virtualization is a concept of providing network connections as a service, without concerning application developer to decide the exact communication stack composition.

Contents

Concept

Dataflow for communication payload leveraging network protocol virtualization software. NPV.png
Dataflow for communication payload leveraging network protocol virtualization software.

Network Protocol Virtualization (NPV) was firstly proposed by Heuschkel et al. in 2015 as a rough sketch as part of a transition concept for network protocol stacks. [1] The concept evolved and was published in a deployable state in 2018. [2]

The key idea is to decouple applications from their communication stacks. Today the socket API requires application developer to compose the communication stack by hand by choosing between IPv4/IPv6 and UDP/TCP. NPV proposes the network protocol stack should be tailored to the observed network environment (e.g. link layer technology, or current network performance). Thus, the network stack should not be composed at development time, but at runtime and it needs the possibility to be adapted if needed.

Additionally, the decoupling relaxes the chains of the ISO OSI network layer model, and thus enables alternative concepts of communication stacks. Heuschkel et al. proposes the concept of Application layer middleboxes as an example to add additional layers to the communication stack to enrich the communication with useful services (e.g. HTTP optimizations [3] )

The Figure illustrates the data flow. Applications interface to the NPV software through some kind of API. Heuschkel et al. proposed socket API equivalent replacements but envisioned more sophisticated interfaces for future applications. A scheduler assigns the application payload to one (of potentially many) communication stack to get processed to network packets, that get sent using networking hardware. A management component decides how communication stacks get composed and the scheduling scheme. To support decisions a management interface is provided to integrate the management system in software-defined networking contexts.

NPV has been further investigated as a central element of LPWAN Internet of Things (IoT) scenarios. Specifically, the deployment of applications that are agnostic to the underlying transport, network, link and physical layers was explored by Rolando Herrero in 2020. [4] In this context, NPV becomes a very successful and flexible tool to accomplish the deployment and management of constrained sensors, actuators and controllers in massive IoT access networks. [5]

Implementations

Currently there is just one academic implementation available to demonstrate the concept. Heuschkel et al. published this implementation as demonstrator in 2016. [6] The last iteration of this code is available under AGPLv3 on Github.

See also

Related Research Articles

A web service (WS) is either:

Message-oriented middleware (MOM) is software or hardware infrastructure supporting sending and receiving messages between distributed systems. Message-oriented middleware is in contrast to streaming-oriented middleware where data is communicated as a sequence of bytes with no explicit message boundaries. Note that streaming protocols are almost always built above protocols using discrete messages such as frames (Ethernet), datagrams (UDP), packets (IP), cells (ATM), et al.

<span class="mw-page-title-main">Contiki</span> Real-time operating system

Contiki is an operating system for networked, memory-constrained systems with a focus on low-power wireless Internet of Things (IoT) devices. Contiki is used for systems for street lighting, sound monitoring for smart cities, radiation monitoring and alarms. It is open-source software released under the BSD-3-Clause license.

REST is a software architectural style that was created to guide the design and development of the architecture for the World Wide Web. REST defines a set of constraints for how the architecture of a distributed, Internet-scale hypermedia system, such as the Web, should behave. The REST architectural style emphasises uniform interfaces, independent deployment of components, the scalability of interactions between them, and creating a layered architecture to promote caching to reduce user-perceived latency, enforce security, and encapsulate legacy systems.

AUTOSAR is a global development partnership founded in 2003 by automotive manufacturers, suppliers and other companies from the electronics, semiconductor and software industries. Its purpose is to develop and establish an open and standardized software architecture for automotive electronic control units (ECUs).

<span class="mw-page-title-main">Profinet</span> Computer network protocol

Profinet is an industry technical standard for data communication over Industrial Ethernet, designed for collecting data from, and controlling equipment in industrial systems, with a particular strength in delivering data under tight time constraints. The standard is maintained and supported by Profibus and Profinet International, an umbrella organization headquartered in Karlsruhe, Germany.

<span class="mw-page-title-main">Computer network</span> Network that allows computers to share resources and communicate with each other

A computer network is a set of computers sharing resources located on or provided by network nodes. Computers use common communication protocols over digital interconnections to communicate with each other. These interconnections are made up of telecommunication network technologies based on physically wired, optical, and wireless radio-frequency methods that may be arranged in a variety of network topologies.

A network socket is a software structure within a network node of a computer network that serves as an endpoint for sending and receiving data across the network. The structure and properties of a socket are defined by an application programming interface (API) for the networking architecture. Sockets are created only during the lifetime of a process of an application running in the node.

A Vehicular ad hoc network (VANET) is a proposed type of mobile ad hoc network (MANET) involving road vehicles. VANETs were first proposed in 2001 as "car-to-car ad-hoc mobile communication and networking" applications, where networks could be formed and information could be relayed among cars. It has been shown that vehicle-to-vehicle and vehicle-to-roadside communications architectures could co-exist in VANETs to provide road safety, navigation, and other roadside services. VANETs could be a key part of the intelligent transportation systems (ITS) framework. Sometimes, VANETs are referred to as Intelligent Transportation Networks. They could evolve into a broader "Internet of vehicles". which itself could evolve into an "Internet of autonomous vehicles".

<span class="mw-page-title-main">Apache Axis2</span> Web service engine

Apache Axis2 is a web service engine. It is a redesign and re-write of the widely used Apache Axis SOAP stack. Implementations of Axis2 are available in Java and C.

<span class="mw-page-title-main">Computer appliance</span> Dedicated computer system

A computer appliance is a computer system with a combination of hardware, software, or firmware that is specifically designed to provide a particular computing resource. Such devices became known as appliances because of the similarity in role or management to a home appliance, which are generally closed and sealed, and are not serviceable by the user or owner. The hardware and software are delivered as an integrated product and may even be pre-configured before delivery to a customer, to provide a turn-key solution for a particular application. Unlike general purpose computers, appliances are generally not designed to allow the customers to change the software and the underlying operating system, or to flexibly reconfigure the hardware.

Carrier Ethernet is a marketing term for extensions to Ethernet for communications service providers that utilize Ethernet technology in their networks.

Web of Things (WoT) describes a set of standards by the World Wide Web Consortium (W3C) for the interoperability of different Internet of things platforms and application domains.

Software-defined networking (SDN) is an approach to network management that uses abstraction to enable dynamic and programmatically efficient network configuration to create grouping and segmentation while improving network performance and monitoring in a manner more akin to cloud computing than to traditional network management. SDN is meant to improve the static architecture of traditional networks and may be employed to centralize network intelligence in one network component by disassociating the forwarding process of network packets from the routing process. The control plane consists of one or more controllers, which are considered the brains of the SDN network, where the whole intelligence is incorporated. However, centralization has certain drawbacks related to security, scalability and elasticity.

The Open Smart Grid Protocol (OSGP) is a family of specifications published by the European Telecommunications Standards Institute (ETSI) used in conjunction with the ISO/IEC 14908 control networking standard for smart grid applications. OSGP is optimized to provide reliable and efficient delivery of command and control information for smart meters, direct load control modules, solar panels, gateways, and other smart grid devices. With over 5 million OSGP based smart meters and devices deployed worldwide it is one of the most widely used smart meter and smart grid device networking standards.

RTP-MIDI is a protocol to transport MIDI messages within Real-time Transport Protocol (RTP) packets over Ethernet and WiFi networks. It is completely open and free, and is compatible both with LAN and WAN application fields. Compared to MIDI 1.0, RTP-MIDI includes new features like session management, device synchronization and detection of lost packets, with automatic regeneration of lost data. RTP-MIDI is compatible with real-time applications, and supports sample-accurate synchronization for each MIDI message.

Network functions virtualization (NFV) is a network architecture concept that leverages IT virtualization technologies to virtualize entire classes of network node functions into building blocks that may connect, or chain together, to create and deliver communication services.

<span class="mw-page-title-main">Open vSwitch</span> Virtual network switch

Open vSwitch (OVS) is an open-source implementation of a distributed virtual multilayer switch. The main purpose of Open vSwitch is to provide a switching stack for hardware virtualization environments, while supporting multiple protocols and standards used in computer networks.

<span class="mw-page-title-main">RIOT (operating system)</span> Real-time operating system

RIOT is a small operating system for networked, memory-constrained systems with a focus on low-power wireless Internet of things (IoT) devices. It is open-source software, released under the GNU Lesser General Public License (LGPL).

<span class="mw-page-title-main">Transition (computer science)</span>

Transition refers to a computer science paradigm in the context of communication systems which describes the change of communication mechanisms, i.e., functions of a communication system, in particular, service and protocol components. In a transition, communication mechanisms within a system are replaced by functionally comparable mechanisms with the aim to ensure the highest possible quality, e.g., as captured by the quality of service.

References

  1. ↑ Heuschkel, Jens; Schweizer, Immanuel; Zimmermann, Thorsten; Wehrle, Klaus; Mühlhäuser, Max (2015). "Protocol Virtualization through Dynamic Network Stacks". Proceedings of 1st Workshop on Software-Defined Networking and Network Function Virtualization for Flexible Network Management (SDNFlex).
  2. ↑ Heuschkel, Jens; Wang, Lin; Fleckstein, Erik; Ofenloch, Michael; Blöcher, Marcel; Crowcroft, Jon; Mühlhäuser, Max (2015). "VirtualStack: Flexible Cross-layer Optimization via Network Protocol Virtualization". Proceedings of 43rd Local Computer Networks (LCN) IEEE.
  3. ↑ Heuschkel, Jens; Forstmann, Jens; Wang, Lin; Mühlhäuser, Max (2018). "Identifying the Performance Impairment of HTTP". Proceedings of 42rd Local Computer Networks (LCN) IEEE.
  4. ↑ Herrero, Rolando (2021). "Protocol stack virtualization support in IoT". Transactions on Emerging Telecommunications Technologies. 32 (11). doi:10.1002/ett.4340. S2CID   238717271.
  5. ↑ Herrero, Rolando (2021). "Towards protocol stack virtualization in massive IoT deployments". Internet of Things. 14: 100396. doi:10.1016/j.iot.2021.100396. S2CID   233522611.
  6. ↑ Heuschkel, Jens; Stein, Michael; Mühlhäuser, Max (2016). "VirtualStack: SDN-controlled Transparent Protocol Transitions At the Edge". Proceedings of 41rd Local Computer Networks (LCN) IEEE.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.