Skip to main content

Components

A Smart Corridor is Face Matcher plus the corridor services built on top of it: the Smart Corridor & eGate Hub, the identity grouping and behavior services, and the operational interface, with multi-camera tracking as an optional overlay. All of them ship and start together from one deployment package. Cameras feed Face Matcher, the corridor services turn its identifications into one event model, and the Hub exposes that model to the officers' screens and to your systems.

Smart Corridor nodeships and starts as one package
Officer App
alerts & floormap
Traveler Display
go / stop guidance
live events
/graphqlevents · queries · watchlist sync
Your border systems
outside the corridor
  • entry / exit & watchlist alerts
  • Border Control Platform
  • gate hardware & peripherals
unified event model
Corridor Services
identity grouping (CIGS) · zone behavior (CBS) · adapters
tracksvia CBS
MCT
multi-camera tracking · optional
raw events
video and face crops
Smart camera
edge stream
Standard camera
RTSP stream
data / event flow/graphql — the only external integrationoptional

This page describes each component in one paragraph. How the layers fit together is in Solution Architecture, and the complete reference for each component is in its manual.

Corridor stack​

ComponentRoleShipsManual
Face MatcherFace detection, recognition and watchlist matchingAlways, as a vendored productFace Matcher in the Corridor
Smart Corridor & eGate HubCentral system: unified events, clearance decisions, the /graphql endpointAlwaysHub
CIGSGroups face detections into anonymous identitiesAlwaysCIGS
CBSZone behavior: entry, exit, occupancy, avoidanceAlwaysCBS
MCTBody-based tracking across camerasOptional overlayMCT
Operational interfaceOfficer Monitoring App and Traveler DisplayAlwaysOperational Interface

Face Matcher​

Face Matcher processes the camera streams, detects and recognizes faces and matches them against watchlists. It is a product of its own, which the corridor vendors unchanged and uses only through its published integration list; cameras and watchlists are managed in its Station UI or through its own APIs. See Face Matcher in the Corridor.

Smart Corridor & eGate Hub​

The Hub is the corridor's central system and, for corridor events, the only one integrators talk to. Its adapters take the output of Face Matcher and CIGS, CBS publishes to it directly, and the Hub normalizes everything into one event model, turns identifications into green or red clearance, stores events with a configurable retention and exposes them on one GraphQL endpoint on port 8090. See the Hub manual and the Event Catalog.

Corridor Identity Grouping Service (CIGS)​

CIGS follows a person through the corridor without needing a watchlist match. It groups the face detections of one person from several cameras and moments into a single anonymous identity, which lets the corridor count individuals and link a later identification to the right person. See the CIGS manual.

Corridor Behavior Service (CBS)​

CBS derives every zone-level event: corridor entry and exit, occupancy and its violations, people moving without a visible face, and position updates. It reads from Face Matcher, CIGS and, when deployed, MCT, and acts as its own adapter towards the Hub. See the CBS manual.

Multi Camera Tracking (MCT)​

MCT is an optional overlay that tracks where people physically are, from body detections on embedded cameras rather than from faces. It needs edge-capable cameras and a per-site calibration onto the floor plan, so it is planned at site design. Without MCT, CBS keeps a fallback for zone events. See the MCT manual.

Operational interface​

The stack ships a dashboard on port 8095 with two views built on the Hub's GraphQL API: the Officer Monitoring App for alerts and the floor map, and the Traveler Display that gives the traveler go or stop guidance. See Operational Interface.

Modules​

Modules extend a corridor beyond its own site. They are optional, are deployed beside the corridor package rather than inside it, and do not change how the corridor stack itself works.

Data Exchange Module (DXM)​

DXM links the corridor to the Border Control Platform. The Data Synchronization Service (DSS) fills Face Matcher watchlists with the travelers due at the site, and the Corridor Event Aggregator (CEA) turns the Hub's identifications of those travelers into encounters in the platform. The corridor keeps running when the platform is unreachable. See Border Control Platform Link-up and Set Up the Platform Link-up.