EMM Enabler Intermediary Application for Multi-System Compatibility
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current Enterprise Mobility Management (EMM) services require software vendors to develop multiple versions of mobile applications for different EMM systems, leading to increased maintenance overhead and reluctance from system administrators to update applications due to the burden of registering and testing updates across various EMM systems.
Innovation Solution
An intermediary application, known as the EMM enabler, supports multiple EMM systems by making EMM-specific requests for configuration information and providing login information to client applications, simplifying the process and reducing the need for multiple versions of applications and frequent updates.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If software vendors develop different versions of mobile applications for each EMM service, then compatibility with multiple EMM systems is improved, but maintenance overhead and complexity increase
Solution Approach 1:
The patent implements a universal EMM client application that can interface with multiple different EMM services through a standardized interface layer. This single application performs the function of multiple vendor-specific applications, allowing one codebase to serve multiple EMM systems without requiring separate versions for each service.
Solution Approach 2:
The patent introduces an intermediary component or abstraction layer between the mobile application and the various EMM services. This intermediary handles the differences between EMM systems, allowing the application to interact with a standardized interface while the intermediary translates to the specific EMM service protocols, thereby reducing maintenance complexity.
2Reliability
If updates are made to mobile applications, then functionality and security are improved, but testing and registration burden increases
Solution Approach 1:
The universal EMM client application allows updates to be performed once for a single codebase that serves multiple EMM systems. This eliminates the need to update and test multiple vendor-specific applications separately, significantly reducing the time and effort required for maintaining security and functionality across different EMM services.
Solution Approach 2:
The standardized interface and intermediary layer are established in advance, creating a framework that anticipates future EMM service variations. This preliminary action allows updates to be prepared generically without needing to know the specific EMM service in advance, reducing testing and registration time when updates are deployed.
3Adaptability or versatility
If administrators manually register and push updates for each EMM service, then service-specific customization is improved, but operational burden increases
Solution Approach 1:
The universal EMM client application with standardized interface allows administrators to manage updates and registrations through a single process that works across multiple EMM services. This maintains the ability to customize for specific services while dramatically reducing the operational burden of having to manually handle each EMM service separately.
Solution Approach 2:
The intermediary layer absorbs the complexity of service-specific customization, allowing administrators to work with a standardized interface while the intermediary handles the service-specific details. This maintains adaptability to different EMM services while making the administrative process much easier and less burdensome.
Data Source
AI summary
Embodiments of the disclosure provide systems and methods for accessing an Enterprise Mobility Management (EMM) application. According to one embodiment, a method for utilizing Enterprise Mobility Management (EMM) services can comprise receiving, at an EMM enabler application executing on an EMM system, a request for EMM information from a client application during a log in processes or the EMM system by the client application. The EMM enabler application can comprise an intermediary between the client application and the EMM system and the EMM enabler application can support a plurality of different EMM systems. The EMM enabler application can make an EMM-specific request for configuration information to the EMM system, receive the requested configuration information from the EMM system in response to the request, and provide, to the client application in response to the received request, the received configuration information from the EMM system.