In this paper, we propose a mechanism for automatic configuration of name-bound virtual networks (NBVNs) for Internet of Things (IoT). Generally, IoT devices indicate their correspondent nodes by names. However, current technologies for the construction of virtual networks (VNs) rely on VLANs, IP routing, and OpenFlow control, thus they do not provide a name-based solution. Our proposal fills this gap. We first define business players and their roles for constructing and using the NBVNs. The players are application service provider (ASP), virtual network operator (VNO), and infrastructure provider (InP). Subsequently, we propose a system to automatically construct NBVN. It automatically allocates and assigns the IPv6 addresses required by the network nodes, including IoT devices, of each NBVN. Moreover, it auto-configures the mechanisms for data forwarding and name resolution. Thus, the proposed system constructs area-and/or time-bound VNs for offering network services to event-centric IoT applications, such as outdoor concerts and sporting events. Furthermore, we apply our proposed system to automatically construct wide-area management networks. Finally, we demonstrate that the constructed NBVNs are capable of configuring thousands of addresses and name entries within a minute, thus IoT devices can communicate with each other by using names instead of addresses. tween VNO and InPs.These management networks are constructed for the automation of the other NBVNs. They are not automatically constructed according to the proposed procedure described in Section 3.2. The network managers must specify network nodes and interfaces, and assign names to the nodes. However, L3 functions such as addressing, forwarding and name resolution, are still automatically configured.
Requirements and Conditions of NBVNs for ASP and the Management NBVNsWe summarize the requirements and conditions of NBVNs for ASP and the management NBVNs, and clarify the differences between the two types of NBVNs, before we describe the construction procedure of the management NBVNs.The requirements of NBVNs for ASP is to construct an NBVN that provides addressing, routing and name resolution functions. The NBVN is used for the ASP to make an access to the access points and the servers, and is used for IoT devices to communicate with each other by names.Conditions are that the network manager of ASP knows locations where access points are to be placed and server specifications, without information about names of access points and servers and their connections. InP management networks and VNO/InPs management network are constructed in advance.In order to construct the NBVN for ASP, the network managers ASP makes a request to the VNO server vno.rb via generic communication means such as the Internet. Then, vno.rb makes a request to each of the InP servers inp.rbs via the VNO/InPs management NBVN. Subsequently, each inp.rb starts a vnn.rb on the nodes in the NBVN for ASP via each InP management NBVN (see Section 4.3 in detail).As for the requirements of In...