WO2010057526A1 - Virtualization mediated system and method - Google Patents

Virtualization mediated system and method Download PDF

Info

Publication number
WO2010057526A1
WO2010057526A1 PCT/EP2008/065837 EP2008065837W WO2010057526A1 WO 2010057526 A1 WO2010057526 A1 WO 2010057526A1 EP 2008065837 W EP2008065837 W EP 2008065837W WO 2010057526 A1 WO2010057526 A1 WO 2010057526A1
Authority
WO
WIPO (PCT)
Prior art keywords
host
electronic device
virtual machine
virtual
software
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/EP2008/065837
Other languages
French (fr)
Inventor
Gregory Allen Kohring
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Europe Ltd
Original Assignee
NEC Europe Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by NEC Europe Ltd filed Critical NEC Europe Ltd
Priority to PCT/EP2008/065837 priority Critical patent/WO2010057526A1/en
Publication of WO2010057526A1 publication Critical patent/WO2010057526A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00Arrangements for program control, e.g. control units
    • G06F9/06Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/44Arrangements for executing specific programs
    • G06F9/4401Bootstrapping
    • G06F9/4411Configuring for operating with peripheral devices; Loading of device drivers
    • G06F9/4413Plug-and-play [PnP]
    • G06F9/4415Self describing peripheral devices
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload

Definitions

  • the present invention relates to an electronic device comprising a virtual appliance stored in a memory thereof.
  • a device software for driving components of the electronic device is provided on the electronic device, preferably encapsulated in the virtual appliance.
  • the virtual appliance being adapted to initiate a virtual machine on a host, such that the device software is preferably encapsulated in said virtual machine.
  • the present invention also relates to a method and a system for providing connectivity between the electronic device and a host, in particular, for providing connectivity between an electronic device and a host by using virtualization technology, more particular, for providing secure connectivity between an electronic device and a host by using virtualization technology.
  • ISDN PBX Primary Branch Exchange
  • PBX Primary Branch Exchange
  • the PBX device itself is self contained and requires no interaction with a computer, except for configuration purposes.
  • special configuration software on the host computer needs to be installed at first, then a connection, e.g., through a USB Interface, is made to a computer, and the previously installed software is used to set the various parameters.
  • the problem with this scenario is that the PBX may run fine for years without needing any user intervention. In the meantime the user's computer has been upgraded and the old configuration software no longer runs on the new platform.
  • the PBX vendor is not willing to supply software for the new platform, then the user has few options other than retaining a copy of the old platform, i.e., hardware and software, simply for the purpose of configuring the PBX, or buying a new PBX. If the PBX vendor is willing to supply software for the new platform, they may send the device software, i.e., device drivers on a CD to end user, or provide the device software on their web page for downloading.
  • the device software i.e., device drivers on a CD to end user, or provide the device software on their web page for downloading.
  • the problem with this approach is that the PBX vendor need to support many different operating systems, or the end users is limited on the operating systems supported by the vendor.
  • the device software handling according to the conventional approach may be summarized as following steps: plugging a device into a computer; searching in a database of device drivers on the computer and attempting to locate an appropriate driver for the device; activating and communicating the device if the appropriate driver is found; or prompting a request for manual intervention such as inserting a CD containing the appropriate driver or downloading the appropriate driver if no appropriate driver is found.
  • the electronic device is preferably provided with a small virtual machine (also virtual appliance in its uninitialized state) which can be dynamically loaded by the host when the device and host are dynamically bound, and can be dynamically shutdown when the connection is broken.
  • the device driver may be provided within the virtual machine, i.e. it is sufficient to run an application platform independent from the host of the virtual machine.
  • the hardware platform is independent but also the software platform, e.g., the favorite operating system without regard to the demands of the device manufacture, may be also freely selected, changed or upgraded as long as the operating system supports the virtual machine provided by the manufacture of the electronic device. That is, the present invention maintains a tight coupling between the device and the device software required to service the device from a host.
  • the dependency between the host operating system and the device software are decoupled, the device may be used in multiple environments. Furthermore, this decoupling may enhance the security of both the electronic device and the host, hence the present invention may also be used in security critical situations.
  • the virtual machine image i.e., the virtual appliance of the first device (electronic device) is dynamically transferred to the second device (the host), giving rise to a symbiotic system with mutually beneficial results for both devices.
  • the second device is the host capable for hosting a virtual machine
  • the first device is the guest or symbiont whose operating system runs on top of operating system of the host.
  • the hardware environment for running the operating system of the electronic device may be virtualized by the virtualizations software of the host.
  • Virtualization technologies are changing the landscape of the enterprise server environment and have also made inroads into the arena of desktop computing.
  • a virtualization enhanced environment hardware and software technologies enables creating a virtual machine (VM), within which an application can run without affecting other applications running on the same server or running in other virtual machine on the same server.
  • VM virtual machine
  • virtualization In a desktop environment virtualization also allows simultaneously running applications written for different operating systems, thus allowing choosing applications based upon their quality and suitability for the purpose and not upon their compatibility with a particular operating system. Furthermore, with the introduction of hardware support for the context switching required in a virtualized environment, many of the performance barriers which previously prevented why spread acceptance of this technology are disappearing.
  • the method for providing device software according to the present invention can have large consequences as a major part of an operating system kernel is taken up by device drivers. If these can all be moved out to their own virtual machine, then the kernel sizes can shrink by several million lines of code, leading to improved stability and performance of the operating system kernel.
  • the present invention provides a method for providing connectivity between an electronic device with a virtual appliance and a host being capable to manage a virtual machine by using a hypervisor.
  • the method comprises steps of: a) establishing a connection between the electronic device and the host; b) providing an access for the host to the electronic device; c) transferring the virtual appliance from the electronic device to the host and instantiating the virtual machine from the virtual appliance; d) launching an application on the host and initiating a communication with the virtual machine by the application via a connection interface provided by the hypervisor of the host; e) shutting down the virtual machine and terminating the connection between electronic device and the host when the communication is no longer required.
  • the subject of the present invention is an electronic device comprising a virtual appliance stored on a memory of the electronic device.
  • the stored appliance being capable to initiate a virtual machine on the host, wherein a device software (device driver) for driving components of the electronic device is encapsulated in the virtual machine.
  • a device software device driver
  • the virtual appliance may be provided in an image format as a file on the electronic device.
  • the virtualization software e.g. the hyper visor on the host may lunch the appliance and initiate a virtual machine.
  • the electronic device may comprise components such as a CPU, an I/O interface, a memory, wherein said memory is preferably a ROM.
  • said memory may also comprise a RAM and/or a flash memory.
  • the electronic device may further comprise a first network interface and the host further comprises a second network interface.
  • the virtual appliance may be provided on the memory of electronic device.
  • a device software for driving the components of the electronic device may be encapsulated in the virtual appliance.
  • the device software may also stored in a separate memory as the virtual appliance located in.
  • the device software may be provided for a particular operating system which may be freely predetermined for hosting the virtual machine. If the device manufacture supports a plurality of operating systems, multiple device software each for driving a particular operating system may also provided.
  • the access for the host to the electronic device may be an exclusive access.
  • the host may be capable to manage multiple virtual machines and the host may comprise at least one preconfigured virtual machine with at least one application.
  • connection between the electronic device and the host may be established over a wired interface such as USB, the first and the second network interface, or a wireless interface such as WLAN, Bluetooth.
  • the host may be operated with a virtual environment software comprising the hypervisor.
  • the hypervisor may provide a virtual machine support which is connected with the I/O interface of the electronic device.
  • the method may further comprise a step of: al) determining if the electronic device includes a virtual appliance.
  • the device software may be provided by a device driver database of the host if the electronic device does not include a virtual appliance.
  • the method may further comprise a step of: a2) terminating the connection between the electronic device and the host if or when the host is not capable to manage the virtual machine.
  • the method may further comprise a step of: cl) launching and interacting the virtual machine by using the standard input and output device.
  • the host may be a secure host and the hypervisor may be secure hypervisor, and the electronic device may be a secure electronic device and the connection between the electronic device and the host may be established through a secure channel.
  • the I/O interface of the electronic device and the virtual machine support may be connected through a secure connection channel, or the first and the second network interface and the virtual machine support may be connected through a secure connection channel.
  • an authentication between the electronic device and the secure host may be carried out before the establishment of the connection therebetween.
  • the subject of the present invention is a system for providing connectivity between the electronic device according to any above mentioned aspects and a host being capable to manage a virtual machine by using a hypervisor.
  • the present invention allows a simplified procedure for providing the device software as follows: plugging the device into the host; a hypervisor running on the host loads the virtual appliance including the device software from the device; the hypervisor instantiates the virtual machine; the hypervisor maps the virtual machine to its list of devices and notifies any other virtual machines that a new device is available, hi this sequence there is no need for the operating system to keep a large database of device drivers, most of which are never needed. There is also no need for the device manufacturer to create and maintain CDs containing the device drivers.
  • the conventional approach that is, the conventional plug-and-play sequence may be replaced by a virtual machine based plug-and-play sequence.
  • devices may also benefit from the present invention, e.g., household appliances, furnaces, smart cards, monitors, sensors, etc.
  • any device which does not require a tight coupling to other applications on the host could benefit from the present invention.
  • device manufactures may also gain as they do not have support multiple combinations of hardware and operating systems, but can rely on the virtualization technology to overcome any compatibility problems. This frees up resources for the software developers to concentrate on producing high quality software and not on getting bogged down in implementation details.
  • the device software servicing the devices runs in its own virtual machine, there is a reduced risk of a manufacture's software having undesired interactions with other software running in the same real machine.
  • Fig. 1 shows a schematic view of the connectivity between the electronic device and the host according to a preferred embodiment of the present invention
  • Fig. 2 shows a flow chart of the connectivity established between the electronic device and the host according to a preferred embodiment of the present invention
  • Fig. 3 shows a schematic view of the connectivity between the electronic device and the host according to a preferred embodiment of the present invention
  • Fig. 4 shows a flow chart of the connectivity established between the electronic device and the host according to a preferred embodiment of the present invention.
  • Fig. 5 shows a further schematic view of the connectivity between the electronic device and the host according to a preferred embodiment of the present invention, similar to the embodiment of Fig. 1.
  • Fig. 1 shows an exemplary architecture for a dynamic symbiotic system according to a preferred embodiment of the present invention.
  • the new components shown here are the symbiont virtual machine 11, i.e., symbiont VM 11 and the symbiont support software 12 in the hypervisor 16.
  • the symbiont support software 12 is a generic device driver which is not dependent upon the details of the symbiont itself and can therefore be re-used for interacting with other symbionts.
  • a simplified description of the sequence of events leading up to such a symbiosis is as follows:
  • the symbiont i.e. the electronic device 20 and the host 10 establish a mutual contact. This might be over a wired or wireless interface 15, e.g., USB, Ethernet, Bluetooth, WLAN, etc.
  • the host 10 retrieves the symbiont virtual machine image, i.e., virtual appliance from the symbiont 20 and instantiates it.
  • the virtual appliance may be stored in ROM 17.
  • the hypervisor 16 may lock the device node providing access to the symbiont 20 in order to ensure no other virtual machines are able to access the symbiont device 20.
  • Other host applications 13 running an other virtual machines 14 may interact with the symbiont VM 11 using an interface, e.g. a network interface provided by the hypervisor 16 as illustrated in the Fig. 1.
  • the application may also directly run on the host and communicate with the virtual machine 11 as shown in Fig.
  • Fig. 2 shows a simplified workflow diagram delineating the exemplary steps of the method according to the present invention for providing connectivity between the electronic device and the host. The step of terminating the connection when the connection is no longer required, is not shown in the workflow.
  • the steps of the method may summarized as follows:
  • step S2 If the device is not a symbiont the normal device activation procedure may be carried out in step S3, or if the device 20 is a symbiont according to the present invention the host 10 queries symbiont for VM requirements in step S4;
  • step S5 If the host is not capable for hosting symbiont, e.g. wrong version and/or lack of hypervisor provided within the virtualization software, the connection between the host and the device 20 may be terminated in step S6, or if host is capable for hosting symbiont the transfer of symbiont VM, e.g. virtual appliance may be transferred from the device 20 to the host 10 in step S7;
  • Fig. 3 shows an exemplary model for a secure symbiotic system according to a preferred embodiment of the present invention.
  • the symbiont 120 and host 110 first may establish a trusted relationship and a secure communication channel 115 using established technologies, e.g., developed by the Trusted Computing Group.
  • a secure hypervisor 116 may be required and all other applications may run within one or more virtual machines started by the secure hypervisor, i.e., the hypervisor should not allow applications to simply run a top of the hypervisor 116.
  • the hypervisor 116 should only allow the different virtual machines to communicate through the virtualized network interface.
  • Fig. 4 shows a simplified workflow illustrating how a secure symbiont 120 interacts with a secure host 110. It shows the exemplary steps of the method according to the present invention for providing a secure connectivity between the electronic device 120 (secure symbiont) and the host 110 (secure host). The additional steps for authentication of the connection may be described as follows:
  • a secure communication channel 115 may be established.
  • Smart cards For example, if a smart card is used for the purposes of digitally signing documents, it may be desired to ensure, that what is being signed is actually what is should be signed.
  • the smart card acting as the secure symbiont may contain a virtual machine capable of displaying the document to be signed. When plugged into a host, they may mutually authenticate and verify the software of the other party, and the secure symbiont's virtual machine may be loaded and run. Such a scenario would not require the host system to install any software other than that necessary to support a secure virtual environment.
  • a secure symbiont used in the area of electronic health records may allow authorized health professionals to examine a patient's electronic health card without any special software.
  • the secure symbiont according to the present invention may prevent the health professionals from making local copies of the information, thus a spread of sensitive patient data may be controlled.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

The present invention relates an electronic device (20, 120) comprising a virtual appliance stored on a memory (17) thereof, in particular, device software for driving components of the electronic device (20, 120) are encapsulated in the virtual machine being initiated from the virtual appliance. The present invention also relates to a method for providing connectivity between the electronic device (20, 120) with a virtual appliance and a host (10, 110) being capable to manage a virtual machine by using a hypervisor (16), wherein the method comprises steps of a) establishing a connection between the electronic device (20) and the host (10); b) providing an access for the host (10) to the electronic device (20); c) transferring the virtual appliance from the electronic device to the host and instantiating the virtual machine from the virtual appliance; d) launching an application (13) on the host (10) and initiating a communication with the virtual machine by the application (13) via a connection interface provided by the hypervisor of the host; e) shutting down the virtual machine and terminating the connection between electronic device and the host when the communication is no longer required.

Description

VIRTUALIZATION MEDIATED SYSTEM AND METHOD
The present invention relates to an electronic device comprising a virtual appliance stored in a memory thereof. In particular, a device software for driving components of the electronic device is provided on the electronic device, preferably encapsulated in the virtual appliance. The virtual appliance being adapted to initiate a virtual machine on a host, such that the device software is preferably encapsulated in said virtual machine. The present invention also relates to a method and a system for providing connectivity between the electronic device and a host, in particular, for providing connectivity between an electronic device and a host by using virtualization technology, more particular, for providing secure connectivity between an electronic device and a host by using virtualization technology.
BACKGROUND OF THE INVENTION
When dynamically attaching a device to a computer problems can arise if the computer does not have the necessary device software to operate the device. Usually this problem is solved by installing the necessary device software (also called device driver or software driver) on the computer using a CD, DVD or some other medium shipped with the device, or downloading the device software from the internet. This conventional method of device software handling, that is, the decoupling of the software from the device provides a limited number of supported platforms, i.e., operating systems and hardware combinations. Thus, the choice of a platform to those supported by the device manufacturer is restricted. If the device manufacture does not support the device any longer, the device may become inoperable when the platform is updated to a newer major version. Furthermore, since the device software can stored separated from the device, in the event the device software is lost, it is impossible to use the device. For example, ISDN PBX (Private Branch Exchange) devices are often used by consumers to manage multiple telephone numbers on their home lines. The PBX device itself is self contained and requires no interaction with a computer, except for configuration purposes. To configure the PBX, special configuration software on the host computer needs to be installed at first, then a connection, e.g., through a USB Interface, is made to a computer, and the previously installed software is used to set the various parameters. The problem with this scenario is that the PBX may run fine for years without needing any user intervention. In the meantime the user's computer has been upgraded and the old configuration software no longer runs on the new platform. If the PBX vendor is not willing to supply software for the new platform, then the user has few options other than retaining a copy of the old platform, i.e., hardware and software, simply for the purpose of configuring the PBX, or buying a new PBX. If the PBX vendor is willing to supply software for the new platform, they may send the device software, i.e., device drivers on a CD to end user, or provide the device software on their web page for downloading. The problem with this approach is that the PBX vendor need to support many different operating systems, or the end users is limited on the operating systems supported by the vendor.
The device software handling according to the conventional approach may be summarized as following steps: plugging a device into a computer; searching in a database of device drivers on the computer and attempting to locate an appropriate driver for the device; activating and communicating the device if the appropriate driver is found; or prompting a request for manual intervention such as inserting a CD containing the appropriate driver or downloading the appropriate driver if no appropriate driver is found.
A previous attempt to solve this problem is disclosed in US 6,754,725, which discloses to store device drivers with the device and to transfer them to a host machine when the device is connected. While this does resolve the problem of providing a tight coupling between the drivers and the device, it is a method, which is dependent on the operating system for which the device drivers are provided. Using Java for the device drivers gains hardware independence, but there is still a residual coupling between the Java VM on the host machine and the byte code version used to compile the device drivers.
It is therefore an object of the present invention to provide an improved electronic device and an improved method and system for a simplified and preferably secure connectivity between the electronic device and a host. In particular, it is a further object of the present invention to provide a method and an electronic device by which a device driver is preferably provided within the device and independent from the platform and/or operating system of the host.
These and other objects are achieved by the features of the independent claims. Further preferred embodiments are characterized in the dependent claims.
SUMMARY OF THE INVENTION
The present invention overcomes the above discussed problems of the prior art solutions and preferably provides a fully platform and/or operating system independent solution. In particular, the electronic device according to a first aspect of the present invention is preferably provided with a small virtual machine (also virtual appliance in its uninitialized state) which can be dynamically loaded by the host when the device and host are dynamically bound, and can be dynamically shutdown when the connection is broken. The device driver may be provided within the virtual machine, i.e. it is sufficient to run an application platform independent from the host of the virtual machine. That is, not only the hardware platform is independent but also the software platform, e.g., the favorite operating system without regard to the demands of the device manufacture, may be also freely selected, changed or upgraded as long as the operating system supports the virtual machine provided by the manufacture of the electronic device. That is, the present invention maintains a tight coupling between the device and the device software required to service the device from a host. As using virrualization technology the dependency between the host operating system and the device software are decoupled, the device may be used in multiple environments. Furthermore, this decoupling may enhance the security of both the electronic device and the host, hence the present invention may also be used in security critical situations.
In other words, according to the present invention, an application for virtualization technology in combination with high speed interconnections and electronic devices is explored. The basic idea here is to equip electronic devices with their own virtual machine which can be read and instantiated by any virtualization enhanced device.
When two such devices come together, the virtual machine image, i.e., the virtual appliance of the first device (electronic device) is dynamically transferred to the second device (the host), giving rise to a symbiotic system with mutually beneficial results for both devices. In view of the relationship of the symbiotic system, the second device is the host capable for hosting a virtual machine, whereas the first device (electronic device) is the guest or symbiont whose operating system runs on top of operating system of the host. The hardware environment for running the operating system of the electronic device may be virtualized by the virtualizations software of the host.
Virtualization technologies are changing the landscape of the enterprise server environment and have also made inroads into the arena of desktop computing. In a virtualization enhanced environment, hardware and software technologies enables creating a virtual machine (VM), within which an application can run without affecting other applications running on the same server or running in other virtual machine on the same server. There are many reasons for wanting such a separation of applications particularly in a server environment where running applications in their own virtual machine allows the operators to make security and performance guarantees even when other applications running in other virtual machines on the same host, hi a traditional time sharing environment with all applications running on a single physical machine, such guarantees are difficult to keep. In a desktop environment virtualization also allows simultaneously running applications written for different operating systems, thus allowing choosing applications based upon their quality and suitability for the purpose and not upon their compatibility with a particular operating system. Furthermore, with the introduction of hardware support for the context switching required in a virtualized environment, many of the performance barriers which previously prevented why spread acceptance of this technology are disappearing.
The method for providing device software according to the present invention can have large consequences as a major part of an operating system kernel is taken up by device drivers. If these can all be moved out to their own virtual machine, then the kernel sizes can shrink by several million lines of code, leading to improved stability and performance of the operating system kernel.
In order to overcome the drawbacks in the prior art, assuming a scenario in which the PBX had a virtual machine containing its device drivers and this VM was automatically instantiated on a virtualization enhanced computer when the PBX is connected. The system upgrades on the host may be carried out without consideration of the requirements of the PBX's configuration software. If all the devices in the home or office were similarly enabled, a favorite platform may be selected without regard to extraneous compatibility issues.
According to an aspect, the present invention provides a method for providing connectivity between an electronic device with a virtual appliance and a host being capable to manage a virtual machine by using a hypervisor. The method comprises steps of: a) establishing a connection between the electronic device and the host; b) providing an access for the host to the electronic device; c) transferring the virtual appliance from the electronic device to the host and instantiating the virtual machine from the virtual appliance; d) launching an application on the host and initiating a communication with the virtual machine by the application via a connection interface provided by the hypervisor of the host; e) shutting down the virtual machine and terminating the connection between electronic device and the host when the communication is no longer required.
According to another aspect, the subject of the present invention is an electronic device comprising a virtual appliance stored on a memory of the electronic device. The stored appliance being capable to initiate a virtual machine on the host, wherein a device software (device driver) for driving components of the electronic device is encapsulated in the virtual machine.
The virtual appliance may be provided in an image format as a file on the electronic device. After the virtual appliance is transferred into the host, the virtualization software, e.g. the hyper visor on the host may lunch the appliance and initiate a virtual machine.
According to another aspect of the present invention, the electronic device may comprise components such as a CPU, an I/O interface, a memory, wherein said memory is preferably a ROM. In a preferred embodiment, said memory may also comprise a RAM and/or a flash memory.
According to another aspect of the present invention, the electronic device may further comprise a first network interface and the host further comprises a second network interface.
According to another aspect of the present invention, the virtual appliance may be provided on the memory of electronic device.
According to another aspect of the present invention, a device software for driving the components of the electronic device may be encapsulated in the virtual appliance. The device software may also stored in a separate memory as the virtual appliance located in.
According to another aspect of the present invention, the device software may be provided for a particular operating system which may be freely predetermined for hosting the virtual machine. If the device manufacture supports a plurality of operating systems, multiple device software each for driving a particular operating system may also provided.
According to another aspect of the present invention, the access for the host to the electronic device may be an exclusive access. According to another aspect of the present invention, the host may be capable to manage multiple virtual machines and the host may comprise at least one preconfigured virtual machine with at least one application.
According to another aspect of the present invention, the connection between the electronic device and the host may be established over a wired interface such as USB, the first and the second network interface, or a wireless interface such as WLAN, Bluetooth.
According to another aspect of the present invention, the host may be operated with a virtual environment software comprising the hypervisor.
According to another aspect of the present invention, the hypervisor may provide a virtual machine support which is connected with the I/O interface of the electronic device.
According to another aspect of the present invention, after the step a) the method may further comprise a step of: al) determining if the electronic device includes a virtual appliance.
According to another aspect of the present invention, the device software may be provided by a device driver database of the host if the electronic device does not include a virtual appliance.
According to another aspect of the present invention, after the step al) the method may further comprise a step of: a2) terminating the connection between the electronic device and the host if or when the host is not capable to manage the virtual machine.
According to another aspect of the present invention, after the step c) the method may further comprise a step of: cl) launching and interacting the virtual machine by using the standard input and output device.
According to another aspect of the present invention, the host may be a secure host and the hypervisor may be secure hypervisor, and the electronic device may be a secure electronic device and the connection between the electronic device and the host may be established through a secure channel.
According to another aspect of the present invention, the I/O interface of the electronic device and the virtual machine support may be connected through a secure connection channel, or the first and the second network interface and the virtual machine support may be connected through a secure connection channel.
According to another aspect of the present invention, an authentication between the electronic device and the secure host may be carried out before the establishment of the connection therebetween.
According to another aspect, the subject of the present invention is a system for providing connectivity between the electronic device according to any above mentioned aspects and a host being capable to manage a virtual machine by using a hypervisor.
The present invention allows a simplified procedure for providing the device software as follows: plugging the device into the host; a hypervisor running on the host loads the virtual appliance including the device software from the device; the hypervisor instantiates the virtual machine; the hypervisor maps the virtual machine to its list of devices and notifies any other virtual machines that a new device is available, hi this sequence there is no need for the operating system to keep a large database of device drivers, most of which are never needed. There is also no need for the device manufacturer to create and maintain CDs containing the device drivers. The conventional approach, that is, the conventional plug-and-play sequence may be replaced by a virtual machine based plug-and-play sequence.
Furthermore, other devices may also benefit from the present invention, e.g., household appliances, furnaces, smart cards, monitors, sensors, etc. Basically, any device which does not require a tight coupling to other applications on the host could benefit from the present invention. Moreover, device manufactures may also gain as they do not have support multiple combinations of hardware and operating systems, but can rely on the virtualization technology to overcome any compatibility problems. This frees up resources for the software developers to concentrate on producing high quality software and not on getting bogged down in implementation details. Furthermore, as the device software servicing the devices runs in its own virtual machine, there is a reduced risk of a manufacture's software having undesired interactions with other software running in the same real machine.
BRIEF DESCRIPTION OF THE DRAWINGS
The invention will now be described in detail with respect to preferred embodiments with reference to accompanying drawings, wherein:
Fig. 1 shows a schematic view of the connectivity between the electronic device and the host according to a preferred embodiment of the present invention;
Fig. 2 shows a flow chart of the connectivity established between the electronic device and the host according to a preferred embodiment of the present invention;
Fig. 3 shows a schematic view of the connectivity between the electronic device and the host according to a preferred embodiment of the present invention;
Fig. 4 shows a flow chart of the connectivity established between the electronic device and the host according to a preferred embodiment of the present invention; and
Fig. 5 shows a further schematic view of the connectivity between the electronic device and the host according to a preferred embodiment of the present invention, similar to the embodiment of Fig. 1. DETAILED DESCRIPTION OF THE INVENTION
Reference is now made in detail to the preferred embodiment of the present invention, examples of which are illustrated in the accompanying drawings.
Fig. 1 shows an exemplary architecture for a dynamic symbiotic system according to a preferred embodiment of the present invention. The new components shown here are the symbiont virtual machine 11, i.e., symbiont VM 11 and the symbiont support software 12 in the hypervisor 16. The symbiont support software 12 is a generic device driver which is not dependent upon the details of the symbiont itself and can therefore be re-used for interacting with other symbionts. A simplified description of the sequence of events leading up to such a symbiosis is as follows:
• The symbiont, i.e. the electronic device 20 and the host 10 establish a mutual contact. This might be over a wired or wireless interface 15, e.g., USB, Ethernet, Bluetooth, WLAN, etc.
• The host 10 retrieves the symbiont virtual machine image, i.e., virtual appliance from the symbiont 20 and instantiates it. For instance, the virtual appliance may be stored in ROM 17. At this point the hypervisor 16 may lock the device node providing access to the symbiont 20 in order to ensure no other virtual machines are able to access the symbiont device 20.
• Users interact with the symbiont VM 11 using standard input devices.
• Other host applications 13 running an other virtual machines 14 may interact with the symbiont VM 11 using an interface, e.g. a network interface provided by the hypervisor 16 as illustrated in the Fig. 1. Alternatively, the application may also directly run on the host and communicate with the virtual machine 11 as shown in Fig.
5.
• When the symbiont 20 is no longer needed, its virtual machine 11 is shutdown and the connection between host 10 and symbiont 20 is closed.
Therefore, according to the present invention, the approach of providing device driver for component is improved significantly, in terms of platform independence and simplicity, in view of the conventional plug and play approach. Fig. 2 shows a simplified workflow diagram delineating the exemplary steps of the method according to the present invention for providing connectivity between the electronic device and the host. The step of terminating the connection when the connection is no longer required, is not shown in the workflow. The steps of the method may summarized as follows:
• Sl : The symbiont (device 20) and host establish a mutual contact;
• S2: If the device is not a symbiont the normal device activation procedure may be carried out in step S3, or if the device 20 is a symbiont according to the present invention the host 10 queries symbiont for VM requirements in step S4;
• S5: If the host is not capable for hosting symbiont, e.g. wrong version and/or lack of hypervisor provided within the virtualization software, the connection between the host and the device 20 may be terminated in step S6, or if host is capable for hosting symbiont the transfer of symbiont VM, e.g. virtual appliance may be transferred from the device 20 to the host 10 in step S7;
• S8: After the transfer of the virtual appliance is completed, the virtual machine (symbiont VM) may be initiated.
The symbiotic system mentioned above is fine for non-critical environments. However. when security is an issue, special precautions need to be taken.
Fig. 3 shows an exemplary model for a secure symbiotic system according to a preferred embodiment of the present invention. The major difference here, is that the symbiont 120 and host 110 first may establish a trusted relationship and a secure communication channel 115 using established technologies, e.g., developed by the Trusted Computing Group. In particular, for a virtualization enhanced host 110, a secure hypervisor 116 may be required and all other applications may run within one or more virtual machines started by the secure hypervisor, i.e., the hypervisor should not allow applications to simply run a top of the hypervisor 116. The hypervisor 116 should only allow the different virtual machines to communicate through the virtualized network interface. Drag and drop, or other such types of GUI operations have to be prohibited in order to prevent other virtual machines from infecting the symbiont 20 virtual machine 11. Fig. 4 shows a simplified workflow illustrating how a secure symbiont 120 interacts with a secure host 110. It shows the exemplary steps of the method according to the present invention for providing a secure connectivity between the electronic device 120 (secure symbiont) and the host 110 (secure host). The additional steps for authentication of the connection may be described as follows:
• S5: If the host 110 is capable for hosting the symbiont VM 11 the transfer of symbiont VM, the mutual authentication of the symbiont 120 and the host 110 may be started in step S 5 a; • S5b: The symbiont 120 and the host 110 verify the software of the other party;
• S5c After the verification, a secure communication channel 115 may be established.
Applications that could benefit from a secure dynamic symbiont system include smart cards. For example, if a smart card is used for the purposes of digitally signing documents, it may be desired to ensure, that what is being signed is actually what is should be signed.
The smart card acting as the secure symbiont may contain a virtual machine capable of displaying the document to be signed. When plugged into a host, they may mutually authenticate and verify the software of the other party, and the secure symbiont's virtual machine may be loaded and run. Such a scenario would not require the host system to install any software other than that necessary to support a secure virtual environment.
A secure symbiont used in the area of electronic health records may allow authorized health professionals to examine a patient's electronic health card without any special software. As further advantage over the standard smart cards, the secure symbiont according to the present invention may prevent the health professionals from making local copies of the information, thus a spread of sensitive patient data may be controlled.
The present invention has now been described with reference to several embodiments thereof. The foregoing detailed description and examples have been given for clarity of understanding only. No unnecessary limitations are to be understood therefore. It will be apparent to those skilled in the art that many changes can be made in the embodiments described without departing from scope of the present invention. In particular, although features and elements of the present invention are described in the preferred embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the preferred embodiments or in various combinations with or without other features and elements of the invention. Therefore, the scope of the present invention should not be limited to the apparatuses, methods and systems described herein.

Claims

Claims
1. A method for providing connectivity between an electronic device (20, 120) with a virtual appliance and a host (10, 110), said host being capable to manage a virtual machine by using a hypervisor (16, 116), wherein the method comprises steps of: a) establishing a connection between the electronic device (20, 120) and the host (10, 110); b) providing an access for the host (10, 110) to the electronic device (20, 120); c) transferring the virtual appliance from the electronic device to the host and instantiating the virtual machine from the virtual appliance; d) launching an application (13) on the host (10) and initiating a communication with the virtual machine (11) by the application (13) via a connection interface provided by the hypervisor (16, 116) of the host; e) shutting down the virtual machine (11) and terminating the connection between electronic device (20, 120) and the host when the communication is no longer required.
2. The method according to claim 1, wherein the electronic device comprises a memory (17, 18), wherein said memory is preferably a ROM, and wherein the virtual appliance is provided on said memory (17, 18).
3. The method according to claim 2, wherein a device software for driving the electronic device is stored in the memory (17, 18) and preferably encapsulated in the virtual appliance.
4. The method according to claim3, wherein the device software is provided for a particular operating system which is predetermined for the virtual machine.
5. The method according to any one of the preceding claims, wherein the access for the host (10, 110) to the electronic device (20, 120) is an exclusive access.
6. The method according to any one of the preceding claims, wherein the host (10, 110) is capable to manage multiple virtual machines (11, 14) and the host comprises at least one preconfϊgured virtual machine (14) with at least one application (13).
7. The method according to any one of the preceding claims, wherein the connection between the electronic device (20, 120) and the host (10, 110) is being established over a wired interface such as USB, a network interface, such as an Ethernet Network Interface, or a wireless interface such as WLAN or Bluetooth.
8. The method according to any one of the preceding claims, wherein the host (10, 110) being operated with a virtual environment software comprising the hypervisor (16).
9. The method according to any one of the preceding claims, wherein the hypervisor (16) provides a virtual machine support (12) which is connected with the electronic device (20, 120).
10. The method according to any one of the preceding claims, wherein after the step a) the method further comprises a step of: al) determining if the electronic device (20, 120) includes a virtual appliance.
11. The method according to claim 10, wherein the device software is provided by a device driver database of the host if the electronic device (20) does not includes a virtual appliance.
12. The method according to claim 10, wherein after the step al) the method further comprises a step of: a2) terminating the connection between the electronic device (20) and the host if the host is not capable to manage the virtual machine.
13. The method according to any one of the preceding claims, wherein after the step c) the method further comprises a step of: cl) launching and interacting the virtual machine by using the Standard input and output device.
14. The method according to any one of the preceding claims, wherein the host is a secure host (110) and the hypervisor is a secure hypervisor (116), and wherein the electronic device is a secure electronic device (120) and the connection between the electronic device and the host is being established through a secure channel (115).
15. The method according to any one of the preceding claims, wherein the electronic device (120) and the virtual machine support (12) is connected through a secure connection channel (115), or the first and the second network interface and the virtual machine support (12) is connected through a secure connection channel (115).
16. The method according to any of the preceding claims, wherein an authentication between the electronic device (120) and the secure host (110) is carried out before the establishment of the connection therebetween.
17. An electronic device (20, 120) comprising a virtual appliance stored on a memory (17, 18) of the electronic device (20, 120), said virtual appliance and being capable to initiate a virtual machine on a host, wherein a device software for driving components of the electronic device is further stored on said memory (17, 18) and preferably encapsulated in the virtual appliance.
18. The electronic device (20, 120) according to claim 17, wherein the device software for driving the electronic device is provided for a particular operating system.
19. A system for providing connectivity between an electronic device (20, 120) according to claims 17 or 18 and a host (10, 110) being capable to manage a virtual machine by using a hypervisor (16, 116).
PCT/EP2008/065837 2008-11-19 2008-11-19 Virtualization mediated system and method Ceased WO2010057526A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/065837 WO2010057526A1 (en) 2008-11-19 2008-11-19 Virtualization mediated system and method

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2008/065837 WO2010057526A1 (en) 2008-11-19 2008-11-19 Virtualization mediated system and method

Publications (1)

Publication Number Publication Date
WO2010057526A1 true WO2010057526A1 (en) 2010-05-27

Family

ID=40377694

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2008/065837 Ceased WO2010057526A1 (en) 2008-11-19 2008-11-19 Virtualization mediated system and method

Country Status (1)

Country Link
WO (1) WO2010057526A1 (en)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100262962A1 (en) * 2009-04-14 2010-10-14 Ravikanth Chaganti Method To Enable Application Sharing On Embedded Hypervisors By Installing Only Application Context
US9245095B2 (en) 2011-10-25 2016-01-26 Ca, Inc. System and method for license management of virtual machines at a virtual machine manager

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997024656A1 (en) * 1995-12-29 1997-07-10 Intel Corporation Method and apparatus for providing an interface between a system and a peripheral device
WO1997049023A2 (en) * 1996-06-20 1997-12-24 Hanson Gordon L Dynamic device driver
EP1056001A2 (en) * 1999-05-26 2000-11-29 Xerox Corporation System and method for dynamically loading platform independent drivers
EP1351138A2 (en) * 2002-04-04 2003-10-08 Matsushita Electric Industrial Co., Ltd. Device control system, network constructed by the system, and program executed on device constructing the system
US6754725B1 (en) * 2001-05-07 2004-06-22 Cypress Semiconductor Corp. USB peripheral containing its own device driver
US6813669B1 (en) * 2000-02-24 2004-11-02 International Business Machines Corporation Agent provided by USB device for executing USB device dependent program in USB host
WO2007149671A2 (en) * 2006-06-23 2007-12-27 Sentillion, Inc. Remote network access via virtual machine
WO2008066574A1 (en) * 2006-11-29 2008-06-05 Sony Ericsson Mobile Communications Ab Methods, devices and computer program products for automatically installing device drivers from a peripheral device onto a host computer

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1997024656A1 (en) * 1995-12-29 1997-07-10 Intel Corporation Method and apparatus for providing an interface between a system and a peripheral device
WO1997049023A2 (en) * 1996-06-20 1997-12-24 Hanson Gordon L Dynamic device driver
EP1056001A2 (en) * 1999-05-26 2000-11-29 Xerox Corporation System and method for dynamically loading platform independent drivers
US6813669B1 (en) * 2000-02-24 2004-11-02 International Business Machines Corporation Agent provided by USB device for executing USB device dependent program in USB host
US6754725B1 (en) * 2001-05-07 2004-06-22 Cypress Semiconductor Corp. USB peripheral containing its own device driver
EP1351138A2 (en) * 2002-04-04 2003-10-08 Matsushita Electric Industrial Co., Ltd. Device control system, network constructed by the system, and program executed on device constructing the system
WO2007149671A2 (en) * 2006-06-23 2007-12-27 Sentillion, Inc. Remote network access via virtual machine
WO2008066574A1 (en) * 2006-11-29 2008-06-05 Sony Ericsson Mobile Communications Ab Methods, devices and computer program products for automatically installing device drivers from a peripheral device onto a host computer

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100262962A1 (en) * 2009-04-14 2010-10-14 Ravikanth Chaganti Method To Enable Application Sharing On Embedded Hypervisors By Installing Only Application Context
US8726269B2 (en) * 2009-04-14 2014-05-13 Dell Products L.P. Method to enable application sharing on embedded hypervisors by installing only application context
US9245095B2 (en) 2011-10-25 2016-01-26 Ca, Inc. System and method for license management of virtual machines at a virtual machine manager

Similar Documents

Publication Publication Date Title
JP5940159B2 (en) Method, computer program, device and apparatus for provisioning an operating system image to an untrusted user terminal
US8201239B2 (en) Extensible pre-boot authentication
EP2513809B1 (en) Systems and methods for service isolation
US8909940B2 (en) Extensible pre-boot authentication
US7162628B2 (en) Method, system, apparatus and program product for temporary personalization of a computer terminal
EP2958257B1 (en) Network policy implementation for a multi-virtual machine appliance
EP2568408B1 (en) Information processing device, information processing method, and program distribution system
TW202507498A (en) Automatically deployed information technology (it) system and method with enhanced security
US10574524B2 (en) Increasing reusability of and reducing storage resources required for virtual machine images
US20110258456A1 (en) Extensible management of self-encrypting storage devices
US9639691B2 (en) Dynamic database and API-accessible credentials data store
KR20060042093A (en) Method and system for providing a common operating system
US20140143794A1 (en) Methods for enabling software in storage-capable devices
JP2004199672A (en) Uniform framework of security token
JP4286798B2 (en) Method for installing driver file on hard drive, computer and computer-readable storage medium
AU2015358292A1 (en) Computing systems and methods
EP2972856B1 (en) System and method for generic product wiring in a virtual assembly builder environment
US20230359741A1 (en) Trusted boot method and apparatus, electronic device, and readable storage medium
EP1615128A1 (en) Techniques for providing services and establishing processing environments
CN104572093A (en) Method for realizing bi-operation system starting of terminal equipment by using USB (universal serial bus) controller
CN101369302B (en) Method and system for controlling access authority of information safety equipment
JP2008524686A (en) Method for maintaining an application in a computer device
CN105144085B (en) Software Framework for Storage Devices
WO2010057526A1 (en) Virtualization mediated system and method
CN116069584A (en) Extending monitoring services into trusted cloud operator domains

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08875342

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 30.08.11)

122 Ep: pct application non-entry in european phase

Ref document number: 08875342

Country of ref document: EP

Kind code of ref document: A1