US 8,355,698 B2Grant
Unlock screen
Issue Date:2013-01-15
•16 Claims
•15 Drawing Sheets
Abstract
Unlock screen and notification techniques are described. In an implementation, an unlock screen is displayed by a mobile communications device that indicates that one or more keys of the mobile communications device are locked. If an input is detected at the mobile communications device to remove the lock, an animation is displayed that gives an appearance that the unlock screen is a page that is being turned and removing the lock of the one or more keys.
Metadata
Assignee
- Microsoft Corporation
Inventors
- Stephanie E. Teng
- Jinsheng Shi
- Albert Shen
- Ryan M. Haning
- Paula Guntaur
- Michael J. Kruzeniski
Application Information
Application Number:US 12/414,434
Filing Date:2009-03-30
Priority Date:2009-03-30
Art Unit:2617
Classifications
IPC:
H04W12/06
Patent Drawings (15 sheets)
Description
Background
[0001] Mobile communications devices (e.g., wireless phones) have become an integral part of everyday life. For example, a user traditionally used mobile communications devices to place and receive telephone calls when the user was away from a fixed communication device, e.g., a house or office telephone. In some instances, the mobile communications device became the primary device via which the user communicated with other users as the user became accustomed to the convenience and functionality of the device.
[0002] Further, the communication techniques that may be employed using a mobile communications device have increased. For example, users were traditionally limited to telephone calls between mobile communications devices. Advances were then made to provide a variety of other communication techniques, e.g., text messaging and email. However, inclusion of these additional communication techniques on mobile communications devices having traditional form factors may cause these devices to become unwieldy and less suitable for mobile applications. For example, traditional input devices that were employed by these communication techniques may be less suitable when applied by traditional mobile communications devices.
Summary
[0003] Unlock screen and notification techniques are described. In an implementation, an unlock screen is displayed by a mobile communications device that indicates that one or more keys of the mobile communications device are locked. If an input is detected at the mobile communications device to remove the lock, an animation is displayed that gives an appearance that the unlock screen is a page that is being turned and removing the lock of the one or more keys.
[0004] In an implementation, an unlock screen is updated of a mobile communications device to include notifications of events that have occurred since a last time the mobile communications device was locked. If a number of the notifications that are to be output on the unlock screen exceeds a specified number, the notifications are condensed into a single condensed notification to be output via the unlock screen that references a type and number of the notifications.
[0005] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Brief Description of the Drawings
[0006] The detailed description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The use of the same reference numbers in different instances in the description and the figures may indicate similar or identical items.
[0007] FIG. 1 is an illustration of an example implementation of a mobile communications device in accordance with one or more embodiments of devices, features, and systems for mobile communications.
[0008] FIG. 2 illustrates an example implementation in which a gesture is used to unlock an unlock screen of FIG. 1 .
[0009] FIG. 3 illustrates an example implementation in which a mobile communication device of FIG. 2 is unlocked after completion of the gesture.
[0010] FIG. 4 illustrates an example implementation in which the mobile communications device of FIG. 1 is shown as having the unlock screen configured to include a specified image.
[0011] FIG. 5 illustrates an example implementation of the mobile communications device of FIG. 1 as outputting an unlock screen having a clock that illustrates the date and time in this instance.
[0012] FIG. 6 illustrates an example implementation of the mobile communications device of FIG. 1 as outputting a full-screen notification.
[0013] FIG. 7 illustrates an example implementation of the mobile communications device of FIG. 1 as arranging and outputting notifications for display in conjunction with the unlock screen 120.
[0014] FIG. 8 illustrates an example implementation in which a notification is displayed singly as received and then displayed in conjunction with other notifications.
[0015] FIG. 9 illustrates the mobile communications device in an example implementation in which a notification that is assigned a medium priority is output with notifications that are assigned a low priority.
[0016] FIG. 10 illustrates an example implementation in which the mobile communications device 102 includes an emergency contact user interface.
[0017] FIG. 11 depicts a procedure in an example implementation in which an animation is displayed in conjunction with removal of a key lock of a mobile communications device.
[0018] FIG. 12 depicts a procedure in an example implementation in which a clock is displayed.
[0019] FIG. 13 depicts a procedure in an example implementation in which a condense mechanism is employed with notifications.
[0020] FIG. 14 illustrates various components of an example device that can be implemented in various embodiments as any type of a mobile communication device to implement embodiments of devices, features, and systems for mobile communications.
Detailed Description
[0021] Overview
[0022] The use of physical control descriptors (e.g., text, images of an action to be performed, and so on) on a mobile communication device that explain how to unlock a touch screen user interface (UI) may be limiting and tough to decipher. Likewise, conventional gestures that are virtualizations of mechanical switches may also be hard to learn and/or discover.
[0023] In one or more implementations, an unlock screen is described that acts like a piece of paper (e.g., vellum) that is curled up at the corner to unlock a mobile device. The corner may be animated to look like it is blowing in a soft breeze to call attention to the corner. To unlock the mobile device, a gesture may be performed that mimics a physical behavior of turning a page to unlock the mobile communications device. Therefore, in this example a user may readily ascertain how to unlock the mobile communications device without a text description or other physical control descriptor. While the phone is locked, the vellum may be used to partially disguise portions of a user interface (UI) behind it to increase visibility of a clock. For example, the vellum of the UI may be configured to be translucent to allow notifications (e.g., updates and alerts) to be at least partially visible from the underlying UI.
[0024] Additional techniques are also described may also provide a variety of functionality, such as serve as an outlet for user customization, display the time, display incoming communication-related notifications since the last time the device was locked, permit the user to perform emergency functions, secure phone content after certain time (e.g., a PIN lock), permit a device “wipe” if a PIN is entered incorrectly a predetermined number of times, provide an entry point for basic music playback control, provide a repository for unnoticed notifications, display notifications that a user has already seen, and so on, further discussion of which may be found in relation to the following description.
[0025] In the following discussion, a variety of example implementations of a mobile communications device are shown. Additionally, a variety of different functionality that may be employed by the mobile communications device is described for each example, which may be implemented in that example as well as in other described examples. Accordingly, example implementations are illustrated of a few of a variety of contemplated implementations. Further, although a mobile communications device having one or more modules that are configured to provide telephonic functionality are described, a variety of other mobile communications devices are also contemplated, such as dedicated messaging devices, music players, portable game devices, and so on.
[0026] Unlock Screen
[0027] FIG. 1 is an illustration of an example implementation 100 of a mobile communications device 102 in accordance with one or more embodiments of devices, features, and systems for mobile communications. The mobile communications device 102 is illustrated as assuming a plurality of configurations, examples of which include a first configuration 104, a second configuration 106, and a third configuration 108.
[0028] The mobile communications device 102 is further illustrated as including a first housing 110 and a second housing 112 that are connected via a slide 114 such that the first and second housings 110, 112 may move (e.g., slide) in relation to one another. The first housing 110 includes a display device 116 (e.g., a touchscreen) that may be used to output a variety of data, such as a caller identification (ID), information related to text messages as illustrated, email, multimedia messages, Internet browsing, game play, music, video and so on. The second housing 112 is illustrated as including a keyboard 118 that may be used to provide inputs to the mobile communications device 102. Although the keyboard 118 is illustrated as a QWERTY keyboard, a variety of other examples are also contemplated, such as a twelve key numeric pad.
[0029] In the example shown in FIG. 1 , the first and second housings 110, 112 of the mobile communications device 102 are rectangular. For example, a plane defined by an outer surface of the display device 116 may be parallel to a plane of the first housing 110 that approximates a rectangle, which may be the same as or different from the plane defined by the display device 116. In another example, the width and height of the plane taken from the first housing that is parallel to the other surface of the display device 116 are approximately square (e.g., one-to-one so as to be equilateral rectilinear). A variety of other examples are also contemplated.
[0030] In the first configuration 104, the mobile communications device 102 is closed such that the first housing 110 covers the second housing 112. Consequently, the keyboard 118 disposed on the second housing 112 is covered and thus is not available to receive inputs from a user of the mobile communications device 102. In an implementation, telephonic functionality is still available when the mobile communications device 102 is in the first configuration 104, e.g., to receive and answer a telephone call via interaction with the display device 116 or other buttons disposed either of the first and/or second housings 108, 110.
[0031] In the second configuration 106, the first housing 108 is moved (e.g., slid) “away” from the second housing 112 using the slide 114. In this example configuration, a portion of the keys of the keyboard 118 is exposed such that the exposed keys are available to receive inputs from a user. In another implementation, however, use of the keys of the keyboard 116 is restricted until the mobile communications device 106 assumes the open configuration illustrated in the third configuration 108 to help prevent inadvertent inputs. In an implementation, the planes of the first and second housings 110, 112 that are used to define the square form factor are parallel to each other, although other implementations are also contemplated.
[0032] In the third configuration 108, the first housing 108 is moved further “away” from the second housing 112 using the slide 114. In this example configuration, at least a majority of the keys of the keyboard 118 are exposed and are available to receive inputs from a user. Accordingly, the third configuration 108 may be considered an “open” configuration. In the illustrated implementation 100, the display device 116 remains viewable by a user in each configuration, examples of which are shown in the first, second, and third configurations 110, 112, 114.
[0033] The display device 116 is further illustrated as including an unlock screen 120 that once unlocked may reveal an underlying user interface 122, unlock a key lock placed physical and/or displayed keys on the mobile communications device 102, and so on. In the illustrated implementation of FIG. 1 , the first housing 110 is slid away from the second housing 112 to unlock keys of the mobile communication device 102. When the keys are locked, mobile communications device 102 application functionality is not accessible and the device does not respond to keyboard 118 presses.
[0034] In the illustrated implementation 100, the unlock screen 120 is animated in a manner mimicking a page being turned such that the user interface 122 is exposed as the first and second housings 110, 112 are slid away from each other. For example, as shown in the second configuration 106 the unlock screen 120 is partially turned to reveal the user interface 122 underneath. In the third configuration 108 of FIG. 3 , the user interface 122 is completely exposed as the mobile communications device 102 has assumed the “open” configuration and is ready to receive inputs entered via the keyboard 118 and/or display device 116. In an implementation, the unlock screen 120 may mimic a layer of vellum that is partially translucent to reveal portions of the user interface 112 below, e.g., to display notifications and so on as further described in relation to FIG. 5 . The unlock screen 120 may also be unlocked using a gesture, further discussion of which may be found in relation to the following figure.
[0035] FIG. 2 illustrates an example implementation 200 in which a gesture is used to unlock the unlock screen 120 of FIG. 1 . In the illustrated implementation, a first configuration 202 is shown in which the mobile communications device 102 is in a key locked state such that the display device 116 is not configured to receive inputs, e.g., a key press entered via a touchscreen.
[0036] A gesture is then initiated in the second configuration 204 by a user's hand 206. For example, a finger of the user's hand 206 may be used to select a corner 208 of the unlock screen 120, which in this instance is illustrated as an upturned corner of a page. The user's hand 206 (and more particularly the user's finger) may then be used to drag the corner 208 across the display device 116 to mimic turning the page as illustrated in the second configuration 204.
[0037] Thus, a user may activate the animation and unlock sequence on the display device 116 by grabbing a touch target (e.g., the upturned corner of the page) and “dragging” it across the screen as shown in FIG. 2 . The corner of the unlock screen 120 may visually follow the user's finger as it is dragged along the surface of the display device 116, exposing some portion of a UI 122 “underneath” the unlock screen 120, such as a PIN unlock pad if the user is removing a device lock (which is described in further detail below). Thus, the gesture may be used to remove a key lock (i.e., unlock) the mobile communication device 102 and enable interaction with the underlying user interface 122.
[0038] FIG. 3 illustrates an example implementation 300 in which the mobile communication device 102 of FIG. 2 is unlocked after completion of the gesture. Once the finger of the user's hand has crossed a threshold 302 (which in this instance is illustrated as seventy five percent of the way across the display device 116 from the touch target), the unlock screen 120 is removed. If the finger of the user's hand is removed before then, the unlock screen 120 may animate back as shown in the first configuration 202 of FIG. 2 and the key lock remains in place.
[0039] Once the threshold 302 is crossed at any point along the Y-axis by the finger of the user's hand 206 and the user releases the gesture (e.g., lifts the finger off the display device 116), the unlock screen 120 of FIG. 2 may complete animating away by continuing a turn of the page and the key lock is removed thereby exposing the user interface 122. If the user does not release the gesture (e.g., ceases the pan) and moves the finger of the user's hand 206 back toward the left side of the display device 116, the corner animation may follow the finger of the user's hand 206. Thus, a release of the touch target (e.g., the upturned corner of the unlock screen 120) on the left side of the threshold 302 may result in the device remaining locked, similar to not having crossed the threshold.
[0040] The mobile communications device 102 may also keep a timer to track idle time, which may reset each time a user leaves the mobile communications device 102 idle. For example, when mobile communications device 102 is active (not in a locked state), ten seconds of non-interaction may result in dimming of the display device 116. The mobile communications device 102 may then wait a specified amount of time before initiating the unlock screen 120 described previously.
[0041] If the mobile communications device 102 is already locked and the user illuminates the display device 116, the mobile communications device 102 may remain at full brightness for ten seconds before fading to half brightness. After ten or more seconds have elapsed without interaction, a full “key locked” state may be entered in which the display device 116 is turned off, which may be reversed by a user through pressing a hardware key. The timer may be reset if user selects the touch target (e.g., the corner 208 of the unlock screen 120 of FIG. 2 ) and does not begin again until the user is no longer interacting with the mobile communications device 102.
[0042] After entering the “key locked” state, the mobile communications device 102 may preserve a state of an application that is executing on the mobile communications device 102, such as an application that is displayed in the “foreground” of the user interface 122. When the user unlocks the mobile communications device 102, the user may be returned to the state of the application when the mobile communications device 102 was locked. In an implementation, downloads, message sending, music playing and other application processes initiated before the lock state may continue even if the display device 116 is locked. Further, an application may elect to change behavior if the display device 116 is locked, i.e., the unlock screen 120 is being employed. Examples include movie playback and games, which may pause if screen locks, further discussion of which may be found later in the description.
[0043] When a power key 304 is pressed, the mobile communications device 102 may enter a key locked state and turn the display device 116 off. If the mobile communications device 102 is already locked and the mobile communications device 102 receives an incoming phone call, interaction with one or more of the hardware or software keys of the mobile communications device 102 may be used to silence the ringer but does not turn the display device 116 off.
[0044] If the mobile communications device 102 is unlocked when a telephone call is received, a first tap on the power key 304 or interaction with another hardware or displayed key may silence the ringer. The mobile communications device 102 may remain unlocked and the timer restarted for screen timeout and device idle. A second press on the power key 304 may result in locking the mobile communications device 102 and turning the display device 116 off.
[0045] In an implementation, if the user has turned off or reset the mobile communications device 102, the mobile communications device 102 starts in the key locked state if there is a device lock and a PIN is enabled. If not, the mobile communications device 102 proceeds directly to a home screen of the user interface 122 after reboot.
[0046] The key lock and the unlock screen 120 may be utilized in a variety of other instances. For example, if a proximity sensor indicates that the mobile communications device 102 is being held vertically during a telephone call, the display device 116 may be turned off and key lock turned on (i.e., the key locked state is entered) thereby initiating the unlock screen 120. The key lock may turn off if the mobile communications device 102 is turned horizontally again.
[0047] FIG. 4 illustrates an example implementation in which the mobile communications device 102 of FIG. 1 is shown as having the unlock screen 120 configured to include a specified image. In this implementation, the user may elect an image (which may be static or dynamic) to appear on the unlock screen 120. In an implementation, this image appears in the background of the display device 116 and is fully visible if the mobile communications device 102 does not have a notification to output, e.g., low battery level as further detailed below.
[0048] The image may come from a variety of different sources. For example, the user may select from a library of images that are local to the mobile communications device 102, which may be populated with default content, taken by an image capture device that is part of the mobile communications device 102, and so on. A user may also access a web service 406 over a network 408 (e.g., the Internet) to access a library of images 412, such as an online marketplace having wallpapers for sale, and download a particular image.
[0049] In an implementation, a particular image may be specified via a setting that is accessible from a settings screen. For example, the user interface 120 may output a selection screen to select an image from a locally stored gallery of wallpaper or to enter the photo gallery collection. After the user navigates to a gallery and selects an image for use for the wallpaper, the user may be presented with a confirmation screen to preview the image and confirm or cancel the use of the image. The image capture device 120 may resize the image to conform to the display device 116, e.g., crop the image.
[0050] Output of images 404 by the mobile communications device 102 on the unlock screen 120 may also be dynamic. For example, a dynamic image may be selected via a “Use Favorites” section of a settings screen. If the user elects to “Use Favorites” and has images in the Favorites folder, the unlock screen 120 may display the images 404 in succession on the unlock screen 120. In an implementation, when this feature is first selected, a first picture in a favorites folder is started on unlock. Each subsequent rotation takes a next image in the folder. Images may appear when button is pressed and a rotation animation may be employed in response to an input received via a key (e.g., a back key) to click through photos while in the key locked state.
[0051] If the user does not have images selected as favorites, selection of this option may cause the mobile communications device to output instructions to select images to go into the favorites folder before using this option. The mobile communications device 102 may then continue to use the previously selected image (e.g., a default wallpaper). If desired, the user may be given an option to navigate to a photo gallery on the mobile communications device 102 to populate the favorites folder before returning to the settings screen.
[0052] FIG. 5 illustrates an example implementation 500 of the mobile communications device 102 of FIG. 1 as outputting an unlock screen 120 having a clock 502 that illustrates the date and time in this instance. In the illustrated example, the unlock screen 120 may be output by the mobile communications device 102 as monochrome on the display device 116 to maximize visibility without using a backlight, thereby conserving battery resources.
[0053] The unlock screen 120 includes a clock 502 having a time and date, which is displayed in the center of the display device 116 in this example. Time may be updated continuously, regardless of whether display device 116 is turned on or off. This way, the clock remains up-to-date as soon as the display device 116 is turned on.
[0054] When the display device 116 is initiated (i.e., “turned on” or illuminated), the clock to consume a substantial portion of the display device. For example, as illustrated the clock 502 is illustrated as being displayed in the center of the display device. After a specified amount of time, the amount of the display area of the display device 116 consumed by the clock 502 may be reduced, such as by minimizing the clock 502 for display at a corner of the display device 116 as illustrated in the unlock screen 120 of FIG. 4 . In an implementation, the minimized clock may be selected to expand the view in the unlock screen 120.
[0055] The unlock screen 120 also includes silhouettes 504, 506, 508 of notifications in the same places as the notifications are to appear in the user interface 122. In an implementation, the unlock screen 120 is updated as notifications are to be output, e.g., a low battery condition, further discussion of notifications may be found in relation to the notifications section of the description.
[0056] Notifications
[0057] The unlock screen 120 may be leverage to output a variety of different types of notifications. Further, these types of notifications may be assigned a priority that may be used to determine how (and even whether) the notifications are to be output in conjunction with the unlock screen. For example, “high priority” notifications may be output using a “full screen”, i.e., the notification consumes a majority of an available display area of the display device 116. Notifications that have a lesser priority may be managed and output in a manner that reflects this lesser priority. Thus, the mobile communications device 102 may provide techniques to manage notifications in a dynamic way that address the priority of the notification as well as a relatively limited display area of the display device 116 of the mobile communications device 102.
[0058] FIG. 6 illustrates an example implementation 600 of the mobile communications device 102 of FIG. 1 as outputting a full-screen notification. In this example, the unlock screen 120 is configured such that the user may address a particular type of notification without unlocking the mobile communications device 102. For instance, this type of notifications may include an incoming phone call notification 602 as illustrated in FIG. 6 , an alarm clock notification, and so on. In an implementation, these high priority notifications persist until the mobile communications device 102 is unlocked as previously described.
[0059] When this particular type of “high priority” notification has been addressed, the mobile communications device 102 may return to the key locked state with the screen timer reset to power down the display device 116. Thus, this particular type of “high priority” notifications may be output and interacted with without manually unlocking the mobile communications device 102. The unlock screen 120 may also be configured to output notifications having a lesser priority, further discussion of which may be found in relation to the following figure.
[0060] FIG. 7 illustrates an example implementation 700 of the mobile communications device 102 of FIG. 1 as arranging and outputting notifications for display in conjunction with the unlock screen 120. In an implementation, the unlock screen 120 is not configured to be an aggregate view of each of a user's unnoticed notifications. Rather, the unlock screen 120 may be configured to provide a summary view of each notification that is to be output since the last time the mobile communications device 102 was unlocked.
[0061] In a first configuration 702 of the example implementation 700 of FIG. 7 , notifications 704, 706, 708 of texts and a missed call are displayed in respective “talk balloons.” These notifications 704-708 are illustrated as obstructing an underlying image 502, which is a clock in this instance, until the mobile communications device 102 has been unlocked.
[0062] The mobile communications device 102 may employ one or more techniques to arrange the notifications 704-708 such that the clock 502 is not occluded. In some instances, however, a number of notifications may be so great as to obscure each other as well as the clock 502. Accordingly, a condense mechanism may be employed as shown in the second configuration 710 of FIG. 7 . In this example, a user of the mobile communications device 102 may miss a call that would cause a notification 712 of the missed call as well as a notification 714 of a voicemail to be output. However, output of these notifications 712, 714 with the notifications 704-708 may cause the unlock screen 120 to become cluttered to a point at which the notifications are difficult to view.
[0063] Accordingly, the condense mechanism may be employed to condense the notifications 704-714 into a single notification 716 that references each of the other notifications 704-714. For example, the notification 716 in the second configuration 710 as illustrated references two missed calls, two text messages and a voicemail. Thus, the notification 716 enumerates a number and type of message that the user has not yet seen and readily informs the user as to “what was missed” since the unlock screen 120 was last unlocked. In an implementation, a setting may be provided by the mobile communications device 102 to disable display of particular types of notifications, e.g., permit or deny notifications according to priority.
[0064] Although these techniques has been described in relation to the unlock screen 120, it should be apparent that these techniques may be applied to a wide variety of user interfaces, such as a home screen of the user interface 122 previously described to manage notifications.
[0065] FIG. 8 illustrates an example implementation 800 in which a notification is displayed singly as received and then displayed in conjunction with other notifications. This example implementation 800 illustrates first, second, and third configurations 802, 804, 806 of the mobile communications device 102. In the first configuration 802, the lock screen as output on the display device 116 includes three notifications 810.
[0066] A SMS text is then received, which causes the mobile communications device 102 to assume the second configuration 804 in which a new notification 812 is output that corresponds to the new SMS text. Associated contact information 814 is also output that corresponds to a sender of the SMS text. In this example, the notification 812 and the information 814 as output in the second configuration 804 replace the output of the notifications 810 and image in the first configuration 802, thereby calling attention to the notification 812.
[0067] After a specified amount of time has passed, the mobile communications device 102 (and more particularly the unlock screen 120) assumes the third configuration 806. In the third configuration 806, the notification 812 of the second configuration 804 is added to the notifications 810 of the first configuration 802. In an implementation, the techniques of this implementation 800 may be leveraged with the condense mechanism of FIG. 7 such that the third configuration 806 is not cluttered when the amount of notifications exceeds a specified amount.
[0068] FIG. 9 illustrates the mobile communications device 102 in an example implementation 900 in which a notification that is assigned a medium priority is output with notifications 810 that are assigned a low priority. As previously described, notifications may be assigned different priorities in a variety of ways, such as based as a likelihood of being of interest to a user at a particular point in time. Therefore, notifications may have a priority that changes over time.
[0069] The mobile communications device 102 may leverage these priorities in order to arrange the notifications on the unlock screen 120. As illustrated in FIG. 9 , for instance, notifications 810 from FIG. 8 are displayed that include missed telephone calls and texts. Another notification 902 is also displayed that has been assigned a medium priority, which is illustrated as a reminder of a doctor's appointment in 15 minutes. Because the reminder has been assigned a medium priority, it is displayed in a layer “above” the layer of the low priority notifications. Although a calendar reminder has been described, it should be apparent that a wide variety of notifications may be assigned a medium priority, such as battery low indicators, an alarm clock, and so on.
[0070] In an implementation, notifications having a medium priority when displayed on the unlock screen 120 may not be interacted with without unlocking the mobile communications device 102. If the user chooses to unlock the mobile communications device 102 rather than dismiss the notification 902, the notification 902 (when assigned a medium priority) may persist on top of the notifications 810 having a low priority after the mobile communications device 102 has been unlocked.
[0071] Although the notification techniques have been described in relation to an unlock screen 120, it should be readily apparent that these techniques may be implemented in a wide variety of user interfaces, such as in a home screen of the user interface 122 described previously.
[0072] Emergency Contact User Interface
[0073] FIG. 10 illustrates an example implementation 1000 in which the mobile communications device 102 includes an emergency contact user interface 1002. When a mobile phone is locked (either key or device locked in which is pin is utilized to unlock the phone), it is required by law to enable emergency dialing. For the most part, a PIN-lock is phone is to protect a user's data and prohibit abuse of the phone's capabilities. Accordingly, techniques are described which are useful for returning a mobile phone or other mobile communications device to the owner, may help bystanders to help an owner of the mobile communications device in an emergency situation, and expedite the process of dialing an emergency number.
[0074] Use of conventional phones on the market relay on an assumption that users know and can dial emergency numbers to call them in an emergency situation. Additionally, conventional phone restrict dialing functionality to specific emergency numbers, rather than contacts that may be able to help. Techniques are described to download locally relevant numbers and make them directly accessible to users from an emergency contact user interface 1002 if the mobile communications device 1002 is device locked (e.g., via a PIN), which may make dialing these emergency numbers easier.
[0075] Additionally, these techniques may be used to give limited access to an “inner circle” of contacts for helping a user who might not be physically capable of unlocking the device, which may also assist in recovery of a lost device-locked phone. In an implementation, this information may be displayed in the emergency contact user interface 1002 while limiting access to personal data through the device lock.
[0076] The mobile communications device 102 is illustrated as including an emergency contact module 1104, which is representative of functionality to form and output the emergency contact user interface 1002. For example, the mobile communications device 102 may be in a device lock state such that a PIN number is to be entered before access to underlying functionality of the mobile communications device 102 is permitted. In this implementation, a user may still be able to call emergency telephone numbers from the unlock screen. For example, a user may switch to emergency calling mode by pressing a call key which may be implemented as a hardware key 1006, a display of a key in a PIN entry screen configured to remove a device lock, and so on.
[0077] As illustrated, the emergency contact user interface 1002 may be output by the mobile communications device 102 to present a user with a list of contacts 1008 that may be dialed. In the illustrated implementation, emergency numbers are displayed at the top of this list, which may be updated based on the mobile communication device's 102 geographic location.
[0078] For example, a geographic location of the mobile communication device 102 may be determined by the mobile communications device 102 or other entity, such as a web service 1010. The geographic position may be determined in a variety of ways, such as through a global positing system, through use of cellular towers that are used to communicate with the mobile communications device 102, and so on. A web service 1010 may then provide contacts 1012 (e.g., emergency numbers) via the network 408 to the mobile communications device 102. In another implementation, the contacts 1012 may be stored locally by the mobile communications device 102.
[0079] The emergency contact user interface 1002 may also include “inner circle contacts,” which may be listed by first name solely in alphabetical order after the emergency numbers. The inner circle contacts may be specified in a variety of ways, such as through information associated with each contact through interaction with a “wizard.” If an inner circle contact has more than one telephone number, the number type may be displayed in parentheses after the name, e.g., “Mom (m)” and “Mom (h).” These contact number may also be used such that if a mobile communications device 102 is lost, a person that finds the phone may call the contact to locate the owner.
[0080] In the device locked state, selection of the representations of the contact 1008 initiates a phone call to the selected contact in limited call mode. If a user wants to access other phone functionality during the call, the user may be prompted with a PIN entry pad to enter a pin number. If a maximum number of PIN entries have already been attempted, the phone call is initiated and user may is not granted access to phone capabilities except to end the call. Although the emergency contact user interface has been described in relation to a device locked state, it should be readily apparent that this user interface may be employed in a variety of different ways, such as by a mobile communications device that is not in a locked state (e.g., by pressing a key to view emergency contacts).
Example Procedures
[0081] The following discussion describes techniques that may be implemented utilizing the previously described systems and devices. Aspects of each of the procedures may be implemented in hardware, firmware, software, or a combination thereof. The procedures are shown as a set of blocks that specify operations performed by one or more devices and are not necessarily limited to the orders shown for performing the operations by the respective blocks. In portions of the following discussion, reference will be made to the previous sections and corresponding figures.
[0082] FIG. 11 depicts a procedure 1100 in an example implementation in which an animation is displayed in conjunction with removal of a key lock of a mobile communications device. An unlock screen 120 is displayed by a mobile communications device 102 that indicates that one or more keys of the mobile communications device 102 are locked (block 1102).
[0083] If an input at the mobile communications device 102 is detected to remove the lock, an animation is displayed that gives an appearance that the unlock screen is a page that is being turned and the lock of the one of more keys is removed (block 1104). A variety of different inputs may be detected, such as opening (e.g., via sliding) of the mobile communications device 102 as illustrated in FIG. 1 , via a gesture as illustrated in FIG. 2 , and so on.
[0084] FIG. 12 depicts a procedure 1200 in an example implementation in which a clock is displayed. A clock is displayed on a display device of a mobile communications device 102 in response to a waking of the display device (block 1202). For example, the mobile communications device 102 may turn the display device 116 off to conserve power after a specified amount of time has passed since the mobile communications device 102 was locked, since an input was received, and so on. The display device 116 may then be woke in response to an input, such as a press of a button by a user, movement of the mobile communications device 102, and so on.
[0085] The display of the clock is minimized after a specified amount of time has passed since the waking of the display device (block 1204). For example, the display of the clock 502 in FIG. 5 may be minimized to a corner of the display device 116 as shown in FIG. 4 . Thus, in this example, the display of the clock 502 is also moved to a corner. A variety of other examples are also contemplated.
[0086] FIG. 13 depicts a procedure 1300 in an example implementation in which a condense mechanism is employed with notifications. An unlock screen 120 of a mobile communications device 102 is updated to include notifications of events that have occurred since a last time the mobile communications device 102 was locked (block 1302). A variety of different events may cause output of a notification, such as hardware (e.g., a battery low condition), software (e.g., reminders, receipt of communications), and so on.
[0087] If a number of notifications that are to be output on the unlock screen exceeds a specified number, the notifications are condensed into a single condensed notification to be output via the unlock screen that references a type and number of the notifications (block 1304). For example, the notification 716 acts to condense notifications 704-708, 712, 714 by referencing the type of notification (e.g., missed call, text message, voicemail, and so on) and a number for a respective type.
[0088] The notifications are rearranged as subsequent notifications are received if the number of the notifications that are to be output on the unlock screen does not exceed the specified number (block 1306). For example, the rearranging may be performed so that the notifications do not obscure each other, that the notifications do not obscure an image that acts as a background (e.g., wallpaper) for the unlock screen 120, and so on.
Example Mobile Communications Device
[0089] FIG. 14 illustrates various components of an example device 1400 that can be implemented in various embodiments as any type of a mobile communication device to implement embodiments of devices, features, and systems for mobile communications. For example, device 1400 can be implemented as any of the mobile communications devices 102 described with reference to respective FIGS. 1-13 . Device 1400 can also be implemented to access a network-based service, such as a content service.
[0090] Device 1400 includes input(s) 1402 that may include Internet Protocol (IP) inputs. Device 1400 further includes communication interface(s) 1404 that can be implemented as any one or more of a wireless interface, any type of network interface, and as any other type of communication interface. A network interface provides a connection between device 1400 and a communication network by which other electronic and computing devices can communicate data with device 1400. A wireless interface enables device 1400 to operate as a mobile communication device for wireless communications.
[0091] Device 1400 also includes one or more processors 1406 (e.g., any of microprocessors, controllers, and the like) which process various computer-executable instructions to control the operation of device 1400 and to communicate with other electronic devices. Device 1400 can be implemented with computer-readable media 1408, such as one or more memory components, examples of which include random access memory (RAM) and non-volatile memory (e.g., any one or more of a read-only memory (ROM), flash memory, EPROM, EEPROM, etc.).
[0092] Computer-readable media 1408 provides data storage to store content and data 1410, as well as device applications and any other types of information and/or data related to operational aspects of device 1400. For example, an operating system 1412 can be maintained as a computer application with the computer-readable media 1408 and executed on processor(s) 1406. Device applications can also include a communication manager module 1414 (which may be used to provide telephonic functionality) and a media manager 1416.
[0093] Device 1400 also includes an audio and/or video output 1418 that provides audio and/or video data to an audio rendering and/or display system 1420. The audio rendering and/or display system 1420 can be implemented as integrated component(s) of the example device 1400, and can include any components that process, display, and/or otherwise render audio, video, and image data. Device 1400 can also be implemented to provide a user tactile feedback, such as vibrate and haptics.
[0094] Generally, the blocks may be representative of modules that are configured to provide represented functionality. Further, any of the functions described herein can be implemented using software, firmware (e.g., fixed logic circuitry), manual processing, or a combination of these implementations. The terms “module,” “functionality,” and “logic” as used herein generally represent software, firmware, or a combination of software and firmware. In the case of a software implementation, the module, functionality, or logic represents program code that performs specified tasks when executed on a processor (e.g., CPU or CPUs). The program code can be stored in one or more computer readable memory devices. The features of the techniques described above are platform-independent, meaning that the techniques may be implemented on a variety of commercial computing platforms having a variety of processors.
[0095] Although the invention has been described in language specific to structural features and/or methodological acts, it is to be understood that the invention defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed invention.
Claims
What is claimed is:
1. A method comprising:
displaying an unlock screen on a display device by a mobile communications device that indicates that one or more keys of the mobile communications device are locked; and
if an input at the mobile communications device is detected to remove the lock of a touch target that is displayed as an upturned corner of the page and dragged across a specified Y-axis of the display device that defines a threshold, displaying an animation that gives an appearance that the unlock screen is a page that is being turned and removing the lock of the one or more keys.
2. A method as described in claim 1, wherein if the touch target is released and is not across a specified Y-axis of the display device, the touch target is animated to return to an original location on the display device.
3. A method as described in claim 1, wherein the input is received by exposing a keyboard of the mobile communications device.
4. A method as described in claim 1, wherein the mobile communications device includes functionality to enable a user to specify an image for display in the unlock screen.
5. A method as described in claim 4, wherein the image is downloaded from a web service via a network.
6. A method as described in claim 4, wherein the image is one of a plurality of images that are output as a slideshow on the unlock screen.
7. A method as described in claim 1, wherein the displaying of the unlock screen includes representations of one or more notifications to be output by the mobile communications device since a last time at which the lock was removed.
8. A method as described in claim 7, wherein the representation of the one or more notifications are displayed on the unlock screen as silhouettes of the notifications that are to be output in a user interface after the removing of the lock is performed.
9. A mobile communications device comprising a display device and one or more modules to display a clock on the display device in response to a waking of the display device and minimize the display of the clock after a specified amount of time has passed since the waking of the display device.
10. A mobile communications device as described in claim 9, wherein the one or more modules include functionality to receive and send telephone calls.
11. A mobile communications device as described in claim 9, wherein the one or more modules further move the display of the clock from a center of the display device to a corner of the display device after the specified amount of time has passed.
12. A mobile communications device as described in claim 9, wherein the one or more modules are configured to display the clock when in a key locked state.
13. A mobile communications device as described in claim 9, wherein the one or more modules are configured to display the clock when in a device locked state that is removable by entering a PIN.
14. One or more tangible computer-readable media comprising instructions that are executable by a mobile communications device to display an animation that gives an appearance that an unlock screen is a page being turned that follows a gesture input via a touch screen of the mobile communications device to remove a lock of the mobile communications device the display of the unlock screen includes representations of one or more notifications to be output by the mobile communications device since a last time at which the lock was removed and displayed on the unlock screen as silhouettes of the notifications that are to be output in a user interface after the removing of the lock is performed.
15. One or more tangible computer-readable media as described in claim 14, wherein the lock is a key lock or a device lock that is removable via a PIN.
16. One or more tangible computer-readable media as described in claim 14, wherein a corner of the page of the unlock screen follows the gesture input via the touchscreen.
Patent Citations (326)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5189732(A) | 1993-02-01 | Kondo | Applicant |
| US5258748(A) | 1993-11-01 | Jones | Applicant |
| US5463725(A) | 1995-10-01 | Henckel et al. | Applicant |
| US5515495(A) | 1996-05-01 | Ikemoto | Applicant |
| US5574836(A) | 1996-11-01 | Broemmelsiek | Applicant |
| US5675329(A) | 1997-10-01 | Barker | Applicant |
| US5860073(A) | 1999-01-01 | Ferrel et al. | Applicant |
| US5905492(A) | 1999-05-01 | Straub et al. | Applicant |
| US5914720(A) | 1999-06-01 | Maples et al. | Applicant |
| US5963204(A) | 1999-10-01 | Ikeda et al. | Applicant |
| US6008816(A) | 1999-12-01 | Eisler | Applicant |
| US6385630(B1) | 2002-05-01 | Ejerhed | Applicant |
| US6396963(B2) | 2002-05-01 | Shaffer | Applicant |
| US6424338(B1) | 2002-07-01 | Andersone | Applicant |
| US6507643(B1) | 2003-01-01 | Groner | Applicant |
| US6662023(B1) | 2003-12-01 | Helle | Applicant |
| US6697825(B1) | 2004-02-01 | Underwood et al. | Applicant |
| US6784925(B1) | 2004-08-01 | Tomat | Applicant |
| US6865297(B2) | 2005-03-01 | Loui | Applicant |
| US6876312(B2) | 2005-04-01 | Yu | Applicant |
| US6904597(B2) | 2005-06-01 | Jin | Applicant |
| US6961731(B2) | 2005-11-01 | Holbrook | Applicant |
| US6983310(B2) | 2006-01-01 | Rouse | Applicant |
| US6987991(B2) | 2006-01-01 | Nelson | Applicant |
| US7013041(B2) | 2006-03-01 | Miyamoto | Applicant |
| US7058955(B2) | 2006-06-01 | Porkka | Applicant |
| US7065385(B2) | 2006-06-01 | Jarrad et al. | Applicant |
| US7065386(B1) | 2006-06-01 | Smethers | Applicant |
| US7111044(B2) | 2006-09-01 | Lee | Applicant |
| US7133707(B1) | 2006-11-01 | Rak | Applicant |
| US7133859(B1) | 2006-11-01 | Wong | Applicant |
| US7139800(B2) | 2006-11-01 | Bellotti et al. | Applicant |
| US7158123(B2) | 2007-01-01 | Myers | Applicant |
| US7178111(B2) | 2007-02-01 | Glein et al. | Applicant |
| US7216588(B2) | 2007-05-01 | Suess | Applicant |
| US7249326(B2) | 2007-07-01 | Stoakley et al. | Applicant |
| US7280097(B2) | 2007-10-01 | Chen | Applicant |
| US7283620(B2) | 2007-10-01 | Adamczyk | Applicant |
| US7289806(B2) | 2007-10-01 | Morris et al. | Applicant |
| US7296184(B2) | 2007-11-01 | Derks et al. | Examiner |
| US7336263(B2) | 2008-02-01 | Valikangas | Applicant |
| US7369647(B2) | 2008-05-01 | Gao et al. | Applicant |
| US7388578(B2) | 2008-06-01 | Tao | Applicant |
| US7403191(B2) | 2008-07-01 | Sinclair | Applicant |
| US7447520(B2) | 2008-11-01 | Scott | Applicant |
| US7461151(B2) | 2008-12-01 | Colson et al. | Applicant |
| US7479949(B2) | 2009-01-01 | Jobs | Applicant |
| US7480870(B2) | 2009-01-01 | Anzures | Applicant |
| US7483418(B2) | 2009-01-01 | Maurer | Applicant |
| US7496830(B2) | 2009-02-01 | Rubin | Applicant |
| US7593995(B1) | 2009-09-01 | He et al. | Applicant |
| US7606714(B2) | 2009-10-01 | Williams et al. | Applicant |
| US7610563(B2) | 2009-10-01 | Nelson et al. | Applicant |
| US7619615(B1) | 2009-11-01 | Donoghue | Applicant |
| US7640518(B2) | 2009-12-01 | Forlines et al. | Applicant |
| US7657849(B2) | 2010-02-01 | Chaudhri et al. | Applicant |
| US7671756(B2) | 2010-03-01 | Herz et al. | Applicant |
| US7702683(B1) | 2010-04-01 | Kirshenbaum | Applicant |
| US7755674(B2) | 2010-07-01 | Kaminaga | Applicant |
| US7834861(B2) | 2010-11-01 | Lee | Applicant |
| US7877707(B2) | 2011-01-01 | Westerman et al. | Applicant |
| US7889180(B2) | 2011-02-01 | Byun et al. | Applicant |
| US7983718(B1) | 2011-07-01 | Roka | Applicant |
| US8006276(B2) | 2011-08-01 | Nakagawa et al. | Applicant |
| US8086275(B2) | 2011-12-01 | Wykes | Applicant |
| US8131808(B2) | 2012-03-01 | Aoki et al. | Applicant |
| US8150924(B2) | 2012-04-01 | Buchheit et al. | Applicant |
| US8175653(B2) | 2012-05-01 | Smuga et al. | Applicant |
| US8238876(B2) | 2012-08-01 | Teng | Applicant |
| US8250494(B2) | 2012-08-01 | Butcher | Applicant |
| US8255473(B2) | 2012-08-01 | Eren et al. | Applicant |
| US8269736(B2) | 2012-09-01 | Wilairat | Applicant |
| US2001/0022621(A1) | 2001-09-01 | Squibbs | Applicant |
| US2002/0000963(A1) | 2002-01-01 | Yoshida et al. | Examiner |
| US2002/0018051(A1) | 2002-02-01 | Singh | Applicant |
| US2002/0035607(A1) | 2002-03-01 | Checkoway | Applicant |
| US2002/0060701(A1) | 2002-05-01 | Naughton et al. | Applicant |
| US2002/0070961(A1) | 2002-06-01 | Xu et al. | Applicant |
| US2002/0091755(A1) | 2002-07-01 | Narin | Applicant |
| US2002/0128036(A1) | 2002-09-01 | Yach et al. | Applicant |
| US2002/0129061(A1) | 2002-09-01 | Swart et al. | Applicant |
| US2002/0138248(A1) | 2002-09-01 | Corston-Oliver et al. | Applicant |
| US2002/0142762(A1) | 2002-10-01 | Chmaytelli et al. | Applicant |
| US2002/0154176(A1) | 2002-10-01 | Barksdale et al. | Applicant |
| US2003/0003899(A1) | 2003-01-01 | Tashiro et al. | Applicant |
| US2003/0008686(A1) | 2003-01-01 | Park et al. | Applicant |
| US2003/0011643(A1) | 2003-01-01 | Nishihihata | Applicant |
| US2003/0040300(A1) | 2003-02-01 | Bodic | Applicant |
| US2003/0073414(A1) | 2003-04-01 | Capps | Applicant |
| US2003/0096604(A1) | 2003-05-01 | Vollandt | Examiner |
| US2003/0105827(A1) | 2003-06-01 | Tan et al. | Applicant |
| US2003/0135582(A1) | 2003-07-01 | Allen et al. | Applicant |
| US2003/0187996(A1) | 2003-10-01 | Cardina et al. | Applicant |
| US2003/0222907(A1) | 2003-12-01 | Heikes et al. | Applicant |
| US2003/0225846(A1) | 2003-12-01 | Heikes et al. | Applicant |
| US2004/0068543(A1) | 2004-04-01 | Seifert | Applicant |
| US2004/0078299(A1) | 2004-04-01 | Down-Logan | Applicant |
| US2004/0111673(A1) | 2004-06-01 | Bowman et al. | Applicant |
| US2004/0185883(A1) | 2004-09-01 | Rukman | Applicant |
| US2004/0212586(A1) | 2004-10-01 | Denny | Applicant |
| US2004/0217954(A1) | 2004-11-01 | O'Gorman et al. | Examiner |
| US2004/0250217(A1) | 2004-12-01 | Tojo et al. | Applicant |
| US2005/0054384(A1) | 2005-03-01 | Pasquale et al. | Applicant |
| US2005/0060647(A1) | 2005-03-01 | Doan et al. | Applicant |
| US2005/0060665(A1) | 2005-03-01 | Rekimoto | Applicant |
| US2005/0079896(A1) | 2005-04-01 | Kokko et al. | Applicant |
| US2005/0085215(A1) | 2005-04-01 | Kokko | Applicant |
| US2005/0085272(A1) | 2005-04-01 | Anderson et al. | Applicant |
| US2005/0114788(A1) | 2005-05-01 | Fabritius | Applicant |
| US2005/0143138(A1) | 2005-06-01 | Lee et al. | Applicant |
| US2005/0182798(A1) | 2005-08-01 | Todd et al. | Applicant |
| US2005/0183021(A1) | 2005-08-01 | Allen et al. | Applicant |
| US2005/0184999(A1) | 2005-08-01 | Daioku | Applicant |
| US2005/0198159(A1) | 2005-09-01 | Kirsch | Applicant |
| US2005/0216300(A1) | 2005-09-01 | Appelman et al. | Applicant |
| US2005/0223057(A1) | 2005-10-01 | Buchheit et al. | Applicant |
| US2005/0232166(A1) | 2005-10-01 | Nierhaus | Applicant |
| US2005/0250547(A1) | 2005-11-01 | Salman et al. | Applicant |
| US2005/0273614(A1) | 2005-12-01 | Ahuja | Applicant |
| US2005/0280719(A1) | 2005-12-01 | Kim | Applicant |
| US2006/0004685(A1) | 2006-01-01 | Pyhalammi et al. | Applicant |
| US2006/0015736(A1) | 2006-01-01 | Callas et al. | Applicant |
| US2006/0015812(A1) | 2006-01-01 | Cunningham | Applicant |
| US2006/0026013(A1) | 2006-02-01 | Kraft | Applicant |
| US2006/0059430(A1) | 2006-03-01 | Bells | Applicant |
| US2006/0070005(A1) | 2006-03-01 | Gilbert et al. | Applicant |
| US2006/0074771(A1) | 2006-04-01 | Kim | Applicant |
| US2006/0103623(A1) | 2006-05-01 | Davis | Applicant |
| US2006/0129543(A1) | 2006-06-01 | Bates et al. | Applicant |
| US2006/0135220(A1) | 2006-06-01 | Kim et al. | Applicant |
| US2006/0136773(A1) | 2006-06-01 | Kespohl et al. | Applicant |
| US2006/0152803(A1) | 2006-07-01 | Provitola | Applicant |
| US2006/0172724(A1) | 2006-08-01 | Linkert et al. | Applicant |
| US2006/0173911(A1) | 2006-08-01 | Levin et al. | Applicant |
| US2006/0199598(A1) | 2006-09-01 | Lee et al. | Examiner |
| US2006/0218234(A1) | 2006-09-01 | Deng et al. | Applicant |
| US2006/0246955(A1) | 2006-11-01 | Nirhamo | Applicant |
| US2006/0253801(A1) | 2006-11-01 | Okaro et al. | Applicant |
| US2006/0259870(A1) | 2006-11-01 | Hewitt et al. | Applicant |
| US2006/0259873(A1) | 2006-11-01 | Mister | Applicant |
| US2006/0271520(A1) | 2006-11-01 | Ragan | Applicant |
| US2006/0281448(A1) | 2006-12-01 | Plestid et al. | Applicant |
| US2006/0293088(A1) | 2006-12-01 | Kokubo | Applicant |
| US2006/0294396(A1) | 2006-12-01 | Witman | Applicant |
| US2007/0005716(A1) | 2007-01-01 | LeVasseur et al. | Applicant |
| US2007/0011610(A1) | 2007-01-01 | Sethi et al. | Applicant |
| US2007/0015532(A1) | 2007-01-01 | Deelman | Applicant |
| US2007/0024646(A1) | 2007-02-01 | Saarinen | Applicant |
| US2007/0035513(A1) | 2007-02-01 | Sherrard et al. | Applicant |
| US2007/0038567(A1) | 2007-02-01 | Allaire et al. | Applicant |
| US2007/0054679(A1) | 2007-03-01 | Cho et al. | Applicant |
| US2007/0061714(A1) | 2007-03-01 | Stuple et al. | Applicant |
| US2007/0067272(A1) | 2007-03-01 | Flynt | Applicant |
| US2007/0073718(A1) | 2007-03-01 | Ramer | Applicant |
| US2007/0076013(A1) | 2007-04-01 | Campbell | Applicant |
| US2007/0080954(A1) | 2007-04-01 | Griffin | Applicant |
| US2007/0082707(A1) | 2007-04-01 | Flynt et al. | Applicant |
| US2007/0082708(A1) | 2007-04-01 | Griffin | Applicant |
| US2007/0106635(A1) | 2007-05-01 | Frieden et al. | Applicant |
| US2007/0127638(A1) | 2007-06-01 | Doulton | Applicant |
| US2007/0157089(A1) | 2007-07-01 | Van Os et al. | Applicant |
| US2007/0171192(A1) | 2007-07-01 | Seo et al. | Applicant |
| US2007/0182595(A1) | 2007-08-01 | Ghasabian | Applicant |
| US2007/0185847(A1) | 2007-08-01 | Budzik et al. | Applicant |
| US2007/0192707(A1) | 2007-08-01 | Maeda et al. | Applicant |
| US2007/0198420(A1) | 2007-08-01 | Goldstein | Applicant |
| US2007/0211034(A1) | 2007-09-01 | Griffin et al. | Applicant |
| US2007/0214429(A1) | 2007-09-01 | Lyudovyk et al. | Applicant |
| US2007/0216651(A1) | 2007-09-01 | Patel | Applicant |
| US2007/0225022(A1) | 2007-09-01 | Satake | Applicant |
| US2007/0233654(A1) | 2007-10-01 | Karlson | Applicant |
| US2007/0238488(A1) | 2007-10-01 | Scott | Applicant |
| US2007/0247435(A1) | 2007-10-01 | Benko et al. | Applicant |
| US2007/0250583(A1) | 2007-10-01 | Hardy | Applicant |
| US2007/0253758(A1) | 2007-11-01 | Suess | Applicant |
| US2007/0256029(A1) | 2007-11-01 | Maxwell | Applicant |
| US2007/0257891(A1) | 2007-11-01 | Esenther et al. | Applicant |
| US2007/0257933(A1) | 2007-11-01 | Klassen | Applicant |
| US2007/0262964(A1) | 2007-11-01 | Zotov et al. | Applicant |
| US2007/0263843(A1) | 2007-11-01 | Foxenland | Applicant |
| US2007/0273663(A1) | 2007-11-01 | Park et al. | Applicant |
| US2007/0280457(A1) | 2007-12-01 | Aberethy | Applicant |
| US2007/0281747(A1) | 2007-12-01 | Pletikosa | Applicant |
| US2008/0005668(A1) | 2008-01-01 | Mavinkurve | Applicant |
| US2008/0032681(A1) | 2008-02-01 | West | Applicant |
| US2008/0036743(A1) | 2008-02-01 | Westerman | Applicant |
| US2008/0048986(A1) | 2008-02-01 | Khoo | Applicant |
| US2008/0052370(A1) | 2008-02-01 | Snyder | Applicant |
| US2008/0057910(A1) | 2008-03-01 | Thoresson et al. | Applicant |
| US2008/0057926(A1) | 2008-03-01 | Forstall et al. | Applicant |
| US2008/0076472(A1) | 2008-03-01 | Hyatt | Applicant |
| US2008/0082934(A1) | 2008-04-01 | Kocienda et al. | Applicant |
| US2008/0085700(A1) | 2008-04-01 | Arora | Applicant |
| US2008/0102863(A1) | 2008-05-01 | Hardy | Applicant |
| US2008/0114535(A1) | 2008-05-01 | Nesbitt | Applicant |
| US2008/0132252(A1) | 2008-06-01 | Altman et al. | Applicant |
| US2008/0153551(A1) | 2008-06-01 | Baek et al. | Applicant |
| US2008/0155425(A1) | 2008-06-01 | Murthy et al. | Applicant |
| US2008/0162651(A1) | 2008-07-01 | Madnani | Applicant |
| US2008/0165132(A1) | 2008-07-01 | Weiss | Applicant |
| US2008/0165136(A1) | 2008-07-01 | Christie et al. | Applicant |
| US2008/0165163(A1) | 2008-07-01 | Bathiche | Applicant |
| US2008/0167058(A1) | 2008-07-01 | Lee et al. | Applicant |
| US2008/0168403(A1) | 2008-07-01 | Westerman et al. | Applicant |
| US2008/0172609(A1) | 2008-07-01 | Rytivaara | Applicant |
| US2008/0180399(A1) | 2008-07-01 | Cheng | Applicant |
| US2008/0182628(A1) | 2008-07-01 | Lee et al. | Applicant |
| US2008/0189658(A1) | 2008-08-01 | Jeong et al. | Applicant |
| US2008/0198141(A1) | 2008-08-01 | Lee et al. | Applicant |
| US2008/0208973(A1) | 2008-08-01 | Hayashi | Applicant |
| US2008/0222560(A1) | 2008-09-01 | Harrison | Applicant |
| US2008/0222569(A1) | 2008-09-01 | Champion | Applicant |
| US2008/0242362(A1) | 2008-10-01 | Duarte | Applicant |
| US2008/0259042(A1) | 2008-10-01 | Thorn | Applicant |
| US2008/0261660(A1) | 2008-10-01 | Huh et al. | Applicant |
| US2008/0263457(A1) | 2008-10-01 | Kim et al. | Applicant |
| US2008/0270558(A1) | 2008-10-01 | Ma | Applicant |
| US2008/0297475(A1) | 2008-12-01 | Woolf et al. | Applicant |
| US2008/0299999(A1) | 2008-12-01 | Lockhart et al. | Applicant |
| US2008/0301046(A1) | 2008-12-01 | Martinez | Applicant |
| US2008/0301575(A1) | 2008-12-01 | Fermon | Applicant |
| US2008/0309626(A1) | 2008-12-01 | Westerman et al. | Applicant |
| US2008/0316177(A1) | 2008-12-01 | Tseng | Applicant |
| US2008/0317240(A1) | 2008-12-01 | Chang et al. | Applicant |
| US2009/0007017(A1) | 2009-01-01 | Anzures et al. | Examiner |
| US2009/0012952(A1) | 2009-01-01 | Fredriksson | Applicant |
| US2009/0029736(A1) | 2009-01-01 | Kim et al. | Applicant |
| US2009/0037469(A1) | 2009-02-01 | Kirsch | Applicant |
| US2009/0051671(A1) | 2009-02-01 | Konstas | Applicant |
| US2009/0061837(A1) | 2009-03-01 | Chaudhri et al. | Applicant |
| US2009/0061948(A1) | 2009-03-01 | Lee et al. | Applicant |
| US2009/0064055(A1) | 2009-03-01 | Chaudhri | Applicant |
| US2009/0077649(A1) | 2009-03-01 | Lockhart | Applicant |
| US2009/0083656(A1) | 2009-03-01 | Dokhon | Applicant |
| US2009/0085851(A1) | 2009-04-01 | Lim | Applicant |
| US2009/0085878(A1) | 2009-04-01 | Heubel | Applicant |
| US2009/0089215(A1) | 2009-04-01 | Newton | Applicant |
| US2009/0109243(A1) | 2009-04-01 | Kraft | Applicant |
| US2009/0117942(A1) | 2009-05-01 | Boningue et al. | Applicant |
| US2009/0140061(A1) | 2009-06-01 | Schultz et al. | Applicant |
| US2009/0140986(A1) | 2009-06-01 | Karkkainen et al. | Applicant |
| US2009/0146962(A1) | 2009-06-01 | Ahonen et al. | Applicant |
| US2009/0153492(A1) | 2009-06-01 | Popp | Applicant |
| US2009/0160809(A1) | 2009-06-01 | Yang | Applicant |
| US2009/0163182(A1) | 2009-06-01 | Gatti et al. | Applicant |
| US2009/0164888(A1) | 2009-06-01 | Phan | Applicant |
| US2009/0205041(A1) | 2009-08-01 | Michalske | Applicant |
| US2009/0228825(A1) | 2009-09-01 | Van Os et al. | Applicant |
| US2009/0265662(A1) | 2009-10-01 | Bamford | Examiner |
| US2009/0284482(A1) | 2009-11-01 | Chin | Examiner |
| US2009/0298547(A1) | 2009-12-01 | Kim et al. | Applicant |
| US2009/0307589(A1) | 2009-12-01 | Inose et al. | Applicant |
| US2009/0307623(A1) | 2009-12-01 | Agarawala et al. | Applicant |
| US2009/0313584(A1) | 2009-12-01 | Kerr et al. | Applicant |
| US2009/0315847(A1) | 2009-12-01 | Fujii | Applicant |
| US2010/0008490(A1) | 2010-01-01 | Gharachorloo et al. | Applicant |
| US2010/0075628(A1) | 2010-03-01 | Ye | Applicant |
| US2010/0079413(A1) | 2010-04-01 | Kawashima et al. | Applicant |
| US2010/0087169(A1) | 2010-04-01 | Lin | Applicant |
| US2010/0087173(A1) | 2010-04-01 | Lin | Applicant |
| US2010/0100839(A1) | 2010-04-01 | Tseng et al. | Applicant |
| US2010/0103124(A1) | 2010-04-01 | Kruzeniski | Applicant |
| US2010/0105370(A1) | 2010-04-01 | Kruzeniski | Applicant |
| US2010/0105424(A1) | 2010-04-01 | Smuga | Applicant |
| US2010/0105438(A1) | 2010-04-01 | Wykes | Applicant |
| US2010/0105439(A1) | 2010-04-01 | Friedman | Applicant |
| US2010/0105440(A1) | 2010-04-01 | Kruzeniski | Applicant |
| US2010/0105441(A1) | 2010-04-01 | Voss | Applicant |
| US2010/0107067(A1) | 2010-04-01 | Vaisanen | Applicant |
| US2010/0107068(A1) | 2010-04-01 | Butcher | Applicant |
| US2010/0107100(A1) | 2010-04-01 | Schneekloth | Applicant |
| US2010/0145675(A1) | 2010-06-01 | Lloyd et al. | Applicant |
| US2010/0146437(A1) | 2010-06-01 | Woodcock et al. | Applicant |
| US2010/0159966(A1) | 2010-06-01 | Friedman | Applicant |
| US2010/0159994(A1) | 2010-06-01 | Stallings et al. | Applicant |
| US2010/0159995(A1) | 2010-06-01 | Stallings et al. | Applicant |
| US2010/0167699(A1) | 2010-07-01 | Sigmund et al. | Applicant |
| US2010/0180233(A1) | 2010-07-01 | Kruzeniski et al. | Applicant |
| US2010/0216491(A1) | 2010-08-01 | Winkler et al. | Applicant |
| US2010/0248688(A1) | 2010-09-01 | Teng | Applicant |
| US2010/0248741(A1) | 2010-09-01 | Setlur et al. | Applicant |
| US2010/0248787(A1) | 2010-09-01 | Smuga et al. | Applicant |
| US2010/0295795(A1) | 2010-11-01 | Wilairat | Applicant |
| US2010/0311470(A1) | 2010-12-01 | Seo et al. | Applicant |
| US2010/0321403(A1) | 2010-12-01 | Inadome | Examiner |
| US2011/0018806(A1) | 2011-01-01 | Yano | Applicant |
| US2011/0055773(A1) | 2011-03-01 | Agarawala et al. | Applicant |
| US2011/0093778(A1) | 2011-04-01 | Kim et al. | Applicant |
| US2011/0231796(A1) | 2011-09-01 | Vigil | Applicant |
| US2012/0028687(A1) | 2012-02-01 | Wykes | Applicant |
| US2012/0050185(A1) | 2012-03-01 | Davydov et al. | Applicant |
| US2012/0179992(A1) | 2012-07-01 | Smuga | Applicant |
| US2012/0212495(A1) | 2012-08-01 | Butcher | Applicant |
| US2012/0244841(A1) | 2012-09-01 | Teng | Applicant |
| CN102197702 | 2011-09-01 | Applicant | |
| EP583060 | 1994-02-01 | Applicant | |
| EP1752868 | 2007-02-01 | Applicant | |
| JP2004227393 | 2004-08-01 | Applicant | |
| JP2004357257 | 2004-12-01 | Applicant | |
| KR200303655 | 2003-02-01 | Applicant | |
| KR20060019198 | 2006-03-01 | Applicant | |
| KR1020070036114 | 2007-04-01 | Applicant | |
| KR1020070098337 | 2007-10-01 | Applicant | |
| KR20070120368 | 2007-12-01 | Applicant | |
| KR1020080025951(A) | 2008-03-01 | Applicant | |
| KR1020080076390 | 2008-08-01 | Applicant | |
| KR100854333 | 2008-09-01 | Applicant | |
| KR1020080084156 | 2008-09-01 | Applicant | |
| KR1020080113913 | 2008-12-01 | Applicant | |
| KR1020090041635 | 2009-04-01 | Applicant | |
| TW201023026 | 2010-06-01 | Applicant | |
| WO-2005026931 | 2005-03-01 | Applicant | |
| WO-2005027506 | 2005-03-01 | Applicant | |
| WO-2006019639 | 2006-02-01 | Applicant | |
| WO-2007121557 | 2007-11-01 | Applicant | |
| WO-2007134623 | 2007-11-01 | Applicant | |
| WO-2008030608 | 2008-03-01 | Applicant | |
| WO-2008031871 | 2008-03-01 | Applicant | |
| WO-2008035831 | 2008-03-01 | Applicant | |
| WO-2009000043 | 2008-12-01 | Applicant | |
| WO-2009049331 | 2009-04-01 | Applicant | |
| WO-2010048229 | 2010-04-01 | Applicant | |
| WO-2010048448 | 2010-04-01 | Applicant | |
| WO-2010048519 | 2010-04-01 | Applicant | |
| WO-2010117643 | 2010-10-01 | Applicant | |
| WO-2010135155 | 2010-11-01 | Applicant |
Non-Patent Literature (120)
- “PCT Search Report and Written Opinion”, Application No. PCT/US2010/034772, (Dec. 29, 2010),12 pages.Applicant
- “PCT Search Report and Written Opinion”, PCT Application No. PCT/US2010/038730, (Jan. 19, 2011),8 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2009/061382, (May 26, 2010),10 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2009/061735, (Jun. 7, 2010),11 pages.Applicant
- “Microsoft Internet Explorer Window.Createpopup() Method Creates Chromeless Windows”, Retrieved from: <http://www.addict3d.org/news/2012/download.html>, Internet Explorer Window Restrictions,(Oct. 22, 2008),6 pages.Applicant
- “Kiosk Browser Chrome Customization Firefox 2.x”, Retrieved from: <http://stlouis-shopper.com/cgi-bin/mozdev-wiki/,pl?ChromeCustomization> Making a new chrome for the kiosk browser, Kiosk Project Kiosk Browser Chrome Customization Firefox-2.x,(Aug. 16, 2007),2 pages.Applicant
- Harrison, Richard “Symbian OS C++ for Mobile Phones: vol. 3 ( Symbian Press): 3 (Paperback)”, Retrieved from: <http://www.amazon.co.uk/Symbian-OS-Mobile-Phones-Press/dp/productdescription/0470066415>, (Jun. 16, 2003),4 pages.Applicant
- “How do you dial 1-800-Flowers”, Retrieved from: <http://blogs.msdn.com/windowsmobile/archive/2007/02/06/how-do-you-dial-1-800-flowers.aspx>, (Feb. 6, 2007),24 pages.Applicant
- “Blackberry office tools: Qwerty Convert”, Retrieved from: <http://blackberrysoftwarelist.net/blackberry/download-software/blackberry-office/qwerty—convert.aspx>, (Nov. 20, 2008),1 page.Applicant
- Gade, Lisa “Samsung Alias u740”, Retrieved from: <http://www.mobiletechreview.com/phones/Samsung-U740.htm>, (Mar. 14, 2007),6 pages.Applicant
- “Dial a number”, Retrieved from: <http://www.phonespell.org/ialhelp.html> on Nov. 20, 2008, 1 page.Applicant
- “Apple IPhone—8GB AT&T”, Retrieved from: <http://nytimes.com.com/smartphones/apple-iphone-8gb-at/4515-6452—7-32309245.html>, (Jun. 29, 2007),11 pages.Applicant
- “IntelliScreen—New iPhone App Shows Today Screen Type Info in Lock Screen”, Retrieved from: <http://justanotheriphoneblog.com/wordpress//2008/05/13/intelliscreen-new-iphone-app-shows-today-screen-type-info-on-lock-screen/>, (May 13, 2008),11 pages.Applicant
- “PocketShield—New Screenlock App for the HTC Diamond and Pro”, Retrieved from: <http://wmpoweruser.com/?tag=htc-touch-diamond>, (Nov. 6, 2008),13 pages.Applicant
- “SecureMe—Anti-Theft Security Application for S60 3rd”, Retrieved from: <http:/www.killermobile.com/newsite/mobile-software/s60-applications/secureme-%11-anti%11theft-security-application-for-s60-3rd.htm>, (Nov. 11, 2008),2 pages.Applicant
- “Winterface Review”, Retrieved from: <http://www.mytodayscreen.com/winterface-review/>, (Jul. 9, 2008),42 pages.Applicant
- Oliver, Sam “Potential iPhone Usability and Interface Improvements”, Retrieved from: <http://www.appleinsider.com/articles/08/09/18/potential—iphone—usability—and—interface—improvements.html>, (Sep. 18, 2008),4 pages.Applicant
- “Google Android has Landed; T-Mobile, HTC Unveil G1”, Retrieved from: <http://www.crn.com/retail/210603348> on Nov. 26, 2008., (Sep. 23, 2008),5 Pages.Applicant
- “Alltel Adds Dedicated Search Key to Phones”, Retrieved from: <http://www.phonescoop.com/news/item.php?n=2159> on Nov. 26, 2008., (Apr. 12, 2007),2 Pages.Applicant
- Oryl, Michael “Review: Asus P527 Smartphone for North America”, Retrieved from: <http://www.mobileburn.com/review.jsp?Id=4257> on Dec. 17, 2008., (Mar. 5, 2008),1 Page.Applicant
- “Nokia E61 Tips and Tricks for Keyboard Shortcuts”, Retrieved from: <http://www.mobiletopsoft.com/board/1810/nokia-e61-tips-and-tricks-for-board-shortcuts.html> on Dec. 17, 2008., (Jan. 27, 2006),2 Pages.Applicant
- Ha, Rick et al., “Simkeys: An Efficient Keypad Configuration for Mobile Communications”, Retrieved from: <http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=01362557.>, (Nov. 2004),7 Pages.Applicant
- “Remapping the Keyboard”, Retrieved from: <http://publib.boulder.ibm.com/infocenter/hodhelp/v9r0/index.jsp?topic=/com.ibm.hod9.doc/help/assignkey.html> on Dec. 11, 2008., (Jul. 15, 2005),5 Pages.Applicant
- “Palm Treo 750 Cell Phone Review—Hardware”, Retrieved from: <http://www.wirelessinfo.com/content/palm-Treo-750-Cell-Phone-Review/Hardware.htm> on Dec. 11, 2008., (Mar. 17, 2007),4 Pages.Applicant
- “Keyboard (5)”, Retrieved from: <http://landru.uwaterloo.ca/cgi-bin/man.cgi?section=5&topic=keyboard> on Dec. 11, 2008., (Aug. 11, 1997),8 Pages.Applicant
- “Calc4M”, Retrieved from: <http://www.hellebo.com/Calc4M.html>, (Sep. 10, 2008),4 Pages.Applicant
- “MIDTB Tip Sheet: Book Courier”, Retrieved from: <http://www.midtb.org/tipsbookcourier.htm> on Dec. 11, 2008., (Sep. 26, 2005),6 Pages.Applicant
- “Freeware .mobi”, Retrieved from: <http://www.palmfreeware.mobi/download-palette.html>, (Oct. 9, 2001),2 pages.Applicant
- “Palette Extender 1.0.2”, Retrieved from: <http://palette-extender.en.softonic.com/symbian>, (Jan. 21, 2003),2 pages.Applicant
- Rice, Stephen V., et al., “A System for Searching Sound Palettes”, Retrieved from: <http://www.comparisonics.com/FindSoundsPalettePaper.pdf>, (Feb. 28-29, 2008),6 pages.Applicant
- “Multi-touch”, Retrieved from <http://en.wikipedia.org/wiki/Multi-touch#Microsoft—Surface>, (Apr. 17, 2009),8 pages.Applicant
- Wilson, Tracy V., “How the iPhone Works”, Retrieved from: <http://electronics.howstuffworks.com/iphone2.htm>, (Jan. 2007),9 pages.Applicant
- “DuoSense™ Multi-Touch Gestures”, Retrieved from: <http://www.n-trig.com/Data/Uploads/Misc/DuoSenseMTG—final.pdf>, (Jul. 2008),4 pages.Applicant
- Vallerio, Keith S., et al., “Energy-Efficient Graphical User Interface Design”, Retrieved from: <http://www.cc.gatech.edu/classes/AY2007/cs7470—fall/zhong-energy-efficient-user-interface.pdf>, (Jun. 10, 2004),13 Pages.Applicant
- Nordgren, Peder “Development of a Touch Screen Interface for Scania Interactor”, Retrieved from: <http://www.cs.umu.se/education/examina/Rapporter/PederNordgren.pdf>, (Apr. 10, 2007),67 Pages.Applicant
- “Elecont Quick Desktop 1.0.43”, Retrieved from: <http://handheld.softpedia.com/get/System-Utilities/Launcher-Applications/Elecont-Quick-Desktop-72131.shtml> on May 5, 2009., (Mar. 13, 2009),pp. 1-2.Applicant
- “Symbian Applications”, Retrieved from: <http://symbianfullversion.blogspot.com/2008—12—01—archive.html> on May 5, 2009., (Jan. 2009),51 Pages.Applicant
- Remond, Mickael “Mobile Marketing Magazine”, Retrieved from: <http://www.mobilemarketingmagazine.co.uk/mobile—social—networking/> on May 5, 2009., (Apr. 28, 2009),16 Pages.Applicant
- “Womma”, Retrieved from: <http://www.womma.org/blog/links/wom-trends/> on May 5, 2009 (2007),70 Pages.Applicant
- Dolcourt, Jessica “Webware”, Retrieved from: <http://news.cnet.com/webware/?categoryld=2010> on May 5, 2009, (Apr. 2009),13 Pages.Applicant
- “HTC Shows HTC Snap with Snappy Email Feature”, Retrieved from: <http://www.wirelessandmobilenews.com/smartphones/ on May 5, 2009>, (May 4, 2009),10 Pages.Applicant
- “Ask Web Hosting”, Retrieved from: <http://www.askwebhosting.com/story/18501/HTC—FUZE—From—ATandampT—Fuses—Fun—and—Function—With—the—One-Touch—Power—of—TouchFLO—3D.html> on May 5, 2009., (Nov. 11, 2008),3 pages.Applicant
- “Live Photo Gallery—Getting Started—from Camera to Panorama”, Retrieved from: <http://webdotwiz.spaces.live.com/blog/cns!2782760752B93233!1729.entry> on May 5, 2009., (Sep. 2008),7 Pages.Applicant
- Yang, Seungji et al., “Semantic Photo Album Based on MPEG-4 Compatible Application Format”, Retrieved from: <http://ieeexplore.ieee.org/stamp/stamp.jsp?arnumber=04146254.>, (2007),2 Pages.Applicant
- Mei, Tao et al., “Probabilistic Multimodality Fusion for Event Based Home Photo Clustering”, Retrieved from: <http://ieeexplore.ieee.org//stamp/stamp.jsp?tp=84arnumber=04036960.>, (2006),4 Pages.Applicant
- “Exclusive: Windows Mobile 7 to Focus on Touch and Motion Gestures”, Retrieved from: <http://anti-linux.blogspot.com/2008/08/exclusive-windows-mobile-7-to-focus-on.html> on May 6, 2009, (Aug. 1, 2008),pp. 1-14.Applicant
- “Mobile/UI/Designs/TouchScreen”, Retrieved from: <https://wiki.mozilla.org/Mobile/UI/Designs/TouchScreen> on May 6, 2009., (Feb. 2009),15 Pages.Applicant
- “Introduction to Windows Touch”, Retrieved from: <http://download.microsoft.com/download/a/d/f/adf1347d-08dc-41a4-9084-623b1194d4b2/Win7—touch.docx>, (Dec. 18, 2008),7 Pages.Applicant
- Terpstra, Brett “Beta Beat: Grape, a New Way to Manage Your Desktop Clutter”, Retrieved from: Beta Beat: Grape, a New Way to Manage Your Desktop Clutter on May 6, 2009., (Apr. 14, 2009),16 Pages.Applicant
- “Touch Shell Free”, Retrieved from: <http://www.pocketpcfreeware.mobi/download-touch-shell-free.html> on May 5, 2009., (Feb. 23, 2009),2 Pages.Applicant
- “Parallax Scrolling”, Retrieved from: <http://en.wikipedia.org/wiki/Parallax—scrolling> on May 5, 2009., (May 4, 2009),3 Pages.Applicant
- Steinicke, Frank et al., “Multi-Touching 3D Data: Towards Direct Interaction in Stereoscopic Display Environments coupled with Mobile Devices”, Retrieved from: <http://viscg.uni-muenster.de/publications/2008/SHSK08/ppd-workshop.-pdf.>, (Jun. 15, 2008),4 Pages.Applicant
- Mann, Richard et al., “Spectrum Analysis of Motion Parallax in a 3D Cluttered Scene and Application to Egomotion”, Retrieved from: <http://www.cs.uwaterloo.ca/˜mannr/snow/josa-mann-langer.pdf.>, (Sep. 2005),15 Pages.Applicant
- “Keyboard Shortcuts”, Retrieved from: <http://www.pctoday.com/editorial/article.asp?article=articles%2F2005%2Ft0311%2F26t11%2F26t11.asp> on Aug. 3, 2009., (Nov. 2005),5 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2010/028699, (Oct. 4, 2010),10 pages.Applicant
- “PCT Search Report and Written Opinion”, Application No. PCT/US2010/028555, (Oct. 12, 2010),10 pages.Applicant
- Raghaven, Gopal et al., “Model Based Estimation and Verification of Mobile Device Performance”, Retrieved from http://alumni.cs.ucsb.edu/˜raimisl/emsoft04—12.pdf., (Sep. 27-29, 2004),10 Pages.Applicant
- Reed, Brad “Microsoft Demos Windows Mobile 6.1 at CTIA”, Retrieved from: <http://www.networkworld.com/news/2008/040208-ctia-microsoft-windows-mobile.html> on Jul. 18, 2008., (Apr. 2, 2008), 1 page.Applicant
- Singh, Kundan et al., “CINEMA: Columbia InterNet Extensible Multimedia Architecture”, Retrieved from http://www1.cs.columbia.edu/˜library/TR-repository/reports-2002/cucs-011-02.pdf, (Sep. 3, 2002),83 Pages.Applicant
- Kcholi, Avi “Windows CE .NET Interprocess Communication”, Retrieved from http://msdn.microsoft.com/en-us/library/ms836784.aspx on Jul. 7, 2008., (Jan. 2004),15 Pages.Applicant
- Gao, Rui “A General Logging Service for Symbian based Mobile Phones”, Retrieved from: <http://www.nada.kth.se/utbildning/grukth/exjobb/rapportlistor/2007/rapporter07/gao—rui—07132.pdf.> on Jul. 17, 2008, (Feb. 2007),pp. 1-42.Applicant
- “Oracle8i Application Developer's Guide—Advanced Queuing Release 2 (8.1.6)”, Retrieved from: http://www.cs.otago.ac.nz/oradocs/appdev.817/a76938/adq01in5.htm on May 6, 2009., 8 pages.Applicant
- “Content-Centric E-Mail Message Analysis in Litigation Document Reviews”, Retrieved from: http://www.busmanagement.com/article/Issue-14/Data-Management/Content-Centric-E-Mail-Message-Analysis-in-Litigation-Document-Reviews/., (May 6, 2009),4 Pages.Applicant
- Mao, Jeng “Comments of Verizon Wireless Messaging Services, LLC”, Retrieved from: http://www.ntia.doc.gov/osmhome/warnings/comments/verizon.htm on May 6, 2009, 5 Pages.Applicant
- “Oracle8i Concepts Release 8.1.5”, Retrieved from: http://www.cs.umbc.edu/help/oracle8/server.815/a67781/c16queue.htm on May 6, 2009., 10 Pages.Applicant
- “Oracle8i Application Developer's Guide—Advanced Queuing”, Retrieved from: http://www.cs.umbc.edu/help/oracle8/server.815/a68005/03—adq1i.htm on May 6, 2009., 29 Pages.Applicant
- “International Search Report”, Mailed Date: Nov. 9, 2010, Application No. PCT/US2010/028553, Filed Date: Mar. 24, 2010, pp. 9.Applicant
- “Final Office Action”, U.S. Appl. No. 12/413,977, (Nov. 17, 2011),16 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/433,667, (Sep. 13, 2011),17 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/469,458, (Nov. 17, 2011),15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/244,545, (Aug. 17, 2011),15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/413,977, (Jul. 19, 2011),17 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/414,382, (Jul. 26, 2011),9 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/414,455, (Aug. 29, 2011),8 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/414,458, (Jul. 6, 2011),8 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/414,476, (Aug. 3, 2011),21 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/433,605, (Jun. 24, 2011),10 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/433,667, (Jun. 7, 2011),15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/469,419, (Nov. 9, 2011),15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/469,458, (Jul. 1, 2011),15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/469,480, (Sep. 22, 2011),14 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/470,558, (Nov. 22, 2011),9 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/484,799, (Aug. 11, 2011),12 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/414,458, (Oct. 31, 2011),2 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/414,458, (Aug. 10, 2011),6 pages.Applicant
- “Advisory Action”, U.S. Appl. No. 12/414,382, (Jan. 20, 2012),3 pages.Applicant
- “Advisory Action”, U.S. Appl. No. 12/433,605, (Apr. 5, 2012),3 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/244,545, (Dec. 7, 2011),16 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/414,382, (Dec. 23, 2011),7 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/414,476, (Dec. 1, 2011),20 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/433,605, (Feb. 3, 2012),11 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/469,480, (Feb. 9, 2012),17 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/560,081, (Mar. 14, 2012),16 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/244,545, (Mar. 27, 2012),18 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/433,667, (Feb. 3, 2012),16 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/484,845, (Dec. 7, 2011),16 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/560,081, (Dec. 7, 2011),16 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/414,382, (Apr. 4, 2012),4 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/414,455, (Jan. 4, 2012),4 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/414,458, (Nov. 29, 2011),2 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/470,558, (Apr. 2, 2012),7 pages.Applicant
- Beiber, Gerald et al., “Screen Coverage: A Pen-Interaction Problem for PDA's and Touch Screen Computers”, In Proceedings of ICWMC 2007,(Mar. 2007),6 pages.Applicant
- La, Nick “Parallax Gallery”, Available at <http://webdesignerwall.comtutorials/parallax-gallery/comment-page-1>,(Apr. 25, 2008),16 pages.Applicant
- Roberts, Neil “Touching and Gesturing on the iPhone”, Available at <http://www.sitepen.com/blog/2008/07/10/touching-and-gesturing-on-the-iphone/comments-pare-1>,(Jul. 10, 2008),16 pages.Applicant
- Wyatt, Paul “/Flash/the art of parallax scrolling”, .net Magazine,(Aug. 1, 2007),pp. 74-76.Applicant
- “Extended European Search Report”, European Patent Application No. 09818253.8, (Apr. 10, 2012),7 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/484,799, (Apr. 30, 2012),13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/469,419, (May 23, 2012),13 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/484,845, (Mar. 16, 2012),5 pages.Applicant
- “PCT Search Report”, Application Serial No. PCT/US2009/061864, (May 14, 2010), 10 pages.Applicant
- “Final Office Action”, U.S. Appl. No. 12/244,545, (Sep. 7, 2012), 23 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/413,977, (Jul. 20, 2012), 18 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/469,458, (Sep. 21, 2012), 14 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/480,969, (Aug. 7, 2012), 15 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/484,799, (Aug. 7, 2012), 13 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 13/492,495, (Sep. 17, 2012), 8 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/470,558, (Aug. 23, 2012), 2 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/414,476, (Nov. 9, 2012), 22 pages.Applicant
- “Non-Final Office Action”, U.S. Appl. No. 12/469,480, (Oct. 17, 2012), 16 pages.Applicant
- “Notice of Allowance”, U.S. Appl. No. 12/484,799, (Oct. 22, 2012), 10 pages.Applicant