Deveryloc is based on a multi-modal geolocation architecture that aggregates several positioning layers (network signaling, GPS, Wi-Fi) to provide a usable real-time position. It is not just a simple tracker: the platform orchestrates heterogeneous data flows, which distinguishes it from the still widespread mono-technology solutions in the fleet and people localization market.
Protocol Stack and Sensor Fusion in Deveryloc
The technical value of Deveryloc lies in its ability for real-time multi-source fusion. While a classic GPS device relies solely on a GNSS constellation, Deveryloc cross-references cellular data (antenna triangulation, Cell-ID, timing advance) with satellite positioning and, depending on the configurations, Wi-Fi fingerprinting.
See also : QR Codes in the Gaming Universe: A Revolution for Bonuses and Rewards
This approach compensates for the limitations of each technology taken in isolation. GPS loses reliability in urban canyons or covered areas. Cellular triangulation offers wide coverage but with limited accuracy of a few hundred meters. By combining these signals through a fusion engine, the platform reduces blind spots without multiplying onboard hardware.
We observe that this fusion logic converges with the recent industrial trend to integrate multi-constellation GNSS (GPS, Galileo, Beidou) with UWB indoors and, recently, 5G RedCap modules for low-power connected objects. Deveryloc has not yet announced an UWB or 5G RedCap component in its public architecture, but its multi-modal design positions it favorably to absorb these additional layers without major redesign.
See also : Mastering the Art of Graphic Design: A Complete Guide for Successful Training
To delve deeper into how this approach works, a detailed article discusses Deveryloc technology on Orvinfait with additional insights on use cases.
GDPR Constraints and Geolocation of Individuals: What Deveryloc Requires to Verify
Locating an object and locating a person do not fall under the same legal framework. The CNIL has strengthened its doctrine on the geolocation of employees, with several requirements that directly condition the deployment of platforms like Deveryloc.
- Strictly justified purpose: only specific objectives (employee safety, route optimization, protection of goods) allow for the collection of positioning data. A “comfort” or managerial tracking does not pass the filter.
- Prohibition of continuous tracking outside working hours: the device must be able to be deactivated or its data purged outside of professional activity periods.
- Principle of precision minimization: if the declared purpose does not require meter-level localization, the resolution must be deliberately degraded (zone rather than exact coordinates).
- Prior information and processing register: each affected employee must be informed before activation, and the processing must be recorded in the company’s GDPR register.
These obligations apply regardless of the technical provider. We recommend documenting the purpose in the platform’s settings, not just in a separate legal note. A compliant localization tool is configured as much as it is deployed.
Deveryloc vs. Industrial RTLS Architectures
The industrial RTLS (Real-Time Location System) market has been structured around indoor positioning technologies: UWB, BLE (Bluetooth Low Energy), active RFID. These systems achieve accuracies on the order of a few tens of centimeters in controlled environments (warehouses, factories, hospitals).
Deveryloc does not position itself in this pure indoor niche. Its strength lies in outdoor and peri-urban tracking, where dedicated RTLS infrastructures do not exist. Therefore, direct comparison does not make sense for a warehouse equipped with UWB anchors. However, for tracking vehicles, parcels in transit, or itinerant personnel, Deveryloc’s cellular + GNSS coverage meets a need that indoor RTLS do not cover.
The European DUNE project, supported under VEDLIoT, combines deep learning and distributed computing (cloud, edge, far-edge) to improve the localization of objects in industrial indoor environments. This type of research illustrates the direction taken by indoor RTLS, while Deveryloc addresses the complementary layer: mobility tracking on open networks.
Data Security for Location: Encryption and Access
Geolocation data are personal data under GDPR as soon as they allow for the identification, directly or indirectly, of a natural person. Their sensitivity requires rigorous processing on the infrastructure side.
A point rarely addressed in commercial documentation: the encryption of positioning data in transit and at rest is as crucial for compliance as consent. Without TLS on the data streams from terminals and without AES encryption (or equivalent) on storage databases, the device presents an exploitable attack surface.
The granularity of access rights constitutes the other pillar. A fleet supervisor does not need access to an employee’s position history over several weeks. We recommend configuring roles with limited time access windows and restricted exports, features that any serious platform should offer natively.
Indoor-Outdoor Continuity: The Next Step for Multi-Modal Localization
The convergence of GNSS + UWB + 5G RedCap represents the next technological leap for localization platforms. The 5G RedCap modules, standardized in Release 17 of 3GPP, specifically target low-power connected objects that require moderate bandwidth but reliable cellular coverage.
For a platform like Deveryloc, integrating this component would ensure a seamless transition between outdoor and indoor positioning without requiring the client to deploy dedicated anchor infrastructure. The terminal would automatically switch from GNSS to 5G RedCap and then to BLE or UWB depending on signal availability.
This scenario remains prospective, but the growing maturity of RedCap chipsets among manufacturers suggests concrete deployments in the short term. Current multi-modal platforms will be the first to benefit from this additional layer, provided their software architecture supports the addition of new positioning sources without heavy refactoring.