System and method for displaying notifications received from multiple applications

The electronic device's notification module aggregates and customizes notifications from multiple applications, addressing the inefficiency of managing numerous notifications by providing a pull-down menu and banners with customizable settings, improving user access and organization.

JP2024164010AActive Publication Date: 2024-11-26APPLE INC
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
JP2024117897
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Priority Date
2011-06-05
Filing Date
2024-07-23
Publication Date
2024-11-26
Estimated Expiration
2032-06-05

AI Technical Summary

Technical Problem

Existing electronic devices face challenges in efficiently organizing and accessing numerous application-based notifications, leading to clutter and inefficiency, especially when users need to access individual applications to view these notifications.

Method used

An electronic device with a touch-sensitive input/output device and a notification module that interacts with application programming interfaces to aggregate and customize notifications, allowing users to view them in a locked or unlocked state through a pull-down menu, notification center, and banners, with customizable settings.

Benefits of technology

Provides an intuitive and efficient way to manage and access notifications from multiple applications, enhancing user experience by organizing and presenting them in a streamlined manner, regardless of the device's lock status.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024164010000001_ABST
    Figure 2024164010000001_ABST
Patent Text Reader

Abstract

To provide systems and methods for displaying notifications received from multiple applications.SOLUTION: An electronic device including a display are configured to: display a first notification having a first appearance, via a display, the first notification corresponding to an application; detect a first input that starts at a specific location outside a location of the first notification, on the display; and display, in response to the detection of the first input, a second notification having a second appearance different from the first appearance, via the display, the second notification corresponding to the first notification.SELECTED DRAWING: Figure 8F
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The disclosed embodiments relate generally to electronic devices, and more particularly to electronic devices that display notifications received from multiple applications. [Background technology]

[0002] Today's portable electronic devices can integrate multiple functions. These devices have the ability to run multiple applications. In particular, some of these applications may generate trigger events that can cause notifications to be displayed.

[0003] Because electronic devices can store many applications, application-based notifications can also become numerous and unwieldy, especially when a user must access each individual application to view the application-specific notifications. Thus, there is a need for a more efficient and intuitive approach to organize these notifications and make them readily accessible. Summary of the Invention

[0004] A system and method for displaying notifications received from multiple applications is disclosed. The electronic device may have a touch-sensitive input / output (I / O) device (e.g., a touch screen) with a graphical user interface (GUI), one or more processors, memory, and one or more modules, programs, or instructions stored in the memory for performing a number of functions.

[0005] In particular, the electronic device can include a notification module capable of interacting with one or more application programming interfaces (APIs) for generating various types of notifications when the device is in a locked or unlocked state. Additionally, the notification module can provide options for customizing notification settings.

[0006] In some embodiments, the notification module can monitor notifications received from multiple applications. In response to receiving a notification, the notification module can control how notifications are displayed when the electronic device is operating in a locked or unlocked state. In some embodiments, the electronic device allows a user to customize how notifications are displayed when the electronic device is in a locked and / or unlocked state.

[0007] In some embodiments, when the electronic device is operating in a locked state, the notification module may display a pull-down menu that allows the user to view notifications that have been received.

[0008] In some embodiments, the notification module can aggregate received notifications and provide the aggregated notifications as multiple panes in a notification center, where each pane of the notification center can be associated with a different application. Additionally, the notification module can display banners corresponding to one or more notifications received from different applications.

[0009] One or more APIs that interact with the notification module can exist in an environment where a calling program communicates with other program code that is being called through one or more interfaces. Various function calls, messages or other types of calls, which may include various types of parameters, may be transferred between the calling program and the called code through the API. Additionally, an API may provide a calling program with the ability to use data types or classes that are defined in the API and implemented in the called program code.

[0010] At least some embodiments include an environment in which a calling software component communicates with a called software component through an API, and a method of operating through the API in this environment includes transmitting one or more function calls, messages, and / or other types of calls or parameters through the API.

[0011] The above and other aspects of the present invention will become more apparent from the following detailed description considered in conjunction with the accompanying drawings in which like reference characters refer to like parts and in which: [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a block diagram of an electronic device configured in accordance with various embodiments of the present invention. [Diagram 2] FIG. 1 is a block diagram of an electronic device configured in accordance with various embodiments of the present invention. [Diagram 3] FIG. 1 is a block diagram of an application programming interface (API) architecture according to various embodiments of the present invention. [Figure 4] FIG. 1 is a block diagram of an application programming interface (API) architecture according to various embodiments of the present invention. [Diagram 5] 1A-1C illustrate display screens associated with a home screen of an electronic device according to various embodiments of the present invention. [Figure 6A] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 6B] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 6C] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 6D] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 6E] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 6F] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 6G] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 6H] 1A-1C illustrate display screens associated with an exemplary notification center according to various embodiments of the present invention. [Figure 7A] 1 is a diagram of an exemplary banner display screen according to various embodiments of the present invention. [Figure 7B] 1 is a diagram of an exemplary banner display screen according to various embodiments of the present invention. [Figure 7C] 1 is a diagram of an exemplary banner display screen according to various embodiments of the present invention. [Figure 7D] 1 is a diagram of an exemplary banner display screen according to various embodiments of the present invention. [Figure 7E] 1 is a diagram of an exemplary banner display screen according to various embodiments of the present invention. [Figure 8A] 1A-1C are diagrams of display screens according to various embodiments of the present invention for displaying notifications when the electronic device is operating in a locked state. [Figure 8B] 1A-1C are diagrams of display screens according to various embodiments of the present invention for displaying notifications when the electronic device is operating in a locked state. [Figure 8C] 1A-1C are diagrams of display screens according to various embodiments of the present invention for displaying notifications when the electronic device is operating in a locked state. [Figure 8D] 1A-1C are diagrams of display screens according to various embodiments of the present invention for displaying notifications when the electronic device is operating in a locked state. [Figure 8E] 1A-1C are diagrams of display screens according to various embodiments of the present invention for displaying notifications when the electronic device is operating in a locked state. [Figure 8F]1A-1C are diagrams of display screens according to various embodiments of the present invention for displaying notifications when the electronic device is operating in a locked state. [Figure 9A] 11A-11C are diagrams of display screens relating to customizing notification settings according to various embodiments of the present invention. [Figure 9B] 11A-11C are diagrams of display screens relating to customizing notification settings according to various embodiments of the present invention. [Figure 9C] 11A-11C are diagrams of display screens relating to customizing notification settings according to various embodiments of the present invention. [Figure 9D] 11A-11C are diagrams of display screens relating to customizing notification settings according to various embodiments of the present invention. [Figure 9E] 11A-11C are diagrams of display screens relating to customizing notification settings according to various embodiments of the present invention. [Figure 9F] 11A-11C are diagrams of display screens relating to customizing notification settings according to various embodiments of the present invention. [Figure 10A] 1A-1C are diagrams of display screens relating to notifications according to various embodiments of the present invention. [Figure 10B] 1A-1C are diagrams of display screens relating to notifications according to various embodiments of the present invention. [Figure 10C] 1A-1C are diagrams of display screens relating to notifications according to various embodiments of the present invention. [Figure 11] 4 is a flowchart of an exemplary process for displaying pull-down options in response to receiving multiple notifications according to various embodiments of the present invention. [Figure 12] 4 is a flowchart of an exemplary process for displaying a notification center according to various embodiments of the present invention. [Figure 13] 4 is a flowchart of an exemplary process for providing a banner according to various embodiments of the present invention. [Figure 14] 4 is a flowchart of an exemplary process for providing notification settings according to various embodiments of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] A system and method for displaying notifications received from multiple applications is provided.

[0014] 1 illustrates a block diagram of an electronic device 100 that includes a touch I / O device 102 capable of accepting touch input for interacting with a computing system 104 over a wired or wireless communication channel 106. The touch I / O device 102 can be used to provide user input to the computing system 104 instead of, or in combination with, other input devices such as a keyboard or mouse. One or more touch I / O devices 102 may be used to provide user input to the computing system 104. The touch I / O device 102 may be an integrated part of the computing system 104 (e.g., a touch screen in a notebook computer) or may be separate from the computing system 104.

[0015] Touch I / O device 102 may include a touch-sensitive panel that is fully or partially transparent, semi-transparent, non-transparent, opaque, or any combination thereof. Touch I / O device 102 may be embodied as a touchscreen, a touchpad, a touchscreen functioning as a touchpad (e.g., a touchscreen replacing the touchpad of a notebook computer), a touchscreen or touchpad combined or integrated with another input device (e.g., a touchscreen or touchpad located over a keyboard), or any multi-dimensional object having a touch-sensitive surface for accepting touch input.

[0016] In one example, touch I / O device 102 implemented as a touch screen may include a transparent and / or translucent touch-sensitive panel disposed in whole or in part over at least a portion of a display. According to this embodiment, touch I / O device 102 functions to display image data transmitted from computing system 104 (and / or other sources) and to accept user input. In another embodiment, touch I / O device 102 may be implemented as an integrated touch screen, in which a touch-sensing component / device is integrated with a display component / device. In yet another embodiment, the touch screen may be used as an auxiliary or additional display screen that displays the same image data as the primary screen or additional image data.

[0017] The touch I / O device 102 may be configured to detect the location of one or more touches or near-touches relative to the touch I / O device 102 based on capacitive, resistive, optical, acoustic, inductive, mechanical, chemical measurements, or any measurable phenomenon related to the occurrence of one or more touches or near-touches in the vicinity of the touch I / O device 102. The detected touch measurements may be processed using software, hardware, firmware, or a combination thereof to identify and track one or more gestures. A gesture may correspond to one or many stationary or moving touches or near-touches on the touch I / O device 102. A gesture may be implemented by moving one or more fingers or other objects substantially simultaneously, consecutively, or continuously in a particular manner on the touch I / O device 102, such as tapping, pressing, rocking, rubbing, twisting, rotating, pressing with varying pressure, or the like. A gesture may be characterized by, but is not limited to, a pinch, slide, swipe, rotate, flex, drag, or tapping motion between one or more other fingers. A gesture may be performed with one or more hands, by one or more users, or by a combination thereof.

[0018] The computing system 104 may drive a display with image data to display a graphical user interface (GUI). The GUI may be configured to accept touch input through the touch I / O device 102. If implemented as a touch screen, the touch I / O device 102 may display the GUI. Alternatively, the GUI may be displayed on a display separate from the touch I / O device 102. The GUI may include graphical elements that are displayed at specific locations within the interface. The graphical elements may include, but are not limited to, various displayed virtual input devices, such as a virtual scroll wheel, a virtual keyboard, a virtual knob, a virtual button, any virtual UI, etc. A user may perform gestures at one or more specific locations that may be associated with graphical elements of the GUI of the touch I / O device 102. In another embodiment, a user may perform gestures at one or more locations that are not related to graphical elements of the GUI. A gesture performed on the touch I / O device 102 may directly or indirectly manipulate, control, modify, move, activate, initiate, or generally affect a cursor, an icon, a media file, a list, text, all or part of an image, etc., within the GUI. For example, in the case of a touchscreen, a user may directly interact with image elements on the touchscreen by making gestures over the image elements. Instead, touchpads generally provide indirect interaction. Gestures may also affect non-displayed GUI elements (e.g., GUI elements that cause a user interface to be displayed) or may affect other operations within the computing system 104 (e.g., affecting the state or mode of the GUI, applications, or OS). Gestures may or may not be performed on the touch I / O device 102 in conjunction with a displayed cursor. For example, if a gesture is made on a touchpad, a cursor (or pointer) may be displayed on the display screen or touchscreen, and the cursor may be controlled through touch input on the touchpad to interact with image elements on the display screen.In another embodiment where gestures are made directly on the touch screen, the user can directly interact with objects on the touch screen, with or without a cursor or pointer displayed on the touch screen.

[0019] In response to or based on a touch or near-touch on the touch I / O device 102, feedback may be provided over the communication channel 106. The feedback may be transmitted in an altered or unaltered manner, optically, mechanically, electrically, olfactory, aural, etc., or any combination thereof.

[0020] Next, an embodiment of a system architecture is described that may be implemented in any portable or non-portable device, including a communication device (e.g., a mobile phone, a smartphone), a multimedia device (e.g., an MP3 player, a TV, a radio), a portable or handheld computer (e.g., a tablet, a notebook, a laptop), a desktop computer, an all-in-one desktop, a peripheral device, or any other system or device that can be adapted to include the system architecture 2000, or a combination of two or more of these devices. FIG. 2 is a block diagram of a system 200 that may include one or more computer-readable media 201, a processing system 204, an input / output (I / O) subsystem 206, a radio frequency (RF) circuitry 208, and an audio circuitry 210. These components may be connected by one or more communication buses or signal lines 203. The system 200 may be the same as or similar to the electronic device 100 (FIG. 1).

[0021] It will be appreciated that the architecture depicted in Figure 2 is one example architecture for system 200, and that system 200 may have more or fewer components and different configurations of components than those depicted. The various components depicted in Figure 2 may be implemented in hardware, software, firmware, or any combination thereof, including one or more signal processing and / or application specific integrated circuits.

[0022] The RF circuitry 208 is used to send and receive information to one or more other devices over a wireless link or network, and includes well-known circuitry for performing that function. The RF circuitry 208 and the audio circuitry 210 may be connected to the processing system 204 through a peripheral interface 216. The interface 216 may include various known components for establishing and maintaining communication between the peripheral devices and the processing system 204. The audio circuitry 210 may be connected to an audio speaker 250 and a microphone 252, and includes well-known circuitry for processing audio signals received from the interface 216 so that the user can communicate with other users in real time. In some embodiments, the audio circuitry 210 includes a headphone jack (not shown).

[0023] A peripheral interface 216 can connect input and output peripherals of the system to the processor 218 and the computer readable medium 201. One or more processors 218 can communicate with one or more computer readable media 201 through a controller 220. The computer readable medium 201 can be any device or medium capable of storing code and / or data for use by one or more processors 218. The medium 201 can have a memory hierarchy including, but not limited to, cache, primary memory, and secondary memory. The memory hierarchy can be implemented using any combination of magnetic and / or optical storage devices such as RAM (e.g., SRAM, DRAM, DDRAM), ROM, flash, disk drives, magnetic tape, CDs (compact discs), and DVDs (digital video discs). The medium 201 can also include a transmission medium for carrying information-bearing signals, indicative of computer instructions or data, which may or may not use a carrier wave to modulate the signals. For example, the transmission medium may include, but is not limited to, communications networks including the Internet (also known as the World Wide Web), one or more intranets, local area networks (LANs), wide local area networks (WLANs), storage area networks (SANs), metropolitan area networks (MANs), and the like.

[0024] The one or more processors 218 may execute various software components stored on the medium 201 to perform various functions for the system 200. In some embodiments, the software components include an operating system 222, a communications module (or instruction set) 224, a touch processing module (or instruction set) 226, a graphics module (or instruction set) 228, one or more applications (or instruction sets) 230, and a notification module 238. Each of these modules and the applications described above corresponds to an instruction set for performing one or more of the functions described above and methods (e.g., computer-implemented methods and other information processing methods described herein). These modules (e.g., instruction sets) may not be implemented as separate software programs, procedures, or modules, and thus various subsets of these modules may be combined or reconfigured in various embodiments. In some embodiments, the medium 201 may store a subset of the modules and data structures described above. Additionally, the medium 201 may store additional modules and data structures not described above.

[0025] Operating system 222 may include various procedures, instruction sets, software components, and / or drivers for controlling and managing general system tasks (e.g., memory management, storage control, power management, etc.) and facilitate communication between various hardware and software components.

[0026] The communications module 224 facilitates communication with other devices through one or more external ports 236 or the RF circuitry 208 and includes various software components for handling data received from the RF circuitry 208 and / or the external port 236.

[0027] Graphics module 228 can include various known software components for rendering, animating, and displaying graphical objects on a display surface. In embodiments in which touch I / O device 102 is a touch-sensitive display (e.g., a touch screen), graphics module 228 includes components for rendering, displaying, and animating objects on the touch-sensitive display.

[0028] The one or more applications 230 may include any application installed on the system 200, including, but not limited to, a browser, address book, contacts, email, instant messaging, word processing, keyboard emulation, widgets, JAVA®-enabled applications, encryption, digital rights management, voice recognition, voice synthesis, location determination capabilities (such as provided by a GPS), music player, etc.

[0029] Touch processing module 226 includes various software components for performing various tasks related to touch I / O device 212, including, but not limited to, receiving and processing touch input received from I / O device 212 via touch I / O device controller 232. For example, touch processing module 226 may further include software components for performing tasks related to other I / O devices 214. That is, touch processing module 226 may receive and process input received from I / O device 214 via other I / O controller 234.

[0030] The system 200 may further include a notification module 238 for performing methods / functions as described herein in conjunction with Figures 5-14. The notification module 238 functions to at least monitor notifications received from multiple applications (e.g., multiple applications on the system 200 and data providers transmitting data to the system 200). For example, the notification module 238 may receive notifications from both non-third-party applications and third-party applications. Additionally, the notification module 238 may receive push-based notifications, trigger-based notifications, and / or other types of personal notifications.

[0031] In response to receiving a notification, the notification module 238 can control how notifications are displayed when the system 200 is operating in a locked or unlocked state. For example, when the system 200 is operating in a locked state, the notification module 238 can display notifications in a banner and can control how these notifications are displayed. As another example, the notification module 238 can aggregate multiple received notifications and provide the aggregated notifications as multiple panes in a notification center. Thus, each pane may be associated with a different application. In some embodiments, the notification module 238 can allow a user to customize how notifications are displayed in the system 200.

[0032] In the locked state, system 200 may restrict user access to certain functions. For example, in the locked state, the user may be prevented from initiating various device functions such as making calls or entering emails. That is, the locked state is designed to prevent unintended access to system 200. When system 200 is in the unlocked state, the user has full access to all system functions.

[0033] Additionally, the notification module 238 may provide the data provider with specific data formats that allow the data provider to target specific notifications to various users. Those skilled in the art will appreciate that any suitable format may be utilized. For example, to display a notification on the system 200, the notification module 238 may request the data provider to specify a title (e.g., a user name), a subtitle (e.g., a subtitle of an incoming message or alert), and a body (e.g., the body of the message).

[0034] The notification module 238 may further communicate with the touch processing module 226 to receive user input. Additionally, the notification module 238 may communicate with the graphics module 228 to display various graphical objects on the display. The notification module 238 may be implemented as hardware, software, firmware, or a combination thereof. Although the notification module 238 is illustrated as residing within the medium 201, all or a portion of the notification module 238 may be implemented within other components within the system 200, or the entirety of the notification module 238 may be implemented as a separate component within the system 200.

[0035] The I / O subsystem 206 interfaces with a touch I / O device 212 and one or more other I / O devices 214 to control or perform various functions. The touch I / O device 212 communicates with the processing system 204 via a touch I / O device controller 232 and includes various components for processing user touch input (e.g., scanning hardware). One or more of the other input controllers 234 receive / send electrical signals from / to the other I / O devices 214. The other I / O devices 214 may include physical buttons, dials, slide switches, sticks, keyboards, touch pads, additional display screens, or any combination thereof.

[0036] When implemented as a touchscreen, the touch I / O device 212 displays visual output to the user in the GUI. The visual output may include text, graphics, video, and any combination thereof. Some or all of the visual output may correspond to user interface objects. The touch I / O device 212 forms a touch-sensitive surface that accepts touch input from the user. The touch I / O device 212 and touchscreen controller 232 (along with associated modules and / or instruction sets in medium 201) detect and track touch or near-touch (and the movement or release of touch) on the touch I / O device 212 and translate the detected touch input into interaction with graphical objects, such as one or more of the user interface objects. When the device 212 is implemented as a touchscreen, the user can directly interact with the graphical objects displayed on the touchscreen. On the other hand, when the device 212 is implemented as a touch device other than a touchscreen (e.g., a touchpad), the user can indirectly interact with the graphical objects displayed on a separate display screen implemented as the I / O device 214.

[0037] Touch I / O device 212 may be similar to a multi-touch sensitive surface as described in U.S. Pat. Nos. 6,323,846, 6,570,557 to Westerman et al., and / or U.S. Pat. No. 6,677,932 to Westerman, and / or U.S. Patent Publication No. 2002 / 001502 A1, each of which is incorporated herein by reference.

[0038] In embodiments in which touch I / O device 212 is a touchscreen, the touchscreen may use LCD (liquid crystal display) technology, LPD (light emitting polymer display), OLED (organic LED), or OEL (organic electroluminescence), although other display technologies may be used in other embodiments.

[0039] Feedback may be provided by touch I / O device 212 based on the currently displayed and / or state or status of the computing system and the user's touch input. Feedback may be conveyed in a variable or unvaried manner, optically (e.g., light signals or displayed images), mechanically (e.g., haptic feedback, touch feedback, force feedback, etc.), electrically (e.g., electrical stimulation), olfactory, auditory (e.g., beeps, etc.), or any combination thereof.

[0040] System 200 can include a power system 244 for providing power to the various hardware components, and may also include a power management system, one or more power sources, a charging system, power fault detection circuitry, power converters or inverters, power status indicators, and any other components specifically related to the generation, management, and distribution of power within a portable device.

[0041] In some embodiments, the peripherals interface 216, the one or more processors 218, and the memory controller 220 may be implemented on a single chip, such as the processing system 204. In other embodiments, they may be implemented on separate chips.

[0042] The notification module 238 can interface with one or more application programming interfaces (APIs) to provide a notification center capable of generating various types of notifications when the system 200 is in a locked or unlocked state. Additionally, the notification module 238 can provide multiple settings for customizing the notification center.

[0043] An API is an interface implemented by a program code component or hardware component (hereafter, API-implementing component) that allows a different program code component or hardware component (hereafter, API-invoking component) to access or use one or more functions, methods, procedures, data structures, classes, and / or other services provided by the API-implementing component. An API may define one or more parameters to be passed between the API-invoking component and the API-implementing component.

[0044] An API allows a developer of an API-invoking component (which may be a third-party developer) to exploit a particular functionality provided by an API-implementing component. There may be one or more API-invoking components. An API may be a source code interface provided by a computing system or program library to support service requests from applications. An operating system (OS) may have multiple APIs, one or more of which may be called by applications running on the OS, and a service (such as a program library) may have multiple APIs, one or more of which may be called by applications that use the service. An API may be specified in terms of a programming language that can be translated or compiled when an application is built.

[0045] In some embodiments, an API-implementing component may provide multiple APIs, each of which provides a different way of accessing or a different view of a different aspect of the functionality implemented by the API-implementing component. For example, one API of the API-implementing component may provide a first set of functionality and may be exposed to third-party developers, while another API of the API-implementing component may be hidden (not exposed) and provide a subset of the first set of functionality plus another set of functionality not included in the first set of functionality, such as testing and debugging functionality. In other embodiments, the API-implementing component may itself call one or more other components via underlying APIs, such that the API-implementing component also doubles as an API calling component.

[0046] An API specifies the language and parameters that an API calling component uses to access and use the specified functionality of the API implementing component. For example, an API calling component accesses the specified functionality of the API implementing component through one or more API calls or invocations exposed by the API (e.g., implemented by function or method invocations) and passes data and control information using parameters through the API calls or invocations. An API implementing component can return values ​​through the API in response to an API call from an API calling component. While an API specifies the syntax and results of an API call (e.g., how to invoke the API and what the API call does), the API may not reveal how the API call achieves the functionality specified in the API call. Various API calls are routed through one or more application programming interfaces between the call (API calling component) and the API implementing component. The route of an API call may include issuing, initiating, invoking, invoking, receiving, replying, or responding to a function call or message. That is, the route may describe an action by either the API calling component or the API implementing component. A function call or other invocation of an API may send or receive one or more parameters through a parameter list or other structure. A parameter may be a constant, a key, a data structure, an object, an object class, a variable, a data type, a pointer, an array, or a list or pointer to a function, method, or other way to reference the data to be passed via the API.

[0047] Additionally, data types or classes may be provided by the API and implemented by an API implementing component, such that an API calling component may use the conventions provided in the API to declare variables, use pointers, and use or instantiate constants of such types or classes.

[0048] In general, an API can be used to access services or data provided by an API-implementing component or to initiate the execution of an operation or computation provided by the API-implementing component. By way of example, the API-implementing component and the API-calling component may each be one of an operating system, a library, a device driver, an API, an application program, or other module (it should be understood that the API-implementing component and the API-calling component may be the same or different types of modules). The API-implementing component may in some cases be implemented at least in part in firmware, microcode, or other hardware logic. In some embodiments, an API allows a client program to use services provided by a software development kit (SDK) library. In other embodiments, an application or other client program may use an API provided by an application framework. In some embodiments, the application or client program may incorporate calls to functions or methods provided by the SDK and the API, or use data types or objects defined in the SDK and provided by the API. In these embodiments, the application framework may provide a main event loop for the program to respond to various events defined in the framework. The API allows an application to specify an event and use the application framework to respond to the event. In some embodiments, API calls may report to applications the capabilities or status of hardware devices related to aspects such as input capabilities and status, output capabilities and status, processing capabilities, power status, storage capacity and status, communication capabilities, etc., and the API may be implemented in part in firmware, microcode, or other low-level logic that runs in part on the hardware components.

[0049] An API invocation component may be a local component (e.g., residing on the same data processing system as the API implementing component) or a remote component (e.g., residing on a different data processing system than the API implementing component) that communicates with the API implementing component over a network through an API. It should be understood that an API implementing component may act as an API invocation component (e.g., may make an API call to an API exposed by another API implementing component) and an API invocation component may act as an API implementing component by implementing an API exposed to another API invocation component.

[0050] Although an API may be implemented with respect to a particular programming language, an API may allow multiple API calling components written in different programming languages ​​to communicate with the API implementing component (and thus the API may include functionality for translating calls and responses between the API implementing and API calling components). In one embodiment, an API calling component may call multiple APIs from different providers, such as one set of APIs from an OS provider, another set of APIs from a plug-in provider, another set of APIs from another provider (e.g., a provider of a software library) or another creator of another set of APIs.

[0051] FIG. 3 is a block diagram illustrating an example API architecture 300 that may be used in some embodiments of the present invention. As shown in FIG. 3, the API architecture 300 includes an API-implementing component 302 (e.g., an operating system, library, device driver, API, application program, software, or other module) that implements an API 304. The API 304 defines one or more functions, methods, classes, objects, protocols, data structures, formats, and / or other features of the API-implementing component 302 that may be used by an API-invoking component 306. The API 304 may define at least one calling convention for how functions in the API-implementing component 302 receive parameters from the API-invoking component 306 and how the functions return results to the API-invoking component 306. The API-invoking component 306 (e.g., an operating system, library, device driver, API, application program, software, or other module) makes an API call through the API 304 to access and use the functionality of the API-implementing component 302 defined by the API 304. The API-implementing component 302 may return a value through the API 304 to the API-invoking component 306 in response to the API call.

[0052] It will be apparent that the API-implementing component 302 may include additional functions, methods, classes, data structures, and / or other functionality that are not defined through the API 304 and available to the API invocation component 306. It is to be understood that the API invocation component 306 may be on the same system as the API invocation component 302 or may be located remotely and access the API invocation component 302 over a network using the API 304. Although Figure 3 shows only one API invocation component 306 interacting with the API 304, it is to be understood that other API invocation components, which may be written in other languages ​​(or the same language) as the API invocation component 306, may use the API 304.

[0053] The API implementation component 302, the API 304, and the API calling component 306 may be stored on a machine-readable medium, which includes any mechanism for storing information in a form readable by a machine (e.g., a computer or other data processing system). For example, machine-readable media include magnetic disks, optical disks, random access memory, read-only memory, flash memory devices, and the like.

[0054] In the exemplary embodiment of Figure 4 (software stack), an application can make calls to service A or B using some service APIs and to the operating system (OS) using some OS APIs. Services A and B can make calls to the OS using some OS APIs.

[0055] Service 2 has two APIs, one (Service 2 API1) that receives calls from Application 1 and returns values ​​to Application 1, and the other (Service 2 API2) that receives calls from Application 2 and returns values ​​to Application 2. Service 1 (which may be, for example, a software library) makes calls to OS API1 and receives return values ​​from OS API1. Service 2 (which may be, for example, a software library) makes calls to both OS API1 and OS API2 and receives return values ​​from both OS API1 and OS API2. Application 2 makes calls to OS API2 and receives return values ​​from OS API2.

[0056] As described above, a notification module (e.g., notification module 238 of FIG. 2) of the electronic device can receive notifications from applications and control how the notifications are provided to the user. For example, the notification module can aggregate multiple notifications received from different applications and provide the aggregated notifications as a series of panes (or lists) in a notification center. Thus, by accessing the notification center, a user can view a list of recently received notifications. In some cases, the notification center may only be accessible when the electronic device is operating in an unlocked state.

[0057] Any suitable technique can be used to activate the notification center. For example, a user may activate the notification center by pressing a button on the electronic device. As another example, if the electronic device (e.g., electronic device 100 of FIG. 1 or system 200 of FIG. 2) is a device in which operation of a predefined set of functions of the device is performed through a touch screen and / or touch pad (e.g., touch I / O device 212), the user can activate the notification center by touching or touching an image on the touch screen.

[0058] For example, referring to Figure 5, a display screen 500 of a home screen of an electronic device is shown. The display screen 500 may be the same as or may be capable of interacting with the touch I / O device 212 of Figure 2. The display screen 500 may include a number of selectable icons 502.

[0059] The notification module may be configured to accept multiple gestures to launch the notification center. For example, a user may perform a gross swipe gesture by quickly flicking one or more fingers downward from the top of screen 500. As another example, a user may slowly drag one or more fingers downward from the top of screen 500.

[0060] The notification module can detect a user swipe or drag in a particular region of the screen 500 (e.g., the top 20 pixel region of the screen 500). Specifically, when the notification module detects that there is movement in multiple pixels within the 20 pixel region, the notification module can initiate the display of a notification center.

[0061] In some embodiments, the notification module may display the notification center in the same manner regardless of the user's manner of invoking the notification center. In other embodiments, the notification module may respond differently depending on the gesture made by the user. For example, if the user performs a gross swipe gesture, the notification module may immediately pull down the notification center to the bottom of screen 500. Alternatively, if the user slowly drags one or more fingers downward, the notification module may pull down the notification center onto screen 500 in real time.

[0062] In some cases, a visual cue may be displayed at the top of display screen 500 to indicate the presence of a notification center. In other embodiments (and as shown in display screen 500), there may be no visual cue to indicate the presence of a notification center, which can help avoid distractions when a user is using an electronic device, as well as save valuable screen real estate.

[0063] Those skilled in the art will appreciate that instead of at the top of the display screen 500, the notification center can be accessed from any suitable portion of the display screen 500 (e.g., the right, left, or bottom of the display screen 500). Additionally, the notification module may allow the user to specify which portion of the display screen 500 is used to launch the notification center.

[0064] Those skilled in the art will also appreciate that although Figure 5 illustrates a home screen, the notification center may be launched at any suitable time, in particular, the notification center may be launched when the device is displaying a particular application.

[0065] 6A-6E show display screens of a notification center of an electronic device. A person skilled in the art will appreciate that although the notification center is shown in FIGURES 6A-6E when the electronic device is operating in portrait mode, the notification center can also be displayed when the electronic device is operating in landscape mode.

[0066] 6A , in response to a user dragging one or more fingers downward from the top of the display screen 600, a notification module may pull down a notification center 602 toward the bottom of the display screen 600. The notification center 602 may include tabs 604 at the bottom.

[0067] In some cases, a user may need to drag notification center 602 up and off the display screen to remove notification center 602 from display screen 600. Those skilled in the art will appreciate that any other suitable technique for removing notification center 602 from display screen 600 (e.g., pressing a home or on / off button) may also be used.

[0068] 6B, the notification center 602 is shown pulled all the way down to the bottom of the display screen 606. The notification center 602 can include one or more panes, each of which can include widgets that represent different applications of the electronic device. For example, the notification center 602 can include a weather pane 608, a stocks pane 610, a social network pane 612, and a mail main 614.

[0069] The notification center 602 may be scrollable such that a user can touch and drag the notification center 602 up or down to view fewer or more notifications. In some embodiments, only certain portions of the notification center 602 may be scrollable. As a result, one or more panes (e.g., the weather pane 608 and the stocks pane 612) may remain fixed while other panes are scrollable.

[0070] The weather pane 608 can display the weather for the current location of the electronic device. Alternatively, the weather pane 608 may display the weather for any default location specified by the user. The user may touch the weather pane 608 to open the weather application on the device. Additionally, the user may swipe left or right on the weather pane 608 to view the weather for another city.

[0071] The stocks pane 610 can include, for example, a scrollable stock ticker that scrolls from right to left independent of a user action. The user may be able to drag the stocks pane 610 left or right to view other hidden or partially displayed stocks. In some cases, the user may select any one of the stock tickers by touching the ticker (e.g., one of the stock tickers 617-619). In response to the user's selection, the notification module can open a stock widget. The stock widget can be based on the contextually selected stock ticker (e.g., the stock widget can display detailed stock information corresponding to the selected company).

[0072] A user may select (e.g., touch) any pane of the notification center 602 to access an application associated with that pane. For example, in response to a user selecting the social network pane 612, the notification module may provide a social network application to the user.

[0073] Each of the panes 608-614 may be associated with an option that allows the user to manually clear notifications from that pane. For example, button 616 may enable the user to clear notifications from the notification center 602 for pane 612. Specifically, in response to a user selecting button 616, the notification module may display a "Clear" button (e.g., button 616 may be flipped over to read "Clear," expanded to become a "Clear" button, and / or transition to a "Clear" button). When the user then selects the "Clear" button, the user may manually clear one or more notifications from the notification center 602.

[0074] In some cases, button 616 may allow a user to clear all notifications in a particular pane (or application), thereby removing the corresponding pane from notification center 602. However, if a new notification is received for that application, the pane corresponding to that application may reappear in notification center 602. Those skilled in the art will appreciate that notifications that have been removed from notification center 602 may still be accessible to the application that generated those notifications. Thus, if a user wishes to view notifications that have been removed from notification center 602, the user may view those notifications by accessing the corresponding application.

[0075] Some panes, such as panes 612 and 614, may have one or more lists of notifications associated with them. For example, social network pane 612 has list 613 that presents one notification, and email pane 614 has list 615 that presents two email notifications. Any suitable number of notifications may be listed as part of the associated list. Each displayed notification may be selectable, and when selected, the notification is opened in the application that corresponds to the associated pane. For example, if a user selects the first email notification in list 615, the email is opened for viewing in an email application.

[0076] Panes with associated lists may be vertically scrollable (e.g., a user can scroll from one pane to the next to view their associated lists). These panes are in contrast to horizontally scrollable panes 608 and 610. A user can scroll from pane with associated list to pane with associated list while panes such as panes 608 and 610 remain in place. Thus, at any time, a user can scroll panes 608 and 610 horizontally and scroll panes with associated lists vertically.

[0077] 6C, a display screen 620 is shown illustrating the notification center 602, which can include a calendar pane 622. The calendar pane 622 can display a list of notifications (e.g., upcoming events) for a predefined period of time (e.g., the next 24 hours) on the user's calendar. In some cases, the calendar pane 622 can organize the upcoming events chronologically. For example, the most imminent event can be displayed at the top of the notification list, followed by the next upcoming event, and so on. Alternatively, the most imminent event can be displayed at the bottom of the notification list.

[0078] The calendar pane 622 may be adjusted in real-time while an event is in progress. For example, as shown in FIGURE 6C, a notification 621 may include text 623 indicating that the event "Yoga" started 40 minutes ago (40m ago). The notification module may continually update the text 623 for the duration of the event.

[0079] In some embodiments, a user can set a predefined number of notifications to be displayed for each application, so that if the number of displayable notifications exceeds the predefined number, the notifications module can automatically remove notifications from the calendar pane 622. Notification settings for specifying the predefined number of notifications are described in more detail in conjunction with Figures 9E and 9F.

[0080] As shown in FIG. 6C, the predetermined number of notifications may be set to 5. Thus, when a new notification is received, the notification module may automatically remove notifications currently displayed in the calendar pane 622. For example, referring now to FIG. 6D, when a new notification 626 is received from a calendar application, the notification module may add the new notification 626 to the top of the calendar pane 622. However, the notification module may remove notification 628 from the calendar pane 622 because the number of notifications that can be displayed exceeds the predetermined number of notifications. In some cases, the notification 628 may be associated with an event that has the latest start time compared to other events displayed in the calendar pane 622. The notification 628 may then be moved back to the calendar pane 622 when another notification is removed from the calendar pane 622 (e.g., when the notification 626 is completed or canceled).

[0081] Once the time for a calendar event has elapsed, one or more notifications corresponding to the event may be automatically removed from the calendar pane 622. For example, if the event "Yoga" lasts for one hour, then the notification 621 (FIG. 6C) corresponding to "Yoga" may be removed from the calendar pane 622 once the event is completed. For example, as shown in FIG. 6E, once the time for the "Yoga" event has elapsed, the notification module may automatically remove the notification 621 from the notification center 602. In addition to removing the notification 621, the notification module may add a new notification 632 to the calendar pane 622.

[0082] Those skilled in the art will appreciate that the panes included in Figures 6A-6E are merely exemplary. Thus, notification center 602 may include any suitable panes associated with one or more applications on the device. In some cases, notification center 602 may include notifications that are displayed when the device is operating in a locked state. These types of notifications are described in more detail in conjunction with Figures 8A-8F.

[0083] 6F-6H, several exemplary display screens are shown illustrating the display of a notification center when a user is currently actively participating in a third party application, such as a game. In FIG. 6F, display screen 640 illustrates an actively running third party application, such as a game. While participating in an active third party application, a user may access a notification center in accordance with an embodiment of the present invention. A user first swipes a finger downward from the top of the screen such that tab 654 appears on screen 650 of FIG. 6G. Once tab 654 appears, the user places a finger on tab 654 and drags tab 654 downward to reveal notification center 662, as partially shown on screen 660 of FIG. 6H. When the user drags tab 654 to the bottom of screen 660, notification center 662 is displayed in its entirety.

[0084] In some embodiments, while the electronic device is operating in an unlocked state, the notification module can display one or more banners that can correspond to notifications received from various applications. For example, the notification module can display rotating banners on the display screen.

[0085] If the user does not select the banner within a predetermined time (e.g., 5 or 6 seconds), the notification module can remove the banner from the display screen, for example by rotating the banner off the display screen, or the user can dismiss the banner by swiping or pushing it away.

[0086] In some embodiments, when two or more banners are received by the notification module at approximately the same time, the banners may be rotated on the display screen at the same time, i.e., multiple banners may be rotated on the display screen at the same time, or, to minimize user distraction, the notification module may time the display of the banners so that only one banner is displayed at any one time.

[0087] Those skilled in the art will appreciate that any suitable visual method may be used to display the banner. For example, the banner may scroll across the display screen, bounce / fall, or tumble into the display screen. Additionally, the banner may be removed with a similar function. The notification module may allow the user to specify how the banner is allowed to be displayed and / or removed.

[0088] In some cases, if a user ignores or removes a banner without accessing it, the notification module may add a notification associated with the banner to a notification center (e.g., notification center 602 of FIGS. 6A-6E) so that when the user subsequently selects to view the notification center, the notification center can provide the user with all accumulated notifications that the user has not accessed.

[0089] 7A-7E, display screens illustrating various types of banners that may be displayed on an electronic device are shown. Those skilled in the art will appreciate that banners may be displayed at any suitable time while the device is operating in an unlocked state (e.g., while the device is displaying a home screen or while displaying a particular application). For example, banners may be displayed while the user is playing a video game, visiting a website, changing system settings, watching a video, etc. Those skilled in the art will appreciate that although FIGS. 7A-7E show banners displayed while the electronic device is operating in portrait mode, banners may also be displayed while the electronic device is operating in landscape mode. Those skilled in the art will appreciate that banners may be displayed in any suitable location on the display screen (e.g., right, left, top, or bottom). Additionally, the notification module may allow a user to specify which portion of the display screen the banner may be displayed on.

[0090] Referring first to Figure 7A, a display screen 700 is shown that may include a banner 702. The banner 702 may present recently received notifications (e.g., text messages received from a user's address book). As shown in Figure 7A, the banner 702 may be displayed while a user is playing a video game.

[0091] Banner 702 may include an icon 704, text 706, and media 708. Icon 704 may indicate the type of application that generated the notification. Text 706 may include address information and / or one or more portions of a received text message. In some cases, text 706 may be an abbreviated version of the full text of the notification (e.g., text 706 may include part of the text or body of an email). Media 708 may be embedded media associated with the text message (e.g., a photo from an address book or a media file attached to a text message).

[0092] In some embodiments, the notification module can detect when a user selects the banner 702 (e.g., by touching the banner 702). In response to the user's selection, the notification module can present an associated notification in the application that generated the notification. For example, in response to the user selecting the banner 702, the notification module can display a particular text message that corresponds to the banner 702 in a text messaging application.

[0093] In some embodiments, the user may drag the banner 702 down to view additional notifications associated with the application. Alternatively, in response to the user dragging the banner 702 down, the notification module may display a notification center. For example, the notification module may display a portion of the notification center that includes the application panel associated with the banner 702. As another example, the notification module may display a portion of the notification center that is centered around the text message.

[0094] 7B, a display screen 710 is shown that may include a banner 710. The banner 710 may include media 712, which may be video that has been attached to a notification. Those skilled in the art will appreciate that the media 712 may display any suitable media, such as, for example, a still image, a video, an audio file, a map, an electronic business card, etc.

[0095] Additionally, banner 710 may include text 713 indicating that the notification is associated with a number of still and video images and no text. Specifically, text 713 may indicate that there are two attachments in addition to media 712. Thus, text 713 may change depending on the number of attachments not displayed in banner 710.

[0096] 7C illustrates a display screen 716 that can include a banner 718. The banner 718 can include a map 720 that can be generated based on the notification associated with the map URL. For example, the map 720 can be a localized map of locations in the immediate vicinity of the location associated with the map URL. Additionally, the map 720 can include pins embedded at specific locations (e.g., restaurant or movie theater locations) associated with the map URL.

[0097] 7D, a display screen 722 is shown that can include a banner 724. The banner 724 can be a coalesced banner. That is, the banner 724 can be information about multiple notifications that are queued for a particular application. For example, as shown in FIG. 7D, the banner 724 indicates that there are seven new mail notifications for a mail application.

[0098] The notification module may generate the coalesced banner using any other technique. For example, the notification module may detect two or more notifications that are associated with at least one common parameter (e.g., a particular subject). Upon detecting that two or more notifications are associated with at least one common parameter, the notification module may add the two or more notifications into a single message in the coalesced banner. As another example, the notification module may shorten (e.g., summarize) the two or more notifications into a single message in the coalesced banner.

[0099] In some cases, the notification module can simultaneously display multiple coalesced banners (e.g., groups of banners), each of which may display a single message, indicating that new notifications are queued for multiple applications.

[0100] The notification module may also provide the banner based on the occurrence of one or more triggering events (e.g., one or more time- or location-based triggering events). For example, when the notification module receives a notification associated with a time-based triggering event (e.g., a reminder to perform a task at a particular time), the notification module may display a banner associated with the event at or a predetermined time before the start of the event.

[0101] As another example, in response to receiving a notification associated with a location-based trigger event (e.g., a reminder to buy milk at the grocery store), the notification module can display a banner associated with that event when the electronic device is detected at the grocery store location. In some embodiments, these alarm banners can include a "snooze" button that allows the user to stop the alarm for a predetermined time.

[0102] The banner displayed on the electronic device may be unobtrusive; that is, the banner may not obstruct user access to overlapping controls on the display screen. For example, referring to FIG. 7E, a display screen 726 is shown that may include a banner 728. The banner 728 may be overlaid on a "Notifications" button 730. Because the banner 728 is an unobtrusive banner, the user may still press the "Notifications" button 730 while the banner 728 is positioned on top of the "Notifications" button 730. In some embodiments, one or more visual cues may be further displayed that may indicate to the user that the "Notifications" button 730 is still selectable even when the banner 728 is overlaid.

[0103] In some embodiments, the notification module can control how notifications are displayed when the electronic device is in a locked state (e.g., when the electronic device is not in use). Specifically, when the device is operating in a locked state, one or more notifications can be received from various applications. Specifically, the electronic device can receive one or more push events (e.g., phone calls, voicemails, emails, or third-party push events) and device alerts (e.g., reminders or alarms).

[0104] In response to receiving the notification, the electronic device may wake up (e.g., the processor may wake up the graphics module) and the notification module may display the received notification on a display screen. In some cases, the notification may be displayed as a large format notification. With reference to Figures 8A-8F, display screens illustrating various types of notifications that may be displayed while the electronic device is operating in a locked state are shown.

[0105] 8A, a display screen 800 is shown that may include a notification 802. The notification 802 may be displayed after being received from a third-party application while the electronic device is operating in a locked state. Specifically, the notification 802 may include an icon 804 that indicates the application that generated the notification 802. Additionally, the notification 802 may include text 806, which may provide associated text or a portion of the text received from the application.

[0106] Upon viewing the notification 802, the user may choose to jump directly to the message associated with the notification 802. For example, the user may access the notification 802 by tapping and holding the notification. In response to a user interaction, the notification module may display a slider on the display screen (e.g., by animating the notification 802) or by flipping the notification over. For example, referring to FIG. 8B , a display screen 808 is shown that may include a slider 810 that may be embedded as a component behind the notification 802. The user may manipulate the slider 810 by dragging a slider button 812 in a particular direction (e.g., to the right).

[0107] Upon detecting manipulation of the slider 810, the notification module can directly unlock the electronic device. After unlocking the device, the notification module can present the notification in the application that generated the notification. In some cases, even if the electronic device receives multiple notifications from a particular application, the notification module can ignore the other notifications and present the particular notification that the user explicitly requested.

[0108] 8C, a display screen 814 is shown that may include a notification 816. The notification 816 may be displayed in response to an image text message received by the electronic device. In particular, the notification 816 may include an embedded image 818. Additionally, the notification 816 may include text 819 that provides an identity of the sender of the text message. Additionally, the notification 816 may include text 820, which may be text that accompanies the image. As shown in FIG. 8C, the image 818 may be prominently displayed within the notification 816 (e.g., the image 818 may be enlarged relative to the text 819 and 820).

[0109] 8A and 8B, when the user makes a selection to access the notification 816 (e.g., by tapping and holding the notification 816), the notification module can display a slider, and when the user manipulates the slider by dragging it, the notification module can unlock the device and provide the image 818 directly to the user (e.g., by displaying the image 818 in an image view of a chat application).

[0110] Those skilled in the art will appreciate that the notification module may display any suitable type of media within a notification. For example, a notification may include one or more of audio, one or more electronic business cards, one or more videos, and one or more map URLs (e.g., the notification module may display a map of the URL's location). Additionally, similar to coalescing banners, the notification module may display in a single notification the content associated with multiple queued notifications for a particular application.

[0111] Additionally, notifications may be displayed in response to one or more triggering events (e.g., time-based or location-based triggering events). For example, in response to receiving a notification associated with a location-based triggering event, the notification module may display a notification associated with that event when the electronic device is detected in the location of the triggering event.

[0112] As another example, when the notification module receives a notification associated with a time-based triggering event, the notification module can display the notification associated with the event at or a predetermined time prior to the start of the event. For example, with reference to FIGURE 8D, a display screen 822 is shown with a notification 824. The notification 824 can include text 826, which may indicate that the notification 824 was displayed in response to a time-based triggering event (e.g., an alarm). Additionally, the text 826 can provide a description of the alarm.

[0113] The notification 824 may further include a "Snooze" button 828. In response to a user selecting the "Snooze" button 828, the notification module may silence the alarm for a predetermined period of time. This feature allows a user to control the alarm without unlocking the electronic device.

[0114] Display screens 800 (FIG. 8A), 808 (FIG. 8B), 814 (FIG. 8C), and 822 (FIG. 8D) may include pull-down options 830 located above the displayed notifications. Those skilled in the art will appreciate that although pull-down options 830 are shown above the notifications in FIGS. 8A-8D, pull-down options 830 may be located in any suitable location on the display screen (e.g., the left, right, or bottom of the display screen). Additionally, pull-down options 830 may be made visible to a user by pressing a button on the electronic device (e.g., an on / off button and / or a home button) when the electronic device is in a sleep mode.

[0115] Pull-down option 830 allows a user to view previously received notifications (e.g., all notifications received while the electronic device was operating in a locked state) A user can select pull-down option 830 by dragging option 830 downward on the display screen.

[0116] 8E, a display screen 832 is shown showing a notification list 834, which may be a list of previously received notifications. Specifically, when each notification in the notification list 834 was initially received, the notification may be displayed as a large format notification (e.g., as shown in FIGS. 8A-8D). However, because the notification was not responded to by the user, the notification was added to the notification list 834 as a separate element. In some embodiments, the initial display of the notification in the locked mode may be larger than the same notification displayed in the notification list 834. For example, notifications 802 (FIG. 8B), 816 (FIG. 8C), and 824 (FIG. 8D) may be larger than elements 835, 837, and 838, respectively. That is, elements 835, 837, and 838 may be displayed in a smaller format.

[0117] The elements of the notification list 834 may be stacked on top of each other. For example, the notification module may display multiple text messages received by the electronic device as individual elements of the notification list 834.

[0118] In some embodiments, notification list 834 may be ordered based on the time each notification was received (e.g., chronologically). That is, the most recently received notification may be added to the top of notification list 834. Alternatively, the most recently received notification may be added to the bottom of notification list 834. For example, as shown in FIG. 8E, notification list 834 may be ordered chronologically with the most recent notification at the top of list 834.

[0119] In another embodiment, the notification list 834 may be arranged based on user-selected parameters. For example, the user may specify which application's notifications should be displayed first, second, third, etc. Based on the user-selected parameters, the notification module may sort the received notifications. For example, notifications corresponding to each application may be grouped first, and then the applications may be arranged in a predefined order. For example, notifications corresponding to voicemails may be listed first, notifications corresponding to emails may be listed second, notifications corresponding to text messages may be listed third, etc. User selection of how to arrange the notification list 834 is described in more detail in conjunction with FIG. 9B.

[0120] The notification list 834 may be scrollable. Specifically, the area 836 of the display screen 832 may be configured to be scrollable such that the notification list 834 can move up or down when the user swipes or drags a portion of the area 830. As a result, the notification list 834 has the capability to display a large number of notifications (e.g., all notifications received while the device is operating in a locked state). In some embodiments, the notification list may be displayed automatically, regardless of whether the pull-down option 830 is displayed and acted upon by the user.

[0121] Additionally, each notification in the notification list 834 may be individually accessible. For example, each notification may be associated with an individual slider. As described above, a user may select to access a notification in the notification list 834 by tapping and holding the notification. For example, a user may tap and hold notification 838, and in response to this user action, the notification may display a slider in the notification list 834 (e.g., by flipping notification 838 over).

[0122] 8F, display screen 840 shows notification list 834 along with the backside of notification 838. In particular, notification 838 may include a slider 842. Similar to slider 810 (FIG. 8B), slider 842 may be configured to be embedded within notification 838. A user may manipulate slider 842 by dragging slider button 844 in one direction (e.g., to the right of display screen 840).

[0123] When slider 842 is manipulated, the notification module can detect that slider 844 has been manipulated, and the notification module can unlock the electronic device. After unlocking the device, the notification module can present the notification in the application that generated the notification.

[0124] In some embodiments, a user may make a selection to unlock the device. For example, a user may make a selection to unlock the device by pressing a button (e.g., an on / off button or a home button) or sliding an "unlock" slider 846. In response to a user action, a notification module may display a notification center (e.g., similar to notification center 602 of FIGS. 6A-6E) on the display screen. In another embodiment, in response to a user unlocking the device, the notification module may not display the notification center until the user explicitly launches the notification center. In some embodiments, the "unlock" slider 846 (or other user input unlock area) may include context-sensitive text that changes based on when a notification is received. For example, when an email is received and displayed in the notification list 834, the text is "slide to read." As another example, when a reminder notification is received, the text may be "slide to view."

[0125] In some cases, the notification module may allow a user to specify a privacy setting such that if a user turns on a privacy setting, one or more notifications or types of notifications (e.g., notifications associated with text messages) received while the electronic device is in a locked state are not displayed as long as the device remains locked. Then, if the user chooses to unlock the device, the notification module may display the received notifications in one or more banners (e.g., similar to the banners in FIGS. 7A-7E).

[0126] As described above, because users may have different preferences for how they want notifications to be displayed, the electronic device may allow users to customize notification settings. Specifically, the user may be able to customize notification settings for a locked state (e.g., notifications) and an unlocked state (e.g., notification center and banners).

[0127] Returning to FIG. 5, display screen 500 may include a "Settings" option 504. Specifically, a user may select "Settings" option 504 to change one or more settings of the electronic device. Thus, in response to a user selecting "Settings" option 504, the electronic device may provide display screens that enable the user to change system settings. For example, with reference to FIGS. 9A-9F, display screens relating to customizing notification settings are shown.

[0128] 9A, a display screen 900 is shown that includes a settings list 902 that may be displayed after a user selects "Settings" option 504 (FIG. 5). Settings list 902 may include a "Notifications" option 904. A user may select "Notifications" option 904 (e.g., by tapping "Notifications" option 904) to access and modify one or more notification settings.

[0129] In response to detecting that the user has selected the "Notifications" option 904, the electronic device can provide one or more notification settings on the display screen. These notification settings can allow the user to change one or more banner options or notification center options (e.g., when the electronic device is in an unlocked state) and one or more notification options (e.g., when the electronic device is in a locked state). For example, referring to FIG. 9B, a display screen 906 is shown that can include multiple notification settings.

[0130] For example, display screen 906 can include manual sorting option 908 and automatic sorting option 910. Sorting options 908 and 910 are user-selected parameters that can specify in what order notifications are displayed in one or more contexts, such as, for example, a notification list (e.g., notification list 834 of FIGS. 8E and 8F).

[0131] When a user selects sort option 908, a notification module (e.g., notification module 238 of FIG. 2) may allow the user (e.g., provide the user with an option) to manually specify the order in which notifications appear in the notification list. That is, the user may specify which application's notifications should appear first, second, and so on. Based on the user's selection of sort option 908, the notification module may sort received notifications into the order specified by the user.

[0132] In some embodiments, the order in which the applications are sorted may correspond to the order in which the applications are listed in the "In Notification Center" group 911. In other embodiments, the electronic device may display another display screen (not shown) that may allow the user to specify the order of the applications.

[0133] Once the notification module has classified the notifications into groups based on the corresponding application, the notifications can be assigned a predefined order to each group. For example, for each group, the notification module can arrange the associated notifications based on the time each notification was received (e.g., chronologically). Those skilled in the art will appreciate that other predefined orders can be used instead.

[0134] In contrast, if the user selects sort option 910, the notification module may assign a predefined order for displaying the notifications in the notification list. Specifically, the notification module may order the received notifications based on the time each notification was received (e.g., chronologically). That is, the most recently received notification may be added to the top (or bottom) of the notification list. As newer notifications are received, the top notification may be pushed down in the notification list.

[0135] Display screen 906 may further include options 912 that may enable a user to specify which applications to display in a notification center (e.g., notification center 602 of FIGS. 6A-6E). As shown in display screen 906, options 912 may include multiple interactive lists (e.g., an "Include in Notification Center" group 911 and a "Do Not Include in Notification Center" group 913). Notifications for applications included in "Include in Notification Center" group 911 are displayed in the notification center, while notifications for applications included in "Do Not Include in Notification Center" group 913 are excluded from the notification center.

[0136] The user may specify which applications to include in the notification center using any suitable technique. For example, the user may select “Edit” option 914 to manually adjust options 912. When the user selects “Edit” option 914, the electronic device may provide a display screen that allows the user to manually move applications to / from groups 911 and 913.

[0137] 9C, there is shown a display screen 920 that may be displayed in response to a user selecting "Edit" option 914 (FIG. 9B). As shown in display screen 920, a user may move each of options 912 to / from "In Notification Center" group 911 and "Not In Notification Center" group 913. For example, a user may tap and drag option 922 from "Not In Notification Center" group 913 to "In Notification Center" group 911.

[0138] 9D illustrates a display screen 924 that may be displayed when a user moves option 922 to the bottom of "Include in Notification Center" group 911. In some cases, the order in which applications are arranged in "Include in Notification Center" group 911 may dictate the order in which application panes are displayed in the notification center. For example, based on "Include in Notification Center" group 911 of FIG. 9D, the notification center may include a weather panel at the top, then a mail panel, .... Thus, a user may adjust the order in which application panes are displayed in the notification center by moving each option 922, 926, 928, or 930 up or down (e.g., by tapping and dragging each option).

[0139] When the user is finished editing the applications to be displayed in the notification center, the user may select a "Done" option 932. After the user's selection, the electronic device may return the display screen to a display screen similar to display screen 906 of FIG.

[0140] As another example, a user may specify an application to be displayed in the notification center by tapping an option in options 912. For example, referring to FIGURE 9B, a user may select "Mail" option 916. In response to the user's selection, the electronic device may provide a details screen of display options for the "Mail" application.

[0141] 9E, a display screen 940 that can provide a detailed view of display options for the "Mail" application is shown. Display screen 940 can include a switch 941 that can enable a user to specify whether notifications received from the "Mail" application are included in the notification center. Specifically, when a user sets switch 941 to "ON," notifications received from the "Mail" application will be displayed in the notification center. On the other hand, when a user sets switch 941 to "OFF," notifications received from the "Mail" application will not be displayed in the notification center.

[0142] If notifications from an application are selected to be included in the notification center, the user may specify a predetermined number of notifications to be displayed for that application by selecting “Show” option 942.

[0143] 9F, the electronic device may provide a display screen 950 that may be displayed in response to a user selecting “display” option 942. Display screen 950 may include an option list 952. Each option included in option list 952 may allow a user to specify a different number (e.g., 1, 5, 10) of notifications to be displayed for an application in the notification center. For example, when a user selects option 954, an application pane corresponding to a mail application (e.g., application pane 614 of FIG. 6B) may display up to 10 notifications. In some cases, a higher number may be set for some applications (e.g., email and social network applications) and a lower number may be set for other applications (e.g., a weather application) based on the frequency of updates.

[0144] Those skilled in the art will appreciate that the options provided in option list 952 are merely exemplary, and in particular, the electronic device may instead provide one or more options that allow the user to specify any predefined number of notifications (e.g., 1, 5, 10, 20 or more).

[0145] Based on the predetermined number of notifications, if the number of displayable notifications exceeds the predetermined number, the notification module can automatically remove the notifications from the application pane (e.g., as shown in FIG. 6C and FIG. 6D). Because the notification module can automatically remove one or more notifications that exceed the predetermined number of notifications, the notification module can provide a concise presentation of notifications in the notification center. Furthermore, this approach is convenient for the user because the user does not need to clear notifications from the notification center (e.g., by selecting button 616 in FIG. 6B).

[0146] Returning to FIG. 9E, display screen 940 may further include option 943 (View in Lock Screen) that may allow a user to select whether or not to display notifications associated with the application when the electronic device is operating in a locked state (e.g., on the display screens of FIGS. 8A-8F). In some embodiments, a user may select option 943. That is, option 943 may have a default state of "OFF" such that notifications received when the electronic device is in a locked state are not displayed until the locked state is released.

[0147] This setting may be advantageous because it allows the user to customize the display of notifications from a privacy perspective. For example, a user may not want new email messages to appear on the display screen while the electronic device is operating in a locked state. However, when the user unlocks the electronic device, the user may want to be able to launch a notification center or view received email messages through one or more banners. However, if the user chooses to set option 943 to "ON," the notification module may immediately display new notifications received, even while the electronic device is in a locked state.

[0148] Options 944 may allow a user to specify how notifications should be displayed when the electronic device is operating in an unlocked state. For example, options 944 may include a “None” option 945, a “Banners” option 946, and an “Alerts” option 947.

[0149] If the user selects "None" option 945, the notification module may not provide visual notifications for the particular application; however, notifications may still be displayed in the notification center. Alternatively, if the user selects "Banner" option 946, the notification module may display received notifications as one or more banners on the display screen (e.g., the banners shown in Figures 7A-7E). A user may select "Banner" option 946, for example, if a particular application sends important, but frequently generated, notifications.

[0150] When the user selects the "Warn" option 947, the notification module may display the received notification as a message requiring a user response (e.g., the user may be prompted to select a "Dismiss" option or a "View" option depending on the type of application).

[0151] Display screen 940 may further include a "Show Application Icon Badge" option 948 that may indicate whether or not to display an image of the application in the banner corresponding to the received notification. For example, if the "Show Application Icon Badge" option 948 is set to "ON," the notification module may display an icon representing the application that generated the notification (e.g., icon 704 of FIG. 7A). If the "Show Application Icon Badge" option 948 is set to "OFF," the notification module will not display an icon in the banner corresponding to the application. Those skilled in the art will appreciate that the "Show Application Icon Badge" option may enable the notification module to add any other visual embellishment to the banner in addition to or instead of the image of the application.

[0152] The "Sounds" option 949 may indicate whether or not sounds are allowed when notifications for the application are received. If the "Sounds" option 949 is set to "OFF", no sound will be played when a notification is received for the application. On the other hand, if the "Sounds" option 949 is set to "ON", the notification may play an audio alert when a new notification is received for the application. As a result, even if the "None" option 945 is selected for a particular application (e.g., even if there is no visual notification), the user may still hear an audio alert when a new notification is received for the application. As a result of hearing the audio alert, the user may later choose to launch the notification center to access the notification. Those skilled in the art will appreciate that the notification settings discussed in Figures 9A-9F are merely exemplary and that any other suitable notification settings may be customizable.

[0153] As discussed above, the notification module may be implemented in any suitable electronic device. For example, the notification module may be implemented in an electronic device with a large display and / or touch screen (e.g., touch I / O device 212 of FIG. 2). In such an embodiment, the notification center may not fill the entire screen, as in embodiments in smaller devices.

[0154] 10A-10C, for example, a display screen for an electronic device with a large display is shown. Referring first to FIG. 10A, display screen 1000 shows that notification center 1002 does not fill the entire display screen 1000.

[0155] Additionally, for devices with larger displays, the notification module may display a visual indication when the notification center does not contain new notifications. For example, as shown in display screen 1004 of FIG. 10B, the notification module may indicate that the notification center 1002 currently does not store any new notifications. Those skilled in the art will appreciate that such indications may also be provided in electronic devices with smaller displays.

[0156] Referring to FIG. 10C, display screen 1006 illustrates the types of notifications that may be displayed when an electronic device having a large screen is locked and in landscape mode. Thus, in contrast to FIGS. 8A-8F, new notifications received are not first displayed on the display screen as separate notifications in a large format. Rather, new notifications are displayed in a scrollable notification list 1008. As a result, the notification module would not need to display a pull-down option such as pull-down option 830 in FIGS. 8A-8D. Those skilled in the art will appreciate that notification list 1008 may be displayed similarly when the electronic device is in portrait mode.

[0157] Those skilled in the art will appreciate that each of the notifications in notification list 1008 may exhibit similar characteristics as the notifications in notification list 834 (FIGS. 8E and 8F). Additionally, those skilled in the art will appreciate that the display screens shown in FIGS. 10A-10C are merely one embodiment of a notification center. Thus, a notification module implemented in an electronic device with a large display may display notifications in any suitable manner (e.g., similar to the notification presentation manners shown in FIGS. 6A-6E, 7A-7E, 8A-8F, and 9A-9F).

[0158] 11-14 illustrate flow charts of example processes according to some embodiments of the present invention. These processes may be performed by one or more components of an electronic device (e.g., device 100 of FIG. 1 or system 200 of FIG. 2). For example, at least some of the steps in the processes of FIGS. 11-14 may be performed by a notification module (e.g., notification module 238 of FIG. 2). Furthermore, those skilled in the art will understand that some of the steps may be performed in conjunction with a touch processing module (e.g., touch processing module 226 of FIG. 2) and / or a graphics module (e.g., graphics module 228 of FIG. 2).

[0159] 11, a process 1100 for displaying pull-down options in response to receiving multiple notifications is shown. The process 1100 may begin at step 1102, where at step 1104, a notification module may receive multiple notifications from at least one application.

[0160] Then, in step 1106, the notification module can detect that the electronic device is operating in a locked state. In a next step 1108, the notification module can provide a pull-down option (e.g., pull-down option 830 of FIGS. 8A-8D) associated with the plurality of notifications. Furthermore, the notification module can provide an additional notification (e.g., notification 802 of FIGS. 8A and 8B, notification 816 of FIG. 8C, notification 824 of FIG. 8D) on the display screen. This notification can be the most recently received notification.

[0161] After providing the pull-down option, process 1100 may proceed to step 1110. In step 1110, the notification module may determine that the user selected the pull-down option. Then, in step 1112, the notification module may provide a list of notifications (e.g., notification list 834 of FIGS. 8E and 8F). Then, process 1110 may end in step 1114.

[0162] 12 illustrates a process 1200 for displaying a notification center. The process 1200 may begin at step 1202, and at step 1204, a notification module may receive a number of notifications including at least one of push-based notifications (e.g., notifications from a non-third party or third party application) and trigger-based notifications (e.g., alarms or reminders).

[0163] The notification module may then detect that the electronic device is in an unlocked state at step 1206. After detecting that the electronic device is in an unlocked state, process 1200 may proceed to step 1208.

[0164] In step 1208, the notification module may detect that the user has selected to access the notification center. For example, the notification module may detect that the user has performed a gloss swipe gesture (e.g., by quickly flicking one or more fingers downward from the top of the display screen). As another example, the notification module may detect that the user has slowly dragged one or more fingers downward from the top of the display screen.

[0165] Continuing at step 1210, the notification module may display a notification center. The notification center may include multiple panes (e.g., panes 608-614 of FIG. 6B) associated with multiple notifications. Process 1200 may then end at step 1212.

[0166] 13 illustrates a flow chart of an example process 1300 for providing a banner. The process 1300 may begin at step 1302, where a notification module may receive a notification from at least one application at step 1304. At step 1306, the notification module may detect that the electronic device is in an unlocked state.

[0167] Continuing at step 1308, the notification module may provide a banner associated with the notification. The banner may allow the user to access at least one control that overlays the banner. For example, as shown in FIG. 7E, the notification module may provide a banner 728 that overlays a "Notifications" button 730. However, the notification module may still allow the user to access the "Notifications" button 730. After providing the banner, method 1300 may end at step 1310.

[0168] 14 shows a flow chart of an example process 1400 for providing notification settings. Process 1400 may begin at step 1402, where a notification module may provide an option to change device notification settings (e.g., "Notifications" option 904 of FIG. 9A) at step 1404, and the notification module may detect that a user has selected the option at step 1406.

[0169] Continuing at step 1408, the notification module may provide a plurality of notification settings, which may include options associated with one or more of a notification order option (e.g., option 912 of FIG. 9B), a notification number option (e.g., option list 952 of FIG. 9F), and an alert style option (e.g., alert style option 944 of FIG. 9E). Process 1400 may then end at step 1410.

[0170] It should be understood that the processes 1100, 1200, 1300, and 1400 of Figures 11-14 are merely exemplary, and any of these steps may be removed, modified, or combined, and any additional steps may be added, without departing from the scope of the present invention.

[0171] The described embodiments of the present invention are presented for purposes of illustration and not limitation.

Claims

1. 1. A data processing system comprising: a processor for executing instructions; a touch processing module; a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to interact with a notification module and an application programming interface (API) calling component of the data processing system, and cause the processor to: receiving a plurality of notifications from at least one application; Detects that the electronic device is operating in a locked state, providing pull-down options associated with the plurality of notifications; Detecting whether a user has selected the pull-down option using the touch processing module; in response to detecting that the user has selected the pull-down option, providing the list of the plurality of notifications to the user.

2. 2. The data processing system of claim 1, wherein said list of said plurality of notifications comprises all notifications received while said electronic device was operating in said locked state.

3. 2. The data processing system of claim 1, wherein said list of said plurality of notifications is ordered based on the time each of said plurality of notifications was received.

4. 2. The data processing system of claim 1, wherein said processor is further operative to sort said list of said plurality of notifications based on user selected parameters.

5. 2. The data processing system of claim 1, wherein the list of the plurality of notifications is scrollable.

6. The processor further comprises: Detecting whether a notification is selected to be accessed from the list of the plurality of notifications using the touch processing module; in response to detecting that the user has selected to access the notification, displaying a slider associated with the application that generated the notification.

2. The data processing system according to claim 1, further comprising:

7. The processor further comprises: Detecting that a user has operated the slider; unlocking the electronic device; presenting the notification to the user in an application that generated the notification; 7. The data processing system according to claim 6, further comprising:

8. 1. A method for displaying a notification when an electronic device is in a locked state, comprising: receiving a plurality of notifications from at least one application; detecting that the electronic device is operating in a locked state; displaying a list of the plurality of notifications; allowing a user to view the displayed list while the electronic device is operating in the locked state; The method according to claim 1, further comprising:

9. 10. The method of claim 8, wherein the step of allowing the user to view the displayed list includes receiving user input to move the displayed list up or down so that additional receipt notifications are displayed.

10. 9. The method of claim 8, wherein each of the displayed notifications has a representative graphic and text.

11. 9. The method of claim 8, wherein the list of the plurality of notifications is ordered based on the time each of the plurality of notifications was received.

12. moreover, receiving a user command to unlock the electronic device; unlocking the electronic device; after the electronic device re-enters the locked state, ceasing to display a list of notifications that was displayed before the electronic device was unlocked; 9. The method of claim 8, further comprising:

13. 10. The method of claim 8, further comprising displaying a user input unlocked field containing text.

14. 14. The method of claim 13, wherein the text in the user input unlock area changes depending on the content of a received notification.

15. 10. The method of claim 8, wherein the locked state is a state in which user interaction with the electronic device is restricted.

16. 1. A machine-readable storage medium providing instructions that, when executed by a processor, cause the processor to generate an application programming interface (API) that enables an API execution component to perform operations, the operations comprising: receiving a plurality of notifications, the notifications comprising at least one of a push-based notification and a trigger-based notification; Detecting that the electronic device is unlocked; Detecting that the user has chosen to access the Notification Center; displaying a notification center having a plurality of panes associated with the plurality of notifications.

17. 20. The machine-readable storage medium of claim 16, wherein the actions further include pulling down the notification center to the bottom of a display.

18. 17. The machine-readable storage medium of claim 16, wherein the act of detecting that the user has accessed the notification center further comprises detecting that the user has flicked or dragged at least one finger off of a top of the display.

19. 17. The machine-readable storage medium of claim 16, wherein the actions further include providing an option for each of the plurality of panes, the option allowing the user to manually remove at least one notification from the pane.

20. The operation further comprises: providing options for changing settings for the notification center; Detecting that the user has selected said option; Offer multiple notification settings, 20. The machine-readable storage medium of claim 16, further comprising:

21. 20. The machine-readable storage medium of claim 16, wherein the operations further include providing functionality for automatically removing at least one notification from the notification center after a time of a calendar event corresponding to the at least one notification has elapsed.

22. The operation further comprises: Detecting a user selection of one of a plurality of panes that are displayed; opening an application associated with the user selected pane; 20. The machine-readable storage medium of claim 16, comprising:

23. 1. A method for displaying a notification center on an unlocked electronic device, comprising: receiving a plurality of notifications; Detecting that a user has selected to access a notification center; displaying a notification center comprising at least one horizontally scrollable pane and at least one vertically scrollable pane; The method, wherein the at least one vertically scrollable pane includes a list of at least one associated notification.

24. 24. The method of claim 23, wherein at least one of the horizontally scrollable panes has auto-scrolling items.

25. receiving a user input on the at least one horizontally scrollable pane; 24. The method of claim 23, wherein the received user input controls horizontal scrolling of displayed content of the at least one horizontally scrollable pane.

26. 24. The method of claim 23, wherein each pane is associated with a particular application.

27. 24. The method of claim 23, wherein each vertically scrollable pane contains a contiguous list of the associated at least one notification.

28. 24. The method of claim 23, wherein each of the notifications within a particular vertically scrollable pane is ordered based on when it was received.

29. 24. The method of claim 23, wherein an order for each of the at least one vertically scrollable pane is based on a user preference.

30. 1. A data processing system comprising: a processor for executing instructions; a touch processing module; a memory coupled to the processor for storing instructions that, when executed by the processor, cause the processor to interact with a notification module and an application programming interface (API) calling component of the data processing system, and cause the processor to: Receive multiple notifications, Detecting that the user has chosen to access the Notification Center; at least one horizontally scrollable pane and at least one vertically scrollable pane, the at least one vertically scrollable pane displaying a notification center including a list of at least one associated notification; The data processing system according to claim 1,

31. 31. The method of claim 30, wherein at least one of the horizontally scrollable panes has auto-scrolling items.

32. receiving a user input on the at least one horizontally scrollable pane; 31. The method of claim 30, wherein the received user input controls horizontal scrolling of displayed content of the at least one horizontally scrollable pane.

33. 31. The method of claim 30, wherein each pane is associated with a particular application.

34. 31. The method of claim 30, wherein each vertically scrollable pane contains a contiguous list of the associated at least one notification.

35. 31. The method of claim 30, wherein each of the notifications within a particular vertically scrollable pane is ordered based on when it was received.

36. 31. The method of claim 30, wherein an order for each of the at least one vertically scrollable pane is based on a user preference.

37. 1. An apparatus comprising: A machine-readable storage medium providing instructions that, when executed by a machine, cause the machine to cause an application programming interface (API) calling component to perform operations, the operations including: Receive notifications from at least one application; Detecting that the electronic device is in an unlocked state; providing a banner associated with the notification, the banner enabling a user to access at least one overlapping control area; An apparatus comprising:

38. 40. The apparatus of claim 37, wherein the banner is provided based on at least one of a time- and location-based trigger event.

39. 40. The apparatus of claim 37, wherein the banner further comprises at least one associated media file.

40. 40. The apparatus of claim 37, wherein the notification includes at least one map URL, the processor further operative to provide a map in the banner proximate to the location.

41. 38. The apparatus of claim 37, wherein the banner is graphically displayed on top of a display of the electronic device.

42. The operation further comprises: Detecting after a predetermined period of time that the banner has not been selected by a user; removing the banner and adding the notification to a notification center; 40. The apparatus of claim 37, further comprising:

43. The operation further comprises: Detecting that the banner has been selected by a user; presenting said notification to a user in the application that generated said notification; 40. The apparatus of claim 37, further comprising:

44. 1. A method for displaying a notification, comprising: detecting that the electronic device is in a locked state; receiving a first notification from an application of the electronic device; Selectably displaying the first notification on a display of the electronic device first in a large format; redisplaying the first notification in a smaller format on the display; The method according to claim 1, further comprising:

45. 45. The method of claim 44, wherein the application is a third party application.

46. 45. The method of claim 44, wherein the first notification of the large format has at least one embedded image.

47. 45. The method of claim 44, wherein the first notification in the large format is displayed in response to a time-based trigger event.

48. 48. The method of claim 47, wherein the first notification in the large format has a snooze button.

49. moreover, detecting a user selection of the large format first notification; animating the first notification in the large format to display a slider; detecting a user operation of the slider; presenting the first notification in the application; 45. The method of claim 44, comprising:

50. moreover, displaying a notification list; 45. The method of claim 44, wherein the notification list comprises a list of received notifications, the list of received notifications being stacked.

51. 51. The method of claim 50, wherein the first notification is at the top of the notification list.

52. moreover, receiving a second notification; displaying the second notification in a large format; detecting a failure of a user to respond to the large format second notification; adding the second notification to the notification list; 51. The method of claim 50, wherein the second notification is stacked on top of the first notification.

53. An electronic device having a display and a processor, The processor, providing an option on the display for changing notification settings on the electronic device; Detecting that the user has selected said option; Offering multiple notification settings, including options for sequencing notifications manually or by time; An electronic device characterized by operating as follows.

54. 54. The electronic device of claim 53, wherein at least one of the plurality of notification settings changes at least one of a banner option, a notification center option, and a notification option.

55. The processor further comprises: receiving a user selection of an automatic mode for specifying an order in which notifications are displayed; assigning a predefined order for displaying notifications in the notification list; 54. The electronic device of claim 53, further comprising:

56. 56. An electronic device as recited in claim 55, wherein said predetermined order is based on the time of receipt of said notifications.

57. The processor further comprises: receiving a manual mode user selection for specifying an order in which notifications are displayed; Provide options for users to specify the order in which notifications appear in the notification list, Sorting the received notifications based on the order; 54. The electronic device of claim 53, further comprising:

58. the plurality of notification options includes an order of notification; The processor further comprises: receiving a user selection to manually edit applications included in the notification center; displaying options that allow the user to adjust the order in which the plurality of panes are displayed in the notification center; 54. The electronic device of claim 53, further comprising:

59. The processor further comprises: receiving a user selection of one of a plurality of notification options; in response to receiving the user selection, providing a detailed display of display options for the application corresponding to the option.

54. The electronic device of claim 53, further comprising:

60. 60. The electronic device of claim 59, wherein the detailed display of the display options comprises at least one option for specifying whether notifications received from the application are to be included in a notification center.

61. 60. The electronic device of claim 59, wherein the detailed display of the display options comprises at least one option for specifying a predetermined number of notifications to display for the application.

62. 60. The electronic device of claim 59, wherein the detailed display of the display options includes at least an option for selecting whether or not to display notifications associated with the application when the electronic device is operating in a locked state.

63. 60. The electronic device of claim 59, wherein the detailed display of the display options includes at least an option for specifying how notifications are displayed when the electronic device is operating in an unlocked state.

64. 60. The electronic device of claim 59, wherein the detailed display of the display options includes at least one option for specifying whether to display an image of the application in a banner corresponding to a notification received for the application.

65. 60. The electronic device of claim 59, wherein the detailed display of the display options includes at least one option for specifying whether to enable sound generation upon receipt of a notification for the application.

66. 1. A method for organizing a notification center, comprising: displaying options for changing notification settings on the electronic device; detecting when the option is selected by a user; displaying a number of notification settings, including options for sequencing notifications manually or by time; The method according to claim 1, further comprising:

67. 67. The method of claim 66, wherein at least one of the plurality of notification settings changes at least one of a banner option, a notification center option, and a notification option.

68. moreover, receiving a user selection of an automatic mode for specifying an order in which notifications are displayed; 67. The method of claim 66, further comprising the step of: assigning a predetermined order for displaying notifications in the notification list.

69. 67. The method of claim 66, wherein the predetermined order is based on the time of receipt of the notification.

70. moreover, receiving a user selection of a manual mode for specifying an order in which notifications are displayed; providing options for a user to specify an order for displaying notifications in the notification list; sorting the received notifications based on the order; 67. The method of claim 66, comprising:

71. the plurality of notification options includes an order of notification; The method further comprises: receiving a user selection to manually edit applications included in the notification center; displaying options that allow the user to adjust the order in which multiple panes are displayed in the notification center; 67. The method of claim 66, comprising:

72. moreover, receiving a user selection of one of a plurality of notification options; in response to receiving the user selection, providing a detailed display of display options for an application corresponding to the option; 67. The method of claim 66, comprising:

73. 73. A method as recited in claim 72, wherein the detailed display of the display options comprises at least one option for specifying whether notifications received from the application should be included in a notification center.

74. 73. A method as recited in claim 72, wherein the detailed display of the display options comprises at least one option for specifying a predetermined number of notifications to display for the application.

75. 73. The method of claim 72, wherein the detailed display of the display options includes at least an option for selecting whether or not to display notifications associated with the application when the electronic device is operating in a locked state.

76. 73. The method of claim 72, wherein the detailed display of the display options includes at least an option for specifying how notifications are displayed when the electronic device is operating in an unlocked state.

77. 73. The method of claim 72, wherein the detailed display of the display options includes at least one option for specifying whether to display an image of the application in a banner corresponding to a notification received for the application.

78. 73. The method of claim 72, wherein the detailed display of the display options comprises at least one option for specifying whether to enable sound generation upon receipt of a notification for the application.

79. 1. A system comprising: A display and A notification module, Receive notifications from your calendar application, a notification module for displaying a list of notifications having upcoming events during a predetermined period in a calendar pane of a notification center on the display; A system comprising:

80. 80. The system of claim 79, wherein the incoming events are organized in chronological order.

81. 80. The system of claim 79, wherein the calendar pane adjusts in real-time as the upcoming event progresses.

82. The notification module: Detecting a predetermined number of notifications to display for the calendar application; Detecting whether a number of notifications in the list of notifications exceeds the predetermined number; automatically removing at least one notice from the calendar pane in response to detecting that the number of notices exceeds the predetermined number.

80. The system of claim 79, further comprising:

83. The notification module: Detecting when a period of the incoming event has completed; automatically removing at least one notification in the list of notifications associated with the upcoming event from the calendar pane; 80. The system of claim 79, further comprising:

84. receiving a notification from a calendar application; displaying the list of notifications, including events coming during a predetermined time period, in a calendar pane of a notification center on the display; The method according to claim 1, further comprising:

85. 85. The method of claim 84, wherein the incoming events are organized in chronological order.

86. 85. The method of claim 84, wherein the calendar pane is adjusted in real time while one of the upcoming events is in progress.

87. moreover, detecting a predetermined number of notifications to display for the calendar application; detecting whether a number of notifications in the list of notifications exceeds the predetermined number; in response to detecting that a number of notices in the list of notices exceeds the predetermined number, automatically removing at least one notice from the calendar pane; 85. The method of claim 84, comprising:

88. moreover, detecting when a period of the incoming event has completed; automatically removing at least one notification in the notification list associated with the upcoming event from the calendar pane; 85. The method of claim 84, comprising:

Citation Information

Patent Citations

  • Information processor

    JP2010073145A

  • Communication system

    JP2011107933A

  • System for and method of displaying notification received from plural applications

    JP2024026134A

  • Smart object based GUI for touch input devices

    US20100262928A1

  • Mobile terminal and method of controlling application execution in a mobile terminal

    US20110080356A1