InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Prevention of multiple notifications across multiple devices

IP.com Disclosure Number: IPCOM000241329D
Publication Date: 2015-Apr-17
Document File: 3 page(s) / 67K

Publishing Venue

The IP.com Prior Art Database


The article proposes a solution to the problem faced by those who own multiple mobile devices, such as smart phones, tablets and laptops, all of which are configured to emit event notifications. In such instances a single event is reported across all devices irrespective of their proximity, which may be a cause of frustration to the user. By locally broadcasting (human) inaudible statements of intent, this source of frustration may be removed.

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

Page 01 of 3

Prevention of multiple notifications across multiple devices

It is common to own multiple mobile devices, such as a smart phone, laptop and tablet device. It is equally common that a notification of an email, or other installed application alert, will be repeated across all devices that have the application

installed. This can be a source of great frustration and distraction; proximate devices should not broadcast alerts for the same notification event.

    The proposed system attempts to stop proximate devices from emitting duplicate event notifications for the same event. This is achieved by proximate user devices being able to locally broadcast an inaudible "statement of intent" to notify a human user of an inbound notification, including the notification type and application issuing the notification, prior to notifying a human. Any other devices that are proximate, may detect this "statement of intent" and if they subsequently receive a push notification from an application server that matches that described in the "statement of intent", then the device will not act to notify a human. In this way, devices that are proximate will not emit the same event notification, though a human

will receive a notification from any instantaneous device subsets.

    Consider the scenario where a user has multiple devices, each configured to receive push notifications from the same application. Each device is assumed to have: · Speaker · Microphone
And may optionally also include: · Bluetooth · IR detector/emitter
A subset of these devices are in proximity, and in the example case the subset is also in proximity to a human.

    The general algorithm can be embodied in a number of ways, though it is predominantly the manner in which the"statement of intent" is relayed to proximate devices. We consider that all devices are configured to be in a listening mode, such that they may:
A) Detect a push notification from an application and issue a "statement of intent" to proximate devices
B) Detect and store a statement of intent issued from a proximate device Considering Item A 1. A device detects a push notification. The device subsequently inspects details relating to the content of the push notification; examples of such notifications may be readily found in documentation: · https://developer.apple.com/library/ios/documentation/NetworkingInternet/Conceptu al/RemoteNotificationsPG/Chapters/ApplePushService.html#//apple_ref/doc/uid/TP4 0008194-CH100-SW1 · http://developer.android.com/google/gcm/index.html · https://msdn.microsoft.com/en-us/library/windows/apps/hh913756.aspx
In order to preserve security and privacy, a unique key is formed from the driving application and the user ID, as well as other components such as the email address or title/name of the user, which is encoded using a cryptographic hash

Page 02 of 3

function (http://en.wikipedia.org/wiki/Cryptographic_hash_function). For instance: socialnetwork:user@socialnetwork.com -> sha3 -> e8a807800b...