Thin Client Map Adapter Runtime Loading
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing mapping systems face difficulties in adding, replacing, and updating map engines due to complex, map engine-specific code requirements, making it costly and time-consuming.
Innovation Solution
A thin client system that receives and loads a map adapter from a map server, allowing for the display of map data in a map engine without requiring restarts of the server or client, enabling plug-and-play functionality and supporting multiple technologies and symbology sets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If map engine-specific code is implemented on the client side for each map engine, then mapping functionality is achieved, but system complexity and maintenance cost increase
Solution Approach 1:
The patent extracts map engine-specific code from the client side and relocates it to the server side, where it is packaged as downloadable map adapters. This allows the client to remain simple and generic while still supporting multiple map engines through server-provided adapters.
Solution Approach 2:
The thin client is designed with universal functionality to support multiple map engines through a standardized interface. By implementing a common framework that can load different map adapters from the server, the client achieves multi-engine support without requiring engine-specific code for each implementation.
2Adaptability or versatility
If map engines are updated or replaced on the client side, then new mapping capabilities are achieved, but system downtime and maintenance time increase
Solution Approach 1:
Map adapters are prepared and validated on the server side before being deployed to clients. The server manages the availability and compatibility of map adapters, allowing clients to download updated adapters without requiring complex local installation procedures or system restarts.
Solution Approach 2:
The server acts as an intermediary that manages map engine updates and distributes them to clients as map adapters. This intermediary layer handles the complexity of updates, version management, and compatibility checks, freeing the client from maintenance burdens and enabling seamless updates without downtime.
3Adaptability or versatility
If multiple map engines are supported on the client side, then application versatility is improved, but code complexity and development cost increase
Solution Approach 1:
Instead of implementing multiple map engines directly in the client codebase, the system uses copyable map adapter packages that are distributed from the server. Each map adapter is a self-contained unit that can be independently developed, tested, and deployed, reducing the complexity of supporting multiple engines in the client.
Solution Approach 2:
The system segments map engine functionality into separate, independent map adapters that are distributed from the server. Each adapter is a modular unit that implements a specific map engine's functionality, allowing the client to load only the adapters it needs without containing all engine implementations.
Data Source
AI summary
A method of operating a thin client in a mapping system includes receiving, by the thin client, a map adapter from a map server; loading the map adapter in the thin client, wherein the loaded map adapter comprises a map engine; receiving, by the thin client, map data from the map server; and displaying, by the thin client, the map data in the map engine in the map adapter.