Browse Prior Art Database

Virtual Access Point

IP.com Disclosure Number: IPCOM000126151D
Original Publication Date: 2005-Jul-05
Included in the Prior Art Database: 2005-Jul-05
Document File: 2 page(s) / 46K

Publishing Venue

IBM

Abstract

In the computer world the trend is to build on a physical machine many different virtual layers. The virtualizzazion allows to run many different Operating System (O.S.) on the same hardware and teorically a virtual layer can runs on other virtual layer. To access any O.S. different solutions are at the moment implemented. For example to access a linux virtual layer you can use a vncclient, to access a win layer you can access the terminal service otherwise for vmware machines you can use the vmware terminal. This article proposes a unique access point for any vmlayers.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 85% of the total text.

Page 1 of 2

Virtual Access Point

Our idea should help an operating system user to access to different virtual os running on the same physical machine. Actually on a physical machine can run different virtual os, some of them are a share/portion of native os (i.e. vncserver), others are new os running in a virtualize machine (i.e vmware). An user accesses to vncserver by native client (vncviewer) or webclient, otherwise for vmware the user can access on virtualize machine only by phisical machine, or same NAT complex redirections. To provide an unique solution for this problem a Virtual Access Point (VAP) can be usefull.

     This solution consists of a software layer running on top all virtual servers, a virtual access point.

With this solution client connects to virtual access point and choose the virtual os to use.

The VAP introduce the following benefits:

     - only one client to access all virtual os (a simple browser instead of a lot of different client: vncviever, remote desktop...)

- the communication protocols are hidding.

     The client is a web browser, an applet java running to provide the access gui to VAP. The VAP running on top the virtual os.

The VAP is a software layer that knows all layer running in background. The following picture shows the main concepts.

1

Page 2 of 2

     By an applet inside the web browser it will be possible communicate with the Virtual Access Point.

     Applet communicate with VAP by http protocol (to pass firewall) otherwise the VAP uses the suitable prot...