Browse Prior Art Database

Detection and resolution of notification profile overlaps of proximate mobile devices

IP.com Disclosure Number: IPCOM000236891D
Publication Date: 2014-May-21
Document File: 3 page(s) / 32K

Publishing Venue

The IP.com Prior Art Database

Abstract

In today's world, when everybody carries at least one mobile device, there is a great overlap between people's devices' notification sounds. Many users don't customize their notification sounds at all, satisfied with the default settings that come with it, and those that do usually pick from the sounds available on the device already. As a result, when you are surrounded by people with mobile devices, it is very often the case that someone shares the same notification sound settings as yours, leading to confusion when e.g. an incoming call or SMS arrives. More so, during meetings people usually set their notifications profile to "silent" or "vibrate". When it's set to "vibrate", ALL the phones share the exact same notification sound (vibrate) and when a phone vibrates, it's nearly impossible to identify which phone is it, which causes everyone in the room to check their phone. This disclosure solves The solution includes both a dedicated communication protocol and a notification profile change mechanism that: 1) Communication protocol used for detection of notification profile overlaps among proximate mobile devices. 2) Communication protocol used for resolving conflicts in notification profiles. 3) Notification profile change mechanism allows the mobile device owner to predefine a resolution plan (e.g., a set of notification preferences) in case of conflict detection to be used during the conflict resolution protocol phase.

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

Page 01 of 3

Detection and resolution of notification profile overlaps of proximate mobile devices

The proposed solution includes a communication protocol that has
two parts: one for notification overlap detection and one for
resolution of conflicts among proximate mobile devices.

In addition, recognizing that automatic changes to the
notification profile of a given mobile device may incur
additional confusion on it's owner, we further propose to allow
the mobile device
owner to define a notification profile resolution plan to be
considered during the resolution part of the communication
protocol.

In any case the user doesn't set a resolution plan, a default
resolution plan can be used instead (e.g., such that may be
implemented within the mobile device default settings).

In addition, upon detection of notification profile overlap among
proximate mobile devices, the owner may be only notified on such
conflict and may decide just to change the notification profile
by her own manually, hence skipping the automatic resolution part
of the protocol.


1. Setting of notification profile resolution plan:

A mobile device owner can set a resolution plan in case that a
notification profile overlap is detected and needs to be
resolved.

The idea behind this plan is that the owner may define a
(ordered) list of notification preferences (e.g., notification
based on sound X is preferred on notification based on sound Y).
Therefore, an owner that defines such a resolution plan is
assumed to be familiar with her alternative notification profiles
that she pre-defined, hence, no confusion will be incurred during
notification profile resolution and change.

The notification profile defined by the owner may include any
usage of types of sounds, ringtons, vibrations or human voices
(e.g., stating the mobile device owner's name).

The mobile device owner can further set conditions upon
resolution of overlaps. For example, the owner may decide to have
its device "participate" in the resolution protocol phase only if
some
threshold is met based on the detection phase of the protocol
(e.g., her device notification settings collide with more than
50% of proximate devices and/or within some distance as well the
presence of the other nearby phones exceed some time threshold).
2. Communication protocol for detection and resolution of
notification profiles overlaps:
It is assumed that near by mobile devices can communicate with
each other using some sorts of short range communication
protocol.

Protocol:


Page 02 of 3


1.

2.

A mobile device detects near by mobile devices.

[Coordinator selection]: proximate mobile devices select a coordinator for taking decisions. (this step is based on
existing protocols for leader selection, e.g., selecting as
leader the device with the smallest
MAC address hash value).
[Overlap detection]: Each peer device sends the leader its device's notification profile.

Leader checks if overlap exists and counts the ratio of overlaps.

Leader sends overlap report (includes a list of ids of collid...