Mobile Cloud Service Protocol Translation for Enterprise Integration
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current systems for mobile application development and security struggle to keep pace with the variety of mobile devices and enterprise systems, leading to compatibility issues and security concerns due to differences in communication protocols and hardware.
Innovation Solution
The implementation of a declarative browser-based client application development tool using the Mobile Cloud Service (MCS) from Oracle Corp., which facilitates communication between mobile devices and enterprise systems through a cloud-based interface, translating protocols to a standardized REST architecture and providing secure adaptors for various enterprise systems.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If traditional mobile application development approaches are used to support various mobile devices and enterprise systems, then device compatibility and system integration are improved, but development complexity and security management burden increase significantly
Solution Approach 1:
The patent introduces a cloud-based translation service that acts as an intermediary between mobile devices and enterprise systems. This service translates diverse communication protocols into a standardized REST architecture, enabling multiple device types to interact with enterprise systems without requiring separate development for each protocol, thereby reducing development complexity while maintaining adaptability
Solution Approach 2:
The patent creates a universal cloud-based interface that handles multiple communication protocols (SMS, MMS, email, instant messaging) through a single standardized REST API. This multi-functional approach allows the same enterprise system to communicate with various mobile devices using different protocols without requiring protocol-specific implementation, simplifying development while supporting diverse devices
2Reliability
If custom security implementations are developed for each mobile device and enterprise system combination, then security requirements are met, but implementation time and security management overhead increase
Solution Approach 1:
The patent introduces a cloud-based security layer that acts as an intermediary between mobile devices and enterprise systems. This centralized security implementation handles authentication, authorization, and protocol translation securely, eliminating the need to implement custom security for each device-system pair while maintaining high security standards and reducing implementation time
Solution Approach 2:
The patent enables the system to automatically handle security protocols and protocol translation through automated authentication and authorization mechanisms. The cloud-based service self-manages security configurations and protocol adaptations, reducing the time and expertise required for security implementation and management
3Adaptability or versatility
If protocol translation services are added to support multiple communication standards, then system compatibility is improved, but service complexity increases
Solution Approach 1:
The patent introduces a cloud-based translation service that acts as an intermediary between mobile devices and enterprise systems. This service translates diverse communication protocols into a standardized REST architecture, enabling multiple device types to interact with enterprise systems without requiring separate development for each protocol, thereby reducing development complexity while maintaining adaptability
Solution Approach 2:
The patent standardizes diverse communication protocols into a uniform REST API format. By converting SMS, MMS, email, and instant messaging protocols into a homogeneous REST interface, the system simplifies service complexity while maintaining compatibility with multiple protocols through consistent handling and transformation rules
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A system restores a user interface ("UI") state. The system receives an action performed by a user that interacts with a UI, and determines a transaction based on the action, where the transaction is configured to modify a model corresponding to the UI. The system stores a first UI state of the UI and a first model state of the model, and then commits the transaction. The system subsequently determines to undo the transaction based on a first user interaction. The system then restores the UI to the first UI state and the model to the first model state. In one embodiment, the first model state is restored before undoing the transaction, while the first UI state is restored after undoing the transaction.