TrackerHub
  1. Docs
TrackerHub
  • Docs
    • 01. Project Overview
    • 02. Authentication
    • 03. Error Handling
    • 04. Input Operations
    • 05. GPS Position Workflow
  • API
    • Device Type
      • Device Type
    • Tracker
      • Tracker
      • Tracker
      • Tracker
      • Tracker
    • Device
      • Create Device
      • List Device
      • Device
      • Device
      • Device
    • Position
      • Position
      • Position
      • Position
      • Create Position
      • Position :vendor
      • latest-position
      • latest-positions
      • latest-positions :deviceId
    • Configuration
      • Config
      • Config
      • Config
      • Config
    • Healthcheck
      GET
  1. Docs

01. Project Overview

Tracker HUB#

The Tracker HUB is a centralized management service that collects tracking data from various external vendors in different formats, parsing them into a unified internal format. Allowing a simpler data processing that enables fast and efficient querying for reports.
Our Tracker HUB was developed with a focus on flexibility, scalability, and efficiency. This means it can manage multiple Client instances, each tailored to a specific client, ensuring secure and personalized administration.

Main Entities of the Project#

Introduction to the entities related to tracking data management.

Devices#

A device refers to the entity being tracked, typically a vehicle. It must be linked to a device type and a tracker. A device contains fields such as the device code and unique device identifier, which can be used to store information like the vehicle's license plate and chassis number.

Trackers#

The tracker is the device that sends tracking data to the service. Registering it in the system allows for saving and assigning information such as the device's IMEI, and enables a device to switch trackers if needed.

Positions#

A position refers to geographical data associated with a specific point in time and links this data to a device. Positions can store other relevant information, such as speed, distance traveled, vehicle direction, tracker signal strength, and the vehicle's engine status, among others. Positions are the foundation upon which movement reports are generated.

Operation Flows#

This section presents the general flowcharts of the input and output operations, along with diagrams of the main flows of Tracker HUB.

General Input Flow#

Below is a diagram illustrating the main entry points of the API, which represent the operations a client can perform by sending requests to the service's API. These and other entry points are detailed under Input Operations.
NestJS Tracker - Entrada.jpg

General Output Flow#

Below is the flowchart of the API's exit points, which represents the requests made by Exati to the Tracker HUB API. These points are detailed under Output Operations.
NestJS Tracker - Saida.jpg
Previous
Docs
Next
02. Authentication