Devices, methods, and graphical user interfaces for authorizing secure operations

Abstract

In some examples, when a three-dimensional environment is visible, a change in a user's current viewpoint is detected. In some examples, user authorization for secure operations using virtual user interface objects is enabled in accordance with a determination that at least a threshold amount of objects are visible from the viewpoint of the user. In some examples, a user is biometrically authenticated at a first time to perform a first type of biometric authentication. In some examples, a request to perform the secure operation is received at a second time. In some examples, in accordance with a determination that the user satisfies respective criteria between the first time and the second time, the secure operation is performed without performing the first type of biometric authentication after receiving the request.

Description

[0001] This application is a divisional application of the invention patent application with application number 202380024002.1, application date February 28, 2023, and name “Device, method and graphical user interface for authorizing security operations”.

[0002] CROSS-REFERENCE TO RELATED APPLICATIONS

[0003] This application claims priority to U.S. patent application No. 18 / 167,767, filed on February 10, 2023, entitled “DEVICES, METHODS, AND GRAPHICALUSER INTERFACES FOR AUTHORIZING A SECURE OPERATION,” and U.S. Provisional Application No. 63 / 314,900, filed on February 28, 2022, entitled “DEVICES, METHODS, AND GRAPHICAL USER INTERFACESFOR AUTHORIZING A SECURE OPERATION,” the entire contents of each of which are hereby incorporated by reference in their entirety for all purposes. Technical Field

[0004] The present disclosure as a whole relates to computer systems that provide computer-generated experiences in communication with display generation components, one or more input devices, and (optionally) biometric sensors, including but not limited to electronic devices that provide virtual reality and mixed reality experiences via displays. Background Art

[0005] In recent years, the development of computer systems for augmented reality has increased significantly. Example augmented reality environments include at least some virtual elements that replace or augment the physical world. Input devices (such as cameras, controllers, joysticks, touch-sensitive surfaces, and touch screen displays) for computer systems and other electronic computing devices are used to interact with virtual / augmented reality environments. Example virtual elements include virtual objects such as digital images, videos, text, icons, and control elements (such as buttons and other graphics). Summary of the invention

[0006] Some methods and interfaces for authorizing security operations within environments that include at least some virtual elements (e.g., augmented reality environments, mixed reality environments, and virtual reality environments) are cumbersome, inefficient, and limited. For example, systems that provide solutions for automatically filling in various text fields, systems that facilitate payment of items or other services, and systems that provide access to third-party applications (e.g., social networking, games, business services, etc.) are complex, tedious, error-prone, impose a significant cognitive burden on users, and detract from the experience of virtual / augmented reality environments. In addition, these methods take longer than necessary, thereby wasting energy from the computer system. This latter consideration is particularly important in battery-powered devices.

[0007] Therefore, there is a need for a computing system with improved methods and interfaces for authorizing security operations so as to make interaction with the computing system more efficient and more intuitive for users. Such methods and interfaces optionally supplement or replace conventional methods for authorizing security operations. Such methods and interfaces reduce the amount, degree and / or nature of inputs from a user by helping the user understand the connection between the inputs provided and the device's response to those inputs, thereby forming a more efficient human-computer interface.

[0008] The above-mentioned defects and other problems associated with the user interface of the computer system are reduced or eliminated by the disclosed system. In some embodiments, the computer system is a desktop computer with an associated display. In some embodiments, the computer system is a portable device (e.g., a notebook computer, a tablet computer, or a handheld device). In some embodiments, the computer system is a personal electronic device (e.g., a wearable electronic device, such as a watch or a head-mounted device). In some embodiments, the computer system has a touch pad. In some embodiments, the computer system has one or more cameras. In some embodiments, the computer system has a touch-sensitive display (also referred to as a "touch screen" or "touch screen display"). In some embodiments, the computer system has one or more eye tracking components. In some embodiments, the computer system has one or more hand tracking components. In some embodiments, in addition to the display generation component, the computer system also has one or more output devices, which include one or more tactile output generators and / or one or more audio output devices. In some embodiments, the computer system has a graphical user interface (GUI), one or more processors, a memory, and one or more modules, a program or instruction set stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI through contact and gestures of a stylus and / or finger on a touch-sensitive surface, movement of the user's eyes and hands in space relative to the GUI (and / or computer system) or the user's body (as captured by a camera and other motion sensors), and / or voice input (as captured by one or more audio input devices). In some embodiments, the functions performed by interaction optionally include image editing, drawing, presentations, word processing, spreadsheet creation, playing games, making and receiving calls, video conferencing, sending and receiving emails, instant messaging, testing support, digital photography, digital video recording, web browsing, digital music playback, note-taking, and / or digital video playback. Executable instructions for performing these functions are optionally included in a transient and / or non-transient computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0009] Electronic devices with improved methods and interfaces are needed to authorize security operations. Such methods and interfaces can supplement or replace conventional methods for authorizing security operations. Such methods and interfaces reduce the amount, degree and / or nature of input from users and produce more efficient human-computer interfaces. For battery-powered computing devices, such methods and interfaces save power and increase the time interval between battery charges. In addition, these methods and interfaces help reduce the number of repeated inputs from users by automatically filling in or otherwise entering sensitive or confidential information (such as passwords or payment information). Such methods and interfaces also reduce processing power and reduce display usage by reducing the amount of time a user spends interacting with a device when authorizing a security operation.

[0010] According to some embodiments, a method is described. The method is performed at a computer system that communicates with one or more input devices and a display generation component. The method includes: when a three-dimensional environment is visible via the display generation component, wherein the three-dimensional environment includes a virtual user interface object that includes information about a security operation, detecting a change in a user's current viewpoint via one or more input devices; and in response to detecting a change in the user's viewpoint: based on determining that at least a threshold amount of the virtual user interface object is visible from the user's viewpoint and the user is authorized to perform the security operation, enabling user authorization for the security operation using the virtual user interface object, and based on determining that less than a threshold amount of the virtual user interface object is visible from the user's viewpoint, abandoning enabling user authorization for the security operation using the virtual user interface object.

[0011] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system in communication with one or more input devices and a display generation component, the one or more programs including instructions for: when a three-dimensional environment is visible via the display generation component, wherein the three-dimensional environment includes a virtual user interface object containing information about a safety operation, detecting a change in a user's current viewpoint via the one or more input devices; and in response to detecting the change in the user's viewpoint: based on determining that at least a threshold amount of the virtual user interface object is visible from the user's viewpoint and the user is authorized to perform the safety operation, enabling user authorization for the safety operation using the virtual user interface object, and based on determining that less than a threshold amount of the virtual user interface object is visible from the user's viewpoint, abandoning enabling user authorization for the safety operation using the virtual user interface object.

[0012] According to some embodiments, a computer system is described. The computer system communicates with one or more input devices and a display generation component. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by the one or more processors, the one or more programs including instructions for the following operations: when a three-dimensional environment is visible via the display generation component, wherein the three-dimensional environment includes a virtual user interface object containing information about a safety operation, detecting a change in the user's current viewpoint via one or more input devices; and in response to detecting a change in the user's viewpoint: based on determining that at least a threshold amount of virtual user interface objects are visible from the user's viewpoint and the user is authorized to perform a safety operation, enabling user authorization for safety operations using virtual user interface objects, and based on determining that less than a threshold amount of virtual user interface objects are visible from the user's viewpoint, abandoning enabling user authorization for safety operations using virtual user interface objects.

[0013] According to some embodiments, a computer system is described. The computer system communicates with one or more input devices and a display generation component. The computer system includes: a component for detecting a change in a user's current viewpoint via one or more input devices when a three-dimensional environment is visible via the display generation component, wherein the three-dimensional environment includes a virtual user interface object containing information about a security operation; and in response to detecting a change in the user's viewpoint: a component for enabling user authorization for security operations using virtual user interface objects based on determining that at least a threshold amount of virtual user interface objects are visible from the user's viewpoint and the user is authorized to perform security operations; and a component for abandoning enabling user authorization for security operations using virtual user interface objects based on determining that less than a threshold amount of virtual user interface objects are visible from the user's viewpoint.

[0014] According to some embodiments, a method is described. The method is performed at a computer system that communicates with one or more input devices, a display generation component, and a biometric sensor. The method includes: at a first time, using a biometric sensor to perform a first type of biometric authentication to authenticate a user of the device in a biometric manner; and at a second time after the first time, receiving a request to perform a security operation; in response to receiving a request to perform a security operation: based on determining that the user of the device meets the corresponding criteria between the first time and the second time, after receiving the request to perform the security operation, perform the security operation without performing the first type of biometric authentication, wherein the corresponding criteria are based on sensor measurements taken at multiple intermediate times between the first time and the second time, including sensor measurements taken at the first intermediate time and sensor measurements taken at the second intermediate time, which detect that the same user is using the device between the first time and the second time; and based on determining that the continuity criteria are not met between the first time and the second time, abandon the execution of the security operation.

[0015] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with one or more input devices, a display generation component, and a biometric sensor, the one or more programs including instructions for the following operations: at a first time, using a biometric sensor to perform a first type of biometric authentication to biometrically authenticate a user of the device; and at a second time after the first time, receiving a request to perform a security operation; in response to receiving a request to perform a security operation: based on determining that the user of the device meets a corresponding criterion between the first time and the second time, after receiving the request to perform the security operation, perform the security operation without performing the first type of biometric authentication, wherein the corresponding criterion is based on sensor measurements taken at multiple intermediate times between the first time and the second time, including a sensor measurement taken at the first intermediate time and a sensor measurement taken at the second intermediate time, which detects that the same user is using the device between the first time and the second time; and based on determining that the continuity criterion is not met between the first time and the second time, abandon the execution of the security operation.

[0016] According to some embodiments, a computer system is described. The computer system communicates with one or more input devices, a display generating component, and a biometric sensor. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by one or more processors, the one or more programs including instructions for the following operations: at a first time, using a biometric sensor to perform a first type of biometric authentication to authenticate the user of the device in a biometric manner; and at a second time after the first time, receiving a request to perform a security operation; in response to receiving a request to perform a security operation: based on determining that the user of the device meets the corresponding criteria between the first time and the second time, after receiving the request to perform the security operation, perform the security operation without performing the first type of biometric authentication, wherein the corresponding criteria are based on sensor measurements taken at multiple intermediate times between the first time and the second time, including sensor measurements taken at the first intermediate time and sensor measurements taken at the second intermediate time, the sensor measurements detect that the same user is using the device between the first time and the second time; and based on determining that the continuity criteria are not met between the first time and the second time, abandon the execution of the security operation.

[0017] According to some embodiments, a computer system is described. The computer system communicates with one or more input devices and a display generation component. The computer system includes: a component for performing a first type of biometric authentication using a biometric sensor at a first time to biometrically authenticate a user of the device; and a component for receiving a request to perform a security operation at a second time after the first time; in response to receiving a request to perform a security operation: a component for performing a security operation without performing the first type of biometric authentication after receiving a request to perform a security operation based on determining that the user of the device meets the corresponding criteria between the first time and the second time, wherein the corresponding criteria are based on sensor measurements taken at multiple intermediate times between the first time and the second time, including sensor measurements taken at the first intermediate time and sensor measurements taken at the second intermediate time, which detect that the same user is using the device between the first time and the second time; and a component for abandoning the execution of the security operation based on determining that the continuity criteria are not met between the first time and the second time.

[0018] According to some embodiments, a method is described. The method is performed at a computer system that communicates with one or more input devices and a display generation component. The method includes: receiving a request to display a user interface associated with performing a security operation via one or more input devices; and in response to the request to display a user interface associated with performing a security operation, displaying a first user interface via a display generation component, the first user interface including a corresponding prompt for providing additional input to authorize the device to perform a security operation, wherein: based on determining that the computer system is operating in a first mode, the corresponding prompt is a first prompt for providing a physical input for authorizing the security operation, and based on determining that the computer system is operating in a second mode different from the first mode, the corresponding prompt is a second prompt for displaying a second user interface, wherein the second user interface enables user authorization for security operations without using physical input.

[0019] According to some embodiments, a non-transitory computer-readable storage medium is described. The non-transitory computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a computer system that communicates with one or more input devices and a display generation component, the one or more programs including instructions for the following operations: receiving a request to display a user interface associated with performing a security operation via one or more input devices; and in response to the request to display a user interface associated with performing a security operation, displaying a first user interface via the display generation component, the first user interface including a corresponding prompt for providing additional input to authorize the device to perform the security operation, wherein: based on determining that the computer system is operating in a first mode, the corresponding prompt is a first prompt for providing a physical input for authorizing the security operation, and based on determining that the computer system is operating in a second mode different from the first mode, the corresponding prompt is a second prompt for displaying a second user interface, wherein the second user interface enables user authorization of the security operation without using physical input.

[0020] According to some embodiments, a computer system is described. The computer system communicates with one or more input devices and a display generation component. The computer system includes: one or more processors; and a memory storing one or more programs configured to be executed by one or more processors, the one or more programs including instructions for the following operations: receiving a request to display a user interface associated with performing a security operation via one or more input devices; and in response to the request to display a user interface associated with performing a security operation, displaying a first user interface via a display generation component, the first user interface including a corresponding prompt for providing additional input to authorize the device to perform a security operation, wherein: based on determining that the computer system is operating in a first mode, the corresponding prompt is a first prompt for providing a physical input for authorizing the security operation, and based on determining that the computer system is operating in a second mode different from the first mode, the corresponding prompt is a second prompt for displaying a second user interface, wherein the second user interface enables user authorization for security operations without using physical input.

[0021] According to some embodiments, a computer system is described. The computer system communicates with one or more input devices and a display generation component. The computer system includes: a component for receiving a request to display a user interface associated with performing a security operation via one or more input devices; and a component for displaying a first user interface via a display generation component in response to a request to display a user interface associated with performing a security operation, the first user interface including a corresponding prompt for providing additional input to authorize the device to perform a security operation, wherein: based on determining that the computer system is operating in a first mode, the corresponding prompt is a first prompt for providing a physical input for authorizing the security operation, and based on determining that the computer system is operating in a second mode different from the first mode, the corresponding prompt is a second prompt for displaying a second user interface, wherein the second user interface enables user authorization for security operations without using physical input.

[0022] It should be noted that the various embodiments described above can be combined with any other embodiments described herein. The features and advantages described in this specification are not comprehensive, and in particular, many additional features and advantages will be apparent to those of ordinary skill in the art based on the drawings, the specification, and the claims. In addition, it should be noted that the language used in this specification is selected in principle for readability and instructional purposes, and may not be selected to describe or define the subject matter of the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] For a better understanding of the various described embodiments, reference should be made to the following detailed description taken in conjunction with the following drawings, wherein like reference numerals designate corresponding parts throughout the several views.

[0024] Figure 1 is a block diagram illustrating an operating environment of a computer system for providing an XR experience according to some embodiments.

[0025] Figure 2 is a block diagram illustrating a controller of a computer system configured to manage and coordinate a user's XR experience according to some embodiments.

[0026] Figure 3 is a block diagram illustrating display generation components of a computer system configured to provide a visual component of an XR experience to a user according to some embodiments.

[0027] Figure 4 is a block diagram illustrating a hand tracking unit of a computer system configured to capture gesture input from a user according to some embodiments.

[0028] Figure 5 is a block diagram illustrating an eye tracking unit of a computer system configured to capture gaze input of a user according to some embodiments.

[0029] Fig. 6A is a flow chart illustrating a flash-assisted gaze tracking pipeline according to some embodiments.

[0030] Figure 6B Example devices connected via one or more communication channels are shown in accordance with some embodiments.

[0031] FIG. 7A to FIG. 7N Example techniques for authorizing security operations according to some embodiments are shown.

[0032] Figure 8 is a flow diagram of a method of facilitating user consent for secure operations according to various embodiments.

[0033] Fig. 9 is a flow diagram of a method for authentication continuity for secure operations according to various embodiments.

[0034] Fig.10 is a flow diagram of a method of authorizing security operations via an accessibility interface according to various embodiments. DETAILED DESCRIPTION

[0035] According to some embodiments, the present disclosure relates to a user interface for providing an extended reality (XR) experience to a user.

[0036] Figures 1 to 6B A description of an example computer system for providing an XR experience to a user is provided. FIG. 7A to FIG. 7N Example techniques for authorizing security operations according to some embodiments are shown. Figure 8 is a flow chart of a method for informed consent for safe operations according to various embodiments. FIG. 7A to FIG. 7N The user interface in Figure 8 process. Fig. 9 is a flow diagram of a method for authentication continuity for secure operations according to various embodiments. FIG. 7A to FIG. 7N The user interface in Fig. 9 process. Fig.10 is a flow diagram of a method of authorizing security operations via an accessibility interface according to various embodiments. FIG. 7A to FIG. 7N The user interface in Fig.10 process.

[0037] The processes described below enhance the operability of the device and make the user-device interface more efficient (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device) through various techniques, including by providing improved visual feedback to the user, reducing the number of inputs required to perform an operation, providing additional control options without cluttering the user interface with additional display controls, performing an operation without further user input when a set of conditions have been met, improving privacy and / or security, and / or additional techniques. These techniques also reduce power usage and extend the battery life of the device by enabling the user to use the device more quickly and efficiently.

[0038] In addition, in the method described herein where one or more steps depend on one or more conditions being met, it should be understood that the method can be repeated in multiple repetitions so that in the process of repetition, all conditions for determining the steps in the method have been met in different repetitions of the method. For example, if the method needs to perform the first step (if the condition is met), and perform the second step (if the condition is not met), then the ordinary technician will know that the steps stated are repeated until both the condition is met and the condition is not met (in no particular order). Therefore, the method described as having one or more steps depending on one or more conditions being met can be rewritten as a method of repeating until each condition described in the method is met. However, this does not require the system or computer-readable medium to declare that the system or computer-readable medium contains instructions for performing a contingent operation based on the satisfaction of the corresponding one or more conditions, and is therefore able to determine whether the possible situation has been met without explicitly repeating the steps of the method until all conditions for determining the steps in the method have been met. It will also be understood by ordinary technicians in the art that, similar to the method with the contingent step, the system or computer-readable storage medium can repeat the steps of the method as many times as needed to ensure that all the contingent steps have been performed.

[0039] In some embodiments, such as Figure 1 As shown in , an XR experience is provided to a user via an operating environment 100 including a computer system 101. The computer system 101 includes a controller 110 (e.g., a processor of a portable electronic device or a remote server), a display generation component 120 (e.g., a head mounted device (HMD), a display, a projector, a touch screen, etc.), one or more input devices 125 (e.g., an eye tracking device 130, a hand tracking device 140, other input devices 150), one or more output devices 155 (e.g., a speaker 160, a tactile output generator 170, and other output devices 180), one or more sensors 190 (e.g., an image sensor, a light sensor, a depth sensor, a tactile sensor, an orientation sensor, a proximity sensor, a temperature sensor, a position sensor, a motion sensor, a speed sensor, etc.), and optionally one or more peripheral devices 195 (e.g., a household appliance, a wearable device, etc.). In some embodiments, one or more of the input device 125, the output device 155, the sensor 190, and the peripheral device 195 are integrated with the display generation component 120 (e.g., in a head mounted device or a handheld device).

[0040] In describing an XR experience, various terms are used to distinguishably refer to several related but distinct environments that a user can sense and / or with which the user can interact (e.g., using inputs detected by the computer system 101 generating the XR experience, which inputs cause the computer system generating the XR experience to generate audio, visual, and / or tactile feedback corresponding to the various inputs provided to the computer system 101). The following is a subset of these terms:

[0041] Physical environment: The physical environment refers to the physical world that people can sense and / or interact with without the help of electronic systems. A physical environment, such as a physical park, includes physical objects, such as physical trees, physical buildings, and physical people. People can directly sense and / or interact with the physical environment, such as through vision, touch, hearing, taste, and smell.

[0042] Extended Reality: In contrast, an extended reality (XR) environment refers to a fully or partially simulated environment that people sense and / or interact with via an electronic system. In XR, a subset of a person's physical movements or a representation thereof is tracked, and in response, one or more characteristics of one or more virtual objects simulated in the XR environment are adjusted in a manner that complies with at least one physical law. For example, an XR system may detect a person's head turn, and in response, adjust the graphical content and sound field presented to the person in a manner similar to the way such views and sounds change in a physical environment. In some cases (e.g., for accessibility reasons), adjustments to the characteristics of virtual objects in the XR environment may be made in response to a representation of physical movement (e.g., a voice command). People can sense and / or interact with XR objects using any of their senses, including vision, hearing, touch, taste, and smell. For example, people can sense and / or interact with audio objects, which create a 3D or spatial audio environment that provides the perception of a point audio source in 3D space. As another example, an audio object can enable audio transparency that selectively introduces ambient sounds from the physical environment with or without computer-generated audio. In some XR environments, a person can sense and / or interact only with an audio object.

[0043] Examples of XR include virtual reality and mixed reality.

[0044] Virtual Reality: A virtual reality (VR) environment refers to a simulated environment designed to be based entirely on computer-generated sensory input to one or more senses. A VR environment includes a plurality of virtual objects that a person can sense and / or interact with. For example, trees, buildings, and computer-generated images representing avatars of people are examples of virtual objects. A person can sense and / or interact with virtual objects in a VR environment through a simulation of the person's presence within the computer-generated environment and / or through a simulation of a subset of the person's physical movement within the computer-generated environment.

[0045] Mixed Reality: In contrast to VR environments, which are designed to be based entirely on computer-generated sensory input, a mixed reality (MR) environment refers to a simulated environment that is designed to include sensory input from the physical environment, or representations thereof, in addition to computer-generated sensory input (e.g., virtual objects). On the virtuality continuum, a mixed reality environment is anything between, but not including, a fully physical environment at one end and a virtual reality environment at the other end. In some MR environments, computer-generated sensory input can respond to changes in sensory input from the physical environment. In addition, some electronic systems used to render MR environments can track position and / or orientation relative to the physical environment to enable virtual objects to interact with real objects (i.e., physical items from the physical environment, or representations thereof). For example, the system can cause motion so that virtual trees appear stationary relative to the physical ground.

[0046] Examples of mixed reality include augmented reality and augmented virtuality.

[0047] Augmented reality: An augmented reality (AR) environment refers to a simulated environment in which one or more virtual objects are superimposed on a physical environment or a representation of a physical environment. For example, an electronic system for presenting an AR environment may have a transparent or translucent display through which a person can directly view the physical environment. The system may be configured to present virtual objects on a transparent or translucent display so that a person uses the system to perceive virtual objects superimposed on the physical environment. Alternatively, the system may have an opaque display and one or more imaging sensors that capture images or videos of the physical environment, which are representations of the physical environment. The system combines the image or video with the virtual object and presents the composition on an opaque display. A person uses the system to indirectly view the physical environment via an image or video of the physical environment and perceives virtual objects superimposed on the physical environment. As used herein, a video of a physical environment displayed on an opaque display is referred to as a "transparent video," meaning that the system uses one or more image sensors to capture images of the physical environment and uses those images when presenting the AR environment on an opaque display. Further alternatively, the system may have a projection system that projects virtual objects into a physical environment, such as as a hologram or on a physical surface, so that a person using the system perceives virtual objects superimposed on the physical environment. An augmented reality environment also refers to a simulated environment in which a representation of a physical environment is transformed by computer-generated sensory information. For example, in providing a pass-through video, the system may transform one or more sensor images to apply a selected perspective (e.g., a viewpoint) that is different from the perspective captured by the imaging sensor. For another example, the representation of the physical environment may be transformed by graphically modifying (e.g., enlarging) a portion thereof so that the modified portion may be a representative but not real version of the original captured image. For another example, the representation of the physical environment may be transformed by graphically eliminating a portion thereof or blurring a portion thereof.

[0048] Augmented Virtual: An augmented virtual (AV) environment refers to a simulated environment in which a virtual environment or a computer-generated environment incorporates one or more sensory inputs from the physical environment. The sensory input may be a representation of one or more characteristics of the physical environment. For example, an AV park may have virtual trees and virtual buildings, but the faces of people are realistically reproduced from images taken of physical people. For another example, a virtual object may take the shape or color of a physical object imaged by one or more imaging sensors. For another example, a virtual object may take a shadow that conforms to the positioning of the sun in the physical environment.

[0049] Viewpoint-locked virtual objects: When a computer system displays a virtual object at the same position and / or location in a user's viewpoint, the virtual object is viewpoint-locked even if the user's viewpoint shifts (e.g., changes). In embodiments where the computer system is a head-mounted device, the user's viewpoint is locked to the forward direction of the user's head (e.g., when the user is looking straight ahead, the user's viewpoint is at least a portion of the user's field of view); thus, without moving the user's head, the user's viewpoint remains fixed even when the user's gaze shifts. In embodiments where the computer system has a display generation component (e.g., a display screen) that is repositionable relative to the user's head, the user's viewpoint is an augmented reality view presented to the user on the display generation component of the computer system. For example, a viewpoint-locked virtual object that is displayed in the upper left corner of the user's viewpoint when the user's viewpoint is in a first orientation (e.g., the user's head is facing north) continues to be displayed in the upper left corner of the user's viewpoint even when the user's viewpoint changes to a second orientation (e.g., the user's head is facing west). In other words, the position and / or location of the viewpoint-locked virtual object displayed in the user's viewpoint is independent of the user's position and / or orientation in the physical environment. In embodiments where the computer system is a head-mounted device, the user's viewpoint is locked to the orientation of the user's head, such that the virtual object is also referred to as a "head-locked virtual object."

[0050] Environment-locked visual objects: A virtual object is environment-locked (alternatively, "world-locked") when a computer system displays a virtual object at a position and / or location in a user's viewpoint that is based on (e.g., selected with reference to and / or anchored to) a location and / or object in a three-dimensional environment (e.g., a physical environment or a virtual environment). As the user's viewpoint moves, the location and / or objects in the environment change relative to the user's viewpoint, which causes the environment-locked virtual object to be displayed at a different location and / or location in the user's viewpoint. For example, an environment-locked virtual object locked to a tree immediately in front of the user is displayed at the center of the user's viewpoint. When the user's viewpoint shifts to the right (e.g., the user's head turns to the right) such that the tree is now to the left of center in the user's viewpoint (e.g., the tree location in the user's viewpoint shifts), the environment-locked virtual object locked to the tree is displayed to the left of center in the user's viewpoint. In other words, the position and / or orientation of the virtual object that is locked to the environment in the user's viewpoint depends on the position and / or orientation of the object and / or the position to which the virtual object is locked in the environment. In some embodiments, the computer system uses a stationary reference system (e.g., a coordinate system anchored to a fixed position and / or object in the physical environment) to determine the positioning of the virtual object that is locked to the user's viewpoint. The virtual object that is locked to the environment can be locked to a stationary part of the environment (e.g., a floor, wall, table, or other stationary object), or can be locked to a movable part of the environment (e.g., a vehicle, animal, person, or even a representation of a part of the user's body that moves independently of the user's viewpoint, such as a hand, wrist, arm, or foot of the user) so that the virtual object moves as the viewpoint or the part of the environment moves to maintain a fixed relationship between the virtual object and the part of the environment.

[0051] In some embodiments, an environment-locked or viewpoint-locked virtual object exhibits an inertial following behavior that reduces or delays the movement of the environment-locked or viewpoint-locked virtual object relative to the movement of the reference point followed by the virtual object. In some embodiments, when exhibiting inertial following behavior, when detecting the movement of a reference point (e.g., a portion of the environment, a viewpoint, or a point fixed relative to the viewpoint, such as a point between 5 cm and 300 cm from the viewpoint) that the virtual object is following, the computer system intentionally delays the movement of the virtual object. For example, when the reference point (e.g., the portion of the environment or the viewpoint) moves at a first speed, the virtual object is moved by the device to remain locked to the reference point, but moves at a second speed that is slower than the first speed (e.g., until the reference point stops moving or slows down, at which point the virtual object begins to catch up with the reference point). In some embodiments, when the virtual object exhibits inertial following behavior, the device ignores small amounts of movement of the reference point (e.g., ignoring movements of the reference point below a threshold movement amount, such as moving 0 to 5 degrees or moving 0 to 50 cm). For example, when a reference point (e.g., the portion of the environment or viewpoint to which the virtual object is locked) moves a first amount, the distance between the reference point and the virtual object increases (e.g., because the virtual object is being displayed so as to maintain a fixed or substantially fixed position relative to a viewpoint or portion of the environment that is different from the reference point to which the virtual object is locked), and when the reference point (e.g., the portion of the environment or viewpoint to which the virtual object is locked) moves a second amount greater than the first amount, the distance between the reference point and the virtual object initially increases (e.g., because the virtual object is being displayed so as to maintain a fixed or substantially fixed position relative to a viewpoint or portion of the environment that is different from the reference point to which the virtual object is locked), and then decreases as the amount of movement of the reference point increases above a threshold (e.g., a “lazy follow” threshold) because the virtual object is moved by the computer system to maintain a fixed or substantially fixed position relative to the reference point. In some embodiments, maintaining a substantially fixed position of the virtual object relative to the reference point includes displaying the virtual object within a threshold distance (e.g., 1 cm, 2 cm, 3 cm, 5 cm, 15 cm, 20 cm, 50 cm) of the reference point in one or more dimensions (e.g., up / down, left / right, and / or forward / backward relative to the position of the reference point).

[0052] Hardware: There are many different types of electronic systems that enable a person to sense various XR environments and / or interact with various CGR environments. Examples include head-mounted systems, projection-based systems, heads-up displays (HUDs), vehicle windshields with integrated display capabilities, windows with integrated display capabilities, displays formed as lenses designed to be placed on a person's eyes (e.g., similar to contact lenses), headphones / earpieces, speaker arrays, input systems (e.g., wearable or handheld controllers with or without tactile feedback), smartphones, tablet devices, and desktop / laptop computers. A head-mounted system can have one or more speakers and an integrated opaque display. Alternatively, a head-mounted system can be configured to accept an external opaque display (e.g., a smartphone). A head-mounted system can incorporate one or more imaging sensors for capturing images or video of the physical environment and / or one or more microphones for capturing audio of the physical environment. Instead of an opaque display, a head-mounted system can have a transparent or translucent display. A transparent or translucent display can have a medium through which light representing the image is directed to a person's eyes. The display can utilize digital light projection, OLED, LED, uLED, liquid crystal on silicon, laser scanning light source, or any combination of these technologies. The medium can be an optical waveguide, a hologram medium, an optical combiner, an optical reflector, or any combination thereof. In one embodiment, a transparent or translucent display can be configured to become selectively opaque. The projection-based system can employ retinal projection technology that projects graphic images onto a person's retina. The projection system can also be configured to project virtual objects into a physical environment, such as as a hologram or on a physical surface. In some embodiments, the controller 110 is configured to manage and coordinate the user's XR experience. In some embodiments, the controller 110 includes a suitable combination of software, firmware, and / or hardware. Reference is made below to Figure 2The controller 110 is described in more detail. In some embodiments, the controller 110 is a computing device that is located locally or remotely relative to the scene 105 (e.g., the physical environment). For example, the controller 110 is a local server located within the scene 105. As another example, the controller 110 is a remote server (e.g., a cloud server, a central server, etc.) located outside the scene 105. In some embodiments, the controller 110 is communicatively coupled to the display generation component 120 (e.g., HMD, display, projector, touch screen, etc.) via one or more wired or wireless communication channels 144 (e.g., Bluetooth, IEEE 802.11x, IEEE802.16x, IEEE 802.3x, etc.). In another example, the controller 110 is included within a housing (e.g., a physical housing) of the display generating component 120 (e.g., an HMD or a portable electronic device including a display and one or more processors, etc.), one or more input devices of the input devices 125, one or more output devices of the output devices 155, one or more sensors of the sensors 190, and / or one or more peripheral devices of the peripheral devices 195, or shares the same physical housing or support structure with one or more of the above devices.

[0053] In some embodiments, the display generation component 120 is configured to provide an XR experience (e.g., at least the visual component of the XR experience) to the user. In some embodiments, the display generation component 120 includes a suitable combination of software, firmware, and / or hardware. Figure 3 Display generation component 120 is described in further detail. In some embodiments, the functionality of controller 110 is provided by and / or combined with display generation component 120.

[0054] According to some embodiments, display generation component 120 provides an XR experience to the user when the user is virtually and / or physically present within scene 105.

[0055] In some embodiments, the display generation component is worn on a part of the user's body (e.g., on his / her head, on his / her hand, etc.). In this way, the display generation component 120 includes one or more XR displays provided for displaying XR content. For example, in various embodiments, the display generation component 120 surrounds the user's field of view. In some embodiments, the display generation component 120 is a handheld device (such as a smart phone or tablet device) configured to present XR content, and the user holds a device with a display facing the user's field of view and a camera facing the scene 105. In some embodiments, the handheld device is optionally placed in a shell worn on the user's head. In some embodiments, the handheld device is optionally placed on a support (e.g., a tripod) in front of the user. In some embodiments, the display generation component 120 is an XR room, shell, or room configured to present XR content, wherein the user does not wear or hold the display generation component 120. Many user interfaces described with reference to one type of hardware for displaying XR content (e.g., a handheld device or a device on a tripod) may be implemented on another type of hardware for displaying XR content (e.g., an HMD or other wearable computing device). For example, a user interface showing interactions with XR content triggered based on interactions occurring in the space in front of a handheld device or a tripod-mounted device may similarly be implemented with an HMD, where the interactions occur in the space in front of the HMD and responses to the XR content are displayed via the HMD. Similarly, a user interface showing interactions with XR content triggered based on movement of a handheld device or a tripod-mounted device relative to a physical environment (e.g., scene 105 or a part of a user's body (e.g., the user's eyes, head, or hands)) may similarly be implemented with an HMD, where the movement is caused by movement of the HMD relative to the physical environment (e.g., scene 105 or a part of a user's body (e.g., the user's eyes, head, or hands)).

[0056] Despite Figure 1 Relevant features of operating environment 100 are shown, but those skilled in the art will recognize from this disclosure that various other features are not shown for the sake of brevity and so as not to obscure more relevant aspects of the example embodiments disclosed herein.

[0057] Figure 2is a block diagram of an example of a controller 110 according to some embodiments. While some specific features are shown, those skilled in the art will recognize from this disclosure that various other features are not shown for the sake of brevity and so as not to obscure more relevant aspects of the embodiments disclosed herein. To this end, as a non-limiting example, in some embodiments, the controller 110 includes one or more processing units 202 (e.g., a microprocessor, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a graphics processing unit (GPU), a central processing unit (CPU), a processing core, etc.), one or more input / output (I / O) devices 206, one or more communication interfaces 208 (e.g., a universal serial bus (USB), IEEE802.3x, IEEE 802.11x, 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 210, a memory 220, and one or more communication buses 204 for interconnecting these components and various other components.

[0058] In some embodiments, the one or more communication buses 204 include circuits that interconnect and control communications between system components. In some embodiments, the one or more I / O devices 206 include at least one of a keyboard, a mouse, a touch pad, a joystick, one or more microphones, one or more speakers, one or more image sensors, one or more displays, etc.

[0059] The memory 220 includes a high-speed random access memory, such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a double data rate random access memory (DDR RAM), or other random access solid-state memory devices. In some embodiments, the memory 220 includes a 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 220 optionally includes one or more storage devices located away from the one or more processing units 202. The memory 220 includes a non-transitory computer-readable storage medium. In some embodiments, the memory 220 or the non-transitory computer-readable storage medium of the memory 220 stores the following programs, modules, and data structures or subsets thereof, including an optional operating system 230 and an XR experience module 240.

[0060] The operating system 230 includes instructions for handling various basic system services and for performing hardware-related tasks. In some embodiments, the XR experience module 240 is configured to manage and coordinate single or multiple XR experiences of one or more users (e.g., a single XR experience of one or more users, or multiple XR experiences of corresponding groups of one or more users). To this end, in various embodiments, the XR experience module 240 includes a data acquisition unit 241, a tracking unit 242, a coordination unit 246, and a data transmission unit 248.

[0061] In some embodiments, the data acquisition unit 241 is configured to obtain Figure 1 120, and optionally obtains data (e.g., presentation data, interaction data, sensor data, location data, etc.) from one or more of input device 125, output device 155, sensor 190, and / or peripheral device 195. To this end, in various embodiments, data acquisition unit 241 includes instructions and / or logic for instructions as well as heuristics and metadata for the heuristics.

[0062] In some embodiments, tracking unit 242 is configured to map scene 105 and track at least display generation component 120 relative to Figure 1 105, and optionally relative to the position / location of one or more of the tracked input device 125, the output device 155, the sensor 190, and / or the peripheral device 195. To this end, in various embodiments, the tracking unit 242 includes instructions and / or logic for the instructions and heuristics and metadata for the heuristics. In some embodiments, the tracking unit 242 includes a hand tracking unit 244 and / or an eye tracking unit 243. In some embodiments, the hand tracking unit 244 is configured to track the position / location of one or more parts of the user's hand, and / or the position / location of one or more parts of the user's hand relative to the user's hand. Figure 1 The movement of the scene 105 relative to the display generation component 120 and / or relative to a coordinate system (the coordinate system is defined relative to the user's hand). Figure 4 The hand tracking unit 244 is described in more detail. In some embodiments, the eye tracking unit 243 is configured to track the position or movement of the user's gaze (or more generally, the user's eyes, face, or head) relative to the scene 105 (e.g., relative to the physical environment and / or relative to the user (e.g., the user's hands)) or relative to the XR content displayed via the display generation component 120. Figure 5 The eye tracking unit 243 is described in more detail.

[0063] In some embodiments, coordination unit 246 is configured to manage and coordinate the XR experience presented to the user by display generation component 120, and optionally by one or more of output device 155 and / or peripherals 195. To this end, in various embodiments, coordination unit 246 includes instructions and / or logic for instructions and heuristics and metadata for the heuristics.

[0064] In some embodiments, data transfer unit 248 is configured to transfer data (e.g., presentation data, position data, etc.) to at least display generation component 120, and optionally to one or more of input device 125, output device 155, sensor 190, and / or peripheral device 195. To this end, in various embodiments, data transfer unit 248 includes instructions and / or logic for instructions as well as heuristics and metadata for the heuristics.

[0065] Although the data acquisition unit 241, the tracking unit 242 (e.g., including the eye tracking unit 243 and the hand tracking unit 244), the coordination unit 246, and the data transmission unit 248 are illustrated as residing on a single device (e.g., the controller 110), it should be understood that in other embodiments, any combination of the data acquisition unit 241, the tracking unit 242 (e.g., including the eye tracking unit 243 and the hand tracking unit 244), the coordination unit 246, and the data transmission unit 248 may be located in separate computing devices.

[0066] also, Figure 2 It serves more as a functional description of various features that may be present in a particular implementation, as opposed to a block diagram of the embodiments described herein. As one of ordinary skill in the art will recognize, items shown separately may be combined, and some items may be separated. For example, Figure 2 Some functional modules shown separately in the figure may be implemented in a single module, and the various functions of a single functional block may be implemented by one or more functional blocks in various embodiments. The actual number of modules and the division of specific functions and how the features are distributed among them will vary depending on the specific implementation, and in some embodiments, depends in part on the specific combination of hardware, software and / or firmware selected for a specific implementation.

[0067] Figure 31 is a block diagram of an example of a display generation component 120 according to some embodiments. Although some specific features are shown, those skilled in the art will recognize from this disclosure that various other features are not shown for the sake of brevity and so as not to obscure more relevant aspects of the embodiments disclosed herein. For this purpose, as a non-limiting example, in some embodiments, the display generation component 120 (e.g., an HMD) includes one or more processing units 302 (e.g., a microprocessor, an ASIC, an FPGA, a GPU, a CPU, a processing core, etc.), one or more input / output (I / O) devices and sensors 306, one or more communication interfaces 308 (e.g., USB, FIREWIRE, THUNDERBOLT, IEEE 802.3x, IEEE802.11x, IEEE 802.16x, GSM, CDMA, TDMA, GPS, IR, BLUETOOTH, ZIGBEE and / or similar types of interfaces), one or more programming (e.g., I / O) interfaces 310, one or more XR displays 312, one or more optional internal-facing and / or external-facing image sensors 314, a memory 320, and one or more communication buses 304 for interconnecting these components and various other components.

[0068] In some embodiments, one or more communication buses 304 include circuits for interconnecting and controlling communications between various system components. In some embodiments, one or more I / O devices and sensors 306 include an inertial measurement unit (IMU), an accelerometer, a gyroscope, a thermometer, one or more physiological sensors (e.g., a blood pressure monitor, a heart rate monitor, a blood oxygen sensor, a blood glucose sensor, etc.), one or more microphones, one or more speakers, a haptic engine, and / or one or more depth sensors (e.g., structured light, time of flight, etc.), etc.

[0069] In some embodiments, one or more XR displays 312 are configured to provide an XR experience to the user. In some embodiments, one or more XR displays 312 correspond to holographic, digital light processing (DLP), liquid crystal display (LCD), liquid crystal on silicon (LCoS), organic light emitting field effect transistor (OLET), organic light emitting diode (OLED), surface conduction electron emission display (SED), field emission display (FED), quantum dot light emitting diode (QD-LED), microelectromechanical system (MEMS) and / or similar display types. In some embodiments, one or more XR displays 312 correspond to diffraction, reflection, polarization, holographic and other waveguide displays. For example, the display generation component 120 (e.g., HMD) includes a single XR display. In another example, the display generation component 120 includes an XR display for each eye of the user. In some embodiments, one or more XR displays 312 can present MR and VR content. In some embodiments, one or more XR displays 312 can present MR or VR content.

[0070] In some embodiments, the one or more image sensors 314 are configured to obtain image data corresponding to at least a portion of the user's face, including the user's eyes (and may be referred to as an eye tracking camera). In some embodiments, the one or more image sensors 314 are configured to obtain image data corresponding to the user's hands and, optionally, at least a portion of the user's arms (and may be referred to as a hand tracking camera). In some embodiments, the one or more image sensors 314 are configured to face forward so as to obtain image data corresponding to the scene that the user would see in the absence of the display generating component 120 (e.g., HMD) (and may be referred to as a scene camera). The one or more optional image sensors 314 may 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, and / or one or more event-based cameras, etc.

[0071] The memory 320 includes a high-speed random access memory, such as a DRAM, SRAM, DDR RAM, or other random access solid-state memory device. In some embodiments, the memory 320 includes a 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 320 optionally includes one or more storage devices located away from the one or more processing units 302. The memory 320 includes a non-transitory computer-readable storage medium. In some embodiments, the memory 320 or the non-transitory computer-readable storage medium of the memory 320 stores the following programs, modules, and data structures or a subset thereof, including an optional operating system 330 and an XR rendering module 340.

[0072] The operating system 330 includes processes for handling various basic system services and for performing hardware-related tasks. In some embodiments, the XR rendering module 340 is configured to present XR content to a user via one or more XR displays 312. To this end, in various embodiments, the XR rendering module 340 includes a data acquisition unit 342, an XR rendering unit 344, an XR map generation unit 346, and a data transmission unit 348.

[0073] In some embodiments, the data acquisition unit 342 is configured to at least Figure 1 The controller 110 obtains data (e.g., presentation data, interaction data, sensor data, location data, etc.). For the purpose, in various embodiments, the data acquisition unit 342 includes instructions and / or logic for instructions and heuristics and metadata for the heuristics.

[0074] In some embodiments, the XR rendering unit 344 is configured to render XR content via one or more XR displays 312. For such purposes, in various embodiments, the XR rendering unit 344 includes instructions and / or logic for the instructions and heuristics and metadata for the heuristics.

[0075] In some embodiments, the XR map generation unit 346 is configured to generate an XR map (e.g., a 3D map of a mixed reality scene or a map of a physical environment in which a computer-generated object can be placed to generate an extended reality) based on the media content data. For such purposes, in various embodiments, the XR map generation unit 346 includes instructions and / or logic for the instructions and heuristics and metadata for the heuristics.

[0076] In some embodiments, the data transmission unit 348 is configured to transmit data (e.g., presentation data, position data, etc.) to at least the controller 110, and optionally one or more of the input device 125, the output device 155, the sensor 190, and / or the peripheral device 195. For such purposes, in various embodiments, the data transmission unit 348 includes instructions and / or logic for the instructions and heuristics and metadata for the heuristics.

[0077] Although the data acquisition unit 342, the XR rendering unit 344, the XR map generation unit 346, and the data transmission unit 348 are shown as residing on a single device (e.g., Figure 1 , but it should be understood that in other embodiments, any combination of the data acquisition unit 342, the XR rendering unit 344, the XR mapping generation unit 346, and the data transmission unit 348 may be located in a separate computing device.

[0078] also, Figure 3 More as a functional description of various features that may be present in a particular implementation, as opposed to a block diagram of the embodiments described herein. As one of ordinary skill in the art will recognize, items shown separately may be combined, and some items may be separated. For example, Figure 3 Some functional modules shown separately in the figure may be implemented in a single module, and the various functions of a single functional block may be implemented by one or more functional blocks in various embodiments. The actual number of modules and the division of specific functions and how the features are distributed among them will vary depending on the specific implementation, and in some embodiments, depends in part on the specific combination of hardware, software and / or firmware selected for a specific implementation.

[0079] Figure 4 is a schematic illustration of an example implementation of the hand tracking device 140. In some implementations, the hand tracking device 140 ( Figure 1 ) is controlled by the hand tracking unit 244 ( Figure 2 ) to track the position / location of one or more parts of a user's hand and / or one or more parts of a user's hand relative to Figure 1The hand tracking device 140 can be used to monitor movement of the scene 105 (e.g., relative to a portion of the physical environment surrounding the user, relative to the display generation component 120, or relative to a portion of the user (e.g., the user's face, eyes, or head), and / or relative to a coordinate system (which is defined relative to the user's hands)). In some embodiments, the hand tracking device 140 is part of the display generation component 120 (e.g., embedded in or attached to the head-mounted device). In some embodiments, the hand tracking device 140 is separate from the display generation component 120 (e.g., located in a separate housing or attached to a separate physical support structure).

[0080] In some embodiments, the hand tracking device 140 includes an image sensor 404 (e.g., one or more IR cameras, 3D cameras, depth cameras, and / or color cameras, etc.) that captures three-dimensional scene information including at least a human user's hand 406. The image sensor 404 captures hand images with sufficient resolution so that fingers and their corresponding positions can be distinguished. The image sensor 404 typically captures images of other parts of the user's body, or may also capture images of all parts of the body, and may have zoom capabilities or a dedicated sensor with increased magnification to capture images of the hand with a desired resolution. In some embodiments, the image sensor 404 also captures 2D color video images of the hand 406 and other elements of the scene. In some embodiments, the image sensor 404 is used in combination with other image sensors to capture the physical environment of the scene 105, or is used as an image sensor to capture the physical environment of the scene 105. In some embodiments, the image sensor is positioned relative to the user or the user's environment in a manner that the field of view of the image sensor 404 or a portion thereof is used to define an interactive space, in which the hand movements captured by the image sensor are regarded as input to the controller 110.

[0081] In some embodiments, the image sensor 404 outputs a sequence of frames containing 3D mapping data (and in addition, possible color image data) to the controller 110, which extracts high-level information from the mapping data. This high-level information is typically provided to an application running on the controller via an application program interface (API), which drives the display generation component 120 accordingly. For example, a user can interact with the software running on the controller 110 by moving his hand 406 and changing his hand posture.

[0082] In some embodiments, the image sensor 404 projects a speckled pattern onto a scene containing the hand 406 and captures an image of the projected pattern. In some embodiments, the controller 110 calculates the 3D coordinates of points in the scene (including points on the surface of the user's hand) by triangulation based on the lateral offset of the spots in the pattern. This method is advantageous because it does not require the user to hold or wear any kind of beacon, sensor, or other marker. The method gives the depth coordinates of points in the scene at a specific distance from the image sensor 404 relative to a predetermined reference plane. In the present disclosure, it is assumed that the image sensor 404 defines an orthogonal set of x-axis, y-axis, and z-axis, so that the depth coordinates of points in the scene correspond to the z component measured by the image sensor. Alternatively, the image sensor 404 (e.g., a hand tracking device) may use other 3D mapping methods based on a single or multiple cameras or other types of sensors, such as stereo imaging or time-of-flight measurement.

[0083] In some embodiments, the hand tracking device 140 captures and processes a time series of depth maps containing the user's hand as the user moves his hand (e.g., the entire hand or one or more fingers). Software running on the image sensor 404 and / or the processor in the controller 110 processes the 3D mapping data to extract patch descriptors of the hand in these depth maps. The software matches these descriptors with patch descriptors stored in the database 408 based on a previous learning process to estimate the pose of the hand in each frame. The pose typically includes the 3D position of the user's hand joints and finger tips.

[0084] The software can also analyze the trajectory of the hand and / or finger over multiple frames in the sequence to identify gestures. The pose estimation function described herein can be alternated with the motion tracking function so that only image block-based pose estimation is performed once every two (or more) frames, and tracking is used to find changes in pose that occur on the remaining frames. The pose, motion, and gesture information is provided to the application running on the controller 110 via the above-mentioned API. The program can, for example, move and modify the image presented on the display generation component 120 in response to the pose and / or gesture information, or perform other functions.

[0085] In some embodiments, gestures include air gestures. An air gesture is a gesture detected without the user touching an input element that is part of a device (e.g., computer system 101, one or more input devices 125, and / or hand tracking device 140) (or independent of an input element that is part of a device) and based on detected movement of a part of the user's body (e.g., head, one or more arms, one or more hands, one or more fingers, and / or one or more legs) through the air (including movement of the user's body relative to an absolute reference (e.g., the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (e.g., movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of a user's finger relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (e.g., a tap gesture in which the hand moves a predetermined amount and / or speed in a predetermined posture, or a shake gesture including a predetermined speed or amount of rotation of a part of the user's body)).

[0086] In some embodiments, according to some embodiments, the input gestures used in the various examples and embodiments described herein include air gestures for interacting with an XR environment (e.g., a virtual or mixed reality environment) performed by movement of a user's fingers relative to other fingers or parts of the user's hand. In some embodiments, an air gesture is a gesture detected without the user touching an input element that is part of the device (or independent of an input element that is part of the device) and based on detected movement of a part of the user's body through the air (including movement of the user's body relative to an absolute reference (e.g., the angle of the user's arm relative to the ground or the distance of the user's hand relative to the ground), movement relative to another part of the user's body (e.g., movement of the user's hand relative to the user's shoulder, movement of one of the user's hands relative to the user's other hand, and / or movement of the user's fingers relative to another finger or part of the user's hand), and / or absolute movement of a part of the user's body (e.g., a tap gesture in which the hand moves a predetermined amount and / or speed in a predetermined posture, or a shake gesture including a predetermined speed or rotation amount of a part of the user's body)).

[0087] In some embodiments where the input gesture is an in-air gesture (e.g., in the absence of physical contact with an input device that provides information to the computer system about which user interface element is the target of the user input, such as contact with a user interface element displayed on a touch screen, or contact with a mouse or trackpad to move a cursor to a user interface element), the gesture takes into account the user's attention (e.g., gaze) to determine the target of the user input (e.g., for direct input, as described below). Thus, in specific implementations involving in-air gestures, for example, the input gesture is combined with (e.g., simultaneously with) movement of the user's fingers and / or hand to detect attention (e.g., gaze) toward a user interface element to perform a pinch and / or tap input, as described in more detail below.

[0088] In some embodiments, an input gesture pointing to a user interface object is performed directly or indirectly with reference to the user interface object. For example, the user input is performed directly on the user interface object according to performing input with the user's hand at a location corresponding to the location of the user interface object in the three-dimensional environment (e.g., as determined based on the user's current viewpoint). In some embodiments, when the user's attention (e.g., gaze) to the user interface object is detected, the input gesture is performed indirectly on the user interface object according to the location of the user's hand not being at the location corresponding to the location of the user interface object in the three-dimensional environment while the user performs the input gesture. For example, for a direct input gesture, the user can guide the user's input to the user interface object by initiating a gesture at or near a location corresponding to the display location of the user interface object (e.g., within 0.5 cm, 1 cm, 5 cm, or a distance between 0 and 5 cm measured from the outer edge of the option or the center portion of the option). For an indirect input gesture, the user can guide the user's input to the user interface object by focusing on the user interface object (e.g., by gazing at the user interface object), and while focusing on the option, the user initiates an input gesture (e.g., at any location detectable by the computer system) (e.g., at a location that does not correspond to the display location of the user interface object).

[0089] In some embodiments, according to some embodiments, the input gestures (e.g., air gestures) used in various examples and embodiments described herein include pinch input and tap input for interacting with a virtual or mixed reality environment. For example, the pinch input and tap input described below are performed as air gestures.

[0090] In some embodiments, the pinch input is part of an air gesture that includes one or more of the following: a pinch gesture, a long pinch gesture, a pinch and drag gesture, or a double pinch gesture. For example, a pinch gesture as an air gesture includes movement of two or more fingers of a hand to contact each other, that is, optionally followed by an immediate (e.g., within 0 to 1 second) interruption of contact with each other. A long pinch gesture as an air gesture includes movement of two or more fingers of a hand in contact with each other for at least a threshold amount of time (e.g., at least 1 second) before an interruption of contact with each other is detected. For example, a long pinch gesture includes the user maintaining a pinch gesture (e.g., in which two or more fingers are in contact), and the long pinch gesture continues until an interruption of contact between the two or more fingers is detected. In some embodiments, a double pinch gesture as an air gesture includes two (e.g., or more) pinch inputs (e.g., performed by the same hand) that are detected consecutively immediately (e.g., within a predefined time period) with each other. For example, the user performs a first pinch input (e.g., a pinch input or a long pinch input), releases the first pinch input (e.g., interrupts contact between two or more fingers), and performs a second pinch input within a predefined time period after releasing the first pinch input (e.g., within 1 second or within 2 seconds).

[0091] In some embodiments, the pinch and drag gesture as an air gesture includes a pinch gesture (e.g., a pinch gesture or a long pinch gesture) performed in conjunction with (e.g., following) a drag input that changes the position of the user's hand from a first position (e.g., the start position of the drag) to a second position (e.g., the end position of the drag). In some embodiments, the user maintains the pinch gesture while performing the drag input, and releases the pinch gesture (e.g., opens their two or more fingers) to end the drag gesture (e.g., at the second position). In some embodiments, the pinch input and the drag input are performed by the same hand (e.g., the user pinches two or more fingers to contact each other and moves the same hand to a second position in the air using the drag gesture). In some embodiments, a pinch input is performed by a first hand of a user, and a drag input is performed by a second hand of the user (e.g., the second hand of the user moves from a first position to a second position in the air while the user continues to pinch input with the first hand of the user. In some embodiments, the input gesture as an air gesture includes input performed using both hands of the user (e.g., pinch and / or tap input). For example, the input gesture includes two (e.g., or more) pinch inputs performed in conjunction with each other (e.g., simultaneously or within a predefined time period). For example, a first pinch gesture (e.g., a pinch input, a long pinch input, or a pinch and drag input) is performed using the first hand of the user, and in conjunction with the pinch input performed using the first hand, a second pinch input is performed using another hand (e.g., a second hand of the user's two hands). In some embodiments, movement between the two hands of the user (e.g., increasing and / or decreasing the distance or relative orientation between the two hands of the user).

[0092] In some embodiments, a tap input performed as an air gesture (e.g., pointing to a user interface element) includes movement of a user's finger toward the user interface element, movement of a user's hand toward the user interface element (optionally, extension of the user's finger toward the user interface element), downward movement of a user's finger (e.g., mimicking a mouse click motion or a tap on a touch screen), or other predefined movement of a user's hand. In some embodiments, a tap input performed as an air gesture is detected based on movement characteristics of the finger or hand performing the tap gesture movement of the finger or hand, which is a movement of the finger or hand away from the user's viewpoint and / or toward an object that is the target of the tap input, followed by an end of the movement. In some embodiments, the end of the movement is detected based on a change in the movement characteristics of the finger or hand performing the tap gesture (e.g., the end of the movement away from the user's viewpoint and / or toward an object that is the target of the tap input, a reversal of the direction of movement of the finger or hand, and / or a reversal of the acceleration direction of the movement of the finger or hand).

[0093] In some embodiments, it is determined that the user's attention is directed to a portion of the three-dimensional environment based on detection of a gaze directed to that portion of the three-dimensional environment (optionally, no other conditions are required). In some embodiments, it is determined that the user's attention is directed to a portion of the three-dimensional environment based on detection of a gaze directed to that portion of the three-dimensional environment using one or more additional conditions, such as requiring the gaze to be directed to the portion of the three-dimensional environment for at least a threshold duration (e.g., a dwell duration) and / or requiring the gaze to be directed to the portion of the three-dimensional environment when the user's viewpoint is within a distance threshold from the portion of the three-dimensional environment, so that the device determines that the user's attention is directed to the portion of the three-dimensional environment, wherein if one of these additional conditions is not met, the device determines that the attention is not directed to the portion of the three-dimensional environment to which the gaze is directed (e.g., until the one or more additional conditions are met).

[0094] In some embodiments, the detection of a ready state configuration of a user or a portion of a user is detected by a computer system. The detection of the ready state configuration of a hand is used by the computer system as an indication that the user may be preparing to interact with the computer system using one or more air gesture inputs (e.g., pinch, tap, pinch and drag, double pinch, long pinch, or other air gestures described herein) performed by the hand. For example, the ready state of the hand is determined based on whether the hand has a predetermined hand shape (e.g., a pre-pinch shape with the thumb and one or more fingers extended and spaced apart to prepare for a pinch or grab gesture, or a pre-tap with one or more fingers extended and the palm facing away from the user), based on whether the hand is in a predetermined position relative to the user's viewpoint (e.g., below the user's head and above the user's waist and extending at least 15 cm, 20 cm, 25 cm, 30 cm, or 50 cm from the body), and / or based on whether the hand has moved in a particular manner (e.g., toward an area in front of the user above the user's waist and below the user's head or away from the user's body or legs). In some embodiments, the ready state is used to determine whether an interactive element of a user interface responds to attention (e.g., gaze) input.

[0095] In scenarios where input is described with reference to air gestures, it should be understood that similar gestures can be detected using a hardware input device attached to or held by one or more hands of a user, where the position of the hardware input device in space can be tracked using optical tracking, one or more accelerometers, one or more gyroscopes, one or more magnetometers, and / or one or more inertial measurement units, and the position and / or movement of the hardware input device is used instead of the position and / or movement of the one or more hands in the corresponding air gesture. In scenarios where input is described with reference to air gestures, it should be understood that similar gestures may be detected using a hardware input device attached to or held by one or more hands of a user, the user input may be detected using controls included in the hardware input device, such as one or more touch-sensitive input elements, one or more pressure-sensitive input elements, one or more buttons, one or more knobs, one or more dials, one or more joysticks, one or more hand or finger overlays that can detect the position or position change of parts of a hand and / or finger relative to each other, relative to the user's body and / or relative to the user's physical environment, and / or other hardware input device controls, wherein user input with controls included in the hardware input device is used in place of hand and / or finger gestures, such as an air tap or air pinch in the corresponding air gestures. For example, a selection input described as being performed with an air tap or air pinch input may alternatively be detected with a button press, a tap on a touch-sensitive surface, a press on a pressure-sensitive surface, or other hardware input. As another example, movement input described as being performed with an air pinch and drag may alternatively be detected based on interaction with a hardware input control (e.g., a button press and hold, a touch on a touch-sensitive surface, a press on a pressure-sensitive surface, or other hardware input followed by movement of a hardware input device (e.g., along with a hand associated with the hardware input device) in space). Similarly, two-handed input involving movement of hands relative to each other may be performed using one air gesture and one hardware input device in the hand not performing the air gesture, two hardware input devices held in different hands, or two air gestures performed by different hands using various combinations of air gestures and / or inputs detected by one or more of the above hardware input devices.

[0096] In some embodiments, the software may be downloaded to the controller 110 in electronic form, for example, over a network, or may alternatively be provided on a tangible, non-transitory medium such as an optical, magnetic, or electronic memory medium. In some embodiments, the database 408 is also stored in a memory associated with the controller 110. Alternatively or in addition, some or all of the described functions of the computer may be implemented in dedicated hardware, such as a custom or semi-custom integrated circuit or a programmable digital signal processor (DSP). Although in Figure 4Controller 110 is shown in FIG. 1 , but some or all of the processing functions of the controller may be performed by a suitable microprocessor and software or by dedicated circuitry within the housing of the image sensor 404 (e.g., a hand tracking device) or other device associated with the image sensor 404, for example, as a separate unit from the image sensor 404. In some embodiments, at least some of these processing functions may be performed by a suitable processor integrated with the display generation component 120 (e.g., in a television receiver, handheld device, or head-mounted device) or with any other suitable computerized device (such as a game console or media player). The sensing functions of the image sensor 404 may also be integrated into a computer or other computerized device to be controlled by the sensor output.

[0097] Figure 4 Also included is a schematic representation of a depth map 410 captured by the image sensor 404 according to some embodiments. As described above, the depth map includes a matrix of pixels with corresponding depth values. Pixels 412 corresponding to the hand 406 have been segmented from the background and wrist in the figure. The brightness of each pixel within the depth map 410 is inversely proportional to its depth value (i.e., the measured z distance from the image sensor 404), where gray shades become darker as depth increases. The controller 110 processes these depth values ​​in order to identify and segment components of the image that have human hand characteristics (i.e., a group of adjacent pixels). These characteristics may include, for example, overall size, shape, and motion from frame to frame in the depth map sequence.

[0098] Figure 4 Also schematically shown is a hand skeleton 414 that the controller 110 eventually extracts from the depth map 410 of the hand 406 according to some embodiments. Figure 4 In the hand skeleton 414, a hand background 416 that has been segmented from the original depth map is superimposed. In some embodiments, key feature points of the hand and optionally on the wrist or arm connected to the hand (e.g., points corresponding to knuckles, finger tips, palm center, end of the hand connected to the wrist, etc.) are identified and located on the hand skeleton 414. In some embodiments, the controller 110 uses the position and movement of these key feature points over multiple image frames to determine the gesture performed by the hand or the current state of the hand according to some embodiments.

[0099] Figure 5 The eye tracking device 130 ( Figure 1 ). In some embodiments, the eye tracking device 130 is composed of an eye tracking unit 243 ( Figure 2) controls to track the position and movement of the user's gaze relative to the scene 105 or relative to the XR content displayed via the display generation component 120. In some embodiments, the eye tracking device 130 is integrated with the display generation component 120. For example, in some embodiments, when the display generation component 120 is a head-mounted device (such as headphones, helmets, goggles, or glasses) or a handheld device placed in a wearable frame, the head-mounted device includes both components for generating XR content for viewing by the user and components for tracking the user's gaze relative to the XR content. In some embodiments, the eye tracking device 130 is separate from the display generation component 120. For example, when the display generation component is a handheld device or an XR room, the eye tracking device 130 is optionally a device separate from the handheld device or the XR room. In some embodiments, the eye tracking device 130 is a head-mounted device or a part of a head-mounted device. In some embodiments, the head-mounted eye tracking device 130 is optionally used in conjunction with a display generation component that is also head-mounted or a display generation component that is not head-mounted. In some embodiments, the eye tracking device 130 is not a head mounted device, and is optionally used in conjunction with a head mounted display generation component. In some embodiments, the eye tracking device 130 is not a head mounted device, and is optionally part of a non-head mounted display generation component.

[0100] In some embodiments, the display generation component 120 uses a display mechanism (e.g., a left near-eye display panel and a right near-eye display panel) to display a frame including a left image and a right image in front of the user's eyes, thereby providing a 3D virtual view to the user. For example, the head-mounted display generation component may include a left optical lens and a right optical lens (referred to herein as eye lenses) located between the display and the user's eyes. In some embodiments, the display generation component may include or be coupled to one or more external cameras that capture a video of the user's environment for display. In some embodiments, the head-mounted display generation component may have a transparent or translucent display, and display a virtual object on the transparent or translucent display, and the user can directly view the physical environment through the transparent or translucent display. In some embodiments, the display generation component projects the virtual object into the physical environment. The virtual object may, for example, be projected on a physical surface or projected as a hologram so that an individual using the system observes the virtual object superimposed on the physical environment. In this case, separate display panels and image frames for the left and right eyes may not be required.

[0101] like Figure 5As shown in , in some embodiments, the eye tracking device 130 (e.g., gaze tracking device) includes at least one eye tracking camera (e.g., an infrared (IR) or near infrared (NIR) camera), and an illumination source (e.g., an IR or NIR light source, such as an array or ring of LEDs) that emits light (e.g., IR or NIR light) toward the user's eyes. The eye tracking camera can be pointed at the user's eyes to receive the IR or NIR light reflected directly from the eyes by the light source, or alternatively can be pointed at "hot" mirrors located between the user's eyes and the display panel, which reflect the IR or NIR light from the eyes to the eye tracking camera while allowing visible light to pass through. The eye tracking device 130 optionally captures images of the user's eyes (e.g., as a video stream captured at 60-120 frames per second (fps)), analyzes the images to generate gaze tracking information, and transmits the gaze tracking information to the controller 110. In some embodiments, the user's two eyes are tracked separately by corresponding eye tracking cameras and illumination sources. In some embodiments, only one eye of the user is tracked by the corresponding eye tracking camera and illumination source.

[0102] In some embodiments, the eye tracking device 130 is calibrated using a device-specific calibration process to determine the parameters of the eye tracking device for a specific operating environment 100, such as the 3D geometric relationships and parameters of the LED, camera, thermal mirror (if present), eye lens, and display screen. The device-specific calibration process can be performed at a factory or another facility before the AR / VR equipment is delivered to the end user. The device-specific calibration process can be an automatic calibration process or a manual calibration process. According to some embodiments, the user-specific calibration process may include an estimate of the eye parameters of a specific user, such as pupil position, foveal position, optical axis, visual axis, eye spacing, etc. According to some embodiments, once the device-specific parameters and user-specific parameters are determined for the eye tracking device 130, a flash-assisted method can be used to process the images captured by the eye tracking camera to determine the current visual axis and the user's gaze point relative to the display.

[0103] like Figure 5As shown in , the eye tracking device 130 (e.g., 130A or 130B) includes an eye lens 520 and a gaze tracking system, which includes at least one eye tracking camera 540 (e.g., an infrared (IR) or near infrared (NIR) camera) positioned on the side of the user's face on which eye tracking is performed, and an illumination source 530 (e.g., an IR or NIR light source, such as an array or ring of NIR light emitting diodes (LEDs)) that emits light (e.g., IR or NIR light) toward the user's eye 592. The eye tracking camera 540 can be directed toward a mirror 550 (which reflects IR or NIR light from the eye 592 while allowing visible light to pass) located between the user's eye 592 and a display 510 (e.g., a left display panel or a right display panel of a head-mounted display, or a display of a handheld device, a projector, etc.) Figure 5 ), or alternatively may be directed toward the user's eye 592 to receive reflected IR or NIR light from the eye 592 (e.g., as shown in the top portion of Figure 5 ).

[0104] In some embodiments, the controller 110 renders AR or VR frames 562 (e.g., left and right frames for left and right display panels) and provides the frames 562 to the display 510. The controller 110 uses the gaze tracking input 542 from the eye tracking camera 540 for various purposes, such as for processing the frames 562 for display. The controller 110 optionally estimates the user's gaze point on the display 510 based on the gaze tracking input 542 obtained from the eye tracking camera 540 using a flash-assisted method or other suitable method. The gaze point estimated from the gaze tracking input 542 is optionally used to determine the direction in which the user is currently looking.

[0105] Several possible use cases for the user's current gaze direction are described below and are not intended to be limiting. As an example use case, the controller 110 may render virtual content differently based on the determined direction of the user's gaze. For example, the controller 110 may generate virtual content at a higher resolution in the foveal region determined according to the user's current gaze direction than in the peripheral region. As another example, the controller may position or move virtual content in a view based at least in part on the user's current gaze direction. As another example, the controller may display specific virtual content in a view based at least in part on the user's current gaze direction. As another example use case in an AR application, the controller 110 may direct an external camera for capturing the physical environment of the XR experience to focus in the determined direction. The autofocus mechanism of the external camera may then focus on an object or surface in the environment that the user is currently looking at on the display 510. As another example use case, the eye lens 520 may be a focusable lens, and the controller uses gaze tracking information to adjust the focus of the eye lens 520 so that the virtual object that the user is currently looking at has an appropriate degree of convergence to match the convergence of the user's eye 592. The controller 110 can use the gaze tracking information to guide the eye lens 520 to adjust the focus so that nearby objects that the user is looking at appear at the correct distance.

[0106] In some embodiments, the eye tracking device is part of a head mounted device that includes a display (e.g., display 510), two eye lenses (e.g., eye lenses 520), an eye tracking camera (e.g., eye tracking camera 540), and a light source (e.g., light source 530 (e.g., IR or NIR LED)). The light source emits light (e.g., IR or NIR light) toward the user's eye 592. In some embodiments, the light sources may be arranged in a ring or circle around each of the lenses, such as Figure 5 In some embodiments, for example, eight light sources 530 (eg, LEDs) are arranged around each lens 520. However, more or fewer light sources 530 may be used, and other arrangements and locations of the light sources 530 may be used.

[0107] In some embodiments, the display 510 emits light in the visible range and does not emit light in the IR or NIR range, and therefore does not introduce noise into the gaze tracking system. Note that the positions and angles of the eye tracking cameras 540 are given by way of example and are not intended to be limiting. In some embodiments, a single eye tracking camera 540 is located on each side of the user's face. In some embodiments, two or more NIR cameras 540 may be used on each side of the user's face. In some embodiments, a camera 540 with a wider field of view (FOV) and a camera 540 with a narrower FOV may be used on each side of the user's face. In some embodiments, a camera 540 operating at one wavelength (e.g., 850 nm) and a camera 540 operating at a different wavelength (e.g., 940 nm) may be used on each side of the user's face.

[0108] like Figure 5 Embodiments of the gaze tracking system shown in may, for example, be used in computer generated reality, virtual reality, and / or mixed reality applications to provide a computer generated reality, virtual reality, augmented reality, and / or augmented virtual experience to a user.

[0109] Fig. 6A FIG. 2 shows a flash-assisted gaze tracking pipeline according to some embodiments. In some embodiments, the gaze tracking pipeline is implemented by a flash-assisted gaze tracking system (e.g., Figure 1 and Figure 5 The flash-assisted gaze tracking system can maintain a tracking state. Initially, the tracking state is off or "no". When in the tracking state, the flash-assisted gaze tracking system uses previous information from previous frames when analyzing the current frame to track the pupil outline and the flash in the current frame. When not in the tracking state, the flash-assisted gaze tracking system attempts to detect the pupil and the flash in the current frame, and if successful, initializes the tracking state to "yes" and continues with the next frame in the tracking state.

[0110] like Fig. 6A As shown in , the gaze tracking camera can capture left and right images of the user's left and right eyes. The captured images are then input to the gaze tracking pipeline for processing starting at 610. As indicated by the arrow returning to element 600, the gaze tracking system can continue to capture images of the user's eyes at a rate of, for example, 60 to 120 frames per second. In some embodiments, each group of captured images can be input to the pipeline for processing. However, in some embodiments or under some conditions, not all captured frames are processed by the pipeline.

[0111] At 610, for the currently captured image, if the tracking status is yes, the method proceeds to element 640. At 610, if the tracking status is no, the image is analyzed to detect the user's pupil and glint in the image, as indicated at 620. At 630, if the pupil and glint are successfully detected, the method proceeds to element 640. Otherwise, the method returns to element 610 to process the next image of the user's eye.

[0112] At 640, if advancing from element 610, the current frame is analyzed to track pupils and glints based in part on previous information from previous frames. At 640, if advancing from element 630, the tracking state is initialized based on the pupils and glints detected in the current frame. The processing results at element 640 are checked to verify that the results of tracking or detection can be credible. For example, the results can be checked to determine whether the pupil and a sufficient number of glints for performing gaze estimation are successfully tracked or detected in the current frame. At 650, if the results are not likely to be credible, at element 660, the tracking state is set to no, and the method returns to element 610 to process the next image of the user's eye. At 650, if the results are credible, the method advances to element 670. At 670, the tracking state is set to YES (if not already yes), and the pupil and glint information is passed to element 680 to estimate the user's gaze point.

[0113] Fig. 6A It is intended to be used as an example of an eye tracking technology that can be used for a particular implementation. As recognized by one of ordinary skill in the art, according to various embodiments, other eye tracking technologies currently existing or developed in the future can be used in place of or in combination with the flash-assisted eye tracking technology described herein in a computer system 101 for providing an XR experience to a user.

[0114] Figure 6B Exemplary devices connected via one or more communication channels to participate in a transaction according to some embodiments are shown. One or more exemplary electronic devices (e.g., devices 602 and 604) are configured to optionally detect input (e.g., specific user input, NFC field), and optionally transmit payment information (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0115] Electronic devices (e.g., devices 602 and 604) are optionally configured to store payment account information associated with each payment account in one or more payment accounts. The payment account information includes, for example, one or more of the following: name or company name, billing address, login name, password, account number, expiration date, security code, telephone number, bank associated with the payment account (e.g., issuing bank) and card network identifier. In some embodiments, the payment account information includes an image, such as a photo of a payment card (e.g., a photo taken by the device and / or received by the device). In some embodiments, the electronic device receives user input including at least some payment account information (e.g., receiving a credit, debit, account or shopping card number and expiration date input by the user). In some embodiments, the electronic device detects at least some payment account information from an image (e.g., of a payment card captured by a camera sensor of the device). In some embodiments, the electronic device receives at least some payment account information from another device (e.g., another user device or server). In some embodiments, the electronic device receives payment account information from a server associated with another service (e.g., an application for renting or selling audio files and / or video files) for which the user or user device's account has previously made purchases or identified payment account data.

[0116] In some embodiments, a payment account is added to an electronic device (e.g., devices 602 and 604) so ​​that the payment account information is securely stored on the electronic device. In some embodiments, after the user initiates such a process, the electronic device transmits the payment account information to a transaction coordination server, which then communicates with a server operated by the account's payment network (e.g., a payment server) to ensure the validity of the information. The electronic device is optionally configured to receive a script from the server that allows the electronic device to program the account's payment information onto a secure element.

[0117] In some embodiments, the communication between the electronic devices 602 and 604 facilitates a transaction (e.g., a general transaction or a specific transaction). For example, a first electronic device (e.g., 602) may be used as a configuration device or a management device, and may send a notification of new or updated payment account data (e.g., information about a new account, updated information about an existing account, and / or a warning about an existing account) to a second electronic device (e.g., 604). In another example, a first electronic device (e.g., 602) may send data to a second electronic device, wherein the data reflects information about a payment transaction facilitated at the first electronic device. The information optionally includes one or more of the following: the payment amount, the account used, the time of purchase, and whether to change the default account. The second device (e.g., 604) optionally uses such information to update the default payment account (e.g., based on a learning algorithm or explicit user input).

[0118] Electronic devices (e.g., 602, 604) are configured to communicate with each other via any of a variety of networks. For example, the devices communicate using a Bluetooth connection 616 (e.g., including a traditional Bluetooth connection or a Bluetooth low energy connection) or using a WiFi network 614. Communications between user devices are optionally regulated to reduce the likelihood of inappropriate sharing of information between devices. For example, communication regarding payment information requires that the communicating devices be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0119] In some embodiments, the electronic device (e.g., 602, 604) is used to communicate with a point-of-sale (POS) payment terminal 606, which optionally supports NFC. The communication is optionally carried out using various communication channels and / or technologies. In some embodiments, the electronic device (e.g., 602, 604) uses an NFC channel 618 to communicate with the payment terminal 606. In some embodiments, the payment terminal 606 uses a peer-to-peer NFC mode to communicate with the electronic device (e.g., 602, 604). The electronic device (e.g., 602, 604) is optionally configured to transmit a signal to the payment terminal 606, which includes payment information of a payment account (e.g., a default account or an account selected for a specific transaction).

[0120] In some embodiments, continuing the transaction includes transmitting a signal including payment information of an account (such as a payment account). In some embodiments, continuing the transaction includes reconfiguring the electronic device (e.g., 602, 604) to respond as a contactless payment card (such as an NFC-enabled contactless payment card) and then transmitting the credentials of the account via NFC to, for example, a payment terminal 606. In some embodiments, after transmitting the credentials of the account via NFC, the electronic device is reconfigured not to respond as a contactless payment card (e.g., authorization is required before being reconfigured again to respond as a contactless payment card via NFC).

[0121] In some embodiments, the generation and / or transmission of the signal is controlled by a security element in an electronic device (e.g., 602, 604). Before issuing payment information, the security element optionally requires specific user input. For example, the security element optionally requires: detecting an electronic device being worn, detecting button presses, detecting password input, detecting touch, detecting one or more option selections (e.g., option selections received when interacting with an application), detecting fingerprint signatures, detecting voice or voice commands, and / or detecting gestures or movements (e.g., rotation or acceleration). In some embodiments, if a communication channel (e.g., NFC communication channel) with another device (e.g., payment terminal 606) is established within a defined time period from when the input is detected, the security element issues payment information so that it is transmitted to another device (e.g., payment terminal 606). In some embodiments, the security element is a hardware component that controls the release of security information. In some embodiments, the security element is a software component that controls the release of security information.

[0122] In some embodiments, the protocol associated with transaction participation depends on, for example, the device type. For example, the conditions for generating and / or transmitting payment information may be different for a wearable device (e.g., device 604) and a phone (e.g., device 602). For example, the generation condition and / or transmission condition for a wearable device includes detecting that a button has been pressed (e.g., after security verification), while the corresponding condition for the phone does not require a button press, but requires detection of a specific interaction with the application. In some embodiments, the conditions for transmitting and / or publishing payment information include receiving specific inputs on each of a plurality of devices. For example, the publication of payment information optionally requires detection of a fingerprint and / or password at a device (e.g., device 602), and detection of a mechanical input (e.g., a button press) on another device (e.g., device 604).

[0123] The payment terminal 606 optionally uses the payment information to generate a signal for transmission to the payment server 612 to determine whether the payment is authorized. The payment server 612 optionally includes any device or system configured to receive the payment information associated with the payment account and determine whether the proposed purchase is authorized. In some embodiments, the payment server 612 includes a server of the issuing bank. The payment terminal 606 communicates directly with the payment server 612 or indirectly via one or more other devices or systems (e.g., a server of the acquiring bank and / or a server of the card network).

[0124] Payment server 612 optionally uses at least some of the payment information to identify the user account from a database of user accounts (e.g., 608). For example, each user account includes payment information. The account is optionally located by locating an account with specific payment information that matches the information from the POS communication. In some embodiments, payment is rejected when the provided payment information is inconsistent (e.g., the expiration date does not correspond to the credit card number, debit card number, or shopping card number) or when no account includes payment information that matches the information from the POS communication.

[0125] In some embodiments, the user account data further identifies one or more constraints (e.g., credit limit); current or previous balances; previous transaction dates, locations, and / or amounts; account status (e.g., active or frozen), and / or authorization instructions. In some embodiments, the payment server (e.g., 612) uses such data to determine whether to authorize a payment. For example, the payment server denies payment when the purchase amount added to the current balance would cause the account limit to be exceeded, when the account is frozen, when the previous transaction amount exceeds a threshold, or when the number or frequency of previous transactions exceeds a threshold.

[0126] In some embodiments, the payment server 612 responds to the POS payment terminal 606 with an indication of whether the proposed purchase is authorized or rejected. In some embodiments, the POS payment terminal 606 transmits a signal to the electronic device (e.g., 602, 604) to identify the result. For example, when the purchase is authorized (e.g., via a transaction coordination server that manages the transaction application on the user device), the POS payment terminal 606 sends a receipt to the electronic device (e.g., 602, 604). In some cases, the POS payment terminal 606 presents an output (e.g., a visual output or an audio output) indicating the result. The payment may be transmitted to the merchant as part of the authorization process, or may be transmitted later.

[0127] In some embodiments, the electronic device (e.g., 602, 604) participates in a transaction that is completed without involving the POS payment terminal 606. For example, upon detecting that the mechanical input has been received, the secure element in the electronic device (e.g., 602, 604) releases the payment information to allow an application on the electronic device to access the information (e.g., and transmit the information to a server associated with the application).

[0128] In some embodiments, the electronic device (e.g., 602, 604) is in a locked state or an unlocked state. In the locked state, the electronic device is powered on and is operable, but it is blocked from performing a predefined set of operations in response to user input. The predefined set of operations may include navigating between user interfaces, activating or deactivating a predefined set of functions, and activating or deactivating certain applications. The locked state can be used to prevent unconscious or unauthorized use of some functions of the electronic device, or to activate or deactivate some functions on the electronic device. In the unlocked state, the electronic device 602 is powered on and is operable, and is not blocked from performing at least a portion of a predefined set of operations that cannot be performed when in the locked state.

[0129] When the device is in the locked state, the device is said to be locked. In some embodiments, the device in the locked state can respond to a restricted set of user inputs, including inputs corresponding to attempts to convert the device to the unlocked state or inputs corresponding to shutting down the device.

[0130] In some embodiments, the security element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, the security element provides (or publishes) payment information (e.g., account number and / or transaction-specific dynamic security code). In some embodiments, the security element provides (or publishes) payment information in response to the device receiving authorization, and the authorization is, for example, user authentication (e.g., fingerprint authentication; password authentication; when the device is in an unlocked state, and optionally when the device has been continuously on the user's wrist since the device was unlocked by providing authentication credentials to the device, a double press of the hardware button is detected, wherein the device is determined to be in contact with the user's skin by periodically checking that the device is in contact with the user's skin. The device detects a fingerprint at the fingerprint sensor of the device (e.g., a fingerprint sensor integrated into a button). The device determines whether the fingerprint is consistent with the registered fingerprint. Based on determining that the fingerprint is consistent with the registered fingerprint, the security element provides (or publishes) payment information. Based on determining that the fingerprint is inconsistent with the registered fingerprint, the security element abandons providing (or publishing) payment information.

[0131] In the present disclosure, various input methods are described with respect to interaction with a computer system. When an input device or input method is used to provide an example, and another input device or input method is used to provide another example, it should be understood that each example is compatible with the input device or input method described with respect to another example and optionally utilizes the input device or input method. Similarly, various output methods are described with respect to interaction with a computer system. When an output device or output method is used to provide an example, and another output device or output method is used to provide another example, it should be understood that each example is compatible with the output device or output method described with respect to another example and optionally utilizes the output device or output method. Similarly, various methods are described with respect to interaction with a virtual environment or a mixed reality environment by a computer system. When an example is provided using interaction with a virtual environment, and another example is provided using a mixed reality environment, it should be understood that each example is compatible with the method described with respect to another example and optionally utilizes these methods. Therefore, the present disclosure discloses an embodiment as a combination of features of multiple examples, without exhaustively listing all features of the embodiment in the description of each example embodiment.

[0132] User interface and associated processes

[0133] Attention is now focused on embodiments of a user interface ("UI") and associated processes that may be implemented on a computer system, such as a portable multifunction device or a head-mounted device, that communicates with a display generating component, one or more input devices, and (optionally) a biometric sensor.

[0134] FIG. 7A to FIG. 7N An example of authorizing a security operation is shown. Figure 8 is a flow chart of an exemplary method 800 for facilitating user consent for security operations. Fig. 9 is a flow chart of an exemplary method 900 for authentication continuity of secure operations. Fig.10 is a flow chart of an exemplary method 1000 for authorizing security operations via an accessibility interface. FIG. 7A to FIG. 7N The user interface in is used to illustrate the process described below, including Figure 8 , Fig. 9 and Fig.10 process.

[0135] Fig. 7A An electronic device 700 including a display 700a is shown. Fig. 7AAt , user 704 is interacting with electronic device 700. Electronic device 700 may correspond to a tablet device, a wearable device (e.g., a head-mounted display), a smart phone, and / or a smart watch. In addition, display 700a may include or be coupled to a display generation component (e.g., a display controller, a touch-sensitive display system, a display (e.g., integrated and / or connected), a 3D display, a transparent display, a projector, and / or a head-up display). Electronic device 700 displays one or more interface objects on display 700a, such as displaying a login user interface 702. In some embodiments, the login user interface 702 corresponds to a virtual interface object within the XR environment. The login user interface 702 optionally includes various display fields, such as a username field 706 and a password field 708. The login user interface 702 also optionally includes an enable representation 710 for initiating a process for security operations, such as authorization of various display fields (e.g., "auto-fill"). In some embodiments, the security operation corresponds to a payment, such as, for example, providing payment information to a third-party service in order to purchase an item, such as providing credit card information to an e-commerce website to purchase shoes (e.g., with respect to Figure 7N In some embodiments, the security operation corresponds to providing access credentials for accessing an application. For example, the security operation provides access credentials to an application associated with a third-party service (e.g., a stock trading application) that requires user authentication before accessing the application. In some embodiments, the electronic device 700 enables the user 704 to manually enter information into fields 706 and / or 708 (e.g., using a displayed keyboard and / or using voice commands).

[0136] In some embodiments, such as Fig. 7AAs shown, electronic device 700 detects selection of affordance 710 by user 704 in order to initiate an autofill function to automatically fill information into fields 706 and / or 708. For example, display 700a is a touch-sensitive display, so that electronic device 700 detects touch input (e.g., tap or tap and hold) on affordance 710. In some embodiments, when device 700 is implemented in an XR environment, electronic device 700 optionally uses a controller communicatively coupled to electronic device 700 to detect selection of affordance 710. In addition, electronic device 700 uses gaze, for example, by detecting that user 704 views affordance 710 for a predetermined period of time and / or (optionally) simultaneously detecting one or more gestures to detect selection of affordance 710. For example, electronic device 700 optionally corresponds to a head-mounted display, so that electronic device 700 detects user 704 performing one or more gestures to activate affordance 710, such as an air gesture. The electronic device 700 optionally displays additional / other elements on the display 700a, such as additional user interfaces (e.g., an email application), representations of other users (e.g., via a video call, an avatar of another user in the XR environment), and / or representations of the physical environment (such as the physical environment of user 704).

[0137] exist Figure 7B At , in response to activation of the enable indication 710, the electronic device 700 displays an authorization interface 712. In some embodiments, the authorization interface 712 corresponds to a virtual interface object displayed within the XR environment. The authorization interface 712 includes a search function 714 and one or more credential options 716a and 716b. For example, the credential option 716a is associated with (e.g., used to select) information used to log in to the website "abc.com", such as the username "janeapples@mail.com". In some embodiments, the electronic device 700 detects a selection of a credential option, such as the credential option 716b (e.g., used to select the credential option). Figure 7B ). For example, credential option 716b is associated with information used to log into website "xyz.com", such as username "janeapples@mail.com". In some embodiments, the credential option is associated with a corresponding password, which may be displayed as part of authorization interface 712, or alternatively may not be displayed to protect privacy. In some embodiments, electronic device 700 receives information (e.g., text and / or audio) via search functionality 714, and in response, displays one or more retrieval result options corresponding to the received information for use with the auto-fill function.

[0138] In some embodiments, the electronic device 700 must meet various requirements (a set of one or more criteria) including visibility criteria and / or user authentication criteria to enable user authorization of security operations. For example, when a threshold amount of one or more interface objects (such as the login user interface 702 and / or the authorization interface 712) are visible from the viewpoint of the user 704 (e.g., the threshold amount may correspond to any portion of the interface object, a non-zero amount of the interface object, or the entire interface object), the visibility criteria are met. In addition, when the electronic device 700 receives a request to perform a security operation, the user authentication criteria are met. For example, the electronic device 700 detects that the user 704 has requested a request such as the credential option 716b (e.g., the credential option 716b) to perform a security operation. Figure 7B Once the credential option is selected, the user 704 may then provide input for authorizing the execution of a security operation (e.g., a double press of a hardware button), such as with respect to Fig.7D Based on determining that input for authorization to perform a security operation is received, the electronic device 700 enables corresponding credential options to be used to automatically fill in corresponding credential information into displayed fields, such as the username field 706 and the password field 708, if a set of one or more criteria is met. Figure 7B At , the electronic device 700 receives a selection of the credentials option 716b.

[0139] exist Figure 7C In response to receiving a selection of the credential option 716b, the electronic device 700 updates the authorization interface, such as Figure 7C As shown. Figure 7CAt , the electronic device 700 detects a user gaze direction 718 associated with (e.g., corresponding to) the gaze direction of the user 704. Typically, the user gaze direction 718 is not part of the displayed user interface of the electronic device 700, and is provided to help discuss the technology. During the interaction between the user 704 and the device 700, the electronic device 700 detects a change in the viewpoint of the user 704 based on a change in the user gaze direction 718 (e.g., from a first viewpoint to a second viewpoint different from the first viewpoint). In some embodiments, the user gaze direction is detected within the context of the XR environment (e.g., via a head-mounted display). The user gaze direction 718 optionally indicates that the gaze of the user 704 is not directed to the login user interface 702 or the authorization interface 712. Therefore, the electronic device 700 determines that the login user interface 702 and the authorization interface 712 are not fully visible from the viewpoint of the user 704. For example, the user gaze direction 718 may point to a portion of the displayed position of the display 700a that is not adjacent to the login user interface 702 and the authorization interface 712. In some embodiments, any portion of the login user interface 702 or the authorization interface 712 that is within a predefined distance (e.g., a predefined number of pixels and / or a predefined length) from the center of the user's gaze direction 718 is determined to be visible from the viewpoint of the user 704. For example, 10% of the authorization interface 712 may be determined to be within the predefined distance from the center of the user's gaze direction 718, and 5% of the login user interface 702 is determined to be within the predefined distance from the center of the user's gaze direction 718. In this example, the electronic device 700 determines that less than a threshold amount (e.g., a 75% threshold amount or a 90% threshold amount) of the login user interface 702 and / or the authorization interface 712 is visible from the user's viewpoint.

[0140] exist Figure 7C At, based on determining that less than a threshold amount of the login user interface 702 and / or the authorization interface 712 are visible from the user's viewpoint, the electronic device 700 disables and / or abandons enabling user authorization for the auto-fill function. In some embodiments, the electronic device 700 modifies the appearance of one or more interface objects to indicate that the user cannot request to perform a security operation (e.g., by graying out the authorization interface 712). For example, in response to detecting a selection of the credentials option 716b and when the login user interface 702 and the authorization interface 712 are not sufficiently visible from the user's 704 viewpoint (e.g., based at least on the user's gaze direction 718), the electronic device 700 does not automatically fill in the username field 706 and the password field 708.

[0141] exist Fig.7DAt, the electronic device 700 determines that the user 704 is authorized to perform a security operation, and therefore enables user authorization for the autofill function. In some examples, in the case of determining that the user 704 is authorized to perform a security operation, the user authorization for the security operation is enabled. For example, the electronic device 700 determines that the user 704 is authorized to perform a security operation based on the gaze criteria or other biometric criteria. When the user 704 gazes at the corresponding interface object (such as the login user interface 702 and / or the authorization interface 712), the gaze criteria are optionally met. The login user interface 702 and / or the authorization interface 712 are optionally displayed in the center part of the display 700a. In some embodiments, when the user does not gaze at the login user interface 702 and / or the authorization interface 712 (for example, the user's eyes are closed or the user is viewing the corner of the display 700a (away from the interface 702 and / or 712)), the electronic device 700 determines that the user 704 is not authorized to perform a security operation. In some embodiments, in the case of determining that the user has or is providing a specific movement of the biometric feature, the user authorization for the security operation is enabled. For example, the particular movement includes the user gazing at a particular portion of the login user interface 702 (e.g., gazing at the affordance 710) or the authorization interface 712 (e.g., a particular credential option), the user providing a particular facial rotation, and / or the user moving a finger along a particular path.

[0142] Generally speaking, the electronic device 700 operates in various modes. For example, the electronic device 700 optionally operates in a first mode (e.g., relative to Fig.7D In some embodiments, the device 700 optionally operates in a second mode, such as an accessibility mode and / or a mode in which input at a physical input mechanism is not required to authorize security operations (as opposed to a standard mode in which accessibility features are not enabled and / or a mode in which authorization of security operations is permitted using a default physical input mechanism (e.g., hardware button 722). Figures 7L to 7M described in more detail). Return to Fig.7D, based on determining that at least a threshold amount of the login user interface 702 and / or the authorization interface 712 is visible from the viewpoint of the user 704, the electronic device 700 enables user authorization for the auto-fill function. For example, the user gaze direction 718 can point to the authorization interface 712. Therefore, the object that the user is looking at is determined to be the authorization interface 712, resulting in a determination that 95% or 100% of the authorization interface 712 is visible from the viewpoint of the user 704. Therefore, the electronic device 700 determines that at least a threshold amount (e.g., a 75% threshold amount or a 90% threshold amount) of the login user interface 702 and / or the authorization interface 712 is visible from the user's viewpoint. In some embodiments, the electronic device 700 then enables user authorization for security operations, and indicates to the user via an indication 720 that user authorization for security operations is enabled, including an indicator with the text "Double-click to authorize". Specifically, the indication 720 notifies the user that double-press activation of a hardware button (such as hardware button 722) will authorize the auto-fill function. In some embodiments, user authorization for the autofill functionality remains enabled for a period of time (e.g., after one second, after three seconds, etc.) after determining that the login user interface 702 and / or the authorization interface 712 are visible from the user's viewpoint, and optionally becomes disabled after that period of time. In some embodiments, the device 700 visually indicates (e.g., by not graying out the authorization interface 712 and / or a portion of the authorization interface 712 (such as a button)) that the viewpoint includes the authorization interface 712, and therefore the corresponding authorization is enabled.

[0143] Once authorization of the auto-fill function is enabled, the user 704 can then proceed to authorize the security operation. Specifically, the electronic device 700 optionally modifies the appearance of one or more interface objects and / or displays one or more additional interface objects to indicate to the user that the user can request to perform a security operation. For example, where the electronic device 700 is implemented in an XR environment, the electronic device 700 displays instructions such as instructions to perform one or more air gestures (e.g., instructions to move one or more hands or fingers with a particular motion) and / or to perform one or more inputs on a controller compatible with the XR environment.

[0144] exist Fig.7DAt , the electronic device 700 receives user authorization for the auto-fill function via a double-click of the hardware button 722. In response to receiving the user authorization for the auto-fill function, a determination is optionally made as to whether one or more sets of execution criteria are satisfied. For example, visibility may be required to be satisfied before, at the time of, and / or after receiving a user authorization request to perform a security operation. In some embodiments, one or more execution criteria optionally also include a requirement that at least a threshold amount of the login user interface 702 and / or the authorization interface 712 is visible from the user 704's point of view once the user 704 requests to perform a security operation. In some embodiments, one or more sets of execution criteria include user authentication criteria that are satisfied when the user is authenticated (e.g., via a password and / or biometric authentication). As relative to Figure 7F As discussed in more detail, for example, the criteria optionally include a positive indication of a first level (e.g., full or high fidelity) iris feature verification, a positive indication of continuous (e.g., second level) iris feature verification since the user 704 began interacting with the device 700, and / or a positive indication of a correct password verification. Thus, based on determining that one or more sets of execution criteria are satisfied upon receiving a request to perform a security operation, the electronic device 700 initiates execution of a security operation.

[0145] exist Fig. 7E At , the electronic device 700 provides an indication to the user 704 that the user authorization of the auto-fill function was successful. Specifically, the electronic device 700 modifies (or otherwise replaces with an additional interface) the authorization interface 712 to include an affirmative indication that the user authorization of the auto-fill function was successful (e.g., a "check" mark next to the text "Done"). In addition, the electronic device 700 updates the login user interface 702 to indicate that the user authorization of the auto-fill function was successful by updating the username field 706 to include a username corresponding to the username of the selected credential option, and updating the password field 708 to include edited characters of the password corresponding to the selected credential option. In some embodiments, the electronic device 700 updates the password field 708 to include unedited and readable characters of the password corresponding to the selected credential option.

[0146] exist Figure 7F The user authentication process is described in detail. Fig.7DContinuing, in response to receiving a request to perform a security operation, a determination is made as to whether the user 704 meets the user authentication criteria in order to perform the security operation. In some embodiments, it is determined that the execution criteria set is not met. Generally speaking, at a first time (e.g., the initial time of device interaction), a first type of biometric authentication is performed so that the electronic device 700 uses one or more biometric sensors of the device 700 to authenticate the user 704 in a biometric manner. The first time may correspond to the initial time when the user first activates the electronic device 700 and / or the user wears the electronic device 700 on a part of the user's body. In an embodiment in which the device 700 corresponds to a head-mounted display, the first time may correspond to the time when the user 704 fixes the electronic device 700 to / wears it on the head of the user 704. The first type of biometric authentication may include a first level (e.g., full or high fidelity) iris feature verification. The first level iris feature verification includes a retinal scan to obtain one or more images and / or measurements of at least one eye of the user 704. In some embodiments, the iris features will be different for different users. The one or more images and / or measurements are then compared to one or more stored images and / or measurements corresponding to the user's registered retinal scans to determine a match and / or degree of similarity between the obtained images / measurements and the registered images / measurements. To the extent that the obtained images / measurements match the registered images with a sufficient degree of similarity (e.g., 95% or 99% similarity), the electronic device 700 determines that the user 704 is authenticated. In some embodiments, the first type of biometric authentication optionally includes (in addition to or in lieu of iris feature authentication), fingerprint authentication, facial recognition authentication, and / or voiceprint authentication.

[0147] The user authentication criteria for determining whether to perform a security operation are optionally based on sensor measurements taken during a specific time frame (and specifically, after the initial time that the user 704 begins to interact with the electronic device 700 and / or at multiple intermediate times after the user 704 wears the electronic device 700). The sensor measurements optionally correspond to measurements taken to detect whether the same user (e.g., user 704) uses the device 700 throughout the duration of the interaction. For example, in an embodiment in which the electronic device 700 corresponds to a head-mounted display, when the user 704 attaches the electronic device 700 to the head of the user 704 / wears it on the head of the user 704, the electronic device 700 optionally authenticates the user 704 via a first type of biometric authentication (e.g., full or high fidelity). Once successfully authenticated via the first type of biometric authentication, the electronic device 700 repeatedly obtains sensor measurements using a second type of biometric authentication. In some embodiments, the first type of biometric authentication corresponds to a high-fidelity biometric verification, so that the electronic device 700 analyzes characteristics associated with the entire eye of the user 704 or a portion of the eye of the user 704 (such as iris features). In some embodiments, the second type of biometric authentication corresponds to one or more sensor measurements that directly or indirectly confirm the continuity of the presence of the biometric feature because high-fidelity biometric verification is performed on the biometric feature. The second type of biometric authentication optionally analyzes the same (or similar) amount of biometric characteristics as the first type of biometric authentication, or optionally analyzes fewer biometric characteristics than the first type of biometric authentication. In some embodiments, the second type of biometric authentication can be referred to as continuity verification because, in some embodiments, the second type of biometric authentication is used to verify that the user authenticated using the first type of biometric authentication has been a user of the electronic device 700 since the first type of biometric authentication was performed (e.g., there was no interruption in the continuity of use of the biometric feature).

[0148] In some embodiments, when the electronic device 700 is operating in a first mode (e.g., a standard mode in which accessibility features are not enabled and / or a mode that permits the use of a default physical input mechanism to authorize security operations), both the first type of biometric authentication and the second type of biometric authentication are enabled. In some embodiments, when the electronic device 700 is operating in a second mode (e.g., an accessibility mode and / or a mode in which input at a physical input mechanism is not required to authorize security operations), the first type of biometric authentication is enabled and the second type of biometric authentication is disabled. Thus, in some embodiments, when operating in the second mode (e.g., relative to Figure 7L and Figure 7M), in response to receiving a request to perform a security operation, optionally requiring a first type of biometric authentication (e.g., full or high fidelity).

[0149] In some embodiments, at least one (e.g., the same or different) biometric sensor is used to perform both the first type of biometric authentication and the second type of biometric authentication (e.g., a retinal scanner, a depth camera, and / or a proximity sensor).

[0150] For example, the second type of biometric authentication optionally focuses on detecting features and characteristics of the pupil, eye glint, iris features (e.g., shape, size and / or color pattern) of the user 704. Specifically, the electronic device 700 captures information about the appearance of the user's eyes and records information about the detected pupil, eye glint and / or iris features. At a subsequent time (e.g., one second later, two seconds later), the electronic device 700 captures information about the appearance of the user's eyes again and stores information about the detected pupil, eye glint and / or iris features. A comparison is made between the information recorded at the first time and the information recorded at the second time to confirm whether the same user (e.g., user 704) is using the device at both times. For example, to the extent that the first detected pupil, eye glint and / or iris features match the second detected pupil, eye glint and / or iris features (e.g., completely and / or with sufficient confidence), the electronic device 700 determines that the same user is using the device at both times, and therefore the corresponding criteria are maintained. This process can be repeated until a specific time, such as when the user provides a request to perform a security operation. At this specific time, if (since the first type of biometric authentication) there is any determination that the same user does not use the device at any given time (e.g., the first detected information does not match the second detected information), it is determined that the corresponding criteria are not met, which results in abandoning the performance of the security operation (e.g., until further authentication is performed). For example, a sensor measurement indicating that no eyes, iris features, pupils, and / or eye flashes are detected will result in the corresponding criteria being determined to be unsatisfied. The lack of the presence of eye features can be based on the user's eyes being closed or the user's eyes being otherwise undetectable from the sensor (e.g., the head-mounted display is not properly assembled). For example, in an embodiment in which the electronic device 700 corresponds to a head-mounted display, the user may have removed the head-mounted display. In an embodiment in which the electronic device 700 corresponds to a tablet device or a smart phone device, the user 704 may hold the device 700 so that the eyes of the user 704 are not within the range of the sensor field of view (e.g., the electronic device 700 is placed upside down on the surface). In other words, the corresponding criteria optionally include an "eyes open" criterion, which is satisfied when at least one eye of the user 704 does not remain continuously closed for more than a threshold time period (e.g., a non-zero time period, such as one or two seconds).

[0151] In some embodiments, the first type of biometric authentication is based on a biometric feature different from the second type of biometric authentication. Specifically, the first type of biometric authentication optionally corresponds to full iris feature verification, so that the electronic device 700 analyzes the characteristics associated with the entire eye of the user 704 or the part of the eye of the user 704 (such as pupil, eye flash and / or iris feature). The second type of biometric authentication can correspond to partial facial recognition verification. Partial facial recognition optionally includes analyzing the characteristics associated with the part of the face of the user 704 (such as eyebrows, eyelids, skin around the eyes, forehead, cheeks and / or nose) around the eyes (and not including the eyes). For example, the electronic device 700 captures the appearance of the part of the face of the user 704 around the eyes. At a subsequent time (for example, one second or two seconds later), the electronic device 700 captures the appearance of the same part of the face of the user 704 around the eyes again. The electronic device 699 compares the information recorded at the first time with the information recorded at the second time to confirm whether the same user (for example, user 704) uses the device at both times. For example, to the extent that the first detected eyebrows, eyelids, skin around the eyes, forehead, cheeks and / or nose match the second detected eyebrows, eyelids, skin around the eyes, forehead, cheeks and / or nose (e.g., completely or with sufficient confidence), it is determined that the same user uses the device at both times, and therefore the corresponding criteria are maintained. This process can be repeated until a specific time, such as when the electronic device 700 receives a request to perform a security operation from the user. At this specific time, if there is any determination that the same user has not used the device since the first type of authentication (e.g., the first detected information does not match the second detected information), it is determined that the corresponding criteria are not met, which causes the electronic device 700 to abandon the execution of the security operation (e.g., until further authentication is performed). In other words, the corresponding criteria optionally include non-eye criteria that can be met even when the eyes of the user 704 are undetectable (e.g., undetectable for a threshold time period (such as 1 second, 5 seconds, 10 seconds, 15 seconds or 60 seconds)).

[0152] In some embodiments, using a first biometric feature for a first type of biometric authentication and using a different biometric feature for a second type of biometric authentication improves authentication. For example, when analyzing eye characteristics for a first type of biometric authentication and analyzing facial characteristics for a second type of biometric authentication, authentication is improved in situations where eye characteristics are not always available for analysis. Specifically, user 704 is initially authenticated based on eye characteristics, although facial characteristics (e.g., eyebrows, eyelids, skin around the eyes, forehead, cheeks, and / or nose) are used for a second type of biometric authentication. In this case, in the case where the eyes of user 704 are not detectable by one or more sensors of electronic device 700, electronic device 700 can still detect the user's facial characteristics and can therefore perform a second type of authentication to authorize the performance of a security operation.

[0153] return Figure 7F In response to receiving a request to perform a security operation, the electronic device 700 determines whether the user 704 meets the corresponding authentication criteria in order to perform the security operation. In some embodiments, the user 704 has been authenticated in a biometric manner at a first time, so that the request to perform the security operation is received at a second time (after the first time). In this case, to the extent that the user 704 does not meet the corresponding criteria between the first time and the second time, an authentication guidance user interface 724 is provided to the user to authenticate the user 704 in a biometric manner using the first type of biometric authentication. In other words, when the electronic device 700 cannot verify that the same user is using the device since the initial first type of biometric authentication (or can verify that the same user has not used the device since the initial first type of biometric authentication), the electronic device 700 attempts to use the first type of biometric authentication to verify the identity of the user again. Failure to meet the corresponding authentication criteria may be the result of multiple factors. For example, the eyes of the user 704 may be undetectable during the time period between the first time and the second time. In some embodiments, the initial authentication is based on different types of biometric authentication (e.g., fingerprint authentication) or can be based on non-biometric authentication (e.g., password input). For certain initial authentications such as fingerprint or password authentication, the corresponding authentication criteria are optionally automatically not satisfied, so that the user 704 will be required to provide a specific first type of biometric authentication (e.g., full or high-fidelity iris feature verification) in order to authorize the security operation. In some embodiments, the authentication guidance user interface 724 includes instructions for performing the first type of biometric authentication, such as instructions requesting the user to provide specific movements of the corresponding biometric feature. For example, the authentication guidance user interface 724 may include an initial prompt such as "Biometric Authentication Required", as well as an option for the user to "Continue" and another option for the user to "Cancel". Figure 7FAt , the electronic device 700 detects activation of the "Continue" option.

[0154] exist Figure 7G At, in response to detecting activation of the "Continue" option, the electronic device 700 initiates a first type of biometric authentication. When the first type of biometric authentication corresponds to iris feature verification, the electronic device 700 commands the user to look at various parts of the display when the biometric authentication begins (e.g., via the prompt "look here"). During the first type of biometric authentication, the electronic device 700 optionally analyzes the gaze 726 corresponding to the user 704 to obtain characteristics associated with the entire eye of the user 704 or a portion of the eye of the user 704 (such as iris features, pupils, and / or glints). In the case where the first type of biometric authentication corresponds to facial verification, the electronic device 700 commands the face of the user 704 to rotate at one or more specific angles. In some embodiments, in the case where the first type of biometric authentication corresponds to fingerprint authentication, the electronic device 700 commands the user to move their finger along a specific path and / or touch their finger in a specific way on the touch-sensitive contact portion of the device 700 or another device.

[0155] exist Figure 7H , depicts a password input prompt 728. In some embodiments, when the password input matches the registered password entered via the password input prompt 728, the user authentication criteria are met. For example, the electronic device 700 is optionally configured so that user authentication (or user authentication for performing security operations) will occur via a passcode or password (e.g., the user has disabled iris feature verification, facial verification, and / or other types of biometric authentication). Alternatively, based on determining that the user authentication criteria are not met based on a failed first type of biometric authentication (e.g., the device 700 cannot successfully complete the first type of biometric authentication), the electronic device 700 displays a password input prompt 728 to provide additional attempts to meet the user authentication criteria. In some embodiments, it can be determined that when the initial first type of biometric authentication is successful (e.g., the user successfully passes the biometric authentication when accessing the device for the first time), the second type of biometric authentication for detecting continuity may fail (e.g., the eyes of the user 704 are undetectable for a period of time after the initial time). In this case, the electronic device 700 displays a password input prompt 728 to the user to attempt to authenticate the user.

[0156] In some embodiments, when continuity verification fails, the electronic device 700 first attempts to authenticate the user by means other than password verification before attempting password verification. For example, the electronic device 700 attempts a first type of biometric authentication, such as full or high-fidelity iris feature verification (e.g., Figure 7G), or attempt a different type of full or high-fidelity biometric authentication, such as fingerprint authentication and / or facial recognition authentication. To the extent that full or high-fidelity biometric authentication fails, password verification is optionally used as a default option. In some embodiments, password entry prompt 728 includes a password entry portion and an indication of rejection of password entry. To the extent that the user chooses to reject password entry, user authorization for security operations is waived.

[0157] exist Fig.7I From Fig.7D Continuing, the change of the viewpoint of the user 704 is depicted. In general, the visible amount of the interface object may change based on the change of the viewpoint of the user 704. In some embodiments, at least a portion of the login user interface 702 and the authorization interface 712 is not visible to the user 704, for example, based on a portion of the login interface and a portion of the authorization interface not being fully displayed on the display 700a. In some embodiments in which the electronic device 700 is implemented in the XR environment, certain user movements optionally make the interface objects invisible or partially invisible. For example, when the wearer device 700 (e.g., a head-mounted display), the user turns their head in a particular direction. The login user interface 702 and the authorization interface 712 are optionally locked in the environment by the environment so that despite the user's head movement or other movement, the interface remains in the same general position within the environment. Therefore, based on the interface being positioned toward the side portion of the field of view of the user 704 (or behind the user in the XR environment), at least a portion of the interface optionally becomes invisible to the user 704. Therefore, based on the movement of the user 704, the visible amount of the login user interface 702 and the authorization interface 712 can be reduced. Therefore, it is determined that less than a threshold amount of login user interface 702 and / or authorization interface 712 is visible from the viewpoint of user 704. Based on this determination, electronic device 700 modifies the appearance of authorization interface 712 to, for example, indicate that user 704 cannot request to perform a security operation.

[0158] exist Figure 7JAt , an exemplary environment including a background area 730 is depicted on the display 700a. In some embodiments, the environment is implemented in the context of an XR environment, so that the electronic device 700 corresponds to a head-mounted display. The background area 730 optionally corresponds to a representation of the physical environment, virtual environment, or a combination of the physical environment and the virtual environment of the user 704. The user 704 can interact with various interface objects, virtual objects, or other objects depicted in the environment. For example, the electronic device 700 is displaying a message transceiver interface 732, through which the user 704 can receive and send messages. In addition, the electronic device 700 also displays a login user interface 702 and an authorization interface 712. When the electronic device 700 detects that the user 704 interacts with the interface, the interface can be completely visible to the user 704, so that there are no objects or other elements in the environment that block the interface. The electronic device 700 optionally detects that the user 704 is currently viewing the authorization interface 712, as depicted by the user's gaze direction 718. As described herein, user authorization for security operations is optionally enabled. Thus, the appearance of authorization interface 712 (eg, not grayed out) and indication 734 inform the user that the user may authorize the auto-fill functionality by, for example, performing the function indicated by indication 734 (eg, a double press of button 722 ).

[0159] exist Figure 7K 704. In some embodiments, the visible amount of an object depicted in the environment changes based on occlusion by other objects within the environment. This occlusion occurs based on movement of the (occluded or occluding) object itself or a change in the viewpoint of user 704. For example, relative to Figure 7J , the electronic device 700 has detected that the user 704 has turned to the left within the environment. Specifically, where the environment is implemented in the context of an XR environment, the electronic device 700 detects that the user 704 has turned their head to the left while wearing the electronic device 700 (e.g., a head-mounted display). Various objects within the environment can be viewpoint-locked or environment-locked. Specifically, the messaging interface 732 can be viewpoint-locked, such that the messaging interface 732 is displayed at the same position and / or location in the viewpoint of the user 704, even when the viewpoint of the user 704 changes. The login user interface 702 and the authorization interface 712 can alternatively be environment-locked, such that the login user interface 702 and the authorization interface 712 are displayed at a location in the user's viewpoint based on the location in the XR environment (e.g., located in front of a representation of a sofa). Thus, when the user 704 adjusts their viewpoint to the left (relative to the left), the login user interface 702 and the authorization interface 712 are displayed at a location in the user's viewpoint based on the location in the XR environment. Figure 7J), the messaging interface 732 appears to move over the login user interface 702 and the authorization interface 712. In other words, from the user's perspective, the login user interface 702 and the authorization interface 712 remain in the same general position relative to the background of the XR environment, and as a result of the user's viewpoint movement, the messaging interface 732 is overlaid on the login user interface 702 and the authorization interface 712. Based on the viewpoint change, the visible amount of the login user interface 702 and the authorization interface 712 is reduced given the overlay of the messaging interface 732. Although the electronic device 700 detects the user's gaze direction 718 as still being directed toward the authorization interface 712, it is determined that less than a threshold amount of the login user interface 702 and / or the authorization interface 712 are visible from the user's viewpoint, and therefore, the appearance of the authorization interface 712 is adjusted (e.g., grayed out) to reflect that user authorization for security operations is disabled.

[0160] exist Figure 7L At the electronic device 700, an interface for authorizing a security operation when the electronic device 700 operates in a second mode different from the first mode (such as with respect to FIG. 7A to FIG. 7K In some embodiments, the electronic device 700 operates in a second mode, such as an accessibility mode and / or a mode in which input at a physical input mechanism is not required to authorize a security operation. When in the second mode, the electronic device 700 displays a login user interface 736. The login user interface 736 corresponds to a login interface, including functions for facilitating interaction of users with accessibility requirements (e.g., limited fine motor, visual and / or auditory abilities). The electronic device 700 also optionally displays an authorization interface 738 to facilitate the process of security operations, such as authorizing information into certain display fields (e.g., an "autofill" function).

[0161] In some embodiments, the login user interface 736 and the authorization interface 738 correspond to the virtual interface objects displayed in the XR environment. The authorization interface 738 includes a search function 742 and one or more credential options 744a and 744b. In some embodiments, the credential option is associated with a username and / or password. In some embodiments, the electronic device 700 receives a search query for additional credential options via the search function 742, and provides any result options based on the search retrieval. When in the second mode, the user 704 can interact with the authorization interface 738 using an input or input combination (such as gaze input, controller input, and / or verbal input) compatible with the accessibility feature (e.g., select credential options 744a or 744b, or search for additional credential options via the search function 742). In some embodiments, the electronic device 700 detects the selection of the credential option (e.g., credential option 744a). Once the credential option is selected, the user 704 can use an input or input combination (such as gaze input, controller input, and / or verbal input) compatible with the accessibility feature to activate the affordance 740. Specifically, affordance 740 may be displayed with the text "Confirm with Assistive Touch" to indicate to the user that the device is operating in the second mode, and accordingly, no physical input mechanism is required to authorize the autofill operation. Figure 7L At this point, the electronic device 700 detects a selection of the enable indication 740.

[0162] exist Figure 7M At, in response to detecting a selection of the enable representation 740, the electronic device 700 displays an auxiliary input interface 742, including representations of multiple functions for facilitating various tasks. In some embodiments, the user 704 is required to look at the enable representation 740 and activate the enable representation 740 at the same time to trigger the selection of the enable representation 740. For example, the user 704 looks at the enable representation 704, and while looking at the enable representation 740, activates a special input (as further discussed in paragraphs

[0272] -

[0273] ). In addition, in response to the user selection of the enable representation 740, the electronic device 700 also modifies the appearance of the authorization interface 738 to indicate that the credential option has been selected by the user. In some embodiments, the positioning or location of the authorization interface 738 is adjusted (for example, in an XR environment, the authorization interface 738 is moved to the side of the user's field of view).

[0163] The multiple functions included in the auxiliary input interface 742 include various options. For example, the various options include an option to navigate to a home screen (e.g., a "home" option), an option to display device notifications (e.g., "notifications"), and / or an option to display a settings menu (e.g., "control menu"). The auxiliary input interface 742 includes a security operation authorization enable indication 744. Multiple functions can optionally be called using specific input types that can be preconfigured by the electronic device 700 or a specific user. For example, when in a first mode, the option to navigate to the home screen is executed in response to the electronic device 700 receiving a primary input type (e.g., a "swipe" input at a specific location), and when in a second mode, the option to navigate to the home screen is executed in response to the electronic device 700 receiving an accessibility-based input type (e.g., a user looking at the "home" icon in combination with a long press on the controller). In addition, when in the first mode, authorization of the security operation is performed in response to the electronic device 700 receiving a primary input type (such as a double press of a particular hardware button), and when in the second mode, authorization of the security operation is performed through an accessibility-based input type (such as activating a security operation authorization enable indication (for example, a user gazing at the security operation authorization enable indication 744 in combination with a long press on the controller)).

[0164] In some embodiments, in response to receiving input for authorizing a security operation, the electronic device 700 performs user authentication. For example, a first type of biometric authentication is performed such that the user 704 is biometrically authenticated using one or more biometric sensors of the device 700. The first type of biometric authentication optionally includes a first level (e.g., full or high fidelity) iris feature verification. Specifically, when operating in the second mode, the second type of biometric authentication (e.g., passive iris feature verification, such that the electronic device 700 repeatedly analyzes specific characteristics associated with the entire eye of the user 704 or a portion of the eye of the user 704 while the user 704 interacts with the device 700) is disabled. Therefore, when input is received to authorize a security operation, the first type of biometric authentication is required. Specifically, (return to reference Figure 7F ) The electronic device 700 provides the user with an authentication guidance user interface to use the first type of biometric authentication to biometrically authenticate the user 704. The authentication guidance user interface includes guidance for performing the first type of biometric authentication, such as guidance requesting the user to provide specific movements of the corresponding biometric feature. For example, the authentication guidance user interface includes an initial prompt such as "Biometric Authentication Required", as well as an option for the user to "Continue" and another option for the user to "Cancel".

[0165] Once the electronic device 700 detects the activation of the "Continue" option, the electronic device 700 initiates the first type of biometric authentication. In the case where the first type of biometric authentication corresponds to iris feature authentication, the electronic device 700 optionally commands the user to view various parts of the display at the beginning of the biometric authentication (e.g., via the prompt "Look here"). During the first type of biometric authentication, the electronic device 700 analyzes the gaze corresponding to the user 704 to obtain characteristics associated with the entire eye of the user 704 or a part of the eye of the user 704 (such as iris features, pupils and / or flashes). In the case where the first type of biometric authentication corresponds to facial authentication, the electronic device 700 commands the user 704 to rotate the face of the user 704 at one or more specific angles. In some embodiments, in the case where the first type of biometric authentication corresponds to fingerprint authentication, the electronic device 700 commands the user to move their fingers along a specific path and / or touch their fingers in a specific way on the touch-sensitive contact portion of the device 700 or another device. In some embodiments, the first type of biometric authentication is based on different types of biometric authentication (e.g., voice authentication) or based on non-biometric authentication (e.g., password entry).

[0166] exist Figure 7N At , an additional exemplary user interface for authorizing a security operation is displayed on the display 700a of the device 700. Specifically, Figure 7NSecurity operations associated with payment are depicted. In some embodiments, security operations associated with payment are implemented in the context of an XR environment so that device 700 corresponds to a head-mounted display. Electronic device 700 receives user input and, in response, navigates to an e-commerce website displayed via web browser 748 to purchase an item (e.g., a pair of shoes). In some embodiments, when electronic device 700 is operating in a first mode (e.g., a standard mode in which accessibility features are not enabled and / or a mode in which security operations are authorized using a default physical input mechanism), electronic device 700 detects selection of enable representation 750 to initiate a payment function. For example, display 700a is a touch-sensitive display so that user 704 presses a finger on enable representation 750. In some embodiments, when device 700 is implemented in an XR environment, electronic device 700 detects selection of enable representation 750 using a controller communicatively coupled to electronic device 700. In addition, electronic device 700 uses gaze, for example, by detecting that user 704 views affordance 750 for a predetermined period of time and / or receives one or more gestures to detect selection of affordance 750. In some embodiments, electronic device 700 corresponds to a head-mounted display, such that electronic device 700 detects that user 704 performs one or more gestures to activate affordance 750, such as an air gesture. Once electronic device 700 detects activation of affordance 750, electronic device 700 displays payment details interface 752. Payment details interface 752 includes details related to information for completing an order for the items depicted in associated web browser 748. For example, payment details interface 752 includes credit card billing information, shipping information, and / or pricing information.

[0167] In some embodiments, the electronic device 700 enables user authorization for payment operations when it is determined that the user 704 is authorized to perform payment operations. For example, it is determined that the user is authorized to perform security operations based on the gaze criteria relative to the user's gaze direction 754. When the user 704 gazes at interface objects such as a web browser 748 and / or a payment details interface 752, the gaze criteria are met. For example, the electronic device 700 optionally displays the web browser 748 and / or the payment details interface 752 in the center portion of the display 700a. In some embodiments, when the user does not gaze at the web browser 748 and / or the payment details interface 752 (for example, the user's eyes are closed or the user is looking at the corner of the display 700a (away from the interface 748 and 752)), the electronic device 700 determines that the user is not authorized to perform security operations. In some embodiments, when it is determined that the user 704 has or is providing a specific movement of a biometric feature, user authorization for security operations is enabled. For example, the particular movement includes the user gazing at a particular portion of the web browser 748 (e.g., gazing at the affordance 750) or the payment detail interface 752 (e.g., a displayed price), the user providing a particular facial rotation, or the user moving a finger along a particular path.

[0168] Once authorization for the payment function is enabled, the user proceeds to authorize the payment function. Specifically, the electronic device 700 modifies the appearance of one or more interface objects and / or displays one or more additional interface objects to indicate to the user that the user can request to perform a payment operation. Instruction 756 includes the instruction "Double-click to authorize", which may be displayed near hardware button 758. In some embodiments, where the electronic device 700 is implemented in an XR environment, the electronic device 700 displays instructions, such as instructions for performing one or more air gestures (e.g., instructions for moving one or more hands or fingers with a particular motion) and / or instructions for performing one or more inputs on an XR-compatible controller.

[0169] In some embodiments, in response to receiving a request to perform a security operation, the electronic device 700 determines whether the user 704 has satisfied user authentication criteria to perform the payment operation, such as with respect to FIG. 7F to FIG. 7H To the extent that the user does not satisfy the user authentication criteria, user authorization for the payment operation is disabled. Therefore, a user authentication process is performed, as described in relation to FIG. 7F to FIG. 7H To the extent that the user does not satisfy the user authentication criteria, the electronic device 700 initiates the payment transaction and provides feedback to the user regarding the payment transaction.

[0170] Refer to the following about FIG. 7A to FIG. 7N The method 800 described provides for FIG. 7A to FIG. 7N Additional description of .

[0171] Figure 8 800 is a flow chart of an exemplary method 800 of facilitating user consent for secure operations according to some embodiments. In some embodiments, the method 800 includes a display generation component (e.g., Figure 1 , Figure 3 and Figure 4 The display generation components 120 in the computer system (e.g., display controller, touch-sensitive display system, display (e.g., integrated and / or connected), 3D display, transparent display, projector and / or head-up display)) (e.g., head-up display, display, touch screen, projector, etc.) and one or more input devices (e.g., Figure 1 In some embodiments, method 800 is performed by storing in a non-transitory (or transient) computer-readable storage medium and executed by one or more processors of a computer system (such as one or more processors 202 of computer system 101) (e.g., Figure 1 Some operations in method 800 are optionally combined, and / or the order of some operations is optionally changed.

[0172] As described below, method 800 provides an intuitive way to facilitate user consent for security operations. The method reduces the cognitive burden on the user when performing security operations, thereby creating a more effective human-computer interface. For battery-powered computing devices, faster and more efficient facilitation of user consent for security operations saves power and increases the time interval between battery charges.

[0173] When a three-dimensional environment (e.g., 730) is visible (802) via a display generating component (e.g., 120 and / or 700a), wherein the three-dimensional environment includes a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) that includes information about a security operation (e.g., 706, 708, 710, 716a, 716b, 744a, and / or 744b), a change in a current viewpoint of a user (e.g., user 704) is detected (e.g., from a first viewpoint to a second viewpoint different from the first viewpoint) via one or more input devices (e.g., 125 and / or 150) (e.g., receiving a request to automatically populate an input field (e.g., with a password and / or email information) and / or detecting activation of a payment affordance).

[0174] In response to detecting (804) a change in a viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704), based on determining that at least a threshold amount of virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) are visible from the user's viewpoint (e.g., 718, 746, and / or 754) and that the user (e.g., 704) is authorized to perform the security operation, user authorization for the security operation using the virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) is enabled (e.g., an auto-fill authorization option is enabled to automatically populate fields of a second user interface (e.g., a form user interface) and / or an activatable purchase authorization option is enabled (e.g., a purchase authorization option is enabled to automatically populate fields of a second user interface (e.g., a form user interface) In some embodiments, the computer system (e.g., 700) visually indicates (e.g., by not graying out the second user interface (e.g., 702, 712, 736, 738, 748, and / or 752) or a portion of the second user interface (e.g., 702, 712, 736, 738, 748, and / or 752), such as the button (e.g., 710)) that the viewpoint (e.g., 718, 746, and / or 754) includes the user interface (e.g., 702, 712, 736, 738, 748, and / or 752), and therefore the corresponding authorization option is enabled. In some embodiments, the activatable purchase authorization option includes a single press, a long press, a single press followed by a long press, a press followed by a rotation, a rotation followed by a press, and / or multiple consecutive presses (e.g., a double press, a triple press).

[0175] Based on determining (806) that less than a threshold amount of the virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) is visible from a viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704) (e.g., gaze (e.g., 718, 746, and / or 754) is not directed toward the user interface (e.g., 702, 712, 736, 738, 748, and / or 752) and / or the user gaze (e.g., 718, 746, and / or 754) is visible from a viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704) 754) is not a user interface (e.g., 702, 712, 736, 738, 748 and / or 752)), waiving user authorization for security operations using virtual user interface objects (e.g., 702, 712, 736, 738, 748 and / or 752) (e.g., disabling an auto-fill authorization option for automatically filling in fields of a second user interface (e.g., a form user interface) and / or disabling an activatable purchase authorization option (e.g., a double-press process of a physical button)). In some embodiments, based on determining that a viewpoint (e.g., 718, 746, and / or 754) does not include a user interface (e.g., 702, 712, 736, 738, 748, and / or 752), the computer system (e.g., 700) visually indicates (e.g., by graying out a second user interface (e.g., 702, 712, 736, 738, 748, and / or 752) or a portion of the second user interface (e.g., 702, 712, 736, 738, 748, and / or 752), such as a button (e.g., 710)) that the viewpoint (e.g., 718, 746, and / or 754) does not include a user interface (e.g., 702, 712, 736, 738, 748, and / or 752) and, therefore, the corresponding authorization option is not enabled). Enabling user authorization for security operations when the corresponding user interface is visible provides improved security / privacy by confirming that the user has an opportunity to review information associated with the security operation before the user authorizes the security operation to proceed.

[0176] In some embodiments, input is received from a user (e.g., 704) to authorize performance of a security operation (e.g., a double-click of a hardware button (e.g., 722 and / or 758) and / or activation of a particular affordance). In some embodiments, input for authorization includes a single press, a long press, a single press followed by a long press, a press followed by a rotation, a rotation followed by a press, or multiple consecutive presses (e.g., a double press, a triple press). In some embodiments, in response to receiving input for authorizing performance of a security operation, execution of the security operation is initiated (e.g., populating fields of a second user interface (e.g., 702, 712, 736, 738, 748, and / or 752) (e.g., a form user interface) based on determining that one or more sets of execution criteria are satisfied (e.g., gaze (e.g., 718, 746, and / or 754) is directed at a user interface (e.g., 702, 712, 736, 738, 748, and / or 752) and / or the object at which the user is gazed (e.g., 718, 746, and / or 754) is a user interface (e.g., 702, 712, 736, 738, 748, and / or 752)). and / or initiating a payment transaction), wherein one or more sets of execution criteria include visibility criteria that are satisfied when at least a threshold amount of a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) is visible from a viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704) (e.g., the threshold amount corresponds to any portion of an interface object (e.g., 702, 712, 736, 738, 748, and / or 752), a non-zero amount of an interface object (e.g., 702, 712, 736, 738, 748, and / or 752), or the entire interface object (e.g., 702, 712, 736, 738, 748, and / or 752)). In some embodiments, execution of a security operation is not initiated (e.g., populating fields (e.g., 706 and / or 708) of a second user interface (e.g., 702, 712, 736, 738, 748 and / or 752) (e.g., a form user interface) is abandoned and / or initiating a payment transaction is abandoned based on determining that one or more sets of execution criteria are not satisfied (e.g., the gaze (e.g., 718, 746 and / or 754) is not directed at a user interface (e.g., 702, 712, 736, 738, 748 and / or 752) and / or the object of the user's gaze (e.g., 718, 746 and / or 754) is not a user interface (e.g., 702, 712, 736, 738, 748 and / or 752)). Initiating execution of the security operation when a threshold amount of the corresponding user interface is visible provides improved security / privacy by confirming that the user has an opportunity to review information associated with the security operation before the user authorizes the security operation to proceed.

[0177] In some embodiments, one or more execution criteria sets include user authentication criteria that are satisfied when a user (e.g., 704) is authenticated (e.g., the criteria include a positive indication of continuous iris feature verification since the user (e.g., 704) utilized the device (e.g., 700), a positive indication of first level (e.g., full or high fidelity) iris feature verification, and / or a correct password authentication). In addition to user authorization for secure operations, requiring user authentication provides improved security / privacy by adding an additional layer of verification specific to the user requesting authorization.

[0178] In some embodiments, biometric information from a user (e.g., 704) is detected (e.g., performing a first level (e.g., full or high fidelity) iris feature verification and / or performing a second level (e.g., for continuous tracking of eye information (e.g., detected flash information and / or detected pupil information)) iris feature verification). In some embodiments, detecting biometric information includes receiving input (e.g., an image of the user's face) from the user (e.g., 704) in response to a prompt (e.g., 724) to look at a particular portion (e.g., 726) of a screen (e.g., 700a). In some embodiments, detecting biometric information includes passively detecting biometric information while the user (e.g., 704) is using a device (e.g., 700) (e.g., wearing a head-mounted display). In some embodiments, detecting biometric information includes detecting biometric information when a hardware button (e.g., 722 and / or 758) is activated (e.g., during a single press, a long press, a single press followed by a long press, a press followed by a rotation, a rotation followed by a press, multiple consecutive presses (e.g., a double press, a triple press)) or in response to a hardware button (e.g., 722 and / or 758) being activated. In some examples, the biometric information is compared to registered biometric information (e.g., comparing an obtained iris scan to a stored iris print and / or comparing current eye information to eye information from a previous frame), where a determination of whether user authentication criteria are met is based on a comparison of the biometric information to the registered biometric information (e.g., if the comparison meets a sufficient similarity threshold (e.g., 95% similarity), the user authentication criteria are met). In some embodiments, a first level (e.g., full or high fidelity) iris feature verification is performed, and at a later time (e.g., one hour later), a second level (e.g., for continuous tracking of eye information) iris feature verification is performed to link the first level iris feature verification to execution criteria for initiating execution of the security operation. Requiring biometric authentication in addition to user authorization for security operations provides improved security / privacy by adding a layer of biometric verification specific to the user requesting authorization.

[0179] In some embodiments, determining that user authentication criteria are satisfied occurs in response to receiving input for authorizing performance of a security operation (e.g., verifying whether user authentication criteria are satisfied in response to activation of a hardware button (e.g., 722 and / or 758) (e.g., single press, long press, single press followed by long press, press followed by rotation, rotation followed by press, multiple consecutive presses (e.g., double press, triple press)). Requiring user authentication when a user requests performance of a security operation provides improved security / privacy by verifying the identity of the user requesting the operation.

[0180] In some embodiments, determining whether user authentication criteria are met includes obtaining stored authentication information, wherein the stored authentication information indicates one or more previously performed biometric authentications (e.g., obtaining a continuity result indicating a positive result (e.g., iris feature continuity and / or facial continuity has been maintained) or a negative result (e.g., iris feature continuity and / or facial continuity has not been maintained)). In addition to user authorization for secure operations, utilizing the stored authentication information provides improved security / privacy by creating an efficient and uninterrupted user experience for biometric authentication, encouraging users to use biometric authentication, and thereby providing a more secure experience.

[0181] In some embodiments, determining whether user authentication criteria are met includes: performing a first type of biometric authentication (e.g., performing a first level (e.g., full or high fidelity) iris feature verification), after performing the first type of biometric authentication (e.g., after performing a successful first level (e.g., full or high fidelity) iris feature verification), repeatedly performing (e.g., performing every 2 frames (e.g., one frame includes a static image or a collection of images obtained from a sensor of the device (e.g., a biometric sensor)), performing every 3 frames, performing every 4 frames, performing every 5 frames, performing every 6 frames, performing every 7 frames, performing every 8 frames, performing every 9 frames, or performing every 5 10 frames) perform a second type of biometric authentication (e.g., perform a second level (e.g., for continuous tracking of eye information) iris feature verification), wherein the second type of biometric authentication includes: receiving an input including first corresponding biometric information from a user (e.g., 704) (e.g., obtaining eye information from a current frame), and comparing the received input with a previously received input including second corresponding biometric information (e.g., comparing eye information from the current frame with eye information from a previous frame). Taking multiple sensor measurements at multiple intermediate times between the first time and the second time provides improved security / privacy by verifying that the same user has been using the device since the initial authentication.

[0182] In some embodiments, performing a first type of biometric authentication includes detecting the presence of a first biometric feature type (e.g., a first level (e.g., full or high fidelity) authentication is based on eye features or a first level (e.g., full or high fidelity) authentication is based on facial features), and performing a second type of biometric authentication includes detecting the presence of a second biometric feature type (e.g., a second level of authentication is based on eye features (e.g., for continuous tracking of eye information) or a second level of authentication is based on facial features (e.g., for continuous tracking of eyebrows, eyelids, forehead, and / or nose)), wherein the first biometric feature type and the second biometric feature type correspond to the same biometric feature type (e.g., the first level of authentication and / or the second level of authentication is based on eye features or the first level of authentication and / or the second level of authentication is based on facial features). In addition to user authorization for security operations, continuously verifying user presence based on the same biometric feature as initial authentication provides improved security / privacy by creating an efficient and uninterrupted user experience for biometric authentication, encouraging users to use biometric authentication, and thereby providing a more secure experience.

[0183] In some embodiments, when a user (e.g., 704) is authenticated based on eye biometrics, user authentication criteria are met (e.g., a first pattern is detected based on multiple features corresponding to the eyes of the user (e.g., 704) (e.g., a pattern formed based on filaments, pits, grooves, crowns and / or rings)). In some embodiments, the detected first pattern is compared to a reference pattern, where the reference pattern is based on multiple features corresponding to the eyes of the user (e.g., a stored pattern based on full or high-fidelity iris feature verification or a stored pattern based on partial iris feature verification for continuity). In addition to user authorization for secure operations, requiring authentication based on eye biometrics provides improved security / privacy by adding a biometric verification layer specific to the user requesting authorization.

[0184] In some embodiments, user authentication criteria are met when a password input matches a registered password (e.g., a multiple digit input (e.g., 0-9) is received and compared to a previously registered password (e.g., a password including the digits 0-9). Requiring password authentication provides improved security / privacy by providing an additional method of verifying a user's identity in addition to user authorization for secure operations.

[0185] In some embodiments, based on a determination that user authentication criteria are not met (e.g., the device cannot obtain a sufficient iris feature scan, the first level iris feature verification result indicates that the iris feature scan does not match the reference scan, or the user refuses to provide iris feature verification), a prompt (e.g., 728) is provided (e.g., displayed via a display generation component (e.g., 120 and / or 700a)) to enable authentication using a password (e.g., a button activated by the user to invoke a password entry interface). In some embodiments, the prompt (e.g., 704) includes a password entry portion and an enabling indication of rejection of password entry. Requiring password authentication after a biometric authentication failure provides improved security / privacy by providing a backup option for verifying the user's identity.

[0186] In some embodiments, user authorization of a security operation (e.g., initiating a payment operation and / or initiating an autofill operation) using a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) includes user activation of a hardware user interface element (e.g., 722 and / or 758) (e.g., a single press, a long press, a single press followed by a long press, a press followed by a rotation of a hardware user interface element, a rotation followed by a press, a continuous double press, a triple press, or more presses). Utilizing hardware elements for authorization provides improved security / privacy by reducing the likelihood of erroneous authorization and / or preventing unauthorized input from malware.

[0187] In some embodiments, the secure operation is a payment (e.g., providing payment information to a third-party service in order to purchase an item, such as providing credit card information to an e-commerce website to purchase shoes). Enabling user authorization of payment operations when the corresponding user interface is visible provides improved security / privacy by confirming that the user has an opportunity to review information associated with the secure operation before the user authorizes the secure operation to proceed.

[0188] In some embodiments, the security operation includes automatically filling in user credentials (e.g., providing login information (e.g., 706 and / or 708) (e.g., a username and / or password) to access secure information (e.g., a banking website, a stock trading application, and / or user profile information)). Enabling user authorization for the autofill operation when the corresponding user interface is visible provides improved security / privacy by confirming that the user has an opportunity to review information associated with the security operation before the user authorizes the security operation to proceed.

[0189] In some embodiments, in response to detecting a change in the viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704), changing the amount of virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) visible to the user (e.g., 704) (e.g., the viewpoint moves (e.g., looking left or right) causing the virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) to be partially (e.g., as if Fig.7I and Figure 7K ) or completely removed from visibility, or the viewpoint moves causing the virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) to become visible after being completely removed from visibility). Enabling user authorization for security operations based on changes in user viewpoint provides improved security / privacy by verifying that the user is still viewing details about the security operation.

[0190] In some embodiments, the amount of a visible virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) changes based on occlusion by a physical (e.g., real) object. In some embodiments, the visible amount of a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) is detected from a viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704), where the viewpoint (e.g., 718, 746, and / or 754) of the user (e.g., 704) includes physical objects represented in a three-dimensional environment. In some embodiments, a user (e.g., 704) views a physical object (e.g., a computer monitor) through an added display, or a user (e.g., 704) views a representation of a physical object rendered on an opaque display, wherein the physical object is closer to the user (e.g., 704) than the representation of the virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752). In some embodiments, a decrease in the visible amount is detected in response to detecting a change in a viewpoint (e.g., 718, 746, and / or 754) of the user (e.g., 704), wherein the detected change in the viewpoint (e.g., 718, 746, and / or 754) of the user (e.g., 704) includes detecting that the physical object appears in front of the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752) relative to the viewpoint (e.g., 718, 746, and / or 754) of the user (e.g., 704). In some embodiments, the reduction in visible amount is based on a detected physical object appearing in front of the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752) (e.g., displaying fewer virtual interface objects than were displayed prior to the viewpoint change (e.g., 702, 712, 736, 738, 748, and / or 752)). In some embodiments, the physical object may move in front of the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752) (e.g., a physical balloon floats in front of the user's (e.g., 704) central field of view). In some embodiments, the user's (e.g., 704) changed viewpoint (e.g., 718, 746, and / or 754) now includes a physical object in close proximity to the user (e.g., 704) that obscures the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752) (e.g., the user (e.g., 704) turns to a tree that is now 1 foot in front of the user (e.g., 704)).When a physical object is described as occluding a virtual object (e.g., 702, 712, 736, 738, 748, and / or 752), this optionally refers to the device (e.g., 700) ceasing to display or obscure at least a portion of a virtual object (e.g., 702, 712, 736, 738, 748, and / or 752) that is in the same line of sight as the physical object but at a simulated distance that is farther from a viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704) than the physical object, thereby effectively virtually occluding the virtual object (e.g., 702, 712, 736, 738, 748, and / or 752) (or a portion of the object) that would otherwise overlap with the physical object. Enabling user authorization of security operations based on occlusion of security operation details by a physical object provides improved security / privacy by verifying that the user is still viewing details about the security operation.

[0191] In some embodiments, the amount of visible virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) changes based on the occlusion by the virtual object (e.g., 732). In some embodiments, in response to detecting a change in the viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704), a decrease in the visible amount is detected (e.g., a portion of the interface is no longer visible or the entire interface is no longer visible). In some embodiments, the detected change in the viewpoint (e.g., 718, 746, and / or 754) of the user (e.g., 704) includes detecting a virtual object (e.g., 732) that appears in front of the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752) relative to the viewpoint of the user (e.g., 704) (e.g., as Figure 7J and Figure 7K In some embodiments, the reduction in the visible amount is based on a detected virtual object (e.g., 732) appearing in front of the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752). Enabling user authorization for security operations based on occlusion of security operation details by virtual objects provides improved security / privacy by verifying that the user is still viewing details about the security operation.

[0192] In some embodiments, the visible amount of a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) changes (e.g., as shown in FIG. 1 ) based on the virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) moving out of the user's field of view (e.g., 704). Fig.7I). In some embodiments, in response to detecting a change in the viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704), the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752) is no longer detected within the current viewpoint (e.g., 718, 746, and / or 754) of the user (e.g., 704) (e.g., the user (e.g., 704) is further away from the interface (e.g., 702, 712, 736, 738, 748, and / or 752) viewing such that the interface is now "behind" the user in the environment). Enabling user authorization for security operations outside of the user's field of view based on security operation details provides improved security / privacy by verifying that the user is still viewing details about the security operation.

[0193] In some embodiments, the visible amount of a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) changes based on the virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) moving more than a threshold distance from the center of a user's (e.g., 704) field of view (e.g., 718, 746, and / or 754) (e.g., the user (e.g., 704) views away from the interface (e.g., 702, 712, 736, 738, 748, and / or 752) so that only a portion of the interface is visible (e.g., visible toward the side of the user's (e.g., 704) field of view) or the interface (e.g., 702, 712, 736, 738, 748, and / or 752) is moved by the user (e.g., 704) or by another user). Enabling user authorization for a security operation based on the security operation details being too far from the center of the user's field of view provides improved security / privacy by verifying that the user is still viewing details about the security operation.

[0194] In some embodiments, the visible amount of the virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) changes based on the occlusion by the physical object. In some embodiments, the movement of the physical object is detected (e.g., a balloon floating in front of the user (e.g., 704)), wherein the detected movement includes the movement of the physical object in front of the virtual user interface (e.g., 702, 712, 736, 738, 748, and / or 752) relative to the user's viewpoint (e.g., 718, 746, and / or 754) (e.g., in adding a display (e.g., a display including transparent portions, wherein the user (e.g., 704) views the actual surrounding physical environment (e.g., 730 through the display). )), the balloon moves such that a portion of a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) is no longer displayed, or on an opaque display (e.g., a display coupled to a sensor and / or camera where a user (e.g., 704) views a representation of the surrounding physical environment on the display (e.g., 730)), the balloon moves such that the representation of the balloon is displayed as obscuring a portion of the virtual interface object (e.g., 702, 712, 736, 738, 748, and / or 752). Enabling user authorization for security operations based on security operation details being obscured by a physical object provides improved security / privacy by verifying that the user is still viewing details about the security operation.

[0195] In some embodiments, determining that a user (e.g., 704) is authorized to perform a security operation includes determining whether a gaze criterion is satisfied when the user (e.g., 704) is looking at a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752). In some embodiments, based on determining that the user (e.g., 704) is looking at a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) (e.g., the user (e.g., 704) is looking at selected login information (e.g., 716a, 716b, 744a, and / or 744b) or the user (e.g., 704) is looking at payment information), while receiving a request to perform a security operation, a security operation is initiated. Requiring the user to review details about the security operation when requesting authorization provides improved security / privacy by ensuring that the user has an opportunity to read details about the operation.

[0196] In some embodiments, determining that the user (e.g., 704) is authorized to perform the security operation includes determining whether eye criteria are met when the eyes of the user (e.g., 704) are open. In some embodiments, the security operation is initiated based on determining that the eyes of the user (e.g., 704) are open or at least one eye of the user (e.g., 704) is open while receiving a request to perform the security operation. Requiring the user's eyes to be open in order to provide authorization for the security operation provides improved security / privacy by ensuring that the user has an opportunity to read details about the operation.

[0197] In some embodiments, based on determining that at least a threshold amount of virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) are visible from a viewpoint of a user (e.g., 704) (e.g., a gaze (e.g., 718, 746, and / or 754) is directed toward the user interface (e.g., 702, 712, 736, 738, 748, and / or 752) and / or the object at which the user is gazed (e.g., 718, 746, and / or 754) is the user interface (e.g., 702, 712, 736, 738, 748, and / or 752)), the appearance of the virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) is modified to indicate to the user (e.g., 704) (e.g., via indicators 720, 734, and / or 756) that the user (e.g., 704) can request that a security operation (e.g., such as Fig.7D as shown) (e.g., the user interface (e.g., 702, 712, 736, 738, 748, and / or 752) does not appear grayed out, the button is marked as active, or the user interface (e.g., 702, 712, 736, 738, 748, and / or 752) provides text (e.g., “Continue Request”) indicating that the user (e.g., 704) can request to perform a security operation). In some embodiments, based on determining that less than a threshold amount of virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) are visible from a viewpoint (e.g., 718, 746, and / or 754) of a user (e.g., 704) (e.g., the gaze (e.g., 718, 746, and / or 754) is not directed toward the user interface (e.g., 702, 712, 736, 738, 748, and / or 752) and / or the object at which the user is gazed (e.g., 718, 746, and / or 754) is the user interface (e.g., 702, 712, 736, 738, 748, and / or 752)), the appearance of the virtual user interface objects (e.g., 702, 712, 736, 738, 748, and / or 752) is modified to indicate to the user (e.g., 704) that the user (e.g., 704) cannot request to perform a security operation (e.g., such as Figure 7C704) cannot request to perform the security operation). Providing a visual indication that user authorization for a security operation can be provided provides improved visual feedback by notifying the user that the security operation can be initiated by the user.

[0198] In some embodiments, a three-dimensional environment (e.g., 730) includes a virtual object associated with a security operation (e.g., a virtual representation of a shoe), including: attaching a virtual user interface object to the virtual object associated with the security operation (e.g., attaching a virtual representation of a worksheet to the shoe, the worksheet including payment information about the shoe), wherein movement of the virtual object causes the attached virtual user interface object to move with the virtual object (e.g., movement of the shoe (e.g., setting the shoe on a table) causes the worksheet to remain attached to the shoe and move with the shoe (e.g., the worksheet remains attached to the shoe when the shoe is resting on a table)). Attaching the corresponding object to an interface with details about the security operation provides improved visual feedback by notifying the user that the security operation is associated with the corresponding object.

[0199] In some embodiments, aspects / operations of methods 800, 900, and 1000 may be interchanged, substituted, and / or added between these methods. For example, as part of method 900, the determination of whether to enable user authorization for security operations in method 800 is optionally used to determine whether to enable user authorization. For the sake of brevity, these details are not repeated here.

[0200] Refer to the following about FIG. 7A to FIG. 7N The method 900 described provides for FIG. 7A to FIG. 7N Additional description of .

[0201] Fig. 9 is a flow chart of an exemplary method 900 for authentication continuity of secure operations according to some embodiments. In some embodiments, the method 900 includes a display generation component (e.g., Figure 1 , Figure 3 and Figure 4 A computer system (e.g., a display generation component 120 in the embodiment (e.g., a display controller, a touch-sensitive display system, a display (e.g., integrated and / or connected), a 3D display, a transparent display, a projector, and / or a head-up display)), one or more input devices, and a biometric sensor (e.g., a facial authentication device, a fingerprint authentication device, and / or an eye tracking device)) Figure 1In some embodiments, method 900 is performed by storing in a non-transitory (or transient) computer-readable storage medium and executed by one or more processors of a computer system (such as one or more processors 202 of computer system 101) (e.g., Figure 1 Some operations in method 900 are optionally combined, and / or the order of some operations is optionally changed.

[0202] As described below, method 900 provides an intuitive way to facilitate authentication continuity for security operations. The method reduces the cognitive burden on the user when performing security operations, thereby creating a more efficient human-machine interface. For battery-powered computing devices, facilitating authentication continuity for security operations more quickly and more efficiently saves power and increases the time interval between battery charges.

[0203] At a first time (902), a user of a device (e.g., 704) is biometrically authenticated using a biometric sensor to perform a first type of biometric authentication (e.g., perform a first level (e.g., full or high fidelity) iris feature authentication, and / or perform a first level (e.g., full or high fidelity) fingerprint authentication). At a second time (904) after the first time, a request to perform a security operation is received (e.g., receiving a request to automatically fill an input field (e.g., 706 and / or 708) (e.g., automatically fill with a password and / or email information) and / or detect activation of a payment enablement indication).

[0204] In some embodiments, in response to receiving a request to perform a security operation (906): based on determining that a user of the device (e.g., 704) satisfies corresponding criteria (e.g., continuity criteria) (908) between a first time and a second time, performing a security operation (e.g., using autofill to populate fields (e.g., 706 and / or 708) of a user interface (e.g., 702, 712, 736, 738, 748, and / or 752) with predefined values ​​and / or initiating a payment transaction) after receiving the request to perform the security operation without performing a first type of biometric authentication (e.g., not performing a first level (e.g., full or high fidelity) iris feature verification between the security operation request and the execution of the security operation, and / or not performing a first level (e.g., full or high fidelity) fingerprint verification between the security operation request and the execution of the security operation). In some embodiments, the corresponding criterion is based on sensor measurements taken at multiple intermediate times between the first time and the second time, including sensor measurements taken at the first intermediate time and sensor measurements taken at the second intermediate time, which sensor measurements detect that the same user is using the device (e.g., 700) between the first time and the second time (e.g., the eye tracking continuity policy has not had an erroneous result since the user (e.g., 704) previously performed a first level (e.g., full or high fidelity) iris feature verification, and / or the fingerprint continuity policy has not had an erroneous result since the user (e.g., 704) previously performed a first level (e.g., full or high fidelity) fingerprint verification).

[0205] In some embodiments, based on determining that a user (e.g., 704) of a device (e.g., 700) does not satisfy corresponding criteria between a first time and a second time (910) (e.g., an eye tracking continuity policy evaluates to false (e.g., the eyes are undetectable for a period of time, the user (e.g., 704) was previously authenticated only by a password, and / or the user (e.g., 704) was previously authenticated only by a fingerprint), and / or a fingerprint tracking continuity policy evaluates to false), performing a security operation is abandoned. Ensuring that biometric continuity conditions are satisfied when a user requests to perform a security operation provides improved security / privacy by verifying that the same user has been using the device since initial authentication.

[0206] In some embodiments, in response to receiving a request to perform a security operation: based on determining that a user of the device (e.g., 704) does not meet corresponding criteria between a first time and a second time (e.g., an eye tracking continuity policy is evaluated as false (e.g., the eyes are undetectable for a period of time, the user (e.g., 704) was previously only authenticated by a password, and / or the user (e.g., 704) was previously only authenticated by a fingerprint), and / or a fingerprint tracking continuity policy is evaluated as false), biometrically authenticate the user of the device (e.g., 704) using a biometric sensor to perform a first type of biometric authentication (e.g., performing a first level (e.g., full or high fidelity) iris feature verification, and / or performing a first level (e.g., full or high fidelity) fingerprint verification). Authenticating the user when biometric continuity conditions are not met provides improved security / privacy by verifying that an authorized user is interacting with the device.

[0207] In some embodiments, a first type of biometric authentication is based on a biometric feature of the eye (e.g., the entire eye or a portion of the eye, such as an iris feature), and a second type of biometric authentication is based on a biometric feature of the eye (e.g., the entire eye or a portion of the eye, such as an iris feature). Ensuring that the biometric continuity condition is satisfied based on the eye feature provides improved security / privacy by verifying that the same user has been using the device since the initial authentication.

[0208] In some embodiments, the first type of biometric authentication is based on biometric features of the face (e.g., eyebrows, eyelids, skin around the eyes, forehead, nose), and the second type of biometric authentication is based on biometric features of the face (e.g., eyebrows, eyelids, skin around the eyes, forehead, nose). Ensuring that biometric continuity conditions are satisfied based on facial features provides improved security / privacy by verifying that the same user has been using the device since the initial authentication.

[0209] In some embodiments, a user of the device (e.g., 704) satisfying corresponding criteria includes repeatedly performing a second type of biometric authentication (e.g., performing a second level (e.g., for continuous tracking of eye information) iris feature verification) using one or more sensors of a computer system (e.g., 101 and / or 700), wherein the second type of biometric authentication includes: receiving input from the user (e.g., 704) including first corresponding biometric information (e.g., obtaining eye information from a current frame); and comparing the received input with previously received input including second corresponding biometric information (e.g., comparing eye information from a current frame with eye information from a previous frame). Taking multiple sensor measurements at multiple intermediate times between the first time and the second time provides improved security / privacy by verifying that the same user has been using the device since the initial authentication.

[0210] In some embodiments, the one or more sensors used to perform the second type of biometric authentication include a biometric sensor used to perform the first type of biometric authentication (e.g., the one or more sensors include a biometric sensor used to obtain a new biometric authentication). Taking multiple sensor measurements at multiple intermediate times between the first time and the second time provides improved security / privacy by verifying that the same user has been using the device since the initial authentication.

[0211] In some embodiments, a first type of biometric authentication is based on a first biometric feature (e.g., eyes and / or iris features of a user (e.g., 704)), and a second type of biometric authentication is based on a second type of biometric feature (e.g., continuous wear of the computer system and / or a fingerprint of the user (e.g., 704)), where the first biometric feature is different from the second biometric feature (e.g., iris feature verification is performed for initial authentication, while facial features are monitored for continuity). In some embodiments, at a first time, a user (e.g., 704) of a device is biometrically authenticated based on the first biometric feature of the user (e.g., 704) (e.g., a first level (e.g., full or high fidelity) iris feature verification is performed, including detecting details associated with the presence of eyes, iris features, pupils, and / or eye flashes). In some embodiments, a second biometric feature of a user (e.g., 704) is periodically detected (e.g., detecting eyebrows, eyelids, skin around the eyes, forehead, nose, mouth, and / or cheeks of the user (e.g., 704)), wherein a corresponding criterion is based on the periodic detection of the second biometric feature of the user (e.g., 704) (e.g., the continuity criterion depends on the detected details associated with the presence of eyebrows, eyelids, skin around the eyes, forehead, nose, mouth, and / or cheeks). When the feature used for initial authentication is not available for continuity verification, improved security / privacy is provided by improving authentication using the corresponding biometric feature used for initial authentication and a different biometric feature used for biometric continuity verification.

[0212] In some embodiments, a first type of biometric authentication is based on a first biometric feature (e.g., eyes and / or iris features of a user (e.g., 704) such that iris feature verification is performed for initial authentication), and a second type of biometric authentication is based on the first type of biometric feature (e.g., eyes and / or iris features of a user (e.g., 704) such that iris feature verification is performed for continuity). In some embodiments, at a first time, a user (e.g., 704) of a device is biometrically authenticated based on the first biometric feature of the user (e.g., 704) (e.g., performing a first level (e.g., full or high-fidelity) iris feature verification, including detecting details associated with the presence of eyes, iris features, pupils, and / or eye flashes). In some embodiments, a first biometric feature of a user (e.g., 704) is periodically detected (e.g., detecting details associated with the presence of an eye, iris features, pupil, and / or eye glint), wherein the corresponding criterion is based on the periodic detection of the first biometric feature of the user (e.g., 704) (e.g., the continuity criterion depends on the detected details associated with the presence of an eye, iris features, pupil, and / or eye glint). Using the corresponding biometric feature for both initial authentication and biometric continuity verification provides improved security / privacy by reducing the types of sensors required for authentication.

[0213] In some embodiments, biometrically authenticating a user of a device (e.g., 704) at a first time is based on a first biometric feature of the user (e.g., 704) (e.g., performing a first level (e.g., full or high fidelity) iris feature verification, including detecting details associated with the presence of an eye, iris feature, pupil, and / or eye glint), including: obtaining sensor measurements at multiple intermediate times between the first time and the second time (e.g., detecting details associated with the presence of an eye, iris feature, pupil, and / or eye glint), wherein the obtained sensor measurements include at least one sensor measurement indicating that the first biometric feature of the user (e.g., 704) was not detected at corresponding intermediate times of the multiple intermediate times (e.g., the sensor measurements indicate the absence of an eye, iris feature, pupil, and / or eye glint (e.g., based on the closure of the eyes of the user (e.g., 704))). When biometric continuity verification is performed based on different features, utilizing the corresponding biometric feature for initial authentication that is hidden and not visible provides improved security / privacy by ensuring that continuity verification can be performed despite the presence of the hidden feature.

[0214] In some embodiments, biometrically authenticating a user of a device (e.g., 704) at a first time is based on a first biometric feature of the user (e.g., 704) (e.g., performing a first level (e.g., full or high-fidelity) iris feature verification, including detecting details associated with the presence of an eye, iris features, pupil, and / or eye glint), including: periodically obtaining sensor measurements of a second biometric feature of the user (e.g., 704) at multiple intermediate times between the first time and the second time (e.g., detecting eyebrows, eyelids, skin around the eyes, forehead, nose, mouth, and / or cheeks of the user (e.g., 704)), wherein the obtained sensor measurements include a first biometric feature indicating that the user (e.g., 704) was not detected at the corresponding intermediate times. At least one sensor measurement of a biometric characteristic (e.g., the sensor measurement indicates the absence of eyes, iris features, pupils, and / or eye glints (e.g., based on the closure of eyes of the user (e.g., 704))), the obtained sensor measurements include at least one sensor measurement indicating that a second biometric characteristic of the user (e.g., 704) was detected at a corresponding intermediate time (e.g., the sensor measurement indicates the presence of eyebrows, eyelids, skin around eyes, forehead, nose, mouth, cheeks of the user (e.g., 704) without detecting the presence of eyes, iris features, pupils, and / or eye glints)), and the first biometric characteristic is different from the second biometric characteristic (e.g., iris feature verification is performed for initial authentication, while facial features are monitored for continuity). When biometric continuity verification is performed based on different visual features, utilizing the corresponding biometric feature for initial authentication that is hidden from view provides improved security / privacy by creating an efficient and uninterrupted user experience for biometric authentication, encouraging users to use biometric authentication, and thereby providing a more secure experience.

[0215] In some embodiments, the corresponding criteria (e.g., continuity criteria) between the first time and the second time include a continuity criteria that is satisfied when a biometric feature (e.g., an eye of a user (e.g., 704) and / or a fingerprint of a user (e.g., 704)) is repeatedly (e.g., continuously or periodically) detected between the first time and the second time (e.g., not determining that no biometric feature was detected between the first time and the second time). Taking multiple sensor measurements at multiple intermediate times between the first time and the second time provides improved security / privacy by verifying that the same user has been using the device since initial authentication.

[0216] In some embodiments, biometrically authenticating a user of a device (e.g., 704) using a biometric sensor to perform a first type of biometric authentication includes providing (e.g., displayed via a display generating component (e.g., 120 and / or 700a)) an authentication guidance user interface (e.g., 724, which includes instructions for performing the first type of biometric authentication, wherein the instructions request the user (e.g., 704) to provide specific movements of the biometric feature (e.g., instructions to gaze at a specific portion of the authentication guidance user interface (e.g., 726), rotate the face along a specific path (for facial authentication), and / or move a finger along a specific path). Displaying the authentication guidance user interface to facilitate user authentication provides improved security / privacy by reducing the chance of failed authentication attempts.

[0217] In some embodiments, the security operation includes providing payment information (e.g., Figure 7NAs shown) (e.g., providing payment information in order to purchase items and / or services (e.g., providing credit card information to an e-commerce website to purchase shoes)). In some embodiments, an electronic device (e.g., 700) participates in a transaction. For example, upon detecting that input has been received at a hardware user interface element (e.g., 722 and / or 758) and other criteria are met, a security element in a computer system (e.g., 700) publishes payment information to allow an application on the computer system (e.g., 700) to access the information (e.g., and transmit the information to a server associated with the application). In some embodiments, a security element is a hardware component (e.g., a secure microcontroller chip) configured to securely store data or algorithms. In some embodiments, the security element provides (or publishes) payment information (e.g., an account number and / or a transaction-specific dynamic security code). In some embodiments, the security element provides (or releases) payment information in response to the device (e.g., 700) receiving authorization, such as user authentication (e.g., fingerprint authentication; password authentication; detecting a double press of a hardware button (e.g., 722 and / or 758) while the device (e.g., 700) is in an unlocked state, and optionally while the device (e.g., 700) has been continuously on the wrist of the user (e.g., 704) since the device (e.g., 700) was unlocked by providing authentication credentials to the device (e.g., 700), wherein the continued presence of the device on the wrist of the user (e.g., 704) is determined by periodically checking that the device (e.g., 700) is in contact with the skin of the user (e.g., 704). In some embodiments, the security element provides (or releases) payment information in response to continuity criteria (e.g., performing a second level (e.g., continuous) iris feature verification) and / or gaze criteria (e.g., gaze is directed to a user interface and / or the object of the user's gaze is a user interface) being satisfied. Using biometric continuous authentication to enable user authorization of payment operations provides improved security / privacy by ensuring that the same user has been using the device since initial authentication.

[0218] In some embodiments, the security operation includes providing access credentials for accessing an application, such as an application associated with a third-party service (e.g., providing facial recognition data to access a stock trading application or a password storage application). In some embodiments, the security operation includes providing access credentials for accessing an application, such as an application associated with a third-party service (e.g., providing facial recognition data to access a stock trading application or a password storage application). Using biometric continuity verification to enable user authorization for application authentication provides improved security / privacy by ensuring that the same user has been using the device since the initial authentication.

[0219] In some embodiments, security operations include automatically filling in user credentials (e.g., username and / or password information for accessing secure information (e.g., providing login information (e.g., 706 and / or 708) to access a banking website)). Using biometric continuity verification to enable user authorization for autofill operations provides improved security / privacy by ensuring that the same user has been using the device since initial authentication.

[0220] In some embodiments, receiving a request to perform a security operation includes detecting a physical input for activating a hardware button (e.g., 722 and / or 758) (e.g., a user (e.g., 704) engaging in a double press of the hardware button initiates a payment operation and / or a user (e.g., 704) engaging in a double press of the hardware button initiates an autofill operation). In some embodiments, when activated using various inputs, the hardware button (e.g., 722 and / or 758) performs various corresponding functions, such as navigating to a home user interface, powering off the device, displaying a system user interface for powering off the device, and / or activating a voice assistant. In some embodiments, the physical input includes a single press, a long press, a single press followed by a long press, a press followed by a rotation, a rotation followed by a press, and / or multiple consecutive presses (e.g., a double press, a triple press). Utilizing a hardware element for authorization provides improved security / privacy by reducing the likelihood of erroneous authorization and / or preventing unauthorized input from malware.

[0221] In some embodiments, a system user interface (e.g., 702, 712, 736, 738, 748, and / or 752) is provided to a user (e.g., 704) (e.g., displayed via a display generation component (e.g., 120 and / or 700a)), the system user interface including an enablement representation associated with a security operation (e.g., an enablement representation labeled "Pay" or an enablement representation labeled "Autofill"), wherein receiving a request to perform a security operation includes detecting activation of an enablement representation (e.g., 710 and / or 750) associated with the security operation (e.g., the user (e.g., 704) activates the enablement representation with gaze, gaze and a hardware button, or only a hardware button). In some embodiments, the user gazes at the enablement representation (e.g., 710 and / or 750), and based on determining that the user has gazed at the enablement representation for a threshold period of time, the enablement representation (e.g., 710 and / or 750) is activated. In some embodiments, a user (e.g., 704) activates an affordance (e.g., 710 and / or 750) by activating a hardware button (e.g., 722 and / or 758) (e.g., a double press of the hardware button and / or a long press of the hardware button). In some embodiments, a user (e.g., 704) activates an affordance by activating a hardware button (e.g., 722 and / or 758) (e.g., a double press of the hardware button and / or a long press of the hardware button), and based on determining that the user (e.g., 704) is looking at the affordance (e.g., 710 and / or 750) while the user (e.g., 704) activates the hardware button, the affordance (e.g., 710 and / or 750) is activated. In some embodiments, a user (e.g., 704) activates an affordance (e.g., 710 and / or 750) by controlling an auxiliary device (e.g., a controller) to select an affordance (e.g., 710 and / or 750) (e.g., moving a cursor on the affordance while activating a hardware button and / or using a pointing device while activating a hardware button (e.g., 722 and / or 758)). Utilizing affordances for authorization in a system user interface provides improved security / privacy when the device is used with one or more alternative input devices.

[0222] In some embodiments, receiving a request to perform a security operation includes: when a virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) including information about a security operation (e.g., 706, 708, 710, 716a, 716b, 744a, and / or 744b) is provided to a user (e.g., 704) (e.g., via a display generating component (e.g., 120 and / or 700a)), detecting user activation of an enablement representation (e.g., 710 and / or 750) within the virtual user interface object (e.g., 702, 712, 736, 738, 748, and / or 752) (e.g., the user (e.g., 704) activates an enablement representation labeled "Authorize Payment" or the user (e.g., 704) activates an enablement representation labeled "Authorize Autofill"). Displaying information about the security operation when requesting authorization provides improved security / privacy by confirming that the user has an opportunity to review information associated with the security operation before the user authorizes proceeding with the security operation.

[0223] In some embodiments, the corresponding criteria include an eye open criterion that is satisfied when one or more eyes (e.g., one eye and / or both eyes) of a user (e.g., 704) do not remain continuously closed for more than a (e.g., non-zero) threshold time period (e.g., the continuity criterion is not satisfied when the eyes of the user (e.g., 704) are closed for more than the threshold time period), and wherein the eye open criterion is not satisfied when one or more eyes (e.g., one eye and / or both eyes) of a user (e.g., 704) remain continuously closed for more than a (e.g., non-zero) threshold time period (e.g., the continuity criterion is not satisfied when the eyes of the user (e.g., 704) are closed for more than the threshold time period). Determining that biometric continuity is not satisfied when eye closure is detected provides improved security / privacy by ensuring informed consent regarding the operation.

[0224] In some embodiments, the corresponding criteria are based on biometric features available for analysis without regard to whether the user's (e.g., 704) eyes are closed (e.g., and without regard to the duration of the user's (e.g., 704) eyes being closed) (e.g., the continuity criteria may be met even when the user (e.g., 704) closes their eyes for an extended period of time). Determining that biometric continuity is met when eye closure is detected provides improved security / privacy by improving authentication when features used for initial authentication are not available for continuity verification.

[0225] In some embodiments, aspects / operations of methods 800, 900, and 1000 may be interchanged, substituted, and / or added between these methods. For example, as part of method 800, the determination of whether a user satisfies corresponding (e.g., continuity) criteria in method 900 is optionally used to determine whether to enable user authorization. For the sake of brevity, these details are not repeated here.

[0226] Refer to the following about FIG. 7A to FIG. 7N The method 1000 described provides for FIG. 7A to FIG. 7N Additional description of .

[0227] Fig.10 1 is a flow chart of an exemplary method 1000 for authentication continuity of secure operations according to some embodiments. In some embodiments, the method 1000 includes a display generation component (e.g., Figure 1 , Figure 3 and Figure 4 The display generation components 120 in the computer system (e.g., display controller, touch-sensitive display system, display (e.g., integrated and / or connected), 3D display, transparent display, projector and / or head-up display)) (e.g., head-up display, display, touch screen, projector, etc.) and one or more input devices (e.g., Figure 1 In some embodiments, method 1000 is performed by storing in a non-transitory (or transient) computer-readable storage medium and executed by one or more processors of a computer system (such as one or more processors 202 of computer system 101) (e.g., Figure 1 Some operations in method 1000 are optionally combined, and / or the order of some operations is optionally changed.

[0228] As described below, method 1000 provides an intuitive way to authorize security operations via an accessibility interface. The method reduces the cognitive burden on the user when performing security operations via the accessibility interface, thereby creating a more efficient human-computer interface. For battery-powered computing devices, authorizing security operations faster and more efficiently via the accessibility interface saves power and increases the time between battery charges.

[0229] A request to display a user interface (e.g., 702, 712, 736, 738, 748, and / or 752) associated with performing a security operation (1002) (e.g., a request to perform an autofill process and / or a request to perform a payment transaction) is received via one or more input devices (e.g., 125 and / or 150). In response to a request to display a user interface (e.g., 702, 712, 736, 738, 748, and / or 752) associated with performing a security operation (1004), a first user interface (e.g., 702, 712, 736, 738, 748, and / or 752) (e.g., an interface displayed in response to receiving a request to perform an autofill process and / or an interface displayed in response to receiving a request to perform a payment transaction) is displayed via a display generating component (e.g., 120 and / or 700a), the first user interface including a corresponding prompt (e.g., 720, 734, and / or 756) for providing additional input (e.g., login details, account details, and / or information associated with pending purchases) to authorize the device to perform the security operation.

[0230] Based on determining that the computer system (e.g., 700) is operating in a first mode (1006) (e.g., a standard mode in which accessibility features are not enabled and / or a mode that permits authorization of security operations using a physical input mechanism (e.g., 722 and / or 758)), the corresponding prompt is a first prompt (e.g., 720, 734, and / or 756) for providing physical input (e.g., 722 and / or 758) (e.g., a first user interface (e.g., 702, 712, 736, 738, 748, and / or 752) prompting a user (e.g., 704) that the user should provide physical input (e.g., 722 and / or 758) (e.g., using a physical input mechanism ( For example, a button (e.g., 722 and / or 758) may be pressed, input of a press and / or multiple presses of a button (e.g., 722 and / or 758) may be provided to authorize a security operation (e.g., if a user (e.g., 704) intends to authorize an autofill process, a prompt (e.g., 720, 734, and / or 756) indicates that the user (e.g., 704) should provide a physical input (e.g., 722 and / or 758)), and / or if a user (e.g., 704) intends to authorize a purchase, a prompt (e.g., 720, 734, and / or 756) indicates that the user (e.g., 704) should provide a physical input (e.g., 722 and / or 758)).

[0231] Based on determining that the computer system (e.g., 700) is operating in a second mode different from the first mode (1008) (e.g., an accessibility mode and / or a mode in which input at the physical input mechanism (e.g., 722 and / or 758) is not required to authorize a security operation), the corresponding prompt (e.g., 720, 734, and / or 756) is a second prompt for displaying the second user interface (e.g., 742) (e.g., if the user (e.g., 704) intends to authorize the auto-fill process, the first user interface (e.g., 702, 712, 736, 738, 748, and / or 752) does not prompt the user (e.g., 704) that the user should provide the physical input (e.g., 722 and / or 758), and / or if the user (e.g., 704) intends to authorize the purchase, the first user interface The second user interface (e.g., 702, 712, 736, 738, 748, and / or 752) does not prompt a user (e.g., 704) that the user should provide physical input (e.g., 722 and / or 758)), wherein a second user interface (e.g., 742) enables user authorization of security operations without using physical input (e.g., 722 and / or 758) (e.g., enabling authorization of security operations using first-level (full or high-fidelity) iris feature authentication (e.g., first-level iris feature authentication performed when the user (e.g., 704) activates an enable representation (e.g., 744) and / or first-level iris feature authentication performed when the user (e.g., 704) gazes at an enable representation (e.g., 744)), and / or enabling authorization of security operations using first-level (full or high-fidelity) fingerprint authentication). When the device is used with one or more alternative input devices, allowing authorization of security operations without physical input provides improved security / privacy.

[0232] In some embodiments, a first corresponding enable representation (e.g., 740 and / or 750) is provided within a second prompt (e.g., 736 and / or 738) (e.g., displayed via a display generating component (e.g., 120 and / or 700a)) (e.g., the enable representation includes an indication that authorization for the security operation can be performed using a secondary input type that is different from the primary input type (e.g., 734) (e.g., an enable representation that displays “AutoFill” next to the text “Confirm with Assistive Touch” or that displays “Pay” next to the text “Confirm with Assistive Touch”)), and a user selection of the enable representation (e.g., 740 and / or 750) is received (e.g., the user (e.g., 704) selects the enable representation (e.g., 740) of “AutoFill” using gaze, gaze and adaptive accessory input, and / or adaptive accessory input, or the user (e.g., 704) selects the enable representation (e.g., 750) of “Pay” using gaze, gaze and adaptive accessory input, and / or adaptive accessory input). In some embodiments, a user (e.g., 704) gazes at an enable representation (e.g., 740 and / or 750), and based on determining that the user (e.g., 704) has gazed at the enable representation (e.g., 740 and / or 750) for a threshold time period, the enable representation (e.g., 740 and / or 750) is activated. In some embodiments, a user (e.g., 704) activates an enable representation (e.g., 740 and / or 750) by controlling an adaptive accessory (e.g., a switch control) to select an enable representation (e.g., 740 and / or 750) (e.g., the user (e.g., 704) taps the switch control a first time to initiate display of a sliding vertical line that slides back and forth across the display (e.g., 700a), and when the vertical line appears on the enable representation (e.g., 740 and / or 750), the user (e.g., 704) taps the switch control a second time, and in response to the second tap, a horizontal line that slides up and down across the display (e.g., 700a) is displayed, and when the horizontal line appears on the enable representation (e.g., 740 and / or 750), the user (e.g., 704) taps the switch control a third time). In some embodiments, a user (e.g., 704) controls an adaptive accessory to select an affordance (e.g., 740 and / or 750), and based on determining that the user (e.g., 704) is looking at an affordance (e.g., 740 and / or 750) while the user (e.g., 704) selects the affordance (e.g., 740 and / or 750), the affordance (e.g., 740 and / or 750) is activated. An adaptive accessory is an accessory that enables a user (e.g., 704) to provide input by alternative means compared to a typical usage scenario of the device, and an example of an adaptive accessory is a switch control that provides a limited number of selection states (e.g., between one and five), which are used to select between options provided by the device (e.g., 700).An example of a switch control is a device that can be activated by pressing, pulling, blinking, squeezing, and / or breathing via blowing / inhaling through a straw, such a device enabling a user with cognitive or physical accessibility needs to interact with the device (e.g., 700) when the user (e.g., 700) is unable to easily interact with the device (e.g., 704) using standard input schemes (e.g., using a touch screen, physical buttons / knobs, and / or mid-air gestures).

[0233] In some embodiments, in response to receiving a user selection of an enable representation, a second user interface (e.g., 742) is displayed, wherein the second user interface (e.g., 742) includes representations of multiple functions (e.g., an accessibility menu (e.g., 742) including multiple enable representations representing device functions is displayed), the multiple functions including a first corresponding function among the multiple functions invoked in response to a secondary input type different from the primary input type (e.g., the accessibility menu (e.g., 742) includes options such as "Home," "Control Center," "Device," "Notification," or "Customize"), and a second corresponding function (e.g., 744) among the multiple functions invoked in response to a third input type different from the primary input type and the secondary input type (e.g., the accessibility menu (e.g., 742) includes a new option "Authorize Autofill" or a new option "Pay"). In some embodiments, the accessibility menu (e.g., 742) includes a grid of affordances and an outline around one of the affordances (e.g., 744), such that the outline periodically (e.g., every 2 seconds or every 5 seconds) moves around different affordances (e.g., 744), where a user (e.g., 704) can provide input (e.g., input to a switch control and / or gaze input directed to the surrounded affordances) to select the currently outlined affordance (e.g., 744). Displaying an accessibility interface with alternative input options provides improved security / privacy when the device is used with one or more alternative input devices.

[0234] In some embodiments, the secondary input type simulates input of the primary input type (e.g., invoking "Home" in response to swiping up from a button on the screen), and the tertiary input type simulates input of the primary input type (e.g., invoking "Home" in response to a custom input (e.g., a long press) via an accessibility menu (e.g., 742)). Enabling simulated input for traditional input types provides improved security / privacy when the device is used with one or more alternative input devices.

[0235] In some embodiments, when the computer system (e.g., 700) is operating in the second mode: an enable representation (e.g., 740 and / or 750) associated with a corresponding prompt is displayed (e.g., an enable representation of "AutoFill" is displayed with the text "Confirm with Assistive Touch" or an enable representation of "Pay" is displayed with the text "Confirm with Assistive Touch"), and based on receiving user input associated with the corresponding prompt (e.g., the user (e.g., 704) selects the enable representation (e.g., 740) of "AutoFill" using gaze, gaze and adaptive accessory input, and / or adaptive accessory input, or the user (e.g., 704) selects the enable representation (e.g., 750) of "Pay" using gaze, gaze and adaptive accessory input, and / or adaptive accessory input), a second user interface (e.g., 742) is displayed, wherein the second user interface ( For example, 742) includes an enable indication (e.g., 744) for authorizing a security operation (e.g., displaying an accessibility menu (e.g., 742) including a new option "Authorize AutoFill" or a new option "Pay", wherein the enable indication (e.g., 744) for authorizing the security operation is invoked in response to a secondary input type different from the primary input type (e.g., in response to a custom input (e.g., long press) via the accessibility menu (e.g., 742) instead of the primary input type (e.g., double press of the side button (e.g., 722 and / or 758)) invoking the option "Authorize AutoFill", or in response to a custom input (e.g., long press) via the accessibility menu (e.g., 742) instead of the primary input type (e.g., double press of the side button (e.g., 722 and / or 758)) invoking the option "Pay". When the device is used with one or more alternative input devices, displaying an accessibility interface including a security operation authorization enable indication provides improved security / privacy.

[0236] In some embodiments, details associated with the performance of a security operation are displayed within a user interface (e.g., 702, 712, 736, 738, 748, and / or 752) associated with performing the security operation (e.g., the interface includes details for performing an autofill process (e.g., a username field and a password field) or the interface includes details for performing a payment transaction (e.g., an item name, an item description, an item price). In some embodiments, when the computer system (e.g., 700) is operating in a second mode (e.g., an accessibility mode and / or a mode in which input at a physical input mechanism (e.g., 722 and / or 758) is not required to authorize the security operation), the display An enable representation (e.g., 740 and / or 750) associated with the corresponding prompt (e.g., an enable representation of "AutoFill" with the text "Confirm with Assistive Touch", or an enable representation of "Pay" with the text "Confirm with Assistive Touch"). In some embodiments, user input associated with the corresponding prompt is received (e.g., the user (e.g., 704) selects the enable representation (e.g., 740) of "AutoFill" using gaze, gaze + adaptive accessory input, and / or adaptive accessory input, or the user (e.g., 704) selects the enable representation (e.g., 750) of "Pay" using gaze, gaze and adaptive accessory input, and / or adaptive accessory input), and based on determining Upon receiving user input associated with a corresponding prompt (e.g., a user (e.g., 704) selecting an affordance (e.g., 740) of “autofill” while gazing at an interface including details for performing an autofill process, or a user (e.g., 704) selecting an affordance (e.g., 750) of “pay” while gazing at an interface including details for performing a payment transaction), the user (e.g., 704) is gazing at a user interface associated with performing a security operation, displaying a second user interface (e.g., 742), wherein the second user (e.g., 742) interface includes an accessibility menu for authorizing the security operation (e.g., displaying a new option “authorize autofill” or a new option “pay”). A single (e.g., 742)) indication (e.g., 744) for authorizing a security operation is displayed, and an indication (e.g., 744) for authorizing a security operation is displayed in response to a secondary input type that is different from the primary input type (e.g., in response to invoking the option "Authorize AutoFill" in response to a custom input (e.g., a long press) via an accessibility menu (e.g., 742) rather than the primary input type (e.g., a double press of a side button (e.g., 722 and / or 758)), or invoking the option "Pay" in response to a custom input (e.g., a long press) via an accessibility menu (e.g., 742) rather than the primary input type (e.g., a double press of a side button (e.g., 722 and / or 758)).Displaying an accessibility interface in response to a combination of gaze and affordance activation provides improved security / privacy when the device is used with one or more alternative input devices.

[0237] In some embodiments, when the computer system (e.g., 700) is operating in a first mode (e.g., a standard mode in which accessibility features are not enabled and / or a mode that permits authorization of security operations using physical input mechanisms), user activation of physical input (e.g., 722 and / or 758) is received while a first prompt (e.g., 720, 734, and / or 756) is displayed (e.g., a user (e.g., 704) performs a predetermined activation mode represented by a hardware input indication, such as a double-click of a hardware button (e.g., 722 and / or 758)). In some embodiments, the predetermined activation mode includes a single press, a long press, a single press followed by a long press, a press followed by a rotation, a rotation followed by a press, and / or multiple consecutive presses (e.g., a double press or a triple press). In some embodiments, in response to user activation of receiving a physical input (e.g., 722 and / or 758) while displaying a first prompt (e.g., 720, 734, and / or 756): based on determining that user authentication criteria are satisfied (e.g., the user (e.g., 704) is looking at the prompt (e.g., 720, 734, and / or 756)), a security operation is authorized (e.g., an autofill process is authorized in response to activation of a hardware button (e.g., 722 and / or 758) or a payment process is authorized in response to activation of a hardware button (e.g., 722 and / or 758)). In some embodiments, authorization for a security operation is waived (e.g., preventing an autofill process in response to a double-click of a hardware button (e.g., 722 and / or 758), or preventing a payment process in response to a double-click of a hardware button (e.g., 722 and / or 758)) based on a determination that user authentication criteria are not met (e.g., the user (e.g., 704) is not looking at a prompt (e.g., 720, 734, and / or 756)). When the device is used with one or more alternative input devices, improved security / privacy is provided using accessible and inaccessible operating modes.

[0238] In some embodiments, the authentication criteria include criteria that are satisfied when the user (e.g., 704) provides a specific movement of the biometric feature (e.g., gazes at a specific portion of the authentication guide user interface (e.g., 724), provides a facial rotation along a specific path, and / or moves a finger along a specific path). Requiring specific movement of the biometric feature when the physical input mechanism is activated provides improved security / privacy by ensuring informed consent for secure operations.

[0239] In some embodiments, input is received from a user (e.g., 704) to authorize a security operation (e.g., when in standard mode, a user (e.g., 704) performs activation of a hardware button (e.g., 722 and / or 758)) (e.g., a single press, a long press, a single press followed by a long press, a press followed by a rotation, a rotation followed by a press, multiple consecutive presses (e.g., a double press, a triple press), or when in accessibility mode, in response to custom input via an accessibility menu (e.g., 742) invoking the option "Authorize AutoFill" or in response to a request via an accessibility menu (e.g., 742) to invoke option "Pay"), and in response to receiving input for authorizing a security operation: performing user authentication (e.g., performing a first level (e.g., full or high-fidelity) iris feature verification, performing a second level (e.g., continuity) iris feature verification, or performing a password verification); and based on determining that the user (e.g., 704) is authenticated, authorizing the security operation (e.g., determining whether authentication continuity is true since the last full or high-fidelity biometric authentication, performing a full or high-fidelity biometric authentication, and / or performing a password authentication). In some embodiments, based on determining that the user (e.g., 704) is not authenticated, the security operation is not authorized (e.g., the device waives authorization of the security operation). In addition to user authorization for security operations, requiring user authentication provides improved security / privacy by adding an additional layer of verification specific to the user requesting authorization.

[0240] In some embodiments, performing user authentication includes performing a second type of biometric authentication (e.g., performing a second level (e.g., for continuously tracking eye information) iris feature verification) (e.g., performing includes repeatedly performing authentication every 2 frames (e.g., a frame includes a static image or a collection of images obtained from a sensor of the device (e.g., a biometric sensor)), every 3 frames, every 4 frames, every 5 frames, every 6 frames, every 7 frames, every 8 frames, every 9 frames, or every 10 frames), wherein the second type of biometric authentication includes: receiving input from a user (e.g., 704) including first corresponding biometric information (e.g., obtaining eye information from a current frame); and comparing the received input with a previously received input including second corresponding biometric information (e.g., comparing eye information from a current frame with eye information from a previous frame). In addition to user authorization for secure operations, utilizing stored authentication information provides improved security / privacy by verifying that the same user has been using the device since the initial authentication.

[0241] In some embodiments, performing user authentication includes performing a first type of biometric authentication, where the first type of biometric authentication includes detecting the presence of a first biometric feature type (e.g., a first level (e.g., full or high fidelity) authentication based on eye features, or a first level (e.g., full or high fidelity) authentication based on facial features). In addition to being used for user authorization for security operations, requiring full or high fidelity biometric authentication provides improved security / privacy by verifying that an authorized user is requesting the security operation.

[0242] In some embodiments, performing user authentication includes: providing a prompt (e.g., 728) requesting a password from a user (e.g., 704); receiving a password from a user (e.g., 704) in response to the prompt (e.g., 728) (e.g., receiving a plurality of numeric entries (e.g., 0-9)); determining that the user (e.g., 704) is authenticated based on determining that the received password matches a stored password; and authorizing a security operation based on determining that the user (e.g., 704) is authenticated (e.g., the user interface is not displayed as grayed out, a button is marked as active, or the user interface provides text indicating that the user (e.g., 704) can request to perform a security operation (e.g., "Continue Request")). In some embodiments, based on determining that the received password does not match the stored password, it is determined that the user (e.g., 704) is not authenticated and the security operation is not authorized. Requiring password authentication provides improved security / privacy by providing an additional method of verifying user identity in addition to user authorization for security operations.

[0243] In some embodiments, an input for authorizing a security operation is detected, and in response to detecting the input for authorizing the security operation: based on determining that the input is a physical input (e.g., 722 and / or 758) for authorizing the security operation (e.g., the activation process of a physical button (e.g., 722 and / or 758) for authorizing autofill or the activation process of a physical button (e.g., 722 and / or 758) for authorizing payment): in some embodiments, the activation process includes a single press, a long press, a single press followed by a long press, a press followed by a rotation, a rotation followed by a press, multiple consecutive presses (e.g., a double press, a triple press). In some embodiments, authentication information is retrieved, the authentication information being associated with a second type of biometric authentication that is repeatedly performed (e.g., retrieving continuity information about a second level (e.g., for continuous tracking of eye information) iris feature verification that has been previously performed). In some embodiments, based on determining that the input is not a physical input for authorizing the security operation, it is determined whether the input is associated with a second user interface (e.g., 742). In some embodiments, a security operation is authorized based on determining that a user (e.g., 704) is authenticated based on the second type of biometric authentication (e.g., authorizing auto-fill if the second level (e.g., for continuous tracking of eye information) iris feature verification is successful, or authorizing payment if the second level (e.g., for continuous tracking of eye information) iris feature verification is successful); in some embodiments, a security operation is not authorized based on determining that a user (e.g., 704) is not authenticated based on the second type of biometric authentication (e.g., the tracked eye information indicates that the user's (e.g., 704) eyes were closed for a period of time (e.g., 5 seconds, 7 seconds, or 10 seconds) during device interaction).

[0244] In some embodiments, based on determining that the input is an input associated with a second user interface (e.g., 742) (e.g., the input is detected via an accessibility menu), where the input associated with the second user interface (e.g., 742) enables user authorization of security operations without using physical input (e.g., the detected input is associated with the option "autofill" or the new option "pay"): performing a first type of biometric authentication; and (e.g., performing a first level (e.g., full or high fidelity) iris feature verification) based on determining that the user (e.g., 704) is authenticated based on the first type of biometric authentication, authorizing the security operation (e.g., authorizing autofill if the first level (e.g., full or high fidelity) iris feature verification is successful, or authorizing payment if the first level (e.g., full or high fidelity) iris feature verification is successful). In some embodiments, based on determining that the user (e.g., 704) is not authenticated based on the first type of biometric authentication, the security operation is not authorized. In some embodiments, based on determining that the input is not an input associated with the second user interface (e.g., 742), it is determined whether the input is an additional input that is not associated with a physical input used to authorize the security operation (e.g., 722 and / or 758). Requiring full or high-fidelity biometric authentication when the device is operating in accessible mode provides improved security / privacy by verifying that an authorized user is requesting the security operation.

[0245] In some embodiments, aspects / operations of methods 800, 900, and 1000 may be interchanged, substituted, and / or added between these methods. For example, as part of method 1000, the determination of whether the user meets the corresponding (e.g., continuity) criteria in method 900 is optionally used to authorize security operations via the accessibility interface. For the sake of brevity, these details are not repeated here.

[0246] For the purpose of explanation, the foregoing description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or to limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. The embodiments are selected and described in order to best illustrate the principles of the present invention and its practical application, so that other technical personnel in the field can best use the present invention and the various described embodiments with various modifications suitable for the specific purpose contemplated.

[0247] As described above, one aspect of the present technology is to collect and use data from various sources to improve authorization of security operations. The disclosure contemplates that, in some instances, these collected data may include personal information data that uniquely identifies or can be used to contact or locate a specific person. Such personal information data may include demographic data, location-based data, phone numbers, email addresses, Twitter IDs, home addresses, data or records (e.g., vital sign measurements, medication information, exercise information) related to the health or fitness level of a user (e.g., 704), date of birth, or any other identification or personal information.

[0248] The present disclosure recognizes that the use of such personal information data in the present technology can be used to benefit users. For example, personal information data can be used to improve authorization of security operations. In addition, the present disclosure also anticipates other uses of personal information data that benefit users. For example, health and fitness data can be used to provide insights into the user's overall health status, or can be used as positive feedback to individuals who use technology to pursue health goals.

[0249] The disclosure anticipates that entities responsible for the collection, analysis, disclosure, transmission, storage or other purposes of such personal information data will comply with sound privacy policies and / or privacy measures. Specifically, such entities should implement and adhere to the use of privacy policies and practices that are recognized as meeting or exceeding the industry or government requirements for maintaining the privacy and security of personal information data. Such policies should be easy for users to access and should be updated as changes in the collection and / or use of data occur. Personal information from users should be collected for legal and reasonable entity purposes and should not be shared or sold outside these legal purposes. In addition, such collection / sharing should be carried out after receiving the informed consent of the user. In addition, such entities should consider taking any necessary steps to protect and safeguard access to such personal information data, and ensure that other entities with access to personal information data comply with their privacy policies and procedures. In addition, such entities can subject themselves to third-party assessments to prove that they comply with widely accepted privacy policies and practices. In addition, policies and practices should be adapted to specific types of personal information data collected and / or accessed, and to applicable laws and standards including considerations of special jurisdictions. For example, in the United States, the collection or acquisition of certain health data may be governed by federal and / or state laws, such as the Health Insurance Portability and Accountability Act (HIPAA); while health data in other countries may be subject to other regulations and policies and should be handled accordingly. Therefore, different privacy measures should be advocated for different types of personal data in each country.

[0250] Regardless of the foregoing, the present disclosure also contemplates implementation schemes in which users selectively block the use or access of personal information data. That is, the present disclosure contemplates hardware components and / or software components to prevent or block access to such personal information data. For example, with respect to authorizing security operations, the technology of the present invention may be configured to allow users to choose to "opt in" or "opt out" to participate in the collection of personal information data during or at any time after the registration service. In another example, the user may choose not to provide data for customizing security operations (such as payment and auto-fill). In yet another example, the user may choose to limit the length of time to maintain the data or completely prohibit the development of customized services to facilitate security operations, such as payment or auto-fill. In addition to providing "opt in" and "opt out" options, the present disclosure also contemplates providing notifications related to access or use of personal information. For example, the user may be notified that their personal information data will be accessed when the application is downloaded, and then the user is reminded again just before the personal information data is accessed by the application.

[0251] In addition, the intention of the present disclosure is that personal information data should be managed and processed in a manner that minimizes the risk of unintentional or unauthorized access or use. Once the data is no longer needed, the risk can be minimized by limiting the collection of data and deleting the data. In addition, and when applicable, including in certain health-related applications, data separation identification can be used to protect the privacy of the user. It can be facilitated to separate from the identification by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of the stored data (e.g., collecting location data at the city level rather than at the address level), controlling how the data is stored (e.g., aggregating data between users), and / or other methods when appropriate.

[0252] Thus, while the present disclosure broadly covers the use of personal information data to implement one or more of the various disclosed embodiments, the present disclosure also contemplates that various embodiments may also be implemented without access to such personal information data. That is, various embodiments of the present technology will not fail to function properly due to the lack of all or a portion of such personal information data. For example, authorization of security operations may be facilitated based on non-personal information data or an absolute minimum amount of personal information, such as content requested by a device associated with a user, other non-personal information available to a service, or publicly available information.

Claims

1. A method comprising: At a computer system in communication with one or more input devices and a display generating component: detecting, via the one or more input devices, a change in a current viewpoint of a user while a three-dimensional environment is visible via the display generation component, wherein the three-dimensional environment includes a virtual user interface object containing information regarding safe operation; and In response to detecting the change in the viewpoint of the user: enabling user authorization of the security operation using the virtual user interface object based on determining that at least a threshold amount of the virtual user interface object is visible from the viewpoint of the user and that the user is authorized to perform the security operation; as well as Based on determining that less than the threshold amount of the virtual user interface object is visible from the viewpoint of the user, enabling user authorization for the security operation using the virtual user interface object is foregone.

2. The method according to claim 1, comprising: receiving input from the user authorizing performance of the security operation; as well as In response to receiving the input for authorizing performance of the security operation: initiating execution of the security operation based on determining that one or more sets of execution criteria are satisfied, wherein the one or more sets of execution criteria include a visibility criterion that is satisfied when at least the threshold amount of the virtual user interface objects is visible from the viewpoint of the user; and Based on determining that the one or more sets of execution criteria are not satisfied, initiating execution of the security operation is abandoned. 3 . The method of claim 2 , wherein the one or more execution criteria sets include user authentication criteria that are satisfied when the user is authenticated.

4. The method according to claim 3, comprising: detecting biometric information from the user; as well as The biometric information is compared to enrolled biometric information, wherein determining whether the user authentication criteria are met is based on the comparison of the biometric information to the enrolled biometric information.

5. A method according to any one of claims 3 to 4, wherein determining that the user authentication criteria are satisfied occurs in response to receiving the input for authorizing performance of the security operation.

6. A method according to any one of claims 3 to 4, wherein determining whether the user authentication criteria are met includes obtaining stored authentication information, wherein the stored authentication information indicates one or more previously performed biometric authentications.

7. The method according to any one of claims 3 to 4, wherein determining whether the user authentication criteria are met comprises: performing a first type of biometric authentication; After performing the first type of biometric authentication, repeatedly performing a second type of biometric authentication, wherein the second type of biometric authentication includes: receiving input including first corresponding biometric information from the user; as well as The received input is compared to a previously received input including second corresponding biometric information.

8. The method according to claim 7, wherein: Performing said first type of biometric authentication includes detecting the presence of a first biometric feature type; as well as Performing the second type of biometric authentication includes detecting the presence of a second biometric feature type, wherein the first biometric feature type and the second biometric feature type correspond to the same biometric feature type.

9. The method according to any one of claims 3 to 4, wherein the user authentication criteria is met when the user is authenticated based on eye biometrics.

10. A method according to any one of claims 3 to 4, wherein the user authentication criteria are met when a password input matches a registered password.

11. The method according to any one of claims 3 to 4, comprising: Based on determining that the user authentication criteria are not met, a prompt is provided for enabling authentication with a password.

12. The method of any one of claims 1 to 4, wherein user authorization of the security operation using the virtual user interface object comprises user activation of a hardware user interface element.

13. The method according to any one of claims 1 to 4, wherein the security operation is a payment.

14. The method of any one of claims 1 to 4, wherein the security operation comprises automatically filling in user credentials.

15. The method according to any one of claims 1 to 4, comprising: In response to detecting the change in the viewpoint of the user, changing an amount of the virtual user interface object that is visible to the user.

16. The method of claim 15, wherein the amount of the virtual user interface object that is visible changes based on occlusion by a physical object.

17. The method of claim 15, wherein the amount of the virtual user interface object that is visible changes based on occlusion by a virtual object.

18. The method of any one of claims 1 to 4, wherein a visible amount of the virtual user interface object changes based on the virtual user interface object moving out of the user's field of view.

19. A method according to any one of claims 1 to 4, wherein the visible amount of the virtual user interface object changes based on the virtual user interface object moving more than a threshold distance from the center of the user's field of view.

20. The method of any one of claims 1 to 4, wherein a visible amount of the virtual user interface object changes based on occlusion by a physical object.

21. The method of any one of claims 1 to 4, wherein determining that the user is authorized to perform the security operation comprises determining whether gaze criteria are satisfied when the user is looking at the virtual user interface object.

22. The method of any one of claims 1 to 4, wherein determining that the user is authorized to perform the security operation comprises determining whether eye criteria are met when the user's eyes are open.

23. The method according to any one of claims 1 to 4, comprising: based on determining that at least a threshold amount of the virtual user interface object is visible from the viewpoint of the user, modifying the appearance of the virtual user interface object to indicate to the user that the user is able to request performance of the security operation; as well as Based on determining that less than the threshold amount of the virtual user interface object is visible from the viewpoint of the user, modifying the appearance of the virtual user interface object to indicate to the user that the user cannot request to perform the security operation.

24. The method according to any one of claims 1 to 4, wherein the three-dimensional environment includes a virtual object associated with the safety operation, the method comprising: The virtual user interface object is attached to the virtual object associated with the safety operation, wherein movement of the virtual object causes the attached virtual user interface object to move with the virtual object.

25. A computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 24.

26. A computer system in communication with a display generation component and one or more input devices, the computer system comprising: one or more processors; as well as A memory storing one or more programs configured to be executed by the one or more processors, the one or more programs comprising instructions for executing the method according to any one of claims 1 to 24.

27. A computer system in communication with a display generation component and one or more input devices, the computer system comprising: A component for carrying out the method according to any one of claims 1 to 24.

28. A computer program product comprising one or more programs configured to be executed by one or more processors of a computer system in communication with a display generating component and one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 1 to 24.

Images