Skip to main content

Technical Architecture

This page provides detailed technical sequence diagrams showing how the Events Bridge system orchestrates monitoring and detection workflows for both Face Recognition and License Plate Recognition systems.

System Overview​

Events Bridge acts as an intermediary service that:

  • Accepts monitoring requests from partners with external IDs
  • Handles enrollment/matching with backend systems (Identities API for faces, eConnect Core for license plates)
  • Manages webhook callbacks when detections occur
  • Maintains the association between partner external IDs and internal system identities

Face Recognition Flow​

Monitor Face Sequence​

The following diagram shows the complete flow when a partner monitors a face through Events Bridge:

Face Detection Callback Sequence​

When a monitored face is detected, the following callback flow occurs:

License Plate Recognition Flow​

Monitor License Plate Sequence​

The following diagram shows the complete flow when a partner monitors a license plate through Events Bridge:

License Plate Detection Callback Sequence​

When a monitored license plate is detected, the following callback flow occurs:

Key Architectural Components​

External ID Management​

  • Purpose: Maps partner-specific identifiers to internal system entities
  • Face Recognition: externalId → Identities API person ID
  • License Plates: externalId → eConnect Core plate record ID
  • Benefits: Allows partners to use their own ID schemes while maintaining system integrity

Webhook System​

  • Delivery: HTTP POST callbacks to partner-configured endpoints
  • Authentication: Supports Basic Auth and Bearer Token authentication
  • Retry Logic: Configurable retry attempts with exponential backoff
  • Payload: Includes original externalId and all additionalFields for context

Multi-System Propagation​

  • Architecture: Single API call propagated to all connected endpoints
  • Face Systems: Distributed across multiple Identities API instances
  • LPR Systems: Distributed across multiple eConnect Core instances
  • Management: Events Bridge handles all connection management and synchronization

Error Handling​

Enrollment Failures​

Detection System Failures​

  • Events Bridge maintains monitoring state even during backend system outages
  • Detection events are queued and processed when systems recover
  • Webhook delivery includes retry mechanisms for partner endpoint failures

Security Considerations​

Authentication Flow​

  • Partners authenticate via JWT tokens obtained through /api/Auth/login
  • Tokens include expiration and can be renewed via /api/Auth/renew-token
  • All API calls require valid JWT in Authorization header

Data Protection​

  • Face images and biometric data encrypted in transit
  • External IDs are isolated per partner to prevent cross-contamination
  • Webhook payloads can be secured with partner-specific authentication

Network Security​

  • HTTPS encouraged for all communications
  • Self-signed certificate support for private network deployments
  • IP whitelisting available for webhook endpoints