Split computing architecture involving wearable devices and companion devices
By splitting the computing architecture and offloading computing tasks to supporting devices, the problems of short battery life and thermal comfort in wearable devices are solved, enabling long-term use and reasonable industrial design, and improving the user experience.
Patent Information
- Application Number
- CN202380035576.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-26
- Filing Date
- 2023-04-26
- Publication Date
- 2024-11-26
AI Technical Summary
Existing wearable devices, such as smart glasses, have short battery life when the display is on, making it difficult to meet the needs of long-term use, and it is also difficult to balance thermal comfort and industrial design constraints.
By adopting a split computing architecture, computing tasks are offloaded to supporting devices such as smartphones or servers, and data and results are transmitted through communication lines, reducing the power and heat consumption of wearable devices. By utilizing low-power processors and network bandwidth, computing tasks can be split and offloaded.
It extends the battery life of wearable devices, meets the needs of continuous use throughout the day, reduces heat generation, and improves user experience and the rationality of industrial design.
Smart Images

Figure CN119032333A_ABST
Abstract
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application claims the benefit of and priority to U.S. Provisional Patent Application No. 63 / 363,592, filed on April 26, 2022, entitled “SPLIT-COMPUTE ARCHITECTURE,” the disclosure of which is incorporated herein by reference in its entirety.
[0002] This application also incorporates by reference the disclosures of the following related co-pending applications: PCT Application No. PCT / US2023 / 019563, filed on April 24, 2023, PCT Application No. PCT / US2023 / 019832, filed on April 25, 2023, "SPLIT-COMPUTE ARCHITECTURE" filed on April 26, 2023 (Agent Docket No. 0120-497WO1), "PERIPHERAL DEVICES IN A SPLIT-COMPUTE ARCHITECTURE" filed on April 26, 2023 (Agent Docket No. 0120-498WO1), "MULTIPLE APPLICATION RUNTIMES IN A SPLIT-COMPUTE ARCHITECTURE" filed on April 26, 2023 (Agent Docket No. 0120-498WO1), (Attorney Docket No. 0120-505WO1), and “MACHINE LEARNING PROCESSING OFFLOAD IN ASPLIT-COMPUTE ARCHITECTURE” filed on April 26, 2023 (Attorney Docket No. 0120-509WO1). Technical Field
[0003] The implementation method relates to a wearable device processing architecture. Background Art
[0004] Some devices (e.g., wearable devices) may have advanced display capabilities. These devices may face the challenge of fitting sufficiently capable electronics into a small form factor. These issues become increasingly challenging in applications where it may be desirable to wear the device all day, such as accessibility.
[0005] Existing commercially available systems cannot support continuous use scenarios. For example, wearable devices (e.g., smart glasses, smart watches, head mounted displays, etc.) are intended for intermittent contact and are built around mobile phone-like systems-on-chip (SoCs). These devices can only provide a few hours of battery life with the display turned on. In addition, due to the small size of head mounted displays, thermal comfort may be an issue. Summary of the invention
[0006] An example implementation includes a wearable device and a companion device using a split computing architecture. To conserve wearable device resources, the companion device can handle computing tasks that would otherwise be performed by the wearable device. The split computing architecture facilitates offloading computing tasks to the companion device.
[0007] In general aspects, an apparatus, a system, a non-transitory computer-readable medium having computer executable program code stored thereon that can be executed on a computer system, and / or a method can perform a process by a method including: initiating a computing process on a wearable device, the computing process including multiple tasks; identifying a companion device and determining that the companion device can be used to perform at least one of the multiple tasks; causing the companion device to perform at least one task, including communicating data generated by the wearable device to the companion device; receiving, by the wearable device, a result associated with completion of the at least one task by the companion device; and completing, by the wearable device, the computing process based on the result associated with completion of the at least one task. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Example implementations will be more fully understood from the detailed description given herein below and the accompanying drawings, in which like elements are represented by like reference numerals, which are given by way of illustration only and thus do not limit example implementations.
[0009] Figure 1 A block diagram of a high-level split computing architecture according to an example implementation is illustrated.
[0010] Figure 2 A block diagram of a high-level split computing architecture with a shared runtime environment according to an example implementation is illustrated.
[0011] Figure 3 A block diagram of a wearable device split computing architecture according to an example implementation is illustrated.
[0012] Figure 4 A block diagram of a high-level split computing architecture according to an example implementation is illustrated.
[0013] Figure 5 A block diagram of active elements in a wearable device application is illustrated according to an example implementation.
[0014] Figure 6 A block diagram of a wearable device application in a wearable device runtime environment according to an example implementation is illustrated.
[0015] Figure 7 A block diagram of a system using a split computing architecture according to an example implementation is illustrated.
[0016] Figure 8 is a block diagram of a method of operating a split computing system according to an example implementation.
[0017] Fig. 9 is a block diagram of a method of operating a wearable device according to an example implementation.
[0018] Fig.10 is a block diagram of a method for operating a companion device according to an example implementation.
[0019] It should be noted that these figures are intended to illustrate the general characteristics of the methods and / or structures utilized in certain example implementations and to supplement the written description provided below. However, these drawings are not necessarily drawn to scale and may not accurately reflect the exact structure or performance characteristics of any given implementation, and should not be interpreted as defining or limiting the range of values or properties covered by the example implementations. For example, the positioning of modules and / or structural elements may be reduced or enlarged for clarity. The use of similar or identical reference numerals in the various figures is intended to indicate the presence of similar or identical elements or features. DETAILED DESCRIPTION
[0020] Wearable devices may only provide a few hours of battery life with the display turned on. For example, computationally expensive operations for wearable display optics (such as image rendering, distortion correction, location services, and / or the like) may not always be efficiently performed on a low-power embedded system implemented in a wearable device. Therefore, display architectures for thin-client wearable devices (e.g., smart glasses) may have an opportunity to reduce device onboard power and thermal footprint by offloading computationally intensive operations (e.g., graphics operations) to a companion device (e.g., a mobile device, smartphone, server, and / or the like).
[0021] Some wearable devices may have implementation constraints. For example, smart glasses implementation constraints may include (1) smart glasses should amplify key services through wearable computing. This may include supporting technologies such as AR and visual perception. For example, smart glasses implementation constraints may include (2) smart glasses should last a full day of use on a single charge. For example, smart glasses implementation constraints may include (3) smart glasses should look or feel like real glasses. Wearable devices may include augmented reality (AR) and virtual reality (VR) devices. Wearable devices may include smart glasses, head-mounted devices, and / or helmet-mounted devices. Wearable devices, head-mounted devices, and / or helmet-mounted devices may be AR / VR devices. A fully standalone wearable device (e.g., smart glasses) solution with a mobile SoC that has the ability to support the desired features may not meet the power and industrial design constraints listed above. It may be difficult to implement an on-device computing solution that meets constraints (1), (2), and (3) using existing technology. A limitation of current technology is that a standalone solution with mobile system-on-chip (SoC) technology that meets the functional requirements cannot meet the power and industrial design constraints listed above.
[0022] A split computing architecture can be used to solve problems associated with existing wearable device technology implementations that meet the above constraints. A split computing architecture can be an architecture that moves the application runtime environment to a remote computing endpoint, such as a smartphone, server, cloud, desktop computer, etc., generally referred to as a companion device in the following. In some implementations, data sources such as an inertial measurement unit (IMU) and a camera sensor can be streamed from the wearable device to the companion device. In some implementations, display content can be streamed from the companion device back to the wearable device. Continuing with the smart glasses example, most of the computing and rendering does not occur on the smart glasses, so a split computing architecture can allow the use of systems based on low-power processors and / or low-power microcontrollers MCU. In some implementations, a split computing architecture combined with a wearable device including an MCU can allow for minimization of power usage, thereby meeting constraints (1), (2), and (3). With new innovations in codecs and networking, it is possible to maintain the required networking bandwidth in a low-power manner. In some implementations, the wearable device can communicate with the companion device through a well-defined protocol. The architecture can be platform independent.
[0023] Figure 1 A block diagram of a high-level split computing architecture according to an example implementation is illustrated. Figure 1As shown, the split computing architecture may include a wearable device 105 and a companion device 110. In an example implementation, the wearable device 105 may be smart glasses, an augmented reality / virtual reality headset, a head mounted display (HMD), a smart watch, a smart ring, and / or the like. As an example, Figure 1 The wearable device 105 is shown as smart glasses 135. In an example implementation, the companion device 110 can be another wearable device, a mobile device, a smartphone, a tablet computer, a server, and a device including a processor and an operating system. As an example, Figure 1 The companion device 110 is shown as a smartphone 140.
[0024] The wearable device 105 and the accessory device 110 can be communicatively coupled. For example, the wearable device 105 and the accessory device 110 can be communicatively coupled in a wired or wireless manner. In other words, the wearable device 105 and the accessory device 110 can be endpoints of a two-way, wired and / or wireless communication link. As an example, the wearable device 105 and the accessory device 110 can communicate an audio stream and / or a video stream via a communication line 115. As an example, the wearable device 105 and the accessory device 110 can communicate data (e.g., an IMU, a camera, an input, and / or the like) via a communication line 120. As an example, the wearable device 105 and the accessory device 110 can communicate a control stream via a communication line 125. The communication line 115, the communication line 120, and / or the communication line 125 can be collectively referred to as a communication line 130. In some implementations, the communication line 130 can be bidirectional.
[0025] In some implementations, the companion device 110 may include a runtime environment to which the wearable device 105 may be connected. In some implementations, the wearable device 105 may stream data such as IMU and camera images into the runtime environment. In some implementations, the runtime environment of the companion device 110 may be configured to perform tracking, sensing and / or application rendering and / or deliver output back to the wearable device 105 via a graphics application programming interface (API), such as encoded video or rendering commands. In some implementations, the runtime environment may be a code or software application and / or container executed on the companion device 110. In some implementations, the runtime environment may be software that operates on the companion device 110 simultaneously with the wearable device 105 and / or during the time when the wearable device 105 and the companion device 110 are communicatively coupled. In some implementations, input is captured from the wearable device 105 and injected (e.g., communicated) into the runtime environment of the companion device 110.
[0026] As an example, in the absence of the companion device 110, the computing process will be executed entirely on the wearable device 105. The computing process can be any computing process associated with the functionality of the wearable device. For example, the computing process can be a computing process configured to display content (e.g., as an image or video) on a display of the wearable device 105. The computing process can be any computing process that includes at least one task (or multiple tasks). At least one task can be a computer instruction (e.g., code) stored on the memory of the wearable device 105 and executed by the processor of the wearable device 105. At least one task can be a computer instruction (e.g., code) stored on the memory of the companion device 110 and executed by the processor of the companion device 110.
[0027] At least one task may be a computer instruction (e.g., code) configured to generate a result. The result may be an intermediate result or output of a computing process. The result may be a completed or final result or output of a computing process. At least one task may be an instruction executed by a processor of the wearable device 105. At least one task may be an instruction executed by a processor of the companion device 110. In some implementations, the task may be implemented as a service. A service may be, for example, a machine-to-machine interaction over a network. A service may be implemented as a background operation. For example, a service may perform network transactions, play audio, perform I / O, interact with a content provider, and / or the like from the background.
[0028] By including a companion device 110 (e.g., a runtime environment for the companion device 110), device onboard power usage and thermal footprint can be reduced by offloading one or more of a plurality of tasks to the companion device 110. In an example implementation, a plurality of tasks can be split. Splitting the tasks can include systematically and / or randomly assigning a plurality of tasks between the wearable device 105 and the companion device 110. For example, systematically assigning a plurality of tasks between the wearable device 105 and the companion device 110 can be based on resource usage. For example, if a greater amount of resources are used to cause a task (or tasks) to be performed on the companion device 110 (note that performing a task includes performing a computer operation) than performing the task (or tasks) on the wearable device 105, the task (or tasks) can be performed on the wearable device 105.
[0029] For example, a task (or tasks) may include and / or use computer data (e.g., a high-resolution image captured by a camera of the wearable device 105). If communicating computer data uses more resources (e.g., battery resources of the wearable device 105) than a task that includes processing data by the wearable device 105, the wearable device 105 should be assigned to complete the task. Otherwise, the companion device 110 should be assigned to complete the task. In this example implementation, both the wearable device 105 and the companion device 110 are capable of performing the task (or tasks). In some implementations, two or more companion devices may be used to complete a process that includes multiple tasks.
[0030] Figure 2 A block diagram of a high-level split computing architecture with a shared runtime environment according to an example implementation is illustrated. Figure 2 As shown, the wearable device 105 is communicatively coupled to two or more supporting devices 110-1, 110-2, ..., 110-n via communication lines 130-1, 130-2, ..., 130-n, respectively. In some implementations, the wearable device 105 can roam between the various supporting devices 110-1, 110-2, ..., 110-n, thereby selecting the supporting device 110-1, 110-2, ..., 110-n that provides the best experience at this time. The wearable device 105 can be connected to multiple supporting devices 110-1, 110-2, ..., 110-n runtime at the same time. Therefore, the wearable device 105 can be connected to multiple runtime environments at the same time.
[0031] For example, a runtime environment associated with accessory device 110-1 may be configured to project content onto a display of wearable device 105, while a runtime environment associated with accessory device 110-2 may be configured to access a data source (e.g., a sensor) from wearable device 105, a database server, the Internet, and / or the like for processing. In addition or alternatively, accessory devices 110-1, 110-2, ..., 110-n may be communicatively coupled (e.g., in a wired or wireless manner) to share resources and / or data. For example, accessory device 110-1 and accessory device 110-2 may be communicatively coupled such that a runtime environment associated with accessory device 110-1 is able to receive data from a runtime environment associated with accessory device 110-2 for use when the runtime environment associated with accessory device 110-2 generates an image (or frame) to project content onto a display of wearable device 105.
[0032] For example, the companion device 110-1 and the companion device 110-2 can be communicatively coupled (e.g., via communication line 205) so that the runtime environment associated with the companion device 110-2 can share processing resources with the runtime environment associated with the companion device 110-1. For example, the runtime environment associated with the companion device 110-1 can be instructed to generate content (e.g., images, frames, maps, and / or the like) that is more efficiently generated by the runtime environment associated with the companion device 110-2. For example, the companion device 110-2 can include a map database and a map (e.g., image) generator. The runtime environment associated with the companion device 110-1 can be instructed to generate content including a map. In this example, the runtime environment associated with the companion device 110-1 can request a map from the runtime environment associated with the companion device 110-2.
[0033] Continuing with the above example, if a determination is made that the accessory device 110 is to perform the task, the accessory device 110 (or the wearable device 105) may determine that two or more accessory devices 110 can perform the task. For example, the task may include generating content (e.g., an image) to be displayed on the wearable device 105. In this example, the accessory device 110-1 may be configured to generate the content. However, the data for generating the content may be generated by the accessory device 110-2, which is then communicated from the accessory device 110-2 (e.g., via the communication line 205) to the accessory device 110-1. For example, the accessory device 110-2 may be a wearable smart watch configured to sense the user's heart rate. Data representing the heart rate may be communicated from the accessory device 110-2 to the accessory device 110-1. The accessory device 110-1 may then generate content using the data representing the heart rate, and the content may be communicated to the wearable device 105 for display on the display of the wearable device 105.
[0034] Figure 3 A block diagram of a wearable device split computing architecture according to an example implementation is illustrated. Figure 3 As shown, the wearable device split computing architecture may include a hardware abstraction layer (HAL) 310 block. HAL 310 may be a software layer configured to interface between an operating system (e.g., RTOS 340) and a hardware device at a general or abstract level rather than a hardware level. In some implementations, the use of an abstraction layer may make the split computing architecture platform independent. HAL 310 may be called from an operating system kernel. In some implementations, HAL 310 may be a virtual HAL. The virtual HAL may minimize interpretation latency based on the similarity of the architectures of the client and host platforms. Virtualization technology helps map virtual resources to physical resources and use native hardware for computing in the virtual HAL.
[0035] Thus, as an example, HAL 310 may include a connectivity 315 block, a codec 320 block, a graphics processing unit (GPU) 325 block, and a display 330 block, each of which is configured to interface with a corresponding hardware device. For example, connectivity 315 may be configured to interface between an operating system (e.g., RTOS 340) and Bluetooth hardware, WIFI hardware, ultra-wideband (UWB) hardware, 5G hardware, and / or the like. Thus, the wearable device split computing architecture may be configured to utilize any connectivity hardware designed into the wearable device 105.
[0036] For example, the codec 320 can be configured to interface between an operating system (e.g., RTOS 340) and an encoder and / or decoder (e.g., a hardware-based encoder and / or decoder). The codec 320 standard can be, for example, H.265, H.264, MPEG, VP9, machine learning, and / or the like. The codec 320 can be an image, video, and / or audio codec. Thus, the wearable device split computing architecture can be configured to utilize any codec software and / or hardware designed into the wearable device 105. For example, the GPU 325 can be configured to interface between an operating system (e.g., RTOS 340) and GPU hardware (e.g., GPU ASIC). Thus, the wearable device split computing architecture can be configured to utilize any GPU designed into the wearable device 105 (e.g., to render images on a display system). For example, the display 330 can be configured to interface between an operating system (e.g., RTOS 340) and display hardware (e.g., a wearable device display). Thus, the wearable device split computing architecture can be configured to take advantage of any display (e.g., display driver system) designed into the wearable device 105.
[0037] like Figure 3 As shown, the wearable device split computing architecture may include an operating system (OS) abstraction layer (OSAL) 335. In some implementations, the use of an abstraction layer can make the split computing architecture independent of the platform. The OSAL 335 can be configured to provide an interface to common system functions provided by the OS of the wearable device 105. These OSALs 335 can simplify the development and porting of software (e.g., applications) to multiple OS and hardware platforms. In some implementations, the OSAL 335 can operate as (or similar to) an application programming interface (API). In some implementations, the OSAL 335 can be platform independent.
[0038] OSAL 335 may include a real-time operating system (RTOS) 340 block. RTOS 340 may be configured to handle, for example, multi-threaded applications to meet real-time deadlines. For example, RTOS 340 may be configured to handle multiple tasks, each task (or task group) having a maximum completion time. Although RTOS is illustrated, any OS may be used. For example, a high-level operating system (HLOS) may be used. In a split computing system, tasks are used to enable these tasks (or task groups) to be distributed between computing devices. For example, the content display operation of wearable device 105 may be divided between wearable device 105 and supporting device 110 (e.g., a runtime environment associated with supporting device 110). In other words, wearable device 105 (and / or supporting device 110) may be configured (e.g., using a wearable device split computing architecture) to cause supporting device 110 to perform a portion (a task or task group) of a process (e.g., content display).
[0039] like Figure 3 As shown, the wearable device split computing architecture may include a peripheral driver 345 block. The peripheral driver 345 may be configured to interface between the OS and the peripheral devices. For example, the wearable device 105 may include multiple peripheral devices, including, for example, cameras, microphones, speakers, inputs, inertial measurement units (IMUs), and / or the like. Therefore, the peripheral driver 345 may be configured to interface between the RTOS 340 and the peripheral devices of the wearable device 105.
[0040] like Figure 3As shown, the wearable device split computing architecture may include a device client 305. The device client 305 may be configured to control the communication between the wearable device 105 and the matching device 110. For example, the device client 305 may be configured to generate, initialize and control the communication line 130 and the communication through the communication line 130. The communication line 130 may be operated as, for example, a socket (e.g., a network socket, a TCP / IP network socket, etc.). A socket may be an endpoint of a two-way communication link between computer codes (e.g., applications, programs, software systems and / or the like) running on two computing devices. The socket mechanism may be configured to provide inter-process communication (IPC) by establishing a named communication contact point between two endpoints and / or between two endpoints and an intermediate device (e.g., an access point (AP)). The socket may be configured to provide a bidirectional first-in, first-out (FIFO) communication channel. A socket connected to the network is created at each end of the communication. As an example, each socket may have an address (or memory location). The address (or memory location) may be, for example, an IP address and a port number. Thus, the device client 305 may be configured to write to and read from a socket associated with the companion device 110 (or a runtime environment associated with the companion device 110). In some implementations, the device client 305 may be platform independent.
[0041] In some implementations, a software development kit (SDK) may be associated with the wearable device 105 and the accessory device 110. The SDK may be used when developing applications for the wearable device 105 and / or the accessory device 110. The SDK may enable a split computing architecture. Thus, any wearable device 105 and / or accessory device 110 that includes a split computing architecture (regardless of the hardware and / or software platform) may use applications developed using the SDK. Thus, it is not necessary to develop an application and port it to each hardware and / or software platform that may be used as a wearable device 105 and / or accessory device 110. When the application is installed on the wearable device 105 and / or the accessory device 110, the SDK may be included within the application (or have elements that may be included within the application).
[0042] Figure 4 A high-level split computing architecture according to an example implementation is illustrated. Figure 4As shown, the system may include a wearable device 105 and a companion device 110. The split computing architecture of the system may include a device client 305 block associated with the wearable device 105, an application 410 block, an SDK 415 block, and a core 420 block associated with the companion device 110. As mentioned above, the device client 305 can be configured to control communication between the wearable device 105 and the companion device 110. The core 420 can be configured to control communication between the companion device 110 and the wearable device 105. Therefore, the core 420 can be configured to generate, initialize and control at least the communication line 130 and the communication through the communication line 130. The communication line 130 can operate as, for example, a socket (as described above).
[0043] In some implementations, the application 410 may include a file format (e.g., Android package kit (APK)) for applications used on an OS that stores application logic. In some implementations, the wearable device application may be linked to a stub (e.g., incomplete) version of the SDK to support compilation and testing services. In some implementations, at runtime, the application 410 may load the wearable device SDK 415 directly from the wearable device runtime environment. In some implementations, the SDK 415 may provide developers with an application programming interface (API) for building wearable device applications. In some implementations, the API versioning scheme allows the introduction of new APIs while maintaining backward compatibility. In some implementations, the wearable device runtime environment may be a collection of core services responsible for maintaining the wearable device execution environment. In some implementations, the wearable device application may not be able to interact directly with the core services. In some implementations, one or more interactions may be performed through the SDK. In some implementations, the device client 305 may be a thin client running on the wearable device 105 hardware.
[0044] As an example, the application 410 can be configured to generate (or facilitate generation of) content for display on the wearable device 105. For example, the application can be configured to process a task. For example, the application can generate content (e.g., as an image) and communicate the content to the core 420 via the SDK 415. Communicating the content to the core 420 via the SDK 415 can be one of the features that allows the application 410 to be developed for any hardware and / or software platform. For example, the SDK 415 can be configured to communicate with the application 410 when developing the application 410. The SDK 415 can also be configured to communicate with the core 420, which is associated with multiple hardware and / or software platforms. After receiving the content, the core 420 can communicate the content to the wearable device 105 via the device client 305 using, for example, a pre-established socket.
[0045] As mentioned above, in some implementations, the wearable device 105 can be configured to connect to more than one companion device 110 at a given time. In some implementations, different companion devices 110 can be configured to provide different services (e.g., using applications 410). In some implementations, as low-latency, high-bandwidth 5G connections become mainstream, the companion devices 110 can be configured to operate in the cloud (e.g., connect via the 5G standard).
[0046] Figure 5 A block diagram of an active element in a wearable device application according to an example implementation is illustrated. Figure 5 As shown, the application 410 may include a wearable activity 505 block, a wearable activity service 510 block, and a wearable activity host 515 block, and the core 420 may include a core service 520 block.
[0047] In some example implementations, the wearable device application design can be similar to the activity model. Figure 3 , RTOS 340 can be configured to handle one task, multiple tasks, each task (or task group) having a maximum completion time. Therefore, each activity can be a task that is executed in a parallel process and has a time (or amount of time) to be completed before it.
[0048] In an example implementation, the activity can be executed in a service context. In some implementations, running in a service context can allow the application 410 to run concurrently with the companion device 110 application. In some implementations, the application can continue to run and render when the companion device 110 display is turned off.
[0049] In some implementations, one or more applications 410 may include a wearable activity service 510. The wearable activity service 510 may be configured to expose the wearable activity 505 so that the wearable activity 505 may be instantiated by the SDK 415. Thus, the wearable activity 505 may be instantiated at a later point in time. From a developer's point of view, the wearable activity service 510 may be boilerplate code that is not directly related to the application 410 logic. The wearable activity 505 may be code related to the application 410 logic. In some implementations, the wearable activity 505 may be managed by an activity manager and behave similarly to a standard OS activity counterpart.
[0050] In some implementations, the wearable device runtime environment can use service binding to launch and manage the life cycle of the application 410. Once the activity manager is bound to the service as part of the startup process, the SDK 415 can instantiate and attach the wearable activity host 515 as a class that can be responsible for general activity state control, for example. For example, during initialization, the wearable activity host 515 can request a surface from the window manager. The surface is then used as a backing store for the virtual display used to render the content of the application 410.
[0051] Figure 6 A block diagram of a wearable device application in a wearable device runtime environment according to an example implementation is illustrated. Figure 6 As shown, the companion device OS 605 can handle two or more application environments simultaneously. For example, the companion device OS 605 can include an application module 610. The application module 610 can be associated with standard OS application activities. In addition, the companion device OS 605 can include an application module 630 that operates in association with a wearable runtime environment 625. The wearable runtime environment 625 can be associated with the wearable device 105.
[0052] Activities 620, 640 can be single, focused tasks that an application can perform. For example, some applications can include a user interface (UI). Therefore, activities 620, 640 can be configured to create a window to place the UI. The window can be a full screen window, a floating window embedded in other windows, a hidden window, and / or the like. Different types of windows can be associated with different activities 620, 640. Activities 620, 640 can be configured for any task, a window is just an example.
[0053] The activity managers 615, 635 may be configured to communicate information about and interact with the activities 620, 640. The activity managers 615, 635 may be further configured to communicate information about and interact with tasks, threads, services, and other processes.
[0054] In an example implementation, the wearable runtime environment 625 can be a virtual runtime environment. A virtual runtime environment can be configured to operate in the background of a computing device. Thus, the wearable runtime environment 625 can be a virtual runtime environment associated with the wearable device 105 and configured to operate as a background process on the companion device 110. In other words, the wearable runtime environment 625 can operate without a user interface shown on a display of the companion device 110. For example, the wearable runtime environment 625 can operate in a hidden window of the companion device 110. Therefore, if the wearable runtime environment 625 is a virtual runtime environment, a user of the companion device 110 may not have visual or I / O control over an application that uses the wearable runtime environment 625.
[0055] In an alternative or additional implementation, the application 410 and / or the application module 630 may be a virtual process. A virtual process may be configured to operate in the background of a computing device. Thus, the application 410 and / or the application module 630 may be a virtual process associated with the wearable device 105 and configured to operate as a background process on the companion device 110. In other words, the application 410 and / or the application module 630 may operate without a user interface shown on a display of the companion device 110. For example, the application 410 and / or the application module 630 may operate in a hidden window of the companion device 110. Therefore, if the process is a virtual runtime process, a user of the companion device 110 may not have visual or I / O control over the application 410 and / or the application module 630.
[0056] Figure 7 A block diagram of a system using a split computing architecture according to an example implementation is illustrated. Figure 7 As shown, the system includes a wearable device 105 and a companion device 110. The wearable device 105 may include a device client 305, a codec 320, a GPU 325, a display 330, and a peripheral driver 345. The companion device 110 may include a core 420, an application module 610 including an encoder 705, and an application module 630 including an application 410. This example implementation can be used to describe the signal flow associated with generating and displaying content on the wearable device 105 using the split computing architecture described herein. This is just one of many possible system configurations and uses, and other configuration uses may also exist and are all within the scope of the present disclosure.
[0057] In this example implementation, the application 410 can be configured to generate content for display on the wearable device 105. The application 410 can be configured to generate content based on data received from the wearable device 105. For example, the peripheral driver 345 can sense data and communicate the data as peripheral data (e.g., IMU data) to the application module 630 via the device client 305 and the core 420 using the communication line 120. In other words, the peripheral data can be data that is collected and / or processed (e.g., compressed, packaged, parsed, filtered, denoised, and / or the like) by the peripheral device via the peripheral driver 345 and packaged for communication with the wearable device 105 and / or the companion device 110 and for use by the wearable device 105 and / or the companion device 110. The application 410 can generate content as, for example, rendered images and / or frames. The encoder 705 can compress the images and / or frames (e.g., using an H.264 codec). The compressed images and / or frames may be communicated to the wearable device 105 via the core 420 and the device client 305 using the communication line 115. The codec 320 may decompress the images and / or frames (e.g., using an H.264 codec). The GPU 325 may cause the images and / or frames to be displayed on the display 330.
[0058] Example 1. Figure 8 is a block diagram of a method of operating a split computing system according to an example implementation, the split computing system including a wearable device and a companion device communicatively coupled to the wearable device. Figure 8As shown, in step S805, a computing process is initiated on the wearable device, the computing process including multiple tasks. For example, the computing process can be initiated by the user of the wearable device providing a corresponding user input (e.g., a gesture) to the wearable device. In some implementations, the wearable device can initiate the computing process based on another computing process, based on the spatial position of the wearable device, and / or the like. In step S810, it is determined that the supporting device can be used to perform at least one of the multiple tasks. For example, the wearable device can identify the supporting device as an available supporting device on a list of potentially available supporting devices stored in a memory of the supporting device. Alternatively, the available supporting device can be any supporting device located near the wearable device that can establish a connection with the wearable device via a two-way or three-way handshake (e.g., the handshake can be bidirectional because both the client and the host determine which capabilities each supports). The available supporting device can signal the wearable device a list of tasks that the supporting device can perform, or the wearable device may already know the tasks that a particular type of supporting device can perform. In step S815, the wearable device communicates the data generated by the wearable device to the supporting device. For example, the data may include IMU and camera images, and / or metadata associated with the images. In step S820, the accessory device performs at least one task. For example, the accessory device may automatically perform at least one task upon receiving the data. In step S825, the accessory device communicates a result associated with the completion of at least one task. Here, the term result may be used to refer to processed data. In step S830, the wearable device receives a result associated with the completion of at least one task. In step S835, the wearable device completes a computing process based on the result associated with the completion of at least one task. Here, the wearable device may combine the processed data received from the accessory device with additional processed data that is associated with the remaining tasks of the multiple tasks completed by the wearable device.
[0059] Example 2. A method as described in Example 1, wherein the accessory device may be a first accessory device and the at least one task is at least one first task, the system may further include a second accessory device, and the system may be configured to cause the second accessory device to perform at least one second task among a plurality of tasks. Causing the device to perform a task may include sending an instruction configured to initiate task processing by the device and / or another device and / or trigger the task processing.
[0060] Example 3. A method as described in Example 2, wherein the first accessory device and the second accessory device can be communicatively coupled.
[0061] Example 4. A method as described in Example 1, wherein the wearable device can be smart glasses.
[0062] Example 5. A method as described in Example 1, wherein the companion device can be at least one of another wearable device, a mobile device, a smartphone, a tablet computer, a server, and a device including a processor and an operating system.
[0063] Example 6. A method as described in Example 1, wherein the runtime environment can be a virtual runtime environment that operates as a background process on a companion device.
[0064] Example 7. The method of Example 6, wherein at least one task may include an application, and at least one task may further include processing an output of the application.
[0065] Example 8. Example 7. The method of Example 7, wherein processing the output of the application may include rendering an image on a display of the wearable device.
[0066] Example 9. The method of Example 7, wherein the device client can be configured to control communications associated with the application.
[0067] Example 10. The method of Example 1, wherein the computing process can be initiated by the wearable device.
[0068] Example 11. A method as described in Example 1, wherein the computing process can be initiated by a supporting device.
[0069] Example 12. Fig. 9 is a block diagram of a method of operating a wearable device according to an example implementation. Fig. 9 As shown, in step S905, a computing process is initiated on the wearable device, and the computing process includes multiple tasks. In step S910, a companion device is identified and it is determined that the companion device can be used to perform at least one of the multiple tasks. In step S915, the companion device is caused to perform at least one task, including communicating data generated by the wearable device to the companion device. In step S920, the wearable device receives a result associated with the completion of at least one task by the companion device. In step S925, the wearable device completes the computing process based on the result associated with the completion of at least one task.
[0070] Example 13. The method of Example 12, wherein the result is a first result, the method may further include: receiving, by the wearable device, a second result associated with processing of at least one task by the accessory device, processing, by the wearable device, the second result into a processed second result, and communicating, by the wearable device, the processed second result to the accessory device, wherein the result associated with completing at least one task by the accessory device may be based on the processed second result. Here, the term second result may be used to refer to intermediate processed data, and the term first result may be used to refer to final processed data.
[0071] Example 14. The method of Example 12, wherein the computing process can be initiated by the wearable device.
[0072] Example 15. A method as described in Example 12, wherein the computing process can be initiated by a companion device, and initiating the computing process on the wearable device can include receiving a trigger from the companion device by the wearable device.
[0073] Example 16. The method of Example 12, wherein the data can be associated with a peripheral device of the wearable device.
[0074] Example 17. A method as described in Example 12, wherein the wearable device may include a first socket, the companion device may include a second socket communicatively coupled to the first socket, and the method may further include: causing the companion device to perform at least one task including writing instructions and data to the first socket, and receiving a result associated with completion of the at least one task including reading the result from the second socket.
[0075] Example 18. The method of Example 12, wherein the result may include an image, the method further comprising: displaying the image on a display of the wearable device.
[0076] Example 19. The method of Example 12, wherein the wearable device may be smart glasses.
[0077] Example 20. A method as described in Example 12, wherein the companion device can be at least one of another wearable device, a mobile device, a smartphone, a tablet computer, a server, and a device including a processor and an operating system.
[0078] Example 21. A method as described in Example 12, wherein the accessory device may include a virtual runtime environment, causing the accessory device to perform at least one task may include causing the virtual runtime environment to execute a computing process, the result of which may be the completion of the computing process, and completing the computing process by the wearable device based on the result includes rendering an image on a display of the wearable device.
[0079] Example 22. Fig.10 is a block diagram of a method for operating a companion device according to an example implementation. Fig.10 As shown, in step S1005, the accessory device determines that the accessory device can be used to perform at least one of a plurality of tasks associated with a computing process. In step S1010, the accessory device receives data associated with the computing process generated by the wearable device. In step S1015, the accessory device performs at least one task. In step S1020, the accessory device communicates a result associated with completing at least one task.
[0080] Example 23. A method as described in Example 22, wherein the result is a first result, the method may further include: communicating, by the accessory device to the wearable device, a second result associated with at least one task processed by the accessory device, receiving, by the accessory device, the processed second result from the wearable device, and completing, by the accessory device, at least one task based on the processed second result, wherein the first result is based on the processed second result.
[0081] Example 24. The method of Example 22, wherein the computing process can be initiated by the wearable device.
[0082] Example 25. A method as described in Example 22, wherein the computing process can be initiated by a companion device, the method can further include: the companion device communicating a trigger associated with initiating the computing process to the wearable device.
[0083] Example 26. The method of Example 22, wherein the data can be associated with a peripheral device of the wearable device.
[0084] Example 27. A method as described in Example 22, wherein the wearable device may include a first socket, the companion device may include a second socket communicatively coupled to the first socket, and the method may further include: causing the companion device to perform at least one task including reading instructions and data from the second socket, and communicating a result associated with completion of the at least one task including writing the result to the second socket.
[0085] Example 28. The method of Example 22, wherein the result may include an image.
[0086] Example 29. The method of Example 22, wherein the wearable device may be smart glasses.
[0087] Example 30. A method as described in Example 22, wherein the companion device can be at least one of another wearable device, a mobile device, a smartphone, a tablet computer, a server, and a device including a processor and an operating system.
[0088] Example 31. A method as described in Example 22, wherein the supporting device may include a virtual runtime environment, and causing the supporting device to perform at least one task may include causing the virtual runtime environment to perform multiple tasks, and the result may be the completion of multiple tasks.
[0089] Example 32. A method may include any combination of one or more of Examples 1 to 31.
[0090] Example 33. A non-transitory computer-readable storage medium comprising instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to perform the method of any one of Examples 1 to 32.
[0091] Example 34. An apparatus comprising components for performing the method as described in any of Examples 1 to 32.
[0092] Example 35. A device comprising at least one processor and at least one memory comprising computer program code, the at least one memory and the computer program code being configured to cause the device to perform at least a method as described in any one of Examples 1 to 32 through the at least one processor.
[0093] An example implementation may include a non-transitory computer-readable storage medium including instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to perform any of the methods described above. An example implementation may include a device including means for performing any of the methods described above. An example implementation may include a device including at least one processor and at least one memory including computer program code, the at least one memory and the computer program code being configured to cause the device, through at least one processor, to perform at least any of the methods described above.
[0094] Various implementations of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system that includes at least one programmable processor that can be either special purpose or general purpose and can be coupled to receive data and instructions from and send data and instructions to a storage system, at least one input device, and at least one output device.
[0095] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages and / or in assembly / machine languages. As used herein, the terms "machine-readable medium," "computer-readable medium," refer to any computer program product, apparatus, and / or device (e.g., disk, optical disk, memory, programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.
[0096] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having a display device (LED (light emitting diode), or OLED (organic LED), or LCD (liquid crystal display) monitor / screen) for displaying information to the user and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other kinds of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form, including sound, voice, or tactile input.
[0097] The systems and techniques described herein may be implemented in a computing system that includes a back-end component (e.g., as a data server), or includes a middleware component (e.g., an application server), or includes a front-end component (e.g., a client computer having a graphical user interface or a web browser through which a user can interact with an implementation of the systems and techniques described herein), or any combination of such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), and the Internet.
[0098] A computing system may include clients and servers. Clients and servers are generally remote from each other and usually interact through a communication network. The relationship of client and server is created by computer programs running on the respective computers and placing each other in a client-server relationship.
[0099] A number of implementations have been described, however, it will be appreciated that various modifications may be made without departing from the spirit and scope of the specification.
[0100] In addition, the logic flows depicted in the figures do not require the particular order shown or sequential order to achieve the desired results. In addition, other steps can be provided, or steps can be deleted from the described processes, and other components can be added to or removed from the described systems. Therefore, other implementations are within the scope of the appended claims.
[0101] Although certain features of the described implementations have been described as described herein, those skilled in the art will now expect many modifications, substitutions, changes and equivalents. Therefore, it should be understood that the appended claims are intended to cover all such modifications and changes that fall within the scope of the implementations. It should be understood that they are presented only in an exemplary and non-limiting manner, and various changes in form and detail may be made. Except for mutually exclusive combinations, any part of the devices and / or methods described herein may be combined in any combination. The implementations described herein may include various combinations and / or sub-combinations of the functions, components and / or features of the different implementations described.
[0102] Although the example implementations may include various modifications and alternative forms, their implementations are shown by way of example in the drawings and will be described in detail herein. However, it should be understood that the example implementations are not intended to be limited to the specific forms disclosed, but rather, the example implementations will cover all modifications, equivalents, and alternatives that fall within the scope of the claims. Like numbers refer to the same elements in the description of the drawings.
[0103] Some of the above example implementations are described as processes and methods depicted as flow charts. Although the flow charts describe the operations as sequential processes, many operations can be performed in parallel, concurrently, or simultaneously. In addition, the order of the operations can be rearranged. Processes can terminate when their operations are completed, but can also have additional steps not included in the figure. A process can correspond to a method, function, procedure, subroutine, subprogram, etc.
[0104] The methods discussed above (some of which are illustrated by flowcharts) may be implemented by hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. When implemented by software, firmware, middleware, or microcode, the program code or code segments for performing the necessary tasks may be stored in a machine or computer readable medium, such as a storage medium. One or more processors may perform the necessary tasks.
[0105] The specific structural and functional details disclosed herein are merely representative for the purpose of describing example implementations. However, example implementations are embodied in many alternative forms and should not be construed as being limited to only the implementations set forth herein.
[0106] It should be understood that although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, without departing from the scope of the example implementation, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. As used herein, the terms and / or include any and all combinations of one or more of the associated listed items.
[0107] It should be understood that when an element is referred to as being connected or coupled to another element, the element may be directly connected or coupled to the other element, or there may be intervening elements. Conversely, when an element is referred to as being directly connected or coupled to another element, there are no intervening elements. Other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., between versus directly between, adjacent versus directly adjacent, etc.).
[0108] The terms used herein are only for the purpose of describing a particular implementation and are not intended to limit the example implementation. As used herein, the singular forms one, a kind and the are also intended to include the plural forms unless the context clearly indicates otherwise. It should be further understood that the terms include, contain, contain and / or have when used herein specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.
[0109] It should also be noted that in some alternative implementations, the functions / actions noted may not occur in the order noted in the figures. For example, two figures shown in succession may actually be executed simultaneously or may sometimes be executed in the reverse order, depending on the functionality / behaviors involved.
[0110] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the example implementations belong. It should be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant art, and should not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.
[0111] Portions of the above example implementations and corresponding detailed descriptions are presented in software or algorithms and symbolic representations of operations on data bits in computer memory. These descriptions and representations are descriptions and representations that effectively convey the essence of their work to other persons of ordinary skill in the art. An algorithm, as the term is used herein and as it is commonly used, is considered to be a self-consistent sequence of steps leading to a desired result. A step is a step that requires physical manipulation of physical quantities. Typically, although not necessarily, these quantities take the form of optical, electrical, or magnetic signals that can be stored, transmitted, combined, compared, and otherwise manipulated. Mainly for general reasons, it has sometimes proven convenient to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, etc.
[0112] In the above exemplary implementations, references to symbolic representations of actions and operations that can be implemented as program modules or functional processes (e.g., in the form of flowcharts) include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types, and can be described and / or implemented using existing hardware at existing structural elements. Such existing hardware may include one or more central processing units (CPUs), digital signal processors (DSPs), application specific integrated circuits, field programmable gate arrays (FPGAs), computers, etc.
[0113] It should be borne in mind, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. Unless otherwise specifically noted or as is apparent from the discussion, terms such as processing or computing or calculating or determining display refer to the actions and processes of a computer system or similar electronic computing device that manipulates data represented as physical electronic quantities within the computer system's registers and memories and transforms that data into other data similarly represented as physical quantities within the computer system's memories or registers or other such information storage, transmission or display devices.
[0114] It is also noted that the software-implemented aspects of the example implementations are typically encoded on some form of non-transitory program storage medium or implemented on some type of transmission medium. The program storage medium may be magnetic (e.g., a floppy disk or hard disk) or optical (e.g., a compact disk read-only memory or CD ROM), and may be read-only or random access. Similarly, the transmission medium may be a twisted pair, a coaxial cable, an optical fiber, or some other suitable transmission medium known in the art. The example implementations are not limited by these aspects of any given implementation.
[0115] Finally, it should also be noted that although the attached claims set forth specific combinations of features described herein, the scope of the present disclosure is not limited to the specific combinations claimed thereafter, but extends to cover any combination of features or implementations disclosed herein, regardless of whether the specific combination has been specifically listed in the attached claims at this time.
Claims
1. A method, include: Initiating a computing process on the wearable device, the computing process including a plurality of tasks; Identifying an associated device and determining that the associated device can be used to perform at least one of the plurality of tasks; causing the accessory device to perform the at least one task, including communicating data generated by the wearable device to the accessory device; receiving, by the wearable device, a result associated with completion of the at least one task by the companion device; as well as The computing process is completed by the wearable device based on the result associated with the completion of the at least one task.
2. The method of claim 1, wherein the result is a first result, the method further comprising: include: receiving, by the wearable device, a second result associated with processing of the at least one task by the companion device; Processing, by the wearable device, the second result into a processed second result; as well as The processed second result is communicated by the wearable device to the supporting device, wherein the first result is based on the processed second result.
3. The method of claim 1 or 2, wherein the computing process is initiated by the wearable device.
4. The method according to claim 1 or 2, wherein The computing process is initiated by the companion device, and Initiating the computing process on the wearable device includes receiving a trigger from the supporting device by the wearable device.
5. The method of any one of claims 1 to 4, wherein the data is associated with a peripheral device of the wearable device.
6. The method according to any one of claims 1 to 5, wherein The wearable device comprises a first socket, The companion device includes a second socket communicatively coupled to the first socket, Causing the companion device to perform the at least one task includes writing instructions and the data to the first socket, and Receiving the result associated with completion of the at least one task includes reading the result from the second socket.
7. The method of any one of claims 1 to 6, wherein the result comprises an image, the method further comprising: include: The image is displayed on a display of the wearable device.
8. The method of any one of claims 1 to 7, wherein the wearable device is smart glasses.
9. A method as described in any one of claims 1 to 8, wherein the supporting device is at least one of another wearable device, a mobile device, a smartphone, a tablet computer, a server, and a device including a processor and an operating system.
10. The method according to any one of claims 1 to 9, wherein The supporting device includes a virtual runtime environment, Causing the supporting device to perform the at least one task includes causing the virtual runtime environment to execute the computing process, and The result is the completion of the computing process, and the method further include: Completing the computing process based on the result by the wearable device includes rendering an image on a display of the wearable device.
11. A system, include: Wearable devices; as well as Supporting devices, The wearable device comprises: Device client, Hardware Abstraction Layer, operating system abstraction layer, and and at least one peripheral device driver, The companion device includes a runtime environment associated with the wearable device, and The system is configured to: Initiating a computing process on the wearable device, the computing process including a plurality of tasks; Determining that the supporting device can be used to perform at least one of the plurality of tasks; The wearable device transmits data generated by the wearable device to the supporting device; The at least one task is performed by the supporting device; communicating, by the companion device, a result associated with completion of the at least one task; receiving, by the wearable device, the result associated with the completion of the at least one task; and The computing process is completed by the wearable device based on the result associated with the completion of the at least one task.
12. The system of claim 11, wherein the accessory device is a first accessory device and the at least one task is at least one first task, the system further include: The second supporting device, The system is configured to cause the second supporting device to perform at least one second task among the multiple tasks.
13. A system as described in claim 12, wherein the first supporting device and the second supporting device are communicatively coupled.
14. The system of any one of claims 11 to 13, wherein the wearable device is smart glasses.
15. A system as described in any one of claims 11 to 14, wherein the supporting device is at least one of another wearable device, a mobile device, a smartphone, a tablet computer, a server, and a device including a processor and an operating system.
16. A system as described in any one of claims 11 to 15, wherein the runtime environment is a virtual runtime environment that operates as a background process on the supporting device.
17. The system of claim 16, wherein The at least one task comprises an application, and The at least one task further includes processing an output of the application.
18. The system of claim 17, wherein processing the output of the application comprises rendering an image on a display of the wearable device.
19. The system of claim 17, wherein the device client is configured to control communications associated with the application.
20. The system of any one of claims 11 to 19, wherein the computing process is initiated by the wearable device.
21. A system as described in any one of claims 11 to 19, wherein the computing process is initiated by the supporting device.
22. A method, include: Determining, by the companion device, that the companion device can be used to perform at least one of a plurality of tasks associated with the computing process; Receiving, by the companion device, data associated with the computing process generated by the wearable device from the wearable device; The at least one task is performed by the supporting device; as well as The accessory device communicates results associated with the completion of at least one task to the wearable device.
23. The method of claim 22, wherein the result is a first result, the method further comprising: include: communicating, by the accessory device to the wearable device, a second result associated with processing of the at least one task by the accessory device; Receiving, by the supporting device, a processed second result from the wearable device; as well as The at least one task is completed by the supporting device based on the processed second result, wherein the first result is based on the processed second result.
24. The method of claim 22 or 23, wherein the computing process is initiated by the wearable device.
25. The method of claim 22 or 23, wherein The computing process is initiated by the supporting device, and the method further include: A trigger associated with initiating the computing process is communicated by the accessory device to the wearable device.
26. The method of any one of claims 22 to 25, wherein the data is associated with a peripheral device of the wearable device.
27. The method of any one of claims 22 to 26, wherein The wearable device comprises a first socket, The companion device includes a second socket communicatively coupled to the first socket, and the method further include: Causing the companion device to perform the at least one task includes reading instructions and the data from the second socket, and Communicating the result associated with completion of the at least one task includes writing the result to the second socket.
28. The method of any one of claims 22 to 27, wherein the result comprises an image.
29. The method of any one of claims 22 to 28, wherein the wearable device is smart glasses.
30. A method as described in any one of claims 22 to 29, wherein the supporting device is at least one of another wearable device, a mobile device, a smartphone, a tablet computer, a server, and a device including a processor and an operating system.
31. The method of any one of claims 22 to 30, wherein The companion device includes a virtual runtime environment that operates as a background process on the companion device, Causing the supporting device to perform the at least one task includes causing the virtual runtime environment to perform the multiple tasks, The result is the completion of the plurality of tasks.
32. A non-transitory computer-readable storage medium comprising instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to perform the method of any one of claims 1 to 10.
33. A non-transitory computer-readable storage medium comprising instructions stored thereon, which when executed by at least one processor are configured to cause a computing system to perform the method of any one of claims 22 to 31.
34. An apparatus comprising means for performing the method of any one of claims 1 to 10.
35. An apparatus comprising means for performing the method of any one of claims 22 to 31.
36. A device, include: at least one processor; as well as at least one memory, the at least one memory comprising computer program code; The at least one memory and the computer program code are configured to cause the apparatus, through the at least one processor, to at least perform the method of any one of claims 1 to 10.
37. A device, include: at least one processor; as well as at least one memory, the at least one memory comprising computer program code; The at least one memory and the computer program code are configured to cause the apparatus, through the at least one processor, to perform at least the method of any one of claims 22 to 31.
