Location
GeoHermes
GeoHermes - Location Service Platform
GeoHermes: Location Service Platform
GeoHermes is a professional location capability platform focused on providing core location data processing services. It handles device registration, access point ingestion, current location and historical trajectory queries, geofence management, and efficiently delivers real-time location data and entry/exit events to upper-layer business systems.
In terms of architectural design, GeoHermes strictly adheres to the principle of separation of duties: profile information for personnel, vehicles, and assets, approval workflows, and permission management ("who can see whom") remain within the business systems. GeoHermes only identifies registered devices and processes location facts associated with these devices. Each business product corresponds to an independent application on the platform, with data strictly isolated by application to ensure data security and privacy.
Diagram Interpretation:
- Upper Part: The business system on the left retains sensitive information such as names, license plates, and asset numbers, as well as approval and viewing permissions. Only the device ID crosses the boundary to the GeoHermes platform on the right. The platform does not know which specific person or vehicle the device belongs to; it only knows the current location and historical path of the registered device. Data from unregistered devices cannot be accessed.
- Lower Part: Demonstrates the application isolation mechanism. For example, personnel positioning products and fleet management act as two different business products, corresponding to Application A and Application B on the platform, respectively. Their location data is mutually invisible, achieving logical isolation.
Source: diagrams/who-keeps-what.svg. The text in the diagram is ASCII, with meanings as shown in the table below:
| Text in Diagram | Meaning |
|---|---|
| BUSINESS KEEPS | Content retained by the business system |
| Person / Vehicle / Asset | Personnel, vehicle, and asset profiles (names, license plates, IDs) |
| Also stays on this side | Approvals and "who can see whom" are not handed over to the platform |
| ONLY THIS / device code | Only the device ID is passed between the two sides |
| GEOHERMES SEES | What the platform actually recognizes |
| Device | Registered device; contains no names or license plates |
| Place | Current location and traveled path of this device |
| One product = one application | One business product corresponds to one application |
| Staff-location product / Application A | E.g., personnel positioning product; location is only within Application A |
| Fleet product / Application B | E.g., fleet product; location is only within Application B |
| no cross access | Locations of the two applications are mutually invisible |
Collaborative Architecture
Upper-layer business systems serve as the product layer, directly facing end users. Users only need to log in to the business system to complete map viewing, trajectory playback, alarm management, and permission control in a unified interface. The business backend is the sole caller of GeoHermes, sending requests to the platform via SDK and rendering the returned location facts back to the business interface.
GeoHermes delivers five core capabilities to the business side, forming a complete closed loop for location services:
Source: diagrams/collaboration.svg. The text in the diagram is ASCII, with meanings as shown in the table below:
| Text in Diagram | Meaning |
|---|---|
| UPPER BUSINESS | Upper-layer business systems: personnel, fleet, or asset products |
| End user | End users only log in to the business system |
| Business UI | Business interface: maps, playback, alarm texts, "who can see whom" |
| Business backend + SDK | Business backend, holding application keys, calls the platform via geohermes-sdk |
| BUSINESS OWNS | Master data, approvals, protocol decoding, and notification channels retained by the business itself |
| call | Capability calls initiated by the backend |
| facts | Location facts returned by the platform, presented by the business interface |
| GEOHERMES | Location capability platform; the five lines below are capability outputs |
| Device / deviceId | Register device after approval to get a stable device identifier; unregistered devices are not accepted |
| Ingest / fix | Accept normalized location points |
| Query / Current/Track | Current location and non-downsampled historical trajectories |
| Fence / ENTER/LEAVE | Geofences and subsequent entry/exit events (including restricted areas or activity ranges) |
| Subscribe / stream | A real-time connection for location streams; fence edge events are stored and can be pulled later |
| applicationId | Platform isolates data by application; console is for application operations only, not a business interface |
The platform provides an intuitive console interface, allowing administrators to view real-time and historical device trajectories:
![]()
It also supports viewing fence events generated by devices. Events are instantly sent to the application side via message streams, facilitating subsequent processing by business systems:

Core Capabilities
GeoHermes provides the following key functions to help business systems quickly build location service capabilities:
- Register First, Then Ingest Points The business side registers devices after approval to obtain stable device identifiers. The platform refuses to accept location data from unregistered devices and does not automatically create profiles upon receiving the first location point, ensuring data compliance and accuracy from the source.
- Current Location and Historical Trajectories Supports querying real-time device locations and extracting historical trajectory point sequences by time window. The platform faithfully records observed facts without downsampling trajectory data, preserving complete movement details.
- Geofencing and Entry/Exit Events Supports polygon-based electronic geofences, categorized into "Restricted Area" and "Activity Range." Devices must be bound to fences first. The platform triggers entry or exit events only when location points fall within the defined range. Events include fence type information, allowing the business side to generate personalized alarm texts. When a single device is associated with multiple activity ranges, the platform issues entry/exit events for the union of these ranges.
- Real-time Subscription with Recovery Support Delivers new location data and fence entry/exit events simultaneously via a single real-time connection. Fence entry/exit events are prioritized for storage. If the business backend experiences a brief interruption, data can be pulled by time upon recovery, ensuring the system does not rely solely on real-time connections as the unique data record source, thereby improving reliability.
- Java Client Support
Business backends can use
geohermes-sdkfor ticket exchange, device registration, point pushing, data querying, and subscription. Application keys are stored only in the business backend to ensure security.
Applicable Scenarios
GeoHermes is particularly suitable for the following teams:
- Teams Seeking Control Over Business Logic: Teams developing personnel positioning, fleet management, or asset tracking applications who wish to retain control over user management, organizational structure, and alarm strategies, while outsourcing only the location data infrastructure to a professional platform.
- Teams with Existing Data Collection Capabilities: Teams possessing existing collection devices or protocol gateways capable of parsing terminal messages into latitude/longitude and observation timestamps, requiring stable data writing, query services, and precise fence determination capabilities.
The platform console is primarily used by administrators to register applications, or by integrators for read-only verification after claiming. End business users always log in to their respective business systems, enjoying a seamless service experience.