CN102301605A - System and method for virtualizing the peripherals in a terminal device to enable remote management via removable portable media with processing capability - Google Patents

Abstract

Systems and methods for virtualizing the peripherals in a wireless device to enable remote management via removable portable media with processing capability are described. One aspect may include a system for virtualizing a peripheral device of a wireless device from a media device, the system comprising a media device, including a first memory; a processor coupled to said first memory; and a virtualization device controller interface remote layer adapted to run on said processor and first memory, wherein said virtualization device controller interface remote layer is adapted to communicate with a peripheral device of the wireless device.

Description

System and method for virtualizing peripheral devices in terminal devices to enable remote management through removable portable devices with processor capabilities

Cross References to Related Applications

This application claims priority to U.S. Patent Application Serial No. 12/386,212, filed April 14, 2009, which claims serial numbers 61/206,454, 61/206,453, and 61/ 206,427, and the priority of US Provisional Patent Application Serial No. 61/206,797, filed February 4, 2009, the entire contents of which are hereby incorporated by reference.

technical field

The present invention relates to a system and method for virtualizing peripheral devices in terminal devices for remote management by removable portable devices with processor capabilities.

Background technique

Current wireless device or wireless handheld device designs have the functionality of a software layer running on a main processor or application processor with a direct path to connected peripherals such as but not limited to displays, keyboards, communication hardware, programming Codecs, printers, cameras, and network hardware. The application and runtime environment depend on the operating system and hardware architecture of each wireless device or wireless handset. The runtime environment accesses the hardware through the hardware framework layer, which uses the embedded operating system and associated device drivers to control the hardware. When migrating software, especially when enhancing wireless device features and upgrading operating systems, significant effort is required to maintain the application and runtime environment.

Contents of the invention

It may be desirable to have a system and method for virtualizing peripherals in a wireless device for remote management by a removable portable device with processor capabilities. This makes the runtime environment and applications independent of the radio hardware implemented on the wireless handset. The removable media with the processor and installed software can be connected to any other wireless handheld device with a different radio hardware configuration and still function properly.

In some aspects, the invention can provide a method. In one aspect, the method may include providing a remote processor package on a removable medium that virtualizes hardware on the terminal or wireless handheld device.

In one aspect, the present invention may provide a remote processor package system disposed on a removable medium. One aspect may include a system for virtualizing peripherals of a wireless device by a media device, the system comprising: a media device including a first memory; a processor coupled to the first memory; and a processor adapted to operate on the A virtualized device controller interface remote layer on the processor and the first memory, wherein the virtualized device controller interface remote layer is adapted to communicate with peripheral devices of the wireless device. Another aspect may include a method for virtualizing a peripheral device of a wireless device by a media device, the method comprising emulating on the media device a hardware interface for communicating with a runtime environment; Hardware configuration; the peripheral device of the wireless device is mapped to the emulated hardware interface by the remote layer of the virtualization device controller interface on the media device, so that the media device operates as if directly connected to the peripheral device; The logical port of the peripheral device on the wireless device; the peripheral device command is packaged into a data packet by the virtualization device controller interface remote layer on the media device; the remote layer is interfaced by the virtualization device controller on the media device transmitting the wrapped data packet containing the peripheral device command to the wireless device; and the media device executing the command as if the peripheral device of the wireless device were directly connected to the media device.

Description of drawings

Features and other aspects of embodiments of the invention are explained in the following description, taken in conjunction with the accompanying drawings, in which:

Fig. 1 shows a wireless handheld device block diagram of a typical wireless handheld device;

Figure 2 shows a wireless handheld device block diagram of a processor in a removable media device according to one aspect of the systems and methods of the present invention;

3 illustrates a block diagram of communications between a wireless handheld device and a removable media device according to one aspect of the systems and methods of the present invention;

Figure 4 shows a flowchart for a WiFi hardware request process in accordance with one aspect of the systems and methods of the present invention;

5 illustrates a VDCI implementation of a radio handset and removable media device according to one aspect of the systems and methods of the present invention; and

Figure 6 shows a block diagram of a removable media device hardware design.

Detailed ways

Now, various embodiments of the present invention will be described.

As shown in FIG. 1 , a typical architecture of a wireless device includes a processor 102 located in the remainder of the interface hardware of a wireless handheld device 101 . Interface hardware may include an LCD display, keyboard or touch screen 108, radio hardware 109, audio codec 110, Bluetooth 111, WiFi 112, GPS 113, and camera 114, each connected to the main processor 102 through hardware device drivers 107. Additionally, handheld device 101 includes applications 103 , runtime environment 104 , radio hardware architecture 105 , and embedded operating system kernel 106 .

An aspect of the present invention may include a method wherein a removable media device 202 with processing capabilities may remotely manage the application software 103, runtime environment 104, Internal communication infrastructure (including but not limited to wireless or fixed copper wires) 105 and embedded operating system 106 . In one aspect, communication link 203 may be a bus, such as USB. In other aspects, communication link 203 may be a wireless connection. In a further aspect, communication link 203 may be a high speed bus. Others include, but are not limited to, USB, SD, microSD, SIM, SAM, and MMC as communication link 203 . In other respects, a terminal device 201 or a wireless handheld device refers to a device having RAM, ROM and a processor 301, and an embedded operating system running on the processor. In another aspect, removable media device 202 may contain at least one processor, memory, and other circuitry with communication link 203 . Other aspects may package the removable media device 202 in form factors including, but not limited to, SIM, SAM, SD, microSD, MMC, or USB.

In one aspect, end device 201 and removable media device 202 may communicate via a virtualized device controller interface ("VDCI"). In a further aspect, the VDCI implementation on the terminal device 201 refers to a VDCI device or a VDCI device daemon 205 . In other aspects, a VDCI implementation on a removable media device is referred to as VDCI remote or VDCI remote layer 204 . In one aspect, the VDCI device daemon 205 in the terminal device 201 is a software program running on the base processor or baseband processor 301 in the terminal device 201 . In another aspect, the VDCI remote layer 204 is a daemon that exists above the embedded operating system 106 of the removable media device 202 and below the runtime environment 104 or the hardware framework 105 of the windowing system of the removable media device 202 .

One aspect uses virtualization to virtualize peripherals in terminal device 201 and enable application 103 in removable media device 202 to control these peripherals over communication link 203 . Other aspects may have a terminal device 201 with a thin layer of software called a VDCI device 205 to virtualize and manage all peripherals without requiring all applications present in the terminal device 201 . Another aspect may include a VDCI remote 204 in the removable media device 202 that may receive requests from the application software 103 . In other aspects, the VDCI remote 204 will communicate with the VDCI device 205 . In other aspects, VDCI device 205 directs VDCI remote communication 204 to the appropriate physical device or peripheral for proper operation.

On the other hand, the terminal device 201 may only require the VDCI device daemon 205 to be installed. In other aspects, the removable media device 202 may require a corresponding VDCI remote layer 204 to be installed. In a further aspect, the application 103 residing in the removable device 202 can be run with any terminal device 201 having a VDCI device 205 without customization and further acceptance testing. FIG. 2 shows an aspect depicting an end device 201 having a VCDI device daemon 205 interacting with a removable media device 202 having a VDCI remote layer 204 . In one aspect, removable media device 202 may be connected to end device 201 via communication link 203 . In one aspect, the terminal device 201 may include a processor 301 that may control hardware devices and peripherals such as radio hardware 109, Bluetooth 111, audio codec 110, WiFi 112, GPS 113, display 108, and camera 114. In a further aspect, the processor 301 in the terminal device 201 may be connected to the removable media device 202 via the communication link 203 .

In one aspect, the VDCI remote layer 204 can map the hardware in the wireless terminal device 201 with the VDCI device daemon 205 , so that the runtime environment 104 and the application 103 in the mobile device 202 can access the hardware on the terminal device 201 . In a further aspect, the VDCI remote layer 204 can allow the applications 103 and the runtime environment 104 on the removable media device 202 to directly access the hardware on the terminal device 201, rather than through the removable media device 202 without any implemented hardware drivers Operating system 106 to access the hardware. Other aspects allow the runtime environment 104 and the applications 103 to run independently of the hardware present in the terminal device 201 . Other aspects require VDCI device daemon 205 updates for new hardware changes to map to existing VDCI remote layer 204 implementations. On the other hand, under the situation of keeping the application 103 and the user interface on the removable media device 202, the user with the removable media device 202 can insert it into any other terminal device 201 with the VDCI device daemon 205, It enables user and application portability.

In one aspect, VDCI may be implemented using point-to-point communication over the transport layer 302 of the communication link 203 between the terminal device 201 and the removable media device 202 . Other aspects may use client-to-server communication over the transport layer 302 of the communication link between the terminal device 201 and the removable media device 202 . Transport layer 302 may be responsible for transporting data to appropriate application processes on the host computer. In one aspect, FIG. 3 illustrates the logical data exchange between the removable media device 202 and the terminal device 201 . In FIG. 3 , the WiFi hardware 112 is mapped to the VDCI remote layer 204 in the removable media device 202 using the transport layer 302 of the communication link 203 . In one aspect, communication link 203 may also include network layer 303 , data link layer 304 , and physical layer 305 . In a further aspect, the VDCI remote layer 204 is mapped to the transport layer 302, as shown at 306b, and the transport layer 302 is mapped to the VDCI device daemon 205, as shown at 306a. In another aspect, the embedded operating system 106 is mapped to the physical layer 305, as shown at 307b, and the physical layer 305 is mapped to the base processor 301, as shown at 307a.

In another aspect, FIG. 4 shows a flow diagram for mapping the WiFi hardware 112 to the VDCI remote layer 204 of the removable media device 202 . First, a user may initiate a scan for WiFi access points, 401 . The application may receive a request to initiate a scan for an access point, 402, and send the request and data to the VDCI remote layer, 403. The VDCI remoting layer can capture the request to initiate scanning and create a TCP/IP wrapper around the request and data, 404 . The VDCI remote layer can then send the TCP/IP wrapper to the logical port allocated for the WiFi hardware, 405. The VDCI device daemon may receive TCP/IP wrappers, 406, from the logical port assigned to the WiFi hardware. The VDCI device daemon may strip the TCP/IP wrapper into a system command requesting to initiate a scan of access points and data, 407 . The VDCI device daemon can send commands to the WiFi hardware. The WiFi hardware can receive commands and issue commands, 408. The wireless device can then establish a connection to the access point, 409. The VDCI device daemon can then alert the VDCI remote layer: Connection succeeded, 410. The VDCI remote layer can receive the alert, 411, and can pass the alert to the user application, 412. The VDCI device daemon may use the controller on the end device to establish a bridge, 413 . The web browser may request web access through the bridge, 414. The bridge client may send the request to the server, 415. The bridge can forward the request to the wireless access point, 416. The wireless access point can send data to the network and receive data, 417. The bridge can receive data from the wireless access point, 418. Next, the web bridge can forward the data to the web browser, 419. The web browser can receive and process the data, and can display the data to the user, 420.

In other aspects, each mapped hardware device can be assigned to a logical port through which it communicates.

In one aspect, the VDCI device daemon 205 on the terminal device 201 can communicate the hardware configuration to the VDCI remote layer 204 on the removable media device 202 . VDIC remote layer 204 may assign a logical port to each hardware device reported by VDCI device daemon 205 . Logical ports may be enabled on eg 8889 and the port address may be decremented for each next hardware device present on terminal device 201 . The VDCI remote layer 204 may notify the VDCI device daemon 205 of the allocation of hardware device logical ports.

In another aspect, for example, port 8889 may be allocated to map WiFi hardware 112 from end device 201 to removable media device 202 . When the application 103 and the runtime environment 104 in the removable media device 202 request a WiFi function, such as scanning for access points, the VDCI remote layer 204 sends the command to the VDCI device background program 205 in the terminal device 201 through port 8889 . The VDCI device daemon 205 can then instruct the WiFi hardware 112 to scan and return a list of discovered access points over the same logical port 8889 . The VDCI remote layer 204 can send the list of access points to the calling application 103 or the runtime environment 104 .

According to one aspect, FIG. 5 illustrates the flow of information from the application 103 requesting access to the WiFi hardware 112 . In this regard, USB driver 501 may control USB hardware 502 on removable media device 202 . The radio handset 201 may also have a baseband processor 504 , a radio driver 505 for the radio hardware 109 , a WiFi driver 506 for the WiFi hardware 112 , and a USB driver 507 for the USB hardware 503 .

When the application 103 requests to establish a WiFi access point, the sequence is as follows. The application may request the WiFi hardware 112 with a scan command, as shown at 511 . The VDCI remote layer 204 can capture this request for WiFi hardware resources, and can encapsulate the command and data into a TCP/IP packet and send the packet to the communication link 203 , as shown at 552 . The removable media device 202 can regard the terminal device 201 as a CDC RNDIS/Ethernet device and can send the TCP/IP data packet to the specific port number corresponding to the WiFi hardware 112 of the terminal device 201, as shown in 553. The terminal device 201 may receive the packet data and may send the data packet to the VDCI device daemon 205 of the terminal device 201 , as shown at 554 . As shown at 555 , the VDCI device daemon 205 on the terminal device 201 can listen to TCP/IP on a specific port number corresponding to the WiFi hardware 112 . Once the data packet is received, the VDCI device daemon 205 may remove the encapsulation from the data packet. The VDCI device daemon 205 can check whether the command is directly supported by the WiFi hardware 205, and can modify the command to ensure compatibility with the supported hardware command set. Different hardware configurations can still work because the VDCI device daemon 205 can change the commands to conform to the supported command set. The VDCI device daemon 205 may pass the request to the WiFi hardware 112 . WiFi hardware 112 may receive the command and may execute the command, as shown at 556 . The results from the command may be returned to the calling application 103 through the reverse order of the information flow (eg, 556 back to 551).

In one aspect, the OpenMoke Neo Free Runner (New Free Runner) handheld can be used, with any hardware configuration possible. In a further aspect, handheld device applications and runtime environments may be removable and replaced with VDCI device daemon 205 . In other aspects, a Samsung S3C2443 development board can be used as the removable media device 202 . In one aspect, there may be no hardware device drivers present on the removable media device 202 . In a further aspect, the terminal device 201 may only have the VDCI device daemon 205 running on the baseband processor 504 .

Figure 6 shows a block diagram of a removable media device hardware design. In one aspect, removable media device 202 can be provided with processor 602, RAM 601 and ROM 603. In other aspects, the removable media device may have a communication link 203 to communicate with the end device 201 .

Linux can be selected as the open source operating system of the embodiment of the present invention. Other available operating systems may include, but are not limited to, or be limited to: Win CE, Symbian, or any other embedded operating system. On the other hand X Window can be included, but any other graphics system can be used. On the other hand Openmoko OM 2008 can be included as a runtime environment, but any other runtime environment can be used, including Android, QT, MontaVista, MatchBox or any other runtime environment.

The advantages of the embodiments of the present invention can be one or more of the following items: (1) cost separation between the terminal device and the removable media device; (2) can reduce the cost of product development, maintenance and enhancement, especially similar (3) Due to the use of virtualization technology, security certificates can be accelerated on security products; and (4) Since applications can be stored in removable media devices, distribution can be simplified.

While illustrative embodiments have been illustrated and described herein, it should be noted and understood by those skilled in the art that there are numerous modifications and other embodiments equivalent to what has been specifically illustrated and described. For example, the scope of the invention is not necessarily limited to performing the foregoing steps in the order discussed in all cases. Unless otherwise stated, the terms and expressions have been used herein for the purpose of description only and not for limitation. Accordingly, the invention is not to be limited by the specific illustrated and described embodiments (or the terms or expressions used to describe them), but only by the scope of the appended claims.

Claims (143)

1. A system for virtualizing a peripheral of a wireless device by a media device, comprising: Wireless equipment, including: processor; a memory coupled to the processor; a peripheral coupled to the processor; and A virtualized device controller interface program adapted to run on the memory and the processor, wherein the virtualized device controller interface program is adapted to communicate with the peripheral devices and media devices. 2. The system of claim 1, wherein the virtualized device controller interface program is adapted to communicate with the media device through a virtualized device controller interface remote layer on the media device. 3. The system of claim 1, wherein the virtualized device controller interface program is a daemon. 4. The system of claim 1, wherein the virtualized device controller interface program is adapted to communicate with the media device over a communication link. 5. The system of claim 4, wherein the communication link is a data bus. 6. The system of claim 4, wherein the communication link is wireless. 7. The system of claim 1, wherein the virtualized device controller interface program is adapted to communicate data related to one or more configuration settings of the peripheral device to a media device. 8. The system of claim 7, wherein the configuration settings include AND thresholds, minimum values, maximum values, upper and lower case characters, language, sensitivity, frequency, channel, frame rate, resolution, color, bit rate, One or more related settings of sample size, sample rate, ISO, and power. 9. The system of claim 1, wherein the virtualized device controller interface program is adapted to receive data from a media device for configuring one or more settings of the peripheral device. the 10. The system of claim 1, wherein the virtualized device controller interface program is adapted to receive data from a media device for execution on the peripheral device. 11. The system of claim 4, wherein the virtualized device controller interface program is adapted to communicate with the media device using a transport layer of the communication link. 12. The system of claim 4, wherein the base processor is adapted to communicate with an embedded operating system of a media device using a physical layer of the communication link. 13. The system of claim 4, wherein the communication link further comprises at least one of a network layer and a data link layer. 14. A system for virtualizing peripherals of a wireless device by a media device, the system comprising: Media equipment, including: first storage; a processor coupled to the first memory; and A virtualized device controller interface remote layer adapted to run on the processor and the first memory, wherein the virtualized device controller interface remote layer is adapted to communicate with peripheral devices of the wireless device. 15. The system of claim 14, wherein the media device is removably coupled to the wireless device. 16. The system of claim 14, wherein the media device is mechanically coupled to the wireless device. 17. The system of claim 14, wherein the media device is attached to a SIM, SAM, SD, microSD, or USB dongle form factor. 18. The system of claim 14, wherein the media device is a removable media card. 19. The system of claim 14, wherein the first memory is RAM. 20. The system of claim 19, wherein the media device includes a second memory, and wherein the second memory is a ROM. 21. The system of claim 14, wherein the virtualized device controller interface remote layer is adapted to communicate with a peripheral device of a wireless device via a communication link. 22. The system of claim 21, wherein the communication link is a data bus. 23. The system of claim 21, wherein the communication link is wireless. 24. The system of claim 14, wherein the processor is adapted to run an embedded operating system. 25. The system according to claim 24, wherein said embedded operating system is Linux, Win CE or Symbian. 26. The system of claim 14, wherein the processor is adapted to run an embedded graphics engine for providing a graphical user interface. 27. The system of claim 26, wherein the embedded graphics engine is X-Windows. 28. The system of claim 14, wherein the processor is adapted to run an embedded runtime environment. 29. The system of claim 28, wherein the runtime environment is MatchBox, Android, QT, MontaVista, or Openmoko. 30. The system of claim 14, wherein the virtualized device controller interface remote layer is adapted to communicate with a virtualized device controller interface program of a wireless device. 31. The system of claim 14, wherein the virtualized device controller interface remote layer is a daemon. 32. The system of claim 21, wherein the virtualized device controller interface remote layer is adapted to communicate with a peripheral device of a wireless device using a transport layer of the communication link. 33. The system of claim 21, wherein the embedded operating system is adapted to communicate with a base processor of a wireless device using a physical layer of the communication link. 34. The system of claim 21, wherein the communication link further comprises at least one of a network layer and a data link layer. 35. The system of claim 14, wherein the virtualized device controller interface remote layer is adapted to communicate with a peripheral device of a wireless device using a virtualized device controller interface protocol. the 36. The system of claim 14, wherein the virtualized device controller interface remote layer is adapted to communicate peripheral data for execution on a peripheral of the wireless device. 37. The system of claim 14, wherein the virtualized device controller interface remote layer is adapted to communicate data related to one or more peripheral settings of a peripheral of the wireless device to the wireless device. 38. The system of claim 37, wherein the peripheral settings include and threshold, minimum value, maximum value, upper and lower case characters, language, sensitivity, frequency, channel, frame rate, resolution, color, bit rate , sample size, sample rate, ISO, and power related to one or more settings. 39. The system of claim 14, wherein the virtualized device controller interface remote layer is adapted to receive data from the wireless device related to one or more configuration settings of peripheral devices of the wireless device. 40. The system of claim 39, wherein the configuration settings include AND thresholds, minimum values, maximum values, upper and lower case characters, language, sensitivity, frequency, channel, frame rate, resolution, color, bit rate, One or more related settings of sample size, sample rate, ISO, and power. 41. The system of claim 14, wherein the virtualized device controller interface remote layer is adapted to communicate with peripheral devices of the wireless device by transmitting wrapped data packets to the wireless device. 42. A system for operating peripherals of a wireless device by a media device, the system comprising: Wireless equipment, including: first processor; a first memory coupled to the first processor; a peripheral coupled to the first processor; and a virtualized device controller interface program adapted to run on said first memory and said first processor, wherein said virtualized device controller interface program is adapted to communicate with said peripheral device; and Media equipment, including: second memory; a second processor coupled to the second memory; and a virtualized device controller interface remote layer adapted to run on said second processor and second memory, wherein said virtualized device controller interface remote layer is adapted to communicate with said virtualized device control of said wireless device and the virtualized device controller interface program is adapted to communicate with the virtualized device controller interface remote layer of the media device. 43. The system of claim 42, wherein the virtualized device controller interface remote layer is a daemon. 44. The system of claim 42, wherein the virtualized device controller interface program is a daemon. 45. The system of claim 42, wherein the virtualized device controller interface program is adapted to communicate with the virtualized device controller interface remote layer over a communication link. 46. The system of claim 45, wherein the communication link is a data bus. 47. The system of claim 45, wherein the communication link is wireless. 48. The system of claim 42, wherein the virtualized device controller interface program is adapted to transmit data related to one or more configuration settings of the peripheral device to the virtualized device controller interface remote layer. 49. The system of claim 42, wherein the virtualized device controller interface remote layer is adapted to communicate data related to one or more settings of the peripheral device to the virtualized device controller interface program . 50. The system of claim 49, wherein the settings correspond to threshold, minimum, maximum, uppercase and lowercase characters, language, sensitivity, frequency, channel, frame rate, resolution, color, bitrate, samples One or more of size, sample rate, ISO, and power. 51. The system of claim 42, wherein the virtualized device controller interface remote layer is adapted to communicate data for execution on the peripheral device to the wireless device. 52. The system of claim 42, wherein the first memory is a buffer memory. 53. The system of claim 42, wherein the wireless device is a cellular telephone. the 54. The system of claim 53, wherein the cellular phone is an OpenMokoNeo FreeRunner. 55. The system of claim 42, wherein the peripheral device comprises a touch screen. 56. The system of claim 42, wherein the first processor is a baseband processor. 57. The system of claim 42, wherein the wireless device further comprises one or more peripheral devices adapted to run on the first processor. 58. The system of claim 57, wherein at least one of the peripheral devices is radio hardware for receiving and transmitting radio signals. 59. The system of claim 58, wherein the radio hardware is adapted to receive or transmit one or more of CDMA, GPRS, GSM, Bluetooth and WiFi signals. 60. The system of claim 57, wherein at least one of the peripheral devices is adapted to receive input from a user. 61. The system of claim 60, wherein the input represents one or more commands for controlling the peripheral device of a wireless device. 62. The system of claim 57, wherein at least one of the peripheral devices includes a keypad, joystick, buttons, keyboard, Bluetooth, GPS, camera, or trackball. 63. The system of claim 57, wherein at least one of the peripheral devices includes an audio codec. 64. The system of claim 57, wherein at least one of the peripheral devices includes a wireless network adapter. 65. The system of claim 42, wherein the wireless device further comprises a hardware configuration module for storing data related to peripheral device settings for the peripheral device. 66. The system of claim 42, wherein the media device is removably coupled to a wireless device. 67. The system of claim 42, wherein the media device is mechanically coupled with a wireless device. 68. The system of claim 42, wherein the media device is attached to a SIM, SAM, SD, microSD, or USB dongle form factor. the 69. The system of claim 42, wherein the media device is a removable media card. 70. The system of claim 42, wherein the second memory is RAM. 71. The system of claim 70, wherein the media device includes a third memory, and wherein the third memory is a ROM. 72. The system of claim 42, wherein the second processor is adapted to run an embedded operating system. 73. The system of claim 72, wherein the embedded operating system is Linux, Win CE or Symbian. 74. The system of claim 42, wherein the second processor is adapted to run an embedded graphics engine for providing a graphical user interface. 75. The system of claim 74, wherein the embedded graphics engine is X-Windows. 76. The system of claim 42, wherein the second processor is adapted to run an embedded runtime environment. 77. The system of claim 76, wherein the runtime environment is MatchBox, Android, QT, MontaVista, or Openmoko. 78. The system of claim 42, wherein the virtualized device controller interface remote layer is adapted to communicate with the virtualized device controller interface program using an application layer protocol. 79. The system of claim 42, wherein the virtualized device controller interface remote layer is adapted to communicate with the virtualized device controller interface program using a virtualized device controller interface protocol. 80. The system of claim 42, wherein the virtualization device controller interface remote layer is adapted to communicate with the virtualization device controller by passing wrapped packets to the virtualization device controller interface program Interface program communication. 81. The system of claim 45, wherein the virtualized device controller interface remote layer is adapted to communicate with a peripheral device of a wireless device using a transport layer of the communication link. 82. The system of claim 45, wherein the embedded operating system is adapted to communicate with the base processor of the wireless device using the physical layer of the communication link. 83. The system of claim 45, wherein the communication link further comprises at least one of a network layer and a data link layer. 84. The system of claim 45, wherein the virtualized device controller interface program is adapted to communicate with the media device using a transport layer of the communication link. 85. The system of claim 45, wherein the base processor is adapted to communicate with an embedded operating system of a media device using a physical layer of the communication link. 86. A system for operating peripherals of a wireless device by a media device, the system comprising: Wireless equipment, including: the device used for the treatment; storage means for coupling with said means for processing; means for inputting data coupled with said storage device; and means for unpacking hardware commands adapted to run on said means for storing and said means for processing, wherein said means for unpacking hardware commands is adapted to communicate with said media device and said means for processing Communicate with the device that inputs the data. 87. A system for operating peripherals of a wireless device by a media device, the system comprising: Media equipment, including: the device used for the treatment; storage means for coupling with said means for processing; and Means for emulating a peripheral device adapted to run on said means for storing and said means for processing, wherein said means for emulating a peripheral device is adapted to communicate with a peripheral device of a wireless device. 88. The system of claim 87, wherein the media device is removably coupled to the wireless device. 89. The system of claim 87, wherein the media device is mechanically coupled to a wireless device. 90. The system of claim 87, wherein the media device is attached to a SIM, SAM, SD, microSD, or USB dongle form factor. the 91. A system for operating peripherals of a wireless device by a media device, the system comprising: Wireless equipment, including: a first means for processing; first storage means for coupling with said first means for processing; means for inputting data coupled to said first processing means; and means for unpacking hardware commands adapted to run on said first storage means and said first processing means, wherein said means for unpacking hardware commands is adapted to communicate with said means for inputting data ; Media equipment, including: a second device for processing; second storage means for coupling with said second means for processing; and means for simulating said means for inputting data adapted to run on said second storage means and said second processing means, wherein said means for unlocking hardware commands of a wireless device is adapted to interact with a media device The means for emulating is in communication with the means for emulating, and the means for emulating is adapted to communicate with the means for deciphering hardware commands. 92. The system of claim 91, wherein the media device is removably coupled to the wireless device. 93. The system of claim 91, wherein the media device is mechanically coupled to the wireless device. 94. The system of claim 91, wherein the media device is attached to a SIM, SAM, SD, microSD, or USB dongle form factor. 95. A method of virtualizing a peripheral of a wireless device by a media device, comprising: a. The hardware configuration of the wireless device is evaluated by the wireless device; b. transferring said hardware configuration of a wireless device to a media device from said wireless device; c. Mapping the processor of the media device through the virtualization device controller interface program on the wireless device; d. receiving at the wireless device from the media device a wrapped packet containing the peripheral device command; e. unpacking said wrapped packet containing peripheral device commands at the wireless device; f. Executing said peripheral device command by the wireless device. 96. The method of claim 95, further comprising the step of establishing, by the wireless device, an access point connection. 97. The method of claim 95, further comprising the step of said virtualized device controller interface program communicating with a virtualized device controller interface remote layer of a media device. 98. The method of claim 95, wherein the wrapped data packet is received from a virtualized device controller interface remote layer of a media device. 99. The method of claim 95, further comprising the step of running a daemon on said virtualized device controller interface program. 100. The method of claim 97, wherein the communicating step further comprises communicating with the virtualized device controller interface remote layer over a communication link. 101. The method of claim 100, wherein the communicating occurs through a transport layer of the communication link. 102. The method of claim 100, wherein the communication link is a data bus. 103. The method of claim 100, wherein the communication link is wireless. 104. The method of claim 95, further comprising the step of transmitting data related to one or more configuration settings of the peripheral device from the wireless device to the media device. 105. The method of claim 95, wherein said performing step is performed by a peripheral device of the wireless device. 106. The method of claim 95, further comprising the step of transmitting command results from the wireless device. 107. A method of virtualizing a peripheral of a wireless device by a media device, comprising: a. Emulate the hardware interface used to communicate with the runtime environment on the media device; b. receiving the hardware configuration of the wireless device on the media device; c. The peripheral device of the wireless device is mapped to the emulated hardware interface by the remote layer of the virtualized device controller interface on the media device, so that the media device operates as if it is directly connected to the peripheral device; d. Transmitting logical ports for peripherals on the wireless device from the media device; e. packaging the peripheral device command into a data packet by the remote layer of the virtualization device controller interface on the media device; f. transmitting, by said virtualized device controller interface remote layer on a media device, said wrapped packet containing said peripheral device command to a wireless device; and g. The command is executed by the media device as if the peripheral device of the wireless device is directly connected to the media device. 108. The method of claim 107, wherein the media device is removably coupled to the wireless device. 109. The method of claim 107, wherein the media device is mechanically coupled to the wireless device. 110. The method of claim 107, wherein the media device is attached to a SIM, SAM, SD, microSD, or USB dongle form factor. 111. The method of claim 107, wherein the media device is a removable media card. 112. The method of claim 107, further comprising the step of communicating with a peripheral device of the wireless device via a communication link. 113. The method of claim 112, wherein the communicating occurs through a transport layer of the communication link. 114. The method of claim 112, wherein the communicating step further comprises communicating with a virtualized device controller interface program of a wireless device using the virtualized device controller interface remote layer. 115. The method of claim 112, wherein the communication link is a data bus. 116. The method of claim 112, wherein the communication link is wireless. 117. The method of claim 107, further comprising the step of running a daemon on the virtualized device controller interface remote layer. 118. The method of claim 107, further comprising the step of receiving, by the media device, a result of the command. 119. The method of claim 107, further comprising the step of communicating from the media device to the wireless device one or more peripheral device settings for peripheral devices of the wireless device. the 120. The method of claim 119, wherein the peripheral settings include and threshold, minimum, maximum, uppercase and lowercase characters, language, sensitivity, frequency, channel, frame rate, resolution, color, bitrate , sample size, sample rate, ISO, and power related to one or more settings. 121. The method of claim 107, further comprising the step of transferring peripheral device data executing on the peripheral device from the media device to the wireless device. 122. The method of claim 107, wherein the peripheral command comprises one of querying configurable and non-configurable attributes of a peripheral on the wireless device, changing a configuration setting for a peripheral, and detecting a configuration setting of a peripheral or more. 123. The method of claim 107, wherein the performing steps are performed by a processor of the media device. 124. A method of virtualizing a peripheral of a wireless device by a media device, comprising: a. On the media device, emulate the hardware interface used to communicate with the runtime environment; b. Evaluating the hardware configuration of the wireless device by the wireless device; c. communicating said hardware configuration of the wireless device from the wireless device to the media device; d. receiving a hardware configuration of the wireless device at the media device; transmitting said hardware configuration of the wireless device from the wireless device to the media device; e. mapping the peripherals of the wireless device to the emulated hardware interface by the remote layer of the virtualized device controller interface of the media device, so that the media device operates as if directly connected to the peripheral; f. Transmitting logical ports for peripherals on the wireless device from the media device; g. The processor of the media device is mapped to the peripheral device by the virtualized device controller interface program of the wireless device, so that the peripheral device operates as if it is directly connected to the processor; h. packaging the peripheral device command into a data packet by the remote layer of the virtualization device controller interface on the media device; i. transmitting, by the VDCI remote layer, the wrapped packet containing peripheral device commands to the VDCI program of the wireless device; j. receiving the packaged packet containing peripheral commands from the virtualized device controller interface remote layer by the virtualized device controller interface program; k. unpacking said wrapped packet containing peripheral device commands at the wireless device; and l. Executing said peripheral command by the wireless device. 125. The method of claim 124, further comprising the step of running a daemon on the virtualized device controller interface remote layer. 126. The method of claim 124, further comprising the step of running a daemon on said virtualized device controller interface program. 127. The method of claim 124, wherein the wrapped peripheral command is sent from the virtualized device controller interface remote layer to the virtualized device controller interface program over a communication link. 128. The method of claim 127, wherein the communicating occurs through a transport layer of the communication link. 129. The method of claim 127, wherein the communication link is a data bus. 130. The method of claim 127, wherein the communication link is wireless. 131. The method of claim 124, wherein the media device is removably coupled to a wireless device. 132. The method of claim 124, wherein the media device is mechanically coupled to a wireless device. 133. The method of claim 124, wherein the media device is attached to a SIM, SAM, SD, microSD, or USB dongle form factor. 134. The method of claim 124, wherein the media device is a removable media card. 135. The method of claim 124, further comprising the step of transmitting data related to one or more configuration settings of the peripheral device from the wireless device to the media device. 136. The method of claim 124, further comprising the step of communicating from the media device to the wireless device one or more peripheral device settings for peripheral devices of the wireless device. 137. The method of claim 136, wherein the peripheral settings include and threshold, minimum value, maximum value, upper and lower case characters, language, sensitivity, frequency, channel, frame rate, resolution, color, bit rate , sample size, sample rate, ISO, and power related to one or more settings. 138. The method of claim 124, further comprising the step of transferring peripheral device data executing on the peripheral device from the media device to the wireless device. 139. The method of claim 124, wherein the peripheral command comprises one of querying configurable and non-configurable properties of a peripheral on the wireless device, changing a configuration setting for a peripheral, and detecting a configuration setting of a peripheral or more. 140. The method of claim 124, wherein the performing steps are performed by a peripheral device of the wireless device. 141. The method of claim 124, wherein said executing step further comprises the step of executing said peripheral device command on the media device as if the peripheral device of the wireless device were directly connected to the media device. 142. The method of claim 124, further comprising the step of receiving, by the media device, a result of the command. 143. The method of claim 124, further comprising the step of establishing, by the wireless device, an access point connection. the

Images