BCMS Smart Law-Enforcement Video Management Platform
Product Overview
BCMS (Body Camera Management System) is a comprehensive audio/video management platform for law enforcement, designed for public security, judiciary, traffic, prison, and large-enterprise organizations. It focuses on three core needs: centralized device control, local data storage, and compliant, auditable operations. The system integrates body-worn cameras, DMS collection servers, and an IoT communication architecture to deliver an end-to-end closed loop—from device onboarding and live streaming to playback, smart storage, and permission management.
The platform uses WebRTC P2P for low-latency live audio/video streaming and playback, synchronizes device status and delivers remote commands over MQTT, and relies on a DMS (Data Management Server) deployed inside the customer's network to receive and persist audio/video, images, and metadata. This ensures that all sensitive data never traverses the public internet and is never uploaded to any third-party cloud, meeting the data-sovereignty and privacy requirements of the Personal Information Protection Law, the Data Security Law, and industry regulators.
BCMS follows a To-B enterprise model with private deployment that adapts to the customer's existing network and security policies. The architecture also reserves multi-tenant isolation, reseller enablement, and individual-user extensibility to support future business evolution.
✅ Architectural principle: Control lives in the cloud; media stays entirely inside the customer network. The DMS handles only signaling coordination and data archiving. No audio/video stream ever passes through any cloud relay, realizing a lightweight "control in the cloud, data on-premises" deployment model.
Core Features
📹 Body Camera Live Monitoring
- Supports anywhere from hundreds to tens of thousands of cameras online concurrently, with clear, stable video and live latency kept under 300 ms.
- Offers multiple split-screen layouts (1x1, 2x2, 3x3, 4x4, 5x5, 6x6, and 1+5, 1+7, 1+9, 1+11) for command-center large displays; a single screen can monitor 20+ video streams simultaneously.
- Video streams travel over WebRTC P2P direct connections from the camera to in-network terminals, bypassing any cloud server or DMS media node; the DMS is used only for recording archives.
- Multiple access controls—passwords, IP allow-lists, time windows—keep live-view permissions manageable and auditable.
🔐 Note: This architecture avoids the bandwidth pressure and data-leak risk of the traditional "device → public cloud → user" model, and is well suited to organizations with strict data-residency requirements.
🗺️ Unified Map Control Interface
- Supports Google Maps and OpenStreetMap to accommodate different regional data-source preferences.
- The map interface integrates the following capabilities:
- Real-time device positioning with dynamic trajectory updates;
- Device status markers (online, offline, low battery, abnormal);
- Manual capture triggering (via device button or Web/App; photos upload to the designated DMS per policy);
- Device info popups (ID, model, battery, signal strength, IP, last heartbeat);
- Tap a device icon to launch live view or play back historical recordings.
💾 DMS Collection Server — Local Deployment
- All audio/video, images, GPS tracks, and logs are pushed over encrypted channels to the customer-deployed DMS local server, with no public-internet access required.
- The DMS can be deployed in the customer intranet, a private network, or a private cloud, meeting classified-system build standards.
- As the unified management platform, BCMS centrally configures and monitors multiple DMS nodes:
🛠️ DMS Unified Policy Management
| Policy | Description |
|---|---|
| Retention period | Set recording retention per tenant, device type, or event severity (e.g., 7 / 30 / 90 days); expired data is purged automatically |
| Backup | Cross-DMS mirror backup, off-site disaster recovery, and RAID integration for higher reliability |
| Capacity alerting | When storage usage exceeds a threshold (e.g., 85%), the system alerts and can run tiered cleanup (high-priority files are retained first) |
| Compression | Long-term recordings can be auto-transcoded to H.265, saving roughly 50%–60% of storage |
| Partitioned storage | Independent storage volumes per department or case type for logical isolation and permission separation |
🔁 Playback and Smart Search
- Playback connects directly via WebRTC P2P to the DMS or the in-network node hosting the camera—no full-file download required, with fast load and low latency.
- Search historical recordings by time range, device ID, geographic location, event tag, keyword, and other combined criteria.
- Speed playback, keyframe jumping, snapshot saving, and clip export support evidence gathering and review.
- Every playback action is recorded in an audit log, with permission control and activity traceability.
💡 Cost tip: Compared with traditional solutions that rely on public-cloud object storage (e.g., AWS S3), this approach keeps all audio/video storage on the customer's premises, substantially reducing long-term cloud-storage and bandwidth spend.
📱 Remote Device Management and Configuration
- Unified firmware upgrade and version management for cameras, DMS servers, and collection boxes.
- Tenant-level firmware isolation: each tenant can upload dedicated firmware packages; the system auto-matches and distributes by device ownership, preventing cross-organization firmware misuse.
- Canary release, automatic rollback on upgrade failure, and scheduled upgrade tasks keep upgrades smooth and controlled.
- Scan a QR code to complete device binding, network configuration, DMS-address injection, and firmware locking—reducing on-site deployment effort.
- Remotely adjust recording parameters (resolution, bitrate, alarm sensitivity, auto-shutdown time) with template-based bulk push.
- Real-time reporting of device battery, signal strength, and GPS status, with automatic alerts on anomalies.
- ✅ Fingerprint check-out authentication: cameras support biometric fingerprint recognition; recording activates only after an authorized person's fingerprint is verified, binding device to user and strengthening accountability.
⚙️ Unified Policy Control (BCMS central configuration)
- Heartbeat reporting: customizable heartbeat interval (30 s / 60 s), reconnect logic, offline-cache duration.
- File upload policy: per event type (e.g., recording start, emergency button, manual capture) configure immediate vs. delayed batch upload, with max file size, compression quality, and priority-queue settings.
- Tiered storage policy: auto-classify storage by event severity:
- Routine patrol → "general library"
- Emergency / capture / conflict records → auto-tagged "high priority", protected from auto-deletion
- Case-related video → encrypted lock-down, accessible only to authorized personnel
- Offline resume: during network outages the device caches files locally and auto-resumes upload with integrity verification once reconnected.
- Power-saving: below 20% battery, non-essential features (Wi-Fi, HD recording, GPS) turn off automatically to extend runtime.
🔐 Security and Permission System
- Data in transit uses HTTPS + SRTP + DTLS encryption for end-to-end communication security.
- Multi-level role-based permissions (super admin, regional supervisor, officer, auditor, etc.) with fine-grained access and operation control.
- IP allow-list + access token + fingerprint triple authentication (fingerprint for device check-out, token for system login).
- When a device comes online, the system auto-generates a unique MQTT account and permission policy—no manual configuration.
- Integrate with LDAP, AD, OAuth2.0 and other enterprise SSO systems for unified account management.
🌐 Distributed Architecture and Deployment
- Deploy STUN/TURN service nodes to assist P2P connection setup in complex networks, improving connection success rates.
- STUN/TURN keys support periodic rotation to reduce long-term key-leak risk.
- The MQTT message service supports cluster deployment, handling hundreds of thousands of concurrent devices with response latency under 50 ms.
- All components are Docker-containerized and support Kubernetes orchestration for easy ops and elastic scaling.
- Minimal deployment: run BCMS control center on a single cloud server, with the DMS and cameras entirely inside the customer network—the cloud handles only control signaling, with no media-stream processing load.
📊 Deployment cost comparison
| Item | Traditional | BCMS |
|---|---|---|
| Cloud server | Required (incl. media relay) | Control-only server (lightweight) |
| Storage cost | High (public-cloud object storage) | Local DMS storage, no extra cloud fees |
| Bandwidth | High (bulk video upload) | Low (control commands only) |
| Data compliance | Higher risk (data egress) | Controllable risk (data stays on-premises) |
| Playback experience | Download-then-play, high latency | P2P direct, sub-second load |
📊 Multi-Dimensional Reports
| Report | Description |
|---|---|
| User activity log | Records 200+ operations—login/logout, device CRUD, permission changes—exportable to Excel |
| MQTT connection log | Tracks device/DMS/client connect-disconnect events; online duration, connection frequency, abnormal drops |
| GPS track log | Real-time track view and historical playback; archives timestamps, speed, accuracy |
| Battery log (admin) | Records device battery curves to assess device lifespan and replacement cycles |
🌍 Multi-Tenant and Multi-Language Support
- Each tenant has an independent database tablespace; data is physically isolated and non-interfering.
- Each tenant manages its own firmware versions and release policies, avoiding custom-firmware conflicts.
- Language packs (English, French, Spanish, etc.) can be uploaded in the back office and hot-loaded on the front end without restarting the service.
- Static assets use CDN caching to improve global access response times.
🤖 User-Experience Optimizations
- Adding a device or user auto-creates MQTT credentials and binds permissions, reducing manual-configuration errors.
- A permission-recommendation feature suggests default permission sets by role and device type, improving configuration efficiency.
- Standard RESTful APIs support integration with policing platforms, OA, ERP, and other third-party systems.
Applicable Scenarios
| Scenario | Value |
|---|---|
| Public-security enforcement | Full-process recording, evidence fixation, standardized conduct, fewer complaints |
| Traffic management | Traffic-patrol, violation evidence, accident investigation fully logged; greater enforcement transparency |
| Prison security | Patrol tracking, rapid incident response, full coverage of key areas |
| Large-event security | Multi-team coordinated dispatch; command-center visual monitoring and decision support |
| Enterprise internal security | Logging for inspection, warehousing, and hazardous-work personnel; stronger safety management |
| Emergency management | Responder location sharing and video feed from disaster sites; faster response |
Technical Highlights
| Highlight | Description |
|---|---|
| High compatibility | Built on mainstream open source—WebRTC, MQTT, Docker, Kubernetes—no vendor lock-in |
| Strong scalability | Scales smoothly from hundreds to hundreds of thousands of devices; modular architecture eases iteration |
| Low latency | WebRTC P2P live latency < 300 ms, playback load < 1 s |
| High availability | Dual-database hot standby, load balancing, automatic failover; 99.9% availability |
| Data localization | All audio/video, GPS, and logs stored on the customer's in-network DMS, never uploaded to the public internet |
| IoT-friendly | Lightweight MQTT supports low-power devices, offline caching, and auto-reconnect |
| Cross-platform consistency | Unified UI and interaction across Web console, mobile app, and PC client |
| Globalization | Multi-language, multi-map, multi-time-zone support for cross-border or cross-region deployment |
| Tenant firmware isolation | Each tenant manages firmware independently, avoiding cross-impact and meeting differentiated needs |
| Storage-cost optimization | Local audio/video storage significantly reduces reliance on public-cloud storage and bandwidth |
| Fingerprint check-out auth | Fingerprint activation binds device to user, reinforcing accountability |
| Centralized policy management | All device policies (storage, upload, heartbeat, power-saving) are pushed and monitored by BCMS, improving ops efficiency |
Business-Model Support
| Model | Description | Platform support |
|---|---|---|
| To-B direct | Private deployment, custom development, and dedicated ops for government and large enterprises | Independent DB, dedicated domain, audit-report export, SLA |
| B2B reseller | White-label system, admin console, device quota, and support packages for channel partners; revenue share and authorization management | Multi-tenant isolation, sub-account system, billing/split, authorization codes |
| To-C individual | Extensible to home-monitoring, outdoor-adventure, and other non-enforcement scenarios | Mobile framework ready; personal-center module reserved |
| C2C collaboration | Temporary device-access sharing between users for collaborative monitoring | MQTT temporary-permission mechanism; invitation codes and time-limited access |
Summary
The BCMS Smart Law-Enforcement Video Management Platform is built on the core principle of "control in the cloud, data on-premises", delivering a body-worn audio/video management system that balances security, compliance, and economy.
The system uses WebRTC for low-latency live view and playback, MQTT for stable massive-device access, and a local DMS for customer-controlled data—meeting the stringent regulatory requirements of public-security and judiciary industries while reducing reliance on public-cloud resources and keeping operating costs reasonable without compromising data security.
✅ Core value summary:
- Data never leaves the intranet: audio/video, GPS, and logs all reside on the customer's premises, meeting data-compliance requirements;
- Lightweight cloud footprint: only a few cloud servers are needed for control dispatch, with no media storage or relay overhead;
- Accountability: the fingerprint check-out mechanism ensures every device in use has a responsible owner;
- Centralized management: unified policy configuration, firmware management, and permission control improve ops efficiency.
ON THIS PAGE