Privacy Screen Security for Multi-User Device Access

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Single-user systems and multi-user systems lack a convenient and secure method to share access to selected functionality when physical access is provided to different users, as they do not effectively manage user access and resource sharing.

Innovation Solution

Implementing a privacy-screen based security system that uses an input interface for authentication, a processor to manage privacy screens, and memory to provide controlled access to subsets of applications and data, allowing users to configure privacy screens for different scenarios and automatically transition between them based on predefined rules or user input.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If physical access to the system is shared among different users, then usability and convenience are improved, but security and access control deteriorate

Engineering Contradiction:
Improveconvenience of sharing accessVSAvoidsecurity of access control
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system segments access control by creating multiple user accounts with different permission levels and privacy screen configurations. Each user has their own authenticated session with customized access rights to specific applications and data, allowing secure multi-user sharing without compromising individual security requirements

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system performs preliminary authentication and privacy screen configuration when users log in, establishing their access permissions before they interact with the system. This pre-configuration ensures that security controls are in place before any resource access occurs

Inventive Principle:
Principle #10Preliminary action

2Adaptability or versatility

If all applications and data are accessible to users, then functionality and versatility are improved, but security and privacy protection deteriorate

Engineering Contradiction:
Improveaccess to functionalityVSAvoidexposure to sensitive resources
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The system applies local quality by creating customized privacy screens for different user accounts, where each user sees only the applications and data they are authorized to access. This selective visibility ensures that sensitive resources are hidden from unauthorized users while maintaining full functionality for authorized users

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The privacy screen acts as an intermediary layer between the user and the system resources. It mediates access by filtering which applications and data are visible and accessible based on user authentication and permission settings, preventing direct exposure to sensitive resources

Inventive Principle:
Principle #24Intermediary (Mediator)

3Reliability

If privacy screens are configured for different scenarios, then security and privacy protection are improved, but device complexity and configuration effort increase

Engineering Contradiction:
Improveprivacy protectionVSAvoidconfiguration complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system provides universal privacy screen functionality that works across multiple scenarios and user accounts through a unified configuration interface. A single privacy screen framework serves all users and situations, reducing the need for separate complex configurations for each scenario

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS9721109B2Privacy screen-based security
Publication Date: 2017.08.01 EMC IP HLDG CO LLC
  • US9721109B2 patent drawing
  • US9721109B2 patent drawing
  • US9721109B2 patent drawing

AI summary

A system for privacy screen-based security comprises an input interface and a processor. The input interface is configured to receive authentication information. The processor is configured to, in the event authentication is determined to be successful, provide a privacy access screen, wherein the privacy access screen provides access to a set of applications or data, and determine whether to automatically transition to a new privacy screen, wherein the transition to the new privacy screen is automatic under a specific set of circumstances.