GpsGate TrackerOne is a reference design for how a tracker unit interacts with GpsGate Server.
TrackerOne can be implemented as a software client on a mobile phone/similar mobile device, or as a black box tracker device. The TrackerOne reference design is focused on tracker/server interaction. It leaves the field open for how the actual software and hardware is designed and implemented.
TrackerOne defines the whole lifespan for a tracker. This includes configuration, how tracking is managed, and how status signals are transferred. Continuous tracking, motion-based, and request-based tracking is supported in the design.
TrackerOne defines the core “tracking engine” necessary in all personal, vehicle, and asset trackers.
The protocol can be extended, and there is a lot of freedom to build on top of the core to extend and customize functionality. If GpsGate Server is used as back-end, there is an open plugin architecture to support custom commands and features from a TrackerOne based device.
A TrackerOne device supports SMS and optionally TCP/IP (over, for example, GPRS). The tracker can either be optimized for mainly GPRS use, only SMS use, or mixed GPRS/SMS use. A TrackerOne device has an IMEI number. TrackerOne uses a subset of GpsGate Protocol.
TrackerOne can be used for vehicle tracking, personal tracking, asset tracking, or sport event tracking. TrackerOne defines the essential features necessary to work in those fields. The same hardware design will not function in all those segments, however. You will need to develop specific hardware designs for each segment. Some segments will require the optional features in TrackerOne for best performance.
A tracker implementing GpsGate TrackerOne can be used by the “QuickStart” feature on GpsGate.com and in GpsGate Server. This will enable a user to get started with a tracking device in less than a minute.