CROSS REFERENCE TO RELATED APPLICATIONS 
       [0001]    The present application is related to and claims priority of copending U.S. provisional patent application (“Copending Provisional application”), Ser. No. 61/991,619, entitled “Mobile Computing Resource,” filed on May 12, 2014. The disclosure of the Copending Provisional application is hereby incorporated by reference herein in its entirety. The present application is also related to (a) U.S. patent application Ser. No. 13/168,666, filed on Jun. 24, 2011, and (b) U.S. Pat. No. 8,432,362, issued Apr. 30, 2013. The disclosures of the related U.S. patent application and U.S. patent are both hereby incorporated by reference herein. 
     
    
     BACKGROUND OF THE INVENTION 
       [0002]    1. Field of the Invention 
         [0003]    The present invention relates to smart connected devices and, more particularly, to providing handheld mobile computing resources to smart connected devices. 
         [0004]    2. Discussion of the Related Art 
         [0005]    There are many problems with current smart connected devices. For example, these devices each belong to a different but distinct smartphone, tablet, notebook, and desktop function. These devices notably lack flexibility, are unable to upgrade to the latest, more powerful processors, are not powerful when provided as desirable, pocket-sized thin clients, and do not provide sufficient cost-effectiveness to customers. Basically, a consumer needs a different device for each of the smartphone, tablet, notebook and desktop function, which is costly and not eco-friendly. 
         [0006]    To support different and more powerful computing resource needs or functions, cloud computing services, remote desktops, virtual desktops, and remote displays are services that have been introduced. These devices, which provide on-demand computing resources, each have its own unique advantages and disadvantages. One common disadvantage among these approaches is that the on-demand computing resource is located at a remote site, and is most likely shared among multiple users. As a result, these resources are inconvenient and largely insecure. For example, Microsoft&#39;s Remote Desktop environments force users to use a server computer in a remote fixed location, so that the user is not able to restart the remote server desktop, in the event that the server computer goes down. In the same manner, when a remote desktop application shuts down on a client device, the action only disconnects the remote desktop application with the remote server computer, but leaves the remote computer still powered. The remote server computer typically does not provide an easy way to shut down or restart the remote computer. In addition, enterprise virtual desktops and cloud computing services are typically complex and costly. Such services require IT professionals to manage and maintain, so that their services are often unaffordable by most consumers. A remote display device, such as Google&#39;s thumb-size Chromecast device, provides a remote display function at a client device, such as a high-definition television set (HDTV). However, the remote display device is required to be physically connected to the client device, which is typically not battery-powered for mobility. 
       SUMMARY OF THE INVENTION 
       [0007]    In accordance with one embodiment of the present invention, there is provided, a mobile computing resource without a built-in display or peripheral, so as to achieve low cost, portability, and flexibility. The mobile resource unit includes a computing unit having a motherboard, a central processing unit (CPU), a read-only memory (ROM), a random access memory (RAM), a basic input/output system (BIOS), and an operating system (OS) that is capable of executing computer processes. A wireless module may be provided in the mobile computing resource to provide wireless communication services. In one embodiment, a power source (e.g., a rechargeable battery pack) provides power to the computing unit, together with a power switch which allows the mobile resource unit to be powered on or powered off. 
         [0008]    According to one embodiment, the computing unit of the mobile computing resource may be pre-installed with an OS and host or client applications for remote display. The mobile computing resource communicates with a client device to support the compatible client applications for remote display. Thus, the mobile computing resource provides additional computing power to a client device (e.g., a smart connected device), and displays its content on the client device remotely. In some embodiments, the mobile computing resource provides a higher power processor, provides functions needed by the client device—thereby reducing the cost of the client&#39;s display device—and shares the display and other peripherals in the client devices. Further, the mobile computing resource may also provide a backup battery function to the client device through a direct connection or through wirelessly charging. 
         [0009]    The present invention thus provides the advantages of a flexible, low-cost mobile computing resource without incurring the costs of a display and other peripherals. Such a mobile computing resource may be handheld, and of a size capable of being carried in a shirt pocket, thereby enjoying the great mobility that cannot be achieved in a conventional server computer. The mobile computing resource may work with any type of client devices that support compatible server or client function to form a “mobile local cloud” through a local network connection or a direct connection. The mobile computing resource is a portable high-power computing resource to the paired simple client device available whenever needed, especially for such applications as Augmented Reality display and gesture operations. The mobile computing resource shares a power source with the client device, and may provide a backup battery charging function (through an optional rechargeable battery) to the client device. 
         [0010]    In some embodiments, the mobile computing resource may provide a next-generation or a higher power CPU or OS to the client device, without requiring upgrade to the client device. This is achieved when the mobile computing resource includes a more powerful CPU than the client device&#39;s CPU, or when the OS in the mobile computing resource (e.g., Windows) is considered more powerful than the OS (e.g., Android or an Apple-based OS) in the smartphone or tablet client device. The mobile computing resource and the client device together becomes a new hybrid entity. The mobile computing resource may also provide a later or more advanced version of the OS that is in the client device. 
         [0011]    The present invention is better understood upon consideration of the detailed description below in conjunction with the accompanying drawings. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0012]      FIG. 1  shows mobile computing resource  100  directly connected to client device  200 , in accordance with one embodiment of the present invention. 
           [0013]      FIG. 2  shows mobile computing resource  100  connected to client device  200  over a computer or communication network, in one embodiment of the present invention. 
           [0014]      FIG. 3  is a top view of mobile computing resource  100  which may include a swappable computing unit  110 , according to one embodiment of the present invention. 
           [0015]      FIG. 4   a  is a top view of mobile computing resource  100  having integrated input unit  190 , and client holder  195  for accommodating a client device (e.g., client device  200 ) in an “open state”, according to one embodiment of the present invention. 
           [0016]      FIG. 4   b  is a cross section view of mobile computing resource  100  having integrated input unit  190  and client holder  195  for accommodating client device  200 , in accordance with one embodiment of the present invention. 
           [0017]      FIG. 5  illustrates one application of mobile computing resource  100 , in accordance with one embodiment of the present invention. 
           [0018]      FIG. 6  shows multiple mobile computing resources  100   a - 100   c  connected to client device  200  through data hub  400 , according to one embodiment of the present invention. 
           [0019]      FIG. 7  is a block diagram showing functional blocks in mobile computing resource  100  and connected client device  200 , according to one embodiment of the present invention. 
           [0020]      FIG. 8  is a flow chart illustrating an operational flow between client device  200  and mobile computing resource  100 , in accordance with one embodiment of the present invention. 
       
    
    
       [0021]    For purposes of clarity and brevity, like elements and components bear the same designations and numbering throughout the Figures. 
       DESCRIPTION OF THE PREFERRED EMBODIMENT 
       [0022]      FIG. 1  shows mobile computing resource  100  directly connected to client device  200 , in accordance with one embodiment of the present invention. As shown in  FIG. 1 , mobile computing resource  100  is a simple device without a display, optional battery pack  120 , or peripherals. Mobile computing resource  100  may be a handheld device which includes computing unit  110  and a motherboard containing its principal components, e.g., a CPU, a graphical processing unit (GPU), ROM, RAM, a storage unit, wireless module  115 , firmware, and an operating system. In  FIG. 1 , computing unit  110  of mobile computing resource  100  is paired with client device  200  (e.g., a laptop computer) directly through a cable with USB  3 . 1  electrical connectors. Such a connection may provide a power interface, a data interface, a video interface, and a control interface. The data interface may include an input interface and an output interface sharing the data interface. In other embodiments, computing unit  110  of mobile computing resource  100  may connect with client device  200  over a wired network or wirelessly using a wireless interface (e.g., Wi-Fi-direct, i.e., without a wireless access point). 
         [0023]    In one embodiment, computing unit  110  of mobile computing resource  100  and client device  200  follow pre-defined roles for each other based on the other device&#39;s resource, content, and services requirements. In one embodiment, client device  200  provides a power source to mobile computing resource  100 , when mobile computing resource  100  is not equipped with a rechargeable battery pack. Computing unit  110  may take control of client device  200 &#39;s peripheral interfaces, providing output data over a data interface or a video interface to client device  200 &#39;s output device (e.g., electronic visual display  220 ) and receiving input data from client device  200 &#39;s input device (e.g., keyboard  225 ) over the data interface or the video interface, thereby integrating with client device  200  with mobile computing resource  100  to form an integrated computing unit. For example, suppose client device  200  is a laptop computer known as a Chromebook, and computing unit  110  runs the Microsoft Windows 8 pocket PC. As shown in  FIG. 1 , client device  200  provides a power source to mobile computing resource  100  through battery  230 . By coupling with mobile computing resource  100 , client device  200  becomes a “new” high-power Windows 8 laptop computer, with mobile computing resource  100  taking control over electronic visual display  220  and keyboard  225 , mouse, touchpad  226 , and a touch screen (for receiving input data). 
         [0024]    In one embodiment, mobile computing resource  100  has a power module that supplies power to computing unit  110 . Alternatively, client device  200  may feed electrical power to mobile computing resource  100  through USB  3 . 1  electrical connector  160 . In another embodiment, the power module can be optional rechargeable battery pack  120 , or a DC power source. In another embodiment, optional AC DC power jack  140  is provided for charging battery pack  120 . In one embodiment, power button  130  allows mobile computing resource  100  to be powered on or powered off. In one embodiment, mobile computing resource  100  can charge client device  200  through an electrical connector when optional rechargeable battery pack  120  is present. 
         [0025]    In one embodiment, computing unit  110  connects and interacts with client device  200  through a wired network or wirelessly. The communication link can be achieved through any of the following protocols: network peer-to-peer, network client and server, network master and slave, remote desktop, remote procedure call, package protocol or communication models, and other applications. Through such a connection, mobile computing resource  100  takes control over electronic visual display  220  and keyboard  225 , mouse, touchpad  226 , and a touch screen (for receiving input data). 
         [0026]    In one embodiment, computing unit  110  may run host or client applications, or master or slave application for remote display. Computing unit  110  and its firewall may be opened to client device  200  to support compatible client application for remote display. In one embodiment, client device  200  runs a compatible client side application. In one embodiment, client device  200  displays the contents created by mobile computing resource  100  (e.g., in conjunction with executing one of its application programs) In one embodiment, optional display connector  150  (e.g., such as HDMI or DisplayPort) allows mobile computing resource  100  to connect an external display, when desired. In one embodiment, a wireless battery charger may be provided to charge battery pack  120 . In one embodiment, an external battery charging station is provided to charge removable battery pack  120 . 
         [0027]      FIG. 2  shows mobile computing resource  100  connected to client device  200  over a communication computer network, in one embodiment of the present invention. In one implementation, mobile computing resource  100  runs the Microsoft Windows 8 operation system installed on it, along with a Microsoft Remote Desktop server or host application. To provide an access mechanism, mobile computing resource  100  has been assigned a unique name as a server, and has registered therein one or more user accounts each accessible through a username and a password. When powered on and connected to a public communication or computer network, mobile computing resource  100  connects to a router through wireless module  115  and becomes accessible through the communication or computer network. At that point, client device  200  (e.g., an Android- or Apple-based smartphone or tablet device) which has a Microsoft Remote Desktop client application installed on it, may connect to mobile computing resource  100  though client wireless module  215 . Client device  200  runs the Microsoft Remote Desktop client application to connect to mobile computing resource  100 , using its assigned device name, and the user name and password of one of the registered accounts. Once connected, the user can review the computing resources on mobile computing resource  100  using electronic visual display  220 , and may control mobile computing resource  100  from client device  200 . In one embodiment, client device  200  displays the contents created by mobile computing resource  100  (e.g., in conjunction with executing one of its application programs) By this process, client device  200  accesses to the computing resources of a powerful Windows 8 device. The user may enjoy both the advantages of both Windows and Android systems by connecting client device  200  to the pocket-size mobile computing resource  100 . 
         [0028]    In one embodiment, a 3G/4G communication service-enabled client device  200  may serve as a mobile hotspot. In one implementation, mobile computing resource  100  runs Microsoft Windows 8 operation system and Microsoft Remote Desktop server or host application, and client device  200  runs a Microsoft remote desktop client application. Client device  200  and mobile computing resource  100  may be connected in the manner described above, using mobile computing resource  100 &#39;s assigned server name, together with access enabled through the registered user account credentials. 
         [0029]    Alternatively, mobile computing resource  100  may include a built-in display connector  150 , which allows a user to connect an external display and an input device. Using this arrangement, a user may configure mobile computing resource  100  (e.g., assigning a device name, and setting user accounts accessible using a user name and a password). Mobile computing resource  100  may be configured to connect to a private computer or communication network (e.g., using a secure password, if required). When connected to the private communication or computer network, one or more client devices (e.g., client device  200 ) can access the computing resources of mobile computing resource  100 . 
         [0030]    In yet another embodiment, mobile computing resource  100  runs a UNIX-based operating system (e.g., Linux) and a UNIX-based remote display server. A client device (e.g., Client device  200 ) having compatible remote display client software installed may connect to mobile computing resource  100 , based on the access mechanism described above. 
         [0031]      FIG. 3  is a top view of mobile computing resource  100  which may include a swappable computing unit  110 , according to one embodiment of the present invention. As shown in  FIG. 3 , computing unit  110  and wireless module  115  can be a swappable, handheld-sized modular pocket PC that can be accepted into a customized slot of mobile computing resource  100 . In one embodiment, the modular pocket PC of computing unit  110  is provided a connector (e.g., a female connector) designed to be coupled to a corresponding connector (e.g., male connector) provided in the housing of mobile computing resource  100 . The pocket PC of computing unit  110  can be detached from mobile computing resource  100 . In one embodiment, the pocket PC of computing unit  110  is powered by mobile computing resource  100  when computing unit  110  is connected by the male and female connectors. In that configuration, mobile computing resource  100  is available for connection by one or more client devices (e.g., client device  200 ). 
         [0032]      FIG. 4   a  is a top view of mobile computing resource  100  having integrated input unit  190 , and client holder  195  for accommodating a client device (e.g., client device  200 ) in an “open state”, according to one embodiment of the present invention. The “open state” refers to the state when integrated input unit  190  is slid out of the housing of mobile computing resource  100  and becomes visible by the user. In contrast, the “close state” refers to the state in which integrated input unit  190  is slid inside of the housing of mobile computing resource  100 , being covered by client holder  195 . In one embodiment, in the close state, client holder  195  hides integrated input unit  190  entirely. In one embodiment, the open state is entered when client holder  195  slides up to expose integrated input unit  190  to allow a user to enter commands. In one embodiment, mobile computing resource  100  connects to client device  200  wirelessly. Integrated input unit  190  may connect to client device  200  wirelessly through, for example, Bluetooth or Wi-Fi protocols. When operating in the wireless mode, client holder  195  may be detached from the housing of mobile computing resource  100 . In one embodiment, client device  200  needs not be attached to client holder  195  while operating in the wireless mode. 
         [0033]      FIG. 4   b  is a cross section view of mobile computing resource  100  having integrated input unit  190  and client holder  195  for accommodating client device  200 , in accordance with one embodiment of the present invention.  FIG. 4   b  shows mobile computing resource  100  in the close state. In one implementation, the housing of mobile computing resource  100  is integrated with a battery and serves as a protective housing for computing unit  110 . In one implementation, integrated input unit  190  is provided on one side of mobile computing resource  100  and may include, for example, a keyboard and a touchpad. In one embodiment, integrated input unit  190  may include a set of gaming control buttons and a joystick. In one embodiment, integrated input unit  190  includes a touch-enabled screen or pad. In one embodiment, client holder  195  includes client connector  196  which mates with a corresponding connector on client device  200 , so as to allow a direct communication link to be established by the connectors. In one embodiment, client connector  196  implements power pins and supports at least one of following standard protocols or interfaces: USB, HDMI, DisplayPort, Thunderbolt, I2C and other industrial communication standards. 
         [0034]      FIG. 5  illustrates one application of mobile computing resource  100 , in accordance with one embodiment of the present invention. As shown in  FIG. 5 , mobile computing resource  100  is mounted on actuator  300  (e.g., a game controller) of client device  200  through a clip or hook provided on the housing of mobile computing resource  100 . In one implementation, mobile computing resource  100  may run the Windows OS, while client device  200  (e.g., a game console) may run the Android OS. Using any one of the access mechanisms described above, mobile computing resource  100  is connected to client device  200 . In that configuration, a user may run a game on the Windows OS on mobile computing resource  100 , while displaying graphical images on client device  200 &#39;s display and interacting with the game through client device  200 &#39;s actuator  300 . In one implementation, mobile computing resource  100  may be provided optional integrated input unit  190  to allow a user to input data, when needed. In one embodiment, actuator  300  includes a slot to accommodate mobile computing resource  100  (e.g., modular pocket PC of  FIG. 3 ). In one embodiment, mobile computing resource  100  is embedded in actuator  300 . In one embodiment, actuator  300  may be implemented in the form of a keyboard, a stationary stand, an electronic toy, an electronic stuffing animal, a camera, an electronic flying device, or any other suitable device. 
         [0035]      FIG. 6  shows multiple mobile computing resources  100   a - 100   c  connected to client device  200  through data hub  400 , according to one embodiment of the present invention. Each of mobile computing resources  100   a - 100   c , data hub  400 , and client device  200  may use the same type of connector for carrying data, video, power and optionally other control interfaces. Data hub  400  has multiple ports for connecting multiple mobile computing resources (e.g., mobile computing resources  100   a - 100   c ), and a host port for connecting client device  200 . In this configuration, client device  200  acts as a host system to access each of mobile computing resources  100   a - 100   c  through its control unit  201 . Mobile computing resources  100   a - 100   c  may have, however, different processors and different operating systems. In one implementation, data hub  400  may be a USB 3.1 hub, which delivers up to 5 A and 100 W power to the connected devices. In one embodiment, data hub  400  repackages the audio, video and data packages from each of mobile computing resources  100   a - 100   c  into the same selected data format prior to forwarding to client data hub  213  of client device  200  for processing. A USB  3 . 1  application may be provided on client device  200  to allow a user to display information regarding each of connected mobile computing resources  100   a - 100   c , and to access to any of mobile computing resources  100   a - 100   c  at will. In the configuration of  FIG. 6 , client device  200  may be, for example, a Google Chrome laptop, and mobile computing resources  100   a - 100   c  may run, for example, Windows 8, Android, and iOS operating systems, respectively. According to one embodiment of the present invention, takeover control module in client device  200  allows any of mobile computing resource  100   a - 100   c  to control operations in client device  200 . In one implementation, a virtue KVM switch implements takeover control module  225 , so as to allow each of connected mobile computing resources  100   a - 100   c , when engaged, to access a keyboard, a video display, and a mouse of client device  200 . In this manner, for example, client device  200  can become a Windows 8 laptop when the user engages mobile computing resource  100   a  through the virtue KVM switch. Mobile computing resource  100   a  may then output to the LCD display of client device  200 , and receives input commands from the keyboard and a mouse of client device  200 . In the same manner, client device  200  can become an Android laptop or an Apple MacBook by the user switching to mobile computing resources  100   b  and  100   c , respectively. The virtue KVM switch of the present invention redirects video and data packages to a designated mobile computing resource without incurring additional hardware cost. 
         [0036]      FIG. 7  is a block diagram showing functional blocks in mobile computing resource  100  and connected client device  200 , according to one embodiment of the present invention. As shown in  FIG. 7 , mobile computing resource  100  and client device  200  communicate over data, audio and video, power and optional control interfaces. These interfaces may be carried on one or more connectors at each device. In one implementation, mobile computing resource  100  may be a Microsoft Windows device, having computing unit  110  which includes data storage module  103 . USB data control module  113 , display control module  114  and control module  101  (e.g., an Intel multicore x86 processor). Control module  101  may be provided a program memory in which executable instructions may be stored. USB data control module  113  controls data ports and interacts with client data hub  213  through data interface  163 , display control module  114  controls display ports and interacts with client display control module  214  through audio and video interfaces  164 , and power bus  112  supplies power to all components in mobile computing resource  100 . Power bus  112  may also supply power to or may receive power from client device  200  through power interface  162 , when required. Computing unit  110  may also use wireless module  107  to send and receive data over an external communication or computer network. Optional power module  102  may be provided a rechargeable battery and may be connected to power jack  102   b . Mobile computing resource  100  may alternatively initiate handshaking with client device  200  through data interface  163  and control interface  161 . 
         [0037]    Alternatively, takeover control module  225  may be implemented by an internal physical KVM switch, which may be controlled by an application program or its firmware. For example, a commercial video controller that supports multiple video streams can be used to provide a video KVM switch which directs any input stream, whether originating from mobile computing resource  100  or client device  200 , to display control module  214  and video controller output display interface  214   a.    
         [0038]    On the side of client device  200 , control unit  201  may be implemented by a simple processor (e.g., an ARM processor), which may have an embedded program memory from which to execute commands. Control unit  201  coordinates with mobile computing resource  100  and control internal operations in client device  200 . As shown in  FIG. 6 , client device  200  includes data storage module  203 , USB data control module  213 , which controls data ports  213   a  and interacts with resource&#39;s data control  113  through data interface  263 , and display control module  214 , which controls display ports. In other embodiments, client device  200  may also include a display and touch panel module (not shown), and an audio module to control a microphone and a speaker. Client display control module  214  interacts with mobile computing resource  100 &#39;s display control module  114  through audio and video interfaces  264 . Client device  200  may also include power supply module  202 , which is connected to power jack  202   b  and supplies power over power bus  212  to all components. A battery in client device  200  may be used to provide power to mobile computing resource  100  over power interface  262 . Power interface  262  interacts with corresponding power interface  162  to supply power from or to provide power to mobile computing resource  100 , when required. Wireless module  207  may be used to send and receive data over an external communication or computer network. 
         [0039]    In one embodiment, mobile computing resource  100  may include power module  102  and a rechargeable battery (not shown), which may be charged or discharged inductively through charging coil  102   a . Mobile computing resource  100  may thus serves as a base charging station. Client device  200 , which may also include power supply module  202  and a rechargeable battery, may be charged or discharged through client charging coil  202   a . When power level is low at client device  200 , a user may place mobile computing resource  100 —in particular, charging coil  102   a —over charging coil  202   a  of client device  200 . Mobile computing resource  100  may therefore charge the rechargeable battery in client device  200  by electromagnetic induction. 
         [0040]      FIG. 8  is a flow chart illustrating an operational flow between client device  200  and mobile computing resource  100  (“the devices”), in accordance with one embodiment of the present invention. As shown in  FIG. 8 , at step  501 , the devices each launch a pre-installed application to initiate connection via a predetermined handshaking protocol through their respective control interface  161  and client control interface  261 . (Alternatively, connection in step  501  may be effectuated wirelessly using wireless module  107  and client wireless module  207 , as described above in conjunction with  FIG. 7 ). The devices may assume any host/client, master/slave, or server/client relationship, as required. At step  502 , the devices exchange platform and locale information so as to allow data to be exchanged over proper format. In heterogeneous computer systems, at step  509 , the devices may need to negotiate a common format for data exchange. The locale information may be a set of parameters that define the user&#39;s language, country and any special variant preferences that the user desires for the user interface. For example, a locale identifier may include a language identifier and a region identifier. In one embodiment, mobile computing resource  100  may be set up for the U.S. English language, while client device  200  may be set up for the Chinese language from Taiwan. Similarly, mobile computing resource  100  may be set up for handling ASCII codepage, while client device  200  may be set up for handling Big  5  codepage. At step  509 , the devices may agree on a Unicode codepage to serve as a bridge for the communication. The devices then encode and decode their codepages into Unicode accordingly. 
         [0041]    Once a proper communication protocol is settled upon, at step  503 , the devices agree on a takeover mechanism. For example, in one embodiment, an internal physical KVM switch is available. At step  504 , client device  200  selects an audio/video physical port on the KVM switch to allow mobile computing resource  100  to use the assigned port to control display control module  214  through video interface  264 . To take over data control, client device  200  switches data hub  213  to a predefined port that connects data interface  263 , so as to allow mobile computing resource  100  to takeover data hub  213 . Once a proper switching is done, at step  506 , mobile computing resource  100  takes over display interface  214   a  and data I/O interface  213   a  from client device  200 . In one embodiment, at step  507 , client device  200  may detect a termination of a physical connection in mobile computing resource  100 . When that occurs, client device  200  resets its physical KVM to a default state at step  508 . 
         [0042]    Alternatively, a virtual KVM (i.e., a KVM service application), rather than a physical KVM, has become available at step  510 . Client device  200  may launch the virtual KVM service application, if required. At step  511 , mobile computing resource  100  takeover display control module  214  and data hub  213  from client device  200 . The virtual KVM may have a lower performance than physical KVM switch, as data package is examined by client device  200  prior to performing proper data routing. At step  512 , either device may end its virtue KVM service application or, alternatively, client device  200  may detect a termination the connection with mobile computing resource  100 . When either event occurs, client device  200  exits the virtue KVM service application at step  513 . 
         [0043]    While the detailed description above illustrates herein specific embodiments of the present invention, various variations, modifications and changes are possible within the scope of the present invention. It is desired that the present invention is to be protected by the following claims in a Letters Patent.
A high-performance handheld mobile computing resource need not be provided a display or any peripheral devices to augment the performance of a client device. The mobile computing resource may include a motherboard, a central processing unit (CPU), a read-only memory (ROM), a random access memory (RAM), a basic input/output system (BIOS), and an operating system (OS). A wireless module may be provided to enable wireless services. A power module may be provided to allow the mobile computing resource to serve as a power source. The mobile computing resource may serve as local cloud computation and storage resources to the client device, or as a remote desktop computer.