Browse Prior Art Database

Enabling functionality based on privileges granted for application

IP.com Disclosure Number: IPCOM000238326D
Publication Date: 2014-Aug-18
Document File: 2 page(s) / 30K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system to new type of communication between application and framework it works on. The framework (operating system in particular) will provide information which resources can be accessed by application or information that access is revoked.

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

Page 01 of 2

Enabling functionality based on privileges granted for application

Application will have a list of all privileges required and information about which function requires particular access. Functionality is disabled if user does not allow application to read data. For example: granting access GPS device cause that application will add location (geo-tag) to an action such status message on social media or photo, access personal information like date of birth to show/hide data that should not be viewed by children. Granting (or revoking) every privilege that application ask for, may enable (or disable) a functionality that may require the data

Today application may be created on many platforms. Some examples of platforms that allows application development are social media or mobile. Such a platforms have a common part: it is common pattern to require some privileges from user, when using or installing the application. Currently, platforms require to accept all privileges during first use or installation and users need to choose if they grant all access for that application asks or user is forced to stop using or drop installation.

Every application consist on a set of functions. Let us assume that we have an application like on Figure 1 that have 3 main functions (F1, F2 and F3) and it requires 3 different access (P1, P2 and P3) as on image below. Additionally, we may assume that F3 is main functionality of the app - disabling this function cause that application no longer provide value to user.

Figure 1. Example of application with three different functions and using three resources on system

• Functionality F1 requires two accesses to resource: P1 and P2 - revoking access from single resource cause that whole function is disabled

• Functionality F2 requires only one resource P2. If access is granted to application, function will work. If user don't grant access to resource P2, both functions F1 and F2 will be disabled

• Revoking access to P3 cause that main function F3 is disabled and application will become unusable for user. In this case user might be notified that main function is disabled

Current approach of platform with limited privileges is to...