US20110252430A1

US20110252430A1 - Opportunistic Multitasking

Info

Publication number: US20110252430A1
Application number: US12/869,553
Authority: US
Inventors: Gregory R. Chapman; Richard Schreyer; Thomas B. Duffy, JR.
Original assignee: Apple Inc
Current assignee: Apple Inc
Priority date: 2010-04-07
Filing date: 2010-08-26
Publication date: 2011-10-13
Also published as: EP2556432A2; WO2011126499A2; TW201135445A; KR20130048290A; JP2013524362A; CN102298538B; US20110249668A1; AU2010350737A1; CA2795489C; WO2011126499A3; CN103955403B; US20110252422A1; CN103955403A; US9104476B2; JP5723968B2; EP3508975A1; CA2795489A1; US20110252429A1; US9135059B2; CA2988269C

Abstract

Services for a personal electronic device are provided through which a form of background processing or multitasking is supported. The disclosed services permit user applications to take advantage of background processing without significant negative consequences to a user's experience of the foreground process or the personal electronic device's power resources. To effect the disclosed multitasking, one or more of a number of operational restrictions may be enforced. By way of example, an application that may normally be placed into the background state may instead be terminated if it controls a lock on a shared system resource.

Description

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Application Ser. No. 61/321,616 entitled “Opportunistic Multitasking” filed Apr. 7, 2010 and which is incorporated by reference in its entirety herein.

BACKGROUND

This disclosure relates generally to the field of computer science. More particularly, this disclosure relates to a technique for improving the user experience and power management in a personal electronic device.
Power constrained, hand-held devices (e.g., mobile phones, personal entertainment devices, and electronic pad computers) are resource limited compared to larger, fixed, systems such as desk-top, workstation and notebook computers. In such systems, the computational power available simply cannot support the execution of a large number of concurrent processes/threads without significantly degrading the user experience and consuming the device's limited power resources. In light of this recognition, system designers for these types of devices have traditionally permitted a limited multitasking capability at the operating system level (e.g., for core system functions), but have not supported multitasking at the user application level. While this approach has the benefit of minimizing the drain on the device's limited power resources, it also limits the ability to provide the user (via a user application) with an interactive environment.

SUMMARY

Services for a personal electronic device are provided through which a form of background processing or multitasking is supported. The disclosed services permit user applications to take advantage of background processing without significant negative consequences to a user's experience of the foreground process or the personal electronic device's power resources. Implementation of the disclosed services may be substantially transparent to the executing user applications and, in some cases, may be performed without the user application's explicit cooperation. To effect the disclosed multitasking, a number of operational restrictions may be enforced. A consequence of such restrictions may be that a process will not be able to do in background, what it may be able to do if it were in the foreground.
In one service, a foreground user application is transitioned to a non-executing state as it is moved out of the foreground state. In another service, a background process is given a maximum amount of time to complete a task before it is transitioned to a non-executing state. In still another service, audio applications (e.g., user applications generating or recording audio signals) are permitted to execute in background until, and unless, they are paused by a user. In yet another service, communication sockets instantiated for a user application may be maintained even if the user application instantiating same, is placed in a non-executing state (e.g., a voice over Internet Protocol user application). One illustrative type of application that can take advantage of this service is voice over Internet protocol (VOIP) user applications. In still other embodiments, user applications are permitted to receive notifications (e.g., location events) when in the non-executing state. Each of the disclosed services relies on or uses one or more restrictions that, in operation, can interfere with or prevent full-time multitasking operations. That is, the disclosed services permit multitasking only when it will not significantly interfere with the foreground process or unduly utilize the personal electronic device's power.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an illustrative thread scheduling scheme in accordance with one embodiment.

FIG. 2 shows, in flow chart form, a Task Completion service operation in accordance with one embodiment.

FIG. 3 shows, in flow chart form, an Audio service operation in accordance with one embodiment.

FIG. 4 shows, in flow chart form, a VOIP service operation in accordance with one embodiment.

FIG. 5 shows, in block diagram form, a personal electronic device in accordance with one embodiment.

FIG. 6 shows, in block diagram form, a personal electronic device in accordance with another embodiment.

FIG. 7 shows, in block diagram form, radio and location processing elements in accordance with one embodiment.

FIG. 8 shows, in block diagram form, a personal electronic device in accordance with one embodiment.

DETAILED DESCRIPTION

Services for a personal electronic device are provided through which a limited form of background processing or multitasking is supported. Use of one or more of the disclosed services, in combination with disclosed operating restrictions, permit user applications to execute in the background to give the user a robust interactive environment with little impact on the device's power resources. In some embodiments, background processing may be limited to the completion of a specific task, a specified amount of time (e.g., 5-30 minutes) or a particular type of task (e.g., audio operations). In other embodiments a user application may cease operation after notifying the operating system that it may be reanimated on the occurrence of one or more specified events. On reanimation, the application may perform additional operations in background. Implementation of the disclosed services may be substantially transparent to the executing user applications and, in some cases, may be performed without the user application's explicit cooperation.
As used herein, the phrase “personal electronic device” is a portable hand-held digital device such as a mobile phone, a personal digital assistant, a hand-held entertainment device, a pad or tablet computer system or a set top box (e.g., an Apple TV® or cable converter box). (APPLE TV is a registered trademark of Apple Inc.) As used herein, the term “service” refers to a utility, function or program code module that performs some task for a calling process, which has no user interface and which is accessed programmatically through a call interface such as an Application Programming Interface (API).
In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent to one skilled in the art, however, that the invention may be practiced without these specific details. In other instances, structure and devices are shown in block diagram form in order to avoid obscuring the invention. References to numbers without subscripts are understood to reference all instance of subscripts corresponding to the referenced number. Moreover, the language used in this disclosure has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the inventive subject matter, resort to the claims being necessary to determine such inventive subject matter. Reference in this specification to “one embodiment” or to “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least one embodiment of the invention, and multiple references to “one embodiment” or “an embodiment” should not be understood as necessarily all referring to the same embodiment.
It will be appreciated that in the development of any actual implementation numerous programming and component decisions must be made to achieve the developers' specific goals (e.g., compliance with system- and business-related constraints), and that these goals will vary from one implementation to another. It will also be appreciated that such development effort might be complex and time-consuming, but would nevertheless be a routine undertaking for those of ordinary skill in the personal computational device development field having the benefit of this disclosure.
To effect background processing or multitasking without significant negative consequences to a user's experience of the foreground process or the personal electronic device's power resources, a number of operational restrictions may be enforced. A consequence of such restrictions may be that a process will not be able to do in background, what it may be able to do if it were in the foreground.
As used herein, the phrase “foreground process” means that process that currently has access to system resources (e.g., the platform's central processing unit and graphical processing unit) and presents a user interface (UI) or graphical user interface (GUI) to a user. (Accordingly, the “foreground” is a state in which a foreground process executes.) In contrast, a “background process” is a process that may be scheduled to access system resources but which does not currently present a UI/GUI to a user. (Accordingly, the “background” is a state in which a background process executes.) As used herein, the term “process” means a user application. A user application, in turn, is an executable code module(s) that is capable of presenting a UI/GUI.
Operational Restrictions: The following illustrative list of operational restrictions may be enforced to limit the deleterious effect a background process may have on a foreground process.
1. Processor Scheduling. Foreground and background processes may be assigned different processor scheduling “priorities” in such a way that background processes do not interfere with foreground processes. One of ordinary skill in the art will recognize that in operational environments such as UNIX and Mach, processes are not scheduled, threads are. (UNIX is a registered trademark of the American Telephone and Telegraph Company.) It will further be recognized that a thread is that portion of a program, application or process that can run independently of, and concurrently with, other portions of the program, application or process.
Referring to FIG. 1, in one embodiment background threads may be assigned a priority from a band of priorities that overlaps in part with those priority levels assigned to foreground threads. The overlapping priority bands increase the likelihood that a background process/thread will make progress (i.e., execute) even when there is a foreground process/thread running. In this embodiment, to improve thread responsiveness it has been found beneficial to demote those threads (i.e., reduce their scheduling priority) that use their entire quantum without blocking for an input/output (I/O) operation. In one embodiment, a thread's priority is reduced by a single count every time it uses its full allotted quantum without blocking. (It will be recognized that a processes use of a full quantum is an indicator that the process is using the central processing unit.) In another embodiment, a thread's priority may be reduced by more than one count when this occurs. The amount of “overlap” in priority levels between the background band and the foreground band may be one (1) or more.
2. Disk Scheduling: In one embodiment, foreground threads are given priority over background threads when accessing system storage units (e.g., magnetic hard drives and solid state hard disk units). In addition, background processes (i.e., threads associated with processes in the background state) may be rate-limited in their access of system storage units.
3. Incoming Network Activity. In one embodiment, incoming network traffic may be moderated by dropping all packets destined for an application in the background or a non-executing state (e.g., suspended). Further, artificially small buffer sizes may be reported to distal network sites so as to throttle incoming TCP (Transmission control protocol) traffic. One of ordinary skill in the art will recognize that TCP has an existing set of traffic flow control mechanisms relating to buffer sizes, so that traffic isn't sent over a network faster than the recipient can handle it. As previously noted, in one embodiment artificially small buffer sizes may be reported so that the sender slows or stops the flow of incoming traffic.
4. Outgoing Network Activity. In one embodiment, network access is mediated through the use of two (2) queues; one for jobs associated with foreground processes and one for jobs associated with background processes. It has been found beneficial to give the foreground queue priority over the background queue. By way of example, the foreground queue may be given 100% priority over the background queue. At this setting, the only time a job in the background queue will be serviced is if the foreground queue is empty. In another embodiment, jobs in the foreground queue may be serviced in any desired ratio with those from the background queue, e.g., 90/10, 80/20, 75/27 or 50/50. In still another embodiment, once a job has been placed into a queue (e.g., the foreground queue) it is not moved if the job's associated process is subsequently placed into a different operating state (e.g., background). In yet another embodiment, a job's queue location is updated to reflect the operational status of its associated process.
5. Graphics Operations. In one embodiment such as, for example, the iPhone® Operating System, there are at least two mechanisms through which an application may write or paint to the display screen. (IPHONE is a registered trademark of Apple Inc.) A first mechanism is through the use of specialized hardware such as a graphics processing unit (GPU). A second mechanism is through use of one or more of the platform's central processing units (CPUs). By way of example, in the iPhone operating environment background processes are not permitted access to specialized graphics hardware; for example, any background process attempting to access the GPU may be terminated. By way of another example, background processes attempting to generate viewable graphics via the CPU are ignored—that is, any attempt to execute commands directed to using the CPU to write to a drawing buffer/memory are ignored. In some embodiments, drawing memory associated with a process/application placed into the background state may be marked as “purgeable.” Thus, if a foreground process needs more memory it may use (through standard memory allocation techniques) display memory originally granted to a process that is now in the background state.
6. Notifications. When a process transitions from the background state to the foreground state, it may be permitted to receive one (1) notification for each type of notification. More particularly, in one embodiment multiple notification events may be consolidated. For example, if a user rotates their personal electronic device (e.g., the iPhone) from portrait presentation to landscape presentation to portrait presentation and then back to landscape presentation, the resulting three (3) orientation notification events may be coalesced into a single notification—the last state, landscape. This can improve an application's response as it does not have to respond to multiple events. Illustrative notification types include orientation change notifications (for example, from accelerometer or gyroscope sensor input), address book database notifications (occurs when an address book entry is modified) and camera roll notifications (occurs when an image in a shared resource image library has been changed).
7. Locks. In one embodiment, any process that has a lock on a shared resource that is going into the suspended state may be terminated (rather than suspended). Illustrative shared resources include specialized graphics hardware and file descriptors. In another embodiment, a shared resource is “taken away” from a user application when it goes into the background state. For example, if an application (process) has a lock on camera hardware, this lock is removed when the user application is placed into the background state. As used herein, the “suspended state” is a condition in which a process is not permitted to schedule threads for execution, but whose state is retained in main memory.
8. Hardware Restrictions. In one embodiment background processes are prevented from gaining access to certain system hardware resources. Illustrative hardware not available to background processes include, but are not limited to: camera, GPU, accelerometer, gyroscope, proximity sensor and microphone.
9. Memory Management. In order to retain sufficient memory to accommodate executing processes, as the personal electronic device's core memory approaches a specified “critical” point, processes may be removed from memory. In one embodiment, a process so removed may be hibernated. In another embodiment a process so removed may be terminated. As used herein, the phrase “core memory” or “main memory” means a personal electronic device's main random access memory from which user applications execute; a “hibernated process” is a process whose operational state has been written to non-volatile memory so that (1) it cannot schedule threads for execution and (2) its main memory “footprint” is substantially zero; and a “terminated process” is a process whose operational state has been deleted and which, therefore, cannot be executed until restarted. In one embodiment, during the act of hibernation memory which can be recreated (purgeable) or reloaded (clean) on demand is disposed of; only memory that has been modified or otherwise un-reconstitutable is written to non-volatile memory. In another embodiment, a specified region of non-volatile memory is set aside at boot time for use as a “hibernation” memory. When a hibernated process is reanimated, its data in non-volatile memory is brought back into main memory, thereby freeing up space in non-volatile storage. In one embodiment, applications not accessed for more than a specified time may be “hibernated.”
Any desired approach for selection of which applications to remove from main memory may be made. For example, the least recently used application may be removed first. Alternatively, the largest currently non-executing application may be removed. In one embodiment, applications selected for removal that are greater than a specified size (e.g., 8 MB, 16 MB or 32 MB) may be terminated while applications less than the specified size may be hibernated. In still another embodiment, background audio user applications may be terminated only after suspended user applications have been terminated, but before foreground user applications.
Similarly, the “critical” point may be any value the designer wishes. Illustrative critical points include 50%, 75% and 90%. Using 75% as an exemplar critical point, applications would be selected for removal from main memory once the main memory reaches 50% of its capacity—for example, when a 256 megabyte (MB) main memory reaches 192 MB full.
Operational States: As an aid in understanding how the above restrictions are applied to the various services described below, Table 1 identifies and describes five (5) operational states for a user process executing on a personal electronic device.

TABLE 1

Operational States

Mode or
State	Description	Restrictions

Foreground	A process in this state	None.
	has access to system
	resources and currently
	presents a user
	interface to a user.
Background	A process in this state	Real-time processes are
	has access to system	subject to real-time
	resources but does not	restrictions (i.e., they
	currently present a user	are demoted to
	interface to a user.	non-real-time priorities
		when placed into
		background - except for
		audio and VOIP/network
		communication's
		applications); all other
		processes are subject to
		all other restrictions.
Suspended	A process in this state	Not eligible for
	has its operational	execution.
	state in main memory and
	could be scheduled for
	execution except for the
	fact that it has been
	suspended.
Hibernated	A process in this state	Not eligible for
	has had its operational	execution.
	state written to
	non-volatile memory.
	Only that information
	necessary to identify,
	locate and reanimate the
	process is retained in
	main memory.
Terminated	A process whose	Not eligible for
	operational state is no	execution.
	longer accessible in
	main memory.

As used herein, the term “non-executing state” means one of the suspended, hibernated or terminated states.

Illustrative Services: In the following, the “environment” within which the described services operate is the iPhone operating system. This is illustrative only, the disclosed services may be equally applicable to any personal electronic device.
1. Fast Task Switching Service. In the past, when an application left the foreground state in the iPhone operating system, it was simply terminated. The Fast-Task Switching service permits an application to receive notification that it is leaving the foreground state and, at that time, is given an opportunity to do some processing (e.g., a few seconds). After this time, the application is suspended (i.e., placed into the suspended state). In one embodiment, an operating environment in accordance with this disclosure can apply Fast Task-Switching to all executing processes (unless making use of another service as described below). In another embodiment, each application must specify programmatically that it may be suspended.
While suspended a process/application can execute no instructions. In a threaded operating environment such as Unix or Mach, this means that a process cannot schedule a thread for execution. In some embodiments, however, kernel efforts initiated on behalf of a process may continue to execute even after the process itself has been suspended (or hibernated or terminated). Illustrative “kernel efforts” include in-progress I/O operations and virtual memory and network buffer operations. Completion of such operations may or may not trigger the reanimation of the suspended process.
It is noted that process suspension of the type discussed here is different from system-level operations such as prior art “sleep” or “hibernate” actions—both of which are “system-wide” operations. In accordance with the prior art, no process may execute while in the sleep or hibernate mode. In contrast, the suspend mode described herein applies to individual processes; suspension of a first process does not interfere with the execution of a second process.
2. Task Completion Service. The Task Completion service provides a process with the limited ability to complete a task begun in the foreground state while in the background state. In one embodiment, background processes (i.e., processes executing in the background state) are throttled to avoid interfering with foreground processes. Illustrative tasks that are well suited to use this service are network upload and download operations, disk storage and retrieval operations and image processing operations (e.g., those operations that do not require specialized graphics hardware such as GPU). In one embodiment, a background process is permitted to continue processing (i.e., receiving CPU time in accordance with its scheduling priority as discussed above) until a specified event occurs. Illustrative events include a system timer (giving the process a specified amount of time to complete processing, e.g., 5 to 30 minutes of “clock time” or 5 millisecond of CPU time), loss of external power to the device, or activation of a primary or secondary display.
Referring to FIG. 2, illustrative Task Completion operation 200 begins when notice that a non-foreground user application (SECOND APP) is to be brought into the foreground (block 205). This may result from, for example, a user's request to start a second user application or an incoming call to a VOIP user application. If the currently foreground user application (FIRST APP) has not designated itself as an application capable of executing in background (the “NO” prong of block 210), FIRST APP is placed into a non-executing state (block 215) and SECOND APP is brought to the foreground (block 220). By way of example, FIRST APP may be suspended (i.e., placed into the suspended state). If FIRST APP has designated itself as an application capable of executing in background, such as though a p-list entry (the “YES” prong of block 210), FIRST APP is placed into the background state and given a specified amount of time to complete its current operation (block 225). SECOND APP may then be brought into foreground and permitted to execute (block 230). Once in background, FIRST APP may be scheduled to execute in due course (see discussion above regarding processor scheduling) (block 235). FIRST APP is permitted to execute in background until a specified event occurs (the “NO” prong of block 240) and it has not completed its task (the “NO” prong of block 245). Once either of the event occurs or the process completes its task (the “YES” prongs of blocks 240 and 245), FIRST APP may be placed into a non-executing state; for example, the suspended or terminated state.
In one embodiment, non-active foreground processes may be similarly limited in their ability to access full system resources. For example, one or more non-active foreground processes (i.e., a foreground process not currently receiving user input) may have their access to storage disks (restriction 2), incoming and outgoing network buffers (restrictions 3 and 4) and their ability to interact with specified hardware (restriction 8) limited in the same manner as described here for background processes. In like manner, on power loss all foreground processes except the active foreground process may be “pushed” into the background, where their behavior is thereafter controlled in accordance with the background processing regime described here.
In one embodiment, a process must declare programmatically that it wants to avail itself of the Task Completion service (e.g., during acts in accordance with block 210). This may be done, for example, by statically declaring the user application can avail itself of the Task Completion service though an API call, a p-list entry or a changeable setting specified by the user at install time or first run rime. In another embodiment, task completion is granted based on an application declaring, at run time and in code, that it is beginning an operation (then subsequently declaring that it has ended that operation). If such tasks are still outstanding when the application leaves the foreground state, the application may be granted some time to complete them. On occurrence of the specified event, or sooner if the task(s) completes, the application may be suspended. In yet another embodiment, any process or user application executing one of a specified number of eligible tasks may avail itself of the Task Completion service (e.g., one of the aforementioned operations). For example, any process executing a file upload or download operation could be placed into background in accordance with Task Completion service restrictions.
3. Audio Service. The Audio service permits a process or application to play or record audio while in the background state. In one embodiment, audio processes utilize real-time threads and are scheduled accordingly (See FIG. 1). While real-time processes are, in general, demoted to a non-real-time priority when placed into background, this is not true for an application using the Audio service (see discussion above). Because the described embodiments utilize real-time threads for audio applications, to minimize interference with foreground processes only one real-time audio process at a time may be allowed in background state. (It will be recognized that this number is merely illustrative. If the processing power of the personal electronic device is sufficient, multiple audio processes may be active in the background at the same time.)
Referring to FIG. 3, illustrative Audio service operation 300 begins when a foreground user application executing an audio operation (e.g., music playback or voice recording operations) receives notice that another user application not currently in the foreground (SECOND APP) is to be brought into the foreground (block 305). The user's audio application is then placed into background (block 310) and the SECOND APP is brought into foreground (block 315). In one embodiment, real-time background threads may be limited to execute from a specified set of libraries. For example, real-time background threads may be prevented from using third party libraries (e.g., libraries supplied by an application developer. At some point in the future, the user may issue a “pause” command to their background audio application (block 320). In response, the user's background audio application is moved from the background state to the suspended state (block 325). The audio application is kept in the suspended state until the user issues a “resume” command (the “YES” prong of block 330), after which the audio application is moved back into the background state where it may continue to execute it's audio operation (block 335). In another embodiment, the audio application may be placed into the hibernate mode rather than the suspended mode.
In some embodiments, a process may statically declare it can avail itself of the Audio service though an API call, a p-list entry or a changeable setting specified by the user at install time or first run rime. In other embodiments, any process either playing or recording audio may have the Audio service applied to it. When executing code within these applications, the associated process could not be suspended during audio operations in accordance with the Fast Task-Switching or Task Completion services.
4. Notification Service. The Notification service permits a process, in whatever state (foreground, background, suspended or hibernated), to receive and respond to messages. These messages may originate from an external source (a “push” notification) or the receiving process/application itself (“local” notification).
Generally speaking, on message receipt an operating system module (e.g., the “Springboard” application in the iPhone operating system) identifies the target application (i.e., that application the notification message is directed towards), launches that application in background and passes the message to the now reanimated application. In another embodiment, on message receipt the operating system (e.g., Springboard) generates a dialog box through which the user can elect to switch to the target application (i.e., the application to which the notification message is directed). If so elected, the target application is brought into foreground. (It will be recognized that if the target application is already in the background, it need not be reanimated.) The application is thereafter given an opportunity to respond to the message, including presenting a dialog to a user through, for example, an operating system request. Control of the receiving process is then provided in accordance with the relevant service (e.g., Fast Task Switching, Task Completion, Audio, VOIP or Location and Geo-Fencing). In another embodiment, notifications destined for a background process may be queued up and delivered at a later time (e.g., every 5 minutes) rather than being delivered substantially immediately after notification receipt.
5. Network Service. The Network service permits a suspended network application to maintain (i.e., keep alive) its communication socket(s). As used herein, a network application is a user application that uses network communication sockets. An illustrative network application is a user VOIP application. In the prior art when a user's network application/process is suspended, it loses its ability to maintain its communication socket(s) and, as a result, cannot continue to receive communication data (e.g., an incoming VOIP phone call).
Referring to FIG. 4, an illustrative Network service operation is demonstrated by VOIP service operation 400 which begins with a user's VOIP application being transitioned into the suspended state (block 405). In one embodiment, as a VOIP process is being transitioned into the suspended state it specifies to the operating system (e.g., to a network daemon) what time interval it requires for the sending of “heartbeat” messages (410). This daemon is responsible for reanimating the process when data is received at the processes associated socket(s) or on expiration of the specified time—the latter for heartbeat maintenance. For more information on this aspect, see U.S. Patent Publication 20090305732 entitled Managing Notification Service Connections and Displaying Icon Badges. Such application being incorporated in its entirety herein.
At some later time, the network daemon receives a message (block 415). The target application is then identified (block 420), reanimated into the background state (block 425) and passed the message (block 430). The background VOIP application may then respond to the message (e.g., an incoming VOIP call or a “heartbeat needed” message) (block 435). If the needed task was to issue a heartbeat, the VOIP application may be returned to the suspended state. If the needed task was to respond to an incoming VOIP call, the VOIP application may request the operating system issue a UI so that a user may select whether to accept or ignore the call. If the call is ignored, the VOIP application may be returned to the suspended state. If the call is to be answered, the VOIP application may be brought to the foreground (e.g., by means of the user selecting the appropriate element in a UI presented by the operating system). While it will be recognized that operating system daemons are well-known in the art, the maintenance of network communication (e.g., VOIP and wireless fidelity or WiFi) sockets for a suspended process in a personal electronic device of the type described herein is novel.
6. Location and Geo-Fencing Service. The Location and Geo-Fencing service permits a background or suspended process to receive notice (e.g., a message from on operating system daemon) when a specified location event occurs. Illustrative location events include, but are not limited to, arriving at a specified location, leaving a specified location, entering a specified region, leaving a specified region or moving a “significant” distance (where what constitutes “significant” can be specified by the user or the user application). In one embodiment, a process/application must declare programmatically that it wants to avail itself of the Location and Geo-Fencing Operation service (e.g., via a p-list parameter). In another embodiment, Geo-Fencing operations do not require the use of a p-list entry—all Geo-Fencing applications may avail themselves of the Geo-Fencing service.
In location operations, as long as a location tracking operation is underway, the application may be kept in background—receiving processing time in accordance with system scheduling mechanisms (see discussion above). In one embodiment, when a tracking operation either terminates or is otherwise halted, the process may be suspended (i.e., placed into the suspended state; the process could also be terminated or hibernated). Once the process responds to the message, it may quiesce (returning to the suspended state) or block in the background state awaiting the next message. In one embodiment the number of user applications using Location services in the background state relates to the usage of other system resources; for example, if system memory runs low, user applications currently performing location tracking may be terminated. In another embodiment, a centralized daemon aggregates all of the location requests (particularly with respect to the desired accuracy requested), and starts appropriate hardware for the most aggressive mode requested. For example, if one user application requests the user's location to within 3 kilometers (in which case mobile phone cell-based positioning may be used), a second user application requests the user's location to within 500 meters (in which case WiFi scanning may be used), and a third application requests the user's location to within 100 meters (for which GPS is necessary), GPS positioning may be used and all applications that are tracking location in the background will get the benefit of the finer positioning.
In geo-fencing operations, whenever a specified region boundary is crossed the process receives a message from the operating system (e.g., via a daemon). If the process is executing (e.g., during its allocated time while in background), it would be given the opportunity to process the message. If the application were not processing (e.g., it was in background and not processing or it was suspended or hibernated), the process/application would be reanimated after which it would be allowed to process the event (in background). In addition, if the process had been terminated, it may be reanimated into the background state in a manner similar to the Notification service described earlier. See the related disclosure entitled “Location-Based Application Program Management,” Ser. No. 12/123,456. In an embodiment where location processing uses a separate processor than that which executes the operating system for user application execution (hereinafter referred to as the “application processor”), location and geo-fencing operations of the type described here may occur even when the application processor is asleep. As with Location services, the number of user applications that may avail themselves of Geo-Fencing services in the background state relates to the usage of other system resources; for example, if system memory runs low, user applications currently performing location tracking may be terminated.
Personal Electronic Device Architecture: Referring to FIG. 5, in one embodiment personal electronic device 500 could implement one or more of the above services using one or more of the above-described restrictions to permit multitasking operations when it is beneficial to do so (e.g., opportunistic multitasking). As illustrated, user applications 505A to 505N interact with application launcher 510 (e.g., “Springboard” in the iPhone operating system) for standard operating system calls and multitasking services library 515 to access and make use of the above-described services.
Referring to FIG. 6, system 600 in accordance with another embodiment could also include radio means 605 and location processing means 610. As shown in FIG. 7, radio means 605 may include receiver circuit 700, transmitter circuit 705 and memory 710. Receiver and transmitter circuits 700 and 705 may be used to connect to, for example, a mobile telephone network, a satellite communications network or a digital computer network (e.g., the Internet via a local area network WiFi connection). Memory 710 may be used to store received data, data to be transmitted and operational parameter information as is known in the art. Interface 715 may be provided to facilitate communications between radio means 605 and location means 610. Location means 610 may include processor 720, memory 725 and operating system interface 730. In general, location means 610 receives requests for location updates and geo-fencing limits (e.g., from one or more user applications 505A to 505N through interface 730), processes location information received from radio means 605 (received via interface 715) and returns location information and updates to the requesting application(s) through interface 730. Processor 720 may be one or more off-the-shelf processors, one or more custom designed processors or a combination of off-the-shelf and custom designed processors. Memory 725 may be any form or combination of volatile and non-volatile solid state, magnetic or optical memories.
In one embodiment, one or more of the described services may be provided based on the availability of power. For example, if the personal electronic device is plugged into a power source (e.g., AC power), multitasking capabilities may be provided in accordance with standard modern operating system procedures (i.e., full or unrestricted multitasking). If, on the other hand, the personal electronic device is not plugged into a power source, multitasking capabilities may be provided in accordance with this disclosure (e.g., partial or opportunistic multitasking).
Referring to FIG. 8, personal electronic device 800 may be embodied in a physical apparatus that includes processing unit 805 and support devices 810. Processing unit 805 may include processor 815, memory 820 and input-output circuit 825. Device 800 may also include radio means 605 and location means 610 as shown. Input-output circuit 825 couples processor 815 and memory 820 to one or more display units 830 (e.g., a touch-screen display), one or more input-output devices 835 (e.g., touch-screen, keyboard, mouse, joy stick), one or more program storage devices 840 (e.g., magnetic, optic or solid-state memory) and other hardware 845 (e.g., a network interface). It is noted that in the architecture presented in FIGS. 6, 7 and 2 location and geo-fencing processing may continue via radio means 605 and location means 610 even when/if the application making the location or geo-fencing request (e.g., application 505A) has been suspended, hibernated or terminated. Further still, location and geo-fencing operations may continue even if application processor 815 is hibernated. That is, location and geo-fencing operations may continue via processor 720 regardless of what state application processor 815 is in.
Various changes in the materials, components, circuit elements, as well as in the details of the illustrated operational methods are possible without departing from the scope of the following claims. For instance, the provision of multitasking capabilities in accordance with this disclosure may be performed by a programmable control device executing instructions organized into one or more program modules. A programmable control device (e.g., processors 720 and 215) may include any programmable controller device including, for example, one or more members of the Intel Atom®, Core®, Pentium® and Celeron® processor families from Intel Corporation and the Cortex and ARM processor families from ARM or custom designed state machines. (INTEL, INTEL ATOM, CORE, PENTIUM, and CELERON are registered trademarks of the Intel Corporation. CORTEX is a registered trademark of the ARM Limited Corporation. ARM is a registered trademark of the ARM Limited Company.) Custom designed state machines may be embodied in a hardware device such as an integrated circuit including, but not limited to, application specific integrated circuits (“ASICs”) or field programmable gate array (“FPGAs”).
Storage devices suitable for tangibly embodying program instructions (e.g., memories 710, 725, 220 and 240) include, but are not limited to: magnetic disks (fixed, floppy, and removable) and tape; optical media such as CD-ROMs and digital video disks (“DVDs”); and semiconductor memory devices such as Electrically Programmable Read-Only Memory (“EPROM”), Electrically Erasable Programmable Read-Only Memory (“EEPROM”), Programmable Gate Arrays and flash devices.
Finally, it is to be understood that the above description is intended to be illustrative, and not restrictive. For example, the above-described embodiments may be used in combination with each other. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of the invention therefore should be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled. In the appended claims, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.”

Claims

1. A multitasking method, comprising:

identifying a first user application executing in a foreground state;

receiving user input directing that a second application is to be placed into the foreground state;

terminating the first user application if said first user application has at least one lock on a shared system resource, else placing the first user application in a background state in response to the received user input only if the first user application has identified itself as a user application that can execute in the background state; and

placing the second application into the foreground state.

2. The method of claim 1, further comprising scheduling the first user application, after the first user application has been placed into the background state, to use a processor in accordance with a priority level, the priority level being selected from a band of priority levels that overlap with some, but not all, priority levels assigned to foreground processes.

3. The method of claim 1, further comprising terminating the first user application, after the first user application has been placed into the background state, if the first user application attempts to execute instructions targeted for a specified hardware resource.

4. The method of claim 3, wherein the specified hardware resource comprises a graphics processing unit.

5. The method of claim 1, further comprising not executing instructions for the first user application, once the first user application is in the background state, if the instructions are directed to changing a display memory.

6. The method of claim 1, wherein the shared system resource comprises a shared file descriptor.

7. The method of claim 1, wherein the act of placing the second application into the foreground state comprises placing an operating system application into the foreground state.

8. A program storage device, readable by a programmable control device, comprising instructions stored thereon for causing the programmable control device to perform a method in accordance with claim 1.

9. A personal electronic device, comprising:

memory;

a programmable control device operatively coupled to the memory, said programmable control device configured to execute instructions, stored in the memory, to—

identify a first user application executing in a foreground state;

receive user input directing that a second application is to be placed into the foreground state;

terminate the first user application if said first user application has at least one lock on a shared system resource, else placing the first user application in a background state in response to the received user input only if the first user application has identified itself as a user application that can execute in the background state; and

place the second application into the foreground state.

10. The personal electronic device of claim 9 comprising a personal electronic device selected from the group consisting of: a mobile telephone, a personal digital assistant, a hand-held entertainment device, a pad computer system and a set top box.

11. The personal electronic device of claim 9, wherein the second application comprises a second user application.