Browse Prior Art Database

Proximity software view enabler for mobile devices

IP.com Disclosure Number: IPCOM000237674D
Publication Date: 2014-Jul-02
Document File: 4 page(s) / 679K

Publishing Venue

The IP.com Prior Art Database

Abstract

Proximity software view enabler for mobile devices

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

Page 01 of 4

Proximity software view enabler for mobile devices

    In a world that is working more and more with mobile devices, it becomes very important to protect data stored in such devices, in particular data defined as Confidential. Our system addresses a way to hide the vision of part or the totality of confidential data based on the proximity of a personal device that enable/disable the vision of them. This can be used to protect confidential data in case the device is stolen or to decide what information can be showed in case of a shared device used by different persons.

    In order to solve the above issue, a proximity device (bracelet or a ring or a key with wireless radio module) is proposed. When the proximity device is near the mobile device then, a particular view of the system is activated. As view we intend the part of files or applications that the user is authorized to use.

Application example :

    
Assuming a user works on a mobile device with a virtual machine in offline mode or with any generic application with confidential data. If the mobile device is stolen or lost, then, the new owner without the proximity device (bracelet or key or ....) cannot access the device or the sensible application and/or files in the device, based on the user configuration.

Assuming the same device such as a smartphone or a tablet can be used by 2 different persons: by default, without any personal proximity device, the mobile device will show only common application accessible by everyone without any confidential data as shown in the picture below.

1


Page 02 of 4

On the same system, User 1 with his own personal device key will see:

while User 2 with his own personal device key will see:

2


Page 03 of 4

    Here below the the detailed solution architecture and the basic use case. The basic components of the architecture are (Figure 1):
1- The first software module (Polling component) is responsible to discover the presence of an authorized proximity device

    2- The second software module (Request Respon...