US20150150027A1 - Flexible architecture for notifying applications of state changes - Google Patents
Flexible architecture for notifying applications of state changes Download PDFInfo
- Publication number
- US20150150027A1 US20150150027A1 US14/609,134 US201514609134A US2015150027A1 US 20150150027 A1 US20150150027 A1 US 20150150027A1 US 201514609134 A US201514609134 A US 201514609134A US 2015150027 A1 US2015150027 A1 US 2015150027A1
- Authority
- US
- United States
- Prior art keywords
- notification
- state
- client
- state property
- change
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F15/00—Digital computers in general; Data processing equipment in general
- G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/542—Event management; Broadcasting; Multicasting; Notifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F1/00—Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/4401—Bootstrapping
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/55—Push-based network services
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
- H04L67/62—Establishing a time schedule for servicing the requests
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/544—Remote
Definitions
- mobile devices are designed to run a variety of applications and keep a user updated with current information. Some of these devices include personal digital assistants, wireless phones, and email devices. Mobile devices are now capable of connecting to the Internet and other networks thorough various means and thus exchange information over the networks. These mobile devices may update applications and send and receive information, such as emails, attachments to emails, and web page content. Providing all of this functionality requires applications on the mobile device to be notified of various events, such as when a new email is available, when a screen of the device is activated, when a phone call is received, and the like. It is difficult, however, to access all of the different state changes associated with the device.
- the present invention is directed at unifying state and notification architecture across devices.
- clients register with a notification broker to receive notifications for changes to state properties.
- a notification broker determines which clients to notify of the state change and provides the client with a notification regarding the change.
- a client may register to receive notifications regarding changes to battery strength, network connectivity, memory usage, and the like.
- the notification broker sends the client a notification message.
- clients may be notified whenever a state changes, when a state change meets a predetermined condition, or based on a schedule.
- an application may be launched in response to a state change or a schedule.
- a client may register to have an application started when a certain event occurs, such as the mobile device receiving a message directed toward the application to be launched.
- the application may also be started based on a schedule configured by the client.
- an application programming interface is provided that is directed to providing a unified way of accessing state change information across different components within the device.
- an application may use the same function call to access state properties set by different components within the device.
- the registered state properties may persist across device reboots.
- FIG. 1 illustrates an exemplary computing device
- FIG. 2 shows an exemplary mobile device
- FIG. 3 illustrates an exemplary state management and notification system
- FIG. 4 illustrates a process for a state change notification system
- FIG. 5 shows a process for processing state change information, in accordance with aspects of the invention.
- the present invention is directed to providing a method and system a unified mechanism for storing device, application, and service state, as well as a rich notification brokerage architecture.
- clients register with a notification broker to receive notifications when certain state properties change.
- the notification broker determines which clients to notify of the state change and provides the client with a notification regarding the change.
- Clients may be notified whenever a state changes, when a state change meets a predetermined condition, or based on a schedule.
- An application may also be launched in response to a state change or a schedule.
- An application programming interface is also provided that is directed at providing a unified way of accessing state change information across different components within the device.
- state property refers to a “status” variable registered and stored with the notification system for maintenance and change-notifications.
- notification request refers to a request from a client to be notified of a state change.
- notification list refers to a collection of clients which have registered for state property change notifications.
- notification broker refers to an underlying driver responsible for adding, updating, and removing data from a data store.
- state change component refers to any component which adds, updates, or generally maintains State Properties in the data store.
- client refers to any component which registers for state property change notifications.
- a client may be a state change component as well as a state change component being a client.
- state property identifier refers to a “friendly” string (name) representation of the State Property. This identifier may be hierarchical and is unique.
- condition notification refers to a notification that is sent when a state property changes and the new value of the state property meets the condition that was specified in the notification request.
- an exemplary system for implementing the invention includes a computing device, such as computing device 100 .
- Computing device 100 may be configured as a client or a server.
- computing device 100 typically includes at least one processing unit 102 and system memory 104 .
- system memory 104 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two.
- System memory 104 typically includes an operating system 105 , one or more program modules 106 , and may include program data 107 . This basic configuration is illustrated in FIG. 1 by those components within dashed line 108 .
- Computing device 100 may have additional features or functionality.
- computing device 100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape.
- additional storage is illustrated in FIG. 1 by removable storage 109 and non-removable storage 110 .
- Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
- System memory 104 , removable storage 109 and non-removable storage 110 are all examples of computer storage media.
- Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computing device 100 . Any such computer storage media may be part of device 100 .
- Computing device 100 may also have input device(s) 112 such as keyboard, mouse, pen, voice input device, touch input device, etc.
- Output device(s) 114 such as a display, speakers, printer, etc. may also be included.
- Computing device 100 also contains communication connections 116 that allow the device to communicate with other computing devices 118 , such as over a network.
- Communication connections 116 are one example of communication media.
- Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.
- modulated data signal means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal.
- communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.
- the term computer readable media as used herein includes both storage media and communication media.
- one exemplary system for implementing the invention includes a mobile device, such as mobile device 200 .
- the mobile device 200 has a processor 260 , a memory 262 , a display 228 , and a keypad 232 .
- the memory 262 generally includes both volatile memory (e.g., RAM) and non-volatile memory (e.g., ROM, Flash Memory, or the like).
- the mobile device 200 includes an operating system 264 , such as the Windows CE operating system from Microsoft Corporation or other operating system, which is resident in the memory 262 and executes on the processor 260 .
- the keypad 232 may be a push button numeric dialing pad (such as on a typical telephone), a multi-key keyboard (such as a conventional keyboard).
- the display 228 may be a liquid crystal display, or any other type of display commonly used in mobile devices.
- the display 228 may be touch-sensitive, and would then also act as an input device.
- One or more application programs 266 are loaded into memory 262 and run on the operating system 264 .
- Examples of application programs include phone dialer programs, email programs, scheduling programs, PIM (personal information management) programs, word processing programs, spreadsheet programs, Internet browser programs, and so forth.
- Application programs 266 may use a common API to perform actions on state properties associated with the device. For example, a phone dialer program may register with a notification system to receive notifications regarding changes to signal strength, phone state, battery strength, and the like.
- the mobile computing device 200 also includes non-volatile storage 268 within the memory 262 . The non-volatile storage 268 may be used to store persistent information which should not be lost if the mobile computing device 200 is powered down.
- the applications 266 may use and store information in the storage 268 , such as e-mail or other messages used by an e-mail application, contact information used by a PIM, appointment information used by a scheduling program, documents used by a word processing program, and the like.
- the mobile computing device 200 has a power supply 270 , which may be implemented as one or more batteries.
- the power supply 270 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.
- the mobile computing device 200 may also include external notification mechanisms, such as an LED (not shown) and an audio interface 274 . These devices may be directly coupled to the power supply 270 so that when activated, they remain on for a duration dictated by the notification mechanism even though the processor 260 and other components might shut down to conserve battery power.
- the audio interface 274 is used to provide audible signals to and receive audible signals from the user.
- the audio interface 274 may be coupled to a speaker for providing audible output and to a microphone for receiving audible input, such as to facilitate a telephone conversation.
- Mobile computing device 200 may also contain communication connections 240 that allow the device to communicate with other computing devices, such as over a wireless network.
- the mobile computing device 200 also includes a radio interface layer 272 that performs the function of transmitting and receiving radio frequency communications.
- the radio interface layer 272 facilitates wireless connectivity between the mobile computing device 200 and the outside world, via a communications carrier or service provider. Transmissions to and from the radio interface layer 272 are conducted under control of the operating system 264 . In other words, communications received by the radio interface layer 272 and communication connections 240 may be disseminated to application programs 266 via the operating system 264 , and vice versa.
- FIG. 3 illustrates an exemplary state management and notification system, in accordance with aspects of the invention.
- Notification system 300 includes state change component 310 , clients 315 and 320 , notification broker 335 , and data store 330 .
- notification broker 335 also maintains notification lists 340 , cached properties 345 and scheduler 350 .
- Clients such as client 315 or 320 register to receive notifications regarding changes to a state property with notification broker 335 .
- a client may make a notification request with notification broker 335 that registers the client to receive notifications whenever a state property changes, when the change meets a conditional, or based upon a schedule.
- the notifications may be permanent or transient notifications.
- Permanent notifications are kept in a data store ( 320 ).
- the permanent notifications are maintained in a back-end data store, such as the registry, and hence are “persisted” across reboots. As these notifications are persisted, these types of state properties have the same value before a soft-reset (or shutdown) as they do upon a restart (or boot).
- state properties are persistent by default.
- Transient notifications are not permanent and are, therefore, not persisted across reboots. In other words, if a device is soft-reset (or rebooted) the notification request is deleted from notification list 340 . In order to restore a transient notification, a client re-registers (sends another notification request to broker 335 ) to receive notifications regarding changes to the state property.
- a client may also register to have an application launched upon the occurrence of a state change and/or according to a schedule.
- notification broker 335 issues a command to start an application specified by the client if the application is not already running when the state change or the scheduled time occurs.
- the client can specify command-line parameters to be passed into the application when it is launched. If the launched process creates a window then a message is sent to the window indicating the notification. If the target process is already running on the client, then the client simply receives the notification message.
- Notifications sent to clients may also be batched. Batched state properties are intended for use by state properties which may undergo frequent value changes.
- a predetermined period of time is set that allows the state property value to “stabilize.” According to one embodiment, the predetermined period is set to 200 ms. If no changes are made to the state property value during the predetermined period, the notification is delivered to the registered clients.
- the batching predetermined period is configurable and is stored in data store 330 .
- Data store 330 is configured to store registered state properties, as well as other information.
- data store 330 is the registry provided with an operating system, such as the registry provided with the Windows XP operating system provided by Microsoft Corporation.
- Data store 330 may also be any other type of data store in which information may be set and accessed.
- Data store 330 may also comprise one or more data stores maintained at various locations within notification system 300 .
- Data store 330 may also be pre-loaded with a default set of state property data that may be accessed by clients 315 and 320 .
- Pre-loading the state property data makes many of state properties available without the client having to add a state property.
- the following states are available to clients without registering the state: Display Orientation (Resolution, Brightness); Undismissed reminders (Count, Subject, Date, Time; Location); Undismissed alarms (Count, Description, Date, Time); Battery (% remaining, State); Backup battery (% remaining, State); Memory (Program memory free, Program memory used, Storage memory free, Storage memory used); Storage card (Total memory free, Total memory used); Hardware (Flip-phone state (open/closed), Keyboard enabled, Wifi enabled, Bluetooth enabled, Headphones present, Camera present); Messaging (Unread count, Total count, Drafts count, Outbox count); Tasks (High priority count, Due today count, Overdue count); Calendar(Next appointment, Name, Location, Date, Time, POOM ID); All
- the state property data is organized into a hierarchy.
- the hierarchy allows a client to specify a group of state properties by referencing the parent.
- the state property may be set to a data type, such as string, integer, float, and the like.
- the client may identify the state property by a “friendly” string (name) representation of the state property. For example, “battery ⁇ a” references the state property “a” under the parent “battery”, and likewise there could be a “battery ⁇ b” which would be the state property “b” under the same parent.
- the parent identifier may be used. For example to receive notifications based on changes to all of the battery states, then “battery” would be provided in the registration, thereby referencing all of the battery state properties using a single name.
- Broker 335 may be configured to control access to setting/adjusting/removing state property types within data store 330 .
- a restriction could be placed on a state property limiting the deletion of the property from the notification system to a predetermined list of clients.
- clients that have registered for notifications relating to the property are notified of its deletion.
- clients 315 and 320 register for the state properties they are interested in receiving notifications about when the state property changes.
- Clients may register to receive a notification whenever the state they registered changes, when a conditional applied to the state value meets a condition, or upon a predetermined schedule.
- a conditional notification may be based upon many different conditions.
- the conditionals include: all, equal, not equal, greater than, greater or equal than, less than or equal, less than, contains, starts with, and ends with.
- client 315 may register with notification broker 335 to receive a notification when the missed call count state property is Greater than fifteen and when the caller name Contains “Ja.”
- Conditionals allow a client to receive the state change information they are interested in without having to process state change information they do not care about.
- Notification broker 335 accesses notification lists 340 to determine the clients that should receive notifications when a registered state property has changed.
- Scheduler 350 may be configured to notify and/or activate a client based on a schedule.
- the scheduled activation notification mode allows a client to receive a notification based on a simplified recurring schedule registered with notification broker 335 .
- Schedules may be configured to occur at any interval, such as on the scale of seconds, minutes, hours, days, weeks, or months. According to one embodiment, schedules are defined by the date/time of the first occurrence and the amount of time between occurrences. Additionally, schedules may be defined without a recurrence interval. When no recurrence interval is provided, the notification is only sent once and then the registration is removed from the notifications list. Additionally, when a notification arrives, if the specified application path (provided during the notification request) cannot be found, the scheduled notification registration is removed from the notification list 340 .
- State change component 310 updates the value of the state property within data store 330 when the state changes.
- State change component 310 may update the state directly in data store 330 or through notification broker 335 .
- data store 330 communicates the change to notification broker 335 .
- notification broker 335 updates the state in data store 330 .
- notification broker 335 determines which clients should be notified based on the state change.
- Notification broker 335 parses notification lists 340 and determines the clients that have registered for notifications regarding the state change.
- Notification broker 335 applies any conditionals to the value of the state property that has changed and notifies the client when the conditional is met. When there is not a conditional associated with the state change, the client is notified of the state change.
- a client such as client 315 and client 320
- the client may call a function within a common API (see discussion below) to retrieve the new state of the state property.
- the property information may be directly delivered to the client along with the notification.
- the client may un-register itself from receiving change notifications relating to the state property.
- Clients 315 and 320 may also directly query broker 335 at any time to find the state of a state property using the common API.
- State property values may also be cached by notification broker 335 in cached properties 345 .
- a state property value may be cached for many different reasons. For example, a state property value may be cached such that a previous value of the state property may be compared with a current value of the state property. Additionally, the cache may help to facilitate quick repeated lookups requesting the value of the state property.
- notification system 300 supports .NET (managed) clients for both additions to the store, as well as change notification registrations.
- Norm the Newbie has built a C# application which keeps a complete database of the current season's Baseball statistics (e.g., teams, players, scores, stats, etc.). He has also built a simple XML web-services client which can connect to a sports website and pull-down updated daily statistics. Since the amount of data the application stores is relatively large, Norm only wants his application to sync data when a “fat pipe” (e.g., 802.1x) is available on the device (e.g., PPC). Norm then registers his application by sending a notification request to notification broker 335 for notifications when a high-bandwidth connection is available. Norm additionally specifies in the notification request to launch his application when the high-bandwidth connection is available.
- a “fat pipe” e.g. 802.1x
- notification broker 335 activates Norm's app when the state indicates that it is a high-speed connection.
- the application allows an insurance adjuster to look-up part #s and costs, make notes, retrieve car schematics, and the like. Each day, the insurance adjuster takes his mobile computing device out in the field to service customers.
- the application persists all of its data for today's operation locally in a data store.
- Elph would like the application to synchronize the offline store with the company's main servers each time the device is cradled. Therefore, Elph registers his application for notifications on synchronization cradle events. Whenever the device is cradled, the application is notified and the application synchronizes its data.
- Golem the phone game developer is building a next-generation multi-player RPG for a phone. He anticipates the game will be so very popular that it will last for weeks and months at a time.
- One of Golem's key concerns is the persistence of game state without user intervention.
- One of the game's neat features is the ability to save current state right before the phone runs out of batteries and ensure the user never loses any data.
- Golem registers his application to receive low battery notifications to ensure that the game information will be saved before the device runs out of batteries.
- Eric the emerging Enterprise Management Client developer is looking to create the next generation mobile computing device and phone management client; able to handle client updates, virus scanning, policy enforcement, and more.
- C# he has built a power device-side client which can handle requests based on server-driven commands.
- Eric would like his application “woken up” so he can contact the server for updated policies, virus scanner signatures, and the like.
- he simply registers his application with notification broker 335 for a scheduled notification (each day at 3am).
- Eric is now assured his app will run at the specified time.
- FIG. 4 illustrates a process for a state change notification system, in accordance with aspects of the invention.
- process 400 flows to block 410 , where a client registers to be notified of changes to at least one state property. If the state property is not already being monitored by another client, the state property is added to the list of available state properties. As discussed above, a list of available properties is pre-loaded into the notification system. The client may register to receive notification on all changes made to the property, changes that meet a condition, as well being notified according to a schedule.
- a callback is registered with the notification system such that when a change is made to a registered state property, the notification system is made aware of the change.
- a notification broker registers a callback with the operating system registry for changes made to the state property value.
- the client is added to a notification list to receive notification messages relating to the state property.
- Clients included in the notification list receive notifications regarding changes to the registered state property.
- a callback is received when a change is made to any of the registered state properties.
- the callback includes an identifier identifying the state property changes, as well as the current value of the state property.
- processing the state change information includes determining if any conditionals, schedules, batches, or application launching conditions, apply to each of the registered clients for the changed state property (See FIG. 5 and related discussion).
- FIG. 5 shows a process for processing state change information, in accordance with aspects of the invention.
- process 500 flows to block 510 where a client registered for receiving notifications regarding a state change for the changed state property is accessed.
- a notification list is accessed to determine the registered clients for the state property that has changed.
- the process flows to decision block 530 where a determination is made as to whether the condition is met.
- the process moves to decision block 540 , where a determination is made as to whether the client has specified to launch an application in response to a change to the state property.
- the process moves to block 550 where the application is launched if it is not already running
- the process moves to block 560 where the client is notified of the state change.
- the process then flows to decision block 570 , where a determination is made as to whether there are more clients registered to receive a notification regarding a change to the state property. When there is another client, the process returns to block 510 . When there are no other clients, the process then moves to an end block and returns to processing other actions.
- two APIs may be used to access the state information in the notification system.
- a native, or underlying API is provided and a managed API is provided to clients.
- the managed API accesses the native API to perform its operations.
Abstract
Described is a method and system a unified mechanism for storing device, application, and service state, as well as a rich notification brokerage architecture. Clients register with a notification broker to receive notifications for changes to state properties. When a registered state property changes, a notification broker determines which clients to notify of the state change and provides the client with a notification regarding the change. Clients may be notified whenever a state changes, when a state change meets a predetermined condition, or based on a schedule. An application may also be launched in response to a state change. An application programming interface (API) is provided that provides a unified way of accessing state change information across different components within the device.
Description
- This application is a continuation of application Ser. No. 12/624,038, filed Nov. 23, 2009, which is a continuation of application Ser. No. 10/873,881, filed Jun. 22, 2004, now U.S. Pat. No. 7,644,376, which application claims the benefit of provisional application Ser. No. 60/513,723, filed Oct. 23, 2003, which applications are incorporated herein by reference in their entirety.
- Today, mobile devices are designed to run a variety of applications and keep a user updated with current information. Some of these devices include personal digital assistants, wireless phones, and email devices. Mobile devices are now capable of connecting to the Internet and other networks thorough various means and thus exchange information over the networks. These mobile devices may update applications and send and receive information, such as emails, attachments to emails, and web page content. Providing all of this functionality requires applications on the mobile device to be notified of various events, such as when a new email is available, when a screen of the device is activated, when a phone call is received, and the like. It is difficult, however, to access all of the different state changes associated with the device.
- Briefly described, the present invention is directed at unifying state and notification architecture across devices. According to one aspect of the invention, clients register with a notification broker to receive notifications for changes to state properties. When a registered state property changes, a notification broker determines which clients to notify of the state change and provides the client with a notification regarding the change. For example, a client may register to receive notifications regarding changes to battery strength, network connectivity, memory usage, and the like. Whenever one of these registered state properties changes, the notification broker sends the client a notification message.
- According to another aspect of the invention, clients may be notified whenever a state changes, when a state change meets a predetermined condition, or based on a schedule.
- According to yet another aspect of the invention, an application may be launched in response to a state change or a schedule. For example, a client may register to have an application started when a certain event occurs, such as the mobile device receiving a message directed toward the application to be launched. The application may also be started based on a schedule configured by the client.
- According to yet another aspect of the invention, an application programming interface (API) is provided that is directed to providing a unified way of accessing state change information across different components within the device. For example, an application may use the same function call to access state properties set by different components within the device.
- According to still yet another aspect of the invention, the registered state properties may persist across device reboots.
-
FIG. 1 illustrates an exemplary computing device; -
FIG. 2 shows an exemplary mobile device; -
FIG. 3 illustrates an exemplary state management and notification system; -
FIG. 4 illustrates a process for a state change notification system; - and
-
FIG. 5 shows a process for processing state change information, in accordance with aspects of the invention. - Briefly described, the present invention is directed to providing a method and system a unified mechanism for storing device, application, and service state, as well as a rich notification brokerage architecture. Generally, clients register with a notification broker to receive notifications when certain state properties change. When a registered state property changes, the notification broker determines which clients to notify of the state change and provides the client with a notification regarding the change. Clients may be notified whenever a state changes, when a state change meets a predetermined condition, or based on a schedule. An application may also be launched in response to a state change or a schedule. An application programming interface (API) is also provided that is directed at providing a unified way of accessing state change information across different components within the device.
- Throughout the specification and claims, the following terms take at least the meanings explicitly associated herein, unless the context clearly dictates otherwise. The meanings identified below are not intended to limit the terms, but merely provide illustrative examples for the terms. The meaning of “a,” “an,” and “the” includes plural reference, the meaning of “in” includes “in” and “on.”
- The term “state property” refers to a “status” variable registered and stored with the notification system for maintenance and change-notifications.
- The term “notification request” refers to a request from a client to be notified of a state change.
- The term “notification list” refers to a collection of clients which have registered for state property change notifications.
- The term “notification broker” refers to an underlying driver responsible for adding, updating, and removing data from a data store.
- The term “state change component” refers to any component which adds, updates, or generally maintains State Properties in the data store.
- The term “client” refers to any component which registers for state property change notifications. A client may be a state change component as well as a state change component being a client.
- The term “state property identifier” refers to a “friendly” string (name) representation of the State Property. This identifier may be hierarchical and is unique.
- The term “conditional notification” refers to a notification that is sent when a state property changes and the new value of the state property meets the condition that was specified in the notification request.
- With reference to
FIG. 1 , an exemplary system for implementing the invention includes a computing device, such ascomputing device 100.Computing device 100 may be configured as a client or a server. In a very basic configuration,computing device 100 typically includes at least oneprocessing unit 102 andsystem memory 104. Depending on the exact configuration and type of computing device,system memory 104 may be volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two.System memory 104 typically includes anoperating system 105, one ormore program modules 106, and may includeprogram data 107. This basic configuration is illustrated inFIG. 1 by those components withindashed line 108. -
Computing device 100 may have additional features or functionality. For example,computing device 100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated inFIG. 1 byremovable storage 109 andnon-removable storage 110. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.System memory 104,removable storage 109 andnon-removable storage 110 are all examples of computer storage media. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computingdevice 100. Any such computer storage media may be part ofdevice 100.Computing device 100 may also have input device(s) 112 such as keyboard, mouse, pen, voice input device, touch input device, etc. Output device(s) 114 such as a display, speakers, printer, etc. may also be included. -
Computing device 100 also containscommunication connections 116 that allow the device to communicate withother computing devices 118, such as over a network.Communication connections 116 are one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The term computer readable media as used herein includes both storage media and communication media. - With reference to
FIG. 2 , one exemplary system for implementing the invention includes a mobile device, such asmobile device 200. Themobile device 200 has aprocessor 260, amemory 262, adisplay 228, and akeypad 232. Thememory 262 generally includes both volatile memory (e.g., RAM) and non-volatile memory (e.g., ROM, Flash Memory, or the like). Themobile device 200 includes anoperating system 264, such as the Windows CE operating system from Microsoft Corporation or other operating system, which is resident in thememory 262 and executes on theprocessor 260. Thekeypad 232 may be a push button numeric dialing pad (such as on a typical telephone), a multi-key keyboard (such as a conventional keyboard). Thedisplay 228 may be a liquid crystal display, or any other type of display commonly used in mobile devices. Thedisplay 228 may be touch-sensitive, and would then also act as an input device. - One or
more application programs 266 are loaded intomemory 262 and run on theoperating system 264. Examples of application programs include phone dialer programs, email programs, scheduling programs, PIM (personal information management) programs, word processing programs, spreadsheet programs, Internet browser programs, and so forth.Application programs 266 may use a common API to perform actions on state properties associated with the device. For example, a phone dialer program may register with a notification system to receive notifications regarding changes to signal strength, phone state, battery strength, and the like. Themobile computing device 200 also includesnon-volatile storage 268 within thememory 262. Thenon-volatile storage 268 may be used to store persistent information which should not be lost if themobile computing device 200 is powered down. Theapplications 266 may use and store information in thestorage 268, such as e-mail or other messages used by an e-mail application, contact information used by a PIM, appointment information used by a scheduling program, documents used by a word processing program, and the like. - The
mobile computing device 200 has apower supply 270, which may be implemented as one or more batteries. Thepower supply 270 might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries. - The
mobile computing device 200 may also include external notification mechanisms, such as an LED (not shown) and anaudio interface 274. These devices may be directly coupled to thepower supply 270 so that when activated, they remain on for a duration dictated by the notification mechanism even though theprocessor 260 and other components might shut down to conserve battery power. Theaudio interface 274 is used to provide audible signals to and receive audible signals from the user. For example, theaudio interface 274 may be coupled to a speaker for providing audible output and to a microphone for receiving audible input, such as to facilitate a telephone conversation. -
Mobile computing device 200 may also containcommunication connections 240 that allow the device to communicate with other computing devices, such as over a wireless network. Themobile computing device 200 also includes aradio interface layer 272 that performs the function of transmitting and receiving radio frequency communications. Theradio interface layer 272 facilitates wireless connectivity between themobile computing device 200 and the outside world, via a communications carrier or service provider. Transmissions to and from theradio interface layer 272 are conducted under control of theoperating system 264. In other words, communications received by theradio interface layer 272 andcommunication connections 240 may be disseminated toapplication programs 266 via theoperating system 264, and vice versa. -
FIG. 3 illustrates an exemplary state management and notification system, in accordance with aspects of the invention.Notification system 300 includesstate change component 310,clients notification broker 335, anddata store 330. According to one embodiment,notification broker 335 also maintains notification lists 340, cachedproperties 345 andscheduler 350. - Clients, such as
client notification broker 335. Generally, a client may make a notification request withnotification broker 335 that registers the client to receive notifications whenever a state property changes, when the change meets a conditional, or based upon a schedule. The notifications may be permanent or transient notifications. - Permanent notifications are kept in a data store (320). According to one embodiment, the permanent notifications are maintained in a back-end data store, such as the registry, and hence are “persisted” across reboots. As these notifications are persisted, these types of state properties have the same value before a soft-reset (or shutdown) as they do upon a restart (or boot). According to one embodiment, state properties are persistent by default.
- Transient notifications are not permanent and are, therefore, not persisted across reboots. In other words, if a device is soft-reset (or rebooted) the notification request is deleted from
notification list 340. In order to restore a transient notification, a client re-registers (sends another notification request to broker 335) to receive notifications regarding changes to the state property. - A client may also register to have an application launched upon the occurrence of a state change and/or according to a schedule. Generally,
notification broker 335 issues a command to start an application specified by the client if the application is not already running when the state change or the scheduled time occurs. According to one embodiment, the client can specify command-line parameters to be passed into the application when it is launched. If the launched process creates a window then a message is sent to the window indicating the notification. If the target process is already running on the client, then the client simply receives the notification message. - Notifications sent to clients may also be batched. Batched state properties are intended for use by state properties which may undergo frequent value changes. A predetermined period of time is set that allows the state property value to “stabilize.” According to one embodiment, the predetermined period is set to 200 ms. If no changes are made to the state property value during the predetermined period, the notification is delivered to the registered clients. The batching predetermined period is configurable and is stored in
data store 330. -
Data store 330 is configured to store registered state properties, as well as other information. According to one embodiment,data store 330 is the registry provided with an operating system, such as the registry provided with the Windows XP operating system provided by Microsoft Corporation.Data store 330 may also be any other type of data store in which information may be set and accessed.Data store 330 may also comprise one or more data stores maintained at various locations withinnotification system 300. -
Data store 330 may also be pre-loaded with a default set of state property data that may be accessed byclients - According to one embodiment, the state property data is organized into a hierarchy. The hierarchy allows a client to specify a group of state properties by referencing the parent. The state property may be set to a data type, such as string, integer, float, and the like.
- The client may identify the state property by a “friendly” string (name) representation of the state property. For example, “battery\a” references the state property “a” under the parent “battery”, and likewise there could be a “battery\b” which would be the state property “b” under the same parent. When referring to a group of state properties under a common parent, then the parent identifier may be used. For example to receive notifications based on changes to all of the battery states, then “battery” would be provided in the registration, thereby referencing all of the battery state properties using a single name.
-
Broker 335 may be configured to control access to setting/adjusting/removing state property types withindata store 330. For example, a restriction could be placed on a state property limiting the deletion of the property from the notification system to a predetermined list of clients. When a state property is deleted, clients that have registered for notifications relating to the property are notified of its deletion. - As discussed above,
clients client 315 may register withnotification broker 335 to receive a notification when the missed call count state property is Greater than fifteen and when the caller name Contains “Ja.” Conditionals allow a client to receive the state change information they are interested in without having to process state change information they do not care about. - The clients registered to receive notifications regarding changes to state properties are maintained in notification lists 340.
Notification broker 335 accesses notification lists 340 to determine the clients that should receive notifications when a registered state property has changed. -
Scheduler 350 may be configured to notify and/or activate a client based on a schedule. The scheduled activation notification mode allows a client to receive a notification based on a simplified recurring schedule registered withnotification broker 335. Schedules may be configured to occur at any interval, such as on the scale of seconds, minutes, hours, days, weeks, or months. According to one embodiment, schedules are defined by the date/time of the first occurrence and the amount of time between occurrences. Additionally, schedules may be defined without a recurrence interval. When no recurrence interval is provided, the notification is only sent once and then the registration is removed from the notifications list. Additionally, when a notification arrives, if the specified application path (provided during the notification request) cannot be found, the scheduled notification registration is removed from thenotification list 340. -
State change component 310 updates the value of the state property withindata store 330 when the state changes.State change component 310 may update the state directly indata store 330 or throughnotification broker 335. When the state is updated throughdata store 330,data store 330 communicates the change tonotification broker 335. When the state is updated throughnotification broker 335 thennotification broker 335 updates the state indata store 330. In either case,notification broker 335 determines which clients should be notified based on the state change.Notification broker 335 parses notification lists 340 and determines the clients that have registered for notifications regarding the state change.Notification broker 335 applies any conditionals to the value of the state property that has changed and notifies the client when the conditional is met. When there is not a conditional associated with the state change, the client is notified of the state change. - When a client, such as
client 315 andclient 320, receives a notification fromnotification broker 335, the client may call a function within a common API (see discussion below) to retrieve the new state of the state property. Alternatively, the property information may be directly delivered to the client along with the notification. When the client is no longer interested in receiving notifications relating to a particular state property, the client may un-register itself from receiving change notifications relating to the state property.Clients broker 335 at any time to find the state of a state property using the common API. - State property values may also be cached by
notification broker 335 in cachedproperties 345. A state property value may be cached for many different reasons. For example, a state property value may be cached such that a previous value of the state property may be compared with a current value of the state property. Additionally, the cache may help to facilitate quick repeated lookups requesting the value of the state property. - According to one embodiment,
notification system 300 supports .NET (managed) clients for both additions to the store, as well as change notification registrations. - The following are some exemplary scenarios to further clarify state
management notification system 300. - Norm the Newbie has built a C# application which keeps a complete database of the current season's Baseball statistics (e.g., teams, players, scores, stats, etc.). He has also built a simple XML web-services client which can connect to a sports website and pull-down updated daily statistics. Since the amount of data the application stores is relatively large, Norm only wants his application to sync data when a “fat pipe” (e.g., 802.1x) is available on the device (e.g., PPC). Norm then registers his application by sending a notification request to
notification broker 335 for notifications when a high-bandwidth connection is available. Norm additionally specifies in the notification request to launch his application when the high-bandwidth connection is available. - When the state change component associated with the connection updates the state of the connection,
notification broker 335 activates Norm's app when the state indicates that it is a high-speed connection. - Elph the Enterprise developer has built a field-service form-based VB.Net application for insurance adjuster usage. The application allows an insurance adjuster to look-up part #s and costs, make notes, retrieve car schematics, and the like. Each day, the insurance adjuster takes his mobile computing device out in the field to service customers. The application persists all of its data for today's operation locally in a data store. Elph would like the application to synchronize the offline store with the company's main servers each time the device is cradled. Therefore, Elph registers his application for notifications on synchronization cradle events. Whenever the device is cradled, the application is notified and the application synchronizes its data.
- Golem the phone game developer is building a next-generation multi-player RPG for a phone. He anticipates the game will be so very popular that it will last for weeks and months at a time. One of Golem's key concerns is the persistence of game state without user intervention. One of the game's neat features is the ability to save current state right before the phone runs out of batteries and ensure the user never loses any data. Golem registers his application to receive low battery notifications to ensure that the game information will be saved before the device runs out of batteries.
- Eric the emerging Enterprise Management Client developer is looking to create the next generation mobile computing device and phone management client; able to handle client updates, virus scanning, policy enforcement, and more. Using C# he has built a power device-side client which can handle requests based on server-driven commands. Each night at 3am, Eric would like his application “woken up” so he can contact the server for updated policies, virus scanner signatures, and the like. In order to achieve this, he simply registers his application with
notification broker 335 for a scheduled notification (each day at 3am). Eric is now assured his app will run at the specified time. -
FIG. 4 illustrates a process for a state change notification system, in accordance with aspects of the invention. After a start block,process 400 flows to block 410, where a client registers to be notified of changes to at least one state property. If the state property is not already being monitored by another client, the state property is added to the list of available state properties. As discussed above, a list of available properties is pre-loaded into the notification system. The client may register to receive notification on all changes made to the property, changes that meet a condition, as well being notified according to a schedule. - Moving to block 420, a callback is registered with the notification system such that when a change is made to a registered state property, the notification system is made aware of the change. According to one embodiment, a notification broker registers a callback with the operating system registry for changes made to the state property value.
- Flowing to block, 430, the client is added to a notification list to receive notification messages relating to the state property. Clients included in the notification list receive notifications regarding changes to the registered state property.
- Transitioning to block 440, a callback is received when a change is made to any of the registered state properties. According to one embodiment, the callback includes an identifier identifying the state property changes, as well as the current value of the state property.
- Moving to block 450, the state change information is processed. Generally, processing the state change information includes determining if any conditionals, schedules, batches, or application launching conditions, apply to each of the registered clients for the changed state property (See
FIG. 5 and related discussion). -
FIG. 5 shows a process for processing state change information, in accordance with aspects of the invention. After a start block,process 500 flows to block 510 where a client registered for receiving notifications regarding a state change for the changed state property is accessed. According to one embodiment, a notification list is accessed to determine the registered clients for the state property that has changed. - Moving to decision block 520, a determination is made as to whether the client has specified any conditionals that are to be applied to the state property before notifying the client.
- When a conditional expression is associated with the notification request, the process flows to decision block 530 where a determination is made as to whether the condition is met. When the condition is met, or when the client has not specified any conditionals, the process moves to decision block 540, where a determination is made as to whether the client has specified to launch an application in response to a change to the state property. When the client has specified to launch the application, the process moves to block 550 where the application is launched if it is not already running When the client has not specified to launch the application, or the application has been launched at
block 550, the process moves to block 560 where the client is notified of the state change. - The process then flows to decision block 570, where a determination is made as to whether there are more clients registered to receive a notification regarding a change to the state property. When there is another client, the process returns to block 510. When there are no other clients, the process then moves to an end block and returns to processing other actions.
- According to one embodiment of the invention, two APIs may be used to access the state information in the notification system. A native, or underlying API is provided and a managed API is provided to clients. The managed API accesses the native API to perform its operations.
- The following is an exemplary native API, in accordance with aspects of the invention:
- The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
Claims (20)
1. A method for providing notifications to clients in response to state property changes, comprising:
at a notification broker that is located on a computing device, receiving a notification request from a client application on the computing device to receive a notification in response to an event that originates on the computing device; wherein the event is associated with a change in a state property of the computing device; wherein an Application Program Interface (API) is utilized by the client application to register the notification request;
ensuring that the state property is registered with the notification broker, wherein the notification broker includes state properties that are updated by different components within the computing device;
determining when the state property changes, wherein determining when the state property changes comprises using the API to specify a batching operation on changes to the state property that occur within a predetermined time period; wherein a call to the API batching operation specifies a time period for which a value of the state property is to remain constant before notifying the client application of a change to the state property;
determining when the client should receive notification of the state property change; and
notifying the client of the state property change by the notification broker on the computing device when determined that the client should receive notification of the state property change.
2. The method of claim 1 , wherein the notification request made through the API specifies to receive a notification upon an occurrence of at least one of: when a registered state property changes, when a change to the state property meets a conditional expression that is specified through the API, and upon a schedule determined by the client.
3. The method of claim 1 , wherein the API also comprises functions for:
registering different state properties across different components of the computing device to be monitored for changes by the notification broker; querying each of the state properties to determine a value; and setting the state properties.
4. The method of claim 1 , wherein execution of at least a particular portion of the client application on the computing device is dependent upon a received notification.
5. The method of claim 1 , wherein the notification request specified through the API comprises indicating when the notification is a permanent notification request and when the notification is a transient notification request; wherein the permanent notification request is stored by the notification broker in a data-store on the computing device that maintains the notification request across a reboot; wherein the transient notification is not maintained across the reboot.
6. The method of claim 1 , wherein the API includes functionality for specifying an action of the computing device when a change occurs to a registered state property when the computing device is in a standby mode, wherein the action comprises: ignoring the change, bringing the device out of the standby mode and raising the event when the computing device is taken out of the standby mode by a different event.
7. The method of claim 1 , further comprising either launching the client or notifying the client in response to a change to a registered state property.
8. The method of claim 1 , further comprising launching the client in response to a schedule defined by the client.
9. The method of claim 1 , wherein the state properties are arranged in a hierarchy.
10. A system for state management and notifications, the system comprising:
a processing unit;
a data store on a computing device that is arranged to store information relating to state properties, wherein at least some of the state properties are modified by different components;
an Application Program Interface (API) configured to perform operations relating to the state properties, and wherein the API is configured to specify a batching operation on changes to the state property that occur within a predetermined time period;
one or more client applications that are configured to execute using the processing unit, register notification requests using the API, and receive notifications in response to a change in a state property for which they have registered to receive a notification, wherein the notification requests indicate when the one or more clients should receive notifications in response to changes associated with the state properties, and wherein execution of the client applications is dependent upon a received notification;
a notification list stored within the data store that is arranged to store the client applications that have been registered to receive notification requests;
the notification broker coupled to the data store, the notification list, and the client applications, wherein the notification broker, includes functionality configured to perform the following actions, including to:
receive a notification request to add at least one client application to the notification list;
add the at least one client application to the notification list; and
determine when a registered state property changes, and when the state property changes, determine the one or more client applications to receive a notification, and notify the determined client applications of the state property change.
11. The system of claim 10 , wherein the computing device comprises a mobile device.
12. The system of claim 10 , wherein a call to the API batching operation specifies a time period for which a value of the state property is to remain constant before notifying a client application of a change to the state property.
13. The system of claim 10 , wherein the API includes functions comprising:
registering the state properties to be monitored for changes by a notification broker;
querying the state properties; setting the state properties; registering notification requests relating to the state properties; launching an application; and comparing the state properties to conditional expressions;
14. The system of claim 10 , wherein the change in the state property is responsive to an event that originates on a device executing the client application.
15. The system of claim 10 , wherein determining the one or more client applications to receive the notification, comprises: applying a conditional expression specified through the API to the state property before notifying the client of the change to the state property.
16. The system of claim 15 , wherein the conditional expression specified through the API comprises the following conditions: all, equal, not equal, greater than, greater or equal than, less than or equal, less than, contains, starts with, and ends with.
17. A method for receiving notifications at a client application in response to state property changes on a computing device, the method comprising:
at a computing device, transmitting a notification request from a client application to a notification broker to receive a notification in response to an event that originates on the client computing device; wherein the event is associated with a change in a state property of the computing device; wherein an Application Program Interface (API) is utilized by the client application to register the notification request, and wherein the notification broker includes state properties that are updated by different components within the computing device; and
based on a determination that the state property changes, receiving at the client application a notification of a state property change from the notification broker on the computing device when it is determined that the client application should receive notification of the state property change,
wherein the determination that the state property changes is performed using the API to specify a batching operation on changes to the state property that occur within a predetermined time period; wherein a call to the API batching operation specifies a time period for which a value of the state property is to remain constant before notifying the client application of a change to the state property.
18. The method of claim 17 , wherein the method further includes launching the client application in response to the notification of the state property change.
19. The method of claim 17 , wherein execution of at least a particular portion of the client application on the computing device is dependent upon a received notification.
20. The computer-readable storage device of claim 17 , wherein the change in the state property is responsive to an event that originates on a device executing the client application.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US14/609,134 US10169111B2 (en) | 2003-10-23 | 2015-01-29 | Flexible architecture for notifying applications of state changes |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US51372303P | 2003-10-23 | 2003-10-23 | |
US10/873,881 US7644376B2 (en) | 2003-10-23 | 2004-06-22 | Flexible architecture for notifying applications of state changes |
US12/624,038 US8990695B2 (en) | 2003-10-23 | 2009-11-23 | Flexible architecture for notifying applications of state changes |
US14/609,134 US10169111B2 (en) | 2003-10-23 | 2015-01-29 | Flexible architecture for notifying applications of state changes |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/624,038 Continuation US8990695B2 (en) | 2003-10-23 | 2009-11-23 | Flexible architecture for notifying applications of state changes |
Publications (2)
Publication Number | Publication Date |
---|---|
US20150150027A1 true US20150150027A1 (en) | 2015-05-28 |
US10169111B2 US10169111B2 (en) | 2019-01-01 |
Family
ID=34526892
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/873,881 Active 2025-08-07 US7644376B2 (en) | 2003-10-23 | 2004-06-22 | Flexible architecture for notifying applications of state changes |
US12/624,038 Active 2026-12-21 US8990695B2 (en) | 2003-10-23 | 2009-11-23 | Flexible architecture for notifying applications of state changes |
US14/609,134 Active 2026-01-14 US10169111B2 (en) | 2003-10-23 | 2015-01-29 | Flexible architecture for notifying applications of state changes |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/873,881 Active 2025-08-07 US7644376B2 (en) | 2003-10-23 | 2004-06-22 | Flexible architecture for notifying applications of state changes |
US12/624,038 Active 2026-12-21 US8990695B2 (en) | 2003-10-23 | 2009-11-23 | Flexible architecture for notifying applications of state changes |
Country Status (5)
Country | Link |
---|---|
US (3) | US7644376B2 (en) |
EP (1) | EP1679596A3 (en) |
JP (1) | JP4790245B2 (en) |
KR (1) | KR100920850B1 (en) |
CN (2) | CN1617501B (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150106474A1 (en) * | 2013-10-16 | 2015-04-16 | Ford Global Technologies, Llc | Method and Apparatus for Handling Application Triggering Events |
US20190073347A1 (en) * | 2017-09-01 | 2019-03-07 | Google Inc. | Lockscreen note-taking |
US20190095259A1 (en) * | 2017-09-26 | 2019-03-28 | Kyocera Document Solutions Inc. | Electronic Device and Log Application |
Families Citing this family (101)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6578054B1 (en) | 1999-10-04 | 2003-06-10 | Microsoft Corporation | Method and system for supporting off-line mode of operation and synchronization using resource state information |
US6909910B2 (en) * | 2002-02-01 | 2005-06-21 | Microsoft Corporation | Method and system for managing changes to a contact database |
US7644376B2 (en) * | 2003-10-23 | 2010-01-05 | Microsoft Corporation | Flexible architecture for notifying applications of state changes |
KR100640483B1 (en) * | 2004-10-22 | 2006-10-30 | 삼성전자주식회사 | Apparatus and method for automatic changing telephony mode of mobile terminal |
US8418075B2 (en) * | 2004-11-16 | 2013-04-09 | Open Text Inc. | Spatially driven content presentation in a cellular environment |
US8001476B2 (en) | 2004-11-16 | 2011-08-16 | Open Text Inc. | Cellular user interface |
US9654427B2 (en) * | 2005-07-11 | 2017-05-16 | Google Inc. | Presenting instant messages |
US7543003B2 (en) * | 2005-08-25 | 2009-06-02 | Microsoft Corporation | Providing change notifications to an entity-regarding a change of a specific type to data in a relational database |
US8225231B2 (en) | 2005-08-30 | 2012-07-17 | Microsoft Corporation | Aggregation of PC settings |
KR100717047B1 (en) * | 2005-10-20 | 2007-05-10 | 삼성전자주식회사 | Method and apparatus for displaying web page conveniently |
KR100739755B1 (en) | 2005-11-09 | 2007-07-13 | 삼성전자주식회사 | Method and apparatus for transmitting and receiving a information for UPnP event |
US7757185B2 (en) * | 2006-01-06 | 2010-07-13 | Apple Inc. | Enabling and disabling hotkeys |
US7599861B2 (en) | 2006-03-02 | 2009-10-06 | Convergys Customer Management Group, Inc. | System and method for closed loop decisionmaking in an automated care system |
US7930727B1 (en) * | 2006-03-30 | 2011-04-19 | Emc Corporation | System and method for measuring and enforcing security policy compliance for software during the development process of the software |
US7809663B1 (en) | 2006-05-22 | 2010-10-05 | Convergys Cmg Utah, Inc. | System and method for supporting the utilization of machine language |
US8379830B1 (en) | 2006-05-22 | 2013-02-19 | Convergys Customer Management Delaware Llc | System and method for automated customer service with contingent live interaction |
US8205189B2 (en) * | 2006-07-13 | 2012-06-19 | Oracle International Corporation | Method and system for definition control in a data repository application |
US20080039166A1 (en) * | 2006-08-03 | 2008-02-14 | Seven Lights, Llc | Systems and methods for multi-character online gaming |
US20080039165A1 (en) * | 2006-08-03 | 2008-02-14 | Seven Lights, Llc | Systems and methods for a scouting report in online gaming |
US20080039169A1 (en) * | 2006-08-03 | 2008-02-14 | Seven Lights, Llc | Systems and methods for character development in online gaming |
US9417758B2 (en) * | 2006-11-21 | 2016-08-16 | Daniel E. Tsai | AD-HOC web content player |
US8671146B2 (en) * | 2007-02-28 | 2014-03-11 | Microsoft Corporation | Presence aware notification for information technology management |
US8015571B2 (en) * | 2007-03-16 | 2011-09-06 | Google Inc. | Registering an event |
JP4413941B2 (en) * | 2007-03-22 | 2010-02-10 | 株式会社東芝 | Information processing device |
US8805346B1 (en) | 2007-04-13 | 2014-08-12 | At&T Mobility Ii Llc | Caller information retrieval system for unavailable calls |
US20090017802A1 (en) * | 2007-04-13 | 2009-01-15 | At&T Mobility Ii Llc | Undelivered Call Indicator |
JP5088080B2 (en) * | 2007-10-04 | 2012-12-05 | ソニー株式会社 | Electronic device and abnormal state display method |
US20090210822A1 (en) * | 2008-02-18 | 2009-08-20 | Microsoft Corporation | Locating meeting users |
US20090210882A1 (en) * | 2008-02-18 | 2009-08-20 | International Business Machines Corporation | System and methods for asynchronously updating interdependent tasks provided by disparate applications in a multi-task environment |
US7860900B2 (en) * | 2008-02-25 | 2010-12-28 | Microsoft Corporation | Consistently signaling state changes |
US7899798B2 (en) * | 2008-02-25 | 2011-03-01 | Microsoft Corporation | Observing and reporting changes in complex software dependencies |
US8832122B2 (en) * | 2008-09-30 | 2014-09-09 | Apple Inc. | Media list management |
US8411046B2 (en) | 2008-10-23 | 2013-04-02 | Microsoft Corporation | Column organization of content |
US20100107100A1 (en) | 2008-10-23 | 2010-04-29 | Schneekloth Jason S | Mobile Device Style Abstraction |
US8628015B2 (en) * | 2008-10-31 | 2014-01-14 | Hand Held Products, Inc. | Indicia reading terminal including frame quality evaluation processing |
US8175653B2 (en) | 2009-03-30 | 2012-05-08 | Microsoft Corporation | Chromeless user interface |
US8238876B2 (en) | 2009-03-30 | 2012-08-07 | Microsoft Corporation | Notifications |
US8836648B2 (en) | 2009-05-27 | 2014-09-16 | Microsoft Corporation | Touch pull-in gesture |
JP4878060B2 (en) * | 2009-11-16 | 2012-02-15 | シャープ株式会社 | Network system and management method |
US20110153728A1 (en) * | 2009-12-17 | 2011-06-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Synchronization of sporadic web poll traffic |
US8566653B2 (en) * | 2009-12-22 | 2013-10-22 | At&T Intellectual Property I, L.P. | Infrastructure for rapid service deployment |
US20110185396A1 (en) * | 2010-01-26 | 2011-07-28 | Ntt Docomo, Inc. | Information-processing apparatus, information-processing method, and computer-readable storage medium |
JP5793869B2 (en) * | 2010-03-05 | 2015-10-14 | 株式会社リコー | Transmission management system, transmission management method, and transmission management program |
JP5625462B2 (en) * | 2010-04-16 | 2014-11-19 | 船井電機株式会社 | Mobile information display terminal |
US9081633B2 (en) * | 2010-05-24 | 2015-07-14 | Microsoft Technology Licensing, Llc | Remote application connection sharing |
US20120066694A1 (en) | 2010-09-10 | 2012-03-15 | International Business Machines Corporation | Event overflow handling by coalescing and updating previously-queued event notification |
US8694625B2 (en) * | 2010-09-10 | 2014-04-08 | International Business Machines Corporation | Selective registration for remote event notifications in processing node clusters |
US8984119B2 (en) | 2010-11-05 | 2015-03-17 | International Business Machines Corporation | Changing an event identifier of a transient event in an event notification system |
US8667126B2 (en) | 2010-12-03 | 2014-03-04 | International Business Machines Corporation | Dynamic rate heartbeating for inter-node status updating |
US8984120B2 (en) * | 2010-12-16 | 2015-03-17 | International Business Machines Corporation | Determining an unexpected disconnect event constraint within a text exchange session |
US20120159383A1 (en) | 2010-12-20 | 2012-06-21 | Microsoft Corporation | Customization of an immersive environment |
US20120159395A1 (en) | 2010-12-20 | 2012-06-21 | Microsoft Corporation | Application-launching interface for multiple modes |
US8612874B2 (en) | 2010-12-23 | 2013-12-17 | Microsoft Corporation | Presenting an application change through a tile |
US8689123B2 (en) | 2010-12-23 | 2014-04-01 | Microsoft Corporation | Application reporting in an application-selectable user interface |
US9423951B2 (en) | 2010-12-31 | 2016-08-23 | Microsoft Technology Licensing, Llc | Content-based snap point |
WO2012102727A1 (en) * | 2011-01-28 | 2012-08-02 | Hewlett-Packard Development Company, L. P. | Distributing information |
US9383917B2 (en) | 2011-03-28 | 2016-07-05 | Microsoft Technology Licensing, Llc | Predictive tiling |
US8634330B2 (en) | 2011-04-04 | 2014-01-21 | International Business Machines Corporation | Inter-cluster communications technique for event and health status communications |
US9158445B2 (en) | 2011-05-27 | 2015-10-13 | Microsoft Technology Licensing, Llc | Managing an immersive interface in a multi-application immersive environment |
US9104307B2 (en) | 2011-05-27 | 2015-08-11 | Microsoft Technology Licensing, Llc | Multi-application environment |
US9104440B2 (en) | 2011-05-27 | 2015-08-11 | Microsoft Technology Licensing, Llc | Multi-application environment |
US8893033B2 (en) | 2011-05-27 | 2014-11-18 | Microsoft Corporation | Application notifications |
US9658766B2 (en) | 2011-05-27 | 2017-05-23 | Microsoft Technology Licensing, Llc | Edge gesture |
US20120304132A1 (en) | 2011-05-27 | 2012-11-29 | Chaitanya Dev Sareen | Switching back to a previously-interacted-with application |
US9146656B1 (en) * | 2011-06-27 | 2015-09-29 | Google Inc. | Notifications user interface |
US8687023B2 (en) | 2011-08-02 | 2014-04-01 | Microsoft Corporation | Cross-slide gesture to select and rearrange |
US10044678B2 (en) | 2011-08-31 | 2018-08-07 | At&T Intellectual Property I, L.P. | Methods and apparatus to configure virtual private mobile networks with virtual private networks |
US20130057587A1 (en) | 2011-09-01 | 2013-03-07 | Microsoft Corporation | Arranging tiles |
US8922575B2 (en) | 2011-09-09 | 2014-12-30 | Microsoft Corporation | Tile cache |
US10353566B2 (en) | 2011-09-09 | 2019-07-16 | Microsoft Technology Licensing, Llc | Semantic zoom animations |
US9557909B2 (en) | 2011-09-09 | 2017-01-31 | Microsoft Technology Licensing, Llc | Semantic zoom linguistic helpers |
US8933952B2 (en) | 2011-09-10 | 2015-01-13 | Microsoft Corporation | Pre-rendering new content for an application-selectable user interface |
US9146670B2 (en) | 2011-09-10 | 2015-09-29 | Microsoft Technology Licensing, Llc | Progressively indicating new content in an application-selectable user interface |
US9244802B2 (en) | 2011-09-10 | 2016-01-26 | Microsoft Technology Licensing, Llc | Resource user interface |
WO2013040674A1 (en) * | 2011-09-23 | 2013-03-28 | Research In Motion Limited | System and method for managing transient notifications using sensors |
JP5913921B2 (en) * | 2011-11-11 | 2016-04-27 | シャープ株式会社 | Information terminal, control method therefor, control program, and computer-readable recording medium |
US9223472B2 (en) | 2011-12-22 | 2015-12-29 | Microsoft Technology Licensing, Llc | Closing applications |
US9128605B2 (en) | 2012-02-16 | 2015-09-08 | Microsoft Technology Licensing, Llc | Thumbnail-image selection of applications |
US10044648B2 (en) | 2012-09-09 | 2018-08-07 | Jianping He | Messaging and updating services over the air from application servers to applications in mobile devices |
US9450952B2 (en) | 2013-05-29 | 2016-09-20 | Microsoft Technology Licensing, Llc | Live tiles without application-code execution |
US8819268B1 (en) * | 2013-06-19 | 2014-08-26 | Google Inc. | Systems and methods for notification of device mirroring |
US9450904B2 (en) | 2013-07-15 | 2016-09-20 | Dropbox, Inc. | Coordinated notifications across multiple channels |
US20150095071A1 (en) | 2013-09-29 | 2015-04-02 | Donan Engineering Co., Inc. | Systems and Methods for Identifying a Subrogation Opportunity for a Potential Subrogation Claim |
CN104333644B (en) * | 2013-10-18 | 2017-02-08 | 广州三星通信技术研究有限公司 | Mobile communication terminal and method thereof for updating state of message |
US20150160951A1 (en) * | 2013-12-06 | 2015-06-11 | Board Of Regents Of The University Of Texas System | Remote launch of application on mobile device |
WO2015149347A1 (en) | 2014-04-04 | 2015-10-08 | Microsoft Technology Licensing, Llc | Expandable application representation |
EP3129873A1 (en) | 2014-04-09 | 2017-02-15 | Convida Wireless, LLC | Service enabler function |
KR102107275B1 (en) | 2014-04-10 | 2020-05-06 | 마이크로소프트 테크놀로지 라이센싱, 엘엘씨 | Collapsible shell cover for computing device |
EP3129847A4 (en) | 2014-04-10 | 2017-04-19 | Microsoft Technology Licensing, LLC | Slider cover for computing device |
US10678412B2 (en) | 2014-07-31 | 2020-06-09 | Microsoft Technology Licensing, Llc | Dynamic joint dividers for application windows |
US10592080B2 (en) | 2014-07-31 | 2020-03-17 | Microsoft Technology Licensing, Llc | Assisted presentation of application windows |
US10254942B2 (en) | 2014-07-31 | 2019-04-09 | Microsoft Technology Licensing, Llc | Adaptive sizing and positioning of application windows |
US10642365B2 (en) | 2014-09-09 | 2020-05-05 | Microsoft Technology Licensing, Llc | Parametric inertia and APIs |
CN106662891B (en) | 2014-10-30 | 2019-10-11 | 微软技术许可有限责任公司 | Multi-configuration input equipment |
US10146473B2 (en) * | 2016-05-10 | 2018-12-04 | Ge Aviation Systems Llc | Systems and methods of subject state change notification |
US10156877B2 (en) | 2016-10-01 | 2018-12-18 | Intel Corporation | Enhanced power management for support of priority system events |
US9959010B1 (en) * | 2016-12-23 | 2018-05-01 | Beijing Kingsoft Internet Security Software Co., Ltd. | Method for displaying information, and terminal equipment |
CN107222632A (en) * | 2017-06-23 | 2017-09-29 | 北京金山安全软件有限公司 | Instant messaging method and device |
CN111064957B (en) | 2018-10-17 | 2021-03-23 | 杭州海康威视数字技术股份有限公司 | Equipment state monitoring method and device |
US10848500B2 (en) * | 2018-10-24 | 2020-11-24 | Jamf Software, Llc | Systems and methods for group-based mobile device management |
CN113055415A (en) * | 2019-12-26 | 2021-06-29 | 阿里巴巴集团控股有限公司 | Service providing method, service consuming method, device and equipment |
Family Cites Families (165)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4058672A (en) | 1976-11-10 | 1977-11-15 | International Telephone And Telegraph Corporation | Packet-switched data communications system |
US4789962A (en) | 1984-10-31 | 1988-12-06 | International Business Machines Corporation | Methods of displaying help information nearest to an operation point at which the help information is requested |
US4780821A (en) | 1986-07-29 | 1988-10-25 | International Business Machines Corp. | Method for multiple programs management within a network having a server computer and a plurality of remote computers |
US4945475A (en) | 1986-10-30 | 1990-07-31 | Apple Computer, Inc. | Hierarchical file system to provide cataloging and retrieval of data |
JPS63286941A (en) | 1987-05-20 | 1988-11-24 | Hitachi Ltd | File system managing system |
US5058000A (en) | 1987-06-30 | 1991-10-15 | Prime Computer, Inc. | System for accessing remote heterogeneous database including formatting retrieved data into applications program format |
US5307494A (en) | 1987-08-05 | 1994-04-26 | Fuji Xerox Co., Ltd. | File name length augmentation method |
US5179703A (en) | 1987-11-17 | 1993-01-12 | International Business Machines Corporation | Dynamically adaptive environment for computer programs |
US5129088A (en) | 1987-11-30 | 1992-07-07 | International Business Machines Corporation | Data processing method to create virtual disks from non-contiguous groups of logically contiguous addressable blocks of direct access storage device |
US4945476A (en) | 1988-02-26 | 1990-07-31 | Elsevier Science Publishing Company, Inc. | Interactive system and method for creating and editing a knowledge base for use as a computerized aid to the cognitive process of diagnosis |
US4999766A (en) | 1988-06-13 | 1991-03-12 | International Business Machines Corporation | Managing host to workstation file transfer |
JPH02165241A (en) | 1988-12-19 | 1990-06-26 | Toshiba Corp | File access system |
CA1323448C (en) | 1989-02-24 | 1993-10-19 | Terrence C. Miller | Method and apparatus for translucent file system |
US5243697A (en) | 1989-03-15 | 1993-09-07 | Sun Microsystems, Inc. | Method and apparatus for selecting button functions and retaining selected options on a display |
US5157768A (en) | 1989-03-15 | 1992-10-20 | Sun Microsystems, Inc. | Method and apparatus for displaying context sensitive help information on a display |
US5083264A (en) | 1989-04-24 | 1992-01-21 | Xerox Corporation | Process and apparatus for saving and restoring critical files on the disk memory of an electrostatographic reproduction machine |
CA2014799A1 (en) | 1989-05-08 | 1990-11-08 | John W. Whisler | System and method for reading and writing disks formatted for an operating system foreign to the host computer |
US5291595A (en) | 1989-05-22 | 1994-03-01 | Martins Augusto B | Batch/application program processing |
US5485606A (en) | 1989-07-10 | 1996-01-16 | Conner Peripherals, Inc. | System and method for storing and retrieving files for archival purposes |
US5363487A (en) | 1989-08-29 | 1994-11-08 | Microsoft Corporation | Method and system for dynamic volume tracking in an installable file system |
US5371885A (en) | 1989-08-29 | 1994-12-06 | Microsoft Corporation | High performance file system |
US5247658A (en) | 1989-10-31 | 1993-09-21 | Microsoft Corporation | Method and system for traversing linked list record based upon write-once predetermined bit value of secondary pointers |
US5347628A (en) | 1990-01-18 | 1994-09-13 | International Business Machines Corporation | Method of graphically accessing electronic data |
US5317733A (en) | 1990-01-26 | 1994-05-31 | Cisgem Technologies, Inc. | Office automation system for data base management and forms generation |
US5202982A (en) | 1990-03-27 | 1993-04-13 | Sun Microsystems, Inc. | Method and apparatus for the naming of database component files to avoid duplication of files |
US5249300A (en) | 1990-04-27 | 1993-09-28 | Bachman Information Systems, Inc. | System and method of constructing models of complex business transactions using entity-set variables for ordered sets of references to user data |
JPH0454541A (en) | 1990-06-21 | 1992-02-21 | Fujitsu Ltd | Processing system for generation of file name |
DE69126391T2 (en) | 1990-09-12 | 1997-10-30 | Toshiba Kawasaki Kk | Method for generating functions by using symbols |
US5367671A (en) | 1990-09-25 | 1994-11-22 | International Business Machines Corp. | System for accessing extended object attribute (EA) data through file name or EA handle linkages in path tables |
US5204947A (en) | 1990-10-31 | 1993-04-20 | International Business Machines Corporation | Application independent (open) hypermedia enablement services |
US5297249A (en) | 1990-10-31 | 1994-03-22 | International Business Machines Corporation | Hypermedia link marker abstract and search services |
US5241545A (en) | 1990-11-14 | 1993-08-31 | Motorola, Inc. | Apparatus and method for recovering a time-varying signal using multiple sampling points |
CA2067650C (en) | 1991-07-24 | 1996-10-22 | Eric Jonathan Bauer | Method and apparatus for operating a computer-based file system |
CA2067633C (en) | 1991-07-24 | 1996-10-01 | Eric Jonathan Bauer | Method and apparatus for accessing a computer-based file system |
US5329427A (en) | 1991-08-02 | 1994-07-12 | Tusk, Incorporated | Modular computer system having an improved docking assembly |
US5359725A (en) | 1991-10-15 | 1994-10-25 | Time Warner Interactive Group, Inc. | Method of creating CD-ROM image of files of different format with proper directories to be read by respective operating systems |
US6347051B2 (en) | 1991-11-26 | 2002-02-12 | Hitachi, Ltd. | Storage device employing a flash memory |
US5333266A (en) | 1992-03-27 | 1994-07-26 | International Business Machines Corporation | Method and apparatus for message handling in computer systems |
US5390328A (en) * | 1992-03-30 | 1995-02-14 | International Business Machines Corporation | Data processing system and method for providing notification in a central processor of state changes for shared data structure on external storage |
US5359724A (en) | 1992-03-30 | 1994-10-25 | Arbor Software Corporation | Method and apparatus for storing and retrieving multi-dimensional data in computer memory |
US5434974A (en) | 1992-03-30 | 1995-07-18 | International Business Machines Corporation | Name resolution for a multisystem network |
US5392390A (en) | 1992-04-10 | 1995-02-21 | Intellilink Corp. | Method for mapping, translating, and dynamically reconciling data between disparate computer platforms |
JPH0619771A (en) | 1992-04-20 | 1994-01-28 | Internatl Business Mach Corp <Ibm> | File management system of shared file by different kinds of clients |
US5421001A (en) | 1992-05-01 | 1995-05-30 | Wang Laboratories, Inc. | Computer method and apparatus for a table driven file interface |
US5355497A (en) | 1992-06-10 | 1994-10-11 | Physiotronics Corporation | File directory structure generator and retrevial tool with document locator module mapping the directory structure of files to a real world hierarchical file structure |
JP3328321B2 (en) | 1992-06-22 | 2002-09-24 | 株式会社日立製作所 | Semiconductor storage device |
US5745902A (en) | 1992-07-06 | 1998-04-28 | Microsoft Corporation | Method and system for accessing a file using file names having different file name formats |
US5627996A (en) | 1992-08-19 | 1997-05-06 | At&T | Method and apparatus for accessing the same computer file using different file name formats |
US5596755A (en) | 1992-11-03 | 1997-01-21 | Microsoft Corporation | Mechanism for using common code to handle hardware interrupts in multiple processor modes |
EP0820008A3 (en) | 1992-12-01 | 2006-05-24 | Microsoft Corporation | A method and system for in-place interaction with embedded objects |
US5666530A (en) | 1992-12-02 | 1997-09-09 | Compaq Computer Corporation | System for automatic synchronization of common file between portable computer and host computer via communication channel selected from a plurality of usable channels there between |
JP2856621B2 (en) | 1993-02-24 | 1999-02-10 | インターナショナル・ビジネス・マシーンズ・コーポレイション | Batch erase nonvolatile memory and semiconductor disk device using the same |
JP3078946B2 (en) | 1993-03-11 | 2000-08-21 | インターナショナル・ビジネス・マシーンズ・コーポレ−ション | Managing method of batch erase nonvolatile memory and semiconductor disk device |
GB2276520A (en) | 1993-03-23 | 1994-09-28 | Us West Advanced Tech Inc | Computer interface method and system |
JPH06290096A (en) | 1993-03-31 | 1994-10-18 | Matsushita Electric Ind Co Ltd | Pass name solving device |
CA2120461C (en) | 1993-04-01 | 2009-09-22 | Aaron R. Reynolds | Common name space for long and short filenames |
JPH06324928A (en) | 1993-05-14 | 1994-11-25 | Mitsubishi Electric Corp | Log generating device, device for arbitrating versions different in file and device for arbitrating version different in computer file being at different places |
WO1995008809A2 (en) | 1993-09-24 | 1995-03-30 | Oracle Corporation | Method and apparatus for data replication |
US5729687A (en) | 1993-12-20 | 1998-03-17 | Intel Corporation | System for sending differences between joining meeting information and public meeting information between participants in computer conference upon comparing annotations of joining and public meeting information |
US5483652A (en) | 1994-01-24 | 1996-01-09 | Digital Equipment Corporation | Mechanism for locating without search discrete application resources known by common name only in a distributed network computing environment |
AU3372095A (en) | 1994-08-24 | 1996-03-14 | Arcada Software, Inc. | Application program interface (api) for a medium changer |
US5805886A (en) | 1994-09-26 | 1998-09-08 | Intel Corporation | Method for notifying client applications of events in a shared application in a computer system |
US5805830A (en) | 1994-09-30 | 1998-09-08 | Intel Corporation | Method and apparatus for managing communications with selective subsets of conference participants |
US5903752A (en) | 1994-10-13 | 1999-05-11 | Intel Corporation | Method and apparatus for embedding a real-time multi-tasking kernel in a non-real-time operating system |
US5721922A (en) | 1994-10-13 | 1998-02-24 | Intel Corporation | Embedding a real-time multi-tasking kernel in a non-real-time operating system |
JPH08129536A (en) * | 1994-10-28 | 1996-05-21 | Oki Electric Ind Co Ltd | Event processing system |
US5745752A (en) | 1994-12-13 | 1998-04-28 | Microsoft Corporation | Dual namespace client having long and short filenames |
US5684990A (en) | 1995-01-11 | 1997-11-04 | Puma Technology, Inc. | Synchronization of disparate databases |
US5758354A (en) | 1995-04-28 | 1998-05-26 | Intel Corporation | Application independent e-mail synchronization |
US5819275A (en) | 1995-06-07 | 1998-10-06 | Trusted Information Systems, Inc. | System and method for superimposing attributes on hierarchically organized file systems |
US5991771A (en) | 1995-07-20 | 1999-11-23 | Novell, Inc. | Transaction synchronization in a disconnectable computer and network |
US5664228A (en) | 1995-08-09 | 1997-09-02 | Microsoft Corporation | Portable information device and system and method for downloading executable instructions from a computer to the portable information device |
JP3188713B2 (en) | 1995-08-14 | 2001-07-16 | インターナシヨナル・ビジネス・マシーンズ・コーポレーシヨン | Improved message queuing distributed system for mail systems |
US5647002A (en) | 1995-09-01 | 1997-07-08 | Lucent Technologies Inc. | Synchronization of mailboxes of different types |
US5630081A (en) | 1995-09-07 | 1997-05-13 | Puma Technology, Inc. | Connection resource manager displaying link-status information using a traffic light iconic representation |
US5884323A (en) | 1995-10-13 | 1999-03-16 | 3Com Corporation | Extendible method and apparatus for synchronizing files on two different computer systems |
US5727202A (en) | 1995-10-18 | 1998-03-10 | Palm Computing, Inc. | Method and apparatus for synchronizing information on two different computer systems |
US5867641A (en) | 1995-10-27 | 1999-02-02 | Scm Microsystems (U.S.) Inc. | Flash translation layer cleanup system and method |
US6014724A (en) | 1995-10-27 | 2000-01-11 | Scm Microsystems (U.S.) Inc. | Flash translation layer block indication map revision system and method |
US5799305A (en) | 1995-11-02 | 1998-08-25 | Informix Software, Inc. | Method of commitment in a distributed database transaction |
US5832218A (en) | 1995-12-14 | 1998-11-03 | International Business Machines Corporation | Client/server electronic mail system for providng off-line client utilization and seamless server resynchronization |
US5799168A (en) | 1996-01-05 | 1998-08-25 | M-Systems Flash Disk Pioneers Ltd. | Standardized flash controller |
US5806074A (en) | 1996-03-19 | 1998-09-08 | Oracle Corporation | Configurable conflict resolution in a computer implemented distributed database |
US5761675A (en) | 1996-03-19 | 1998-06-02 | Symantec Corporation | Diagnosis and repair of defective long filenames |
DE69720857T2 (en) * | 1996-05-31 | 2004-02-05 | Hewlett-Packard Co. (N.D.Ges.D.Staates Delaware), Palo Alto | Systems and methods for operating a network management station |
US5787262A (en) | 1996-06-26 | 1998-07-28 | Microsoft Corporation | System and method for distributed conflict resolution between data objects replicated across a computer network |
US5812793A (en) | 1996-06-26 | 1998-09-22 | Microsoft Corporation | System and method for asynchronous store and forward data replication |
US5930350A (en) | 1996-06-27 | 1999-07-27 | Mci Communications Corporation | System, method and computer program for automated speed dialing |
US5812773A (en) | 1996-07-12 | 1998-09-22 | Microsoft Corporation | System and method for the distribution of hierarchically structured data |
KR100260028B1 (en) | 1996-08-13 | 2000-06-15 | 윤종용 | Data recovery method in a file system |
US6016478A (en) | 1996-08-13 | 2000-01-18 | Starfish Software, Inc. | Scheduling system with methods for peer-to-peer scheduling of remote users |
US5754848A (en) | 1996-09-11 | 1998-05-19 | Hewlett-Packard Co. | Apparatus and method for disaster recovery of an operating system utilizing long file and directory names |
US5767854A (en) | 1996-09-27 | 1998-06-16 | Anwar; Mohammed S. | Multidimensional data display and manipulation system and methods for using same |
US5765169A (en) | 1996-09-30 | 1998-06-09 | International Business Machines Corporation | Method and apparatus for converting long file names to short file names |
US5884325A (en) | 1996-10-09 | 1999-03-16 | Oracle Corporation | System for synchronizing shared data between computers |
US5757616A (en) | 1996-10-31 | 1998-05-26 | Hewlett-Packard Company | Physical security system for portable computer |
US5924094A (en) | 1996-11-01 | 1999-07-13 | Current Network Technologies Corporation | Independent distributed database system |
US5991536A (en) * | 1996-11-12 | 1999-11-23 | International Business Machines Corporation | Object-oriented tool for registering objects for observation and causing notifications to be made in the event changes are made to an object which is being observed |
US6405218B1 (en) | 1996-11-13 | 2002-06-11 | Pumatech, Inc. | Synchronizing databases |
US5745418A (en) | 1996-11-25 | 1998-04-28 | Macronix International Co., Ltd. | Flash memory mass storage system |
US5956473A (en) | 1996-11-25 | 1999-09-21 | Macronix International Co., Ltd. | Method and system for managing a flash memory mass storage system |
US5878408A (en) | 1996-12-06 | 1999-03-02 | International Business Machines Corporation | Data management system and process |
US5826265A (en) | 1996-12-06 | 1998-10-20 | International Business Machines Corporation | Data management system having shared libraries |
US5920873A (en) | 1996-12-06 | 1999-07-06 | International Business Machines Corporation | Data management control system for file and database |
US6018761A (en) | 1996-12-11 | 2000-01-25 | The Robert G. Uomini And Louise B. Bidwell Trust | System for adding to electronic mail messages information obtained from sources external to the electronic mail transport process |
US5926501A (en) | 1996-12-12 | 1999-07-20 | Motorola, Inc. | Method and apparatus for dynamic channel configuration |
US5930268A (en) | 1996-12-20 | 1999-07-27 | Motorola, Inc. | Transceiver and associated method for surviving fades |
US6279069B1 (en) | 1996-12-26 | 2001-08-21 | Intel Corporation | Interface for flash EEPROM memory arrays |
US5812749A (en) | 1996-12-27 | 1998-09-22 | Mci Communication Corporation | Method of and system for testing network time protocol client accuracy |
US6035379A (en) | 1997-01-09 | 2000-03-07 | Microsoft Corporation | Transaction processing for user data employing both logging and shadow copying |
US5887198A (en) | 1997-04-07 | 1999-03-23 | The United States Of America As Represented By The Secretary Of The Navy | Programmable stand-alone drive apparatus for interfacing a host computer with PCMCIA memory cards having multiple formats |
US5961590A (en) | 1997-04-11 | 1999-10-05 | Roampage, Inc. | System and method for synchronizing electronic mail between a client site and a central site |
US5884328A (en) | 1997-08-29 | 1999-03-16 | Tandem Computers, Inc. | System and method for sychronizing a large database and its replica |
US5991778A (en) | 1997-09-30 | 1999-11-23 | Stratfor Systems, Inc. | Method and apparatus for real-time secure file deletion |
US6018571A (en) | 1997-09-30 | 2000-01-25 | Mitel Corporation | System for interactive control of a computer and telephone |
US6070174A (en) | 1997-09-30 | 2000-05-30 | Infraworks Corporation | Method and apparatus for real-time secure file deletion |
US5924096A (en) | 1997-10-15 | 1999-07-13 | Novell, Inc. | Distributed database using indexed into tags to tracks events according to type, update cache, create virtual update log on demand |
US5937425A (en) | 1997-10-16 | 1999-08-10 | M-Systems Flash Disk Pioneers Ltd. | Flash file system optimized for page-mode flash technologies |
CA2307635C (en) * | 1997-11-05 | 2004-07-06 | Microsoft Corporation | Notification scheduling system on a mobile device |
US6034621A (en) | 1997-11-18 | 2000-03-07 | Lucent Technologies, Inc. | Wireless remote synchronization of data between PC and PDA |
US5960406A (en) | 1998-01-22 | 1999-09-28 | Ecal, Corp. | Scheduling system for use between users on the web |
AU2787899A (en) * | 1998-02-26 | 1999-09-15 | Sun Microsystems, Inc. | Method and system for facilitating access to a lookup service |
US6098093A (en) * | 1998-03-19 | 2000-08-01 | International Business Machines Corp. | Maintaining sessions in a clustered server environment |
US6611877B2 (en) | 1998-06-30 | 2003-08-26 | Sun Microsystems, Inc. | System and method for aggregating registration of entities for notifications of events |
US6741994B1 (en) | 1998-07-27 | 2004-05-25 | Hewlett-Packard Development Company, L.P. | Method and automatic organization of data |
US6269254B1 (en) | 1998-09-28 | 2001-07-31 | Motorola, Inc. | Radio communications device and method with API between user application program and telephony program and method |
US6393485B1 (en) * | 1998-10-27 | 2002-05-21 | International Business Machines Corporation | Method and apparatus for managing clustered computer systems |
US6922708B1 (en) * | 1999-02-18 | 2005-07-26 | Oracle International Corporation | File system that supports transactions |
US7950017B1 (en) * | 1999-04-23 | 2011-05-24 | Avaya Inc. | Apparatus and method for forwarding messages between two applications |
US6915457B1 (en) * | 1999-04-23 | 2005-07-05 | Nortel Networks Limited | Apparatus and method for monitoring messages forwarded between applications |
US6925513B1 (en) | 1999-05-04 | 2005-08-02 | Apple Computer, Inc. | USB device notification |
US6678830B1 (en) * | 1999-07-02 | 2004-01-13 | Hewlett-Packard Development Company, L.P. | Method and apparatus for an ACPI compliant keyboard sleep key |
US6442565B1 (en) * | 1999-08-13 | 2002-08-27 | Hiddenmind Technology, Inc. | System and method for transmitting data content in a computer network |
US6141564A (en) | 1999-09-30 | 2000-10-31 | Motorola, Inc. | Method of sharing a SIM card between two masters |
US6631363B1 (en) | 1999-10-11 | 2003-10-07 | I2 Technologies Us, Inc. | Rules-based notification system |
US7305475B2 (en) | 1999-10-12 | 2007-12-04 | Webmd Health | System and method for enabling a client application to operate offline from a server |
US7003571B1 (en) | 2000-01-31 | 2006-02-21 | Telecommunication Systems Corporation Of Maryland | System and method for re-directing requests from browsers for communication over non-IP based networks |
US6584185B1 (en) | 2000-01-31 | 2003-06-24 | Microsoft Corporation | Telephone abstraction layer and system in a computer telephony system |
US20020046299A1 (en) * | 2000-02-09 | 2002-04-18 | Internet2Anywhere, Ltd. | Method and system for location independent and platform independent network signaling and action initiating |
CN100594701C (en) * | 2000-03-16 | 2010-03-17 | 微软公司 | Notification system |
US7030837B1 (en) * | 2000-04-24 | 2006-04-18 | Microsoft Corporation | Auxiliary display unit for a computer system |
US6928300B1 (en) * | 2000-11-09 | 2005-08-09 | Palmsource, Inc. | Method and apparatus for automated flexible configuring of notifications and activation |
US20020105548A1 (en) * | 2000-12-12 | 2002-08-08 | Richard Hayton | Methods and apparatus for creating a user interface using property paths |
US6874094B2 (en) * | 2000-12-19 | 2005-03-29 | Microsoft Corporation | Method for locking user input elements for a small computer device by ignoring input signals if a locking signal is generated by a calendar-type application program |
US7299257B2 (en) * | 2001-02-06 | 2007-11-20 | Lucent Technologies Inc. | Apparatus and method for use in collaboration services |
US6826762B2 (en) | 2001-02-16 | 2004-11-30 | Microsoft Corporation | Radio interface layer in a cell phone with a set of APIs having a hardware-independent proxy layer and a hardware-specific driver layer |
US7472396B2 (en) * | 2001-05-18 | 2008-12-30 | Qualcomm Incorporated | Extensible event notification mechanism |
US20020178077A1 (en) * | 2001-05-25 | 2002-11-28 | Katz Steven Bruce | Method for automatically invoking a software module in response to an internal or external event affecting the procurement of an item |
JP2003044320A (en) * | 2001-07-31 | 2003-02-14 | Pfu Ltd | Educational system |
US6954781B2 (en) | 2001-08-01 | 2005-10-11 | International Business Machines Corporation | Messaging system for directing a server to convert voice message into text and appending a converted text message to another converted text message |
US7171671B2 (en) | 2001-08-23 | 2007-01-30 | Microsoft Corporation | Method and system for providing state change notifications in device drivers |
US20040066920A1 (en) | 2001-08-31 | 2004-04-08 | Vandermeijden Tom R. | Method and apparatus for automatically populating a contact database in a mobile communication device |
US6993327B2 (en) | 2001-10-29 | 2006-01-31 | Motorola, Inc. | Multicast distribution of presence information for an instant messaging system |
US6909910B2 (en) | 2002-02-01 | 2005-06-21 | Microsoft Corporation | Method and system for managing changes to a contact database |
US7657765B2 (en) * | 2002-02-19 | 2010-02-02 | Hewlett-Packard Development Company, L.P. | Power saving features for computing systems |
JP4091792B2 (en) * | 2002-05-17 | 2008-05-28 | 株式会社エヌ・ティ・ティ・ドコモ | Electronic device, event providing method, program, and recording medium |
GB0223498D0 (en) * | 2002-10-09 | 2002-11-13 | Nokia Corp | Provision of information regarding a mobile station |
US7269433B2 (en) * | 2002-11-05 | 2007-09-11 | Microsoft Corporation | Scheduling of synchronization operation on a mobile device based on predetermined subset of user actions |
US7809384B2 (en) * | 2002-11-05 | 2010-10-05 | Microsoft Corporation | User-input scheduling of synchronization operation on a mobile device based on user activity |
US7240228B2 (en) * | 2003-05-05 | 2007-07-03 | Microsoft Corporation | Method and system for standby auxiliary processing of information for a computing device |
US7103785B2 (en) * | 2003-05-30 | 2006-09-05 | Hewlett-Packard Development Company, L.P. | Method and apparatus for power management event wake up |
US7644376B2 (en) | 2003-10-23 | 2010-01-05 | Microsoft Corporation | Flexible architecture for notifying applications of state changes |
JP4297934B2 (en) | 2006-10-24 | 2009-07-15 | 三菱電機株式会社 | Vehicle communication device |
US20160088046A1 (en) * | 2014-09-18 | 2016-03-24 | Multipop Llc | Real time content management system |
US9633622B2 (en) * | 2014-12-18 | 2017-04-25 | Intel Corporation | Multi-user sensor-based interactions |
-
2004
- 2004-06-22 US US10/873,881 patent/US7644376B2/en active Active
- 2004-10-06 EP EP04023852A patent/EP1679596A3/en not_active Ceased
- 2004-10-22 CN CN200410087701XA patent/CN1617501B/en active Active
- 2004-10-22 KR KR1020040084927A patent/KR100920850B1/en active IP Right Grant
- 2004-10-22 CN CN201110222798.0A patent/CN102291446B/en active Active
- 2004-10-25 JP JP2004310058A patent/JP4790245B2/en not_active Expired - Fee Related
-
2009
- 2009-11-23 US US12/624,038 patent/US8990695B2/en active Active
-
2015
- 2015-01-29 US US14/609,134 patent/US10169111B2/en active Active
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20150106474A1 (en) * | 2013-10-16 | 2015-04-16 | Ford Global Technologies, Llc | Method and Apparatus for Handling Application Triggering Events |
US9854061B2 (en) * | 2013-10-16 | 2017-12-26 | Ford Global Technologies, Llc | Method and apparatus for handling application triggering events |
US10715631B2 (en) | 2013-10-16 | 2020-07-14 | Ford Global Technologies, Llc | Method and apparatus for handling application triggering events |
US20190073347A1 (en) * | 2017-09-01 | 2019-03-07 | Google Inc. | Lockscreen note-taking |
US20190095259A1 (en) * | 2017-09-26 | 2019-03-28 | Kyocera Document Solutions Inc. | Electronic Device and Log Application |
Also Published As
Publication number | Publication date |
---|---|
US8990695B2 (en) | 2015-03-24 |
KR100920850B1 (en) | 2009-10-09 |
US20050091219A1 (en) | 2005-04-28 |
EP1679596A2 (en) | 2006-07-12 |
US20100077310A1 (en) | 2010-03-25 |
US10169111B2 (en) | 2019-01-01 |
EP1679596A3 (en) | 2007-08-22 |
CN1617501B (en) | 2011-09-14 |
CN102291446A (en) | 2011-12-21 |
CN102291446B (en) | 2014-11-26 |
KR20050039665A (en) | 2005-04-29 |
JP2005129067A (en) | 2005-05-19 |
US7644376B2 (en) | 2010-01-05 |
CN1617501A (en) | 2005-05-18 |
JP4790245B2 (en) | 2011-10-12 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US10169111B2 (en) | Flexible architecture for notifying applications of state changes | |
US8271889B1 (en) | Automatically updated user interfaces for a mobile device | |
US8200626B1 (en) | Mobile device file management | |
US8868613B2 (en) | Updating data on a remote device | |
US7974194B2 (en) | Optimizing data traffic and power consumption in mobile unified communication applications | |
US8214619B1 (en) | Memory allocation in a mobile device | |
KR101109238B1 (en) | Rapidly obtaining a subset of message data from a server for filtering | |
US20050216563A1 (en) | System and method for exposing instant messenger presence information on a mobile device | |
US20060073820A1 (en) | Method and apparatus for remote control and updating of wireless mobile devices | |
US20060218029A1 (en) | Smart reminders | |
US20060069727A1 (en) | System and method for synchronizing between an instant messenger client and a central contact store | |
US8041372B1 (en) | Selecting data in a mobile information system | |
US20050003850A1 (en) | Terminal device and program | |
US9055116B2 (en) | Presence system, communication terminal, server and computer program product therefor | |
US8281390B1 (en) | Remotely defining security data for authorization of local application activity | |
US20140342710A1 (en) | Method and apparatus for providing mobile device information through a computing device | |
US20070124514A1 (en) | Storing account information with related data in a common store | |
US8677476B2 (en) | Providing remotely defined security data to a local application extension | |
US9384344B2 (en) | Authorizing local application activity using remotely defined security data |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
MAFP | Maintenance fee payment |
Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Year of fee payment: 4 |