throbber
as) United States
`a2) Patent Application Publication (0) Pub. No.: US 2012/0127098 Al
`
` Lazaridis etal. (43) Pub. Date: May24, 2012
`
`
`US 20120127098A1
`
`(54) PORTABLE ELECTRONIC DEVICE AND
`METHOD OF CONTROLLING SAME
`
`(75)
`
`Inventors:
`
`MihalLazaridis, Waterloo (CA);
`Daniel Thomas Dodge, Ottawa
`(CA); Donald James Lindsay,
`Mountain View, CA (US)
`
`Publication Classification
`
`(51)
`
`Int. Cl.
`GO6F 3/041
`
`(2006.01)
`
`(52) US. C0. ceesesssssssssesnsessssenssesnseecessseennee 345/173
`
`(73) Assignees:
`
`QNX SOFTWARE SYSTEMS
`ABSTRACT
`(57)
`LIMITED,Ottawa (CA);
`A methodincludes displaying information associated with a
`RESEARCH IN MOTION
`sas
`wes
`:
`.
`LIMITED,Waterloo (CA)
`first application on a touch-sensitive display, detecting a
`touch on a touch-sensitive display and determining touch
`13/243,613
`(21) Appl. No.:
`; attributes, determining when the touchisafirst gesture type
`
`Filed:
`(22)
`Sep. 23, 2011
`based on the touch attributes, and when the touch is deter-
`+
`as
`mined to be the first gesture type, forwarding information
`Related U.S. Application Data
`related to the touch to a second application, otherwise for-
`(60) Provisional application No. 61/386,219,filed on Sep.
`warding the informationrelated to the touch to thefirst appli-
`cation.
`24, 2010.
`
`402
`
`DISPLAY INFORMATION
`ASSOCIATED WITH APPLICATION
`
`404
`
`
`
`UTILIZE TOUCH DATA WITH
`APPLICATION
`
`406
`
`META-NAVIGATION
`GESTURE?
`
`
`
`
`
`UTILIZE TOUCH DATA WITH
`FURTHER APPLICATION
`
`410
`
`1
`
`APPLE 1106
`
`APPLE 1106
`
`1
`
`

`

`Patent Application Publication May 24,2012 Sheet 1 of 5
`
`US 2012/0127098 Al
`
`100
`
`134
`
`OTHER
`SUBSYSTEMS
`
`’
`
`132
`
`,
`
`SHORT RANGE
`COMMUNICATIONS
`
`3
`
`9
`
`SPEAKER
`
`|
`
`DATA PORT
`
`AUXILIARY I/O
`
`FORCE SENSOR
`
`1
`
`.
`128
`
`126
`
`124
`
`N N)
`
`i:s CONTROLLER
`
`146
`
`We
`
`OPERATING
`SYSTEM
`
`110
`
`PROGRAMS
`
`108
`
`ACCELEROMETERS
`
`i
`MEMORY
`
`-
`
`oy
`
`DECODER
`
`|(“7>
`
`106
`
`116!
`TI
`148
`
` OVERLAY 114)COMMUNICATION _) [OVERLAY_SUBSYSTEM
`
`
` DISPLAY
`t-P)
`04
`S 1112}
`102
`Nis
`
`150
`
`SIM/RUIM
`
`138
`
`POWER
`SOURCE
`
`142
`
`FIG. 1
`
`2
`
`

`

`Patent Application Publication May 24,2012 Sheet 2 of 5
`
`US 2012/0127098 Al
`
`202
`
`204
`
`206
`
`212
`
`208
`
`210
`
`FIG. 2
`
`—
`
`iO
`
`3
`
`

`

`Patent Application Publication May 24,2012 Sheet 3 of 5
`
`US 2012/0127098 Al
`
`202
`
`
`
`OO
`
`204
`
`N|\___9 PORSESS
` SLIDELLLLLLLLEMEELEELELEN\\NN
`
`304
`
`FIG. 3
`
`4
`
`

`

`Patent Application Publication May 24,2012 Sheet 4 of 5
`
`US 2012/0127098 Al
`
` 402
`
`ASSOCIATED WITH APPLICATION
`
`404
`
` DISPLAY INFORMATION
`
`UTILIZE TOUCH DATA WITH
`APPLICATION
`
`406
`
`META-NAVIGATION
`GESTURE?
`
`
`
`
`
`UTILIZE TOUCH DATA WITH
`FURTHER APPLICATION
`
`410
`
`FIG. 4
`
`5
`
`

`

`Patent Application Publication
`
`May24, 2012 Sheet 5 of 5
`
`US 2012/0127098 Al
`
`512
`
`NOTIFICATIONS
`
`APPLICATION
`SETTINGS
`504
`
`10
`
`08
`
`PREVIOUS
`APPLICATION
`
`506
`
`306
`
`4
`
`CURRENT
`APPLICATION
`502
`
`512
`
`NOTIFICATIONS
`
`312
`
`508
`
`NEXT APPLICATION
`
`316
`
` Sat 1:12pm
`
`514
`
`510
`
`314
`
`302
`
`ROOT NAVIGATOR
`
`FIG. 5
`
`
`
`(00(JOU(JOU(JOU
`
`514
`
`
`
`
`Sat 1:12pm
`
`
`
`
`6
`
`

`

`US 2012/0127098 Al
`
`May24, 2012
`
`PORTABLE ELECTRONIC DEVICE AND
`METHOD OF CONTROLLING SAME
`
`CROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`[0001] This application claims the benefit of U.S. Provi-
`sional Patent Application 61/386,219, filed Sep. 24, 2010, the
`entire content of which is incorporated herein by reference.
`
`FIELD OF TECHNOLOGY
`
`[0002] The present disclosure relates to electronic devices
`including,but not limitedto, portable electronic devices hav-
`ing touch-sensitive displays.
`
`BACKGROUND
`
`including portable electronic
`[0003] Electronic devices,
`devices, have gained widespread use and may providea vari-
`ety offunctions including,for example, telephonic, electronic
`messaging and other personal information manager (PIM)
`application functions. Portable electronic devices include
`several types of devices including mobile stations such as
`simple cellular telephones, smart telephones, Personal Digi-
`tal Assistants (PDAs), tablet computers, and laptop comput-
`ers, with wireless network communications or near-field
`communications connectivity such as Bluetooth® capabili-
`ties.
`
`Portable electronic devices such as PDAs, ortablet
`[0004]
`computers are generally intended for handheld use and ease
`of portability. Smaller devices are generally desirable for
`portability. A touch-sensitive display, also knownas a touch-
`screen display, is particularly useful on handheld devices,
`which are small and have limited space for user input and
`output. The information displayed on the touch-sensitive dis-
`play may be modified depending on the functions and opera-
`tions being performed.
`[0005]
`Improvementsin electronic devices with touch-sen-
`sitive displays are desirable.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`[0006] Embodiments of the present disclosure will now be
`described, by way of example only, with reference to the
`attached Figures, wherein:
`[0007]
`FIG. 1 is a block diagram of a portable electronic
`device in accordance with an example embodiment;
`[0008]
`FIG. 2 is a front view of an example of a portable
`electronic device;
`[0009]
`FIG. 3 illustrates examples of touches on the por-
`table electronic device of FIG.2;
`[0010]
`FIG. 4 is a flowchart illustrating a method of con-
`trolling the portable electronic device in accordance with the
`disclosure; and
`[0011]
`FIG.5 illustrates examples of associations between
`meta-navigation gestures and information from applications.
`
`DETAILED DESCRIPTION
`
`[0012] The following describes an electronic device and a
`methodthat includes displaying information associated with
`a first application on a touch-sensitive display, detecting a
`touch on a touch-sensitive display and determining touch
`attributes, determining whenthe touchis a first gesture type
`based on the touch attributes, and when the touch is deter-
`mined to be the first gesture type, forwarding information
`
`related to the touch to a second application, otherwise for-
`warding the informationrelated to the touchto the first appli-
`cation.
`
`For simplicity and clarity of illustration, reference
`[0013]
`numerals may be repeated amongthe figures to indicate cor-
`responding or analogous elements. Numerousdetails are set
`forth to provide an understanding of the embodiments
`described herein. The embodiments may be practiced without
`these details. In other instances, well-known methods, proce-
`dures, and components have not been described in detail to
`avoid obscuring the embodiments described. The description
`is not to be consideredaslimited to the scope of the embodi-
`ments described herein.
`
`[0014] The disclosure generally relates to an electronic
`device, such as a portable electronic device. Examples of
`portable electronic devices include wireless communication
`devices such as pagers, mobile or cellular phones, smart-
`phones, wireless organizers, PDAs, notebook computers, net-
`book computers, tablet computers, and so forth. The portable
`electronic device may also be a portable clectronic device
`without wireless communication capabilities. Examples
`include handheld electronic game device, digital photograph
`album, digital camera, notebook computers, netbook com-
`puters, tablet computers, or other device.
`[0015] A block diagram of an example of a portable elec-
`tronic device 100 is shown in FIG.1. The portable electronic
`device 100 includes multiple components, suchas a processor
`102 that controls the overall operation of the portable elec-
`tronic device 100. The portable electronic device 100 pres-
`ently described optionally includes a communication sub-
`system 104 and a short-range communications 132 module to
`perform various communication functions, including data
`and voice communications. Data received by the portable
`electronic device 100 is decompressed and decrypted by a
`decoder 106. The communication subsystem 104 receives
`messages from and sends messages to a wireless network
`150. The wireless network 150 may be any type of wireless
`network,including, butnot limited to, data wireless networks,
`voice wireless networks, and networks that support both
`voice and data communications. A power source 142, such as
`one or more rechargeable batteries or a port to an external
`power supply, powers the portable electronic device 100.
`[0016] The processor 102 interacts with other components,
`such as Random Access Memory (RAM) 108, memory 110,
`a display 112 with a touch-sensitive overlay 114 operably
`connected to an electronic controller 116 that together com-
`prise a touch-sensitive display 118, one or more actuators
`120, one or more force sensors 122, an auxiliary input/output
`(I/O) subsystem 124, a data port 126, a speaker 128, a micro-
`phone 130, short-range communications 132, and other
`device subsystems 134. User-interaction with a graphical
`user interface is performed through the touch-sensitive over-
`lay 114. The processor 102 interacts with the touch-sensitive
`overlay 114 via the electronic controller 116. Information,
`such as text, characters, symbols, images, icons, and other
`items that may be displayed or rendered on a portable elec-
`tronic device, is displayed on the touch-sensitive display 118
`via the processor 102. The processor 102 mayinteract with an
`orientation sensor such as an accelerometer 136 to detect
`direction of gravitational forces or gravity-induced reaction
`forces so as to determine, for example, the orientation of the
`portable electronic device 100.
`[0017]
`‘To identify a subscriber for network access, the por-
`table electronic device 100 uses a Subscriber Identity Module
`
`7
`
`

`

`US 2012/0127098 Al
`
`May24, 2012
`
`or a Removable User Identity Module (SIM/RUIM)card 138
`for communication with a network, such as the wireless net-
`work 150. Alternatively, user identification information may
`be programmed into memory 110.
`[0018] The portable electronic device 100 includes an oper-
`ating system 146 and software programs or components 148
`that are executed by the processor 102 andare typically stored
`in a persistent, updatable store such as the memory 110.
`Additional applications or programs may be loaded onto the
`portable electronic device 100 through the wireless network
`150, the auxiliary I/O subsystem 124, the data port 126, the
`short-range communications subsystem 132, or any other
`suitable subsystem 134.
`[0019] A received signal, such as a text message, an e-mail
`message, or web page download,is processed by the commu-
`nication subsystem 104 andinput to the processor 102. The
`processor 102 processes the received signal for outputto the
`display 112 and/or to the auxiliary I/O subsystem 124. A
`subscriber may generate data items, for example e-mail mes-
`sages, which may be transmitted over the wireless network
`150 through the communication subsystem 104, for example.
`[0020] The touch-sensitive display 118 may be anysuitable
`touch-sensitive display, such as a capacitive,resistive, infra-
`red, surface acoustic wave (SAW) touch-sensitive display,
`strain gauge, optical imaging, dispersive signal technology,
`acoustic pulse recognition, and so forth, as known intheart.
`In the presently described example embodiment, the, the
`touch-sensitive display 118 is a capacitive touch-sensitive
`display which includes a capacitive touch-sensitive overlay
`114. The overlay 114 may be an assembly of multiple layers
`in a stack which may include, for example, a substrate, a
`ground shield layer, a barrier layer, one or more capacitive
`touch sensor layers separated by a substrate or other barrier,
`and a cover. The capacitive touch sensor layers may be any
`suitable material, such as patterned indium tin oxide (ITO).
`[0021] The display 112 of the touch-sensitive display 118
`includes a display area in which information may be dis-
`played, and a non-display area extending around the periph-
`ery of the display area. Information is not displayed in the
`non-display area, which is utilized to accommodate, for
`example, electronic traces or electrical connections, adhe-
`sives or other sealants, and/or protective coatings around the
`edges of the display area.
`[0022] One or more touches, also known as touch contacts
`or touch events, may be detected by the touch-sensitive dis-
`play 118. The processor 102 may determineattributes of the
`touch, including a location of a touch. Touch location data
`may include an area of contact or a single point of contact,
`such as a pointat or near a center ofthe area of contact, known
`as the centroid. A signal is provided to the controller 116 in
`response to detection of a touch. A touch may be detected
`from any suitable object, such as a finger, thumb, appendage,
`or other items, for example, a stylus, pen, or other pointer,
`depending on the nature of the touch-sensitive display 118.
`Thelocation of the touch movesas the detected object moves
`during a touch. The controller 116 and/or the processor 102
`may detect a touch by any suitable contact member on the
`touch-sensitive display 118. Similarly, multiple simultaneous
`touches, are detected.
`[0023] One or moregestures are also detected by the touch-
`sensitive display 118. A gesture is a particular type of touch
`on a touch-sensitive display 118 that beginsat an origin point
`and continues to an end point. A gesture may be identified by
`attributes of the gesture, including the origin point, the end
`
`point, the distance travelled, the duration,the velocity, and the
`direction, for example. A gesture may be long or short in
`distance and/or duration. Two points of the gesture may be
`utilized to determine a direction of the gesture.
`[0024] An example ofa gesture is a swipe (also known as a
`flick). A swipe has a single direction. The touch-sensitive
`overlay 114 may evaluate swipes with respect to the origin
`point at which contact is initially made with the touch-sensi-
`tive overlay 114 and the end point at which contact with the
`touch-sensitive overlay 114 ends rather than using each of
`location or pointof contact over the duration of the gesture to
`resolve a direction.
`
`[0025] Examples of swipes include a horizontal swipe, a
`vertical swipe, and a diagonal swipe. A horizontal swipe
`typically comprises an origin point towards the left or right
`side of the touch-sensitive overlay 114 to initialize the ges-
`ture, a horizontal movementof the detected object from the
`origin point to an end point towards the rightorleft side ofthe
`touch-sensitive overlay 114 while maintaining continuous
`contact with the touch-sensitive overlay 114, and a breaking
`of contact with the touch-sensitive overlay 114. Similarly, a
`vertical swipe typically comprises an origin point towards the
`top or bottom of the touch-sensitive overlay 114 to initialize
`the gesture, a horizontal movement of the detected object
`from the origin point to an end point towards the bottom or top
`ofthe touch-sensitive overlay 114 while maintaining continu-
`ous contact with the touch-sensitive overlay 114, and a break-
`ing of contact with the touch-sensitive overlay 114.
`[0026]
`Swipes can be of various lengths, can be initiated in
`various places on the touch-sensitive overlay 114, and need
`not span the full dimension of the touch-sensitive overlay
`114. Inaddition, breaking contact ofa swipe can be gradualin
`that contact with the touch-sensitive overlay 114is gradually
`reduced while the swipe is still underway.
`[0027] Meta-navigation gestures may also be detected by
`the touch-sensitive overlay 114. A meta-navigation gestureis
`a gesture that has an origin point that is outside the display
`area of the touch-sensitive overlay 114and that moves to a
`position on the display area of the touch-sensitive display.
`Otherattributes ofthe gesture may be detected and be utilized
`to detect the meta-navigation gesture. Meta-navigation ges-
`tures may also include multi-touch gestures in which gestures
`are simultaneous or overlap in time and at least one of the
`toucheshas an origin pointthat is outside the display area and
`movesto a position on the display area of the touch-sensitive
`overlay 114. Thus, two fingers may be utilized for meta-
`navigation gestures. Further, multi-touch meta-navigation
`gestures may be distinguished from single touch meta-navi-
`gation gestures and mayprovide additional or further func-
`tionality.
`In some example embodiments, an optional force
`[0028]
`sensor 122 or force sensors is disposed in any suitable loca-
`tion, for example, between the touch-sensitive display 118
`and a back of the portable electronic device 100 to detect a
`force imparted by a touch on the touch-sensitive display 118.
`The force sensor 122 maybe a force-sensitive resistor, strain
`gauge, piezoelectric or piezoresistive device, pressure sensor,
`or other suitable device. Force as utilized throughout the
`specification refers to force measurements, estimates, and/or
`calculations, such as pressure, deformation, stress, strain,
`force density, force-area relationships, thrust, torque, and
`other effects that include force or related quantities.
`[0029]
`Force information related to a detected touch may
`be utilized to select information, such as information associ-
`
`8
`
`

`

`US 2012/0127098 Al
`
`May24, 2012
`
`ated with a location of a touch. For example, a touch that does
`not meet a force threshold may highlight a selection option,
`whereas a touch that meets a force threshold may select or
`input that selection option. Selection options include, for
`example, displayed or virtual keys of a keyboard; selection
`boxes or windows,e.g., “cancel,” “delete,” or “unlock”; func-
`tion buttons, such as play or stop on a music player; and so
`forth. Different magnitudes of force may be associated with
`different functions or input. For example, a lesser force may
`result in panning, and a higher force mayresult in zooming.
`[0030] A front view of an example of the portable elec-
`tronic device 100 is shown in FIG.2. The portable electronic
`device 100 includes a housing 202 that encloses components
`such as shown in FIG.1. The housing 202 mayinclude a back,
`sidewalls, and a front 204 that frames the touch-sensitive
`display 118.
`[0031]
`Inthe shown example of FIG.2, the touch-sensitive
`display 118 is generally centered in the housing 202 suchthat
`a display area 206 of the touch-sensitive overlay 114 is gen-
`erally centered with respect to the front 204 of the housing
`202. The non-displayarea 208 of the touch-sensitive overlay
`114 extends around the display area 206. In the presently
`described embodiment, the width of the non-display area is 4
`mm.
`
`[0035] Gestures that have an origin point in the buffer
`region 212, for example, may be identified as non-meta navi-
`gation gestures. Optionally, data from such gestures may be
`utilized by an application as a non-meta navigation gesture.
`Alternatively, data from such gestures may be discarded such
`that touchesthat havean origin point onthe buffer region 212
`are not utilized as input at the portable electronic device 100.
`[0036]
`FIG.3 illustrates examples of touches on the touch-
`sensitive display 118. The buffer region 212 is illustrated in
`FIG. 3 by hash markings for the purpose of explanation. As
`indicated, the buffer region 212 maynotbevisible to the user.
`For the purpose of explanation, touches are illustrated by
`circles at their points of origin. Arrows extending from the
`circles illustrate the paths of the touches that are gestures.
`[0037] The touch 302 begins at the origin point outside the
`boundary 210 andthe outside the buffer region 212. The path
`of the touch 302 crosses the buffer region 212 and the bound-
`ary 210 andis therefore identified as a meta-navigation ges-
`ture. Similarly, the touches 304, 306, 308, 310, 312, 314, 316
`each have origin points outside the boundary 210 and the
`buffer region 212 and their paths cross the buffer region 212
`and the boundary 210. Each ofthe touches 304, 306, 308, 310,
`312, 314, 316 is therefore identified as a meta-navigation
`gesture. The touch 318, however, has an origin pointthatfalls
`within the buffer region 212 and the touch 318 is therefore not
`identified as a meta-navigation gesture. The touch 320 begins
`at an origin point outside the boundary 210 and the buffer
`region 212. The path ofthe touch 320, however, does not cross
`the boundary 210 andis therefore not identified as a meta-
`navigation gesture. The touch 322 also has an origin point
`outside the boundary 210 and the buffer region 212 but is not
`a gesture and therefore does notcross the boundary 210 andis
`not identified as a meta-navigation gesture.
`[0038] A flowchart illustrating a method of controlling an
`electronic device, such as the portable electronic device 100,
`is shown in FIG. 4. The method maybecarried out by com-
`puter-readable code executed, for example, by the processor
`102. Coding of software for carrying out such a method is
`within the scope of a person of ordinary skill in the art given
`the present description. The method may contain additional
`or fewer processes than shown and/or described, and may be
`performed in a different order. Computer-readable code
`executable by at least one processor ofthe portable electronic
`device to perform the method may be stored in a computer-
`readable medium, such as a non-transitory computer-read-
`able medium.
`
`For the purpose of the present example, the touch-
`[0032]
`sensitive overlay 114 extends to cover the display area 206
`and the non-display area 208. Toucheson the display area 206
`may be detected and, for example, may be associated with
`displayed selectable features. Touches on the non-display
`area 208 may be detected, for example, to detect a meta-
`navigation gesture. Alternatively, meta-navigation gestures
`may be determined by both the non-display area 208 and the
`display area 206. The density of touch sensors may differ
`from the display area 206 to the non-display area 208. For
`example, the density of nodes in a mutual capacitive touch-
`sensitive display, or density of locations at which electrodes
`ofone layer cross over electrodes of anotherlayer, may differ
`between the display area 206 and the non-display area 208.
`[0033] Gestures received on the touch-sensitive display
`118 maybe analyzed based ontheattributes to discriminate
`between meta-navigation gestures and other touches, or non-
`meta navigation gestures. Meta-navigation gestures may be
`identified when the gesture crosses over a boundary near a
`periphery ofthe display 112, such as a boundary 210 between
`the display area 206 and the non-display area 208. In the
`example of FIG. 2, the origin point of a meta-navigation
`[0039] Theprocess maybe carried out in any suitable appli-
`gesture may be determined utilizing the area of the touch-
`cation, such as, a homescreen application, an email applica-
`sensitive overlay 114 that covers the non-display area 208.
`tion, a text messaging application, a calendar application, a
`tasks application, an address book application, a web browser
`[0034] A buffer region 212 or band that extends aroundthe
`application, or any other suitable application. Information
`boundary 210 between the display area 206 and the non-
`from the application, referred to as the first application, is
`display area 208 maybeutilized such that a meta-navigation
`displayed on the touch-sensitive display 118 of the portable
`gesture is identified when a touch hasan origin point outside
`electronic device 100 at 402. Whenatouchis detected at 404,
`the boundary 210 and the buffer region 212 and crosses
`through the buffer region 212 and over the boundary 210 to a
`the process continues at 406 and a determination is made
`point inside the boundary 210. Although illustrated in FIG.2,
`whether or not the touch is a meta-navigation gesture. The
`determination is made basedonthe attributes of the touch as
`the buffer region 212 may notbe visible. Instead, the buffer
`region 212 may be a region around the boundary 210 that
`described above. In response to determiningthat the touch is
`extends a width that is equivalent to a predetermined number
`not a meta-navigation gesture, which may be a tap on the
`of pixels, for example. Alternatively, the boundary 210 may
`touch-sensitive display 118 or may be a non-meta navigation
`extend a predetermined number of touch sensors or may
`gesture, the touch data is utilized in association with the first
`extend a predetermined distance from the display area 206.
`application for which informationis displayed on the touch-
`The boundary 210 maybe a touch-sensitive region or may be
`sensitive display 118 at the time the gesture is received, at
`a region in which touchesare not detected.
`408. In responseto identifying the touch as a meta-navigation
`
`9
`
`

`

`US 2012/0127098 Al
`
`May24, 2012
`
`portion of the information of the previous application 506
`gesture at 406, the touch data is utilized in a second applica-
`tion and information associated with the second, or with a
`may be displayedinathin sliver adjacent the edge or edges of
`further application, is displayed on the touch-sensitive dis-
`the display area 206 during the gesture andpriorto replace-
`play 118 at 410. The information associated with the second
`mentof the information associated with the current applica-
`application may be overlaid on the information associated
`tion 502. The information associated with the current appli-
`with the first application, for example,to facilitate navigation
`cation 502 may be replaced with the previous or next
`back to the information associated with the first application.
`application 508 as the gesture continues. In an alternative
`Alternatively, the information associated with the second
`example, a portion of the information of the previous appli-
`application may include, for example, information from a
`cation 506 or a portion of the information for the next appli-
`system level navigation interface, a configuration interface, a
`cation 508 may be displayedin a thinsliver adjacent the edges
`notification interface, a status interface, a menu interface, or
`ofthe display area 206 in responseto a receipt ofa first lateral
`information associated with any otherinterface.
`gesture. In this example, a swipe within the thin sliver may
`cause scrolling of the next and last applications in a list. A
`[0040] Referring again to FIG.3, the touches 302, 304, 306,
`second lateral meta-navigation gesture such as the gestures
`308, 310, 312, 314, 316 identified as meta-navigation ges-
`304, 306 may beutilized to cause the information associated
`tures may each be associated with information from an appli-
`with the current application 502, which information is
`cation suchthatattributes ofthe meta-navigation gesture such
`reduced in size, to be replaced.
`as the origin point, maybe utilized to determine whichappli-
`[0044] The meta-navigation gesture 308, which originates
`cation the meta-navigation gesture is associated with. FIG. 5
`near a top, center of the touch-sensitive display 118 and
`illustrates examples of associations between meta-navigation
`follows a generally vertical path, causes the information asso-
`gestures and information from applications, other than the
`ciated with the current application 502 to be replaced with
`application associated with the information displayed on the
`information associated with an applications settings applica-
`touch-sensitive display 118 at the timethe gestureis received.
`tion 504.
`The relationships shown in FIG. 5 are shownforillustrative
`purposes only andare interchangeable. Further applications
`and alternative associations may beutilized. Further applica-
`tions and alternative associations may be utilized. The terms
`top, bottom,right, andleft are utilized herein for the purpose
`of providing a reference and refer to an area of the portable
`electronic device 100 relative to the orientation in which the
`information associated with the application is displayed.
`[0041] The meta-navigation gesture 302, which originates
`near a bottom, center of the touch-sensitive display 118 and
`follows a generally vertical path in the orientation in which
`the information from a current application 502 is displayed,
`causes a homescreen associated with a root-navigation appli-
`cation 510 to replace the information associated with the
`current application 502. The homescreen includesa carousel
`showing the currently active applications indicated in a top
`portion of the display. Accordingly, currently active apps are
`shown in a browsable carousel in the top portion of the Home
`Screen. The carousel is located at a top portion of the home-
`screen. In the present example, the top portion utilizes only
`about 4 of the home screen, and application icons for non-
`active applications are provided at the bottom portion of the
`homescreen for ease of selection.
`
`[0045] The meta-navigation gesture 310, which originates
`near a top, left corner of the touch-sensitive display 118,
`causes information associated with a notification application
`512 to be tiled over the information associated with the cur-
`rent application 502. Similarly, the meta-navigation gesture
`312, which originates near a top, right corner of the touch-
`sensitive display 118, causes information associated with the
`notification application 512 to be tiled over the information
`associated with the current application 502.
`[0046] The meta-navigation gesture 314, which originates
`near a bottom, left corner of the touch-sensitive display 118,
`causes information associated with a status application 514 to
`be tiled over the information associated with the current
`
`[0042] The meta-navigation gesture 304, which originates
`near a left, center of the touch-sensitive display 118 and
`follows a generally lateral path, causes the information asso-
`ciated with the current application 502 to be replaced with
`information associated with a previous application 506,
`which maybe a previous application in a grouping or may be
`an application associated with information previously dis-
`played. The meta-navigation gesture 306, which originates
`near a right, center of the touch-sensitive display 118 and
`follows a generally lateral path, causes the information asso-
`ciated with the current application 502 to be replaced with
`information associated with a next application 508, which
`may be a next application in a grouping.
`[0043] The lateral gesture from either the left side or the
`right side of the touch-sensitive display 118 may cause the
`information associated with the current application 502 to be
`reducedin size to provide a visual cue of other active appli-
`cations prior to replacing the information with the previous
`application 506 or the next application 508. For example, a
`
`application 502. Similarly, the meta-navigation gesture 316,
`which originates near a bottom, right corner of the touch-
`sensitive display 118, causes information associated with the
`status application 514 to be tiled over the information asso-
`ciated with the current application 502.
`[0047] The present disclosureis not limited to identifying
`meta-navigation gestures utilizing a touch-sensitive overlay
`that extends over the non-display area. Meta-navigation ges-
`tures may be detected based on, for example,the first detected
`touch location at a margin of the touch-sensitive overlay,
`which maybe at amargin ofthe displayable area, and, option-
`ally, based on the gesture speedor direction whenthe touchis
`detected or path traversed by the gesture. Identification of
`meta-navigation gestures mayalso be carried out utilizing a
`heuristic algorithm based on touchattributes and responsive
`to touch attributes such as one or more of the origin point,
`speed, direction, distance and path of the gesture.
`[0048] Optionally,
`the electronic device may include a
`touch-sensitive frame of the housing or a touch-sensitive
`bezel circumscribing the touch-sensitive overlay. Meta-navi-
`gation gestures may be identified based on an origin point
`detected on the touch-sensitive frame or bezel.
`
`Further, the boundary that is crossed by a meta-
`[0049]
`navigation gesture is not limited to the boundary between the
`display area and the non-display area of the touch-sensitive
`display. Other suitable boundaries may be utilized and may
`include a region or band along a margin ofthe touch-sensitive
`overlay, a predeterminedline, or lines on the touch-sensitive
`
`10
`
`10
`
`

`

`US 2012/0127098 Al
`
`May24, 2012
`
`5. The method according to claim 3, wherein the boundary
`display 118, or the boundary wherethe bezel or frame of the
`
`electronic device meets the touch-sensitive display. comprises a boundary betweenadisplay area and non-display
`[0050] Thus, identification of meta-navigation gestures is
`area of the touch-sensitive display.
`notlimitedto electronic devices with touch-sensitive displays
`6. The method according to claim 1, wherein determining
`that include a touch-sensitive overlay that covers the non-
`comprises determining that the touch is a meta-navigation
`display area of the display. Identification of meta-navigation
`gesture based on gesture speed whenthe touchis detected.
`gestures maybecarried out utilizing other electronic devices.
`7

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket