Smart Subway Security: A Million Passengers, One Platform
Dense crowds, long operating hours and open public spaces make metros the hardest transport environment. This system covers gates to track with panoramic halls, 150 m platform zoom, crowd-density warnings, photo-based person search and PB-scale storage — old and new lines on one platform.
Why Metro Stations Are Hard Mode
The manufacturer's reference solution names the structural challenges of rail transit:
Dense crowds, tight spacesStation layouts leave little room for equipment, yet every square metre carries peak-hour crowds — coverage must be total with hardware that fits where there is no space.
Old lines, new lines, no bridgeEvery construction phase bought different systems; interconnecting them is the classic metro headache — the OCC ends up with one console per line era.
One station's incident, one line's crisisA fire, a stampede risk or a suspicious package at one station cascades down the whole line within minutes — response speed is measured in stations, not hours.
Open doors, open risksMetros are public by design — anyone walks in. Threats that airports filter at a checkpoint must here be caught by cameras and analytics in the flow.
Lost people, slow searchesA missing child or a wandering elder means scrubbing hours of footage across dozens of cameras — manually, while the family waits at the service desk.
System Architecture
Layered per the manufacturer's reference design: dual-lens entrances, panoramic ticket halls, long-range platform PTZ and counting cameras feed the station LAN; line fiber carries everything to the OCC — unified platform, behavior analytics, PB-scale IPSAN storage, video wall with 4K decoders.
Simplified diagram. Camera schedules per station type (underground/elevated/interchange) and OCC sizing follow your line drawings.
Six Jobs This System Does
Each card is a module of the manufacturer's reference solution, told from the platform edge.
Entrances that see twiceDual-lens units at every entrance watch the whole flow with one lens and pull face-level detail with the other, auto-tracking targets — so the same device answers 'how many came in' and 'who exactly was that'.
Halls held in one frame180° panoramic cameras cover the ticket hall without blind seams, running crowd-gathering recognition and trajectory analysis — fewer cameras, better continuity, and the analytics see the whole room, not slices of it.
Platforms watched to 150 mHigh-zoom units with auto-cruise patrol the platform and track area, capturing detail at up to 150 m — the full length of a platform from one position, including the track bed where intrusion matters most.
Crowds counted before they crushCounting cameras track real-time occupancy and density per zone; thresholds trigger peak warnings so staff redirect flow before a platform becomes dangerous — and the historical reports feed staffing and train-frequency decisions.
A face found in minutesUpload one photo — a missing child, a wandering elder, a suspect — and the system returns their trail across the station's cameras: where they entered, which corridor, which exit. What used to be hours of manual scrubbing becomes a minutes-long query at the service desk.
Alarms that reach the OCCFights, falls, intrusion, loitering, smoking, fire and smoke — plus non-video sources: device faults, video loss, storage failure, audio anomaly. Everything grades into the alarm chain (wall popup, e-mail, siren, phone) so the operations control center reacts to events, not rumors.
The Numbers That Matter
Key capabilities from the manufacturer's reference solution:
Platform detail capture at up to 150 m with auto-cruise patrol
Photo-based person search: upload one face, get their station trail
180° panoramic hall coverage — fewer cameras, no blind seams
PB-scale IPSAN storage for line-level retention
Alarm sources beyond video: device faults, video loss, storage failure, audio anomaly
System Components
These are the equipment roles the solution is built from. Exact models are chosen per site conditions, country requirements and budget — several of our product lines fit each role, so we spec the model list after receiving your requirement list.
| Item | What it does |
|---|---|
| Entrance dual-lens (crowd + detail) | One lens for the flow, one auto-tracking detail channel — the door's counter and witness in one body. |
| Hall & concourse panoramic units | Stitched wide view plus auto-tracked detail for the busiest space in the station. |
| Platform long-range zoom PTZ | 33× optical with auto-cruise — platform end to end, track bed included. |
| Corridor / escalator / TVM domes | Discreet coverage of the station's connective tissue. |
| People-counting cameras | Real-time occupancy and density per zone; feeds the peak-warning thresholds. |
| Station network & recording | PoE switches per equipment room; edge NVRs keep the station recording if the line backbone drops. |
| IPSAN storage + platform + video wall + decoders | OCC-level gear sized to station count, channel count and retention rule. |
Browse the full product catalog — cameras, NVRs & switches →
Send station drawings and your retention rule — we reply with a zone-by-zone camera plan and a line-level storage calculation.
Design Notes & Honest Limits
Read this before you order:
- Metro CCTV usually must integrate with existing SCADA/PIS/AFC systems and follow rail-sector standards — interface protocols and approval processes belong in the contract before hardware is chosen.
- Tunnels and platforms are maintenance-hostile: every camera position must be reachable within engineering-hours windows, which constrains mounting more than image quality does.
- Face search and person analytics in public transit are privacy-regulated in many countries — data retention, access rights and signage need the operator's legal sign-off before enabling.
- The 150 m platform figure assumes a clear sight line — platform screen doors, columns and curvature cut it; camera positions are set from the civil drawings, not the spec sheet.
- Crowd-density thresholds must be tuned per station during commissioning — a terminus and a mid-line station have different 'normal'; expect a calibration period, not plug-and-play.
FAQ
How many cameras does a metro station need?
From this architecture: 1 dual-lens per entrance, 1-2 panoramic units in the ticket hall, domes along corridors and every escalator head and foot, a long-range PTZ per platform (two on curved or 200 m+ platforms), TVM and gate-line domes, equipment-room and control-room coverage. A standard two-level island-platform station typically lands between 60 and 120 channels; interchanges run higher.
Can old lines and new lines run on one platform?
That is one of the solution's stated goals: the platform layer absorbs mixed device generations through standard protocols (ONVIF/RTSP and SDK integrations), so the OCC sees one map, one alarm queue and one user directory across construction phases. Honest caveat: very old analog fronts need encoders first, and some legacy analytics won't carry over — we audit the existing inventory before promising the bridge.
How does the crowd-density warning actually work?
Counting cameras at entrances and zone boundaries maintain a live in/out ledger per area; panoramic units add density estimation over the open floor. When a zone crosses its threshold, the platform raises a graded alarm — screens at the OCC, phones for station staff — early enough to slow inflow at the gates, open extra corridors or hold trains. History reports then show which thresholds fire daily, feeding timetable and staffing decisions.
How fast can a missing child be found?
The workflow: a parent shows any photo at the service desk; staff upload it and the system searches the station's cameras for matches, returning a time-stamped trail — entrance, corridors, platform, exit — typically within minutes. If the child boarded a train, the last-seen platform and time tell staff which train to call ahead to. The same photo-search serves wandering elders and suspect tracing; each use is logged for accountability.
How much storage does a metro line need?
The solution specifies PB-scale IPSAN for a reason: a 20-station line at ~90 channels per station is ~1,800 channels; at typical bitrates and 30-90 day retention (set by your transit authority), the math lands in the petabytes. The architecture splits it: edge NVRs per station for resilience, IPSAN pools at the OCC for retention, with RAID and fast retrieval. We calculate the exact disk count from your channel list and retention rule in the BOQ.
Send your station drawings — get a zone-by-zone camera plan back
Station count, platform lengths, entrances per station and your retention rule are enough for a first line-level BOQ.