Reset

Part 2: Applying Deep Learning’s Proactive Response Solutions to Address Specific Security Challenges

November 17, 2021

Hikvision HikWire blog article Part 2: Applying Deep Learning’s Proactive Response Solutions to Address Specific Security Challenges

Last week, we covered Deep Learning’s proactive security response capabilities, which run the gamut from license plate recognition to mask detection, and encompass human and vehicle detection, queue management, auto object tracking and more. Deep Learning capabilities are broad and offer enhancements that solve security challenges. In today’s blog, we’ll cover some considerations in the selection process and delve into specific types of applications — such as entry points — and how Deep Learning algorithms offer a more effective solution. 

The process of implementing Deep Learning-fueled security systems starts by selecting the right combination of partners who can deliver the best combination of products and software, and integrate and implement them to address your specific needs and areas of focus.

Typical applications for these powerful and versatile new Deep Learning embedded solutions include:

  • Location: Entry/Egress points pose a complex challenge for organizations across all verticals that need to maintain open and nurturing environments yet need to be controlled to deter and prevent unwanted visitors. This applies to both people and vehicles entering a property, campus, or facility. The ability to automatically differentiate between various moving objects and classify them enables specific policy driven triggers to be implemented for specific locations and times of day. Personal identification and authentication are also a major issue, more so than ever before with the new and emerging demand for contact tracing.

    - Application: Touchless video and biometric technologies provide a multi-tiered solution for better surveillance, access control and visitor management applications that improve both physical security and workforce management operations, especially when used for highly accurate time and attendance applications. Biometric solutions with embedded thermal imaging can also be deployed for health safety and compliance, further leveraging their ROI potential. The integration of analytics either embedded in end-point devices like cameras and access control readers, or through centrally applied software via an intelligent video management system (VMS) provide new and advanced levels of protection for entry/egress at virtually any facility.  
     

  • Location: Interior stairwells and hallways pose a unique surveillance challenge given their inherent narrow and often long physical dimensions. Cameras with Deep Learning powered processing that offer acute light sensitivity and vertical orientation resolve longstanding surveillance issues in these spaces by providing the best perspective to visually monitor long and narrow hallways. With the addition of new intelligent analytics, cameras in hallways and stairwells can now be used for a variety of applications like violence or bullying detection, and to locate specific individuals or objects within a facility based on specific characteristics such as clothing type and color, accessories like hats and eyeglasses, and more.

    - Application: Intelligent analytics fueled by Deep Learning can be used to locate lost children in airports or shopping malls or help locate elderly patients who may have wandered off-site unnoticed. Policy-driven alerts can be set to automatically notify authorized personnel of specific incidents that require their immediate attention.
     

  • Location: Parking garages and open areas present their own set of challenges given with varying levels of permissions and access. In addition to detecting unauthorized vehicles, damage to vehicles can easily be investigated based on specific detection and search parameters.

    - Application: Vehicle access control employing License Plate Recognition (LPR) analytics can alleviate the need for physical gatehouses and/or guards to physically patrol parking areas, and help reduce costs and liabilities resulting from vandalism, theft, robbery, and even physical harm to individuals.  

Depending on your industry classification, virtually all these new Deep Learning-driven solutions are available in a variety of affordable products from leading suppliers like Hikvision. More important, these solutions are already proving to deliver tangible Return on Investment (ROI) with low Total Cost of Ownership (TCO). It’s a win-win for both end-users, as well as security integrators and resellers with the knowledge to integrate these new solutions for their customers.

To determine the best Deep Learning security system for your application, contact your local representative. Or contact Hikvision here for more information.

IMPORTANT! This model requires non-standard firmware. Do Not Install standard firmware (e.g. v.4.1.xx) on this model. Doing so will permanently damage your system. You must use custom firmware v.4.1.25 from the iDS-9632NXI-I8/16S product page.

View the most updated version of this document here:

https://techsupportca.freshdesk.com/en/support/solutions/articles/17000113531-i-series-nvr-firmware-upgrade-instructions

 

The I-series NVR (such as the DS-7716NI-I4) is one of Hikvision's most popular and feature-rich recorders. As such, many firmware revisions have been introduced over the years to continually ensure the product is compatible with the newest technology available. Due to the many revisions, we recommend that the user closely follows the instructions below in order to reduce the amount of time spent as well as the chance of failure.

 

Database Optimization and Repair

As more affordable IP cameras are introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.

 

After upgrading to v4.X, the recorder database will need to be converted and optimized. If you are experiencing issues where playback is expected but not found, make sure "Database Repair" is performed as indicated in the procedures and scenarios below.

 

Preparing the Upgrade

Before proceeding with upgrade, it is recommended that NVR configuration file is exported from the NVR over the network or on to a local USB drive.

 

Upgrading from v3.4.92 build 170518 or Older

  1. All recorders must reach v3.4.92 before proceeding further. Upgrading from versions before v3.4.92 directly to any version of v4.X will likely cause the recorder to fail.
  2. If the recorder is already at v3.4.92, a full factory default is highly recommended before upgrading to any version of v4.X. There is a high chance of unit failure (requiring RMA) if the unit is not defaulted before upgrade.
  3. After reaching v3.4.92 and performing a full factory default, an upgrade directly to v4.50.00 is acceptable.
  4. After the upgrade is completed and the recorder is reprogrammed, it may be beneficial to perform a Database Repair. For details, refer to the section "Database Optimization and Repair" above.
  5. To verify repair progress, you may refer to the HDD status, or search the recorder log for repair started and stopped entries. Note that while the HDD is repairing, new recordings are still being made, but some existing recordings may not be searchable until repair is complete.
  6. If you continue to observe playback issues after database repair, ensure there are no power, network, or motion detection issues. Should the problem persist, contact technical support.

 

Upgrading from Any v4.X Build to v4.50.00.

  1. Any v4.X build can be upgraded directly to v4.50.00.
  2. Export configuration is highly recommended before performing the upgrade.
  3. If upgrading from any v4.X version that was not v4.22.005, a Database Repair is recommended. Refer to Step 4 and onwards in the previous section.

 

Downgrading

Downgrading is not recommended. Due to new features and parameters constantly being added, downgrading may cause the NVR to factory default itself or require a manual default to operate properly.

View the most updated version of this document here:
K-Series DVR upgrade instruction
The Turbo 4 Hybrid DVR K series has multiple models and across different platform and chipset. It also has similar firmware development of other recording product line; DVR K series has also introduced the GUI4.0 to ensure the series to be compatible to the newest technology available. The new database architecture is also brought into the DVR firmware v4.0 to be future proof and for better recording search experience. 
 


Database Optimization and Repair

As more affordable cameras introduced over time with greater video resolution and data sizes, more efficient database management also becomes necessary. The introduction of firmware v4.0 brought about a new database architecture in order to be futureproof.
After upgrading to v4.X, the recorder database will need to be converted and optimize. If you are experiencing issues, where playback is expected but not found, please make sure to perform "Database Rebuild" as indicated in the procedures and scenarios below.
 


Preparing the Upgrade

Before proceeding with upgrade, it is recommend exporting DVR configuration file from the DVR over the network or on to a local USB drive.

 

Action after firmware upgraded 

1. Upgrade the DVR according to the chart above. 

2. Reconfirming Channel's Recording Schedule 

    - Confirm channel's recording schedule is enable. 

    - Check if the channel is on correct recording schedule.

3. Double Check Storage Setting

    - Make sure all channel are assigned to record on its HDD group when the Storage setting is under Group Mode. 

4. Perform Database Rebuild locally. 

    • Some version above support Database Rebuild via web access - K51 and K72

    • Perform Database Rebuild regardless if system is having any database issue symptom. 

    • Database Rebuild process is average ~30 to 60min per TB. The process may still varies depends recording data.

    • After Database Rebuild - Check log to confirm Database Rebuild has went thru properly. 

    • If Database Rebuild Started and Stopped log has been log only within few minutes. Database rebuild may not has been completed properly. It is strongly recommend performing the Database Rebuild again.

    • To check log > System > Log > Information > Database Rebuild Started and Stopped.

    • If the log option is not available - access system via SSH can also obtain similar result.

5. Recording Data is still missing after database rebuild process. 

If the data has not been recorded or has been overwritten, Database rebuild process is not able retrieve those lost data. Have the system upgraded to the latest available firmware version above to prevent any future data lost is strongly recommended for all application.

 

 

 

 

In light of the global semiconductor shortage, Hikvision has made some hardware changes to the DS-76xxNI-Q1(2)/P NVRs, also known as “Q series.”

 

These changes do not have any effect on the performance, specifications, or the user interface of the NVRs. For the ease of reference, these modified units are known as “C-Version” units. This is clearly indicated on the NVR label and on the box by the serial number.

 

The only difference between the “C-Version” and “non-C-Version” is the firmware. The firmware is not interchangeable:

 

  • The C-Version NVRs must use firmware version v4.31.102 or higher.
  • The non-C-Version (Q series) NVRs must use firmware version v4.30.085 or older.

 

Please do not be alarmed if a “Firmware Mismatch” message pops up on the screen during the firmware upgrade. This simply means that the firmware does not match the NVR’s hardware. Simply download the correct firmware and the upgrade will go through without any issue.

In light of the global semiconductor shortage, Hikvision has made some hardware changes to the Value Express Series NVRs

These changes do not have any effect on the performance and specification of the recorders. For ease of reference, these modified units are known as “C-Version” units. This is clearly indicated on the NVR label and on the box by the serial number.

The only difference between the “C-Version” and “non-C-Version” is the firmware. The firmware is not interchangeable:

  • The C-Version NVRs must use firmware version v4.30.216 or higher.
  • The non-C-Version (Q series) NVRs must use firmware version v3.4.104 or older.

Please do not be alarmed if a “Firmware Mismatch” message pops up on the screen during the firmware upgrade. This simply means that the firmware does not match the NVR’s hardware. Simply download the correct firmware and the upgrade will go through without any issue.

By downloading and using software and other materials available via this website, you agree to be legally bound by HIKVISION General Terms of Use . If you don’t agree to these terms, you may not download or use any of those materials.

If you are agreeing on behalf of your company, you represent and warrant that you have legal authority to bind your company to the General Terms of Use above. Also you represent and warrant that you are of the legal age of majority in the jurisdiction in which you reside (at least 18 years of age in many countries).