Browse Prior Art Database

A context based system to control the level of exposure of content shared across different sections of people

IP.com Disclosure Number: IPCOM000249507D
Publication Date: 2017-Mar-02
Document File: 4 page(s) / 49K

Publishing Venue

The IP.com Prior Art Database

Abstract

This system enables sharing of data among different audience, yet maintain the different levels of data confidentiality among them based on a simple context/configuration. This proposal is especially applicable in cases where audience/recipients belong to multilevel hierarchy and data that needs to be shared is different at different levels in hierarchy.

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

1

A context based system to control the level of exposure of content shared across different sections of people

Summary Many a times information shared via e-mail, documents or PDF's contain confidential contents, which can be hazardous if it reaches wrong hands or wrong sections of audience. This system proposes a solution to control the data that is shared across different sections of people, based on what they should know/see/read as defined by content owner.

This system enables sharing of data among different audience, yet maintain the different levels of data confidentiality among them based on a simple context/configuration. This proposal is especially applicable in cases where audience/recipients belong to multilevel hierarchy and data that needs to be shared is different at different levels in hierarchy. The content owner/author need not maintain different versions of information for different groups of people, instead with simple context setting, information can be customized to different exposure levels within the same document/email/streaming source. The recipient will get access only to the content that is meant for him/her.

Use case to understand it better:

A CEO of an MNC, needs to share the company's performance report with employees in different geographical locations OR employees in different hierarchy levels OR employees in different organizations in the company. But the performance figures that need to be shared with employees may not be same. Based on Geo OR hierarchy OR organization, CEO may have to share different financial numbers with different employees. Or there may not be a need to share some of the confidential numbers with all employees, but only executives.

In such cases, CEO needs to maintain different versions of document or different versions of e-mail, which can be difficult to manage and follow up.

With this system, using simple annotations, CEO can control the content to be sent to different sections of employees in one email or one document.

Following is the sample, where content between @>AP_IN_401 and @<AP_IN_401 will be sent only to employees belonging to AP_IN_401 group in email distribution list. Similarly, next section is sent only to EU_IN_402 group.

...

...

@>AP_IN_401 ... ...

2

@<AP_IN_401 @>EU_IN_402 ... ... @<EU_IN_402 … …

In case of sharing a document, a simple context map can be maintained which will validate the access privilege to certain section within the document, based on key/certificate passed. The document can also be annotated like the email as shown in above example and the access privilege will be validated when the user/employee/member enters his/her unique key/certificate. Once validated, the user shall see the information based on...