Analysis and implementation of the virtual network system

Messaging applications want to use different communication networks. But the unfortunate state of affairs is that applications need to use several different application programming interfaces (APIs) and to design protocols on how and when to use a specific communication network(s). This is troublesome, error-prone and APIs vary a lot; applications want to use just one API but get the benefit of several communications networks. In this paper we detail, implement and test in real field tests a virtual network system (VNS). We argue why messaging applications should use and benefit from VNS. The VNS is a middleware solution that enables seamless usage of different networks. Netlink Next Generation (NLNG) protocol is a practical implementation of VNS and we elaborate on it's features, design choices and problems faced. The NLNG protocol has its origins in the Linux Netlink and VNS concept is a middleware, thus we provide a comparison between these previous works and our work. The VNS system and NLNG protocol have already been tested with several applications, e.g., mail clients, tracking and command softwares, and network interfaces, e.g., IP, VHF, HF, GSM SMS and TETRA SDS.