Unlocking a device by performing gestures on an unlock image
24 claims: 18 independent, 6 dependent
- 1タッチセンシティブディスプレイと、 メモリと、 1 つ 以上のプロセッサと、 前記メモリに記憶されると共に、前記1 つ 以上のプロセッサにより実行されるように構成された1 つ 以上のプログラムと、を備える携帯用電子機器であって、前記 1つ以上の プログラムは、 前記タッチセンシティブディスプレイ上の第1の所定の位置に表示されたアンロック画像において、前記タッチセンシティブディスプレイとの接触を 検出 するための命令と、 前記タッチセンシティブディスプレイとの持続的な接触を維持し ている間の 前記 検出 された接触の動きに従って前記タッチセンシティブディスプレイ上の前記アンロック画像を 移動する ための命令と、 前記アンロック画像が前記タッチセンシティブディスプレイ上の前記第1の所定の位置から前記タッチセンシティブディスプレイ上の所定のアンロック領域へ移動する場合に、前記携帯用電子機器をアンロック し、前記アンロック画像の表示を終了 するための命令と、を含 み、 前記アンロック画像は、ユーザが前記携帯用電子機器をアンロックするために交信するグラフィカルでインタラクティブなユーザインタフェースオブジェクトである ことを特徴とする携帯用電子機器。
- 2前記 移動する ことは、任意の所望の経路に沿った動きを含む、ことを特徴とする請求項1に記載の携帯用電子機器。
- 3前記 移動する ことは、前記第1の所定の位置から前記所定のアンロック領域への所定の表示経路に沿った動きを含む、ことを特徴とする請求項1に記載の携帯用電子機器。
- 4前記携帯用電子機器はハンドヘルド電子機器である、ことを特徴とする請求項1乃至3の何れか1項に記載の携帯用電子機器。
- 5前記携帯用電子機器をアンロックするのに必要な前記アンロック画像の動きの方向を通知する視覚的な合図を表示するための命令をさらに含む、ことを特徴とする請求項1乃至4の何れか1項に記載の携帯用電子機器。
- 6前記視覚的な合図はテキストを含む、ことを特徴とする請求項5に記載の携帯用電子機器。
- 7前記視覚的な合図は動きの方向を示す矢印を含む、ことを特徴とする請求項5に記載の携帯用電子機器。
- 8前記アンロック画像は単一の画像である、ことを特徴とする請求項1乃至7の何れか1項に記載の携帯用電子機器。
- 9タッチセンシティブディスプレイを備えた携帯用電子機器によって実行される 場合 に、該携帯用電子機器に、 前記タッチセンシティブディスプレイ上の第1の所定の位置に表示されたアンロック画像において、前記タッチセンシティブディスプレイとの接触を 検出させるための命令と 、 前記タッチセンシティブディスプレイとの持続的な接触を維持し ている間の 前記 検出 された接触の動きに従って前記タッチセンシティブディスプレイ上の前記アンロック画像を 移動させるための命令と 、 前記タッチセンシティブディスプレイ上の前記アンロック画像が動く結果として前記アンロック画像が前記タッチセンシティブディスプレイ上の前記第1の所定の位置から所定のアンロック領域へ移動する場合に、前記携帯用電子機器をアンロック させ、前記アンロック画像の表示を終了させるための命令と、 を 含 み、 前記アンロック画像は、ユーザが前記携帯用電子機器をアンロックするために交信するグラフィカルでインタラクティブなユーザインタフェースオブジェクトである ことを特徴とするコンピュータプログラム。
- 10前記 移動する ことは、任意の所望の経路に沿った動きを含む、ことを特徴とする請求項 9 に記載のコンピュータプログラム。
- 11前記 移動する ことは、前記第1の所定の位置から前記所定のアンロック領域への所定の表示経路に沿った動きを含む、ことを特徴とする請求項 9 に記載のコンピュータプログラム。
- 12前記携帯用電子機器はハンドヘルド電子機器である、ことを特徴とする請求項 9乃至11 の何れか1項に記載のコンピュータプログラム。
- 13前記携帯用電子機器をアンロックするのに必要な前記アンロック画像の動きの方向を通知する視覚的な合図を前記携帯用電子機器に表示させる命令をさらに含む、ことを特徴とする請求項 9乃至12 の何れか1項に記載のコンピュータプログラム。
- 14前記視覚的な合図はテキストを含む、ことを特徴とする請求項 13 に記載のコンピュータプログラム。
- 15前記視覚的な合図は動きの方向を示す矢印を含む、ことを特徴とする請求項 13 に記載のコンピュータプログラム。
- 16前記アンロック画像は単一の画像である、ことを特徴とする請求項 9乃至15 の何れか1項に記載のコンピュータプログラム。
- 17タッチセンシティブディスプレイを含む携帯用電子機器をアンロックする方法であって、 前記タッチセンシティブディスプレイ上の第1の所定の位置に表示されたアンロック画像において、前記タッチセンシティブディスプレイとの接触を 検出 するステップと、 前記タッチセンシティブディスプレイとの持続的な接触を維持し ている間の 前記 検出 された接触の動きに従って前記タッチセンシティブディスプレイ上の前記アンロック画像を 移動する ステップと、 前記タッチセンシティブディスプレイ上の前記アンロック画像が動く結果として前記アンロック画像が前記センシティブディスプレイ上の前記第1の所定の位置から所定のアンロック領域へ移動する場合に、前記携帯用電子機器をアンロック し、前記アンロック画像の表示を終了 するステップと、を含 み、 前記アンロック画像は、ユーザが前記携帯用電子機器をアンロックするために交信するグラフィカルでインタラクティブなユーザインタフェースオブジェクトである ことを特徴とする方法。
- 18前記 移動する ことは、任意の所望の経路に沿った動きを含む、ことを特徴とする請求項 17 に記載の方法。
- 19前記 移動する ことは、前記第1の所定の位置から前記所定のアンロック領域への所定の表示経路に沿った動きを含む、ことを特徴とする請求項 17 に記載の方法。
- 20前記携帯用電子機器はハンドヘルド電子機器である、ことを特徴とする請求項 17乃至19 の何れか1項に記載の方法。
- 21前記携帯用電子機器をアンロックするのに必要な前記アンロック画像の動きの方向を通知する視覚的な合図を表示するステップをさらに含む、ことを特徴とする請求項 17乃至20 の何れか1項に記載の方法。
- 22前記視覚的な合図はテキストを含む、ことを特徴とする請求項 21 に記載の方法。
- 23前記視覚的な合図は動きの方向を示す矢印を含む、ことを特徴とする請求項 21 に記載の方法。
- 24前記アンロック画像は単一の画像である、ことを特徴とする請求項 17乃至23 の何れか1項に記載の方法。
Independent claims24
95 paragraphs, as filed
[Cross-reference with related applications] This application relates to US Patent Application No. 11 / 322,550, filed December 23, 2005, entitled "Indication of Progress in the Direction to Satisfy User Input Conditions," which is in its entirety Incorporated herein by reference.
The disclosed embodiments generally relate to user interfaces using touch-sensitive displays, and more specifically to unlocking user interfaces in portable electronic devices.
Touch-sensitive displays (also known as "touch screens") are well known in the art. Touch screens are used in many electronic devices to display graphics and text and provide a user interface that allows the user to communicate with the device. The touch screen senses and responds to contact on the touch screen. The device may display one or more softkeys, menus, and other user interface objects on the touch screen. The user can communicate with the device by touching the touch screen at a position corresponding to the user interface object that the user wants to communicate with.
Touch screens are becoming more common as displays and user input devices in mobile devices such as mobile phones and personal digital assistants (PDAs). One problem associated with the use of touch screens in mobile devices is that unintentional contact with the touch screen causes the function to unintentionally start or stop. Thus, mobile devices, touch screens on such devices, and / or applications running on such devices can enter an active call, after a preset amount of idle time, or by the user. It can be locked when certain locking conditions are met, such as when manually locked.
Devices with touch screens and / or applications running on such devices have several, such as pressing a given set of buttons (simultaneously or consecutively) or entering a code or password. It can be unlocked by any of the well-known unlocking procedures. However, these unlocking procedures have drawbacks. Button combinations can be difficult to perform. Creating, remembering, and remembering passwords, codes, etc. can be very cumbersome. These drawbacks can reduce the ease of use of the unlocking method and, as a result, the ease of use of the device in general.
<patcit num="1"><text>U.S. Patent Application No. 11 / 322,550</text></patcit><patcit num="2"><text>U.S. Pat. No. 6,323,846</text></patcit><patcit num="3"><text>U.S. Pat. No. 6,570,557</text></patcit><patcit num="4"><text>U.S. Pat. No. 6,677,932</text></patcit><patcit num="5"><text>U.S. Patent Publication No. 2002/0015024 A1</text></patcit>
<p> Therefore, there is a need for more efficient, user-friendly procedures for unlocking such devices, touch screens, and / or applications. More generally, such devices, touch screens, and / or applications (eg, from the state of the user interface corresponding to the first application to the state of the user interface corresponding to the second application, the user interface in the same application. There is a need for more efficient, user-friendly procedures for transitioning between states of the user interface (such as between states of) or between locked and unlocked states. In addition, there is a need to provide the user with sensory feedback on progress towards satisfying the user input requirements required for the transition to take place.</p><p> In some embodiments, the method of controlling an electronic device with a touch-sensitive display is to detect contact with the touch-sensitive display while the device is in a user interface locked state, and in response to this contact, the device. The step of moving the image corresponding to the user interface unlocked state, the step of shifting the device to the user interface unlocked state when the detected contact corresponds to the predetermined gesture, and the detected contact do not correspond to the predetermined gesture. This includes the step of holding the device in the user interface locked state.</p><p> In some embodiments, the method of controlling a device with a touch-sensitive display senses the step of displaying an image on the touch-sensitive display while the device is in the user interface locked state and the contact with the touch-sensitive display. If the step to do and the sensed contact correspond to moving the image to a predetermined position on the touch-sensitive display, the step to move the device to the user interface unlocked state and the sensed contact to the predetermined position. If it does not correspond to moving the image, it includes a step of holding the device in the user interface locked state.</p><p> In some embodiments, the method of controlling a device with a touch-sensitive display senses the step of displaying an image on the touch-sensitive display while the device is in the user interface locked state and the contact with the touch-sensitive display. If the step to be performed and the sensed contact correspond to moving the image on the touch-sensitive display according to a predetermined path on the touch-sensitive display, the step to move the device to the user interface unlocked state and the sensed contact are , Includes a step of holding the device in a user interface locked state if it does not correspond to moving the image according to a predetermined path.</p><p> In some embodiments, the method of controlling the device with the touch-sensitive display is to display the first and second images on the touch-sensitive display while the device is in the user interface locked state, and touch-sensitive. A step of sensing contact with the display, and a step of transitioning the device to the first active state corresponding to the first image, if the sensed contact corresponds to a given gesture for the first image. If the contact made corresponds to a predetermined gesture for the second image, it includes a step of transitioning the device to a second active state different from the first active state.</p><p> The methods described above include a graphical user interface (GUI), one or more processors, memory and one or more modules, and a set of programs or instructions stored in memory to perform these methods. It can be performed by a portable electronic device having a touch-sensitive display provided. In some embodiments, the portable electronic device provides multiple functions, including wireless communication.</p><p> Computer program products configured to be executed by one or more processors may include instructions for performing the methods described above.</p><p> In order to better understand the above-described embodiments and additional embodiments of the present invention, the following embodiments will be described with the following drawings showing the corresponding parts of the same reference numerals throughout the figure.</p>
Hereinafter, embodiments will be described in detail, and examples thereof are shown in the accompanying drawings. In the following detailed description, many specific detailed description will be given in order to fully understand the present invention. However, it will be apparent to those skilled in the art that the present invention can be practiced without these particular detailed description. Other examples do not elaborate on well-known methods, procedures, components, and circuits so as not to unnecessarily obscure aspects of the embodiment.
FIG. 1 is a diagram showing a portable electronic device according to some embodiments of the present invention. The device 100 includes a memory 102, a memory controller 104, one or more processing units (CPU) 106, a peripheral interface 108, an RF circuit 112, an audio circuit 114, a speaker 116, a microphone 118, and an input / output (I / O) sub. Includes system 120, touch screen 126, other inputs or controls 128, and external port 148. These components communicate through one or more communication buses or signal lines 110. Device 100 includes, but is not limited to, handheld computers, tablet computers, mobile phones, media players, personal digital assistants (PDAs), or similar combinations of two or more of these items. It may be any portable electronic device including. It should be understood that the device 100 is only one example of the portable electronic device 100, and that the device 100 can have more or fewer components than those shown, or components of different configurations. The various components shown in FIG. 1 can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing circuits and / or application-specific integrated circuits.
The memory 102 can include a high speed random access memory and may further include one or more non-volatile memory devices such as magnetic disk storage devices, flash memory devices, or other non-volatile solid-state memory devices. .. In some embodiments, the memory 102 is a storage device remotely located from one or more processors 106, such as an RF circuit 112 or an external port 148, and the Internet, an intranet (s), a local area network (s). Further includes storage devices attached to communication networks (not shown) such as LANs), wide local area networks (WLANs), storage area networks (SANs), or networks accessed via any suitable combination thereof. be able to. Access to memory 102 by other components of device 100, such as CPU 106 and peripheral interface 108, can be controlled by memory controller 104.
The peripheral interface 108 couples the input / output peripheral device of the device to the CPU 106 and the memory 102. One or more processors 106 execute various software programs and / or instruction sets stored in memory 102 to perform various functions of device 100 and process data.
In some embodiments, the peripheral interface 108, CPU 106, and memory controller 104 can be mounted on a single chip, such as chip 111. In some other embodiments, they can also be mounted on separate chips.
The RF (radio frequency) circuit 112 transmits and receives electromagnetic waves. The RF circuit 112 converts between an electric signal and an electromagnetic wave, and communicates with a communication network and other communication devices via the electromagnetic wave. The RF circuit 112 is, but is 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 identification module ( It can include well-known circuits for performing these functions, including SIM) cards, memory, and the like. RF circuits 112 include networks such as the Internet, intranets, and / or cellular telephone networks, wireless local area networks (LANs) and / or urban networks (MANs), sometimes referred to as the Worldwide Web (WWW), and wireless communications. Can communicate with other devices. Wireless communication is not limited to the following, but is limited to wide area system for mobile communication (GSM), data-enhanced GSM environment (EDGE), wideband code division multiple access (W-CDMA), code division multiple access (CDMA). , Time division multiple access (TDMA), Bluetooth, Wireless fidelity (Wi-Fi) (such as IEEE802.11a, IEEE802.11b, IEEE802.11g and / or IEEE802.11n), Voice over Internet Protocol (VoIP), Wi- Any, including any other suitable communication protocol, including protocols for MAX, email, instant messaging, and / or short message services (SMS), or communication protocols that have not yet been developed as of the filing date of this specification. Multiple communication standards, communication protocols, and communication technologies can be used.
The audio circuit 114, the speaker 116, and the microphone 118 provide an audio interface between the user and the device 100. The audio circuit 114 receives audio data from the peripheral interface 108, converts the audio data into an electric signal, and transmits the electric signal to the speaker 106. Speakers convert electrical signals into sound waves that humans can hear. The audio circuit 114 also receives an electrical signal converted from sound waves by the microphone 116. The audio circuit 114 converts this electrical signal into audio data and transmits the audio data to the peripheral interface 108 for processing. This audio data can be retrieved from and / or transmitted to the memory 102 and / or the RF circuit 112 by the peripheral interface 108. In some embodiments, the audio circuit 114 also includes a headset jack (not shown). This headset jack is for audio circuits 114 and removable audio inputs / outputs such as output-only headphones or headsets with both output (one-ear or binaural headphones) and input (microphone). Provides an interface to and from peripheral devices.
The I / O subsystem 120 provides an interface between an input / output peripheral on the device 100, such as a touch screen 126 and other input / control device 128, and a peripheral interface 108. The I / O subsystem 120 includes a touch screen controller 122 and one or more input controllers 124 for other inputs or controls. One or more input controllers 124 send and receive electrical signals to and from other inputs or controller 128. Other input / control devices 128 may include physical buttons (push buttons, rocker buttons, etc.), dials, slider switches, sticks, and the like.
The touch screen 126 provides both an output interface and an input interface between the device and the user. The touch screen controller 122 sends and receives electrical signals to and from the touch screen 126. The touch screen 126 provides the user with a visual output. This visual output can include text, graphics, video, and any combination thereof. Some or all of the visual output can correspond to user interface objects, further details of which are described below.
The touch screen 126 also accepts input from the user based on tactile and / or tactile contact. The touch screen 126 forms a touch-sensitive surface that accepts user input. The touch screen 126 and the touch screen controller 122 sense and sense a contact (and any movement or interruption due to the contact) on the touch screen 126 (along with any associated module and / or instruction set in memory 102). Converts contact into communication with a user interface object, such as one or more softkeys displayed on the touch screen. In an exemplary embodiment, the point of contact between the touch screen 126 and the user corresponds to one or more fingers of the user. The touch screen 126 can use LCD (Liquid Crystal Display) technology or LPD (Luminescent Polymer Display) technology, but other display technologies can also be used in other embodiments. The touch screen 126 and the touch screen controller 122 are, but are not limited to, capacitive, resistive, infrared, and surface acoustic wave technologies, and one or more with other proximity sensor arrays, or the touch screen 126. Any plurality of touch sensitivity techniques, including other factors for determining the above contact points, can be used to sense contact and any movement or interruption due to contact. Touch-sensitive displays include the following U.S. Pat. Nos. 6,323,846 (Westerman et al.), U.S. Pat. No. 6,570,557 (Westerman et al.), And / or U.S. Pat. No. 6,677, It can be similar to the multi-touch sensitive tablet described in Westerman and / or US Patent Publication No. 2002/0015024 A1, and each of these patents is incorporated herein by reference. However, while the touch screen 126 displays the visual output from the mobile device, the touch-sensitive tablet does not. The touch screen 126 can have resolutions well in excess of 100 dpi. In an exemplary embodiment, the touch screen 126 can have a resolution of about 168 dpi. The user can touch the touch screen 126 with any suitable object or accessory such as a stylus pen or finger.
In some embodiments, the device 100 may include, in addition to the touch screen, a touch pad (not shown) for activating or stopping a particular function. In some embodiments, the touchpad is a touch-sensitive area of the device and, unlike a touch screen, does not display a visual output. The touchpad can be a touch-sensitive surface separate from the touch screen 126, or can be an extension of the touch-sensitive surface formed by the touch screen 126.
Equipment 100 also includes a power system 130 for powering various components. This power system 130 includes a power management system, one or more power sources (batteries, alternating current (AC), etc.), charging systems, power supply anomaly detection circuits, power converters or converters, light emitting diodes (LEDs), etc. It can include a power status indicator and any other component related to the generation, management, and distribution of power for portable devices.
In some embodiments, the software components are operating system 132, communication module (or instruction set) 134, contact / operation module (or instruction set) 138, graphic module (or instruction set) 140, user interface state module (or instruction set). Or instruction set) 144, and one or more applications (or instruction set) 146.
Operating system 132 (for example, embedded operating systems such as Darwin, RTXC, LINUX, UNIX, OS X, WINDOWS, or VxWorks) controls common system tasks (such as memory management, storage control, power management, etc.). Includes various software components and / or drivers for managing and facilitating communication between various hardware and software components.
The communication module 134 facilitates communication with other devices through one or more external ports 148 and also includes various software components for processing the data received by the RF circuit 112 and / or the external port 148. .. External ports 148 (such as Universal Serial Bus (USB), FireWIRE, etc.) are designed to connect directly to other devices or indirectly through a network (eg, Internet, WiFi, etc.).
The contact / operation module 138 senses contact with the touch screen 126 together with the touch screen controller 122. The contact / action module 138 determines if a contact has occurred, if there is movement due to the contact, tracks the movement across the touch screen, and if the contact is interrupted (contact is Includes various software components for performing various actions related to sensing contact with the touch screen 122, such as determining whether it has finished). The step of determining the movement of the contact point may include the step of determining the speed (magnitude), velocity (magnitude and direction), and / or acceleration (including magnitude and / or direction) of the contact point. it can. In some embodiments, the contact / operation module 126 and the touch screen controller 122 also sense contact on the touchpad.
The graphics module 140 includes various known software components for rendering and displaying graphics on the touch screen 126. The term "graphic" may be displayed to the user, including, but not limited to, text, web pages, icons (such as user interface objects including softkeys), digital images, videos, animations, etc. Note that it contains any object that can be.
In some embodiments, the graphic module 140 includes a light intensity module 142. The light intensity module 142 controls the light intensity of a graphical object such as a user interface object displayed on the touch screen 126. The step of controlling the light intensity can include a step of increasing or decreasing the light intensity of the graphical object. In some embodiments, this increase or decrease can follow a predetermined function.
User Interface State Module 144 controls the state of the user interface of device 100. The state module 144 of this user interface can include a lock module 150 and an unlock module 152. The lock module senses that any one or more conditions have been met, shifts the device 100 to the user interface locked state, and shifts the device 100 to the locked state. The unlock module senses that any one or more conditions have been met, shifts the device to the user interface unlocked state, and shifts the device 100 to the unlocked state. Further details regarding the state of the user interface will be described below.
One or more applications 130 are, but not limited to, browsers, address books, contact lists, email, instant messaging, word processing, keyboard emulation, widgets, JAVA-enabled applications, encryption, digital rights. Management, voice recognition, voice duplication, location features (such as those provided by the Global Positioning System (GPS)), recorded music stored in the form of one or more files (such as MP3 or AAC files). It can include any application installed on the device 100, including a music player (to play) and the like.
In some embodiments, device 100 may include the functionality of an MP3 player such as an iPod (trademark of Apple Computer). Device 100 can therefore include a 36-pin connector compatible with the iPod. In some embodiments, the device 100 can include one or more optional optical sensors (not shown) such as CMOS or CCD image sensors used in imaging applications.
In some embodiments, the device 100 is a device in which the operation of a predetermined set of functions of the device is performed only through the touch screen 126 and, if included in the device 100, a touch pad. By using the touch screen and touchpad as the primary input / control devices to operate the device 100, it is possible to reduce the number of physical input / control devices (push buttons, dials, etc.) in the device 100. it can. In one embodiment, the device 100 includes a touch screen 126, a touchpad, a push button for turning the device on and off, a push button for locking the device, a rocker button for volume adjustment, and a slider for switching the characteristics of the ringer. Includes switch. A push button can be used to power on / off a device by pressing it down and holding it down for a given time interval, or by pushing it down for a given amount of time. It can be used to lock the device by releasing the button before the interval elapses. In an alternative embodiment, device 100 can accept language input via microphone 118 to activate or stop any function.
A given set of features, performed only via the touch screen and touch pad, includes navigation between user interfaces. In some embodiments, when the user touches the touchpad, the touchpad navigates the device 100 to the main, home, or root menu from any user interface that can be displayed on the device 100. In such an embodiment, the touchpad can be referred to as a "menu button". In some other embodiments, this menu button can be a physical push button or other physical input / control device instead of a touchpad.
User interface state The device 100 can have a plurality of user interface states. The state of the user interface is the state when the device 100 responds to the user input by a predetermined method. In some embodiments, the state of the plurality of user interfaces includes a user interface locked state and a user interface unlocked state. In some embodiments, the state of the plurality of user interfaces includes a state for a plurality of applications.
In the user interface locked state (hereinafter referred to as "locked state"), the device 100 is powered on and can be operated, but almost ignores user input, if not all. That is, the device 100 takes no action in response to the user input, and / or the device 100 is prevented from performing a predetermined set of actions in response to the user input. A given set of actions can include navigation between user interfaces and activation or stopping of a given set of features. This locked state can be used to prevent unintentional or improper use of the device 100, or activation or stop of functions in the device 100. When the device 100 is in the locked state, it can be indicated that the device 100 is locked. In some embodiments, the locked device 100 includes an input corresponding to an attempt to move the device 100 to a user interface unlocked state, or an input corresponding to turning off the device 100. Can respond to a limited set of user inputs. In other words, the locked device 100 responds to user input in response to an attempt to move device 100 to a user interface unlocked state, or to user input that powers off device 100. It will not respond to user input corresponding to attempts to navigate between user interfaces. Even if the device 100 ignores the user input, the device 100 may also provide the user with sensory feedback (such as visual, audio, or vibrational feedback) upon sensing the input to indicate that the input is ignored. Please understand that you can.
In an embodiment where the device 100 includes a touch screen 126, while the device 100 is locked, navigation between user interfaces, etc., in response to contact with the touch screen 126 when the device 100 is locked, etc. The predetermined operation set of is not performed. In other words, the touch screen is locked when the contact is ignored by the locked device 100. However, the locked device 100 can still respond to a limited type of contact with the touch screen 126. This limited type includes contacts defined by the device 100 to accommodate attempts to move the device 100 into a user interface unlocked state.
In the user interface unlocked state (hereinafter "unlocked state"), the device 100 is in its normal operating state and senses and responds to user input corresponding to communication with the user interface. The device 100 in the unlocked state can be referred to as the unlocked device 100. The unlocking device 100 senses and responds to user inputs for navigating between user interfaces, entering data, and activating or stopping functions. In an embodiment where the device 100 includes a touch screen 126, the unlock device 100 senses and responds to a contact corresponding to navigation between user interfaces, data entry, and activation or stop of a function via the touch screen 126. To do.
Unlocking equipment through gestures FIG. 2 is a flow chart showing a process 200 for shifting the device according to some embodiments of the present invention to the user interface unlocked state. As used herein, transitioning from one state to another means that processing proceeds from one state to another. This process can be instantaneous, near-instantaneous, gradual, or any suitable speed, as the user perceives. When the process starts, a device independent of the user, such as device 100 (FIG. 1), automatically controls the progress of this process, or the user can control it. The processing flow 200 described below contains many operations that appear to occur in a particular order, but these operations can include more or less operations, and these operations It is clear that it can be run continuously or in parallel (eg using a parallel processor or a multithreaded environment).
The device is set to the locked state (202). When any one or more lock conditions are met, the device can be set to the locked state (ie, transition completely from any other state to the locked state). This locking condition can include an event such as the elapse of a predetermined inactivity, a rush into an active call, or a power-on of the device. This locking condition can also include user intervention, i.e., the user locking the device by predetermined user input. In some embodiments, the user can specify an event that acts as a lock condition. For example, the user can configure the device to transition to the locked state when a predetermined inactivity time elapses rather than when the device is turned on.
In some embodiments, the locked device displays on the touch screen one or more visual cues about the unlock action that the user can perform to unlock the device (204). This (s) visual cues provide the user with hints or advice on unlocking actions. This visual signal can be text, graphic, or any combination thereof. In some embodiments, this visual signal is displayed when a particular event occurs while the device is locked. This particular event that triggers the display of a visual signal can include an incoming call, an incoming message, or any other event that requires the user's response. In some embodiments, this visual signal also causes the user to communicate using menu buttons, the user to touch a locked touch screen, and / or the user to any other input / control device. It is displayed at the time of specific user input such as when communicating using. When not displaying visual cues, the locked device either turns off the touch screen (which saves power) or screen saver or (battery charge, date and time, network strength, etc.) ) Other objects such as information of interest to the user can be displayed on the touch screen.
Unlocking actions include contact with the touch screen. In some embodiments, the unlock action is a predetermined gesture performed on the touch screen. Gestures as used herein are movements of objects / accessories that come into contact with the touch screen. For example, this given gesture is a contact at the left edge of the touch screen (to initialize the gesture), a movement that moves the contact point horizontally to the opposite edge while maintaining continuous contact with the touch screen, and It can include a break in contact at the opposite end (to end the gesture).
While the touch screen is locked, the user can initiate contact with the touch screen, i.e. touch the touch screen (206). For convenience of description, contact with the touch screen in process 200 and another embodiment described below will be described as being performed by the user with one or more fingers and at least one hand. However, it should be understood that this contact can be made using any suitable object or accessory such as a stylus pen, finger. This contact is one or more taps on the touch screen while maintaining continuous contact with the touch screen, movement of the contact point while maintaining continuous contact, interruption of contact, or Any combination of these can be included.
The device senses contact with the touch screen (208). If this contact does not correspond to an attempt to perform an unlock action, or if this contact corresponds to a user failing or aborting an attempt to perform an unlock action (210-No), the device. Remains locked (212). For example, the unlock action is the movement of the contact point horizontally across the touch screen while maintaining lasting contact with the touch screen, and the perceived contact is a series of random taps on the touch screen. If so, the device remains locked because this contact does not correspond to an unlock action.
If the contact corresponds to the successful execution of the unlock action, that is, if the user successfully executes the unlock action (210-yes), the device transitions to the unlocked state (214). For example, an unlock action is a horizontal movement of a contact point across the touch screen while maintaining sustained contact with the touch screen, and the perceived contact is horizontal with sustained contact. If it is moving, the device transitions to the unlocked state.
In some embodiments, upon detecting any contact with the touch screen, the device begins the process of transitioning to the unlocked state, the contact does not correspond to the unlock action, or the unlock action fails / cancels. As soon as the device determines that it is a thing, the transition is stopped. For example, if the unlock action is a given gesture, the device can initiate the process of transitioning to the unlocked state as soon as it senses the first contact by the gesture, and continues to transition as the gesture is performed. If the user aborts the gesture before the gesture is complete, the device aborts the transition and remains locked. When the gesture is completed, the device completes the transition to the unlocked state and becomes the unlocked state. As another example, if the unlock action is a movement that moves the contact point horizontally across the touch screen while maintaining lasting contact with the touch screen, then a single tap on the touch screen may result. The device starts the state transition process as soon as it senses the tap, but at the same time, it recognizes that this tap is just a tap and does not correspond to the unlock action, so the process is stopped immediately afterwards.
While the device is unlocked, the device may display on the touch screen a user interface object corresponding to one or more functions of the device and / or information of interest to the user. User interface objects are objects that make up the user interface of a device, and are not limited in meaning, but are text, images, icons, softkeys (or "virtual buttons"), pull-down menus, radio buttons, and checks. It can contain boxes, selectable lists, and so on. The displayed user interface objects can include non-interactive objects that convey information or contribute to the look and feel of the user interface, interactive objects that the user can communicate with, or any combination thereof. .. The user can communicate with the user interface object by touching the touch screen at one or more touch screen positions corresponding to the interactive object that the user wants to communicate with. The device senses the contact and responds to the sensed contact by performing a (single) action that corresponds to the communication with the (single) interactive object.
The user can still touch the touch screen while the device is locked. However, the locked device cannot perform a given set of actions in response to any sensed contact until the device is unlocked. The prohibited set of actions can include navigating between user interfaces and entering data by the user.
While the device is locked, the device may display one or more visual cues about the unlock action as described above. In some embodiments, the device can also display an unlocked image with a visual signal. An unlocked image is a graphical and interactive user interface object that the user communicates with to unlock the device. In other words, the unlock action is performed on the unlocked image. In some embodiments, the step of performing an unlock action on an image comprises dragging the unlocked image in a predetermined manner and moving the unlocked image across the touch screen. In some embodiments, if the unlock action is not complete, the GUI display moves backwards towards the locked state by gradually returning the unlocked image to the locked state position. It can be shown that it is.
In some embodiments, in addition to visual feedback, the electronics provide non-visual feedback to indicate progress towards the completion of the unlock action. In some embodiments, in addition to visual feedback, the electronics provide non-visual feedback to indicate the completion of the unlock action. Additional feedback can include audible feedback (eg, (single) sound) or physical feedback (eg, (single) vibration).
FIG. 3 is a flow chart showing a process 300 for shifting the device to the user interface unlocked state by using the unlocked image according to some embodiments of the present invention. Process 300 is similar to Process 200 (FIG. 2), with an unlocked image displayed with a visual signal. The unlock action in process 300 is performed on the unlocked image, that is, the unlocking action includes communication with the unlocked image. The processing flow 300 described below contains many operations that appear to occur in a particular order, but these operations can include more or less operations, and they It is clear that these operations can be performed continuously or in parallel (eg, using a parallel processor or multithreaded environment).
The device is locked when the lock condition is met, as in operation 202 (FIG. 2) (302). An unlocked image and a visual signal about the unlocking action using this unlocked image are displayed (304). The operation 304 is the same as the operation 204 (FIG. 2) except that the unlock image is displayed in the operation 304 in addition to the visual signal.
As mentioned above, the unlock action includes communication with the unlock image. In some embodiments, the unlock action involves the user making a predetermined gesture on the unlocked image. In some embodiments, the gesture comprises dragging the unlocked image onto a position on the touch screen that meets one or more predetermined unlocking criteria. In other words, the user touches the touch screen at a position corresponding to the unlocked image, then makes a predetermined gesture while maintaining continuous contact with the touch screen, and is in a position that meets a predetermined unlock criterion. You will drag the image. In some embodiments, this unlocking action is completed by interrupting contact with the touch screen (and thus releasing the unlocked image) upon completion of a given gesture.
A position that meets one or more predetermined unlock criteria is simply a position on the touch screen that is predetermined as the position where the unlocked image is dragged to unlock the device. This (s) position can be narrow or wide and can be one or more specific positions on the touch screen, one or more areas on the touch screen, or any combination thereof. it can. For example, this position can be defined as a particular marked position, an area at each of the four corners of the touch screen, or one quadrant of the touch screen.
In some embodiments, the communication comprises the step of dragging the unlocked image into place on the touch screen. For example, an unlock action can include the step of dragging an unlocked image from one corner of the touch screen to another corner of the touch screen. As another example, the unlock action can include the step of dragging the unlock image from one edge of the touch screen to the other edge. The emphasis here is on the final destination (and finger) of the unlocked image. Thus, the user can drag the unlocked image from its initial position along any desired path. The device is unlocked as long as the unlocked image reaches a predetermined position and is released at that position. This predetermined position can be narrow or wide as described above, with one or more specific positions on the touch screen, one or more areas on the touch screen, or any combination thereof. Please understand that you can.
In some other embodiments, this unlocking action involves dragging the unlocked image along a predetermined path. For example, this unlocking action can include dragging the unlocked image clockwise from one of the corners along the perimeter of the touch screen (the path that exists around the touch screen) to its original position. As another example, this unlocking action can include the step of dragging the unlocked image from one end of the touch screen to the other end in a straight line. The emphasis here is on the path that the unlocked image (and finger) moves along. Since the emphasis is placed on the path, the final position where the unlocked image is moved can be broadly defined. For example, this unlocking action can be to drag the unlocked image from its initial position along a predetermined path to any spot within a predetermined area on the touch screen. This predetermined path can include one or more straight lines, or winding lines.
The user touches the touch screen as in operation 206 (Figure 2) (306). The device senses contact with the touch screen as in operation 208 (Figure 2) (308). If the contact does not correspond to the successful execution of the unlock action on the image (310-No), the device remains locked. If the contact corresponds to the successful execution of the unlock action on the image (310-yes), the device is unlocked (314).
4A to 4B are diagrams showing GUI displays of devices in a user interface locked state according to some embodiments of the present invention. In FIG. 4A, the device 400 includes a touch screen 408 and a menu button 410. The device 400 is locked and the touch screen 408 displays an unlocked image 402 and a visual signal. The illustrated visual cues show channel 404, which indicates the path of gesture / movement that the unlock image 402 follows as it is dragged, and 1 or that, which indicates the direction of gesture / movement, as well as the groove that follows when the slider switch moves. Includes the above arrow 406. The end of channel 404 (in FIGS. 4A-4B and 5A-5D, the "end" of the channel is the right end) also serves as a predetermined position to which the unlocked image 402 is dragged. The unlocked image 402 can also include an arrow to further remind the user of the direction of the gesture / movement. As mentioned above, visual cues and unlocked images can be used during events that require user response (such as incoming or incoming messages) or when the user presses menu button 410 (while the device is locked). Displayed by device 400 during user intervention (such as).
In some embodiments, the arrows in arrow 406 and unlocked image 402 can be animated. For example, the arrow in the unlocked image 402 can be shown and hidden in a pulse-like manner, and the arrow 406 emanates from one end of the channel 406 in synchronization with the pulse of the arrow in the unlocked image 402. Can be done. As shown in FIG. 4B, the arrow 406 can be made to move along channel 404 and disappear when it moves to the end of channel 404.
The visual cues shown in FIGS. 4A and 4B indicate that this unlocking action is the horizontal movement of the finger along channel 404 from the origin of channel 404 where the unlock image is first located to the end of channel 404. Remind the user that it is a given gesture, including (and moving the contact point in this way). However, the visual cues shown in FIGS. 4A-4B are merely exemplary, with more or less visual cues, or other visual cues. Please understand that it can be used. The content of the visual cues can be based on the details of the unlock action.
5A-5D show GUI displays of the device at various points of operation relating to unlock action gestures according to some embodiments of the present invention. In FIG. 5A, a user represented by a hand and a finger 502 (not shown to scale) initiates an unlock action by touching the touch screen 408 of the device 400 with the user's finger 502. In some embodiments, the touch screen 408 is initially in sleep mode and / or dark state, and the screen 408 displays an unlocked image 402 when touched. The user first touches the touch screen 408 at the position corresponding to the unlocked image 402 located at the left end of the channel 404. This contact is based on the fact that the device 400 senses a contact either overlapping the unlocked image 402 or in close proximity to the unlocked image 402 and the user 502 is communicating with the unlocked image 402. Determined to be an attempt to unlock the touch screen.
In FIG. 5B, the user is in the process of making a gesture by moving the user's finger in continuous contact with the touch screen 408 in the direction of 504. As a result of this gesture, the unlocked image 402 is dragged along the channel 404. Channel 404 reminds the user that the unlock gesture is a horizontal movement. In some embodiments, the channel 404 points to a predetermined position (the right edge of the channel in FIGS. 5A-5D), and the user drags the unlock image 402 to that position to complete the unlock action, and / Alternatively, channel 404 indicates a predetermined route, and the user drags the unlock image 402 along the route to complete the unlock action.
In Figure 5C, the user has just dragged the unlocked image to the right edge of channel 404. The unlock action is complete when the user releases the unlock image 402 at the right edge of channel 404. The device is unlocked upon completion of the unlock gesture and displays a user interface object related to the standard operation of device 400 on the touch screen 408. FIG. 5D is a diagram showing an example of a user interface object that can be displayed when the device 400 is unlocked. In Figure 5D, device 400 displays menu 506. Menu 506 includes interactive user interface objects for various applications or behaviors. The user can communicate with this user interface object to launch an application or perform an action. However, it should be understood that device 400 may also display additional or alternative user interface objects upon unlocking.
In some embodiments, the unlock image 402 can be used to indicate that the unlock action operation has failed. For example, if the user interrupts contact with the touch screen before the unlocked image reaches the right edge of channel 404, the unlocking action will fail. The device 400 returns the unlock image 402 to the initial position at the left end of the channel 404 and displays it, and if the user selects it, the unlock action can be tried again. In some embodiments, the device returns to sleep if no gesture is performed for a preset amount of time.
In some embodiments, the user touches the touch screen 408 and slightly moves the contact point horizontally along the channel 404, i.e., the device 400 without the user having to move the contact point to the right edge of the channel to the end. Can be unlocked. In some embodiments, the device 400 can be unlocked by the user touching somewhere on the touch screen 408 and moving the contact point horizontally to follow channel 404.
In some embodiments, the lock / unlock function can be applied to a particular application running on the device 400, rather than being applied to the device 400 as a whole. In some embodiments, the unlock gesture moves from one application to another, such as from a telephone application to a music player, and vice versa. The lock / unlock function can include a hold function or a pause function. In some embodiments, when the user migrates from the first application to the second application, the user interface for the second application fades in (ie increases in strength) and the user for the first application The interface can be made to fade out (ie reduce its strength). The fade-in and fade-out can be smoothly performed over a predetermined time interval such as 0.2 seconds, 1 second, or 2 seconds. This predetermined time interval can be subject to unlocked gestures, such as the time it takes for the user to make a gesture.
Display of progress status in the direction that satisfies the user input condition FIG. 6 is a flow chart showing a process 600 for showing a progress state in a direction satisfying the user input condition according to some embodiments of the present invention. The processing flow 600 described below contains many operations that appear to occur in a particular order, but these operations can include more or less operations, and they It is clear that these operations can be performed continuously or in parallel (eg, using a parallel processor or multithreaded environment).
When the electronic device is in the state of the first user interface, the progress state in the direction satisfying the user input condition required for transitioning to the state of the second user interface is detected (602). In some embodiments, the state of the first user interface corresponds to the first application and the state of the second user interface corresponds to the second application. In some embodiments, the state of the first user interface is locked and the state of the second user interface is unlocked.
When the device is in the state of the first user interface, the progress state in the direction to satisfy the condition is shown by shifting the light intensity of one or more user interface objects related to the state of the second user interface. (604). Changes in the light intensity of the user interface object provide the user with sensory feedback on the progress of the transition between the states of the user interface.
In some embodiments, the device provides non-visual feedback in addition to visual feedback to indicate progress in a direction that satisfies the user input condition. Additional feedback can also include audible feedback (eg, (single) sound) or physical feedback (eg, (single) vibration).
If the conditions are met, the device transitions to the state of the second user interface (606). In some embodiments, the device provides non-visual feedback in addition to visual feedback to indicate that the user input condition has been met. Additional feedback can also include audible feedback (eg, (single) sound) or physical feedback (eg, (single) vibration).
The light intensity of a user interface object as used herein is the degree to which the object is visually embodied. The light intensity can be measured along a scale between a predetermined minimum value and a predetermined maximum value. In some embodiments, the light intensity can be measured along a logarithmic scale. In some embodiments, the user can perceive this light intensity as an effect (or lack thereof) of transparency added to the user interface object. In some embodiments, the minimum light intensity means that the object is completely invisible (ie, the user cannot perceive the object), and the maximum light intensity means that the object does not have any transparency effect. It means that it is visible (ie, the object is visually fully embodied and perceptible to the user). In some other embodiments, the light intensity is a visual division between the user interface object and the background based on color, color tone, saturation, brightness, contrast, transparency, and any combination thereof. be able to.
In some embodiments, the light intensity of the user interface object displayed in the state of the second user interface increases smoothly. Smooth means that a transition time longer than a predetermined threshold, such as 0.2 seconds, 1 second, or 2 seconds, can be included. The transition speed of the light intensity can be any predetermined speed.
In some embodiments, the display of progress in the direction in which the user input condition is completed is a function of satisfying the user's condition. For example, in the case of transition to the unlocked state, the display of the progress status in the direction of completion is a function of the operation related to the unlocking action of the user. In the case of a linear function, if the unlock action is 10% complete, the progress status display indicates 10% completion, if the unlock action is 50% complete, the progress status display indicates 50% completion, and so on. It will be shown until the action is 100% complete, at which point the transition to the unlocked state will occur. Similarly, for a linear function, if the unlock action is 10% complete, the light intensity transition from the initial value to the final value is 10% complete, and if the unlock action is 50% complete, it is 50% complete. Etc. are shown until the unlock action is 100% complete, at which point the light intensity becomes its final value. In some embodiments, the user will be able to perceive the transition of light intensity as the user interface object fades in when the unlock action is performed. It should be understood that this function does not have to be linear and other functions can be used, which will be described in more detail below in connection with FIGS. 8A-8C.
When the user input condition includes a predetermined gesture, the display of the progress status of the gesture can be defined from the viewpoint of how much the gesture is completed and how much the gesture remains. For example, if a gesture involves moving a finger horizontally from one edge of the screen to the other, you can define this progress display in terms of the distance between the two edges. This is because the remaining distance objectively measures how much more finger the user needs to move to complete the gesture.
If the user input condition includes a step of dragging the image to a predetermined position, this in terms of the distance between the initial position of the image and the predetermined position where the image should be dragged to complete the input condition. You can define a display of progress.
If the user input condition includes a step of dragging the image along a predetermined path, the display of this progress can be defined in terms of the length of the predetermined path.
7A-7D show the GUI display of the device that shifts the light intensity of the user interface object at the same time as the transition from the state of the first user interface to the state of the second user interface according to some embodiments of the present invention. It is a figure which shows. In Figure 7A, device 700 is locked and has just received an incoming call. The device 700 displays a prompt 706 for notifying the user of the incoming call on the touch screen 714 to the user. The device also displays an unlock image 702 and channel 704, which allows the user to unlock the device 700 to accept or reject the incoming call. The user initiates the unlock action by touching the touch screen with the finger 710 on the unlock image 702.
In FIG. 7B, the user is moving along channel 704 and dragging the unlocked image 702 in the direction of 712. As the user drags the unlocked image, a set of virtual buttons 708 appears, increasing the light intensity. Virtual buttons 708 are outlined with dotted lines, indicating that they are not yet at their final light intensity level. The virtual button 708 is associated with prompt 706, and the virtual buttons shown in FIGS. 7B-7D allow the user to reject or accept the incoming call. However, the user cannot communicate with the virtual button 708 until the device is unlocked and the virtual button reaches its final light intensity. In FIG. 7C, the user further moves along channel 704 and drags the unlocked image 702 in the direction of 712. The virtual button 708 has even higher light intensity compared to the light intensity in FIG. 7B, as indicated by different types of dotted contours. The increase in light intensity indicates to the user the progress towards the completion of the unlock action.
In FIG. 7D, the user completes the unlock action by dragging the unlocked image to the right edge of channel 704 and releasing the unlocked image 702. The device 700 shifts to the unlocked state. The unlocked image 702 and channel 704 have disappeared from the display, and the virtual button 708 has reached the final light intensity level of that button, as outlined by the solid line. The user can now communicate with the virtual button 708 and accept or reject incoming calls.
As described above in connection with FIGS. 5A-5D, if the unlock action fails due to the user releasing the unlocked image early, the unlocked image can return to its initial position. In some embodiments, the light intensity of the virtual button 708 or other user interface object, which increases in light intensity as the unlock action is performed, causes the unlocked image to return to its initial position and at the same time its light intensity. The strength can be smoothly reduced to its initial level.
8A-8C are graphs showing light intensity as a function of completion of user input conditions according to some embodiments of the present invention. In FIG. 8A, the light intensity is a linear function of the completion of the user input condition. At 0% completion, the light intensity becomes the initial value (in this case, the initial value becomes 0). As the percentage of completion increases, the light intensity increases linearly with the percentage of completion until the final value of 100% completion is reached.
In FIG. 8B, the light intensity is a non-linear function of the completion of the user input condition. At 0% completion, the light intensity becomes the initial value (in this case, the initial value becomes 0). As the percentage of completion increases, the light intensity initially gradually increases until the final value of 100% completion is reached, but as the percentage of completion increases, the increase becomes steeper.
In Figure 8C, light intensity is another non-linear function of completion of user input conditions. At 0% completion, the light intensity becomes the initial value (in this case, the initial value becomes 0). As the percentage of completion increases, the light intensity initially increases sharply until the final value of 100% completion is reached, but as the percentage of completion increases, the increase slows down. In some embodiments, the light intensity may increase with a logarithmic scale.
In some embodiments, the light intensity may reach its final value before 100% completion of the user input condition (eg, 90% completion).
User interface active state corresponding to an event or application FIG. 9 is a flow chart showing a process 900 for migrating the device to the user interface active state corresponding to one of the plurality of unlocked images according to some embodiments of the present invention. In some embodiments, when the device is locked, the device can run one or more active applications. In addition, the device can continue to receive events such as incoming calls, messages, and voicemail notifications while locked. The device can display multiple unlocked images on the touch screen, each corresponding to an active application or incoming event. By performing an unlock action using one of a plurality of unlocked images, the device is unlocked and the application and / or event corresponding to this unlocked image is displayed. As used herein, the active state of the user interface means that the device is unlocked and the corresponding application or event is displayed to the user on the touch screen. The processing flow 900 described below contains many operations that appear to occur in a particular order, but these operations can include more or less operations. It is clear that these operations can be performed continuously or in parallel (eg, using a parallel processor or multithreaded environment).
The device is locked when certain locking conditions are met (902). The device can run an active application when it is locked and can continue to run this active application while the device is locked. In addition, the device can receive events such as incoming calls, messages, and voicemail notifications while the device is locked.
While the device is locked, the device displays multiple unlocked images, each corresponding to an active application running or an event received (904). In some embodiments, the device also displays a visual signal about the unlock action for each unlocked image. The device may display additional unlock images and visual cues when it receives additional events. The user touches the touch screen (906). The device senses a contact gesture (908). The sensed contact gesture is any of the unlocked images displayed (for example, because this contact is not an attempt to perform an unlock action or is a failed / aborted unlock action). If it does not correspond to the normal unlock action action for one (910-No), the device remains locked (912). If the sensed contact gesture corresponds to a normal unlock action action for one of the displayed unlocked images (910-Yes), the touch screen is unlocked and one of the unlocked images The corresponding running application or event is displayed on the touch screen (914). In other words, if the perceived contact corresponds to a predetermined gesture for the first image, the device transitions to the first active state corresponding to the first image and the perceived contact corresponds to a predetermined gesture for the second image. In response to this gesture, the device will transition to a second active state that corresponds to a second image that is different from the first active state.
When an unlock action is performed on a particular unlocked image, the device will be unlocked and the corresponding event or application will be visible to the user, activated, or run in the foreground instead of running in the background. To do. In addition to unlocking the device, the user interface active state includes the step of prominently displaying a running application or incoming event corresponding to a particular unlocked image communicated by the user on the touch screen. Therefore, unlocking with the first unlocked image (when multiple unlocked images are displayed) shifts the device to the first user interface active state, in which the device is unlocked and the first The application / event corresponding to the unlocked image of 1 will be displayed prominently. Unlocking with the second image shifts the device to the second user interface active state, where the device is unlocked and the application / event corresponding to the second unlocked image is prominently displayed. Will be done.
In some embodiments, the device can prioritize which unlocked image to display. The device can display a subset of the corresponding unlocked images on the touch screen at once. The device can determine which subset to display based on one or more predetermined criteria. For example, the device can only display unlocked images that correspond to the latest events and / or running applications. As another example, the device may only display the unlocked image corresponding to the incoming event.
FIG. 10 is a diagram showing a GUI of a device 1000 in a user interface locked state for displaying a plurality of unlocked images according to some embodiments of the present invention. In FIG. 10, the touch screen 1014 of device 1000 is locked. The first unlock image 1002 is displayed with corresponding visual cues such as first channel 1004 and arrow 1006. The second unlock image 1008 is displayed with corresponding visual cues such as second channel 1010 and arrow 1012. The touch screen 1014 can display additional unlocked images and visual cues. The first unlock image 1002 corresponds to the first running application or received event. The second unlock image 1008 corresponds to the second running application or received event. The first and second unlock images and visual cues are similar to the unlock images and visual cues described above with respect to FIGS. 4A and 4B. Arrows 1006 and 1012 can be animated to move from one end to the other of channels 1004 and / or 1010 to indicate the exact direction of a given gesture or movement of the unlocked image.
11A-11F are diagrams showing the GUI display of the device at various time points of the operation relating to the unlock action gesture corresponding to one of the plurality of unlocked images according to some embodiments of the present invention. is there. In FIG. 11A, the user touches the touch screen 1014 with the user's finger 1102 (not shown to scale) at a position corresponding to the second unlock image 1008. The user makes an unlock action gesture by moving the contact point and dragging the second unlock image 1008. Figure 11B shows a snapshot of device 1000 pending unlock action. The second unlock image 1008 moves along channel 1010 in the direction of 1104.
FIG. 11C shows a second unlock image 1008 moved to the end of channel 1010, with respect to the second unlock image 1008 when the user interrupts contact (and releases the second unlock image 1008). The unlock action will be completed. In some embodiments, the unlock action completes when the unlock image 1008 is moved to the edge of channel 1010 and the second unlock image 1008 disappears, regardless of whether the user interrupts contact. Upon completion of the unlock action for the second unlock image 1008, the device brings the user interface object 1106 associated with the application or event corresponding to the second unlock image 1008 on the touch screen, as shown in Figure 11D. indicate. In FIG. 11D, the event corresponding to the second unlock image is an incoming text message event and a prompt for the user to read it.
The user can perform an unlock action gesture on the first unlock image 1002 instead of performing an unlock action on the second unlock image 1108. In FIG. 11E, the user performs an unlock action on the first unlock image 1002 by dragging the first unlock image in the direction of 1104 to the right edge of channel 1004. Upon completion of the unlock action, device 1000 displays the user interface object 1108 associated with the application or event corresponding to the first unlock image 1002. In FIG. 11F, the application corresponding to the first unlocked image is a music player application.
In some embodiments, as described in FIGS. 9 and 11A-11E, the transition to the user interface active state is the transition described above with respect to FIGS. 6, 7A-7D, and 8A-8C. As in the case, simultaneous transitions in the light intensity of the user interface object can be included. At the same time as the transition to the user interface active state, the user interface object associated with the application or event corresponding to the communicated unlock image for the user to unlock the device becomes stronger. For example, the light intensity of the user interface object 1106 associated with the text message prompt of FIG. 11D can be smoothly increased depending on the progress towards the completion of the unlock action for the second unlock image 1008. As another example, smoothly increasing the light intensity of the user interface object 1108 associated with the music player application of FIG. 11F, depending on the progress towards the completion of the unlock action for the first unlock image 1002. Can be done.
For convenience of explanation, the above description has been given with reference to a specific embodiment. However, this exemplary description is not exhaustive or limited to the detailed forms disclosed by the present invention. Many modifications and changes are possible in the light of the above teachings. The above embodiments have been selected and described to best explain the principles of the invention and its practical application, and thus those skilled in the art will appreciate the invention and various embodiments. It will be possible to make various changes to suit the intended use of.
<figref num="1">It is a block diagram which shows the portable electronic device by some embodiments of this invention.</figref><figref num="2">It is a flow diagram which shows the process for shifting the device to the user interface unlocked state by some Embodiments of this invention.</figref><figref num="3">It is a flow diagram which shows the process for shifting the device to the user interface unlocked state by some Embodiments of this invention.</figref><figref num="4A">It is a figure which shows the GUI display of the device in the user interface locked state by some Embodiments of this invention.</figref><figref num="4B">It is a figure which shows the GUI display of the device in the user interface locked state by some Embodiments of this invention.</figref><figref num="5A">As operations relating to gesture unlock action by some embodiments of the present invention is a diagram showing a GUI display of a device at various time points.</figref><figref num="5B">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="5C">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="5D">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="6">It is a flow chart which shows the process which shows the progress state in the direction which satisfies the user input condition by some Embodiments of this invention.</figref><figref num="7A">It is a figure which shows the GUI display of the device which is shifting the light intensity of the user interface object by some Embodiments of this invention.</figref><figref num="7B">It is a figure which shows the GUI display of the device which is shifting the light intensity of the user interface object by some Embodiments of this invention.</figref><figref num="7C">It is a figure which shows the GUI display of the device which is shifting the light intensity of the user interface object by some Embodiments of this invention.</figref><figref num="7D">It is a figure which shows the GUI display of the device which is shifting the light intensity of the user interface object by some Embodiments of this invention.</figref><figref num="8A">It is a graph which shows the light intensity as a function of the completion of the user input condition by some embodiments of this invention.</figref><figref num="8B">It is a graph which shows the light intensity as a function of the completion of the user input condition by some embodiments of this invention.</figref><figref num="8C">It is a graph which shows the light intensity as a function of the completion of the user input condition by some embodiments of this invention.</figref><figref num="9">It is a flow diagram which shows the process for shifting the apparatus to the user interface active state by some Embodiments of this invention.</figref><figref num="10">It is a figure which shows the GUI of the device in the user interface locked state which displays a plurality of unlocked images by some Embodiments of this invention.</figref><figref num="11A">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="11B">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="11C">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="11D">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="11E">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref><figref num="11F">It is a figure which shows the GUI display of the device at various time points of the operation concerning the gesture of the unlock action by some embodiments of this invention.</figref>
Code description
302 Set the device to the user interface locked state by any predetermined method to prevent the device from performing the specified operation set. 304 Unlock image and display visual cues about unlock actions using this image (such as moving the image in place, moving the image along the path, etc.) 306 Touch the touch-sensitive display 308 Detects contact with the touch-sensitive display 310 Does contact correspond to image-based unlock gestures? 312 Keeping the device in the user interface locked state 314 Move the device to the user interface unlocked state User user Device device Yes yes No no
25 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13 Sheet 14 Sheet 15 Sheet 16 Sheet 17 Sheet 18 Sheet 19 Sheet 20 Sheet 21 Sheet 22 Sheet 23 Sheet 24 Sheet 25
Every citation, both waysCites: the store holds 6 of 7
| Document | Relation | Office |
|---|---|---|
| JP09221950A | Cites | Japan |
| JP200391370A | Cites | Japan |
| JP08263215A | Cites | Japan |
| JP2005122271A | Cites | Japan |
| JP200571008A | Cites | Japan |
| JP0965406A | Cites | Japan |
| Catherine Plaisant and Daniel Wallace, ”Touchscreen toggle design”, CHI’92 Proceedings of the SIGCHI conference on Human factors in computing systems, 1992年, p.667-668 | Non-patent | – |
104 members in 11 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 11322549 | United States of America | – | |
| 32254905 | United States of America | A | |
| 32254905 | United States of America | A | |
| 2006061370 | United States of America | W | |
| 2006061370 | United States of America | W | |
| 2005322549 | – | – | – |
| 2006061370 | – | – | – |
| US20050322549 | – | – | – |
| WO2006US61370 | – | – | – |
Members104
| Document | Office | Kind | |
|---|---|---|---|
| US2007150842A1 | United States of America | A1 | |
| AU2006330724A1 | Australia | A1 | |
| WO2007076210A1 | World Intellectual Property Organization (WIPO) | A1 | |
| AU2008100419A4 | Australia | A4 | |
| AU2008100419B4 | Australia | B4 | |
| DE212006000081U1 | Germany | U1 | |
| KR20080079333A | Republic of Korea | A | |
| EP1964022A1 | European Patent Office (EPO) | A1 | |
| DE112006003515T5 | Germany | T5 | |
| CN101371258A | China | A | |
| JP2009521753A | Japan | A | |
| KR20090069344A | Republic of Korea | A | |
| HK1124141A | Hong Kong, China | A | |
| HK1124141A1 | Hong Kong, China | A1 | |
| US2009241072A1 | United States of America | A1 | |
| AU2009100820A4 | Australia | A4 | |
| AU2009100820B4 | Australia | B4 | |
| EP2128782A1 | European Patent Office (EPO) | A1 | |
| AU2006330724B2 | Australia | B2 | |
| US7657849B2 | United States of America | B2 | |
| EP1964022B1 | European Patent Office (EPO) | B1 | |
| AU2010200661A1 | Australia | A1 | |
| AT460710T | Austria | T | |
| ATE460710T1 | Austria | T1 | |
| AU2006330724B8 | Australia | B8 | |
| CN101697181A | China | A | |
| DE602006012876D1 | Germany | D1 | |
| ES2338370T3 | Spain | T3 | |
| KR100993459B1 | Republic of Korea | B1 | |
| CN101371258B | China | B | |
| EP2299381A1 | European Patent Office (EPO) | A1 | |
| AU2011101192A4 | Australia | A4 | |
| AU2011101193A4 | Australia | A4 | |
| US8046721B2 | United States of America | B2 | |
| US2011296356A1 | United States of America | A1 | |
| US2012023458A1 | United States of America | A1 | |
| AU2011101192B4 | Australia | B4 | |
| AU2011101193B4 | Australia | B4 | |
| US8209637B2 | United States of America | B2 | |
| AU2010200661B2 | Australia | B2 | |
| JP2012181847A | Japan | A | |
| US8286103B2 | United States of America | B2 | |
| US2012293438A1 | United States of America | A1 | |
| AU2012254900A1 | Australia | A1 | |
| JP2013127800A | Japan | A | |
| US2013185677A1 | United States of America | A1 | |
| US2013185678A1 | United States of America | A1 | |
| US2013185680A1 | United States of America | A1 | |
| US2013190056A1 | United States of America | A1 | |
| US8527903B2 | United States of America | B2 | |
| JP5298218B2 | Japan | B2 | |
| JP5303688B2 | Japan | B2 | |
| JP5319852B1 | Japan | B1 | |
| JP2013232198A | Japan | A | |
| US8627237B2 | United States of America | B2 | |
| US8640057B2 | United States of America | B2 | |
| JP5457679B2This record | Japan | B2 | |
| US8694923B2 | United States of America | B2 | |
| US8745544B2 | United States of America | B2 | |
| KR20140129372A | Republic of Korea | A | |
| KR20140148500A | Republic of Korea | A | |
| US2015082252A1 | United States of America | A1 | |
| AU2012254900B2 | Australia | B2 | |
| AU2015255304A1 | Australia | A1 | |
| KR101595688B1 | Republic of Korea | B1 | |
| KR101595691B1 | Republic of Korea | B1 | |
| KR101600620B1 | Republic of Korea | B1 | |
| KR20160029152A | Republic of Korea | A | |
| AU2015255304B2 | Australia | B2 | |
| AU2017203078A1 | Australia | A1 | |
| KR101754928B1 | Republic of Korea | B1 | |
| KR20170081736A | Republic of Korea | A | |
| KR20180006513A | Republic of Korea | A | |
| CN101697181B | China | B | |
| KR101819147B1 | Republic of Korea | B1 | |
| EP2128782B1 | European Patent Office (EPO) | B1 | |
| AU2017203078B2 | Australia | B2 | |
| US10078439B2 | United States of America | B2 | |
| AU2018260823A1 | Australia | A1 | |
| US2019026003A1 | United States of America | A1 | |
| EP3435213A1 | European Patent Office (EPO) | A1 | |
| KR101963092B1 | Republic of Korea | B1 | |
| KR20190032649A | Republic of Korea | A | |
| EP3483716A1 | European Patent Office (EPO) | A1 | |
| AU2018260823B2 | Australia | B2 | |
| AU2019283970A1 | Australia | A1 | |
| KR102116840B1 | Republic of Korea | B1 | |
| KR20200062368A | Republic of Korea | A | |
| US10754538B2 | United States of America | B2 | |
| US2020348816A1 | United States of America | A1 | |
| KR102193129B1 | Republic of Korea | B1 | |
| KR20200142126A | Republic of Korea | A | |
| AU2019283970B2 | Australia | B2 | |
| AU2021201814A1 | Australia | A1 | |
| AU2019283970B9 | Australia | B9 | |
| US11086507B2 | United States of America | B2 | |
| US2021342052A1 | United States of America | A1 | |
| AU2021201814B2 | Australia | B2 | |
| KR102426486B1 | Republic of Korea | B1 | |
| AU2022206793A1 | Australia | A1 |
25 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Receipt of annual feesJAPANESE INTERMEDIATE CODE: R250R250 | R250 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| Certificate of patent or registration of utility modelJAPANESE INTERMEDIATE CODE: R150R150 | R150 | |
| First payment of annual fees (during grant procedure)JAPANESE INTERMEDIATE CODE: A61A61 | A61 | |
| Decision of refusalJAPANESE INTERMEDIATE CODE: A02A02 | A02 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 | |
| Written permission of extension of timeJAPANESE INTERMEDIATE CODE: A602A602 | A602 | |
| Notification of resignation of power of attorneyJAPANESE INTERMEDIATE CODE: A7424RD04 | RD04 | |
| Written request for extension of timeJAPANESE INTERMEDIATE CODE: A601A601 | A601 | |
| Notification of appointment of power of attorneyJAPANESE INTERMEDIATE CODE: A7423RD03 | RD03 | |
| Notification of reasons for refusalJAPANESE INTERMEDIATE CODE: A131A131 | A131 | |
| Request for written amendment filedJAPANESE INTERMEDIATE CODE: A523A521 | A521 |
Numbers
- Publication
- 5457679
- Publication, DOCDB
- 5457679
- Publication, EPODOC
- JP5457679B
- Application
- 2008547675
- Application, DOCDB
- 2008547675
- Application, EPODOC
- JP20080547675
Titles2
- Japanese
- アンロック画像上でジェスチャを行うことによる機器のアンロッキング
- English
- Unlocking the device by making a gesture on the unlocked image
Classification
- CPC, 10
- G06F3/04883
- H04M1/67
- G06F3/0488
- G06F21/36
- H04M1/575
- H04M1/663
- H04M2250/22
- G06F3/017
- G06F3/0484
- G06F3/04842
- IPC, 1
- G06F3 048
