陳芮芮 RUIRUI Projects
City Guardian
Project 03 · City Guardian

City GuardianIntersection Recording Patrol

The intersection feed is still live, yet the recording may have stopped long ago.
I look over every intersection unit, layer by layer, until all is clear.

Recording HealthAutomated checksInstant alerts
In progress・Build and pilot phase

What it solves

THE PROBLEM

Across a city's intersections stand hundreds, even thousands, of recording units. On the day the footage is truly needed, the words you most dread hearing are: “That one stopped recording long ago.”
Patrols used to know only one thing: the unit can't be reached. But there are many reasons it can't be reached. Did the host crash, the recording software stop, the camera disconnect, the disk fill up, or is it just the network? Without knowing what failed, repair crews arrive on site only to find they brought the wrong parts and made the trip for nothing.
So what we built isn't “one more report,” but letting every unit tell you, by itself, which layer has failed.

Ruirui ♡

Five-layer check

FIVE LAYERS
L1

Network

Whether the host is online, and whether its common service ports respond.

Every 10 minutes
L2

Host

Uptime, CPU and memory, how much disk space is left and whether the drives are healthy, and whether the system clock has drifted.

Hourly
L3

Recording

Is the recorder still running? How many minutes ago each camera wrote its latest recording—if it's been too long, it has stopped.

Every 30 minutes
L4

Screens

Captures a frame and checks for black screens, freezes, obstructions, or heavy blur. Every judgment is made on site, with no reliance on the cloud.

Twice a day
L5

Integrity

Looks back over the past 24 hours of footage for any gaps.

Once a day
NormalCaution (disk nearly full, clock drift)Fault (with the exact layer named)

How it works

ARCHITECTURE
Intersection recording units Hundreds upon thousands・each guarding an intersection Scheduled checks Patrol Server L1 L2 L3 L4 L5 Placed inside the on-site network Footage stays on site and is never sent out Two network cards・two worlds that never meet Patrol dashboard・status lights at a glance Daily patrol report Instant alerts for new faults Remote maintenance: only status numbers are sent back, over encrypted outbound connections
Outbound only　The reporting side opens no inbound doors; it only makes encrypted connections outward.
Footage never leaves the site　Screenshots are stored only on the patrol unit; all that comes back are status lights and numbers.
Pinpoints what's broken　Every fault is tagged with its layer, L1–L5, so the repair crew brings the right parts the first time.
No repeat alerts　Each problem on each unit is reported only once, and you'll hear again when it's fixed.

Illustration

CONCEPT
Concept illustration: among a thousand lights, spot at a glance the one unit that needs a person's attention

This is a conceptual illustration, not an actual system screen. Once the project is complete and permission is granted, real screens and results will be added.

Progress

PROGRESS

What it's built with

BUILT WITH
UbuntuPythonFastAPIPostgreSQLRTSP / FFmpegOpenCVOn-site image analysisCloudflare TunnelMini PC