Surety is performing system maintenance this weekend. Electronic date stamps on new Prior Art Database disclosures may be delayed.
Browse Prior Art Database

Filtering notifications from multiple devices

IP.com Disclosure Number: IPCOM000247660D
Publication Date: 2016-Sep-26
Document File: 3 page(s) / 187K

Publishing Venue

The IP.com Prior Art Database


A method of using automatic selection of a primary device and on device filtering of push notifications is proposed. This method can be used to prevent duplicate push notifications from being shown on multiple devices in use by the same user.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 46% of the total text.

Page 01 of 3

Filtering notifications from multiple devices

Disclosed is a method for filtering device push notifications. Push notifications are frequently used to display small snippets of information to users of (primarily mobile) devices. It is not uncommon for users to have multiple devices for example a mobile phone and at least one more of a tablet computer, smart watch, or laptop. The same user can be signed in on all these devices and the same push notifications are delivered to all devices simultaneously. This leads to duplicate notifications for the same information if a user moves between devices.

    This problem has been addressed previously with solutions rely on sending a message back to the server that a notification has been acknowledged and then sending additional information to the devices to remove or change the seen push notifications [1]. For example this can be achieved by sending an additional hidden push notification [2]. An extension to this approach is to allow configuration of a primary device for specific application notifications such that all the notifications from that application will remain unread across all the devices until acknowledged on the primary device [3].

    The drawbacks of these solutions are that the notifications are delivered to all devices and messages must be returned to the server and re-sent to all devices to dismiss notifications. Additionally there is a configuration burden to setting a primary device for particular application notifications. This burden may be reduced by automatic identification of a primary device. One method of using various sources of data and a connection between devices to automatically identify the primary device has been previously disclosed [4].

    Further to that existing solutions have been used to route notifications solely to a preferred device [5]. The disadvantage of sending a notification only to a single device is that some information may be missing from the local history on the device. For example even if the notification is not displayed on the secondary device, because it will be acknowledged on the primary device, it may be added to the history of notifications within an application that may be consulted by the user at some other time.

    The proposed solution is to continue to send push notifications to all devices, but to include metadata within a push notification about which device is the current primary device for that type of notification and therefore should display it. One advantage of this approach is that only one device ever need display the notification. This has improved security and privacy over delivering the notifications to multiple devices, which may be in shared usage within a family, for example. An additional advantage is that an acknowledgement does not need to be sent back to the server from the primary device and subsequent notifications received by all other devices before a push notification is removed from display. This provides a more...