FreshPatents.com Logo
stats FreshPatents Stats
n/a views for this patent on FreshPatents.com
Updated: July 21 2014
newTOP 200 Companies filing patents this week


    Free Services  

  • MONITOR KEYWORDS
  • Enter keywords & we'll notify you when a new patent matches your request (weekly update).

  • ORGANIZER
  • Save & organize patents so you can view them later.

  • RSS rss
  • Create custom RSS feeds. Track keywords without receiving email.

  • ARCHIVE
  • View the last few months of your Keyword emails.

  • COMPANY DIRECTORY
  • Patents sorted by company.

Follow us on Twitter
twitter icon@FreshPatents

Foreground/background assortment of hidden windows

last patentdownload pdfdownload imgimage previewnext patent


20130024812 patent thumbnailZoom

Foreground/background assortment of hidden windows


Graphical navigation of foreground and background applications running on a mobile computing device across multiple active user environments, even when graphics information for background applications is not maintained by a mobile operating system of the mobile computing device. A last graphical representation of an application screen may be captured as the application state is transitioned from the foreground state to the background state. The last graphical representation may be associated with a position in an application activity stack representing foreground and background mobile operating system applications. The navigation techniques may be used in a computing environment with multiple active user environments. A first active user environment may be associated with the mobile operating system. A second active user environment may be associated with the mobile operating system or a desktop operating system running concurrently with the mobile operating system on the mobile computing device.
Related Terms: Graphics Mobile Computing Operating System Windows Concurrent Desktop Foreground Graph Mobile Operating System Navigation Computing Device Mobile Computing Device

Browse recent Z124 patents - Georgetown, KY
USPTO Applicaton #: #20130024812 - Class: 715810 (USPTO) - 01/24/13 - Class 715 
Data Processing: Presentation Processing Of Document, Operator Interface Processing, And Screen Saver Display Processing > Operator Interface (e.g., Graphical User Interface) >On-screen Workspace Or Object >Menu Or Selectable Iconic Array (e.g., Palette)

Inventors: Brian Reeves, Paul E. Reeves, Wuke Liu

view organizer monitor keywords


The Patent Description & Claims data below is from USPTO Patent Application 20130024812, Foreground/background assortment of hidden windows.

last patentpdficondownload pdfimage previewnext patent

BACKGROUND

1. Field

This Application relates generally to the field of mobile computing environments, and more particularly to supporting application navigation in a mobile computing environment with multiple active user environments.

2. Relevant Background

Mobile communications devices are becoming ubiquitous in today\'s society. For example, as of the end of 2008, 90 percent of Americans had a mobile wireless device. Among the fastest growing mobile communications devices are smartphones, that is, mobile phones built on top of a mobile computing platform. Mobile providers have launched hundreds of new smartphones in the last three years based upon several different computing platforms (e.g., Apple iPhone, Android, BlackBerry, Palm, Windows Mobile, and the like). In the U.S., smartphone penetration reached almost 23% by the middle of 2010, and over 35% in some age-groups. In Europe, the smartphone market grew by 41% from 2009 to 2010, with over 60 million smartphone subscribers as of July 2010 in the five largest European countries alone.

Smartphone computing platforms typically include a mobile operating system (“OS”) running on a mobile processor. While mobile processors and mobile OSs have increased the capabilities of these devices, smartphones have not tended to replace personal computer (“PC”) environments (i.e., Windows, Mac OS X, Linux, and the like) such as desktop or notebook computers at least because of the limited user experience provided. In particular, smartphones typically have different processing resources, user interface device(s), peripheral devices, and applications. For example, mobile processors may have a different processor architecture than PC processors that emphasizes features like low-power operation and communications capabilities over raw processing and/or graphics performance. In addition, smartphones tend to have smaller amounts of other hardware resources such as memory (e.g., SRAM, DRAM, etc.) and storage (e.g., hard disk, SSD, etc.) resources. Other considerations typically include a smaller display size that limits the amount of information that can be presented through a mobile OS graphical user interface (“GUI”) and different user input devices. Use interface input device(s) for smartphones typically include a small thumb-style QWERTY keyboard, touch-screen display, click-wheel, and/or scroll-wheel. In contrast, laptop, notebook, and desktop computers that use a desktop OS typically have a full-size keyboard, pointing device(s), and/or a larger screen area. As a result, mobile OSs typically have a different architecture where some capabilities and features such as communications, lower power consumption, touch-screen capability, and the like, are emphasized over traditionally emphasized PC capabilities such as processing speed, graphics processing, and application multi-tasking

Because of the architecture differences, applications or “Apps” designed for mobile OSs tend to be designed for tasks and activities that are typical of a mobile computing experience (e.g., communications, gaming, navigation, and the like). For example, over a third of all Android App downloads have been targeted towards the gaming and entertainment categories while less than 20% of downloads fall under the tools and productivity categories. In addition, many applications that are common on PC platforms are either not available for mobile OSs or are available only with a limited features set.

For example, many smartphones run Google\'s Android operating system. Android runs only applications that are specifically developed to run within a Java-based virtual machine runtime environment. In addition, while Android is based on a modified Linux kernel, it uses different standard C libraries, system managers, and services than Linux. Accordingly, applications written for Linux do not run on Android without modification or porting. Similarly, Apple\'s iPhone uses the iOS mobile operating system. Again, while iOS is derived from Mac OS X, applications developed for OS X do not run on iOS. Therefore, while many applications are available for mobile OSs such as Android and iOS, many other common applications for desktop operating systems such as Linux and Mac OS X are either not available on the mobile platforms or have limited functionality. As such, these mobile OSs provide

Accordingly, smartphones are typically suited for a limited set of user experiences and provide applications designed primarily for the mobile environment. In particular, smartphones do not provide a suitable desktop user experience, nor do they run most common desktop applications. For some tasks such as typing or editing documents, the user interface components typically found on a smartphones tend to be more difficult to use than a full-size keyboard and large display that may be typically found on a PC platform.

As a result, many users carry and use multiple computing devices including a smartphone, laptop, and/or tablet computer. In this instance, each device has its own CPU, memory, file storage, and operating system. Connectivity and file sharing between smartphones and other computing devices involves linking one device (e.g., smartphone, running a mobile OS) to a second, wholly disparate device (e.g., notebook, desktop, or tablet running a desktop OS), through a wireless or wired connection. Information is shared across devices by synchronizing data between applications running separately on each device. This process, typically called “synching,” is cumbersome and generally requires active management by the user.

SUMMARY

Embodiments of the present invention are directed to providing the mobile computing experience of a smartphone and the appropriate user experience of a secondary terminal environment in a single mobile computing device. A secondary terminal environment may be some combination of visual rendering devices (e.g., monitor or display), input devices (e.g., mouse, touch pad, touch-screen, keyboard, etc.), and other computing peripherals (e.g., HDD, optical disc drive, memory stick, camera, printer, etc.) connected to the computing device by a wired (e.g., USB, Firewire, Thunderbolt, etc.) or wireless (e.g., Bluetooth, WiFi, etc.) connection. In embodiments, a mobile operating system associated with the user experience of the mobile environment and a desktop operating system associated with the user experience of the secondary terminal environment are run concurrently and independently on a shared kernel.

According to one aspect consistent with various embodiments, a mobile computing device includes a first operating system. A first application is running on the mobile operating system. A first application screen, associated with the first application, is displayed on an active display device. For example, the application screen may be displayed on a display of the mobile computing device. A process for managing application graphics associated with the application includes receiving an application interaction state change event indicating that a current interaction state of the first application is to be changed from a foreground state to a background state, generating a bitmap image corresponding to a graphical representation of the first application screen, changing the current interaction state of the first application from the foreground state to the background state, associating the bitmap image with a position within an application activity stack corresponding to the application, receiving a user input command related to the application activity stack, and displaying a representation of the bitmap image within a graphical representation of the application activity stack. The process may include receiving a user command indicative of a selection of the bitmap image within the graphical representation of the application activity stack, and changing the current interaction state of the first application from the background state to the foreground state.

According to other aspects consistent with various embodiments, the mobile computing device may define a first user environment, and the graphical representation of the application activity stack may be presented on a display of a second user environment. The second user environment may be associated with a second operating system running concurrently with the first operating system on a shared kernel of the mobile computing device. The application activity stack may be maintained by an application model manager. The application activity stack may include applications that have been started by the user and not actively closed by the user. A process associated with the first application screen may be suspended in response to the change in the current interaction state of the first application from the foreground state to the background state.

According to other aspects consistent with various embodiments, a mobile computing device includes a first application and a second application running concurrently on a first operating system. A process for managing application graphics may include displaying the first application on an active display device, receiving an application interaction state change event indicating that a current interaction state of the first application is to be changed from a foreground state to a background state, generating a bitmap image corresponding to a graphical representation of an application screen associated with the first application, changing the current interaction state of the first application from the foreground state to the background state, associating the bitmap image with a position within an application activity stack corresponding to the application, and displaying a graphical representation of the application activity stack on a display device associated with a secondary terminal environment, the secondary terminal environment connected to the mobile computing device via a communications interface, the graphical representation of the application activity stack including the bitmap image.

According to other aspects consistent with various embodiments, the secondary terminal environment may be associated with a second operating system running concurrently with the first operating system on a shared kernel of the mobile computing device. Displaying of the graphical representation of the application activity stack may be in response to a user initiated event within the secondary terminal environment and/or a dock event. The dock event may include connecting the mobile computing device with the secondary terminal environment via the communications interface. The bitmap image may be generated from graphical information maintained by a bitmap server within a surface manager of the first operating system. The bitmap server may provide an application level interface to the bitmap image data.

According to other aspects consistent with various embodiments, a mobile computing device includes a first operating system and a display device. A first application screen, associated with a first application running on the first operating system, is displayed on the display device. The first application may be considered to be in a foreground state. The first operating system includes an activity manager that maintains a list of currently running applications, an application model manager of the first operating system that receives application state information from the activity manager service, and a bitmap server module that maintains references to active surfaces of the first application. The bitmap server module may store a copy of the surface information of the first application screen responsive to an application interaction state change event indicating that a current interaction state of the first application is to be changed from the foreground state to a background state. The first operating system may display a transition animation based on the copy of the surface information of the first application screen. The transition animation may be displayed by an application space component of the first operating system. The first operating system may be a mobile operating system. The mobile operating system may include a surface manager module, and the bitmap server module may be implemented as a class in the surface manager module. The bitmap server module may provide references to the copy of the surface information of the first application screen to the framework layer of the mobile operating system. The bitmap server module may create a bitmap image from the copy of the surface information of the first application screen.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention are illustrated in referenced figures of the drawings, in which like numbers refer to like elements throughout the description of the figures.

FIG. 1 illustrates a computing environment that provides multiple user computing experiences, according to various embodiments.

FIG. 2 illustrates an exemplary system architecture for a mobile computing device, according to various embodiments.

FIG. 3 illustrates an operating system architecture for a computing environment, according to various embodiments.

FIG. 4 illustrates an operating system architecture for a computing environment, according to various embodiments.

FIG. 5 illustrates aspects of a kernel for a computing environment, according to various embodiments.

FIG. 6 illustrates an operating system architecture for a computing environment, according to various embodiments.

FIG. 7 illustrates a computing environment with multiple active user environments, according to various embodiments.

FIG. 8 illustrates a computing environment including a mobile computing device, according to various embodiments.

FIG. 9 illustrates aspects of cross-environment assortment of application windows, according to various embodiments.

FIG. 10 illustrates aspects of graphical cross-environment application navigation, according to various embodiments.

FIG. 11 illustrates aspects of a computing architecture supporting cross-environment application navigation and assortment, according to various embodiments.

FIG. 12 illustrates a flow diagram for managing graphical navigation in a computing environment, according to various embodiments.

DETAILED DESCRIPTION

The present disclosure is generally directed to managing navigation of foreground and background applications in a computing environment with multiple active user environments. More particularly, applications or “Apps” may be running on a mobile operating system (“OS”) of a mobile computing device that generally defines a first active user environment. The mobile OS typically presents a single active application (i.e., foreground application) at a time through a graphical user interface (“GUI”) of the mobile operating system. Other applications may be running on the mobile operating system but not actively displayed (i.e., background applications). Commonly, processes of background applications related to displaying graphics information and accepting user input are suspended or paused by the mobile operating system. While some of these processes may save an instance state of application data before being paused or suspended, the mobile OS typically does not update or maintain graphical information for these processes while the application is in the background. Navigation among foreground and background applications running on the mobile OS on the mobile computing device typically consists of navigating away from the foreground application (e.g., back to a home screen, etc.) before selecting an icon associated with a background application.

In a computing environment with multiple active user environments, it may be desirable to present user interfaces for multiple concurrent applications within an active user environment of the computing environment. Additionally, it may be desirable to graphically browse and/or navigate through applications running on a first operating system through a second active user environment. For example, cross environment application browsing and/or navigation using preview representations of application screens may allow faster cross-environment application navigation as they provide a visual representation of an application state.

In disclosed embodiments with multiple active user environments, a mobile computing device running a mobile operating system defines a first active user environment. A second active user environment may be connected to the mobile computing device. Mobile OS applications may be accessed from and actively displayed through the second active user environment. In embodiments, the second active user environment may be associated with a second operating system (e.g., a desktop operating system) running on the mobile computing device.

Disclosed embodiments present a seamless computing experience in a computing environment with multiple active user environments by automatically presenting application screens across user environments in certain conditions. Other disclosed embodiments support graphical navigation of foreground and background applications of the mobile operating system across multiple active user environments. For example, preview screens of foreground and background applications running on the mobile operating system may be displayed within the second active user environment to allow a user to navigate quickly between applications running on the mobile operating system. Disclosed techniques allow graphical cross-environment application navigation even where the mobile operating system does not maintain graphical information for background applications of the mobile OS. For example, graphical and/or user input processes of background applications may be paused, stopped, suspended, and/or killed. In various embodiments, a last graphical representation of a mobile OS application is captured before the application is moved from a foreground state to a background state and graphical information and/or user input processes of the application are paused or suspended. The last graphical representation for mobile OS applications may be maintained as bitmap images or graphics surface information. While the foreground/background application navigation techniques presented in the disclosure are discussed with reference to a mobile computing device and various docked terminal environments, the disclosure may, in various embodiments, be applied to other computing devices (e.g., laptop computers, tablet computers, desktop computers, etc.) and is not intended to be limited to handheld mobile computing devices unless otherwise explicitly specified.

FIG. 1 illustrates a computing environment 100 that provides multiple user computing experiences through multiple active user environments, according to various embodiments. A first active user environment 115 of computing environment 100 is defined by display(s) 116, touch screen sensor(s) 117, and/or I/O devices 118 of mobile computing device 110. The display(s) 116 may be operative to display a displayed image or “screen.” As used herein, the term display is intended to connote device hardware, whereas screen is intended to connote the displayed image produced on the display. In this regard, a display is physical hardware that is operable to present a screen to the user. A screen may encompass a majority of one or more displays. For instance, a screen may occupy substantially all of the display area of one or more displays except for areas dedicated to other functions (e.g. menu bars, status bars, etc.). A screen may be associated with an application and/or an operating system executing on the mobile computing device 110. For instance, applications may have various kinds of screens that are capable of being manipulated as will be described further below.

When mobile computing device 110 is operated as a stand-alone mobile device, active user environment 115 presents a typical mobile computing user experience. In this regard, mobile computing device 110 typically includes mobile telephony capabilities and user interaction features suited to a mobile computing use model. For example, mobile computing device 110 may present a graphical user interface (“GUI”) suited to active user environment 115 including display(s) 116, touch-screen sensor(s) 117, and/or I/O device(s) 118. The user may interact with application programs (i.e., “Apps”) running on mobile computing device 110 through an application screen including various interactive features (e.g., buttons, text fields, toggle fields, etc.) presented on display(s) 116. In some instances, the user interacts with these interactive features by way of I/O device(s) 118. In other instances, the user interacts with these features by way of touch-screen sensor(s) 117 using gestures and symbols that are input to touch screen sensor(s) 117 using the user\'s fingers or a stylus. In yet other instances, the user interacts with these features using a combination of I/O device(s) 118 and touch-screen sensor(s) 117.

FIG. 2 illustrates an exemplary hardware system architecture for mobile computing device 110, according to various embodiments. Mobile computing device 110 includes mobile processor 114 with one or more CPU cores 204 and external display interface 220. Generally, mobile computing device 110 also includes memory 206, storage devices 208, touch-screen display controller 212 connected to touch-screen display(s) 116 and/or touch-screen sensor(s) 117, I/O devices 118, power management IC 214 connected to battery 216, cellular modem 218, communication devices 222, and/or other devices 224 that are connected to processor 114 through various communication signals and interfaces. I/O devices 118 generally includes buttons and other user interface components that may be employed in mobile computing device 110. For example, I/O devices 118 may include a set of buttons, (e.g., back, menu, home, search, etc.), off-screen gesture area, click-wheel, scroll-wheel, QWERTY keyboard, etc. Other devices 224 may include, for example, GPS devices, LAN connectivity, microphones, speakers, cameras, accelerometers, gyroscopes, magnetometers, and/or MS/MMC/SD/SDIO card interfaces. External display interface 220 may be any suitable display interface (e.g., VGA, DVI, HDMI, wireless, etc.).

One or more sensor devices of the mobile computing device 110 may be able to monitor the orientation of the mobile computing device with respect to gravity. For example, using an accelerometer, gyroscope, inclinometer, or magnetometer, or some combination of these sensors, mobile computing device 110 may be able to determine whether it is substantially in a portrait orientation (meaning that a long axis of the display(s) 116 are oriented vertically) or substantially in a landscape orientation with respect to gravity. These devices may further provide other control functionality by monitoring the orientation and/or movement of the mobile computing device 110. As used herein, the term orientation sensor is intended to mean some combination of sensors (e.g., accelerometer, gyroscope, inclinometer, magnetometer, etc.) that may be used to determine orientation of a device with respect to gravity and is not intended to be limited to any particular sensor type or technology.

Processor 114 may be an ARM-based mobile processor. In embodiments, mobile processor 114 is a mobile ARM-based processor such as Texas Instruments OMAP3430, Marvell PXA320, Freescale iMX51, or Qualcomm QSD8650/8250. However, mobile processor 114 may be another suitable ARM-based mobile processor or processor based on other processor architectures such as, for example, x86-based processor architectures or other RISC-based processor architectures.

While FIG. 2 illustrates one exemplary hardware implementation 112 for mobile computing device 110, other architectures are contemplated as within the scope of the invention. For example, various components illustrated in FIG. 2 as external to mobile processor 114 may be integrated into mobile processor 114. Optionally, external display interface 220, shown in FIG. 2 as integrated into mobile processor 114, may be external to mobile processor 114. Additionally, other computer architectures employing a system bus, discrete graphics processor, and/or other architectural variations are suitable for employing aspects of the present invention.

Returning to FIG. 1, mobile computing device 110 may be docked with a secondary terminal environment 140. Secondary terminal environment 140 may be some combination of visual rendering devices (e.g., monitor or display) 140, I/O devices (e.g., mouse, touch pad, touch-screen, keyboard, etc.) 146, and other computing peripherals (e.g., HDD, optical disc drive, memory stick, camera, printer, GPS, accelerometer, etc.) 148 connected to mobile computing device 110 by connecting port 142 on secondary terminal environment 140 with port 120 on mobile computing device 110 through interface 122. Interface 122 may be some combination of wired (e.g., USB, Firewire, Thunderbolt, HDMI, VGA, etc.) or wireless (e.g., Bluetooth, WiFi, Wireless HDMI, etc.) interfaces. While secondary terminal environments may have some processing or logic elements such as microcontrollers or other application specific integrated circuits (“ASICs”), they typically do not have a processor that runs a separate instance of an operating system.

Secondary terminal environments that define a second user environment may be suited for one or more of various use models, depending on the components that make up the secondary terminal environment. Some secondary terminal environments may be associated with a user computing experience that is similar to the user computing experience of the mobile computing device 110, while others may provide a user computing experience more traditionally associated with desktop computing. For example, secondary terminal environment 140 may be a device that includes a display 144 with a corresponding touch-screen sensor 146 that serves as the primary user input for the device. This type of secondary terminal environment may be called a tablet-style secondary terminal environment. While a tablet-style secondary terminal environment may have a larger touch-screen display than mobile computing device 110, the user experience of this type of secondary terminal environment may be similar in some ways to the user experience of mobile computing device 110. Specifically, it may be convenient for a user to interact with applications displayed on this type of secondary terminal environment through similar gesture-based techniques (i.e., touching, swiping, pinching, etc.) and/or virtual keyboards as they might use on mobile computing device 110. In one embodiment known as a “Smart Pad,” a tablet-style secondary terminal environment includes a 10.1-inch diagonal (1280×800 resolution) touch-enabled display, standard set of buttons (e.g., back, menu, home, search, etc.), one or more cameras, and an off-screen gesture area. A tablet-style secondary terminal environment may include other peripheral devices 148 that may be used to influence the configuration of applications presented to the user on the tablet-style secondary terminal environment. For example, a tablet-style secondary terminal environment may include a GPS receiver, accelerometer, gyroscope, magnetometer, and/or other sensors for determining its location and/or orientation.

Another type of secondary terminal environment is a laptop or notebook-style secondary terminal environment. A notebook-style secondary terminal environment generally includes a display screen 144, keyboard and pointing device(s) 146, and/or other peripheral devices 148 in a clam-shell type enclosure. In embodiments, a laptop or notebook-style secondary terminal environment may be known as a “Smart Display” or “LapDock.” Because this type of secondary terminal environment includes a larger display, keyboard, and pointing device(s), it typically has a user computing experience associated with a desktop computing experience. In this regard, this type of secondary terminal environment may not have a similar user experience profile to mobile computing device 110. A notebook-style secondary terminal environment may include other peripheral devices that may be used to influence the configuration of applications presented to the user on the secondary terminal environment. For example, a notebook-style secondary terminal environment may include a GPS receiver, accelerometer, gyroscope, magnetometer, and/or other sensors for determining its location and/or orientation.

The various secondary terminal environments may also include a variety of generic input/output device peripherals that make up a typical desktop computing environment. The I/O devices may be connected through a docking hub (or “dock cradle”) that includes port 142 and one or more device I/O ports for connecting various commercially available display monitors 144, I/O devices 146, and/or other peripheral devices 148. For example, a docking hub may include a display port (e.g., VGA, DVI, HDMI, Wireless HDMI, etc.), and generic device ports (e.g., USB, Firewire, etc.). As one example, a user may connect a commercially available display, keyboard, and pointing device(s) to the docking hub. In this way, the user may create a secondary terminal environment from a combination of input/output devices. Commonly, this secondary terminal environment will be suited to a desktop computing experience. In particular, this type of secondary terminal environment may be suited to a computing experience designed around the use of a pointing device(s) and physical keyboard to interact with a user interface on the display.

In embodiments, mobile computing device 110 includes multiple operating systems running concurrently and independently on a shared kernel. Concurrent execution of a mobile OS and a desktop OS on a shared kernel is described in more detail in U.S. patent application Ser. No. 13/217,108, filed Aug. 24, 2011, entitled “MULTI-OPERATING SYSTEM,” herein incorporated by reference. In this way, a single mobile computing device can concurrently provide a mobile computing experience through a first user environment associated with a mobile OS and a desktop computing experience through a second user environment associated with a full desktop OS.

FIG. 3 illustrates OS architecture 300 that may be employed to run mobile OS 130 and desktop OS 160 concurrently on mobile computing device 110, according to various embodiments. As illustrated in FIG. 3, mobile OS 130 and desktop OS 160 are independent operating systems running concurrently on shared kernel 320. Specifically, mobile OS 130 and desktop OS 160 are considered independent and concurrent because they are running on shared kernel 320 at the same time and may have separate and incompatible user libraries, graphics systems, and/or framework layers. For example, mobile OS 130 and desktop OS 160 may both interface to shared kernel 320 through the same kernel interface 322 (e.g., system calls, etc.). In this regard, shared kernel 320 manages task scheduling for processes of both mobile OS 130 and desktop OS 160 concurrently.

In addition, shared kernel 320 runs directly on mobile processor 114 of mobile computing device 110, as illustrated in FIG. 3. Specifically, shared kernel 320 directly manages the computing resources of processor 114 such as CPU scheduling, memory access, and I/O. In this regard, hardware resources are not virtualized, meaning that mobile OS 130 and desktop OS 160 make system calls through kernel interface 322 without virtualized memory or I/O access. Functions and instructions for OS architecture 300 may be stored as computer program code on a tangible computer readable medium of mobile computing device 110. For example, instructions for OS architecture 300 may be stored in storage device(s) 208 of mobile computing device 110.

As illustrated in FIG. 3, mobile OS 130 has libraries layer 330, application framework layer 340, and application layer 350. In mobile OS 130, applications 352 and 354 run in application layer 350 supported by application framework layer 340 of mobile OS 130. Application framework layer 340 includes manager(s) 342 and service(s) 344 that are used by applications running on mobile OS 130. Libraries layer 330 includes user libraries 332 that implement common functions such as I/O and string manipulation, graphics functions, database capabilities, communication capabilities, and/or other functions and capabilities.

Application framework layer 340 may include a window manager, activity manager, package manager, resource manager, telephony manager, gesture controller, and/or other managers and services for the mobile environment. Application framework layer 340 may include a mobile application runtime environment that executes applications developed for mobile OS 130. The mobile application runtime environment may be optimized for mobile computing resources such as lower processing power and/or limited memory space.

Applications running on mobile OS 130 may be composed of multiple application components that perform the functions associated with the application, where each component is a separate process. For example, a mobile OS application may be composed of processes for displaying graphical information, handling user input, managing data, communicating with other applications/processes, and/or other types of processes.



Download full PDF for full patent description/claims.

Advertise on FreshPatents.com - Rates & Info


You can also Monitor Keywords and Search for tracking patents relating to this Foreground/background assortment of hidden windows patent application.
###
monitor keywords



Keyword Monitor How KEYWORD MONITOR works... a FREE service from FreshPatents
1. Sign up (takes 30 seconds). 2. Fill in the keywords to be monitored.
3. Each week you receive an email with patent applications related to your keywords.  
Start now! - Receive info on patent apps like Foreground/background assortment of hidden windows or other areas of interest.
###


Previous Patent Application:
User interface overlay system
Next Patent Application:
Method, system, and means for expressing relative sentiments towards subjects and objects in an online environment
Industry Class:
Data processing: presentation processing of document
Thank you for viewing the Foreground/background assortment of hidden windows patent info.
- - - Apple patents, Boeing patents, Google patents, IBM patents, Jabil patents, Coca Cola patents, Motorola patents

Results in 0.87033 seconds


Other interesting Freshpatents.com categories:
Qualcomm , Schering-Plough , Schlumberger , Texas Instruments ,

###

All patent applications have been filed with the United States Patent Office (USPTO) and are published as made available for research, educational and public information purposes. FreshPatents is not affiliated with the USPTO, assignee companies, inventors, law firms or other assignees. Patent applications, documents and images may contain trademarks of the respective companies/authors. FreshPatents is not affiliated with the authors/assignees, and is not responsible for the accuracy, validity or otherwise contents of these public document patent application filings. When possible a complete PDF is provided, however, in some cases the presented document/images is an abstract or sampling of the full patent application. FreshPatents.com Terms/Support
-g2-0.3154
     SHARE
  
           

FreshNews promo


stats Patent Info
Application #
US 20130024812 A1
Publish Date
01/24/2013
Document #
13399901
File Date
02/17/2012
USPTO Class
715810
Other USPTO Classes
International Class
06F3/048
Drawings
13


Graphics
Mobile Computing
Operating System
Windows
Concurrent
Desktop
Foreground
Graph
Mobile Operating System
Navigation
Computing Device
Mobile Computing Device


Follow us on Twitter
twitter icon@FreshPatents