Solution Architecture
The platform is organized as four layers. Sensing engines produce the raw biometric signals at the bottom, the middle layer normalizes them into a unified event model, the Smart Corridor & eGate Hub aggregates and exposes them, and thin UI clients consume them on top. Only the Hub is visible to integrators — every layer beneath it is internal.
Architecturally, the solution is built on VPP (the Video Processing Platform): VPP does the biometric heavy lifting, and the corridor layers above it add identity grouping, zone behavior, and the unified integration surface. All four layers deploy together as one bundle; deployment topologies are covered in Deployment Layouts.
Source / sensing engines
The engines that turn camera streams into raw signals. Both are owned by the Innovatrics Platforms team, not the corridor team — the Hub consumes them as read-only upstream sources.
| Component | Role | Status |
|---|---|---|
| VPP — Video Processing Platform | Face detection, recognition, and watchlist matching | Active |
| MCT — Multi Camera Tracking | Re-identification and handoff across camera zones | Planned |
Until MCT is integrated, CBS derives the zone signals from VPP data.
Processing & adaptation
This layer turns the raw signals into the Hub's unified event model: the VPP and CIGS adapters translate their sources' output, while CIGS and CBS add the processing that groups identities and derives zone behavior.
| Component | Role | Connection |
|---|---|---|
| VPP Adapter | Translates VPP identification events | Hub component |
| CIGS — Identity Grouping Service | Groups cross-camera face detections into corridor identities | Via CIGS Adapter |
| CIGS Adapter | Translates CIGS identity events | Hub component |
| CBS — Behavior Service | Derives zone behavioral events (entry, dwell, exit) | Publishes directly |
Smart Corridor & eGate Hub
The Hub is the central integration layer and the only system integrators interact with. It aggregates and normalizes events from the internal components, persists the finalized outgoing events, and exposes them to external consumers. Internally, components communicate over a RabbitMQ exchange named biometric_events.
| Service | Role | Status |
|---|---|---|
| GraphQL API | Live subscriptions and data queries for external consumers | Active |
| DbWorker Service | Event persistence and data retention | Active |
| REST API | Alternative HTTP interface for integrations | Planned |
UI
On top sit the Officer Monitoring App and the Traveler Display, which connect exclusively to the Hub's GraphQL API. See the Operational Interface for details.
Related pages
- Components — every source system and Hub service in detail
- Integration — the unified event model, event catalog, and storage
- Operational Interface — the GUI clients built on the Hub's API