v3 Tag Architecture
- Scalable provisioning.
- Controlled lifecycle.
- Reliable configuration.
Quuppa v3 tag architecture is designed for modern RTLS deployments that require centralised control, scalable provisioning and reliable configuration management. It enables efficient tag lifecycle management across projects, sites and organisations.
Provision a large number of tags with minimal manual work.
With v3 architecture, configuration is defined once in the project and applied automatically when tags are activated within Locator coverage. Tags are detected, configured and verified by the Quuppa Positioning Engine.
Mass provisioning becomes a controlled system process rather than a manual device-by-device task.
- Pre-defined default configurations.
- Automatic provisioning at activation.
- Tag group–based configuration management.
- Scalable batch handling.
How v3 provisioning works
The standard provisioning flow is straightforward:
1. Define configuration and
tag groups in the project.
2. Activate the tag
within locator coverage.
3. The system provisions
the tag automatically.
4. Configuration status
is verified centrally.
For advanced deployment scenarios and offline environments, detailed technical guidance is available in the product documentation.
Continuous lifecycle visibility
Maintain clear oversight of tag configuration throughout the deployment lifecycle.
v3 tags periodically communicate their configuration status to the system. This enables reliable background verification and automatic updates when configuration changes are required.
Configuration management becomes transparent and traceable.
- Monitor tag configuration status.
- Detect mismatches between target and actual configuration.
- Apply updates as a background process.
- Verify configuration completion centrally.
Controlled tag ownership
Ensure authorised use and controlled management of tags.
v3 architecture introduces controlled tag ownership and authorised system access. Tag communication and management are tied to the appropriate Quuppa RTLS instances, enabling organisations to manage who can configure and use their tags.
This architecture supports deployments that require controlled ownership and operational integrity.
- Tag-specific authorisation.
- Project-level access control.
- Optional tag white-listing.
- Delegated usage management.
API-driven management
Integrate tag lifecycle management into enterprise workflows.
v3 tags can be managed via the Quuppa Positioning Engine API, enabling automated configuration changes, tag group management and integration with backend systems.
Tag management becomes part of the overall system architecture, not a separate operational task.
- Automated tag group assignment.
- Programmatic configuration updates.
- Integration with middleware and enterprise systems.
- Reduced dependency on manual project file synchronisation.
Platform evolution and compatibility
With Quuppa System Release 8.0 and the introduction of Q generation Locators, tag lifecycle management and provisioning capabilities have been enhanced through the v3 architecture.
v3 tags are designed for use with Q generation Locators and current Quuppa system releases, enabling access to the latest platform capabilities.
Previous-generation LD Locators support v1 firmware tags. While v1 tags remain supported in compatible environments, ongoing system development and new feature enhancements are aligned with v3 architecture.
| v3 | v1 | |
| Q Generation QPE ≥ 8.0 |
Yes | Limited |
| LD Generation QPE ≤ 7.6 |
No | Yes |