Kiosk Notification Layer for OS Event Filtering
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Kiosk devices restrict users from accessing system notifications related to operating system events, such as battery level or network disconnection, which can be useful but are inaccessible due to kiosk software design, limiting user experience.
Innovation Solution
A notification layer between the OS and the specific kiosk application manages a notification restriction list to determine which OS events are restricted or unrestricted, allowing only unrestricted notifications to be displayed on the graphical user interface, configurable by users or administrators.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If kiosk software restricts access to system functions, then kiosk application control is improved, but user access to useful notifications is worsened
Solution Approach 1:
A notification layer is introduced as an intermediary component between the operating system and the kiosk application. This layer intercepts notification requests from the OS, checks them against a restriction list, and selectively allows or blocks them. The intermediary approach maintains kiosk control while preserving access to important notifications by filtering rather than completely blocking them.
Solution Approach 2:
The notification system is segmented into restricted and unrestricted categories through a notification restriction list. Instead of a blanket restriction, the system divides notifications into segments - some blocked (e.g., system updates) and some allowed (e.g., battery warnings). This segmentation enables selective control, maintaining security while preserving useful information flow.
2Reliability
If all OS notifications are blocked, then kiosk functionality is improved, but user awareness of system events is worsened
Solution Approach 1:
Different notification types receive different treatment based on their local quality or characteristics. The notification layer evaluates each notification's content and origin, applying different restriction rules to different types. Critical user-awareness notifications (battery, network) are allowed while non-essential system notifications are blocked, creating localized quality differences in notification delivery.
3Reliability
If notification restrictions are implemented, then system control is improved, but notification filtering capability is worsened
Solution Approach 1:
The notification restriction list is prepared in advance before runtime notification processing. Administrators or the system pre-configure which notification types should be restricted. This preliminary action eliminates the need for complex real-time analysis of each notification's content, reducing filtering complexity while maintaining effective control.
Data Source
AI summary
Example implementations relate to operating system events of a kiosk device. For example, a computing device may include a processor. The processor monitors an operating system of the computing device, where the computing device is to operate as a kiosk device to execute a specific application while restricting access to other applications. The processor identifies an operating system event generated by the operating system and determines, based on a notification restriction list, whether the operating system event is to be restricted. A notification associated with the operating system event is restricted when the operating system even is determined to be restricted and is displayed on a graphical user interface when the operating system event is determined to be unrestricted.