Professional Documents
Culture Documents
IP Technologies
The following diagrams depict the basic setup of an analog camera system and a network-based,
or IP camera system.
In the traditional analog CCTV application, security cameras capture an analog video signal and
transfer that signal over coax cable to the Digital Video Recorder (DVR). Each camera may be
powered by plugging in the power supply right at the camera or by using RG59 Siamese cable
which bundles the video and the power cables. The DVR converts the analog signal to digital,
compresses it, and then stores it on a hard drive for later retrieval. Intelligence is built into the
DVR to handle such things as scheduling, motion detection, and digital zoom. Monitors for
viewing the video are connected to the DVR, or it can be set up to publish over an internal
network for viewing on PCs. The DVR can also be set up to broadcast over the Internet and can
add password protection and other features. When broadcasting over the Internet, the video for
all of the cameras is transmitted as one stream (one IP address). Therefore, it is very efficient.
In the IP world, each network camera captures an analog image but immediately converts it to
digital inside the camera. Some digital processing can happen right at the camera, such as
compression and motion detection. The digital video stream is then broadcast over the IP
network using Ethernet (CAT5) cable. The power supply may be plugged in at the camera or can
be run over the ethernet cable by using Power-Over-Ethernet (POE) adapters. The CAT5 cable
for each camera is plugged into a switch which feeds into the network hub. As with all network
devices, some set-up needs to be done for each network camera to set up its IP address and other
identifying attributes.
Software is required on each PC that you want to view the cameras or playback video. Another
high powered PC is set up with the appropriate software to record the cameras. Since
communication standards are not consistently followed in this industry yet, the viewing and
recording software must be purchased from the same vendor that sells the IP cameras. This can
make switching or mixing camera vendors very expensive.
The IP camera signal is broadcast over the Internet in the same way that a DVR signal is.
However, each camera is a separate stream and has its own IP address or port. This can greatly
affect bandwidth as we'll see below. When viewing remotely each camera can be pulled up
individually by its IP address. If you want to see all of the cameras side-by-side, additional
software (again, from the same camera vendor) must be installed.
To make bandwidth matters worse for IP - many of the newest IP cameras are coming out with
'megapixel' resolution. This is wonderful from the standpoint of how much clarity and field-ofview can be captured, but it comes at a huge price to bandwidth. A single 2-megapixel IP camera,
running 30 fps with MPEG4 compression will use a whopping 6.5Mbps of bandwidth. These
high-resolution IP cameras also require a great deal of hard drive space to store the video. The 2megapixel camera described above would require approximately 67 Gigs of hard drive space to
record one day's worth of video.
It's worth noting that DVRs will also use bandwidth if viewed remotely over a network.
However, the DVR will only use bandwidth if people are currently viewing the cameras.
Otherwise, they will not. Furthermore, a DVR will combine several camera images into one
video stream vs. a separate video stream for each camera, as in IP. For example, a typical 16
camera DVR will combine its camera images and throttle its output to a maximum 360Kbps. To
run 16 similar IP cameras on a network would generate about 11Mbps
cameras for internet viewing using a DVR because access is provided to all cameras at once by
using one external IP address to the DVR.
Network failure ? Only poorly defined systems/networks tend to fail. A properly built and
configured network is among the most reliable components of an organization. Why else would
any and every major organization and entity rely on networks to transfer information and
valuable data?
The burden put on a network by an IP CCTV system, is not purely the fact its IP, but rather the
type of components put on it, and the actual configuration of the network. Again, poorly
configured networks will consume far more resources than properly configured ones.
As for components put on the network, there is no common standard in cameras, in compression
algorithms, in image quality, in fact there is no common ground whatsoever on IP cameras. Some
manufacturers even call mjpeg a digital compression algorithm. Point is that there is an
enormous difference in bandwidth (and thus in network load) between different IP cameras, even
amidst cameras of a same brand! Chosing a proper IP camera, with decent H.264 compression,
and a proper implementation of this algorithm, will deliver bandwidth for effective network
efficient streams.
If high numbers of devices need to be implemented, a multicast network should be considered.
If multiple, external or public network connections need to be defined, a trancsoding engine
should be considered, as correctly suggested.
Decentralised architectures, edge-enabled systems, as opposed to client server architectures,
could indeed be defined as slightly more reliable, simply due to their configuraiton. However,
even in typical IP environments (which are here referred to as client/server) back-up storage, failsafe recording, guaranteed functioning, failover network, dual ring configurations, etc, can be
foreseen, with the same limited cost! This client/server architecture is actually also the result of
the lacking of any common denominator or language in IP CCTV so far. Hopefully, ONVIF or
PSIA will solve this issue going forward. At that time, all units and all devices should be capable
of communicating directly with one another, thus creating the absolute key advantage of an IP
system.
As for the example of a 750 camera system, and the cost estimation: first and foremost, the
points mentioned are correct indeed of course; network performance, servers costs, CPU
requirement for analytics, etc, etc, all put high demands and thus high costs for the system!
However, at this moment the only environments where I have found 750 cameras running on one
single LAN network, storage being centralised in one single location, is either an airport or a
casino. Both are high risk, high security facilities, where cost of the CCTV system is less
dominant, to say the least.
Any enterprise, where the security director or the integrator, has the least bit of common sense,
will distribute their architecture, thus pushing processing, recording, storage, etc as far to the
edge as possible. The least one will do in such projects, is to create different nodes or clusters,
each of which function on their own.
The specification, and thus also the cost, of a decoding server, is again related to the lack of a
common algorithm: the burden to decode an mpeg-4 or H.264 stream is again heavily
dependent on the quality of this stream, or the way the compression algorithm is implemented.
When using good cameras, one can achieve a high number of streams onto one single
machine, thus displaying up to almost 100 streams on a single machine. All however depends on
the cameras, their compression algorithm, the way it has been implemented, etc etc.
As for driving video walls, the limits there are defined by video wall manufacturers, rather then
by IP CCTV manufacturers. Having said this though, it is true that you do not necessarily need
expensive multiple units, decoders, and video wall drivers. Far more effective (and cheaper)
solutions exist in the market today!
The concept of the ICR seems somewhat contradictory to the statements made earlier on
distributed architecture: with such ICR, one puts all functions into the camera itself, and the
camera is actually referred to as a server. What processor(s) are used ? How much heat is
dissipated ? How much noise is generated ? What are operational specs for such device ? What
dimensions will such device have ? With the definition of this ICR, it is again referred to failure
of the TCP/IP structure or the network. Repeating the first question, how often do we actually
still see true network failures?? Does this ICR have 2 processors? Which? FPGA so they are field
upgradeable ? Or ASIC which means they arent? How is licensing handled/stored/managed?
Most interesting aspect of this whole paper: there is no mentioning or referral whatsoever to
non-IP parts. The only key message I find in this paper is that of a distributed architecture, vs a
centralized one, no more, no less.
All in all, one might argue that several things hold true, that there are numerous reasons to
remain with old analogue technology, that IP isnt necessarily the answer to all our concenrs
and questions. However, the drive to this new technology, which I prefer to call the merger into
IP, in line with what happens all around us, is simply forced onto us by the market itself! Every
product or technology we use in our CCTV business, is a direct derivative from a consumer
product (VCR, CCTV camera, DVR, NVR, ..). So in this respect, our industry simply follows
developments of consumer electronics. So as for what the future brings us: simply look at
consumer markets; access anywhere, anytime; full wireless systems; broad bandwidths available
all around; massive data transfer over (even public) networks; full HD television; multi mage
pixel cameras (still as well as moving images), ever increasing HDD sizes; ever longer storing of
images; gigabit networks even in residential environments; .
The industry is simply going digital, full stop. Look at Sony for example, worlds biggest
manufacturer of sensors. For several years already, no more R&D is spent on traditional sensors;
all investment are going into digital technology. So even if one would want to remain with
analogue, the industry will simply prevent this. This evolution, combined with price decrease of
digital technology components (network cost, switches, routers, PC, servers, HDD, storage, )
shows that the shift towards a complete digital world is simply inevitable.
The point of an end-to-end solution vs multi-vendor solutions is to my belief a key
advantage of the IP world: one can pick and chose various parts and components, and create his
solution with different building blocks from different vendors. This way, the customer is ensured
he has a solution that perfectly meets his demands, that fits his requirements perfectly, and that
offers the best price/quality ratio. Manufacturers in their turn can focus on their core
competences, and develop strong VMS systems, high quality IP cameras, cost effective storage
systems, new processing & analytics algorithms. When (not if) we have common standards in
our industry, customers will be able to simply pick and chose products, systems and solutions,
and have the ability to easily connect them together.
To read the original articles about the analogue Vs IP CCTV debate and receive a free cost
breakdown for a 750 camera system (mentioned as an example in the original article by Mike
Newton), click here.
Do you currently have an existing analogue (all cameras which are still wired
back to DVR or VCR via Coaxial Cable) CCTV System installed at your
premises?
Would you like to invest into something future proof - and not into an agingsoon out of date technology - avoiding repetitive investments in the near
future?
Would you like to invest into a state of the art system, but not abandon the
current system completely, not rendering it a mis-investment?
We can incorporate all your existing cameras into our modern state of the art
system
Have the option of replacing Analogue Cameras with IP Cameras 'bit by bit' as
the need arises
Many more...