Device, method and graphical user interface for conference space management and interaction
By achieving a faster and more effective user interface interaction method on electronic devices, the problem of cumbersome management of meeting space and interaction operations in the prior art is solved, which improves device efficiency and user experience, saves power, and extends battery life.
Patent Information
- Application Number
- CN202110499271.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2017-04-30
- Filing Date
- 2017-06-07
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2037-06-07
AI Technical Summary
When managing and interacting with the meeting space, existing touch-sensitive surface electronic devices have cumbersome and inefficient operation methods, resulting in a large and time-consuming cognitive burden on users, especially in battery-driven devices, which affects the performance of the device and the battery. life.
Provide an electronic device and method to enable or disable statement and display the status interface of the conference space and detect changes in the condition, display the report interface, select user input sequence to generate service requests, display meeting arrangement information, provide media management interface, and coordinate Media input feeds facilitate the presentation and transfer of electronic conferences, create and manage calendar events, confirm appointments and participants identities, and enable faster and more efficient user interface interactions.
It reduces the complexity and time-consuming of user operations, improves the efficiency and user satisfaction of the device, saves battery power, extends battery life, and improves the utilization of conference space.
Smart Images

Figure CN113325967B_ABST
Abstract
Description
[0001] Divisional Application Instructions
[0002] This application is a divisional application of a patent application with an international application date of June 7, 2017, international application number PCT / US2017 / 036350, application number 201780036079.5, and name “Device, method and graphical user interface for conference space management and interaction”, which entered the Chinese national phase on December 10, 2018. Technical Field
[0003] This document generally relates to electronic devices with touch-sensitive surfaces, including but not limited to electronic devices with touch-sensitive surfaces for managing and interacting with meeting spaces. Background Art
[0004] The use of touch-sensitive surfaces as input devices for computers and other electronic computing devices has grown significantly in recent years. Exemplary touch-sensitive surfaces include touchpads and touch screen displays. Such surfaces are widely used to manipulate user interface objects on displays.
[0005] Exemplary manipulations include adjusting the position and / or size of one or more user interface objects, or activating a button or opening a file / application represented by a user interface object, as well as associating metadata with one or more user interface objects or otherwise manipulating the user interface. Exemplary user interface objects include digital images, videos, text, icons, control elements (such as buttons), and other graphics. In some cases, a user will need to perform such manipulations on user interface objects in: a file management program (e.g., Finder from Apple Inc. (Cupertino, California)); an image management application (e.g., Aperture, iPhoto, Photos from Apple Inc. (Cupertino, California)); a digital content (e.g., video and music) management application (e.g., iTunes from Apple Inc. (Cupertino, California)); a drawing application; a presentation application (e.g., Keynote from Apple Inc. (Cupertino, California)); a word processing application (e.g., Pages from Apple Inc. (Cupertino, California)); a website creation application (e.g., iWeb from Apple Inc. (Cupertino, California)); a disc editing application (e.g., iDVD from Apple Inc. (Cupertino, California)); or a spreadsheet application (e.g., Numbers from Apple Inc. (Cupertino, California)).
[0006] However, methods for performing these manipulations are cumbersome and inefficient. For example, using a sequence of mouse-based inputs to select one or more user interface objects and perform one or more actions on the selected user interface objects is tedious and places a significant cognitive burden on the user. Furthermore, these methods take longer than necessary, thereby wasting energy. This latter consideration is particularly important in battery-powered devices. Summary of the Invention
[0007] Therefore, there is a need for electronic devices that utilize faster and more efficient methods and interfaces for managing and interacting with meeting spaces. Such methods and interfaces optionally supplement or replace conventional methods for managing and interacting with meeting spaces. Such methods and interfaces reduce the cognitive burden on users and create more efficient human-computer interfaces. For battery-powered devices, such methods and interfaces can conserve power and increase the time between battery charges.
[0008] The above-mentioned defects and other problems associated with the user interface of an electronic device with a touch-sensitive surface can be reduced or eliminated with the help of the disclosed device. In some embodiments, the device is a desktop computer. In some embodiments, the device is portable (e.g., a laptop, tablet computer, or handheld device). In some embodiments, the device has a touchpad. In some embodiments, the device has a touch-sensitive display (also referred to as a "touch screen" or "touch screen display"). In some embodiments, the device has a graphical user interface (GUI), one or more processors, memory, and one or more modules, a program or instruction set stored in the memory for performing multiple functions. In some embodiments, the user interacts with the GUI primarily through stylus and / or finger contact and gestures on the touch-sensitive surface. In some embodiments, these functions optionally include image editing, drawing, presentation, word processing, web page creation, disk editing, spreadsheet creation, playing games, making and receiving calls, video conferencing, sending and receiving emails, instant messaging, fitness support, digital photography, digital video recording, web browsing, digital music playback, and / or digital video playback. 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.
[0009] According to some embodiments, a method is performed on a device associated with a conference space having non-volatile memory, a display, an input device, and one or more processors. The method includes: displaying a conference space status interface on the display, the conference space status interface including a status indicator indicating the current reservation status of the conference space and a declaration enable representation provided to declare the reservation of the conference space; and while displaying the conference space status interface, detecting a change in conditions at the conference space. In response to detecting a change in conditions at the conference space, and determining that one or more declaration criteria are met based on the change in conditions at the conference space, the method also includes enabling the declaration enable representation. In response to detecting a change in conditions at the conference space, and determining that one or more declaration criteria are not met based on the change in conditions at the conference space, the method also includes disabling the declaration enable representation.
[0010] According to some embodiments, a method is performed on a device associated with a meeting space having non-volatile memory, a display, an input device, and one or more processors. The method includes: displaying a reporting interface having a plurality of affordances on the display, the reporting interface provided for reporting issues associated with corresponding features of the meeting space; detecting, via the input device, a sequence of one or more user inputs corresponding to selection of one or more affordances from the plurality of affordances; and in response to the sequence of one or more user inputs selecting the one or more affordances, initiating a process for generating a service request associated with one or more features of the meeting space, the service request corresponding to the selected one or more affordances.
[0011] According to some embodiments, a method is performed on a device associated with a first meeting space having non-volatile memory, a display, an input device, and one or more processors. The method includes: displaying a meeting space discovery interface having a plurality of affordances on the display, the plurality of affordances corresponding to a plurality of available meeting spaces different from the first meeting space; detecting, via the input device, a first user input corresponding to selecting a corresponding affordance corresponding to a second meeting space from a plurality of affordances displayed within the meeting space discovery interface; and providing instructions for navigating from the first meeting space to the second meeting space in response to the first user input selecting the corresponding affordance.
[0012] According to some embodiments, a method is performed on a first electronic device having a display and one or more input devices. The method includes: displaying a user interface on the display of the first electronic device, the user interface including information about a meeting schedule for a meeting space; while displaying the user interface, determining, based on input from a second electronic device associated with the meeting space, that a change has occurred in reservation information for a corresponding meeting in the meeting schedule for the meeting space; and in response to determining that a change has occurred in reservation information for the corresponding meeting, updating the user interface displayed on the display of the first electronic device to show the change in reservation information.
[0013] According to some embodiments, a method is performed on a first electronic device having a display and one or more input devices. The method includes: obtaining a scheduled appointment associated with a meeting space, the meeting space having a plurality of scheduled meetings, including a next meeting that has not yet been confirmed; and obtaining a proximity indicator indicating that a portable device is within a predefined distance of the meeting space. In response to obtaining the proximity indicator and determining, based on the scheduled appointment associated with the meeting space, that the proximity indicator includes a participant identifier associated with an upcoming appointment for the meeting space, the method also includes confirming the upcoming appointment for the meeting space.
[0014] According to some embodiments, a method is performed on an electronic device having a display and one or more input devices. The method includes displaying a media management interface on the display, the media management interface including: displaying representations of multiple media input feeds, the multiple media input feeds including at least one media input feed from a source device different from the electronic device; and displaying representations of multiple display areas of one or more media output devices. While displaying the media management interface, the method also includes detecting a first user input via the one or more input devices, the first user input corresponding to movement of a first representation of a first media input feed to a representation of a first display area in a plurality of display areas. In response to detecting the first user input, the method also includes coordinating display of the first media input feed on the first display area.
[0015] According to some embodiments, a method is performed on an electronic device having non-volatile memory and one or more processors. The method includes: facilitating the presentation of an electronic conference corresponding to an ongoing appointment in a meeting space, wherein presenting the electronic conference corresponding to the ongoing appointment in the meeting space includes presenting electronic conference data using a device in the meeting space; and when facilitating the presentation of the electronic conference, obtaining a request to continue the meeting outside the meeting space. In response to obtaining the request to continue the meeting outside the meeting space, the method also includes displaying one or more options for transferring the electronic conference on a display. The method also includes: detecting, via one or more input devices, a selection of a first option from one or more options for transferring the electronic conference; and in response to detecting the selection of the first option: stopping presenting the electronic conference in the meeting space via the device; and initiating a process to transfer the electronic conference to a device not associated with the meeting space.
[0016] According to some embodiments, a method is performed on an electronic device having a display and one or more input devices. The method includes displaying on the display a first user interface element provided for creating a calendar event, wherein the first user interface element includes a location input element, and the location input element is provided to receive user input to add a location of the calendar event. The method also includes: detecting a first input corresponding to the location input element via one or more input devices; and in response to detecting the first input, displaying one or more locations of the calendar event in association with the location input element on the display, wherein at least one of the one or more locations corresponds to a virtual meeting. The method also includes: detecting a second input corresponding to the virtual meeting via one or more input devices; and in response to detecting the second input: generating incoming call information and a link for the virtual meeting; and associating the incoming call information and the link with the calendar event.
[0017] According to some embodiments, a method is performed on an electronic device having a display and one or more input devices. The method includes displaying on the display a first user interface element provided for creating a calendar event, wherein the first user interface element includes a location input element and a schedule input element, the location input element being provided to receive user input for adding a location for the calendar event, and the schedule input element being provided to receive user input for adding a time and date for the calendar event. The method also includes: selecting one or more invitees to be invited to the calendar event; and after the one or more invitees have been selected: based on location attributes of the one or more invitees and the organizer of the calendar event, populating a displayed portion of the location input element with a meeting space identifier that meets a location criterion; and based on schedule attributes of the one or more invitees and the organizer of the calendar event, populating a displayed portion of the schedule input element with a date and time identifier that meets a time and date criterion.
[0018] According to some embodiments, a method is performed on an electronic device having a display and one or more input devices. The method includes displaying a meeting list interface on the display indicating details of an ongoing meeting, the meeting list interface including a meeting invitee area having a first sub-area and a second sub-area, the first sub-area including a first plurality of invitee representations associated with participating invitees, and the second sub-area including a second plurality of invitee representations associated with non-participating invitees. The method also includes: detecting a connection corresponding to the ongoing meeting; and based on determining that the connection corresponds to a first invitee among the non-participating invitees, updating the meeting list interface by stopping displaying a first representation of a first invitee in the second plurality of invitee representations in the second sub-area and displaying a first representation of a first invitee in the first plurality of invitee representations in the first sub-area associated with the participating invitees.
[0019] According to some embodiments, a method is performed on a first electronic device having a display and one or more input devices. The method includes displaying a meeting list interface on the display of the first electronic device indicating details of an ongoing meeting associated with a virtual conference service application and a physical meeting space, the meeting list interface including a screen sharing enable representation that is provided to share content displayed on the display of the first electronic device to one or more other devices connected to the virtual conference service application and a second electronic device associated with a physical meeting space connected to a local interface different from the virtual conference service application. The method also includes: detecting a first input via one or more input devices, the first input corresponding to a selection of the screen sharing enable representation displayed by the first electronic device; and in response to detecting the first input: causing the content displayed by the first electronic device to be included in a virtual display area available to one or more other devices connected to the virtual conference service application; and causing the content displayed by the first electronic device to be displayed by a second electronic device associated with a physical meeting space connected to the local interface.
[0020] According to some embodiments, an electronic device associated with a meeting space includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled to the display unit and the one or more input units. The processing unit is configured to: enable display of a meeting space status interface on the display unit, the meeting space status interface including a status indicator indicating the current reservation status of the meeting space and a declaration enable representation provided for declaring a reservation for the meeting space; and, while displaying the meeting space status interface, detect a change in conditions at the meeting space. In response to detecting a change in conditions at the meeting space and determining that one or more declaration criteria are satisfied based on the change in conditions at the meeting space, the processing unit is further configured to enable the declaration enable representation. In response to detecting a change in conditions at the meeting space and determining that one or more declaration criteria are not satisfied based on the change in conditions at the meeting space, the processing unit is further configured to disable the declaration enable representation.
[0021] According to some embodiments, an electronic device associated with a meeting space includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled to the display unit and the one or more input units. The processing unit is configured to: enable display of a reporting interface having a plurality of affordances on the display unit, the reporting interface being provided for reporting issues associated with corresponding features of the meeting space; detect, via the one or more input units, a sequence of one or more user inputs corresponding to selection of one or more affordances from the plurality of affordances; and in response to the sequence of one or more user inputs selecting the one or more affordances, initiate a process for generating a service request associated with one or more features of the meeting space, the service request corresponding to the selected one or more affordances.
[0022] According to some embodiments, an electronic device includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled to the display unit and the one or more input units. The processing unit is configured to: enable display of a meeting space discovery interface having multiple affordances on the display unit, the multiple affordances corresponding to multiple available meeting spaces different from a first meeting space; detect, via the one or more input units, a first user input corresponding to selecting a corresponding affordance corresponding to a second meeting space from a plurality of affordance tables displayed within the meeting space discovery interface; and provide instructions for navigating from the first meeting space to the second meeting space in response to the first user input selecting the corresponding affordance.
[0023] According to some embodiments, an electronic device includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled to the display unit and the one or more input units. The processing unit is configured to: enable display of a user interface on the display unit of the electronic device, the user interface including information about a meeting schedule for a meeting space; while displaying the user interface, determine, based on input from another electronic device associated with the meeting space, that a change has occurred in reservation information for a corresponding meeting in the meeting schedule for the meeting space; and in response to determining that a change has occurred in reservation information for the corresponding meeting, update the user interface displayed on the display unit of the electronic device to show the change in reservation information.
[0024] According to some embodiments, an electronic device includes an optional display unit configured to display a user interface, one or more optional input units configured to receive user input, and a processing unit coupled to the display unit and the one or more input units. The processing unit is configured to: obtain a scheduled appointment associated with a meeting space, the meeting space having multiple scheduled meetings, including a next meeting that has not yet been confirmed; and obtain a proximity indicator indicating that a portable device is within a predefined distance of the meeting space. In response to obtaining the proximity indicator and determining that the proximity indicator includes a participant identifier associated with an upcoming appointment for the meeting space based on the scheduled appointment associated with the meeting space, the processing unit is further configured to confirm the upcoming appointment for the meeting space.
[0025] According to some embodiments, an electronic device includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled to the display unit and the one or more input units. The processing unit is configured to enable display of a media management interface on the display unit, the media management interface including: displaying representations of multiple media input feeds, the multiple media input feeds including at least one media input feed from a source device different from the electronic device; and displaying representations of multiple display areas of one or more media output devices. While displaying the media management interface, the processing unit is further configured to detect a first user input via the one or more input units, the first user input corresponding to movement of a first representation of a first media input feed to a representation of a first display area among a plurality of display areas. In response to detecting the first user input, the processing unit is further configured to coordinate display of the first media input feed on the first display area.
[0026] According to some embodiments, an electronic device includes a display unit configured to display a user interface, one or more input units configured to receive user input, and a processing unit coupled to the display unit and the one or more input units. The processing unit is configured to: facilitate the presentation of an electronic conference corresponding to an ongoing appointment in a meeting space, wherein presenting the electronic conference corresponding to the ongoing appointment in the meeting space includes presenting electronic conference data using devices in the meeting space; and when facilitating the presentation of the electronic conference, obtain a request to continue the meeting outside the meeting space. In response to obtaining the request to continue the meeting outside the meeting space, the processing unit is further configured to enable display of one or more options for transferring the electronic conference on the display unit. The processing unit is further configured to: detect, via the one or more input units, a selection of a first option from the one or more options for transferring the electronic conference; and in response to detecting the selection of the first option: stop presenting the electronic conference in the meeting space via the device; and initiate a process for transferring the electronic conference to a device not associated with the meeting space.
[0027] According to some embodiments, an electronic device includes a display, an input device, one or more processors, a non-volatile memory, and one or more programs; the one or more programs are stored in the non-volatile memory and configured to be executed by the one or more processors, and the one or more programs include instructions for performing or causing the performance of any of the operations of any method described herein. According to some embodiments, a non-volatile computer-readable storage medium stores therein instructions that, when executed by one or more processors of an electronic device having a display and an input device, cause the device to perform or cause the performance of any of the operations of the methods described herein. According to some embodiments, a graphical user interface on an electronic device includes one or more elements displayed in any of the methods described above, wherein the electronic device has a display, an input device, a memory, and one or more processors for executing one or more programs stored in the non-volatile memory, the one or more elements being updated in response to input, as described in any of the methods described herein. According to some embodiments, an electronic device includes: a display, an input device; and a device for performing or causing the performance of any of the operations of the methods described herein. According to some embodiments, an information processing device used in an electronic device having a display and an input device includes a device for performing or causing the performance of any of the operations of the methods described herein.
[0028] Thus, a faster and more efficient method and interface for managing and interacting with a meeting space is provided for an electronic device having a display, a touch-sensitive surface, and optionally one or more sensors for detecting the intensity of contact with the touch-sensitive surface, thereby improving the effectiveness, efficiency, and user satisfaction of such a device. Such a method and interface may supplement or replace conventional methods for managing and interacting with a meeting space. BRIEF DESCRIPTION OF THE DRAWINGS
[0029] 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.
[0030] Figure 1A is a block diagram illustrating a portable multifunction device with a touch-sensitive display according to some embodiments.
[0031] Figure 1B is a block diagram illustrating example components for event processing according to some embodiments.
[0032] Figure 2 A portable multifunction device with a touch screen according to some embodiments is shown.
[0033] Figure 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments.
[0034] Figure 4A An exemplary user interface for an application menu on a portable multifunction device according to some embodiments is shown.
[0035] Figure 4B An exemplary user interface for a multifunction device having a touch-sensitive surface separate from the display is shown according to some embodiments.
[0036] Figure 5A An exemplary meeting space data processing environment is shown in accordance with some embodiments.
[0037] Figure 5B An exemplary meeting space is shown in accordance with some embodiments.
[0038] Figure 5A An exemplary meeting space data processing environment is shown in accordance with some embodiments.
[0039] Figure 5B An exemplary meeting space is shown in accordance with some embodiments.
[0040] Figures 6A to 6W An exemplary user interface for managing and interacting with a meeting space is shown in accordance with some embodiments.
[0041] Figures 7A to 7Z An exemplary user interface for managing and interacting with a meeting space is shown in accordance with some embodiments.
[0042] Figure 8 An example state diagram of status indicators associated with a meeting space is shown according to some embodiments.
[0043] Figures 9A to 9B A flowchart of a method of declaring a meeting space according to some embodiments is shown.
[0044] FIG. 10A to FIG. 10B A flow chart illustrating a method of reporting a meeting space issue according to some embodiments is shown.
[0045] Figures 11A to 11C A flow chart illustrating a method of finding available meeting space according to some embodiments is shown.
[0046] Figures 12 to 14 is a functional block diagram of an electronic device according to some embodiments.
[0047] Figures 15A to 15R An exemplary user interface is shown for updating a user interface displayed on a first device based on input from a second device according to some embodiments.
[0048] 16A to 16C An exemplary flow diagram for authenticating a user to confirm a reservation of a meeting space is shown, according to some embodiments.
[0049] 17A to 17D An exemplary flow diagram for authenticating a user to confirm a reservation of a meeting space is shown, according to some embodiments.
[0050] 18A to 18S An exemplary user interface for managing media input / output (I / O) for a meeting space is shown in accordance with some embodiments.
[0051] Figures 19A to 19N An exemplary user interface for continuing an electronic conference is shown according to some embodiments.
[0052] FIG. 20A to FIG. 20B A flowchart of a method for updating a user interface displayed on a first device based on input from a second device according to some embodiments is shown.
[0053] 21A to 21D A flow chart illustrating a method of confirming a reservation for a meeting space according to some embodiments is shown.
[0054] Figures 22A to 22CA flow chart illustrating a method of managing media input / output (I / O) for a meeting space, according to some embodiments.
[0055] Figures 23A to 23C A flowchart of a method of continuing an electronic conference is shown according to some embodiments.
[0056] Figures 24 to 27 is a functional block diagram of an electronic device according to some embodiments.
[0057] Figures 28A to 28Z An exemplary user interface for creating and managing calendar events is shown according to some embodiments.
[0058] Figures 29A to 29L An exemplary user interface for managing meeting attendance and screen sharing is shown according to some embodiments.
[0059] 30A to 30D A flowchart of a method for creating a calendar event associated with a virtual meeting is shown according to some embodiments.
[0060] Figures 31A to 31C A flowchart of a method for populating the schedule and / or location portion of a new calendar event based on invitees is shown according to some embodiments.
[0061] Figures 32A to 32C A flow chart illustrating a method of managing attendance of meeting invitees according to some embodiments is shown.
[0062] Figures 33A to 33C A flow chart illustrating a method of screen sharing via a remote virtual conference service application and also via a local interface according to some embodiments. DETAILED DESCRIPTION
[0063] Meeting rooms are a valuable commodity on a corporate campus. Even with a robust scheduling system, no-show rates are typically in the 20% to 30% range. Therefore, it is beneficial to make meeting spaces available in such no-show situations by implementing room reservation policies and etiquette. In some embodiments, a first device used for reservation declaration (e.g., signing in to and taking over an available space) is located outside the meeting space adjacent to the entrance. In some embodiments, a second device located within the meeting space is synchronized with the first device (e.g., a meeting organizer can sign in to a meeting using either device) and is also capable of interfacing with user accounts and / or devices within the meeting space (e.g., environmental controls, projectors, smart TVs, teleconferencing devices, etc.). In some embodiments, the first device indicates the status of the meeting space (and optionally allows the display of schedules), and the second device is used to declare the meeting space (e.g., sign in to an existing reservation, or requisition an available meeting space) and control the meeting space. In some embodiments, both the first and second devices indicate the status of the meeting space and can be used to declare reservations. In some embodiments, a single device provides the functionality of both the first and second devices.
[0064] In some embodiments, the action of changing the appointment information detected by the first device causes the second device (and possibly the first device) to update its user interface. In some embodiments, a confirmation process is performed using a proximity indicator (e.g., broadcast by a device associated with the meeting space or a user's portable device) that includes identification information (e.g., a participant ID and a location ID) to determine whether to confirm (e.g., passively) an upcoming appointment. In some embodiments, a media management interface that includes representations of media input feeds and representations of display areas of output devices within the meeting space enables a user to coordinate the presentation of media input feeds on output devices from a unified interface. In some embodiments, when facilitating an electronic conference for a meeting within a meeting space, the device displays an option for continuing the electronic conference outside of the current meeting space by transferring the electronic conference to a device associated with another available meeting space or to the phone of at least one participant of the meeting.
[0065] under, Figure 1A to Figure 1B 、 Figures 2 to 3 as well as Figures 4A to 4B A description of an exemplary apparatus is provided. Figures 5A to 5B An exemplary usage environment is shown. Figures 9A to 9B A process for claiming a meeting space is shown. FIG. 10A to FIG. 10B A process for reporting a meeting space problem is shown. Figures 11A to 11C A process for finding available meeting space is shown. Figure 6A to Figure 6W as well as Figures 7A to 7ZDescribes a method for use by a device such as, Figures 12 to 14 FIG6A to FIG6B illustrate an exemplary user interface for managing and interacting with a conference space executed by a device described in FIG6B . Figure 6W as well as Figures 7A to 7Z The user interface in Figures 9A to 9B , Figure 10A to Figure 10B as well as Figures 11A to 11C in the process.
[0066] FIG. 20A to FIG. 20B A process for updating a user interface displayed on a first device based on input from a second device is shown. Figures 15A to 15R Describes a method for use by a device such as, Figure 24 An exemplary user interface for updating a user interface displayed on a first device based on input from a second device, performed by the device described in . 21A to 21D A process for confirming a reservation of a meeting space is shown. 16A to 16C as well as 17A to 17D shows a method for use by a device such as, Figure 25 Flowchart of the device described in (described in) performing authentication of a user to confirm a reservation of a meeting space. Figures 22A to 22C A process for managing media input / output (I / O) for a conference space is shown. 18A to 18S Describes a method for use by a device such as, Figure 26 An exemplary user interface for managing media I / O of a conference space executed by the device described in ( ). Figures 23A to 23C A process for continuing an electronic conference is shown. Figures 19A to 19N Describes a method for use by a device such as, Figure 27 An exemplary user interface for continuing an electronic conference executed by the device described in (). Figures 15A to 15R 、 18A to 18S as well as Figures 19A to 19N The user interface in FIG. 20A to FIG. 20B 、 Figures 22A to 22C as well as Figures 23A to 23C in the process.
[0067] 30A to 30D A process for creating a calendar event associated with a virtual meeting is shown. Figures 31A to 31C A process is shown for populating the schedule and / or location portion of a new calendar event based on invitees and sharing via the remote virtual conferencing service application and also via the local interface. Figures 28A to 28CC Describes a method for use by a device such as, Figure 1A 、 Figure 2 To Figure 3 and Figures 4A to 4B An exemplary user interface for creating and managing calendar events executed by the device described in . Figures 32A to 32CFIG33A to FIG33B show a process for managing the attendance of meeting invitees. Figure 32C The process of the screen is shown. Figures 29A to 29L Describes a method for use by a device such as, Figure 1A 、 Figures 2 to 3 as well as Figures 4A to 4B An exemplary user interface for managing conference attendance and screen sharing executed by the device described in (described in). Figures 28A to 28CC as well as Figure 29A to Figure 29L The user interface in 30A to 30D 、 Figures 31A to 31C 、 Figure 32A to Figure 32C as well as Figures 33A to 32C in the process.
[0068] Exemplary devices
[0069] Reference will now be made in detail to the embodiments, examples of which are illustrated in the accompanying drawings. Numerous specific details are set forth in the following detailed description in order to provide a thorough understanding of the various described embodiments. However, it will be apparent to one of ordinary skill in the art that the various described embodiments may be practiced without these specific details. In other cases, well-known methods, processes, components, circuits, and networks have not been described in detail so as not to unnecessarily obscure various aspects of the embodiments.
[0070] It will also be understood that, although in some cases, the terms "first," "second," etc., are used herein to describe various elements, these elements should not be limited by these terms. These terms are simply used to distinguish one element from another. For example, a first contact can be named a second contact, and similarly, a second contact can be named a first contact without departing from the scope of the various described embodiments. Both a first contact and a second contact are contacts, but they are not the same contact unless the context clearly indicates otherwise.
[0071] The terms used in the description of the various embodiments described herein are only for the purpose of describing specific embodiments, and are not intended to be limiting. As used in the description of the various embodiments described and in the appended claims, the singular forms "a" and "the" are intended to also include plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms used herein "and / or" refer to and encompass any and all possible combinations of one or more items in the associated listed items. It will also be understood that the terms "comprise" and / or "comprising" when used in this manual specify the presence of stated features, integers, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts and / or their groupings.
[0072] As used herein, the term "if" is optionally interpreted to mean "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined that" or "if [stated condition or event] is detected" are optionally interpreted to mean "upon determining that" or "in response to determining that" or "upon detecting [stated condition or event]" or "in response to detecting [stated condition or event]," depending on the context.
[0073] Embodiments of electronic devices, user interfaces for such devices, and processes associated with 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 music player. Exemplary embodiments of portable multifunction devices include, but are not limited to, the Apple Watch from Apple Inc. (Cupertino, California). iPod and Device. Other portable electronic devices, such as laptops or tablets with touch-sensitive surfaces (e.g., touch screen displays and / or touch pads), are optionally used. It should also be understood that in some embodiments, the device is not a portable communication device, but rather a desktop computer with a touch-sensitive surface (e.g., touch screen displays and / or touch pads).
[0074] 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.
[0075] The device typically supports a variety of applications, such as one or more of the following: a drawing application, a rendering 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.
[0076] 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 the touch-sensitive surface) optionally supports the various applications with a user interface that is intuitive and clear to the user.
[0077] Attention is now turned to embodiments of portable devices having touch-sensitive displays. Figure 1A 1 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 system 112 is sometimes referred to as a "touch screen" for convenience, and sometimes simply as a touch-sensitive display. The device 100 includes 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, RF circuitry 108, audio circuitry 110, a speaker 111, a microphone 113, an input / output (I / O) subsystem 106, other input or control devices 116, and external ports 124. The device 100 optionally includes one or more optical sensors 164. The device 100 optionally includes one or more intensity sensors 165 for detecting the intensity of contacts 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 163 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.
[0078] 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 a 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 that will be detected by a user using the user's sense of touch. For example, when a device or a component of the device is in contact with a surface that is touch-sensitive to a user (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 that corresponds to a perceived change in a physical characteristic 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" on 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 was physically pressed (e.g., displaced) by the user's movement does not move. As another example, even when the smoothness of the touch-sensitive surface does not change, movement of the touch-sensitive surface may optionally be interpreted or sensed by the user as "roughness" of the touch-sensitive surface. While 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. Thus, 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.
[0079] 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 in the drawings are implemented in hardware, software, firmware, or any combination thereof, including one or more signal processing circuits and / or application specific integrated circuits.
[0080] Memory 102 optionally includes high-speed random access memory and optionally also includes non-volatile memory, such as one or more magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. Access to memory 102 by other components of device 100 (such as one or more CPUs 120 and peripheral device interface 118) is optionally controlled by a memory controller 122.
[0081] Peripherals interface 118 may be used to couple the device's input and output peripherals to memory 102 and one or more CPUs 120. The one or more processors 120 run or execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data.
[0082] In some embodiments, peripherals interface 118, one or more CPUs 120, and memory controller 122 are optionally implemented on a single chip, such as chip 104. In some other embodiments, they are optionally implemented on separate chips.
[0083] RF (radio frequency) circuitry 108 receives and transmits RF signals, also known as electromagnetic signals. RF circuitry 108 converts electrical signals into / from electromagnetic signals and communicates with a communication network and other communication devices via the electromagnetic signals. RF circuitry 108 optionally includes well-known circuitry for performing these functions, including but not limited to an antenna system, an RF transceiver, one or more amplifiers, a tuner, one or more oscillators, a digital signal processor, a codec chipset, a subscriber identity module (SIM) card, memory, and the like. RF circuitry 108 optionally communicates with a network and other devices via wireless communications, such as the Internet (also known as the World Wide Web (WWW)), an intranet, and / or a wireless network (such as a cellular telephone network, a wireless local area network (LAN), and / or a metropolitan area network (MAN)). The 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, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11ac, IEEE 802.11ax, IEEE 802.11b, IEEE 802.11g, and / or IEEE 802.11d). or IEEE 802.11n), 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 not yet developed on the date of filing of this document.
[0084] The audio circuit 110, the speaker 111, and the microphone 113 provide an audio interface between the user and the device 100. The audio circuit 110 receives audio data from the peripheral device interface 118, converts the audio data into an electrical signal, and transmits the electrical signal to the speaker 111. The speaker 111 converts the electrical signal into sound waves audible to the human ear. The audio circuit 110 also receives the electrical signal converted from the sound wave by the microphone 113. The audio circuit 110 converts the electrical signal 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 with both output (e.g., a single or dual-ear headset) and input (e.g., a microphone).
[0085] The I / O subsystem 106 couples input / output peripherals on the device 100, such as a touch-sensitive display system 112 and other input or 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, 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 / to other input or control devices 116. 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 alternative embodiments, the one or more input controllers 160 are optionally coupled to any (or none) of the following: a keyboard, an infrared port, a USB port, a stylus, and / or a pointer device such as a mouse. One or more buttons (e.g., Figure 2 208) optionally includes up / down buttons for volume control of the speaker 111 and / or microphone 113. The one or more buttons optionally include a push button (e.g., Figure 2 206 in ).
[0086] The touch-sensitive display system 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-sensitive display system 112 and / or sends electrical signals to the touch-sensitive display system 112. The touch-sensitive display system 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 corresponds to user interface objects.
[0087] The touch-sensitive display system 112 has a touch-sensitive surface, sensor, or set of sensors that accepts input from a user based on haptic / tactile contact. The touch-sensitive display system 112 and the display controller 156 (together with any associated modules and / or instruction sets in the memory 102) detect contact (and any movement or interruption of that contact) on the touch-sensitive display system 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-sensitive display system 112. In an exemplary embodiment, the point of contact between the touch-sensitive display system 112 and the user corresponds to the user's finger or stylus.
[0088] The touch-sensitive display system 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-sensitive display system 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-sensitive display system 112 to detect contact and any movement or interruption thereof. In one exemplary embodiment, projected mutual capacitance sensing technology is used, such as the ATmega 2000 from Apple Inc. (Cupertino, California). iPod and Technology found in.
[0089] The touch-sensitive display system 112 optionally has a video resolution exceeding 100 dpi. In some embodiments, the touch screen video resolution exceeds 400 dpi (e.g., 500 dpi, 800 dpi, or greater). The user optionally uses any suitable object or appendage, such as a stylus, finger, or the like, to contact the touch-sensitive display system 112. In some embodiments, the user interface is designed to work with finger-based contacts and gestures, which may not be as precise as stylus-based input due to the larger contact area of a finger on the touch screen. In some embodiments, the device converts rough finger-based input into precise pointer / cursor positions or commands for performing the action desired by the user.
[0090] In some embodiments, in addition to the touch screen, the device 100 optionally includes a touchpad (not shown) 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 that is separate from the touch-sensitive display system 112 or an extension of the touch-sensitive surface formed by the touch screen.
[0091] 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 circuitry, a power converter or inverter, a power status indicator (e.g., a light emitting diode (LED)), and any other components associated with the generation, management, and distribution of power in a portable device.
[0092] Device 100 optionally also includes one or more optical sensors 164 . Figure 1A An optical sensor coupled to an optical sensor controller 158 in the I / O subsystem 106 is shown. One or more optical sensors 164 optionally include a charge coupled device (CCD) or a complementary metal oxide semiconductor (CMOS) phototransistor. The one or more optical sensors 164 receive light projected from the environment through one or more lenses and convert the light into data representing an image. In conjunction with the imaging module 143 (also called a camera module), the one or more optical sensors 164 optionally capture still images and / or video. In some embodiments, the optical sensor is located on the rear portion of the device 100 opposite the touch-sensitive display system 112 on the front of the device, so that the touch screen can be used as a viewfinder for still image and / or video image acquisition. In some embodiments, another optical sensor is located on the front of the device to obtain an image of the user (e.g., for self-portraits, for video conferencing when the user views other video conference participants on the touch screen, etc.).
[0093] Device 100 optionally also includes one or more contact intensity sensors 165 . Figure 1A A contact force sensor is shown coupled to a force sensor controller 159 in the I / O subsystem 106. One or more contact force sensors 165 optionally include 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 a contact on a touch-sensitive surface). One or more contact force sensors 165 receive 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 with 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 rear portion of the device 100 opposite the touch-sensitive display system 112 located on the front portion of the device 100.
[0094] 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 coupled to the input controller 160 in the I / O subsystem 106. 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-sensitive display system 112.
[0095] Device 100 optionally also includes one or more tactile output generators 163 . Figure 1AA tactile output generator is shown coupled to a tactile feedback controller 161 in the I / O subsystem 106. One or more tactile output generators 163 optionally include one or more electroacoustic devices such as speakers or other audio components; and / or electromechanical devices for converting energy into linear motion such as motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators, or other tactile output generating components (e.g., components for converting electrical signals into tactile outputs on the device). The tactile output generators 163 receive tactile feedback generation instructions from the tactile feedback module 133 and generate tactile outputs on the device 100 that can be felt by the user of the device 100. In some embodiments, at least one tactile output generator is juxtaposed or adjacent to a touch-sensitive surface (e.g., touch-sensitive display system 112) and optionally generates tactile outputs by moving the touch-sensitive surface vertically (e.g., inward / outward toward the surface of the device 100) or laterally (e.g., back and forth 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-sensitive display system 112 located on the front of the device 100.
[0096] Device 100 optionally also includes one or more accelerometers 167 , gyroscopes 168 , and / or magnetometers 169 (eg, as part of an inertial measurement unit (IMU)) for obtaining information about the position (eg, attitude) of the device. Figure 1A Sensors 167, 168, and 169 are shown coupled to peripherals interface 118. Alternatively, sensors 167, 168, and 169 are optionally coupled to input controller 160 in I / O subsystem 106. In some embodiments, information is displayed on the touch screen display in a portrait view or a landscape view based on analysis of data received from the one or more accelerometers. Device 100 optionally includes a GPS (or GLONASS or other global navigation system) receiver (not shown) for obtaining information about the location of device 100.
[0097] 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 tactile feedback module (or instruction set) 133, 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 stores device / global internal state 157, as shown in Figures 1A and 1B. Figure 3. The device / global internal state 157 includes one or more of the following: an active application state, which indicates which applications, if any, are currently active; a display state, which indicates what applications, views, or other information occupy various areas of the touch-sensitive display system 112; a sensor state, which includes information obtained from the device's various sensors and other input or control devices 116; and position and / or orientation information regarding the device's position and / or posture.
[0098] The operating system 126 (e.g., iOS, Darwin, RTXC, LINUX, UNIX, OS X, 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 facilitates communication between various hardware and software components.
[0099] 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 a device that is compatible with some of Apple Inc. (Cupertino, California). iPod A multi-pin (e.g., 30-pin) connector that is the same as, similar to, and / or compatible with the 30-pin connector used in iPod devices. In some embodiments, the external port is compatible with some of Apple Inc. (Cupertino, California) iPod A Lightning connector that is the same as, similar to, and / or compatible with the Lightning connector used in iPod devices.
[0100] The contact / motion module 130 optionally detects contact with the touch-sensitive display system 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 software components for performing various operations related to contact detection (e.g., a finger or stylus), such as determining whether contact has occurred (e.g., detecting a finger down event), determining the strength of the contact (e.g., the force or pressure of the contact, or a surrogate for the force or pressure of the contact), determining whether there has been 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 ceased (e.g., detecting a finger lift event or contact break). The contact / motion module 130 receives contact data from the touch-sensitive surface. Determining the movement of a contact point optionally includes determining a rate (magnitude), velocity (magnitude and direction), and / or acceleration (change in magnitude and / or direction) of the contact point, the movement of which is 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 a stylus contact) or multiple points of contact simultaneously (e.g., "multi-touch" / multi-finger contact and / or stylus contact). In some embodiments, the contact / motion module 130 and the display controller 156 detect contact on the touchpad.
[0101] The contact / motion module 130 optionally detects gesture input from 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 single-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 an icon location). 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. Similarly, taps, swipes, drags, and other gestures of the stylus are optionally detected by detecting a specific contact pattern of the stylus.
[0102] The graphics module 132 includes various known software components for rendering and displaying graphics on the touch-sensitive display system 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.
[0103] 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 specifying the graphics to be displayed from an application program, etc., along with coordinate data and other graphic attribute data, if necessary, and then generates screen image data for output to the display controller 156.
[0104] Haptic feedback module 133 includes various software components for generating instructions used by one or more tactile output generators 163 to produce tactile output at one or more locations on device 100 in response to user interaction with device 100 .
[0105] 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 137, email 140, IM 141, browser 147, and any other application requiring text input).
[0106] The GPS module 135 determines the location of the device and provides this information for use in various applications (e.g., to the phone 138 for location-based dialing; to the camera 143 as picture / video metadata; and to applications that provide location-based services such as a weather widget, local pages widget, and map / navigation widget).
[0107] Application 136 optionally includes the following modules (or instruction sets), or a subset or superset thereof:
[0108] Contacts module 137 (sometimes called address book or contact list);
[0109] Telephone module 138;
[0110] Video conferencing module 139;
[0111] Email client module 140;
[0112] Instant messaging (IM) module 141;
[0113] Fitness support module 142;
[0114] A camera module 143 for still and / or video images;
[0115] Image management module 144;
[0116] Browser module 147;
[0117] Calendar module 148;
[0118] Widget module 149, which optionally includes one or more of the following: weather widget 149-1, stock widget 149-2, calculator widget 149-3, alarm clock widget 149-4, dictionary widget 149-5, and other widgets obtained by the user, and user-created widgets 149-6;
[0119] A widget creator module 150 for forming user-created widgets 149-6;
[0120] Search module 151;
[0121] A video and music player module 152, optionally consisting of a video player module and a music player module;
[0122] Notepad module 153;
[0123] Map module 154; and / or
[0124] Online video module 155.
[0125] 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.
[0126] In combination with the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the contacts module 137 includes executable instructions for managing an address book or contact list (e.g., stored in the application internal state 192 of the contacts module 137 in memory 102 or memory 370), including: adding names to the address book; deleting names from the address book; associating phone numbers, email addresses, physical addresses, or other information with names; associating images with names; categorizing and classifying names; providing phone numbers and / or email addresses to initiate and / or facilitate communications via telephone 138, video conferencing 139, email 140, or instant messaging 141; and so on.
[0127] In conjunction with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, phone module 138 includes executable instructions for entering a character sequence corresponding to a phone number, accessing one or more phone numbers in address book 137, modifying an entered phone number, dialing the corresponding phone number, conducting a conversation, and disconnecting or hanging up when the conversation is complete. As described above, wireless communication optionally uses any of a variety of communication standards, protocols, and technologies.
[0128] In combination with RF circuitry 108, audio circuitry 110, speaker 111, microphone 113, touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, text input module 134, contact list 137, and phone module 138, 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.
[0129] In conjunction with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact 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.
[0130] In conjunction with the RF circuitry 108, the touch-sensitive display system 112, the display controller 156, the contact module 130, the graphics module 132, and the text input module 134, the instant messaging module 141 includes executable instructions for entering a character sequence corresponding to an instant message, modifying previously entered characters, sending the corresponding instant message (e.g., using the Short Message Service (SMS) or Multimedia Message Service (MMS) protocols for phone-based instant messaging or using XMPP, SIMPLE, Apple Push Notification Service (APNs), 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 Service (EMS). As used herein, "instant messaging" refers to both telephony-based messaging (eg, messages sent using SMS or MMS) and Internet-based messaging (eg, messages sent using XMPP, SIMPLE, APNs, or IMPS).
[0131] In combination with RF circuitry 108, touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, map module 154, and music player module 146, fitness support module 142 includes executable instructions for creating a workout (e.g., with time, distance, and / or calorie burn goals); communicating with fitness sensors (in sports equipment and smart watches); receiving fitness sensor data; calibrating sensors for monitoring a workout; selecting and playing music for a workout; and displaying, storing, and transmitting fitness data.
[0132] In conjunction with touch-sensitive display system 112, display controller 156, one or more optical sensors 164, optical sensor controller 158, contact module 130, graphics module 132, and image management module 144, camera module 143 includes executable instructions for capturing still images or videos (including video streams) and storing them in memory 102, modifying characteristics of still images or videos, and / or deleting still images or videos from memory 102.
[0133] In conjunction with touch-sensitive display system 112, display controller 156, contact 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.
[0134] In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, and the text input module 134, the browser module 147 includes executable instructions for browsing the Internet (including searching for, linking to, receiving, and displaying web pages or portions thereof, as well as attachments and other files linked to web pages) in accordance with user instructions.
[0135] In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact 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.
[0136] In conjunction with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget module 149 is a mini-application that is optionally downloaded and used by the user (e.g., the weather desktop widget 149-1, the stock desktop widget 149-2, the calculator desktop widget 149-3, the alarm desktop widget 149-4, and the dictionary desktop widget 149-5), or a mini-application created by the user (e.g., the user-created desktop widget 149-6). In some embodiments, the desktop widget includes HTML (Hypertext Markup Language) files, CSS (Cascading Style Sheets) files, and JavaScript files. In some embodiments, the desktop widget includes XML (Extensible Markup Language) files and JavaScript files (e.g., the Yahoo! desktop widget).
[0137] In combination with the RF circuit 108, the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, the text input module 134, and the browser module 147, the desktop widget creator module 150 includes executable instructions for creating a desktop widget (e.g., transferring a user-specified portion of a web page into a desktop widget).
[0138] In conjunction with the touch-sensitive display system 112, the display system controller 156, the contact module 130, the graphics module 132, and the 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.
[0139] In conjunction with touch-sensitive display system 112, display system controller 156, contact 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), as well as executable instructions for displaying, presenting, or otherwise playing back video (e.g., on touch-sensitive display system 112 or on an external display wirelessly 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.).
[0140] In conjunction with the touch-sensitive display system 112, display controller 156, contact module 130, graphics module 132, and text input module 134, the notes module 153 includes executable instructions for creating and managing notes, to-do lists, etc. according to user instructions.
[0141] In combination with RF circuitry 108, touch-sensitive display system 112, display system controller 156, contact module 130, graphics module 132, text input module 134, GPS module 135, and browser module 147, map module 154 includes executable instructions for receiving, displaying, modifying, and storing maps and data associated with the maps (e.g., driving directions; data about stores and other points of interest at or near a particular location; and other location-based data) in accordance with user instructions.
[0142] In conjunction with touch-sensitive display system 112, display system controller 156, contact 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 executable instructions that allow a user to access, browse, receive (e.g., by streaming and / or downloading), play back (e.g., on touch screen 112 or on an external display connected wirelessly or via external port 124), send an email with a link to a particular 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 particular online video.
[0143] Each module and application identified above corresponds to a set of executable instructions for performing one or more functions and methods described herein (e.g., computer-implemented methods and other information processing methods described herein). These modules (i.e., instruction sets) do not have to be implemented as independent software programs, processes, or modules, so various subsets of these modules are optionally combined or otherwise rearranged in various embodiments. In some embodiments, memory 102 optionally stores a subset of the above modules and data structures. In addition, memory 102 optionally stores other modules and data structures not described above.
[0144] In some embodiments, device 100 is a device in which operation of a predefined set of functions on the device is performed exclusively through a touch screen and / or a touchpad. By using a touch screen and / or a touchpad as the primary input control device for operating device 100, the number of physical input control devices (e.g., push buttons, dials, etc.) on device 100 is optionally reduced.
[0145] A predefined set of functions that are exclusively performed through the touch screen and / or trackpad optionally includes navigation between user interfaces. In some embodiments, the touchpad, when touched by the user, navigates the device 100 from any user interface displayed on the device 100 to a main menu, home menu, or root menu. In such embodiments, the touchpad is used to implement a "menu button." In some other embodiments, the menu button is a physical push button or other physical input control device, rather than a touchpad.
[0146] 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 136, 137 to 155, 380 to 390).
[0147] The event classifier 170 receives event information and determines the application 136-1 and the application view 191 of the application 136-1 to which the event information is to be delivered. The event classifier 170 includes an event monitor 171 and an event dispatcher module 174. In some embodiments, the application 136-1 includes an application internal state 192 that indicates one or more current application views displayed on the touch-sensitive display system 112 when the application is active or executing. In some embodiments, the device / global internal state 157 is used by the event classifier 170 to determine which application(s) is currently active, and the application internal state 192 is used by the event classifier 170 to determine the application view 191 to which the event information is to be delivered.
[0148] 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 the application 136-1 resumes execution, user interface state information indicating information being displayed by the application 136-1 or information ready for display by the application, a state queue for enabling the user to return to a previous state or view of the application 136-1, and a redo / undo queue of previous actions taken by the user.
[0149] Event monitor 171 receives event information from peripherals interface 118. The event information includes information about sub-events (e.g., a user touch on touch-sensitive display system 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 167, one or more gyroscopes 168, one or more magnetometers 169, and / or microphone 113 (via audio circuit 110). The information received by peripherals interface 118 from I / O subsystem 106 includes information from touch-sensitive display system 112 or a touch-sensitive surface.
[0150] 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).
[0151] In some embodiments, the event classifier 170 also includes a hit view determination module 172 and / or an active event identifier determination module 173.
[0152] When the touch-sensitive display system 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.
[0153] 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 programmatic levels within the application's programmatic or view hierarchy. 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 recognized as correct input is optionally determined based at least in part on the hit view of the initial touch that started the touch-based gesture.
[0154] 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 where the sub-events should be processed. In most cases, the hit view is the lowest-level view in which the initiating sub-event (i.e., 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 the hit view determination module, the hit view typically receives all sub-events related to the same touch or input source for which it was identified as the hit view.
[0155] 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 thereby 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, views higher in the hierarchy will still remain actively participating views.
[0156] Event dispatcher module 174 dispatches event information to event recognizers (e.g., event recognizer 180). In some embodiments that include active event recognizer determination module 173, event dispatcher module 174 delivers the event information to the event recognizer determined by active event recognizer determination module 173. In some embodiments, event dispatcher module 174 stores the event information in an event queue, which is retrieved by corresponding event receiver module 182.
[0157] In some embodiments, operating system 126 includes event classifier 170. Alternatively, application 136-1 includes event classifier 170. In another embodiment, event classifier 170 is a standalone module or part of another module stored in memory 102, such as contact / motion module 130.
[0158] 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 that occur within a corresponding view of the application's user interface. Each application view 191 of application 136-1 includes one or more event recognizers 180. Typically, a corresponding application view 191 includes multiple event recognizers 180. In other embodiments, one or more of event recognizers 180 is part of a separate module, such as a user interface toolkit (not shown) or a higher-level object from which application 136-1 inherits methods and other properties. In some embodiments, a corresponding event handler 190 includes one or more of the following: a data updater 176, an object updater 177, a GUI updater 178, and / or event data 179 received from an event classifier 170. Event handler 190 optionally utilizes or calls data updater 176, object updater 177, or GUI updater 178 to update the application's internal state 192. Alternatively, one or more of the application views in application view 191 include one or more corresponding event handlers 190. Additionally, in some embodiments, one or more of data updater 176, object updater 177, and GUI updater 178 are included in the corresponding application view 191.
[0159] A corresponding event identifier 180 receives event information (e.g., event data 179) from event classifier 170 and identifies an event from the event information. Event identifier 180 includes an event receiver 182 and an event comparator 184. In some embodiments, event identifier 180 also includes metadata 183 and at least a subset of event delivery instructions 188 (which optionally include sub-event delivery instructions).
[0160] The event receiver 182 receives event information from the event classifier 170. The event information includes information about sub-events such as touches or touch movements. 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 a touch, the event information optionally also includes the rate and direction of the sub-event. In some embodiments, the event includes the device rotating from one orientation to another (e.g., from a portrait orientation to a landscape 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).
[0161] The event comparator 184 compares the event information with predefined event or sub-event definitions and determines the event or sub-event based on the comparison, or determines or updates the state of the event or sub-event. In some embodiments, the event comparator 184 includes an event definition 186. The event definition 186 includes the definition of the event (e.g., a predefined sequence of sub-events), such as event 1 (187-1), event 2 (187-2), and others. In some embodiments, the sub-events in event 187 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 the displayed object, a first lift (touch end) of a predetermined duration, a second touch (touch start) of a predetermined duration on the displayed object, and a second lift (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 system 112, and lifting of the touch (touch end). In some embodiments, the event also includes information for one or more associated event handlers 190.
[0162] In some embodiments, event definition 187 includes definitions of events for associated user interface objects. 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 system 112, when a touch is detected on touch-sensitive display system 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 the sub-event and the object that triggered the hit test.
[0163] 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 whether the sub-event sequence does or does not correspond to the event type of the event identifier.
[0164] When a corresponding event recognizer 180 determines that a series of sub-events does not match any event in event definition 186, the corresponding event recognizer 180 enters the 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 the sub-events of the ongoing touch-based gesture.
[0165] In some embodiments, the corresponding event identifier 180 includes metadata 183 having configurable properties, flags, and / or lists that indicate how the event delivery system should perform sub-event delivery for actively participating event identifiers. In some embodiments, metadata 183 includes configurable properties, flags, and / or lists that indicate how event identifiers 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.
[0166] 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 an 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 issues a flag associated with the identified event, and the event handler 190 associated with the flag obtains the flag and performs a predefined process.
[0167] In some embodiments, event delivery instructions 188 include sub-event delivery instructions that deliver event information about a sub-event without activating an event handler. Instead, the sub-event delivery instructions deliver the event information to an event handler associated with the sub-event sequence or to an actively participating view. The event handler associated with the sub-event sequence or with the actively participating view receives the event information and performs a predetermined process.
[0168] 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 145. In some embodiments, object updater 177 creates and updates objects used in application 136-1. For example, object updater 176 creates new user interface objects or updates the location 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.
[0169] In some embodiments, one or more event handlers 190 include or have 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.
[0170] It should be understood that the above discussion of event handling for user touches on a touch-sensitive display also applies to other forms of user input utilizing input devices to operate the multifunction device 100, and not all user input is initiated on a touch screen. For example, mouse movement and mouse button presses, optionally in conjunction with single or multiple keyboard presses or holddowns; contact movement on a touchpad, such as taps, drags, scrolls, etc.; stylus input; movement of the device; spoken commands; detected eye movement; biometric input; and / or any combination thereof, are optionally used as input corresponding to sub-events defining the event to be recognized.
[0171] Figure 2 A device with a touch screen (e.g., Figure 1A The portable multifunction device 100 includes a touch-sensitive display system 112 (e.g., a touch screen). The touch screen optionally displays one or more graphics within a user interface (UI) 200. In this embodiment, and in other embodiments described below, a user can select one or more of the graphics by, for example, making gestures on the graphics using one or more fingers 202 (not drawn to scale in the figures) or using one or more styluses 203 (not drawn to scale in the figures). In some embodiments, selection of the one or more graphics occurs when the user breaks contact with the one or more graphics. In some embodiments, the gesture optionally includes one or more taps, one or more swipes (from left to right, from right to left, up and / or down), and / or rolling of a finger that has made contact with the device 100 (from right to left, from left to right, up and / or down). In some implementations or in some cases, inadvertent contact with a graphic does not select the graphic. For example, a swipe gesture that sweeps over an application icon optionally does not select the corresponding application when the gesture corresponding to selection is a tap.
[0172] The device 100 optionally also includes one or more physical buttons, such as a "home" button, or a 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 display.
[0173] In some embodiments, the device 100 includes a touch screen display, a menu button 204, a push button 206 for powering the device on / off and for locking the device, one or more volume adjustment buttons 208, a subscriber identity module (SIM) card slot 210, a headset 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 holding the button in the depressed state for a predefined time interval; to lock the device by pressing the button and releasing the button before the predefined time interval has passed; and / or to unlock the device or initiate an unlocking process. In some embodiments, the device 100 also accepts voice input for activating or deactivating certain functions through the microphone 113. The device 100 also optionally includes one or more contact intensity sensors 165 for detecting the intensity of contact on the touch-sensitive display system 112, and / or one or more tactile output generators 163 for generating tactile output for the user of the device 100.
[0174] Figure 3 3 is a block diagram of an exemplary multifunction device with a display and a touch-sensitive surface according to some embodiments. The device 300 does not have to be portable. In some embodiments, the device 300 is a laptop, a desktop computer, a tablet computer, a multimedia player device, a navigation device, an educational device (such as a children's learning toy), a gaming system, or a control device (e.g., a home controller or an industrial controller). The 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 called chipsets) that interconnect system components and control communications between system components. The 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 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 referenced devices). Figure 1A The one or more tactile output generators 163 described above), sensors 359 (e.g., similar to those described above with reference to Figure 1AThe memory 370 may include touch sensors, optical sensors, contact intensity sensors, proximity sensors, acceleration sensors, gesture and / or magnetic sensors of the sensors 112, 164, 165, 166, 167, 168 and 169 described above. The memory 370 includes high-speed random access memory, such as DRAM, SRAM, DDR RAM or other random access solid-state memory devices; and optionally includes non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices or other non-volatile solid-state storage devices. The memory 370 optionally includes one or more storage devices located remotely from the one or more CPUs 310. In some embodiments, the memory 370 stores information related to the 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.
[0175] Figure 3 Each element in the above-mentioned identified element is optionally stored in one or more memory devices in the previously mentioned memory device.Each module in the above-mentioned identified module corresponds to a group of instructions for performing the functions described above.The above-mentioned identified module or program (that is, instruction set) need not be implemented as independent software program, process or module, so 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 above-mentioned modules and data structure.In addition, memory 370 optionally stores other modules and data structure not described above.
[0176] Attention is now turned to an embodiment of a user interface (“UI”) that is optionally implemented on portable multifunction device 100 .
[0177] Figure 4A An exemplary user interface for an application menu on portable multifunction device 100 is shown according to some embodiments. 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:
[0178] One or more signal strength indicators 402 of one or more wireless communications, such as cellular signals and Wi-Fi signals;
[0179] Time 404;
[0180] Bluetooth indicator 405;
[0181] Battery status indicator 406;
[0182] A tray 408 with icons for commonly used applications, such as:
[0183] o An icon 416 labeled "Phone" for the phone module 138, which optionally includes an indicator 414 of the number of missed calls or voice messages;
[0184] o An icon 418 of the email client module 140 labeled "Mail," which optionally includes an indicator 410 of the number of unread emails;
[0185] o An icon 420 labeled "Browser" for the browser module 147; and
[0186] o An icon 422 labeled “iPod” for the video and music player module 152 (also referred to as the iPod (trademark of Apple Inc.) module 152); and
[0187] Icons for other apps, such as:
[0188] o Icon 424 labeled "Text" of the IM module 141;
[0189] o An icon 426 labeled “Calendar” of the calendar module 148;
[0190] o Icon 428 labeled "Photos" of the image management module 144;
[0191] o An icon 430 labeled “Camera” of the camera module 143;
[0192] ○ An icon 432 labeled “Online Video” of the online video module 155;
[0193] ○ Icon 434 labeled “Stock Market” of the Stock Market widget 149-2;
[0194] o An icon 436 labeled “Map” of the map module 154;
[0195] ○ Icon 438 labeled “Weather” of the weather widget 149-1;
[0196] ○ Icon 440 labeled “Clock” of the alarm clock widget 169-6;
[0197] o An icon 442 labeled “Fitness Support” of the fitness support module 142;
[0198] o An icon 444 labeled "Notepad" of the Notepad module 153; and
[0199] o An icon 446 for a settings application or module that provides access to settings for the device 100 and its various applications 136 .
[0200] It should be noted that Figure 4A The icon labels shown are exemplary only. For example, in some embodiments, icon 422 of 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 a respective application icon includes the name of the application corresponding to the respective 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.
[0201] Figure 4B A touch-sensitive surface 451 (e.g., Figure 3 a device (e.g., a tablet or touchpad 355) Figure 3 Device 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 359 for generating tactile output for a user of device 300.
[0202] Figure 4B A touch-sensitive surface 451 (e.g., Figure 3 a device (e.g., a tablet or touchpad 355) Figure 3 Although many of the examples that follow will be given with reference to input on the touch screen display 112 (where the touch-sensitive surface and the 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 4B ) has a main axis (eg, 451 in FIG. 4B ) corresponding to a main axis (eg, 453 in FIG. 4B ) on a display (eg, 450 ). Figure 4BAccording to these embodiments, the device detects contact with the touch-sensitive surface 451 at a location that corresponds to a corresponding location on the display (e.g., Figure 4B 460 and 462 in (e.g., in Figure 4B , 460 corresponds to 468 and 462 corresponds to 470). Thus, on a touch-sensitive surface (e.g., Figure 4B 451) and a display of a multi-function device (e.g., Figure 4B When the user interface 450 in FIG. 4 is separated, the user input detected by the device on the touch-sensitive surface (e.g., contacts 460 and 462 and their movement) is used by the device to manipulate the user interface on the display. It should be understood that similar methods are optionally used for other user interfaces described herein.
[0203] Additionally, while the examples below are primarily given with reference to finger inputs (e.g., finger contacts, single-finger tap gestures, finger swipe gestures, etc.), 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). For 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 the contact, followed by ceasing to detect the contact). Similarly, when multiple user inputs are detected simultaneously, it should be understood that multiple computer mice are optionally used simultaneously, or mice and finger contacts are optionally used simultaneously.
[0204] User interface and associated processes
[0205] Figure 5A An exemplary meeting space data processing environment 500 is shown, in accordance with some embodiments. While relevant features are shown, those skilled in the art will appreciate from this disclosure that various other features are not shown for the sake of brevity and to avoid obscuring more relevant aspects of the exemplary implementations disclosed herein. To this end, by way of non-limiting example, meeting space data processing environment 500 includes: a controller 510; a scheduling database 525; a network 515; and buildings A...N (e.g., a corporate campus).
[0206] In some embodiments, the controller 510 includes one or more processors and non-volatile memory. According to some embodiments, the controller 510 manages and maintains a scheduling and reservation system for one or more meeting spaces (e.g., conference rooms, open-air meeting spaces, etc.) associated with one or more buildings (e.g., a corporate campus). In some embodiments, the controller 510 maintains and manages a scheduling database 525 that includes a reservation schedule for each of the one or more meeting spaces. In some embodiments, the controller 510 is operated by a scheduling administrator for a particular building or building campus. In some embodiments, the controller 510 is also communicatively coupled to a personnel directory that includes a plurality of users (e.g., employees on a corporate campus) and their corresponding login / biometric credentials.
[0207] For example, Figure 5A As shown, building A includes multiple meeting spaces 1...X. According to some embodiments, each meeting space is associated with two devices. For example, meeting space 1 in building A includes first device 502-A-1 and second device 504-A-1 (e.g., portable multifunction device 100 or device 300). Similarly, meeting space X in building A includes first device 502-AX and second device 504-AX (e.g., portable multifunction device 100 or device 300).
[0208] For example, Figure 5A As shown, building N includes multiple meeting spaces 1...Y. According to some embodiments, each meeting space is associated with two devices. For example, meeting space 1 in building N includes first device 502-N-1 and second device 504-N-1 (e.g., portable multifunction device 100 or device 300). Similarly, meeting space Y in building N includes first device 502-NY and second device 504-NY (e.g., portable multifunction device 100 or device 300).
[0209] For ease of reference, first devices 502-A-1 ... 502-AX and 502-N-1 ... 502-NY are collectively referred to as first devices 502. For ease of reference, second devices 504-A-1 ... 504-AX and 504-N-1 ... 504-NY are collectively referred to as second devices 504. In some embodiments, first devices 502 are located outside the door of the corresponding meeting space, and second devices 504 are located inside the corresponding meeting space. In some embodiments, a single device for the meeting space replaces first device 502 and second device 504.
[0210] In some embodiments, the controller 510 obtains and provides scheduling information from the first device 502 and the second device 504 over a network 515, including any LAN and / or WAN, such as an intranet, extranet, virtual private network, and / or portion of the Internet.
[0211] In some embodiments, a user can remotely schedule a meeting space reservation through an online portal that indicates the availability of meeting spaces within a building campus. In some embodiments, a user can also make a local reservation by accessing a first device 502 or a second device 504 associated with the meeting space. For example, Meeting Space 1 in Building A is available, and a user uses First Device 502-A-1, located outside the door of Meeting Space 1, to take over Meeting Space 1 in Building A for the next hour. In this example, First Device 502-A-1 sends a message to Controller 510 indicating that Meeting Space 1 in Building A is unavailable for the next hour. Continuing with this example, Controller 510 updates Schedule Database 525 to reflect the unavailability of Meeting Space 1 in Building A for the next hour.
[0212] Figure 5B An exemplary meeting space is shown, corresponding to meeting space 1 of building A, according to some embodiments. Figure 5B An exterior elevation view 510 of conference space 1 of building A is shown. Figure 5B As shown, door 512 is the entry point into conference space 1 of building A, and first device 502 -A- 1 is fixed to a wall outside conference space 1 of building A and adjacent to door 512 of conference space 1 of building A.
[0213] Figure 5B Also shown is an interior plan 520 of conference space 1 of building A. Figure 5B As shown, the conference space 1 of building A includes a table 521 and a plurality of chairs 522a, 522b, 522c, 522d, 522e and 522f. The conference space 1 of building A also includes a display 524a, a projector 524b and a telephone 524c. Those skilled in the art will recognize that Figure 5B 1 and 2 illustrate any devices included in the conference space 1 of building A. Thus, in some embodiments, the conference space 1 of building A includes different devices and / or additional devices. In one example, the conference space 1 of building A includes a first display 524a-1 and a second display 524a-2. Figure 5B As shown, meeting space 1 of building A also includes a second device 504-A-1 (eg, a portable tablet or laptop).
[0214] Attention now turns to embodiments of a user interface ("UI") and related processes that can be implemented on an electronic device, such as a portable multifunction device 100 having a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface, or a device 300 having non-volatile memory, a display, an input device, and one or more processors.
[0215] Figures 6A to 6W Figures 1 and 2 illustrate exemplary user interfaces for managing and interacting with a conference space according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Figures 9A to 9B 、 FIG. 10A to FIG. 10B as well as Figures 11A to 11C Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, such as Figure 4B As shown in .
[0216] Figure 6A The first device 502-A-1 is shown displaying the conference status interface 605. Figure 6A As shown, meeting status interface 605 includes meeting space affordance 606, which indicates that first device 502-A-1 corresponds to meeting space 1 of building A and the occupancy limit of meeting space 1 of building A (e.g., because there are six chairs in meeting space 1 of building A, the occupancy limit is six people). When activated (e.g., using contact), meeting space affordance 606 causes the log of meeting space 1 of building A to be displayed (e.g., as shown in FIG. 1 ). Figure 6Q For example, the log indicates: previously or unresolved issues reported for meeting space 1 in building A; cleaning records for meeting space 1 in building A; the last occupant of meeting space 1 in building A; and so on.
[0217] like Figure 6A As shown, the meeting status interface 605 also includes a plurality of attribute icons 608a, 608b, and 608c (collectively referred to as "attribute icons 608"), which indicate devices or features associated with the meeting space 1 of the building A. Figure 6A, first attribute icon 608a indicates that meeting space 1 in building A is equipped with a display, second attribute icon 608b indicates that meeting space 1 in building A includes a video or video conferencing device, and third attribute icon 608c indicates that meeting space 1 in building A includes a projector. When activated (e.g., by contact), attribute icons 608 cause more details about the equipment or features associated with meeting space 1 in building A to be displayed. For example, if first attribute icon 608a is selected, information or details about the display, such as model name, size, age, etc., are displayed.
[0218] like Figure 6A As shown, meeting status interface 605 also includes: the current time (e.g., 9:47); a status indicator 614 that indicates the current availability or reservation status of meeting space 1 in building A; a statement enable representation 616 that, when activated (e.g., using a swipe gesture from left to right or a predefined gesture such as a single-finger tap gesture), causes status indicator 614 to change (e.g., from reservation to meeting in progress / meeting about to start, or from available to meeting in progress); and a scheduling enable representation 618 that, when activated (e.g., using an upward swipe gesture or a predefined gesture such as a single-finger tap gesture), causes the appointment schedule associated with meeting space 1 in building A to be displayed (e.g., Figure 6C ).exist Figure 6A In , status indicator 614 indicates that meeting space 1 in building A is currently reserved by person X, and person X must check in before 10:07. Figure 6A In the example, the statement 616 also prompts the user to "Swipe to Sign In".
[0219] In this example, meeting space 1 in building A is available from 9:30 to 10:00 and is reserved by person X from 10:00 to 11:00. According to some embodiments, status indicator 614 indicates "reserved" between an early check-in threshold 622 (e.g., 15 minutes before the appointment start time) and a check-in deadline 624 (e.g., 7 minutes after the appointment start time). Thus, in some embodiments, status indicator 614 indicates "reserved" when the current time is between the early check-in threshold 622 and the check-in deadline 624. Furthermore, in some embodiments, when the meeting space is available and the current time is between the early check-in threshold 622 and the check-in deadline 624, an affordance 616 is declared enabled to check in to the upcoming appointment.
[0220] In some embodiments, the user is not authenticated as a subscription holder (e.g., Figure 6A X) or invitees (e.g. Figures 6A to 6BThus, any user can check in to person X's appointment from 10:00 to 11:00. In some embodiments, before being able to claim or check in to an appointment, the user is authenticated as the appointment organizer or, optionally, an invitee of the appointment (e.g., 7A to 7C ).
[0221] like Figure 6A As shown, meeting status interface 605 also includes a "Find Space" affordance 610, which, when activated (eg, by contact), causes the Find Space interface to replace the display of meeting status interface 605 (eg, Figure 6T In some embodiments, when the "Find Space" affordance 610 is activated (eg, by contact), the Find Space interface 6105 replaces the display of the meeting status interface 605 (eg, Figure 6T In some embodiments, when the "Find Spaces" affordance 610 is activated (eg, by contact), a list of available meeting spaces is overlaid on the meeting status interface 605 (eg, Figure 7X ).like Figure 6A As shown, meeting status interface 605 also includes a "Report a Problem" affordance 612, which, when activated (eg, by contact), causes the reporting interface to replace meeting status interface 605 (eg, Figure 6K and Figure 7I ).
[0222] Figures 6A to 6B A sequence is shown where a user checks in to an existing reservation for Meeting Space 1 at Building A. Figure 6A Also shown is a left-to-right swipe gesture performed using contact 620 on detection declaration enable representation 616. Figure 6B The status indicator 614 is shown in response to Figure 6A The claim affordance in represents a left-to-right swipe gesture on 616 indicating "meeting in progress." Thus, the user checks in to the appointment starting at 10:00 and claims meeting space 1 of building A before the appointment starts because meeting space 1 of building A is available before the appointment.
[0223] According to some embodiments, when a user checks in to an existing appointment when meeting space is available and the current time is between the early check-in threshold 622 and the appointment start time, the status indicator 614 indicates "meeting in progress." In some embodiments, when a user checks in to an existing appointment when meeting space is available and the current time is between the early check-in threshold 622 and the appointment start time, the status indicator 614 indicates "meeting about to start." Figure 6B As shown, in response to Figure 6AA left-to-right swipe gesture on the declaration enable representation 616 in disables (e.g., no longer displays) the declaration enable representation 616.
[0224] Figures 6B to 6C A sequence showing the appointment schedule for conference space 1 of building A is shown. Figure 6B Also shown is an upward swipe gesture performed using contact 621 on detection arrangement enable representation 618. Figure 6C Shows the response to Figure 6B , and an upward swipe gesture in FIG is used to overlay an appointment schedule 634 associated with meeting space 1 of building A on meeting status interface 605. For example, appointment schedule 634 shows existing appointments for meeting space 1 of building A in the next N hours.
[0225] like Figure 6C As shown, meeting status interface 605 also includes a hide scheduling affordance 632, which, when activated (e.g., using a swipe down gesture or a predefined gesture such as a single-finger tap gesture), stops displaying scheduled appointment 634. For example, scheduled appointment 634 slides upward from the bottom edge of meeting status interface 605 in response to an upward swipe gesture on scheduling affordance 618, and slides downward into the bottom edge of meeting status interface 605 in response to a downward swipe gesture on hide scheduling affordance 632.
[0226] Figures 6D to 6E Another sequence is shown where a user checks in to an existing reservation at Meeting Space 1 in Building A. Figure 6D Similar to and adapted from Figure 6A .therefore, Figure 6A and Figure 6D The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity only the differences are described here. Figure 6D As shown, the current time is 10:05—after the start time of the appointment but before the check-in deadline 624 . Figure 6D A left-to-right swipe gesture with contact 625 on detection declaration enable representation 616 is shown. Figure 6E The status indicator 614 is shown in response to Figure 6E The claim affordance in FIG. 6 indicates a swipe gesture from left to right on 616 indicating “meeting in progress.” Thus, the user checks in to the appointment after it starts and claims meeting space 1 in building A. Figure 6E As shown, in response to Figure 6DA left-to-right swipe gesture on the declaration affordance 616 in disables (e.g., no longer displays) the declaration affordance 616. According to some embodiments, if the user fails to check in to the appointment before the check-in deadline 624, the appointment is canceled and the meeting space is made available for a subsequent local takeover or remote appointment.
[0227] Figures 6F to 6G Yet another sequence is shown where a user checks in to an existing reservation at Meeting Space 1 in Building A. Figure 6F Similar to and adapted from Figure 6A .therefore, Figure 6A and Figure 6F The user interface is similar, and elements labeled with the same reference numbers in the two figures have the same functionality. For the sake of brevity, only the differences are described here. In this example, meeting space 1 in building A is booked from 9:30 to 10:00 by person Y and from 10:00 to 11:00 by person X. Figure 6F As shown, status indicator 614 indicates "meeting in progress" based on the current time (e.g., 9:47) because meeting space 1 in building A is not available before 10:00. Figure 6F , status indicator 614 indicates that meeting space 1 in building A is currently reserved by person Y until 10:00. In FIG6F , affordance 616 also prompts the user to “Slide to check in to the next meeting.”
[0228] According to some embodiments, when an appointment is in progress, status indicator 614 indicates "Meeting in Progress." Additionally, in some embodiments, when the meeting space is unavailable and the current time (e.g., 9:47) is between the early check-in threshold 622 and the appointment start time, an affordance 616 is declared enabled to check in to the upcoming appointment.
[0229] Figure 6G The status indicator 614 is shown in response to Figure 6F The statement in the affordance indicates a swipe gesture from left to right on 616 indicating "meeting is about to start." Therefore, the user checks in to the appointment starting at 10:00. Figure 6G As shown, in response to Figure 6F A left-to-right swipe gesture on the declaration enable representation 616 in disables (e.g., no longer displays) the declaration enable representation 616.
[0230] Figure 6H 6H is similar to and adapted from Figure 6A .therefore, Figure 6A and Figure 6HThe user interface is similar, and elements labeled with the same reference numbers in the two figures have the same functionality. For the sake of brevity, only the differences are described here. In this example, meeting space 1 in building A is booked from 9:30 to 10:00 by person Y and from 10:00 to 11:00 by person X. Figure 6H As shown, status indicator 614 indicates "meeting in progress" based on the current time (e.g., 9:40) because meeting space 1 in building A is not available before 10:00. Figure 6H , status indicator 614 indicates that meeting space 1 in building A is currently booked by person Y until 10:00, and claim affordance 616 is disabled (e.g., no longer displayed). According to some embodiments, claim affordance 616 is disabled when the meeting space is unavailable and the current time (e.g., 9:40) is before the early check-in threshold 622 for the next appointment (e.g., person X's appointment at 10:00).
[0231] Figures 6I to 6J The sequence is shown in which a user takes over meeting space 1 in building A when it becomes available. Figure 6I Similar to and adapted from Figure 6A .therefore, Figure 6A and Figure 6I The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity, only the differences are described here. In this example, meeting space 1 in building A is available from 9:30 to 10:00 and is reserved by person X from 10:00 to 11:00. Figure 6I As shown, status indicator 614 indicates "Available" based on the current time (e.g., 9:40) because meeting space 1 of building A is available before 10:00. Figure 6I , the indicator states that 616 is enabled and also prompts the user to "Slide to take over before 10:00."
[0232] According to some embodiments, status indicator 614 indicates "Available" when the meeting space is available and the current time (e.g., 9:40) is before the next appointment's early check-in threshold 622. According to some embodiments, affordance 616 is declared enabled to take over the meeting space when the meeting space is available and there is a threshold amount of time before the next appointment based on the current time (e.g., 20 or 30 minutes).
[0233] Figure 6I A left-to-right swipe gesture performed with contact 636 on detection declaration enable representation 616 is shown. Figure 6J The status indicator 614 is shown in response to Figure 6IThe claim affordance in represents a swipe gesture from left to right on 616 indicating "meeting in progress." Thus, the user takes over / claims meeting space 1 in building A until the next appointment. Figure 6J As shown, in response to Figure 6I A left-to-right swipe gesture on the declaration enable representation 616 in disables (e.g., no longer displays) the declaration enable representation 616.
[0234] Figures 6J to 6O A sequence in which a user reports a problem with Space 1 of Building A is shown. Figure 6J Detection of contact 638 at a location corresponding to "Report a Problem" affordance 612 is shown. FIG. 6K shows a Figure 6J The “Report Problem” option in the display can indicate the selection of 612 and replace the display of the meeting status interface 605 with the reporting interface 655.
[0235] like Figure 6K As shown, the reporting interface 655 includes a cancel indicator 654a, which, when activated (e.g., by contact), causes the reporting interface 655 to be Figure 6J and the next step can indicate 654b, which, when activated (eg, using contact), causes the reporting interface 655 to be identified interface (eg, Figure 6M ) is replaced. Figure 6K As shown, the reporting interface 655 also includes multiple enable indications 656a, 656b, 656c, 656d, 656e, 656f, 656g, 656h, 656i, 656j, 656k and 656l (collectively referred to as "enabled indications" 656) for reporting equipment or feature problems associated with meeting space 1 of building A (e.g., telephone, lighting, chairs, displays, tables, projectors, power supplies, etc.) and / or for requesting service options for meeting space 1 of building A (e.g., cleaning, refreshments, supplies, etc.).
[0236] Figure 6K Also shown is detection of contact 662 at a location corresponding to affordance 656h (which was provided to report a projector problem in meeting space 1 of building A). Figure 6L A badge 657 is shown displayed within affordance 656h in response to Figure 6K The enable indication 656h in the badge indicates that the enable indication 656h has been selected.
[0237] Figure 6L Also shown is detection of contact 664 at a location corresponding to next enable indication 654b. Figure 6M Shows the response to Figure 6LThe next step in the display can indicate the selection of 654b and replace the display of the report interface 655 with the identification interface 675.
[0238] like Figure 6M As shown, the identification interface 675 includes a back indicator 674a, which, when activated (e.g., using contact), causes the identification interface 675 to be Figure 6L and sending affordance 674b, which, when activated (e.g., by contact), initiates a process for generating a problem report or service request associated with the projector in conference space 1 of building A. For example, referring to Figure 5B , device 504-A-1 sends a message to controller 510 indicating that there is a problem associated with the projector in meeting space 1 of building A. In this example, the administrator can then contact the service department of building A to assess the problem. Alternatively, in another example, device 504-A-1 sends a message directly to the service department of building A indicating that there is a problem associated with the projector in meeting space 1 of building A.
[0239] like Figure 6M As shown, identification interface 675 also includes a plurality of affordances 676a, 676b, and 676c (collectively, "affordances 676") that are provided to identify the user reporting the problem. According to some embodiments, affordances 676 are determined based on the next appointment, the previous appointment, and / or the current appointment for meeting space 1 in building A. Figure 6M , an enable indication 676a is provided to identify the user who initiated the problem report as the organizer of the current appointment, an enable indication 676b is provided to identify the user who initiated the problem report as the meeting invitee A of the current appointment, and an enable indication 676c is provided to identify the user who initiated the problem report as an unlisted person.
[0240] Figure 6M Also shown is detection of contact 666 at a location corresponding to affordance 676c. FIG. 6N shows an example of a Figure 6M Selection of affordance 676c in displays a text input field 678 within identification interface 675 for entering the email address of the user initiating the problem report. FIG6N also illustrates detecting contact 680 at a location corresponding to text input field 678.
[0241] For example, a user of device 502-A-1 enters his / her email address into text entry field 678 via a software keyboard and selects send affordance 674b (not shown). Figure 6O Display message 677 is shown indicating that a problem report associated with the projector in meeting space 1 in building A was successfully submitted. Figure 6O , message 677 also indicates that the originator of the problem report will be contacted for confirmation and if additional information is required.
[0242] Figures 6P to 6Q A sequence is shown in which the meeting status interface 605 indicates a problem reported for Space 1 of Building A. Figure 6P Similar to and adapted from Figure 6J .therefore, Figure 6A and Figure 6J A similar user interface is included, and elements labeled with the same reference numbers in both figures have the same function, and for the sake of brevity, only the differences are described here. Figure 6P Shown is a badge 682 displayed within the meeting space affordance 606 in response to Figures 6J to 6O A problem report is generated and submitted in , the badge indicates an unresolved issue associated with meeting space 1 in building A. Figure 6P Also shown is detection of contact 684 at a location corresponding to meeting space affordance 606. Figure 6Q Shows the response to Figure 6P The conference space in the display can indicate the selection of 606 and display the log 686 overlaid on the conference status interface 605. Figure 6Q As shown, log 686 lists the meetings associated with meeting space 1 in building A (e.g., Figures 6J to 6O The nature, time, and date of the open issue 685 (associated with the problem report generated and submitted in ).
[0243] Figures 6Q to 6R Reporting interface 655 is shown indicating a sequence of reported issues with Space 1 of Building A. Figure 6Q Also shown is detection of contact 688 at a location corresponding to the "Report a Problem" enable indication 612. Figure 6R Shows the response to Figure 6Q The “Report Problem” option in the display can indicate the selection of 612 and replace the display of the meeting status interface 605 with the reporting interface 655.
[0244] Figure 6R Similar to and adapted from Figures 6K to 6L .therefore, Figures 6K to 6L as well as Figure 6R The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity only the differences are described here. Figure 6R As shown, a badge 690 is displayed within affordance 656h indicating that a problem report has been reported associated with the projector. Figure 6RAs shown, the time and date of the problem report associated with the projector is also displayed within affordance 656h. According to some embodiments, after a problem is submitted for a corresponding feature of meeting space 1 in building A, the corresponding affordance 656 is disabled to avoid duplicate problem reporting.
[0245] Figure 6R Also shown is detection of contact 692 at a location corresponding to the cancel-indication 654a. Figure 6S Shows the response to Figure 6R The cancel indicator in represents the selection of 654a and replaces the display of the report interface 655 with the meeting status interface 605. Figure 6S Similar to and adapted from Figure 6J .therefore, Figure 6J and Figure 6S A similar user interface is included, and elements labeled with the same reference numbers in both figures have the same function, and for the sake of brevity, only the differences are described here.
[0246] Figures 6S to 6W The sequence of a user taking over another available meeting space through the find space interface 6105 is shown. Figure 6S Also shown is detection of contact 694 at a location corresponding to the "find space" enable indication 610. Figure 6T Shows the response to Figure 6S The selection of the "Find Space" icon 610 in FIG. 6 replaces the display of the conference status interface 605 with the search space interface 6105 associated with building A. Figure 6T As shown, the search space interface 6105 includes a cancel affordance 6104a that, when activated (e.g., by contact), causes the search space interface 6105 to be Figure 6S ; and a floor indicator 6104b, which indicates the floor associated with the floor plan displayed within the search space interface 6105 (e.g., the first floor of building A) and is provided to display floor plans of different floors of building A within the search space interface 6105.
[0247] exist Figure 6T , find space interface 6105 displays a floor plan of the first floor of building A and an indicator 6106 of the location of device 502-A-1. According to some embodiments, the user of device 502-A-1 can navigate the floor plan by pinching to zoom in or out and dragging to pan east, west, north, or south. Figure 6T , search space interface 6105 includes a centering affordance 6111 that, when activated (e.g., by contact), re-centers the plan view within search space interface 6105 around indicator 6106;
[0248] like Figure 6T As shown, the search space interface 6105 also includes a first plurality of unavailable meeting spaces 6112a and 6112b (collectively referred to as "unavailable meeting spaces 6112") having a first appearance (e.g., a first shadow pattern). For example, meeting space 1 of building A corresponds to unavailable meeting space 6112a. Figure 6T As shown, the find space interface 6105 also includes a second plurality of available meeting spaces 6114a, 6114b, and 6114c (collectively, "available meeting spaces 6114") having a second appearance (e.g., a second shading pattern). According to some embodiments, when the corresponding available meeting space 6114 is activated (e.g., selected using contact), a path from the indicator 6106 to the corresponding available meeting space 6114 is overlaid on the floor plan within the find space interface 6105 (e.g., as shown in FIG6U). According to some embodiments, when the corresponding available meeting space 6114 is activated (e.g., selected using contact), a menu is overlaid on the floor plan within the find space interface 6105, wherein the menu includes details of the corresponding available meeting space 6114 and an affordance provided to take over or reserve the corresponding available meeting space 6114 (e.g., as shown in FIG6U). Figure 6U shown).
[0249] like Figure 6T As shown, find space interface 6105 also includes more meeting spaces affordance 6108, which, when activated (e.g., by contact), causes a list of available meeting spaces in building A to be displayed within find space interface 6105. According to some embodiments, the list of available meeting spaces is sorted based at least in part on proximity to the location of device 502-A-1. According to some embodiments, the list of available meeting spaces is sorted based at least in part on a set of one or more filtering criteria (e.g., number of chairs, projectors, video conferencing equipment, etc.) provided by a user of device 502-A-1.
[0250] Figure 6T Also shown is detection of contact 6110 at a location corresponding to floor enable indication 6104b. Figure 6U Shown is a display of: a first enable representation 6116a associated with the first floor of building A, which is disabled because the floor plan of the first floor of building A is currently displayed within the search space interface 6105; and a second enable representation 6116b associated with the second floor of building A, which, when activated (e.g., by contact), causes the floor plan of the first floor of building A to be replaced by the floor plan of the second floor of building A within the search space interface 6105.
[0251] Figure 6UAlso shown is detection of contact 6118 at a location corresponding to available meeting space 6114c. Figure 6V Shows the response to Figure 6U Selection of available meeting space 6114c in FIG. 1 displays a path 6126 from indicator 6106 to the door of available meeting space 6114c overlaid on the floor plan of the first floor of Building A. Figure 6V Also shown is the response to Figure 6U The menu 6120 associated with the available meeting space 6114c is displayed by selecting the available meeting space 6114c. Figure 6V As shown, menu 6120 includes properties of available meeting space 6114c, such as an occupancy limit of available meeting space 6114c (e.g., six people) and icons corresponding to devices included in available meeting space 6114c (e.g., a display, a video conferencing device, and a projector). Figure 6V As shown, menu 6120 also includes a takeover affordance 6122, which, when activated (eg, using contact), causes available meeting space 6114c to be taken over by the user of device 502-A-1 until 11:00.
[0252] Figure 6V Also shown is detection of contact 6124 at a location corresponding to the takeover enable indication 6122. Figure 6W Shows the response to Figure 6V The takeover indicator 6122 is selected to change the available conference space 6114c into the unavailable conference space 6112c. Figure 6W Similar to and adapted from Figure 6T and Figure 6V .therefore, Figure 6T 、 Figure 6V and Figure 6W The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity only the differences are described here. Figure 6W As shown, unavailable meeting space 6112c is displayed in the find space interface 6105 with a first appearance (eg, a first shadow pattern).
[0253] Figures 7A to 7Z Figures 1 and 2 illustrate exemplary user interfaces for managing and interacting with a conference space according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including Figures 9A to 9B 、 FIG. 10A to FIG. 10B as well as Figures 11A to 11C Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, such as Figure 4B As shown in .
[0254] Figure 7A The first device 504-A-1 is shown displaying the conference status interface 705. Figure 7A As shown, meeting status interface 705 includes meeting space affordance 706, which indicates that first device 504-A-1 corresponds to meeting space 1 of building A and the occupancy limit of meeting space 1 of building A (e.g., because there are six chairs in meeting space 1 of building A, the occupancy limit is six people). When activated (e.g., using contact), meeting space affordance 706 causes the log of meeting space 1 of building A to be displayed (e.g., as shown in FIG. 1 ). Figure 6Q For example, the log indicates: previously or unresolved issues reported for meeting space 1 in building A; cleaning records for meeting space 1 in building A; the last occupant of meeting space 1 in building A; and so on.
[0255] like Figure 7A As shown, the meeting status interface 705 also includes a plurality of attribute icons 708a, 708b, and 708c (collectively referred to as "attribute icons 708"), which indicate devices or features associated with the meeting space 1 of the building A. Figure 7A , first attribute icon 708a indicates that meeting space 1 in building A is equipped with a display, second attribute icon 708b indicates that meeting space 1 in building A includes a video or video conferencing device, and third attribute icon 708c indicates that meeting space 1 in building A includes a projector. When activated (e.g., by contact), attribute icons 708 cause more details about the equipment or features of meeting space 1 in building A to be displayed. For example, if first attribute icon 708a is selected, information or details about the display, such as model name, size, age, etc., are displayed.
[0256] like Figure 7A As shown, meeting status interface 705 also includes: the current time (e.g., 10:01); a status indicator 714 that indicates the current availability or reservation status of meeting space 1 in building A; a statement enable representation 716 that, when activated (e.g., using a swipe gesture from left to right or a predefined gesture such as a single-finger tap gesture), causes status indicator 714 to change (e.g., from reservation to meeting in progress / meeting about to start, or from available to meeting in progress); and a scheduling enable representation 718 that, when activated (e.g., using an upward swipe gesture or a predefined gesture such as a single-finger tap gesture), causes the reservation schedule associated with meeting space 1 in building A to be displayed (e.g., Figure 6C ).exist Figure 7AIn , status indicator 714 indicates that meeting space 1 in building A is currently reserved by person X, and person X must check in before 10:07. Figure 7A In the example, the indicator 716 also prompts the user to "Swipe to Sign In".
[0257] In this example, meeting space 1 in building A is available from 9:30 to 10:00 and is reserved by person X from 10:00 to 11:00. According to some embodiments, status indicator 714 indicates "reserved" between an early check-in threshold 711 (e.g., 15 minutes before the appointment start time) and a check-in deadline 713 (e.g., 7 minutes after the appointment start time). Thus, in some embodiments, status indicator 714 indicates "reserved" when the current time is between the early check-in threshold 711 and the check-in deadline 713. Furthermore, in some embodiments, when the meeting space is available and the current time is between the early check-in threshold 711 and the check-in deadline 713, an affordance 716 is declared enabled to check in to the upcoming appointment.
[0258] Figures 7A to 7Z The conference status interface 705 in is similar to and adapted from Figures 6A to 6W Thus, according to some embodiments, the status indicator 714 and the statement affordance 716 of the conference status interface 705 are configured as follows: Figures 6A to 6W The same principles described with reference to the conference status interface 605 work.
[0259] 7A to 7C Shown is the sequence for authenticating a user before signing in to an existing reservation. Figure 7A A left-to-right swipe gesture performed with contact 722 on detection declaration enable representation 716 is shown. Figure 7B Shows the response to Figure 7A The statement in the enable representation represents a left-to-right swipe gesture on 716 to replace the display of the conference status interface 705 with the authentication interface 745.
[0260] like Figure 7B As shown, the authentication interface 745 prompts the user to log in to his / her account. Figure 7B , the authentication interface 745 includes: a first text input field 742a, which is provided for inputting a user's account name; a second text input field 742b, which is provided for inputting a user's password; a cancel enable indication 744a, which, when activated (e.g., by contact), causes the authentication interface 745 to be Figure 7Aand a login affordance 744b which, when activated (e.g., using contact), causes the credentials entered in the first text input field 742a and the second text input field 742b to be verified (e.g., by Figure 5A In some embodiments, the authentication interface 745 prompts or enables the input of biometric authentication information (such as a fingerprint signature, voice signature, retinal signature, etc.).
[0261] Figure 7B Also shown is detecting contact 746 at a location corresponding to first text input field 742. For example, in response to Figure 7B Selection of the first text input field 742 in the software keyboard 745 (in Figure 7C Continuing with this example, the user utilizes software keyboard 745 to fill in first text input field 742a and second text input field 742b with his / her account credentials.
[0262] Figures 7C to 7D A sequence is shown in which meeting list interface 750 is displayed in response to verifying account credentials entered by a user of device 504 -A- 1 . Figure 7C Detection of contact 748 at a location corresponding to log-in enable indication 744b is shown. Figure 7D Shows the response to Figure 7C The meeting list interface 750 (e.g., with Figure 7A 00 to 11:00 shown in the figure) replaces the display of the authentication interface 745.
[0263] like Figure 7D As shown, meeting list interface 750 includes a chrome area 753a, a sidebar area 753b, a first content area 754a, and a second content area 754b. Chrome area 753a includes: the current time (e.g., 10:01); a meeting space affordance 706; and an end meeting affordance 754, which, when activated (e.g., using contact), causes the balance of the current appointment to be canceled and also causes meeting list interface 750 to be replaced by meeting status interface 705, wherein, in some cases, status indicator 714 indicates that the room is available. According to some embodiments, reference Figure 5A In response to selecting end meeting affordance 754, device 504-A-1 sends a message to controller 510 indicating that meeting space 1 in building A is now available. Controller 510 then updates schedule database 525 to release meeting space 1 in building A for subsequent local takeover or remote reservation.
[0264] The sidebar region 753b includes a first affordance 752a that is provided to display the meeting list interface 750 (currently active); a second affordance 752b that is provided to display the control interface 780 (e.g., Figure 7H ); a third indication 752c, which is provided to display a report interface 790 (e.g., in Figure 7I and a fourth affordance 752d, which is provided to display a search space interface (e.g., in Figure 6U and Figure 7X shown in ).
[0265] exist Figure 7D , first content area 754a includes: a first affordance 756a provided to display invitees associated with the current appointment (current activity); and a second affordance 756b provided to display the appointment schedule for meeting space 1 in building A (e.g., Figure 7M As shown in Figure 7D As shown, first content area 754a (which is currently in invitee mode, as indicated by the shading of first affordance 756a) displays a current appointment with meeting space 1 in building A from 10:00 to 11:00 (e.g., as shown in FIG. Figure 7A 758a, 758b, 758c, 758d, and 758e (collectively, "invitees 758") associated with the invitation. Figure 7D In the example, each invitee 758 is associated with a name, a participation request (e.g., required or optional), and an RSVP status. For example, invitee 758a is associated with a check mark icon 759a, which indicates that invitee 758a has accepted the appointment / meeting invitation. In another example, invitee 758d is associated with a question mark icon 759b, which indicates that invitee 758d has made a tentative response to the appointment / meeting invitation. In another example, invitee 758e is associated with an X icon 759c, which indicates that invitee 758e has responded by declining the appointment / meeting invitation.
[0266] exist Figure 7D , the second content area 754b shows a current reservation with meeting space 1 in building A from 10:00 to 11:00 (e.g., as shown in FIG. Figure 7A As shown) the details associated with Figure 7DAs shown, the second content area 754b includes: the duration of the current meeting / appointment (e.g., 10:00 to 11:00), the meeting title, meeting comments, and attachments 760a and 760b associated with the meeting invitation, which, when activated (e.g., using a touch), cause the attachments to be downloaded and also cause device 504-A-1 to provide an option for displaying the attachments. Figure 7D As shown, the second content area 754b also includes multiple enable representations 762a, 762b, 762c, 762d and 762e (collectively referred to as "enable representations 762"), which are provided to access and control devices or features associated with meeting space 1 of building A through device 504-A-1.
[0267] Figure 7D Also shown is the detection of contact 764 at a location corresponding to invitee 758d who made a tentative response to the meeting / appointment invitation. Figure 7E Shown is a display contacts menu 766, which is provided in response to Figure 7D The invitee 758d is contacted based on the selection of the invitee 758d. Figure 7E As shown, the contact menu 766 includes: a first enable representation 768a, which is provided for calling the mobile phone of the invitee 758d through the device 504-A-1 or the device associated with the conference space 1 of the building A; a second enable representation 768b, which is provided for calling the work phone of the invitee 758d through the device 504-A-1 or the device associated with the conference space 1 of the building A; a third enable representation 768c, which is provided for sending an instant message or SMS to the invitee 758d through the device 504-A-1 or the device associated with the conference space 1 of the building A; and a fourth enable representation 768d, which is provided for sending an email to the work email address of the invitee 758d through the device 504-A-1 or the device associated with the conference space 1 of the building A.
[0268] Figure 7E Also shown is detection of contact 770 at a location corresponding to end meeting indicator 754. Figure 7F Shows the response to Figure 7E The selection of the end meeting indication 754 in the display will display the end meeting prompt 772 covered on the meeting list interface 750. Figure 7F As shown, the end meeting prompt 772 indicates that the user can exit from device 504-A-1 and cancel the remaining reservation, and then another user can take over. Figure 7F As shown, the end meeting prompt 772 includes: a cancel enable indication 774a, which is provided to cancel the end meeting operation; and an end meeting enable indication 774b, which is provided to confirm the end meeting operation.
[0269] Figure 7F Also shown is detection of contact 776 at a location corresponding to the cancel-indication 774a. Figure 7G Shows the response to Figure 7F The cancel indicator in indicates the selection of 774a and stops displaying the end meeting prompt 772. Figure 7G Similar to and adapted from Figure 7D .therefore, Figure 7D and Figure 7G A similar user interface is included, and elements labeled with the same reference numbers in both figures have the same function, and for the sake of brevity, only the differences are described here.
[0270] Figures 7G to 7H A sequence is shown in which meeting list interface 750 is replaced with control interface 780 . Figure 7G Also shown is detection of contact 778 at a location corresponding to second enable indication 752b in sidebar area 753b. Figure 7H Shows the response to Figure 7G The second indicator in represents the selection of 752b and replaces the display of the meeting list interface 750 with the control interface 780. Figure 7H Similar to and adapted from Figure 7D .therefore, Figure 7D and Figure 7H The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity only the differences are described here. Figure 7H As shown, the control interface 780 includes a chrome area 753a, a sidebar area 753b, a first control area 781a and a second control area 781b.
[0271] like Figure 7H As shown, the first control area 781a includes a list of control enable representations 782a, 782b, 782c, 782d, 782e, 782f, and 782g (collectively referred to as "control enable representations 782"), which are provided to concentrate the corresponding controls in the second control area 781b. According to some embodiments, the control enable representation list 782 corresponds to the device or feature associated with the meeting space 1 of the building A. Therefore, the user is able to use the control interface 780 to control the device or feature associated with the meeting space 1 of the building A through the device 504-A-1. Figure 7H, the first control area 781a further includes: a preset enable indication 784a, which is provided to set devices or features associated with meeting space 1 of building A to predefined settings (e.g., turning off the display, setting the temperature to room temperature, turning off the lights, etc.); and an add enable indication 784b, which is provided to add custom controls.
[0272] like Figure 7H As shown, the second control area 781b includes a plurality of controls 784a, 784b, 784d, 784d, 784d, and 784e for adjusting respective devices or features associated with meeting space 1 of building A. For example, control 784c is a slider provided to adjust the zoom of camera #1.
[0273] Figures 7H to 7I A sequence is shown in which control interface 780 is replaced with reporting interface 790 . Figure 7H Also shown is detection of contact 788 at a location corresponding to third enable indication 752c in sidebar area 753b. Figure 7I Shows the response to Figure 7H The third indicator in the figure indicates the selection of 752c and replaces the display of the control interface 780 with the report interface 790. Figure 7I Similar to and adapted from Figure 7D .therefore, Figure 7D and Figure 7I The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity only the differences are described here. Figure 7I As shown, the report interface 790 includes a chrome area 753a, a sidebar area 753b, a first problem reporting area 794a and a second problem reporting area 794b.
[0274] like Figure 7I As shown, first problem reporting region 794a includes a list of affordances 792a, 792b, 792c, 792d, 792e, 792f, 792g, 792h, 792i, 792j, and 792k (collectively, "affordance list 792") that are provided to generate a problem report or service request for corresponding services or features associated with meeting space 1 of building A. For example, selecting affordance 792a (e.g., using a contact) results in generating a service request for cleaning meeting space 1 of building A. For another example, selecting affordance 792g (e.g., using a contact) results in generating a problem report indicating a problem with a telephone in meeting space 1 of building A.
[0275] like Figure 7I As shown, the second problem reporting area 794b includes an image of meeting space 1 of building A. Figure 7I , affordances 794a, 794b, 794c, 794d, 794e, 794f, and 794g (collectively, "affordances 794") are co-located with at least some of the devices or features of meeting space 1 of building A. Affordances 794 are provided to generate problem reports or service requests for the corresponding features associated with meeting space 1 of building A. For example, selecting affordance 794b (e.g., using a contact) results in the generation of a problem report indicating a problem with display #2 of meeting space 1 of building A. For another example, selecting affordance 794g (e.g., using a contact) results in the generation of a problem report indicating a problem with a chair of meeting space 1 of building A.
[0276] Figures 7I to 7K A sequence for generating a problem report for a feature of Meeting Space 1 of Building A using reporting interface 790 is shown. Figure 7I Also shown is detecting contact 7100 at a location corresponding to enable indication 794a within second problem reporting area 794b. Figure 7J Shows the response to Figure 7I The "Report Problem" enable indication 798 is displayed in the first problem reporting area 794a based on the selection of the enable indication 794a. Figure 7J Similar to and adapted from Figure 7I .therefore, Figure 7I and Figure 7J The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity only the differences are described here. Figure 7J As shown, in response to Figure 7I 794a, a help prompt 7102 is overlaid on the second problem reporting area 794b. For example, when activated (e.g., using contact), the help prompt 7102 enables the user of the device 504-A-1 to enter a description of the problem or more details associated with the problem.
[0277] Figure 7J Also shown is detection of contact 7104 at a location corresponding to the "Report a Problem" enable indication 798 within the first problem reporting area 794a. Figure 7K Shows the response to Figure 7J Selection of "Report a Problem" enable representation 798 in the display 7106 displays an alert indicating that a problem report has been reported for the feature associated with the enable representations 792c and 794a (e.g., display #1). For example, alert 7106 indicates the time and date the problem report was submitted, and the user who initiated the problem report (e.g., the user currently logged into device 504-A-1).
[0278] Figures 7K to 7L A sequence is shown where the report interface 790 is replaced with the meeting list interface 750 . Figure 7K Also shown is detection of contact 7108 at a location corresponding to first enable indication 752a within sidebar area 753b. Figure 7L Shows the response to Figure 7L The first indicator in the diagram indicates selection 752a and replaces the display of the report interface 790 with the meeting list interface 750. Figure 7L Similar to and adapted from Figure 7D .therefore, Figure 7D and Figure 7L A similar user interface is included, and elements labeled with the same reference numbers in both figures have the same function, and for the sake of brevity, only the differences are described here.
[0279] Figures 7L to 7M A sequence is shown for changing the first content area 754a of the meeting list interface 750 from invitee mode to scheduling mode. Figure 7L Also shown is detection of contact 7110 at a location corresponding to arrange-enable representation 756b within first content region 754a. Figure 7M The display of invitee affordance list 758 is shown replaced with an appointment schedule associated with meeting space 1 of building A within first content area 754a.
[0280] Figure 7N 7. The first alert message 7120 is shown displayed overlaid on the meeting list interface 750. According to some embodiments, the first alert message 7120 is displayed when the current time (e.g., 10:45) is less than 15 minutes before the end of the appointment and there is another appointment for the meeting space after the current appointment. Figure 7N As shown, first alert message 7120 indicates that the current meeting is about to end and meeting space 1 of building A is reserved for another meeting. First alert message 7120 also indicates that the user can extend the current meeting in another meeting space if additional time is needed.
[0281] like Figure 7N As shown, the first alert message 7120 includes a search space affordance 7122a, which is provided to display a search space interface (e.g., Figure 6T and Figure 7Y ), so that the user can find another meeting space to take over if additional time is needed for the current meeting; and a disabling indication 7122b, which is provided to stop displaying the first alert message 7120. Figure 7N Also shown is detection of contact 7126 at a location corresponding to the release indication 7122b.
[0282] Figure 7O 7O , the second alert message 7130 is shown displayed overlaid on the meeting list interface 750. According to some embodiments, the second alert message 7130 is displayed when the current time (e.g., 10:45) is less than 15 minutes before the end of the appointment and the meeting space is available at the end of the current appointment. As shown in FIG. 7O , the second alert message 7130 indicates that the current meeting is about to end and that meeting space 1 in building A is available at the end of the current meeting. The second alert message 7130 also indicates that the user can extend the current appointment in meeting space 1 in building A if additional time is needed. Figure 7O As shown, the second alarm message 7130 includes: an add time enable indication 7132a, which is provided to extend the current appointment in meeting space 1 of building A by adding 30 minutes to the current appointment; and a release enable indication 7132b, which is provided to stop displaying the second alarm message 7130.
[0283] Figure 7P Notification 7140 is shown displayed overlaid on meeting list interface 750. According to some embodiments, notification 7140 is displayed when the user signs in to the next appointment using device 502-A-1. Figure 7P As shown, notification 7140 indicates that 2 people have checked in to a reservation for meeting space 1 in building A from 11:00 to 12:00. Figure 7P , notification 7140 includes a disabling indicator 7142 that is provided to stop displaying notification 7140. Figure 7P As shown, a countdown is displayed in the second content area 754b. According to some embodiments, a countdown is displayed when the current time (e.g., 10:45) is less than 15 minutes before the end of the appointment. Figure 7P Also shown is detection of contact 7144 at a location corresponding to the release indication 7142.
[0284] Figure 7Q 7146 is shown displayed overlaid on the meeting list interface 750. For example, according to some embodiments, the alert 7146 counts down the last 10 seconds of the current appointment. Figure 7Q As shown, alert 7146 indicates that the current appointment will end in 10 seconds.
[0285] Figure 7R Alert 7148 is shown displayed overlaid on meeting list interface 750. For example, according to some embodiments, alert 7148 is displayed once the current appointment ends. Figure 7R As shown, alert 7148 indicates that the current appointment has ended and the user has logged out of device 504-A-1.
[0286] Figure 7S Similar to and adapted from Figure 7A .therefore, Figure 7A and Figure 7S Similar user interfaces are included, and elements labeled with the same reference numbers in both figures have the same function, and for the sake of brevity, only the differences are described here. Figure 7S The first device 504-A-1 is shown displaying the meeting status interface 705. In this example, the meeting space 1 of the building A is available from 9:00 to 10:00 and is reserved by person X from 10:00 to 11:00. Figure 7S As shown, status indicator 714 indicates "Available" based on the current time (e.g., 9:20) because meeting space 1 of building A is available before 10:00. Figure 7S , the indicator states that 716 is enabled and also prompts the user to "Slide to take over before 10:00."
[0287] According to some embodiments, status indicator 714 indicates "Available" when the meeting space is available and the current time (e.g., 9:20) is before the next appointment's early check-in threshold 711. According to some embodiments, affordance 716 is declared enabled to take over the meeting space when the meeting space is available and there is a threshold amount of time before the next appointment based on the current time (e.g., 20 or 30 minutes).
[0288] Figures 7S to 7T Shown is the sequence in which a user takes over an available room without authentication. Figure 7S A left-to-right swipe gesture performed using contact 7112 on detection declaration enable representation 716 is shown. Figure 7T Shows the response to Figure 7S The statement in the enabling representation 716 replaces the display of the meeting status interface 705 with the meeting list interface 750 by a left-to-right swipe gesture on the meeting status interface 705 . Figure 7T Similar to and adapted from Figure 7M .therefore, Figure 7M and Figure 7T The user interface is similar and elements labeled with the same reference numbers in the two figures have the same function, and for the sake of brevity only the differences are described here. Figure 7T As shown, the second content area 754b does not include any meeting details because meeting space 1 in building A is currently open with no existing reservations. Figure 7S was taken over. Figure 7T , the second content area 754b includes a countdown for the takeover period of meeting space 1 of building A.
[0289] Figure 7U5. The display of meeting status interface 705 is shown in response to device 504-A-1 entering standby mode. For example, according to some embodiments, after displaying meeting list interface 750 for a predefined timeout duration (e.g., 5 minutes) without any user input or interaction, meeting status interface 705 replaces meeting list interface 750, as shown in FIG. Figure 7U shown. Figure 7U Similar to and adapted from Figure 7A .therefore, Figure 7A and Figure 7U The user interfaces are similar and elements labeled with the same reference numbers in the two figures have the same functions, and for the sake of brevity, only the differences are described here. According to some embodiments, when a meeting / appointment is in progress and the device 504-A-1 enters standby mode, the status indicator 714 indicates "meeting in progress". Figure 7U As shown, the statement enable representation 716 is enabled and provided for using the meeting list interface 750 (e.g., as Figure 7D As shown) replaces the display of the conference status interface 705.
[0290] Figures 7U to 7V The sequence of changes in status indicator 714 is shown while conference status interface 705 is in standby mode and based on determining that the current time is within a predefined reminder duration (eg, 15 minutes) of the end of the current appointment. Figure 7V Similar to and adapted from Figure 7A .therefore, Figure 7A 7V include similar user interfaces, and elements labeled with the same reference numbers in these two figures have the same functions, and for the sake of brevity, only the differences are described here. Figure 7V As shown, status indicator 714 indicates that the current appointment will end in 15 minutes. For example, according to some embodiments, when in standby mode, based on determining that the current time (e.g., 10:45) is within a predefined reminder duration (e.g., 15 minutes) of the end of the current appointment (e.g., 11:00), status indicator 714 changes from Figure 7U The status in Figure 7V Status in.
[0291] exist Figure 7V In FIG. 7 , the status indicator 714 also includes an extend meeting indication 7114, which is provided to extend the current appointment. Figure 7V As shown, the statement enable representation 716 is enabled and provided for using the meeting list interface 750 (e.g., as Figure 7D As shown) replaces the display of the conference status interface 705.
[0292] Figures 7V to 7WA sequence for extending a current reservation in Meeting Space 1 in Building A is shown. Figure 7V Also shown is detection of contact 7116 at a location corresponding to the "extend meeting" enable indication 7114. Figure 7W The status indicator 714 is shown in response to Figure 7V Selection of the "Extend Meeting" affordance 7114 in the dialog box indicates that the current meeting / appointment will now end at 11:30 (e.g., instead of 11:00). According to some embodiments, if meeting space 1 in building A is available after the current appointment, selecting the "Extend Meeting" affordance 7114 causes 30 minutes to be added to the current appointment in meeting space 1 in building A. Figure 7W As shown, the statement enable representation 716 is enabled and provided for using the meeting list interface 750 (e.g., as Figure 7D ) replaces the display of the conference status interface 705.
[0293] Figure 7V and Figure 7X A sequence is shown in which the available meeting spaces list 7150 is overlaid on the meeting status interface 705 . Figure 7V Also shown is detection of contact 7116 at a location corresponding to the "extend meeting" enable indication 7114. Figure 7X Shows the response to Figure 7V Selection of "Extend Meeting" affordance 7114 in the menu displays a list of available meeting spaces 7150 overlaid on meeting status interface 705. According to some embodiments, if meeting space 1 in building A is not available after the current reservation, selecting "Extend Meeting" affordance 7114 causes list of available meeting spaces 7150 to be overlaid on meeting status interface 705. According to some embodiments, if meeting space 1 in building A is not available after the current reservation, selecting "Extend Meeting" affordance 7114 causes find space interface 7165 (e.g., as shown in FIG. 1 ) to be displayed. Figure 7Y As shown) replaces the display of the conference status interface 705.
[0294] like Figure 7X As shown, status indicator 714 indicates that meeting space 1 in building A is reserved from 11:00 to 12:00. Therefore, the current meeting / reservation cannot be extended in meeting space 1 in building A. However, the user can extend the current meeting / reservation in a different meeting space by using available meeting space list 7150.
[0295] like Figure 7XAs shown, available meeting space list 7150 includes a plurality of affordances 7152a, 7152b, 7152c, 7152d, and 7152e (collectively referred to as "affordances 7152") associated with available meeting spaces. Figure 7X As shown, the list of available meeting spaces 7150 is sorted by proximity to meeting space 1 of building A. Figure 7X , each available meeting space 7152 is associated with a name, an occupancy limit, one or more attribute icons corresponding to equipment or features associated with the meeting space, and a distance from meeting space 1 of building A.
[0296] Figure 7X to Figure 7Y A sequence is shown in which the find space interface 7165 replaces the display of the meeting status interface 705 . Figure 7X Also shown is detection of a left-to-right swipe gesture with contact 7154 on affordance 7152b associated with meeting space 13. Figure 7Y Shows the response to Figure 7X The swipe gesture in the figure replaces the display of the conference status interface 705 with the search space interface 7165. Figure 7Y As shown, find space interface 7165 displays a floor plan of the first floor of building A and indicator 7166 of the location of device 504-A-1 (eg, located within meeting space 1 of building A, corresponding to unavailable meeting space 7174a).
[0297] Figure 7Y Also shown is the response to Figure 7X A swipe gesture is performed to display the list of available meeting spaces 7172c (e.g., corresponding to the location of the available meeting space 7172c) from indicator 7166 overlaid on the find space interface 7165. Figure 7X The indication in FIG. 7176 represents the path 7176 of the conference space 13) of FIG. 7152b. Figure 7Y Also shown is the response to Figure 7X 7172c and displays a menu 7180 associated with available meeting spaces 7172c using a swipe gesture in .
[0298] like Figure 7Y As shown, menu 7180 includes properties of available meeting space 7172c, such as an occupancy limit of available meeting space 7172c (e.g., six people) and icons corresponding to devices associated with available meeting space 7172c (e.g., a display, a video conferencing device, and a projector). Figure 7Y As shown, menu 7180 also includes a takeover indicator 7182, which, when activated (e.g., using contact), causes the current meeting / appointment to be extended in available meeting space 7172c until 11:30.
[0299] According to some embodiments, the user of device 504-A-1 can navigate the floor plan by pinching to zoom in or out and dragging to pan east, west, north, or south. Figure 7Y , find space interface 7165 includes a centering affordance 7177 that, when activated (e.g., by contact), re-centers the plan view within find space interface 7165 around indicator 7166;
[0300] like Figure 7Y As shown, search space interface 7165 includes a cancel affordance 7164a that, when activated (e.g., by contact), causes search space interface 7165 to be Figure 7V ; and a floor indicator 7164b, which indicates the floor associated with the floor plan displayed within the search space interface 7165 (e.g., the first floor of building A) and is provided to display floor plans of different floors of building A within the search space interface 7165.
[0301] like Figure 7Y As shown, the search space interface 7165 also includes an unavailable meeting space 7174a having a first appearance (e.g., a first shadow pattern). Figure 7Y As shown, the find space interface 7165 further includes a second plurality of available meeting spaces 7172a, 7172b, and 7172c (collectively, "available meeting spaces 7172") having a second appearance (e.g., a second shading pattern). According to some embodiments, when a corresponding available meeting space 7172 is activated (e.g., selected using contact), a path from the indicator 7166 to the corresponding available meeting space 7172 is overlaid on the floor plan within the find space interface 7165 (e.g., as shown in FIG. Figure 6U According to some embodiments, when the corresponding available meeting space 7172 is activated (e.g., selected using contact), a menu is overlaid on the floor plan within the find space interface 7165, wherein the menu includes details of the corresponding available meeting space 7172 and affordances provided to take over or reserve the corresponding available meeting space 7172 (e.g., Figure 7Y shown).
[0302] like Figure 7YAs shown, find spaces interface 7165 also includes more meeting spaces affordance 7168, which, when activated (e.g., by contact), causes a list of available meeting spaces in building A to be displayed within find spaces interface 7165 (which is overlaid on or replaces the display of a floor plan of the first floor of building A). According to some embodiments, the list of available meeting spaces is sorted based at least in part on proximity to the location of device 504-A-1. According to some embodiments, the list of available meeting spaces is sorted based at least in part on a set of one or more filtering criteria (e.g., number of chairs, projectors, video conferencing equipment, etc.) provided by a user of device 504-A-1.
[0303] Figures 7Y to 7Z A sequence of extending the current meeting / appointment in a different meeting space is shown. Figure 7Y also shows detecting contact 7184 at a location corresponding to take over affordance 7182. Figure 7Z Similar to and adapted from Figure 7Y .therefore, Figure 7Y and Figure 7Z A similar user interface is included, and elements labeled with the same reference numbers in both figures have the same function, and for the sake of brevity, only the differences are described here. Figure 7Z Shows the response to Figure 7Y The takeover indication in 7182 indicates the selection of the available conference space 7172c to become the unavailable conference space 7174b. Figure 7Z As shown, unavailable meeting space 7174b is displayed within find space interface 7165 with a first appearance (eg, a first shading pattern).
[0304] Figure 7Z Also shown is the response to Figure 7Y The selection of the takeover indicator 7182 in the display will display an alert 7190 overlaid on the search space interface 7165. Figure 7Z As shown, alert 7190 indicates that the current reservation is extended by 30 minutes in unavailable meeting space 7174b. Figure 7Z In , alert 7190 also prompts the user to check in to the extended appointment upon arrival at unavailable meeting space 7174b. Figure 7Z , alert 7190 also includes a cancel takeover enable indication 7192, which, when activated (e.g., using contact), causes the extended reservation of unavailable meeting space 7174b to be canceled.
[0305] Figure 8An exemplary state diagram 500 is shown illustrating various states of a status indicator associated with a meeting space, according to some embodiments. Although relevant features are shown, persons of ordinary skill in the art will recognize from this disclosure that various other features are not shown for the sake of brevity and so as not to obscure more relevant aspects of the exemplary implementations disclosed herein. To this end, according to some embodiments, the state diagram 500 is applied to the status indicator 614 within the meeting status interface 605 (e.g., in Figures 6A to 6B). Figure 6W Similarly, according to some embodiments, the state diagram 500 is applied to the status indicator 714 within the conference status interface 705 (e.g., Figures 7A to 7Z shown in ).
[0306] like Figure 8 As shown, the status indicator starts with "Available" (801). When the status indicator is "Available", if the current time is after the early check-in threshold associated with the next appointment (e.g., 15 minutes before the next appointment), the status indicator changes from "Available" to "Appointment" (802). When the status indicator is "Appointment", if the user checks in to the appointment, the status indicator changes from "Appointment" to "Meeting in Progress" (804). When the status indicator is "Appointment", if the current time is after the check-in deadline (e.g., 7 minutes after the appointment start time) and the user fails to check in to the appointment, the status indicator changes from "Appointment" to "Available" (814).
[0307] When the status indicator is "Meeting in Progress," if an appointment ends and there is at least a threshold amount of time before the next appointment (e.g., at least 15, 20, 30 minutes before the next appointment), the status indicator changes from "Meeting in Progress" to (806) "Available." When the status indicator is "Meeting in Progress," if an appointment ends and there are less than 15 minutes before the next appointment, the status indicator changes from "Meeting in Progress" to (808) "Scheduled."
[0308] If the user signs in to the next appointment while the status indicator is "Meeting in Progress", the status indicator remains (812) "Meeting in Progress". If the appointment ends and the user signs in to the next appointment while the status indicator is "Meeting in Progress", the status indicator remains (810) "Meeting in Progress".
[0309] When the status indicator is "Available," if there is at least a threshold amount of time before the next appointment (e.g., at least 15, 20, 30 minutes before the next appointment) and the user takes over the meeting space, the status indicator changes from "Available" to (822) "Meeting in Progress."
[0310] Figures 9A to 9B A flow chart of a method 900 for declaring a meeting space according to some embodiments is shown. In a first electronic device (e.g., Figure 1A The portable multifunction device 100 or Figure 3 Method 900 is performed on the device 300 in FIG. In some embodiments, the display is a touch screen display, and the input device is located on or integrated with the display. In some embodiments, the display and the input device are separate. Some operations in method 900 may optionally be combined, and / or the order of some operations may optionally be changed.
[0311] In some embodiments, the first device is associated with a conference space rather than a specific user. For example, the first device does not store the entire calendar of a specific user, but rather has information about reservations for the conference space, optionally including reservations for the conference space by the specific user. In another example, the first device has access to a scheduling database (e.g., Figure 5A In some embodiments, the first device is associated with the meeting space. For example, the first device is a user's phone or tablet. In this example, when the user walks into the meeting space with the first device, the device's location is associated with the meeting space, and the meeting space functionality for the specific meeting space is enabled on the first device.
[0312] In some embodiments, the first device is located outside the meeting space (e.g., Figure 5A to device 502-A-1 in FIG. 5B ). In some embodiments, a second device within the meeting space (e.g., Figures 5A to 5B For example, the second device displays notifications associated with the ongoing meeting, such as the end time, an alarm / countdown for when the meeting ends (e.g., Figures 7Q to 7R ), the ability to extend the meeting in the current meeting space if the next time slot becomes available (e.g., Figure 7O ), and / or the ability to extend the meeting to another meeting space (e.g. Figure 7N For example, after authenticating the user, the second device enables the user of the second device to view and edit meeting details (e.g., Figure 7D ), call the missing attendee (e.g., Figure 7E), and using a meeting space device (e.g., Figure 7D Tools 760a, 760b, 760c, 760d and 760e) within the meeting list interface 750 in the projected meeting attachments.
[0313] As described below, method 900 provides an intuitive way to claim a meeting space. This method reduces the cognitive burden on users when claiming a meeting space, thereby creating a more efficient human-computer interface. For battery-powered electronic devices, enabling users to claim a meeting space more quickly and efficiently saves power and increases the time between battery charges.
[0314] The device displays (902) a meeting space status interface on a display, the meeting space status interface including a status indicator indicating the current reservation status of the meeting space (e.g., "Available," "Reserved," "Meeting in Progress," "Meeting Starting Soon," etc.) and a claim affordance provided to claim a reservation for the meeting space. In one example, the claim affordance is associated with a "Slide to Sign In" prompt for signing in to an upcoming reservation. In another example, the claim affordance is associated with a "Slide to Take Over" prompt for requisitioning an available meeting space. Thus, for example, a user can directly gather information about the status and availability of a meeting space through one interface.
[0315] For example, Figure 6A A meeting status interface 605 associated with meeting space 1 at building A is shown displayed by first device 502-A-1. In this example, meeting status interface 605 includes: the current time (e.g., 9:47); a status indicator 614 that indicates the current availability or reservation status of meeting space 1 at building A; and an affordance 616 that, when activated (e.g., using a left-to-right swipe gesture or a predefined gesture such as a single-finger tap gesture), causes status indicator 614 to change (e.g., from reserved to meeting in progress / meeting about to start, or from available to meeting in progress). Figure 6A As shown, status indicator 614 indicates that meeting space 1 in building A is currently reserved by person X, and person X must check in before 10:07. Figure 6A In the example, the statement 616 also prompts the user to "Swipe to Sign In".
[0316] In some embodiments, the meeting space status interface also includes (904) a scheduling affordance that is provided to display the appointment schedule associated with the meeting space. Thus, according to some embodiments, in addition to collecting information about the status and availability of the meeting space through one interface, the user is also able to collect scheduling information. For example, if the user swipes up from the bottom of the meeting space status interface, the booking schedule slides up from the bottom of the meeting status interface 605 and overlays at least a portion of the status indicator and / or the stated affordance. For example, in Figure 6A , meeting status interface 605 also includes a schedule affordance 618 that, when activated (e.g., using an upward swipe gesture or a predefined gesture such as a single-finger tap gesture), causes the appointment schedule associated with meeting space 1 in building A to be displayed. For example, Figures 6B to 6C A sequence is shown in which a reservation schedule 634 for meeting space 1 in building A is displayed within meeting status interface 605 due to selection of schedule affordance 618 .
[0317] In some embodiments, the meeting space status interface also includes (906) one or more graphical representations corresponding to features associated with the meeting space. Thus, according to some embodiments, in addition to collecting information about the status and availability of the meeting space through an interface, the user is also able to collect information about the attributes of the meeting space in order to make an informed decision about using the meeting space. For example, the features include equipment in the meeting space, such as teleconferencing equipment, projectors, displays, etc. In some embodiments, when the user selects a graphical representation, additional details are displayed, such as the type of equipment, model, age, etc. For example, in Figure 6A , the meeting status interface 605 also includes a plurality of attribute icons 608a, 608b, and 608c (collectively referred to as "attribute icons 608"), which indicate devices or features associated with the meeting space 1 of the building A. Figure 6A , first attribute icon 608a indicates that meeting space 1 in building A is equipped with a display, second attribute icon 608b indicates that meeting space 1 in building A includes a video or video conferencing device, and third attribute icon 608c indicates that meeting space 1 in building A includes a projector. When activated (e.g., by contact), attribute icons 608 cause more details about the equipment or features associated with meeting space 1 in building A to be displayed. For example, if first attribute icon 608a is selected, information or details about the display, such as model name, size, age, etc., are displayed.
[0318] In some embodiments, the meeting space status interface further includes (908) a report affordance that is provided to report one or more issues with features of the meeting space. Thus, according to some embodiments, in addition to collecting information about the status and availability of the meeting space through an interface, users are also able to report issues with the meeting space. For example, in Figure 6A , meeting status interface 605 also includes a "Report a Problem" affordance 612 that, when activated (e.g., by contact), causes a reporting interface to replace meeting status interface 605. For example, Figures 6J to 6O A sequence is shown in which reporting interface 655 replaces the display of meeting status interface 605 and a user reports a problem with the projector in meeting space 1 of building A.
[0319] In some embodiments, the meeting space status interface also includes (910) a problem indicator that is provided to indicate one or more unresolved issues for the meeting space. Thus, according to some embodiments, in addition to collecting information about the status and availability of the meeting space through an interface, the user is also able to collect information about unresolved issues for the meeting space in order to make an informed decision about using the meeting space. In some embodiments, the meeting space status interface includes an indicator that notifies the user of unresolved issues for the meeting space. For example, when the indicator is selected, a list of previously reported and / or unresolved issues for the meeting space and / or its features is displayed, such as a malfunctioning projector, a malfunctioning teleconferencing equipment, or a cleaning request. Figures 6P to 6Q The conference status interface 605 is shown in Figure 6J to Figure 6O Indicates the sequence of reported problems for room 1 of building A. For example, Figure 6P Shows the response to Figures 6J to 6O 6 and a badge 682 is displayed within the meeting space affordance 606. In this example, badge 682 indicates that the unresolved issue is associated with meeting space 1 in building A. Continuing with this example, in Figure 6Q In the example, log 685 is overlaid on the meeting status interface 605. Log 686 lists the nature, time and date of the unresolved issues 685 associated with meeting space 1 in building A. For example, unresolved issues 685 are associated with Figures 6J to 6O Associated with the problem report generated and submitted in.
[0320] In some embodiments, the meeting space status interface also includes (912) a find room affordance that is provided to find available meeting spaces. Thus, according to some embodiments, in addition to collecting information about the status and availability of meeting spaces through one interface, the user is also able to find available meeting spaces. In some embodiments, if the user selects the find room affordance, the find room interface 6105 (e.g., Figure 6T For example, find room interface 6105 includes a map with available meeting spaces that are shown in a different display mode than occupied meeting spaces. In some embodiments, if the user selects the find room affordance, a list of available meeting spaces sorted by proximity to the current meeting space overlays meeting status interface 605 (e.g., as shown in FIG. Figure 7X shown).
[0321] For example, Figure 6A As shown, meeting status interface 605 also includes a "Find Space" affordance 610, which, when activated (e.g., by contact), causes the Find Space interface to replace the display of meeting status interface 605. For example, Figures 6S to 6W A sequence is shown in which meeting status interface 605 is replaced with find space interface 6105 and the user takes over available meeting spaces through find space interface 6105 .
[0322] While displaying the conference space status interface, the device detects (914) a change in conditions at the conference space. According to some embodiments, reference Figure 8 State diagram 800 in [ 15 ] describes the triggering of various condition changes at a meeting space. As an example, a condition at a meeting space changes when a time change is detected relative to an upcoming appointment for the meeting space. As another example, a condition at a meeting space changes when a user checks in to an upcoming appointment. As another example, a condition at a meeting space changes when an ongoing appointment ends. As yet another example, a condition at a meeting space changes when a user requisitions an available meeting space. As yet another example, a condition at a meeting space changes when a user fails to check in to an appointment before the check-in deadline.
[0323] In response to detecting a change in conditions at the meeting space, and in accordance with determining that one or more declaration criteria are met based on the change in conditions at the meeting space, the device enables (916) the declaration affordance (keeping the declaration affordance enabled). In some embodiments, when the prompt is displayed, the declaration affordance 616 is enabled within the meeting status interface 605. For example, the declaration affordance 616 is activated using a swipe gesture from left to right, a swipe gesture from right to left, a single-finger tap gesture, a two-finger tap gesture, and the like. Thus, according to some embodiments, meeting space is better utilized in, for example, a corporate campus where meeting space or conference rooms are limited. For example, the ability of a user to interact with a meeting space changes based on the conditions at the meeting space in order to release a meeting space that has not yet been signed in or to allow an available meeting space to be requisitioned.
[0324] In some embodiments, when the status indicator indicates that the conference room is available and the amount of time between the current time and the next appointment is greater than a threshold meeting time (e.g., more than 15 or 30 minutes before the next appointment), the claim criteria are met and the affordance is enabled to take over the available room. Figures 6I to 6J In the example, meeting space 1 in building A is available from 9:30 to 10:00 and is reserved by person X from 10:00 to 11:00. Figure 6I As shown, status indicator 614 indicates "Available" based on the current time (e.g., 9:40) because meeting space 1 of building A is available before 10:00. Figure 6I , the affordance 616 is declared enabled and also prompts the user to "Slide to take over by 10:00." According to some embodiments, the status indicator 614 indicates "Available" when the meeting space is available and the current time (e.g., 9:40) is before the early check-in threshold 622 for the next appointment. According to some embodiments, the affordance 616 is declared enabled to take over the meeting space when the meeting space is available and there is a threshold amount of time before the next appointment based on the current time (e.g., 20 or 30 minutes).
[0325] In some embodiments, the claim criteria are met and the claim affordance is enabled between an early check-in threshold (e.g., 15 minutes before the appointment starts) and a check-in deadline (e.g., 7 minutes after the appointment starts). Figures 6A to 6B, meeting space 1 in building A is available from 9:30 to 10:00 and is reserved by person X from 10:00 to 11:00. According to some embodiments, status indicator 614 indicates "reserved" between an early check-in threshold 622 (e.g., 15 minutes before the appointment start time) and a check-in deadline 624 (e.g., 7 minutes after the appointment start time). Thus, in some embodiments, status indicator 614 indicates "reserved" when the current time is between the early check-in threshold 622 and the check-in deadline 624. Furthermore, in some embodiments, when the meeting space is available and the current time is between the early check-in threshold 622 and the check-in deadline 624, an affordance 616 is declared enabled to check in to the upcoming appointment.
[0326] In some embodiments, when the claim affordance is enabled, the device detects (918) user input via an input device corresponding to selection of the claim affordance, and in response to the user input selecting the claim affordance, the device changes the status indicator to indicate that the meeting space has been claimed. In one example, Figures 6A to 6B 6 shows a sequence where status indicator 614 changes from “appointment” to “meeting in progress” as a result of a left-to-right swipe gesture on declaration affordance 616 to check in to an upcoming appointment when meeting space is available. In another example, Figures 6I to 6J 6 shows a sequence where status indicator 614 changes from “Available” to “Meeting in Progress” as a result of a left-to-right swipe gesture being made on affordance 616 to claim a meeting space when it is available at least a threshold amount of time before an upcoming appointment. As yet another example, Figures 6F to 6G A sequence is shown where status indicator 614 changes from "Meeting in Progress" to "Meeting Starting Soon" as a result of a left-to-right swipe gesture on claim affordance 616 to check in to an upcoming appointment when the meeting space is occupied.
[0327] In some embodiments, changing the status indicator includes (920) changing a display associated with the status indicator to indicate that the meeting space has been claimed without authenticating the user associated with the user input. In some embodiments, the user can swipe on the claim affordance 616 to check in to an existing reservation without authentication. Similarly, in some embodiments, the user can swipe on the claim affordance 616 to claim the available space. As an example, Figures 6A to 6B A sequence is shown where a user signs in to an upcoming appointment without authentication.
[0328] In some embodiments, in response to user input selecting the declaration affordance, the device display (922) is provided with an authentication interface for authenticating a user associated with an existing appointment, and based on determining that the user is authenticated, the device displays a meeting list including details associated with the existing appointment. Thus, according to some embodiments, unauthorized users cannot check in to an existing appointment or requisition available meeting space to better utilize a limited number of meeting spaces, such as on a corporate campus. For example, the meeting list includes a list of invitees to the appointment and attachments associated with the meeting invitation corresponding to the appointment. In some embodiments, check-in is limited to users who are authenticated as meeting organizers or meeting invitees with assistant capabilities. For example, 7A to 7D 7. A sequence is shown in which a user signs in to an upcoming appointment after being authenticated. In this example, when the user swipes on affordance 716 to sign in to an upcoming existing appointment, meeting status interface 705 is replaced with authentication interface 745. Continuing with this example, after the user is authenticated, authentication interface 745 is replaced with meeting list interface 750 with appointment details.
[0329] On the contrary, for example, Figures 7S to 7T 7. The sequence of a user requisitioning a meeting space without authentication is shown. In this example, when the user swipes on affordance 716 to requisition an available meeting space, meeting status interface 705 is replaced with meeting list interface 750. Continuing with this example, meeting list interface 750 does not include meeting details since there are no previously scheduled appointments, but does include a countdown to the takeover period.
[0330] In some embodiments, the declaration affordance is displayed (924) in conjunction with an indicator of an existing reservation to check in to the meeting space. In some embodiments, the status indicator indicates that the meeting space is "available," and the declaration affordance is displayed with text such as "Slide to check in" (e.g., as Figure 6A In some embodiments, the status indicator indicates "meeting in progress," and the affordance is associated with text such as "Slide to check in to the next appointment" (e.g., as Figure 6F In some embodiments, the status indicator indicates that the meeting space is "available," and the affordance is associated with text such as "Slide to take over" (e.g., as shown). Figure 6I shown).
[0331] In some embodiments, an indicator of an existing appointment to check in to the meeting space is displayed (926) within the meeting space status interface between an early check-in threshold (e.g., 15 minutes before the appointment starts) and a check-in deadline (e.g., 7 minutes after the appointment starts). For example, referring to FIG6A , a statement affordance 616 is enabled for person X's appointment from 10:00 to 11:00 between early check-in threshold 622 and check-in deadline 624.
[0332] In some embodiments, based on determining that the meeting space is available and there is at least a predetermined amount of time before the upcoming reservation for the meeting space, in conjunction with requisitioning the meeting space (e.g., Figure 6I to Figure 6J Take over the available meeting space as shown, or Figures 7X to 7Z In some embodiments, the affordance is enabled to requisition available meeting space when there are at least 15, 20, 30 minutes, etc., before the upcoming appointment. For example, referring to Figure 6I If the current time is between the early check-in threshold 622 (e.g., 15 minutes before Person X's appointment at 10:00) and 10:00, then the affordance is declared to indicate that the user will not be enabled to take over the room due to Person X's appointment at 10:00. Conversely, continuing with the example, the affordance is declared to indicate that the user will be enabled to check in to Person X's appointment at 10:00.
[0333] In some embodiments, determining that the meeting space is available includes (930) determining that a check-in deadline for a previous reservation of the meeting space has passed. Figure 6A If the user fails to check in to the appointment from 10:00 to 11:00 before the check-in deadline 624, the appointment will be canceled and the meeting space will be freed for a subsequent local takeover or remote appointment.
[0334] In some embodiments, based on determining that the meeting space is reserved for an existing meeting and that the check-in deadline has passed, the device changes (932) the status indicator to indicate that the meeting space is available. In some embodiments, if no one checks in to the appointment before the check-in deadline, the meeting space becomes available for local takeover and the meeting space is released to the scheduling tool for a subsequent remote appointment. For example, referring to Figure 6D If no one has checked in to the appointment from 10:00 to 11:00 before 624, the appointment from 10:00 to 11:00 is removed from the schedule and the meeting space is available for takeover. In this example, the status indicator changes from "Appointed" to "Available" and the affordance is declared enabled for local takeover (e.g., the prompt "Slide to Take Over" is displayed).
[0335] In response to detecting a change in conditions at the meeting space, and based on determining that one or more declaration criteria are not met based on the change in conditions at the meeting space, the device disables (934) the declaration affordance. In some embodiments, the declaration affordance is disabled when the declaration affordance is not displayed within the meeting status interface. In some embodiments, when the status indicator indicates that the meeting room is currently occupied (e.g., "meeting in progress"), the declaration criteria are not met and the declaration affordance is disabled. For example, after a user signs in to an upcoming appointment, the declaration affordance is disabled (e.g., not displayed). In some embodiments, when the status indicator indicates that the meeting room is currently occupied and the next appointment for the meeting room has been checked in (e.g., "meeting is about to start"), the declaration criteria are not met and the declaration affordance is disabled. In some embodiments, when the status indicator indicates that the meeting room is available and the amount of time between the current time and the next appointment is less than a threshold meeting time (e.g., less than 15 or 30 minutes before the next appointment), the declaration criteria are not met and the declaration affordance is disabled. Thus, according to some embodiments, the user currently occupying the meeting space is protected from other users requisitioning the meeting space.
[0336] In some embodiments, one or more declaration criteria are not met (936) when a meeting is in progress in the meeting space and the current time is before the early check-in threshold for the upcoming appointment. In some embodiments, the declaration affordance is displayed but disabled. In some embodiments, the declaration affordance is not displayed when disabled. For example, Figure 6H , the declaration affordance 616 is not displayed within the meeting status interface 605 because the current time is before the early check-in threshold 622 for the upcoming 10:00-11:00 appointment and the meeting space is occupied (e.g., "meeting in progress").
[0337] In some embodiments, the declaration affordance is also disabled after the user signs in to the appointment. Figure 6B In another example, the statement affordance 616 is not displayed in the meeting status interface 605 because the meeting space is occupied (e.g., "meeting in progress"). Figure 6G In the example embodiment, the declaration indication 616 is not displayed in the meeting status interface 605 because the meeting space is occupied (eg, "meeting is about to start").
[0338] It should be understood that Figures 9A to 9BThe specific order in which the operations are described in the description is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will appreciate various ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 1000, 1100, 2000, 2100, 2200, 2300, 3000, 3100, 3200, and 3300) are also applicable in a similar manner to the details of the processes described above in conjunction with Figures 9A to 9B Method 900 is described. For example, the user interface objects and focus selectors described above with reference to method 900 optionally have one or more of the features of the user interface objects and focus selectors described herein with reference to other methods described herein (e.g., methods 1000, 1100, 2000, 2100, 2200, 2300, 3000, 3100, 3200, and 3300). For the sake of brevity, these details are not repeated here.
[0339] FIG. 10A to FIG. 10B A flow chart of a method 1000 for reporting a meeting space problem according to some embodiments is shown. In a first electronic device (e.g., Figure 1A The portable multifunction device 100 or Figure 3 Method 1000 is performed on a device 300 in FIG. 10 . In some embodiments, the display is a touch screen display, and the input device is located on or integrated with the display. In some embodiments, the display is separate from the input device. Some operations in method 1000 may be optionally combined, and / or the order of some operations may be optionally changed.
[0340] In some embodiments, the first device is associated with a conference space rather than a specific user. For example, the first device does not store the entire calendar of a specific user, but rather has information about reservations for the conference space, optionally including reservations for the conference space by the specific user. In another example, the first device has access to a scheduling database (e.g., Figure 5A In some embodiments, the first device is associated with the meeting space. For example, the first device is a phone or tablet of the user. In this example, when the user walks into the meeting space with the first device, the location of the device is associated with the meeting space, and the meeting space function for the specific meeting space is enabled on the first device. In some embodiments, the first device is located outside the meeting space (e.g., Figures 5A to 5B In some embodiments, a second device in the conference space (e.g., Figures 5A to 5B Device 504-A-1) in is synchronized with the first device.
[0341] As described below, method 1000 provides an intuitive way to report a meeting space issue. This method reduces the cognitive burden on users when reporting a meeting space issue, thereby creating a more efficient human-computer interface. For battery-powered electronic devices, enabling users to report meeting space issues more quickly and efficiently conserves power and increases the time between battery charges.
[0342] The device displays (1002) on a display a reporting interface having a plurality of affordances (e.g., text or images), the reporting interface being provided to report problems associated with corresponding features of the meeting space. For example, these features include a projector, a display, a power source, temperature, missing chairs, missing whiteboard markers, etc. For example, Figure 6K A reporting interface 655 is shown having a plurality of affordances 656a, 656b, 656c, 656d, 656e, 656f, 656g, 656h, 656i, 656j, 656k, and 656l (collectively, “affordances” 656) for reporting equipment or feature issues (e.g., phone, lighting, chairs, displays, tables, projectors, power, etc.) associated with meeting space 1 in building A and / or for requesting service options (e.g., cleaning, refreshments, supplies, etc.) for meeting space 1 in building A. Thus, according to some embodiments, a user is able to quickly report issues with a meeting space.
[0343] In some embodiments, at least some of the plurality of affordances are provided (1004) to initiate service options associated with the meeting space (e.g., requiring cleaning, catering / refreshments, etc.). Figure 6K As shown, affordance 656c is provided to initiate a service option associated with meeting space 1 of building A (eg, cleaning required).
[0344] In some embodiments, the reporting interface includes (1006) an image of the meeting space, and at least some of the affordances are co-located with corresponding meeting space features within the image. For example, Figure 7IA reporting interface 790 is shown with an image of meeting space 1 in building A, including affordances 794a, 794b, 794c, 794d, 794e, 794f, and 794g (collectively, "affordances 794") co-located with at least some devices or features of meeting space 1 in building A. In one example, selecting affordance 794b (e.g., by contact) results in the generation of a problem report indicating a problem with display #2 in meeting space 1 in building A. In another example, selecting affordance 794g (e.g., by contact) results in the generation of a problem report indicating a problem with a chair in meeting space 1 in building A. Thus, according to some embodiments, a user can quickly report a problem with a meeting space in a visual manner.
[0345] In some aspects, the reporting interface includes (1008) at least one service request indicator provided to indicate unresolved service requests associated with the conference space. Figure 6R In FIG. 6A , affordance 656h is associated with badge 690, which indicates association with a projector (e.g., as in FIG. 6K through FIG. 6B ). Figure 6O Unresolved issue reports associated with the issue reports created and submitted in .
[0346] In some embodiments, the indicator is at least one of a graphical representation (e.g., a badge and / or a timestamp) or text within a corresponding enable representation in the plurality of enable representations (1010) that indicates an unresolved service request for a feature associated with the corresponding enable representation, and the corresponding enable representation is disabled in response to initiating a process for generating a service request. Thus, according to some embodiments, the corresponding enable representation is disabled to prevent duplicate problem reporting. For example, the indicator is a badge within the corresponding enable representation. For example, Figure 6R A badge 690 is shown displayed within affordance 656h indicating that a problem report has been reported associated with the projector. Figure 6R As shown, the time and date of the problem report associated with the projector are also displayed within the enable indication 656h.
[0347] The device detects (1012) via an input device a sequence of one or more user inputs corresponding to selecting one or more affordances from a plurality of affordances. For example, Figures 6K to 6L A sequence is shown in which a user selects affordance 656h to create a problem report associated with a projector in meeting space 1 of building A.
[0348] In response to a sequence of one or more user inputs selecting one or more affordances, the device initiates (1014) a process for generating a service request associated with one or more features of the meeting space, the service request corresponding to the selected one or more affordances. For example, Figure 6K 6O illustrates a sequence in which a user initiates a process for generating a service request associated with a problematic projector in conference space 1 of building A. Thus, according to some embodiments, a user is able to quickly report a problem with a conference space without placing a phone call.
[0349] According to some embodiments, reference Figure 5A , a service request or problem report is sent to the controller 510. In some embodiments, the controller 510 processes the service request or problem report to resolve the problem with the problematic projector. For example, an indication of one or more problematic features is sent to an administrator who issues a service request to the relevant parties. For example, the administrator has a dashboard view of the meeting space and the accompanying problems and appointment schedules. As another example, Figures 7I to 7K A sequence is shown in which a user initiates a process for generating a service request associated with a problematic display within conference space 1 of building A.
[0350] In some embodiments, the service request is associated with at least one of the organizers of the current meeting scheduled in the meeting space, the previous meeting scheduled in the meeting space, or the next meeting scheduled in the meeting space (1016). In some embodiments, the service request or problem report is associated with the organizer of the current meeting, the previous meeting, or the next meeting in the meeting space. In some embodiments, the service request or problem report is associated with one or more attendees or invitees of the current meeting, the previous meeting, or the next meeting in the meeting space. Thus, according to some embodiments, the problem report or service request is associated with the identity of the user to avoid false positives.
[0351] In some embodiments, in response to selecting a sequence of one or more user inputs represented by one or more affordances, the device displays (1018) on a display an identification interface that is provided to the identity of the user who initiated the service request, and in response to obtaining the identity of the user who initiated the service request, the device associates the service request with the identity of the user who initiated the service request. For example, Figures 6M to 6N An identification interface 675 is shown that is provided to associate a service request or problem report with a user. Figure 6MAs shown, identification interface 675 includes a plurality of affordances 676a, 676b, and 676c (collectively, "affordances 676") that are provided to identify the user reporting the issue. According to some embodiments, affordances 676 are determined based on the next appointment for the meeting space, the previous appointment for the meeting space, and / or the current appointment for the meeting space. Figure 6M , affordance 676a is provided to identify the user initiating the problem report as the organizer of the current appointment, affordance 676b is provided to identify the user initiating the problem report as invitee A of the current appointment, and affordance 676c is provided to identify the user initiating the problem report as an unlisted person. Thus, according to some embodiments, the problem report or service request is associated with the identity of the user to avoid false positives and false negatives.
[0352] In some embodiments, the device displays (1022) on the display a meeting space status interface having a status indicator provided to indicate a current reservation status of the meeting space and a report affordance provided to report one or more issues with a characteristic of the meeting space, wherein the report interface is displayed in response to selection of the report affordance. As an example, Figures 6J to 6K 6 shows a sequence in which the display of the meeting status interface 605 is replaced by the reporting interface 655 in response to selection of the "Report a Problem" affordance 612 within the meeting status interface 605. As another example, Figures 7H to 7I A sequence is shown in which reporting interface 790 is displayed in response to selection of third affordance 752c within sidebar area 753b.
[0353] In some embodiments, the meeting space status interface includes (1024) a service request indicator that is provided to indicate one or more unresolved service requests associated with the meeting space. In some embodiments, the service request indicator is added to the meeting space status interface after a problem is reported. For example, Figure 6P Shows the response to Figures 6J to 6O 6 and a badge 682 is displayed within the meeting space affordance 606. In this example, badge 682 indicates that the unresolved issue is associated with meeting space 1 in building A. Continuing with this example, in Figure 6Q In response to selecting badge 682, log 685 is overlaid on meeting status interface 605. In this example, log 686 lists the nature, time and date of unresolved issues 685 associated with meeting space 1 in building A. For example, unresolved issues 685 are associated with Figures 6J to 6OThus, according to some embodiments, in addition to collecting information about the status and availability of a meeting space through one interface, users can also collect information about unresolved issues with the meeting space in order to make informed decisions about using the meeting space.
[0354] It should be understood that FIG. 10A to FIG. 10B The specific order in which the operations are described in the description is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will appreciate a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 900, 1100, 2000, 2100, 2200, 2300, 3000, 3100, 3200, and 3300) are also applicable in a similar manner to the details of the processes described above in conjunction with FIG. 10A to FIG. 10B Method 1000 is described. For example, the user interface objects and focus selectors described above with reference to method 1000 optionally have one or more of the features of the user interface objects and focus selectors described herein with reference to other methods described herein (e.g., methods 900, 1100, 2000, 2100, 2200, 2300, 3000, 3100, 3200, and 3300). For the sake of brevity, these details are not repeated here.
[0355] Figures 11A to 11C A flow chart of a method 1100 for finding available meeting spaces according to some embodiments is shown. In a first electronic device (e.g., Figure 1A The portable multifunction device 100 or Figure 3 Method 1100 is performed on a device 300 in FIG. 1 . In some embodiments, the display is a touch screen display, and the input device is located on or integrated with the display. In some embodiments, the display is separate from the input device. Some operations in method 1100 may be optionally combined, and / or the order of some operations may be optionally changed.
[0356] In some embodiments, the first device is associated with a conference space rather than a specific user. For example, the first device does not store the entire calendar of a specific user, but rather has information about reservations for the conference space, optionally including reservations for the conference space by the specific user. In another example, the first device has access to a scheduling database (e.g., Figure 5AIn some embodiments, the first device is associated with the meeting space. For example, the first device is a user's phone or a user's tablet. In this example, when the user walks into the meeting space with the first device, the location of the device is associated with the meeting space, and the meeting space functionality for the specific meeting space is enabled on the first device. In some embodiments, the first device is located outside the meeting space (e.g., Figures 5A to 5B In some embodiments, a second device in the conference space (e.g., Figures 5A to 5B Device 504-A-1) in synchronizes with the first device.
[0357] As described below, method 1100 provides an intuitive way to find available meeting spaces. This method reduces the cognitive burden on users when searching for available meeting spaces, thereby creating a more efficient human-computer interface. For battery-powered electronic devices, enabling users to find available meeting spaces more quickly and efficiently conserves power and increases the time between battery charges.
[0358] The device displays (1102) on a display a meeting space discovery interface having a plurality of affordances corresponding to a plurality of available meeting spaces different from a first meeting space. In some embodiments, the meeting space discovery interface includes a list of available meeting spaces sorted by their respective attributes / facilities. In some embodiments, the list of available meeting spaces is sorted according to proximity to the first device. In some embodiments, the meeting space discovery interface includes a floor plan of a map of a floor (including the first meeting space) showing available rooms relative to the first meeting space. Thus, according to some embodiments, a user is able to quickly find an available meeting space.
[0359] As an example, Figure 6T The search space interface 6105 is shown with a floor plan of the first floor of Building A. Figure 6T In the search space interface 6105, the search space interface 6105 includes a first plurality of unavailable meeting spaces 6112a and 6112b (collectively referred to as "unavailable meeting spaces 6112") having a first appearance (e.g., a first shading pattern). For example, meeting space 1 (e.g., the first meeting space) of building A corresponds to unavailable meeting space 6112a. Figure 6TAs shown, the find space interface 6105 also includes a second plurality of available meeting spaces 6114a, 6114b, and 6114c (collectively, "available meeting spaces 6114") having a second appearance (e.g., a second shading pattern). According to some embodiments, when a corresponding available meeting space 6114 is activated (e.g., selected using contact), a path from the indicator 6106 to the corresponding available meeting space 6114 is overlaid on the floor plan within the find space interface 6105 (e.g., as shown in FIG. Figure 6U According to some embodiments, when the corresponding available meeting space 6114 is activated (e.g., selected using contact), a menu is overlaid on the floor plan within the find space interface 6105, wherein the menu includes details of the corresponding available meeting space 6114 and affordances provided to take over or reserve the corresponding available meeting space 6114 (e.g., as shown in FIG. 1 ). Figure 6U shown).
[0360] For example, Figure 7X 7. Shown is a list 7150 of available meeting spaces overlaid on the meeting status interface 705. Figure 7X As shown, available meeting space list 7150 includes a plurality of affordances 7152a, 7152b, 7152c, 7152d, and 7152e (collectively referred to as "affordances 7152") associated with available meeting spaces. Figure 7X As shown, the list of available meeting spaces 7150 is sorted by proximity to meeting space 1 of building A. According to some embodiments, when a corresponding available meeting space 7152 is activated (e.g., selected using a single-finger tap gesture, a two-finger tap gesture, a left-to-right swipe gesture, a right-to-left swipe gesture, etc.), a floor plan (e.g., as shown in FIG. 1 ) is displayed within the find space interface 7165 along with a path 7176 from the first meeting space to the corresponding available meeting space. Figure 7Y According to some embodiments, when a corresponding available meeting space is activated (e.g., selected using a single-finger tap gesture, a two-finger tap gesture, a left-to-right swipe gesture, a right-to-left swipe gesture, etc.), a menu is overlaid on the floor plan within the find space interface 7165, wherein the menu includes details of the corresponding available meeting space and affordances provided to take over or reserve the corresponding available meeting space (e.g., Figure 7Y shown).
[0361] In some embodiments, the meeting space discovery interface includes (1104) an indication of one or more attributes of each of the plurality of available meeting spaces. For example, the attributes include at least one of a name, size, features provided (e.g., equipment), and a distance of the one or more available meeting spaces from the first meeting room. In some embodiments, unresolved issues for any attribute are also reported within the meeting space discovery interface. For example, Figure 7X , each available meeting space 7152 in available meeting space list 7150 is associated with: a name, an occupancy limit, one or more attribute icons corresponding to equipment or features associated with the meeting space, and a distance from meeting space 1 of building A.
[0362] The device detects (1106) via an input device a first user input corresponding to selecting a corresponding affordance corresponding to a second meeting space from a plurality of affordances displayed within the meeting space discovery interface. As an example, Figure 6U 61. User input is shown selecting an available meeting space 6114c within the find space interface 6105. As another example, Figure 7X User input (eg, a left-to-right swipe gesture) is shown selecting affordance 7152b associated with meeting space 13 within available meeting spaces list 7150 .
[0363] In response to a first user input selecting a corresponding affordance, the device provides (1108) instructions for navigating from the first meeting space to the second meeting space. In some embodiments, the instructions include a path from the first meeting space to the second meeting space overlaid on a map (e.g., a floor plan of a floor). In some embodiments, the instructions include turn-by-turn directions (e.g., visual and / or auditory turn-by-turn directions) from the first meeting space to the second meeting space. Thus, according to some embodiments, visual and / or auditory instructions are provided to the user that orient and navigate the user to another available meeting space to avoid getting lost or disoriented when navigating to an available meeting space. For example, Figure 6V Shows the response to the selection Figure 6U 6114c and a path 6126 from indicator 6106 to the selected available meeting space 6114c. As another example, Figure 7Y Shows the response to the selection Figure 7X Path 7176 from indicator 7166 to available meeting space 7172c (e.g., associated with meeting space 13) is provided by affordance 7152b.
[0364] In some embodiments, the instructions are overlaid (1110) on a floor plan associated with a second meeting space corresponding to the respective affordance. As an example, Figure 6V , path 6126 is overlaid on the floor plan of the first floor of Building A within the search space interface 6105. As another example, in Figure 7Y , path 7176 is overlaid on the floor plan of the first floor of building A within the search space interface 7165.
[0365] In some embodiments, the floor plan shows (1112) unavailable meeting spaces in a first graphical state (e.g., a first state, a first shading pattern, a first color, a first cross-hatching pattern, etc.) and shows available meeting spaces in a second graphical state (e.g., a second state, a second shading pattern, a second color, a second cross-hatching pattern, etc.). As an example, referring to Figure 6T to Figure 6V , unavailable meeting spaces 6112a and 6112b are displayed with a first shading pattern (e.g., cross-hatching), and available meeting spaces 6114a, 6114b, and 6114c are displayed with a second shading pattern (e.g., dots). As another example, referring to Figures 7Y to 7Z , the unavailable meeting space 7174a is displayed with a first shading pattern (e.g., cross-hatching), and the available meeting spaces 7172a, 7172b, and 7172c are displayed with a second shading pattern (e.g., dots).
[0366] In some embodiments, the device detects (1114) via the input device a second user input corresponding to selecting a third meeting space in the floor plan, and in response to detecting the second user input selecting the third meeting space, the device replaces display of instructions for navigating from the first meeting space to the second meeting space with different instructions for navigating from the first meeting space to the third meeting space. For example, referring to Figure 6V , instead of selecting the take over affordance, the user selects another available meeting space, such as meeting space 6114a (not shown). Continuing with this example, menu 6120 and path 6126 cease to be displayed within find space interface 6105. Continuing with this example, another menu for taking over available meeting space 6114a and a path from indicator 6106 to available meeting space 6114a are displayed within find space interface 6105 (not shown).
[0367] In some embodiments, in response to a first user input selecting a corresponding affordance, the device displays (1116) on the display an option for reserving a second meeting space within the meeting space discovery interface. Figure 6VIn the example, menu 6120 is overlaid on the floor plan in the search space interface 6105. Figure 6V As shown, menu 6120 includes details / attributes of available meeting space 6114c and affordances 6122 provided to take over or reserve available meeting space 6114c. Figure 7Y , menu 7180 is overlaid on the floor plan within the search space interface 7165. Figure 7Y As shown, menu 7180 includes details / attributes of available meeting space 7172c and affordances 7182 provided to take over or reserve available meeting space 7172c. In some embodiments, in response to selecting a reservation option (e.g., Figure 6V The affordance in 6122, or Figure 7Y 7182 in the affordance), the device displays an intermediate UI for entering meeting details (such as meeting length, invitees, and attachments). According to some embodiments, the user still has to go to the reserved room to sign in (temporarily reserved meeting space).
[0368] In some embodiments, the device displays (1118) a meeting space status interface on a display having a status indicator indicating that the current appointment for the first meeting space is about to end and an extend enable indication for extending the appointment (e.g., the meeting space status interface is displayed before the meeting space discovery interface), and the device detects, via an input device, a second user input corresponding to a selection of the extend enable indication, wherein in response to the second user input selecting the extend enable indication and based on a determination that the first meeting space is not available for extending the current appointment, the meeting space discovery interface is displayed. Thus, according to some embodiments, a user is able to quickly extend his / her appointment to another available meeting space if additional time is needed to complete the meeting. For example, there is a reservation for the first meeting space by another user at the end of the current appointment. For example, Figure 7X Shows the response to the selection Figure 7V The “Extend Meeting” option 7114 is indicated and overlaid on the list of available meeting spaces 7150 on the meeting status interface 705 . Figures 7X to 7Z Shows the user Figure 7Y The user may extend the sequence of the current meeting in the meeting space 13 of building A associated with the available meeting space 7172c in building A. According to some embodiments, the user must still check in at the other meeting space where the appointment is to be extended.
[0369] In some embodiments, in response to a second user input selecting the extend affordance and based on determining that the first meeting space is available to extend the current appointment, the device extends (1120) the current appointment in the first meeting space. Thus, according to some embodiments, a user is able to quickly extend his / her appointment in the same meeting space if additional time is needed to complete the meeting. For example, there are no appointments after the current appointment. For example, Figures 7V to 7W The sequence shows that a user is extending a current meeting in Meeting Space 1 of Building A (e.g., the meeting space associated with the second device 504-A-1). Figure 7W , status indicator 714 indicates that the meeting will now end at 11:30 (e.g., extended by 30 minutes). According to some embodiments, when extending an appointment in the first meeting space, the user does not need to sign in again.
[0370] In some embodiments, the device filters (1122) multiple available meeting spaces that are different from the first meeting space based on one or more attributes of the first meeting space and / or one or more parameters of the current appointment. In some embodiments, displaying the meeting space discovery interface includes displaying the meeting space discovery interface with a subgroup of multiple affordances, the subgroup of the multiple affordances corresponding to a subgroup of multiple available meeting spaces that are different from the first meeting space, the multiple available meeting spaces satisfying one or more attributes of the first meeting space and / or one or more parameters of the current appointment. In some embodiments, when extending a meeting to another meeting space, the meeting space discovery interface filters the available meeting spaces based on attributes of the first meeting space (e.g., size, equipment, etc.) and / or details of the current appointment such as the invitee list and meeting parameters (e.g., room size, required equipment, badge access, etc.). Thus, for example, the available meeting spaces displayed in the meeting space discovery interface are customized to at least suit the user's current needs. For example, in Figure 7X , due to the occupancy limit of meeting space 1 of building A (eg, the meeting space associated with second device 504 -A- 1 ), available meeting space list 7150 includes available meeting spaces having an occupancy limit of at least 6.
[0371] In some embodiments, the device displays (1124) on the display a meeting space status interface that includes a find room affordance provided to find an available meeting space, wherein the meeting space discovery interface is displayed in response to detecting a second user input corresponding to selecting the find room affordance. In some embodiments, the meeting space status interface also includes a status indicator that indicates the current reservation status of the meeting space. For example, in Figure 6A, the meeting status interface includes a "Find Space" affordance 610 that, when activated (e.g., by contact), causes a Find Space interface 6105 to replace the display of meeting status interface 605. Figure 6T For example, in response to selecting Figure 6S The "Find Space" indicator in FIG610 shows that the display of the Find Space interface 6105 replaces the display of the conference status interface 605. As another example, in Figure 7D , sidebar region 753b includes a fourth affordance 752d that is provided to replace the display of meeting list interface 750 with the display of find space interface 7165 (eg, Figure 7X Thus, according to some embodiments, in addition to gathering information about the status and availability of meeting spaces through one interface, users can also search for available meeting spaces.
[0372] In some embodiments, the plurality of affordances within the meeting space discovery interface includes (1126) a list of a plurality of available meeting spaces other than the first meeting space overlaid on the meeting space status interface. For example, Figure 7X A list 7150 of available meeting spaces is shown overlaid on the meeting status interface 705 .
[0373] In some embodiments, the list of multiple available meeting spaces is sorted based on the proximity of multiple available meeting spaces different from the first meeting space to the first meeting space (1128). In Figure 7X, for example, the list of available meeting spaces 7150 is sorted by proximity to meeting space 1 of building A (e.g., associated with second device 504-A-1). In some embodiments, the list is also filtered based on attributes of the first meeting space (e.g., size, equipment, etc.).
[0374] In some embodiments, the device displays (1130) a plurality of filter affordances on a display, and the device detects, via an input device, a sequence of one or more user inputs corresponding to selection of the one or more filter affordances. In response to the sequence of one or more user inputs selecting the one or more filter affordances, the device: obtains a set of filter criteria corresponding to the one or more filter affordances; and replaces the display of the list of a plurality of available meeting spaces other than the first meeting space with a subset of the list of a plurality of available meeting spaces other than the first meeting space that meet the set of filter criteria. For example, a user of the first device selects desired room attributes for the next meeting space, such as a projector and the number of chairs. For example, after the user enters additional filter criteria for the meeting space (e.g., more than 6 people, projector, smart TV, whiteboard, refreshments / catering, etc.), the list of available meeting spaces (not shown) is redisplayed along with the meeting spaces that meet the one or more filter criteria. Thus, for example, the list of a plurality of available meeting spaces is customized to suit the user's current needs.
[0375] In some embodiments, in response to detecting a second user input corresponding to a selection of a find room affordance, the device displays (1132) on the display an authentication interface provided to authenticate the user of the first device, wherein the meeting space discovery interface is displayed in response to authenticating the user of the first device. Thus, in some embodiments, a user cannot extend a meeting to a new meeting space without authentication. Thus, in some embodiments, a user cannot find available meetings without authentication. In some embodiments, the authentication interface prompts the user to enter a set of login credentials. In some embodiments, the authentication interface prompts the user to swipe his / her badge. In some embodiments, the authentication interface prompts the user to provide biometric information, such as a fingerprint, a voice sample, a retinal scan, etc. Thus, according to some embodiments, only authenticated users can use the meeting space discovery interface to find available meeting spaces. For example, this limits unauthorized users from occupying valuable meeting space.
[0376] In some embodiments, a plurality of available meeting spaces other than the first meeting space are filtered (1134) based on access credentials associated with an account corresponding to the authenticated user of the first device. Figure 7X , the list of available meeting spaces is filtered 7150 based on the access credentials associated with the authenticated user (not shown). For example, the list of available meeting spaces shows available meeting spaces in areas of a building to which the user has access. Thus, for example, the available meeting spaces displayed in the meeting space discovery interface are tailored to the user's access so that the user cannot access available displayed meeting spaces that are out of reach of the user.
[0377] It should be understood that Figures 11A to 11C The specific order in which the operations are described in the description is merely exemplary and is not intended to indicate that the order is the only order in which the operations may be performed. A person of ordinary skill in the art will appreciate a variety of ways to reorder the operations described herein. In addition, it should be noted that the details of other processes described herein in conjunction with other methods described herein (e.g., methods 900, 1000, 2000, 2100, 2200, 2300, 3000, 3100, 3200, and 3300) are also applicable in a similar manner to the details of the processes described above in conjunction with Figures 11A to 11C Method 1100 is described. For example, the user interface objects and focus selectors described above with reference to method 1100 optionally have one or more of the features of the user interface objects and focus selectors described herein with reference to other methods described herein (e.g., methods 900, 1000, 2000, 2100, 2200, 2300, 3000, 3100, 3200, and 3300). For the sake of brevity, these details are not repeated here.
[0378] According to some embodiments, Figure 12 1 shows a functional block diagram of an electronic device 1200 configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, firmware, or a combination thereof that implements the principles of the various described embodiments. It should be understood by those skilled in the art that Figure 12 The functional blocks described in the present invention are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further limitation of the functional blocks described herein.
[0379] like Figure 12 As shown, an electronic device 1200 associated with a conference space includes a display unit 1202 configured to display a user interface, one or more input units 1204 configured to receive user input, and a processing unit 1208 coupled to the display unit 1202 and the one or more input units 1204. In some embodiments, the processing unit 1208 includes: a display control unit 1210, an input detection unit 1212, a condition detection unit 1214, and a declaration unit 1216.
[0380] Processing unit 1208 is configured to: (e.g., using display control unit 1210) enable display of a meeting space status interface on display unit 1202, the meeting space status interface including a status indicator indicating the current reservation status of the meeting space and a claim affordance provided for claiming the reservation of the meeting space; and, while displaying the meeting space status interface, detect a change in conditions at the meeting space (e.g., using condition detection unit 1214). In response to detecting the change in conditions at the meeting space and, based on a determination based on the change in conditions at the meeting space, that one or more claim criteria are satisfied, processing unit 1208 is further configured to enable the claim affordance (e.g., using claim unit 1216). In response to detecting the change in conditions at the meeting space and, based on a determination based on the change in conditions at the meeting space, that one or more claim criteria are not satisfied, processing unit 1208 is further configured to disable the claim affordance (e.g., using claim unit 1216).
[0381] In some embodiments, when the declaration enable indication is enabled, the processing unit 1208 is further configured to detect user input corresponding to selection of the declaration enable indication via one or more input units 1204 (e.g., using input detection unit 1212), and in response to the user input selecting the declaration enable indication, the processing unit 1208 is further configured to change (e.g., using declaration unit 1216) the status indicator to indicate that the meeting space has been declared.
[0382] In some embodiments, changing the status indicator includes changing a display associated with the status indicator to indicate that the meeting space has been claimed without authenticating a user associated with the user input.
[0383] In some embodiments, in response to user input indicating a selection statement, processing unit 1208 is further configured to (e.g., using display control unit 1210) enable display of an authentication interface provided to authenticate a user associated with an existing appointment, and based on determining that the user is authenticated, processing unit 1208 is further configured to (e.g., using display control unit 1210) enable display of a meeting list including details associated with the existing appointment.
[0384] In some embodiments, the declaration affordance is displayed in conjunction with an indicator of an existing reservation checked in to the meeting space.
[0385] In some embodiments, an indicator of existing reservations checked in to the meeting space is displayed within the meeting space status interface between the early check-in threshold and the check-in deadline.
[0386] In some embodiments, based on determining that the meeting space is available and there is at least a predetermined amount of time before an upcoming reservation for the meeting space, a claim affordance is displayed in conjunction with an indicator to requisition the meeting space.
[0387] In some embodiments, determining that the meeting space is available includes determining that a check-in deadline for a previous reservation of the meeting space has passed.
[0388] In some embodiments, based on determining that the meeting space is reserved for an existing meeting and the check-in deadline has passed, processing unit 1208 is further configured (eg, using declaration unit 1216 ) to change the status indicator to indicate that the meeting space is available.
[0389] In some embodiments, one or more of the declaration criteria are not met when a meeting is in progress in the meeting space and the current time is before the early check-in threshold for the upcoming appointment.
[0390] In some embodiments, the meeting space status interface also includes a scheduling affordance that is provided to display appointment schedules associated with the meeting space.
[0391] In some embodiments, the meeting space status interface also includes one or more graphical representations corresponding to characteristics associated with the meeting space.
[0392] In some embodiments, the meeting space status interface also includes a reporting affordance that is provided to report one or more problems with characteristics of the meeting space.
[0393] In some embodiments, the meeting space status interface also includes a problem indicator provided to indicate one or more unresolved issues with the meeting space.
[0394] In some embodiments, the meeting space status interface also includes a find room affordance that is provided for finding available meeting spaces.
[0395] According to some embodiments, Figure 13 1 shows a functional block diagram of an electronic device 1300 configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, firmware, or a combination thereof that implements the principles of the various described embodiments. It should be understood by those skilled in the art that Figure 13 The functional blocks described in the present invention are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further limitation of the functional blocks described herein.
[0396] like Figure 13As shown, the electronic device 1300 associated with the meeting space includes a display unit 1302 configured to display a user interface, one or more input units 1304 configured to receive user input, and a processing unit 1308 coupled to the display unit 1302 and the one or more input units 1304. In some embodiments, the processing unit 1308 includes: a display control unit 1310, an input detection unit 1312, and a service request unit 1314.
[0397] Processing unit 1308 is configured to: (e.g., using display control unit 1310) enable display of a reporting interface having multiple enable representations on display unit 1302, the reporting interface being provided to report issues associated with corresponding features of the meeting space; detect via one or more input units 1304 (e.g., using input detection unit 1312) a sequence of one or more user inputs corresponding to selection of one or more enable representations from multiple enable representations; and in response to the sequence of one or more user inputs selecting one or more enable representations, initiate (e.g., using service request unit 1314) a process for generating a service request associated with one or more features of the meeting space, the service request corresponding to the selected one or more enable representations.
[0398] In some embodiments, at least some of the multiple affordances are provided to initiate service options associated with the meeting space.
[0399] In some embodiments, the reporting interface includes an image of the meeting space, and at least some of the affordances are co-located with corresponding meeting space features within the image.
[0400] In some aspects, the reporting interface includes at least one service request indicator provided to indicate unresolved service requests associated with the meeting space.
[0401] In some embodiments, the indicator is at least one of a graphical representation or text within a corresponding enable representation of a plurality of enable representations that indicates an unresolved service request for a feature associated with the corresponding enable representation, and the corresponding enable representation is disabled in response to initiating a process for generating a service request.
[0402] In some embodiments, the service request is associated with at least one of an organizer of a current meeting scheduled in the meeting space, a previous meeting scheduled in the meeting space, or a next meeting scheduled in the meeting space.
[0403] In some embodiments, in response to selecting a sequence of one or more user inputs represented by one or more enable representations, processing unit 1308 is further configured to (e.g., using display control unit 1310) enable display on display unit 1302 of an identification interface providing the identity of the user who initiated the service request, and in response to obtaining the identity of the user who initiated the service request, processing unit 1308 is further configured to (e.g., using service request unit 1314) associate the service request with the identity of the user who initiated the service request.
[0404] In some embodiments, processing unit 1308 is further configured (e.g., utilizing display control unit 1310) to enable display on display unit 1302 of a meeting space status interface having a status indicator and a report enable indication, wherein the status indicator is provided to indicate the current reservation status of the meeting space and the report enable indication is provided to report one or more issues with characteristics of the meeting space, wherein the reporting interface is displayed in response to selection of the report enable indication.
[0405] In some embodiments, the meeting space status interface includes a service request indicator provided to indicate one or more unresolved service requests associated with the meeting space.
[0406] According to some embodiments, Figure 14 1 shows a functional block diagram of an electronic device 1400 associated with a first conference space configured according to the principles of the various described embodiments. The functional blocks of the device are optionally implemented by hardware, software, firmware, or a combination thereof that implements the principles of the various described embodiments. It should be understood by those skilled in the art that Figure 14 The functional blocks described in the present invention are optionally combined or separated into sub-blocks to implement the principles of the various described embodiments. Therefore, the description herein optionally supports any possible combination or separation or further limitation of the functional blocks described herein.
[0407] like Figure 14 As shown, the electronic device 1400 includes a display unit 1402 configured to display a user interface, one or more input units 1404 configured to receive user input, and a processing unit 1408 coupled to the display unit 1402 and the one or more input units 1404. In some embodiments, the processing unit 1408 includes: a display control unit 1410, an input detection unit 1412, a navigation unit 1414, and a supply unit 1416.
[0408] Processing unit 1408 is configured to: (e.g., using display control unit 1410) enable display of a meeting space discovery interface having multiple enable representations on display unit 1402, wherein the multiple enable representations correspond to multiple available meeting spaces different from the first meeting space; detect a first user input via one or more input units 1402 (e.g., using input detection unit 1412), the first user input corresponding to selection of a corresponding enable representation corresponding to a second meeting space from a plurality of enable representation tables displayed within the meeting space discovery interface; and in response to the first user input selecting the corresponding enable representation, provide instructions for navigating from the first meeting space to the second meeting space (e.g., using navigation unit 1414).
[0409] In some embodiments, the meeting space discovery interface includes an indication of one or more attributes of each of a plurality of available meeting spaces.
[0410] In some embodiments, in response to a first user input selecting a corresponding enable representation, processing unit 1408 is further configured (e.g., using display control unit 1410) to enable displaying on display unit 1402 an option for reserving a second meeting space within the meeting space discovery interface.
[0411] In some embodiments, the processing unit 1408 is further configured to: (e.g., using the display control unit 1410) enable display of a meeting space status interface on the display unit 1402, the meeting space status interface having a status indicator indicating that the current reservation of the first meeting space is about to end and an extend enable indication for extending the reservation, and detect a second user input corresponding to selection of the extend enable indication via one or more input units 1404 (e.g., using the input detection unit 1412), wherein in response to the second user input selecting the extend enable indication and based on determining that the first meeting space is not available for extending the current reservation, a meeting space discovery interface is displayed.
[0412] In some embodiments, processing unit 1408 is further configured to extend the current appointment in the first meeting space (e.g., using provisioning unit 1416) in response to a second user input selecting the extend affordance and based on determining that the first meeting space is available to extend the current appointment.
[0413] In some embodiments, processing unit 1408 is further configured to filter (e.g., using supply unit 1416) multiple available meeting spaces different from the first meeting space based on one or more attributes of the first meeting space and / or one or more parameters of the current reservation, wherein displaying a meeting space discovery interface includes displaying a meeting space discovery interface having a subgroup of multiple enable representations, the subgroups of the multiple enable representations corresponding to subgroups of multiple available meeting spaces different from the first meeting space, the multiple available meeting spaces satisfying one or more attributes of the first meeting space and / or one or more parameters of the current reservation.
[0414] In some embodiments, processing unit 1408 is further configured to: (e.g., using display control unit 1410) enable display of a meeting space status interface on display unit 1402, the meeting space status interface including a find room enable representation provided for finding available meeting spaces, wherein the meeting space discovery interface is displayed in response to detecting a second user input corresponding to selection of the find room enable representation.
[0415] In some embodiments, the multiple affordances within the meeting space discovery interface include a list of multiple available meeting spaces that are different from the first meeting space overlaid on the meeting space status interface.
[0416] In some embodiments, the list of multiple available meeting spaces other than the first meeting space is ordered based on a proximity of the multiple available meeting spaces to the first meeting space.
[0417] In some embodiments, processing unit 1408 is further configured to: enable display of multiple filter enable representations on display unit 1402 (e.g., using display control unit 1410); detect a sequence of one or more user inputs corresponding to selection of one or more filter enable representations via one or more input units 1404 (e.g., using input detection unit 1412); and in response to the sequence of one or more user inputs selecting one or more filter enable representations: obtain a set of filter criteria corresponding to one or more filter enable representations (e.g., using supply unit 1416); and replace the display of the list of multiple available meeting spaces other than the first meeting space with a subset of the list of multiple available meeting spaces other than the first meeting space that meet the set of filter criteria (e.g., using display control unit 1410).
[0418] In some embodiments, in response to detecting a second user input corresponding to selecting a find room enable indication, processing unit 1408 is further configured to: (e.g., utilizing display control unit 1410) enable display of an authentication interface provided to a user of authentication device 1400 on display unit 1402, wherein the meeting space discovery interface is displayed in response to the user of authentication device 1400.
[0419] In some embodiments, the plurality of available meeting spaces other than the first meeting space are filtered based on access credentials associated with an account corresponding to the authenticated user of device 1400 .
[0420] In some embodiments, the floor plan shows unavailable meeting spaces in a first graphical state and available meeting spaces in a second graphical state.
[0421] In some embodiments, the processing unit 1408 is further configured to detect a second user input corresponding to selecting a third meeting space in the floor plan via one or more input units 1404 (e.g., using the input detection unit 1412), and in response to detecting the second user input selecting the third meeting space, the processing unit 1408 is further configured to replace the display of instructions for navigating from the first meeting space to the second meeting space with different instructions for navigating from the first meeting space to the third meeting space (e.g., using the display control unit 1410).
[0422] The operations in the above information processing method are optionally implemented by running one or more functional modules in an information processing device, such as a general-purpose processor (for example, as described above with respect to Figure 1A and Figure 3 described) or application-specific chips.
[0423] The above reference Figures 9A to 9B 、 FIG. 10A to FIG. 10B as well as Figures 11A to 11C The operation is optionally performed by Figure 1A to Figure 1B or Figures 12 to 1410. For example, detection operation 914, detection operation 1012, and detection operation 1106 are optionally implemented by event classifier 170, event recognizer 180, and event handler 190. Event monitor 171 in event classifier 170 detects contact on touch-sensitive display 112, and event distributor module 174 transmits the event information to application 136-1. A corresponding event recognizer 180 of application 136-1 compares the event information with a corresponding event definition 186 and determines whether a first contact at a first location on the touch-sensitive surface (or rotation of the device) corresponds to a predefined event or sub-event, such as selection of an object on a user interface or rotation of the device from one orientation to another. When a corresponding predefined event or sub-event is detected, event recognizer 180 activates an event handler 190 associated with the detection of the event or sub-event. Event handler 190 optionally uses or calls data updater 176 or object updater 177 to update application internal state 192. In some embodiments, the event handler 190 accesses the corresponding GUI updater 178 to update the content displayed by the application. Similarly, those skilled in the art will clearly understand that based on the Figure 1A to Figure 1B How the components depicted in FIG. 1 can implement other processes.
[0424] Attention now turns to embodiments of a user interface ("UI") and related processes that can be implemented on an electronic device, such as a portable multifunction device 100 having a display, a touch-sensitive surface, and optionally one or more sensors for detecting intensity of contact with the touch-sensitive surface, or a device 300 having non-volatile memory, a display, an input device, and one or more processors.
[0425] Figures 15A to 15R Figures 1 and 2 illustrate exemplary user interfaces for updating a user interface displayed on a first device based on input from a second device according to some embodiments. The user interfaces in these figures are used to illustrate the processes described below, including FIG. 20A to FIG. 20B Although some of the examples that follow will be given with reference to input on a touch screen display (where the touch-sensitive surface and display are combined), in some embodiments, the device detects input on a touch-sensitive surface 451 that is separate from the display 450, such as Figure 4B As shown in .
[0426] In some embodiments, the first device is located outside the meeting space (e.g., Figures 5A to 5BFor example, the first device is associated with the meeting space, such as being fixed to a wall outside the meeting space. In some embodiments, the first device is associated with the meeting space. For example, the first device is a personal device associated with the user, such as a phone, tablet, laptop, etc. In this example, when the user walks into the meeting space with the first device, the location of the device is associated with the meeting space, and the meeting space functionality for the particular meeting space is enabled on the first device. In some embodiments, a second device (e.g., Figures 5A to 5B The second device 504-A-1 in the embodiment is synchronized with the first device. For example, the second device is associated with the meeting space, such as being fixed to a wall in the meeting space, fixed to furniture or equipment in the meeting space, or being movably located in the meeting space.
[0427] Figure 15A A first device 502-A-1 (e.g., Figures 5A to 5B The external device associated with the conference space 1 of the building A in the conference room displays the conference status interface 1518. Figure 15A Also shown is a second device 504-A-1 (e.g., Figures 5A to 5B 15. Meeting status interface 1520 is displayed (within the device associated with meeting space 1 in building A). Meeting status interface 1520 is similar to and adapted from meeting status interface 1518. Therefore, meeting status interface 1518 and meeting status interface 1520 include elements labeled with the same reference numbers and have the same functionality. For the sake of brevity, only the differences are described here.
[0428] like Figure 15A As shown, meeting status interface 1518 includes meeting space affordance 1506, which indicates that first device 502-A-1 corresponds to a Ganymede meeting space and an occupancy limit of the Ganymede meeting space (e.g., because there are eight chairs in the Ganymede meeting space, the occupancy limit is eight people). When activated (e.g., using contact), meeting space affordance 1506 causes a log of the Ganymede meeting space to be displayed. For example, the log indicates: reported previous or unresolved issues with the Ganymede meeting space; cleaning records of the Ganymede meeting space; the last occupant of the Ganymede meeting space; and so on. For example, see Figures 6P to 6Q and its description.
[0429] like Figure 15A As shown, the meeting status interface 1518 also includes a plurality of property icons 1508a and 1508b, collectively referred to as "property icons 1508," which indicate devices or features associated with the Ganymede meeting space. Figure 15A , a first attribute icon 1508a indicates that the Ganymede meeting space is equipped with at least one display. A second attribute icon 1508b indicates that the Ganymede meeting space includes video and / or video conferencing equipment. When activated (e.g., by contact), the attribute icons 1508 cause more details about the equipment or features associated with the Ganymede meeting space to be displayed. For example, if the first attribute icon 1508a is selected, information or details about the display, such as model name, size, resolution, aspect ratio, input, age, etc., are displayed.
[0430] like Figure 15A As shown, meeting status interface 1518 also includes calendar affordance 1510, which, when activated (e.g., by contact), causes the scheduling of an appointment associated with the Ganymede meeting space. Figures 6B to 6C and its description. Figure 15A As shown, meeting status interface 1518 also includes a "room help" affordance 1516, which, when activated (e.g., by contact), causes a problem reporting interface to replace meeting status interface 1518. For example, see Figures 6J to 6P and its description.
[0431] like Figure 15A As shown, meeting status interface 1518 also includes: the current time (e.g., 9:41); a status indicator 1512 that indicates the current availability or reservation status of the Ganymede meeting space; and an affordance 1514 that, when activated (e.g., using a left-to-right swipe gesture or a predefined gesture such as a single-finger tap gesture), causes status indicator 1512 to change (e.g., from "reserved" to "meeting in progress," or from "available" to "meeting in progress"). In this example, the Ganymede meeting space is available from 9:30 to 10:00 and is reserved by A. Broccoli from 10:00 to 11:00. Figure 15A As shown, status indicator 1512 indicates "Available" based on the current time (e.g., 9:41) because the Ganymede meeting space is available until 10:00. Figure 15A , the indicator states that 1514 is enabled and also prompts the user to "Slide to take over before 10:00."
[0432] According to some embodiments, when the meeting space is unoccupied, status indicator 1512 indicates "available" until an early check-in threshold 1522 associated with the next appointment (e.g., 15 minutes before the start time of the upcoming appointment). In some embodiments, when the meeting space is unoccupied and the current time is before the early check-in threshold 1522 associated with the next appointment, the assertion indicator 1514 is enabled to take over / requisition the meeting space. In some embodiments, when the meeting space is unoccupied, the current time is before the early check-in threshold 1522 associated with the next appointment, and there is a predefined amount of time (e.g., 20, 25, or 30 minutes) before the next appointment, the assertion indicator 1514 is enabled to take over / requisition the meeting space. For example, see also Figures 6I to 6J and its description.
[0433] FIG. 15A to FIG. 15B The sequence of the status indicator changing from "Available" to "Booked" is shown. Figure 15B In , status indicator 1512 indicates that the Ganymede conference space is "reserved" by A. Broccoli and that A. Broccoli must check in before 10:07. Figure 15B , the affordance 1514 also prompts the user to "Swipe to Check In." In this example, the Ganymede meeting space is available from 9:30 to 10:00 and is reserved by A. Broccoli from 10:00 to 11:00.
[0434] In accordance with some embodiments, status indicator 1512 indicates "Appointment" between an early check-in threshold 1522 and a check-in deadline 1524 (e.g., 7 minutes after the start time of the upcoming appointment). Thus, in some embodiments, status indicator 1512 indicates "Appointment" when the current time (e.g., 9:46) is between the early check-in threshold 1522 and the check-in deadline 1524. Furthermore, in some embodiments, when meeting space is available and the current time is between the early check-in threshold 1522 and the check-in deadline 1524, the affordance 1514 is declared enabled to check in to the upcoming appointment.
[0435] In some embodiments, an appointment is claimed or signed in to an appointment without authenticating the user as an appointment holder or invitee. Thus, any user can sign in to an appointment from 10:00 to 11:00. In some embodiments, a user is authenticated as an appointment organizer or, optionally, an invitee of an appointment before being able to claim or sign in to an appointment.
[0436] Figures 15B to 15CA sequence is shown of a user checking in to an upcoming appointment at a meeting space when the meeting space is not occupied. Figure 15B Also shown is first electronic device 502-A-1 detecting a left-to-right swipe gesture using contact 1526 on assertion indicator 1514. Figure 15C The status indicators 1512 displayed by the first electronic device 502-A-1 and the second electronic device 504-A-1 are shown in response to Figure 15C The statement in the affordance represents a left-to-right swipe gesture on 1514 to indicate "meeting in progress." Figure 15C The second electronic device 504-A-1 responds to Figure 15B A left-to-right swipe gesture on the claim affordance 1514 in displays the sign-out affordance 1528. Thus, the user checks in to the appointment that starts at 10:00, and the user claims the Ganymede meeting space before the appointment starts because the Ganymede meeting space is available before the appointment start time.
[0437] In some embodiments, the second electronic device 504-A-1 responds to Figure 15C The statement in the affordance indicates that a left-to-right swipe gesture on 1514 displays the meeting list interface. For example, see also 7A to 7D For example, if the user has not yet been confirmed as a participant in an upcoming appointment, the meeting list interface corresponds to Figure 18D In another example, if the user has been confirmed as a participant in an upcoming appointment, the meeting list interface corresponds to Figure 18D In the authorized conference list interface 1858. According to some embodiments, reference 16A to 16C as well as 17A to 17D The confirmation process is described in more detail.
[0438] Figures 15D to 15F Shows the sequence checked out from the current meeting. Figure 15D Second electronic device 504 -A- 1 is shown detecting a right-to-left swipe gesture with contact 1530 on sign-out enable representation 1528 . Figure 15E The second device 504-A-1 is shown responding to Figure 15D The sign-out interface 1536 is displayed by swiping from right to left on the screen 1528. Figure 15EAs shown, sign-out confirmation interface 1536 includes prompt 1532 indicating that the user will automatically sign out of the Ganymede meeting space in 10 seconds. Sign-out confirmation interface 1536 also includes: a sign-out confirmation enable indication 1534A, which, when activated (e.g., by touch), causes the remainder of the ongoing meeting to be canceled and the Ganymede meeting space to be released for a subsequent local takeover or remote reservation; and a cancel enable indication 1534B, which, when activated (e.g., by touch), causes the sign-out process to be aborted.
[0439] Figure 15E Also shown is second electronic device 504-A-1 detecting contact 1538 at a location corresponding to sign-out confirmation enable indication 1534A. Figure 15F The second electronic device 504-A-1 responds to Figure 15E The sign-out confirmation screen 1534A is selected and the display of the sign-out confirmation screen 1536 is replaced with the conference status screen 1520. Figure 15F As shown, in response to Figure 15E The sign-out confirmation indicator in 1534A indicates the selection of 1534A, and the status indicators 1512 displayed on the conference status interface 1518 and the conference status interface 1520 both indicate "available." According to some embodiments, after signing out of the conference, the conference space is released for local takeover and / or remote reservation.
[0440] Figure 15G Shows the assumption that the user has aborted Figures 15D to 15F The checkout process shown (e.g., by selecting to cancel indication 1534B) or assuming the user does not perform Figure 15D 15F, the first device 502-A-1 displays the conference status interface 1518 and the second electronic device 504-A-1 displays the conference status interface 1520. Figure 15G As shown, since the reservation of A. Broccoli in the Ganymede conference space was an ongoing meeting before 11:00, the status indicators 1512 displayed on the meeting status interface 1518 and the meeting status interface 1520 both indicate “meeting in progress”.
[0441] Figures 15H to 15J 15H shows a sequence of a user extending a meeting in a current meeting space. FIG15H shows a first state of second device 504-A-1 displaying first extension interface 1546A-1. According to some embodiments, when the meeting space is available after the current meeting, second device 504-A-1 displays the first state of first extension interface 1546A-1 for a predefined time before the end of the current meeting (e.g., 5 minutes before the end time).
[0442] like Figure 15H As shown, the first state of the first extension interface 1546A-1 includes a prompt 1540, which indicates that the meeting is about to end (e.g., at 11:00) and that participants of the current meeting can extend the meeting from 11:00 to 11:30 in the Ganymede meeting space. The first state of the first extension interface 1546A-1 also includes an extension enable indication 1542A, which, when activated (e.g., using contact), causes the current meeting to be extended and the first state of the first extension interface 1546A-1 to be replaced by the second state of the first extension interface 1546A-2 (e.g., as shown in FIG. Figure 15G and "No, thank you" can indicate 1542B, which, when activated (eg, using contact), causes the first state of the first extended interface 1546A-1 to be replaced by the conference status interface 1520 (eg, as shown); Figure 15E As shown). Figure 15H As shown, the first state of the first extension interface 1546A-1 also includes a timer 1544, which indicates that the user has 2 minutes and 59 seconds to extend the current meeting in the Ganymede meeting space before automatically signing out of the meeting from the meeting space. After signing out, the user will no longer be able to extend the current meeting and must schedule a new meeting to occupy the Ganymede meeting space.
[0443] Figure 15H Also shown is second electronic device 504-A-1 detecting contact 1548 at a location corresponding to extended enable indication 1542A. Figure 15I The second electronic device 504-A-1 responds to Figure 15H The selection of the extended indicator 1542A replaces the display of the first state of the first extended interface 1546A-1 with the second state of the first extended interface 1546A-2. Figure 15I As shown, the second state of first extended interface 1546A-2 includes: prompt 1550, which indicates that the current meeting in the Ganymede meeting space will now end at 11:30; and confirmation enable representation 1552, which, when activated (e.g., using contact), causes the second state of first extended interface 1546A-2 to be replaced by meeting status interface 1520 (e.g., as shown in FIG. Figure 15J shown).
[0444] Figure 15I Also shown is second electronic device 504-A-1 detecting contact 1554 at a location corresponding to confirmation indication 1552. Figure 15JThe display of the second state of the first extended interface 1546A-2 is shown as being replaced by the meeting status interface 1520 in response to selection of the confirmation enable indication 1552 in FIG. 15I .
[0445] Figures 15K to 15L A sequence is shown of a user checking in to an upcoming appointment for a meeting space while the meeting space is occupied. Figure 15K The conference status interfaces 1518 and 1520 shown in FIG are similar to and adapted from Figure 15B and Figure 15J The conference status interfaces 1518 and 1520 in FIG. Figure 15B 、 Figure 15J and Figure 15K A similar user interface is included, and elements labeled with the same reference numbers in both figures have the same function, and for the sake of brevity, only the differences are described here.
[0446] In this example, the Ganymede meeting space is reserved for A. Broccoli from 10:00 to 11:30 (e.g., an ongoing meeting), and the Ganymede meeting space is reserved for C. Schmidlapp from 11:30 to 12:30 (e.g., the next meeting). Figure 15K As shown, first electronic device 502-A-1 displays meeting status interface 1518, in which status indicator 1512 indicates that the Ganymede meeting space is "reserved" to C. Schmidlapp, and C. Schmidlapp has not checked in until 11:37. The statement enable representation 1514 displayed by first electronic device 502-A-1 also prompts the user to "slide to check in" to the upcoming appointment. In addition, Figure 15K In FIG, second electronic device 504-A-1 displays meeting status interface 1520 with status indicator 1512, indicating that A. Broccoli's "meeting is in progress" until 11:30. The sign-out affordance 1528 displayed by second electronic device 504-A-1 also prompts the user to "slide to sign out" from the ongoing meeting.
[0447] Figure 15K Also shown is first electronic device 502-A-1 detecting a left-to-right swipe gesture of contact 1556 on assertion affordance 1514. Figure 15L Shows the response to Figure 15K With a swipe gesture on the statement indicator 1514, the first electronic device 502-A-1 updates the status indicator 1512 to indicate "meeting is about to start." Figure 15L Also shown is the response to Figure 15KWith a swipe gesture on the indicator 1514, the second electronic device 504-A-1 displays a notification 1558 indicating that the participants for the next meeting have signed in.
[0448] Figures 15M to 15N 15M illustrates a sequence of a user extending a meeting in different meeting spaces. FIG15M illustrates second device 504-A-1 in a first state displaying second extension interface 1546B-1. According to some embodiments, when the meeting space is unavailable after the current meeting, second device 504-A-1 displays the first state of second extension interface 1546B-1 for a predefined time before the end of the current meeting (e.g., 5 minutes before the end time).
[0449] like Figure 15M As shown, the first state of the second extension interface 1546B-1 includes a prompt 1560 indicating that the meeting is about to end (e.g., at 11:30) and that participants in the current meeting are able to extend the meeting in one of a plurality of available meeting spaces other than the Ganymede meeting space. The first state of the second extension interface 1546B-1 also includes a plurality of enable indications 1562A, 1562B, 1562C, and 1562D (sometimes collectively referred to as "indicators 1562") associated with the available meeting spaces. Each enable indication 1562 is associated with a meeting space name, an occupancy limit, and an available length. When activated (e.g., by contact), the enable indication 1562 causes the first state of the second extension interface 1546B-1 to be replaced by the second state of the second extension interface 1546B-2 (e.g., as Figure 15N 15M ), the first state of the second extended interface 1546B-1 also includes a disarm indicator 1564, which, when activated (e.g., by contact), causes the first state of the second extended interface 1546B-1 to be replaced with the meeting state interface 1520 (e.g., as shown in FIG. 15M ). Figure 15J shown).
[0450] Figure 15M Second electronic device 504-A-1 is also shown detecting contact 1566 at a location corresponding to affordance 1562B associated with the Callisto meeting space. Figure 15N It is shown that in response to selection of affordance 1562B in FIG. 15M , second electronic device 504 -A- 1 replaces display of the first state of second extended interface 1546B- 1 with the second state of second extended interface 1546B- 2 .
[0451] like Figure 15NAs shown, the second state of the second extension interface 1546B-2 includes: a first prompt 1568 indicating that the current meeting has been extended to 12:30 in the Callisto meeting space; and a second prompt 1570 indicating that the user will automatically sign out of the Ganymede meeting space in ten seconds. The second state of the second extension interface 1546B-2 also includes: a sign-out enable indication 1572A, which, when activated (e.g., by contact), causes the user to sign out of the Ganymede meeting space; and a cancel enable indication 1572B, which, when activated (e.g., by contact), causes the second state of the second extension interface 1546B-2 to be replaced by the meeting status interface 1520 (e.g., as shown in FIG. 1 ). Figure 15O shown).
[0452] Figure 15N Also shown is second electronic device 504-A-1 detecting contact 1574 at a location corresponding to cancel-indication 1572B. Figure 15O The second electronic device 504-A-1 is shown to replace the display of the second state of the second extended interface 1546B-2 with the conference status interface 1520 in response to the selection of the cancel enable indication 1572B in Figure 15N. According to some embodiments, the second electronic device 504-A-1 also displays an option for transferring the electronic conference (e.g., telephone conference or video conference) to the Callisto meeting space (e.g., as shown in Figure 15N). Figures 19H to 19K In one example, the electronic conference is placed on hold until the participant signs in at the Callisto conference space, at which point the electronic conference is presented via a device within the Callisto conference space. In another example, the electronic conference is transferred to the participant's personal device (e.g., mobile phone, tablet, etc.) until the participant signs in at the Callisto conference space, at which point the electronic conference is presented via a device within the Callisto conference space. According to some embodiments, the second electronic device 504-A-1 also displays a plan view with a direction pointing to the Callisto conference space (e.g., as shown in FIG. 1 ). Figure 7Y and 19K shown).
[0453] Figures 15P to 15R A sequence is shown in which participants of an expired meeting are reminded to make their next reservation for a meeting space. Figure 15P The first electronic device 502-A-1 is shown displaying a meeting status interface 1518, wherein the status indicator 1512 indicates that "the meeting is about to start" (eg, Figure 15O shown). Figure 15PAlso shown is second electronic device 504-A-1 displaying meeting expiration interface 1580, indicating that the current meeting can end and the user will be automatically signed out in 10 seconds. In this example, A. Broccoli's appointment expires at 11:30, and C. Schmidlapp's appointment starts at 11:30.
[0454] Figure 15Q FIG. 5 shows that in response to the start of C. Schmidlapp's appointment, the first electronic device 502-A-1 updates the status indicator 1512 from "meeting is about to start" to "meeting in progress". Figure 15Q , meeting status interface 1518 includes doorbell affordance 1590 in response to participants of a previous meeting in the Ganymede meeting space failing to leave after their appointments expired. When activated (e.g., by contact), doorbell affordance 1590 causes an alert (e.g., as shown) to be presented to the participants of the previous meeting in the Ganymede meeting space. Figure 15R shown). Figure 15Q Also shown is that in response to C. Schmidlapp's appointment start, the second electronic device 504-A-1 replaces the display of the meeting expiration interface 1580 with the meeting status interface 1520, wherein the status indicator 1512 indicates "meeting in progress."
[0455] Figure 15Q It is further shown that the first electronic device 504-2-1 detects contact 1592 at a location corresponding to the doorbell enable indication 1590. Figure 15R Shows the response to Figure 15Q Upon selection of the doorbell indicator 1590, the second electronic device 504-A-1 replaces the display of the meeting status interface 1520 with an expiration alert interface 1594. According to some embodiments, the expiration alert interface 1594 is accompanied by an audible alert or message provided by the second electronic device 504-A-1 and / or audio / video devices within the Ganymede meeting space. Figure 15R As shown, expiration alert interface 1594 includes a disarm indicator 1596 that, when activated (e.g., by contact), causes expiration alert interface 1594 to be replaced by meeting status interface 1520 (e.g., as shown in FIG. Figure 15Q shown).
[0456] Figure 16A 16 shows a flow diagram of a method 1600 for authenticating a user to confirm a reservation of a meeting space, according to some embodiments. Figure 16A As shown, method 1600 is associated with a particular meeting space (e.g., Figures 5A to 5B5A ). According to some embodiments, method 1600 is performed at least in part by: a conference space device 1601A (e.g., first device 502-A-1 or second device 504-A-1 associated with the conference space); a personal device 1601B (e.g., a mobile device associated with a user, such as a mobile phone, tablet, or laptop); and a server 1601C (e.g., controller 510 in FIG. 5A ).
[0457] In some embodiments, meeting space device 1601A broadcasts (1602) a beacon signal that includes at least a meeting space (MS) identifier (ID) associated with the meeting space or meeting space device 1601A. For example, the MS ID is the name of the meeting space, a unique number associated with the meeting space, a unique number associated with meeting space device 1601A, a MAC address of meeting space device 1601A, etc. In some embodiments, a beacon application is executed on meeting space device 1601A. In some embodiments, the beacon signal is broadcast via BLUETOOTH, a near field communication (NFC) protocol, WLAN, etc.
[0458] In some embodiments, personal device 1601B obtains a beacon signal from conference space device 1601A and sends 1604 a proximity indicator to server 1601C. According to some embodiments, the proximity indicator includes at least an MS ID and a user ID associated with personal device 1601B or a user of personal device 1601B. For example, the user ID is the name of the user associated with personal device 1601B, a unique number associated with personal device 1601B, a MAC address of personal device 1601B, etc.
[0459] According to some embodiments, a beacon discovery application is executed on personal device 1601B. In some embodiments, personal device 1601B sends a proximity indicator while the beacon discovery application is active. In some embodiments, personal device 1601B sends a proximity indicator while the beacon discovery application is active and personal device 1601B is unlocked. According to some embodiments, when personal device 1601B is within range of meeting space device 1601A, personal device 1601B obtains a beacon signal from meeting space device 1601A. In some embodiments, the proximity indicator is sent to server 1601C via a WLAN, VLAN, LAN, etc.
[0460] In some embodiments, after obtaining the proximity indicator, server 1601C performs (1606) a confirmation process to determine whether to allow the user to confirm (e.g., claim or check in) the upcoming appointment for the meeting space. According to some embodiments, in response to obtaining the proximity indicator, server 1601C obtains the appointment schedule for the meeting space based on the MS ID to identify candidate user IDs associated with attendees of the upcoming appointment for the meeting space. After identifying the candidate user IDs, server 1601C confirms the user if the user ID associated with the proximity indicator matches one of the identified candidate user IDs.
[0461] According to some embodiments, in response to obtaining the proximity indicator, server 1601C obtains a reservation schedule for the meeting space based on the MS ID, wherein the MS ID is used to identify a candidate user ID associated with an organizer of an upcoming reservation for the meeting space. After identifying the candidate user ID associated with the organizer, server 1601C confirms the user if the user ID associated with the proximity indicator matches the candidate user ID associated with the organizer of the upcoming reservation for the meeting space.
[0462] In some embodiments, if the user is confirmed, server 1601C sends (1608) an instruction to conference space device 1601A to confirm the upcoming appointment. According to some embodiments, in response to obtaining the instruction, conference space device 1601A passively declares or checks in (1610) the upcoming appointment. For example, in response to obtaining the instruction, conference space device 1601A checks in the upcoming appointment without the user interacting with the declaration enable representation and updates the status from "appointment" to "meeting in progress" if the meeting space is not occupied, or to "meeting about to start" if the meeting space is still occupied. In some embodiments, in response to obtaining the instruction, conference space device 1601A displays a meeting list interface (e.g., as shown in FIG. Figure 7D or Figure 19C shown).
[0463] In some embodiments, if the user is not confirmed, the server 1601C sends (1612) a request to the personal device 1601B to obtain login credentials. According to some embodiments, in response to the obtain request, the personal device 1601B presents (1614) a prompt (e.g., such as a user name and password) requesting the user to manually enter his / her login credentials (e.g., username and password, etc.). Figure 7B ), the login credentials may be sent to server 1601C to attempt to complete the confirmation process. In some embodiments, the login credential prompt is replaced or supplemented by a prompt for biometric information (e.g., voice sample, retinal scan, fingerprint scan, etc.).
[0464] Figure 16B 16 shows a flow diagram of a method 1650 for authenticating a user to confirm a reservation of a meeting space, according to some embodiments. Figure 16B As shown, method 1650 is associated with a particular meeting space (e.g., Figures 5A to 5B 5A ). In some embodiments, method 1650 is performed at least in part by: conference space device 1601A (e.g., first device 502-A-1 or second device 504-A-1 associated with the conference space); personal device 1601B (e.g., a mobile device associated with a user, such as a mobile phone, tablet, or laptop); and server 1601C (e.g., controller 510 in FIG. 5A ).
[0465] In some embodiments, personal device 1601b broadcasts 1652 a beacon signal that includes at least a user identifier (ID) associated with personal device 1601b or a user of personal device 1601b. For example, the user ID is the name of the user associated with personal device 1601B, a unique number associated with personal device 1601B, a MAC address of personal device 1601B, etc. According to some embodiments, a beacon application is executed on personal device 1601B. In some embodiments, the beacon signal is broadcast via BLUETOOTH, near field communication (NFC) protocol, WLAN, etc.
[0466] In some embodiments, meeting space device 1601A obtains a beacon signal from personal device 1601B and sends (1654) a proximity indicator to server 1601C. According to some embodiments, the proximity indicator includes at least a user ID and a meeting space (MS) ID associated with the meeting space or meeting space device 1601A. For example, t...
Claims
1. A method comprising: At an electronic device having a display and one or more input devices: facilitating presentation of an electronic conference corresponding to an ongoing appointment in a first conference space, wherein presenting the electronic conference corresponding to the ongoing appointment in the first conference space comprises presenting electronic conference data using a device in the conference space; in facilitating presentation of the electronic conference, determining whether an end time of the ongoing appointment within the first conference space is less than a threshold amount of time from a current time; as well as displaying on the display one or more options for continuing the electronic conference outside of the first conference space based on determining that the end time of the ongoing appointment in the first conference space is less than the threshold amount of time from the current time and that the first conference space is unavailable after the end time of the ongoing appointment in the first conference space; detecting, via the one or more input devices, a selection of a first option from the one or more options for continuing the electronic conference outside of the first meeting space; as well as In response to detecting selection of the first option: ceasing to facilitate the electronic conference via the device in the first meeting space; as well as initiating a process for continuing the electronic conference to a device not associated with the first conference space, wherein displaying the one or more options for continuing the electronic conference outside of the first conference space includes: displaying a first transfer affordance provided to transfer the electronic conference to a second available conference space, wherein the selected first option corresponds to the first transfer affordance; and Initiating the process for transferring the electronic conference to a device not associated with the first conference space includes transferring the electronic conference to one or more handheld electronic devices of participants in the first conference space of the electronic conference.
2. The method according to claim 1, further comprising: Based on determining that the end time of the ongoing appointment in the first meeting space is less than the threshold amount of time starting from the current time, and the first meeting space is available after the end time of the ongoing meeting in the first meeting space, an enabling indication is displayed on the display to continue the electronic conference after the end time and extend the ongoing appointment in the first meeting space.
3. The method of claim 1 , wherein displaying the one or more options for continuing the electronic conference outside of the first conference space further comprises: A second transfer affordance representation is displayed that is provided to transfer the electronic conference to one or more handheld electronic devices of participants in the first meeting space of the electronic conference.
4. The method according to claim 3, further comprising: In response to detecting selection of the first option, an option to sign out from the ongoing appointment is displayed on the display.
5. The method according to claim 3, further comprising: detecting, via the one or more input devices, a selection of a second option from the one or more options for continuing the electronic conference outside of the first meeting space; as well as In response to detecting selection of the second option: ceasing to facilitate the electronic conference via the device in the first meeting space; and initiating a process for continuing the electronic conference to a device not associated with the first conference space, wherein the selected second option corresponds to the second transfer affordance, and the method further comprises: in response to the selection of the second transfer affordance, A floor plan of available meeting space is displayed on the display.
6. The method according to claim 5, further comprising: detecting, via the one or more input devices, a selection of a second available meeting space from the floor plan of available meeting spaces; as well as In response to detecting a selection of the second available meeting space: ceasing to present the electronic conference using the device in the first conference space; and The electronic conference is transferred to a device associated with the second available conference space.
7. The method according to claim 3, further comprising: detecting, via the one or more input devices, a selection of a second option from the one or more options for continuing the electronic conference outside of the first meeting space; as well as In response to detecting selection of the second option: ceasing to facilitate the electronic conference via the device in the first meeting space; and initiating a process for continuing the electronic conference to a device not associated with the first conference space, wherein the selected second option corresponds to the second transfer affordance, and the method further comprises: in response to the selection of the second transfer affordance, A list of available meeting spaces is displayed on the display.
8. The method according to claim 7, further comprising: Prior to displaying the list of available meeting spaces, the list of available meeting spaces is filtered according to at least one of the attributes or the selected attributes associated with the meeting spaces.
9. The method of claim 1 , wherein facilitating presentation of the electronic conference comprises: The electronic conference is transferred from a handheld electronic device of at least one participant of the electronic conference to the device associated with the first conference space.
10. An electronic device comprising: monitor; one or more input devices; one or more processors; non-transitory memory; and One or more programs, wherein the one or more programs are stored in the memory and configured to be executed by the one or more processors, the one or more programs comprising instructions for performing the following operations: facilitating presentation of an electronic conference corresponding to an ongoing appointment in a first conference space, wherein presenting the electronic conference corresponding to the ongoing appointment in the first conference space comprises presenting electronic conference data using a device in the conference space; in facilitating presentation of the electronic conference, determining whether an end time of the ongoing appointment within the first conference space is less than a threshold amount of time from a current time; as well as displaying on the display one or more options for continuing the electronic conference outside of the first conference space based on determining that the end time of the ongoing appointment in the first conference space is less than the threshold amount of time from the current time and that the first conference space is unavailable after the end time of the ongoing appointment in the first conference space; detecting, via the one or more input devices, a selection of a first option from the one or more options for continuing the electronic conference outside of the first meeting space; as well as In response to detecting selection of the first option: ceasing to facilitate the electronic conference via the device in the first meeting space; as well as initiating a process for continuing the electronic conference to a device not associated with the first conference space, wherein displaying the one or more options for continuing the electronic conference outside of the first conference space includes: displaying a first transfer affordance provided to transfer the electronic conference to a second available conference space, wherein the selected first option corresponds to the first transfer affordance; and Initiating the process for transferring the electronic conference to a device not associated with the first conference space includes transferring the electronic conference to one or more handheld electronic devices of participants in the first conference space of the electronic conference.
11. The electronic device of claim 10, wherein displaying the one or more options for continuing the electronic conference outside the first conference space further comprises: A second transfer affordance representation is displayed that is provided to transfer the electronic conference to one or more handheld electronic devices of participants in the first meeting space of the electronic conference.
12. The electronic device of claim 11, wherein the one or more programs further comprise instructions for: detecting, via the one or more input devices, a selection of a second option from the one or more options for continuing the electronic conference outside of the first meeting space; In response to detecting selection of the second option: ceasing to facilitate the electronic conference via the device in the first meeting space; and initiating a process for continuing the electronic conference to a device not associated with the first conference space, wherein the selected second option corresponds to the second transfer affordance, and the one or more programs further include instructions for: In response to selection of the second transfer affordance, a floor plan of available meeting space is displayed on the display.
13. The electronic device of claim 12, wherein the one or more programs further comprise instructions for performing the following operations: detecting, via the one or more input devices, a selection of a second available meeting space from the plan view of available meeting spaces; and In response to detecting a selection of the second available meeting space: ceasing to present the electronic conference using the device in the first conference space; and The electronic conference is transferred to a device associated with the second available conference space.
14. A non-transitory computer-readable storage medium storing one or more programs, the one or more programs comprising instructions that, when executed by an electronic device having a display and one or more input devices, cause the electronic device to: facilitating presentation of an electronic conference corresponding to an ongoing appointment in a first conference space, wherein presenting the electronic conference corresponding to the ongoing appointment in the first conference space comprises presenting electronic conference data using a device in the conference space; in facilitating presentation of the electronic conference, determining whether an end time of the ongoing appointment within the first conference space is less than a threshold amount of time from a current time; as well as displaying on the display one or more options for continuing the electronic conference outside of the first conference space based on determining that the end time of the ongoing appointment in the first conference space is less than the threshold amount of time from the current time and that the first conference space is unavailable after the end time of the ongoing appointment in the first conference space; detecting, via the one or more input devices, a selection of a first option from the one or more options for continuing the electronic conference outside of the first meeting space; as well as In response to detecting selection of the first option: ceasing to facilitate the electronic conference via the device in the first meeting space; as well as initiating a process for continuing the electronic conference to a device not associated with the first conference space, The one or more options displayed for continuing the electronic conference outside the first conference space include: displaying a first transfer affordance provided to transfer the electronic conference to a second available conference space, wherein the selected first option corresponds to the first transfer affordance; and Initiating the process for transferring the electronic conference to a device not associated with the first conference space includes transferring the electronic conference to one or more handheld electronic devices of participants in the first conference space of the electronic conference.
15. The non-transitory computer-readable storage medium of claim 14, wherein displaying one or more options for continuing the electronic conference outside of the first conference space further comprises: A second transfer affordance representation is displayed that is provided to transfer the electronic conference to one or more handheld electronic devices of participants in the first meeting space of the electronic conference.
16. The non-transitory computer-readable storage medium of claim 15, wherein the one or more programs further cause the electronic device to: detect, via the one or more input devices, a selection of a second option from the one or more options for continuing the electronic conference outside of the first conference space; In response to detecting selection of the second option: ceasing to facilitate the electronic conference via the device in the first meeting space; and initiating a process for continuing the electronic conference to a device not associated with the first conference space, Wherein the selected second option corresponds to the second transfer enable indication, and wherein the one or more programs further cause the electronic device to: display a floor plan of available meeting space on the display in response to selection of the second transfer enable indication.
17. The non-transitory computer-readable storage medium of claim 16, wherein the one or more programs further cause the electronic device to: detecting, via the one or more input devices, a selection of a second available meeting space from the plan view of available meeting spaces; and In response to detecting a selection of the second available meeting space: ceasing to present the electronic conference using the device in the first conference space; and The electronic conference is transferred to a device associated with the second available conference space.
