Device detection and content management for a wearable device

Abstract

According to at least one implementation, a method includes displaying content on a first device and identifying a second device in a field of view of the first device. The method further includes, in response to identifying the second device within the field of view of the first device, determining at least a portion of the content to be transferred to the second device, and communicating at least that portion of the content to the second device.

Description

Atty Docket No. 0120-1011WO1DEVICE DETECTION AND CONTENT MANAGEMENT FOR A WEARABLE DEVICECROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 739,027, filed December 26, 2024, the disclosure of which is incorporated herein by reference in its entirety.BACKGROUND

[0002] Wearable devices, such as extended reality (XR) devices, encompass a range of technologies designed to be worn by users, including head-mounted displays, headsets, or glasses, that create immersive experiences by blending the physical and virtual worlds. This category includes Virtual Reality (VR) devices that fully immerse users in a computer-generated environment, as well as Augmented Reality (AR) and Mixed Reality (MR) devices that overlay digital information onto the user’s view of the real world. Content can be displayed on these devices through optical see-through or video see-through methods. In optical see-through systems, which can be found in AR glasses, the device features transparent lenses that allow a user to view the physical world directly, with digital elements projected onto the lenses via components like projectors or waveguides. In contrast, video see-through systems, common in many VR and MR headsets, use external cameras to capture a live video feed of the real-world environment, which is then displayed on internal screens where it is combined with virtual elements to create a seamless, integrated view for the user.SUMMARY

[0003] This disclosure relates to systems and methods for detecting additional devices on a wearable device and managing content displayed across the devices. In some implementations, a first device can use its outward-facing camera to identify when the user is looking at a second device. Once this second device is identified, the system can be configured to determine a portion of the content currently on the wearable device that should be transferred, and then communicate that selected portion to the second device for display. In some examples, beforeAtty Docket No. 0120-1011WO1any transfer happens, the system can first verify that the second device belongs to (or is associated with) the user, for example, by recognizing unique visual cues on its screen, such as a familiar wallpaper. Additionally, to improve the user experience, the system can be configured to update the display on the first wearable device. In some examples, this involves removing or relocating its own virtual content to create a passthrough window, allowing the user to view the physical screen of their second device without needing to remove the wearable device (e.g., an XR headset or smart glasses).

[0004] In some aspects, the techniques described herein relate to a method including: displaying content on a first device; identifying a second device in a field of view of the first device; in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

[0005] In some aspects, the techniques described herein relate to a system including: a computer-readable storage medium; at least one processor operatively coupled to the computer-readable storage medium; and program instructions stored on the computer-readable storage medium that, when executed by the at least one processor, direct the at least one processor to perform a method, the method including: display content on a first device; identifying a second device in a field of view of the first device; in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

[0006] In some aspects, the techniques described herein relate to a computer-readable storage medium with program instructions stored thereon that, when executed by at least one processor, direct the at least one processor to perform a method, the method including: display content on a first device; identifying a second device in a field of view of the first device; in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

[0007] The accompanying drawings and the description below outline the details of one or more implementations. Other features will be apparent from the description, drawings, and claims.Atty Docket No. 0120-1011WO1BRIEF DESCRIPTION OF THE DRAWINGS

[0008] FIG. 1 illustrates a computing environment to move content from a first device to a second device according to an implementation.

[0009] FIG. 2 illustrates a method of operating a device to move content to a second device according to an implementation.

[0010] FIG. 3 illustrates an operational scenario of moving content between devices according to an implementation.

[0011] FIG. 4 illustrates an operational scenario of moving content between devices according to an implementation.

[0012] FIG. 5 illustrates an operational scenario of verifying a second device according to an implementation.

[0013] FIG. 6 illustrates an operational scenario of updating content on a wearable device based on the presence of a second device according to an implementation.

[0014] FIG. 7 illustrates a computing system to manage the display of content based on the positioning of devices according to an implementation.DETAILED DESCRIPTION

[0015] Wearable computing devices, such as Extended Reality (XR) devices, encompass a range of technologies that blend the physical and virtual worlds to create immersive user experiences. This category includes Virtual Reality (VR) devices, which fully immerse users in a computer-generated environment, and Augmented Reality (AR) or Mixed Reality (MR) devices, which overlay digital information and interactive virtual elements onto the user’s view of the real world. These devices are utilized in a variety of applications, from gaming and entertainment to professional training and remote collaboration, by enhancing how users perceive and interact with their surroundings.

[0016] Content is presented to the user through sophisticated display systems integrated into wearable devices, such as a head-mounted displays. These systems often employ either optical see-through methods, where digital elements are projected onto transparent lenses, or video see-through methods, where cameras capture the real world and display it on internal screens combined with virtual graphics. Both approaches allow digital content, such as application windows or notifications, to appear overlaid upon or anchored within the user’s physicalAtty Docket No. 0120-1011WO1environment, enabling interaction with virtual objects while maintaining awareness of the real world. However, technical problems arise in managing the display of content when a user of an XR device also attempts to use a secondary device, like a smartphone, which can obstruct the view and create a clumsy user experience.

[0017] In at least one technical solution, a wearable device, such as AR glasses or XR goggles, manages the display of content when a companion device (also referred to herein as a companion device) is detected. Using outward-facing cameras and computer vision, the wearable device determines when a second device, such as a smartphone, enters the user’s field of view. In response, the wearable can automatically take several actions to enhance the user experience, such as clearing the XR display, relocating interface elements, or creating a transparent passthrough area to allow the user to view the companion device’s screen. Furthermore, the wearable device can permit the transfer of content to the companion device. For example, a file or application active on the XR device can be automatically communicated and displayed on the companion device, ensuring a fluid transition between screens. This interaction can be customized based on the type of device detected, the content being viewed, and user preferences, and can be configured to only activate for devices recognized as belonging to the user.

[0018] In some implementations, a wearable device (e.g., an XR device) is configured to display first content for a user. The content can include interactive 3D environments, virtual tours, educational simulations, games, product visualizations, collaborative workspaces, training modules, medical imaging, artistic experiences, and augmented overlays with real-time data or navigation assistance. While displaying the first content, the XR device can be configured to determine when a second or companion device enters the field of view. This second device can include a smartphone, tablet, laptop, desktop computer, or other computing device. The field of view can refer to the angular extent of the observable world that is captured by a single camera onto its image sensor at a given moment. It can be defined by the horizontal and vertical angles that encompass the scene. In a multi-view camera system, each camera has its own field of view, and these individual fields of view can be partially or fully overlapping to provide comprehensive coverage of a scene or object. In some examples, the field of view captured by the device corresponds to the field of view of the user. The field-of-view of the device can be an outward-facing camera that captures images from the perspective of the user.Atty Docket No. 0120-1011WO1

[0019] In some implementations, the XR device can detect the second device using cameras, depth sensors, or infrared scanners. These sensors capture the environment in real-time, creating a spatial understanding of the environment through computer vision and spatial tracking algorithms. The device can process this data to identify devices, track their positions, and determine their spatial relationship with the user. Additionally, eye-tracking technology can determine where the user is looking, enabling the device to detect other devices within the user’s line of sight. This combination of hardware and software allows the device to detect when devices are within the user’s field of view.

[0020] Once a device is detected, the content displayed for the user can be updated. In some implementations, the XR device can be configured to remove at least a portion of the content displayed, permitting the user to view the second device. In some implementations, the XR device can adjust the translucency, allowing the second device to be visible to the user. In some implementations, the XR device can move at least a portion of the content on the XR display, permitting the user to view the companion device. In some implementations, at least a portion of the first content or files associated with the first content can be moved to the second device. For example, a file viewed on the XR device can be communicated to the second device for display. In some implementations, the formatting of the content can be adjusted to reflect the identified device. For example, the format on the XR device can differ from the format on the second device. In some implementations, the content moved to the second device can be determined based on the file or content type. For example, a configuration can permit movie files to move to the second device while productivity files are maintained on the XR device. The configuration can be defined by the user in some examples. Further, in some implementations, the content and / or files moved between the devices can be dictated based on the type of secondary device detected. For example, when a first companion device is detected, first content elements can be provided to the first companion device. In contrast, when a second companion device is detected, second content elements can be provided to that device.

[0021] In some implementations, the XR device can be configured to identify specific devices (e.g., devices that belong to the user). As a technical effect, if a device is visible in the user’s field of view but is not associated with the user, then no action may be taken by the XR device. However, if the device is related to the user, which can be determined by visual characteristics (e.g., device type or background), then the content can be changed as describedAtty Docket No. 0120-1011WO1herein. The association with the user can also be determined based on information exchanged via a wireless protocol between the devices, indicating the proximity of the companion device to the XR device. In some implementations, the XR device can display different options when a device (or a particular type of device) is identified. The options can permit the user to select the desired use of the companion device via gesture, controller, or another input mechanism. The options can include moving one or more content items to the companion device, using the companion device as intended (e.g., as a phone), permitting a passthrough to view the phone, or some other option. In some examples, based on the device or device type, a different amount of translucency can be provided. For example, when the user uses a computer, the content can be removed from the XR display or supplied with a first amount of translucency. However, when the user uses a smartphone, the content can be provided with a different level of translucency. The display on the XR device can be changed based on the companion device being used.

[0022] In some examples, the wearable XR device can include sensors, such as outwardfacing cameras, that capture information about the field of view. In some implementations, outward-facing sensors, such as cameras, depth sensors, and infrared scanners, can be configured to capture the user’s environment. This data is then processed by computer vision and spatial tracking algorithms. These algorithms can be configured (i.e., trained) to recognize the shape, size, and features of electronic devices, such as smartphones, tablets, or laptops. Additionally, in some examples, eye-tracking sensors can be used to confirm that the user is actively looking at the detected device, ensuring that the system only reacts when the user’s attention is focused on the secondary device.

[0023] In some implementations, once a device is detected, the system can perform more specific identification to determine if it is a companion device associated with the user. This can be done by analyzing visual characteristics in the captured image, such as the device type or a familiar background wallpaper. Alternatively, the wearable device can utilize a wireless protocol, such as Bluetooth, to communicate with nearby devices and confirm proximity. For example, a user wearing AR glasses might be viewing a virtual workspace. When they pick up their smartphone, the glasses’ outward-facing camera identifies the phone. The system then recognizes it as the user’s paired device (e.g., using Bluetooth or identifying individualized attributes associated with the device). For example, an XR device can identify a user’sAtty Docket No. 0120-1011WO1smartphone using an outward-facing camera that can capture the lock screen image of the user, indicating that the device is a companion device.

[0024] As used herein, determining that the second device is “associated with the user” refers to a verification process performed by the first device to establish a trusted relationship with the second device. This process can involve matching one or more identifying characteristics of the second device against a preconfigured profile associated with the user. In some implementations, these characteristics are identified visually using an outward-facing camera on the first device. For instance, the system may capture an image of the second device's screen and use image recognition to verify a specific wallpaper, lock screen image, or application icon layout previously registered by the user. In another visual -based approach, computer vision algorithms can identify physical attributes of the second device, such as its model, color, or a unique accessory, and match these attributes against a known device profile. Alternatively, or in combination, the association can be determined through wireless communication protocols. This can include verifying a pre-existing digital pairing (e.g., via Bluetooth), confirming that both devices are logged in the same user account or ecosystem, or detecting a wireless signal strength indicating close physical proximity. By successfully matching one or more of these characteristics, the first device can confirm the association before enabling content transfer or other interactions.

[0025] In some examples, when a companion device is detected in the field of view, the wearable XR device can modify its display to enable the user to see and interact with the second device. The system can achieve this by altering the virtual content being presented to the user. For example, it can remove a portion of the virtual content, move that content to a different area of the XR display, or make the virtual overlay translucent. This creates a passthrough region in the user’s vision, clearing their line of sight to the companion device’s screen without the user needing to remove the XR headset.

[0026] For instance, if a user is viewing a large virtual diagram projected in their smart glasses and then looks down at their smartphone to read a message, the glasses can automatically create a transparent window in the lower portion of the virtual display. This action clears the diagram from that specific area, allowing the user to see the phone screen clearly without having to close the application on the glasses. The rest of the virtual diagram can remain visible around the cleared space, maintaining the user’s context while enabling seamless interaction with theirAtty Docket No. 0120-1011WO1physical device. In alternative examples, the content can be moved to a different location on the XR display, provided in a different format, or modified in another manner, permitting the user to view the content on the second device.

[0027] In some implementations, when a secondary device is detected in the user’s field of view, the wearable XR device can utilize sensors, such as outward-facing cameras and depth sensors, to identify the companion device. The system may then verify whether the device is associated with the user, using visual characteristics such as the device type or background, or by exchanging information via a wireless protocol (e.g., identifier information via Bluetooth). Once the companion device is confirmed, the XR device determines which portion of the content to transfer. This selection can be based on the content or file type, user preferences, the specific application in use, or the type of companion device identified. The actual transfer of the selected content or its associated files can then be performed using a wireless communication protocol, such as WIFI or Bluetooth.

[0028] In some examples, the system can provide a wide variety of content to the companion device. This includes specific files like movies, text documents, or productivity files, as well as content associated with entire applications, such as a maps application or a web browser. The information transferred is the content itself, which may be reformatted better to suit the display and capabilities of the companion device. For example, content displayed as an augmented overlay on the XR device might be sent to a smartphone as a standard 2D application view. The system can be configured to move certain types of content automatically while keeping others on the primary XR device, allowing for a seamless context switch for the user. In some examples, the devices can communicate images, text, websites, application identifiers (e.g., game identifiers and game states), or other types of information.

[0029] For example, a user could be viewing turn-by-turn navigation directions as an overlay in their XR glasses while also listening to a music application. When the user looks down at their smartphone, the XR device’s camera identifies it as a recognized companion device. Based on a pre-set configuration, the system determines that the maps application content should be moved. The XR device then communicates the map data to the smartphone, which displays the full map interface. Meanwhile, the music application’s controls might remain on the XR display, allowing the user to interact with the map on their phone while still managing their music from the glasses. In some examples, the map data can include an identifier for the destination location, aAtty Docket No. 0120-1011WO1current route for the map application, or other data associated with continuing operations on the companion device.

[0030] In some implementations, the system can permit content to be passed or communicated from the companion device to the wearable device. For example, when the companion device leaves a field of view associated with the user (or the wearable device captured by the outward-facing camera), at least a portion of the content can be communicated to the wearable device for display. For instance, if the user moves a smartphone out of their field of view that is playing a video, the video can be communicated to the wearable device (i.e., an XR device) and displayed on the wearable device. In some examples, to communicate the content to the wearable device, the companion device can provide the file itself. In other implementations, the device can transmit a source of the file (e.g., a URL, a timestamp associated with the current state of the video, and the like), allowing the user to continue viewing the video. Similar operations can be performed for other types of content and media, including articles, games, or other content viewable by the user. Rather than providing all the content, the device can identify a source (e.g., game title) and state information associated with the content (e.g., for a game, the location of the user in the game or the display state).

[0031] In some implementations, the system can permit content to be passed or communicated from the companion device to the wearable device. This reverse transfer can be triggered when the companion device leaves the field of view of the first device. As used herein, "detecting that the second device has moved out of the field of view" refers to the process where the wearable device's outward-facing sensors no longer register the presence of the companion device within their operational range for a predetermined duration. This can occur, for example, when a user puts their smartphone down on a table or in their pocket. Upon this detection, the wearable device can initiate a communication handshake with the companion device over a wireless protocol to request the transfer of its current active content.

[0032] The content received from the companion device, referred to as the second content, can be the content itself or state information associated with it. For instance, if the user was watching a video on the companion device, the received content could be the video file or, more efficiently, a Uniform Resource Locator (URL) pointing to the video stream along with a precise timestamp of the last viewed frame. Similarly, if the user was reading an article, the companion device could transmit the article's URL and the user's current scroll position. Upon receiving thisAtty Docket No. 0120-1011WO1state information, the wearable device retrieves the content and displays it, seamlessly continuing the user's activity. The second content may also be reformatted to suit the display characteristics of the wearable device, such as converting a webpage into a floating virtual panel within the user's augmented view.

[0033] In some implementations, when a companion device is detected in the field of view of the wearable device, the system can determine whether the user intends to transfer at least a portion of the content to the companion device. This determination of user intent can be based on a combination of explicit user inputs and implicit contextual cues. As used herein, “user intent” refers to the inferred goal of the user to perform an action, such as transferring content, derived from sensor data. An explicit input can include a user gesture, such as a flicking motion of the hand from the location of the virtual content on the first device toward the physical location of the companion device, as tracked by motion sensors and outward-facing cameras on the wearable device. In some examples, this can be described as a gesture directed toward the second device. As used herein, “a gesture directed toward the second device” refers to a physical movement made by the user, detectable by one or more sensors of the first device, that is interpreted by the system as a command to initiate an interaction between the first device and the second device. The gesture is characterized by a vector or trajectory originating from or near a virtual content element displayed by the first device and terminating at or near the detected physical location of the second device. Additionally, in some cases, implicit cues can be derived from the user's gaze and the companion device's orientation. For example, eye-tracking sensors can determine if the user’s gaze remains fixed on the companion device for a duration exceeding a predetermined threshold, indicating focused attention.

[0034] Furthermore, the system can analyze the spatial relationship between the companion device and the user. The device’s orientation relative to the user’s line of sight is a significant factor; a device held perpendicular to the user's gaze, with its screen facing the user, is a strong indicator of an intent to interact. In contrast, a device held at an angle or positioned at the periphery of the user's view may not trigger a transfer. The system can be configured to compute an intent score by combining these factors, such as gesture recognition, gaze duration, and device orientation, and initiate the content transfer process only when this score surpasses a defined confidence threshold, thereby preventing accidental transfers and ensuring the action aligns with the user's implicit or explicit command.Atty Docket No. 0120-1011WO1

[0035] FIG. 1 illustrates a computing environment to manage displayed content on an XR device according to an implementation. Computing environment 100 includes user 110, XR device 130, user gaze 140, and user view 141. XR device 130 includes display 131, sensors 132, camera 133, application 134, and display application 126. XR device 130 further includes data 170, data 171, data 172, and an update 181. User view 141 is representative of the view for user 110 and includes companion device 175 and content 176. Content 176 is representative of the content displayed by XR device 130. Companion device 175 can comprise a smartphone, a tablet, a laptop, a desktop, or another computing device.

[0036] In at least one implementation, XR device 130 can display content 176 via display 131. For example, display 131 can display a video to user 110. During the display of content 176, XR device 130 and display application 126 can identify companion device 175 in the field of view for user 110 (also the field of view of XR device 130 captured via camera 133). In response to identifying companion device 175, display application 126 can provide at least a portion of content 176 to companion device 175. In response to receiving the portion of content, companion device 175 can display the content in the same or a different format. For example, when the user is viewing a video, the content can be transferred to companion device 175 and formatted for the display of companion device 175.

[0037] In computing environment 100, XR device 130 includes display 131, which is a screen or projection surface that presents immersive visual content to user 110, merging virtual elements with the real world or creating a completely virtual environment. XR device 130 further includes sensors 132, which include accelerometers, gyroscopes, magnetometers, depth sensors, infrared sensors, and proximity sensors. The sensors can be used to monitor the user’s physical movement, identify depth information for other objects, monitor eye movement, or perform other operations. XR device 130 also includes camera 133, which can capture the real or physical environment to overlay virtual objects (e.g., application interfaces) and track the movements of user 110 and their surroundings, enabling accurate interaction within the augmented or virtual space. In some examples, camera 133 can be positioned to capture an outward view of the physical world associated with the user’s gaze. Display 131 can be used to display information using optical see-through or video see-through methods. Optical see-through devices, such as AR glasses, feature transparent lenses that allow users to view the real world directly, with digital elements overlaid via projectors or waveguides. In contrast, video see-through devices, includingAtty Docket No. 0120-1011WO1VR headsets, can use external cameras to capture real-world video and display it on internal screens, combining it with virtual elements to create a seamless augmented view. Both methods can enable users to interact with digital content while remaining aware of their physical environment.

[0038] As illustrated in computing environment 100, user gaze 140 includes companion device 175 and content 176. In some technical solutions, camera 133 can be configured as an outward-facing camera that identifies objects within the user’s field of view (or the device’s field of view). When a potential companion device is determined, such as companion device 175, display application 126 can perform an action associated with content 176. In some implementations, the action can include removing at least a portion of the content from display 131 via an update to display 131. In some implementations, the content can be updated with a transparent region or passthrough, allowing the screen of companion device 175 to be visible to user 110. In some implementations, at least a portion of content 176 can be communicated and displayed on companion device 175. For example, if user 110 is working on a file and brings companion device 175 into the field of view, the file can be transferred to companion device 175 and viewed on the device. In some implementations, display application 126 can consider the device’s orientation relative to the field of view in determining whether to transfer the content between the devices. Thus, content can be moved when the device is more perpendicular, or a more significant portion of the screen is visible in the image captured by XR device 130.However, if companion device 175 is positioned to face away from the user’s gaze, content may not be transferred to the companion device.

[0039] In some implementations, display application 126 can be configured to determine whether the companion device is associated with the user. If the companion device is not associated with the user, no action may be taken in association with content 176. However, if the companion device is associated with the user, then an action can be taken in association with content 176. The action can include creating a passthrough to view the device, transferring at least a portion of the content to the device, or another action. In some implementations, display application 126 can be configured to identify devices associated with the user based on the device type, the device’s background, or another factor. The information can be stored for the XR device to determine when an available companion device enters the user’s field of view.Atty Docket No. 0120-1011WO1

[0040] For example, XR device 130 can be configured to verify companion device 175 by analyzing visual characteristics to determine if companion device 175 is associated with user 110. When a smartphone (e.g., companion device 175) enters the user’s field of view, camera 133 captures an image of the smartphone’s screen and identifies the background wallpaper. This captured wallpaper is then compared to a pre-stored image that the user has designated as belonging to their personal devices. If the captured background matches the stored image, XR device 130 verifies the smartphone as a trusted companion device. XR device 130 can then initiate actions such as transferring content or adjusting the user interface.

[0041] In some implementations, the XR device can be configured to determine what content to transfer based on the application on the device and / or the type of companion device identified. For example, content 176 can include content for a maps application and a music application. When XR device 130 identifies companion device 175, XR device 130 can determine that the maps application should be moved to the companion device, while the music application remains displayed by the XR device. Consequently, the content transferred to the device can depend on the application. In another example, XR device 130 can determine the identity of the companion device and select content accordingly. For example, when the companion device 175 comprises a first type of device, then a first portion of content can be moved to the companion device.However, when the companion device 175 is a second type, a second portion of the content can be moved to the companion device. In some implementations, the portion transferred from the XR device to the companion device is based on a combination of the identity of the companion device and the applications available to be moved to the identified companion device.

[0042] Although demonstrated as moving content to the companion device, the XR device can be configured to request and receive content from the companion device. For example, when the companion device leaves the field of view of the companion device, at least a portion of the content can be moved to the XR device. In some implementations, the content comprises content that was previously moved from the XR device to the companion device (e.g., a maps application). In some implementations, the content includes content that has not been previously displayed on the XR device. For example, the user can search a maps application on a smartphone. When the smartphone leaves the field of view of the XR device, the content associated with the map location can be moved to the XR device. In some examples, the moved content can be presented in a format that differs from the format of the companion device. ForAtty Docket No. 0120-1011WO1example, using the maps application, it can be offered as a map on the companion device and displayed as a list of directions on the XR device. The content can change configurations or formats when moved between the XR device and the companion device. The changed configuration can better support the display type provided by each device.

[0043] In some examples, content 176 can be updated to accommodate companion device 175 when companion device 175 enters user view 141 (user’s field of view). In some implementations, content 176 can be moved. In some implementations, content 176 can be resized. In some implementations, at least a portion of content 176 can be removed from display 131. In some implementations, content 176 can be modified and / or updated using any of the actions above. For example, a user wearing an XR headset might be viewing three large virtual displays arranged in their field of view for a work task. When they pick up their smartphone, the XR device’s outward-facing cameras detect the companion device. In response, the three virtual displays automatically shrink to become small icons and move to the top comers of the user’s vision, clearing the central viewing area. This creates a rectangular passthrough window in the center of the XR display, allowing the user to clearly see their physical smartphone and interact with it without having to remove the headset or manually close their virtual windows. As used herein, a passthrough can be defined as a mode that prioritizes the view of the physical environment over the virtual one, enabling a seamless context switch for the user. When activated, it removes or minimizes the XR content (content 176) to allow the user to focus on the display from companion device 175.

[0044] FIG. 2 illustrates method 200 of operating a wearable device to manage content according to an implementation. The steps of method 200 are indicated parenthetically in the paragraphs that follow. Examples are provided using elements from computing environment 100 of FIG. 1.

[0045] Method 200 includes causing (201) a display of first content on a first device. Method 200 further includes identifying (202) a companion device (also referred to as a second device) in a field of view of the first device. In some implementations, identifying the companion device comprises receiving an image captured by a camera of the first device and detecting the companion device in the image. In some implementations, the picture is captured via an outwardfacing camera on the XR device. In some examples, the first device can consider the device’s orientation relative to the user’s gaze and field of view to determine whether the user intends toAtty Docket No. 0120-1011WO1move at least a portion of the content to the companion device. For example, the XR device may not recognize the companion device when the display is positioned out of the user’s line of sight. A field of view can refer to the angular scope of an environment that is visible to a camera's sensor or to a user's eye. It can represent the portion of the world that is captured in an image and serves as the spatial context for interpreting actions such as gestures or gaze direction.

[0046] As used herein, the phrase “in a field of view of the first device” refers to the three-dimensional space from which the first device (e.g., a wearable device such as an XR headset) can capture sensor data. This space is defined by the operational range and angular coverage of its outward-facing sensors, including but not limited to cameras, depth sensors, and infrared scanners. A second device can be considered within this field of view when its physical presence is detected by these sensors and processed by computer vision or spatial tracking algorithms to determine its location, orientation, and potentially its type or state. This determination may require the second device to occupy a minimum pixel area in a captured image, be present for a threshold duration, or exhibit an orientation that makes its screen or other identifying features visible to the first device's sensors, thereby enabling the system to reliably identify it as a target for interaction.

[0047] In response to identifying the companion device, method 200 further includes determining (203) at least a portion of the first content to transfer to the companion device. The portion can be determined based on the content type (e.g., movie or text document), user preferences, or another relevant factor. For example, if content 176 included a movie, XR device 130 could select the movie to move to companion device 175. In some implementations, other content, such as a web browser, could remain displayed from XR device 130. Once the portion of the content is identified, method 200 further includes communicating (204) at least the portion of the first content to the companion device. The communication could use various protocols, including WIFI, Bluetooth, or another wireless connection.

[0048] In some implementations, the first device (i.e., XR device) can be configured to determine whether the companion device belongs to or is associated with the user. The determination can be based on the device type, the background on the device, proximity using a wireless protocol, or another factor. If the device is not associated with the user, the XR device will not change the content configuration. If the device is associated with the user, the XR device may communicate at least a portion of the content to the companion device.Atty Docket No. 0120-1011WO1

[0049] As used herein, determining that the second device is “associated with the user” refers to a verification process performed by the first device to establish a trusted relationship with the second device. This process can involve matching one or more identifying characteristics of the second device against a pre-configured profile linked to the user. In some implementations, these characteristics are identified visually using an outward-facing camera on the first device. For instance, the system may capture an image of the second device's screen and use image recognition to verify a specific wallpaper, lock screen image, or application icon layout previously registered by the user. In another visual -based approach, computer vision algorithms can identify physical attributes of the second device, such as its model, color, or a unique accessory, and match these attributes against a known device profile. Alternatively or in combination, the association can be determined through wireless communication protocols. This can include verifying a pre-existing digital pairing (e.g., via Bluetooth), confirming that both devices are logged into a common user account or ecosystem, or detecting a wireless signal strength that indicates close physical proximity. By successfully matching one or more of these characteristics, the first device can confirm the association before enabling content transfer or other interactions.

[0050] In some examples, the first device (i.e., XR device) can determine which content is available to a companion device through a multi-step process that considers the device’s identity, its capabilities, and user-defined configurations. In some implementations, the XR device utilizes its outward-facing cameras and sensors to visually identify a companion device within the user's field of view, recognizing characteristics such as its type (e.g., smartphone, laptop), screen size, and orientation. Additionally, the XR device can utilize wireless protocols such as Bluetooth or Wi-Fi to establish a connection, verify the device’s identity (ensuring it belongs to the user), and / or query the device for supported applications and file types. Based on this information, combined with user preferences or contextual awareness of the current application, the XR device determines which specific content or files are suitable for transfer.

[0051] For example, if the companion device is a smartphone, the XR device may determine that media files or simple documents are most suitable for use. When a user viewing a 3D architectural model on their XR glasses looks at their phone, the system could make a video walkthrough or a floor plan image related to the model available for transfer, while keeping the complex, interactive 3D model on the more powerful XR device. In another example, if theAtty Docket No. 0120-1011WO1companion device is a laptop, the XR device would identify its larger screen and keyboard as ideal for productivity. If the user is in a virtual meeting, the XR device could determine that a shared spreadsheet or text document is the best content to move to the laptop for easier editing, while the video feed of the meeting remains displayed on the XR glasses.

[0052] In some implementations, the XR device can be configured to take other actions associated with the displayed content when the companion device is identified. In some examples, the XR device can remove at least a portion of the content from its display in response to detecting the companion device. In some examples, the XR device can move at least a portion of the content to different parts of the display to make content on the companion device visible. In some examples, the device can allocate a region that permits the companion device to be visible to the user (i.e., a passthrough). In some examples, the operations can be provided in addition to or in place of moving content (or files) from the first XR device to the companion device.

[0053] FIG. 3 illustrates an operational scenario 300 of moving content between devices according to an implementation. Operational scenario 300 includes user perspective 312 at time 310 and time 311. Time 310 includes content 330, device 340, and movement 345. Time 311 includes updated content 332, content 334, and device 340. Operational scenario 300 further comprises step 320, step 322, and step 324 that represent operations that a wearable device, such as an XR device, can perform. In some examples, step 320, step 322, and step 324 can be performed by a computing system 700 of FIG. 7.

[0054] In operational scenario 300, at time 310, user perspective 312 includes content 330 that is displayed by a wearable XR device. While providing content 330, device 340 moves into the field of view of the user and the wearable device in user perspective 312. For example, a user can pick up a smartphone and rotate the screen to align it with their view. The wearable device can be configured to identify the device at step 320 and identify an intent to move content to the device at step 322.

[0055] In some implementations, a wearable device can identify a companion device (e g., device 340) using its built-in, outward-facing cameras and computer vision processes. These sensors can be configured to capture the environment in real-time, and spatial tracking algorithms process this data to detect when a companion device, like a smartphone or tablet, enters user perspective 312. For example, if a user wearing smart glasses is viewing a virtualAtty Docket No. 0120-1011WO1display and then picks up their smartphone, the camera on the glasses captures the phone’s appearance. The system’s software analyzes the image, recognizes the object as a smartphone, and can then trigger an action, such as moving content from the smart glasses to the companion device 340.

[0056] To ensure that the wearable device only interacts with approved devices, the wearable device can perform a verification step to determine if the detected companion device is associated with the user. This prevents the system from acting when another recognizable device is visible (e.g., another user’s phone). Verification can be accomplished in a few ways. The system can use visual characteristics, such as recognizing the specific device type or the unique background wallpaper on the device’s screen. Alternatively, or in addition, the wearable device and companion device can use a wireless protocol, such as Bluetooth, to exchange information that confirms their proximity and association with the same user account. If the device is not verified as belonging to the user, no action is taken.

[0057] Here, the wearable device recognizes device 340, and an intent is identified to move at least a portion of content 330 to device 340. In some implementations, the intent to move the content can be inferred based on the position of device 340 in user perspective 312. For example, the wearable device can infer intent based on the orientation of the device toward the user’s perspective (e.g., facing toward the user within a threshold degree). In some examples, the device can consider the position of the device in the user’s point of view or perspective, where the device 340 being centered may indicate that the user intends to shift content to the companion device. In contrast, if device 340 is near the edge of user perspective 312, the user’s point of view may indicate that the user does not intend to shift content. In some examples, the device can consider gestures or movements by the user to shift content from the wearable device to device 340 (e.g., a swiping gesture from displayed content toward the location of device 340). In some implementations, the device can utilize additional factors, such as the device type associated with device 340, the type of content displayed (content 330), or other information, to determine the user’s intent. In some examples, the user can use various combinations of user movement, content type, companion device type, and the like to determine whether the user intends to move content from the wearable XR device to the companion or secondary device.

[0058] When an intent is identified to move content, the wearable device can be configured to determine what portion of its currently displayed content should be moved. This selection canAtty Docket No. 0120-1011WO1be based on the type of content (e.g., a movie file), user-defined preferences, the specific application in use, or the identified type of the companion device. After the content is selected, the wearable device initiates a transfer by communicating the data or file to the companion device. This communication occurs over a wireless protocol, such as WIFI or Bluetooth, allowing the content to be sent from the wearable device and received by the companion device for display on its screen.

[0059] In some implementations, the wearable device can be configured to select a subset of the content. For example, the wearable device can execute a set of three applications. When the companion device is identified, the wearable device can select at least one application from the set and provide content associated with the application to the companion device. The companion device can use the information provided from the wearable device (e.g., smart glasses) to display a form of the content. In some examples, the wearable device can rearrange the remaining content. The rearranging of the content can include moving, resizing, or providing some other change to the content. In some implementations, the modification is used to provide a passthrough, permitting the user to view the content on the companion device.

[0060] In some implementations, the system can determine whether the user intends to transfer at least a portion of the content to the companion device. This determination of user intent can be based on a combination of explicit user inputs and implicit contextual cues. As used herein, “user intent” refers to the inferred goal of the user to perform an action, such as transferring content, derived from sensor data. An explicit input can include a user gesture, such as a flicking motion of the hand from the location of the virtual content on the first device toward the physical location of the companion device, as tracked by motion sensors and outward-facing cameras. Implicit cues can be derived from the user's gaze and the orientation of the companion device. For example, eye-tracking sensors can determine if the user's gaze remains fixed on the companion device for a duration exceeding a predetermined threshold, indicating focused attention.

[0061] Furthermore, the system can analyze the spatial relationship between the companion device and the user. The device’s orientation relative to the user’s line of sight is a significant factor; a device held perpendicular to the user's gaze, with its screen facing the user, is a strong indicator of an intent to interact. In contrast, a device held at an angle or positioned at the periphery of the user's view may not trigger a transfer. The system can be configured to computeAtty Docket No. 0120-1011WO1an intent score by combining these factors, such as gesture recognition, gaze duration, and device orientation, and initiate the content transfer process only when this score surpasses a defined confidence threshold, thereby preventing accidental transfers and ensuring the action aligns with the user's implicit or explicit command.

[0062] FIG. 4 illustrates an operational scenario 400 of moving content between devices according to an implementation. Operational scenario 400 includes user perspective 412 at time 410 and time 411. Time 410 includes content 430, content 434, device 440, and movement 445. Time 411 includes updated content 432 and device 440. Operational scenario 400 further comprises step 420, step 422, and step 424 that represent operations that a wearable device, such as an XR device, can perform. In some examples, step 420, step 422, and step 424 can be performed by a computing system 700 of FIG. 7.

[0063] In operational scenario 400, content 430 and content 434 are displayed by a wearable XR device and device 440. Device 440 can represent a smartphone or tablet that is viewable in user perspective 412 via passthrough to the user’s vision. In some examples, with optical passthrough, a wearable device can be configured to use transparent lenses that allow the user to view a secondary companion device directly by removing or adjusting the digital overlay. In contrast, video passthrough utilizes external cameras on the wearable device to capture a live video of the secondary device and display that feed on the internal screens.

[0064] Once displayed, the wearable device can identify, at step 420, movement 445 associated with device 440 that removes device 440 from user perspective 412. In response to the movement, the wearable device can identify content to be moved from device 440 to the wearable device at step 422. Once the content is selected, the wearable device can provide updated content 432 at step 424 based on the content information provided from device 440. In some implementations, when movement 445 is detected that removes device 440 from the user’s field of view or the field of view associated with the wearable device, the wearable device can be configured to request and receive content from the companion device. In some instances, the system can select content based on application type, content type, or another factor. In some examples, the system can choose content that was previously displayed on the wearable device before being moved to the companion device, effectively returning the task to the wearable’s display. Alternatively, the wearable can pull new content that the user was interacting with onAtty Docket No. 0120-1011WO1the companion device, allowing for a seamless transition of a task started on one device to be continued on another.

[0065] In some implementations, the content’s format can be adapted during the transfer to better suit the display capabilities of the wearable device. The system can reconfigure the content to present it in a more optimal layout for the wearable’s user interface. For example, information displayed in a graphically rich format on the companion device might be converted into a more concise, text-based format on the wearable device. This transition of format ensures the moved content is useful and appropriate for the context of the wearable display without requiring user intervention.

[0066] For example, a user could perform a search for a specific location using a maps application on their smartphone. When the user puts the smartphone away, moving the phone out of the field of view associated with the wearable device, the system can be configured to identify the map location content as the most recent task. This specific content related to the searched map location would then be selected for transfer to the wearable device.

[0067] In some examples, content from specific applications can be communicated to the wearable device. For example, a first application can be configured in association with the wearable device, while a second application may not be configured for the wearable device. Accordingly, content associated with the first application can be provided, while other content remains on the companion device.

[0068] FIG. 5 illustrates an operational scenario 500 of verifying a second device according to an implementation. Operational scenario 500 includes user perspective 512 at time 510 and time 511. Time 510 includes content 530, device 540, movement 545, and image 547. Time 511 includes updated content 532, device 540, content 534, and gesture 550. Operational scenario 500 further includes step 520, step 522, and step 524 that can be performed by a wearable device, such as an XR device. In some implementations, step 520, step 522, and step 524 can be performed by a computing system, such as computing system 700 of FIG. 7 described below.

[0069] In operational scenario 500, at time 510, user perspective 512 includes content 530 that is displayed by a wearable XR device. While providing content 530, device 540 moves into the field of view of the user and the wearable device in user perspective 512. For example, a user can pick up a smartphone and rotate the screen to align it with their view. The wearable deviceAtty Docket No. 0120-1011WO1can be configured to identify the device at step 520 and identify an intent to move content to the device at step 522.

[0070] In some implementations, a wearable device can identify a companion device (e.g., device 540) using its built-in, outward-facing cameras and computer vision processes. These sensors can be configured to capture the environment in real-time, and spatial tracking algorithms process this data to detect when a companion device, like a smartphone or tablet, enters user perspective 512. For example, if a user wearing smart glasses is viewing a virtual display and then picks up their smartphone, the camera on the glasses captures the phone’s appearance. The system’s software analyzes the image, recognizes the object as a smartphone, and can then trigger an action, such as moving content from the smart glasses to the companion device 540.

[0071] Here, in addition to identifying device 540 in user perspective 512, the wearable device can further be configured to perform a verification step 524 to confirm device 540 is associated with the user, preventing unintended interactions with other people’s devices (or unwanted devices). This verification can be achieved by analyzing visual characteristics within the captured image, such as recognizing a specific device model, a known background wallpaper on the device’s screen, or other unique visual cues. Additionally, the system can use the image to track the device’s position, orientation, and movement, determining if the screen is facing the user and is ready for interaction, which can be a prerequisite for triggering actions like transferring files or altering the user interface on the wearable device. In the example of operational scenario 500, the wearable device can identify image 547 on device 540 and compare the image to a known image of a user’s background. Based on the comparison, the wearable device can permit modifications associated with the content 530. In some examples, the wearable device can further provide wireless communication with device 540 to provide a verification, such as exchanging keys or other verification information.

[0072] Once device 540 is identified in association with the wearable device and the user, operational scenario 500 implements step 524, which updates content based on user intent. In some implementations, the user intent can be based on the user gaze transitioning to viewing device 540. For example, the user can execute a maps application on the wearable device and view directions to a coffee shop. When device 540 enters user perspective 512 and is verified, the user can transition their gaze to device 540, permitting the wearable device to identify theAtty Docket No. 0120-1011WO1user intent to move the content associated with the maps application. In response, the wearable device can communicate at least a portion of the content to device 540, permitting device 540 to display content associated with the map (e.g., an overhead view of the directions).

[0073] In some implementations, such as that demonstrated in operational scenario 500, once device 540 is verified, the user can provide a gesture, a motion with a controller, or another input to move content from the wearable device to device 540. For instance, while a user is watching a video from a media application displayed as content 530 on their XR glasses, they can perform gesture 550, such as a flicking or pushing motion with their hand, directed from the virtual video screen towards the physical location of device 540. The wearable device’s motion sensors and outward-facing cameras track this gesture and interpret it as a command to move the active content. In response, the system seamlessly transfers the video’s playback state to device 540, which immediately begins displaying the video as new content 534, while the virtual screen on the XR device is updated to content 532, either by minimizing, closing, or becoming transparent to allow an unobstructed view of the companion device. In some implementations, updated content 532 can remove the application on the device, while the application is transitioned to content 534 on device 540.

[0074] Although demonstrated as a movement of content to device 540, similar operations can be performed to move content from device 540 to the display of the wearable device. For example, a user browsing a news article on their smartphone can simply put the device down, causing it to leave the field of view of their XR glasses. Upon detecting this movement, the wearable device communicates with the smartphone to receive the article’s URL and the user’s current scroll position. The XR glasses then seamlessly display the article as a floating virtual panel, allowing the user to continue reading from the exact point they left off without any manual intervention, with the content automatically reformatted for optimal viewing within the augmented reality environment. In some examples, the content displayed by the companion device can also be removed in response to the user’s request.

[0075] FIG. 6 illustrates an operational scenario 600 of updating content on a wearable device based on the presence of a second device according to an implementation. Operational scenario 600 includes user perspective 612 at time 610 and time 611. Time 610 further includes content 630, device 640, movement 645, and image 647. Time 611 further includes content 631 and passthrough 650. Operational scenario 500 further comprises step 620, step 622, and stepAtty Docket No. 0120-1011WO1624 that a wearable device, such as an XR device, can perform. In some implementations, step 620, step 622, and step 624 can be performed by a computing system, such as computing system 700 of FIG. 7 described below.

[0076] In operational scenario 600, at time 610, content 630 is displayed by a wearable device in user perspective 612. While displaying content 630, the user raises device 640, making it visible in the field of view of both the user and the wearable device. At step 620, the wearable device can be configured to identify movement 645 and device 640 within user perspective 612. Once identified, the wearable device can be configured to verify device 640 at step 622. In some implementations, the verification can be based on wireless communication (e.g., exchange of passkeys). In some implementations, such as that demonstrated in operational scenario 600, the wearable device can be configured to capture an image of device 640 and compare the information in the image to that of a device associated with the user. For example, the wearable device can compare the background on a smartphone to a known image of the user’s background. Once verified, the wearable device can update content 630 to content 631 to provide passthrough 650 at step 624.

[0077] In some implementations, when an outward-facing camera or other sensor detects a companion device, such as a smartphone, within the user’s field of view, the system modifies the user interface to create an unobstructed view of that device. This modification can involve clearing a specific portion of the XR display, relocating virtual windows to the periphery of the user’s vision, or adjusting the opacity of virtual elements to make them translucent. The result is a dedicated passthrough window that allows the user to seamlessly view and interact with their companion device’s physical screen without removing the XR headset, thus maintaining context within the immersive environment.

[0078] In some implementations, the technical implementation of this passthrough can vary based on the XR device’s display technology. For devices using an optical see-through system, such as AR glasses with transparent lenses, the passthrough is created by simply deactivating or dimming the projectors or waveguides in the specific region corresponding to the companion device’s location. This allows the user to view the physical device directly through the lens. In contrast, for devices using a video see-through system, such as in VR and MR headsets, the passthrough can be achieved by rendering a live video feed from the outward-facing cameras onto a portion of the internal display. The video window shows the real-world view of theAtty Docket No. 0120-1011WO1companion device, effectively creating a portal through the virtual environment to the physical world.

[0079] In some implementations, although not depicted in operational scenario 600, content can be moved between the wearable device and the second device 640. The content can include fdes like movies and documents, content from entire applications such as a web browser, and data like images, websites, or application identifiers and states. The system can transfer the content itself, which may be reformatted to suit the companion device’s display, allowing for a seamless transition for the user.

[0080] For example, consider a user watching a film on their XR glasses, with the movie displayed on a large virtual screen in their living room (e.g., content 631). Midway through the film, the user decides they would rather watch on their smartphone. When the user picks up their smartphone and brings it into their field of view, the outward-facing cameras on the XR glasses immediately detect the device. To ensure the device belongs to the user and prevent accidental transfers to nearby devices, the system can initiate a two-part verification process. First, an algorithm can capture an image of the smartphone’s lock screen and compare it to a pre-stored image designated by the user as their trusted background, confirming a visual match.

[0081] Further, in addition to or in place of the image comparison, the XR glasses can send a low-energy Bluetooth handshake request to the smartphone, which, upon receiving a valid response, confirms the device’s proximity and digital identity. Once the smartphone is verified, the wearable device identifies the active content as a video file and determines it is suitable for transfer. The wearable device then communicates the video’s source URL and the current timestamp (e.g., 1 hour, 12 minutes, and 34 seconds) to another application on the smartphone. The smartphone can be configured to execute a video player, queue the stream from the source, and begin playback from that exact moment. Concurrently, the XR glasses pause the local playback and fade or remove the large virtual screen, allowing the user to see their physical smartphone screen without any virtual obstruction, ensuring a seamless and uninterrupted viewing experience as they switch between devices.

[0082] FIG. 7 illustrates a computing system 700 to manage the display of content based on the positioning of devices according to an implementation. Computing system 700 is representative of any computing system or systems with which the various operational architectures, processes, scenarios, and sequences disclosed herein can be implemented toAtty Docket No. 0120-1011WO1display content across multiple devices. Computing system 700 may represent a wearable computing device, such as an XR device or smart glasses. Computing system 700 can include multiple computing devices in some examples, such as a wearable device and a companion device (e.g., a smartphone or tablet). Computing system 700 includes storage system 745, processing system 750, communication interface 760, and input / output (I / O) device(s) 770. Processing system 750 is operatively linked to communication interface 760, I / O device(s) 770, and storage system 745. In some implementations, communication interface 760 and / or I / O device(s) 770 may be communicatively linked to storage system 745. Computing system 700 may further include other components, such as a battery and enclosure, that are not shown for clarity.

[0083] Communication interface 760 comprises components that communicate over communication links, such as network cards, ports, radio frequency, processing circuitry and software, or some other communication devices. Communication interface 760 may be configured to communicate over metallic, wireless, or optical links. Communication interface 760 may be configured to use Time Division Multiplex (TDM), Internet Protocol (IP), Ethernet, optical networking, wireless protocols, communication signaling, or some other communication format, including combinations thereof. Communication interface 760 may be configured to communicate with external devices, such as servers, user devices, or some other computing device.

[0084] VO device(s) 770 may include computer peripherals that facilitate the interaction between the user and computing system 700. Examples of VO device(s) 770 may include keyboards, mice, trackpads, monitors, displays, printers, cameras, microphones, external storage devices, and the like.

[0085] Processing system 750 comprises microprocessor circuitry (e.g., at least one processor) and other circuitry that retrieves and executes operating software from storage system 745. Storage system 745 may include volatile and nonvolatile, removable, and non-removable media implemented in any method or technology for information storage, such as computer-readable instructions, data structures, program modules, or other data. Storage system 745 may be implemented as a single storage device, but may also be implemented across multiple storage devices or sub-systems. Storage system 745 may comprise additional elements, such as a controller to read operating software from the storage systems. Examples of storage media (alsoAtty Docket No. 0120-1011WO1referred to as computer-readable storage media) include random access memory, read-only memory, magnetic disks, optical disks, and flash memory, as well as any combination or variation thereof or any other type of storage media. In some implementations, the storage media may be non-transitory. In some instances, at least a portion of the storage media may be transitory. In no case is the storage media a propagated signal.

[0086] Processing system 750 is typically mounted on a circuit board that may hold the storage system. The operating software of storage system 745 comprises computer programs, firmware, or another form of machine-readable program instructions. The operating software of storage system 745 comprises display application 724. The operating software on storage system 745 may include an operating system, utilities, drivers, network interfaces, applications, or other types of software. When read and executed by processing system 750, the operating software on storage system 745 directs computing system 700 to operate as described in the previously described FIGs 1-6.

[0087] In at least one implementation, display application 724 directs processing system 750 to display content on a first device. In some examples, the first device includes a wearable device, such as an XR device or smart glasses. The content can include an article, a video, a webpage, or some other content. Display application 724 further directs processing system 750 to identify a second device in a field of view of the first device and, in response to identifying the second device, determine at least a portion of the content to transfer to the second device. Once determined, display application 724 can direct processing system 750 to communicate at least the portion of the content to the second device.

[0088] For example, a user wearing AR glasses could be browsing a gallery of vacation photos, which appear as floating virtual windows in their living room. When the user turns their gaze towards their smart TV, the outward-facing cameras on the wearable device and image processing applications can detect the TV’s distinct shape and screen. Recognizing it as a trusted companion device on the same WIFI network, the system projects a “Cast to TV” icon over the physical television in the user’s augmented view. With a user gesture (e.g., a swipe toward the TV), the user selects the icon, prompting the AR glasses to wirelessly transmit the photo gallery content to the smart TV, which then displays the photos on its large screen for everyone in the room to see. Additionally, the virtual windows in the user’s glasses can be minimized or removed.Atty Docket No. 0120-1011WO1

[0089] Below are example clauses associated with the present disclosure. The described clauses should not be considered exhaustive.

[0090] Clause 1. A method comprising: displaying content on a first device; identifying a second device in a field of view of the first device; in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

[0091] Clause 2. The method of clause 1 further comprising: determining that the second device is associated with a user of the first device, wherein determining at least the portion of the content to transfer to the second device occurs in response to determining that the second device is associated with the user.

[0092] Clause 3. The method of clause 2, wherein determining that the second device is associated with the user of the first device comprises: identifying second content on a display of the second device; and determining that the second device is associated with the user of the first device based on the second content.

[0093] Clause 4. The method of any one of the preceding clauses, wherein the portion comprises a first portion, and the method further comprises: determining a second portion of the content to be removed on the first device; and removing the second portion from a display of the first device.

[0094] Clause 5. The method of any one of the preceding clauses, wherein identifying the second device in the field of view of the first device comprises: receiving an image captured by a camera of the first device; and identifying the second device in the image.

[0095] Clause 6. The method of any one of the preceding clauses further comprising: determining a display capability of the second device; and reformatting the portion of the content based on the display capability of the second device.

[0096] Clause 7. The method of any one of the preceding clauses, wherein the determining and communicating occur in further response to receiving a user input, the user input comprising a gesture directed toward the second device.

[0097] Clause 8. The method of any one of the preceding clauses, further comprising: detecting that the second device has moved out of the field of view of the first device; in response to detecting that the second device has moved out of the field of view, receiving, at theAtty Docket No. 0120-1011WO1first device, second content from the second device; and displaying the second content on the first device.

[0098] Clause 9. A system comprising: a computer-readable storage medium; at least one processor operatively coupled to the computer-readable storage medium; and program instructions stored on the computer-readable storage medium that, when executed by the at least one processor, direct the at least one processor to perform a method, the method comprising: display content on a first device; identifying a second device in a field of view of the first device; in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

[0099] Clause 10. The system of clause 9, wherein the method further comprises: determining that the second device is associated with a user of the first device, wherein determining at least the portion of the content to transfer to the second device occurs in response to determining that the second device is associated with the user.

[0100] Clause 11. The system of clause 10, wherein determining that the second device is associated with the user of the first device comprises: identifying second content on a display of the second device; and determining that the second device is associated with the user of the first device based on the second content.

[0101] Clause 12. The system of any one of clauses 9 to 11, wherein the portion comprises a first portion, and the method further comprises: determining a second portion of the content to be removed on the first device; and removing the second portion from a display of the first device.

[0102] Clause 13. The system of any one of clauses 9 to 12, wherein identifying the second device in the field of view of the first device comprises: receiving an image captured by a camera of the first device; and identifying the second device in the image.

[0103] Clause 14. The system of any one of clauses 9 to 13, wherein the first device comprises a wearable device for a user, and wherein the method further comprises: identifying a location associated with the second device; and updating the content displayed on the first device based on the location associated with the second device.

[0104] Clause 15. The system of any one of clauses 9 to 14, wherein updating the content displayed on the first device includes moving a second portion of the content displayed on the first device.Atty Docket No. 0120-1011WO1

[0105] Clause 16. The system of any one of clauses 9 to 15, wherein the determining and communicating occur in further response to receiving a user input, the user input comprising a gesture directed toward the second device.

[0106] Clause 17. A computer-readable storage medium with program instructions stored thereon that, when executed by at least one processor, direct the at least one processor to perform a method, the method comprising: display content on a first device; identifying a second device in a field of view of the first device; in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

[0107] Clause 18. The computer-readable storage medium of clause 17, wherein the method further comprises: determining that the second device is associated with a user of the first device, wherein determining at least the portion of the content to transfer to the second device occurs in response to determining that the second device is associated with the user.

[0108] Clause 19. The computer-readable storage medium of clause 18, wherein determining that the second device is associated with the user of the first device comprises: identifying second content on a display of the second device; and determining that the second device is associated with the user of the first device based on the second content.

[0109] Clause 20. The computer-readable storage medium of clause 18, wherein determining that the second device is associated with the user of the first device comprises: identifying a device type associated with the second device; and determining that the second device is associated with the user of the first device based on the device type.

[0110] In accordance with aspects of the disclosure, implementations of various techniques and methods described herein may be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. Implementations may be implemented as a computer program product (e.g., a computer program tangibly embodied in an information carrier, a machine-readable storage device, a computer-readable medium, a tangible computer-readable medium), for processing by, or to control the operation of, data processing apparatus (e.g., a programmable processor, a computer, or multiple computers). In some implementations, a tangible computer-readable storage medium may be configured to store instructions that when executed cause a processor to perform a process. A computer program, such as the computer program(s) described above, may be written in any form of programmingAtty Docket No. 0120-1011WO1language, including compiled or interpreted languages, and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may be deployed to be processed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.

[0111] While certain features of the described implementations have been illustrated as described herein, many modifications, substitutions, changes, and equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the scope of the implementations. They have been presented by way of example only, not limitation, and various changes in form and details may be made. Any portion of the apparatus and / or methods described herein may be combined in any combination, except mutually exclusive combinations. The implementations described herein can include various combinations and / or sub-combinations of the functions, components and / or features of the different implementations described.

[0112] It will be understood that, in the foregoing description, when an element is referred to as being on, connected to, electrically connected to, coupled to, or electrically coupled to another element, it may be directly on, connected or coupled to the other element, or one or more intervening elements may be present. In contrast, when an element is referred to as being directly on, directly connected to or directly coupled to another element, there are no intervening elements present. Although the terms directly on, directly connected to, or directly coupled to may not be used throughout the detailed description, elements that are shown as being directly on, directly connected or directly coupled can be referred to as such. The claims of the application, if any, may be amended to recite exemplary relationships described in the specification or shown in the figures.

[0113] As used in this specification, a singular form may, unless definitively indicating a particular case in terms of the context, include a plural form. Spatially relative terms (e.g., over, above, upper, under, beneath, below, lower, and so forth) are intended to encompass different orientations of the device in use or operation in addition to the orientation depicted in the figures. In some implementations, the relative terms above and below can, respectively, include vertically above and vertically below. In some implementations, the term adjacent can include laterally adjacent to or horizontally adjacent to.

Claims

Atty Docket No. 0120-1011WO1WHAT IS CLAIMED IS:

1. A method comprising:displaying content on a first device;identifying a second device in a field of view of the first device;in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

2. The method of claim 1 further comprising:determining that the second device is associated with a user of the first device, wherein determining at least the portion of the content to transfer to the second device occurs in response to determining that the second device is associated with the user.

3. The method of claim 2, wherein determining that the second device is associated with the user of the first device comprises:identifying second content on a display of the second device; anddetermining that the second device is associated with the user of the first device based on the second content.

4. The method of any one of the preceding claims, wherein the portion comprises a first portion, and the method further comprises:determining a second portion of the content to be removed on the first device; and removing the second portion from a display of the first device.

5. The method of any one of the preceding claims, wherein identifying the second device in the field of view of the first device comprises:receiving an image captured by a camera of the first device; andidentifying the second device in the image.

6. The method of any one of the preceding claims further comprising:Atty Docket No. 0120-1011WO1determining a display capability of the second device; andreformatting the portion of the content based on the display capability of the second device.

7. The method of any one of the preceding claims, wherein the determining and communicating occur in further response to receiving a user input, the user input comprising a gesture directed toward the second device.

8. The method of any one of the preceding claims, further comprising:detecting that the second device has moved out of the field of view of the first device; in response to detecting that the second device has moved out of the field of view, receiving, at the first device, second content from the second device; anddisplaying the second content on the first device.

9. A system comprising:a computer-readable storage medium;at least one processor operatively coupled to the computer-readable storage medium; and program instructions stored on the computer-readable storage medium that, when executed by the at least one processor, direct the at least one processor to perform a method, the method comprising:display content on a first device;identifying a second device in a field of view of the first device;in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

10. The system of claim 9, wherein the method further comprises:determining that the second device is associated with a user of the first device, wherein determining at least the portion of the content to transfer to the second device occurs in response to determining that the second device is associated with the user.Atty Docket No. 0120-1011WO111. The system of claim 10, wherein determining that the second device is associated with the user of the first device comprises:identifying second content on a display of the second device; anddetermining that the second device is associated with the user of the first device based on the second content.

12. The system of any one of claims 9 to 11, wherein the portion comprises a first portion, and the method further comprises:determining a second portion of the content to be removed on the first device; and removing the second portion from a display of the first device.

13. The system of any one of claims 9 to 12, wherein identifying the second device in the field of view of the first device comprises:receiving an image captured by a camera of the first device; andidentifying the second device in the image.

14. The system of any one of claims 9 to 13, wherein the first device comprises a wearable device for a user, and wherein the method further comprises:identifying a location associated with the second device; andupdating the content displayed on the first device based on the location associated with the second device.

15. The system of any one of claims 9 to 14, wherein updating the content displayed on the first device includes moving a second portion of the content displayed on the first device.

16. The system of any one of claims 9 to 15, wherein the determining and communicating occur in further response to receiving a user input, the user input comprising a gesture directed toward the second device.Atty Docket No. 0120-1011WO117. A computer-readable storage medium with program instructions stored thereon that, when executed by at least one processor, direct the at least one processor to perform a method, the method comprising:display content on a first device;identifying a second device in a field of view of the first device;in response to identifying the second device in the field of view of the first device, determining at least a portion of the content to transfer to the second device; and communicating at least the portion of the content to the second device.

18. The computer-readable storage medium of claim 17, wherein the method further comprises:determining that the second device is associated with a user of the first device, wherein determining at least the portion of the content to transfer to the second device occurs in response to determining that the second device is associated with the user.

19. The computer-readable storage medium of claim 18, wherein determining that the second device is associated with the user of the first device comprises:identifying second content on a display of the second device; anddetermining that the second device is associated with the user of the first device based on the second content.

20. The computer-readable storage medium of claim 18, wherein determining that the second device is associated with the user of the first device comprises:identifying a device type associated with the second device; anddetermining that the second device is associated with the user of the first device based on the device type.

Images