We all know that the benefits of IP-based networked CCTV are significant compared to traditional analog systems. But the real benefit of IP video can only be realized if the solution is based on a truly distributed architecture.
Serious scalability problems arise when an IP-CCTV system is based on a Centralized Architecture. Instead, a Distributed Architecture delivers a flexible and scalable solution than can lead to systems being deployed across sites, cities and countries.
Storing IP video data
There are typically two different approaches to storing data in an IP video system. A centralized architecture uses a master database usually located in the central control room or head office. A distributed architecture spreads the data around the security management system, generally keeping it close to where it is produced or needed.
The stored data can be categorized into two types: configuration and live.
Configuration data is site information specifying the design and make-up of the security management system. Examples of configuration data include lists of cameras, lists of users, user permissions, site structure, maps representing the layout of the system and licensing information. After the initial installation and commissioning stages of a security management system, configuration data is not routinely changed. It is however routinely accessed by operators when logging into the system.
Live data is typically CCTV video recordings and alarm information. Live data is accessed continuously during normal security management operations, either by devices recording the data or operators reviewing the data.
Configuration data is usually held in a database called the Site Database. This makes it easy for administrators to make and manage changes; however it also creates a problem. When an administrator makes a change to the site database how do the users, distributed throughout the security management system, get the change?
The obvious and easy solution is to have the site database held centrally on a master database server and have all users access the master server over the network. This is called a centralized architecture.
Many systems use a centralized architecture for storing more than just configuration data. They may also use it for storing live data such as video recordings or alarm data.
Figure 1 shows a security management system consisting of one or more sites each with its own local area network (LAN) connected to a central office. The central office is also where the central file server is located, hosting the site database. Also in the central office are network video recorders (NVRs) for recording video and alarm data.
Every camera and workstation in each remote office must regularly, and in some cases continuously, communicate with the central office in order to check for changes and updates in the site database. This includes checking for valid licenses or storing recording and alarm data.
A centralized architecture causes four major problems:
- Cost: All users continuously communicate with the central office. On a local area network (LAN) that means buying expensive high-end switches and on a wide area network (WAN) it means using up precious bandwidth.
- Reliability and resilience: What happens when the WAN or core LAN switch breaks? Remote users can be left stranded with no access to the live and recorded video from cameras which are actually located locally to them on a working LAN.
- Single point of failure: What happens if the server hosting the site database fails? All users of the system rely on access to the site database, for example, to get log-in credentials verified or license permissions checked. If the site database server fails, the whole security management system goes down.
- Scalability: As more cameras and users get added to each remote office and as more remote offices get added to the network, everything gets congested. The local LANs, WAN links and central server all get congested coping with increasing levels of traffic checking for site database changes, valid licensing and storing recordings and alarms.
Figure 2 shows how the same security management network can be constructed using distributed databases.
To distribute configuration data, each remote workstation can keep a local cache of the site database. Configuration data does not change very frequently. This means the information can be synchronized between the central server and the remote workstations either according to a managed schedule or on-demand when a change happens. In the event that the central server, a core LAN switch or the WAN fails, users at workstations can continue to work using their locally cached site database.
Distributing licensing data
Rather than holding license information centrally in the central server, individual components of the security management system can hold their own licenses. For example, cameras can hold information in their on-board memory about allowed viewing and recording resolutions, or allowed frame rates. They can also hold information on which features are enabled such as advanced motion analytics.
Such a model, where the sources of the valuable data (the cameras and recorders) contain their own licenses, means that the cameras and recorders never need to talk to the central server. Because the data sources have their own distributed licenses, this frees up the data viewing applications, running on each workstation, from requiring any license at all. An operator can’t view video if the camera or recorder won’t let him. This means none of the workstations need to check licensing conditions with the central server.
Distributing live data
Rather than continuously streaming recording and alarm data back from the remote sites to the central site across the WAN, it would be much better to keep the data locally on the LAN. One or more local NVRs at each remote site would reduce traffic across the WAN and allow users at the remote sites to access recordings and alarms even when the WAN is not available.
Of course the central office is often where alarm management happens across the whole security management system so users in the central office can still access the remote NVRs in the event of an alarm or incident investigation. Usually when this happens they only need to playback or export certain portions of video from certain cameras and don’t need to access the full 24x7 recordings that have been made of all cameras at the remote site.
Less than 0.1 percent of video ever gets looked at, so why waste valuable WAN bandwidth unnecessarily? Just use the WAN to restore the pertinent recorded video data when required.
System designers and end-users should ensure that when choosing an IP video platform for their security system it is based on a distributed solution, otherwise the lack of scalability may hinder future expansion and the single point of failure could lead to unreliable operation.
Before joining IndigoVision as Chief Technical Officer (CTO) in 1999, Barry Keepence worked for over 10 years in the space industry and at 3Com as a System Architect.