User interface for sharing electronic key

Abstract

The present disclosure generally relates to a user interface for sharing and / or re-sharing an electronic key provisioned onto an electronic wallet of a computer system.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Patent Application No. 63 / 349,088, filed on June 4, 2022, entitled “USER INTERFACES FOR SHARING AN ELECTRONIC KEY” and U.S. Patent Application No. 17 / 949,042, filed on September 20, 2022, entitled “USER INTERFACES FOR SHARING AN ELECTRONIC KEY”. The contents of each of these patent applications are incorporated herein by reference in their entirety. Technical Field

[0003] The present disclosure relates generally to computer user interfaces and, more particularly, to techniques for sharing electronic keys. Background Art

[0004] The electronic key optionally provides access to the physical location, for example, through wireless communication between the device storing the electronic key and an external device that grants physical access to the physical location. Summary of the invention

[0005] However, some techniques for sharing electronic keys using electronic devices are often cumbersome and inefficient. For example, some prior art techniques use complex and time-consuming user interfaces that may include multiple key presses or keystrokes. Prior art techniques require more time than necessary, which results in wasted user time and device energy. This latter consideration is particularly important in battery-powered devices.

[0006] Therefore, the present technology provides a faster and more efficient method and interface for electronic devices to share electronic keys. Such methods and interfaces optionally supplement or replace other methods for sharing electronic keys. Such methods and interfaces reduce the cognitive burden on users and produce a more efficient human-computer interface. For battery-driven computing devices, such methods and interfaces save power and increase the time interval between battery charges. In addition, such methods and interfaces provide improved security for the electronic key sharing process and how electronic devices share physical access rights when sharing electronic keys.

[0007] According to some embodiments, a method is described. The method includes: at a first computer system in communication with a display generation component and one or more input devices: when the first computer system is associated with a first user, detecting via the one or more input devices a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations; and in response to detecting the set of one or more inputs corresponding to the request to share the electronic key: initiating a process of sharing the electronic key with a second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system includes: displaying via the display generation component a first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is enabled; and abandoning displaying the first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is disabled.

[0008] 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 a display generation component and one or more input devices, the one or more programs including instructions for the following operations: when a first computer system is associated with a first user, detecting via the one or more input devices a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations; and in response to detecting the set of one or more inputs corresponding to the request to share the electronic key: initiating a process of sharing the electronic key with a second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system includes: displaying via the display generation component a first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is enabled; and abandoning displaying the first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is disabled.

[0009] According to some embodiments, a transient computer-readable storage medium is described. The transient 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 a display generation component and one or more input devices, the one or more programs including instructions for the following operations: when a first computer system is associated with a first user, detecting via the one or more input devices a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations; and in response to detecting the set of one or more inputs corresponding to the request to share the electronic key: initiating a process of sharing the electronic key with a second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system includes: displaying via the display generation component a first selectable object for initiating a process of transmitting the activation code based on determining that an activation code for sharing the electronic key is enabled; and abandoning displaying the first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is disabled.

[0010] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. 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 first computer system is associated with a first user, detecting via the one or more input devices a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations; and in response to detecting the set of one or more inputs corresponding to the request to share the electronic key: initiating a process of sharing the electronic key with a second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system includes: displaying a first selectable object for initiating a process of transmitting the activation code via the display generation component based on determining that an activation code for sharing the electronic key is enabled; and abandoning displaying the first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is disabled.

[0011] According to some embodiments, a computer system configured to communicate with a display generation component and one or more input devices is described. The computer system includes: when a first computer system is associated with a first user, a component for detecting a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user via the one or more input devices, wherein the electronic key provides one or more access rights to one or more physical locations; and a component for initiating a process of sharing the electronic key with a second user of a second computer system different from the first user of the first computer system in response to detecting the set of one or more inputs corresponding to the request to share the electronic key, wherein the process of sharing the electronic key with the second user of the second computer system includes: displaying a first selectable object for initiating a process of transmitting the activation code via the display generation component based on determining that an activation code for sharing the electronic key is enabled; and abandoning displaying the first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is disabled.

[0012] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a computer system in communication with a display generation component and one or more input devices, the one or more programs including instructions for the following operations: when a first computer system is associated with a first user, detecting via the one or more input devices a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations; and in response to detecting the set of one or more inputs corresponding to the request to share the electronic key: initiating a process of sharing the electronic key with a second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system includes: displaying via the display generation component a first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is enabled; and abandoning displaying the first selectable object for initiating a process of transmitting the activation code based on determining that the activation code for sharing the electronic key is disabled.

[0013] According to some embodiments, a method is described. The method includes: at a first computer system in communication with one or more input devices: when the first computer system is associated with a first user, receiving first information from a second user of a second computer system different from the first user of the first computer system, the first information about an electronic key to be supplied to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; supplying the electronic key to the electronic wallet of the first computer system using the first information about the electronic key; after supplying the electronic key to the electronic wallet of the first computer system, detecting a request to share the electronic key with a third user different from the first user and the second user via the one or more input devices, wherein the request to share the electronic key with the third user specifies a second set of access rights for sharing the electronic key; and in response to detecting the request to share the electronic key with the third user, initiating a process of sharing the electronic key with a third user of a third computer system different from the first computer system and the second computer system having a second set of access rights.

[0014] 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 first computer system in communication with one or more input devices, and the one or more programs include instructions for the following operations: when the first computer system is associated with a first user, receiving first information from a second user of a second computer system different from the first user of the first computer system, the first information about an electronic key to be supplied to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; using the first information about the electronic key to supply the electronic key to the electronic wallet of the first computer system; after supplying the electronic key to the electronic wallet of the first computer system, detecting a request to share the electronic key with a third user different from the first user and the second user via the one or more input devices, wherein the request to share the electronic key with the third user specifies a second set of access rights for sharing the electronic key; and in response to detecting the request to share the electronic key with the third user, initiating a process of sharing the electronic key with a third user of the third computer system different from the first computer system and the second computer system with the second set of access rights.

[0015] According to some embodiments, a transient computer-readable storage medium is described. The transient computer-readable storage medium stores one or more programs configured to be executed by one or more processors of a first computer system in communication with one or more input devices, the one or more programs including instructions for the following operations: when the first computer system is associated with a first user, receiving first information from a second user of a second computer system different from the first user of the first computer system, the first information about an electronic key to be supplied to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; using the first information about the electronic key to supply the electronic key to the electronic wallet of the first computer system; after supplying the electronic key to the electronic wallet of the first computer system, detecting a request to share the electronic key with a third user different from the first user and the second user via the one or more input devices, wherein the request to share the electronic key with the third user specifies a second set of access rights for sharing the electronic key; and in response to detecting the request to share the electronic key with the third user, initiating a process of sharing the electronic key with a third user of the third computer system different from the first computer system and the second computer system having the second set of access rights.

[0016] According to some embodiments, a first computer system configured to communicate with one or more input devices is described. The first 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 the first computer system is associated with a first user, receiving first information from a second user of a second computer system different from the first user of the first computer system, the first information about an electronic key to be supplied to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; using the first information about the electronic key to supply the electronic key to the electronic wallet of the first computer system; after supplying the electronic key to the electronic wallet of the first computer system, detecting a request to share the electronic key with a third user different from the first user and the second user via the one or more input devices, wherein the request to share the electronic key with the third user specifies a second set of access rights for sharing the electronic key; and in response to detecting the request to share the electronic key with the third user, initiating a process of sharing the electronic key with a third user of a third computer system different from the first computer system and the second computer system having a second set of access rights.

[0017] According to some embodiments, a first computer system configured to communicate with one or more input devices is described. The computer system includes: a component for receiving first information from a second user of a second computer system different from the first user of the first computer system when the first computer system is associated with a first user, the first information about an electronic key to be supplied to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; a component for supplying the electronic key to the electronic wallet of the first computer system using the first information about the electronic key; after supplying the electronic key to the electronic wallet of the first computer system, a component for detecting a request to share the electronic key with a third user different from the first user and the second user via the one or more input devices, wherein the request to share the electronic key with the third user specifies a second set of access rights for sharing the electronic key; and a component for initiating a process of sharing the electronic key with a third user of a third computer system different from the first computer system and the second computer system in response to detecting the request to share the electronic key with the third user.

[0018] According to some embodiments, a computer program product is described. The computer program product includes one or more programs configured to be executed by one or more processors of a first computer system in communication with one or more input devices, and the one or more programs include instructions for the following operations: when the first computer system is associated with a first user, receiving first information from a second user of a second computer system different from the first user of the first computer system, the first information about an electronic key to be supplied to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; using the first information about the electronic key to supply the electronic key to the electronic wallet of the first computer system; after supplying the electronic key to the electronic wallet of the first computer system, detecting a request to share the electronic key with a third user different from the first user and the second user via the one or more input devices, wherein the request to share the electronic key with the third user specifies a second set of access rights for sharing the electronic key; and in response to detecting the request to share the electronic key with the third user, initiating a process of sharing the electronic key with a third user of the third computer system different from the first computer system and the second computer system having a second set of access rights.

[0019] Executable instructions for performing these functions are optionally included in a non-transitory computer-readable storage medium or other computer program product configured for execution by one or more processors. Executable instructions for performing these functions are optionally included in a transient computer-readable storage medium or other computer program product configured for execution by one or more processors.

[0020] Thus, a faster, more efficient method and interface is provided to devices for sharing electronic keys, thereby increasing the effectiveness, efficiency, and user satisfaction of such devices.Such methods and interfaces may supplement or replace other methods for sharing electronic keys. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] 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.

[0022] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.

[0023] Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments.

[0024] Figure 2 A portable multifunction device with a touch screen according to some embodiments is illustrated.

[0025] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.

[0026] Figure 4A An exemplary user interface for a menu of applications on a portable multifunction device according to some embodiments is illustrated.

[0027] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is illustrated according to some embodiments.

[0028] Figure 5A Personal electronic devices according to some embodiments are illustrated.

[0029] Figure 5B is a block diagram illustrating a personal electronic device according to some embodiments.

[0030] Figure 5C Illustrated are example devices connected via one or more communication channels in accordance with some embodiments.

[0031] FIG. 6A to FIG. 6RAn exemplary user interface for sharing an electronic key according to some embodiments is illustrated.

[0032] Figure 7 is a flow chart illustrating a method of sharing an electronic key according to some embodiments.

[0033] FIG. 8A to FIG. 8L An exemplary user interface for re-sharing an electronic key according to some embodiments is illustrated.

[0034] Fig. 9 is a flow chart illustrating a method of re-sharing a shared electronic key according to some embodiments. DETAILED DESCRIPTION

[0035] The following description sets forth exemplary methods, parameters, etc. However, it should be appreciated that such description is not intended to limit the scope of the present disclosure, but is provided as a description of exemplary embodiments.

[0036] An electronic device that provides an efficient method and interface for sharing electronic keys is needed. For example, a shared electronic key provides access rights to a physical location for different electronic devices. Such technology can reduce the cognitive burden of users who share electronic keys, thereby improving productivity. In addition, such technology can reduce processor power and battery power that would otherwise be wasted on redundant user input. In addition, such technology improves the security of how to share electronic keys (including the initial process of sharing electronic keys and / or managing access rights of a shared key that has been re-shared with another electronic device).

[0037] under, Figure 1A to Figure 1B , Figure 2 , Figure 3 , FIG. 4A to FIG. 4B as well as FIG. 5A to FIG. 5C A description of an exemplary device for implementing techniques for sharing an electronic key is provided. FIG. 6A to FIG. 6R An exemplary user interface for sharing an electronic key is illustrated. Figure 7 is a flow chart illustrating a method of sharing an electronic key according to some embodiments. FIG. 6A to FIG. 6R The user interface in is used to illustrate the processes described below, which include Figure 7 process. FIG. 8A to FIG. 8L An exemplary user interface for re-sharing a shared electronic key is illustrated. Fig. 9 is a flow chart illustrating a method of re-sharing a shared electronic key according to some embodiments. FIG. 8A to FIG. 8L The user interface in is used to illustrate the process described below, including Fig. 9 process.

[0038] The processes described below enhance the operability of the device and make the user-device interface more efficient through various techniques (e.g., by helping the user provide appropriate input and reducing user errors when operating / interacting with the device), 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 displayed controls, performing an operation without further user input when a set of conditions have been met, improving the security of shared electronic keys, improving how multiple devices share access to physical locations, and / or other 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.

[0039] 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.

[0040] Although the following description uses the terms "first", "second", etc. to describe various elements, these elements should not be limited by the terms. In some embodiments, these terms are used to distinguish one element from another element. For example, a first touch can be named a second touch and similarly a second touch can be named a first touch without departing from the scope of the various described embodiments. In some embodiments, the first touch and the second touch are two separate references to the same touch. In some embodiments, both the first touch and the second touch are touches, but they are not the same touch.

[0041] The terms used in the description of various described embodiments herein are only for the purpose of describing specific embodiments, and are not intended to be limited. As used in the description of various described embodiments and in the appended claims, the singular forms "one" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the term "and / or" used herein refers to and encompasses any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "including" and / or "comprising" when used in this specification specify the presence of stated features, integers, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or their grouping.

[0042] The term "if" is optionally interpreted to mean "when," "upon," or "in response to determining," or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that ..." or "if [a stated condition or event] is detected" are optionally interpreted to mean "upon determining that ..." or "in response to determining that ..." or "upon detecting [a stated condition or event]," or "in response to detecting [a stated condition or event]," depending on the context.

[0043] Embodiments of electronic devices, user interfaces for such devices, and associated processes for using such devices are described herein. In some embodiments, the device is a portable communication device, such as a mobile phone, that also includes other functions, such as a PDA and / or a music player function. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). Devices, iPod Equipment and Device. Optionally use other portable electronic devices, such as laptop computers or tablet computers with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads). It should also be understood that in some embodiments, the device is not a portable communication device, but a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads). In some embodiments, the electronic device is a computer system that communicates with the display generation component (e.g., via wireless communication, via wired communication). The display generation component is configured to provide visual output, such as display via a CRT display, display via an LED display, or display via image projection. In some embodiments, the display generation component is integrated with the computer system. In some embodiments, the display generation component is separated from the computer system. As used herein, "display" content includes transmitting data (e.g., image data or video data) to an integrated or external display generation component via a wired or wireless connection to visually generate content to display content (e.g., video data rendered or decoded by display controller 156).

[0044] In the following discussion, an electronic device including a display and a touch-sensitive surface is described. However, it should be understood that the electronic device optionally includes one or more other physical user interface devices, such as a physical keyboard, mouse and / or joystick.

[0045] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a presentation application, a word processing application, a website creation application, a disk editing application, a spreadsheet application, a gaming application, a telephony application, a video conferencing application, an email application, an instant messaging application, a fitness support application, a photo management application, a digital camera application, a digital video camera application, a web browsing application, a digital music player application, and / or a digital video player application.

[0046] Various applications executed on the device optionally use at least one common physical user interface device, such as a touch-sensitive surface. One or more functions of the touch-sensitive surface and corresponding information displayed on the device are optionally adjusted and / or varied for different applications, and / or adjusted and / or varied within the respective applications. In this way, the common physical architecture of the device (such as a touch-sensitive surface) optionally supports various applications with a user interface that is intuitive and clear to the user.

[0047] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A1 is a block diagram illustrating a portable multifunction device 100 with a touch-sensitive display system 112 according to some embodiments. The touch-sensitive display 112 is sometimes referred to as a "touch screen" for convenience, and is sometimes referred to as or referred to as a "touch-sensitive display system." The device 100 includes a memory 102 (which optionally includes one or more computer-readable storage media), a memory controller 122, one or more processing units (CPUs) 120, a peripheral device interface 118, an RF circuit 108, an audio circuit 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input control devices 116, and an external port 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more contact force sensors 165 for detecting the intensity of contact on the device 100 (e.g., a touch-sensitive surface, such as the touch-sensitive display system 112 of the device 100). Device 100 optionally includes one or more tactile output generators 167 for generating tactile output on device 100 (e.g., generating tactile output on a touch-sensitive surface such as touch-sensitive display system 112 of device 100 or touch pad 355 of device 300). These components optionally communicate via one or more communication buses or signal lines 103.

[0048] As used in this specification and claims, the term "intensity" of a contact on a touch-sensitive surface refers to the force or pressure (force per unit area) of a contact (e.g., a finger contact) on the touch-sensitive surface, or to a surrogate (surrogate) of the force or pressure of a contact on the touch-sensitive surface. The intensity of a contact has a range of values ​​that includes at least four different values ​​and more typically includes hundreds of different values ​​(e.g., at least 256). The intensity of a contact is optionally determined (or measured) using various methods and various sensors or combinations of sensors. For example, one or more force sensors below or adjacent to the touch-sensitive surface are optionally used to measure the force at different points on the touch-sensitive surface. In some implementations, force measurements from multiple force sensors are combined (e.g., weighted average) to determine an estimated contact force. Similarly, the pressure-sensitive tip of a stylus is optionally used to determine the pressure of the stylus on the touch-sensitive surface. Alternatively, the size of the contact area detected on the touch-sensitive surface and / or its change, the capacitance of the touch-sensitive surface near the contact and / or its change, and / or the resistance of the touch-sensitive surface near the contact and / or its change are optionally used as a substitute for the force or pressure of the contact on the touch-sensitive surface. In some embodiments, the substitute measurement of the contact force or pressure is used directly to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is described in units corresponding to the substitute measurement). In some embodiments, the substitute measurement of the contact force or pressure is converted into an estimated force or pressure, and the estimated force or pressure is used to determine whether the intensity threshold has been exceeded (e.g., the intensity threshold is a pressure threshold measured in units of pressure). Using the intensity of the contact as an attribute of the user input allows the user to access additional device functions that would otherwise be inaccessible to the user on a smaller device with limited real estate, which is used to display an enable indication (e.g., on a touch-sensitive display) and / or receive user input (e.g., via a touch-sensitive display, touch-sensitive surface, or physical / mechanical controls, such as knobs or buttons).

[0049] As used in this specification and claims, the term "tactile output" refers to a physical displacement of a device relative to a previous position of the device, a physical displacement of a component of the device (e.g., a touch-sensitive surface) relative to another component of the device (e.g., a housing), or a displacement of a component relative to the center of mass of the device, which will be detected by a user using the user's sense of touch. For example, in the case where a device or a component of the device is in contact with a user's touch-sensitive surface (e.g., a finger, palm, or other part of the user's hand), the tactile output generated by the physical displacement will be interpreted by the user as a tactile sensation corresponding to a perceived change in the physical properties of the device or component of the device. For example, movement of a touch-sensitive surface (e.g., a touch-sensitive display or trackpad) is optionally interpreted by the user as a "press click" or "release click" to a physical actuation button. In some cases, the user will feel a tactile sensation, such as a "press click" or "release click", even when the physical actuation button associated with the touch-sensitive surface that is physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when there is no change in the smoothness of the touch-sensitive surface, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. Although such a user's interpretation of touch will be limited by the user's individualized sensory perceptions, many sensory perceptions of touch are common to most users. Therefore, when a tactile output is described as corresponding to a particular sensory perception of a user (e.g., "press click," "release click," "roughness"), unless otherwise stated, the generated tactile output corresponds to a physical displacement of the device or a component thereof that would generate that sensory perception for a typical (or average) user.

[0050] It should be understood that device 100 is merely one example of a portable multifunction device, and that device 100 optionally has more or fewer components than shown, optionally combines two or more components, or optionally has a different configuration or arrangement of the components. Figure 1A The various components shown are implemented in hardware, software, or a combination of both hardware and software, including one or more signal processing and / or application specific integrated circuits.

[0051] Memory 102 optionally includes high-speed random access memory, and optionally also includes non-volatile memory, such as one or more disk storage devices, flash memory devices or other non-volatile solid-state memory devices. Memory controller 122 optionally controls other components of device 100 to access memory 102.

[0052] The peripheral device interface 118 can be used to couple the input peripheral devices and output peripheral devices of the device to the CPU 120 and the memory 102. The one or more processors 120 run or execute various software programs (such as computer programs (e.g., including instructions)) and / or instruction sets stored in the memory 102 to perform various functions of the device 100 and process data. In some embodiments, the peripheral device interface 118, the CPU 120, and the memory controller 122 are optionally implemented on a single chip such as the chip 104. In some other embodiments, they are optionally implemented on separate chips.

[0053] RF (radio frequency) circuit 108 receives and sends RF signals, also referred to as electromagnetic signals. RF circuit 108 converts electrical signals into / converts electromagnetic signals into electrical signals, and communicates with communication networks and other communication devices via electromagnetic signals. RF circuit 108 optionally includes well-known circuits for performing these functions, including but not limited to antenna systems, RF transceivers, one or more amplifiers, tuners, one or more oscillators, digital signal processors, codec chipsets, user identity modules (SIM) cards, memories, and the like. RF circuit 108 optionally communicates with networks and other devices via wireless communications, such as the Internet (also referred to as the World Wide Web (WWW)), intranets, and / or wireless networks (such as cellular telephone networks, wireless local area networks (LANs), and / or metropolitan area networks (MANs)). RF circuit 108 optionally includes well-known circuits for detecting near field communications (NFC) fields, such as through short-range communication radio components. Wireless communication optionally uses any of a variety of communication standards, protocols and technologies, including, but not limited to, Global System for Mobile Communications (GSM), Enhanced Data GSM Environment (EDGE), High Speed ​​Downlink Packet Access (HSDPA), High Speed ​​Uplink Packet Access (HSUPA), Evolution, Data-Only (EV-DO), HSPA, HSPA+, Dual Cell HSPA (DC-HSPDA), Long Term Evolution (LTE), Near Field Communication (NFC), Wideband Code Division Multiple Access (W-CDMA), Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11d), IEEE 802.11e, IEEE 802.11f, IEEE 802.11g, IEEE 802.11g). 11n and / or IEEE 802.11ac), Voice over Internet Protocol (VoIP), Wi-MAX, email protocols (e.g., Internet Message Access Protocol (IMAP) and / or Post Office Protocol (POP)), instant messaging (e.g., Extensible Messaging and Presence Protocol (XMPP), Session Initiation Protocol for Instant Messaging and Presence Utilizing Extensions (SIMPLE), Instant Messaging and Presence Service (IMPS)) and / or Short Message Service (SMS), or any other suitable communication protocol including communication protocols that have not been developed as of the filing date of this document.

[0054] The audio circuit 110, speaker 111, and microphone 113 provide an audio interface between a user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into electrical signals, and transmits the electrical signals to the speaker 111. The speaker 111 converts the electrical signals into sound waves audible to humans. The audio circuit 110 also receives electrical signals converted from sound waves by the microphone 113. The audio circuit 110 converts the electrical signals into audio data and transmits the audio data to the peripheral device interface 118 for processing. The audio data is optionally retrieved from and / or transmitted to the memory 102 and / or the RF circuit 108 by the peripheral device interface 118. In some embodiments, the audio circuit 110 also includes a headset jack (e.g., Figure 2 The headset jack provides an interface between the audio circuit 110 and a removable audio input / output peripheral device, such as an output-only headset or a headset having both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).

[0055] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch screen 112 and other input control devices 116, to a peripheral device interface 118. The I / O subsystem 106 optionally includes a display controller 156, an optical sensor controller 158, a depth camera controller 169, an intensity sensor controller 159, a tactile feedback controller 161, and one or more input controllers 160 for other input or control devices. The one or more input controllers 160 receive / send electrical signals from other input control devices 116. The other input control devices 116 optionally include physical buttons (e.g., push buttons, rocker buttons, etc.), dials, slide switches, joysticks, click wheels, etc. In some embodiments, the input controller 160 is optionally coupled to any of the following (or none of the following): a keyboard, an infrared port, a USB port, and a pointing device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes an increase / decrease button for volume control of the speaker 111 and / or the microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2206 in). In some embodiments, the electronic device is a computer system that communicates with one or more input devices (e.g., via wireless communication, via wired communication). In some embodiments, the one or more input devices include a touch-sensitive surface (e.g., a touchpad as part of a touch-sensitive display). In some embodiments, the one or more input devices include one or more camera sensors (e.g., one or more optical sensors 164 and / or one or more depth camera sensors 175), such as for tracking a user's gestures (e.g., hand gestures and / or air gestures) as input. In some embodiments, the one or more input devices are integrated with the computer system. In some embodiments, the one or more input devices are separate from the computer system. In some embodiments, an air gesture is a gesture that is detected without the user touching an input element that is part of the device (or is independent of an input element that is part of the device) and is 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 (for example, 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 (for example, 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 (for example, a tap gesture involving a hand moving a predetermined amount and / or speed in a predetermined position, or a shake gesture involving a predetermined speed or amount of rotation of a part of the user's body).

[0056] A quick press of the push button optionally disengages the lock of the touch screen 112 or optionally begins the process of unlocking the device using gestures on the touch screen, as described in U.S. Patent Application 11 / 322,549, filed on December 23, 2005, entitled "Unlocking a Device by Performing Gestures on an Unlock Image" (i.e., U.S. Patent No. 7,657,849), which is hereby incorporated by reference in its entirety. A long press of the push button (e.g., 206) optionally turns the device 100 on or off. The functions of one or more buttons are optionally user-customizable. The touch screen 112 is used to implement virtual buttons or soft buttons and one or more soft keyboards.

[0057] The touch-sensitive display 112 provides an input interface and an output interface between the device and the user. The display controller 156 receives electrical signals from the touch screen 112 and / or sends electrical signals to the touch screen. The touch screen 112 displays visual output to the user. The visual output optionally includes graphics, text, icons, videos, and any combination thereof (collectively referred to as "graphics"). In some embodiments, some or all of the visual output optionally corresponds to user interface objects.

[0058] The touch screen 112 has a touch-sensitive surface, sensor, or sensor group that accepts input from a user based on tactile and / or haptic contact. The touch screen 112 and display controller 156 (together with any associated modules and / or instruction sets in memory 102) detect contact (and any movement or interruption of the contact) on the touch screen 112 and convert the detected contact into interaction with a user interface object (e.g., one or more soft keys, icons, web pages, or images) displayed on the touch screen 112. In an exemplary embodiment, the point of contact between the touch screen 112 and the user corresponds to the user's finger.

[0059] The touch screen 112 optionally uses LCD (liquid crystal display) technology, LPD (light emitting polymer display) technology, or LED (light emitting diode) technology, although other display technologies are used in other embodiments. The touch screen 112 and display controller 156 optionally use any of a variety of touch sensing technologies now known or later developed, including but not limited to capacitive, resistive, infrared, and surface acoustic wave technologies, as well as other proximity sensor arrays or other elements for determining one or more points of contact with the touch screen 112 to detect contact and any movement or interruption thereof. In an exemplary embodiment, projected mutual capacitance sensing technology is used, such as in the Apple ® from Apple Inc. (Cupertino, California). and iPod The technology used in.

[0060] The touch-sensitive display in some embodiments of touch screen 112 is optionally similar to the multi-touch-sensitive touchpad described in the following U.S. Patents: 6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and / or 6,677,932 (Westerman et al.), and / or U.S. Patent Publication 2002 / 0015024A1, each of which is hereby incorporated by reference in its entirety. However, touch screen 112 displays visual output from device 100, while a touch-sensitive touchpad does not provide visual output.

[0061] The touch-sensitive display in some embodiments of the touch screen 112 is described in the following applications: (1) U.S. patent application No. 11 / 381,313, filed on May 2, 2006, "Multipoint Touch Surface Controller"; (2) U.S. patent application No. 10 / 840,862, filed on May 6, 2004, "Multipoint Touchscreen"; (3) U.S. patent application No. 10 / 903,964, filed on July 30, 2004, "Gestures For Touch Sensitive Input Devices"; (4) U.S. patent application No. 11 / 048,264, filed on January 31, 2005, "Gestures For Touch Sensitive Input Devices"; (5) U.S. patent application No. 11 / 038,590, filed on January 18, 2005, "Mode-Based Graphical User Interfaces For Touch Sensitive Input Devices”; (6) U.S. patent application Ser. No. 11 / 228,758, filed on September 16, 2005, “Virtual Input Device Placement On A Touch Screen User Interface”; (7) U.S. patent application Ser. No. 11 / 228,700, filed on September 16, 2005, “Operation Of A Computer With A Touch Screen Interface”; (8) U.S. patent application Ser. No. 11 / 228,737, filed on September 16, 2005, “Activating Virtual Keys Of A Touch-Screen Virtual Keyboard”; and (9) U.S. patent application Ser. No. 11 / 367,749, filed on March 3, 2006, “Multi-Functional Hand-Held Device”. All of these applications are incorporated herein by reference in their entirety.

[0062] The touch screen 112 optionally has a video resolution of more than 100 dpi. In some embodiments, the touch screen has a video resolution of about 160 dpi. The user optionally uses any suitable object or attachment such as a stylus, a finger, etc. to contact the touch screen 112. In some embodiments, the user interface is designed to work primarily through finger-based contacts and gestures, which may not be as accurate as stylus-based input due to the larger contact area of ​​the finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positioning or commands for performing the actions desired by the user.

[0063] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touchpad for activating or deactivating specific functions. In some embodiments, the touchpad is a touch-sensitive area of ​​the device that, unlike the touch screen, does not display visual output. The touchpad is optionally a touch-sensitive surface separate from the touch screen 112, or an extension of the touch-sensitive surface formed by the touch screen.

[0064] Device 100 also includes a power system 162 for powering the various components. Power system 162 optionally includes a power management system, one or more power sources (e.g., batteries, alternating current (AC)), a recharging system, power fault detection circuits, power converters or inverters, power status indicators (e.g., light emitting diodes (LEDs)), and any other components associated with the generation, management, and distribution of power in a portable device.

[0065] Device 100 optionally also includes one or more optical sensors 164 . Figure 1AAn optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. The optical sensor 164 optionally includes a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The optical sensor 164 receives light projected through one or more lenses from the environment and converts the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the optical sensor 164 optionally captures a static image or video. In some embodiments, the optical sensor is located on the rear of the device 100, opposite to the touch screen display 112 on the front of the device, so that the touch screen display can be used as a viewfinder for static images and / or video image acquisition. In some embodiments, the optical sensor is located on the front of the device so that when the user views other video conference participants on the touch screen display, the image of the user is optionally obtained for video conferencing. In some embodiments, the positioning of the optical sensor 164 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that a single optical sensor 164 is used with the touch screen display for both video conferencing and static image and / or video image acquisition.

[0066] Device 100 optionally also includes one or more depth camera sensors 175 . Figure 1A A depth camera sensor coupled to a depth camera controller 169 in the I / O subsystem 106 is shown. The depth camera sensor 175 receives data from the environment to create a three-dimensional model of an object (e.g., a face) within the scene from a viewpoint (e.g., a depth camera sensor). In some embodiments, in conjunction with the imaging module 143 (also referred to as a camera module), the depth camera sensor 175 is optionally used to determine a depth map of different portions of an image captured by the imaging module 143. In some embodiments, the depth camera sensor is located at the front of the device 100, so that an image of the user with depth information is optionally obtained for video conferencing while the user is viewing other video conference participants on the touch screen display, and a selfie with depth map data is captured. In some embodiments, the depth camera sensor 175 is located at the rear of the device, or at both the rear and front of the device 100. In some embodiments, the positioning of the depth camera sensor 175 can be changed by the user (e.g., by rotating the lens and sensor in the device housing) so that the depth camera sensor 175 is used with the touch screen display for both video conferencing and still image and / or video image acquisition.

[0067] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1AA contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. Contact force sensor 165 optionally includes one or more piezoresistive strain gauges, capacitive force sensors, electrical force sensors, piezoelectric force sensors, optical force sensors, capacitive touch-sensitive surfaces, or other force sensors (e.g., sensors for measuring the force (or pressure) of contact on a touch-sensitive surface). Contact force sensor 165 receives contact force information (e.g., pressure information or a surrogate for pressure information) from the environment. In some embodiments, at least one contact force sensor is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112). In some embodiments, at least one contact force sensor is located on the back of device 100, opposite to touch screen display 112 located on the front of device 100.

[0068] Device 100 optionally also includes one or more proximity sensors 166 . Figure 1A A proximity sensor 166 is shown coupled to the peripherals interface 118. Alternatively, the proximity sensor 166 is optionally coupled to the input controller 160 in the I / O subsystem 106. The proximity sensor 166 is optionally implemented as described in the following U.S. patent application numbers: 11 / 241,839, entitled "Proximity Detector In Handheld Device"; 11 / 240,788, entitled "Proximity Detector In Handheld Device"; 11 / 620,702, entitled "Using Ambient Light Sensor To Augment Proximity Sensor Output"; 11 / 586,862, entitled "Automated Response To And Sensing Of User Activity In Portable Devices"; and 11 / 638,251, entitled "Methods And Systems For Automatic Configuration Of Peripherals", which are hereby incorporated by reference in their entirety. In some embodiments, when the multifunction device is placed near the user's ear (e.g., when the user is on a phone call), the proximity sensor turns off and disables the touch screen 112.

[0069] Device 100 optionally also includes one or more tactile output generators 167 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. The tactile output generator 167 optionally includes one or more electroacoustic devices such as a speaker or other audio component; and / or an electromechanical device for converting energy into linear motion such as a motor, solenoid, electroactive polymer, piezoelectric actuator, electrostatic actuator, or other tactile output generating component (e.g., a component for converting an electrical signal into a tactile output on the device). The contact force sensor 165 receives tactile feedback generation instructions from the tactile feedback module 133 and generates a tactile output on the device 100 that can be felt by a user of the device 100. In some embodiments, at least one tactile output generator is arranged in parallel or adjacent to a touch-sensitive surface (e.g., a touch-sensitive display system 112) and optionally generates a tactile output by moving the touch-sensitive surface vertically (e.g., inward / outward of the surface of the device 100) or laterally (e.g., backward and forward in the same plane as the surface of the device 100). In some embodiments, at least one tactile output generator sensor is located on the back of the device 100, opposite the touch screen display 112 located on the front of the device 100.

[0070] Device 100 optionally also includes one or more accelerometers 168 . Figure 1A An accelerometer 168 is shown coupled to the peripheral device interface 118. Alternatively, the accelerometer 168 is optionally coupled to the input controller 160 in the I / O subsystem 106. The accelerometer 168 is optionally implemented as described in the following U.S. Patent Publication Nos.: 20050190059, entitled "Acceleration-based Theft Detection System for Portable Electronic Devices" and 20060017692, entitled "Methods And Apparatuses For Operating A Portable Device Based On An Accelerometer", both of which are incorporated herein by reference in their entirety. In some embodiments, information is displayed in a portrait view or a landscape view on the touch screen display based on analysis of data received from one or more accelerometers. The device 100 optionally includes a magnetometer and a GPS (or GLONASS or other global navigation system) receiver in addition to the accelerometer 168 for obtaining information about the position and orientation (e.g., portrait or landscape) of the device 100.

[0071] In some embodiments, the software components stored in memory 102 include an operating system 126, a communication module (or instruction set) 128, a contact / motion module (or instruction set) 130, a graphics module (or instruction set) 132, a text input module (or instruction set) 134, a global positioning system (GPS) module (or instruction set) 135, and an application (or instruction set) 136. In addition, in some embodiments, memory 102 ( Figure 1A ) or 370( Figure 3 ) storage device / global internal state 157, such as Figure 1A and Figure 3 . The device / global internal state 157 includes one or more of the following: active application state, which indicates which application (if any) is currently active; display state, which indicates what applications, views, or other information occupy various areas of the touch screen display 112; sensor state, including information obtained from the device's various sensors and input control devices 116; and position information related to the device's position and / or posture.

[0072] The operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS, WINDOWS, or an embedded operating system such as VxWorks) includes various software components and / or drivers for controlling and managing general system tasks (e.g., memory management, storage device control, power management, etc.), and facilitating communication between various hardware components and software components.

[0073] The communication module 128 facilitates communication with other devices through one or more external ports 124, and also includes various software components for processing data received by the RF circuit 108 and / or the external port 124. The external port 124 (e.g., Universal Serial Bus (USB), FireWire, etc.) is suitable for coupling directly to other devices, or indirectly through a network (e.g., the Internet, wireless LAN, etc.). In some embodiments, the external port is connected to (trademark of Apple Inc.) devices.

[0074] The contact / motion module 130 optionally detects contact with the touch screen 112 (in conjunction with the display controller 156) and other touch-sensitive devices (e.g., a touchpad or physical click wheel). The contact / motion module 130 includes various software components for performing various operations related to contact detection, such as determining whether contact has occurred (e.g., detecting a finger press event), determining the contact strength (e.g., the force or pressure of the contact, or a substitute for the force or pressure of the contact), determining whether there is movement of the contact and tracking the movement on the touch-sensitive surface (e.g., detecting one or more finger drag events), and determining whether the contact has stopped (e.g., detecting a finger lift event or contact disconnection). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of the contact point optionally includes determining the rate (magnitude), velocity (magnitude and direction) and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of the contact point being represented by a series of contact data. These operations are optionally applied to a single point of contact (e.g., a single finger contact) or multiple points of simultaneous contact (e.g., "multi-touch" / multiple finger contacts). In some embodiments, the contact / motion module 130 and display controller 156 detect contact on the touch pad.

[0075] In some embodiments, the contact / motion module 130 uses a set of one or more intensity thresholds to determine whether an action has been performed by a user (e.g., to determine whether a user has "clicked" an icon). In some embodiments, at least a subset of the intensity thresholds are determined based on software parameters (e.g., the intensity thresholds are not determined by the activation thresholds of specific physical actuators and can be adjusted without changing the physical hardware of the device 100). For example, without changing the touchpad or touchscreen display hardware, the mouse "click" threshold of a touchpad or touchscreen can be set to any one of a large range of predefined thresholds. Additionally, in some specific implementations, a software setting is provided to the user of the device for adjusting one or more intensity thresholds in a set of intensity thresholds (e.g., by adjusting individual intensity thresholds and / or by utilizing a system-level click on an "intensity" parameter to adjust multiple intensity thresholds at once).

[0076] The contact / motion module 130 optionally detects gesture input by the user. Different gestures on the touch-sensitive surface have different contact patterns (e.g., different motions, timings, and / or intensities of the detected contacts). Therefore, gestures are optionally detected by detecting specific contact patterns. For example, detecting a finger tap gesture includes detecting a finger press event, and then detecting a finger lift (lift-off) event at the same location (or substantially the same location) as the finger press event (e.g., at the location of an icon). As another example, detecting a finger swipe gesture on the touch-sensitive surface includes detecting a finger press event, then detecting one or more finger drag events, and then detecting a finger lift (lift-off) event.

[0077] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch screen 112 or other display, including components for changing the visual impact (e.g., brightness, transparency, saturation, contrast, or other visual attributes) of the displayed graphics. As used herein, the term "graphics" includes any object that can be displayed to a user, including but not limited to text, web pages, icons (such as user interface objects including soft keys), digital images, videos, animations, etc.

[0078] In some embodiments, the graphics module 132 stores data representing graphics to be used. Each graphic is optionally assigned a corresponding code. The graphics module 132 receives one or more codes for specifying the graphics to be displayed from an application or the like, along with coordinate data and other graphic attribute data if necessary, and then generates screen image data to be output to the display controller 156.

[0079] Haptic feedback module 133 includes various software components for generating instructions used by tactile output generator 167 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .

[0080] Text input module 134, which is optionally a component of graphics module 132, provides a soft keyboard for entering text in various applications (e.g., contacts module 137, email client module 140, IM module 141, browser module 147, and any other application requiring text input).

[0081] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone module 138 for use in location-based dialing; to the camera module 143 as picture / video metadata; and to applications that provide location-based services, such as a weather widget, a local yellow pages widget, and a map / navigation widget).

[0082] Application 136 optionally includes the following modules (or instruction sets) or a subset or superset thereof:

[0083] ● Contacts module 137 (sometimes called address book or contact list);

[0084] ● Telephone module 138;

[0085] ● Video conferencing module 139;

[0086] ● Email client module 140;

[0087] ●Instant messaging (IM) module 141;

[0088] ●Fitness support module 142;

[0089] ● Camera module 143 for still images and / or video images;

[0090] ●Image management module 144;

[0091] ●Video player module;

[0092] ●Music player module;

[0093] ●Browser module 147;

[0094] ● Calendar module 148;

[0095] A widget module 149, which optionally includes one or more of the following: a weather widget 149-1, a stock market widget 149-2, a calculator widget 149-3, an alarm widget 149-4, a dictionary widget 149-5, and other widgets acquired by the user, and a user-created widget 149-6;

[0096] A widget creator module 150 for forming a user-created widget 149-6;

[0097] ●Search module 151;

[0098] ● Video and music player module 152, which merges the video player module and the music player module;

[0099] ●Note module 153;

[0100] ● Map module 154; and / or

[0101] ●Online video module 155.

[0102] Examples of other applications 136 optionally stored in memory 102 include other word processing applications, other image editing applications, drawing applications, rendering applications, JAVA-enabled applications, encryption, digital rights management, voice recognition, and voice replication.

[0103] In combination with the touch screen 112, display controller 156, touch / motion module 130, graphics module 132 and text input module 134, the contact module 137 is optionally used to manage an address book or contact list (for example, stored in the application internal state 192 of the contact module 137 in memory 102 or memory 370), including: adding one or more names to the address book; deleting names from the address book; associating telephone numbers, email addresses, physical addresses or other information with names; associating images with names; categorizing and classifying names; providing telephone numbers or email addresses to initiate and / or facilitate communications via the telephone module 138, video conferencing module 139, email client module 140 or IM module 141; and the like.

[0104] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, phone module 138 is optionally used to enter a sequence of characters corresponding to a phone number, access one or more phone numbers in contact module 137, modify an entered phone number, dial a corresponding phone number, conduct a conversation, and disconnect or hang up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.

[0105] In combination with the RF circuit 108, the audio circuit 110, the speaker 111, the microphone 113, the touch screen 112, the display controller 156, the optical sensor 164, the optical sensor controller 158, the contact / motion module 130, the graphics module 132, the text input module 134, the contact module 137 and the telephone module 138, the video conferencing module 139 includes executable instructions for initiating, conducting and terminating a video conference between a user and one or more other participants in accordance with user instructions.

[0106] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, email client module 140 includes executable instructions for creating, sending, receiving, and managing emails in response to user instructions. In conjunction with image management module 144, email client module 140 makes it very easy to create and send emails with still images or video images captured by camera module 143.

[0107] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, instant messaging module 141 includes executable instructions for the following operations: inputting a character sequence corresponding to an instant message, modifying previously input characters, transmitting a corresponding instant message (e.g., using a short message service (SMS) or multimedia message service (MMS) protocol for phone-based instant messaging or using XMPP, SIMPLE, or IMPS for Internet-based instant messaging), receiving instant messages, and viewing received instant messages. In some embodiments, the transmitted and / or received instant messages optionally include graphics, photos, audio files, video files, and / or other attachments supported in MMS and / or enhanced messaging services (EMS). As used herein, "instant messaging" refers to both phone-based messages (e.g., messages sent using SMS or MMS) and Internet-based messages (e.g., messages sent using XMPP, SIMPLE, or IMPS).

[0108] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the contact / motion module 130, the graphics module 132, the text input module 134, the GPS module 135, the map module 154 and the music player module, the fitness support module 142 includes executable instructions for creating a fitness (e.g., with time, distance and / or calorie burn goals); communicating with fitness sensors (sports equipment); receiving fitness sensor data; calibrating sensors for monitoring fitness; selecting and playing music for fitness; and displaying, storing and transmitting fitness data.

[0109] In conjunction with the touch screen 112, display controller 156, optical sensor 164, optical sensor controller 158, contact / motion module 130, graphics module 132 and image management module 144, the camera module 143 includes executable instructions for the following operations: capturing still images or videos (including video streams) and storing them in the memory 102, modifying the characteristics of the still images or videos, or deleting the still images or videos from the memory 102.

[0110] In conjunction with touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134, and camera module 143, image management module 144 includes executable instructions for arranging, modifying (e.g., editing) or otherwise manipulating, labeling, deleting, presenting (e.g., in a digital slideshow or album), and storing still images and / or video images.

[0111] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132 and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet in accordance with user instructions, including searching, linking to, receiving and displaying web pages or portions thereof, as well as attachments and other files linked to web pages.

[0112] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the email client module 140 and the browser module 147, the calendar module 148 includes executable instructions for creating, displaying, modifying and storing calendars and data associated with the calendar (e.g., calendar entries, to-do items, etc.) in accordance with user instructions.

[0113] In conjunction with RF circuit 108, touch screen 112, display controller 156, contact / motion module 130, graphics module 132, text input module 134, and browser module 147, widget module 149 is a mini-application that is optionally downloaded and used by a user (e.g., weather widget 149-1, stock market widget 149-2, calculator widget 149-3, alarm widget 149-4, and dictionary widget 149-5) or a mini-application created by a user (e.g., user-created widget 149-6). In some embodiments, the widget includes an HTML (Hypertext Markup Language) file, a CSS (Cascading Style Sheets) file, and a JavaScript file. In some embodiments, the widget includes an XML (Extensible Markup Language) file and a JavaScript file (e.g., Yahoo! widget).

[0114] In combination with the RF circuit 108, touch screen 112, display controller 156, touch / motion module 130, graphics module 132, text input module 134 and browser module 147, the widget creator module 150 is optionally used by a user to create widgets (e.g., converting a user-specified portion of a web page into a widget).

[0115] In combination with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132 and text input module 134, the search module 151 includes executable instructions for searching the memory 102 for text, music, sound, images, videos and / or other files that match one or more search criteria (e.g., one or more user-specified search terms) in accordance with user instructions.

[0116] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuitry 110, speaker 111, RF circuitry 108, and browser module 147, video and music player module 152 includes executable instructions that allow a user to download and play back recorded music and other sound files stored in one or more file formats, such as MP3 or AAC files, and executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch screen 112 or on an external display connected via external port 124). In some embodiments, device 100 optionally includes the functionality of an MP3 player, such as an iPod (trademark of Apple Inc.).

[0117] In conjunction with the touch screen 112, display controller 156, contact / motion module 130, graphics module 132, and text input module 134, the note module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.

[0118] In combination with the RF circuit 108, the touch screen 112, the display controller 156, the touch / motion module 130, the graphics module 132, the text input module 134, the GPS module 135 and the browser module 147, the map module 154 is optionally used to receive, display, modify and store maps and data associated with the maps (e.g., driving directions, data relating to stores and other points of interest at or near a particular location, and other location-based data) in accordance with user instructions.

[0119] In conjunction with touch screen 112, display controller 156, contact / motion module 130, graphics module 132, audio circuit 110, speaker 111, RF circuit 108, text input module 134, email client module 140, and browser module 147, online video module 155 includes instructions for the following operations: allowing a user to access, browse, receive (e.g., by streaming and / or downloading), playback (e.g., on the touch screen or on an external display connected via external port 124), send an email with a link to a specific online video, and otherwise manage online videos in one or more file formats such as H.264. In some embodiments, instant messaging module 141 is used instead of email client module 140 to send a link to a specific online video. Additional descriptions of online video applications may be found in U.S. Provisional Patent Application No. 60 / 936,562, filed on June 20, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” and U.S. Patent Application No. 11 / 968,067, filed on December 31, 2007, entitled “Portable Multifunction Device, Method, and Graphical User Interface for Playing Online Videos,” the contents of which are hereby incorporated by reference in their entirety.

[0120] Each of the modules and applications described above corresponds to an executable instruction set for performing one or more of the functions described above and the methods described in this patent application (e.g., the computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) do not have to be implemented as independent software programs (such as computer programs (e.g., including instructions)), processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. For example, a video player module is optionally combined with a music player module into a single module (e.g., Figure 1A In some embodiments, the memory 102 optionally stores a subset of the above modules and data structures. In addition, the memory 102 optionally stores additional modules and data structures not described above.

[0121] In some embodiments, the device 100 is a device where the operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touch pad. By using a touch screen and / or a touch pad as the primary input control device for operating the device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on the device 100 is optionally reduced.

[0122] A predefined set of functions that are performed exclusively through the touch screen and / or touchpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 to a main menu, a home menu, or a root menu from any user interface displayed on the device 100. In such embodiments, a "menu button" is implemented using the touchpad. In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.

[0123] Figure 1B is a block diagram illustrating exemplary components for event processing according to some embodiments. In some embodiments, memory 102 ( Figure 1A ) or memory 370( Figure 3 ) includes an event classifier 170 (e.g., in the operating system 126) and a corresponding application 136-1 (e.g., any one of the aforementioned applications 137 to 151, 155, 380 to 390).

[0124] Event classifier 170 receives event information and determines the application 136-1 and the application view 191 of application 136-1 to which the event information is to be delivered. Event classifier 170 includes event monitor 171 and event distributor module 174. In some embodiments, application 136-1 includes application internal state 192, which indicates one or more current application views displayed on touch-sensitive display 112 when the application is active or executing. In some embodiments, device / global internal state 157 is used by event classifier 170 to determine which application(s) is currently active, and application internal state 192 is used by event classifier 170 to determine the application view 191 to which the event information is to be delivered.

[0125] In some embodiments, the application internal state 192 includes additional information, such as one or more of the following: resumption information to be used when application 136-1 resumes execution, user interface state information indicating that information is being displayed or is ready to be displayed by application 136-1, a state queue for enabling a user to return to a previous state or view of application 136-1, and a repeat / undo queue of previous actions taken by the user.

[0126] Event monitor 171 receives event information from peripherals interface 118. Event information includes information about sub-events (e.g., user touches on touch-sensitive display 112 as part of a multi-touch gesture). Peripherals interface 118 transmits information it receives from I / O subsystem 106 or sensors such as proximity sensor 166, one or more accelerometers 168, and / or microphone 113 (through audio circuit 110). The information that peripherals interface 118 receives from I / O subsystem 106 includes information from touch-sensitive display 112 or a touch-sensitive surface.

[0127] In some embodiments, event monitor 171 sends requests to peripheral device interface 118 at predetermined intervals. In response, peripheral device interface 118 transmits event information. In other embodiments, peripheral device interface 118 transmits event information only when there is a significant event (e.g., receiving an input above a predetermined noise threshold and / or receiving an input for more than a predetermined duration).

[0128] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.

[0129] When the touch-sensitive display 112 displays more than one view, the hit view determination module 172 provides software procedures for determining where within one or more views a sub-event has occurred. A view consists of controls and other elements that a user can see on the display.

[0130] Another aspect of the user interface associated with an application is a set of views, sometimes also referred to herein as application views or user interface windows, in which information is displayed and touch-based gestures occur. The application views (of the respective application) in which a touch is detected optionally correspond to a programmatic level within the programmatic or view hierarchy of the application. For example, the lowest level view in which a touch is detected is optionally referred to as a hit view, and the set of events that are identified as correct input is optionally determined at least in part based on the hit view of the initial touch that started the touch-based gesture.

[0131] Hit view determination module 172 receives information related to sub-events of touch-based gestures. When an application has multiple views organized in a hierarchy, hit view determination module 172 identifies the hit view as the lowest view in the hierarchy that should handle the sub-events. In most cases, the hit view is the lowest level view in which the initiating sub-event (e.g., the first sub-event in a sequence of sub-events that form an event or potential event) occurs. Once a hit view is identified by hit view determination module 172, the hit view typically receives all sub-events related to the same touch or input source for which it is identified as the hit view.

[0132] Active event recognizer determination module 173 determines which view or views within the view hierarchy should receive a particular sequence of sub-events. In some embodiments, active event recognizer determination module 173 determines that only the hit view should receive a particular sequence of sub-events. In other embodiments, active event recognizer determination module 173 determines that all views that include the physical location of the sub-event are actively participating views, and therefore determines that all actively participating views should receive a particular sequence of sub-events. In other embodiments, even if a touch sub-event is completely confined to an area associated with one particular view, higher views in the hierarchy will still remain as actively participating views.

[0133] Event distributor module 174 distributes event information to event recognizers (e.g., event recognizers 180). In embodiments including active event recognizer determination module 173, event distributor module 174 delivers the event information to the event recognizers determined by active event recognizer determination module 173. In some embodiments, event distributor module 174 stores the event information in an event queue, which is retrieved by corresponding event receivers 182.

[0134] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In yet another embodiment, event classifier 170 is a standalone module or is part of another module stored in memory 102, such as contact / motion module 130.

[0135] In some embodiments, application 136-1 includes multiple event handlers 190 and one or more application views 191, each of which includes instructions for handling touch events occurring within a corresponding view of the user interface of the application. Each application view 191 of application 136-1 includes one or more event identifiers 180. Typically, the corresponding application view 191 includes multiple event identifiers 180. In other embodiments, one or more event identifiers in event identifiers 180 are part of an independent module, which is a higher-level object such as a user interface toolkit or application 136-1 from which methods and other properties are inherited. In some embodiments, the corresponding event handler 190 includes one or more of the following: data updater 176, object updater 177, GUI updater 178 and / or event data 179 received from event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177 or GUI updater 178 to update application internal state 192. Alternatively, one or more of the application views 191 include one or more corresponding event handlers 190. In addition, in some embodiments, one or more of the data updater 176, the object updater 177, and the GUI updater 178 are included in the corresponding application view 191.

[0136] The corresponding event identifier 180 receives event information (e.g., event data 179) from the event classifier 170 and identifies the event based on the event information. The event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, the event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally includes sub-event delivery instructions).

[0137] Event receiver 182 receives event information from event classifier 170. Event information includes information about sub-events such as touch or touch movement. Depending on the sub-event, the event information also includes additional information, such as the location of the sub-event. When the sub-event involves the movement of the touch, the event information optionally also includes the speed and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another orientation (for example, from a longitudinal orientation to a transverse orientation, or vice versa), and the event information includes corresponding information about the current orientation of the device (also referred to as the device posture).

[0138] Event comparator 184 compares event information with predefined event or sub-event definitions, and determines an event or sub-event based on the comparison, or determines or updates the state of an event or sub-event. In some embodiments, event comparator 184 includes event definition 186. Event definition 186 includes the definition of an event (e.g., a predefined sub-event sequence), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, sub-events in events (e.g., 187-1 and / or 187-2) include, for example, touch start, touch end, touch move, touch cancel, and multi-touch. In one example, the definition of event 1 (187-1) is a double-click on a displayed object. For example, a double-click includes a first touch (touch start) of a predetermined duration on a displayed object, a first lift-off (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on a displayed object, and a second lift-off (touch end) of a predetermined duration. In another example, the definition of event 2 (187-2) is a drag on a displayed object. For example, dragging includes a touch (or contact) of a predetermined duration on a displayed object, movement of the touch on the touch-sensitive display 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.

[0139] In some embodiments, event definition 186 includes a definition of an event for a corresponding user interface object. In some embodiments, event comparator 184 performs a hit test to determine which user interface object is associated with a sub-event. For example, in an application view displaying three user interface objects on touch-sensitive display 112, when a touch is detected on touch-sensitive display 112, event comparator 184 performs a hit test to determine which of the three user interface objects is associated with the touch (sub-event). If each displayed object is associated with a corresponding event handler 190, the event comparator uses the result of the hit test to determine which event handler 190 should be activated. For example, event comparator 184 selects an event handler associated with a sub-event and the object that triggered the hit test.

[0140] In some embodiments, the definition of the corresponding event (187) also includes a delay action that delays the delivery of the event information until it has been determined that the sub-event sequence does or does not correspond to the event type of the event identifier.

[0141] When a corresponding event recognizer 180 determines that a sequence of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters an event impossible, event failed, or event ended state, after which subsequent sub-events of the touch-based gesture are ignored. In this case, other event recognizers (if any) that remain active for the hit view continue to track and process sub-events of the ongoing touch-based gesture.

[0142] In some embodiments, the corresponding event recognizers 180 include metadata 183 with configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery to actively participating event recognizers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event recognizers interact or can interact with each other. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate whether sub-events are delivered to different levels in a view or programmatic hierarchy.

[0143] In some embodiments, when one or more specific sub-events of an event are identified, the corresponding event recognizer 180 activates an event handler 190 associated with the event. In some embodiments, the corresponding event recognizer 180 delivers event information associated with the event to the event handler 190. Activating the event handler 190 is different from sending (and deferred sending) the sub-events to the corresponding hit view. In some embodiments, the event recognizer 180 throws a tag associated with the identified event, and the event handler 190 associated with the tag obtains the tag and executes a predefined process.

[0144] In some embodiments, the event delivery instructions 188 include a sub-event delivery instruction that delivers event information about a sub-event without activating an event handler. Instead, the sub-event delivery instruction delivers the event information to an event handler associated with a sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with an actively participating view receives the event information and executes a predetermined process.

[0145] In some embodiments, data updater 176 creates and updates data used in application 136-1. For example, data updater 176 updates phone numbers used in contact module 137 or stores video files used in video player module. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 177 creates new user interface objects or updates the positioning of user interface objects. GUI updater 178 updates the GUI. For example, GUI updater 178 prepares display information and sends the display information to graphics module 132 for display on a touch-sensitive display.

[0146] In some embodiments, event handler 190 includes or has access to data updater 176, object updater 177, and GUI updater 178. In some embodiments, data updater 176, object updater 177, and GUI updater 178 are included in a single module of the corresponding application 136-1 or application view 191. In other embodiments, they are included in two or more software modules.

[0147] It should be understood that the above discussion of event processing for user touches on a touch-sensitive display also applies to other forms of user input that utilize input devices to operate the multifunction device 100, and not all user input is initiated on the touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or hold; contact movement on a touch pad, such as tapping, dragging, scrolling, etc.; stylus input; movement of the device; verbal commands; detected eye movement; biometric input; and / or any combination thereof are optionally used as input corresponding to sub-events that define the event to be distinguished.

[0148] Figure 2A portable multifunction device 100 with a touch screen 112 according to some embodiments is illustrated. The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment and other embodiments described below, a user can select one or more of these graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figure) or one or more styluses 203 (not drawn to scale in the figure). In some embodiments, when the user interrupts contact with one or more graphics, selection of one or more graphics will occur. In some embodiments, gestures optionally include one or more taps, one or more swipes (from left to right, from right to left, up and / or down) and / or rolling of fingers that have been in contact with the device 100 (from right to left, from left to right, up and / or down). In some specific implementations or in some cases, inadvertent contact with a graphic will not select the graphic. For example, when the gesture corresponding to the selection is a tap, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application.

[0149] The device 100 optionally also includes one or more physical buttons, such as a "home" or menu button 204. As previously described, the menu button 204 is optionally used to navigate to any application 136 in a set of applications that are optionally executed on the device 100. Alternatively, in some embodiments, the menu button is implemented as a soft key in a GUI displayed on the touch screen 112.

[0150] In some embodiments, the device 100 includes a touch screen 112, a menu button 204, a push button 206 for turning the device on / off and for locking the device, one or more volume adjustment buttons 208, a user identity module (SIM) card slot 210, an earphone jack 212, and a docking / charging external port 124. The push button 206 is optionally used to turn the device on / off by pressing the button and keeping the button in a pressed state for a predefined time interval; lock the device by pressing the button and releasing the button before the predefined time interval passes; and / or unlock the device or initiate an unlocking process. In an alternative embodiment, the device 100 also accepts voice input for activating or deactivating certain functions through a microphone 113. The device 100 also optionally includes one or more contact strength sensors 165 for detecting the strength of contact on the touch screen 112, and / or one or more tactile output generators 167 for generating tactile output for a user of the device 100.

[0151] Figure 3300 is a block diagram of an exemplary multi-function device with a display and a touch-sensitive surface according to some embodiments. Device 300 does not have to be portable. In some embodiments, device 300 is a laptop computer, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a game system, or a control device (e.g., a home controller or an industrial controller). Device 300 typically includes one or more processing units (CPUs) 310, one or more network or other communication interfaces 360, a memory 370, and one or more communication buses 320 for interconnecting these components. The communication bus 320 optionally includes circuits (sometimes referred to as a chipset) that interconnect system components and control communications between system components. Device 300 includes an input / output (I / O) interface 330 with a display 340, which is typically a touch screen display. The I / O interface 330 also optionally includes a keyboard and / or a mouse (or other pointing device) 350 and a touchpad 355, a tactile output generator 357 for generating tactile output on the device 300 (e.g., similar to the above reference 300). Figure 1A The tactile output generator 167 described above), the sensor 359 (e.g., an optical sensor, an acceleration sensor, a proximity sensor, a touch sensitive sensor, and / or a contact intensity sensor (similar to the above reference Figure 1A Memory 370 optionally includes one or more storage devices located away from CPU 310. In some embodiments, memory 370 stores data related to portable multifunction device 100 ( Figure 1A ) or a subset thereof. In addition, memory 370 optionally stores additional programs, modules, and data structures not present in memory 102 of portable multifunction device 100. For example, memory 370 of device 300 optionally stores a drawing module 380, a presentation module 382, ​​a word processing module 384, a website creation module 386, a disk editing module 388, and / or a spreadsheet module 390, while portable multifunction device 100 ( Figure 1A )'s memory 102 optionally does not store these modules.

[0152] Figure 3Each element in the above-mentioned elements in is optionally stored in one or more memory devices of the previously mentioned memory device. Each module in the above-mentioned modules corresponds to the instruction set for performing the function described above. The above-mentioned modules or computer programs (for example, instruction sets or including instructions) do not have to be realized with independent software programs (such as computer programs (for example, including instructions)), processes or modules, and therefore the various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 370 optionally stores the subset of the above-mentioned modules and data structures. In addition, memory 370 optionally stores additional modules and data structures not described above.

[0153] Attention is now turned to an embodiment of a user interface that is optionally implemented on, for example, portable multifunction device 100.

[0154] Figure 4A An exemplary user interface of an application menu on portable multifunction device 100 according to some embodiments is illustrated. A similar user interface is optionally implemented on device 300. In some embodiments, user interface 400 includes the following elements, or a subset or superset thereof:

[0155] ● Signal strength indicators 402 for wireless communications such as cellular signals and Wi-Fi signals;

[0156] ●Time 404;

[0157] ●Bluetooth indicator 405;

[0158] ●Battery status indicator 406;

[0159] A tray 408 with icons for commonly used applications, such as:

[0160] o an icon 416 of the phone module 138 labeled “Phone”, which optionally includes an indicator 414 of the number of missed calls or voicemails;

[0161] o an icon 418 of the email client module 140 labeled “Mail”, which optionally includes an indicator 410 of the number of unread emails;

[0162] o an icon 420 labeled "Browser" of the browser module 147; and

[0163] o an icon 422 labeled “iPod” of a video and music player module 152 (also referred to as an iPod (trademark of Apple Inc.) module 152); and

[0164] ● Icons for other apps, such as:

[0165] o Icon 424 labeled “Messages” of IM module 141;

[0166] o Icon 426 labeled “Calendar” of calendar module 148;

[0167] o Icon 428 labeled “Photos” of the image management module 144;

[0168] o Icon 430 labeled “Camera” of camera module 143;

[0169] o Icon 432 labeled “Online Video” of the online video module 155;

[0170] o Icon 434 labeled “Stock Market” of the stock market widget 149 - 2 ;

[0171] o an icon 436 labeled “MAP” of the map module 154;

[0172] o Icon 438 labeled “Weather” of the weather widget 149 - 1 ;

[0173] o Icon 440 labeled “Clock” of the alarm clock widget 149 - 4 ;

[0174] o an icon 442 labeled “Fitness Support” of the fitness support module 142;

[0175] o an icon 444 labeled "Notes" of the notes module 153; and

[0176] o An icon 446 of a settings application or module labeled “Settings” that provides access to settings for the device 100 and its various applications 136 .

[0177] It should be noted that Figure 4A The illustrated icon labels are exemplary only. For example, the icon 422 of the video and music player module 152 is labeled "Music" or "Music Player". Other labels are optionally used for various application icons. In some embodiments, the label of the corresponding application icon includes the name of the application corresponding to the corresponding application icon. In some embodiments, the label of a particular application icon is different from the name of the application corresponding to the particular application icon.

[0178] Figure 4B The example embodiment has a touch-sensitive surface 451 (eg, touch screen display 112) that is separate from a display 450 (eg, touch screen display 112). Figure 3 tablet computer or touch pad 355) device (e.g., Figure 3Device 300 also optionally includes one or more contact intensity sensors (e.g., one or more of sensors 359) for detecting intensity of contacts on touch-sensitive surface 451 and / or one or more tactile output generators 357 for generating tactile output for a user of device 300.

[0179] Although some of the examples below are given with reference to input on a touch screen display 112 (where a touch-sensitive surface and a display are combined), in some embodiments, the device detects input on a touch-sensitive surface that is separate from the display, such as Figure 4B In some embodiments, the touch-sensitive surface (e.g., Figure 4B 451) has a main axis (e.g., Figure 4B 453) corresponding to the principal axis (for example, Figure 4B According to these embodiments, the device detects a position corresponding to a corresponding position on the display (e.g., Figure 4B 460 corresponds to 468 and 462 corresponds to 470) in contact with touch-sensitive surface 451 (e.g., Figure 4B Thus, when the touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is separated, the device is used to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.

[0180] Additionally, although the following examples are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures), it should be understood that in some embodiments, one or more of these finger inputs are replaced by input from another input device (e.g., mouse-based input or stylus input). For example, a swipe gesture is optionally replaced by a mouse click (e.g., instead of contact), followed by movement of the cursor along the path of the swipe (e.g., instead of movement of the contact). As another example, a tap gesture is optionally replaced by a mouse click when the cursor is over the location of the tap gesture (e.g., instead of detecting contact, followed by ceasing to detect contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or a mouse and finger contact are optionally used simultaneously.

[0181] Figure 5AAn exemplary personal electronic device 500 is illustrated. Device 500 includes a body 502. In some embodiments, device 500 may include components related to devices 100 and 300 (e.g., Figures 1A to 4B ) some or all of the features described in the foregoing. In some embodiments, device 500 has a touch-sensitive display screen 504, referred to hereinafter as touch screen 504. Alternatively, or in addition to touch screen 504, device 500 also has a display and a touch-sensitive surface. As with devices 100 and 300, in some embodiments, touch screen 504 (or touch-sensitive surface) optionally includes one or more intensity sensors for detecting the intensity of contact (e.g., touch) applied. One or more intensity sensors of touch screen 504 (or touch-sensitive surface) can provide output data representing the intensity of touch. The user interface of device 500 can respond to touch based on the intensity of the touch, which means that touches of different intensities can invoke different user interface operations on device 500.

[0182] Exemplary techniques for detecting and processing touch intensity are found, for example, in the following related patent applications: International patent application serial number PCT / US2013 / 040061, entitled “Device, Method, and Graphical User Interface for Displaying User Interface Objects Corresponding to an Application,” filed on May 8, 2013, published as WIPO patent publication number WO / 2013 / 169849; and International patent application serial number PCT / US2013 / 069483, entitled “Device, Method, and Graphical User Interface for Transitioning Between Touch Input to Display Output Relationships,” filed on November 11, 2013, published as WIPO patent publication number WO / 2014 / 105276, each of which is hereby incorporated by reference in its entirety.

[0183] In some embodiments, the device 500 has one or more input mechanisms 506 and 508. The input mechanisms 506 and 508 (if included) can be physical. Examples of physical input mechanisms include push buttons and rotatable mechanisms. In some embodiments, the device 500 has one or more attachment mechanisms. Such attachment mechanisms (if included) can allow the device 500 to be attached to, for example, hats, glasses, earrings, necklaces, shirts, jackets, bracelets, watchbands, bracelets, pants, belts, shoes, wallets, backpacks, etc. These attachment mechanisms allow the user to wear the device 500.

[0184] Figure 5B An exemplary personal electronic device 500 is depicted. In some embodiments, the device 500 may include information about Figure 1A , Figure 1B and Figure 3 Some or all of the components described. Device 500 has a bus 512 that operatively couples an I / O portion 514 to one or more computer processors 516 and a memory 518. I / O portion 514 may be connected to a display 504, which may have a touch-sensitive component 522 and optionally a strength sensor 524 (e.g., a contact strength sensor). In addition, I / O portion 514 may be connected to a communication unit 530 for receiving application and operating system data using Wi-Fi, Bluetooth, near field communication (NFC), cellular and / or other wireless communication technologies. Device 500 may include input mechanisms 506 and / or 508. For example, input mechanism 506 is optionally a rotatable input device or a depressible input device and a rotatable input device. In some examples, input mechanism 508 is optionally a button.

[0185] In some examples, input mechanism 508 is optionally a microphone. Personal electronic device 500 optionally includes various sensors, such as GPS sensor 532, accelerometer 534, orientation sensor 540 (e.g., compass), gyroscope 536, motion sensor 538, and / or combinations thereof, all of which are operably connected to I / O portion 514.

[0186] The memory 518 of the personal electronic device 500 may include one or more non-transitory computer-readable storage media for storing computer-executable instructions that, when executed by one or more computer processors 516, may cause the computer processors to perform the techniques described below, including processes 700 and 900 ( Figure 7 and Fig. 9). Computer-readable storage media can be any medium that can tangibly contain or store computer-executable instructions for use by or in conjunction with instruction execution systems, devices, and apparatuses. In some examples, the storage medium is a transient computer-readable storage medium. In some examples, the storage medium is a non-transitory computer-readable storage medium. Non-transitory computer-readable storage media may include, but are not limited to, magnetic storage devices, optical storage devices, and / or semiconductor storage devices. Examples of such storage devices include magnetic disks, optical disks based on CD, DVD, or Blu-ray technology, and persistent solid-state memories such as flash memory, solid-state drives, and the like. Personal electronic device 500 is not limited to Figure 5B components and configurations, but may include other components or additional components in a variety of configurations.

[0187] As used herein, the term "indicative representation" refers to an optional feature of the apparatus 100, 300, and / or 500 ( Figure 1A , Figure 3 and FIG. 5A to FIG. 5B ) is a user-interactive graphical user interface object displayed on a display screen of a computer. For example, an image (e.g., an icon), a button, and text (e.g., a hyperlink) optionally each constitute an affordance.

[0188] As used herein, the term "focus selector" refers to an input element used to indicate the current portion of a user interface that a user is interacting with. In some implementations that include a cursor or other position marker, the cursor acts as a "focus selector" such that when the cursor is over a particular user interface element (e.g., a button, window, slider, or other user interface element), a focus selector is displayed on a touch-sensitive surface (e.g., Figure 3 Touchpad 355 or Figure 4B In the event that an input (e.g., a press input) is detected on the touch-sensitive surface 451 in the display, the particular user interface element is adjusted according to the detected input. In the case that a touch-screen display (e.g., Figure 1A A touch-sensitive display system 112 or Figure 4AIn some implementations of the touch screen 112 in FIG. 1 , a contact detected on the touch screen acts as a “focus selector” such that when an input (e.g., a press input by the contact) is detected at the location of a particular user interface element (e.g., a button, window, slider, or other user interface element) on the touch screen display, the particular user interface element is adjusted in accordance with the detected input. In some implementations, the focus moves from one area of ​​the user interface to another area of ​​the user interface without corresponding movement of a cursor or movement of a contact on the touch screen display (e.g., by using a tab key or arrow keys to move the focus from one button to another); in these implementations, the focus selector moves in accordance with the movement of the focus between different areas of the user interface. Regardless of the specific form the focus selector takes, the focus selector is typically a user interface element (or contact on the touch screen display) that is controlled by the user to deliver the user's intended interaction with the user interface (e.g., by indicating to the device the element of the user interface with which the user desires to interact). For example, when a press input is detected on a touch-sensitive surface (e.g., a touchpad or touchscreen), the position of a focus selector (e.g., a cursor, contact, or selection box) over a corresponding button will indicate that the user intends to activate the corresponding button (rather than other user interface elements shown on the device display).

[0189] As used in the specification and claims, the term "characteristic intensity" of a contact refers to a characteristic of a contact based on one or more intensities of the contact. In some embodiments, the characteristic intensity is based on multiple intensity samples. The characteristic intensity is optionally based on a predefined number of intensity samples or a set of intensity samples collected during a predetermined time period (e.g., 0.05 seconds, 0.1 seconds, 0.2 seconds, 0.5 seconds, 1 second, 2 seconds, 5 seconds, 10 seconds) relative to a predefined event (e.g., after contact is detected, before contact is detected to be lifted off, before or after contact starts to move, before contact ends, before or after contact intensity is detected to increase, and / or before or after contact intensity is detected to decrease). The characteristic intensity of a contact is optionally based on one or more of the following: the maximum value of the intensity of the contact, the mean value of the intensity of the contact, the average value of the intensity of the contact, the value at the top 10% of the intensity of the contact, the half-maximum value of the intensity of the contact, the 90% maximum value of the intensity of the contact, etc. In some embodiments, the duration of the contact is used when determining the characteristic intensity (e.g., when the characteristic intensity is the average value of the intensity of the contact over time). In some embodiments, the feature strength is compared to a set of one or more strength thresholds to determine whether the user has performed an operation. For example, the set of one or more strength thresholds optionally includes a first strength threshold and a second strength threshold. In this example, a contact whose feature strength does not exceed the first threshold results in a first operation, a contact whose feature strength exceeds the first strength threshold but does not exceed the second strength threshold results in a second operation, and a contact whose feature strength exceeds the second threshold results in a third operation. In some embodiments, a comparison between the feature strength and one or more thresholds is used to determine whether to perform one or more operations (e.g., whether to perform the corresponding operation or to abandon the corresponding operation) rather than to determine whether to perform the first operation or the second operation.

[0190] Figure 5C An exemplary device connected via one or more communication channels to participate in a transaction according to some embodiments is shown. One or more exemplary electronic devices (e.g., devices 100, 300, and 500) are configured to optionally detect input (e.g., specific user input, NFC field), and optionally transmit credential information (e.g., payment information and / or physical location unlocking information to unlock a physical lock) (e.g., using NFC). The one or more electronic devices optionally include NFC hardware and are configured to support NFC.

[0191] The electronic device (e.g., device 100, 300, and 500) is optionally configured to store payment account information associated with each payment account in one or more payment accounts and / or store electronic key information associated with each electronic key account in one or more electronic key 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, phone 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 card number, debit card number, account number or gift 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 the user device's account has previously made purchases or for which payment account data is identified. The electronic key information includes, for example, access rights (e.g., to unlock or otherwise access a physical location).

[0192] In some embodiments, a payment account is added to an electronic device (e.g., devices 100, 300, and 500) 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 information of the payment account to a transaction coordination server, which then communicates with a server (e.g., a payment server) operated by the payment network of the account to ensure the validity of the information. The electronic device is optionally configured to receive a script from a server that allows the electronic device to program the payment information of the account onto a security element. In some embodiments, an electronic key account is added to an electronic device (e.g., devices 100, 300, and 500) so that the electronic key account information is securely stored on the electronic device, such as a security element of the electronic device.

[0193] In some embodiments, the communication between the electronic devices 100, 300 and 500 facilitates transactions (e.g., general transactions or specific transactions). For example, the first electronic device (e.g., 100) can be used as a supply device or a management device, and can send new or updated account data (e.g., information of new accounts, updated information of existing accounts, and / or warnings about existing accounts) to the second electronic device (e.g., 500). In another example, the first electronic device (e.g., 100) can send data to the second electronic device, wherein the data reflects information about the transaction facilitated at the first electronic device. The information optionally includes one or more of the following: access information, location information, electronic key usage information, payment amount, account used, purchase time, and whether to change the default account. The second device (e.g., 500) optionally uses such information to update the default account (e.g., based on a learning algorithm or explicit user input).

[0194] Electronic devices (e.g., 100, 300, 500) are configured to communicate with each other via any of a variety of networks. For example, the devices communicate using a Bluetooth connection 558 (e.g., including a traditional Bluetooth connection or a Bluetooth low energy connection) or using a WiFi network 556. Communications between user devices are optionally adjusted to reduce the possibility of improper sharing of information between devices. For example, communication about electronic key information optionally requires that the communication devices be paired (e.g., associated with each other via explicit user interaction) or associated with the same user account.

[0195] In some embodiments, the electronic device (e.g., 100, 300, 500) is used to communicate with a terminal 550 (e.g., a secure access terminal associated with a secure location and / or a point of sale (POS) payment terminal), which optionally supports NFC. The communication is optionally performed using various communication channels and / or technologies. In some embodiments, the electronic device (e.g., 100, 300, 500) uses an NFC channel 560 to communicate with the terminal 550. In some embodiments, the terminal 550 uses a peer-to-peer NFC mode to communicate with the electronic device (e.g., 100, 300, 500). The electronic device (e.g., 100, 300, 500) is optionally configured to transmit a signal to the terminal 550, the signal including electronic key information for accessing a physical location and / or payment information of a payment account (e.g., a default account or an account selected for a particular transaction).

[0196] In some embodiments, continuing the transaction includes transmitting a signal including electronic key information and / or payment information of the account. In some embodiments, continuing the transaction includes reconfiguring the electronic device (e.g., 100, 300, 500) to respond as a contactless payment card (such as an NFC-enabled contactless payment card) and then transmitting the account credentials via NFC to, for example, terminal 550. In some embodiments, after transmitting the account credentials 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).

[0197] In some embodiments, the generation and / or transmission of the signal is controlled by a security element in an electronic device (e.g., 100, 300, 500). Before issuing payment information, the security element optionally requires specific user input. For example, the security element optionally requires: detecting the 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., terminal 550) is established within a defined time period from when the input is detected, the security element releases electronic key information and / or payment information so that it is transmitted to another device (e.g., terminal 550). 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.

[0198] 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 500) and a phone (e.g., device 100). For example, a generation condition and / or a transmission condition for a wearable device includes detecting that a button has been pressed (e.g., after security verification), while a corresponding condition for a phone does not require a button press, but requires detection of a specific interaction with an application. In some embodiments, conditions for transmitting and / or publishing payment information include receiving specific input on each of a plurality of devices. For example, the release of payment information optionally requires detection of a fingerprint and / or password at a device (e.g., device 100), and detection of a mechanical input (e.g., a button press) on another device (e.g., device 500).

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

[0200] Payment server 554 optionally uses at least some of the payment information to identify the user account from a database of user accounts (e.g., 552). 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 gift card number) or when no account includes payment information that matches the information from the POS communication.

[0201] 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., 554) 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.

[0202] In some embodiments, the payment server 554 responds to the POS payment terminal (e.g., terminal 550) with an indication of whether the proposed purchase is authorized or rejected. In some embodiments, the POS payment terminal (e.g., terminal 550) transmits a signal to the electronic device (e.g., 100, 300, 500) to identify the result. For example, when the purchase (e.g., via a transaction coordination server that manages the transaction application on the user device) is authorized, the POS payment terminal (e.g., terminal 550) sends a receipt to the electronic device (e.g., 100, 300, 500). In some cases, the POS payment terminal (e.g., terminal 550) 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.

[0203] In some embodiments, the electronic device (e.g., 100, 300, 500) participates in a transaction that is completed without involving a POS payment terminal (e.g., terminal 550). For example, upon detecting that a mechanical input has been received, a secure element in the electronic device (e.g., 100, 300, 500) publishes 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).

[0204] In some embodiments, the electronic device (e.g., 100, 300, 500) 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 100 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.

[0205] 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.

[0206] 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.

[0207] Attention is now turned to embodiments of a user interface ("UI") and associated processes implemented on an electronic device, such as portable multifunction device 100, device 300, or device 500.

[0208] FIG. 6A to FIG. 6R illustrative user interfaces for sharing electronic keys according to some embodiments are shown. The user interfaces in these figures are used to illustrate the process described below, including Figure 7 In some embodiments, device 600 includes one or more features of devices 100, 300, and / or 500.

[0209] exist Fig. 6A In some embodiments, the electronic wallet of device 600 stores electronic hotel keys (e.g., device 600 has been provisioned to include account information for electronic hotel keys). In some embodiments, device 600 has been provisioned to include account information for multiple accounts, including electronic hotel keys, university electronic identification cards, electronic boarding passes, electronic concert tickets, and loyalty cards. Fig. 6A As shown, device 600 displays a wallet user interface (UI) 602 that includes an electronic hotel key representation 604 of an electronic hotel key. Wallet UI 602 also includes representations of a college identification card, a boarding pass, concert tickets, and a loyalty card.

[0210] exist Fig. 6AAt (e.g., after user authentication at device 600) device 600 is held by first user 606 near a secure access terminal 608 associated with a secure location (e.g., a secure entrance to the secure location, such as a locked door to a secure room or building). In some embodiments, the secure access terminal 608 is configured to control access to the secure location (e.g., a room, building, swimming pool, and / or gym) by locking / unlocking a secure door 610. In some embodiments, device 600 (e.g., via a wireless communication radio of device 600) detects the presence of a field 612 generated by the secure access terminal 608. In response to detecting the presence of the field 612 generated by the secure access terminal 608 (or after and / or thereafter), device 600 (e.g., via a wireless communication radio of the device) transmits credentials of a money transfer account (e.g., a secure access account) associated with the electronic hotel key to the secure access terminal 608. In some embodiments, transmitting the credentials of the money transfer account to the secure access terminal 608 causes the secure door 610 to unlock and / or open, thereby enabling the user to enter the secure location. In some embodiments, if the transfer account is not configured to provide access at the location, the transfer account's credentials are transmitted to the security access terminal 608 without causing the security door 610 to unlock or open (e.g., because the valid credentials are not presented to the security access terminal 608). In some embodiments, the security access terminal 608 communicates with the network associated with the entity that issues the electronic hotel key. In some embodiments, the network associated with the entity that issues the electronic hotel key sends and / or (e.g., from device 600 and / or device 800) receives communications about the state of the electronic hotel key (e.g., what access rights have been shared and / or whether the electronic hotel key has been supplied to the wallet of the device). In some embodiments, the user can manage the electronic hotel key by logging into the application and / or website of the entity that issues the electronic hotel key (e.g., using all the techniques described herein to manage the electronic hotel key, including managing what access rights are shared, managing whether the electronic key can be shared, managing whether an activation code is required, and / or managing whether different users have shared keys).

[0211] exist Fig. 6A , while displaying the wallet UI 602, the device 600 detects a tap input 650 directed to the electronic hotel key representation 604. In response to detecting the tap input 650, the device 600 displays the wallet UI 602, such as Figure 6B As depicted in .

[0212] exist Figure 6B, the wallet UI 602 includes a key representation 604 and a room representation 614 of a room to which the electronic hotel key grants access. The wallet user interface 602 also includes a share icon 616. If the electronic hotel key can be shared with another device associated with a user other than the user of the device 600, the device 600 displays the share icon 616. In some embodiments, a hotel that authorizes electronic hotel keys can configure the electronic hotel key to enable sharing of the electronic hotel key with another user or to disable sharing of the electronic hotel key. While displaying the wallet UI 602, the device 600 detects a tap input 650b directed to the share icon 616 to share the electronic hotel key. In response to detecting the tap input 650b, the device 600 displays a communication options user interface 618, such as Figure 6C As depicted in .

[0213] exist Figure 6C , communication options user interface 618 includes enable indications 620 associated with different contacts and / or different communication applications. For example, activation indication 620a initiates the use of an instant messaging application to share an electronic hotel key with a user (e.g., Jane). Activation indication 620b initiates the use of an instant messaging application to share an electronic hotel key without initially specifying a recipient. Activation indication 620c initiates the use of an email application to share an electronic hotel key. Activation indication 620d initiates the use of other communication applications (such as a third-party communication application) to share an electronic hotel key. Figure 6CAt, when displaying communication options user interface 618, device 600 detects the selection of an affordance in affordance 620. In some embodiments, the first affordance in affordance 620 corresponds to a specific application, and optionally corresponds to a specific individual. In response to receiving the selection of affordances corresponding to the first application and the first individual in affordance 620, device 600 continues the process to share an electronic hotel key with the first individual using the first application. In response to receiving the selection of affordances corresponding to the second application and not corresponding to the specific individual in affordance 620, device 600 continues the process to share an electronic hotel key using the second application without initially specifying the recipient of the shared electronic hotel key. In some embodiments, when device 600 detects the selection of affordances in affordance 620, and according to determining that the selected affordance corresponds to a user account of a user (e.g., Jane) of a specific service (e.g., a service for which the user of device 600 also has a user account), the computer system automatically disables the activation code feature for sharing electronic hotel keys. In some embodiments, when device 600 detects a selection of an enablement representation in enablement representation 620, and based on determining that the selected enablement representation does not correspond to a user account of a user for a particular service (e.g., a service for which the user of device 600 also has a user account), the computer system automatically enables an activation code feature for sharing electronic hotel keys.

[0214] For example, in Figure 6C At , device 600 detects tap input 650c1 directed to enable indication 620a, and in response to detecting tap input 650c1 and based on determining that enable indication 620a corresponds to a user account (e.g., Jane's) for a particular service (e.g., a service for which the user of device 600 also has a user account), device 600 displays key sharing user interface 622 with activation code enable indication 628 disabled, as shown. Fig.6D For another example, Figure 6C At , device 600 detects tap input 650c3 directed to enable indication 620c, and in response to determining that enable indication 620c does not correspond to a user account for a particular service (e.g., a service for which the user of device 600 also has a user account), device 600 displays key sharing user interface 622 with activation code enable indication 628 enabled, as shown in FIG. Fig. 6E shown.

[0215] Back to Figure 6C, device 600 detects tap input 650c1 directed to affordance 620a. In response to detecting tap input 650c1 and based on determining that affordance 620a corresponds to a user account (e.g., Jane's) for a particular service (e.g., a service for which the user of device 600 also has a user account), device 600 displays key sharing user interface 622 with activation code affordance 628 disabled, as shown. Fig.6D shown.

[0216] exist Fig.6D At , key sharing user interface 622 includes an enabled re-sharing affordance 624. When enabled, re-sharing affordance 624 gives the recipient and another user (e.g., Fig. 8E In some embodiments, the recipient cannot reshare the electronic hotel key with another user (device 800 of a second user 806). In some embodiments, when the reshare enable indication 624 is disabled, the recipient cannot reshare the electronic hotel key with another user. In some embodiments, the reshare enable indication 624 is enabled by default. In some embodiments, the reshare enable indication 624 is disabled by default. In some embodiments, the selection of the reshare enable indication 624 switches the reshare enable indication 624 between an enabled state and a disabled state.

[0217] exist Fig.6D At , the key sharing user interface 622 includes an activation code indicator 628. Fig.6D At the activation code, the 628 is disabled, and Fig. 6E When the activation code enable indication 628 is enabled, the device 600 displays (e.g., concurrently displays) an indication 603 (e.g., Fig. 6E ), and when the activation code indication 628 is disabled, the device 600 does not display the indication 603 (as depicted in Fig.6D ). The activation code provides an additional layer of security when sharing the electronic hotel key. In some embodiments, the recipient cannot use the electronic hotel key until the user associated with the recipient's device has entered the activation code. In some embodiments, the device cannot be provisioned with the electronic hotel key until the activation code is entered at the device (e.g., at the recipient's device).

[0218] exist Fig.6D At the same time, device 600 enables or disables activation code enablement representation 628 (e.g., automatically) based on how the electronic hotel key will be shared. In some embodiments, device 600 determines which application will be used to share the electronic hotel key to enable or disable activation code enablement representation 628 (e.g., based on the Figure 6C). In such an embodiment, the device 600 enables the activation code enable indication 628 in response to detecting that the electronic hotel key will be shared using an instant messaging application, and disables the activation code enable indication 628 in response to detecting that the electronic hotel key will be shared using an email application. In some embodiments, the device 600 determines whether the user with whom the electronic hotel key is shared is known. In such an embodiment, the device 600 enables the activation code enable indication 628 in response to detecting that the user is a contact stored on the device 600 and / or that the first user 606 and the user with whom the key is shared both have an account with the same entity (e.g., the same online service). In response to detecting input directed to the activation code enable indication 628 (e.g., if the user wants to manually enable or disable the activation code), the device 600 enables or disables the activation code enable indication 628. As shown, in Fig.6D At 615, while displaying key sharing user interface 622, device 600 detects tap input 650d directed to activation code enable representation 628. In response to detecting tap input 650d, device 600 enables activation code enable representation 628, such as Fig. 6E 622 as depicted in the key sharing user interface.

[0219] exist Fig. 6E , key sharing user interface 622 includes access level affordance 626. Activating access level affordance 626 causes device 600 to display affordances that allow the user to select which permissions to share with the recipient. In some embodiments, device 600 cannot add or share permissions beyond those already granted to device 600 (e.g., the entity (e.g., the hotel) providing access). Fig. 6E At 640, while displaying key sharing user interface 622, device 600 detects tap input 650e directed to access level affordance 626. In response to detecting tap input 650e, device 600 displays access level editing user interface 632, such as Fig. 6F As depicted in .

[0220] exist Fig. 6F, access level editing user interface 632 allows a user to configure different shared access rights. Access level editing user interface 632 includes: an enable indication 634, which is used to modify location access rights for different security areas; an enable indication 636, which is used to share access rights associated with using the provider's services; and a time limit enable indication 638, which, when selected, displays a user interface to configure a time limit for the shared access rights. Device 600 optionally detects input on enable indication 634 and, in response, disables (or enables) the corresponding access rights. Thus, device 600 can modify which access rights are provided to the recipient of the electronic hotel key. As shown in FIG. Fig. 6F As shown, secure areas include specific rooms (e.g., rooms 203 and 205) and secure areas of the property (e.g., a gym and / or swimming pool). In some embodiments, users may share access to one or more provider services, such as updating one or more aspects of a reservation (e.g., extending a reservation, shortening a reservation, and / or exchanging rooms) and utilizing services provided by a provider (e.g., room service and / or restaurant dining deals). Fig. 6F At , while displaying access level editing user interface 632, device 600 detects tap input 650f1 directed to room affordance 634a. In response to detecting tap input 650f1, device 600 disables access to room 203, which results in device 600 not sharing access to room 203.

[0221] exist Fig. 6F At 640, while displaying access level editing user interface 632, device 600 detects tap input 650f2 directed to time limit affordance 638. In response to detecting tap input 650f2, device 600 displays time limit user interface 640, as shown in FIG. Figure 6G As depicted in .

[0222] exist Figure 6G , time limit user interface 640 allows the user to set a time range for when access rights are enabled (e.g., valid and / or authorized), as well as a start date and / or end date for when access rights are enabled. In some embodiments, device 600 cannot share permissions (or extend those permissions) beyond those initially received from the hotel. Activation day enablement representation 642 causes device 600 to display an enablement representation for selecting a specific day for enabling access rights. Activation time enablement representation 644 causes device 600 to display an enablement representation for selecting a specific time of day for enabling access rights. In some embodiments, activation enablement representation 646 causes device 600 to display an enablement representation for specifying a start date and end date for enabling and disabling access rights, respectively.

[0223] exist Figure 6G At 640, while the time limit user interface 640 is displayed, the device 600 detects a tap input 650g pointing to the sky indicator 642. In response to detecting the tap input 650g, the device 600 displays the time limit user interface 640, as shown in FIG. Figure 6H As depicted in .

[0224] exist Figure 6H At , time limit user interface 640 includes an enable indication 652 for configuring a day of the week on which access rights are enabled (e.g., the access rights displayed in access level editing user interface 632). As shown, Monday enable indication 652a and Tuesday enable indication 6502b are enabled. Thus, for example, the access rights associated with the shared electronic hotel key will only be valid on Mondays and Tuesdays (e.g., a recipient receiving the electronic hotel key from device 600 will only enable access rights on Mondays and Tuesdays). Because the enable indications for other days are not enabled, the access rights associated with the shared electronic hotel key are invalid for those days. While displaying time limit user interface 640, device 600 detects a tap input 650h directed to time enable indication 644. In response to detecting tap input 650h, device 600 displays time limit user interface 640, as shown in FIG. Fig.6I As depicted in .

[0225] exist Fig.6I At, time limit user interface 640 includes the indication for specifying the time range of enabling the access rights to shared electronic hotel keys in one day.As shown in the figure, time limit user interface 640 includes start time indication 654a and end time indication 654b.In some embodiments, in response to detecting the selection of start time indication 654a or end time indication 654b, device 600 displays one or more indications for configuring the start time or one or more indications for configuring the end time respectively.As shown in the figure, start time indication 654a has the indication of 9:00 am, and end time indication 654b has the indication of 5:00 pm.Thus, as shown in the figure, the access rights to shared electronic hotel keys will be enabled from 9:00 am to 5:00 pm on Monday and Tuesday.Because access rights are enabled from 9:00 am to 5:00 pm, the access rights associated with shared electronic hotel keys are not valid during any other time on Monday or Tuesday.

[0226] exist Fig.6IAt , time limit user interface 640 includes advanced sharing affordances 648. Advanced sharing affordances 648 allow a user to configure a time range for specific access rights to be enabled (e.g., valid and / or authorized). In some embodiments, for example, in response to detecting input directed to advanced sharing affordances 648, device 600 displays one or more affordances for configuring time limits for specific access rights. Thus, for example, device 600 can selectively disable access to room 205 from 8:00 a.m. to noon, while access to the swimming pool is not disabled during the same time range.

[0227] exist Figure 6J At , after disabling room affordance 634a and configuring time limits for other access permissions, device 600 displays key sharing user interface 622 (e.g., based on selection of the left chevron of time limit user interface 640). Figure 6J As shown, the device 600 changes the access level indicator 626 from indicating that full access rights are being shared (eg, Fig. 6E ) to indicate that limited access rights are being shared (as depicted in Figure 6J ) of the access level affordance 626. Similar to Figure 6J , device 600 displays re-sharing enable indication 624 and activation code enable indication 628 as both enabled. Device 600 also displays an indication 603 of the activation code. While displaying key sharing user interface 622, device 600 detects a tap input 650j directed to continue enable indication 656. In response to detection 650j, device 600 initiates a process of authenticating first user 606 (e.g., using biometric authentication (e.g., facial authentication, fingerprint authentication, and / or iris authentication) and / or using a password or passcode).

[0228] exist Figure 6K At , the device 600 authenticates the first user 606. As shown, the face authentication notification 659 indicates that the device 600 is using facial authentication to authenticate the first user 606. In response to authenticating the first user 606, the device 600 displays an instant messaging user interface 660a, such as Figure 6L As depicted in .

[0229] exist Figure 6LAt , device 600 displays instant messaging user interface 660a. Device 600 displays a key representation 604 of the electronic hotel key in the draft message. Instant messaging user interface 660 also includes a representation 664 of the second user 806 so that the first user 606 will know to whom the key will be sent. As shown, instant messaging user interface 660 includes text message 668 of a conversation between first user 606 and second user 806 before the electronic hotel key is sent. While displaying instant messaging user interface 660a, device 600 detects a tap input 650l directed to a send enable representation 662. In response to detecting tap input 650l, device 600 displays activation code interface 670, as shown in FIG. Figure 6M In some embodiments, in response to detecting the tap input 6501, the device 600 stops displaying the instant messaging user interface 660a. In some embodiments, in response to detecting the tap input 6501, the device 600 does not stop displaying the instant messaging user interface 660a. In some embodiments, the device 600 displays an activation code interface 670 overlaid on the wallet UI 602. In some embodiments, the device 600 displays the activation code interface 670 overlaid on the instant messaging user interface 660. In some embodiments, in response to detecting the tap input 6501, the device 600 transmits a message 804 including information about the electronic hotel key (e.g., account information, access permissions, and / or a link to the access account information of the electronic hotel key) to the device 800, such as Fig. 8A In some embodiments, in response to detecting tap input 6501, device 600 does not transmit an activation code (eg, the activation code is not included in message 804).

[0230] exist Figure 6M At , activation code interface 670 includes an indication 603 of an activation code and one or more enable indications for initiating a corresponding process for transmitting the activation code to a recipient. As shown, activation code interface 670 includes a call enable indication 672a, a share enable indication 672b, and a copy enable indication 672c. In some embodiments, in response to detecting input directed to the share enable indication 672b, device 600 displays an enable indication for sharing the activation code with different contacts and / or communication applications. In some embodiments, options are displayed for different communication applications of the same recipient (e.g., Jane) with whom the electronic hotel key is shared. For example, in some embodiments, device 600 displays different communication applications and / or contact information similar to the communication application and / or contact information in communication options user interface 618, such as Figure 6C In some embodiments, in response to detecting input pointing to the copy-enabling representation 672c, the device 600 copies the activation code, which allows the first user 606 to paste the activation code into the notebook application and / or the communication application.

[0231] exist Figure 6M In some embodiments, one or more affordances for initiating a process of transmitting an activation code with device 800 include affordances for a communication application (and / or channel) different from the communication application used to transmit the electronic hotel key. As shown, communication call affordance 672a, when selected, initiates a process of calling device 800, as opposed to sending a text using instant messaging user interface 660. Providing affordances for initiating a process of transmitting an activation code on a different communication channel enhances the security of sharing an electronic hotel key with another user because it prevents an unknown person from intercepting message 804 and using the electronic hotel key.

[0232] exist Figure 6M At 650 m, while displaying activation code interface 670, device 600 detects tap input 650 m directed to call enable indication 672 a. In response to detecting tap input 650 m, device 600 displays call enable indication 673, as shown in FIG. Figure 6N As depicted in .

[0233] exist Figure 6N At , device 600 displays a call enable representation 673, which, when selected, initiates an audio call between device 600 and the recipient of the shared electronic hotel key (e.g., at device 800). In some embodiments, in response to detecting input directed to call enable representation 673, device 600 initiates a call to the recipient of the shared electronic hotel key (e.g., at device 800). Thus, in some embodiments, first user 606 can transmit an access code to second user 806 via a call, which ensures the identity of second user 806 and / or prevents a different person who may have intercepted message 804 from receiving the access code.

[0234] exist Fig.6O At 600, the device 600 displays a wallet user interface 602 for the electronic key. Fig.6O As shown, wallet user interface 602 includes a management affordance 674 that allows a user to manage different aspects associated with how a shared electronic hotel key is shared (e.g., access rights and / or other users with access rights to use the shared electronic hotel key). In some embodiments, device 600 displays management affordance 674 based on detecting that the electronic hotel key has been shared with a particular user by the original key holder (e.g., first user 606) and / or when another user reshares the key, as described herein. While displaying wallet user interface 602, device 600 detects a tap input 650o directed to management affordance 674. In response to detecting tap input 650o, device 600 displays management user interface 676, as described herein. Figure 6P As depicted in .

[0235] exist Figure 6P At , management user interface 676 includes enable representations 678a to 678c associated with users with whom the electronic hotel key has been shared. In response to detecting input on a corresponding enable representation of enable representations 678a to 678c, device 600 displays a user management interface 677 for the corresponding user. Management user interface 676 also includes add person enable representation 680. In some embodiments, in response to detecting a selection of add person enable representation 680, device 600 initiates a process of sharing the electronic hotel key with another user, including optionally displaying FIG. 6C to FIG. 6O The user interface and / or affordance described in .

[0236] like Figure 6P As shown, while displaying management user interface 676, device 600 detects tap input 650p1 directed to affordance 678a associated with second user 806. In response to detecting tap input 650p1, device 600 displays individual user management interface 677 associated with second user 806 (Jane), as shown in FIG. Figure 6Q While displaying management user interface 676, device 600 detects tap input 650p2 directed at affordance 678c associated with Dave. In response to detecting tap input 650p2, device 600 displays individual user management interface 677 associated with Dave, as shown in FIG. Figure 6R As depicted in .

[0237] exist Figure 6Q In the example embodiment, the individual user management interface 677 allows the user to modify the permissions that have been shared with a specific user. The individual user management interface 677 allows the user to manage the access rights (including time limits) provided via the shared electronic hotel key discussed herein. Figure 6Q The individual user management interface 677 in FIG. 1 allows the first user 606 to modify the permissions that have been shared with the second user 806 associated with the device 800. The individual user management interface 677 includes a re-sharing enable indication 624 and an access level enable indication 626, which, when activated, enable the device 600 to be used as described in reference to FIG. FIG. 6D to FIG. 6I For example, in some embodiments, in response to detecting input directed to re-sharing enable indication 624, device 600 disables re-sharing enable indication 624 to prevent user 806 from sharing the key (even if user 606 originally shared the permission with user 806). Figure 6QThe individual user management interface 677 in the embodiment also includes an indication 603 of the access code and a refresh enable indication 630, which, when activated, causes the device 600 to replace / update the indication 603 with a new access code (e.g., different from the access code). Figure 6Q The individual user management interface 677 in includes an indication 603 of the access code and a refresh enable representation 630 because the second user 806 has not yet added the electronic hotel key to the digital wallet. Therefore, if the second user 806 misplaces or forgets the access code, the first user 606 can view the access code and / or generate a new access code. In some embodiments, after the electronic hotel key has been added to the device 800 (the device associated with Jane), the device 600 modifies the access rights shared with the second user 806. In some embodiments, the device 600 stops displaying the access code and the refresh enable representation 630 based on receiving an indication that the device (e.g., device 800) has added the shared electronic hotel key to the digital wallet.

[0238] exist Figure 6R , the individual user management interface 677 allows the first user 606 to modify the access permissions that have been shared with the device associated with Dave. Figure 6R Individual user management interface 677 in Figure 6Q The individual user management interface 677 in FIG. However, as shown in the figure, Figure 6R The individual user management interface 677 in does not include an indication of the access code 603 and the refresh enable indication 630 because the device associated with Dave has already added the shared electronic hotel key to the digital wallet. Figure 6R The individual user management interface 677 in also includes an indication 688 that Dave has shared the electronic hotel key with Tom. Figure 6P In some embodiments, in response to detecting input on affordance 678c, device 600 modifies the access permissions that Dave shares with Tom. Figure 6R In some embodiments, device 600 terminates any permissions that Dave shared with Tom in response to detecting input on stop sharing enable indication 686. In some embodiments, in response to detecting input on stop sharing enable indication 686, device 600 causes Tom's device to disable (and / or stop displaying) the shared electronic hotel key and / or any access permissions associated with the shared electronic hotel key.

[0239] Figure 7700 is a flowchart illustrating a method for sharing an electronic key using a computer system according to some embodiments. Method 700 is performed at a computer system (e.g., 100, 300, 500, 600, and / or 800) (e.g., a smart watch, a smart phone, a tablet computer, a head-mounted device (e.g., a head-mounted augmented reality and / or extended reality device), and / or a laptop computer) that communicates with one or more input devices (e.g., a touch-sensitive surface, a keyboard, a controller, a rotatable input device, a microphone, and / or a mouse). In some embodiments, the computer system communicates with a display generation component (e.g., 601 and / or 801) (e.g., a display controller, a head-mounted display system, a touch-sensitive display system, and / or a monitor). Some operations in method 700 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0240] As described below, method 700 provides an intuitive way to share electronic keys. The method reduces the cognitive burden of sharing electronic keys on users, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to share electronic keys more quickly and efficiently saves power and increases the time interval between battery charges. The method also improves the security of sharing electronic keys.

[0241] When the first computer system is associated with a first user (e.g., 606 and / or 806) (e.g., corresponds to the first user, is being used by the first user, and / or is logged in by the first user) (e.g., the first user is logged in to the computer system using a first user account), the computer system (702) detects, via one or more input devices, an electronic key (e.g., an electronic wallet including credentials of one or more accounts (e.g., a transportation account, a payment account, a loyalty account, electronic keys and / or tickets), electronic keys that can be accessed using the wallet, and / or electronic keys stored and / or saved in the electronic wallet) that is shared with a second user (e.g., 606 and / or 806) that is different from the first user (e.g., corresponds to the second user account). FIG. 6A to FIG. 6R Electronic hotel keys and / or FIG. 8A to FIG. 8LA set of one or more inputs (e.g., 650b, 650c1, 650c2, 650c3, 650c4, 650j, 659, 650l, 850f, 850g, 850j, and / or 830) corresponding to a request for an electronic hotel key (e.g., credentials for an electronic card key and / or credentials for accessing a key account) (e.g., including at least one input on a selectable UI object to send the electronic key, or not including an input on a selectable UI object), wherein the electronic key provides access to one or more physical locations (e.g., One or more access rights (e.g., access rights associated with affordances (e.g., 634 and / or 636) in access level editing user interface 632 and / or time limits associated with affordances (e.g., 642, 644, 646, and / or 648) of time limit user interface 640) are provided (e.g., an electronic key provides access to a room or building; and / or an electronic key unlocks a physical lock and / or door). In some embodiments, the physical location is a secure area (e.g., in a building (e.g., a room, an elevator, and / or a washing machine), or an outdoor area (e.g., a gated area, an outdoor pool, and / or a private driveway) and / or a vehicle (e.g., a car or truck)). In some embodiments, the one or more access rights include temporary access rights (e.g., the access rights are valid for a corresponding time range). In some embodiments, the wallet includes a visual representation of the electronic key. In some embodiments, the wallet includes credentials other than an electronic key for one or more accounts (e.g., a loyalty account, a payment account, a transportation account, an electronic credit card, and / or an electronic ticket). In some embodiments, the wallet includes one or more visual representations of one or more accounts (e.g., a first representation for a first account, a second representation for a second account, and / or a third representation for an electronic key).

[0242] In response to detecting the set of one or more inputs corresponding to a request to share an electronic key, the computer system initiates (704) (e.g., starts, causes and / or executes a transfer command) a process of sharing an electronic key (e.g., transmitting information to enable the recipient to access an electronic key that provides access to at least some of one or more access rights to a physical location while the first user maintains access to the electronic key) with a second user of a second computer system (e.g., 600 and / or 800) that is different from the first user of the first computer system (e.g., a remote computer system, an external computer system, a computer system associated with a user different from the user associated with the first computer system, a smart phone, a tablet computer, a laptop computer, a desktop computer and / or a head mounted device). In some embodiments, the process of sharing an electronic key with a second user of a second computer system includes: based on determining that an activation code (e.g., 603) (e.g., a security code and / or PIN) for sharing the electronic key is enabled (e.g., the activation code enable indication 628 is enabled) (e.g., activated), displaying (706) via a display generation component a first selectable object (e.g., 672a to 672c and / or 673) (e.g., a button and / or other user-selectable interface object) for initiating the process of transmitting the activation code (e.g., initiating a communication channel to allow the user (e.g., orally or by writing) to transmit the activation code, and / or start an audio call, start a video call, start a draft of an instant message, start a draft of an email); and based on determining that the activation code for sharing the electronic key is disabled (e.g., the activation code enable indication 628 is disabled), abandoning (708) displaying the first selectable object for initiating the process of transmitting the activation code.

[0243] In some embodiments, the electronic key is shared without transmitting the activation code. In some embodiments, the activation code is transmitted independently of the shared electronic key. In some embodiments, the first computer system displays the corresponding user interface when detecting the set of one or more inputs corresponding to the request to share the electronic key (e.g., the set of inputs includes at least one input on the enabling representation for sending the electronic key). In some embodiments, based on determining that the activation code for sharing the electronic key is enabled, at least a portion of the corresponding user interface (e.g., the entire portion and / or sub-portion (e.g., the first portion instead of the second portion)) stops being displayed (e.g., at least a portion of the instant messaging user interface stops being displayed). In some embodiments, based on determining that the activation code for sharing the electronic key is disabled, the first computer system displays the user interface of the electronic wallet (e.g., after the user requests the computer system to send the key in the communication application, the first computer system automatically displays the user interface of the wallet). If the activation code for sharing the electronic key is enabled, displaying the selectable object to transmit the activation code improves the computer system because the computer system displays the selectable object when a set of conditions are met, which performs an operation when a set of conditions are met without further user input. Additionally, displaying a selectable object to communicate an activation code improves the computer system because it provides enhanced security when sharing an electronic key.

[0244] In some embodiments, the computer system detects a second group of one or more inputs including an input pointing to a first selectable object (e.g., an input on 650m and / or 673) via one or more input devices. In some embodiments, in response to detecting the second group of one or more inputs, the computer system transmits (e.g., transmits and / or sends) the activation code to the second user. In some embodiments, the selection of the first selectable object causes a draft text message including the activation code to be displayed to the second user. In some embodiments, the selection of the first selectable object causes a draft email including the activation code to be displayed to the second user. In some embodiments, the selection of the first selectable object causes an audio call to be made to the second user to transmit the activation code. In some embodiments, the first computer system detects the selection of the first selectable object, and in response, initiates a process for transmitting the activation code to the second user. In some embodiments, the first selectable object is displayed in response to transmitting the shared electronic key to the second user. In some embodiments, the detection of the second group of one or more inputs includes an input on the sending affordance representation of the detection message (e.g., a text message and / or an email message). In some embodiments, in response to detecting the second set of one or more inputs, the first computer system (e.g., via a telecommunications network and / or a wireless network) initiates a voice communication channel to transmit the activation code. In some embodiments, the first selectable object corresponds to the second user (e.g., to start communication with the second user). In some embodiments, based on determining that the activation code (e.g., security code and / or PIN) for sharing the electronic key is enabled, the first computer system displays a plurality of selectable objects for communicating with the second user (e.g., each selectable object is used for options using different communication technologies). Transmitting the activation code in response to user input (e.g., rather than when the electronic key is shared) enhances security during the process of sharing the electronic key by enabling the first user to transmit the activation code to the second user separately from the shared electronic key.

[0245] In some embodiments, transmitting the activation code does not activate the shared electronic key. In some embodiments, after the shared electronic key has been provisioned to the electronic wallet of the second computer system, the shared electronic key provides one or more access permissions to the one or more physical locations (e.g., to the second user) at the second computer system. In some embodiments, the first computer system continues to retain the one or more access permissions to the one or more physical locations provided by the electronic key at the first computer system.

[0246] In some embodiments, the computer system detects the selection of the first selectable object via the one or more input devices. In some embodiments, in response to detecting the selection of the first selectable object, the computer system initiates the process of transmitting the activation code, including displaying the conversation between the first user and the second user (e.g., displaying the indication 603 of the access code in the instant messaging interface 660 and / or the instant messaging interface 802) (e.g., a chat conversation, an instant messaging conversation, and / or an email thread). In some embodiments, the conversation is displayed as part of the instant messaging application. In some embodiments, when displaying the conversation between the first user and the second user, the computer system detects the selection of the option (e.g., 662, 672a to 672c and / or 830) (e.g., sending an affordance and / or a voice command) for transmitting the activation code (e.g., filling in the draft message) to the second user via the one or more input devices. In some embodiments, in response to detecting the selection of the option for transmitting the activation code to the second user, the computer system transmits the activation code to the second user as part of the conversation between the first user and the second user. In some embodiments, the computer system automatically fills the activation code into a draft message that can be sent via the option of selecting the transmission activation code. In some embodiments, the computer system enables user input to add additional information (and / or modify existing information) in the draft message before sending the message. In some embodiments, the displayed conversation is updated to reflect the transmitted activation code (and any additional corresponding message). In some embodiments, the process of sharing an electronic key with a second user includes: a representation (e.g., image and / or text) of a shared electronic key in a draft message of an instant messaging application (e.g., an instant messaging application, a text messaging application, and / or an email application) and a representation of a conversation between the first user and the second user (e.g., text that has been sent and / or received) (e.g., a message that has been sent before the draft message including the representation of the shared key) is displayed concurrently via a display generation component. While concurrently displaying the representation of the shared electronic key in the draft message and the representation of the conversation, the computer system detects a selection of an option to transfer the shared electronic key to the second user (e.g., selection of a send button and / or receipt of a send voice command), and in response, the computer system transfers the shared electronic key to the second user as part of the conversation between the first user and the second user. Displaying the option to transfer the activation code and / or the representation to transfer the shared electronic key concurrently with the representation of the conversation provides visual feedback to the user as to to whom the activation code and / or electronic key will be sent, and reduces the risk of the activation code and / or electronic key being inadvertently shared with a user other than the intended recipient, which provides improved visual feedback and provides enhanced security when sharing the electronic key.

[0247] In some embodiments, during the process of sharing an electronic key with a second user of a second computer system: based on determining that an activation code (e.g., a security code and / or a PIN) for sharing an electronic key is enabled (e.g., activated), the computer system displays a second selectable object (e.g., 672a to 672c and / or 673) (e.g., a button and / or other user-selectable interface object) for initiating a process of transmitting an activation code (e.g., initiating a different type of communication channel to allow a user to transmit an activation code (e.g., verbally or by writing) based on a selected selectable object) concurrently with the first selectable object via a display generation component; and based on determining that the activation code for sharing an electronic key is disabled, the computer system abandons displaying the second selectable object for initiating the process of transmitting the activation code. In some embodiments, while displaying the first selectable object and the second selectable object concurrently, the computer system detects an object selection user input via the one or more input devices. In some embodiments, in response to detecting an object selection user input: based on determining that the object selection user input corresponds to a selection of a first selectable object, a process of transmitting an activation code is initiated using a first communication technology (e.g., a first application, an instant messaging application (such as by displaying a draft message), and / or an email application (such as by displaying a draft email)); and based on determining that the object selection user input corresponds to a selection of a second selectable object, a process of transmitting an activation code is initiated using a second communication technology different from the first communication technology (e.g., a second application different from the first application, an audio call application (such as by starting (or actively starting) an audio call), and / or a video call application (such as by starting (or actively starting) a video call)). In some embodiments, the first communication technology uses first contact information (e.g., an email address) for the first communication technology without using second contact information (e.g., a phone number), and the second communication technology uses the second contact information without using the first contact information. In some embodiments, based on determining that the shared electronic key is shared with the corresponding user, the first computer system displays a selectable object that initiates communication using the contact information (e.g., phone number and / or email) of the corresponding user. In some embodiments, based on determining that the shared electronic key is shared with a user different from the corresponding user, the first computer system displays a selectable object for initiating communication using contact information (e.g., phone number and / or email) of a user different from the corresponding user. In some embodiments, the first application and the second application utilize different communication channels, modalities, and / or networks. Using various corresponding techniques to display various selectable objects to initiate transmission of the activation code when sharing an electronic key provides enhanced security (e.g., because it is difficult for a malicious actor to access both communication applications at the same time).

[0248] In some embodiments, during the process of sharing an electronic key with a second user of a second computer system: based on determining that an activation code (e.g., a security code and / or a PIN) for sharing an electronic key is enabled (e.g., activated), the computer system displays a third selectable object (e.g., 672a to 672c and / or 673) (e.g., a button and / or other user-selectable interface object) via the display generation component and concurrently with the first selectable object to copy the activation code (e.g., to a specific application and / or to a memory for later pasting into a different user interface); and based on determining that the activation code for sharing an electronic key is disabled, the computer system abandons displaying the third selectable object for copying the activation code. In some embodiments, while displaying the first selectable object and the third selectable object concurrently, the computer system detects an object selection user input via the one or more input devices. In some embodiments, in response to receiving an object selection user input: based on determining that the object selection user input corresponds to a selection of a first selectable object, the computer system initiates a process of transmitting the activation code using a first communication technology (e.g., a first application, an instant messaging application (such as by displaying a draft message), and / or an email application (such as by displaying a draft email)) but does not copy the activation code; and based on determining that the object selection user input corresponds to a selection of a third selectable object, the computer system copies the activation code but does not initiate a process of transmitting the activation code using the first communication technology. In some embodiments, in response to detecting the set of one or more inputs corresponding to a request to share an electronic key and based on determining that an activation code for sharing an electronic key is enabled, a third selectable object is displayed via a display generation component, the third selectable object copying (e.g., saving and / or storing) the activation code when selected. Displaying the selectable object to copy the activation code improves the computer system because it allows the user to save the activation code and send it later, and / or allows the user to save the activation code and send it from a different application, which provides enhanced security when transmitting the activation code.

[0249] In some embodiments, the second computer system uses the activation code to activate the shared electronic key (e.g., as described in reference FIG. 8B to FIG. 8E In some embodiments, the computer system cannot activate the shared electronic key (e.g., cannot be used by the second user to gain access to one or more physical locations and / or provisioned to an electronic wallet of the second computer system) without using the activation code. In some embodiments, the second computer system uses the activation code to provision the shared electronic key to a wallet application of the second computer system. Using the activation code to activate the shared electronic key (and / or provision the shared electronic key to an electronic wallet) enhances the security of the shared electronic key.

[0250] In some embodiments, the activation code is received and / or generated during the process of sharing the electronic key (e.g., by the first computer system and / or by a server in communication with the first computer system). In some embodiments, a new activation code is received and / or generated during the process of sharing the electronic key with a third computer system (different from the second computer system) (e.g., by the first computer system and / or by a server in communication with the first computer system). In some embodiments, the activation code is a single-use activation code (e.g., the activation code is not reused and / or the activation code is specific to a specific case of sharing the electronic key).

[0251] In some embodiments, the activation code is predetermined before initiating the sharing process. In some embodiments, the activation code is received and / or generated before initiating the process of sharing the electronic key (e.g., by a computer system different from the computer system and / or an entity that issues the electronic key). In some embodiments, the same activation code is used during the process of sharing the electronic key with a third computer system (different from the second computer system). In some embodiments, the activation code is a multiple use activation code (e.g., the activation code is reused and / or the activation code is not specific to a particular case of sharing the key).

[0252] In some embodiments, during the process of sharing an electronic key with a second user of a second computer system, the computer system displays, via a display generation component, a user interface (e.g., 640) for specifying a time range (e.g., 642, 644, 646, 648, 654a to 654b, and / or 652) for the shared electronic key (e.g., specific days, specific hours, and / or specific minutes), during which time range at least one of the one or more access permissions of the shared electronic key to one or more physical locations is active (e.g., enabled and / or valid) (and / or specifies a second time range during which one or more access permissions are inactive (e.g., disabled and / or invalid)), and outside of which time range at least one of the one or more access permissions of the shared electronic key to the one or more physical locations is inactive (e.g., not enabled and / or invalid). In some embodiments, during the process of sharing the electronic key with the second user of the second computer system, the computer system detects a third set of one or more inputs (e.g., touch input, voice command, and / or air input) specifying a first time range (e.g., 642, 644, 646, 648, 654a to 654b, and / or 652) while displaying a user interface for specifying a time range. In some embodiments, during the process of sharing the electronic key with the second user of the second computer system, in response to detecting the third set of one or more inputs specifying a time range, the computer system specifies (e.g., configures the shared electronic key so that) a first time range (e.g., a specific day, a specific hour, and / or a specific minute) during which at least one of the one or more access permissions of the shared electronic key to the one or more physical locations is active (e.g., enabled and / or valid) (and / or specifies a second time range during which the one or more access permissions are inactive (e.g., disabled and / or invalid)), and outside of the first time range, at least one of the one or more access permissions of the shared electronic key to the one or more physical locations is inactive. One or more selectable objects that display specified when access rights are active and when access rights are inactive improve the electronic key sharing process because it allows the first user to share a key but limit access rights to a specific time frame.

[0253] In some embodiments, after sharing the electronic key (e.g., before and / or while supplying the electronic key to the electronic wallet of the second computer system), the computer system detects via the one or more input devices a fourth set of one or more inputs corresponding to a request to modify one or more access rights of the shared electronic key (e.g., inputs on 674, 678a to 678d, 682, 624, 626, 688, 686, including, for example, inputs 650o, 650p1, 650p2). In some embodiments, in response to detecting a fourth set of one or more inputs corresponding to a request to modify (e.g., increase, decrease, edit and / or change) the one or more access rights of the shared electronic key, the computer system modifies (e.g., changes, deactivates and / or activates) the corresponding access rights of one or more access rights (e.g., modifies (extends or further restricts) the corresponding time range of activity of one or more access rights). Modifying the access rights after sharing the electronic key improves the security of the electronic key sharing process because the first user can modify the access rights if the electronic key is shared with an unintended recipient and / or unintended access rights. Modifying access rights after an electronic key has been shared improves the electronic key sharing process because it allows the first user to customize the permissions of the share even after the shared electronic key has been shared.

[0254] In some embodiments, during the process of sharing an electronic key with a second user of a second computer system, the computer system displays a user interface for configuring the shared electronic key to be able to be shared by the second user (with a corresponding user different from the first user and the second user, to whom the second user decides to share the shared electronic key) via a display generation component. In some embodiments, during the process of sharing an electronic key with a second user of a second computer system, when displaying a user interface for configuring the shared electronic key to be able to be shared, the computer system detects a user input (e.g., input on 624) for configuring the shared electronic key to be able to be shared by the second user via the one or more input devices. In some embodiments, during the process of sharing an electronic key with a second user of a second computer system, in response to detecting a user input for configuring the shared electronic key to be able to be shared by the second user, the computer system configures the shared electronic key to be able to be shared by the second user (e.g., the electronic hotel key can be shared by the device 800 and / or the user 806) (e.g., the second user can re-share the high-shared electronic key with a third user different from the first user and the second user). In some embodiments, the user interface for configuring the shared electronic key to be able to be shared by the second user includes a default option that the shared electronic key is not shareable. Providing the option of enabling the second user to re-share the shared electronic key improves the security of the electronic key sharing process because it provides the first user with the option to prevent the second user from re-sharing the shared electronic key. In addition, enabling the second user to share the shared electronic key improves the sharing process because it allows the first user to customize whether the second user can share the shared electronic key, which provides additional control options.

[0255] In some embodiments, after sharing the electronic key, the computer system (e.g., in response to detecting a display request via one or more input devices) displays a management user interface for the shared electronic key via a display generation component (e.g., 677), the management user interface including: based on determining that the activation code for the shared electronic key is enabled and the activation code has not been used to activate the shared electronic key (e.g., the second user has not used the activation code to activate the shared electronic key), displaying the activation code via the display generation component (e.g., in Figure 6Q 603) (and optionally, an option for transmitting the activation code to the second user); and based on determining that the activation code for the shared electronic key is enabled and the shared electronic key has been activated using the activation code (e.g., the second user has activated the shared electronic key using the activation code), canceling display of the activation code (e.g., Figure 6R603 is not displayed in the example. In some embodiments, the first computer system receives (e.g., from a server monitoring the sharing of electronic keys and / or from a second computer system) a communication regarding the status of the shared electronic key and / or whether the shared electronic key has been provisioned to the electronic wallet of the second computer system. Displaying the activation code when the shared electronic key has not yet been activated improves the electronic key sharing process because it provides the first user with the option to view the activation code (e.g., after the activation code has been transmitted and / or if the second user forgets the activation code after the activation code has been transmitted).

[0256] In some embodiments, displaying a management user interface for a shared electronic key includes displaying an option (e.g., 684) of providing a new activation code different from the activation code for the shared electronic key via a display generation component. In some embodiments, when displaying the option of providing a new activation code, the computer system detects the selection of the option of providing a new activation code via the one or more input devices. In some embodiments, in response to detecting the selection of the option of providing a new activation code: the computer system displays a new activation code for the shared electronic key via a display generation component (e.g., in response to input update 603 on 684). In some embodiments, in response to detecting the selection of the option of providing a new activation code, the computer system generates a new activation code for the shared electronic key. In some embodiments, the new activation code can be used (e.g., by a second user) to activate the shared electronic key. In some embodiments, in response to detecting the selection of the option of providing a new activation code, the first computer system configures the shared electronic key to be unable to be activated using the original activation code. In some embodiments, selecting the option of generating a new activation code disables the (original) activation code (e.g., only the new activation code will activate the shared electronic key). Displaying a new activation code that is different than a previous activation code (e.g., an activation code that has already been transmitted) improves the security of the electronic key sharing process because it provides the first user with the option to update the activation code (e.g., if the second user misplaces the activation code and / or if a malicious actor obtains the activation code).

[0257] In some embodiments, during the process of sharing an electronic key with a second user of a second computer system: the computer system displays, via a display generation component, an option to change (enable or disable) an activation code (e.g., security code and / or PIN) setting for the shared electronic key (e.g., 628). In some embodiments, the computer system displays the option to enable / disable the activation code for the shared electronic key before displaying the first selectable object. Displaying the option to enable / disable the activation code during the key sharing process improves the security of the electronic key sharing process because it enables the first user to decide whether the activation code should be used, which reduces the risk that a user other than the intended recipient can access and use the shared electronic key.

[0258] In some embodiments, during the process of sharing an electronic key with a second user of a second computer system, when the activation code for sharing the electronic key is not displayed, the computer system detects, via the one or more inputs, a selection of an option to change (enable or disable) an activation code setting for sharing the electronic key. In some embodiments, during the process of sharing an electronic key with a second user of a second computer system, in response to detecting a selection of an option to change an activation code setting for the shared electronic key, based on determining that the selection of the option to change the activation code setting for the shared electronic key is enabled, the activation code (e.g., alphanumeric text and / or image) for the shared electronic key is enabled: the computer system enables the activation code for the shared electronic key; and the computer system concurrently displays the option to change the activation code setting for the shared electronic key and the activation code (e.g., alphanumeric text and / or image) for the shared electronic key via a display generation component (e.g., when the activation code enable indication 628 is enabled, the device 600 and / or the device 800 displays the indication 603 and the activation code enable indication 628; and / or when the activation code enable indication 628 is enabled, the device 600 and / or the device 800 displays the activation code enable indication 628 and does not display the indication 603). In some embodiments, in response to detecting a selection of an option to change an activation code setting for a shared electronic key and based on determining that the selection of the option to change the activation code setting for the shared electronic key is disabled: the activation code for the shared electronic key is disabled, and the option to change the activation code setting for the shared electronic key is displayed via the display generation component without displaying the activation code for the shared electronic key (e.g., alphanumeric text and / or image). When the activation code provides visual feedback to the user about what the activation code is, the activation code is automatically displayed, thereby providing improved visual feedback.

[0259] In some embodiments, displaying an option to change (enable or disable) an activation code (e.g., security code and / or PIN) setting for sharing an electronic key includes: based on determining that the request to share the electronic key satisfies a first set of sharing conditions (e.g., what technology, application, and / or recipient, including, for example, 620a to 620d, is selected by the first user 606 and / or the second user 806 in the communication options user interface 618) (e.g., selecting a particular type of user and / or selecting a particular type of application through which the electronic key is shared), the option to change the activation code setting for sharing the electronic key is disabled by default; and based on determining that the request to share the electronic key does not satisfy the first set of sharing conditions, the option to change the activation code setting for sharing the electronic key is enabled by default. Automatically enabling and / or disabling the activation code based on whether the first set of sharing conditions is met improves the computer system because the operation is performed when a set of conditions has been met without further user input. Additionally, automatically enabling and / or disabling the activation code based on whether the first set of sharing conditions are met increases the security of sharing the shared electronic key because the first computer system automatically enables the activation code based on how the user has decided to share the electronic key.

[0260] In some embodiments, the first set of sharing conditions includes a first sharing condition that is satisfied when the second user is a known user (e.g., a user associated with affordance 620a and / or 820a). Automatically enabling and / or disabling activation codes based on the sharing conditions that are satisfied when the first computer system identifies the second user improves the computer system because operations are performed when a set of conditions have been met without further user input. In addition, it improves the security of sharing the electronic key because the first computer system automatically enables the activation code based on how the user has decided to share the electronic key.

[0261] In some embodiments, when the second user is associated with the stored contact information (e.g., a user associated with enable representation 620a and / or enable representation 820a) (e.g., in the electronic contacts application of the first computer system), the second user is a known user. Automatically enabling and / or disabling activation codes based on sharing conditions satisfied when the second user is associated with the stored contact information improves the computer system because operations are performed without further user input when a set of conditions have been met. In addition, since an activation code is not required when the second user is associated with the stored contact information, the number of required inputs is reduced, which reduces the number of inputs required to perform the operation.

[0262] In some embodiments, when the second user corresponds to a corresponding user account of a trusted service (e.g., a service that provides end-to-end encryption, a service for which the first user also has a corresponding user account, and / or a service that provides a specific security level when transmitting a message) (e.g., both the first user 606 and the user associated with the affordance 620a have a user account for the trusted service and / or both the second user 806 and the user associated with the affordance 820a have a user account for the trusted service), the second user is a known user. In some embodiments, the first computer system receives an indication that the second computer system is associated with a user account for the service from a server associated with the service and / or from a second computer system. In some embodiments, the first computer system stores an indication of the second user of the second computer system based on previous communications between the second computer systems. Automatically enabling and / or disabling the activation code based on the shared conditions satisfied when the second user has a corresponding account for the trusted service improves the computer system because the operation is performed without further user input when a set of conditions have been met. In addition, since no activation code is required, the number of required inputs is reduced.

[0263] In some embodiments, the first set of sharing conditions includes a second sharing condition, which is satisfied when a corresponding (e.g., predetermined and / or predefined) communication application is selected to share an electronic key (e.g., based on the selection in the communication option user interface 618, including, for example, the selection of 620a to 620d and / or 820a, what application is used to share an electronic hotel key). In some embodiments, in response to detecting the one or more inputs corresponding to the request to share an electronic key and in response to detecting a request to share an electronic key using a first application, the first computer system enables an activation code. In some embodiments, in response to detecting the one or more inputs corresponding to the request to share an electronic key and in response to detecting a request to share an electronic key using a second application different from the first application, the first computer system disables the activation code. Automatically enabling and / or disabling the activation code based on the sharing conditions satisfied at the corresponding time improves the computer system because the operation is performed without further user input when a set of conditions has been met. In addition, it reduces the number of required inputs because no activation code is required when the corresponding communication application is selected to share an electronic key (e.g., if the corresponding communication application has been determined to meet a specific security level), which reduces the number of inputs required to perform the operation.

[0264] In some embodiments, after sharing the electronic key, the computer system receives an indication that the second user shares the shared electronic key with a third user who is different from the second user and the first user. In some embodiments, in response to receiving an indication that the second user shares the shared electronic key with the third user, the computer system displays an indication (e.g., 678a to 678d and / or 688) that the second user shares the shared electronic key via a display generation component. In some embodiments, the indication that the second user shares the shared electronic key includes a representation of the third user. In some embodiments, the first computer system receives an indication that the second user shares the shared electronic key from a shared server that monitors the shared electronic key and / or from a second computer system. The indication that the second user has shared the shared electronic key with the third user improves the security of the key sharing process, because the first user can view who has access rights to the physical location. In addition, it provides visual feedback that the shared electronic key has been shared, which provides improved visual feedback.

[0265] In some embodiments, while displaying the indication that the second user shares the shared electronic key, the computer system detects the selection of the indication that the second user shares the shared electronic key via the one or more input devices. In some embodiments, in response to detecting the selection of the indication that the second user shares the shared electronic key, the computer system displays a management user interface (e.g., 677) for sharing the electronic key via the display generation component, the management user interface including options (e.g., 624, 626, and / or 686) that, when selected, modify (e.g., change, deactivate, and / or activate) one or more access rights shared by the second user with the third user (including the corresponding time range during which the one or more access rights are active). In some embodiments, the second user shares the shared electronic key with a subset of the one or more access rights shared by the first user with the second user (e.g., the first access right but not the second access right). In some embodiments, the second user shares the shared electronic key with all one or more access rights received from the first user. Displaying a second set of one or more selectable objects that modify the one or more access rights shared by the second user with the third user when selected improves the security of the key sharing process (e.g., how the computer system shares the electronic key) because the first user can modify the access rights shared by the second user.

[0266] In some embodiments, in response to the completion of the process of sharing the electronic key without the activation code being enabled, the first computer system displays a user interface for sharing the electronic key with an option to manage the shared electronic key. In some embodiments, in response to the completion of the process of sharing the electronic key with the activation code being enabled, the first computer system forgoes displaying the user interface for sharing the electronic key with an option to manage the shared electronic key.

[0267] In some embodiments, the user interface of the electronic wallet application includes a representation of the electronic key, and based on determining that the electronic key can be shared, also includes an option for sharing the key; and based on determining that the electronic key cannot be shared, does not display the option for sharing the key.

[0268] In some embodiments, the user interface of the electronic wallet application includes a representation of the electronic key and also includes options for managing the shared electronic key once the electronic key has been shared.

[0269] In some embodiments, when a recipient is selected for key sharing and the recipient does not have an account with the trusted service, the computer system displays an option to enable an activation code for sharing the electronic key.

[0270] In some embodiments, access permissions for an electronic key (e.g., an original electronic key and / or a shared electronic key) can be modified remotely (e.g., by the issuer of the original electronic key and / or by a user logged into the issuer's application and / or website).

[0271] It should be noted that the process described above with respect to method 700 (eg Figure 7 ) also apply in a similar manner to the methods described below. For example, method 900 optionally includes one or more of the features of the various methods described above with reference to method 700. For example, method 900 may include an interface for displaying method 700, the interface including techniques for sharing (e.g., re-sharing) and / or configuring access rights (including time limits), techniques for enabling and / or disabling access codes, and / or techniques for managing shared access rights. For the sake of brevity, these details are not repeated below.

[0272] FIG. 8A to FIG. 8L Illustrated are exemplary user interfaces for access rights provided by an electronic key according to some embodiments. The user interfaces in these figures are used to illustrate the process described below, including Fig. 9 In some embodiments, device 600 includes one or more features of devices 100, 300, 500, and / or 600.

[0273] exist Fig. 8A At the device 800, an instant messaging interface 802 is displayed on the display 801, and the instant messaging interface includes Figure 6L The instant messaging interface 802 includes a dialog box that is displayed by the device 600 in response to the instant messaging interface 606a. Figure 6L800. Message 804 includes key representation 604 and add affordance 805. Add affordance 805 allows the user to initiate the process of adding an electronic hotel key to the digital wallet of device 800. While displaying instant messaging interface 802, device 800 detects tap input 850a directed to add affordance 805. In response to detecting tap input 850a, device 800 displays main add interface 808, such as Figure 8B As depicted in .

[0274] exist Figure 8B At the main add interface 808, the main add interface 808 includes an add activation code enable indication 810 and a continue enable indication 809. As shown, the continue enable indication 809 is disabled, thereby preventing the second user 806 from adding the shared electronic hotel key to the digital wallet of the device 800. While displaying the main add interface 808, the device 800 detects a tap input 850b directed to the add activation code enable indication 810. In response to detecting the tap input 850b, the device 800 displays a user interface and / or an enable indication to allow the user to enter an activation code.

[0275] exist Figure 8C At 800, after the device 800 detects the input of the activation code, the main add interface 808 includes an indication 603 of the activation code. As shown, the continued enable indication 809 is enabled, thereby allowing the second user 806 to add the shared electronic hotel key to the digital wallet of the device 800. In some embodiments, the second user 806 is on a communication channel and / or in a communication application other than an instant messaging application (e.g., in response to selecting Fig.6O The call indication indicates that the activation code is received in the telephone call initiated by 673.

[0276] exist Figure 8C , main add interface 808 also includes view access level affordance 812. View access level affordance 812 allows a user to view a read-only (e.g., non-editable) version of the access rights shared with device 800. While displaying main add interface 808, device 800 detects tap input 850c1 directed to view access level affordance 812. In response to detecting tap input 850c1, device 800 displays access level interface 814, such as Fig.8D While displaying the main add interface 808, the device 800 detects a tap input 850c2 directed to the continue enable indication 809. In response to detecting the tap input 850c2, the device 600 supplies the shared electronic hotel key to the device 800 and displays the wallet user interface 819, as shown in FIG. Fig. 8E As depicted in .

[0277] exist Fig.8DAt 814, the access level interface 814 includes a read-only version of the access rights shared with the device 800. The access rights of the access level interface 814 include the access rights that are shared by the device 600 in response to detecting the access rights. Fig. 6F The access level editing user interface 632 and / or FIG. 6J to FIG. 6I 815, 817 of the access rights (including time limits) configured in response to the selection of the affordance in the time limit user interface 640. In some embodiments, the access level interface 814 does not include an indication of unshared access rights (e.g., indication 815a disabling access to room 203). In some embodiments, the device 800 displays a read-only version of the time limit for the shared access rights in response to detecting the selection of the time limit affordance 816.

[0278] exist Fig. 8E In response to detecting Figure 8C Input 850c2 in the device 800, the wallet user interface 819 is displayed. The wallet user interface 819 includes representations of different electronic cards, including electronic hotel keys, electronic identification cards, electronic commuter cards, electronic credit cards, and electronic movie tickets. As shown in the figure, similar to the reference Fig. 6A With the described techniques, sharing the electronic hotel key gives the second user 806 access to the secure door 610 (eg, after user authentication at the device 800).

[0279] exist Fig. 8E At the time when the wallet user interface 819 is displayed, the device 800 detects that the user is pointing to Fig. 8E In response to detecting the tap input 850e, the device 800 displays the wallet user interface 819, such as Figure 8F As depicted in .

[0280] exist Figure 8F At 800, the device 800 displays a wallet user interface 819 for sharing electronic hotel keys, similar to Figure 6B The wallet user interface 602 of FIG. 819 includes a share icon 616, similar to the reference Figure 6B While displaying the wallet user interface 819 for the electronic hotel key, the device 800 detects a tap input 850f directed to the share icon 616. In response to detecting the tap input 850f, the device 800 displays the communication options user interface 618, such as Figure 8G As depicted in .

[0281] exist Figure 8G Department, Figure 8G The communication options user interface 618 in the Figure 6C, but in a different state (e.g., in some embodiments, with different contacts and / or communication applications). While displaying communication options user interface 618, device 800 detects tap input 850g directed to affordance 820a, which affordance is associated with initiating a process of re-sharing the electronic hotel key with Sarah using the email application. In response to detecting tap input 850g, device 800 displays key sharing user interface 622, as shown in FIG. Figure 8H As depicted in .

[0282] exist Figure 8H Department, Figure 8H The key sharing user interface 622 in is similar to Fig. 6E The key sharing user interface 622. As shown in the figure, Figure 8H The key sharing user interface 622 includes an enabled re-sharing indication 624, an access level indication 626, and an enabled activation code indication 628. Figure 8H The key sharing user interface 622 in the embodiment also includes an indication of an activation code 603. The device 800 automatically enables the activation code enable indication 628 based on how the electronic key will be shared (e.g., which communication application). In some embodiments, the activation code enable indication 628 is automatically enabled based on the device 800 receiving an indication that the device receiving the electronic key also has an account of the entity that provides the communication channel in the key to be transferred (e.g., both the transmitting user and the intended recipient have user accounts for the same service).

[0283] It is worth noting that Figure 8H Instruction 603 includes the same Fig. 8E 603 in the indication. In some embodiments, the activation codes are the same. For example, in some embodiments, the entity that issues the electronic key configures the activation code. In such embodiments, when the electronic key is shared (by the original key holder such as the first user 606, or by a user who receives the key from the original key holder such as the second user 806), the activation code is the same. In some embodiments, the device (e.g., the device's digital wallet) generates and / or receives (e.g., from a server) the activation code during the process of re-sharing the electronic hotel key. While displaying the key sharing user interface 622, the device 800 detects a tap input 850h directed to the access level enable indication 626. In response to detecting the tap input 850h, the device 800 displays the access level editing user interface 632, as shown Figure 8I As depicted in .

[0284] exist Figure 8I middle, Figure 8I The access level editing user interface 632 in is similar to Fig. 6F The access level editing user interface 632 of the second user 806 is displayed, but with a different state (e.g., based on the access rights shared with the second user 806). Figure 8I The access level editing user interface 632 in allows the second user 806 to modify (e.g., further restrict) the access rights shared with the second user 806. It is worth noting that Figure 8I The access level editing user interface 632 in the device 800 only allows the device 800 to modify the access rights enabled at the device 600. For example, the device 800 may enable and / or disable the exclusion room enabling representation 634a (which is displayed by the device 600 in response to Fig. 6F Room affordance 634a is displayed with a different appearance based on being disabled (e.g., not configurable by device 800). In some embodiments, room affordance 634a is not displayed. In other words, in some embodiments, access rights that are disabled (and / or not shared) are not displayed at device 800.

[0285] exist Figure 8I At , access level editing user interface 632 allows second user 806 to modify other access permissions shared using affordance 636 and time limit affordance 638. In some embodiments, in response to detecting selection of time limit affordance 638, device 800 displays a screen similar to FIG. 6J to FIG. 6I In some embodiments, device 800 modifies the time limit to limit access rights to 3:00 p.m. to 5:00 p.m., which is a shorter time range than the access rights of device 600 (e.g., as shown in FIG. 1 ). Fig.6I 9am to 5pm as described).

[0286] exist Figure 8I At, in display Figure 8I When access level editing user interface 632 is displayed at device 800, device 800 detects tap input 850i1 directed to room affordance 634b. In response to detecting tap input 850i1, device 800 disables room affordance 634b. Thus, when device 800 shares an electronic hotel key with a device associated with a different user (e.g., Sarah), when the key is added to the digital wallet of the device, the user associated with the receiving device will be unable to access neither room 203 (which is disabled by device 800) nor room 205 (which is disabled by device 600).

[0287] exist Figure 8I When the display Figure 8IWhen access level editing user interface 632 is displayed at the device 800, the device 800 detects a tap input 850i2 directed to the affordance 822. In response to detecting the tap input 850i2, the device 800 displays the key sharing user interface 622, such as Figure 8J As depicted in .

[0288] exist Figure 8J At , while displaying key sharing user interface 622, device 800 detects a tap input 850j directed to continue enabling indication 656. In response to detecting tap input 850j, device 800 initiates a process of authenticating second user 806 (e.g., using facial recognition, using fingerprints, and / or using a password). In some embodiments, device 800 displays a screen similar to Figure 6K Face authentication notification in 659 Face authentication notification in 659.

[0289] exist Figure 8K At , device 800 has successfully authenticated second user 806. As a result, device 800 displays an email message interface 826 of the email application associated with affordance 820a. Figure 8K At 804, second user 806 has entered text to recipient Sarah in email 828. As shown, email 828 includes a representation of an electronic hotel key that is being shared. While displaying email message interface 826, device 800 detects tap input 850k directed to send enable indication 830. In response to detecting tap input 850k, device 800 sends email 828 to a device associated with Sarah. Notably, in some embodiments, because activation code enable indication 628 is enabled, device 800 displays an activation code interface similar to activation code interface 670 and / or a call enable indication similar to call enable indication 673, similar to the activation code interface 670 of FIG. Figures 6M to 6N Additionally, device 800 updates wallet user interface 819 of the electronic hotel key to include management affordance 674, similar to Fig.6O Describe the technology.

[0290] exist Figure 8L In response to device 600 transmitting the electronic hotel key to a device associated with Sarah, device 800 updates management user interface 676 to include affordance 678d associated with Sarah. Figure 6P and Figure 6R As discussed, device 600 displays an affordance for editing the access rights re-shared by Dave and Tom. In some embodiments, in response to detecting input directed to affordance 678d at device 600, device 600 displays an individual user management interface 677 associated with Sarah, similar to the one described in reference to FIG. Figure 6P to Figure 6RThus, in some embodiments, device 600 can modify the access permissions that device 800 shares with devices associated with Sarah. In some embodiments, device 600 receives an indication that device 600 has shared a key based on communications received from device 800, a server associated with a hotel that issues electronic hotel keys, and / or a device associated with Sarah.

[0291] exist Figure 8L At , device 800 displays a management user interface 676 similar to the management user interface 676 displayed at device 600, but from the perspective of device 800. As shown, the management user interface 676 displayed by device 800 includes affordances 678a to 678c. In some embodiments, although affordances 678a to 678c are displayed, the device can only modify the access rights shared by device 800 (for example, device 800 cannot modify the access rights shared by David and Tom and / or cannot modify the access rights shared by the first user 606 and David). In some embodiments, affordances 678a to 678c allow device 800 to modify access rights not shared by device 800 (for example, device 800 can modify the access rights shared by David and Tom and / or can modify the access rights shared by the first user 606 and David). In some embodiments, the management user interface 676 displayed by device 800 includes affordances 678a. In some embodiments, management user interface 676 displayed by device 800 does not include affordances 678b-678c. In such embodiments, management user interface 676 displayed by device 800 includes (e.g., only) affordances of users with whom second user 806 shared the electronic hotel key.

[0292] exist Figure 8LIn some embodiments, the receiver (e.g., Jane) of the electronic hotel key can view the access level and / or permissions that the sender (e.g., Amy) has, optionally including viewing the access level and / or permissions that have not yet been shared with the receiver. In such embodiments, device 800 displays an affordance similar to affordances 678b to 678c associated with user 606 (e.g., Amy). In some embodiments, affordances associated with user 606 include indications of access levels and / or a set of access rights granted to device 600 (e.g., Jane can see what permissions are granted to Amy). For example, in some embodiments, device 800 displays affordances of user 606, which include indications of "full access", indicating that user 606 maintains a set of access rights granted and / or made available by the entity (e.g., hotel) of the electronic key. In such embodiments, the selection of affordances of user 606 displays an unmodifiable version (e.g., read-only version) of a set of access rights granted. In some embodiments, device 800 does not display the option of modifying the access rights in the set of access rights. In some embodiments, selection of an affordance optionally displays a Figure 8L The access level interface 814 of the access level interface. In such embodiments, the access level interface includes an indication of a set of access rights granted to the user 606 (e.g., with Figure 8L 6 ). In an embodiment where device 800 displays an affordance representation of user 606 , device 800 displays an indication to user 806 that a shared electronic hotel key has been received from user 606 .

[0293] exist Figure 8L In some embodiments, device 800 does not receive permission to share the electronic hotel key. In such embodiments, device 600 disables re-sharing enable indication 624 (e.g., as shown in reference Figure 6J Additionally or alternatively, when the electronic hotel key is initially shared with device 600, device 800 re-shares enabling indication 624 and device 600 subsequently disables re-share enabling indication 624 (e.g., as described in reference Figure 6Q described).

[0294] Fig. 9900 is a flowchart illustrating a method for re-sharing a shared electronic key using a computer system according to some embodiments. Method 900 is performed at a computer system (e.g., 100, 300, 500, 600, and / or 800) (e.g., a smart watch, a smart phone, a tablet, a head-mounted device (e.g., a head-mounted augmented reality and / or extended reality device), and / or a laptop computer) that communicates with one or more input devices (e.g., a touch-sensitive surface, a keyboard, a controller, a rotatable input device, a microphone, and / or a mouse). In some embodiments, the computer system communicates with a display generation component (e.g., 601 and / or 801) (e.g., a display controller, a touch-sensitive display system, a head-mounted display system, and / or a monitor). Some operations in method 900 are optionally combined, the order of some operations is optionally changed, and some operations are optionally omitted.

[0295] As described below, method 900 provides an intuitive way to re-share a shared electronic key. The method reduces the cognitive burden of re-sharing a shared electronic key on the user, thereby creating a more efficient human-machine interface. For battery-powered computing devices, enabling users to re-share a shared electronic key more quickly and efficiently saves power and increases the time interval between battery charges.

[0296] When a first computer system is associated with a first user (e.g., 606 and / or 806) (e.g., corresponds to a first account of the first user, is being used by the first account of the first user, and / or is logged in by the first account of the first user), the computer system receives (902) first information from a second user (e.g., 606 and / or 806) on a second computer system (e.g., 100, 300, 500, 600, and / or 800) different from the first user of the first computer system (e.g., a remote computer system, an external computer system, a computer system associated with a second user different from the first user, a smart phone, a tablet computer, a laptop computer, and / or a desktop computer) that is associated with the first user, the first information relating to an electronic key (e.g., a key that is stored in the electronic wallet) to be provisioned to (or optionally stored in) an electronic wallet (e.g., 602 and / or 818) of the first computer system associated with the first user (e.g., the electronic wallet includes credentials for one or more accounts (e.g., a transportation account, a payment account, a loyalty account, electronic keys, and / or airline tickets), electronic keys that can be accessed using the wallet, and / or electronic keys that are stored and / or saved in the wallet). FIG. 6A to FIG. 6R and / or FIG. 8A to FIG. 8LAn electronic hotel key (e.g., credentials for an electronic card key and / or credentials for accessing a key account) (e.g., a shared electronic key and / or an electronic key shared between at least two different users), wherein the electronic key provides a first set of access rights (e.g., access rights associated with the affordances (e.g., 634 and / or 636) in the access level editing user interface 632 and / or time limits associated with affordances (e.g., 642, 644, 646, and / or 648) in the time limit user interface 640) to one or more physical locations (e.g., 610 and / or a physical location associated with affordance 634 in the access level editing user interface 632) (e.g., the electronic key unlocks a physical lock and / or door). In some embodiments, the physical location is a secure area (e.g., in a building (e.g., a room, an elevator, and / or a laundry machine), an outdoor area (e.g., a gated area, an outdoor pool, and / or a private driveway), and / or a vehicle (e.g., a car or truck)). In some embodiments, the one or more access rights include temporary access rights (e.g., one or more access rights are valid for a corresponding time range). In some embodiments, after the electronic key is provisioned to the electronic wallet, the electronic wallet includes a visual representation of the electronic key. In some embodiments, the electronic wallet includes credentials for one or more accounts (e.g., a transportation account, a payment account, a loyalty account, an electronic key, and / or an airline ticket), one or more electronic cards different from the electronic key (e.g., an electronic credit card and / or an electronic ticket). In some embodiments, the electronic wallet includes one or more visual representations of the one or more accounts.

[0297] In some embodiments, the computer system supplies (904) the electronic key to the electronic wallet of the first computer system using the first information about the electronic key. In some embodiments, after supplying the electronic key to the electronic wallet of the first computer system, the computer system detects (906) a request to share the electronic key with a third user (e.g., a user associated with the enablement representation 820a and / or the enablement representation 620a) different from the first user and the second user via one or more input devices, wherein the request to share the electronic key with the third user specifies a second set of access rights for the shared electronic key (e.g., access rights associated with the enablement representation (e.g., 634 and / or 636) in the access level editing user interface 632 and / or a time limit associated with the enablement representation (e.g., 642, 644, 646, and / or 648) of the time limit user interface 640) (e.g., the same as or different from the first set of access rights). In some embodiments, the second set of access rights is a subset of the first set of access rights (including the first access rights but not the second access rights). In some embodiments, the first set of access rights includes access rights that are not included in the second set of access rights. In some embodiments, the second set of access permissions does not include access permissions that were not included in the first set of access permissions (eg, a user cannot re-share access permissions that were not originally shared with the user).

[0298] In some embodiments, in response to detecting a request to share an electronic key with a third user, the computer system initiates (908) (e.g., starts, causes, and / or executes a transfer command) a process of sharing an electronic key having a second set of access permissions with a third user (e.g., a remote computer system, an external computer system, a computer system associated with a user different from the user associated with the first computer system, a smart phone, a tablet computer, a laptop computer, and / or a desktop computer) that is different from the first computer system and the second computer system. Initiating the process of sharing a received electronic key in response to a request to share an electronic key with a third user (wherein the request specifies a second set of access permissions) improves the computer system because it allows the first user to re-share an electronic key received from the second user, which improves the electronic key sharing process (e.g., how the computer system re-shares a shared electronic key) and how the computer system provides access to a physical location.

[0299] In some embodiments, after sharing the electronic key (and / or when the shared electronic key is supplied to the electronic wallet of the third computer system), the computer system keeps supplying the electronic key on the electronic wallet of the first computer system (e.g., the electronic wallet of the device 600 and / or the device 800 stores the electronic hotel key after sharing) (e.g., so that the first user of the first computer system keeps the first set of access rights to one or more physical locations). In some embodiments, after sharing the electronic key, the first computer system receives the user input of the credential for accessing the electronic key, and after authenticating the first user (e.g., by a password and / or by biometric authentication), the computer system releases the credential of the electronic key from the security element of the first computer system. In some embodiments, the first computer system (e.g., via NFC) transmits the credential to a contactless terminal. In some embodiments, the credential of the electronic key is stored in the security element because the electronic key is supplied to the electronic wallet of the first computer system. Continuing to retain the electronic key in the electronic wallet of the first computer system improves the computer system because it allows the first user to retain access rights to one or more physical locations while still allowing the first user to share those rights with a third user, which improves the electronic key sharing process (e.g., how the computer system re-shares shared electronic keys) and how the computer system provides access to physical locations.

[0300] In some embodiments, the second set of access rights includes a subset of access rights that is smaller than the first set of access rights (e.g., the device 800 disables access rights associated with the room enable representation 634b) (e.g., the second set of access rights does not include access rights included in the first set of access rights) (e.g., where the second set of access rights includes at least one access right having a smaller time range than the time range of the corresponding access right in the first set of access rights, e.g., when the first user further restricts the time range of the access rights included in the first set of access rights). Sharing a shared electronic key with a subset of access rights rather than access rights received from a second user improves the computer system because it allows the first user to further restrict access rights to one or more physical locations while still allowing the first user to share other rights with a third user, which improves the electronic key sharing process (e.g., how the computer system reshares a shared electronic key) and how the computer system provides access to physical locations.

[0301] In some embodiments, the request to share the electronic key with the third user specifies a first time range (e.g., a range of specific days, a range of specific hours, and / or a range of specific minutes) and a second time range different from the first time range (e.g., 642, 644, 646, 648, 654a to 654b, and / or 652), during which at least one access right in the second set of access rights is activated, and during which at least one access right in the second set of access rights is deactivated. In some embodiments, at least one access right is included in the first set of access rights and does not have a time range in which the at least one access right is deactivated when received (e.g., when the second user shares the at least one access right with the first user, the second user does not limit the time range in which the at least one access right is active). Sharing an electronic key received from a second user with access rights limited to a specific time range improves a computer system because it allows the first user to further limit access rights by limiting the time range in which they are active, while still allowing the first user to share other rights with a third user, which improves the electronic key sharing process (e.g., how the computer system reshares the shared electronic key) and how the computer system provides access to a physical location.

[0302] In some embodiments, the second user receives information about an electronic key from a fourth user of a fourth computer system (e.g., 100, 300, and / or 500) that is different from the first user, the second user, and the third user (e.g., the first user 606 receives an electronic hotel key from another user) (e.g., the first user receives the electronic key because the second user reshared the key that the second user received from the fourth user). In some embodiments, the fourth user has shared the electronic key with the second user, and the second user is resharing the electronic key with the first user. Allowing the second user to reshare the electronic key received from the fourth user improves the computer system because it allows the second user to share access rights to one or more physical locations that the second user received from the fourth user, which improves the electronic key sharing process (e.g., how the computer system shares electronic keys) and how the computer system provides access to physical locations.

[0303] In some embodiments, the first user cannot share access rights that are not included in the first set of access rights as part of sharing the electronic key (e.g., the first user 606 and / or the second user 806 cannot share access rights that are not shared with the device 600 and / or 800). In some embodiments, the second set of access rights does not include access rights that are not included in the first set of access rights (e.g., the first user cannot share access rights that have not been received from the second user). Allowing the first user to reshare only those access rights received from the second user improves the computer system because it does not allow the first user to expand rights beyond those shared by the second user, which improves the security of the electronic key sharing process (e.g., how the computer system reshares the shared electronic key) and how the computer system provides access to physical locations.

[0304] In some embodiments, the first computer system activates the computer using a first activation code (e.g., Figure 8C 603 in the first computer system) (e.g., supplying the electronic key to the electronic wallet of the first computer system), and during the process of sharing the electronic key with the third user, the computer system displays a second activation code different from the first activation code via the display generation component (e.g., Figure 8H 603) for activating the shared electronic key. In some embodiments, the first user uses a first activation code to provision the electronic key to the electronic wallet of the first computer system, and the first computer system displays a second activation code (different from the first activation code) that the first user should share with a third user to enable the third user to activate the shared electronic key. Displaying a representation of an activation code different from the activation code used to provision the electronic key to the electronic wallet of the first computer system improves the computer system because it prevents the risk that a malicious actor can use an old activation code to use and / or save the electronic key, which improves the security of the electronic key sharing process (e.g., how the computer system re-shares the shared electronic key) and how the computer system provides access to a physical location.

[0305] In some embodiments, before the electronic key is provisioned to the electronic wallet of the first computer system, the computer system (e.g., in response to a request to view the first set of access rights) displays an unmodifiable (e.g., read-only and / or cannot be edited) representation of the first set of access rights (e.g., access rights associated with 815, 817, and / or 816 displayed in the access level interface 814) (e.g., the user can view the first set of access rights but cannot modify the first set of access rights before the electronic key is provisioned to the electronic wallet of the first computer system). Displaying a read-only version of the first set of access rights improves the computer system because it provides visual feedback of the rights received from the second user, which provides improved visual feedback of receiving the access rights and improves how the computer system shares the electronic key.

[0306] In some embodiments, supplying an electronic key to an electronic wallet of a first computer system includes: supplying an electronic key to an electronic wallet of a first computer system using a third activation code (e.g., an access code specified by an issuer of the electronic key, a vehicle manufacturer and / or a supplier and / or an access code not specified by an issuer and / or a supplier of the electronic key) by the first computer system (e.g., the same or different from the first activation code and / or the activation code entered by the first user); and detecting by the first computer system that an external device (e.g., a key card and / or a computer system associated with a vehicle) is within a threshold proximity of the first computer system (e.g., within a threshold distance and / or within a threshold communication range) (e.g., based on determining that one or more wireless communications (e.g., using Bluetooth, NFC and / or communications with location information) are detected. In some embodiments, the external device provides access rights to one or more physical locations (e.g., associated with a first set of access rights and / or not associated with a first set of access rights). In some embodiments, the electronic key cannot be supplied to the electronic wallet of the computer system if the external device is not within a threshold proximity of the first computer system and does not have access to the third activation code. In some embodiments, the third activation code is a vehicle code and / or a vehicle-specific activation code. Detecting the proximity of an external device improves the computer system because it prevents the risk that a malicious actor could use an old activation code to use and / or save an electronic key, which improves the security of the electronic key sharing process (e.g., how the computer system re-shares shared electronic keys) and how the computer system provides access to physical locations.

[0307] In some embodiments, the computer system (e.g., before and / or after provisioning the electronic wallet on the first computer system) detects, via one or more input devices, a request to view a set of access permissions that are not shared by the second user. In some embodiments, in response to the request to view a set of access permissions that are not shared by the second user, the computer system displays an unmodifiable (e.g., read-only and / or cannot be edited) representation of the set of access permissions that are not shared by the second user (e.g., Figure 8I 815a and / or 634a in (e.g., the user can view the set of access rights but cannot modify and / or share the set of access rights that are not shared by the second user). Displaying an unmodifiable representation of the set of access rights that are not shared improves the computer system because it provides visual feedback of the access rights that were not received from the second user, which provides improved visual feedback of what access rights were not received, allowing the first user to request shared access rights and improving how the computer system shares electronic keys.

[0308] Note that the above description is relative to method 900 (eg, Fig. 9 ) also apply in a similar manner to the methods described above. For example, method 700 optionally includes one or more of the characteristics of the various methods described above with reference to method 900. For example, method 700 may include an interface for displaying method 700, which includes techniques for adding electronic keys, techniques for resharing and / or reconfiguring access rights (including time restrictions), techniques for enabling and / or disabling access codes, and / or techniques for managing shared access rights. For the sake of brevity, these details are not repeated herein.

[0309] For the purpose of explanation, the preceding description is described by reference to specific embodiments. However, the above exemplary discussion is not intended to be exhaustive or limit the invention to the disclosed precise form. According to the above teachings, many modifications and variations are possible. These embodiments are selected and described in order to best explain the principles of these technologies and their practical applications. Others skilled in the art can thus best utilize these technologies and various embodiments with various modifications suitable for the intended specific use.

[0310] Although the disclosure and examples have been fully described with reference to the accompanying drawings, it should be noted that various changes and modifications will become apparent to those skilled in the art. It should be understood that such changes and modifications are considered to be included within the scope of the disclosure and examples defined by the claims.

[0311] As described above, one aspect of the present technology is to collect and use data from various sources to improve the process of sharing electronic keys. The present 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, social network IDs, home addresses, data or records related to the user's health or fitness level (e.g., vital sign measurements, medication information, exercise information), date of birth, or any other identifying or personal information.

[0312] 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 facilitate sharing of electronic keys. Therefore, the use of such personal information data enables users to exercise planned control over shared electronic keys. 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.

[0313] 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.

[0314] 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 elements and / or software elements to prevent or block access to such personal information data. For example, with respect to shared electronic keys, 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 registration for the service or at any time thereafter. In another example, a user may choose not to provide data for the electronic key sharing service. 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, a user may be notified that their personal information data will be accessed when downloading an application, and then be reminded again just before the personal information data is accessed by the application.

[0315] In addition, it is the intention of the present disclosure 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 data collection and data deletion. In addition, and when applicable, including in certain health-related applications, data de-identification can be used to protect the privacy of users. De-identification can be facilitated by removing specific identifiers (e.g., date of birth, etc.), controlling the amount or specificity of 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.

[0316] 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, the 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, information about a shared electronic key may be selected and delivered to a user by inferring preferences 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 content electronic key sharing service, or publicly available information.

Claims

1. A method, comprising: At a first computer system in communication with a display generation component and one or more input devices: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, while the first computer system is associated with a first user, wherein the electronic key provides one or more access rights to one or more physical locations; and In response to detecting the set of one or more inputs corresponding to the request to share the electronic key: Initiating a process of sharing the electronic key with the second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system comprises: Based on determining that the activation code for the shared electronic key is enabled, displaying, via the display generation component, a first selectable object for initiating a process of transmitting the activation code; and Based on determining that the activation code for the shared electronic key is disabled, displaying the first selectable object for initiating the process of transmitting the activation code is abandoned.

2. The method according to claim 1, further comprising: detecting, via the one or more input devices, a second set of one or more inputs, the second set of one or more inputs comprising input directed to the first selectable object; as well as In response to detecting the second set of one or more inputs, the activation code is transmitted to the second user.

3. The method according to any one of claims 1 to 2, further comprising: detecting, via the one or more input devices, a selection of the first selectable object; in response to detecting a selection of the first selectable object, initiating the process of transmitting the activation code, including displaying a dialog between the first user and the second user; while displaying the conversation between the first user and the second user, detecting, via the one or more input devices, a selection of an option to transmit the activation code to the second user; as well as In response to detecting a selection of the option to transmit the activation code to the second user, the activation code is transmitted to the second user as part of the conversation between the first user and the second user.

4. The method according to any one of claims 1 to 3, further comprising: During the process of sharing the electronic key with the second user of the second computer system: Based on determining that the activation code for the shared electronic key is enabled, displaying via the display generation component concurrently with the first selectable object a second selectable object for initiating the process of transmitting the activation code; and based on determining that the activation code for the shared electronic key is disabled, forgoing displaying the second selectable object for initiating the process of transmitting the activation code; as well as detecting object selection user input via the one or more input devices while the first selectable object and the second selectable object are displayed concurrently; as well as In response to detecting the object selection user input: initiating said process of transmitting said activation code using a first communication technology based on determining that said object selection user input corresponds to a selection of said first selectable object; as well as Based on determining that the object selection user input corresponds to a selection of the second selectable object, the process of transmitting the activation code using a second communication technology different from the first communication technology is initiated.

5. The method according to any one of claims 1 to 4, further comprising: During the process of sharing the electronic key with the second user of the second computer system: displaying, via the display generation component and concurrently with the first selectable object, a third selectable object for copying the activation code based on determining that the activation code for the shared electronic key is enabled; as well as based on determining that the activation code for the shared electronic key is disabled, abandoning displaying a third selectable object for copying the activation code; detecting object selection user input via the one or more input devices while concurrently displaying the first selectable object and the third selectable object; as well as In response to receiving the object selection user input: initiating said process of transmitting said activation code using a first communication technology but without copying said activation code based on determining that said object selection user input corresponds to a selection of said first selectable object; as well as Based on determining that the object selection user input corresponds to a selection of the third selectable object, the activation code is copied but the process of transmitting the activation code is not initiated using the first communication technology. 6 . The method according to claim 1 , wherein a second computer system uses the activation code to activate the shared electronic key.

7. The method according to any one of claims 1 to 6, further comprising: During the process of sharing the electronic key with the second user of the second computer system: displaying, via the display generation component, a user interface for specifying a time range for the shared electronic key, during which at least one of the one or more access rights to the one or more physical locations is active for the shared electronic key, and outside of which the at least one of the one or more access rights to the one or more physical locations is inactive for the shared electronic key; while displaying the user interface for specifying the time range, detecting a third set of one or more inputs specifying the first time range; as well as In response to detecting the third set of one or more inputs specifying the time range, specifying the first time range, during which at least one of the one or more access rights of the shared electronic key to the one or more physical locations is active, and outside of the first time range, at least one of the one or more access rights of the shared electronic key to the one or more physical locations is inactive.

8. The method according to any one of claims 1 to 7, further comprising: After sharing the electronic key, detecting, via the one or more input devices, a fourth set of one or more inputs corresponding to a request to modify the one or more access permissions of the shared electronic key; as well as In response to detecting the fourth set of one or more inputs corresponding to the request to modify the one or more access rights of the shared electronic key, a corresponding access right of the one or more access rights is modified.

9. The method according to any one of claims 1 to 8, further comprising: During the process of sharing the electronic key with the second user of the second computer system: displaying, via the display generation component, a user interface for configuring the shared electronic key to be shareable by the second user; while displaying the user interface for configuring the shared electronic key to be shareable, detecting, via the one or more input devices, a user input for configuring the shared electronic key to be shareable by the second user; as well as In response to detecting the user input for configuring the electronic key to be shared so as to be shareable by the second user, the electronic key to be shared is configured so as to be shareable by the second user.

10. The method according to any one of claims 1 to 9, further comprising: After the electronic key is shared, a management user interface for the shared electronic key is displayed via the display generation component, including: displaying the activation code via the display generation component based on determining that the activation code for the shared electronic key is enabled and the shared electronic key has not been activated using the activation code; and Based on determining that the activation code for the shared electronic key is enabled and the shared electronic key has been activated using the activation code, displaying the activation code is abandoned.

11. The method according to any one of claims 1 to 10: wherein displaying the management user interface for the shared electronic key includes displaying, via the display generation component, an option to provide a new activation code different from the activation code for the shared electronic key; detecting, via the one or more input devices, a selection of the option to provide the new activation code while displaying the option to provide the new activation code; and In response to detecting selection of the option to provide the new activation code: The new activation code for the shared electronic key is displayed via the display generation component.

12. The method according to any one of claims 1 to 11, further comprising: During the process of sharing the electronic key with the second user of the second computer system: An option for changing an activation code setting for the shared electronic key is displayed via the display generation component.

13. The method according to claim 12, further comprising: During the process of sharing the electronic key with the second user of the second computer system: detecting, via the one or more inputs, a selection of the option for changing the activation code setting for the shared electronic key when the activation code for the shared electronic key is not displayed; as well as In response to detecting a selection of the option for changing the activation code setting for the electronic key being shared: enabling the activation code for the shared electronic key based on determining the selection of the option for changing the activation code setting for the shared electronic key: enabling the activation code for the shared electronic key; as well as The option for changing the activation code setting for the shared electronic key and the activation code for the shared electronic key are concurrently displayed via the display generation component.

14. The method of any one of claims 12 to 13, wherein displaying the option for changing the activation code setting for the shared electronic key comprises: upon determining that the request to share the electronic key satisfies a first set of sharing conditions, changing the option for setting the activation code for the electronic key being shared by default to disable the activation code for the electronic key being shared; as well as Based on a determination that the request to share the electronic key does not satisfy the first set of sharing conditions, the option to change the activation code setting for the electronic key being shared defaults to the activation code for the electronic key being shared being enabled.

15. The method of claim 14, wherein the first set of sharing conditions comprises a first sharing condition that is satisfied when the second user is a known user.

16. The method of claim 15, wherein the second user is a known user when the second user is associated with the stored contact information.

17. The method according to any one of claims 15 to 16, wherein the second user is a known user when the second user corresponds to a respective user account of a trusted service.

18. The method according to any one of claims 14 to 17, wherein the first set of sharing conditions includes a second sharing condition that is satisfied when a corresponding communication application is selected to share the electronic key.

19. The method according to any one of claims 1 to 18, further comprising: After sharing the electronic key, receiving an instruction from the second user to share the shared electronic key with a third user different from the second user and the first user; as well as In response to receiving the indication that the second user shares the shared electronic key with the third user, the indication that the second user shares the shared electronic key is displayed via the display generation component.

20. The method according to claim 19, further comprising: while displaying the indication that the second user shares the shared electronic key, detecting, via the one or more input devices, a selection of the indication that the second user shares the shared electronic key; as well as In response to detecting a selection of the indication that the second user is sharing the shared electronic key, a management user interface for the shared electronic key is displayed via the display generation component, the management user interface including an option to modify one or more access permissions shared by the second user with the third user when selected.

21. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first computer system that communicates with a display generation 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 20.

22. A first computer system configured to communicate with a display generation component and one or more input devices, the first computer system comprising: 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 comprising instructions for executing the method according to any one of claims 1 to 20.

23. A first computer system configured to communicate with a display generation component and one or more input devices, the first computer system comprising: A component for carrying out the method according to any one of claims 1 to 20.

24. A computer program product comprising one or more programs configured to be executed by one or more processors of a first computer system in communication with a display generation 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 20.

25. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations, when the first computer system is associated with a first user; as well as In response to detecting the set of one or more inputs corresponding to the request to share the electronic key: Initiating a process of sharing the electronic key with the second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system comprises: Based on determining that the activation code for the shared electronic key is enabled, displaying, via the display generation component, a first selectable object for initiating a process for transmitting the activation code; as well as Based on determining that the activation code for the shared electronic key is disabled, displaying the first selectable object for initiating the process of transmitting the activation code is abandoned.

26. A first computer system configured to communicate with a display generation component and one or more input devices, the first computer system comprising: 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: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations, when the first computer system is associated with a first user; as well as In response to detecting the set of one or more inputs corresponding to the request to share the electronic key: Initiating a process of sharing the electronic key with the second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system comprises: Based on determining that the activation code for the shared electronic key is enabled, displaying, via the display generation component, a first selectable object for initiating a process for transmitting the activation code; as well as Based on determining that the activation code for the shared electronic key is disabled, displaying the first selectable object for initiating the process of transmitting the activation code is abandoned.

27. A first computer system configured to communicate with a display generation component and one or more input devices, the first computer system comprising: means for detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations, when the first computer system is associated with a first user; and means for, in response to detecting the set of one or more inputs corresponding to the request to share the electronic key: Initiating a process of sharing the electronic key with the second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system comprises: Based on determining that the activation code for the shared electronic key is enabled, displaying, via the display generation component, a first selectable object for initiating a process for transmitting the activation code; as well as Based on determining that the activation code for the shared electronic key is disabled, displaying the first selectable object for initiating the process of transmitting the activation code is abandoned.

28. A computer program product comprising one or more programs configured to be executed by one or more processors of a first computer system in communication with a display generation component and one or more input devices, the one or more programs comprising instructions for: detecting, via the one or more input devices, a set of one or more inputs corresponding to a request to share an electronic key of an electronic wallet with a second user different from the first user, wherein the electronic key provides one or more access rights to one or more physical locations, when the first computer system is associated with a first user; as well as In response to detecting the set of one or more inputs corresponding to the request to share the electronic key: Initiating a process of sharing the electronic key with the second user of a second computer system different from the first user of the first computer system, wherein the process of sharing the electronic key with the second user of the second computer system comprises: Based on determining that the activation code for the shared electronic key is enabled, displaying, via the display generation component, a first selectable object for initiating a process for transmitting the activation code; as well as Based on determining that the activation code for the shared electronic key is disabled, displaying the first selectable object for initiating the process of transmitting the activation code is abandoned.

29. A method comprising: At a first computer system in communication with one or more input devices: receiving, when the first computer system is associated with a first user, first information from a second user of a second computer system different from the first user of the first computer system, the first information relating to an electronic key to be provisioned to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; provisioning the electronic key to the electronic wallet of the first computer system using the first information about the electronic key; detecting, after provisioning the electronic key to the electronic wallet of the first computer system, via the one or more input devices, a request to share the electronic key with a third user different from the first user and the second user, wherein the request to share the electronic key with the third user specifies a second set of access rights for the electronic key being shared; as well as In response to detecting the request to share the electronic key with the third user, a process is initiated to share the electronic key having the second set of access rights with the third user of a third computer system different from the first computer system and the second computer system.

30. The method according to claim 29, further comprising: After the electronic key is shared, the electronic key is kept provisioned on the electronic wallet of the first computer system.

31. A method according to any one of claims 29 to 30, wherein the second set of access rights comprises a smaller subset of access rights than the first set of access rights.

32. A method according to any one of claims 29 to 31, wherein the request to share the electronic key with the third user specifies a first time range and a second time range different from the first time range, and at least one access right in the second group of access rights is activated during the first time range, and the at least one access right in the second group of access rights is deactivated during the second time range.

33. The method according to any one of claims 29 to 32, wherein the second user receives the information about the electronic key from a fourth user of a fourth computer system who is different from the first user, the second user and the third user.

34. A method according to any one of claims 29 to 33, wherein the first user is unable to share access rights not included in the first set of access rights as part of sharing the electronic key.

35. The method of any one of claims 29 to 34, wherein the first computer system uses a first activation code to provision the electronic key to the electronic wallet of the first computer system, the method further comprising: During the process of sharing the electronic key with the third user, a representation of a second activation code different from the first activation code is displayed via a display generation component for activating the shared electronic key.

36. The method according to any one of claims 29 to 35, further comprising: Prior to provisioning the electronic key to the electronic wallet of the first computer system, a non-modifiable representation of the first set of access rights is displayed via a display generation component.

37. The method of any one of claims 29 to 36, wherein provisioning the electronic key to the electronic wallet of the first computer system comprises: provisioning, by the first computer system, the electronic key to the electronic wallet of the first computer system using a third activation code; as well as An external device is detected, by the first computer system, within a threshold proximity of the first computer system.

38. The method according to any one of claims 29 to 37, further comprising: detecting, via the one or more input devices, a request to view a set of access permissions not shared by the second user; as well as In response to the request to view the set of access permissions not shared by the second user, a non-modifiable representation of the set of access permissions not shared by the second user is displayed.

39. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first computer system that communicates with a display generation component and one or more input devices, the one or more programs comprising instructions for executing a method according to any one of claims 29 to 38.

40. A first computer system, the first computer system being configured to communicate with one or more input devices, the computer system comprising: 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 comprising instructions for executing the method according to any one of claims 29 to 38.

41. A first computer system, the first computer system being configured to communicate with one or more input devices, the first computer system comprising: A component for carrying out the method according to any one of claims 29 to 38.

42. A computer program product comprising one or more programs configured to be executed by one or more processors of a first computer system in communication with one or more input devices, the one or more programs comprising instructions for performing the method according to any one of claims 29 to 38.

43. A non-transitory computer-readable storage medium storing one or more programs configured to be executed by one or more processors of a first computer system in communication with one or more input devices, the one or more programs comprising instructions for: receiving, when the first computer system is associated with a first user, first information from a second user of a second computer system different from the first user of the first computer system, the first information relating to an electronic key to be provisioned to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; provisioning the electronic key to the electronic wallet of the first computer system using the first information about the electronic key; detecting, after provisioning the electronic key to the electronic wallet of the first computer system, via the one or more input devices, a request to share the electronic key with a third user different from the first user and the second user, wherein the request to share the electronic key with the third user specifies a second set of access rights for the electronic key being shared; as well as In response to detecting the request to share the electronic key with the third user, a process is initiated to share the electronic key having the second set of access rights with the third user of a third computer system different from the first computer system and the second computer system.

44. A first computer system, the first computer system being configured to communicate with one or more input devices, the first computer system comprising: 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: receiving, when the first computer system is associated with a first user, first information from a second user of a second computer system different from the first user of the first computer system, the first information relating to an electronic key to be provisioned to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; provisioning the electronic key to the electronic wallet of the first computer system using the first information about the electronic key; detecting, after provisioning the electronic key to the electronic wallet of the first computer system, via the one or more input devices, a request to share the electronic key with a third user different from the first user and the second user, wherein the request to share the electronic key with the third user specifies a second set of access rights for the electronic key being shared; as well as In response to detecting the request to share the electronic key with the third user, a process is initiated to share the electronic key having the second set of access rights with the third user of a third computer system different from the first computer system and the second computer system.

45. A first computer system, the first computer system being configured to communicate with one or more input devices, the first computer system comprising: means for receiving, when the first computer system is associated with a first user, first information from a second user of a second computer system different from the first user of the first computer system, the first information relating to an electronic key to be provisioned to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; means for provisioning the electronic key to the electronic wallet of the first computer system using the first information about the electronic key; means for detecting, via the one or more input devices, a request to share the electronic key with a third user different from the first user and the second user after provisioning the electronic key to the electronic wallet of the first computer system, wherein the request to share the electronic key with the third user specifies a second set of access rights for the electronic key being shared; and Means for initiating a process of sharing the electronic key having the second set of access rights with the third user of a third computer system different from the first computer system and the second computer system in response to detecting the request to share the electronic key with the third user.

46. ​​A computer program product comprising one or more programs configured to be executed by one or more processors of a first computer system in communication with one or more input devices, the one or more programs comprising instructions for: receiving, when the first computer system is associated with a first user, first information from a second user of a second computer system different from the first user of the first computer system, the first information relating to an electronic key to be provisioned to an electronic wallet of the first computer system associated with the first user, wherein the electronic key provides a first set of access rights to one or more physical locations; provisioning the electronic key to the electronic wallet of the first computer system using the first information about the electronic key; detecting, after provisioning the electronic key to the electronic wallet of the first computer system, via the one or more input devices, a request to share the electronic key with a third user different from the first user and the second user, wherein the request to share the electronic key with the third user specifies a second set of access rights for the electronic key being shared; as well as In response to detecting the request to share the electronic key with the third user, a process is initiated to share the electronic key having the second set of access rights with the third user of a third computer system different from the first computer system and the second computer system.

Images