Native vs. cross-platform: business effects in video surveillance protocols

Native vs. cross-platform: business effects in video surveillance protocols

IP camera-based security systems have brought many new benefits to the market since their introduction, but development has not always been smooth sailing. For decades, video surveillance designers have been faced with equipment compatibility issues.

A single international protocol was supposed to solve this problem by combining products from different manufacturers within one system, including high-speed PTZ cameras, devices with varifocal lenses and zoom lenses, multiplexers, and network video recorders.

However, to date, the native protocols of video equipment manufacturers remain relevant. Even in the Ivideon Bridge device, which allows you to connect ≈98% of camera types to the cloud, we provide special capabilities when working with native protocols.

Why this happened and what advantages native protocols have, we will further explain using the example of integration with Dahua Technology.

Single standard

Native vs. cross-platform: business effects in video surveillance protocols

Historically, creating the most efficient system that combines best-in-class solutions from a number of vendors has required a huge amount of integration work.

To solve the problem of equipment incompatibility, the Open Network Video Interface Forum standard was developed in 2008. ONVIF allowed designers and installers to reduce the time spent setting up all video system components.

System integrators and end users were able to save money using ONVIF due to the free choice of any manufacturer when scaling the system or partially replacing individual components.

Despite the support of ONVIF from all leading video equipment manufacturers, almost every major company still has a native protocol native to each camera and video recorder of the manufacturer.

Dahua Tech has many devices that support both onvif and the proprietary Dahua private protocol, which Dahua uses to build complex security systems based on its own equipment.

Native protocols

Native vs. cross-platform: business effects in video surveillance protocols

The absence of any restrictions is the advantage of native development. In the built-in functions, the manufacturer focuses on those “features” that it considers the most important, supporting all the capabilities of its own hardware.

As a result, the native protocol gives the manufacturer more confidence in the performance and security of the device, as it ensures maximum efficiency in the use of hardware resources.

This is not always good - and the huge number of cameras from Aliexpress that work using simply “leaky” and open protocols, “exposing” traffic to the whole world, is clear evidence of this. With manufacturers like Dahua Technology, who can afford to test systems for security for a long time, the situation is different.

The native IP camera protocol allows for a level of integration that is not achievable with ONVIF. For example, when you connect an ONVIF-compatible camera to an NVR, you need to find the device, add it, and then test the operation in real time. If the camera “communicates” using the native protocol, then it is detected and connected to the network automatically.

Sometimes when using a recorder with a third-party camera, you may notice a deterioration in picture quality. When using native protocols for devices from the same manufacturer, this problem, in principle, does not arise even when transmitting a signal over a cable of up to 800 meters (with Extended Power over Ethernet technology).

This technology was created and introduced by Dahua Technology. ePoE (Power over Ethernet) technology overcomes the limitation of traditional Ethernet and POE (both limited to 100 meters between network ports) and eliminates the need for PoE devices, Ethernet extenders, or additional network switches.

Using 2D-PAM3 encoding modulation, the new technology delivers power, video, audio and control signals over long distances: over 800 meters at 10 Mbps or 300 meters at 100 Mbps via Cat5 or coaxial cable. Dahua ePoE is a more flexible and reliable video surveillance system and allows you to save on installation and wiring.

Integration with Dahua Technology

Native vs. cross-platform: business effects in video surveillance protocols

In 2014, Ivideon began collaborating with the company Dahua, which is one of the leading video equipment manufacturers in the world, owning second largest share of the global security systems market. Currently Dahua which usually takes second position in the ranking of companies with the largest sales a&s Security 50.

The close interaction of our companies has made it possible to implement the integration of many equipment platforms, totaling thousands of models of network cameras and video recorders.

In 2017, we developed a solution that allows you to connect standard and high definition analog cameras to the cloud using Dahua HDCVI DVRs.

We also managed to provide easy mechanics for connecting any number of Dahua cameras to the cloud, regardless of their geographic location, without using DVRs, PCs or additional software.

In 2019, we became strategic partners within the DIPP (Dahua Integration Partner Program) – a program for technology cooperation aimed at joint development of complex integrated solutions, including video analytics solutions. DIPP provides priority design and technical support for joint products.

Dahua's support at all stages of creating new products allowed us to interact with the native protocol in different solutions. One of the most interesting gadgets of the last year is Ivideon Bridge, through which we were able to achieve compatibility with Dahua cameras at the level of their “native” device.

Where does the “bridge” lead?

Native vs. cross-platform: business effects in video surveillance protocols
Bridge is a gadget the size of a small Wi-Fi router. This box allows you to connect up to 16 cameras of any kind to the Ivideon cloud. This means that users of local systems get access to the cloud service without replacing installed equipment. You can even add analog cameras to the cloud through a video recorder connected to Ivideon Bridge.

The cost of the device today is 6 rubles. In terms of price/channel ratio, Bridge has become the most profitable way to connect to the Ivideon cloud: one channel with Bridge with paid basic archive storage from Ivideon will cost 000 rubles. For comparison: when purchasing a camera with access to the cloud, the cost of one channel will be 375 rubles.

Ivideon Bridge is not just another DVR, but a plug-and-play device that greatly simplifies remote administration via the cloud.

One of the interesting features of the “bridge” is full support for the native Dahua protocol. As a result, Bridge has been enriched with functions that have a direct impact on the effectiveness of video surveillance systems.

Bridge's native and cross-platform features

Local data recording

Edge Storage operating mode is available for all Dahua cameras and DVRs connected via Bridge using the native protocol. Edge lets you record video directly to your internal memory card or NAS. Edge Storage provides the following flexible recording tools:

  • saving network and storage resources;
  • complete decentralization of data storage;
  • optimizing bandwidth usage;
  • creating a backup backup of the archive in case of connection failure;
  • savings on cloud archive: it is enough to install a junior tariff plan - for example, the minimum annual cost for 8 cameras in the cloud will be only 1 rubles/month or 600 rubles/year.

Available only via the native protocol, Edge mode is a hybrid recording solution that, on the one hand, reduces the business risks associated with a sudden connection loss, and on the other hand, allows you to save on high traffic costs.

Setting up OSD and backlight

Native vs. cross-platform: business effects in video surveillance protocols

Ivideon Bridge provides access to setting the overlay of arbitrary text, date and time on an image (On Screen Display, OSD).

As you drag, text and date marks "stick" to an invisible grid. This grid is different for each camera, and depending on where in the image the label is located, the actual position of the overlaid text may be calculated differently.

When you turn off text or date overlays, their settings are saved, and when you turn them on, they are restored.

The settings available on a specific camera depend on its model and firmware version.

Motion detector operating parameters

Native vs. cross-platform: business effects in video surveillance protocols

The system allows you to quite sensitively change the operating parameters of the motion detector, including setting an arbitrary detection zone.

Changing video stream parameters

Native vs. cross-platform: business effects in video surveillance protocols

Adjusting the parameters of video and audio streams will help reduce the load on the Internet channel - you can “cut” a number of values ​​and save on traffic.

Microphone setup

Native vs. cross-platform: business effects in video surveillance protocols

As with video streaming, microphone settings provide access to a sensitivity scale that allows you to optimize the use of the device inside noisy rooms.

Conclusion

Bridge is a universal device that has the ability to expertly configure camera connections. This mode will be required if you plan to connect an old recorder or camera to the cloud that cannot be detected automatically.

Due to the flexibility of Bridge settings, the user can easily cope with situations when the IP address, camera login/password changes, or the device is replaced. By changing the camera, you will not lose the previously recorded video archive in the cloud and the already paid subscription to the service.

And although Bridge allows you to work with ONVIF and RTSP at an expert level, without exhausting the user with “first time in the Boeing cockpit” level settings, the greatest “return” from the cameras can be felt with deep integration, as can be seen in the example of support for native Dahua Technology protocol.

Source: habr.com

Add a comment