Files
ANSCORE/docs/diagrams/01-system-context.puml
T
2026-06-12 14:13:26 +10:00

49 lines
1.3 KiB
Plaintext

@startuml 01-system-context
title ANSCORE — System Context (L1 / L2 / L3)
skinparam componentStyle rectangle
skinparam packageStyle rectangle
package "Layer 3 — Qt/QML Desktop UI\n(Windows / macOS / Linux)" as L3 {
component "Qt/QML application" as UI
}
package "Layer 2 — ANSVIS Communication Layer (CL)" as L2 {
component "/api/v1\nREST surface" as APIV1
component "Legacy ANSVIS core\n(reused as-is)" as LEGACY
component "Media relay\nHLS / RTSP / WebRTC" as RELAY
component "SSE event\nbroadcaster" as SSEHUB
database "Event DB\n+ clip object store" as STORE
queue "Async job queue" as JOBS
component "Auth + RBAC" as AUTH
}
package "Layer 1 — ANSCORE Edge Runtime\n(one per target)" as L1 {
component "Camera + Inference\n+ Triggers" as EDGE
}
UI --> APIV1 : (1) REST / HTTPS\ncontrol + CRUD
UI --> SSEHUB : (2) SSE / HTTPS\nlive event tail
UI --> RELAY : (3) HLS / RTSP / WebRTC\nlive video
APIV1 --> AUTH
APIV1 --> LEGACY
APIV1 --> JOBS
APIV1 --> STORE
LEGACY --> STORE
STORE --> SSEHUB
RELAY <--> EDGE
LEGACY <--> EDGE
note bottom of L3
L3 only talks to L2 — never directly to edges.
end note
note bottom of L2
All three UI transports are brokered by the REST API:
the URL + token for live media and the SSE filter for
events are obtained via REST calls first.
end note
@enduml