Enterprise Notification Service Prioritization via EMM Mediator
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Enterprises face challenges in managing and controlling notifications across various applications, leading to uncertainty and ineffectiveness in ensuring that important work-related notifications are prioritized and delivered to users, as existing systems lack centralized management and flexibility.
Innovation Solution
A notification platform managed by an Enterprise Mobility Management (EMM) system that allows administrators to whitelist or blacklist notifications, prioritize them based on managed and unmanaged applications, and provide a graphical user interface for creating and managing notifications, including options for defining recipients, priority, and action buttons, ensuring important notifications are displayed prominently.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If enterprises use pre-defined native notifications from various applications, then notifications can be delivered to users, but enterprises have very little flexibility and control over which notifications are sent
Solution Approach 1:
The patent introduces an EMM server as an intermediary between applications and users. The server receives notifications from multiple applications, standardizes their format, applies enterprise policies, and delivers them to users. This mediator enables centralized control and flexibility without requiring enterprises to manage each application's notification system individually.
Solution Approach 2:
The EMM server provides a universal notification service that handles notifications from both managed and unmanaged applications through a single platform. It performs multiple functions including receiving notifications, applying policies, prioritizing them, and delivering them, replacing the need for separate notification mechanisms for each application.
2Loss of information
If multiple applications send notifications to users, then users receive comprehensive information, but users are inundated with notifications and important enterprise notifications get overlooked
Solution Approach 1:
The patent applies different quality attributes to different notifications based on their source and content. Enterprise notifications are assigned higher priority and displayed more prominently, while personal application notifications receive lower priority. This local differentiation ensures important information stands out without completely blocking other notifications.
Solution Approach 2:
The EMM server performs preliminary sorting and prioritization of notifications before they reach the user. By pre-processing notifications according to enterprise policies and importance levels, the system prevents notification overload at the user interface, ensuring critical enterprise notifications are always visible.
3Adaptability or versatility
If enterprises allow notifications from unmanaged applications, then users have access to personal applications, but enterprises cannot control or prioritize these notifications
Solution Approach 1:
The EMM server acts as an intermediary that receives notifications from both managed and unmanaged applications. Even though unmanaged applications are outside direct enterprise control, their notifications pass through the EMM server which applies enterprise policies, ensuring consistent control and prioritization across all notification sources.
Solution Approach 2:
The system changes the priority parameter of notifications based on their source. Notifications from managed applications are assigned higher priority values, while unmanaged application notifications receive lower priority values. This parameter change enables automatic differentiation and control without restricting application compatibility.
Data Source
AI summary
A notification builder implemented through a graphical user interface (“GUI”) provides a platform for building notifications and defining priorities for how the notifications will be presented to users of managed devices. Elements included in the notification builder and selectable as part of a build process can provide options for naming a notification, providing content for the notification, defining recipients, setting a respective priority, and creating action buttons. An action button can allow a user that has received a notification built with the notification builder to interact with the notification in a predetermined manner. The GUI can also provide data relating to the notification, such as success/failure, read/unread, etc.