Classifications

• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
  • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
  • G06F1/16—Constructional details or arrangements
  • G06F1/1613—Constructional details or arrangements for portable computers
  • G06F1/1633—Constructional details or arrangements of portable computers not specific to the type of enclosures covered by groups G06F1/1615 - G06F1/1626
  • G06F1/1684—Constructional details or arrangements related to integrated I/O peripherals not covered by groups G06F1/1635 - G06F1/1675
  • G06F1/169—Constructional details or arrangements related to integrated I/O peripherals not covered by groups G06F1/1635 - G06F1/1675 the I/O peripheral being an integrated pointing device, e.g. trackball in the palm rest area, mini-joystick integrated between keyboard keys, touch pads or touch stripes
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
  • G06F3/033—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor
  • G06F3/0354—Pointing devices displaced or positioned by the user, e.g. mice, trackballs, pens or joysticks; Accessories therefor with detection of 2D relative movements between the device, or an operating part thereof, and a plane or surface, e.g. 2D mice, trackballs, pens or pucks
  • G06F3/03547—Touch pads, in which fingers can move on a surface
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/03—Arrangements for converting the position or the displacement of a member into a coded form
  • G06F3/041—Digitisers, e.g. for touch screens or touch pads, characterised by the transducing means
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0481—Interaction techniques based on graphical user interfaces [GUI] based on specific properties of the displayed interaction object or a metaphor-based environment, e.g. interaction with desktop elements like windows or icons, or assisted by a cursor's changing behaviour or appearance
  • G06F3/0482—Interaction with lists of selectable items, e.g. menus
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0484—Interaction techniques based on graphical user interfaces [GUI] for the control of specific functions or operations, e.g. selecting or manipulating an object, an image or a displayed text element, setting a parameter value or selecting a range
  • G06F3/0485—Scrolling or panning
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
  • G06F3/0487—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser
  • G06F3/0488—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures
  • G06F3/04883—Interaction techniques based on graphical user interfaces [GUI] using specific features provided by the input device, e.g. functions controlled by the rotation of a mouse with dual sensing arrangements, or of the nature of the input device, e.g. tap gestures based on pressure sensed by a digitiser using a touch-screen or digitiser, e.g. input of commands through traced gestures for inputting data by handwriting, e.g. gesture or text
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2203/00—Indexing scheme relating to G06F3/00 - G06F3/048
  • G06F2203/033—Indexing scheme relating to G06F3/033
  • G06F2203/0339—Touch strips, e.g. orthogonal touch strips to control cursor movement or scrolling; single touch strip to adjust parameter or to implement a row of soft keys
• • G—PHYSICS
  • G06—COMPUTING OR CALCULATING; COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F2203/00—Indexing scheme relating to G06F3/00 - G06F3/048
  • G06F2203/041—Indexing scheme relating to G06F3/041 - G06F3/045
  • G06F2203/04104—Multi-touch detection in digitiser, i.e. details about the simultaneous detection of a plurality of touching locations, e.g. multiple fingers or pen and finger

Definitions

• the present disclosure relates generally to touch-based user interfaces, and more particularly to, navigating between user interface layers of an application hosted by a computing device having a side-mounted touchpad.
• a touchpad is an input device including a surface that detects touch-based inputs of users.
• a touch screen is an electronic visual display that detects the presence and location of user touch inputs.
• Mobile devices such as a mobile phone, a tablet computer, and a laptop computer often incorporate a touch screen or a touchpad to facilitate user interactions with application programs running on the mobile device.
• Figure 1 illustrates an example touch screen of a mobile phone that hosts a browser client displaying a web page.
• Figure 2 illustrates an example processing stack of a mobile device with touch-based input device(s).
• Figure 3A-3C illustrate an example method of navigating between user interface layers of an application hosted on a touch-screen device.
• Figure 4 illustrates an example application user interface hierarchy of an application hosted on a touch-screen device.
• Figure 5 illustrates a front view and a side view of an example mobile device with a front-mounted touch screen and a side-mounted touchpad.
• Figure 5 A illustrates another example of the mobile device of Figure 5.
• Figure 5B illustrates an example mobile device with a back-mounted touch surface.
• Figures 5C-5F illustrate example touch events associated with the one or more side- mounted touchpads of the example mobile device of Figure 5.
• Figures 5G-5I illustrate example touch events associated with a back-mounted touch surface of the example mobile device of Figure 5B.
• Figure 6 illustrates an example method of navigating between user interface layers of an application using side-mounted touchpads.
• Figure 7 illustrates an example mobile device platform.
• a touchpad is an input device including a surface that detects touch-based inputs of users.
• a touch screen is an electronic visual display that detects the presence and location of user touch inputs.
• So-called dual touch or multi-touch displays or touchpads refer to devices that can identify the presence, location and movement of more than one touch input, such as two or three finger touches.
• a system incorporating one or more touch-based input devices may monitor one or more touch- sensitive surfaces for one or more touch or near touch inputs from a user.
• the system may determine the distinct area(s) of contact and identify the nature of the touch or near touch input(s) via geometric features and geometric arrangements (e.g., location, movement), and determine if they correspond to various touch events (e.g., tap, drag, swipe, pinch). These touch events may then be processed by handler functions that register or subscribe as listeners to such events, as illustrated in Figure 1.
• Figure 1 illustrates an example touch screen of a mobile phone that hosts a browser client displaying a web page.
• touch screen 101 of mobile phone 100 displays an HTML/JavaScript code snippet displaying a text string "Tap on this text", as listed below.
• a touch event listener "onTouchEvent” can trigger an action of changing the text string from “Tap on this text.” to "Boo! (103).
• Recognition of touch events by a system with one or more touch-based input devices- -i.e., identifying one or more touch inputs by a user and determining corresponding touch event(s)-- may be implemented by a combination of hardware, software, and/or firmware (or device drivers).
• Figure 2 illustrates an example processing stack of a mobile device (e.g., a smart phone) with touch-based input device(s).
• Hardware layer 201 can include one or more processors and various hardware input/output devices such as camera, communication interface, and touch-based input device (e.g., touch screen, touchpad).
• Drivers layer 202 includes one or more drivers that communicate and control hardware layer 200, for example, a driver receiving and processing touch input signals generated by a touch-screen display.
• Operating system 203 runs computing programs and manages hardware layer 201 via one or more drivers in driver layer 202.
• Libraries 204 include one or more libraries used by one or more application programs in applications 205 (e.g., web browser, address book, etc.).
• touch events library 210 can contain codes that interpret touch inputs to touch events or gestures, and a web browser application program can access touch event library 210 (e.g., via function calls) and process a web page with touch event handlers embedded within the page, as illustrated in Figure 1 and in the HTML/JavaScript code snippet above.
• User interface layers of application programs hosted by a computing device are generally arranged in a hierarchy, such as a hierarchical tree structure.
• a root node of the tree structure may correspond to a home user interface layer or home screen of an application, including icons, buttons, pull-down menus, hypertext links or other controls that allow users to navigate to child user interface layers.
• Child user interface layers may include icons or buttons that allow users to navigate back to parent user interface layers by selecting an icon or button. Many such buttons are displayed on the top of a menu bar, but there are a lot of exceptions.
• a user can often navigate between user interface layers of an application hosted on the touch-screen device by touching one or more selectable elements within the application's user graphic interface displayed with the touchscreen, as illustrated in Figures 3A-3C.
• the particular application shown in Figures 3A-3C is a Facebook(r) client hosted by a mobile phone with a touch screen (e.g., an iPhone(r) smartphone offered by Apple, Inc. of Cupertino, California).
• the application shows a home screen 301 ( Figure 3A), or an interface displaying home user interface layer of the application.
• the home screen 301 may include user interface elements such as icons or buttons for navigating to other layers, for example, News Feed icon 310, Photos icon 330, or Friends icon 340.
• Figure 4 illustrates an example application user interface hierarchy 400 of the application illustrated in Figures 3A-3C.
• the application user interface hierarchy includes home layer 401 and one or more sub-layers 402, such as News Feed 410, Profile 420, Photos 430, Friends 440, and the like.
• Photos layer 430 itself has a sub-layer of Album list 432 which in turn has a sub-layer Photo list 434, and so on. Not all layers have sub-layers, such as News Feed content 412, Self Profile content 422, "Photo 1" 436, which are leaf layers.
• the nodes of the hierarchy represent different user interface layers provided by the application, while the edges between the nodes illustrate a potential navigation flow. Additionally, the application may allow for navigation among the nodes in a way that does not observe a hierarchical model, such as navigating directly between sibling node layers, traversing more than one hop directly between layers, and the like.
• the user can navigate to Friends layer 440 by touching Friends icon 340 within home screen 301, the current screen will change to a screen 341 for Friends layer 440, as illustrated in Figure 3B.
• the screen 341 for Friends layer 440 comprises a list of friends wherein each friend is represented by a selectable icon (e.g., a profile picture).
• the user can navigate to a particular friend layer "Laura" 442 by touching a corresponding icon (342), the current screen will change to a screen for the particular friend (343), as illustrated in Figure 3C.
• the user can look up additional information (e.g., an email address, a phone number) of the particular friend by touching "info" icon 344, navigate back to Friends layer by touching "Friends” icon 345, or navigating to home layer by touching home icon 346.
• additional information e.g., an email address, a phone number
• Particular embodiments herein relate to a computing device (such as a mobile phone, netbook, smartphone, tablet, or other portable device) with a touch screen and one or more side-mounted touchpads and methods of allowing users to use the one or more side-mounted touchpads to navigate between application user interface layers.
• a computing device such as a mobile phone, netbook, smartphone, tablet, or other portable device
• Particular embodiments can improve user experience associated with mobile devices as the side-mounted touchpad(s) can offload user interaction to the side-mounted touchpad(s) and yield better usage of the touch screen (e.g., a less congested graphic user interface with less navigation elements or icons).
• Figure 5 illustrates a front view and a side view of an example mobile device with a front-mounted touch screen and a side-mounted touchpad.
• mobile device 500 may comprise a housing with multi-touch touch screen 501 disposed on a front face of the housing.
• the mobile device 500 may also include a side-mounted multi-touch touchpad 502 and a side-mounted single-touch touchpad 503, both disposed on a lateral face or edge of the device 500.
• mobile device 500 may include hardware and/or software that supports or implements a variety of functions.
• mobile device 500 may support telephony functions, chat and/or email functions.
• Mobile device 500 may also support network data communications and include a web browser for accessing and displaying web pages.
• Mobile device 500 may also support or incorporate, a Wi-Fi base station functions, a digital media player functions, and/or a gaming device functions.
• the side-mounted touchpad 503 may be replaced by a clickable button or keypad device. In another embodiment, the side-mounted touchpad 503 may be a multi-touch touchpad. In some implementations, the touchpad 402 may be a single- or multi-touch device. In some embodiments, side-mounted touchpad 502 may comprise a slightly concave multi- touch surface, as illustrated in Figure 5 A.
• the touch screen 501 and side-mounted touchpad 503 may be single-touch, dual-touch or multi-touch devices.
• implementations of the invention can operate without a touch screen device, relying instead on a regular display device and a pointer device, such as a trackball or tackpad.
• mobile device 500 may include a back-mount touch surface 505 on a back-side of mobile device 500.
• the back-mounted touch 505 may cover substantially all or a portion of a back side of mobile device 500, as illustrated in Figure 5B.
• the back-mounted touch surface 505 may comprise a multi-touch touchpad or a multi-touch touch screen.
• Mobile device 500 may recognize touch inputs, and determine one or more corresponding touch events or gestures.
• One or more applications hosted on mobile device 500 may be configured to register a handler function that responds to the one or more touch events.
• mobile device 500 may recognize one or more user touch inputs performed on touch screen 501, touchpad 502, touchpad 503, and/or back-mounted touch surface 505, and determine one or more corresponding touch events.
• mobile device 500 may determine a forward lateral flick event associated with touchpad 502, as illustrated in Figure 5C.
• a user touches touchpad 502 in a quick motion in forward lateral direction (indicated by the arrow 510), and a gesture recognition library of mobile device 500 can access data generated by touchpad 502 and determine the touch input corresponding to a forward lateral flick event or gesture associated with touchpad 502.
• mobile device 500 may determine a backward lateral flick event associated with touchpad 502, as illustrated in Figure 5D.
• a user touches touchpad 502 in a quick motion in backward lateral direction (indicated by the arrow 512), and a gesture recognition library of mobile device 500 can access data generated by touchpad 502 and determine the touch input corresponding to a backward lateral flick event or gesture associated with touchpad 502.
• mobile device 500 may identify a tap event.
• mobile device 500 may determine a tap event associated with touchpad 502, as illustrated in Figure 5E.
• a user taps or strikes lightly on touchpad 502 (indicated by the arrow 514), and a gesture recognition library of mobile device 500 can interpret the user's touch input and identify the touch input corresponding to a tap event.
• mobile device 500 may identify a tap event associated with touchpad 503, as illustrated in Figure 5F.
• a user taps or strikes lightly on touchpad 503 (indicated by the arrow 516), and a gesture recognition library of mobile device 500 can interpret the user's touch input and identify the touch input corresponding to a tap event.
• mobile device 500 may identify a tap event associated with touchpad 503 if touchpad 503 is a clickable button and a user clicks on the clickable button.
• mobile device 500 may identity touch events associated with back-mounted touch surface 505, as illustrated in Figures 5G-5I.
• a user touches back-mounted touch surface 505 in a quick motion in an upward direction (indicated by the arrow 531).
• a gesture recognition library of mobile device 500 can interpret the user's touch input and identify the touch input corresponding to an upward flick event or gesture associated with back-mounted touch surface 505.
• a user touches back-mounted touch surface 505 in a quick motion in a downward direction (indicated by the arrow 532).
• a gesture recognition library of mobile device 500 can interpret the user's input and identify the touch input corresponding to a downward flick event or gesture associated with back-mounted touch surface 505.
• a user taps or strikes lightly on back-mounted touch surface 505 (as indicated by the arrow 533).
• a gesture recognition library of mobile device 500 can interpret the user's input and identify the touch input corresponding to a tap event associated with back-mounted touch surface 505.
• Figure 6 illustrates an example method of navigating between user interface layers of an application using side-mounted touchpads.
• the example method of Figure 6 may enable a user to navigate between user interface layers by flicking across a side-mounted touchpad, to jump to the application's home screen by tapping or clicking a side-mounted "home button".
• the handler function can, responsive to a touch event, cause an application to navigate to a different user interface layer.
• the handler function may determine a current application layer corresponding to the touch event.
• the application may store a navigation history that tracks the layers to which the user has navigated.
• the handler function may determine if the touch event is a forward lateral flick event (602). In particular embodiments, if the touch event is a forward lateral flick event, and if the forward navigation history identifies a next layer for the current layer, the handler function may cause the application navigate to the next layer (603). In particular embodiments, the handler function may determine if the touch event is a backward lateral flick event (604). In particular embodiments, if the touch event is a backward lateral flick event, and if the backward navigation history identifies a previous layer for the current layer, the handler function may cause the application navigate to the previous layer (605).
• the handler function may determine if the touch event is a tap event in connection with input device 503 (606). In particular embodiments, if the touch event is a tap event, and if the current layer is not a home layer, the handler function may cause the application navigate to the home layer (607).
• particular embodiments may enable navigating between user interface layers of an application using the back-mounted touch surface described earlier.
• the handler function can, responsive to a touch event, cause an application to navigate to a different user interface layer.
• the handler function may determine a current application layer corresponding to the touch event.
• the application may store a navigation history that tracks the layers to which the user has navigated.
• the handler function may determine if the touch event is an upward flick event associated with back-mounted touch surface 505. If the touch event is an upward flick event associated with back-mounted touch surface 505, and if the forward navigation history identifies a next layer for the current layer, the handler function may cause the application to navigate to the next layer.
• the hander function may determine if the touch event is a downward flick event associated with back-mounted touch surface 505. If the touch event is a downward flick event associated with back-mounted touch surface 505, and if the backward navigation history identifies a previous layer for the current layer, the handler function may cause the application navigate to the previous layer. The handler function may determine if the touch event is a tap event associated with back- mounted touch surface 505. If the touch event is a tap event associated with back- mounted touch surface 505, and if the current layer is not a home layer, the handler function may cause the application to navigate to the home layer.
• the forward and back gestures, as well as the home control input, described above can be utilized in connection with a variety of applications and computing devices.
• the forward and back gestures, as well as the home control input may be used in connection with a special-purpose client application in order to facilitate navigation of the various application layers.
• the home input causes navigation back to the home or root layer of the application.
• the forward and back gestures, as well as the home control input may also be used in connection with a browser client to facilitate navigation of a series of web pages provided by one or more domains.
• the home input may cause navigation back to a home page, while the forward and back gestures may implement corresponding forward and backward navigation functions common to browser client applications.
• the forward and back gestures can be used in connection with a graphical user interface shell of an operating system.
• the home input may cause navigation back to the home screen of the operating system, while the forward and back gestures may implement corresponding forward and backward navigation functions across various layers provided by the operating system shell.
• the application and functionality described above can be implemented as a series of instructions stored on a computer-readable storage medium that, when executed, cause a programmable processor to implement the operations described above.
• the mobile device 500 may be implemented in a variety of different hardware and computing systems
• FIGURE 7 shows a schematic representation of the main components of an example computing platform of a client or mobile device, according to various particular embodiments.
• computing platform 702 may comprise controller 704, memory 706, and input output subsystem 710.
• controller 704 which may comprise one or more processors and/or one or more microcontrollers configured to execute instructions and to carry out operations associated with a computing platform.
• controller 704 may be implemented as a single-chip, multiple chips and/or other electrical components including one or more integrated circuits and printed circuit boards.
• Controller 704 may optionally contain a cache memory unit for temporary local storage of instructions, data, or computer addresses.
• controller 704 may control the reception and manipulation of input and output data between components of computing platform 702.
• controller 704 may include one or more processors or one or more controllers dedicated for certain processing tasks of computing platform 702, for example, for 2D/3D graphics processing, image processing, or video processing.
• Controller 704 together with a suitable operating system may operate to execute instructions in the form of computer code and produce and use data.
• the operating system may be Windows-based, Mac-based, or Unix or Linux-based, Symbian-based, or Android-based among other suitable operating systems.
• the operating system, other computer code and/or data may be physically stored within memory 706 that is operatively coupled to controller 704.
• Memory 706 may encompass one or more storage media and generally provide a place to store computer code (e.g., software and/or firmware) and data that are used by computing platform 702.
• memory 706 may include various tangible computer-readable storage media including Read-Only Memory (ROM) and/or Random-Access Memory (RAM).
• ROM Read-Only Memory
• RAM Random-Access Memory
• Memory 706 may also include one or more fixed storage devices in the form of, by way of example, hard disk drives (HDDs), solid-state drives (SSDs), flash-memory cards (e.g., Secured Digital or SD cards, embedded MultiMediaCard or eMMD cards), among other suitable forms of memory coupled bi-directionally to controller 704. Information may also reside on one or more removable storage media loaded into or installed in computing platform 702 when needed. By way of example, any of a number of suitable memory cards (e.g., SD cards) may be loaded into computing platform 702 on a temporary or permanent basis.
• HDDs hard disk drives
• SSDs solid-state drives
• flash-memory cards e.g., Secured Digital or SD cards, embedded MultiMediaCard or eMMD cards
• Information may also reside on one or more removable storage media loaded into or installed in computing platform 702 when needed.
• any of a number of suitable memory cards e.g., SD cards
• Input output subsystem 710 may comprise one or more input and output devices operably connected to controller 704.
• input-output subsystem may include keyboard, mouse, one or more buttons, thumb wheel, and/or display (e.g., liquid crystal display (LCD), light emitting diode (LED), Interferometric modulator display (IMOD), or any other suitable display technology).
• display e.g., liquid crystal display (LCD), light emitting diode (LED), Interferometric modulator display (IMOD), or any other suitable display technology.
• input devices are configured to transfer data, commands and responses from the outside world into computing platform 702.
• the display is generally configured to display a graphical user interface (GUI) that provides an easy to use visual interface between a user of the computing platform 702 and the operating system or application(s) running on the mobile device.
• GUI graphical user interface
• the GUI presents programs, files and operational options with graphical images.
• Input output subsystem 710 may also include touch based devices such as touchpad and touch screen.
• a touchpad is an input device including a surface that detects touch-based inputs of users.
• a touch screen is a display that detects the presence and location of user touch inputs.
• Input output system 710 may also include dual touch or multi-touch displays or touchpads that can identify the presence, location and movement of more than one touch inputs, such as two or three finger touches.
• computing platform 702 may additionally comprise audio subsystem 712, camera subsystem 712, wireless communication subsystem 716, sensor subsystems 718, and/or wired communication subsystem 720, operably connected to controller 704 to facilitate various functions of computing platform 702.
• Audio subsystem 712 including a speaker, a microphone, and a codec module configured to process audio signals, can be utilized to facilitate voice-enabled functions, such as voice recognition, voice replication, digital recording, and telephony functions.
• camera subsystem 712 including an optical sensor (e.g., a charged coupled device (CCD), or a complementary metal-oxide semiconductor (CMOS) image sensor), can be utilized to facilitate camera functions, such as recording photographs and video clips.
• wired communication subsystem 720 can include a Universal Serial Bus (USB) port for file transferring, or a Ethernet port for connection to a local area network (LAN).
• computing platform 702 may be powered by power source 732.
• USB Universal Serial Bus
• Wireless communication subsystem 716 can be designed to operate over one or more wireless networks, for example, a wireless PAN (WPAN) (such as, for example, a BLUETOOTH WPAN, an infrared PAN), a WI-FI network (such as, for example, an 802.1 la/b/g/n WI-FI network, an 802.11s mesh network), a WI-MAX network, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network, an Enhanced Data Rates for GSM Evolution (EDGE) network, a Universal Mobile Telecommunications System (UMTS) network, and/or a Long Term Evolution (LTE) network).
• WPAN wireless PAN
• WI-FI network such as, for example, an 802.1 la/b/g/n WI-FI network, an 802.11s mesh network
• WI-MAX such as, for example, a cellular telephone network (such as, for example, a Global System for Mobile Communications (GSM) network, an
• Sensor subsystem 718 may include one or more sensor devices to provide additional input and facilitate multiple functionalities of computing platform 702.
• sensor subsystems 718 may include GPS sensor for location positioning, altimeter for altitude positioning, motion sensor for determining orientation of a mobile device, light sensor for photographing function with camera subsystem 714, temperature sensor for measuring ambient temperature, and/or biometric sensor for security application (e.g., fingerprint reader).
• Other input/output devices may include an accelerometer that can be used to detect the orientation of the device.
• various components of computing platform 702 may be operably connected together by one or more buses (including hardware and/or software).
• the one or more buses may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a front-side bus (FSB), a HYPERTRANSPORT (HT) interconnect, an Industry Standard Architecture (ISA) bus, an INFINIBAND interconnect, a low-pin-count (LPC) bus, a memory bus, a Micro Channel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a serial advanced technology attachment (SATA) bus, a Video Electronics Standards Association local (VLB) bus, a Universal Asynchronous Receiver/Transmitter (UART) interface, a Inter-Integrated Circuit (I 2 C) bus, a Serial Peripheral Interface (SPI) bus, a Secure Digital (SD) memory interface, a MultiMediaCard (MMC) memory interface, a Memory Stick (MS) memory interface, a Secure Digital In
• a computer-readable storage medium encompasses one or more non-transitory, tangible computer-readable storage media possessing structure.
• a computer-readable storage medium may include a semiconductor-based or other integrated circuit (IC) (such, as for example, a field-programmable gate array (FPGA) or an application-specific IC (ASIC)), a hard disk, an HDD, a hybrid hard drive (HHD), an optical disc, an optical disc drive (ODD), a magneto-optical disc, a magneto-optical drive, a floppy disk, a floppy disk drive (FDD), magnetic tape, a holographic storage medium, a solid-state drive (SSD), a RAM-drive, a SECURE DIGITAL card, a SECURE DIGITAL drive, a MultiMediaCard (MMC) card, an embedded MMC (eMMC) card, or another suitable computer-readable storage medium or a combination of two or more of these, where appropriate.
• IC semiconductor-based or other integrated circuit
• reference to a computer-readable storage medium excludes any medium that is not eligible for patent protection under 35 U.S.C. ⁇ 101.
• reference to a computer-readable storage medium excludes transitory forms of signal transmission (such as a propagating electrical or electromagnetic signal per se) to the extent that they are not eligible for patent protection under 35 U.S.C. ⁇ 101.
• a computer-readable storage medium implements one or more portions of controller 704 (such as, for example, one or more internal registers or caches), one or more portions of memory 705, or a combination of these, where appropriate.
• a computer-readable storage medium implements RAM or ROM.
• a computer-readable storage medium implements volatile or persistent memory.
• one or more computer-readable storage media embody software.
• reference to software may encompass one or more applications, bytecode, one or more computer programs, one or more executables, one or more instructions, logic, machine code, one or more scripts, or source code, and vice versa, where appropriate.
• software includes one or more application programming interfaces (APIs).
• APIs application programming interfaces
• This disclosure contemplates any suitable software written or otherwise expressed in any suitable programming language or combination of programming languages.
• software is expressed as source code or object code.
• software is expressed in a higher-level programming language, such as, for example, C, Perl, JavaScript, or a suitable extension thereof.
• software is expressed in a lower-level programming language, such as assembly language (or machine code).
• software is expressed in JAVA.
• software is expressed in Hyper Text Markup Language (HTML), Extensible Markup Language (XML), or other suitable markup language

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Human Computer Interaction (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Computer Hardware Design (AREA)
• User Interface Of Digital Computer (AREA)
• Position Input By Displaying (AREA)
• Telephone Function (AREA)

Priority Applications (12)

Applications Claiming Priority (2)

Publications (1)

Family

ID=48085662

Family Applications (1)

Country Status (12)

Families Citing this family (33)

Citations (5)

Family Cites Families (21)

• 2011
  • 2011-10-17 US US13/275,095 patent/US8711116B2/en active Active
• 2012
  • 2012-09-13 CN CN201280051212.1A patent/CN103890697B/zh active Active
  • 2012-09-13 CA CA2852664A patent/CA2852664C/en not_active Expired - Fee Related
  • 2012-09-13 MX MX2014004717A patent/MX344760B/es active IP Right Grant
  • 2012-09-13 CA CA2929619A patent/CA2929619C/en not_active Expired - Fee Related
  • 2012-09-13 EP EP12841962.9A patent/EP2769287B1/en active Active
  • 2012-09-13 AU AU2012326592A patent/AU2012326592B2/en not_active Ceased
  • 2012-09-13 IN IN3013CHN2014 patent/IN2014CN03013A/en unknown
  • 2012-09-13 MX MX2017000197A patent/MX353890B/es unknown
  • 2012-09-13 WO PCT/US2012/054973 patent/WO2013058896A1/en not_active Ceased
  • 2012-09-13 KR KR1020147013156A patent/KR101555627B1/ko active Active
  • 2012-09-13 CA CA2907550A patent/CA2907550C/en not_active Expired - Fee Related
  • 2012-09-13 JP JP2014537067A patent/JP5806411B2/ja active Active
  • 2012-09-13 BR BR112014009521A patent/BR112014009521A2/pt not_active IP Right Cessation
• 2014
  • 2014-01-13 US US14/153,910 patent/US8866786B2/en active Active
  • 2014-04-22 IL IL232191A patent/IL232191A/en active IP Right Grant
  • 2014-07-29 US US14/445,989 patent/US8976142B2/en active Active
• 2015
  • 2015-09-03 JP JP2015173781A patent/JP2016027481A/ja active Pending
  • 2015-12-31 AU AU2015285964A patent/AU2015285964B2/en not_active Ceased
• 2016
  • 2016-08-31 AU AU2016222381A patent/AU2016222381B2/en not_active Ceased
  • 2016-11-22 IL IL249114A patent/IL249114B/en not_active IP Right Cessation
• 2018
  • 2018-06-06 JP JP2018108529A patent/JP6663453B2/ja not_active Expired - Fee Related

Patent Citations (5)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events