Demo Abstract: Service-Oriented Future Internet Architecture (SOFIA)

Demo Abstract: Service-Oriented Future Internet Architecture (SOFIA) Gaogang XIE, Yi SUN, Yujun ZHANG, Zhenyu LI, Hongxia ZHENG, Xiaokun ZHENG Institute of Computing Technology, Chinese Academy of Sciences, Beijing, P.R China {xie, sunyi, zhmj, zyli, hxzheng,zhengxiaokun}@ict.ac.cn Abstract—In this demo, we introduce SOFIA, a Service-Oriented Future Internet Architecture. SOFIA introduces a service layer as the thin waist of the protocol stack and includes a series of new mechanisms such as service migration, service label/location separation, service authentication. Therefore, our new architecture can significantly improve the efficiency of the service transmission, better support terminal/network mobility and facilitate security at the service level. We implemented SOFIA on common PCs as well as on our programmable virtual router platform. Results show that SOFIA properly meets the developing trends of the future Internet, significantly improving the efficiency of services and quality of user experiences.

I.

INTRODUCTION

The fundamental mechanism of today’s Internet architecture (TCP/IP) created in the 1960s is a host-to-host communication model. However, after a 50-year truly explosive growth due to the progress of information and communication technologies, nowadays Internet has become an absolutely critical worldwide infrastructure with the unprecedented size. Thus, the current architecture has many difficulties to meet the new demands for Internet development [1], especially on traffic management [2], mobility [3], security [4] etc. First of all, the new computing paradigm (eg. cloud computing) has been accelerating the exponential growth of Internet traffic. To fulfill this requirement in the current Internet architecture, the network capacity should be expanded without limit or data centers should be built everywhere. This is obviously not sustainable. Secondly, mobile computing will be dominant inspirited by the progress of wireless communication technology. However, the current architecture was initially designed for the fixed host-to-host communication model. The IP address not only labels the node’s service but also its location. Thus, when a node moves both its service and location has to be changed. Thirdly, most of the current solutions on security are to check the validity of the devices. However, what the user concerns is a secure service. Thus, the security mechanisms should be designed on a service basis. All the above problems can be properly solved by the service oriented Internet architecture. Actually, what the users want are services, and Internet should be taken as a service pool instead of channels for packet forwarding. Therefore, we propose a new architecture named SOFIA for future Internet. Our architecture has the following advantages. Firstly, applications will be service-aware. Thus, we can improve the efficiency of service acquiring. The popular services can be migrated in the network so that the efficiency of services is enhanced. Secondly, it naturally accommodates mobility. The roaming of

mobile devices only changes their access points but not their services. Thirdly, it facilitates security at the service level. The interfaces between users and the Internet will focus on service requests and service responses. Fourthly, this architecture facilitates the integration of the cloud computing infrastructure into the Internet, allowing users to pay as they use it. Finally, SOFIA is compatible with IPv6, and supports the evolutional revolution on today’s Internet. II.

SOFIA

Comparing with the TCP/IP protocol stack, SOFIA replaces IP with a global unified service ID which is the code of a specific service. The Service ID layer, the thin waist of the stack, is the universal layer which can be located over every data link layer or IP network layer, and all applications can be built over the Service ID layer. In addition, another label “locator” is utilized to specify the location of the network node, thus realizing the separation of service identity/location.

Fig. 1. SOFIA replaces IP with a global unified service ID.

The technical progress of processing capabilities and storage are much faster than that of the transmission bandwidth. Thus, in SOFIA design, we add a processor and storage device in the router model, and that makes the SOFIA router not only providing packet forwarding but also offering popular services to users. The service localization from frequently used services migrating to the local network in SOFIA can not only optimize the service workload and enlarge the capacity of Internet, but also improve the quality of user experience. Fig. 2 depicts the router model of SOFIA. There are five tables in SOFIA routers: Service Information Base (SIB), Routing Information Base (RIB), LSIB (Local Service Information Base), LRIB (Local Routing Information Base) and BIB (Binding Information Base). In addition, Memory Storage and Computing Capability (MSCC) is deployed in the router or connected to the router with a high speed interface. MSCC can localize services by providing cached content and computing ability.

cards formed a simple SOFIA network. In addition, because SOFIA is compatible with IPv6, we also connected one of the routers with the CSTNET. Thereby, users in the current Internet can also visit the services in our SOFIA network. Tens of SOFIA terminals ran the file applications concurrently. In addition, TestCenter was used to produce background traffic.

Communication in SOFIA is driven by services. There are three kinds of basic service operations in SOFIA including Service Registration, Service Updating and Service Request. Once a service starts up, it will register the service into the Internet. Once an active service provider changes its location, it will update its new location to the Internet as well as to its corresponding nodes. Once a user wants to get a service, a service request message will be sent to the access network. Finally, the request message will be delivered to the optimal service provider, which is near the service requestor. Service Registration and Service Updating have the same purpose to register a service provider’s location to others. In addition, service authentication is utilized to prevent the faked service and realize the security at the service level.

B. Experiment Results We repeat the same tests under the SOFIA architecture and the normal TCP/IP architecture separately. The experiments results are as follows. 1) Packet delay The average end-to-end packet delay from the service provider to the service requestor in SOFIA is only 3% of that in normal TCP/IP due to the service location and migration. 2) Packet loss Fig. 3 shows the variation of the packet loss rate with the increase of the traffic intensity in the network. We can see that packet loss becomes seriously high in TCP/IP when the network is busy. However, in SOFIA, service requests are processed at the local routers and therefore, the packet loss rate is significantly decreased.

Fig. 2. SOFIA router model

III.

EXPERIMENT RESULTS

A. Testbed Setup We have implemented several SOFIA routers on common PCs. The common PCs which are chosen to emulate the SOFIA routers are equipped with more than one 100Mbps network cards. The typical configuration parameters of the PC are: Intel(R) Pentium(R) D 3.4GHz CPU, 1G DDR2 RAM and 320G hard disk.

Fig. 3. Variation of the packet loss rate

3) File downloading time Fig. 4 shows the variation of the downloading time of a 100M file with the increase of the traffic intensity in the network. Again, we can conclude that SOFIA greatly improves this performance metric especially when the network is heavily loaded.

We also have implemented SOFIA routers on our programmable virtual router platform. Our programmable virtual router platform uses a common server with specialized network cards. The common server is equipped with a Xeon 2.5GHz 64bit CPU, 16G DDR2 RAM and can be installed with 2 network cards though its PCIE slots. The PCIE bus between the server and network card takes 8 lanes to support 40Gbps bandwidth. Each network card has 4 Gigabit Ethernet ports which are compatible with 10/100M Ethernet. Xilinx Virtex-5 155T FPGA are used for packet processing. TCAM and SRAM are embedded to improve the lookup performance. The implementation of the SOFIA router is realized in Linux Fedora 12 with the kernel version of 2.6.31. The version numbers of gcc and make are 4.2.2 and 3.81 respectively. Netfilter/IPtable scheme is used for the communication between the kernel and the user space. Each packet is extracted from the kernel and processed in the user space.

Fig. 4. Variation of the file downloading time REFERENCES [1]

Finally, a file transfer application is developed for the SOFIA architecture. A client can use this application to download its interesting resources in the network. We use common PCs and notebooks to act as SOFIA terminal devices.

[2] [3]

We conducted experiments in our lab. Two programmable virtual routers and three common PCs each with dual network

[4]

2

A. Feldmann. Internet clean-slate design: what and why?. ACM SIGCOMM Computer Communication Review, 2007, 37(3): 59-64. L. Zhang, D. Estrin, J. Burke et al. Named data networking (NDN) project. PARC Technical Report NDN-0001, 2010 G. Parulkar. Reinventing Internet infrastructure and services. Technical Report, USA: Standford University, http://cleanslate.standford.edu, 2011 J. Wu, J. Bi, X. Li, et.al. A source address validation architecture (SAVA) testbed and deployment experience. IETF RFC 5210, 2008