Offline Model Graph for Mobile CRM Data Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current mobile CRM systems face challenges in providing offline access to CRM services, as they rely heavily on continuous data communication with servers, limiting user interaction and data management capabilities when mobile devices are offline.
Innovation Solution
The implementation of a model-view-controller architecture with dynamic client views (DCVs) and a model graph stored in database tables, allowing mobile devices to locally render and manage CRM data, including sorting, searching, and updating, even without internet connectivity by using universal resource indicators (URIs) and Java Server Faces technology.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If mobile CRM systems rely on continuous data communication with servers, then data synchronization and centralization are improved, but user access and data management capabilities deteriorate when devices are offline
Solution Approach 1:
The system performs preliminary actions by downloading and caching CRM data (contacts, opportunities, accounts) to the mobile device's local database before offline periods occur. This allows the device to access and manipulate CRM data locally without server connection, resolving the contradiction between maintaining data synchronization reliability and enabling ease of operation offline.
Solution Approach 2:
The patent introduces a local database as an intermediary between the server and the user interface. This intermediary layer stores copies of CRM data locally, enabling operations to proceed offline while maintaining the ability to synchronize with the server when connectivity is restored, thus balancing data synchronization reliability with offline accessibility.
2Ease of operation
If mobile devices store and process CRM data locally, then offline access and user interaction capabilities are improved, but data consistency and synchronization with servers deteriorate
Solution Approach 1:
The system implements feedback mechanisms where the mobile device monitors its offline status and automatically initiates data synchronization with the server when connectivity is restored. This feedback loop ensures that locally stored and processed data is eventually reconciled with the central server, maintaining data consistency while preserving offline operational capabilities.
Solution Approach 2:
The system performs preliminary data synchronization and conflict resolution actions when connectivity is available, preparing data for offline use. This includes pre-resolving potential conflicts and ensuring data consistency before offline periods begin, thereby maintaining reliability while enabling offline access.
3Reliability
If CRM systems require internet connectivity for all operations, then data centralization and security are improved, but productivity and user efficiency deteriorate during offline periods
Solution Approach 1:
The patent segments the CRM system into multiple components: a central server for data security and management, and a local mobile device component for offline operations. This segmentation allows critical security functions to remain centralized while enabling productive offline operations through local data caching and processing, thus resolving the contradiction between data security and offline productivity.
Solution Approach 2:
The local database acts as an intermediary that enables productive offline operations while maintaining security through controlled synchronization with the central server. This intermediary layer allows users to work offline with cached data and only communicates with the secure server when necessary for synchronization, preserving both security and productivity.
4Ease of operation
If mobile devices cache extensive CRM data locally, then offline functionality and user interaction are improved, but device memory usage and data synchronization complexity increase
Solution Approach 1:
The system applies local quality by caching only the specific CRM data relevant to each user's role and current tasks, rather than storing all data universally. This selective local caching optimizes offline functionality for each user's needs while reducing the overall data volume that requires synchronization, thereby lowering synchronization complexity while maintaining ease of operation.
Solution Approach 2:
The system implements partial action by caching only essential CRM data (such as frequently accessed contacts and opportunities) locally, rather than all possible data. This partial caching provides sufficient offline functionality for common operations while minimizing the complexity and overhead of data synchronization when online.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
A method and system for defining an offlinable model graph. In one embodiment of the method, a request is generated by a mobile device. The mobile device receives a response to the request. The mobile device updates a plurality of tables stored in memory of the mobile device, wherein the updating comprises adding a component of the response to a first table of the plurality of tables.