Mounting and dismounting routine

Abstract

In one implementation, a method of executing a routine is performed by a head-mounted device having one or more processors and a non-transitory memory. The method includes detecting a trigger indicating that a user has mounted or dismounted the head-mounted device. The method includes, in response to detecting the trigger, executing a routine that includes sending a request to change a state of the remote device from a first state to a second state.

Description

[0001] Cross Reference to Related Applications

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 677,744, filed July 31, 2024, which is hereby incorporated by reference in its entirety. TECHNICAL FIELD

[0003] The present disclosure generally relates to systems, methods, and devices that trigger routines based on detecting mounting and / or unmounting of a head-mounted device. BACKGROUND

[0004] In various implementations, a user can program a routine to be performed in response to detecting a trigger. The routine can include sending a request to a smart device to change a state. BRIEF DESCRIPTION OF DRAWINGS

[0005] To enable a person of ordinary skill in the art to understand the present disclosure, some aspects of exemplary implementations can be described in more detail by referring to the drawings, in which:

[0006] Figure 1 is a block diagram of an example operating environment according to some implementations.

[0007] Figures 2A to 2I shows a user view during various time periods according to some implementations.

[0008] Figure 3 is a flowchart representation of a method of triggering a routine according to some implementations.

[0009] Figure 4 is a block diagram of an example controller according to some implementations.

[0010] Figure 5 is a block diagram of an example electronic device according to some implementations.

[0011] According to common practice the various features illustrated in the drawings can not be drawn to scale. Accordingly, the dimensions of the various features can be arbitrarily expanded or reduced for the clarity of presentation. In addition, some of the drawings can not depict all of the components of a given system, method or device. Finally, like reference numerals can be used to denote like features throughout the specification and figures. SUMMARY

[0012] Various implementations disclosed herein include devices, systems, and methods for performing a routine. In various implementations, the method is performed by a head-mounted device having one or more processors and non-transitory memory. The method includes detecting a trigger that indicates that a user has mounted or unmounted the head-mounted device. The method includes, in response to detecting the trigger, performing a routine that includes sending a request to change a state of a remote device from a first state to a second state.

[0013] According to some implementations, a device includes one or more processors, non-transitory memory, and one or more programs; the one or more programs are stored in the non-transitory memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing or causing performing any of the methods described herein. According to some implementations, a non-transitory computer-readable storage medium stores instructions that, when executed by one or more processors of a device, cause the device to perform or cause performing any of the methods described herein. According to some implementations, a device includes one or more processors, non-transitory memory, and means for performing or causing performing any of the methods described herein. DETAILED DESCRIPTION

[0014] Many details are described to provide a thorough understanding of example implementations shown in the drawings. It will be apparent, however, that other effective aspects and / or variants can be practiced without some or all of these details. In other instances, well-known systems, methods, components, devices and circuits have not been described in detail in order to avoid obscuring the described example implementations.

[0015] As described above, in various implementations, a user can program a device to perform a routine in response to detecting a trigger. Performing the routine can include, for example, sending a request to a smart device to change a state, play audio, or display information. As discussed herein, the routine is performed by the head-mounted device in response to detecting that the user has mounted or unmounted the head-mounted device. Specifically, mounting includes placing the head-mounted device on the user’s head, and unmounting includes removing the head-mounted device from the user’s head. In various implementations, mounting the head-mounted device can be referred to as putting on (or donning) the head-mounted device, and unmounting the head-mounted device can be referred to as taking off (or doffing) the head-mounted device.

[0016] Figure 1is a block diagram of an example operating environment 100 according to some implementations. Although relevant features are illustrated, one of ordinary skill in the art, in light of the disclosure, will appreciate that various other features are not illustrated for the sake of brevity and so as not to obscure more pertinent aspects of the example implementations disclosed herein. To that end, by way of non-limiting example, the operating environment 100 includes a controller 110 and an electronic device 120.

[0017] In some implementations, the controller 110 is configured to manage and coordinate the user’s XR experience. In some implementations, the controller 110 includes a suitable combination of software, firmware, and / or hardware. The controller 110 is described in greater detail below with respect to Figure 4 The controller 110 is described in greater detail. In some implementations, the controller 110 is a computing device that is in a local or remote location with respect to the physical environment 105. For example, the controller 110 is a local server that is located within the physical environment 105. As another example, the controller 110 is a remote server (e.g., a cloud server, a central server, etc.) that is located outside of the physical environment 105. In some implementations, the controller 110 is communicatively coupled with the electronic device 120 via one or more wired or wireless communication channels 144 (e.g., Bluetooth, IEEE 802. l lx, IEEE 802.16x, IEEE 802.3x, etc.). As another example, the controller 110 is included within the housing of the electronic device 120. In some implementations, the functionality of the controller 110 is provided by and / or combined with the electronic device 120.

[0018] In some implementations, the electronic device 120 is configured to provide an XR experience to a user. In some implementations, the electronic device 120 includes a suitable combination of software, firmware, and / or hardware. In accordance with some implementations, the electronic device 120 presents XR content to the user via the display 122 while the user is physically present within the physical environment 105, which includes the table 107 that is within the field of view 111 of the electronic device 120. In this regard, in some implementations, the user holds the electronic device 120 in one or both of his / her hands. In some implementations, while providing the XR content, the electronic device 120 is configured to display an XR object (e.g., the XR cylinder 109) and to enable video pass-through of the physical environment 105 (e.g., including the representation 117 of the table 107) on the display 122. The electronic device 120 is described in greater detail below with respect to Figure 5 The electronic device 120 is described in greater detail.

[0019] In accordance with some implementations, the electronic device 120 provides an XR experience to a user while the user is virtually and / or physically present within the physical environment 105.

[0020] In some implementations, the user wears the electronic device 120 on his / her head. For example, in some implementations, the electronic device includes a head-mounted system (HMS), a head-mounted device (HMD), or a head-mounted enclosure (HME). Accordingly, the electronic device 120 includes one or more XR displays that are disposed to display XR content. For example, in various implementations, the electronic device 120 encloses the user’s field of view. In some implementations, the electronic device 120 is a handheld device (such as a smartphone or a tablet computer) that is configured to present XR content, and the user no longer wears the electronic device 120 but instead holds the device with the display facing the user’s field of view and the camera facing the physical environment 105. In some implementations, the handheld device can be placed within an enclosure that can be worn on the user’s head. In some implementations, the electronic device 120 is replaced with an XR pod, enclosure, or chamber that is configured to present XR content, in which the user no longer wears or holds the electronic device 120.

[0021] Figures 2A to 2I A physical environment 200 of a bedroom is shown during a sequence of time periods. In various implementations, each time period is an instant, a fraction of a second, a few seconds, a few hours, a few days, or any length of time. The physical environment 200 includes a bed 211, a dresser 212, a light 213, a speaker 214, a window 215, and blinds 216 on the window 215.

[0022] Figure 2A The physical environment 200 is shown during a first time period. During the first time period, the light 213 is in an “off’ state, and the blinds 216 are in a “closed” state.

[0023] Figure 2B The physical environment 200 is shown during a second time period that is after the first time period. Between the first time period and the second time period, the user has installed a head-mounted device 217. Accordingly, during the second time period, the physical environment 200 includes the head-mounted device 217 that presents an XR environment 201 based on the physical environment 200.

[0024] The XR environment 201 includes a plurality of objects, including one or more real objects (e.g., a bed 211, a dresser 212, a lamp 213, a speaker 214, a window 215, and blinds 216) and one or more virtual objects (e.g., a virtual clock 221 and a virtual confirmation window 222). In various implementations, certain objects, such as real objects and the virtual confirmation window 222, are rendered at a certain location in the XR environment 201, e.g., at a location defined by three coordinates in a three-dimensional (3D) XR coordinate system. Thus, as the head-mounted device 217 moves (e.g., changes position and / or orientation) in the XR environment 201, the objects move on the display of the head-mounted device, but maintain their (possibly time-dependent) position in the XR environment 201. In response to the motion of the head-mounted device, such virtual objects that move on the display but maintain their position in the XR environment 201 are referred to as world-locked objects. In various implementations, certain virtual objects, such as the virtual clock 221, are displayed at a position on the display such that, as the electronic device moves in the XR environment 201, the object is stationary on the display of the electronic device. In response to the motion of the head-mounted device, such virtual objects that maintain their position on the display are referred to as head-locked or display-locked objects.

[0025] During the second time period, in response to detecting that the user has installed the head-mounted device 217, the head-mounted device performs an installation routine. The installation routine includes displaying the virtual confirmation window 222. The virtual confirmation window 222 includes a “Yes” affordance 231 for continuing the installation routine and a “No” affordance 232 for stopping the installation routine. During the second time period, the user selects the “Yes” affordance 231. In various implementations, the user selects the “Yes” affordance 231 by gazing at the “Yes” affordance and performing a gesture (e.g., touching the thumb and index finger). In various implementations, the user selects the “Yes” affordance 231 by verbally saying “Yes.”

[0026] Figure 2C The physical environment 200 during a third time period after the second time period is shown. During the third time period, in response to detecting that the user selected the “Yes” affordance 231, the head-mounted device 217 continues the installation routine by sending a command to the lamp 213 to change to an “on” state, sending a command to the blinds 216 to change to an “open” state, and playing audio indicating the current weather state (shown in the third time period by the optionally displayed audio playback indicator 299). Figure 2C Thus, during the third time period, the lamp 213 is in the “on” state and the blinds 216 are in the “open” state.

[0027] Although Figure 2BA virtual confirmation window 222 is shown, but in various implementations, the installation routine does not include display of the virtual confirmation window 222. Thus, in various implementations, in response to detecting that the user has installed the head-mounted device 217, the head-mounted device 217 automatically sends a command to the light 213 to change to the "on" state, sends a command to the blinds 216 to change to the "open" state, and plays audio indicating the current weather state. In various implementations, the head-mounted device 217 audibly requests confirmation of performing the installation routine, rather than the virtual confirmation window 222.

[0028] Figure 2D The physical environment 200 during a fourth time period after the third time period is shown. During the fourth time period, the head-mounted device 217 detects a user speech requesting the current inventory state (indicated by the optionally displayed audio detection indicator 298 in Figure 2D .

[0029] Figure 2E The physical environment 200 during a fifth time period after the fourth time period is shown. During the fifth time period, the head-mounted device 217 plays audio indicating the current inventory state (as indicated by the optionally displayed audio playback indicator 299) and additional audio suggesting a change to the installation routine. In various implementations, the head-mounted device suggests changing the installation routine based on user actions that are frequently performed soon after installing the head-mounted device 217. In response to the user confirming the change, the head-mounted device 217 changes the installation routine to include playing audio indicating the current inventory state.

[0030] Figure 2F The physical environment 200 during a sixth time period after the fifth time period is shown. During the sixth time period, the head-mounted device 217 determines a confidence that the user will soon dismount the head-mounted device 217. In various implementations, the head-mounted device 217 determines the confidence based on the time of day (e.g., the confidence is higher if it is late in the day or a time of day when the user typically dismounts the head-mounted device 217). In various implementations, the head-mounted device 217 determines the confidence based on location (e.g., the confidence is higher if the user returns to the bedroom after being absent for a long period of time). In various implementations, the head-mounted device 217 determines the confidence based on data received from other devices (e.g., the confidence is higher if the data includes an indication that the user has set a phone to charge or dismounted a watch).

[0031] In various implementations, the head-mounted device 217 triggers the uninstall routine before detecting that the user has uninstalled the head-mounted device if the confidence breaches the threshold. In various implementations, the uninstall routine includes displaying a virtual confirmation window similar to the virtual confirmation window 222 of the install routine. However, in various implementations, the uninstall routine does not include displaying a virtual confirmation window.

[0032] Figure 2G The physical environment 200 is shown during a seventh time period after the sixth time period. Between the sixth time period and the seventh time period, the user has uninstalled the head-mounted device 217. During the seventh time period, the head-mounted device triggers an uninstall routine in response to detecting that the user has uninstalled the head-mounted device 217. In various implementations, the uninstall routine includes sending a command to the light 213 to change to an "off state, and sending a command to the blinds 216 to change to a "closed" state. Accordingly, during the seventh time period, the light 213 is in the "off state, and the blinds 216 are in the "closed" state.

[0033] During the seventh time period, the head-mounted device 217 suggests performing an additional action of sending a command to the lock to change to a "locked" state by playing audio suggesting the additional action (as indicated by the audio playback indicator 299). In various implementations, the head-mounted device 217 suggests performing the additional action by sending a command to the speaker 214 to play the audio.

[0034] Figure 2H The physical environment 200 is shown during an eighth time period after the seventh time period. During the eighth time period, the user verbally confirms (as indicated by the audio detection indicator 298) that the head-mounted device will perform the additional action. In response to detecting the confirmation, the head-mounted device sends a command to the lock to change to a "locked" state.

[0035] Figure 2I The physical environment 200 is shown during a ninth time period after the eighth time period. During the ninth time period, the head-mounted device 217 plays audio (as indicated by the audio playback indicator 299), indicating a change to the uninstall routine. In various implementations, the head-mounted device suggests changing the install routine based on a user action that is typically performed before and / or shortly after uninstalling the head-mounted device 217. In response to the user confirming the change, the head-mounted device 217 changes the uninstall routine to include sending a command to the lock to change to a "locked" state.

[0036] In various implementations, the head-mounted device 217 performs the disassembly routine by sending a disassembly notification to the speaker 214, rather than sending commands directly to the plurality of devices, such as the light 213, the blinds 216, and the lock. In response to receiving the disassembly notification, the speaker 214 advances the disassembly routine by sending commands to the light 213, the blinds 216, and the lock.

[0037] Figure 3 is a flowchart representation of a method 300 of performing a routine in accordance with some implementations. In various implementations, the method 300 is performed by an electronic device, such as Figure 1 the electronic device 120. In various implementations, the method 300 is performed by a head-mounted device having one or more processors and a non-transitory memory. In some implementations, the method 300 is performed by processing logic, including hardware, firmware, software, or a combination thereof. In some implementations, the method 300 is performed by a processor executing instructions (e.g., code) stored in a non-transitory computer-readable medium (e.g., a memory).

[0038] The method 300 begins in block 310, where the head-mounted device detects a trigger indicating that a user has mounted or dismounted the head-mounted device. In various implementations, the trigger indicates that the user has mounted the head-mounted device (e.g., placed the head-mounted device on the user’s head). In various implementations, the head-mounted device detects that the user has mounted the head-mounted device using a proximity sensor that determines that the user’s head is proximate to the proximity sensor. In various implementations, the head-mounted device detects that the user has mounted the head-mounted device using an image sensor and detecting the user (e.g., the user’s eyes) in an image captured by the image sensor.

[0039] In various implementations, the trigger indicates that the user has dismounted the head-mounted device (e.g., removed the head-mounted device from the user’s head). In various implementations, the head-mounted device detects that the user has dismounted the head-mounted device using a proximity sensor that determines that the user’s head is no longer proximate to the proximity sensor. In various implementations, the head-mounted device detects that the user has dismounted the head-mounted device using an image sensor and fails to detect the user (e.g., the user’s eyes) in an image captured by the image sensor.

[0040] The method 300 continues in block 320, where the head-mounted device performs a routine in response to detecting the trigger, the routine including sending a request to change a state of a remote device from a first state to a second state. In various implementations, the remote device can be a “smart object” that wirelessly receives commands to change states. For example, in Figure 2CIn some implementations, the head-mounted device 217 has sent a request to the light 213 to change from an "off' state to an "on' state and has sent a request to the blinds 216 to change from a "closed' state to an "open' state. Thus, in various implementations, performing the routine includes sending requests to change respective states of multiple remote devices.

[0041] In various implementations, performing the routine includes playing audio. For example, in Figure 2C In some implementations, the head-mounted device 217 plays audio indicating a current weather state (as indicated by the optionally displayed audio playback indicator 299). As another example, in Figure 2E In some implementations, the head-mounted device 217 plays audio indicating a current inventory state (as indicated by the optionally displayed audio playback indicator 299). Thus, in various implementations, audio is generated based on data retrieved as part of the routine. In various implementations, the audio is generated by the head-mounted device itself. The audio can be preset (e.g., saying "good morning" or playing a song stored on the head-mounted device) or selected from a list of preset options (e.g., saying one of "good night," "sleep tight," or "rest well" or playing a song from a playlist).

[0042] In various implementations, performing the routine includes receiving confirmation to continue the routine. For example, in Figure 2B In some implementations, the head-mounted device 217 displays the virtual confirmation window 222 and receives a selection of the "yes' affordance 231.

[0043] In various implementations, performing the routine includes sending an indirect request to another device to send a direct request to the remote device to change a state of the remote device from a first state to a second state. For example, in Figure 2G In some implementations, the head-mounted device 217 sends an indirect request to the speaker 214 to send a direct request to the light 213 to change the light from an "on' state to an "off' state. As another example, in Figure 2G In some implementations, the head-mounted device 217 sends a disassembly notification to the speaker 214, which, in response to receiving the disassembly notification, sends a direct request to the blinds 216 to change the blinds 216 from an "open' state to a "closed' state.

[0044] In various implementations, where the triggering indicates that the user has installed the device, the method 300 further includes detecting a second triggering indicating that the user has disassembled the head-mounted device, and in response to detecting the second triggering, performing a second routine including sending a request to change a state of the remote device from a second state to a first state. In various implementations, the second routine includes features of the routines discussed above.

[0045] In various implementations, where the trigger indicates that the user has installed the device, the method 300 further includes detecting a user request to perform a function within a predetermined period of time after detecting the trigger, and in response to detecting the user request, modifying the routine to include performing the function. For example, in Figure 2D , the head-mounted device detects a user request for the head-mounted device to play audio indicating a current inventory status. In response to detecting the user request shortly after installing the head-mounted device 217 (and determining that the user frequently makes similar requests), the head-mounted device 217 suggests modifying the installation routine. In response to the user’s confirmation, the head-mounted device modifies the installation routine to include playing audio indicating the current inventory status. Thus, in various implementations, modifying the routine is further performed in response to detecting the user’s confirmation of the modification.

[0046] In various implementations, where the trigger indicates that the user has removed the head-mounted device, the method 300 includes detecting a user request to perform a function within a predetermined period of time before detecting the trigger, and in response to detecting the user request, modifying the routine to include performing the function. In response to detecting the user request shortly before removing the head-mounted device (and determining that the user frequently makes similar requests), the head-mounted device modifies the removal routine to include performing the function (optionally after detecting a user confirmation).

[0047] In various implementations, where the trigger indicates that the user has removed the head-mounted device, the method 300 includes determining a standard state of the additional remote device and determining that the current state of the additional remote device is not the standard state. For example, in Figure 2G , the head-mounted device 217 determines that the lock is in an “unlocked” state, rather than the “locked” state that it is frequently in when the removal routine is performed. The method 300 includes, in response to determining that the current state of the additional remote device is not the standard state, sending a request to change the state of the additional remote device from the current state to the standard state. For example, in Figure 2H , the head-mounted device 217 sends an indirect request to the speaker 214 to play audio requesting a user confirmation that the speaker 214 will send a direct request to the lock to change the lock from the “unlocked” state to the “locked” state.

[0048] In various implementations, the method 300 further includes modifying the routine to include sending a request to change the state of the additional remote device from the current state to the standard state. For example, in Figure 2I , in response to the user’s confirmation of the query played by the speaker 214, the head-mounted device 217 modifies the removal routine to include sending a request to change the state of the lock from the “unlocked” state to the “locked” state.

[0049] In various implementations, the routine or triggering routine depends on time. For example, in various implementations, when the head-mountable device is disassembled during the day, e.g., to clean the lenses, the disassembly routine to turn off the lights and close the blinds is not performed. However, when the head-mountable device is disassembled at night, e.g., to go to bed, the disassembly routine to turn off the lights and close the blinds is performed.

[0050] Accordingly, in various implementations, the method 300 includes determining a time at which the trigger was detected and determining that the time at which the trigger was detected is within a predetermined time window, where performing the routine is further performed in response to determining that the time at which the trigger was detected is within the predefined time window.

[0051] In various implementations, the routine or triggering routine depends on location. For example, in various implementations, when the head-mountable device is installed at a hotel during a business trip, the installation routine to turn on the lights and open the blinds at home is not performed. However, when the head-mountable device is installed at home, the installation routine to turn on the lights and open the blinds is performed.

[0052] Accordingly, in various implementations, the method 300 includes determining a location of the head-mountable device when the trigger was detected and determining that the location of the head-mountable device when the trigger was detected is within a predefined area, where performing the routine is further performed in response to determining that the location of the head-mountable device when the trigger was detected is within the predefined area.

[0053] Figure 4 is a block diagram of an example of a controller 110 in accordance with some implementations. While certain specific features are illustrated, one skilled in the art will recognize that for brevity, certain other features are not illustrated, and that some of the features illustrated are for simplicity. For this reason, as a non-limiting example, in some implementations, the controller 110 includes one or more processing units 402 (e.g., microprocessors, application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), graphics processing units (GPUs), central processing units (CPUs), processing cores, and / or similar processing units), one or more input / output (I / O) devices 406, one or more communication interfaces 408 (e.g., universal serial bus (USB), FIREWIRE, THUNDERBOLT, IEEE 802.3x, IEEE 802.1 lx, IEEE 802.16x, global system for mobile communications (GSM), code division multiple access (CDMA), time division multiple access (TDMA), global positioning system (GPS), infrared (IR), BLUETOOTH, ZIGBEE, and / or similar types of interfaces), one or more programming (e.g., I / O) interfaces 410, a memory 420, and one or more communication buses 404 for interconnecting these and various other components.

[0054] In some implementations, the one or more communication buses 404 include circuitry that interconnects the system components and / or controls communication between the system components. In some implementations, the one or more I / O devices 406 include at least one of a keyboard, a mouse, a touchpad, a joystick, one or more microphones, one or more speakers, one or more image sensors, one or more displays, etc.

[0055] The memory 420 includes high-speed random access memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), double data rate random access memory (DDR RAM), or other random access solid-state memory devices. In some implementations, the memory 420 includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory 420 optionally includes one or more storage devices remotely located from the one or more processing units 402. The memory 420 comprises a non-transitory computer readable storage medium. In some implementations, the memory 420, or the non-transitory computer readable storage medium of the memory 420, stores the following programs, modules, and data structures, or a subset thereof, including an optional operating system 430 and an XR experience module 440.

[0056] The operating system 430 includes procedures for handling various basic system services and for performing hardware dependent tasks. In some implementations, the XR experience module 440 is configured to manage and coordinate single or multiple XR experiences for one or more users (e.g., a single XR experience for one or more users, or multiple XR experiences for respective groups of one or more users). To this end, in various implementations, the XR experience module 440 includes a data acquisition unit 442, a tracking unit 444, a coordination unit 446, and a data transmission unit 448.

[0057] In some implementations, the data acquisition unit 442 is configured to acquire data (e.g., presentation data, interaction data, sensor data, location data, etc.) from the electronic device 120 of the user. Figure 1 To this end, in various implementations, the data acquisition unit 442 includes instructions and / or logic therefor, as well as heuristics and metadata therefor.

[0058] In some implementations, the tracking unit 444 is configured to map the physical environment 105 and to track at least a location / orientation of the electronic device 120 relative to the physical environment 105 of the user. Figure 1 To this end, in various implementations, the tracking unit 444 includes instructions and / or logic therefor, as well as heuristics and metadata therefor.

[0059] In some implementations, the coordination unit 446 is configured to manage and coordinate the XR experience presented to the user by the electronic device 120. To this end, in various implementations, the coordination unit 446 includes instructions and / or logic for the instructions, as well as heuristics and metadata for the heuristics.

[0060] In some implementations, the data sending unit 448 is configured to send data (e.g., presentation data, location data, etc.) to at least the electronic device 120. To this end, in various implementations, the data sending unit 448 includes instructions and / or logic for the instructions, as well as heuristics and metadata for the heuristics.

[0061] Although the data acquisition unit 442, the tracking unit 444, the coordination unit 446, and the data sending unit 448 are shown as residing on a single device (e.g., the controller 110), it will be appreciated that, in other implementations, any combination of the data acquisition unit 442, the tracking unit 444, the coordination unit 446, and the data sending unit 448 can be located in separate computing devices.

[0062] Furthermore, Figure 4 More functionality is described as various features that can be present in particular implementations, rather than structural diagrams of the implementations described herein. As will be appreciated by those of ordinary skill in the art, the items shown separately can be combined, and some items can be separated. For example, Figure 4 Some of the functional modules shown separately in the figures can be implemented in a single module, and various functions of a single functional block can be implemented through one or more functional blocks in various implementations. The actual number of modules and the division of particular functions between them, and how features are allocated among them, will vary from implementation to implementation, and in some implementations, depend in part on the particular combination of hardware, software, and / or firmware chosen for a particular implementation.

[0063] Figure 5is a block diagram of an example of an electronic device 120 in accordance with some implementations. While certain specific features are illustrated, one skilled in the art will appreciate from the present disclosure that the application includes a variety of other features as well. In some implementations, for example, the electronic device 120 includes one or more processing units 502 (e.g., microprocessors, ASICs, FPGAs, GPUs, CPUs, processing cores, etc.), one or more input / output (I / O) devices and sensors 506, one or more communication interfaces 508 (e.g., USB, FIREWIRE, THUNDERBOLT, IEEE 802.3x, IEEE 802.1 lx, IEEE 802.16x, GSM, CDMA, TDMA, GPS, IR, BLUETOOTH, ZIGBEE, and / or the like types of interfaces), one or more programming (e.g., I / O) interfaces 510, one or more XR displays 512, one or more optional inward- and / or outward-facing image sensors 514, memory 520, and one or more communication buses 504 for interconnecting these and various other components.

[0064] In some implementations, the one or more communication buses 504 include circuitry that interconnects the system components and / or controls communication between system components. In some implementations, the one or more I / O devices and sensors 506 include at least one of: an inertial measurement unit (IMU), an accelerometer, a gyroscope, a thermometer, one or more physiological sensors (e.g., blood pressure monitor, heart rate monitor, blood glucose sensor, etc.), one or more microphones, one or more speakers, a haptics engine, or one or more depth sensors (e.g., structured light, time-of-flight, etc.), etc.

[0065] In some implementations, the one or more XR displays 512 are configured to provide an XR experience to a user. In some implementations, the one or more XR displays 512 correspond to holographic, digital light processing (DLP), liquid crystal display (LCD), liquid crystal on silicon (LCoS), organic light-emitting field-effect transitory (OLET), organic light-emitting diode (OLED), surface-conduction electron-emitter display (SED), field emission display (FED), quantum dot light-emitting diode (QD-LED), micro-electromechanical system (MEMS), and / or similar display types. In some implementations, the one or more XR displays 512 correspond to diffractive, reflective, polarized, holographic, etc. waveguide displays. For example, the electronic device 120 includes a single XR display. In another example, the electronic device includes an XR display for each eye of a user. In some implementations, the one or more XR displays 512 are capable of presenting MR and VR content.

[0066] In some implementations, one or more image sensors 514 are configured to acquire image data corresponding to at least a portion of a user’s face, including the user’s eyes (and can be referred to as eye tracking cameras). In some implementations, one or more image sensors 514 are configured to face forward so as to acquire image data corresponding to a physical environment that the user would see when the electronic device 120 is not present (and can be referred to as a scene camera). One or more optional image sensors 514 can include one or more RGB cameras (e.g., with a complementary metal-oxide-semiconductor (CMOS) image sensor or a charge-coupled device (CCD) image sensor), one or more infrared (IR) cameras, one or more event-based cameras, and the like.

[0067] The memory 520 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid state memory devices. In some implementations, the memory 520 includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid state storage devices. The memory 520 optionally includes one or more storage devices remotely located from the one or more processing units 502. The memory 520 comprises non-transitory computer readable storage media. In some implementations, the memory 520, or the non-transitory computer readable storage medium of the memory 520, stores the following programs, modules, and data structures, including optional operating system 530 and XR presentation module 540, or a subset thereof.

[0068] The operating system 530 includes procedures for handling various basic system services and for performing hardware dependent tasks. In some implementations, the XR presentation module 540 is configured to present XR content to a user via the one or more XR displays 512. To this end, in various implementations, the XR presentation module 540 includes a data acquisition unit 542, an entry positioning unit 544, an XR presentation unit 546, and a data transmission unit 548.

[0069] In some implementations, the data acquisition unit 542 is configured to acquire data (e.g., presentation data, interaction data, sensor data, location data, etc.) from at least the controller 110 of the system 100. Figure 1 To this end, in various implementations, the data acquisition unit 542 includes instructions and / or logic for the instructions, as well as heuristics and metadata for the heuristics.

[0070] In some implementations, the routine execution unit 544 is configured to detect a trigger and, in response, execute a routine. To this end, in various implementations, the routine execution 544 includes instructions and / or logic therefor, as well as heuristics and metadata therefor.

[0071] In some implementations, the XR presentation unit 546 is configured to display XR content via one or more XR displays 512. To this end, in various implementations, the XR presentation unit 546 includes instructions and / or logic therefor, as well as heuristics and metadata therefor.

[0072] In some implementations, the data transmission unit 548 is configured to transmit data (e.g., presentation data, location data, etc.) to at least the controller 110. In some implementations, the data transmission unit 548 is configured to transmit authentication credentials to an electronic device. To this end, in various implementations, the data transmission unit 548 includes instructions and / or logic therefor, as well as heuristics and metadata therefor.

[0073] While the data acquisition unit 542, the routine execution unit 544, the XR presentation unit 546, and the data transmission unit 548 are shown as residing on a single device (e.g., the electronic device 120), it will be appreciated that, in other implementations, any combination of the data acquisition unit 542, the routine execution unit 544, the XR presentation unit 546, and the data transmission unit 548 can be located in separate computing devices.

[0074] Furthermore, Figure 5 More functionality is described as the functionality of various features that can be present in particular implementations, rather than the structural diagrams of the implementations described herein. As will be appreciated by those of ordinary skill in the art, the items shown separately can be combined, and some items can be separated. For example, Figure 5 Some of the functional modules shown separately in the can be implemented in a single module, and various functions of a single functional block can be implemented by one or more functional blocks in various implementations. The actual number of modules and the division of particular functions between them, and how features are allocated among them, will vary from implementation to implementation and, in some implementations, depend partly on the particular combination of hardware, software, and / or firmware chosen for a particular implementation.

[0075] While various aspects of implementations within the scope of the appended claims are described above, it should be apparent that the various features of implementations described above can be embodied in a wide variety of forms and that any specific structure and / or function described above is merely illustrative. Based on the teachings herein one skilled in the art should appreciate that an aspect described herein can be implemented independently of any other aspects and that an aspect described herein can be implemented both as any stand-alone implementation and in combination with other aspects. For example, an apparatus can be implemented using any number of the aspects described herein. Additionally, the scope of the application is intended to cover any and all combinations of the aspects described herein.

[0076] It will also be understood that, although the terms“first,”“second,” etc. can 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. For example, a first node could be termed a second node, and, similarly, a second node could be termed a first node, which changes the meaning of the description, so long as all occurrences of“first node” are renamed consistently and all occurrences of“second node” are renamed consistently. The first node and the second node are both nodes, but they are not the same node.

[0077] The terminology used herein is for the purpose of describing particular implementations only and is not intended to be limiting of the claims. As used in the description of the implementations and the appended claims, the singular forms“a,”“an,” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term“and / or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms“comprises” and / or“comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0078] As used herein, the term“if’ can be construed to mean“when” or“when a” or“in response to a determination of” or“in response to detecting” that a stated condition precedent has been met, depending on the context. Similarly, the phrase“if it is determined [that a stated condition precedent has been met]” or“if [a stated condition precedent is true]” or“when [a stated condition precedent is true]” can be construed to mean“when it is determined” or“in response to a determination” or“in response to a determination of” that the stated condition precedent has been met or “when [a stated condition precedent is true]” or“in response to detecting” that the stated condition precedent is true, depending on the context.

Claims

1. A method, the method comprising: In a head-mounted device having one or more processors and non-transitory memory; The system detects a trigger indicating that the user has installed or removed the headset. as well as In response to the detection of the trigger, a routine is executed, the routine including sending a request to change the state of the remote device from a first state to a second state.

2. The method of claim 1, wherein performing the routine includes sending requests to change the respective states of a plurality of remote devices.

3. The method of claim 1, wherein performing the routine includes playing audio.

4. The method of claim 1, wherein executing the routine includes receiving confirmation to continue the routine.

5. The method of claim 1, wherein performing the routine includes sending an indirect request to another device to send a direct request to the remote device to change the state of the remote device from the first state to the second state.

6. The method of claim 1, wherein the trigger indicates that the user has installed the head-mounted device.

7. The method according to claim 6, further comprising: A second trigger indicating that the user has removed the headset; as well as In response to detecting the second trigger, a second routine is executed, the second routine including sending a request to change the state of the remote device from the second state to the first state.

8. The method according to claim 6, further comprising: Within a predetermined time period following the detection of the trigger, detect user requests to perform the function; as well as In response to detecting the user request, the routine is modified to include performing the function.

9. The method of claim 8, wherein the modified routine is further executed in response to the detection of user confirmation of the modification.

10. The method of claim 1, wherein the trigger indicates that the user has removed the head-mounted device.

11. The method according to claim 10, further comprising: Within a predetermined time period prior to detecting the trigger, detect user requests to perform the function; as well as In response to detecting the user request, the routine is modified to include performing the function.

12. The method according to claim 10, further comprising: Determine the standard status of the attached remote device; It is determined that the current state of the additional remote device is not the standard state; as well as In response to determining that the current state of the additional remote device is not the standard state, a request is sent to change the state of the additional remote device from the current state to the standard state.

13. The method of claim 12, further comprising modifying the routine to include sending a request to change the state of the attached remote device from the current state to the standard state.

14. The method according to claim 1, further comprising: Determine the time when the trigger was detected; as well as It is determined that the time at which the trigger was detected is within a predefined time window, wherein the routine is executed further in response to determining that the time at which the trigger was detected is within the predefined time window.

15. The method according to claim 1, further comprising: Determine the position of the head-mounted device when the trigger is detected; as well as Determine that the position of the head-mounted device is within a predefined area when the trigger is detected, wherein the routine is executed further in response to determining that the position of the head-mounted device is within the predefined area when the trigger is detected.

16. A head-mounted device, the head-mounted device comprising: Non-transitory memory; and One or more processors, said one or more processors being used to: The system detects a trigger indicating that the user has installed or removed the headset. as well as In response to the detection of the trigger, a routine is executed, the routine including sending a request to change the state of the remote device from a first state to a second state.

17. The head-mounted device of claim 10, wherein the trigger indicates that the user has installed the head-mounted device.

18. The head-mounted device of claim 10, wherein the trigger indicates that the user has removed the head-mounted device.

19. The method according to claim 1, further comprising: Determine the spatiotemporal conditions of the device when the trigger is detected; as well as The spatiotemporal conditions are determined to be within a predefined window, wherein the routine is executed in response to the determination that the spatiotemporal conditions are within the predefined time window.

20. A non-transitory memory storing one or more programs, said one or more programs causing the head-mounted device to: The system detects triggers indicating that the user has installed or removed the headset; and In response to the detection of the trigger, a routine is executed, the routine including sending a request to change the state of the remote device from a first state to a second state.

Images