HCIP-Intelligent Vision V1.0 Lab Guide

Huawei Intelligent Vision Certification Training
HCIP-Intelligent Vision V1.0

Video Site Installation,
Deployment, and
Commissioning Experiment
Guide
ISSUE:1.0
HUAWEI TECHNOLOGIES CO., LTD.
1
Copyright © Huawei Technologies Co., Ltd. 2020. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means
without prior written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their
respective holders.
Notice
The purchased products, services and features are stipulated by the contract made
between Huawei and the customer. All or part of the products, services and features
described in this document may not be within the purchase scope or the usage scope.
Unless otherwise specified in the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been
made in the preparation of this document to ensure accuracy of the contents, but all
statements, information, and recommendations in this document do not constitute a
warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
Huawei Prorietary and Confidential

Copyright © Huawei Technologies Co,Ltd
HCIP-Intelligent Vision V1.0 Experiment Guide Page 1
Huawei Certificate System

Huawei Certification is an integral part of the company's "Platform +
Ecosystem" strategy, and it supports the ICT infrastructure featuring "Cloud-
Pipe-Device". It evolves to reflect the latest trends of ICT development.
Huawei Certification consists of three categories: ICT Infrastructure
Certification, Platform and Service Certification, and ICT Vertical Certification,
making it the most extensive technical certification program in the industry.
Huawei offers three levels of certification: Huawei Certified ICT Associate
(HCIA), Huawei Certified ICT Professional (HCIP), and Huawei Certified ICT
Expert (HCIE).
With its leading talent development system and certification standards,
Huawei is committed to developing ICT professionals in the digital era,
building a healthy ICT talent ecosystem.
HCIP-Intelligent Vision is intended for Huawei regional offices, frontline
engineers at representative offices, and other technicians who want to learn
Huawei Intelligent Vision. HCIP-Intelligent Vision certification covers Huawei
Intelligent Vision platform construction, advanced service commissioning,
Huawei HoloSens Software-Defined Camera (SDC) technical principles,
intelligent algorithm management and application, and video cloud
technologies.
The Huawei certification system introduces the industry, fosters innovation,
and imparts cutting-edge ICT knowledge.
About This Document
Overview
This document is applicable to the candidates who are preparing for the HCIP-Intelligent
Vision exam and the readers who want to learn the intelligent vision basics, installation
and deployment, and standard protocols.
Description
This document consists of seven chapters. Chapter 1 describes how to install the
PowerCube500, Chapter 2 describes how to install and deploy cameras, and Chapter 3
describes how to install the photovoltaic (PV) module, lightning rod, and pole. Chapter 5–
7 describe how to commission an integrated video site, including how to commission the
PowerCube 500D, situation awareness camera, facial recognition camera, and license plate
recognition camera.
Background Knowledge Required

To fully understand this course, the readers should have basic knowledge about intelligent
vision and be familiar with Huawei intelligent vision devices.
Experiment Environment Overview
Networking
This experiment environment is intended for video site engineers who are preparing for
the HCIP-Intelligent Vision exam. Each experiment environment consists of two to six
cameras, one to two PowerCube 500s, one access switch, and one to four computers, and
is applicable to four to 12 trainees.
Device
 The following table lists the recommended device configurations in each experiment
environment, including the device name, model, and software version:
Device Model Software Version
Camera X series, M series, V100R019CX0

D series
PowerCube 500 S7006-300H1
Access switch S5700
Computer Internet Explorer/Google Chrome
Experiment Environment Preparation
Checking Devices
Before starting the experiment, check whether all required devices are ready. The following
table lists the required devices.
Device Quantity Remarks
Camera 2 for each group
PowerCube 500 1
Laptop or desktop computer 1 for each group
Twisted pair 4 for each group
iClient/SDC Intelligent Management System (SiMS) tool 1
Preparing Installation Tools

Figure 1-1 Installation tools
Experiment Topology
Contents
Overview ............................................................................................................................................................................................ iii

Description ........................................................................................................................................................................................ iii
Background Knowledge Required ............................................................................................................................................ iii
Experiment Environment Overview ......................................................................................................................................... iii
Experiment Environment Preparation ..................................................................................................................................... iv
1 Installation of the PowerCube 500 ................................................................................................. 8
1.1 Introduction ................................................................................................................................................................................ 8
1.1.1 About This Experiment ....................................................................................................................................................... 8
1.1.2 Objectives ................................................................................................................................................................................ 8
1.1.3 Site Types ................................................................................................................................................................................ 8
1.1.4 Site Installation Procedure ..............................................................................................................................................10
1.2 Experiment Task .....................................................................................................................................................................11
1.2.1 Installation Roadmap ........................................................................................................................................................11
1.2.2 Installation Procedure .......................................................................................................................................................11
2 Camera Installation ............................................................................................................................17
2.1 Introduction ..............................................................................................................................................................................17
2.1.1 About This Experiment .....................................................................................................................................................17
2.1.2 Objectives ..............................................................................................................................................................................17
2.1.3 Camera Installation Procedure ......................................................................................................................................17
3 Installation of the PV Module, Lightning Rod, and Pole ........................................................20
3.1 Introduction ..............................................................................................................................................................................20
3.1.2 Objectives ..............................................................................................................................................................................20
3.1.3 Procedure of Installing Pole Components .................................................................................................................20
4 PowerCube 500 Commissioning.....................................................................................................32
4.1 Introduction ..............................................................................................................................................................................32
4.1.2 Commissioning Roadmap ................................................................................................................................................32
4.1.3 Commissioning Steps ........................................................................................................................................................33
5 Commissioning of a Situation Awareness Camera ..................................................................35
5.1 Introduction ..............................................................................................................................................................................35
5.1.3 Commissioning Procedure ...............................................................................................................................................35
6 Commissioning of a Facial Recognition Camera .................................................................43

6.1 Introduction ..............................................................................................................................................................................43
6.1.3 Commissioning Procedure ...............................................................................................................................................44
7 Commissioning of a License Plate Recognition Camera ..................................................51
7.1 Introduction ..............................................................................................................................................................................51
7.1.3 Commissioning of an ePolice Camera ........................................................................................................................54
7.1.4 Commissioning Procedure for a Standard Checkpoint Camera ........................................................................57
7.1.5 Commissioning Procedure for a Checkpoint Camera............................................................................................58
1 Installation of the PowerCube 500
1.1 Introduction
1.1.1 About This Experiment
This experiment uses Huawei integrated video site as an example to describe how to install
and deploy components of a video site.
1.1.2 Objectives
Understand how to install and deploy the PowerCube 500.
1.1.3 Site Types

 By power supply mode, integrated sites are classified into mains power, solar-grid
hybrid, and solar-only solutions.
 Solar-grid hybrid: mains + solar + lithium battery
Table 1-1 Configurations in the solar-grid hybrid scenario
Item Description
Functional module S7006-300H1
Lithium battery A maximum of two CBM20E-N14A1 modules can be installed.
Pole Solar pole
PV module Two PV modules

Figure 1-1 Networking in the solar-grid hybrid scenario

1.1.4 Site Installation Procedure
Figure 1-2 Site types

1.2 Experiment Task

1.2.1 Installation Roadmap
Huawei integrated site is used as an example to demonstrate the hardware installation
and deployment of a front-end video site.
Figure 1-3 Integrated site installation flowchart
1.2.2 Installation Procedure

Routing cables through the pole
Step 1 Place the pole on a wooden case or a similar object.

Step 2 Route a pull wire.
Step 3 Route cables.
 PMP microwave cables can be used only in scenarios where the PMP microwave is adopted.
 The cables routed from the pole cable hole have a length of 1.5 m reserved.
 The object where the pole is placed should be able to bear a load of at least 700 kg and at
least 850 mm high.
Figure 1-4 Routing cables through the pole

Installing the battery cabinet and functional module (solar-only scenario)
 At least three people should work together during installation.

 Wear gloves during installation.
 Do not place a function module with its bottom against the ground.
 Do not install with power on.
 Ensure that the angle between the battery cabinet and function module and the line
vertical to the ground is within 10 degrees.
 The paint on the battery cabinet and function module exterior should be intact. If
paint has flaked off, repaint the area to avoid corrosion.
Figure 1-5 Installing the battery cabinet and functional module
There are three types of screw rods for installing the pole mounting kit. Choose the screw rods
that fit the pole diameter at the installation position.
Pole Diameter at the Installation Position (mm) Screw Rod Length (mm)
105–140 150
140–175 190
175–210 230
Figure 1-6 Installing the battery cabinet and functional module
Routing cables through cantilevers
 PMP microwave cables can be used only in scenarios where the PMP microwave is adopted.
 Reserve a length of 1.5 m for the cable routed out of the pole cable hole, and reserve a length
of 0.5 m for the cable routed out of the cantilever cable hole.
 The object where the pole is placed should be able to bear a load above 700 kg.
Figure 1-7 Routing cables through cantilevers
Installing cantilevers
Figure 1-8 Installing cantilevers
----End
2 Camera Installation
2.1 Introduction
This experiment uses Huawei integrated video site as an example to describe how to install
and deploy cameras at an integrated video site.
2.1.2 Objectives
Understand how to install and deploy different types of cameras during integrated video
site installation.
2.1.3 Camera Installation Procedure
Figure 2-1 Camera installation flowchart
1.1.1.1 Installing a Box Camera

To install a box camera on the wall, perform the following steps:
Step 1 Place the wall-mount bracket in the desired installation position. Use a marker to
mark the screw installation locations. Use a claw hammer to install white expansion
sleeves into the holes.
Step 2 Use screws to fix the wall-mount bracket to the wall.

Step 3 Loosen the screws on the universal joint for the universal joint to rotate freely. Fix
the shield on the universal joint, adjust the shield position, and tighten all the screws
on the universal joint.
Figure 2-2 Wall-mounted installation of a box camera
----End
2.1.3.2 Installing a Bullet Camera

To install a bullet camera on a beam, perform the following steps:
Step 1 Install the universal joint in hole 2 of the pole-mount bracket. Fix the camera on the
universal joint using the screws marked with 1, adjust the horizontal and vertical
shooting angles, and tighten all the screws on the universal joint.
Step 2 Route three hose clamps through the installation holes on the pole-mount bracket,
place the hose clamps around the beam, and tighten them up. Adjust the shooting
angle and tighten all screws on the universal joint to secure the universal joint. Then
adjust the position of the sun shield marked with d.
Figure 2-3 Beam-mounted installation of a bullet camera
----End
2.1.3.3 Installing a PTZ Dome Camera

To install a PTZ dome camera on a pole, perform the following steps:
Step 1 Align the tapped holes on the wall-mount bracket with those on the pole-mount
bracket, and tighten the screws.
Step 2 Open up the three hose clamps and thread them through the installation holes on
the pole mount.
Step 3 Thread the cables that need to connect to the pigtails of the PTZ dome camera
through the pole-mount bracket and wall-mount bracket. Place the clamps around
the pole, tighten the clamps, and secure the pole-mount bracket to the pole.
Figure 2-4 Pole-mounted installation of a PTZ dome camera
----End
2.1.3.4 Installing a Fixed Dome Camera in the Ceiling

To install a fixed dome camera in the ceiling, perform the following steps:
Step 1 Thread the cables that need to connect to the pigtails of the fixed dome camera
through the pendant-mount bracket. Thread the four expansion bolts through the
four screw holes on the base of the pendant-mount bracket and tighten the nuts.
Step 2 Align the screw holes on the camera base with the installation slots on the mounting
plate. Thread the screws through the screw holes and tighten the screws.
Step 3 Connect the cables to the camera pigtail and insulate the cables. Align the screw
holes on the side of the mounting plate with the four screw holes on the mount
bracket, and then use a Phillips screwdriver to tighten the screws.
Figure 2-5 In-ceiling installation of a fixed dome camera
----End
3 Installation of the PV Module, Lightning

Rod, and Pole
3.1 Introduction
This experiment describes how to install pole components at Huawei integrated video sites.
This experiment helps you understand how to install PV modules, lightning rods, and poles
for video sites.
3.1.2 Objectives
Understand how to install pole components at an integrated video site.
3.1.3 Procedure of Installing Pole Components

Step 1 Install PV modules and cables.
In the northern hemisphere, PV modules face due south. In the southern hemisphere, PV
modules face due north.
Step 2 Install two PV modules.

Figure 3-1 Installation of two PV modules

Step 3 Install an antenna fastener and a lightning rod.

Mains power scenario
Figure 3-2 Installation of a lightning rod
Solar-grid hybrid scenario or solar-only scenario (two PV modules)
Figure 3-3 Installation of a lightning rod
Step 4 Install cables (solar-grid hybrid or mains power scenario).

Route inter-device cables through the pole.

Install ground cables for modules.
Figure 3-4 Installation of ground cables for modules
Figure 3-5 Installation of maintenance compartment cables
Table 3-1 Cable outlets of the functional module
No. Cable Outlet Cable Type Cable Outer Diameter
1 GE1/POE+ -, GE4/POE+, Optical fiber and P&E 6.8 (±0.3 mm)

GE5/POE++, GE6/POE++ network cable
2 GE7 -
3 GE8/DI -
4 DO Alarm linkage cable for

the PTZ dome camera
5 12 V DC Bullet camera power 9.3 (±0.4 mm)

cable
No. Cable Outlet Cable Type Cable Outer Diameter
6 24 V AC PTZ dome camera power

cable
Figure 3-6 Cable connections of the functional module

Step 5 Prepare cable terminals.

 PV input power cables are used only in the solar-grid hybrid scenario.
 PV input cables and battery cables are finished cables. You only need to strip the cables and
then insert them into the cable terminals.
 AC input cables need to be prepared onsite. Multi-core cables must be used. Otherwise, water
leakage may occur on the waterproof connectors.
 Before assembling cables with waterproof connectors, ensure that the connections between
the cables and terminals are secure and reliable.
Figure 3-7 Cable terminal connection
Table 3-2 Cable types
Cable Type Core Cross-Sectional Area Cable Outer Diameter
Battery cable (2-core) 3.36 mm2 9.014.5 mm
PV input power cable (2-core) 1.54 mm2
AC input power cable (3-core) 1.54 mm2
Prepare the battery cable and connecting waterproof connectors.
Figure 3-8 Preparation of a battery cable
Prepare PV input cables and connecting waterproof connectors.

Figure 3-9 Preparation of a PV input power cable
Prepare AC input cables and connecting waterproof connectors.
Figure 3-10 Preparation of an AC input power cable
Step 6 Install power cables and signal cables.
 Ensure that caps and waterproof connectors are installed at all idle ports on the
modules.
 Install an RJ45 communications cable for a lithium battery.
Figure 3-11 Installation of an RJ45 communications cable

Connect cables between a functional module and lithium batteries.
Figure 3-12 Cable connection between the functional module and lithium batteries
Step 7 Install a cable cover.

Install a cable cover for the functional module.
Figure 3-13 Installation of a cable cover for the functional module
Install a cable cover for lithium batteries (mains power scenario or solar-grid hybrid
scenario).
Figure 3-14 Installation of a cable cover for the lithium battery
Step 8 Install a pole.

Install a pole in solar-grid hybrid or solar-only scenario.
Pole installation in solar-grid hybrid or solar-only scenario
Step 9 Perform check after installation.

1. Check that the mounting kits are securely installed and all screws are
tightened.
2. Check that all cables are reliably connected with correct polarity and there is
no short circuit.
3. Check that all unused cable holes in modules are protected with waterproof
rubber caps.
----End
4 PowerCube 500 Commissioning
4.1 Introduction
This experiment describes how to commission the PowerCube 500, helping you understand
indicator definition of the PowerCube 500 and the corresponding commissioning methods.
4.1.2 Commissioning Roadmap

The procedure of integrated site commissioning is as follows:
Step 1 Power on the lithium battery of the PowerCube 500 and check its status.
Step 2 Power on the function module of the PowerCube 500 and check its status.
Figure 4-1 Integrated site commissioning procedure
----End
4.1.3 Commissioning Steps

4.1.3.1 Commissioning the Energy Module
 Switch on the energy storage unit (ESU) circuit breaker and check whether the
controller is powered on (whether the LCD lights up).
 Switch on the PV and load circuit breakers (in the solar power supply scenario).
 Check whether the controller status is correct. (Check whether the controller is
properly charged and whether the load is enabled. For details, see the controller
status description.)
Table 4-1 Checking status of the lithium battery
Indicator Definition Color Status Description
Running RUN Green Steady off The lithium battery has no

indicator power input or is faulty.
Steady on The lithium battery is

powered on and started.
Blinking slowly (0.5 Hz) The lithium battery is

communicating properly
with upstream monitoring
equipment.
Blinking fast (4 Hz) The lithium battery has

failed to communicate with
upstream monitoring
equipment.
Alarm ALM Red Steady off There is no alarm.

indicator
Steady on The lithium battery has
generated a fault alarm
and needs to be replaced.
Blinking slowly (0.5 Hz) The lithium battery has

generated a protection
alarm, which can be
cleared.
4.1.3.2 Commissioning the Functional Module

Power on the functional module of the PowerCube 500 and check its status.
Figure 4-2 Functional module of the PowerCube 500
Table 4-2 Checking status of the functional module
Indicator Color Status Description
Running Green Steady off The functional module has no power

indicator input or is faulty.
Blinking slowly (0.5 Hz) The functional module is

communicating properly with upstream
monitoring equipment.
Blinking fast (4 Hz) The functional module has failed to

communicate with upstream monitoring
equipment.
Alarm Yellow Steady off There is no alarm.

indicator
Blinking slowly The functional module has generated
an alarm, which can be cleared.
Steady on The functional module has generated

an AC power failure or PV array fault
alarm, which can be cleared.
Fault Red Steady off The functional module is normal.

indicator
Blinking slowly The functional module has an external
fault, which can be cleared.
Steady on The functional module has an internal

fault, which cannot be cleared.
5 Commissioning of a Situation Awareness

Camera
5.1 Introduction
This experiment describes how to commission a situation awareness camera.

Log in to a Adjust angle Set image
Set IP address Verify effect
camera of view parameters
Figure 5-1 Commissioning flowchart
The field of view of the situation awareness camera must meet the following requirements:
 The image angle shall be horizontal.
 The shooting object shall be in the middle of the image.
 During lens focusing, place an object for verifying focus (such as a sight meter) in a
position where pedestrians appear. Adjust the focus ring until the image becomes
the sharpest.
5.1.3 Commissioning Procedure

Step 1 Configure the IP address and change the time.
 There are multiple methods for configuring the IP address of a camera, including but
not limited to:
 Enable a camera to automatically obtain its IP address, subnet mask, gateway, and
DNS through dynamic host control protocol (DHCP).
 Access the camera web system from a computer and manually change the default IP
address.
 Manually configure the IP address using a configuration tool such as the video
surveillance tester.
 For some camera models that supports Wi-Fi, you can connect the camera to a Wi-Fi
network to obtain an IP address.
a) Open a browser.
Connect the camera to the computer using a network cable. Set the computer IP
address to be in the same network segment as the camera's default IP address
(192.168.0.120), open Internet Explorer, enter the camera IP address https://
192.168.0.120 in the address bar, and press Enter to go to the camera web system.
Figure 5-2 Camera web page
b) Log in to the camera web system.

Enter the user name and password. The default user name and password are admin
and HuaWei123, respectively. Click Log In. You can select a language from the drop-
down list box in the upper right corner.
Figure 5-3 Login page of the camera web system
You must change the user name and password when you log in to the camera web system for
the first time.
c) Change the time.

On the View page, click the Network/Time tab, and set the parameters under Time
Settings.
Figure 5-4 Changing the time
− Time zone: Set the local time zone. For China, select (UTC+08:00) Beijing.
− Synchronization: You can select either Manual or NTP. To ensure the accuracy of
the clock, the network time protocol (NTP) is adopted in this experiment.
− NTP server: Enter the IP address of the NTP server. If the camera is registered with
the surveillance platform, enter the IP address of the surveillance platform.
− Synchronization interval (min): Retain the default value, which is 60 minutes.
Click Save.
d) Change the camera IP address.
On the View page, click the Network/Time tab, and set the parameters under Set IP
Address. Select Use the following IP address for IPv4 address assignment, change the
IP address, subnet mask, gateway, and domain name server (DNS) of the camera,
and click Save. Then use a network cable to connect the camera to the switch.
Figure 5-5 Changing the camera IP address
After the IP address is changed, use the new IP address to log in to the camera. The figure
shown below is displayed.
Figure 5-6 Home page of the camera web system
The web page varies between camera models.

e) Install the player control.
Before performing other operations, install the player control so that live video can
be played.
Step 2 Download the player control.

Open the browser on your computer, enter the camera IP address in the address box, and
press Enter. On the login page displayed, enter the user name and password, and click Log
In. On the home page, click Click here to download the player.
Figure 5-7 Downloading the player control
Step 3 Install the player control.

In the download path, double-click the installation program, click Run, and click Install.
Figure 5-8 Installing the player control
Step 4 View live video.

After the player control is installed, restart the browser, log in to the camera web system
again, click to allow the browser to run npIVS_VideoPlugin, and click Allow and Remember
in the dialog box displayed.
The live video captured by the camera is displayed.
Figure 5-9 Viewing live video
You can use the buttons on the toolbar at the bottom of the live video pane to set live
video.
Table 5-1 Buttons on the toolbar at the bottom
Button Function
Stop live video viewing. Click this button again to enable live video viewing.
Start or stop local recording. Click this button to start local recording. After
local recording is started, click the button again to stop local recording.
Start SD card–based video recording. This is available only on a camera

with an SD card.
Capture live video images.
Only PTZ cameras support this function.

Automatically adjust the PTZ rotation direction and focal length based on
the area selected on the video image. The following describes the detailed
procedure:
1. Click .
2. Draw a box on the video image. The area inside the box is automatically
displayed at the center of the video image.
 Zooming in: Drag a box from left to right on a video image.
 Zooming out: Drag a box from right to left on a video image.
Button Function

Quickly navigate to a specific location. The following describes the detailed
procedure:
1. Click .
2. Click a location on a video image to display the point at the center of
the video image.

Adjust the PTZ rotation direction. The following describes the detailed
procedure:
1. Click . A cross is displayed in the image center. Then click a position

on the video image. An arrow is displayed there.
2. Press and hold the left mouse button to rotate the camera around the
arrow.
A shorter distance between the arrow and the cross indicates a slower
rotation speed.
You can scroll the mouse wheel to control the zoom. The image zooms in
when the mouse wheel is scrolled up and zooms out when it is scrolled
down.
The electronic PTZ (ePTZ) adjusts the focal length or shooting angle
through software, instead of by using lens zooming or PTZ rotation. The
ePTZ is mainly used to zoom in on high-resolution images to show more
details. Zooming in too far on low-resolution images may result in artifacts
due to the limited pixels.
The ePTZ function can be used only after the area cropping function is
enabled and live video is switched to the required secondary stream type.
A shorter distance between the arrow and the cross indicates a slower
rotation speed.
You can scroll the mouse wheel to control the zoom. The image zooms in
when the mouse wheel is scrolled up and zooms out when it is scrolled
down.
Enable or disable the voice intercom function. This function is disabled by

default.
Channel-associated voice and voice intercom cannot be enabled at the
same time.
To set the volume, drag the slider.
Button Function
Enable or disable the channel-associated voice function. This function is

disabled by default. Channel-associated voice and voice intercom cannot be
enabled at the same time.
The function is available only when you set Stream switch to Hybrid
stream. To set the volume, drag the slider.
Switch between the primary and secondary streams.

By default, secondary stream 1 is displayed for 4K cameras. To change the
default stream, choose Settings > System > Local Settings > Playing
Settings, and set Code stream type to a specified stream.
Display the video stream resolution. The icon changes based on the video
resolution.
Crop an area on the live video image and zoom in on it.
Toggle among Full Screen, Actual Size, 16:9, 4:3, and 1:1.
View video in full-screen mode. Press Esc to exit full-screen mode.
View real-time camera information, including the protocol type, frame rate,
resolution, current bit rate, and packet loss rate.
The function buttons vary between camera models.

 Manually configure the IP address using a configuration tool such as the video
surveillance tester.
 Connect a camera that supports Wi-Fi to a Wi-Fi network to obtain an IP address.
 In this experiment, use a computer to access the camera web system and manually
configure the IP address.
----End
6 Commissioning of a Facial Recognition

Camera
6.1 Introduction
This experiment uses an X series SDC as an example to describe how to commission a facial
recognition camera.

Log in to a Adjust angle Configure the
Set IP address Verify effect
camera of view facial recongnition
Figure 6-1 Commissioning flowchart
Key Points for Camera Position Selection

Installation position: The camera should be installed in the due front of a walkway and
directly face pedestrians to ensure a better capture effect.
Installation height: The recommended installation height (H) ranges from 2.5 m to 4 m.
The optimal height is 2.5 m to 3.2 m.
Installation distance and surveillance width: The surveillance width (W) and installation
distance (D) vary depending on the camera model. When selecting the location, check
whether D and W of the cameras meet the requirements (calculated based on the
recommended resolution of 120 pixels). D indicates the distance between the camera
installation position and the planned snapshot position, and W indicates the coverage
width of the planned snapshot position, as shown in the following figure.
Tilt angle: The tilt angle (α) of the camera should be within 15°. The recommended tilt
angle is 8° to 10°. It is difficult to measure the tilt angle onsite. You can determine the tilt
angle based on the installation height and distance.
Figure 6-2 Camera installation distance and coverage width
6.1.3 Commissioning Procedure

6.1.3.1 Configuring an IP Address
Choose Settings > Network > TCP/IP > IP Address, set the IP address based on the IP address,
mask, and gateway allocated by the customer, and save the settings.
6.1.3.2 Adjusting the Field of View

Adjusting the Horizontal Angle and Zoom Ratio
To make captured face images clearer, you are advised to select a narrow field of view.
Adjust the horizontal angle of the camera to enable the image view to cover the center of
the walkway. Adjust the zoom ratio (zoom-in and zoom-out) to ensure that the image
view covers the left and right sides of the walkway.
Figure 6-3 Field of view to cover the walkway

Figure 6-4 Field of view to cover the walkway
Adjusting the Tilt Angle of a Camera

Arrange a test person to stand in the middle of the planned capture position and adjust
the camera tilt angle to ensure that the pedestrian's face is in the middle of the image, as
shown in the following figure.
1. If the person's face is in the upper part of the image view, slightly tilt the camera up.
2. If the person's face is much below the middle part of the image, for instance, in less
than lower third part of the image, slightly tilt the camera downward.
3. The captured face is about 120 pixels, as shown in the following figure.
Figure 6-5 Face in the middle of the image view
Figure 6-6 Face with a width of about 120 pixels

Adjusting the Image Effect

After the field of view is adjusted, the image brightness may be too high or too low. You
can choose Settings > Image and modify the image parameters to adjust the image effect.
For non-snapshot areas in the image view, you can choose Settings > Focus Area to set the
focus priority.
Adjusting the Image Clarity
To improve the clarity adjustment efficiency, you are advised to use a Siemens star chart
to adjust the focus. A clearer internal view of the Siemens star chart indicates a better focus
effect. When adjusting the image clarity, pay attention to the following points:
The camera usually captures faces in the middle and lower parts of the image. Therefore,
you need to ensure that close-up objects in the center and lower parts of the image are
focused clearly, as shown in the following figures.
Higher requirements may be raised on the overall image in some scenarios. Distant objects
in the upper part of the image shall also be as clear as possible.
Figure 6-7 Siemens star chart in the middle or slightly lower part of the image
Figure 6-8 Siemens star chart in close-up view

Figure 6-9 Siemens star chart in distant view
6.1.3.3 Configuring Face Detection

1. Choose Settings > Intelligent Analysis > Face Detection. The Face Detection
page is displayed.
2. Select Enable face detection and Quality filter switch, and set other
parameters as required. Click Save.
Figure 6-10 Enabling face detection
In some special scenarios, you can enable wide dynamic range (WDR), draw a region of
interest (ROI), or make a profile plan to optimize the image effect. The common
troubleshooting methods for captured face images are as follows:
1. Dark face image in backlight conditions
Symptom: In backlight scenarios such as a lobby, face images are too dark.
Solutions:
Method 1
Decrease the zoom ratio to enable the image view to cover more indoor areas,
reducing the impact of backlight on the image.
When the zoom ratio is reduced, the resolution of captured faces also decreases.
Check whether the horizontal resolution of captured faces reaches 120 pixels. If not,
the facial recognition effect is affected.
Method 2
Increase the face brightness compensation coefficient. If the face image is still dark,
enable WDR. This method can improve the brightness of faces, but may cause
overexposure of the background.
Increase brightness compensation: Choose Settings > Intelligent Analysis > Face
Detection, set the face compensation coefficient to about 60 (default value: 50), and
check the effect.
Figure 6-11 Adjusting the face compensation coefficient
Enable WDR: Choose Settings > Video/Audio/Image > Image. Click Backlight and set
WDR/HLC/BLC to Wide dynamic range. Adjust the WDR coefficient to about 40.
Figure 6-12 Enabling the WDR function

2. Face overexposure in front light conditions

Symptom: When pedestrians face strong light sources such as the sunlight or
illuminator, the face image may be overexposed.
Solution: Decrease the contrast and exposure compensation coefficient.

Decrease the contrast: Choose Settings > Video/Audio/Image > Image > Image
Adjustment. Gradually decrease the contrast. Generally, the value is greater than or
equal to 40. The default value is 50.
Figure 6-13 Adjusting the contrast
Decrease the exposure compensation coefficient: Choose Settings >

Video/Audio/Image > Image, click Exposure, and decrease the value of Exposure
compensation coefficient gradually. Generally, the value is greater than or equal to
40. The default value is 50.
Figure 6-14 Adjusting the face compensation coefficient
3. Motion blur
Symptom: As the object moves fast and the shutter speed is slow, the captured
image is blurred.
Solution: Adjust the shutter limit or decrease the noise reduction level.
Adjust the shutter limit: Choose Settings > Video/Audio/Image > Image. Click
Exposure and set Shutter limit (s) to 1/100.
Figure 6-15 Setting the shutter limit
Decrease the denoising level: If the problem persists, choose Settings >
Video/Audio/Image > Image > Image Enhancement. Decrease the noise reduction
level. Generally, the value is greater than or equal to 30. The default value is 50.
Figure 6-16 Setting noise reduction parameters
----End
Huawei WLAN Certification Training Lab Guide Page 51
7 Commissioning of a License Plate

Recognition Camera
7.1 Introduction
This experiment uses an X series SDC as an example to describe how to commission a
license plate recognition camera.

ePolice Camera Commissioning Procedure
Install the camera
Check Adjust angle
Determine and external Adjust Verify
Installation of view and
system scheme devices on the illuminators installation
environment focal length
pole
Key Points for Selecting a Position for the ePolice Camera

Table 7-1 Key points for selecting a position for the ePolice camera
Installation Attribute Requirement
Number of lanes under 2 to 4

surveillance
Camera installation 5.5 m ≤ H ≤ 6.5 m (recommended: 6 m)

height (H)
Lens configured 16 mm (recommended), 20 mm
Optimal installation Standard scheme: When the installation location ranges

range X from 21 m to 25 m and a 16 mm lens is configured, the
optimal X is 21 m.
Distance (L) from the 8m≤L≤9m

lower edge of the If large vehicles such as trucks need to be captured, L must
image to the stop line be greater than or equal to the length of a large vehicle.
The recommended value of L is as follows: L ≥ Large vehicle
length + 1 m
Distance (D) from the D≥2m

strobe light to the
camera
External device installation requirements
Traffic light
Pole height: 6 m
Illuminator light spot
Stop line
8m L 9m
Lane Lower image edge
3.75m
X=20m
Camera Pole height

(H)=6 m
Strobe light
d 2m (supplement light for
the lane)
Figure 7-1 Single-lane ePolice installation scenario

红绿灯
杆高6m
补光灯光斑位置
停止线
8m L 9m
车道1 车道2 摄像机画

面下边缘
X=20m
3.75m
摄像机架杆高度
d 2m d 2m H=6m
频闪灯频闪灯
车道2补光车道1补光
Figure 7-2 Two-lane ePolice installation scenario
Traffic light
Pole height: 6 m
Stop line
8m L 9m
Lane 1 Lane 2 Lane 3 Lower

image edge
X=21.5m
3.75m
Camera Pole height

(H)=6 m
d 2m d 2m Strobe light
Strobe light Strobe light (supplement light
(supplement light (supplement light for for lane 2)
for lane 3) lane 1)
Figure 7-3 Three-lane ePolice installation scenario

Traffic light
Pole height:
6m
Stop line
8m L 9m
Lane 1 Lane 2 Lane 3 Lane 4 Lower image

edge
X=21.5m
3.75m
Camera
Pole height
(H)=6 m
Strobe lights Strobe lights
(supplement light for d 2m d 2m (supplement light for
lanes 3 and 4) lanes 1 and 2)
Figure 7-4 Four-lane ePolice installation scenario
7.1.3 Commissioning of an ePolice Camera

Step 1 Configure the IP address.
Refer to the IP address of the situation awareness camera.
Step 2 Configure the application mode.

Choose Intelligent Transportation, click the Application tab, and set Application mode to
ePolice.
Step 3 Select a snapshot mode.

Select the snapshot mode. By default, the single-shutter mode is selected in ePolice mode,
and the dual-shutter mode is selected in checkpoint mode.
Step 4 Select a detection mode.

Select a detection mode from the Detection mode drop-down list box based on the site
requirements.
Table 7-2 Detection mode description
Mode Description
External This detection mode can be selected if the camera has been connected
device to an external device (such as a loop detector). In this mode, only traffic
access behavior detected by external devices can trigger snapshot taking.
Video- The camera uses intelligent algorithms to analyze video images and
based determines whether to trigger traffic detection based on the vehicle
detection behavior.
Mode Description
External In this mode:

device  When the camera is connected to an external device and the external
priority device is working properly, the external device will detect and take
snapshots of traffic violations supported by the external device. The
system will detect and take snapshots of other traffic violations in
video analysis mode.
 When the camera is not connected to an external device or the
connected external device is faulty, the system will detect and take
snapshots of traffic violations in video analysis mode.
Table 7-3 External device description
External Function Traffic Detection Function

Device Implemented by Working
with Cameras
Induction- Detects vehicles that pass the induction Checkpoint (checkpoint

loop vehicle loop. When multiple loops are deployed, snapshot), speeding/low
detector the driving speed of the vehicle can be speed detection, wrong-way
estimated based on the distance driving detection, and red
between two loops and the time for the light running detection
vehicle to pass the two loops.
Traffic light Obtains the status of the traffic light in Red light running
detector real time, and then transmits the
information to the camera so that the
camera can learn the status of the
traffic light in real time.
Step 5 Set a snapshot interval.

You can set the interval for the camera to take snapshots of vehicles violating traffic rules
or regulations. Currently, you can set the snapshot interval or use an adaptive interval.
Step 6 Set the detection function.

Select the traffic violations for which the detection is to be enabled, set the number of
snapshots to take and other related parameters, and click Save.
Step 7 Set lane parameters.

On the Application tab page, click Lane Settings. On the Lane Settings page, select a lane
and set parameters based on the site requirements. You can click Copy settings to to copy
the settings of the current lane to other lanes. After the setting is complete, click Save.
Step 8 Configure external devices in ePolice mode.

In ePolice mode, the external devices supported are the induction-loop vehicle detector
and traffic light detector.
a) Configure the RS-485 induction-loop vehicle detector.
Click the Vehicle Detector tab. Set related parameters based on the site
requirements, as shown in the following figure. To copy settings for a lane to other
lanes, select the lanes under Copy settings to and click Save.
Figure 7-5 Configuring the RS-485 induction-loop vehicle detector
b) Configure the traffic light detector.

On the Traffic light tab page, set the parameters based on the site requirements.
Figure 7-6 Configure the traffic light detector.
----End
7.1.4 Commissioning Procedure for a Standard Checkpoint

Camera
Install the camera

Check Adjust angle
Determine and external Adjust Verify
Installation of view and
system scheme devices on the illuminators installation
environment focal length
pole
Figure 7-7 Commissioning flowchart for a standard checkpoint camera
Figure 7-8 Key points for selecting a position for the standard checkpoint camera
Table 7-4 Checkpoint camera installation parameters
Scenario Lens Lane Width (m) Snapshot

Distance (m)
9-megapixel checkpoint camera for 50 mm 3.75 24 m to 25 m

two-lane surveillance

three-lane surveillance

four-lane surveillance

single-lane surveillance
Scenario Lens Lane Width (m) Snapshot

Distance (m)

two-lane surveillance
7.1.5 Commissioning Procedure for a Checkpoint Camera

Step 1 Configure the IP address.
Refer to the IP address of the situation awareness camera.
Step 2 Configure the checkpoint application mode.

Log in to the camera web system, choose Intelligent Transportation, click the Application
tab, and select Checkpoint as the application mode.
Step 3 Select a snapshot mode.

Select the snapshot mode. By default, the single-shutter mode is selected in ePolice mode,
and the dual-shutter mode is selected in checkpoint mode.
Step 4 Select a detection mode.

Select a detection mode from the Detection mode drop-down list box based on the site
requirements. For details about the detection modes, see the related description for the
ePolice camera.
Step 5 Set a snapshot interval.

You can set the interval for the camera to take snapshots of vehicles violating traffic rules
or regulations. Currently, you can set the snapshot interval or use an adaptive interval.
Step 6 Set the detection function.

Select the traffic violations for which the detection is to be enabled, set the number of
snapshots to take, and click Save.
For details about the parameters, see the related description for the ePolice camera.
Step 7 Set lane parameters.

On the Application tab page, click Lane Settings. On the Lane Settings page, select a lane
and set parameters based on the site requirements. You can click Copy settings to to copy
the settings of the current lane to other lanes. After the setting is complete, click Save.
Step 8 Configure external devices in checkpoint mode.

Choose Intelligent Transportation > External Device. On the page that is displayed, the
external devices in use are displayed. You can deselect Enable to disable the external device.
In checkpoint mode, the external devices supported are the induction-loop vehicle detector
and radar detector.
a) Configuring the RS-485 induction-loop vehicle detector

On the RS-485 Loop Vehicle Detector tab page, set related parameters based on the
actual external device.
Figure 7-9 Configuring the RS-485 induction-loop vehicle detector
b) Configure the radar.

On the Radar tab page, set radar parameters based on the site requirements. For
example, set single-lane radar parameters or multi-lane radar parameters.
Figure 7-10 Configuring the radar

Table 7-5 Radar parameters
Parameter Description
Lane Lane where the radar is located.
Enable Indicates whether to enable the radar corresponding to the

current lane.
Device type Select a type from the drop-down list box based on the current
radar type. For Huawei radar detectors, select ACC7310 (A)
single-lane radar. For WHST radar detectors, select ACC7310 (B)
single-lane radar.
Serial port Port through which the radar connects to the camera.
Detection Indicates whether to detect approaching or leaving vehicles. The

direction/Capture radar can also detect both approaching and leaving vehicles.
direction  CSR_IK radar: The parameter name is Detection direction.
 ACC7310 (A) radar: The parameter name is Capture
direction.
Angle When the speed estimated by the radar differs greatly from the
actual vehicle speed, you can set this parameter to correct the
estimated speed. The specific value of this parameter can be
obtained from the commissioning software provided by the
radar vendor. The value ranges from 0 to 70.
Sensitivity Sensitivity of radar-triggered snapshot.

 CSR_IK radar: A larger value indicates a higher sensitivity.
The value ranges from 1 to 240. In normal cases, the default
value 10 is recommended.
 ACC7310 (A) radar: A smaller value indicates a higher
sensitivity. The value ranges from 50 to 1000. In normal
cases, the default value 300 is recommended.
 ACC7310 (B) radar: A smaller value indicates a higher
sensitivity. The value ranges from 0 to 1. In normal cases, the
default value 0.4 is recommended.
Triggering distance Maximum distance from the radar to the position where the
(cm) speed estimation is triggered. Set this parameter based on the
site requirements. The default value 2400 is recommended.
Min. triggering Minimum speed for radar-triggered snapshot. A snapshot can

speed (km/h) be triggered when the speed of a vehicle is greater than or
equal to the minimum speed. The unit is km/h. For the CSR_IK
radars, the value ranges from 1 to 150. For the ACC7310 (B)
radars, the value ranges from 0 to 255, and the default value is
5.
Maximum trigger Maximum speed for radar-triggered snapshot. A snapshot can

speed be triggered when the speed of a vehicle does not exceed the
maximum speed. The unit is km/h. The value ranges from 0 to
255. The default value is 250.
Height (cm) Installation height of the radar. The value ranges from 0 to
1000.
Speed correction In some special scenarios, the speed detected by radar needs to
be corrected to ensure the accuracy of the detection data.
Set this parameter based on the site requirements. The unit is
km/h. The value ranges from –50 to +50. The default value is –
2.
Large vehicle Energy threshold for determining an object as a large or small

limit/Small vehicle vehicle.
limit Set this parameter based on the site requirements. If a large
number of large vehicles are captured, the value of Large
vehicle energy threshold needs to be decreased.
 The value of Small vehicle energy threshold ranges from 300
to 1500. The default value 500 is recommended.
 The value of Large vehicle energy threshold ranges from
1500 to 6000. The default value 5000 is recommended.
 The value of Large vehicle limit or Small vehicle limit ranges
from 1 to 5. The default value 3 is recommended.
Non-motor vehicle Indicates whether to filter out non-motor vehicles based on the
filtration actual scenario. The options are as follows:
 0: Reserve non-motor vehicles.
 1: Filter out non-motor vehicles.
Operating mode Detection and snapshot mode of the ACC7310 (B) radars. The
options are as follows:
 Front trigger: Only approaching vehicles can be detected.
Data is sent only once for each vehicle that enters the
detection area. Data is not sent if no vehicle enters the
detection area.
 Rear trigger: Only leaving vehicles can be detected. Data is
sent only once for each vehicle that enters the detection
area. Data is not sent if no vehicle enters the detection area.
 Double touch mode: Both approaching and leaving vehicles
can be detected. Data is sent only once for each vehicle that
enters the detection area. Data is not sent if no vehicle
enters the detection area.
 Continuous mode: When a vehicle enters the detection area,
data is sent. Data is not sent if no vehicle enters the
detection area.
c) Configure the I/O loop vehicle detector.

On the I/O tab page, set related parameters based on the actual external device.
Figure 7-11 Configuring the I/O-loop vehicle detector
Table 7-6 I/O-loop vehicle detector parameters
Lane Lane where the loop is located.

Enable Indicates whether to enable the induction-loop vehicle detector on this

lane.
Device type External device type. Set this parameter to Single I/O loop detector.
Snapshot Scheme for vehicle capture after the detector detects the vehicle. The
scheme options are as follows:
 None: No snapshot is taken when a vehicle violates regulations.
 One_Into loop 1: Only one loop is deployed. The camera takes a
snapshot of the vehicle when the vehicle enters the loop.
 One_Out of loop 1: Only one loop is deployed. The camera takes a
snapshot of the vehicle when the vehicle leaves the loop.
Alarm Input Select the alarm input port that a single I/O loop vehicle detector
connects to. For example, if the single I/O loop vehicle detector is
connected to alarm input port 1 of the camera, set this parameter to
Alarm input 1.
Trigger Set this parameter based on the output signal triggering mode when
mode the vehicle passes the vehicle detector. The options are as follows:
 None: The snapshot is not triggered when a vehicle passes the
vehicle detector.
 Rising edge: When a vehicle passes the vehicle detector, the output
signal of the vehicle detector is rising edge-triggered.
 Falling edge: When a vehicle passes the vehicle detector, the output
signal of the vehicle detector is falling edge-triggered.
After the setting is complete, click Save.

----End

Intelligent Vision System
Installation and Deployment
Experiment Guide
ISSUE: 1.0
1
No part of this document may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of
their respective holders.
Notice
recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has
been made in the preparation of this document to ensure accuracy of the contents, but
all statements, information, and recommendations in this document do not constitute
a warranty of any kind, express or implied.

Huawei Certification System

Expert (HCIE).
technologies.
About This Document
Overview
This document is a training course for HCIP-Intelligent Vision certification. It is intended
for trainees who are going to take the HCIP-Intelligent Vision exam or readers who want
to understand Huawei Intelligent Vision platform construction, advanced service
commissioning, SDC technical principles, intelligent algorithm management and
application, and Intelligent Vision technologies such as video cloud.
Content Description
This document, which consists of seven parts, uses Huawei HoloSens IVS3800 (IVS3800)
as an example to provide the Intelligent Vision platform construction method step by
step.
 Experiment 1 lists materials to be obtained (including software packages and
process files to be downloaded) before the experiment and describes how to
provide the LLD.
 Experiment 2 describes how to install the IVS3800 platform server and
corresponding switches and how to connect the hardware.
 In experiment 3, the network is configured (including configuration of switches
connected to servers and VLAN division) after experiment 2.
 In experiment 4, basic data about hardware servers (including system time
setting and RAID creation) is configured.
 In experiment 5, the CSP is installed. CSP installation determines the
architecture of the whole environment and lays a foundation of IVS
applications.
 In experiment 6, the IVS application system is deployed. The IVS3800 is
installed and deployed in the experiment.
 In experiment 7, system basic configuration is performed, including changing
the host name and configuring floating IP addresses, on the Intelligent Vision
platform. In addition, the surveillance platform and analysis platform are
connected.

This course is for Huawei's professional certification. To better understand this course,
familiarize yourself with the following requirements:
 Understand basic datacom knowledge and know how to perform simple switch
configuration.
 Have the capability of Huawei HCIA-Intelligent Vision and be able to

independently commission basic services of the platform and cameras.
Lab Environment Description

Network Diagram
This lab environment is intended for Intelligent Vision engineers who are preparing for
the HCIP-Intelligent Vision exam. Each lab environment consists of two to eight
Intelligent Vision servers and two to four access switches. Each lab environment allows
four to twelve trainees to perform lab practice at the same time.
Device Introduction
To meet the HCIP-Intelligent Vision experiment requirements, you are advised to use the
configurations described in the following table in each environment.
The following table describes the mapping among devices, models, and versions.
Device Model Version
Intelligent IVS3800F/IVS3800S/IVS3800C/IVS3800 V100R019C50

Vision server R/IVS1800h and CloudIVS 3000
Switch CloudEngine 6800 CloudEngine 6800

V200R005C10SPC800

Checking the Devices
Before the experiment, each group of trainees should check whether their experiment
devices are complete. The following table lists the experiment devices.
Intelligent Vision 7 Shared by all groups

server
Network switch 4 Shared by all groups
Desktop or laptop One for each group A PC must have a wireless network
adapter.
Twisted pair One for each group At least 2 meters long
Console cable One for each group

Experiment Topology
Requirements on switches
 Device management Top of Rack (TOR): TOR access switch on the device
management plane. The management port of each hardware device is
connected to the switch. S5700 series switches are recommended.
 Management TOR: TOR access switch on the management plane. The GE
electrical port on the management plane is connected to the switch. CE5800
series switches are recommended.
 Service TOR: TOR access switch on the service plane. The 10GE optical port or
GE electrical port on the service plane is connected to the switch. CE6800 series
switches are recommended.
 End of Row (EOR): aggregation switch. The networks of the service plane and
management plane are aggregated through the aggregation switch and then
connected to the customer's network.
Network requirements:
 The GE electrical ports connected to the management TOR switch are bonded
in active-standby (Bond=1) mode. The 10GE optical ports or GE electrical ports
connected to the service TOR switch are bonded in LACP (Bond=4) mode. The
service TOR switch must support static LACP, and an Eth-Trunk must be
configured for the service TOR switch.
 Management TOR switches and service TOR switches must be stacked.
Contents
1 Preparations ........................................................................................................................................... 8
1.1 Introduction ................................................................................................................................................................................ 8
1.1.1 About This Experiment........................................................................................................................................................ 8
1.1.2 Objectives ................................................................................................................................................................................ 8
1.2 Configuration Procedure........................................................................................................................................................ 8
1.2.1 Downloading Software Packages and Process Files ................................................................................................ 8
1.2.2 Verifying Software Package Integrity ............................................................................................................................ 9
1.2.3 Obtaining Installation Tools ...........................................................................................................................................13
1.2.4 Changing the Power Plan on the Local Computer .................................................................................................13
1.2.5 Default IP Addresses, User Names, and Passwords ...............................................................................................14
1.2.6 Obtaining Project Configurations .................................................................................................................................15
1.2.7 Generating the LLD ............................................................................................................................................................17
2 Hardware Installation........................................................................................................................23
2.1 Introduction ..............................................................................................................................................................................23
2.1.1 About This Experiment......................................................................................................................................................23
2.1.2 Objectives ..............................................................................................................................................................................23
2.2 Configuration Procedure......................................................................................................................................................23
2.2.1 Installing the Switch Hardware .....................................................................................................................................23
2.2.2 Installing the Server Hardware ......................................................................................................................................29
2.2.3 Physical Network Connections .......................................................................................................................................30
3 Network Configuration .....................................................................................................................38
3.1 Introduction ..............................................................................................................................................................................38
3.1.2 Objectives ..............................................................................................................................................................................38
3.2.1 Configuring Basic Data .....................................................................................................................................................38
3.2.2 Configuring Stacking .........................................................................................................................................................43
3.2.3 Configuring the Switch Network ...................................................................................................................................44
4 Basic Configuration of the CSP.......................................................................................................50
4.1 Introduction ..............................................................................................................................................................................50
4.1.2 Objectives ..............................................................................................................................................................................50
4.2.1 Configuring the iBMC ........................................................................................................................................................50
4.2.2 Checking the Firmware Versions ...................................................................................................................................53

4.2.3 Configuring Basic Data .....................................................................................................................................................54
4.2.4 Configuring RAID Groups.................................................................................................................................................63
5 Installing the CSP ................................................................................................................................80
5.1 Introduction ..............................................................................................................................................................................80
5.1.2 Objectives ..............................................................................................................................................................................80
5.2.1 Disabling Memory Interleaving .....................................................................................................................................80
5.2.2 Installing the Management Node in a Single-Node System ..............................................................................82
5.2.3 Installing Management Nodes in a Cluster ..............................................................................................................97
5.2.4 Enabling Memory Interleaving.................................................................................................................................... 118
5.2.5 Disabling the Automatic Backup Function ............................................................................................................. 119
5.2.6 Setting the System Time ............................................................................................................................................... 119
6 IVS Application System Deployment ......................................................................................... 123
6.1 Introduction ........................................................................................................................................................................... 123
6.1.1 About This Experiment................................................................................................................................................... 123
6.1.2 Objectives ........................................................................................................................................................................... 123
6.2 Configuration Procedure................................................................................................................................................... 123
6.2.1 Managing Service Nodes............................................................................................................................................... 123
6.2.2 Uploading a Software Package and a Process File ............................................................................................. 125
6.2.3 Deploying Applications and Verifying the Installation ....................................................................................... 126
6.2.4 Creating RAID Groups .................................................................................................................................................... 130
6.2.5 Importing a License......................................................................................................................................................... 132
6.2.6 Enabling the Automatic Backup Function .............................................................................................................. 136
7 System Configuration ..................................................................................................................... 140
7.1 Introduction ........................................................................................................................................................................... 140
7.1.2 Objectives ........................................................................................................................................................................... 140
7.2.1 Changing Host Names ................................................................................................................................................... 140
7.2.2 Configuring Floating Gateways for a Cluster ........................................................................................................ 141
7.2.3 Configuring Recording and Checkpoint Data Storage Policies ....................................................................... 142
7.2.4 Configuring Domain Names and Load Balancing Policies ............................................................................... 143
7.2.5 Configuring NTP Time Synchronization for Cameras ......................................................................................... 144
7.2.6 Configuring the Connection Between the Surveillance Platform and the Analysis Platform.............. 145
1 Preparations
1.1 Introduction
This experiment provides guidance on how to install devices, including downloading the
installation package and process file, obtaining project information, and generating the
LLD.
1.1.2 Objectives
 Understand the platform installation software download path.
 Master the LLD configuration method.
1.2 Configuration Procedure

1.2.1 Downloading Software Packages and Process Files
Download the software packages and process files of the corresponding versions based
on the obtained hardware server information. The detailed procedure is as follows:
Log in to Huawei enterprise technical support website and select the software packages
and process files. In this experiment, the software packages and process files of the non-
commercial usage version are downloaded as an example. The actual version varies
according to the project requirements.
 IVS3000 application software packages (including facial recognition and
personal feature recognition)
 Process files
 EulerOS and CSP installation image package
Figure 1-1 Downloading the software package and process file
Download the software packages and process files to the local computer.
Figure 1-2 Downloaded files
1.2.2 Verifying Software Package Integrity

To prevent a software package from being maliciously tampered with during
transmission or storage, download the corresponding digital signature file for integrity
verification when downloading a software package. In this experiment, the PGPVerify tool
is used for verification.
1.2.2.1 Downloading the PGPVerify

The PGPVerify is a Huawei-developed PGP verification tool running on the Windows 7,
Windows Server 2008, Windows 8, and Windows 10.
Download path: https://support.huawei.com/enterprise/en/tool/pgp-verify-TL1000000054
Figure 1-3 PGP Verify download page
Step 1 Click the version package. The file download page is displayed. Select the public
key file KEYS and tool program VerificationTools and download them. The
signature verification guide is the operation guide, which can be downloaded as
required.
Figure 1-4 Downloading the PGPVerify and public key file
Step 2 Decompress VerificationTools to extract the PGPVerify, as shown in the following

figure.
Figure 1-5 File list
----End
1.2.2.2 Using the PGPVerify to Verify Software Packages

There is a one-to-one mapping between a software package and a signature file and
they are stored in the same directory. Generally, a software package and its signature file
have the same name but different extensions. A signature file has the file name
extension .asc. For example, the signature file for the software package V100R019C10.zip
is V100R019C10.zip.asc.
Assume that the signature file and software package are stored in the C:\PGP directory,
and the PGPVerify tool and public key file are stored in the C:\ directory.
Step 1 Double-click PGPVerify.exe to start the tool.
Figure 1-6 Starting the PGPVerify
Step 2 Click Select Public Key and select the downloaded KEYS file.
Figure 1-7 Selecting the KEYS file
Step 3 Verify files.

To verify a single file, click Single Verify and select the .asc signature file. The tool starts
the verification. When the item is displayed in green and the Results column displays
PASS, the verification is successful.
To verify all files in the directory, click Multiple Verify and select the C:\PGP\ directory.
The tool starts the verification. The verification result examples are as follows.
----End
Figure 1-8 Verification result
 [PASS] (highlighted in green): The verification is successful.

 [WARN] (highlighted in yellow): The verification cannot be performed. For

example, the signature file or software package does not exist.
 [FAIL] (highlighted in red): The verification failed.
 If neither WARN nor FAIL is displayed for any item, that is, all items are displayed
in green and the signature files are valid.
1.2.3 Obtaining Installation Tools

The following table lists the software and hardware required in the installation.
Download them to the local computer.
Table 1-1 Preparing tools
Tool Description How to Obtain
WinZip Used for file decompression. -
Serial Used to connect your computer Obtain the serial cable from the
cable to the console port of a switch delivered accessories of the switch or
for initial configuration of the purchase it separately. Before
switch. installing the CloudIVS 3000, ensure
that the driver is installed and
commissioned.
KVM Used to log in to the remote To download the KVM, visit the
console of the server following website:
independently. You can use this http://support.huawei.com/onlinetools
tool if login to the iBMC WebUI web/itexpress/kvmclient/cn.html
fails.
1.2.4 Changing the Power Plan on the Local Computer

The installation will take a long time. If the sleep setting in the power plan used by the
local computer is too short, the installation may be interrupted. As a result, you need to
change the power plan of the computer. After the installation, restore the power plan.
The procedure is as follows:
Step 1 Choose Start > Control Panel.

Step 2 Select Power Options in Control Panel. The following page is displayed.
Figure 1-9 Selecting a power plan
Step 3 Click Change settings for the plan, set Put the computer to sleep to 3 hours, and
click Save changes. The following page is displayed.
Figure 1-10 Changing the power plan
----End
1.2.5 Default IP Addresses, User Names, and Passwords

The following table describes the default IP address, user name, and password involved in
installation.
Table 1-2 Default IP addresses, user names, and passwords
System Default IP Address Default User Name Default Password
iBMC WebUI 192.168.2.100 Administrator Admin@9000

of the server
System Default IP Address Default User Name Default Password
CSP OM N/A admin Changeme_123

portal
iClient N/A admin Change_Me
Operating N/A root cnp200@cspos@RD

system
N/A cspexpert mt2017@cspos@RD
To log in to the operating system in SSH mode, log in as the cspexpert user, and then run the su
- root command to switch to the root user.
1.2.6 Obtaining Project Configurations

Before the first-time installation, you need to obtain site configurations, such as node
information and number of hard disks, to ensure proper system installation. The
configurations include the types and quantity of containers to be installed on each server.
The system can be automatically installed according to the configurations.
Configuration procedure:
Step 1 Log in to the SCT configurator at http://unistar.huawei.com/sct. Enter the user

name and password to access the home page. Click My Quotation.
Figure 1-11 Logging in to the SCT home page
Step 2 In the quotation list, find the corresponding project configuration list and click it
to enter the quotation list.
Figure 1-12 Quotation list
Step 3 Find the corresponding server. The product parameter details page is displayed.
Figure 1-13 Configuring data on the details page
Step 4 On the Product Parameter tab page, set related parameters.

Figure 1-14 Product parameter page
Step 5 Wait until the configuration is complete. The system exports the corresponding
Excel file, which contains the detailed configuration of the project.
----End
1.2.7 Generating the LLD

After obtaining the Excel file containing project configurations, you need to generate a
network plan based on this file.
Step 1 Use Google Chrome to access
https://serviceturbocloud.huawei.com/serviceturbocloud/ and use your Huawei
account to log in. Before login, clear the browser cache.
Figure 1-15 Network design home page
Step 2 Choose Tool Application Market, enter CloudDesign IVS, and click the search
result. The tool page is displayed.
Figure 1-16 Searching for CloudDesign IVS
Step 3 Click Create. The Project Info page is displayed. Enter project information based on
the project requirements. Click Confirm to go to the next step.
Figure 1-17 Creating project information
Step 4 On the Select Scenario page, configure scenario information.
Figure 1-18 Select Scenario page
Set parameters based on the site requirements. The following table describes the
parameters.
Table 1-3 Parameter description
Parameter Description Setting
Solution Type Cloud Edge: applicable to the Select Cloud Edge.

CloudIVS 3000 and IVS3800.
Cloud Center: applicable to the
IVS9000.
Delivery Scenario The options are Capacity expansion Select New Deployment.
and
New Deployment.
BMU Requires Selected: The external management If the

Management Plane plane (Outer_OM) is used to CloudVCM/CloudVCN,
connect the upper- and lower-level IVS9000, or CloudIVS
domains or algorithm repositories. 3000 V100R019C10 or a
Deselected: The external service later version is deployed
plane (Outer_Service) is used to on the entire network,
connect the upper- and lower-level select the check box.
domains or algorithm repositories. Set this parameter
based on the actual
networking.
The system allows you
to switch the BMU
network plane after the
installation.
Step 5 Click Next. The page for importing the configurator parameter file is displayed.
Step 6 Click Add File, select the file generated in the preceding step for obtaining the
project configurations, and click Next.
Step 7 When an import success dialog box is displayed, click OK. The following page is
displayed.
Figure 1-19 Network design
The BMC logical network and Outer_OM logical network can be on the same VLAN and the same
network segment. The setting method is as follows:
a In the navigation tree on the left, choose NE Logical Network Design.
b Set Logical Network Name in the records whose Logical Network Type is
BMC_OM1 and Outer_OM1 to the same value, for example,
Outer_OM1_IVS3800_01.
c Click Next and then click Next.
Step 8 Set the network segment address and IP address range according to the network
plan, and click Next, as shown in the following page.
Figure 1-20 Network segment allocation
Do not change the Inner_OM and Inner_Service addresses. If you change the addresses, the
operation will fail and capacity expansion cannot be performed.
The following table describes the IP address input modes.
Table 1-4 IP address input modes
IP Address Input Mode Description
By Network VLAN Plan network segments based on logical network

planes. That is, assign one network segment to each
logical network plane.
By VPN Plan network segments based on VPNs. A VPN can

have multiple network segments. Click to add
network segments. After the planning, click Assign IP.
By One Address Segment Plan a network segment, in which IP addresses will be

automatically assigned to VPNs. Click to add
network segments. After the planning, click Assign IP.
Step 9 Set network plan parameters based on the site requirements.

You are advised to use the default settings and click Network Design for the tool to
automatically generate the detailed network IP address information. Then, the following
page is displayed.
Figure 1-21 Generating the parameter file
Click Next and perform the following steps to adjust the network configuration if
necessary:
a In the IP Network Segment Assignment area, adjust the values of Start IP and End IP
based on the value of IP Required Num, and click Next.
b In the Detailed IP Address Design area, adjust the value of IP based on the value of
IP Network Segment and click Next.
c In the NE Account Management area, record the user name, password, IP address,
and login URL, and click Next.
d In the Interconnection Design area, record the eSight connection information and
click Next.
e In the CSP Design area, set App Name and App ID, and click Next.
Step 10 Set VNF Version (CSP) to V100R019Cxx and VNF Scene (CSP) to
VERTICAL_AUTO_ARM.
Step 11 Select. The system automatically generates a configuration file. When the
configuration file is generated, the dialog box shown in the following figure is
displayed.
Figure 1-22 Configuration file generated successfully
Step 12 Click this dialog box to download the configuration file. Then decompress the file
to obtain the JSON file.
Step 13 Click Next. In the Generate Report area that is displayed, click Generate LLD
report. The system automatically generates a low level design (LLD) report, as
Figure 1-23 Generating an LLD report
Step 14 Click this dialog box to download the LLD report package. Then decompress the
package to obtain the LLD report (Excel file).
Step 15 Open the LLD report. When the message shown in the following figure is
displayed, click Enable Content.
Figure 1-24 Security warning
Step 16 On the Cabinet Layout sheet, click Please click. The system automatically
generates the plan.
----End
2 Hardware Installation
2.1 Introduction
In this experiment, you will master how to install Intelligent Vision-related hardware and
devices and physically connect them.
2.1.2 Objectives
 Understand how to install Intelligent Vision-related hardware.
 Master the installation method of Intelligent Vision-related network hardware.

2.2.1 Installing the Switch Hardware
Obtain the model of the switch on the live network and the corresponding product
documentation. Install the switch and connect power cables according to the product
documentation. This section uses CloudEngine 6800 series switches as an example.
2.2.1.1 Cabinet Requirements

Step 1 The CE5800, CE6800 (420 mm deep), and CE8850-32CQ-EI can be installed in a
cabinet with a depth not less than 600 mm. The CE6800 (600 mm deep) can be
installed in a cabinet with a depth not less than 600 mm. The CE7800, CE8850-
64CQ-EI, CE8860, CE8861, and CE8868 can be installed in a cabinet with a depth
not less than 800 mm.
Step 2 On a switch, the side with power modules and fan modules installed is the power
supply side, and the side with service ports is the port side. To leave sufficient
space for cabling, the vertical distance from the port side to the interior side of the
cabinet door must be no less than 130 mm, and the distance from the power
supply side to the interior side of the cabinet door must be no less than 70 mm.
Step 3 The cabinet must have reliable ground points to ground the switches.
Step 4 When the CE8800&7800&6800&5800 series switches need to be installed in the
same cabinet with a CE12800 switch, keep the distance between the front and
rear mounting rails in the range of 700 mm to 800 mm.
----End
2.2.1.2 Installing a Switch in the Cabinet

The directions of the port side and power supply side of the switch in the cabinet depend
on the actual installation scenario. (For example, in the typical data center scenario, if
the switch needs to be connected to the server and installed in the same cabinet as the
server, the port side of the switch and the port side of the server are installed in the same
direction, facilitating the connection to the server.) You can determine whether to install
mounting brackets A, B and C on the interface side or power supply side of the switch
and ensure that the rear mounting bracket does not touch the cabinet door. Figures in
this document are only examples.
If the distance between front and rear mounting bars does not meet the requirement,
use a pair of guide rails or a tray instead. In this case, purchase the guide rails or tray
beforehand.
The following table lists the mapping between mounting brackets.
Table 2-1 Mapping between mounting brackets
Step 1 Measure the distance between the front and rear mounting bars in the cabinet.
The mounting brackets, mounting bracket installation methods, and mounting
bracket guide rails vary depending on the obtained distance. For details, see Table
2-2
Figure 2-1 Measuring the distance between mounting bars.
Step 2 Use M4 screws to install mounting brackets on the switch. The following table
lists the installation methods for different distances between mounting bars.
Table 2-2 Selection of mounting brackets and rear mounting bracket guide rails
Step 3 Install two floating nuts on each mounting bar on the front and rear sides of the
cabinet. A total of eight floating nuts are installed.
Step 4 Connect the ground cable to the switch and place the other end of the ground
cable on the top of the switch. The ground points of the CE6850HI, CE6855-
48T6Q-HI, CE6856-48T6Q-HI, CE6850U-HI, and CE6875EI are located at the front
of the switch (power supply side).
Step 5 Use M6 screws to install guide rails on the front mounting bars.
Step 6 Hold the switch with both hands, align the mounting ears on both sides of the
switch with the guide rails, and slowly insert the switch into the cabinet.
Step 7 Use M6 screws to secure the switch to the cabinet.

Step 8 Connect the ground cable to the ground point.
Figure 2-2 Installing the switch
----End
2.2.1.3 Installing Modules on a Switch

 If a switch is delivered with the power and fan modules installed, you do not
need to install them again.
 Before installing the power and fan modules, remove the filler panel.
 When only one power module is installed, install a power module filler panel
on the empty power module slot.
 A switch must have two working fan modules to ensure normal operating.
 Two fan modules cannot be replaced at the same time. The replacement time
of a single fan module cannot exceed 3 minutes.
 Power modules can be fixed by captive screws or latches and are installed in
different modes.
 Power and fan modules are hot swappable. The procedures for installing and
removing a fan module are the same as the procedures for installing and
removing a power module fixed by captive screws. The following provides the
procedure for installing and removing a power module as an example.
Fixed by captive screws
Install a power module into a power supply slot of the switch and fasten the captive
screws on the panel of the power module.
Figure 2-3 Fixed by captive screws
Fixed by latches
Horizontally insert the power module into the slot until the power module is completely
inserted into the slot. Then, the latch is automatically locked.
Figure 2-4 Fixed by latches
2.2.1.4 Device Connection

Connect switches as shown in the following figure.
Figure 2-5 Device connection
The following table describes the device numbers.

Table 2-3 Device numbers
2.2.2 Installing the Server Hardware

The installation procedures for different product models are similar. The following uses
the IVS3800S V2 as an example to describe the installation procedure.
2.2.3 Physical Network Connections

2.2.3.1 Physical Network Connections of the IVS3800C V2 and IVS3800R V2
The IVS3800C V2 or IVS3800R V2 is a 2 U server. Each provides two GE electrical ports for
the management plane and three 10GE optical ports for the service plane. Multiple
switches can be configured in stack mode.
Figure 2-6 IVS3800C V2 physical connections
 The silkscreen of the slot where the 10GE network adapter is located is SLOT7.
 The silkscreen of the slots for GE network adapters on the left is OCP(NIC)1, and that on the
right is OCP(NIC)2.
Figure 2-7 IVS3800R V2 physical connections
right is OCP(NIC)2.
The following table describes the logical numbers.
Table 2-4 Logical numbers
1, 2 IVS3800C V2: 1, 2, and 3 in SLOT7 Service planes (Inner_Service

IVS3800R V2: 1, 2, and 3 in SLOT1 and Outer_Service planes)
3, 4 1 and 2 in OCP(NIC)1 Management planes

(Inner_OM and Outer_OM
planes)
5 Mgmt Management network port of

the server
6 - Switch stack port
7 - DAD port of the switch
 Ports 1 and 2 must be bonded in LACP mode, and ports 3 and 4 must be bonded in
active/standby mode to improve network reliability.
 The PoE function must be disabled for the switch to ensure server network connectivity.
2.2.3.2 IVS3800F V2 Physical Network Connections

The IVS3800F V2 is a 4 U server. It provides two GE electrical ports for the management
plane and three 10GE optical ports for the service plane. Switches must be stacked.
Figure 2-8 IVS3800F V2 physical connections
right is OCP(NIC)2.
1, 2 1, 2, 3 in SLOT3 Service planes (Inner_Service and

Outer_Service planes)
3, 4 1, 2, and 3 in OCP(NIC)1 Management planes (Inner_OM and

Outer_OM planes)
5 Mgmt Management network port of the

server
 Ports 1 and 2 must be bonded in LACP mode, and ports 3 and 4 must be bonded in
active/standby mode to improve network reliability.
2.2.3.3 IVS3800S V2 Physical Network Connections
The IVS3800S V2 and IVS3800SH V2 support GE electrical ports or 10GE optical ports for
the service plane. If a server is configured with 10GE optical ports, you must use the 10GE
optical ports for connection to ensure network connectivity of the service plane after the
installation.
Before the arrival of service optical switches or server optical modules, you can use GE
electrical ports for service commissioning. After the arrival of service optical switches
or server optical modules, you can switch back to 10GE optical ports.
The IVS3800S V2 is a 4 U server. The server provides two GE electrical ports for the
management plane and a maximum of six GE electrical ports for the service plane. When
only one server is deployed, the number of electrical service ports can be flexibly
configured based on service requirements. When two or more servers are deployed, all
the six GE ports on the service plane must be connected to switches.
Figure 2-9 Physical connection diagram (GE electrical ports for the service plane)
The silkscreen of the slots for GE network adapters on the left is OCP(NIC)1, and that on the
right is OCP(NIC)2.
1, 2 3 and 4 in OCP(NIC)1 Service planes (Inner_Service and

1, 2, 3, and 4 in OCP(NIC)2 Outer_Service planes)
3, 4 1 and 2 in OCP(NIC)1 Management planes (Inner_OM and

Outer_OM planes)
5 Mgmt Management network port of the server

The IVS3800S V2 also allows you to use 10GE optical ports to replace six GE electrical
ports on the service plane.
Figure 2-10 Physical connection diagram (10GE optical ports for the service plane)
right is OCP(NIC)2.
1, 2 10GE: 1 and 2 in SLOT7 Service planes (Inner_Service and

GE: 3 and 4 in OCP(NIC)1 Outer_Service planes)
and 1, 2, 3, and 4 in
OCP(NIC)2

Outer_OM planes)

 In the physical connection diagram, ports 1 and 2 must be bonded in LACP mode, and ports
3 and 4 must be bonded in active/standby mode to improve network reliability.
2.2.3.4 IVS3800SH V2 Physical Network Connections
The IVS3800S V2 and IVS3800SH V2 support GE electrical ports or 10GE optical

ports for the service plane. If a server is configured with 10GE optical ports, you must
use the 10GE optical ports for connection to ensure network connectivity of the service
plane after the installation. Before the arrival of service optical switches or server
optical modules, you can use GE electrical ports for service commissioning. After the
arrival of service optical switches or server optical modules, you can switch back to
10GE optical ports.
The IVS3800SH V2 is a 4 U server. The server provides two GE electrical ports for the
management plane and a maximum of six GE electrical ports for the service plane. When
only one server is deployed, the number of electrical service ports can be flexibly
configured based on service requirements. When two or more servers are deployed, all
the six GE ports on the service plane must be connected to switches.
Figure 2-11 Physical connection diagram (GE electrical ports for the service plane)
The silkscreen of the slots for GE network adapters on the left is OCP(NIC)1, and that on the
right is OCP(NIC)2.
1, 2 3 and 4 in OCP(NIC)1 Service planes (Inner_Service and

1, 2, 3, and 4 in OCP(NIC)2 Outer_Service planes)

Outer_OM planes)
The IVS3800SH V2 also allows you to use 10GE optical ports to replace six GE electrical
ports on the service plane.
Figure 2-12 Physical connection diagram (10GE optical ports for the service plane)
right is OCP(NIC)2.
1, 2 10GE: 1 and 2 in SLOT3 Service planes (Inner_Service and

GE: 3 and 4 in OCP(NIC)1 Outer_Service planes)
and 1, 2, 3, and 4 in
OCP(NIC)2

Outer_OM planes)

In the physical connection diagram, ports 1 and 2 must be bonded in LACP mode, and ports 3
and 4 must be bonded in active/standby mode to improve network reliability.
The PoE function must be disabled for the switch to ensure server network connectivity.
3 Network Configuration
3.1 Introduction
After completing this experiment, you will be able to configure switches during the
construction of the Intelligent Vision platform.
3.1.2 Objectives
 Master the basic data configuration of the switch.
 Learn how to configure switch stack.
 Learn how to divide VLANs of switches.

3.2.1 Configuring Basic Data
This section describes how to configure basic data, including the switch name,
management IP address, and system time. Perform the following operations:
Step 1 Use a serial cable to connect the local computer to the console port of the switch.
 Connect the DB9 connector of the console cable delivered with the product to
the 9-pin serial port on the computer, and connect the RJ-45 connector to the
console port on the switch.
Portable computers do not have DB-9 COM ports. In this case, a USB-to-COM converter is
required.
Figure 3-1 Connecting to the switch through the console port
Step 2 Use PuTTY to log in to the console port of the switch. In the PuTTY window,
configure the following login information and click Open.
Figure 3-2 Logging in to the switch through the console port
The following table describes the parameter values.

Table 3-1 Parameter values
Parameter Value
Connection type Serial
Serial line Select COM1, COM2, or another serial port based on

the serial port of the computer to be connected.
You can choose Device Manager > Ports on the
computer to query the serial port information of the
computer.
If the serial port information is not clear, connect the
ports one by one.
"Speed" "9600"
Step 3 (Optional) Set a password for logging in to the switch through the serial port. This
password is required only when you log in to the switch for the first time.
An initial password is required for the first login via the console.
Continue to set it? [Y/N]: y
Set a password and keep it safe! Otherwise you will not be able to login via the console.
Please configure the login password (8-16)
Enter Password: // The password is in ciphertext and is not displayed on the GUI.
Confirm Password:
The password is a string of 8 to 16 case-sensitive characters. The password must contain at least two
types of the following characters: uppercase letters, lowercase letters, digits, and special characters.
The special characters do not include the question mark (?) or space character.
Step 4 Configure the switch name and management IP address.
<HUAWEI>system-view # Going to the system view

[~HUAWEI]sysname S1_LSW_EOR01 # Configuring the switch name to S1_LSW_EOR01
[*HUAWEI]commit # Submit
[~S1_LSW_EOR01]
[~S1_LSW_EOR01]interface meth 0/0/0 # Accessing the meth 0/0/0 interface view.
[*S1_LSW_EOR01-MEth0/0/0]ip address 10.1.0.1 255.255.255.0 # Configuring the switch gateway
address and subnet mask to 10.1.0.1 and 255.255.255.0
[*S1_LSW_EOR01-MEth0/0/0]commit # Submitting the configuration
[~S1_LSW_EOR01-MEth0/0/0]return # Return
Step 5 Optional: Configure data for the user to log in based on STelnet. Configure the
expert user and the password Changeme_123. After the configuration is
successful, use the PuTTY to log in to the switch management port. You need to
change the password upon first login based on STelnet. Configure the information
only when you need to remotely access a switch on the live network.
<S1_LSW_EOR01>system-view // Going to the system view

[~S1_LSW_EOR01]stelnet server enable // Enabling the STelnet service
Info: Succeeded in starting the Stelnet server.
[*S1_LSW_EOR01]rsa local-key-pair create // Generating a local key pair on the server
The key name will be: expert_Host

The range of public key size is (512 ~ 2048).
NOTE: Key pair generation will take a short while.
Input the bits in the modulus [default = 2048]:2048 // The host key consists of 2048 bits.
[*S1_LSW_EOR01]user-interface vty 0 4 // Going to the VTY user interface
[*S1_LSW_EOR01-ui-vty0-4]authentication-mode aaa // Configuring the authentication mode on the
VTY user interface to AAA
[*S1_LSW_EOR01-ui-vty0-4]protocol inbound ssh // Configuring the VTY user interface to support SSH
[*S1_LSW_EOR01-ui-vty0-4]quit // Exiting the current operation view
[*S1_LSW_EOR01]aaa // Entering the AAA view
[*S1_LSW_EOR01-aaa]local-user expert password irreversible-cipher Changeme_123 // Configuring
the local user name expert and password Changeme_123
Info: A new user is added.
[*S1_LSW_EOR01-aaa]local-user expert level ? // Querying the user level. For switches whose version
is earlier than V100R006C00, the level ranges from 0 to 15.
INTEGER<0-3> Value // For switches of the V100R006C00 or a later version, when command-
privilege level exists, the level ranges from 0 to 15; when command-privilege level does not exist, the
level ranges from 0 to 3.
[*S1_LSW_EOR01-aaa]local-user expert level 3 // Configuring the priority of the local expert user to
the management level (highest value obtained in the preceding command)
[*S1_LSW_EOR01-aaa]local-user expert service-type ssh // Configuring the access type of the local
user to SSH
[*S1_LSW_EOR01-aaa]quit // Exiting the current operation view
[*S1_LSW_EOR01]ssh user expert authentication-type password // Configuring the SSH user
authentication mode to password
Info: Succeeded in adding a new SSH user.
[*S1_LSW_EOR01]ssh user expert service-type stelnet // Configuring the service mode of the SSH user
expert to STelnet
[*S1_LSW_EOR01]commit // Submitting the configuration
Step 6 Optional: Configure the switch time zone. You need to configure this information
only when the time zone on the live network is different from the default time
zone.
clock timezone time-zone-name { add | minus } offset

In Beijing, set the local time zone to BJ.
The default UTC time is London time. During the configuration, the expected time zone is the default
UTC time zone minus the offset. The configuration is as follows:
<S1_LSW_EOR01>clock timezone BJ add 08:00:00 # Configuring the time zone to Beijing time
<S1_LSW_EOR01>clock datetime 0:0:0 2012-12-01 # Configuring the date to 0:0:0 2012-12-01
<S1_LSW_EOR01>save # Saving the configuration.
Step 7 (Optional) Connect to the NTP server. You need to connect to the NTP server only
when an independent NTP server is planned on the live network.
When an external NTP server is connected, the client and server passwords are authenticated (NTP
authentication). Then, the client synchronizes data only with devices that pass the authentication,
improving the network security. If NTP authentication is not configured on the NTP server, you do not
need to configure NTP authentication on the client. The following describes the configuration in the
two scenarios:
NTP authentication not configured on the NTP server
[~S1_LSW_EOR01]ntp unicast-server 10.1.1.1 vpn-instance VRF_OM
// Connecting to the external NTP server. In this example, the IP address of the external NTP server is
10.1.1.1. vpn-instance VRF_OM: VPN instance used for interworking with the NTP server. If no VPN
instance is available, you do not need to add this parameter.
[~S1_LSW_EOR01]commit // Submitting the configuration
NTP authentication configured on the server
[~S1_LSW_EOR01]ntp authentication enable // Enabling NTP authentication
[*S1_LSW_EOR01]ntp authentication-keyid 42 authentication-mode hmac-sha256 Hello@123456 //
Configuring the NTP authentication key
[*S1_LSW_EOR01]ntp trusted authentication-keyid 42 // Claiming a trusted key
[~S1_LSW_EOR01]ntp unicast-server 10.1.1.1 authentication-keyid 42 vpn-instance VRF_OM//
Connecting to an external NTP server and using the key with the ID 42 for encryption
Step 8 (Optional) Configure the daylight saving time (DST). This step is performed only
when the DST is configured in the local place of the carrier.
Run clock daylight-saving-time to configure the DST. The following configurations are supported:
a Configure an absolute DST, which is valid only in the current year.

b clock daylight-saving-time time-zone-name one-year start-time start-date end-time end-
date offset
c Configure the periodic DST in Start time+End time format.
clock daylight-saving-time time-zone-name { repeating | repeating } start-time start-date1 end-time

end-date1 offset [ start-year [ end-year ]]
Configure the periodic DST in Start week+End week format.
clock daylight-saving-time time-zone-name repeating start-time { first | second | third | fourth | last }
weekday month end-time { first | second | third | fourth | last } weekday month offset [ start-year
[ end-year ]]
Assume that the DST time is NY. Set the DST duration from 00:00 on the first Sunday in January to
00:00 on the first Sunday in April of each year from 2010 to 2020. To configure the DST one hour
earlier, run the following commands:
<S1_LSW_EOR01> system-view
[~S1_LSW_EOR01] clock daylight-saving-time NY repeating 0 first sun jan 0 first sun apr 2 2010 2020
[~S1_LSW_EOR01]commit // Submitting the configuration
Step 9 Save the switch configuration.
You can run commands to modify the current configuration of the device. However, the modifications
will be lost after a restart. To make your modifications valid after a restart, run save configuration-file
in the user view to save your configurations in the configuration file.
<S1_LSW_EOR01>save
The current configuration will be written to the device.
Are you sure to continue?[Y/N]y
Now saving the current configuration to the slot 0...
Save the configuration successfully.
Step 10 Repeat the preceding steps to configure other switches.

----End
3.2.2 Configuring Stacking

Stacking is a technology that virtualizes multiple switches into one switch. Switch
stacking provides high network reliability and scalability and simplifies network
management.
No stacking cable is connected between the switches before they are stacked. If stacking cables
are connected before stacking is configured, network loops may occur.
Before the configuration, ensure that you have obtained the stack data plan of the switch.
Step 1 Use the local computer to connect to the console port of the active switch.
<S1_LSW_EOR01>system-view # Going to the system view

[~S1_LSW_EOR01]stack # Going to the stack view
[~S1_LSW_EOR01-stack]stack member 1 priority 100 // Configuring the switch priority to 100 and
stack member ID to 1. If stack member IDs conflict with each other, the stack member IDs are
automatically configured after stacking
Info: The operation will take effect after reboot
[*S1_LSW_EOR01-stack]stack member 1 domain 10 // Configuring the switch stack domain ID to 10.
Different domain IDs are selected on the same network for different stacks.
Info: The operation will take effect after reboot.
[*S1_LSW_EOR01-stack]quit // Exiting the current configuration page
[~S1_LSW_EOR01]interface stack-port 1/1 // Going to the stack port view
[*S1_LSW_EOR01-Stack-Port1/1]port member-group interface 10GE 1/0/1 to 1/0/2 // Adding member
ports 10GE 1/0/1 and 10GE 1/0/2 to stack ports
[*S1_LSW_EOR01-Stack-Port1/1]quit // Exiting the current configuration page
[~S1_LSW_EOR01]return // Returning to the user view
<S1_LSW_EOR01>save // Saving the current configuration
Warning: The current configuration will be written to the device. Continue? [Y/N]:y // Confirming
Info: Please input the file name(*.cfg, *.zip, *.dat)[vrpcfg.zip]vrpcfg.zip
<S1_LSW_EOR01>reboot // Restarting the switch
Warning: The system will reboot. Continue? [Y/N]:y // Confirming
Step 2 Use serial cables to connect standby switches and configure stacks. Use stacking
ports 10GE 1/0/1 and 10GE 1/0/2 as an example.

[~S1_LSW_EOR02]stack # Going to the stack view
[~S1_LSW_EOR02-stack]stack member 1 priority 50
Info: The operation will take effect after reboot
[*S1_LSW_EOR02-stack]stack member 1 domain 10
Info: The operation will take effect after reboot.
[*S1_LSW_EOR02-stack]quit
[*S1_LSW_EOR02]commit
[~S1_LSW_EOR02]interface stack-port 1/1
[*S1_LSW_EOR02-Stack-Port1/1]port member-group interface 10GE 1/0/1 to 1/0/2
[*S1_LSW_EOR02-Stack-Port1/1]quit
[~S1_LSW_EOR02]return
<S1_LSW_EOR02>save
Warning: The current configuration will be written to the device. Continue? [Y/N]:y
Info: Please input the file name(*.cfg, *.zip, *.dat)[vrpcfg.zip]vrpcfg.zip

<S1_LSW_EOR02>reboot // Restarting the switch
Warning: The system will reboot. Continue? [Y/N]:y
Step 3 Repeat steps 1 and 2 to configure the second switch.

Step 4 Connect stack cables based on the switch stack data plan.
Step 5 Query the stack configuration. Wait for about 5 minutes and run the following
commands on the active switch to query the stack configuration. Devices whose
roles are master are active devices.
<S1_LSW_EOR01>display stack
--------------------------------------------------------------------------------
MemberID Role MAC Priority DeviceType Description
--------------------------------------------------------------------------------
1 Master 006c-2003-0740 100 CE5855-48T4S2Q-EI # Active switch
+2 Standby 006c-2003-0780 50 CE5855-48T4S2Q-EI # Standby switch
Step 6 Configure DAD. After stacking, configure DAD to check and process the dual-
active conflicts during stack split.
Configure switch S1_LSW_EOR01.

[~S1_LSW_EOR01]interface ge1/0/48 # Going to the ge1/0/48 interface view
[~S1_LSW_EOR01-GE1/0/48]dual-active detect mode direct # Configuring DAD of service ports
Warning: The interface will block common data packets, except BPDU packets. Continue? [Y/N]:Y #
Enter Y.
[*S1_LSW_EOR01-GE1/0/48]commit # Submitting the configuration
[~S1_LSW_EOR01-GE1/0/48]return # Return.
<S1_LSW_EOR01>save # Saving the configuration.
Step 7 Configure switch S1_LSW_EOR02.
<S1_LSW_EOR02>system-view
[~S1_LSW_EOR02]interface ge1/0/48
[~S1_LSW_EOR02-GE1/0/48]dual-active detect mode direct
Warning: The interface will block common data packets, except BPDU packets. Continue? [Y/N]:Y
[*S1_LSW_EOR02-GE1/0/48]commit
[~S1_LSW_EOR02-GE1/0/48]return
<S1_LSW_EOR02>save
----End
3.2.3 Configuring the Switch Network

You need to configure the network for each type of switch to ensure network
connectivity. The configuration content includes the VLAN ID, VLAN IF, switch interface
mode, and switch interfaces.
The logical network of the system consists of five network planes. You need to configure
the switch network based on the network plan. The following table provides an example
of the network plan.
Table 3-2 Data plan
Physical Port Switch Logical Configuration Default VLAN VLAN IF

for Connecting Network Requirement VLAN ID Alias Gateway and
a Server to a Subnet Mask
Switch
Device Device Device Configure access 200 BMC_ Gateway:

management management management interfaces on the OM 192.168.2.1
port (Mgmt switch network/BMC_ switch. Subnet mask:
port) OM Plan an 255.255.255.0
independent VLAN
ID.
Service Service Internal Configure trunk 400 Inner_ Network

management management management interfaces on the OM segment:
electrical port switch with network/Inner_ switch. 172.17.0.0/16
(GE electrical electrical ports OM Plan an
port) independent VLAN
ID.
External Configure trunk 300 Outer_ Gateway:

management interfaces on the OM 192.168.5.1
network/Outer_ switch. Subnet mask:
OM Plan an 255.255.255.0
independent VLAN
ID.
10GE optical Service optical Internal service Configure trunk 600 Inner_ Network
service port/GE port network/Inner_ interfaces on the Servic segment:
electrical switch/service Service switch. e 172.18.0.0/16
service port electrical port Plan an
independent VLAN
ID.
External service Configure trunk 500 Outer_ Gateway:

network/Outer_ interfaces on the Servic 192.168.11.1
Service switch. e Subnet mask:
Plan an 255.255.255.0
independent VLAN
ID.
For details about the switch port plan, see the Server Cable Connection sheet in the LLD
report.
This section uses the default VLAN IDs as an example. The actual switch configuration
may vary.
Configuring a Device Management Switch
Step 1 Log in to a device management switch.

Step 2 Create VLAN ID 200.
[~S1_LSW_EOR01]vlan 200
[*S1_LSW_EOR01-vlan200]description BMC_OM
[*S1_LSW_EOR01-vlan200]quit
Step 3 Configure the VLAN IF interface.
[~S1_LSW_EOR01]interface vlanif 200

[*S1_LSW_EOR01-Vlanif200]ip address 192.168.2.1 255.255.255.0
[*S1_LSW_EOR01-Vlanif200]quit
Step 4 Configure interfaces on the switch.
[~S1_LSW_EOR01]interface gigabitethernet 0/0/1

[*S1_LSW_EOR01-GigabitEthernet0/0/1]port link-type access
[*S1_LSW_EOR01-GigabitEthernet0/0/1]port default vlan 200
[*S1_LSW_EOR01-GigabitEthernet0/0/1]quit
Use the same method to configure other interfaces on the switch based on physical
connections.
[~S1_LSW_EOR01]quit
<S1_LSW_EOR01>save
Step 6 Query the configuration result.
<S1_LSW_EOR01>display current-configuration
----End
3.2.3.2 Configuring a Service Management Switch with Electrical Ports

Step 1 Log in to a service management switch with electrical ports.
Step 2 Create VLAN ID 300 and VLAN ID 400.
[*S1_LSW_EOR02-vlan300]description Inner_OM
[*S1_LSW_EOR02]vlan 300
[*S1_LSW_EOR02-vlan400]description Outer_OM

The network plane (Inner_OM) of VLAN 400 does not have a gateway. Therefore, you do not
need to configure the VLAN IF interface.

[~S1_LSW_EOR02]interface gigabitethernet 0/0/1

[*S1_LSW_EOR02-GigabitEthernet0/0/1]port link-type trunk
[*S1_LSW_EOR02-GigabitEthernet0/0/1]port trunk allow-pass vlan 300 400
[*S1_LSW_EOR02]interface gigabitethernet 1/0/1
[*S1_LSW_EOR02-GigabitEthernet1/0/1]port link-type trunk
[*S1_LSW_EOR02-GigabitEthernet1/0/1]port trunk allow-pass vlan 300 400
Use the same method to configure other interfaces on the switch based on physical
connections.
Two GE ports on the physical node are bonded in active/standby (bond=1) mode, so you
do not need to configure LACP on the switch.
[~S1_LSW_EOR02]quit
<S1_LSW_EOR02>save

----End
3.2.3.3 Configuring a Switch with Optical Service Ports/Electrical Service

Ports
Step 1 Log in to a switch with optical service ports/electrical service ports.
Step 2 Create VLAN ID 500 and VLAN ID 600.
[*S1_LSW_EOR03-vlan500]description Inner_Service
[*S1_LSW_EOR03]vlan 500
[*S1_LSW_EOR03-vlan600]description Outer_Service

The network plane (Inner_Service) of VLAN 600 does not have a gateway. Therefore, you do not
need to configure the VLAN IF interface.
If the server uses 10GE optical ports:

[~S1_LSW_EOR03]interface Eth-Trunk 1
[*S1_LSW_EOR03-Eth-Trunk1]port link-type trunk
[*S1_LSW_EOR03-Eth-Trunk1]port trunk allow-pass vlan 500 600
[*S1_LSW_EOR03-Eth-Trunk1]mode lacp-static
[*S1_LSW_EOR03-Eth-Trunk1]load-balance src-dst-ip
[*S1_LSW_EOR03-Eth-Trunk1]least active-linknumber 1
[*S1_LSW_EOR03-Eth-Trunk1]quit
[*S1_LSW_EOR03]interface 10GE1/0/1
[*S1_LSW_EOR03-10GE1/0/1]eth-trunk 1
[*S1_LSW_EOR03-10GE1/0/1]quit
[*S1_LSW_EOR03]interface 10GE2/0/1
[*S1_LSW_EOR03-10GE2/0/1]eth-trunk 1
[*S1_LSW_EOR03-10GE2/0/1]quit
If the server uses GE electrical ports:
[~S1_LSW_EOR03]interface Eth-Trunk 1
[*S1_LSW_EOR03-Eth-Trunk1]port link-type trunk
[*S1_LSW_EOR03-Eth-Trunk1]port trunk allow-pass vlan 500 600
[*S1_LSW_EOR03-Eth-Trunk1]mode lacp-static
[*S1_LSW_EOR03-Eth-Trunk1]load-balance src-dst-ip
[*S1_LSW_EOR03-Eth-Trunk1]least active-linknumber 1
[*S1_LSW_EOR03-Eth-Trunk1]quit
[*S1_LSW_EOR03-GigabitEthernet0/0/1]eth-trunk 1
[*S1_LSW_EOR03-GigabitEthernet1/0/1]eth-trunk 1
Use the same method to configure other interfaces on the switch based on physical connections.
Connection requirements for the standard network:
 For a server that uses 10GE optical ports, add the two switch ports connected
to the server to an Eth-Trunk.
 For a server that uses GE electrical ports, add the six switch ports connected to
the server to an Eth-Trunk.
 Add all switch ports connected to each server to an Eth-Trunk. Configure
different Eth-Trunks for different servers.
 If LACP (bond=4) has been configured for the service plane of the server, you
need to configure static LACP on the switch.
If the switch does not support the lacp-static mode, run the mode lacp command.
If the switch does not support the src-dst-ip mode, you are advised to use the src-ip mode.
If NAT is configured between the system and other components and the switch supports NAT, the
user-defined enhanced load balancing mode is recommended. If the switch cannot calculate hash
based on the port number of the Layer 4 protocol to implement load balancing, the network
bandwidth performance may deteriorate.
[~S1_LSW_EOR03]quit
<S1_LSW_EOR03>save
----End
4 Basic Configuration of the CSP
4.1 Introduction
After completing this experiment, you can master how to set basic parameters of the
Intelligent Vision platform, for example, configuring the remote access IP address of the
iBMC, time zone, time, and RAID card mode, ensuring that the systems deployed later
can run properly.
4.1.2 Objectives
 Master the iBMC configuration method.
 Learn how to set the server time and memory mode.
 Learn how to configure RAID for system disks and data disks.

4.2.1 Configuring the iBMC
Step 1 Configure iBMC remote management.
a Set the IP address of the computer to be in the same network segment as the
default iBMC IP address so that the computer can communicate with the server.
b Use a network cable to connect your computer to the iBMC port on the server.
c Visit https://192.168.2.100 and log in to the iBMC WebUI. The default user name and
password are Administrator and Admin@9000, respectively. If the iBMC IP address
has been configured, use the new IP address.
If you cannot access the iBMC login page on the computer, use either of the following methods
to rectify the fault:
 Add a route to the same network segment as the iBMC on the computer.
 If the computer is configured with a proxy server, disable the proxy server.
d Choose iBMC Settings > Network Settings and configure a new IP address as
planned, as shown in the following figure.
Figure 4-1 Configuring a new iBMC IP address
e Click Save.
f Use a network cable to connect the iBMC port to the switch based on the network
plan.
g Change the computer IP address to one in the same network segment as the new
iBMC IP address.
h Visit https://Newly configured iBMC IP address.
Step 2 Configure the time zone.

Choose iBMC Settings > Time Zone & NTP, set the time zone and NTP for the current city,
and click Save.
Figure 4-2 Setting the time zone
Step 3 Set the timeout interval.

a Choose Services > Web Services. Set Timeout Period (min) to the maximum value
480 to avoid forced logout during RAID configuration, and set Session Mode to
Shared.
Figure 4-3 Setting timeout parameters
b Choose Virtual Console. Set Timeout Period (min) to 0 to avoid forced logout during
CSP installation.
Figure 4-4 Setting the timeout interval of the console
Step 4 (Skip this step for the IVS3800SH V2 server.) Set the RAID controller card to work
in JBOD mode.
Choose System > Storage Management and set JBOD to Enable.
Figure 4-5 Setting JBOD
----End
4.2.2 Checking the Firmware Versions

Before the installation, you need to check the firmware version of the iBMC, BIOS, and
CPLD. If the firmware versions do not meet the requirements, the keyboard input may be
invalid during image package loading and the system may run abnormally after the
installation.
Step 1 Log in to the iBMC WebUI.

Step 2 Choose System > System Info. In the Mainboard Info area, check the iBMC, BIOS,
and CPLD firmware versions, as shown in the following figure.
Figure 4-6 Checking the firmware versions
− If the iBMC firmware version is not 5.62, upgrade or downgrade the iBMC
firmware.
− If the BIOS firmware version is not 1.25, upgrade or downgrade the BIOS
firmware.
− If the CPLD firmware version is not 3.12, upgrade or downgrade the CPLD
firmware.
− If the versions do not meet the requirements, download the firmware and
install the firmware at http://support.huawei.com/.
----End
4.2.3 Configuring Basic Data

Before deploying the system, you need to set key parameters in the BIOS to ensure
normal operating of the system.

Step 2 Configure the UTC time.
a In the Virtual Console area on the Home page, choose Start > HTML5 Integrated
Remote Console (Shared). The interface shown in the following figure is displayed.
Figure 4-7 Confirmation dialog box
b Click and select BIOS Setup to display the BIOS Setup menu upon server startup.
c Click and select Forced Restart. In the dialog box that is displayed, click OK to
forcibly restart the system.
d During the restart, when the interface shown in the following figure is displayed,
press Delete to enter the password input interface.
Figure 4-8 Restarting the server
e Enter the password and press Enter. The default password is Admin@9000. If the
system prompts you to change the password, press Enter.
The interface shown in the following figure is displayed.
Figure 4-9 Setup Utility interface
f Click the Main tab and set the system time. The CSP requires that the server time be
set to the UTC time.
For example, if Beijing time is 08:00, set the system time to 00:00 because the Beijing
time zone is UTC+8.
If New York time is 08:00, set the system time to 13:00 because the New York time zone
is UTC-5.
− Use the arrow keys on the keyboard to select System Time. Then set the time
in HH:MM:SS format.
− Use the arrow keys on the keyboard to select System Date. Then set the date in
MM/DD/YYYY format.
To switch among the hour, minute, and second settings, press Enter. To change a value, use the
following methods:
 Press + to increase the value by 1.

 Press - to decrease the value by 1.
 Press a number key to change the value.
Figure 4-10 Setting the system time
Step 3 Set Power Policy to Performance.

a Choose Advanced > Performance Config. The page shown in the following
figure is displayed.
Figure 4-11 Performance Config
b Set Power Policy to Performance.
Step 4 Configure the memory information.

a Choose Advanced > Memory Config. The page shown in the following figure is
displayed.
Figure 4-12 Memory Config
b Set Die Interleaving, Channel Interleaving 3Way, and NUMA to Enable, Rank
Interleaving to 4-way Interleave, One Numa Per Socket to Disabled, and
Memory Test to Disable.
Step 5 Disable the SMMU and CPU Prefetching functions.

a Choose Advanced > MISC Config. The MISC Config interface is displayed.
Figure 4-13 Navigating to the MISC Config interface
b Verify that Support Smmu and CPU Prefetching Configuration are set to
Disabled.
Figure 4-14 MISC Config interface
Step 6 Change the default BIOS password.

Click the Security tab. Then select Set Supervisor Password and press Enter. Enter the
current and new password, and confirm the new password, as shown in the following
figure.
Figure 4-15 Changing the BIOS password
Step 7 Disable the emergency hot spare function.

In the system, system disks are configured as a RAID 1 group. If the emergency hot spare
function is enabled when one system disk is faulty, a data disk will be used as the system
disk, causing system exceptions. Therefore, you need to disable the emergency hot spare
function.
a Choose Advanced, as shown in the following figure.
Figure 4-16 Advanced interface
b Select the required RAID controller card and press Enter. The main interface
shown in the following figure is displayed.
Figure 4-17 RAID controller card interface
c Choose Main Menu > Controller Management, as shown in the following

figure.
Figure 4-18 Controller Management
d Select Advanced Controller Properties and press Enter. The Advanced Controller
Properties interface is displayed, as shown in the following figure.
Figure 4-19 Advanced Controller Properties interface
e Select Spare and press Enter. The Spare interface is displayed, as shown in the
following figure.
Figure 4-20 Spare interface
f Set Emergency Spare to None and press Enter.

g Select Apply Changes and press Enter. Select OK and press Enter.
Step 8 Save the system settings.

a Press F10.
b When the system displays the message "Save configuration changes and reset and
exit?, click Yes to save the settings. The system automatically restarts to complete
the settings.
4.2.4 Configuring RAID Groups

The following table describes how to configure RAID groups for system disks and data
disks.
Table 4-1 Configuration description
Physical Node Configure RAID Configure RAID Groups for Data Disks
Type Groups for System (Yes/No)
Disks (Yes/No)
IVS3800S V2 Yes. RAID 1 with two No.

960 GB SSDs. The firmware state of SATA disks must
be set to JBOD.
IVS3800C V2 Yes. RAID 1 with two Yes. RAID 5 with six 3.84 TB SSDs.
960 GB SSDs. Yes. RAID 1 with two 3.84 TB SSDs.
Physical Node Configure RAID Configure RAID Groups for Data Disks
Type Groups for System (Yes/No)
Disks (Yes/No)
There are no SATA disks.
IVS3800R V2 Yes. RAID 1 with two Yes. RAID 5 with six 3.84 TB SSDs.
There are no SATA disks.
The NVMe disks automatically form a
RAID 0 group. No configuration is
required.
IVS3800F V2 Yes. RAID 1 with two Yes. RAID 5 with four 3.84 TB SSDs.
No for SATA disks. However, the
firmware state of SATA disks must be set
to JBOD.
The NVMe disks automatically form a
RAID 0 group. No configuration is
required.
----End
4.2.4.1 Configure RAID Groups for System Disks

The IVS3800 server uses the Avago3408iMR and Avago 3508 RAID controller cards, which
support RAID group creation on the iBMC WebUI. Therefore, you can configure RAID
groups on the iBMC WebUI.
The server uses two 960 GB SSDs as system disks to form a RAID 1 group. The storage
space displayed on the UI is about 90% of the hard disk space.

Step 2 On the iBMC WebUI, choose System > Storage Management.
Step 3 (Optional) If a logical drive exists in the Logical Drive area, delete the logical
drive.
a Move the pointer to the logical drive row and click .

b In the dialog box that is displayed, click Yes.
Figure 4-21 Deleting a logical drive
Step 4 Set Firmware State of hard disks to UNCONFIGURED GOOD.

a Select a system disk, for example, Disk0. In the Physical Drive Information area,
click Settings in the upper right corner and set Firmware State to
UNCONFIGURED GOOD, as shown in the following figure.
Figure 4-22 Setting the firmware state for the hard disk
b Click OK.
c Set Firmware State to UNCONFIGURED GOOD for the other system disk in the
same way.
By default, you need to set Disk0 and Disk1 for the IVS3800S V2, IVS3800C V2, and
IVS3800R V2, and Disk40 and Disk41 for the IVS3800F V2.
Step 5 Create a logical drive for the system disk.

a Click Add on the right of RAID Card1. The following page is displayed.
Figure 4-23 Creating a logical drive (IVS3800C V2 and IVS3800R V2)

Figure 4-24 Creating a logical drive (IVS3800F V2)

Figure 4-25 Creating a logical drive (IVS3800S V2)
The following table describes the parameters. Set the parameters according to the setting
method in the following table.
Name Name of the logical drive. Set this parameter to OS.
L2 Cache Indicates whether to enable CacheCade. Use the default value.
Strip Size Size of a data stripe on each physical drive. Use the default value.
Read Policy Data read policy of the logical drive. Use the default value.
Write Policy Data write policy of the logical drive. Use the default value.
IO Policy I/O policy for reading data from special Use the default value.
logical drives. This policy does not affect
cache pre-reading.
Drive Cache Cache policy of the physical drive. Use the default value.

Policy
Access Access policy of the logical drive. Use the default value.
Policy
Initialization Indicates whether to initialize the logical Select Quick Init. In the
State drive. dialog box that is
displayed, click OK.
RAID Level RAID level of the logical drive. Select 1.
Number of Number of physical disks per span when You do not need to set
Drives per the RAID level is 10, 50, or 60. this parameter.
Span
Physical Disks to be added to the logical drive. Select the system disks,
Drive for example, Disk0 and
Disk1.
By default:
 Select Disk0 and Disk1
for the IVS3800S V2,
IVS3800C V2, and
IVS3800R V2.
 Select Disk40 and
Disk41 for the
IVS3800F V2.
Capacity Capacity of the logical drive. The value is

automatically displayed
by the system and does
not need to be changed.
c Click Save. The system automatically creates the logical drive.

d Select the logical drive and check whether it is successfully created. As shown in the
following figure, if the name of the logical drive is OS and the hard disks under the
logical drive are those selected in Step 5, the logical drive is successfully created.
Figure 4-26 Checking the result
Step 6 Set the logical drive as the system boot drive.

a Select the logical drive created in Step 5 and click Settings in the Logical Drive
Information area.
b Set Boot Drive to Yes and click OK.
----End
Figure 4-27 Setting the system boot drive
4.2.4.2 Configuring RAID Groups for Data Disks (IVS3800F V2)

a Select a hard disk, for example, Disk0. In the Physical Drive Information area,
b Click OK.
c Set Firmware State to UNCONFIGURED GOOD for other data disks in the same
way.
Step 3 Create a logical drive for the data disk.

a Click Add on the right of RAID Card1. The following page is displayed.
Figure 4-29 Creating a RAID 5 logical drive
The following table describes the parameters. Set the parameters by referring to the
Setting column.
Name Name of the logical drive.  For RAID 5, enter common.

 For RAID 1, enter mp.
L2 Cache Indicates whether to enable Use the default value.

CacheCade.
Strip Size Size of a data stripe on each Use the default value.
physical drive.
Read Policy Data read policy of the logical Use the default value.
drive.
Write Policy Data write policy of the logical Use the default value.
drive.
IO Policy I/O policy for reading data from Use the default value.
special logical drives. This policy
does not affect cache pre-
reading.
Drive Cache Cache policy of the physical Use the default value. Select
Policy drive. Disk's Default.
Access Policy Access policy of the logical drive. Use the default value.
Initialization Indicates whether to initialize Select Quick Init. In the dialog

State the logical drive. box that is displayed, click OK.
RAID Level RAID level of the logical drive.  If you select Disk0 to Disk3,
select 5.
 If you select Disk4 to Disk5,
select 1.
Number of Drives Number of physical disks per You do not need to set this
per Span span when the RAID level is 10, parameter.
50, or 60.
Physical Drive Disks to be added to the logical By default:

drive.  For RAID 5, select Disk0 to
Disk3.
 For RAID1, select Disk4 to
Disk5.
Capacity Capacity of the logical drive.  RAID 5:

common: all space
 RAID 1:
 mp: all space
b Click Save. The system automatically creates the logical drive.

c Select the logical drive and check whether it is successfully created.
For example, as shown in the following figure, if the name of the logical drive is
common, the RAID level is the level selected in Step 3, and the hard disks under the
logical drive are the hard disks selected in Step 3, the logical drive is successfully created.
----End
4.2.4.3 Configuring RAID Groups for Data Disks (IVS3800C V2 and

IVS3800R V2)
a Select a hard disk, for example, Disk2. In the Physical Drive Information area,
b Click OK.
c Set Firmware State to UNCONFIGURED GOOD for other data disks in the same
way.
In full configuration, you need to set this parameter for data disks from Disk2 to Disk9.
Step 3 Create a logical drive for the data disk.

The following table describes the parameters.
Name Name of the logical drive.  For RAID 5, enter a value as

required, for example,
safe_data or common.
 For RAID1, enter mp.
L2 Cache Indicates whether to enable Use the default value.

CacheCade.
Strip Size Size of a data stripe on each Use the default value.
physical drive.
Read Policy Data read policy of the logical Use the default value.
drive.
Write Policy Data write policy of the logical Use the default value.
drive.
IO Policy I/O policy for reading data Use the default value.
from special logical drives. This
policy does not affect cache
pre-reading.
Drive Cache Cache policy of the physical Use the default value. Select

Policy drive. Disk's Default.
Access Policy Access policy of the logical Use the default value.
drive.
Initialization Indicates whether to initialize Select Quick Init. In the dialog

State the logical drive. box that is displayed, click OK.
RAID Level RAID level of the logical drive.  If Disk2 to Disk7 are selected,
select 5.
 If Disk8 and Disk9 are
selected, select 1.
Number of Drives Number of physical disks per You do not need to set this
per Span span when the RAID level is 10, parameter.
50, or 60.
Physical Drive Disks to be added to the By default:

logical drive.  For RAID 5, select Disk2 to
Disk7.
 For RAID 1, select Disk8 and
Disk9.
Capacity Capacity of the logical drive.  RAID 5:

safe_data: 101 GB
common: remaining space
 RAID 1:
mp: all space
a Click Add on the right of RAID Card1. Select Disk2 to Disk7 and manually change the
capacity to 101 GB, as shown in the following figure.
Figure 4-33 Creating a safe_data logical drive
b Click Save. The system automatically creates the logical drive.

c Select the logical drive and check whether it is successfully created. For
example, as shown in the following figure, if the name of the logical drive is
safe_data, the RAID level is the level selected in Step 3, and the hard disks
under the logical drive are the hard disks selected in Step 3, the logical drive is
successfully created.
d Use the same method to create the common logical drive. Select Disk2 to
Disk7. The capacity and RAID level are automatically displayed. After the
configuration is complete, view the configuration result.
e Create the mp logical drive. Create RAID 1 based on the parameter description,
set RAID Level to 1, and select Disk8 and Disk9. The following figure shows the
configuration.
f After the configuration is complete, click Save and check whether the
configuration is correct, as shown in the following figure.
----End
4.2.4.4 Configuring the SATA Disk Firmware State (IVS3800S V2 and

IVS3800F V2)
If the physical node type is IVS3800S V2 or IVS3800F V2, set the firmware state of SATA
disks for RAID 5 to JBOD.

Step 3 Check whether the firmware state of hard disks is set to JBOD.
a Select a hard disk, for example, Disk11, click Settings in the Physical Drive
Information area, and set Firmware State to JBOD, as shown in the following
figure.
b Click OK. In the dialog box that is displayed, click Yes.

c Set Firmware State to JBOD for other data disks in the same way.
In full configuration mode, the SATA disks are Disk2 to Disk35 and Disk40 to Disk43 for
the IVS3800S V2, and Disk6 to Disk35 for the IVS3800F V2.
----End
5 Installing the CSP
5.1 Introduction
This experiment provides guidance on how to install the cloud service platform (CSP).
5.1.2 Objectives
 Learn how to install the active and standby management nodes using an ISO
file.
 Learn how to install service nodes.

5.2.1 Disabling Memory Interleaving
Before installing the CSP, you need to disable the memory interleaving function for the
IVS3800C V2, IVS3800R V2, and IVS3800F V2 by referring to this section. You do not need
to disable the memory interleaving function for the IVS3800S V2 and IVS3800SH V2.

Step 2 Log in to the BIOS.
a. In the Virtual Console area on the Home page, choose Start > HTML5 Integrated
Figure 5-1 Remote console
b. Click and select BIOS Setup to display the BIOS Setup menu upon server startup.
c. Click and select Forced Restart. In the dialog box that is displayed, click OK to
forcibly restart the system.
d. During the restart, when the interface shown in the following figure is displayed, press
Delete and then enter the password on the password input page. Press Enter to enter the
BIOS interface.
Figure 5-2 Setup Utility interface
Step 3 Disable the memory interleaving function.

Choose Advanced > Memory Config and set Channel Interleaving 3Way to Disable.
Step 4 Save the system settings. Press F10. The message "Save configuration changes and
reset and exit?" is displayed. Click Yes to save the settings. The system
automatically restarts to complete the settings.
----End
5.2.2 Installing the Management Node in a Single-Node System

5.2.2.1 Installing the Management Node Using an ISO File
The server that contains the CSPOM container is a management node.
On the Server Node sheet of the LLD report, servers whose Node Type is management
node are CSP management nodes.
5.2.2.1.1 Preparing for the Installation
Before the installation, obtain the software installation image package
EulerOS_CSP_IVS3000_Vxxxx_ARM.iso.
The hardware environment requirements are as follows:
 The hardware installation, cable connections, and configurations have been
completed.
 Your computer is connected to the iBMC network of the server, and the
transmission rate is higher than 30 Mbit/s.
5.2.2.1.2 Mounting the ISO File

Step 1 Open a browser, enter http://iBMC IP address of the server in the address box, and
press Enter. On the page that is displayed, enter the user name and password, and
click Login.
Step 2 In the Virtual Console area on the Home page, choose Start > HTML5 Integrated
Step 3 Click and select CD/DVD.
Step 4 Mount the DVD-ROM image file, as shown in the following figure.
Figure 5-5 Mounting the DVD-ROM image file

During the installation, do not disconnect the mounted DVD-ROM image. Otherwise,
the CSP installation will fail.
----End
5.2.2.1.3 Installing the CSP Using an ISO File
Step 1 Click and select Forced Restart. In the dialog box that is displayed, click OK
to forcibly restart the system.
If the information shown in the following figure is displayed, the CSP installation starts.
Step 2 Wait for 2 to 3 minutes. The CSP configuration page is displayed. Complete the
CSP configuration according to the process shown in the following figure.
The data used in the configuration example is for reference only. Use the data
specified in the live network plan during the installation.
The following figure describes the parameters and data required for installing the
CSP.
Is New Installation New Installation: Install the CSP for the Select New
first time. Installation.
Reinstallation: Reinstall the CSP.
Install Mode Single Install: Install the service server Select Single Install.
in single-node system mode.
Cluster Install: Install the service server
in cluster mode.
Install Mode Include CSP: Install the CSP Select Include CSP.
management node.

Exclude CSP: Install a service node.
CSP Network Standard: In standard networking, the Set this parameter to

IP address convergence technology is Standard.
used, and the internal management
plane is isolated from the service plane.
Therefore, the switch must support
static LACP.
CSP Network Internal VLAN ID: VLAN ID Obtain the values

Configurations corresponding to the CSP internal from the Installation
management plane (Inner_OM). Parameter Value sheet
in the LLD report.
Internal Network Segment: network
segment and subnet mask length of the
CSP internal management plane
(Inner_OM).
The value is in Network segment/Prefix
length format.
Example:
If the subnet mask is 255.255.255.0, the
prefix length is 24.
prefix length is 8.
Internal Network Start IP: start IP

address of the CSP internal
management plane (Inner_OM).
Internal Network End IP: end IP address

of the CSP internal management plane
(Inner_OM).
Host IP: IP address used by the CSP host

to communicate with the internal
External VLAN ID: VLAN ID

corresponding to the CSP external
management plane (Outer_OM).
External IP: IP address used by the CSP

host to communicate with the external
External Subnet Mask: subnet mask.

External Gateway: gateway.
Floating IP: floating IP address used for

logging in to the CSP OM portal.
Input Management Node1 Host IP address On the Installation

Node Name Parameter Value sheet
in the LLD report,
obtain the value of
Server Name based on
the value of Host IP.
For example, the value
of Server Name
corresponding to the
host IP address is as
follows:
If the management
node is ivs3800sv2-
om-01, enter
ivs3800sv2-om-01.
Note:
The node name must
meet the following
requirements:
Cannot be empty and
can contain a
maximum of 25
characters.
Consists of lowercase
letters, digits (0 to 9),
periods (.), and
hyphens (-).
Must start with a
lowercase letter or
digit.
Cannot contain two or
more consecutive
hyphens (-) or periods
(.).
During installation, you can press the up and down arrow keys to switch parameters,
press Tab to switch the parameter area, press Enter to select a parameter, and press Esc
to exit the installation interface. If you press any other keys, there will be no response.
Exercise caution when pressing Esc.
Step 3 Check whether the system automatically restarts after the installation. The restart
takes about 5 minutes. After the restart, the remote login page is displayed, as
shown in the following figure. For the IVS3800S V2 or IVS3800SH V2, the system
does not automatically restart. Press Enter to switch to the remote login page. If a
blank screen is displayed on the remote login page, press Enter.
Figure 5-6 EulerOS login prompt
If the message "Installation Successful" is not displayed during the installation and the
page shown in the following figure is displayed, perform the following steps to check
system deployment logs. Ensure that the installation is successful and then perform
subsequent operations.
a Log in to the system background as the cspexpert user. The default password
of the cspexpert user is mt2017@cspos@RD.
b Run the su - root command to switch to the root user. The default password of
the root user is cnp200@cspos@RD.
c Run the cat /opt/csp/csp_edge_log/edge_install.log command to check the
installation progress. If 100% is displayed in the command output, the CSP or
service operating system is installed successfully.
CSP-OM install process 100%
Step 4 On the remote login page of the server, click Disconnect to disconnect the
CD/DVD-ROM image, as shown in the following figure.
Figure 5-7 Disconnecting the CD/DVD-ROM image
Step 5 On the iBMC WebUI, choose System > BIOS Settings, set Effective to Permanent
and Boot Medium to Hard Drive, and click Save.
Figure 5-8 Modifying the system boot items
5.2.2.1.4 Logging In to the CSP OM Portal

Step 1 Connect your computer to the Outer_OM network of the service management
switch with electrical ports.
Step 2 Open a browser, enter https://Floating IP address:31943 in the address box, and
press Enter. Ignore the displayed security warning. The CSP login page is
displayed. Enter the default user name (admin) and password (Changeme_123).
Change the default password as prompted upon your first login.
Wait about 2 to 3 minutes after the installation is complete. Then log in to the CSP OM portal.
Use Google Chrome v46.0 or a later version to log in to the CSP OM portal.
You are advised to disable the translation function of the browser. Otherwise, garbled characters
may appear.
Step 3 Check for faulty servers and containers at the bottom of the Home page. If there
is no faulty server or container, the CSP is successfully installed.
Figure 5-9 Checking the server and container status
----End
5.2.2.2 Installing Service Nodes Using an ISO File

The server that does not contain the CSPOM container is a service node. On the Server
Node sheet of the LLD report, servers whose Node Type is service node are CSP service
nodes. If no service node exists in the environment, skip this section.
EulerOS_CSP_IVS3000_Vxx_ARM.iso.
completed.
During the installation, set the parameters in strict accordance with the LLD report.
Otherwise, the installation may fail or O&M exceptions may occur after the installation.
The following table describes the parameters and data required for installing a service
node.
Table 5-1 Installation parameters
Is New New Installation: Install the CSP for the first Select New
Installation time. Installation.
Install Mode Single Install: Install the service server in Select Single Install.
single-node system mode.

Cluster Install: Install the service server in
cluster mode.
Install Mode Include CSP (First Node): Install the CSP Select Exclude CSP.
master management node.
Include CSP (Other Node): Install the CSP
slave management nodes.
CSP Network Standard: In standard networking, the IP Set this parameter to

address convergence technology is used, and Standard.
the internal management plane is isolated
from the service plane. Therefore, the switch
must support static LACP.
Application Internal VLAN ID: VLAN ID corresponding to Obtain the values

Network the CSP internal management plane from the Installation
Configuration (Inner_OM). Parameter Value
s sheet in the LLD
Host IP: IP address used by the CSP host to report.
communicate with the internal management
plane (Inner_OM).
External VLAN ID: VLAN ID corresponding to

the CSP external management plane
(Outer_OM).

click Login.

----End
5.2.2.2.3 Installing the Operating System on a Service Node Using an ISO Image
Figure 5-12 Starting CSP installation
service node configuration according to the process shown in the following figure.
 During installation, you can press the up and down arrow keys to switch
parameters, press Tab to switch the parameter area, press Enter to select a
parameter, and press Esc to exit the installation interface. If you press any
other keys, there will be no response.
Figure 5-13 Configuring the service nodes

It takes about 20 to 60 minutes for the CSP to complete the configuration after you specify
required parameters. You are advised to pay attention to the installation progress and do not
switch to other pages to ensure successful installation.
shown in the following figure. If a blank screen is displayed on the remote login
page, press Enter.
Figure 5-14 Euler OS login prompt
If the message "Installation Successful" is not displayed during the installation and the page
shown in the preceding figure is displayed, perform the following steps to check system
deployment logs. Ensure that the installation is successful and then perform subsequent
operations.
Log in to the system background as the cspexpert user. The default password of the cspexpert
user is mt2017@cspos@RD.
Run the su - root command to switch to the root user. The default password of the root user is
cnp200@cspos@RD.
Run the cat /opt/csp/csp_edge_log/edge_install.log command to check the installation progress. If
100% is displayed in the command output, the CSP or service operating system is installed
successfully.

----End
5.2.3 Installing Management Nodes in a Cluster

5.2.3.1 Installing the Slave Management Nodes Using an ISO File
The server that contains the CSPOM container is a management node.
On the Server Node sheet of the LLD report, servers whose Node Type is management
node are CSP management nodes.
In the cluster scenario, three servers contain the CSPOM container. You need to manually
specify one server as the CSP master management node and the other two servers as CSP
 You need to install the CSP master management node after all CSP slave
management nodes.
 The IVS3800C V2 and IVS3800R V2 can only be used as service nodes.

EulerOS_CSP_IVS3000_Vxxxx_ARM.iso.
completed.

click Login.
Step 4 Mount the DVD-ROM image file, as shown in the following figure. Click Connect.
----End
The following figure describes the parameters and data required for installing the
CSP.
Is New Installation New Installation: Install the CSP for the Select New
first time. Installation.
Install Mode Single Install: Install the service server in Select Cluster
single-node system mode. Install.
cluster mode.
Install Mode Include CSP (First Node): Install the CSP Select Include CSP
master management node. (Other Node).
CSP Network Standard: In standard networking, the IP Set this parameter

address convergence technology is used, to Standard.
and the internal management plane is
isolated from the service plane. Therefore,
the switch must support static LACP.
CSP Network Internal VLAN ID: VLAN ID corresponding Obtain the values
Configurations to the CSP internal management plane from the
(Inner_OM). Installation
Parameter Value
Host IP: IP address used by the CSP host to sheet in the LLD
communicate with the internal report.
External VLAN ID: VLAN ID corresponding

to the CSP external management plane
(Outer_OM).

 During installation, you can press the up and down arrow keys to switch parameters,
press Tab to switch the parameter area, press Enter to select a parameter, and press
Esc to exit the installation interface. If you press any other keys, there will be no
response.
 Exercise caution when pressing Esc.
Figure 5-19 CSP configuration
It takes about 20–60 minutes for the CSP to complete the configuration after you specify required
parameters. You are advised to pay attention to the installation progress and do not switch to
other pages to ensure successful installation.
page, press Enter.
shown in the following figure is displayed, perform the following steps to check system
operations.
a Log in to the system background as the cspexpert user. The default password
of the cspexpert user is mt2017@cspos@RD.
b Run the su - root command to switch to the root user. The default password of
the root user is cnp200@cspos@RD.
c Run the cat /opt/csp/csp_edge_log/edge_install.log command to check the
installation progress. If 100% is displayed in the command output, the CSP or
service operating system is installed successfully.

Figure 5-22 Modifying the system boot items
5.2.3.2 Installing the Master Management Node Using an ISO File

EulerOS_CSP_IVS3000_Vxxx_ARM.iso.
completed.
The following figure describes the parameters and data required for installing the CSP.

click Login.
----End
If the information shown in the following figure is displayed, the CSP installation
starts.
Is New New Installation: Install the CSP for the Select New Installation.
Installation first time.
Install Mode Single Install: Install the service server in Select Cluster Install.
cluster mode.
Install Mode Include CSP (First Node): Install the CSP Select Include CSP (First
master management node. Node).
Include CSP (Other Node): Install the
CSP slave management nodes.

address convergence technology is used, Standard.
and the internal management plane is
isolated from the service plane.
Therefore, the switch must support static
LACP.
CSP Network Internal VLAN ID: VLAN ID Obtain the values from
Configurations corresponding to the CSP internal the Installation
management plane (Inner_OM). Parameter Value sheet
in the LLD report.
Internal Network Segment: network
segment and subnet mask length of the
CSP internal management plane
(Inner_OM).
The value is in Network segment/Prefix
length format.
Example:
If the subnet mask is 255.0.0.0, the prefix
length is 8.
Internal Network Start IP: start IP

address of the CSP internal management
plane (Inner_OM).
Internal Network End IP: end IP address

of the CSP internal management plane
(Inner_OM).
Host IP: IP address used by the CSP host

to communicate with the internal
Host IP of Secondary Node 1 and Host IP

of Secondary Node 2: host IP addresses
of two slave management nodes.
External VLAN ID: VLAN ID

corresponding to the CSP external

External Subnet Mask: subnet mask.
External Gateway: gateway.
Floating IP: floating IP address used for

logging in to the CSP OM portal.
Input Node1 Host IP address On the Installation

Management Node2 Host IP address Parameter Value sheet
Node Name in the LLD report, obtain
Node3 Host IP address
the value of Server
Name based on the
value of Host IP.
For example, the value
of Server Name
corresponding to the
host IP address is as
follows:
If the management
node is ivs3800sv2-om-
01, enter ivs3800sv2-
om-01.
Note:
The node name must
meet the following
requirements:
Cannot be empty and
can contain a maximum
of 25 characters.
Consists of lowercase
letters, digits (0 to 9),
periods (.), and hyphens
(-).
Must start with a
lowercase letter or digit.
Cannot contain two or
more consecutive
hyphens (-) or periods
(.).
Input root Input password: password of the root Enter

password of user of the slave management nodes. cnp200@cspos@RD.
other nodes
 During installation, you can press the up and down arrow keys to switch
parameters, press Tab to switch the parameter area, press Enter to select a
parameter, and press Esc to exit the installation interface. If you press any
other keys, there will be no response.

Figure 5-26 CSP configuration
page, press Enter.
operations.
cnp200@cspos@RD.
successfully.
----End
5.2.3.2.4 Logging In to the CSP OM Portal
Step 1 Connect your computer to the Outer_OM network of the service management
switch with electrical ports.
Step 2 Open a browser, enter https://Floating IP address:31943 in the address box, and
press Enter. Ignore the displayed security warning. The CSP login page is
displayed. Enter the default user name (admin) and password (Changeme_123).
Change the default password as prompted upon your first login.
Figure 5-29 CSP OM portal login page
 Wait about 2 to 3 minutes after the installation is complete. Then log in to the CSP OM
portal.
 Use Google Chrome v46.0 or a later version to log in to the CSP OM portal.
 You are advised to disable the translation function of the browser. Otherwise, garbled
characters may appear.
Step 3 Check for faulty servers and containers at the bottom of the Home page. If there
is no faulty server or container, the CSP is successfully installed.
Figure 5-30 Checking the server and container status
----End
5.2.3.3 Installing Service Nodes Using an ISO File

The server that does not contain the CSPOM container is a service node. On the Server
Node sheet of the LLD report, servers whose Node Type is service node are CSP service
nodes.
EulerOS_CSP_IVS3000_Vxx_ARM.iso.
completed.
The following table describes the parameters and data required for installing a service
node.
Is New New Installation: Install the CSP for the first Select New
Installation time. Installation.
Install Mode Single Install: Install the service server in Select Cluster Install.
cluster mode.
Install Mode Include CSP (First Node): Install the CSP Select Exclude CSP.
master management node.

address convergence technology is used, and Standard.
the internal management plane is isolated
from the service plane. Therefore, the switch
must support static LACP.
Application Internal VLAN ID: VLAN ID corresponding to Obtain the values

Network the CSP internal management plane from the Installation
Configurations (Inner_OM). Parameter Value
sheet in the LLD
Host IP: IP address used by the CSP host to report.
communicate with the internal management
plane (Inner_OM).
External VLAN ID: VLAN ID corresponding to

the CSP external management plane
(Outer_OM).

click Login.

----End
5.2.3.3.3 Installing the Operating System on a Service Node Using an ISO Image
If the information shown in the following figure is displayed, the CSP installation
starts.
service node configuration according to the process shown in the following figure.
During installation, you can press the up and down arrow keys to switch parameters,
press Tab to switch the parameter area, press Enter to select a parameter, and press Esc
to exit the installation interface. If you press any other keys, there will be no response.
Figure 5-34 Configuring the service nodes
page, press Enter.
operations.
cnp200@cspos@RD.
successfully.
----End
5.2.4 Enabling Memory Interleaving

After installing the CSP, you need to enable the memory interleaving function for the
IVS3800C V2, IVS3800R V2, and IVS3800F V2 by referring to this section. You do not need
to enable the memory interleaving function for the IVS3800S V2 and IVS3800SH V2.

Step 2 Log in to the BIOS. Choose Advanced > Memory Config and set Channel
Interleaving 3Way to Enable, as shown in the following figure.
Step 3 Save the system settings.

Press F10. The message "Save configuration changes and reset and exit?" is
displayed. Click Yes to save the settings. The system automatically restarts to
complete the settings.
----End
5.2.5 Disabling the Automatic Backup Function

You must disable the automatic backup function to prevent operation failures.
Step 1 Log in to the CSP OM portal as the admin user.

Step 2 Choose Application Lifecycle > Backup&Restore > Auto Backup and click
Configure.
Step 3 Disable the automatic backup function.
Figure 5-38 Disabling automatic backup
Step 4 Click Save. When the system displays a message, indicating that the automatic
backup policy is set, click OK.
5.2.6 Setting the System Time

5.2.6.1 Setting the Time Zone and DST
Step 1 Choose System > Time.
Step 2 In the Time Zone area, set basic information as prompted and click Apply.
Time Zone Time zone.
DST Indicates whether the DST is enabled.

Yes: The DST is enabled.
No: The DST is disabled.
DST Start/DST End This parameter is valid only when DST is set to Yes.
By Date: start and end dates of the DST. The start date cannot
be later than the end date. The DST starts from March by
default.
By·Week: start and end weeks of the DST. The start week
cannot be later than the end week. The DST starts from March
by default.
Offset (min) Time offset after the DST is used. The offset cannot be shorter
than 1 minute, and cannot be longer than the whole DST
period.
Set the time zone to the local time zone according to the preceding table. You need to
set the DST only when the DST is specified in the local time zone.
Figure 5-39 Setting the time zone and DST
5.2.6.2 Configuring the NTP Server

If the system time is different from the local standard time, configure the NTP server
data to ensure time consistency.
The requirements for the NTP server are as follows:
 The NTP server supports NTP V3 and later versions.
 The network latency between the NTP server and application system is less
than 100 milliseconds.
 The clock offset of the NTP server is less than 100 milliseconds.
 The number of stratums of the·NTP server is as small as possible. It is
recommended that the number be three or less.
 It is recommended that the NTP server be deployed in redundancy mode.

Step 2 In the External Clock Source area, configure the NTP server and click Apply.
Step 3 (Optional) Enter the authentication key ID and value. If you enter the
authentication key ID for the configured NTP server, you must enter the
authentication key value. The key value must be the same as the key ID. Click
Apply.
Figure 5-40 Setting the external clock source
 For the values of the NTP server parameters, see the Cloud Mgmt
Interconnection sheet of the LLD document.
 The authentication key ID and value are set based on the configured NTP
server. Only SHA-1-type values are supported.
 The system supports a maximum of four NTP servers. If multiple NTP servers
are available, the system selects the one with the least time offset from the
system time for time synchronization.
 If a single NTP server is available, it serves as the external clock source and its
IP address is displayed in green.
 If multiple NTP servers are available, the server with the least time offset from
the system time is the optimal external clock source, and the IP address of that
server is displayed in green.
 If an NTP server is available and forced time synchronization is enabled, the
system can synchronize time from the NTP server even when the time
difference between the NTP server and the system exceeds 3s (preset
threshold).
 If an NTP server is available but forcible time synchronization is disabled, and
the time difference between the system and the NTP server exceeds 3s, the
system reports the alarm "ALM-6501 Abnormal NTP Connection Status" and
does not synchronize time from the NTP server.
 If an NTP server is available and the time difference between the NTP server
and the system is less than 3s, the system can synchronize time from the NTP
server regardless of whether forcible synchronization is enabled or not.
5.2.6.3 Setting the Time Synchronization Policy

By default, if the time difference between the NTP server and the system exceeds 3s, the
system will not synchronize time from the NTP server. You can enable Forced
Synchronization to force the system to synchronize time from the NTP server
unconditionally.

Step 2 In the Forced Time Synchronization area, enable Forced Synchronization.
Figure 5-41 Setting the time synchronization policy
 The Forced Synchronization parameter is disabled by default.

 If Forced Synchronization is disabled and the time difference between the
system and the NTP server exceeds 3s, the system does not synchronize time
from the NTP server.
 If Forced Synchronization is enabled, the system synchronizes time from the
NTP server regardless of whether the time difference between the system and
the NTP server exceeds 3s or not. 2s will be synchronized every 1 minute until
the time is consistent.
6 IVS Application System Deployment
6.1 Introduction
This experiment provides guidance on how to deploy IVS applications, including
managing service nodes, uploading a software package and a process file, and deploying
applications.
6.1.2 Objectives
 Learn how to configure service nodes to be managed.
 Learn how to upload software packages and process files.
 Learn how to deploy applications and verify the deployment.
 Learn how to create a RAID group and import a license.

6.2.1 Managing Service Nodes
Before deploying an application, add the service nodes to the CSP for subsequent
application deployment, server management, and resource monitoring. If there is no
service node, skip this section.
Server Name Server name of a service node. Server name of a service node.
The value is a string of up to 63 The value is a string of up to
characters. 63 characters.
The value must start and end The value must start and end

with a lowercase letter or digit. It with a lowercase letter or digit.
can contain lowercase letters, It can contain lowercase
digits, periods (.), and hyphens letters, digits, periods (.), and
(-). Periods (.) and hyphens (-) in hyphens (-). Periods (.) and
the value must be separated by hyphens (-) in the value must
letters or digits. be separated by letters or
digits. Use the value of Server
Name on the Server Node
sheet in the LLD report.
Server IP Address Host IP address of a service node. Use the value of HOSTIP on
the Server Node sheet in the
LLD report.
Step 1 Log in to the CSP OM portal and choose Resources > Edge Site Resources >
Servers.
Step 2 Click Add Server. The following page is displayed.
Figure 6-1 Add Servers page
Step 3 Select a mode to add servers based on the number of service nodes.
Manually adding servers one by one:
a Select manually next to Add Servers.
b Set Server Name and Server IP Address based on the description in the
preceding table and click Save. If there are multiple service nodes, click to
add them one by one.
c After all service nodes are added, click Add Servers. When Status is Available,
the management is successful.
d Importing servers in batches:

a Select in a batch (recommended) next to Add Servers.
b Download the template file according to UI instructions.
c Open the template file, set Server Name and Server IP Address according
to Table 6-1, and save the template file.
d Click Upload, select the saved template file, and upload it.
When the system displays a message indicating upload success, click Add Servers.
When Status is Available, the management is successful.
6.2.2 Uploading a Software Package and a Process File

6.2.2.1 Uploading a Software Package
Before installing the IVS application, you need to upload the software package
IVS3000_Vxx_ARM_Full.tar.gz to the CSP OM portal. During application deployment, the
CSP automatically installs the application software in the application software package.
Step 1 Choose Software > Inventory > Software package.

Step 2 On the Software package page, click Add and select the software packages to
upload.
Step 3 Click Upload.
Do not switch the page during the upload. Otherwise, the upload may fail.
Step 4 After the software package is uploaded, it is automatically displayed on the

software package list. You can click the software package name to view the
service software packages and service container images contained in the
application software package.
6.2.2.2 Uploading a Process File

Before deploying the application, you need to upload the process file
TOSCA_IVS3000_V100R019C30_ARM.tar.gz. The process file contains the specifications of
each container, such as the CPU size and memory size. During application deployment,
the CSP automatically creates containers based on the container specifications.
Step 1 Choose Software > Inventory > Process Files.

Step 2 On the Process Files page, click Add and select the required process file to upload.
When adding a process file for the first time, click Add a Process File.
Step 3 Click Select upload file and upload the process file of the application. Then,
configure basic information about the process file, including the version, publisher,
and description.
After the process file is imported, the process file name is automatically generated. Do not
change the file name.
Figure 6-2 Adding a process file
Step 4 Click Create. After being added, the process file is automatically displayed on the
process file list.
6.2.3 Deploying Applications and Verifying the Installation

6.2.3.1 Deploying Applications
Use the software package, process file, and JSON file exported from the CloudDesign to
install the application.
The software package contains the application software. The process file contains the
specifications of each container. The JSON file contains the number of containers and the
corresponding storage space.
Step 1 Choose Application Lifecycle > Deployment.

Step 2 Click Create.
Step 3 Select Use Existing Servers and click Next.
On the page that is displayed, select the process file uploaded in Uploading a Process
File. The system automatically finds the matching software package, as shown in the
following figure.
Figure 6-3 Preparing a process file and a software package
Step 4 Click Next. The following page is displayed. Click Import Configuration File, select
the JSON file generated in the LLD design guide, and import the configuration file.
Figure 6-4 Setting application parameters
After the configuration file is imported, you only need to change the value of appname.
clusterassign Reserved. The default value is NULL. clusterassign
LANGUAGE Language of the IVS application UI. LANGUAGE
appid Application ID. Enter an integer ranging from 1 to appid

65535.
appname Application name, which can be customized. appname
apptype Application type. The default value cannot be changed. apptype
appversion Application version. The default value cannot be appversion

changed.
applabels Application label. The default value cannot be applabels

changed.
Step 5 Set Timeout Interval to 1 hour.

Step 6 Click Next, confirm the information, and click Next.
Step 7 Click Start. The system automatically checks the parameter settings, container
image, network information, and node resources.
Step 8 When the check succeeds, click Deploy.

When a message is displayed indicating task execution success, click Details to view
application details.
Do not perform any operations after the installation starts.
Step 9 Click the Execute Logs tab to view the installation progress, as shown in the
following figure.
----End
Figure 6-5 Execution Logs tab
When the message "IVS is installed successfully" is displayed, the installation is

successful. The installation takes about 30 to 260 minutes, depending on the number of
servers.
6.2.3.2 Verifying the Installation

6.2.3.2.1 Checking the Software Installation in the CSP
Step 2 Choose Application Lifecycle > Deployment and view the application status.
----End
6.2.3.2.2 Checking the Container Status
Step 2 Choose Resources > Edge Site Resources > Containers and check the container
status. If the containers are in Running state, the containers are normal.
----End
Figure 6-6 Container status
6.2.3.2.3 Checking the Single-Node System or Two-Node Cluster Status

Step 2 Choose Application Configuration > Configuration Management > Configuration >
Application Name > Two-Node Cluster and check the value of Status. If the value
of Status is Online or Standby, the single-node system or two-node cluster has
been created successfully.
----End
Figure 6-7 Single-node system/Two-node cluster status

When Role is Single-node system, the container is deployed in single-node system mode. In a
single-node system, single point of failures (SPOFs) may occur and services are interrupted
during capacity expansion.
6.2.3.2.4 Checking the Cluster Status

Application Name > Cluster and check the status. The cluster is normal if Status is
Online on the Surveillance, Analysis, and Common tab pages.
Figure 6-8 Cluster status
The cluster is automatically created after the application is installed. No manual intervention is
required.
----End
6.2.4 Creating RAID Groups

IVS3800S V2, IVS3800F V2, and IVS3800SH V2 servers use the software RAID technology
to create RAID 5 groups for data disks, and use the SafeVideo function to ensure high
data reliability.
You need to manually configure RAID groups on the CSP OM portal.
Application Name > Storage > Cloud Edge Storage.
Step 2 Create a RAID group, as shown in the following figure.
Figure 6-9 Configuring RAID group information
a Select a SafeVideo group and click Create RAID Group or Recreate RAID Group.
b Set RAID Configuration. Open the LLD report and check the value of RAID
Mode on the Solution Information sheet. If the value is Economic mode, set
RAID Configuration to Economic. If the value is Recommendation mode, set
RAID Configuration to Standard.
The following table lists the rules for creating RAID groups.
Table 6-3 Rules for creating RAID groups
RAID Level Description Rule
Recommended The system  If the number of hard disks ranges from

configuration automatically performs 4 to 14, the system creates one RAID
optimized group and one global hot spare disk.
configuration, ensuring  If the number of hard disks ranges from
high data reliability. 15 to 24, the system creates two RAID
groups and one global hot spare disk.
 If the number of hard disks ranges from
25 to 28, the system creates two RAID
groups and two global hot spare disks.
 If the number of hard disks ranges from
29 to 40, the system creates three RAID
groups and two global hot spare disks.
Software RAID groups cannot be created
for three or fewer hard disks.
Economical The system  If the number of hard disks ranges

configuration automatically performs from 4 to 21, the system creates one
the most economic RAID group and one global hot spare
configuration, ensuring disk.
high disk usage.  If the number of hard disks ranges
from 22 to 40, the system creates two
RAID groups and one global hot
spare disk.
Software RAID groups cannot be created
for three or fewer hard disks.
c Click Start to start a route test. The system starts to create RAID groups.
Step 3 (Optional) Enable the Writable upon RAID Failure function.

After the Writable upon RAID Failure function is enabled, if multiple hard disks are
faulty, the RAID group level is degraded from RAID 5 to RAID 0 and data can still
be written to the hard disks. However, if any hard disk in the RAID 0 group is faulty
again, data cannot be restored. To improve hard disk utilization, you can enable
this function. After this function is enabled, you must replace faulty disks promptly
if any.
After the Writable upon RAID Failure function is disabled, if multiple hard disks are
faulty, the RAID group becomes invalid and data cannot be written to the hard
disks. Then cameras' data will be written to the storage space of other containers,
which increases performance pressure of the other containers. In scenarios that
require high reliability, you can disable this function.
a Click Configure Writable upon RAID Failure.
b Click Enable or Disable in the lower part of the Configure Writable upon RAID
Failure dialog box.
c Click OK.
Step 4 If there are multiple SafeVideo groups, repeat the preceding steps to create RAID
groups.
Step 5 View the newly created RAID groups on the RAID group list, as shown in the
following figure. If Status is Normal, the RAID groups are successfully created.
Click Details to view the status of member disks and LUNs.
Figure 6-10 RAID groups
6.2.5 Importing a License

If the servers are all IVS3800S V2, no license is required for local domain camera access,
but a license is required for external domain camera access.
If there are other types of servers, you need to import the service license to implement
the corresponding function. Before applying for a license, you need to obtain the ESN of
the server.
When the application is redeployed, the ESN changes. You need to apply for a new
license.
The following table describes the functions of licenses in the system.
Table 6-4 License description
Category Project Code Project Description Feature Description
Networked 88035DQY IVS External Domain Number of external domain

sharing Access (Per Channel) cameras that can be connected.
One license is required for each
camera.
Algorithm 88035DRA IVS Algorithm Total number of recognition

manageme Repository (Per channels using multiple intelligent
nt Channel) analysis algorithms, including
facial recognition, personal
feature recognition, vehicle
recognition, license plate
recognition, facial recognition-
based access control, and list
import. One license is required for
each channel.
88036FYH IVS traffic-based The license requirement is the

scheduling (Images same as that in image-based

Per Second) facial recognition.
Video 88035DRD IVS Video Synopsis Number of concurrent video

synopsis, (Per Channel) synopsis channels. One license is
video required for each channel.
search,
and 88035DRE IVS Behavior Number of concurrent behavior
behavior Analysis (Per analysis channels. One license is
analysis Channel) required for each channel.
algorithms 88035DRF IVS Video Search Number of concurrent video
(Per Channel) search channels. One license is
required for each channel.
Face 88035DRL IVS Image-based Number of images processed by

algorithm Facial Recognition the FaceReg1100 facial
Basic Algorithm - recognition algorithm per second
FaceReg1100 in image mode. One license is
(Images Per Second) required for each image per
second.
88035DRR IVS Video-based Number of concurrent execution

Facial Recognition channels of the FaceReg1100
Basic Algorithm - facial recognition algorithm in
FaceReg1100 (Per video mode. One license is
Channel) required for each channel.
88036BDG IVS Image-based Number of images processed by

Facial Recognition the FaceReg1200 facial
Basic Algorithm - recognition algorithm per second
FaceReg1200 in image mode. One license is
(Images Per Second) required for each image per
second.
88036BDH IVS Video-based Number of concurrent execution

Facial Recognition channels of the FaceReg1200
Basic Algorithm - facial recognition algorithm in
FaceReg1200 (Per video mode. One license is
Channel) required for each channel.
88035DRG IVS Face Search Data search capacity of the face

Basic Package (Per search algorithm. One license is
Million Records) required per million records.
88035XLP IVS Dynamic Face FaceReg1100 facial recognition

Clustering Basic N:N clustering basic algorithm.
Algorithm (100,000 For example, one license is
x 100,000) - required for 100,000 x 100,000;
FaceReg1100 (Per two licenses are required for

Set) 200,000 x 200,000; 10 licenses are
required for 1 million x 1 million.
88036EWB IVS Dynamic Face FaceReg1200 facial recognition

Clustering Basic N:N clustering basic algorithm.
Algorithm (100,000 For example, one license is
x 100,000) - required for 100,000 x 100,000;
FaceReg1200 (Per two licenses are required for
Set) 200,000 x 200,000; 10 licenses are
required for 1 million x 1 million.
Person 88035DRN IVS Personal Feature Total number of concurrent

algorithm Recognition Basic execution channels of the
Algorithm (Per personal feature recognition
Channel) algorithm in video and image
modes. In video mode, one license
is required for each channel. In
image mode, one license is
required for each image per
second.
88035DRH IVS Person Search Data search capacity of the

Basic Package (Per person search algorithm. One
Million Records) license is required per million
records.
Vehicle 88035DRC IVS Vehicle Number of concurrent execution

algorithm Recognition Basic channels of the vehicle
for Hong Algorithm - recognition algorithm in Hong
Kong VehicleReID1100 - Kong (China), Macao (China),
(China), Hong Kong (China), Taiwan (China) and
Macao Macao (China), countries/regions outside China.
(China), Taiwan (China) and One license is required for each
Taiwan Countries/Regions channel.
(China) Outside China (Per
and Channel)
countries/r
egions 88035PYM IVS Vehicle Search Data search capacity of the
outside Basic Package - vehicle search algorithm in Hong
China Hong Kong (China), Kong (China), Macao (China),
Macao (China), Taiwan (China) and
Taiwan (China) and countries/regions outside China.
Countries/Regions One license is required per million
Outside China (Per records.
Million Records)
88035FHQ IVS License Plate Number of concurrent execution

Recognition channels of the Q-Free

Algorithm PlateReg2600 license plate
Management recognition algorithm in Hong
Software - Kong (China), Macao (China),
PlateReg2600 - Taiwan (China) and
Hong Kong (China), countries/regions outside China.
Macao (China), One license is required for each
Taiwan (China) and channel.
Countries/Regions
Outside China (Per
Channel)
88036EWA IVS Vehicle Number of concurrent execution

Recognition Basic channels of the VehicleReID1200
Algorithm - vehicle recognition algorithm.
VehicleReID1200 One license is required for each
(Per Channel) channel.
Vehicle 88035DRP IVS Vehicle Number of concurrent execution

algorithm Recognition Basic channels of the vehicle
for the Algorithm - recognition algorithm in the
Chinese VehicleReID1100 - Chinese mainland. One license is
mainland Chinese Mainland required for each channel.
(Per Channel)
88035DRQ IVS Pedestrian and Number of concurrent execution

Vehicle Data channels of the pedestrian and
Structuring Basic vehicle data structuring algorithm
Algorithm - Chinese in the Chinese mainland. One
Mainland (Per license is required for each
Channel) channel.
88035DRJ IVS Vehicle Search Data search capacity of the

Basic Package - vehicle search algorithm in the
Chinese Mainland Chinese mainland. One license is
(Per Million Records) required per million records.
Procedure
Step 1 Choose Application Lifecycle > Licenses > License Management. The License
Management page is displayed.
Step 2 Obtain the ESN for an application.

a Select the application.
b Obtain the ESN in the Basic Information area.
Step 3 Record the obtained ESN and apply for a license file by referring to the license
application guide released with the software version.
Step 4 Upload the license file.

a Choose Application Lifecycle > Licenses > License File Management.
b Select the required application name and click Upload License File.
c In the dialog box that is displayed, click Browse and select the license file that
you have obtained.
d Click OK.
Step 5 Activate the license file.

a Choose Application Lifecycle > Licenses > License Management.
b Select the required application name and click Activate.
c In the dialog box that displays the uploaded license files, select the license file
to be activated.
d Click Activate to activate the license file.
If the license status in the Basic Information area is Activated, the license file has been
activated successfully. You can view the detailed license information, as shown in the
following figure.
Figure 6-11 License information
6.2.6 Enabling the Automatic Backup Function

You need to enable the automatic backup function to ensure system reliability.

Step 2 Choose Application Lifecycle > Backup & Restore > Auto Backup. The Auto Backup
page is displayed.
Step 3 Click Configure. The following page is displayed.

Figure 6-12 Automatic backup configuration
Auto Backup Indicates whether to enable automatic backup.
Period You are advised to set this parameter to 1.

Note:
The recommended automatic backup period is one day,
which is the same as the Data Safe backup period. In this
way, the time of the CSP data can be the same as that of
the Data Safe data during restoration.
Start Time Set this parameter to 03:00.
Set this parameter to 03:00 to ensure that the backup task can be
completed correctly.
GaussDB Backup Maximum retention period of backup data packets in the

Retention Period GaussDB. By default, the system deletes backup data
packets whose retention period is longer than the
maximum at 02:00 every day.
You are advised to use the default value 7.
Step 4 Select SFTP for Network Backup and set parameters for the SFTP server.
If the backup data needs to be stored on a remote SFTP server, set the parameters based
on the site requirements, in which SFTP Server IP Address is set to an SFTP server IP
address that is on the same network segment as the CSP internal management network.
If the backup data needs to be stored on a local data disk of the server, set the
parameters according to the following table.
Table 6-6 SFTP server parameters
SFTP Server IP Address Set this parameter to the host IP address of the CSP
management node. You can perform the following
operations to obtain the value:
Choose Resources > Cloud Resources > Container List.
Enter ServiceCenter in the search box and obtain the
value of Host IP of the ServiceCenter container.
If the CSP management node is deployed in cluster mode, there

will be three ServiceCenter containers. You can select any one of
them.
SFTP Server Port No. SFTP server port number. Use the default value 22.
SFTP User Name FTP user name. Enter paas.
SFTP Password SFTP password. Set this parameter based on the site
requirements. The initial value is ps2017@cspos@RD.
Public Key Authentication If this parameter is selected, the backup server will be
authenticated to eliminate spoofing risks and improve
system reliability.
If Public Key Authentication is selected, a dialog box is

displayed. Configure the public key on the server following
instructions in the dialog box.
If this parameter is deselected, public key authentication will
not be enabled on the server.
Target Directory This parameter is mandatory. Perform the following

steps to set it:
1. Log in to the server where the active CSP
management node resides as the cspexpert user in
SSH mode.
2. Run the su - root command to switch to the root
user.
3. Run the df -h /opt/SmartData_D/G* command.
Select any directory that is mounted with a disk.
Replace the groupid and diskid variables in the
destination directory
/opt/SmartData_D/Ggroupid_diskid/backup/csp with
the values corresponding to the selected disk
directory.
The destination directory, for example,

/opt/SmartData_D/G0_0/backup/csp, varies according to the
actual environment.
Viewing the directories where disks are mounted
Step 5 Click Save. The system displays a message, indicating that the policy is successfully
set. Click OK.
----End
7 System Configuration
7.1 Introduction
This experiment provides guidance on how to perform other configurations after the IVS
is installed, including configuring floating gateways, changing host names, and
configuring storage policies.
7.1.2 Objectives
 Learn how to configure floating gateways and storage policies.
 Learn how to configure domains/clusters and host names.
 Learn how to configure NTP time synchronization for cameras.
 Learn how to configure the connection between the surveillance platform and
analysis platform.
 Learn how to install and start the client.

7.2.1 Changing Host Names
A server has two names in the system:
Server Name:
The value of Server Name is the node name specified during the CSP installation and also
the server name entered during service node management. This name cannot be
changed.
Host Name:
You can customize Host Name, which is displayed on the CSP OM portal. If you log in to
the server operating system through SSH, Host Name is the host name of the operating
system.
Because Server Name corresponds to the label on the server and cannot be changed after
the server is installed, you must set Server Name in strict accordance with the network
design template to facilitate subsequent operation and maintenance.
To facilitate understanding, you are advised to customize Host Name to distinguish
servers.
For example, if the server whose Server Name is ivs3800sv2-01 is installed in slot 5 of
cabinet A of the customer (customer code: hz), you can customize Host Name as hz-A-5.
1. Choose Resources > Edge Site Resource > Servers.
2. Select a server from the server list, click More, and choose Change Host Name.
3. Enter a host name in the Custom Host Name text box.
Comply with the following rules when customizing a host name:

 The host name must be a string of up to 50 characters, including digits, letters, and
hyphens (-).
 The host name cannot start or end with a hyphen (-). In addition, a host name
starting with a digit is not recommended.
 You are advised not to use special words in the computer field, such as reboot, in the
host name.
 The host name is not case-sensitive. The system automatically changes all the
uppercase letters into lowercase letters.
4. Click OK. Check whether the host name is changed.
If the server is performing operations such as backup, the system displays a message indicating
that the host name cannot be changed. In this case, change the host name after the server
backup is complete.
7.2.2 Configuring Floating Gateways for a Cluster

To ensure the normal running of the system, you need to set the floating gateway IP
address of the cluster.
Before using video-based intelligent analysis, you must configure the floating gateway IP
address of the cluster. Otherwise, intelligent analysis tasks will fail.
 Choose Application Configuration > Configuration Management >
Configuration > Application Name > Cluster > Surveillance.
 Click Nodes in the Operation column.
 Enter the floating gateway IP address and click Configure, as shown in the
following figure.
Figure 7-1 Configuring floating gateways for a cluster

 You can obtain the floating IP addresses from the Floating Gateway IP Addresses of a
Cluster table on the Installation Parameter Value sheet in the LLD report.
 Select any containers of the same type as those in the LLD report and enter the floating
gateway IP addresses. For example, three floating gateway IP addresses have been planned
for the MPUR containers in the LLD report, and there are five MPUR nodes on the CSP OM
portal. Then you can select any three of the MPUR nodes and enter the planned floating
gateway IP addresses.
7.2.3 Configuring Recording and Checkpoint Data Storage Policies

Application Name > Storage > Storage Policy.
Step 2 Select the service node for which you want to configure a storage policy.
 Batch configuration: Select service nodes and click Batch Edit.
 Single configuration: Click Edit next to a service node.
Step 3 Configure storage policies. The following table describes the parameters.
Node Name Name of an MPUR node.
External External service IP address of an MPUR node.

Service IP
Address
Space Full Policy used when the recording storage space is used up. The options
Policy are as follows:
Stop: Only recordings or images that have been stored for a period
longer than the storage period are recycled. When the storage space
is used up, the recording and image storage is stopped.
Overwrite: Recordings or images are overwritten based on the
following sequence: recordings or images whose storage period
expires > recordings or images for which no storage period is
configured > earliest recordings or images within the storage period.
Recycling Recording recycling policy. The options are as follows:

Policy By storage space: If the storage space is less than or equal to the
system threshold, recordings or images are recycled based on the
processing policy of insufficient storage space.
By storage period: If the storage period ends or the storage space is
less than or equal to the system threshold, recordings or images are
recycled based on the processing policy of insufficient storage space.
Third-Party Period for storing images uploaded by a third-party system through

Image Storage the northbound SDK.
Period (days)
Operation Edit: Button for modifying the storage policy for the corresponding
node.
Step 4 Click OK. The storage policy configuration is complete.

----End
7.2.4 Configuring Domain Names and Load Balancing Policies

Before service configuration, you can plan names for domains and clusters, facilitating
relevant personnel to search for information. You can configure a load balancing policy
based on the site requirements.
7.2.4.1 Configuring Domain Names

Application Name > Local Domain. Set Domain Name and Description as planned,
as shown in the following figure.
Figure 7-2 Setting the domain name and description
Step 2 Click Apply.

----End
7.2.4.2 Configuring the Cluster Name and Load Balancing Policy

Application Name > Cluster > Surveillance.
Step 2 Click Edit in the Operation column and configure Cluster Name and the load
balancing policy, as shown in the following figure.
Figure 7-3 Configuring the cluster name and load balancing policy
Load Balancing Indicates whether to enable load balancing. After load

balancing is enabled, a cluster can dynamically
balance service loads across nodes based on the node
statuses, preventing any individual node from getting
overloaded.
Fault Migration Indicates whether to enable fault-triggered migration.

After fault-triggered migration is enabled, if a cluster
detects a failed node, the cluster can quickly schedule
another normal node in the cluster to take over
services from the failed node to ensure proper
operating of services.
Step 3 Click Save.

----End
7.2.5 Configuring NTP Time Synchronization for Cameras

If you set the time on the camera web system separately, a camera-camera or camera-
server time difference may exist. The system provides the NTP synchronization function.
Cameras automatically synchronize time with the connected node, and the node
automatically synchronizes time with the management node, ensuring time consistency.
Configuration > Application Name > Local Domain > IPC NTP Service.
 ChooseSan NTP synchronization policy based on the site requirements.
Table 7-3 Camera NTP parameters
Enable Button for enabling NTP time synchronization on the node.

The node delivers NTP time synchronization configuration
to cameras and enables the NTP time synchronization
function for cameras. The cameras automatically
synchronize time with the node.
Disable Button for disabling NTP time synchronization on the node.

The node does not deliver NTP time synchronization
configuration to cameras and disables the NTP time
synchronization function for cameras.
Default The node does not deliver the NTP time synchronization
configuration to cameras, and the NTP time synchronization
configuration of cameras is used.
7.2.6 Configuring the Connection Between the Surveillance

Platform and the Analysis Platform
7.2.6.1 Connecting the Surveillance Platform to the Analysis Platform
To manage the surveillance platform and analysis platform on the iClient in a unified
manner, you need to configure the connection between the surveillance platform and the
analysis platform on the CSP OM portal of the surveillance platform.
 The surveillance platform and analysis platform are two service modules of the IVS
platform. The surveillance platform provides the image management service, including video
and image access, storage, and forwarding. The analysis platform provides the image
analysis and image search services, including intelligent service processing.
 Only the IVS platform of V100R019C20 or later versions supports unified management of
the surveillance platform and analysis platform on the iClient.
 A surveillance platform can connect to only one analysis platform, and an analysis platform
can connect to only one surveillance platform.
Step 1 Record the surveillance platform information.

a Log in to the CSP OM portal of the surveillance platform as the admin user.
b Record the value of Version for the ivs application on the home page.
c Choose Application Configuration > Configuration Management >
Configuration > Application Name > Two-Node Cluster, and record the value of
External Service IP of the VCNAPI and BMU nodes if they exist.
d Choose Application Configuration > Configuration Management >
Configuration > Application Name > Node, enter VCNAPI in the search box, and
press Enter to search for the VCNAPI node. Record the external service IP
address of the VCNAPI node. If the VCNAPI is deployed in a two-node cluster,
record the external service IP addresses of the two VCNAPI nodes.
Step 2 Record the analysis platform information.

a Log in to the CSP OM portal of the analysis platform as the admin user.
b Record the value of Version for the analysis platform application on the home
page.
c Choose Application Configuration > Configuration Management >
Configuration > Application Name > Two-Node Cluster, and record the value of
External Service IP for the NGINX node.
Step 3 Set the CUServerConnection and VCMConnection parameters of the

VCNSvcMgrService service on the surveillance platform.
b Choose Application Configuration > Configuration Management >
Configuration > Application Name > Unified Configuration. Click the
Surveillance Platform tab.
c Select VCNSvcMgrService from the Service drop-down list box.
d Set CUServerConnection.
i. Locate the row in which the value of Name is CUServerConnection and
click Edit on the right, as shown in the following figure.
Figure 7-4 Setting CUServerConnection
ii. Enter the IP address, port number, and version information of the
surveillance platform, in IP address,Port number,Version information
format. The following table describes the parameters.
IP Address Set this parameter to the external service IP address of the VCNAPI
node recorded in c .
Port Number The default value is 18531.
Version Set this parameter to the surveillance platform application version

information recorded in b .
In the NAT scenario, use NAT to separate the pre-NAT surveillance platform
information from the post-NAT surveillance platform information and
supplement VCNAPISurveillance Platform IP address,9900. Example:
10.10.10.11,18531,V100R019C50SPCxxxNAT10.164.151.211,15831,V100R019C50S
PCxxxVCNAPI10.10.10.11,9900
iii. Click Save.
e Set VCMConnection.
i. Locate the row in which the value of Name is VCMConnection and click
Edit on the right, as shown in the following figure.
Figure 7-5 Setting VCMConnection
ii. Enter the IP address, port number, and version information of the analysis
platform, in IP address,Port number,Version information format. The following
table describes the parameters.
IP Address Set this parameter to the external service IP address of the NGINX
node recorded in c .
Version Set this parameter to the analysis platform application version

information recorded in b .
In the NAT scenario, use NAT to separate the information about the analysis platform before and
after NAT. Example:
10.10.10.10,443,V100R019C50SPCxxxNAT10.164.151.211,223,V100R019C50SPCxxx
iii. Click Save.
Step 4 Configure the VCMAPIService service on the analysis platform and add an IP
address authentication whitelist.
 Log in to the CSP OM portal of the analysis platform as the admin user.
Configuration > Application Name > Unified Configuration > Analysis Platform.
 Select VCMAPIService from the Service drop-down list box.
 Click New on the right of IP Authentication Whitelist, as shown in the following
figure. The New dialog box is displayed.
Figure 7-6 Setting the IP authentication whitelist
 Set Type to IP, enter External Service IP of the VCNAPI node recorded in d , and
click Save.
 If the VCNAPI is deployed in a two-node cluster, add the external service IP
addresses of the two VCNAPI nodes to the whitelist.
 Repeat the preceding steps to add the values of External Service IP of the
VCNAPI and BMU nodes recorded in c to the IP address whitelist.
 Click Apply.
For a single-node system that integrates the storage, compute, and search capabilities, you do
not need to add the IP address authentication whitelist. You only need to enable the IP address
authentication bypass function.
7.2.6.2 Installing and Logging In to the iClient

Before performing service operations and verification, you need to install the iClient.
7.2.6.2.1 iClient Installation Requirements
Minimum configuration
 CPU: at least Intel quad-core with a clock speed that is greater than or equal to
3.2 GHz
 Memory: at least 3 GB
 Hard disk: at least 500 GB
 Operating system: 32-bit or 64-bit Windows 7 or Windows 10
 Video card: at least 1.0 GB (reference model: GeForce GTX 550 Ti)
 Network port: at least one 1000 Mbit/s (or higher) network port
 Monitor: at least 21.5-inch; recommended optimum resolution: 1920 x 1080
You are advised to set the monitor resolution to 1920 x 1080. Otherwise, the display may
be abnormal.
Recommended configuration
 CPU: eighth-generation Intel Core CPU or higher for desktop computers or
laptops
 Memory: at least 8 GB (DDR3 1600 MHz or higher)
 Hard disk: at least 500 GB
 Operating system: 32-bit or 64-bit Windows 7 or Windows 10
 Video card: Intel integrated graphics card with a display memory of more than
2.0 GB (Intel® HD Graphics 520 or higher is recommended)
 Network port: at least one 1000 Mbit/s (or higher) network port
 Monitor: at least 21.5-inch; recommended optimum resolution: 1920 x 1080
You are advised to set the monitor resolution to 1920 x 1080. Otherwise, the display may
be abnormal.
Live video specifications
The following table describes the number of live video channels supported under
different configurations.
Configuration A: I5-2400 CPU @3.10 GHz; 32-bit operating system; memory: 4 GB;
Windows 7 Professional Edition
Configuration B: I7-6600 CPU @3.2 GHz; 64-bit operating system; memory: 16 GB;
Windows 10 Professional Edition (CPU software decoding)
Configuration C: I7-8700 CPU @3.2 GHz; 64-bit operating system; memory: 16 GB;
Windows 10 Professional Edition (hardware decoding based on the integrated graphics
card)
Table 7-4 Number of live video channels supported by an iClient
Parameter Configuration A Configuration A Configuration Configuration Configuration Configuration

(H.264) (H.265) B (H.264) B (H.265) C (H.264) C (H.265)
CIF (512 38 38 60 42 64 60
kbit/s)
4CIF/D1 (2 22 22 45 36 50 45
Mbit/s)
720p (2 Mbit/s 12 10 16 14 34 30
at 30 fps)
1080p (4 8 6 14 10 20 14
Mbit/s at 30
fps)
3840 x 2160 1 1 3 1 4 4
(12 Mbit/s at
25 fps)
3840 x 2160 1 1 2 1 4 3
Parameter Configuration A Configuration A Configuration Configuration Configuration Configuration

(H.264) (H.265) B (H.264) B (H.265) C (H.264) C (H.265)
(12 Mbit/s at
30 fps)
7.2.6.2.2 Installing the iClient

Step 1 Download the online help (HoloSens_iClient_help.zip) and client software package
(HoloSens_iClient_Vxxx.zip) from http://support.huawei.com to the local computer.
https://support.huawei.com/enterprise/en/intelligent-video-surveillance/ivs3800-
pid-250614775
Step 2 Decompress HoloSens_iClient_x86.zip or HoloSens_iClient_x64.zip to a directory on

the local computer.
 The directory extracted from HoloSens_iClient_x86.zip contains the standard

installation program HoloSens_iClient_x86.exe, user-defined installation
program HoloSens_iClient_Package_x86.exe, signature files
HoloSens_iClient_x86.exe.crl and HoloSens_iClient_x86.exe.cms, white box
customization installation program iClient_x86.exe, white box package
signature files iClient_x86.exe.crl and iClient_x86.exe.cms, and description file
version101.xml.
 The directory extracted from HoloSens_iClient_x64.zip contains the standard
installation program HoloSens_iClient_x64.exe, user-defined installation
program HoloSens_iClient_Package_x64.exe, signature files
HoloSens_iClient_x64.exe.cms and HoloSens_iClient_x64.exe.crl, white box
customization installation program iClient_x64.exe, white box package
signature files iClient_x64.exe.crl and iClient_x64.exe.cms, and description file
version102.xml.
Step 3 Upload the online help, signature files, client installation packages, and
description files to the CSP OM portal as the administrator.
a Log in to the CSP OM portal as the admin user.

Configuration > Application Name > Client.
c Click Upload File and upload the description files.
− In the line where the client name is HoloSens_iClient_x86, upload the 32-
bit client description file version101.xml.
− In the line where the client name is HoloSens_iClient_x64, upload the 64-
bit client description file version102.xml.
Figure 7-7 Uploading the description files
d Click Upload Signature File and upload the signature files, as shown in the
following figure.
− In the line where the client name is HoloSens_iClient_x86, upload the
signature files (HoloSens_iClient_x86.exe.crl and
HoloSens_iClient_x86.exe.cms) for the 32-bit client.
− In the line where the client name is HoloSens_iClient_x64, upload the
signature files (HoloSens_iClient_x64.exe.crl and
HoloSens_iClient_x64.exe.cms) for the 64-bit client.
Figure 7-8 Uploading signature files
e Click Upload Client and upload the HoloSens iClient installation package. For a
32-bit operating system, upload the installation package to
HoloSens_iClient_x86. For a 64-bit operating system, upload the installation
package to HoloSens_iClient_x64.
Figure 7-9 Uploading the installation package
Step 4 Download the iClient installation package.

a. Choose Application Configuration > Configuration Management >
Configuration > Application Name > Client on the CSP OM portal.
b. Click Download Client to download the 32- or 64-bit client installation package
based on the operating system of the local computer.
Step 5 Double-click the iClient installation program and complete iClient installation as
prompted.
----End
 If the system does not display the iClient installation page, double-click the
installation program to install the iClient.
 If the system displays a message indicating that the Microsoft Visual C++ 2010
Redistributable Package fails to be installed during the installation, the software of a
later version may have been installed on the computer. Ignore the message and
continue with the installation. To check whether the software of a later version is
installed, choose Control Panel > Programs and Features on the computer.
7.2.6.2.3 Logging In to the iClient
Step 1 Start the iClient.
On Windows 7, double-click the shortcut icon on the desktop.
On Windows 10, right-click the shortcut icon on the desktop, choose Properties
from the shortcut menu, click the Compatibility tab, select Run this program as an
administrator, and click OK. Then double-click the shortcut icon on the desktop.
The iClient login page is displayed, as shown in the following figure.
Figure 7-10 iClient login page
Authentication Three identity authentication modes are available.

Basic: Use the default user admin or a new user to log in. This is the
most common login method. The default user name and password
are admin and Change_Me, respectively. When you log in to the
system as the admin user for the first time, the system forces you to
change the password. Change the password and remember the new
password.
Windows domain (current user): Log in to the iClient as the user of
the current computer. The user name and password are those for
logging in to the current PC.
Windows domain: Log in to the iClient as the user of another
computer. The user name and password are those for logging in to
another PC.
After changing the password, exercise caution when using the Remember
password function to ensure information security.
Remember If this check box is selected, the current user does not need to enter
password the password when logging in to the system again.
The Remember password check box exists only when the server supports the
function of remembering the password.
Language Select a language displayed on the iClient.

Enable TLS After TLS is enabled, signaling data between the iClient and server is
encrypted to prevent data from being captured and cracked. If TLS is
not enabled, a risk warning will be displayed.
Enable You need to select Enable security certificate only when Enable TLS is
security selected. After the security certificate is enabled, security verification
certificate is performed on backend services.
If the security certificate is not enabled, the system may be attacked.
Server IP To obtain the value of sign, proceed as follows:

address Method 1:
a Log in to the CSP OM portal as the admin user.
b Choose Application Configuration > Configuration
Management > Configuration > Application Name > Local
Domain > Local Domain. The value of iClient Login Address is the
server IP address.
Method 2:
On the Installation Parameter Value sheet of the LLD, find Edge Site
Resource to obtain the server IP address.
Port When Enable TLS is not selected, the default value is 9900. When
Enable TLS is selected, the default value is 9910. You are advised to
use the default value.
If NAT has been configured, the port number is a post-NAT port
number.
2. Click Login. The iClient home page is displayed, as shown in the following
figure.
Figure 7-11 iClient home page

If the analysis platform fails to be connected, the message indicating that the user name or
password of the intelligent account is left empty is displayed and only the Intelligent Recognition
tab page is displayed in Intelligent Applications on the home page.
7.2.6.3 Creating a User on the Surveillance Platform

Before connecting the analysis platform to the surveillance platform, you need to create
a user for connection on the iClient of the surveillance platform. The analysis platform
uses this user to exchange data with the surveillance platform. The user is responsible for
synchronizing devices from the surveillance platform to the analysis platform.
After the connection is complete, you are advised to use the admin user, but not the
connection user, to log in to the iClient.
Step 1 Log in to the iClient of the surveillance platform as the admin user.
Step 2 Choose System Management > User Management > Role Management on the
iClient home page.
Step 3 Create a role for the user.

a Click New Role.
b Set Role Name and Role Description and select corresponding permissions for
the role. You are advised to select the permissions (except the user
management permission) of the system administrator.
c (Important) Determine whether to enable the account password rules.
− If the account and password rules are disabled, the password is vulnerable to
brute force cracking, lowering the account security.
− Enabling the account password rules can improve account security. The default
password validity period is 90 days. You must periodically change the password
to ensure account security.
 The account and password rules are enabled by default. Disabling the
account password rule may bring account security risks.
 The default password validity period of a role is 90 days. The password
validity period of the account is the same as that of the role to which the
account is bound. Users need to change their passwords periodically to
ensure account security.
 When the account and password rules are enabled for a role, if the
password of the connection user expires, the connection user cannot
access cameras or perform operations on these cameras. The user cannot
perform intelligent analysis operations on cameras on the IVS platform.
d Click OK.
Step 4 Choose System Management > User Management > User Maintenance on the
iClient home page.
Step 5 Create a user.

a Click New User. The New User dialog box is displayed, as shown in the
following figure.
Figure 7-12 Creating a user
b Select the role created in Step 3 from the Surveillance Role drop-down list.
c Set User Type to IVS common user.
d Set Account, Password, and Confirm Password.
e (Optional) Enter the IP address and MAC address.
You can bind a user account to the IP addresses and MAC addresses of a maximum of four
computers.
After the account is bound to the IP addresses and MAC addresses of computers, you can log in
to the iClient only on these computers.
f Click Add.
The system allows you to create multiple users simultaneously. When you create other users, the
role selected for Surveillance Role must be the same as that selected during the first user
creation.
g Click Next.
The permission setting dialog box is displayed.
h Set PTZ Control Priority and Max Login Sessions.
PTZ Control  PTZ control priority when the PTZ device is locked. The value ranges
Priority from 1 to 32. A smaller value indicates a higher priority.
 When the PTZ device is unlocked, the PTZ control priority is not
distinguished.
Max Login Maximum number of connections between the analysis platform and
Sessions surveillance platform for an account. You can set this parameter based
on the site requirements. The maximum value 2000 is recommended.
i Use the default value of Validity Period. By default, Validity Period is disabled.
In this case, the user is permanently valid.
j Select cameras and assign the device viewing permission. You are advised to
select the root directory of cameras. Otherwise, the analysis platform cannot
perform intelligent analysis on cameras that are not selected.
k Click Next.
If the value of Result is Successful, the user is successfully created.
l Click OK.
Step 6 (Mandatory) Log in to the iClient as the new user to activate the account. You are
forced to change the password at the first login.
----End
7.2.6.4 Configuring the Surveillance Platform on the Analysis Platform

When you need to synchronize camera information from the surveillance platform to the
analysis platform for intelligent analysis, you can configure the surveillance platform
information on the CSP OM portal.
1. Log in to the CSP OM portal of the analysis platform as the admin user.
2. Choose Application Configuration > Configuration Management > Configuration >
Application Name > Unified Configuration > Analysis Platform.
3. Select VCMAPIService from the Service drop-down list box.
4. In the Surveillance Platform Configuration area, set the surveillance platform
connection parameters, as shown in the following figure. The following table
describes the parameters.
Figure 7-13 Setting surveillance platform parameters
Platform Name Name of the surveillance platform to be connected.
IP Address Login address of the surveillance platform iClient.
Post-NAT IP Set the IP address and port number of the surveillance platform
after NAT mapping based on the site requirements.
Post-NAT Port
User User name and password created in section 7.2.6.3 "Creating a

Name/Password User on the Surveillance Platform" for connecting to the analysis
platform. Enter the user name and password, and click Check to
check whether the user name and password are correct.
You are advised not to use a super administrator, such as the
admin user.
 The default password validity period of a role is 90 days. The password validity period
of the account is the same as that of the role to which the account is bound. Users
need to change their passwords periodically to ensure account security.
 When the account and password rules are enabled for a role, if the password of the
connection user expires, the connection user cannot access cameras or perform
operations on these cameras. The user cannot perform intelligent analysis operations
on cameras on the IVS platform.
Step 2 Click Save.

Step 3 Click Apply.

----End
7.2.6.5 Synchronizing Cameras

After you configure the surveillance platform information on the CSP OM portal of the
analysis platform, the configuration is automatically synchronized to the iClient. You need
to log in to the iClient and synchronize the camera information on the surveillance
platform to the analysis platform for intelligent analysis.
Perform the following steps even if cameras have not been connected.
Step 2 Choose System Management > Analysis Platform Configuration > Surveillance
Platform.
Step 3 Click Synchronize. The system automatically synchronizes the camera information
from the surveillance platform.
----End
7.2.6.6 Configuring the Analysis Platform on the Surveillance Platform

When you need to use the structured data generated by intelligent cameras to perform
intelligent analysis tasks (such as vehicle search, person search, or face search), you can
configure the analysis platform information on the CSP OM portal so that the
surveillance platform can forward the structured data from the cameras to the analysis
platform for applications such as data search.
Creating an Analysis User
Step 2 Choose System Management > User Management > Role Management > Analysis
Role on the iClient home page.
Step 3 Create a role for the user.

a Click New Role.
b Set Role Name and Role Description and select corresponding permissions for
the role. You must select the Manage cameras and Manage intelligent search
permissions.
c (Important) Determine whether to enable the account password rules.
− If the account and password rules are disabled, the password is vulnerable to
brute force cracking, lowering the account security.
− Enabling the account password rules can improve account security. The default
password validity period is 90 days. You must periodically change the password
to ensure account security.
 The account and password rules are enabled by default. Disabling the account
password rule may bring account security risks.
 The default password validity period of a role is 90 days. The password validity period
of the account is the same as that of the role to which the account is bound. Users
need to change their passwords periodically to ensure account security.
d Click OK.
Step 4 Choose System Management > User Management > User Maintenance on the
iClient home page.
Step 5 Create a user.

a Click New User.
The New User dialog box is displayed, as shown in the following figure.
Figure 7-14 Creating a user
b Select the role created in section 7.2.6.3 "Creating a User on the Surveillance
Platform" from the Surveillance Role drop-down list.
c Set Analysis Role to the role created in this section.
d Set User Type to IVS common user.

e Set Account, Password, and Confirm Password.
f (Optional) Enter the IP address and MAC address.
You can bind a user account to the IP addresses and MAC addresses of a maximum of four
computers.
After the account is bound to the IP addresses and MAC addresses of computers, you can log in
to the iClient only on these computers.
g Click Add.
Multiple users can be created simultaneously. When you create other users, the roles selected for
Surveillance Role and Analysis Role must be the same as those selected during the first user
creation.
h Click Next. The permission setting dialog box is displayed.
i Set PTZ Control Priority and Max Login Sessions.
Table 7-7 Permission parameters
PTZ Control  PTZ control priority when the PTZ device is locked. The value ranges
Priority from 1 to 32. A smaller value indicates a higher priority.
 When the PTZ device is unlocked, the PTZ control priority is not
distinguished.
Max Login Maximum number of connections between the analysis platform and
Sessions surveillance platform for an account. You can set this parameter based
on the site requirements. The maximum value 2000 is recommended.
j Use the default value of Validity Period. By default, Validity Period is disabled.
In this case, the user is permanently valid.
k Select cameras and assign the device viewing permission. You are advised to
select the root directory of cameras.
l Click Next.
If the value of Result is Successful, the user is successfully created.
m Click OK.
Step 6 (Mandatory) Log in to the iClient as the new user to activate the account. You are
forced to change the password at the first login.
----End
Setting Analysis Platform Parameters
Step 1 Obtain the analysis platform IP address.

a Log in to the CSP OM portal of the analysis platform as the admin user.
Configuration > Application Name > Two-Node Cluster.
c Record the value of External Service IP of the NGINX.
Step 2 Configure the analysis platform on the surveillance platform.

Configuration > Application Name > Connection > Analysis Platform.
c Click Add. The following page is displayed. The following table describes the
parameters.
Figure 7-15 Parameters for adding an analysis platform
Table 7-8 Parameters for adding an analysis platform
Platform User-defined name of the analysis platform to be connected.

Name
IP Address External service IP address of the NGINX. Set this parameter to the
value of External Service IP obtained in Step 1.
User Name User name and password created in Creating an Intelligent User.
Password Note:
The user name cannot be the default user admin. You need to use
other user names.
d Click Save.
----End

Intelligent Vision System Service
Commissioning Experiment Guide
ISSUE: 1.0
1
No part of this document may be reproduced or transmitted in any form or by any
means without prior written consent of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of
their respective holders.
Notice
recommendations in this document are provided "AS IS" without warranties,
guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has
been made in the preparation of this document to ensure accuracy of the contents, but
all statements, information, and recommendations in this document do not constitute
a warranty of any kind, express or implied.

Huawei Prorietary and Confidential

Copyright © Huawei Technologies Co,Ltd
Huawei Certificate System

Expert (HCIE).
technologies.
About This Document
Overview
This document is applicable to the candidates who are preparing for the HCIP-Intelligent
Vision exam and the readers who want to understand intelligent vision technologies,
including Huawei IVS establishment and advanced service commissioning, technical
principles of Huawei HoloSens SDCs, intelligent algorithm management and application,
and video cloud technologies.
Description
This document introduces six experiments step by step, including camera access, intelligent
analysis configuration, domain management, and backup management, to help trainees
master the advanced service commissioning of the IVS. For basic service commissioning
not described in this document, trainees can learn by themselves by referring to the HCIA-
Intelligent Vision course.
 Experiment 1 describes how to configure video management services, including
camera management and intelligent camera metadata subscription on the platform.
It aims to help trainees understand and operate the Matrix Intelligence.
 Experiment 2 describes how to install and configure algorithm plug-ins, preparing for
subsequent intelligent service configuration.
 Experiment 3 describes how to configure intelligent analysis services, including facial
analysis, person analysis, and vehicle analysis.
 Experiment 4 describes how to connect upper- and lower-level domains and external
domains, laying a foundation for subsequent experiments.
 Experiment 5 describes how to configure video backup and image backup in detail.
 Experiment 6 describes how to implement algorithm collaboration and
resource/task/data collaboration when an external domain or an upper- and lower-
level domain is connected to the platform.

To fully understand this course, readers should have
Huawei HCIA-Intelligent Vision capabilities and be able to independently commission basic
services of the intelligent vision system and cameras.
Experiment Environment Overview
Networking
This experiment environment is intended for intelligent vision engineers who are preparing
for the HCIP-Intelligent Vision exam. Each experiment environment consists of 2 to 7
intelligent vision servers and 2 to 4 access switches, and is applicable to 4 to 12 trainees.
Device
The following table lists the recommended device configurations in each experiment
environment of HCIP-Intelligent Vision, including the device name, model, and software
version:
Intelligent IVS3800F, IVS3800S, V100R019C50

vision server IVS3800C, IVS3800R,
IVS1800, or CloudIVS 3000
Switch CloudEngine 6800 CloudEngine 6800 V200R005C10SPC800
Checking Devices
Before starting the experiment, check whether all required devices are ready. The following
table lists the required devices.
Intelligent vision 7 Shared by all groups

server
Network switches 4 Shared by all groups
Laptop or desktop 1 for each group A desktop computer requires a wireless

computer network interface card.
Twisted pair 1 for each group The twisted pair must be 2 meters long at
least.
Console cable 1 for each group

Experiment Topology
Requirements on switches:
 Device management Top of Rack (TOR): TOR access switch on the device
management plane. The management port of each hardware device is connected to
the switch. S5700 series switches are recommended.
 Management TOR: TOR access switch on the management plane. The Gigabit
Ethernet (GE) electrical port on the management plane is connected to the switch.
CE5800 series switches are recommended.
 Service TOR: TOR access switch on the service plane. The 10GE optical port or GE
electrical port on the service plane is connected to the switch. CE6800 series switches
are recommended.
 End of Row (EOR): aggregation switch. The networks of the service plane and
management plane are aggregated through the aggregation switch and then
connected to the customer's network.
Requirements on the network:
 The GE electrical ports connected to the management TOR switch are bonded in
active-backup (Bond=1) mode. The 10GE optical ports or GE electrical ports
connected to the service TOR switch are bonded in LACP (Bond=4) mode. The service
TOR switch must support static LACP, and an Eth-Trunk must be configured for the
service TOR switch.
 Management TOR switches and service TOR switches must be stacked.
Contents
Overview ............................................................................................................................................................................................. 3
Description ......................................................................................................................................................................................... 3
Background Knowledge Required ............................................................................................................................................. 3
Experiment Environment Overview .......................................................................................................................................... 4
Experiment Environment Preparation ...................................................................................................................................... 4
1 Configuration of Video Management Services ............................................................................ 8
1.1 Introduction ................................................................................................................................................................................ 8
1.1.1 About This Experiment........................................................................................................................................................ 8
1.1.2 Objectives ................................................................................................................................................................................ 8
1.2 Configuration Procedure........................................................................................................................................................ 8
1.2.1 Installing the PU Access Plug-in ...................................................................................................................................... 8
1.2.2 Connecting Cameras ............................................................................................................................................................ 9
1.2.3 Viewing Live Video .............................................................................................................................................................28
1.2.4 Configuring the Recording Function ............................................................................................................................31
2 Installation and Configuration of Algorithms ............................................................................39
2.1 Introduction ..............................................................................................................................................................................39
2.1.2 Objectives ..............................................................................................................................................................................39
2.2.1 Checking Before Installation ...........................................................................................................................................39
2.2.2 Obtaining Plug-in Packages ............................................................................................................................................40
2.2.3 Verifying Software Package Integrity ..........................................................................................................................42
2.2.4 Uploading Plug-in Packages ...........................................................................................................................................45
2.2.5 Installing algorithm plug-ins ..........................................................................................................................................46
3 Intelligent Analysis .............................................................................................................................66
3.1 Introduction ..............................................................................................................................................................................66
3.1.2 Objectives ..............................................................................................................................................................................66
3.2.1 Intelligent Analysis Service Configuration on PUs ..................................................................................................66
3.2.2 Intelligent Facial Analysis on the IVS Platform........................................................................................................72
3.2.3 Intelligent Person Analysis on the IVS Platform ................................................................................................... 100
3.2.4 Intelligent Vehicle Analysis on the IVS Platform .................................................................................................. 110
4 Domain Management .................................................................................................................... 139
4.1 Introduction ........................................................................................................................................................................... 139

4.1.2 Objectives ........................................................................................................................................................................... 139
4.2.1 Connecting Upper- and Lower-Level Domains ..................................................................................................... 139
4.2.2 Connecting to External Domains ............................................................................................................................... 146
5 Backup Management ..................................................................................................................... 161
5.1 Introduction ........................................................................................................................................................................... 161
5.1.2 Objectives ........................................................................................................................................................................... 161
5.2.1 Video Backup ..................................................................................................................................................................... 161
5.2.2 Image Backup.................................................................................................................................................................... 182
6 Cloud-Edge Collaboration ............................................................................................................. 189
6.1 Introduction ........................................................................................................................................................................... 189
6.1.2 Objectives ........................................................................................................................................................................... 189
6.2.1 Algorithm Collaboration................................................................................................................................................ 189
6.2.2 Task/Resource/Data Collaboration............................................................................................................................ 194
6.3 Connection to the IVS1800 .............................................................................................................................................. 208
6.3.1 Network ............................................................................................................................................................................... 208
6.3.2 Connection Using ONVIF .............................................................................................................................................. 209
1 Configuration of Video Management

Services
1.1 Introduction
After installing the system software and hardware, you can configure basic services by
referring to this document. After the configuration is complete, you can view live video
from connected cameras, record live video, and view multiple live video feeds on the video
wall.
1.1.2 Objectives
Master basic service operations such as adding cameras, viewing live video, and configuring
recording.

1.2.1 Installing the PU Access Plug-in
1.2.1.1 Obtaining the Plug-In Package
Cameras of the specified model can be connected to the IVS platform only after the plug-
in that supports the camera model is installed. For details about supported protocols, see
Table 1-1.
By default, the peripheral unit (PU) access plug-in is preinstalled on the IVS platform. (To
view the plug-in, log in to the CSP OM portal as the admin user and choose Application
Configuration > Configuration Management > Configuration > Application Name > Plugin >
PU Access Plug-ins.) If cameras to be connected are supported by the preinstalled plug-in,
skip the steps for installing the PU access plug-in.
If cameras to be connected are not supported by the preinstalled plug-in, you need to
manually install the PU access plug-in. To obtain the PU access plug-in, perform the
following steps:
Log in to the enterprise technical support website. Enter IVS3800 in the search box and
select the option under the search box. On the Software Download tab page, click the
version to be downloaded. On the page that is displayed, click the package name to
download the package and click to download the corresponding digital signature file.
1.2.1.2 Installing the Plug-in Package

Application Name > Plugin > PU Access Plug-ins.
Step 3 Click Upload Plug-in Package.

Step 4 Select the PU access plug-in package and click Open.
Step 5 Click Install to install the plug-in package.
After the plug-in is successfully installed, the status bar displays Installed, as shown in the
following figure. The following image is for reference only.
Figure 1-1 Installing the plug-in
You can click Uninstall to uninstall the device communication gateway (DCG) plug-in. By default,
the plug-in is installed or uninstalled on all nodes in the domain.
----End
1.2.2 Connecting Cameras

This section describes how to configure automatic adding of cameras in batches on the
iClient.
There are several camera registration modes. Table 1-1 describes the application scenario
of each camera registration mode.
Table 1-1 Applicable scenarios
Registration Operation Scenarios Supported

Method Protocols
Automatic batch If a large number of online cameras that support HWSDK and
access HWSDK or ONVIF need to connect to the IVS ONVIF
(recommended) platform, you can use the automatic batch
connection function to quickly add the cameras
in batches.
This method requires that cameras be online but
does not require that the IP address of each
camera be specified. This method applies to
Registration Operation Scenarios Supported

Method Protocols
scenarios where a large number of cameras need
to be added. Compared with the method of
manually adding cameras in batches, this
method enables quicker camera access.
However, this method cannot be used to add
offline cameras and supports fewer camera
protocols.
Manual batch If you have planned IP addresses for a large HWSDK,

access number of cameras and want to connect them ONVIF, GB/T
to the IVS platform, you can manually add the 28181, and GB
cameras in batches. 35114.
Both online and offline cameras can be added,
but you must specify the IP address of each
camera.
Manual single If only a few cameras need to connect to the IVS HWSDK,
access platform, you can add the cameras one by one. ONVIF, GB/T
Both online and offline cameras can be added, 28181, and GB
but you must specify the IP address of each 35114.
camera.
Camera access If you want to add cameras connected to a DVR, ONVIF and
through a DVR, a a DVS, or an NVR to the IVS platform, you can GB/T 28181
DVS, or an NVR add the cameras by adding the DVR, DVS, or
NVR.
1.2.2.2 Setting Cameras in the Camera Web System

Before adding cameras to the IVS platform, you need to set the cameras to ensure that the
cameras can be connected to the platform. This document uses Huawei cameras as an
example to describe how to connect cameras to the video cloud platform through the
HWSDK or ONVIF protocol.
Prerequisites
The cameras have been connected to the network and can communicate with the
intelligent vision platform.
Configuration Steps
Step 1 Log in to the camera web system as the admin user.

Step 2 Choose Settings > Network > Platform Connection > SDK Parameters. Enable the
HWSDK protocol.
Figure 1-2 Enabling the HWSDK protocol
Table 1-2 describes the parameters.
Parameter Setting Method
Active SDK Indicates whether to proactively register a camera. If you select this
registration check box, the camera will be proactively registered with the IVS
platform using the HWSDK protocol.
Two-factor Authentication mode between the camera and platform. If Two-

authentication factor authentication is selected, Transport Layer Security (TLS)
authentication is used. If Two-factor authentication is deselected,
password authentication is used. You are advised to select this
check box to improve system security.
Registration Select Single-server mode.

type
Device ID Unique ID of a device. The eleventh to thirteenth digits must be

132, and the last two digits must be 0.
Platform IP Enter the IP address of the IVS platform.
Port number Generally, the default port number 5060 is used. If another port is
planned for the camera, set this parameter to that port number.
If Two-factor authentication is selected, change the port number to
5062. Otherwise, the camera cannot proactively register with the
IVS platform.
Enable SDK Select this check box when the camera is passively registered with
the IVS platform through the HWSDK protocol. You do not need to
set all the preceding parameters.
Step 3 Choose Settings > Network > Platform Connection > Second Protocol Parameters.
Enable the ONVIF protocol.
Step 4 Choose Settings > Network > Platform Connection > Password Management.
Configure the registration user name and password. The procedure for configuring
the user name and password for HWSDK-compliant cameras is similar to that for
ONVIF-compliant cameras. This section describes how to configure the user name
and password for HWSDK-compliant cameras, as shown in the following figure.
Figure 1-3 Configuring the registration user name and password
Parameter Setting Method
User name User name for logging in to the web page and user name
registered with the platform.
Current password Password for logging in to the camera web system.

To ensure account security, you are advised to change the
password periodically and keep the password secure.
New password Set a complex password for the registration user. For details
about password complexity, refer to the password maintenance
Confirm password suggestions.
----End
1.2.2.3 Auto Batch Access (Recommended)

Step 1 Log in to the iClient as the admin user.
Step 2 Choose System Management > Device Access > Auto Batch Access (Recommended)
and Click Start. The Auto Batch Access tab page is displayed.
Step 3 Add an IP address.

1. Select the driver supported by the device, that is, the protocol for connecting
cameras.
2. In Mount Server, select the server or cluster to which cameras are to be added. When
adding a camera to a stack network, you must select the target server as the mount
server. When adding a camera to a cluster, you must set the target cluster as the
mount server.
3. Click Add Network Segment and enter the start and end IP addresses of cameras.
 It is recommended that you specify a proper network segment to shorten the search time.
 If a network segment is set, the system searches this network segment for cameras in unicast
mode. You can set multiple network segments so that you can search multiple VLANs for
cameras.
 If you do not set the network segment, the system searches for cameras in broadcast mode.
In this case, the system can only search for cameras located on the same network segment as
the IP address of the local server. You are advised to search for cameras by number segment
or add cameras in batches.
4. Click Next to search for cameras.
Step 4 Verify accounts.

1. You can use IP Address and Vendor and to filter the required cameras in the camera
search result and select the required cameras. Alternatively, you can directly select
the required cameras in the camera list. Then verify accounts, as shown in the
following figure.
Figure 1-4 Verifying accounts
− Set Port for each camera, set Account and Password respectively to the
registration user name and password of the camera, and click Verify.
− If all cameras to be added have the same registration user name and password,
you can use the batch verification function.
 Port number: If you add a camera through ONVIF, you do not need to set the port number. If
you add a camera through HWSDK, you are advised to set the port number to 6061. After the
camera is connected, messages are encrypted for transmission, improving security.
 User name and password for camera registration: Generally, the registration user name and
password of the camera are the user name and password for logging in to the camera web
system. The registration user name and password may be different from the web login user
name and password for some cameras. In this case, use the actual registration user name and
password of the camera. If the default password of a camera is changed, do not consecutively
click Verify. If you consecutively click Verify for five times or more, the client will be locked.
You need to wait for the password lock duration to elapse or restart the camera before
adding the camera again.
2. View the verification result.
− If the verification result is , the camera passes the verification. The system
automatically selects the cameras that pass the verification.
− If the verification result is , the camera does not pass the verification. When
you move the cursor to , the verification failure cause is displayed.
Step 5 Select the cameras to be added and click Next. The camera adding result is
displayed, as shown in the following figure.
Figure 1-5 Camera adding result
Step 6 Click Finish.

Step 7 (Optional) Add cameras to a group.
1. Choose System Management > Device Management > Cameras.
2. Create a group at the same or a lower level in the group list, as shown in the
following figure.
Figure 1-6 Creating a group
3. Select one or more cameras in the camera list to move or copy the cameras to the
target group.
 To move multiple cameras in batches to another group, hold down Ctrl or Shift, select
cameras (you can press Ctrl+A to select all cameras), and click Move To to move them to the
target group.
 To share multiple cameras in batches to another group, hold down Ctrl or Shift, select
cameras (you can press Ctrl+A to select all cameras), and click Copy To to share them with
the target group.
 By default, a maximum of 5000 cameras can be added to one group. If you need to add more
cameras to a group, choose Settings > Local Parameters > Others and change the value of
Max. devices displayed for a device group.
----End
1.2.2.4 Manual Batch Access

Before adding cameras in batches, export a template and fill it in based on your surveillance
requirements. After filling in the template, you can import it to add cameras in batches on
the device management page.
 The number of cameras to be added in batches using a template cannot exceed the maximum
number of cameras supported by a single server or cluster. Otherwise, the excess cameras will
fail to be added.
 To import master cameras in the master-slave camera surveillance (1+N) solutions by using a
template, perform the following steps:
Specify the model for each master camera in the template. The system reserves 1+N
channels for each of them. After the batch import is complete, the number of occupied
channels equals the number of channels that are actually reported by the online master
cameras plus the number of channels reserved for the offline master cameras.
If the number of slave cameras connected to a master camera is less than N, free channels
will be released after these cameras go online. Then you can import more cameras in
batches.
For example, a single server supports the import of up to 256 camera channels at a time.
When you add master cameras in 1+2 solutions in batches by using a template:
 The system reserves three channels for each master camera, and a maximum of 85
(256/3 ≈ 85.3) master cameras can be imported at a time.
 Assume that 80 master cameras are online and five are offline after they are
imported. If only one slave camera is connected to each of these online master
cameras, the number of occupied channels is 175 (80 x 2 + 5 x 3). In this case, 81
(256 – 175) channels are available and you can add 81 more cameras.

Step 2 Obtain the template for importing cameras in batches.
1. Choose System Management > Device Access > Manual Batch Access. Click Start. The
Manual Batch Access tab page is displayed.
2. Click Download and download the Device Batch Import.xlsx file to the local
computer.
Step 3 Open the Device Batch Import.xlsx file and fill in the corresponding sheet based on
the access protocol. For details about whether a parameter needs to be filled in, see
Table 1-4 and Table 1-5.
 In Table 1-4, M indicates that the parameter is mandatory, O indicates that the parameter is
optional, and - indicates that the parameter is not involved or required.
 KEDASDK is not a protocol certified by Huawei and may bring security risks.
Table 1-4 Batch import template items description
Parameter/P HWSDK HWSDK (Passive T 28181/GB 35114 ONVIF

rotocol (Proactive Registration)
Registration)
Camera M M M M
Name
Vendor O O O O
Camera O O M O
Type
Camera O O O O
Parameter/P HWSDK HWSDK (Passive T 28181/GB 35114 ONVIF

rotocol (Proactive Registration)
Registration)
Model
Cluster or M M M M
NVR Code
Platform O O O O
Code
Connection O O M O
Code
IP - M - M
Port M M - M
User Name M M - M
Password M M M M
Enable RTSP - - - -
RTSP Port - - - -
Intelligent O O - -
Attribute
Registration M M - -
Method
Floating - - M -
Gateway IP
Enable - - - -
HTTPS
GA/T 1400 - - - -
Gateway
Code
VIID Code - - - -
Collection - - - -
System Code
GA/T 1400 - - - -
User Name
Table 1-5 Parameters in the template
Camera Name Camera name to be displayed on the iClient. You are

advised to set this parameter to the device installation
location or surveillance area.
Vendor Vendor of the camera. This parameter is optional.
Camera Type Camera type. The camera type can be IPC, DVR, DVS, or
eNVR. This parameter is optional.
Camera Model Actual camera model. This parameter is optional.

Only specific cameras can serve as the master camera on the 1+N
network. For details, refer to the compatibility list of the correct
version.
Cluster or NVR Code Obtain the value of Cluster or NVR Code of the current
domain from the Guidance sheet in the same template.
Platform Code Unique 16-digit code of the IVS platform. This parameter
is optional. The first 10 digits of the platform code must
be the same as the 10-digit HW code configured on the
CSP OM portal.
Connection Code User-defined code, which is used for connecting a camera

to the IVS platform.
The connection code requirements vary depending on the
connection protocol.
GB/T 28181 and GB 35114: This parameter is mandatory.
Camera access: This parameter is mandatory and the
value must be the same as the value of Device ID for
Huawei cameras or SIP Authentication ID for Hikvision
cameras. The eleventh to thirteenth digits must be 132.
DVR access: This parameter is mandatory and its value
must be the same as the value of SIP Authentication ID for
Hikvision DVRs. The eleventh to thirteenth digits must be
111.
Other protocols: Leave the parameter empty.
IP IP address of the device.

 This parameter is mandatory only when the HWSDK
(passive registration) or ONVIF protocol is used to
connect cameras.
 Do not set this parameter when cameras are connected
through GB/T 28181, GB 35114, or HWSDK (proactive
registration).
Port Access port of the device, which must be the same as the
setting on the camera side. You are advised to use the
default port number. If the port number is changed on the
camera side, set this parameter based on the site
requirements.
 If the HWSDK protocol is used for passive registration, set the

port number to 6061. After the camera is connected, messages
are encrypted for transmission, which improves the security of
information transmission.
 If you change the port number after a camera is connected, the
camera will be disconnected and reconnected within 1 to 5
seconds. The reconnection duration depends on the network
conditions.
User Name/Password User name and password used by the camera to register
with the platform.
Generally, the registration user name and password of a camera

are the user name and password for logging in to the camera web
system. The registration user name and password may be
different from the web login user name and password for some
cameras. In this case, use the actual registration user name and
password of the camera.
When a camera is connected through GB/T 28181 or GB
35114, the user name is unconfigurable, and you simply
need to enter the camera registration password in the
Password and Confirm Password text boxes.
For Huawei cameras, the navigation path of the
registration password in the camera web system varies
depending on the protocol.
 HWSDK protocol: Choose Settings > Network >
Platform Connection > Password Management. On the
SDK Password tab page, the value of Current password
is the registration password. The default value is
HuaWei123.
 ONVIF protocol: Choose Settings > Network > Platform
Connection > Password Management. On the ONVIF
Password tab page, the value of Current password is
the registration password. The default value is
HuaWei123.
GB/T 28181 or GB 35114: Choose Settings > Network >
Platform Connection > Second Protocol Parameters. The
value of Password is the registration password.
Floating Gateway IP IP address of the floating gateway to which the device

belongs. Obtain the value of Floating Gateway IP from the
Guidance sheet in the same template.
This field is required only for cameras that are added to a
cluster and proactively register with the platform. If this
field is set in other scenarios, the device will fail to be
added.
The floating gateway IP address must be one of the
floating gateway IP addresses of the cluster.
Intelligent Attribute Intelligent attribute of a checkpoint camera. The

intelligent attribute of the checkpoint camera must be the
same as the actual intelligent attribute. Otherwise,
snapshots taken by the checkpoint camera cannot be
uploaded to the IVS platform.
 0: common camera
 1: face detection camera
 2: license plate detection camera
 4: object classification camera
 5: person detection camera
 6: vehicle and face detection camera
 7: face and person detection camera
 8: object classification and face detection camera
 9: other intelligent camera
If this parameter is not set, the camera is a common
camera by default.
Registration Method Indicates whether proactive or passive registration is

required when HWSDK is used to add cameras.
 1: indicates that a camera proactively registers with the
system. After the system IP address is configured on a
camera, the camera proactively sends a connection
request to the system. After the system receives the
request, the camera connects to the system.
 2: indicates that a camera is passively registered. That
is, the system actively sends an access request to the
camera. After receiving the request, the camera
connects to the system.
Enable HTTPS Indicates whether to use HTTPS for data transmission

between a collection device and the IVS platform.
 Yes: HTTPS is used for data transmission.
 No: HTTP is used for data transmission.
To enhance data security, you are advised to select Enable.
GA/T 1400 Gateway Code Code of the GA/T 1400 floating gateway of the cluster to
which a collection device is connected.
This parameter is optional. If this parameter is not set, the
collection device can still be added.
VIID Code VIID code.
Collection System Code Collection system code.
GA/T 1400 User Name Collection device user name.
Step 4 Click Browse and select the template file, or directly drag the template file to the
Drag file here area. Import the template file to the system.
Cameras to be added are displayed on different tab pages based on their protocols, as
Figure 1-7 Importing the template file
Step 5 Click Next. The camera adding result is displayed.

Step 7 Perform subsequent configurations. In this experiment, cameras are passively
registered.

following figure.
3. Select one or more cameras on the camera list to move or copy the cameras to the
target group.
 To move multiple cameras in batches to another group, hold down Ctrl or Shift, select these
cameras (you can press Ctrl+A to select all cameras), and click Move To move them to the
target group.
 To share multiple cameras in batches to another group, hold down Ctrl or Shift, select these
the target group.
Max. devices displayed for a device group.
----End
1.2.2.5 Manual Single Access

Step 2 Choose System Management > Device Access > Manual Single Access and click Start.
The Manual Single Access tab page is displayed.
Step 3 Set related parameters. The parameters to be set vary according to the protocol. For
details, see Table 1-6.
In Table 1-6, M indicates mandatory, O indicates optional, and - indicates not required or
involved.
Parameter/P HWSDK (Proactive HWSDK (Passive GB/T 28181/GB ONVIF

rotocol Registration) Registration) 35114
Name M M M M
User Name M M - M
Password/Co M M M M
nfirm
Password
IP Address - M - M
Device Login M M - M
Port
Vendor O O O O
Model O O O O
Driver M M M M
Access Connection to a - Connection to a -

Gateway single MPU: - single MPU: -
Connection to a Connection to a
cluster: M cluster: M
Platform O O O O
Code
Connection - - M -
Code
NVR List M M M M
Enable - - - -
RTSP/Port
Include - - - -
Video/Image
Channel
(Enable
HTTPS/VIID
Code)
Table 1-7 Parameters for manually adding a camera
Name Camera name to be displayed on the iClient. You are advised to set
this parameter to the device installation location or surveillance area.
User User name and password used by the camera to register with the
Name/Passwor platform.
d/Confirm
Password
Generally, the registration user name and password of a camera are the user
name and password for logging in to the camera web system. The registration
user name and password may be different from the web login user name and
password for some cameras. In this case, use the actual registration user name
and password of the camera.
When a camera is connected through GB/T 28181 or GB 35114, the
user name is unconfigurable, and you simply need to enter the
camera registration password in the Password and Confirm Password
text boxes.
For Huawei cameras, the navigation path of the registration
password in the camera web system varies depending on the
protocol.
 HWSDK protocol: Choose Settings > Network > Platform
Connection > Password Management. On the SDK Password tab
page, the value of Current password is the registration password.
The default value is HuaWei123.
 ONVIF protocol: Choose Settings > Network > Platform
Connection > Password Management. On the ONVIF Password tab
page, the value of Current password is the registration password.
The default value is HuaWei123.
GB/T 28181 or GB 35114: Choose Settings > Network > Platform
Connection > Second Protocol Parameters. The value of Password is
the registration password.
IP Address IP address of the device.

 This parameter is mandatory only when the HWSDK (passive
registration) or ONVIF protocol is used to connect cameras.
 Do not set this parameter when cameras are connected through
GB/T 28181, GB 35114, or HWSDK (proactive registration).
Device Login Access port of the device, which must be the same as the setting on
Port the camera side. You are advised to use the default port number. If
the port number is changed on the camera side, set this parameter
 If the HWSDK protocol is used for passive registration, set the port number
to 6061. After the camera is connected, messages are encrypted for
transmission, which improves the security of information transmission.
 If you change the port number after a camera is connected, the camera will
be disconnected and reconnected within 1 to 5 seconds. The reconnection
duration depends on the network conditions.
Vendor This parameter is optional. If this parameter is not set, the camera
can still be added.
If Vendor and Model are set, the camera vendor and model will be
displayed after a camera is added on the platform.
If the Model drop-down list box does not contain the required model,
you can select the corresponding protocol from the Model drop-
down list box.
Model
When the M60 multi-service video management platform is to be added

through DHSDK, set Vendor to DAHUA and Model to DHSDK_M60. The two
parameters are mandatory in this case.
Driver Protocol used by the camera to connect to the platform.
Access  When a device is to be connected through the GB/T 28181, GB

Gateway 35114 or HWSDK (proactive registration) protocol:
− If the device is to be connected to an MPUT or MPUR, use the
default value.
− If the device is to be connected to a cluster, set this parameter
to the floating gateway IP address of the cluster.
 When a device is to be connected through the HWSDK (passive
registration) or ONVIF protocol:
Use the default value.
Platform Code Unique 16-digit code of the IVS platform. This parameter is optional.
The first 10 digits of the platform code must be the same as the 10-
digit HW code configured on the CSP OM portal.
Connection User-defined code, which is used for connecting a camera to the IVS
Code platform.
The connection code requirements vary depending on the connection
protocol.
 GB/T 28181 and GB 35114: This parameter is mandatory.
− Camera access: This parameter is mandatory and the value
must be the same as the value of Device ID for Huawei
cameras or SIP Authentication ID for Hikvision cameras. The
eleventh to thirteenth digits must be 132.
− DVR access: This parameter is mandatory and its value must be
the same as the value of SIP Authentication ID for Hikvision
DVRs. The eleventh to thirteenth digits must be 111.
 Other protocols: Leave the parameter empty.
NVR List Cluster node to which a camera is connected.
Include Select this parameter only when you add a collection device to the
Video/Image VIID. Only after this parameter is selected, the mandatory
Channel parameters Enable HTTPS and VIID Code are available.
Enable HTTPS Indicates whether to use HTTPS for data transmission between a
collection device and the IVS platform.
 Enable: HTTPS is used for data transmission.
 Disable: HTTP is used for data transmission.
To enhance data security, you are advised to select Enable.
VIID Code VIID to which a collection device belongs.

following figure.
3. Select one or more cameras in the camera list to move or copy the cameras to the
target group.
 To move multiple cameras in batches to another group, hold down Ctrl or Shift, select these
cameras (you can press Ctrl+A to select all cameras), and click Move To to move them to the
target group.
 To share multiple cameras in batches to another group, hold down Ctrl or Shift, select these
the target group.
Max. devices displayed for a device group to a larger one.
----End
1.2.2.6 Synchronizing Camera Information

After a camera is connected, you are advised to synchronize the camera information from
the surveillance platform to the analysis platform for follow-up intelligent analysis.

Step 2 Choose Analysis Platform Configuration > Surveillance Platform.
Step 3 Click Synchronize. The system automatically synchronizes the camera information
from the surveillance platform.
----End
1.2.2.7 Verification
If a camera is added successfully, the status of the camera is Online and you can view the
live video from this camera.
Step 1 Check whether each camera is online.

1. On the iClient home page, choose System Management > Device Management >
Main Devices.
2. Select a server or cluster and check whether the camera status is Online in the
Device Status column.
If a camera is added successfully but goes offline later, no cause will be displayed on the page
and you need to manually locate the cause.

1. Click Live on the iClient home page.
2. Drag the target camera to the live video pane. If the live video can be properly
played, the camera is added successfully, as shown in the following figure.
 If the target camera is not displayed in the camera list, click to refresh the camera list.
 For cameras connected to the IVS platform through the master-slave camera surveillance
(1+N) solution, only the master camera is listed on the camera list under System
Management > Device Management > Main Devices. On the Live page, both the master and
slave cameras are contained in the camera list and live video from them can be viewed.
----End
1.2.3 Viewing Live Video

Strictly follow your local laws and regulations when using video surveillance services, for
example, recording video, recording voice, and taking snapshots. Do not use them for
illegitimate purposes such as infringing on personal privacy or illegally monitoring

employee behavior.
Step 1 Choose Basic Operations > Live on the iClient home page.
Step 2 Enable live video viewing.
Viewing live video from a single camera
Double-click an online camera in the device list or drag the camera to a live video pane to
view the live video.
 During live video viewing, do not overlap the video pane that is playing live video with the
window or dialog box of another program. The overlap may cause artifacts or even frozen
images.
 If the live network is unstable, frame freezing or artifacts may occur on the live video. In this
case, you are advised to enable the bandwidth adaptation function in the camera web system.
After bandwidth adaptation is enabled, the camera can reduce or increase the bit rate based
on the network condition to ensure smooth live video playing.
 Viewing live video from cameras in a group (containing more than one camera and excluding
cameras in subgroups)
1. On the iClient home page, choose System Management > Device Management >
Cameras and group cameras, as shown in the following figure.
Figure 1-11 Grouping cameras
2. Choose Basic Operations > Live on the iClient home page. Hold down Ctrl, select
multiple cameras from the device tree, and drag them to one or more live video
panes. Alternatively, drag a group to one or more live video panes and select Tile,
Cycling, or Smart Tracking to start viewing live video from cameras in the group.
− In Tile mode, if the number of idle live video panes is less than that of online
cameras in the group, the pane layout is automatically adapted.
− In Cycling mode:
i. Click Advanced and set parameters. Table 1-8 lists the key parameters.
Panes Number of cycling panes, which must be less than the

number of cameras to cycle.
Arrangement Tile
Custom: In the Customize Panes window that is displayed,
select panes and click Start.
Interval Set the time for playing video from each round of cameras
on the live video image.
ii. Click OK to start cycling.

 The smart tracking camera can be registered with the platform through
the HWSDK protocol. Before registering the camera with the platform,
configure smart tracking using the SiMS tool.
 In smart tracking, the view of the box camera displays recognition frames
of vehicles and persons, and the PTZ dome camera tracks a random
recognition frame (marked by a red box). After the object in the
recognition frame leaves the view of the box camera, the PTZ dome
camera switches to another random recognition frame.
To track a vehicle or person, click the recognition frame in the view of the box
camera. When the recognition box turns red, the PTZ dome camera starts to track
the recognition frame until the object leaves the view. Then, the PTZ dome camera
tracks another object.
Table 1-9 describes the colors of the recognition frames in the view of the box
camera.
Table 1-9 Colors of the recognition frames in the view of the box camera
Color Description
Red Tracked object.
Blue Other detected objects.
Yellow Person who crosses the tripwire during tripwire crossing

detection.
No recognition frame is displayed for the panoramic surveillance device. You can
manually frame an area.
3. (Optional) Enable or disable the manual tracking function of the panoramic
surveillance device.
i. In the live video pane of the panoramic surveillance device, click on the live
video image of the panoramic camera to enter the manual tracking mode.
ii. Click on the live video pane of the panoramic camera to exit the manual
tracking mode.
(Optional) Enable or disable manual positioning.
− Smart tracking device:
i. Click in the live video pane that plays the live video from the box camera
involved in smart tracking to enable manual positioning. Then, draw a rectangle
or click a point on the live video image. The PTZ dome camera will rotate to the
selected position.
ii. Click on the live video pane of the box camera to exit the manual
positioning mode.
− Panoramic surveillance device:
i. Click in the live video pane that plays the live video from a panoramic
surveillance camera to enable manual positioning. Then, draw a rectangle or click
a point on the live video image. The PTZ dome camera will rotate to the selected
position.
ii. Click on the live video pane of the panoramic surveillance camera to exit
the manual positioning mode.
----End
1.2.4 Configuring the Recording Function

1.2.4.1 Configuring a Recording Storage Policy
Before configuring a recording plan or using manual recording, you need to configure a
recording storage policy.
Step 1 On the iClient home page, choose System Management > Storage Management.
Step 2 Click the Storage Policy tab. In the Camera area, select a camera. Alternatively, click
, set search criteria, and obtain the camera whose recording parameters are to be
set. The system interface is shown in the following figure.
If the master-slave camera surveillance (1+N) network changes, the camera list will be updated
accordingly.
Figure 1-12 Storage policy
Step 3 Set storage policy parameters. Table 1-10 describes the parameters.
The MPUT cannot store recordings. Server recording parameter settings do not take effect for
cameras connected to the MPUT.
Table 1-10 Storage policy parameters
Storage Mode Select All frames.

Complete recordings can be stored within a specified period,
which is called all-frame storage period. When complete
recordings are stored for a period longer than the specified
period and the storage space is insufficient, the earliest
recordings are deleted.
If you enable manual server recording or alarm-triggered recording for

a device that supports the video buffering function, the video buffered
due to network interruption will be stored and recycled in scheduled
recording mode.
If the remaining storage space is less than or equal to the
threshold:
 When Space Full Policy is set to Stop on the CSP OM portal:
− If the storage period of some recordings exceeds the all-
frame storage period, the system deletes these files in
ascending order of their generation time.
− If the storage period of all recordings is shorter than the
all-frame storage period, the system stops recording
immediately after the storage space is used up.
 When Space Full Policy is set to Overwrite on the CSP OM
portal:
ascending order of their generation time until the
remaining storage space is greater than the threshold.
If the remaining storage space is still less than the threshold after the
system deletes the recordings whose storage period exceeds the all-
frame storage period, the system will first delete recordings that have
not been configured with a storage period and then the earliest
recordings within the all-frame storage period.
all-frame storage period, the system first deletes
recordings that are not configured with a storage period
and then the earliest recordings within the all-frame
storage period until the remaining storage space is
greater than the threshold.
If the remaining storage space is greater than the threshold:
 If Recycling Policy is set to By storage space on the CSP OM
portal, the system continues recording as planned.
 If Recycling Policy is set to By storage period on the CSP
OM portal:
ascending order of their generation time until they are
all deleted.
all-frame storage period, the system continues recording
as planned.
All Frame Storage Recording storage duration.

(days) The value ranges from 0 to 9999. A larger value indicates that
Alarm-Triggered the video is stored for a longer period of time. The default
Recording Storage value is 0 for the IVS 3000 and IVS3800 and 90 for the
(days) IVS9000.
This parameter is
available for alarm-
triggered recordings. The value 0 indicates that the storage period is not fixed and the
storage priority is low. When the storage space is used up, the
Manual Recording recording is recycled first.
Storage (days) Do not set this parameter to 0 for the IVS9000.
This parameter is
available for manual
server recording.
Server Recording Stream type used for scheduled server recording (stored on
Stream server disks). Set this parameter based on the bandwidth and
network quality.
The options are as follows:
 Automatic: No stream is specified, and the primary stream
is used by default.
 Primary: The primary stream of the camera is used. The
primary stream features high bit rates, definition, and
bandwidth usage.
 Secondary: Secondary streams of the camera are used.
Secondary streams feature low bit rates, definition, and
bandwidth usage. If a camera has multiple secondary
streams, the parameter has multiple secondary stream
options such as secondary 1 and secondary 2.
Streams cannot be selected for slave cameras connected through the

master-slave camera surveillance (1+N) solution. Only the primary
streams of the slave cameras can be recorded.
Alarm-Triggered Stream type used for alarm-triggered recordings (stored on

Recording Stream server disks).
Pre-recording Pre-recording mode.

 No pre-recording: This is the default value.
 PU pre-recording: A PU stores the video of several seconds
before an alarm is triggered. This ensures the recording
integrity and facilitates analysis of alarm-triggered
recordings.
Pre-recording This parameter is available when Pre-recording is set to PU

Duration (s) pre-recording.
Period of the video stored on the PU. The default pre-recording
duration is 10 seconds.
Save Image Indicates whether to store checkpoint images. The options are
Yes and No.
Full Image (days) The value ranges from 0 to 9999. A larger value indicates that
the video is stored for a longer period of time. The default
value is 90.
You can select a value from the drop-down list box or enter a value.
It is recommended that the storage period of different cameras
be the same to reduce system resource usage. For example,
you are advised to set the storage period of full images to 90
days for all the 10 cameras.
Partial Image (days) The value ranges from 0 to 9999. A larger value indicates that
the video is stored for a longer period of time. The default
value is 365. For details, see the description of Full Image
(days).
Traffic Violation The value ranges from 0 to 9999. A larger value indicates that
Image (days) the video is stored for a longer period of time. The default
value is 365. For details, see the description of Full Image
(days).
PU Recording Stream Stream type used for scheduled PU recording (stored on

camera SD cards).
Step 4 Click Save.

Step 5 (Optional) Select a camera, click Apply to Others to copy its recording storage policy,
select other cameras, and click OK.
----End
1.2.4.2 Configuring Server Recording Plans

The system can automatically record video in a user-defined period and store the recorded
video to server disks.
In a cluster with both MPUT and MPUR nodes:

 When load balancing is enabled for the cluster, server recording plans can be configured for
cameras connected to MPUT nodes. After a recording plan is configured, cameras are
automatically migrated to other MPUR nodes to start recording.
 When load balancing is disabled for the cluster, server recording plans cannot be configured
for cameras connected to MPUT nodes.
Step 1 On the iClient home page, choose System Management > Storage Management.
Step 2 Click the Server Recording Plan tab. The tab page for configuring a server recording
plan is displayed.
Step 3 Configure server recording plans.

 Configure a server recording plan.
1. In the Cameras area on the left, select a camera whose recording storage policy has
been configured.
2. In the Server Recording Plan area on the right, click next to Enable Recording,
Figure 1-13 Creating a recording plan
3. Move the cursor on the timeline to select the time period of the recording plan.
If you click Continuous, you do not need to select a recording time segment.
4. Click Save.
 Configure server recording plans in batches.
1. After configuring a server recording plan, click Apply to Others.
2. Select a batch of cameras for which you want to configure the same recording
plan, as shown in the following figure.
Figure 1-14 Adding recording plans in batches
3. Click OK.
----End
Step 1 On the iClient home page, choose Basic Video > Playback.
Step 2 Set recording playback parameters.
1. Select a camera whose recordings are to be played back in Cameras. Alternatively,
click , set search criteria, and search for a camera.
2. In the Video Search area, set the search time range, click Advanced, set Location, and
then click Search. You can search for video by recording time and storage device.
3. In the search result, drag the slider on a timeline to select the playback start time, as
shown in the following figure. If the recording can be properly played back, the
recording is successful.
Figure 1-15 Recording playback
----End
2 Installation and Configuration of

Algorithms
2.1 Introduction
This experiment describes how to download and install algorithm plug-ins in different
application scenarios, preparing for subsequent intelligent analysis.
2.1.2 Objectives
 Master the functions of different algorithm packages.
 Know how to download, upload, and install an algorithm package.

2.2.1 Checking Before Installation
 When installing video analysis (VA) plug-ins for some algorithms, you need to set
resident memory parameters for GPUVA nodes. Pay attention to the following
restrictions on GPUVA nodes:
 The artificial intelligence (AI) accelerator card configured on one GPUVA compute
node has four AI chips, and each AI chip supports one available node for which the
resident memory mode can be configured (available node).
 Different algorithms cannot share the same available node. For example, when
algorithm A is installed, if an available node is set to work in resident memory mode,
this node cannot be selected during resident memory parameter settings when
algorithm B is installed.
 An available node with the exclusive mode enabled can carry out only the reverse
image search service. An available node with the exclusive mode disabled can carry
out services such as reverse image search, list import, and image-based intelligent
analysis tasks.
 Before installing an algorithm plug-in, you need to import the algorithm license file.
If you do not import the license file, the installation of the media content search
(MCS) plug-in will fail, and the algorithm search function will be unavailable. If an
MCS algorithm plug-in is installed before the license file is imported, you need to
uninstall and reinstall the plug-in after the license is imported.
Configuration Steps

Step 2 Choose Monitoring > Alarms > Active Alarms and check for uncleared alarms.
Step 3 If there are uncleared alarms on the page, view the alarm details.
Step 4 Check whether the alarm information contains information indicating that the
A_VA_C, A_VA_D, A_MCS_S_C, A_MCS_N_C, or A_MCS_S_D node is abnormal. If so,
go to the next step.
Step 5 Click on the right of Alarm ID and clear the alarm according to the alarm
handling procedure.
----End
2.2.2 Obtaining Plug-in Packages

Obtain the required algorithm plug-ins. Table 2-1 lists plug-in packages. The version
number varies depending on the actual environment. The version number here is for
reference only.
Table 2-1 Plug-in package list
Algorithms Package Package Name on Description How to Obtain at

Type Name the CSP OM Enterprise Technical
Portal Support Website
Huawei VA Plugin_huawe huawei_fac The video Log in to the

facial i_facial_recog e_sdk analysis (VA) enterprise technical
recognition nition_VA_V1 algorithm support website. Enter
algorithm 00R019C30.zi plug-in IVS3800 in the search
p analyzes box and select the
video and option under the
MCS Plugin_huawe huawei_fac images and search box. On the
i_facial_retrie e_sdk extracts Software Download
val_MCS_V10 features tab page, click the
0R019C30.zip from them. version. On the page
Huawei VA Plugin_huawe huawei_sbi The media that is displayed, click
personal i_body_recog content the package name to
feature nition_VA_V1 search download the package
recognition 00R019C30.zi (MCS) and click to
algorithm p algorithm download the
plug-in is corresponding digital
MCS Plugin_huawe sbi_mcs_sdk signature file.
used for
i_body_retriev
reverse
al_MCS_V100

R019C30.zip image search
and alert
CloudWalk VA Plugin_cloud CloudWalk_ deployment.
facial walk_facial_r face_sdk The
recognition ecognition_V functions of
algorithm A_V100R019C different
30.zip algorithms
MCS Plugin_cloud CloudWalk_ vary.
walk_facial_r mcs_sdk
etrieval_MCS_
V100R019C30
.zip
CloudWalk VA Plugin_cloud CloudWalk_

facial walk_facial_r global_face_
recognition ecognition_gl sdk
algorithm obal_VA_V10
(global) 0R019C30.zip
MCS Plugin_cloud CloudWalk_

walk_facial_r global_mcs_
etrieval_globa sd
l_MCS_V100R
019C30.zip
Algorithm VA Plugin_huawe huawei_cmv This VA

for vehicle i_vehicle_reco algorithm
recognition gnition_VA_V plug-in is
and 100R019C30. used to
pedestrian zip analyze
and vehicle video and
data images and
structuring extract
in the features
Chinese from video
mainland and image
data.
MCS Plugin_huawe lpr_mcs_sdk The MCS

i_vehicle_retri algorithm
eval_MCS_V1 plug-in
00R019C30.zi implements
p reverse
image
search.

Pedestrian VA Plugin_huawe huawei_stru The VA

and vehicle i_struct_recog ct algorithm
data nition_VA_V1 plug-in is
structuring 00R019C30.zi used to
algorithm p analyze
for the video or
Chinese images.
mainland
2.2.3 Verifying Software Package Integrity

To prevent a software package from being maliciously tampered with during transmission
or storage, download the corresponding digital signature file for integrity verification when
downloading the software package. This experiment uses PGPVerify for verification.
2.2.3.1 Download PGPVerify

PGPVerify is a PGP verification tool developed by Huawei. It runs on Windows 7, Windows
Server 2008, Windows 8, or Windows 10. You can download this tool from
https://support.huawei.com/enterprise/zh/tool/pgp-verify-TL1000000054.
Figure 2-1 PGPVerify download page
Step 1 Click the version package. The file download page is displayed. Select the public key
file (KEYS) and tool program (VerificationTools.rar) and click Download. The
OpenPGP Signature Verification Guide.pdf file is an operation guide. You can
download it as required.
Figure 2-2 Downloading PGPVerify and the public key file
Step 2 Decompress VerificationTools.rar to obtain PGPVerify, as shown in the following

figure.
Figure 2-3 File list
----End
2.2.3.2 Verifying Software Packages with PGPVerify

Each software package corresponds to a signature file and they are stored in the same
directory. In addition, each software package corresponds to a verification file. Generally,
a software package and its signature file have the same name but different extensions. A
signature file has the file name extension .asc. For example, the signature file for the
software package V100R019C10.zip is V100R019C10.zip.asc.
Assume that the signature file and software package are stored in the C:\PGP directory,
and the PGPVerify tool and public key file are stored in the C:\ directory.
Step 1 Double-click PGPVerify.exe to start the tool.

Figure 2-4 Starting the verification tool
Step 2 Click Select Public Key and select the downloaded KEYS file.
Figure 2-5 Selecting the KEYS file
Step 3 Verify the file.

To verify a single file, click Single Verify and select the .asc signature file. The tool starts to
verify the file. When the item is displayed in green and the Results column displays PASS,
the verification is successful.
To verify all files in the directory, click Multiple Verify and select the C:\PGP\ directory. The
tool starts to verify the files. The verification result examples are shown below.
Figure 2-6 Verification result
 [PASS] (highlighted in green): The verification is successful.

 [WARN] (highlighted in yellow): The verification cannot be performed. For example,
the signature file or software package does not exist.
 [FAIL] (highlighted in red): The verification failed.
 If no WARN or FAIL is displayed, the signature file is valid. All items are displayed in
green.
----End
2.2.4 Uploading Plug-in Packages

Application Name > Plugin > Algorithm Plug-ins.
Step 3 Upload the VA intelligent analysis plug-in packages for face, person, and license
plate recognition and the MCS search plug-in package in sequence.
 You can upload a maximum of five plug-in packages at a time using Internet Explorer.
 You cannot upload a plug-in package that has been uploaded. To update the algorithm plug-
in, replace it instead of uploading its package again.
 To delete a plug-in that has been uninstalled or has not been completely installed, click
Delete.
Select Local Algorithms and click Upload Plug-in Package.
Select the plug-in packages to be uploaded and click Open. The plug-in packages must be
in .zip format. The system automatically uploads the plug-in packages, as shown in the
following figure. After the upload is successful, the plug-ins are displayed in the list of the
corresponding type.
You can close the window only when the message "File uploaded successfully" is
displayed. If the upload fails, re-upload the plug-in packages.
Figure 2-7 Uploading plug-in packages
----End
2.2.5 Installing algorithm plug-ins

The procedures for installing different types of algorithm plug-ins are similar. Note that
when a third-party algorithm such as CloudWalk needs to be installed, import the license
file before installing the algorithm. To install algorithm plug-ins such as Huawei pedestrian
and vehicle data structuring, behavior analysis, video synopsis, and video search, you only
need to install VA plug-ins.
Table 2-2 lists the operations to perform for different algorithms.
Table 2-2 Algorithm installation description
Importing or Installing Configuring Installing Configuring the

Updating the the VA the VA Plug-in the MCS Person Library
CloudWalk Plug-in Plug-in Capacity and
Algorithm Reference Library
License Capacity
Huawei × √ √ √ √
Facial
Recognition
Algorithm
Plug-ins
Huawei × √ √ √ ×
Facial
Recognition

License Capacity
Algorithm
Plug-ins
(Facial
Recognition
-based
Access
Control)
CloudWalk √ √ √ √ √
Facial
Recognition
Algorithm
Plug-ins
CloudWalk √ √ √ √ ×
Facial
Recognition
Algorithm
Plug-ins
(Facial
Recognition
-based
Access
Control)
Huawei × √ √ √ ×
Personal
Feature
Recognition
Algorithm
Plug-ins
Huawei × √ √ √ ×
Vehicle
Recognition
Algorithm
Plug-in
Huawei × √ × × ×
Pedestrian
and Vehicle
Data
Structuring
Algorithm

License Capacity
Plug-in
Behavior × √ × × ×
analysis,
video
synopsis,
and video
search
features
The symbol "√" indicates that the configuration is required, and "×" indicates that the
configuration is not required.
2.2.5.1 Importing or Updating the CloudWalk Algorithm License

To use a third-party facial recognition algorithm such as CloudWalk, you need to import a
license file on the Third-Party Licenses tab page. For details about how to apply for a
license, see the License Application Instructions.
Before applying for a license for the CloudWalk facial recognition algorithm, ensure that
the algorithm plug-in has been uploaded to the IVS platform.

Application Name > Plugin > Third-Party Licenses.
Step 3 Set Vendor to CloudWalk.

Step 4 Click Generate and Download ESN to obtain the ESN package for CloudWalk.
Step 5 Apply for a license file based on the ESN package by referring to the License
Application Instructions. If a compressed license file is returned by the vendor,
decompress it.
Step 6 Check the license file name.

1. Decompress the machine code file, as shown in the following figure. Record the file
name of a .c2v file.
Figure 2-8 .c2v file
If the business management unit (BMU) is deployed in single-node system mode, there is only
one .c2v file. If the BMU is deployed in two-node cluster mode, there are two .c2v files.
2. Check whether the names of the obtained .v2c license files are the same as that
recorded in 1.
If they are different, change the name of the obtained license file to the file name
recorded in 1, as shown in the following figure.
Figure 2-9 CloudWalk algorithm license file
If the BMU is deployed in two-node cluster mode, there are two .v2c license files. Ensure that the
name of each .v2c file is the same as that of the corresponding .c2v file. If the license activation
fails, exchange the names of the .v2c files, upload them, and activate them again.
Step 7 Click under Import License.
Step 8 Import the license file and click Update. If the BMU is deployed in two-node cluster
mode, upload both .v2c files in step 6.
If License Status: Imported is displayed, the license file is successfully imported.
The system automatically backs up the license file every 3 hours. Do not restart the BMU node
within 3 hours after the license is activated. If the value of License Status is Not imported, import
the license file again.
----End
2.2.5.2 Installing the VA Plug-in

Step 3 Install the plug-in package.

1. Click Local Algorithms.
2. Select VA from the Plug-in Type drop-down list box and click Install in the Operation
column corresponding to the algorithm plug-in to be installed.
The Confirm dialog box is displayed.

3. Click Yes. The system starts to install the plug-in.
4. Check whether the plug-in is successfully installed.
Select VA from the Plug-in Type drop-down list box and check the value of Installed
Nodes. If the value is the same as the VA nodes to be installed and the plug-in is in
Installed state, the plug-in is successfully installed, as shown in the following figure.
If the installation fails, click Installation failed to view the installation failure details. In the dialog
box that is displayed, click Retry.
Figure 2-10 Installing the VA algorithm plug-in
----End
2.2.5.3 Configuring the VA Plug-in
 If the resident memory mode is not configured, the reverse image search, person list
record adding, and facial recognition-based access control of the algorithm are
unavailable.
 To use the reverse image search function of the Huawei vehicle recognition algorithm,
you need to configure the VA plug-in. Otherwise, skip the operation.
 Modifying the resident memory configuration will cause the VA algorithm plug-in to
restart. Exercise caution when performing this operation.
 Each AI accelerator card configured on one GPUVA compute node has four AI chips,
and each AI chip supports one available node for which the resident memory mode
can be configured.
 If an available node is configured to work in resident memory mode, the node cannot
be used by other algorithms. The value of Available Nodes is reduced by one.

Step 3 Set resident memory parameters.

1. Select VA from the Plug-in Type drop-down list box.
2. Click Configure corresponding to the algorithm. The Configure Resident Memory
page is displayed, as shown in the following figure.
Figure 2-11 Setting resident memory
3. Set resident memory parameters. You can set the parameters using either of the
following methods (automatic configuration is used in this experiment):
 Automatic configuration: Use this method when you only need to pay attention to the
number of nodes for which the resident memory mode needs to be enabled but do not need
to specify each GPUVA node. This section uses this method as an example to describe how to
set resident memory parameters.
 Customized configuration: Use this method when you need to configure resident memory
parameters for specified nodes. Table 2-3 describes the customized configuration parameters.
i. Set Nodes to Enable Resident Mode. Table 2-3 describes the parameters.
Available Nodes Number of nodes for which the resident memory mode can
be configured. The value is related to the number of GPUVA
nodes deployed on the IVS platform.
Each AI accelerator card configured on one GPUVA compute
node has four AI chips, and each AI chip supports one
available node for which the resident memory mode can be
configured.
Nodes to Enable Total number of nodes for which resident memory will be
Resident Mode enabled. Set this parameter to 1.
Exclusive Mode The mode is disabled by default.

After the exclusive mode is enabled, the image feature
extraction performance of the algorithm will be improved.
The exclusive mode can be enabled when the QPS is greater
than 120.
A GPUVA node with the exclusive mode enabled can carry
out only reverse image search. It cannot be used for Matrix
Intelligence, list record import, or other intelligent services.
Nodes to Enable Total number of available nodes for which the exclusive
Exclusive Mode mode will be enabled.
Before enabling the exclusive mode on an available node, ensure

that the available node does not execute other intelligent search
services; otherwise, intelligent services in progress might be
interrupted.
Before configuring the exclusive mode, you need to set
Nodes to Enable Resident Mode.
ii. Click Apply. In the dialog box that is displayed, click Yes. The system displays a
message, indicating that the operation is successful.
iii. Click Customized Configuration and check whether the number of nodes enabled
with the resident memory is the same as the configured value.
If they are the same, the resident memory mode is configured successfully.
Step 4 Set the number of algorithm licenses.
When installing a third-party algorithm VA plug-in, you need to set the number of
algorithm licenses. Otherwise, the functions of the algorithm are unavailable.
1. Click Configure in the Operation column corresponding to the algorithm. The

Configuration page is displayed.
2. Click Configure License.
3. Set Video-based Facial Recognition (per Channel) and Image-based Facial
Recognition (Images/Second). Table 2-4 describes the parameters.
Video-based Facial Number of video channels that can be concurrently processed

Recognition (per by the facial recognition algorithm in video-based mode.
Channel) Enter the actual number of purchased licenses. You can query
the number of purchased licenses in the configurator file. The
value of Number of channels (Real-time) of the CloudWalk
algorithm in the configurator file indicates the number of
purchased licenses.
Image-based Facial Number of images that can be concurrently processed by the

Recognition facial recognition algorithm in image-based mode.
(Images/Second) Enter the actual number of purchased licenses. You can query
the number of purchased licenses in the configurator file. The
value of Maximum number of images per channel (/s)(Real-
time) of the CloudWalk algorithm in the configurator file
indicates the number of purchased licenses.
----End
2.2.5.4 Installing the MCS Plug-in

2.2.5.4.1 Installing the Huawei Facial Recognition Algorithm Plug-in

2. Select MCS from the Plug-in Type drop-down list box and click Install in the
Operation column corresponding to the algorithm plug-in to be installed.
The installation page is displayed.
3. Set Work Mode and Node Type and select MCS nodes for which the algorithm needs
to be installed. Table 2-5 describes the parameters.
Parameter Description Setting Method
Work Mode  Search Set Work Mode and Node

− Select this mode when you Type and select MCS nodes
need to use the search function according to the LLD report.
of the algorithm. For details about the MCS
− If this mode is selected, the node plan, check the Container
MCS node can be used only for Requirements sheet in the LLD
search. report.
− Only A_MCS_N_C nodes For example,

support this mode. If there are four nodes that are
 Alert deployment of the A_MCS_N_C type and
whose Remarks column
− Select this mode when you
indicates that the nodes are
need to use the alert function

of the algorithm. used for reverse image search,
− Only A_MCS_S_C and set Work Mode to Search and
A_MCS_S_D nodes support this Node Type to A_MCS_N_C and
mode. select four MCS nodes.
 Tagging If there are four nodes that are
of the A_MCS_S_D type and
whose Remarks column
need to use the tagging
indicates that the nodes are
function of the algorithm.
used for NvN, set Work Mode
− Only A_MCS_S_C and to NvN and Node Type to
A_MCS_S_D nodes support this A_MCS_S_D and select four
mode. MCS nodes.
 NvN
need to use the N:N face
clustering function of the
algorithm.
− You can use the N:N face
clustering function only when
at least one MCS node whose
Work Mode is set to Search has
been deployed.
The A_MCS_S_D and A_FDA nodes
support this mode.
Node Type  A_MCS_S_C

Container of the A_MCS_S_C type.
 A_MCS_N_C
Container of the A_MCS_N_C type.
 A_MCS_S_D
Container of the A_MCS_S_D type.
 A_FDA
Container of the A_FDA type.
4. Perform this step if Work Mode is set to Search in 3.

i. Click Next.
ii. Select the dynamic table and static table, and enter the partition information and
number of copies. Table 2-6 describes the parameters.
Partition Info  Dynamic table

The default value is 300. You are advised to use the default value.
 Static table
Copies The default value is 1. You are advised to use the default value.
iii. Click OK.

5. Perform this step if Work Mode is set to Alert deployment in 3.
i. Click OK.
If the selected MCS node is A_MCS_S_D, the Select group dialog box is displayed.
ii. Determine whether to group the nodes.
− If the face list capacity is greater than 3 million, select Yes to group the nodes. If
the face list capacity is between 3 million and 12 million, set Select the members
in group to 1. If the face list capacity ranges from 12 million to 20 million
(excluded), set Select the members in group to 2.
− If the face list capacity is not greater than 3 million, select No, indicating that
nodes are not grouped.
You can query the value of Person Library Capacity in the configurator file. For example, in the
Retrieval Business Configuration area of the configurator file, if Blacklist and Whitelist control
about face recognition is set to 30W, the value of Person Library Capacity is 300,000.
iii. Click OK.
6. Perform this step if Work Mode is set to Tagging in 3.
i. Click OK.
If the selected MCS node is A_MCS_S_D, the Select group dialog box is displayed.
ii. Determine whether to group the nodes.
− If the static list capacity is greater than 3 million, select Yes to group the nodes. If
the static list capacity is between 3 million and 15 million, set Select the members
in group to 1. If the static list capacity ranges from 15 million to 30 million
(excluded), set Select the members in group to 2.
− If the static list capacity is not greater than 3 million, select No, indicating that
records are not grouped.
You can query the value of Closing Library Capacity in the configurator file. For example, in the
Retrieval Business Configuration area of the configurator file, if the face tagging library capability
is set to 30 million, the value of Closing Library Capacity is 30,000,000.
iii. Click OK.
7. When you need to deploy MCS nodes in other work modes, deploy them through
MCS capacity expansion.
i. Click Configure. The installation page is displayed.
ii. Click the Scale-out & Scale-in tab.
iii. Select Expansion.
iv. Set Work Mode and Node Type and select MCS nodes. For details, see 3.
− If you install search nodes for the first time, click Next and configure the service
algorithm table. For details, see 4.
− If you install alert nodes, determine whether to group the nodes. For details, see
5.
− If you install tagging nodes, determine whether to group the nodes. For details,
see 6.
Select MCS from the Plug-in Type drop-down list box and check the Status column.
If the status is Installed, the plug-in is successfully installed, as shown in the
following figure. Click the number in the Installed Nodes column and check the
work mode of the nodes.
Figure 2-12 Installing the MCS algorithm plug-in
----End
2.2.5.4.2 Installing the Huawei Facial Recognition Algorithm Plug-in (Facial

Recognition-based Access Control)

to be installed.
You can view the number of nodes used for Huawei facial recognition-based access
control in the Remarks column corresponding to the A_MCS_S_C node on the
Container Requirements sheet of the LLD report. The number is the same as the
number of MCS nodes where the algorithm needs to be installed.
Work Mode Face Switch.

Select this mode when you need to use the facial recognition-
based access control function.
Node Type A_MCS_S_C.

Only the A_MCS_S_C containers support the Face Switch mode.
4. Click OK.
Select MCS from the Plug-in Type drop-down list box and view the plug-in status. If
the status is Installed, the plug-in is successfully installed, as shown in the following
figure. Click the number in the Installed Nodes column and check whether the work
mode of the nodes is Face Switch.
----End
2.2.5.4.3 Installing the CloudWalk Facial Recognition Algorithm Plug-in


Parameter Description Configuration Method
Work Mode  Search Set Work Mode and Node

− Select this mode when you Type and select MCS nodes

need to use the search according to the LLD report.
function of the algorithm. For details about the MCS
− If this mode is selected, node plan, check the Container
the MCS node can be used Requirements sheet in the LLD
only for search. report.
− Only A_MCS_N_C nodes For example,
support this mode. if there are four nodes that are
 Alert deployment of the A_MCS_N_C type and
− Select this mode when you whose Remarks column
need to use the alert indicates that the nodes are
function of the algorithm. used for reverse image search,
set Work Mode to Search and
− Only A_MCS_S_C and
Node Type to A_MCS_N_C and
A_MCS_S_D nodes support
select four MCS nodes.
this mode.
 Tagging
need to use the tagging
function of the algorithm.
− Only A_MCS_S_C and
A_MCS_S_D nodes support
this mode.
 NvN
need to use the N:N face
clustering function of the
algorithm.
− You can use the N:N face
clustering function only
when at least one MCS
node whose Work Mode is
set to Search has been
deployed.
The A_MCS_S_D and A_FDA
nodes support this mode.
Node Type  A_MCS_S_C

Container of the A_MCS_S_C
type.
 A_MCS_N_C
Container of the A_MCS_N_C
type.
 A_MCS_S_D

Container of the A_MCS_S_D
type.
 A_FDA
Container of the A_FDA type.
4. Perform this step if Work Mode is set to Search in 3.

i. Click Next.
ii. Select the dynamic table and static table, and enter the partition information
and number of copies. Table 2-9 describes the parameters.
Partition Info Dynamic table

Static table
5. Click OK.
6. When you need to deploy MCS nodes in other work modes, deploy them through
MCS capacity expansion.
i. Click Configure. The installation page is displayed.
ii. Click the Scale-out & Scale-in tab.
iii. Select Expansion.
iv. Set Work Mode and Node Type and select MCS nodes. For details, see 3. If you
install search nodes for the first time, click Next and configure the service
algorithm table. For details, see 4 .
Select MCS from the Plug-in Type drop-down list box and check the Status column. If
mode and node quantity are the same as those in the LLD report.

Step 4 Configure license information. When Work Mode in 3 is set to NvN, you need to
configure the license information.
1. Click Configure corresponding to the algorithm. The Configuration page is displayed.

2. Configure license information. Table 2-10 describes the parameters.
Facial Recognition N:N Clustering (100,000 x Number of N:N face clustering

100,000) (per Set) algorithms in a license.
3. Click Apply.
----End
2.2.5.4.4 Installing the CloudWalk Facial Recognition Algorithm Plug-in (Facial

Recognition-based Access Control)

to be installed.
You can view the number of nodes used for Huawei facial recognition-based access
control in the Remarks column corresponding to the A_MCS_S_C node on the
Container Requirements sheet of the LLD report. The number is the same as the
number of MCS nodes where the algorithm needs to be installed.
Work Mode Face Switch.

Select this mode when you need to use the facial recognition-based
access control function.
Node Type A_MCS_S_C.

Only the A_MCS_S_C containers support the Face Switch mode.
4. Click OK.
Select MCS from the Plug-in Type drop-down list box and view the plug-in status. If
mode of the nodes is Face Switch.
----End
2.2.5.4.5 Installing the Huawei Personal Feature Recognition Algorithm Plug-in


Work Search Set Work Mode and Node Type and

mode  Select this mode when select MCS nodes according to the LLD
you need to use the report.
search function of the For details about the MCS node plan,
algorithm. check the Container Requirements sheet
 If this mode is selected, in the LLD report.
the MCS node can be used For example, if there are four nodes that
only for search. are of the A_MCS_N_C type and whose
Remarks column indicates that the nodes
Node Type A_MCS_N_C are used for reverse image search, set
Node of the A_MCS_N_C Work Mode to Search, set Node Type to
type. A_MCS_N_C, and select four MCS nodes.
4. Click Next.
5. Set parameters.
Select Dynamic table and enter the partition information and number of copies, as
shown in the following figure. Table 2-13 describes the parameters.
Figure 2-16 Setting parameters

6. Click OK.
figure. Click the number in the Installed Nodes column and check the work mode of
the nodes.
----End
2.2.5.4.6 Installing the Huawei Vehicle Recognition Algorithm Plug-in


Work Mode Search Set Work Mode and Node Type and
 Select this mode when you select MCS nodes according to the LLD
need to use the search report.
function of the algorithm. For details about the MCS node plan,
 If this mode is selected, the check the Container Requirements sheet
MCS node can be used in the LLD report.
only for search. For example, if there are four nodes
that are of the A_MCS_N_C type and
Node Type A_MCS_N_C whose Remarks column indicates that
Node of the A_MCS_N_C type. the nodes are used for reverse image
search, set Work Mode to Search, set
Node Type to A_MCS_N_C, and select
four MCS nodes.
4. Click Next.
5. Set parameters.
Select Dynamic table and enter the partition information and number of copies, as
shown in the following figure. Table 2-15 describes the parameters.
Figure 2-18 Setting parameters

6. Click OK.
figure. Click the number in the Installed Nodes column and check the work mode of
the nodes.
----End
2.2.5.5 Configuring the Person Library Capacity and Reference Library Capacity
Step 3 Select the VCMAPIService service.

Step 4 In the Service Parameters area, set Person Library Capacity and Closing Library
Capacity. Table 2-16 describes the parameters.
The settings of Person Library Capacity and Closing Library Capacity cannot be rolled
back.
Person Library Maximum number of blacklisted, The values of Person

Capacity whitelisted, and redlisted persons that can Library Capacity and
be added to the IVS platform. Closing Library
200,000: A maximum of 200,000 blacklisted, Capacity can be
whitelisted, and redlisted persons can be obtained in the
added. configurator file.
300,000: A maximum of 300,000 blacklisted, For example, in the

whitelisted, and redlisted persons can be Retrieval Business
added. When this option is selected, the IVS Configuration area of
platform no longer supports the facial the configurator file, if

recognition-based access control. Blacklist and Whitelist
900,000: A maximum of 900,000 blacklisted, control about face
whitelisted, and redlisted persons can be recognition is set to
added. When this option is selected, the IVS 30W, select 300,000
platform no longer supports the facial for Person Library
recognition-based access control. Capacity and Yes for
Whether To Modify
2,000,000: A maximum of 2,000,000
The Control Library,
blacklisted, whitelisted, and redlisted
and change the value
persons can be added. When this option is
of Closing Library
selected, the IVS platform no longer
Capacity to 300,000.
supports the facial recognition-based access
control.
20,000,000: A maximum of 20,000,000
blacklisted, whitelisted, and redlisted
persons can be added. When this option is
selected, the IVS platform no longer
supports the facial recognition-based access
control.
Whether To Indicates whether to synchronize the

Modify The reference library capacity with the person
Control Library library capacity.
 Yes: The reference library capacity is
changed to be the same as the person
library capacity. The reference library
capacity cannot be configured
independently.
 No: The reference library capacity is not
synchronized with the person library
capacity and must be manually changed.
Closing Library Maximum number of persons under alert

Capacity that can be added on the IVS platform.
----End
3 Intelligent Analysis
3.1 Introduction
This experiment provides guidance on how to configure intelligent analysis tasks of faces,
persons and vehicles.
3.1.2 Objectives
 To understand the differences between intelligent PUs and the IVS platforms.
 To understand how to configure intelligent analysis tasks of faces, persons, and
vehicles.

3.2.1 Intelligent Analysis Service Configuration on PUs
3.2.1.1 Scenario Description
Intelligent data sources are as follows:
Data Source Intelligent Application Supported
Subscribed structured data and images Supported: vehicle, face, and person
from checkpoint cameras search and vehicle alert Unsupported:
face alert
Structured data and features obtained by Supported: vehicle, face, and person
intelligent analysis task created on the IVS search and vehicle and face alert
platforms
This section describes how to obtain intelligent data from checkpoint cameras.
PU intelligence refers to that the IVS platform subscribes to checkpoint data from
intelligent cameras for analysis, search, and alert, reducing the analysis pressure.
Figure 3-1 PU intelligence
Checkpoint camera (intelligent camera):

Detects objects and recognizes some of them by converting video streams into structured
data.
Detects and locates objects, tracks them, and takes snapshots.
Recognizes license plates, persons, faces, and objects.
Surveillance platform:
Connects to intelligent cameras, and stores and forwards original video, images, and
structured data.
Analysis platform:
Stores and searches for structured data, and performs intelligent analysis on image streams
and video streams.
Third-party application platform:
Subscribes to intelligent data and displayed data on the IVS platforms.
3.2.1.2 Prerequisites
 The surveillance platform has been connected to the analysis platform.
 Checkpoint cameras have been installed.
Table 3-1 lists reference documentation for the installation of Huawei cameras. For
details about how to install cameras provided by other vendors, see their
documentation.
Table 3-1 Camera installation reference documentation
Camera Type Reference Documentation
Micro checkpoint Quick Guide to Huawei Micro Checkpoint Camera Site

camera Survey and Commissioning
ePolice camera Quick Guide to Huawei SDC ePolice Camera Site Survey and
Commissioning
Checkpoint camera Quick Guide to Huawei SDC Checkpoint Camera Site Survey
and Commissioning
Face capture camera Quick Guide to Huawei SDC Face Capture Camera Site
Camera Type Reference Documentation

Survey and Commissioning
Facial Recognition Quick Guide to Huawei Facial Recognition Camera Site

Camera Survey and Commissioning
Omni-data structuring Quick Guide to Huawei Omni-Data Structuring Camera Site

camera Survey and Commissioning
 Checkpoint cameras have been added. The process for connecting checkpoint
cameras is the same as that for connecting common ones.
Checkpoint cameras can upload snapshots to the IVS platforms only when they are
connected through HWSDK, HIKSDK, or DHSDK.
3.2.1.3 Setting Intelligent Attributes for Checkpoint Cameras
If the intelligent attribute configured for a checkpoint camera does not take effect, check
whether camera parameters have been correctly set in the web system of the checkpoint
camera.
Snapshots taken by checkpoint cameras can be uploaded to the IVS platform only when
the cameras are connected through HWSDK, HIKSDK, or DHSDK and the intelligent
attribute is configured correctly on the IVS platform.

Step 2 Choose System Management > Device Management > Cameras.
Step 3 Search for cameras and double-click a checkpoint camera on the search result page.
Step 4 Choose Video Channel > Video and set Intelligent Attribute for the checkpoint
camera.
The intelligent attribute of the checkpoint camera must be the same as the actual
intelligent attribute. Otherwise, snapshots taken by the checkpoint camera cannot be
uploaded to the IVS platform.
Step 5 Set Report Synthesized Image and Report Vehicle Coordinates.

To enable a checkpoint camera or a third-party platform to upload synthesized images, set
Report Synthesized Image to Yes (default: No).
If you do not want vehicle images uploaded by a checkpoint camera or a third-party
platform to provide vehicle coordinates, set Report Vehicle Coordinates to No (default: Yes).
Step 6 Click OK.

----End
3.2.1.4 Configuring Checkpoint Data Storage

After a checkpoint camera is connected to the IVS platform, the IVS platform does not
store checkpoint data by default. To store checkpoint data for intelligent analysis tasks
such as vehicle data search, vehicle recognition, and face search, you need to manually
enable checkpoint data storage on the IVS platform and set the storage duration.

Step 2 Choose System Management > Storage Management > Storage Policy.
Step 3 Find and double-click the to-be-configured checkpoint camera.
Step 4 Configure checkpoint data storage, as shown in the following figure.
Figure 3-2 Configuring the image storage duration
Full Image Number of days for storing full You can select a value from the
(days) images, including background drop-down list box or manually
images or scene images. enter a value.
Partial Image Number of days for storing partial It is recommended that the
(days) images, including close-up images storage period of different
of single objects, such as face, cameras be the same to reduce
person, or license plate. system resource usage. For
example, you are advised to set
Traffic Number of days for storing images this parameter to 90 for all the
Violation uploaded by cameras that support 10 cameras.
Image (days) traffic violation detection and
snapshot taking.
Step 5 Click Save.

Step 6 (Optional) Select a checkpoint camera, click Apply to Others to copy its checkpoint
data storage period settings, select other cameras, and click Save to paste the
checkpoint data storage period settings to these cameras.
----End
3.2.1.5 Subscribing to Data from Checkpoint Cameras

This section describes how to configure structured data subscription so that the IVS
platform can use the structured data and images provided by checkpoint cameras to
perform intelligent analysis tasks (such as vehicle search and person search), alleviating
the analysis pressure on the IVS platform and improving the search efficiency.

Step 2 Choose System Management > Device Management > Metadata Subscription.
Step 3 In the navigation tree on the left, click the directory where the camera to be
subscribed to is located. The subscription details of the camera are displayed, as
Figure 3-3 Camera tree
Subscription Indicates whether metadata of a camera is subscribed to. The options

Status are as follows: All, Subscribed, and Unsubscribed.
Physical Intelligent attribute of a camera. The options are as follows:

Attribute  Face detection: The camera can detect and take snapshots of
faces.
 Plate analysis: The camera can detect and recognize license plates.
 Object classification: The camera can detect and take snapshots of
motor vehicles, non-motor vehicles, and persons.
 Person detection: The camera can detect and take snapshots of
pedestrians.
 Vehicle detection+face detection: The camera can detect and take
snapshots of vehicles and faces.
 Face detection+person detection: The camera can detect and take
snapshots of faces and persons.
 Object classification+face detection: The camera can detect and
take snapshots of motor vehicles, non-motor vehicles, persons, and
faces.
Step 4 View the value of Subscription Status in the search result.

If the value of Subscription Status is Unsubscribed, go to the next step.
If the value of Subscription Status is Subscribed, the task ends.
Step 5 Select the camera to be subscribed to and click Subscribe, as shown in the following
figure.
Figure 3-4 Subscription
If the system displays a message indicating that the operation is successful and the value
of Subscription Status is changed to Subscribed, the camera is successfully subscribed to.
After subscription is complete, the value of Subscription Status is automatically changed to

Subscribed. If the status is not changed, click Refresh to refresh the status.
If the camera that you want to subscribe to is performing an intelligent analysis task, the
system displays a message indicating that the subscription fails when you click Subscribe.
----End
The following uses vehicle search as an example.
Step 1 Choose Intelligent Applications > Vehicle Search on the home page.
Step 2 Click the Filter by Criteria tab and click Search without setting any search criteria.
Step 3 On the vehicle search page, set search criteria and click Search to quickly search for
subscribed images from cameras.
Table 3-4 Setting search criteria
Condition Setting
Captured Select the period for data subscription. Assume that the data to be
subscribed to is generated on March 24, 2020. You are advised to
set the period to 00:00-23:59 on March 24, 2020.
Source Select data source. This section uses camera data subscription as
an example. Therefore, set this parameter to Camera and select
the camera for which data subscription has been configured.
Select Algorithm Set this parameter to Vehicle metadata subscription.
The subscribed images are displayed in the search result area.
Figure 3-5 Search result
----End
3.2.2 Intelligent Facial Analysis on the IVS Platform

Based on intelligent facial analysis, the platform provides the following functions:
 Searches for faces based on the uploaded face image or specified attributes.
 Recognizes faces in live or recorded video, and generates alarms for blacklisted faces
or non-whitelisted faces based on the blacklist or whitelist.
 Filters image-based face search and alert results based on redlisted faces; sends
search results, face trajectories, and alarms only to authorized users.
 Matches two images and provides the similarity to help users determine whether the
two persons are the same one.
 Allows users to import, view, group, and use personnel information through the face
list management and face search functions.
 Enables the system to match the facial features that are analyzed in real time with
the customer's facial feature library to obtain the identification information about
the individual from the customer's facial feature library.
3.2.2.1 Face Lists

Face lists are classified into Blacklists, Whitelists, Redlists, Static Lists, and Temporary Lists.
Table 3-5 describes their application scenarios and functions.
Table 3-5 Face list types
List Type Application Scenario
Blacklists Used in scenarios such as turnstiles, archway metal detectors,

and straight pedestrian walkways. When a blacklisted face is
detected, an alarm is generated in real time and the individual
is tracked.
Whitelists Used in scenarios such as turnstiles and archway metal

detectors. When a non-whitelisted face is detected, an alarm is
generated in real time and the individual is tracked.
Redlists Used to protect customer privacy, preventing unauthorized use

of customer trajectories and images. When a redlisted face is
detected, the generated alarm and trajectory are not displayed
to users who do not have the redlist viewing permission.
Face blacklists and face whitelists can be invoked during face alert task
creation, while face redlists can take effect directly.
After a face alert task is created, if a face image captured by the camera
matches a blacklisted or non-whitelisted face, the system uses the same
facial recognition algorithm to calculate the similarity between the face
and the redlisted faces. If the similarity exceeds the threshold, the face
image, related trajectory, and generated alarm are pushed only to users
who have the redlist viewing permission.
Static Lists Used to store, manage, and query information about

permanent staff.
Temporary Lists Used to store information about persons involved in face alert
tasks.
3.2.2.1.1 Adding New Lists

The methods of adding face blacklists, whitelists, and redlists are the same.
Step 1 On the iClient home page, choose Intelligent Applications > Face Library.
Step 2 Click New List and choose Special list.

Step 3 Set Type and customize the face list name.
Step 4 Click OK twice.
----End
A common static list can be created.

The procedure for creating a common static list is as follows:
Step 2 Click New List and select Static list.
Step 3 Set List Name and Description, and set Static List Type to Common.
Step 4 Click OK twice.
Generating a Temporary List
After you create a face alert task for specific individuals, a temporary list and the
individual's information are automatically generated.
 You cannot manually add a temporary list on the Face Library page.
 Before deleting a person list under Temporary Lists, you must delete the corresponding face
alert task.
----End
3.2.2.1.2 Adding Person Information to a Face List

You can create person information in or import person information to the face blacklist,
whitelist, redlist, and static list.
Configuring Face List Capacity

Step 3 Select VCMAPIService and set Face List Capacity. Maximum number of blacklisted,
whitelisted, and redlisted persons that can be added to the IVS platform.
 200,000: A maximum of 200,000 blacklisted, whitelisted, and redlisted persons can
be added.
be added.
be added.
You are not allowed to set this parameter back to a smaller value.
----End
Creating Person Information
Step 1 Click the face list to which person information will be added and click New.
Step 2 Click the profile icon. In the displayed dialog box, select a face image, and click Open.
Then frame the required part, and click OK.
Face images in the face list must meet the following requirements:
 Only .BMP, .DIB, .JPE, .JPEG, .JPG, and .PNG images are supported.
 Image size: The recommended image size is 35 KB to 200 KB. The size of a single
image cannot exceed 5 MB.
 Image quality: Faces in images must be clear. Images support a minimum of 8-bit
grayscale.
 Resolution: The recommended face resolution ranges from 80 x 80 pixels to 200 x
200 pixels. The pupillary distance must be not less than 60 pixels, and 90 pixels or
more is recommended.
 Brightness and contrast: The ambient illumination must be at least 300 lux with
uniform brightness of images and moderate contrast. The face should not be
shadowed, without backlight, light reflection and overexposure.
 Posture: Use proper posture and look straight ahead. The yaw angle, pitch angle, and
roll angle of the face should be within the range of –10° to +10°.
 Occluding: The eyebrows, eyes, mouth, nose, and face contours must not be occluded
by hair, mouth mask, accessories, or glasses. If glasses are worn, the lenses should be
clear and non-reflective.
 Face: A complete, clear, unretouched image of the face is required. The contour and
facial features should be clear without heavy makeup.
 Facial expression: Wear a neutral expression, with eyes open and mouth closed
naturally. Avoid laugh, frown, or other strong expressions.
Step 3 (Optional) Fill in more information in the following figure.

Figure 3-6 New Person
The Ethnicity parameter is displayed only when Display Ethnicity is set to Yes for the
VCMAPIService service under Application Configuration > Configuration Management >
Configuration > Application Name > Unified Configuration > Analysis Platform on the CSP OM
portal.
Step 4 Click OK.

----End
Importing Person Information
Step 1 Select a face list and click Import.

Step 2 Set Import Method to Template import, click Download Template to download the
template to the local computer, and decompress the template.
You can also set Import Method to Batch import or Quick import.
 Batch import: Each image must be named in the format of Name_ID Number_ID
Type_Gender_Date of birth_Nationality_Ethnicity_Occupation.jpg. You can select a
folder to upload all images in the folder. The values of some fields in the image
name must be digits. For details, see Table 3-6. When a field in the middle is
ignored, the enumerated value of this field is not entered and is replaced with an
underscore (_). For example, if the image can contain only the name and gender, the
image is named in the format of Name ___ Gender .jpg (There are three underscores
(_) in the name).
 Quick import: Each image must be named in the format of Name.jpg. You can select
a folder to upload all images in the folder.
Image Naming Values

Parameters
ID Type The options are as follows: 0: resident ID card; 1: passport; 2:

student card; 3: military ID card; 4: driver's license; 5: others.
Gender The values are 0 and 1. (0 indicates male and 1 indicates female.)
Date of birth The value is in the format of YYYY-MM-DD, for example, 2019-09-
30.
Step 3 (Optional) If a large number of persons' information needs to be imported, you can
use Image Batch Import Tool.xlsm to read the IDs of all face images.
1. Create a folder locally and save the face images to be imported to the folder.
2. Open Image Batch Import Tool.xlsm, click Read All Files in Target Folder, select the
face image folder, and click OK.
The tool automatically reads the image IDs, as shown in the following figure.
Figure 3-7 Reading the image IDs
Step 4 Enter other information in the Image Batch Import Tool.xlsm file.
 The image names (including the file name extensions) in the Image ID column must be the
same as the names of the images to be uploaded.
 A maximum of 10,000 persons' information can be imported at a time.
Step 5 Click Generate CSV File.

The message "CSV file generated successfully" is displayed, and the template.csv file is
generated in the same folder as the tool.
Step 6 Place the template.csv file in folder where the face images are stored.
Step 7 Click List File, load the local template.csv file, and click Open.
Step 8 After the file is uploaded, click Import.

----End
3.2.2.1.3 Searching for Person Information in a Face List

Step 2 Enter a face list name under New List, search for the target face list, and select the
face list.
All person information in the selected face list is displayed on the right.
Step 3 Correctly enter a complete name or ID number in the search box on the right. Fuzzy
match is not supported.
Step 4 (Optional) Click Advanced Search and enter other search parameters. Table 3-7
describes the parameters.
Table 3-7 Person search parameter description
Created Time when a record is successfully created in a face list.
Age Age in a record.
Sex Sex in a record.
Step 5 Click OK.

Click a record in the search result to view the person details.
----End
3.2.2.2 1:1 Face Match

The 1:1 face match feature enables you to:
 Match two uploaded face images.
 Match an uploaded face image with face images in the face list.
The obtained similarity helps you determine whether a person is the desired one. The
following describes the procedure.
Step 1 On the iClient home page, choose Intelligent Applications > 1:1 Face Match.
Step 2 Click + on the left, select a face image, and click Open.
Step 3 Enter an ID number in the Enter ID number text box, search for face images in the
face library based on the ID number and select a face image.
Step 4 Select a 1:1 face match algorithm in the middle.

Step 5 After you click Match, the 1:1 face match result is displayed.
Step 6 Click Clear to restore the initial page.
----End
3.2.2.3 Face Search

Prerequisites
 The facial recognition function has been commissioned.
 The facial recognition algorithm plug-in has been installed on the CSP OM portal.
For details, see chapter 2 "Installation and Configuration of Algorithms."
 Face lists and person information have been added to the face library.
3.2.2.3.1 (Optional) Creating an Intelligent Analysis Task for Live Video from Cameras
If a camera is required to recognize faces in video, you can perform the following steps to
create a facial recognition task for live video from the camera:
Step 1 On the iClient home page, choose Intelligent Applications > Tasks.
Step 2 Click New Task. The New Intelligent Analysis Task page is displayed.
Step 3 Click the Cameras tab and select a camera.
Step 4 Create an intelligent analysis task for the camera. Table 3-8 describes the
parameters. You can select multiple cameras, select Apply to all, and set Video Type
and Task Type for the selected cameras in batches.
Table 3-8 Vehicle recognition task parameter description
Video Type Video type. Select Live.
Execution Domain Execution domain type. Select Local domain. Intelligent analysis
Type tasks will be executed on the IVS platform in the local domain.
Task Type Task type. Select Facial recognition and select required facial
recognition algorithms. Multiple algorithms can be selected.
If the CloudWalk facial recognition algorithm is used, the
scheduled snapshot mode can be enabled for video stream
analysis. In this case, the Snapshot parameter needs to be set. In
scheduled snapshot mode, if the same face remains in the video
shot by a camera, the system captures the face image at the
interval specified by Snapshot. Generally, the scheduled snapshot
mode applies to facial recognition–based roll call after whitelist-
based alert.
Advanced Settings Advanced settings. Set Save snapshot. If the snapshot storage
function is enabled, the face images recognized by intelligent
cameras are stored on the platform server. This parameter is not
valid for common cameras.

----End
3.2.2.3.2 (Optional) Creating an Intelligent Analysis Task for Recorded Video from
Cameras
If a camera is required to recognize faces in video, you can perform the following steps to
create a facial recognition task for recorded video from the camera:
Step 1 On the iClient home page, choose Basic Operations > Information Center.
Step 2 Click the Recordings tab.
Step 3 Click the Camera text box and select the camera from which recordings are to be
searched for.
Step 4 Set recording search criteria and click Search.

Step 5 Select one or more cameras from the search result and click Intelligent Analysis.
Step 6 Create an intelligent analysis task for recorded video from the cameras. You can
select multiple cameras, select Apply to all, and set intelligent analysis task
parameters for the selected cameras in batches. Table 3-9 describes the parameters.
Table 3-9 Intelligent analysis task parameter description
Video Type Video type. Select Recorded.
Analyzed Recording segment for intelligent analysis
Type tasks will be executed on the IVS server in the local domain.
Task Type Task type. Select Facial recognition and select the required facial
recognition algorithm. If multiple algorithms are available, you
can select multiple algorithms.
Fast Analysis When Video Type is set to Recorded and Task Type to Facial
recognition, you can select Fast Analysis.
 After Fast Analysis is selected, Execution Domain Type can only be set to
Local domain.
 When performing an intelligent analysis task in the Fast Analysis mode,
the system provides a maximum analysis capability of 50x. The analysis
capability in a specific situation depends on the idle GPU resources,
available license channels, and MPUR container download bandwidth.
 If the MPUR node is running recording playback services, such as video
viewing and video analysis, the intelligent analysis task with Fast Analysis
selected shares the 256 Mbit/s download bandwidth with these services,
and therefore the speed cannot reach 50x.
If Fast Analysis is selected for a task, a large number of GPU
resources are required to execute this task. As a result, subsequent
intelligent analysis tasks can be executed only after these GPU
resources are released.

----End
3.2.2.3.3 (Optional) Uploading a Local Video File and Creating an Intelligent Analysis
Task
In addition to extracting facial features from live or recorded video from cameras, you can
create a facial recognition task for a video file that is uploaded locally to extract facial
features. The detailed operations are as follows:
Uploading a Video File
Step 2 Click the Uploads tab.
Step 3 Click Upload. In the dialog box that is displayed, select a video file and click Open.
The system starts uploading the video file. You can view the uploaded video file on
the Uploaded Video tab page.
----End
Creating a Facial Recognition Task
Step 2 Click the Uploaded Video tab.
Step 3 Select a video file and click New Analysis Task. Alternatively, you can select multiple
video files, click New Analysis Task, select Apply to all, and set parameters for the
selected video files in batches.
Step 4 Create a facial recognition task for the video file and select one or more required
algorithms. For details about other parameters, see Table 3-9.

----End
3.2.2.3.4 Searching for Faces

By image
A face search task can be initiated from different entries. Table 3-10 describes the main
entries and application scenarios. This section describes how to initiate face search on the
Face Search page.
Table 3-10 Face search entries
Entry Application Scenario
Face Search page If images or features (such as sex, glasses, and hat) of the
face to be searched have been obtained, the face images
or facial features can be directly used for face search.
Capturing a face image During live video preview, if you want to search for a face
during live video preview that appears in the video, you can capture the face image
to perform face search.
Capturing a face image During recording playback, if you want to search for a face
during recording playback that appears in the recording, you can capture the face
image to perform face search.
Capturing a face image During person search, you can capture a clear face image
from a person search from a person search result to perform face search.
result
Selecting a face on the When viewing alarms generated by face alert tasks on the
Alarm Center page Alarm Center page, if you want to perform face search on
the person that appears on the alarm detail page, capture
the face, and create and initiate a face search task for the
target face.
Selecting a face snapshot When viewing face snapshots on the Information Center
on the Information page, if you want to perform face search on the person
Center page that appears on the snapshot detail page, capture the
face, and create and initiate a face search task for the
target face.
Step 1 On the iClient home page, choose Intelligent Applications > Face Search.
Step 2 Select the Search by Image tab.
Step 3 (Optional) Click More and enter search criteria based on the site requirements. Table
3-11 describes the parameters.
Table 3-11 Parameters for face search by image
Period Period during which the face images are captured.

 You can select Past 3 Days, Past Week, or Past Month.
 Alternatively, specify a period in the calendar.
Search Domain Search domain. Select the local domain for face search.
Sort by Similarity Threshold of similarity to the target for search.
Algorithm Facial recognition algorithm.
Source Video source of the captured face images. The options are
Camera, Video file, and All.
Image Quality The face image quality is affected by factors such as color,
definition, and resolution. You can set this parameter to filter
out face images with poor quality (such as black-and-white,
fuzzy, or low resolution images).
Some algorithms cannot analyze the image quality score. If
you want to search for face snapshots without image quality
score, deselect Image Quality.
Step 4 Upload a face image for face search.

Use either of the following methods to upload a face image:
 Enter the full ID number or name in the search box and select the face image for
face search from the drop-down list box.
 Drag a face image to the search box. On the Upload Image page that is displayed,
frame the required part and click OK, as shown in the following figure.
Figure 3-8 Framing the required part
The uploaded face image must meet the following requirements:

 The image format must be .JPG, .JPEG, .DIB, .BMP, or .PNG.
 The image cannot exceed 5 MB, and the image resolution cannot exceed 4096 x
3000 pixels.
 The resolution of the selected face area ranges from 60 x 60 pixels to 800 x 1200
pixels.
Step 5 Click Search. The Snapshot Library tab page is displayed by default with the search
results, as shown in Figure 3-9 and Figure 3-10. The snapshot library contains face
images captured by cameras and extracted by facial recognition tasks.
The recommended face images shown in Figure 3-10 are from the face library and provide
possible identity information for the target face.
Figure 3-9 Face image search result (matched to the face library)
Figure 3-10 Face image search result (not matched to the face library)
Step 6 (Optional) Select multiple face images and click Trajectory Analysis to analyze the
person trajectory. The following figure shows the analysis result.
Figure 3-11 Trajectory analysis
The prerequisite for successful track analysis is that the camera location information has been
configured.
Step 7 (Optional) Select multiple face images, and select Export Selected. You can also
select Export This Page or Export All from the drop-down list box as required. The
following figure shows the page for exporting files.
Figure 3-12 Export options

You can enable the encrypted export function when exporting files. After this function is enabled,
you need to enter the preset password when opening the file exported to the local computer.
Step 8 Click the Face Library tab and search for faces in the face library (face list).
You can select All, Blacklists, Whitelists, Redlists, or Static lists from the drop-down list box
under the face image to specify the search scope.
----End
Filter by Criteria
Step 1 On the iClient home page, choose Intelligent Applications > Face Search.
Step 2 Click the Filter by Criteria tab.
Step 3 Set the parameters for searching by criteria. Table 3-12 describes the key parameters.
Table 3-12 Parameters for searching faces by criteria
Source Video source of the captured face images. The options are Camera,
Video file, and All.
Captured Period during which the face images are captured.
Search Search domain. Select the local domain for face search.
Domain
Algorithm Facial recognition and face search algorithm

You can select Facial metadata subscription for search by criteria.
Images in the search results are from subscribed metadata of intelligent
cameras.
Feature Indicates whether to display the images from which facial features have
Extracted been extracted.
 Yes: displays the images from which facial features have been
extracted.
 No: displays the images from which facial features have not been
extracted.
 All: displays all images.
Ethnicity Ethnicity of an individual.
The Ethnicity parameter is displayed only when Display Ethnicity is set to Yes for
the VCMAPIService service under Application Configuration > Configuration
Management > Configuration > Application Name > Unified Configuration >
Analysis Platform on the CSP OM portal.
Image Image quality. The face image quality is affected by factors such as
Quality color, definition, and resolution. You can set this parameter to filter out
face images with poor quality (such as black-and-white, fuzzy, or low
resolution images).
Some algorithms cannot analyze the image quality score. If you want to
search for face snapshots without image quality score, deselect Image
Quality.
Step 4 Click Search. The Snapshot Library tab page is displayed by default with the search
results, as shown in the following figure. The snapshot library contains face images
captured by cameras and extracted by facial recognition tasks.
Figure 3-13 Results of face search by criteria
Step 5 (Optional) Use a clear target face image for secondary search to obtain more images
of the target face. The operations are as follows:
Click a search result. In the face details, click Search.
Step 6 (Optional) Select multiple face images and click Trajectory Analysis to analyze the
person trajectory.
Figure 3-14 Trajectory analysis result
The trajectory analysis can succeed only when the camera sites have been configured on the
electronic map.
Step 7 (Optional) Select multiple face images, and select Export Selected. You can also
select Export This Page or Export All from the drop-down list box as required. The

You can enable the encrypted export function when exporting files. After this function is enabled,
you need to enter the preset password when opening the file exported to the local computer.
----End
3.2.2.4 Face Alerts

Prerequisites
 The facial recognition function has been commissioned.
3.2.2.4.1 (Optional) Creating a Face Checkpoint Group
If you want to deploy an alert on one, several, or all cameras in the local domain, skip the
following operations.
If you want to deploy an alert on a checkpoint group in the alert domain, perform the
following steps to configure the checkpoint group and add cameras to the checkpoint
group in advance:
Step 1 On the iClient home page, choose System Management > Device Management.
Step 2 Click the Cameras tab, select cameras from the camera list on the right, and click
Virtual Attribute.
Step 3 Set Virtual Attribute to Facial recognition and click OK.

Step 4 Click the Checkpoint Management tab.
Step 5 Click Create Group, enter a group name, set Checkpoint Type to Face checkpoint, and
click OK.
Step 6 Select the created checkpoint group and click Add.

Step 7 In the dialog box that is displayed, select cameras. Only cameras whose physical or
virtual attribute is facial recognition are displayed.
Step 8 Click OK.

----End
3.2.2.4.2 Creating a Facial Recognition Task

Step 3 Click the Cameras tab and set intelligent analysis task parameters. Table 3-13
describes the key parameters.
You can select multiple cameras, select Apply to all, and set intelligent analysis task
parameters for the selected cameras in batches.
Table 3-13 Facial recognition task parameters
Video Type Video type. To use the face alert function, set Video Type to Live
to ensure the alert timeliness.
Type tasks will be executed on the IVS platform in the local domain.
Task Type Task type. Select Facial recognition and select the required facial
recognition algorithm. Multiple algorithms can be selected.
If the CloudWalk facial recognition algorithm is used, the
scheduled snapshot mode can be enabled for video stream
analysis. In this case, the Snapshot parameter needs to be set. In
scheduled snapshot mode, if the same face remains in the video
shot by a camera, the system captures the face image at the
interval specified by Snapshot. Generally, the scheduled snapshot
mode applies to facial recognition–based roll call after whitelist-
based alert.

----End
3.2.2.4.3 Creating a Face Alert Task

Step 1 On the iClient home page, choose Intelligent Applications > Face Alerts.
Step 2 Click New Alert Task. The New Task Info page is displayed, as shown in the following
figure.
Figure 3-16 Creating a face alert task
Set alert task parameters. Table 3-14 describes the parameters.
Table 3-14 Parameters for creating a face alert task
Alert Task Name Customized alert task name.
Active Time range for executing a face alert task. Use either of the
following methods to set this parameter:
 Select One Week, One Month, or One Year.
 Specify a period in the calendar.
 Click Set Hours to set the time segment for alert.
Alert Object Alert object. You can select either of the following options at a
time:
 Individual: Upload a face image and enter certificate
information. The system automatically adds the person to a
temporary face list in the face library.
 List: Select a face blacklist or whitelist.
Note:
 A face alert task can be created for only one type of face lists.
Therefore, you can select either blacklists or whitelists.
 You can create multiple alert tasks for face blacklists and
whitelists under the same alert scope.
Click New Alert Task and set alert task parameters, as shown in
the following figure.
Algorithm  Algorithm. You can select For all algorithms or For specified
algorithm.
− If you select For all algorithms, the value of Match
Threshold (%) applies to all algorithms enabled on the
iClient.
− If you select For specified algorithm, select algorithms used
for the alert task and set Match Threshold (%) for the
algorithms.
 Match Threshold (%): When the similarity between a passer-by
face and the target face is greater than or equal to the
threshold, the two faces match.
− A smaller threshold indicates more matched faces, lower
false negative rate, and higher false positive rate.
− A higher threshold indicates fewer matched faces, lower
false positive rate, and higher false negative rate.
Alert Level Alert level. Set this parameter based on the importance and
urgency level of the alert task. The severity of alarms generated by
an alert task depends on the importance and urgency of the task.
For example, if this parameter is set to Critical, the severity of
alarms generated by this alert task is also critical.
Alarm Type  Alarm type. When listed detected: When the recognized face
matches the target face of the face alert task, an alarm is
generated.
 When non-listed detected: When the recognized face does not
match the target face of the face alert task, an alarm is
generated.
Alert Scope  Alert domain.

− You can create an alert task in the local domain or lower-
level domain. When creating an alert task for the whole
domain, select the domain but do not select the checkpoint
groups in the domain.
− You can deploy an alert on cameras in a checkpoint group.
When creating an alert task for a checkpoint group, select
the checkpoint group but do not select the domain to which
the checkpoint group belongs.
 Camera: Select cameras in the local domain and deploy an alert
for the selected cameras. A maximum of 5000 cameras can be
selected.
----End
3.2.2.4.4 Viewing Face Alert Results

On the iClient home page, choose Intelligent Applications > Face Alerts and view the status
and details of each face alert task, as shown in the following figure.
Figure 3-17 Face alert page
On this page, you can perform the following operations:

 Enter a complete or partial alert task name and the user name (case-insensitive) of
the alert task creator in the search box to search for an alert task.
 You can click to filter alert tasks by Created, Alert Level, Alert Domain, and
False Positive List.
 Click a face alert task in the list on the left. The details about the task are displayed
on the right.
Checking the Alert Result on the Intelligent Recognition Page
On the Intelligent Recognition page, you can view the face snapshots and alert alarms of
specific cameras.
Step 1 On the iClient home page, choose Intelligent Applications > Intelligent Recognition.
Step 2 Double-click a camera in Cameras or drag a camera to the video pane. The live video
from the camera is played.
Step 3 View the face snapshots and alert alarms of the camera, as shown in the following
figure.
Figure 3-18 Intelligent recognition page
Choose More > Face Alarms on the right of Snapshot Alarms to go to the Alarm Center
page and view historical face alert alarms.
Choose More > More Faces on the right of Snapshot Results to go to the Information
Center page and view historical face snapshots.
----End
Viewing Alert Results on the Alarm Center Page

View the alarm information. You can obtain the location of the target face based on the
information about the camera that generates the alarm.
Step 1 On the iClient home page, choose Basic Operations > Alarm Center > Face Alerts.
The Face Alerts page is displayed.
Step 2 Set alarm search criteria. The Cameras parameter corresponds to Alert Scope, and
the Severity parameter corresponds to Alert Level.
Step 3 Click Search. The search result is displayed, as shown in the following figure.
Figure 3-19 Face alert alarm result
Export the face alert alarms to an Excel file and save the file to the local computer.
 To export selected alarms, select alarms and select Export Selected from the drop-
down list box.
 To export alarms on the current page, select Export This Page from the drop-down
list box.
 To export all alarms, select Export All from the drop-down list box.
You are advised to use professional video or image editing tools to shield irrelevant persons in
downloaded video or images and meet the HD requirements of the data subject. The
recommended procedure is as follows:
1. Download the required video to the local computer and extract the common video
from the required video.
2. Use a video editing tool to anonymize irrelevant persons' faces and only retain the
HD part of the data subject.
3. Export the anonymized video to meet the data transfer requirements of the data
subject.
Step 4 Click an alarm in the search result. The alarm details are displayed, as shown in the
following figure.
Figure 3-20 Face alert alarm details
The following functions are available:

 Live: View the live video shot by the camera corresponding to the alarm.
 Playback: View recorded video from the camera for which the alarm is generated.
 Map: Locate the camera for which the alarm is generated on the map.
 Face Search: Search for images of the face for which the alarm is generated.
 Task View: View information about the alert task that generates the alarm.
----End
3.2.2.4.5 Collecting Statistics on Face Snapshots

Prerequisites
 You have subscribed to face metadata generated by intelligent cameras or have
created intelligent facial recognition analysis tasks for cameras.
Procedure
Step 1 On the iClient home page, choose System Management > O&M Center.
Step 2 Choose Service Statistics > Analysis Platform and set Statistical Type to Face
snapshot statistics.
Step 3 Set Statistical Method to By time, set View Mode to Real-time passer-by face
statistics, and click Search.
The results are shown as follows:

Figure 3-21 Real-time passer-by face statistics
 When Statistical Method is set to By time, Data Source is automatically set to All and cannot
be modified.
 When View Mode is set to Real-time passer-by face statistics, Queried is from 00:00:00 of the
current day to the current time by default and cannot be modified.
Step 4 Set Statistics Method to By time, set View mode to Historical passer-by face statistics,
click Year, Month, or Date, or click to set Queried, and click Search.
Figure 3-22 shows the results.
Figure 3-22 Viewing historical passer-by face statistics by month
Step 5 (Optional) Click Export to export the statistics to an Excel file and save the file to the
local computer.
You are advised to use professional video or image editing tools to shield irrelevant persons
in downloaded video or images and meet the HD requirements of the data subject. The
subject.
Step 6 If Statistical Method is set to By device, you need to select a camera from the Data
Source drop-down list box. You can also select Real-time passer-by face statistics or
Historical passer-by face statistics for View Mode. The other operations are similar to
those in 3, 4, and 5 in statistics by time.
----End
3.2.2.4.6 Collecting Statistics on Face Alarms

Prerequisites
 A face alert task has been created for cameras.
Procedure
Step 2 Choose Service Statistics > Analysis Platform and set Statistical Type to Face alarm
statistics.
Step 3 Set Statistical Method to By time, set View Mode to Real-time alarm statistics, and
click Search.
Figure 3-23 Real-time face alarm statistics
be modified.
 When View Mode is set to Real-time alarm statistics, Queried is from 00:00:00 of the current
day to the current time by default and cannot be modified.
Step 4 Set Statistical Method to By Time, set View Mode to Historical alarm statistics, click
Year, Month, or Date, or click to set Queried, and click Search.

Figure 3-24 Viewing historical facial alarm statistics by month
local computer.
subject.
Source drop-down list box. You can also select Real-time alarm statistics or Historical
alarm statistics for View Mode. The other operations are similar to those in 3, 4, and
5 in statistics by time.
----End
3.2.3 Intelligent Person Analysis on the IVS Platform

Personal feature recognition is to recognize a person who appears in the surveillance area
and obtain the personal attributes including sex, age group, tops style, tops pattern, tops
color, bottoms style, bottoms color, backpack, hat, and umbrella.
 Person search by image allows users to import a person image to the IVS platform so
that the system can automatically analyze personal features in the image, search for
data based on the features, and sort the data by similarity.
 Person search by criteria allows users to set attributes to search for persons.
Prerequisites
 The person search function has been commissioned.
 The personal feature recognition algorithm plug-in has been installed on the CSP
OM portal. For details, see chapter 2 "Installation and Configuration of Algorithms."
3.2.3.1 (Optional) Creating an Intelligent Analysis Task for Live Video from Cameras
To recognize persons in live video, you can create a personal feature recognition task or
pedestrian and vehicle data structuring task for live video from the camera. The procedure
is as follows:
Step 2 Click New Task.
The New Intelligent Analysis Task page is displayed.

parameters.
You can select multiple cameras and select Apply to all to set parameters for the selected
cameras in batches.
Table 3-15 Intelligent analysis task for live video parameter description
Video Type Select Live.
Execution Domain Select Local domain. Intelligent analysis tasks will be executed
Type on the IVS platform in the local domain.
Priority Task priority for determining the task execution sequence. The
Level 1 (highest) value indicates the highest priority.
Stream When creating an intelligent analysis task for cameras, you can
select the stream type used during intelligent analysis.
Intelligent analysis can be performed only when the video type
is live video.
Execution Period Time segment during which an intelligent analysis task can be
scheduled and executed.
Task Type Select Personal feature recognition or Pedestrian and vehicle

data structuring. After setting Task Type, select one or more
algorithms as required.
Advanced Settings Area for specifying a region of interest (ROI), as shown in the
following figure.
It is recommended that the ROI avoid areas without human
activities to exclude non-person images and reduce the false
positive rate.
Figure 3-25 Specifying an ROI
Step 5 Click Save.

----End
3.2.3.2 (Optional) Creating an Intelligent Analysis Task for Recorded Video from
Cameras
To recognize persons in recorded video, you can create a personal feature recognition task
or pedestrian and vehicle data structuring task for recorded video from the camera. The
procedure is as follows:
Step 3 Click the Camera text box and select the camera whose recordings are to be
searched for.
Step 4 Set search criteria and click Search.

Step 6 Create an intelligent analysis task for recordings and select Apply to all. On the page
that is displayed, you can set intelligent analysis task parameters in batches. Table 3-
16 describes the parameters.
Table 3-16 Personal feature recognition task parameter description
Video Type Select Recorded.
Analysis Period When the value of Video Type is Recorded, you need to
configure the recording time segment for which personal
feature recognition is to be performed.
Execution Domain Type Select Local domain. Intelligent analysis tasks will be
executed on the IVS platform in the local domain.
Task Type Select Personal feature recognition or Pedestrian and

vehicle data structuring. After setting Task Type, select
required algorithms. If multiple algorithms are available,
you can select multiple algorithms.
Fast Analysis When Video Type is set to Recorded and Task Type is set
to Pedestrian and vehicle data structuring or Personal
feature recognition, you can select Fast Analysis.
Note:
 If Fast Analysis is selected, you can set Execution
Domain Type only to Local domain.
 An intelligent analysis task with Fast Analysis selected
provides at most 50x analysis. The analysis capability is
restricted by the amount of idle GPU resources, number
of remaining license channels, and MPUR node
download bandwidth.
 If the MPUR node is running recording playback
services, such as video viewing and video analysis, the
intelligent analysis task with Fast Analysis selected
shares the 256 Mbit/s download bandwidth with these
services, and therefore the speed cannot reach 50x.
 If Fast Analysis is selected for a task, a large number of
GPU resources are required to execute this task. As a
result, subsequent intelligent analysis tasks can be
executed only after these GPU resources are released.
Advanced Settings Area for specifying an ROI.

It is recommended that the ROI avoid areas without
human activities to exclude non-person images and reduce
the false positive rate.
Step 7 Click Save.

----End
3.2.3.3 (Optional) Uploading a Local Video File and Creating an Intelligent Analysis
Task
In addition to extracting personal features from live or recorded video, you can create a
personal feature recognition task or pedestrian and vehicle data structuring task for an
uploaded video file to extract personal features from the video file. The procedure is as
follows:
Step 4 After the video file is uploaded, view the uploaded video file on the Uploaded Video
tab page.
----End
Creating a Person-related Analysis Task
Step 4 Create a personal feature recognition task or pedestrian or vehicle data structuring
task for the video file. After setting Task Type, select one or more algorithms as
required.
Step 5 Click Save.

----End
3.2.3.4 Performing Person Search

Searching by Image
Step 1 On the iClient home page, choose Intelligent Applications > Person Search.
Step 2 Click the Search by Image tab.
Step 3 (Optional) To specify more restrictions on the search scope, click More and enter
search criteria as required. Table 3-17 describes the parameters.
Table 3-17 Parameters for person search by image
Period Period during which the person images are captured.

 Select Past 3 Days, Past Week, or Past Month.
Search Domain Select the local domain for person search.
Sort by Threshold of the similarity to the target for the search.

Similarity
Algorithm Algorithm used for personal feature recognition and person search.
Source Video source of the captured person images. The options are
Step 4 Drag a person image to the search box. In the Upload Image dialog box that is
displayed, frame a part of the person body, and click OK.
Figure 3-26 Framing a person body
The uploaded person image must meet the following requirements:

 The image format must be JPG, JPEG, DIB, BMP, or PNG.
 The image size does not exceed 5 MB, and the image resolution does not exceed
4096 x 3000 pixels.
 The resolution of the selected person area ranges from 60 x 60 pixels to 800 x 1200
pixels.
Step 5 Click Search. The Snapshot Library tab page is displayed to search for the target
person. Images in the snapshot library are extracted by the personal feature
recognition task and person and vehicle data structuring task. The following figure
shows the search results.
Figure 3-27 Results of person search by image
Step 6 (Optional) Select multiple person images and click Trajectory Analysis to analyze the

electronic map.
Step 7 (Optional) Select multiple face images, and select Export Selected, or select Export
This Page or Export All from the drop-down list box as required. The following figure
shows the export page.
You can enable the encrypted export function. After this function is enabled, you need to enter
the preset password when opening the file exported to the local computer.
----End
Filter by Criteria
Step 1 On the iClient home page, choose Intelligent Applications > Person Search.
Step 3 Set desired search parameters. Table 3-18 describes the parameters.
Table 3-18 Parameters for filtering persons by criteria
Source Video source of the captured person images. The options are
Captured Period during which the person images are captured.
Search Domain Search domain. Select the local domain for person search.
Algorithm Personal feature recognition and person search algorithm.

You can select Personal metadata subscription for search by criteria.
Images in the search results are from subscribed metadata of
intelligent cameras.
Feature Indicates whether to display the images from which personal

Extracted features have been extracted. The options are as follows:
 Yes: displays the images from which personal features have been
extracted.
 No: displays the images from which personal features have not
been extracted.
All: displays all images.
Object Type Type of the target for search, for example, Person or Cyclist.
Step 4 Click Search. The Snapshot Library page is displayed to search for the target person.
Results are shown in the following figure. Images in the snapshot library are
extracted by the personal feature recognition task and person and vehicle data
structuring task.
Figure 3-30 Results of person search by criteria
Step 5 (Optional) Use a clear target person image for secondary search to obtain more
images of the target person. Click the person search result. On the details page that
is displayed, click Search.
Step 6 (Optional) Select multiple person images and click Trajectory Analysis to analyze the
electronic map.
Step 7 (Optional) Select multiple face images and click Export Selected. You can also select
Export This Page and Export All from the drop-down list box as required. The
following figure shows the export page.
----End
3.2.4 Intelligent Vehicle Analysis on the IVS Platform

Based on the vehicle recognition algorithm, the IVS platform can extract license plate and
vehicle information from video and implement intelligent vehicle analysis, including vehicle
recognition, vehicle search, vehicle alert, and passing vehicle statistics. The IVS platform
can also subscribe to the vehicle metadata from intelligent cameras to implement
intelligent vehicle analysis.
3.2.4.1 Vehicle Library

3.2.4.1.1 Adding a Vehicle List
Adding a Vehicle Blacklist
The default vehicle blacklist is available by default. Global alerts are automatically deployed on
vehicles in this blacklist. You cannot manually create alert tasks for vehicles in the default
blacklist, and cannot delete or modify the blacklist.
Step 1 On the iClient home page, choose Intelligent Applications > Vehicle Library.
Step 2 Click New List, set Name and List Type, and click OK.
Step 3 Click OK.
Generating a Temporary List
After you create a vehicle alert task for specific vehicles, a temporary list and the
corresponding vehicle information are automatically generated.
 You cannot manually add a temporary list on the Vehicle Library page.
 Before deleting a vehicle list under Temporary Lists, you must delete the corresponding
vehicle alert task.
----End
3.2.4.1.2 Adding Vehicle Records to a Vehicle List

Adding Vehicle Records One by One
Step 1 Select a vehicle list and click New.
Step 2 (Optional) Upload a vehicle image. To be specific, click . In the dialog box that is
displayed, draw a box to select the vehicle image for alert, and click OK.
The supported image formats are .JPG, .JPEG, .JPE, .DIB, .BMP, and .PNG. Each image cannot
exceed 5 MB.
Step 3 Fill in the basic information about the vehicle, as shown in the following figure. The
License Plate parameter is mandatory. You can use an asterisk (*) to represent zero,
or more unknown license plate characters. Set other parameters based on the actual
available information.
Figure 3-33 Basic vehicle information
Step 4 Click OK.

----End
Importing Vehicle Records
Step 1 Select a vehicle list and click Import.

Step 2 Set Import Method to Template import, Batch import, or Quick import.
 Import by template
1. Click Download Template or Download Template (No Image) to download either
template to the local computer. If you click Download Template (No Image), you
cannot fill in vehicle images in the downloaded template. Download either template
2. Decompress the downloaded package, open Image Batch Import Tool.xlsm, and fill
in vehicle information in the template.
 If you click Download Template, you can click Read All Files in Target Folder in the
downloaded template to automatically read image names. Vehicle images must be stored in
the same folder as the Image Batch Import Tool.xlsm template and the .csv file generated
later.
 You must set the License Plate parameter in the template. Otherwise, the .csv file cannot be
generated.
 The supported image formats are .JPG, .JPEG, .JPE, .DIB, .BMP, and .PNG. Each image cannot
exceed 5 MB.
 A maximum of 10,000 vehicle records can be imported at a time.
3. Click Generate CSV File in the template.
4. Click on the right of List File, select a local .csv file, and upload the file.
 Batch import
Click on the right of List File and select the folder for storing vehicle images.
 The supported image formats are .JPG, .JPEG, .JPE, .DIB, .BMP, and .PNG. Each image cannot
exceed 5 MB.
 An image must be named in the format License plate_Vehicle color_Vehicle type_Plate
color_Plate type_Make_Model_Year_Owner_Owner ID number. Fields in each image name
must be by underscores (_). The License plate field is mandatory.
 Fields in the image name must be separated by underscores (_). The values of Vehicle color,
Vehicle type, and Plate color must be enumerated values. For details, see Table 3-19.
 If a field between two other fields needs to be ignored, use an underscore (_) to replace the
field. For example, if only the license plate and vehicle type can be identified for a vehicle
image, the vehicle image can be named in the format License plate__Vehicle type.File name
extension.
Image Naming Values

Parameter
Vehicle color 0: white; 1: gray; 2: yellow; 3: pink; 4: red; 5: green; 6: blue; 7:

brown; 8: black; 9: unknown; 10: purple; 11: orange; 12: silver; 13:
cyan; 14: golden; 996: blue/cyan; 997: white/gray/silver; 998:
yellow/brown/orange/golden; 999: red/pink/purple; -1: others.
Vehicle type 0: unknown; 1: car; 2: truck; 3: van; 4: bus; 5: small truck; 6: SUV; 7:
medium-sized bus; 8: motorcycle; 9: others.
Plate color 0: white; 2: yellow; 5: green; 6: blue; 8: black; 9: unknown; 10:

gradient green; 11: yellow and green.
Vehicle color 0: white; 1: gray; 2: yellow; 3: pink; 4: red; 5: green; 6: blue; 7:

brown; 8: black; 9: unknown; 10: purple; 11: orange; 12: silver; 13:
cyan; 14: golden; 996: blue/cyan; 997: white/gray/silver; 998:
yellow/brown/orange/golden; 999: red/pink/purple; -1: others.
 Quick import
Click on the right of List File and select the folder for storing vehicle images.
The supported image formats are .JPG, .JPEG, .JPE, .DIB, .BMP, and .PNG. Each image cannot
exceed 5 MB.
IVS platform extracts fields from image names. Therefore, images must meet the
following requirements:
 An image must be named after the license plate.
 A license plate can include 1 to 255 characters, including letters and digits.
Step 3 Ensure that all vehicle information is successfully verified and click Import. If the
verification fails, rectify the fault.
Step 4 Click OK.

----End
3.2.4.1.3 Searching for Vehicle Records in a Vehicle List

Step 1 Select a vehicle list on the left, enter characters of a license plate, a vehicle owner
name, or an ID number of a vehicle owner in the search box, and click to search
for the vehicle.
Step 2 Select a vehicle list on the left, click Advanced, set search criteria, and click Search to
search for the vehicle. You can double-click a record in the search result to view the
vehicle details.
Figure 3-34 Searching for vehicle records by criteria
----End
3.2.4.2 Vehicle Search

Prerequisites
 The vehicle recognition function has been commissioned.
 Install the vehicle algorithm plug-in on the CSP OM portal. For details, see chapter 2
"Installation and Configuration of Algorithms."
 Vehicle lists and corresponding vehicle information have been added to the vehicle
library.
3.2.4.2.1 Setting Algorithm Parameters
Parameters in the algorithm are automatically set to the default values after the system is
initialized. Only a small number of parameters need to be manually adjusted based on the
site requirements. Parameters that require manual settings are described in the parameter
tables. Use the default values for other parameters. If any modification is required, contact
technical support.
Vehicle Recognition Algorithm huawei_cmv
After the system is initialized, the vehicle recognition algorithm huawei_cmv takes effect only
after the huawei_cmv algorithm plug-in is manually installed.
Step 1 On the iClient home page, choose System Management > Algorithm Management.
Step 2 Click the huawei_cmv algorithm. The algorithm details are displayed, as shown in the
following figure.
Figure 3-35 huawei_cmv algorithm details
When the algorithm is used, the characters that indicate the provinces to which the license
plates belong need to be adapted in the Plug-In Initialization Parameter text box. Table 3-
20 shows details about the parameters and functions.
Table 3-20 Parameters to be set for huawei_cmv
LocalChar Shortened forms of the provinces to which the license plates belong.
If the first character of the license plate is not clear enough, the algorithm
matches it with those configured for this parameter, and selects the
character with the highest similarity as the first character of the license
plate. This helps improve the recognition accuracy of the first character.
The options are the shortened forms of Chinese provinces and cities.
You can configure one or more characters. (One character is recognized).
If there are multiple values, do not add separators (such as spaces or
commas) between values. When there are more than six characters, only
the first six characters are valid and the repeated characters are counted.
For huawei_cmv, only the LocalChar parameter needs to be adjusted. Use the default
values for other parameters. If other parameters are modified or the XML syntax
structure is modified, license plates cannot be recognized and a large number of
intelligent analysis tasks will fail.
Step 3 Click OK. A dialog box is displayed, as shown in Figure 3-36.
Figure 3-36 Confirm dialog box
Step 4 After confirming that the parameter settings are correct, click OK.
Step 5 (Optional) If an intelligent analysis task has been created for the algorithm, restart
this task for the parameter settings to take effect.
----End
License Plate Recognition Algorithm lpr_qfreeAPI
Step 1 On the iClient home page, choose System Management > Algorithm Management.
Step 2 Click the lpr_qfreeAPI algorithm. The algorithm details are displayed, as shown in the
following figure.
When the algorithm is used, the characters that indicate the height of license plate
characters, country or region code, and confidence need to be adapted in the Plug-In
Initialization Parameter text box. Table 3-21 shows details about the parameters and
functions.
Figure 3-37 lpr_qfreeAPI algorithm details
Table 3-21 Parameters to be modified for lpr_qfreeAPI
CharacterSize Character height, including the minimum character height and

maximum character height.
As a vehicle approaches the camera, the alphanumerics of the
license plate in the image changes from small to large. This
parameter specifies the minimum and maximum height of
characters that can be clearly identified. Only license plates whose
character height is within the specified range can be recognized.
The optimal character height must be calculated based on the site
requirements. To view the minimum and maximum heights of
license plate characters, perform the following steps:
1. Choose Basic Operations > Live.
2. Select a camera for license plate recognition and view the live
video. Right-click the live video image and choose Snapshot >
Local to capture passing vehicles.
3. Open the snapshots using a drawing software and view the
heights of characters that can be clearly identified.
4. Draw a rectangle tightly close to the license plate characters and
view the vertical pixel value of the selected area, as shown in the
following figure.
Countries Country or region code.

The license plate recognition can be performed only for license
plates belonging to the specified country or region.
When setting a country or region code, fill in also the general license plate
style codes of the country or region, and use commas (,) to separate
multiple style codes. For example, enter T,X_EU for Thailand.
RejectConfidence Rejection confidence.

Adjust the rejection confidence based on the site requirements. The
license plate recognition result is displayed only when the license
plate confidence is higher than the rejection confidence. A higher
rejection confidence indicates that fewer license plates will be
recognized. If the rejection confidence is too low, the false positive
rate may increase.
The value is an integer that ranges from 0 to 1000. The default
value is 700.
For the lpr_qfreeAPI algorithm, only the parameters in the preceding table need to be
modified. Do not modify other parameters but use their default values. If other
parameters are modified or the XML syntax structure is modified, license plates cannot be
recognized and a large number of intelligent analysis tasks will fail.
Step 3 Click OK. A dialog box is displayed, as shown in Figure 3-38.
Figure 3-38 Confirm dialog box
Step 4 After confirming that the parameter settings are correct, click OK.
Step 5 (Optional) If an intelligent analysis task has been created for the algorithm, restart
this task for the parameter settings to take effect.
----End
3.2.4.2.2 (Optional) Creating an Intelligent Analysis Task for Live Video from Cameras
To recognize vehicles in video, create an intelligent analysis task for live video from cameras.
The detailed operations are as follows:
parameters. You can select multiple cameras and then select Apply to all to set
intelligent analysis task parameters for cameras in batches.
Execution Select Local domain. Intelligent analysis tasks will be executed on

Domain Type the IVS platform in the local domain.
Priority Task priority for determining the task execution sequence. The
Level 1 (highest) value indicates the highest priority.
Stream When creating an intelligent analysis task for cameras, you can
select the stream type used during intelligent analysis. Intelligent
analysis can be performed only when the video type is live video.
Execution Period Time segment during which an intelligent analysis task can be
scheduled and executed.
Task Type  When creating a license plate recognition task, select License
plate recognition and select one or more license plate
recognition algorithms.
 When creating a vehicle recognition task, select Vehicle
recognition and select one or more vehicle recognition
algorithms. By default, Vehicle attributes is selected. If you
want to use the function of vehicle search by image, select
Vehicle features.
 When creating a pedestrian and vehicle data structuring task,
select Pedestrian and vehicle data structuring and select one or
more related algorithms.
Advanced  ROI parameters: You can specify an ROI. It is recommended

Settings that the ROI avoid areas without vehicle activities to exclude
obstacles and reduce the false positive rate.
 You can set Min. Plate Frame and Max. Plate Frame.
 You can set Save snapshot. If the snapshot storage function is
enabled, the vehicle images recognized and pushed by
intelligent cameras are stored on the platform server. This
parameter is not valid for common cameras.

Step 5 Click Save.

----End
3.2.4.2.3 (Optional) Creating an Intelligent Analysis Task for Recorded Video from
Cameras
To recognize vehicles in video, you can create an intelligent analysis task for recordings
from cameras. The detailed operations are as follows:
Step 3 Click the Camera text box, and select the camera whose recordings are to be
searched for.
Step 4 Set search criteria and click Search.

Step 6 Create an intelligent analysis task for recorded video from the cameras. You can
select multiple cameras, select Apply to all, and set intelligent analysis task
parameters for the selected cameras in batches. Table 3-23 describes the parameters.
Video Type Select Recorded.
Analyzed Recording segment for intelligent analysis

Task Type  When creating a vehicle recognition task, select Vehicle

algorithms. If you select huawei_cmv, Vehicle attributes is
selected by default. If you want to use the function of vehicle
search by image, select Vehicle features.
By default, Personal and vehicle attributes is selected. If you want
to use the function of person search by image, select Personal
features.
Fast Analysis When Video Type is set to Recorded and Task Type to Pedestrian
and vehicle data structuring or Vehicle recognition (vehicle
recognition algorithm: huawei_cmv), you can select Fast Analysis.
If Fast Analysis is selected, you can set Execution Domain Type only to Local
domain.
 An intelligent analysis task with Fast Analysis selected provides
at most 50x analysis. The analysis capability is restricted by the
amount of idle GPU resources, number of remaining license
channels, and MPUR node download bandwidth.
 If the MPUR node is running recording playback services, such
as video playback and video analysis tasks, the intelligent
analysis task with Fast Analysis selected shares the 256 Mbit/s
download bandwidth with these services, and therefore the
speed cannot reach 50x.
 If Fast Analysis is selected for a task, a large number of GPU
resources are required to execute this task. As a result,
subsequent intelligent analysis tasks can be executed only after
these GPU resources are released.

Step 7 Click Save.

----End
3.2.4.2.4 (Optional) Uploading a Local Video File and Creating an Intelligent Analysis
Task
In addition to extracting vehicle data from live or recorded video, you can create an
intelligent analysis task for an uploaded video file to extract vehicle data from the video
file. The procedure is as follows:
The system starts uploading the video file. You can view the uploaded video file on
----End
Creating an Intelligent Vehicle Analysis Task
Step 7 Create an intelligent analysis task for the video file. Table 2-16 describes the
parameters.
Step 8 Click Save.

----End
3.2.4.2.5 Performing Vehicle Search

Searching by image
Step 1 On the iClient home page, choose Intelligent Applications > Vehicle Search.
Step 2 Select the Search by Image tab.
Step 3 (Optional) To specify more restrictions on the search scope, click More and enter
search criteria as required. Table 3-24 describes the parameters.
Table 3-24 More search criteria
Period Period during which the vehicle images are captured.

Search Domain Select Local domain for vehicle search.
Sort by Similarity Threshold of the similarity to the target for the search.
Algorithm Algorithm used for vehicle recognition and search.
Source Video source of the captured vehicle images. The options are
Step 4 Upload or select a vehicle image.

 Drag a vehicle image to the search box. On the Upload Image page that is displayed,
frame the required part and click OK.
 Enter some or all characters of a license plate, a complete vehicle owner name, or a
complete vehicle owner ID number in the search box. Select a vehicle image among
those found in the vehicle library.
Figure 3-40 Selecting a vehicle image found in the vehicle library
Step 5 Click the search icon. The Snapshot Library page is displayed to search for the target
person. Images in the snapshot library are extracted from vehicle feature recognition
tasks. The following figure shows the search results.
Figure 3-41 Results of vehicle search by image
Step 6 (Optional) Select multiple vehicle images and click Trajectory Analysis. The following
figure shows the analysis result.
Figure 3-42 Vehicle trajectory analysis
electronic map.
Step 7 (Optional) Select multiple face images and select Export Selected. You can also select
Export This Page and Export All from the drop-down list box as required. The
----End
Filtering by Criteria
Step 3 Set the parameters for searching by criteria. Table 3-25 describes the key parameters.
Table 3-25 Key filter criteria for vehicle search
License Plate License plate characters of the vehicle that is searched for. Fuzzy
search is supported, where the question mark (?) matches exactly one
character, and the asterisk (*) matches zero or more characters.
Unknown If you select this parameter, you cannot set License Plate, and the
plate iClient searches for vehicles without specific license plates.
Approximate The vehicle or license plate recognition algorithm may recognize

matches multiple approximate license plates for the same vehicle. The vehicle
information in the database includes the license plates with the
highest confidence and other approximate license plates.
If this check box is selected, iClient compares the entered license
plate with all license plates.
If the check box is not selected, iClient compares the entered license
plate only with license plates with the highest confidence.
Click Search. The Snapshot Library page is displayed to search for the target vehicle. The
snapshot library contains vehicle images extracted by vehicle recognition, license plate
recognition, or pedestrian and vehicle data structuring. The following figure shows the
search results.
The vehicle image on the right of the page is found in the vehicle library and contains
related vehicle information.
For more accurate search results, you can click More to set more filter criteria.
Figure 3-43 Vehicle search results
Step 4 (Optional) To obtain more accurate vehicle information, you can perform secondary
feature recognition on the images displayed as search results.
Typically, secondary feature recognition applies to the scenario where the vehicle recognition
algorithm of the IVS platform is used to recognize the vehicle images obtained through metadata
subscription again. After secondary feature recognition, if the vehicle information is not
consistent, the results obtained from secondary feature recognition prevails. The analysis result of
secondary feature recognition overwrites the original vehicle metadata.
1. Select the vehicle search result.
2. Click Secondary Feature Recognition.
3. In the Select algorithm dialog box, click the algorithm used for vehicle analysis and
click OK.
4. You can choose Intelligent Applications > Tasks to view the progress of secondary
feature recognition.
Step 5 (Optional) Select multiple vehicle images and click Trajectory Analysis. The following
figure shows the analysis result.
Figure 3-44 Vehicle trajectory analysis
electronic map.
Step 6 (Optional) Select multiple face images, and select Export Selected, or select Export
This Page Export All from the drop-down list box as required. The following figure
shows the page for exporting files.
Step 7 Click the Vehicle Library tab to view the search results in the vehicle library, as shown
in the following figure.
For more accurate search results, you can click Advanced Search to set more filter criteria.
Figure 3-45 Search result in the vehicle library
----End
3.2.4.3 Vehicle Alert

This section describes how to configure a vehicle alert task. After creating an intelligent
analysis task or subscribing to vehicle metadata generated by intelligent cameras on the
iClient, you can configure alert tasks to implement vehicle alert.
Prerequisites
 The vehicle recognition function has been commissioned.
 To use vehicle recognition to implement intelligent vehicle analysis, ensure that the
vehicle recognition algorithm plug-in has been installed on the iClient and has been
enabled. For details, see chapter 2 "Installation and Configuration of Algorithms."
 Metadata subscription has been completed if vehicle metadata generated by
intelligent cameras needs to be used to implement intelligent vehicle analysis.
 Ensure that the video and image resolution is greater than or equal to 768 x 432
pixels and no greater than 8,847,360 pixels or 4096 x 3000 pixels. If the resolution is
not in the defined range, the iClient cannot obtain the vehicle recognition result.
3.2.4.3.1 (Optional) Creating a License Plate Checkpoint Group
If you want to create alerts on one or more cameras in the local domain, skip the following
operations. If you want to deploy an alert on a checkpoint group in the alert domain,
perform the following steps to configure the checkpoint group and add cameras to the
checkpoint group in advance:
Step 1 On the iClient home page, choose System Management > Device Management.
Step 2 Click the Cameras tab, select cameras from the camera list on the right, and click
Virtual Attribute.
Step 3 Set Virtual Attribute to Vehicle recognition and click OK.

Step 4 Click the Checkpoint Management tab.
Step 5 Click Create Group, set Group Name, and set Checkpoint Type to License plate
checkpoint.
Step 6 Select the created checkpoint group and click Add.

Step 7 In the dialog box that is displayed, select cameras. Only cameras whose value of
Physical Attribute or Virtual Attribute is Vehicle recognition are displayed.
Step 8 Click OK.

----End
3.2.4.3.2 (Optional) Creating an Intelligent Analysis Task

You can create a pedestrian and vehicle data structuring task or vehicle recognition task
for a camera, or subscribe to vehicle metadata from intelligent checkpoint cameras for
alerts. Select an alert mode based on the service plan. To create an intelligent analysis task,
perform the following steps:
parameters. You can select multiple cameras, select Apply to all, and set intelligent
analysis task parameters for the cameras in batches.
Video Type When creating an intelligent vehicle analysis task for alert, set
Video Type to Live to ensure the alert timeliness.

Task Type  When creating a vehicle recognition task, select Vehicle

algorithms. If you select huawei_vehicle_sdk, Vehicle attribute is
selected by default. If you want to use the function of vehicle
search by image, select Vehicle features.
If you select huawei_struct, Personal and vehicle attributes is
selected by default. If you want to use the function of person
search by image, select Personal features.

Step 5 Click Save.

----End
3.2.4.3.3 Creating a Vehicle Alert Task

Step 1 (Optional) View the recordings generated around the incident occurrence time to
obtain preliminary information about the target vehicle.
1. On the iClient home page, choose Basic Operations > Information Center.
2. Click Recordings.
3. Click the Camera text box and select a camera near the incident location.
4. Set search criteria and click Search.
Figure 3-47 Searching for recordings
5. Specify a time segment that covers the incident occurrence time on the timeline of
the camera recording, hold down Ctrl, and click the timeline to view the recording.
6. Hold down and drag on the timeline to select a time segment and click to
view related information.
Figure 3-48 Viewing a recording
When viewing a recording, you can pause it and take snapshots, and then obtain vehicle
information from the snapshots. For example, the vehicle license plate number is AS*H2,
the vehicle color is black, the license plate color is blue, and the vehicle brand is Volkswagen.
You can search for vehicles based on the preliminary information to obtain more accurate
vehicle information, which helps you find the target vehicle more accurately.
Step 2 (Optional) To create an alert on a vehicle in the vehicle library, create a vehicle
whitelist/blacklist first. For details, see section 3.2.4.1 "Vehicle Library."
Step 3 Configure a vehicle alert task.

1. On the iClient home page, choose Intelligent Applications > Vehicle Alerts.
2. Click New Alert Task and set alert task parameters, as shown in the following figure.
Figure 3-49 New alert task information
Table 3-27 Parameters on the page for creating a vehicle alert task
Alert Task Name Alert task name.
Active Time range in which a vehicle alert task is executed.
Set Hours Time segment in which a vehicle alert task is executed.
Alert Object The vehicle object that the alert task targets. You can select either
of the following options at a time:
 Vehicle: You must enter a license plate (or upload a license
plate image). To create a fuzzy alert, you can use an asterisk (*)
to represent zero or more unknown license plate characters.
The vehicle is automatically added to Temporary Lists under
Vehicle Library.
 List: You can select a vehicle blacklist. To support fuzzy alerting,
a fuzzy plate number can be included in the list, with zero or
more unknown license plate characters replaced with an
asterisk (*).
Approximate The vehicle recognition algorithm can provide the recognition

License Plate result of the license plates whose similarities rank top 3.
 If Approximate License Plate is not selected, only the license
plate whose similarity ranks top 1 triggers the alarm.
 If Approximate License Plate is selected, license plates whose
similarities rank top 3 trigger the alarm.
Alert Level Set this parameter based on the importance and urgency level of
the alert task. The severity of alarms generated by an alert task
depends on the importance and urgency of the task. For example,
if this parameter is set to Critical, the severity of alarms generated
by this alert task is also critical.
Alarm Type  When listed detected: When the recognized vehicle matches the
vehicle specified by Alert Object, this type of alarm is
generated.
 When non-listed detected: When the recognized vehicle does
not match the vehicle specified by Alert Object, this type of
alarm is generated.
Alert Scope  Alert domain: Deploys an alert on cameras in the checkpoint

camera group.
 Camera: Select cameras in the local domain and deploy an alert
for the selected cameras. A maximum of 5000 cameras can be
selected.
----End
3.2.4.3.4 Viewing Vehicle Alert Search Results

On the iClient home page, choose Intelligent Applications > Vehicle Alerts and view the
status and details of each vehicle alert task, as shown in the following figure.
Figure 3-50 Vehicle alert page
On this page, you can perform the following operations:

 Enter a complete or partial alert task name and the user name (case-insensitive) of
the alert task creator in the search box to search for an alert task.
 Click to filter alert tasks by Created Since, Alert Level, Alert Domain, and List.
 Click a vehicle alert task in the list on the left. The details about the task are
displayed on the right.
Checking the Alert Result on the Intelligent Recognition Page
On the Intelligent Recognition page, you can view the vehicle snapshots and alerts of
specific cameras.
Step 1 On the iClient home page, choose Intelligent Applications > Intelligent Recognition.
Step 2 Double-click a camera in Cameras or drag a camera to the video pane. The live video
from the camera is played.
Step 3 View the face snapshots and alert alarms of the camera, as shown in the following
figure.
Figure 3-51 Intelligent Recognition page
Click More > Vehicle Alarms on the right of Snapshot Alarms. On the displayed Alarm
Center page, check historical vehicle alert information.
Choose More > More Vehicles on the right of Snapshot Results. The Information Center
page is displayed, showing historical vehicle snapshots.
----End
Viewing Alert Results on the Alarm Center Page

When viewing alarm information, you can obtain the location of the target vehicle based
on the information about the camera that generates the alarm.
Step 1 Click More. The Alarm Center page is displayed, showing historical vehicle alerts, as
shown in Figure 3-52.
Figure 3-52 Vehicle alerts
Export the vehicle alerts to an Excel file and save the file to the local computer.
 To export selected alarms, select alarms and select Export Selected from the drop-
down list box.
 To export alarms on the current page, select Export This Page from the Export
Selected drop-down list box.
 To export all alarms, select Export All from the Export Selected drop-down list box.
You are advised to use professional video or image editing tools to shield irrelevant persons
in downloaded video or images and meet the HD requirements of the data subject. The
subject.
Step 2 Click an alarm in the search result. The alarm details are displayed, as shown in
Figure 3-53.
Figure 3-53 Vehicle alarm details
The following functions are available:

 Live: View the live video shot by the camera for which the alarm is generated.
 Playback: View live video from the camera for which the alarm is generated.
 Map: Locate the camera for which the alarm is generated on the map.
 Vehicle Search: Search for images of the vehicle that triggers the alarm.
 Task View: View information about the alert task that generates the alarm.
----End
3.2.4.3.5 Passing vehicle statistics

Prerequisites
 Install the vehicle algorithm plug-in on the CSP OM portal. For details, see chapter 2
"Installation and Configuration of Algorithms."
 You have subscribed to passing vehicle metadata generated by intelligent cameras,
or have created intelligent analysis tasks such as vehicle recognition, or pedestrian
and vehicle data structuring tasks for cameras.
Step 2 Choose Service Statistics > Analysis Platform and set Statistical Type to Passing
vehicle statistics.
Step 3 Set Statistical Method to By time, set View mode to Real-time passing vehicle
statistics, and click Search.

Figure 3-54 Real-time passing vehicle statistics
be modified.
 When View Mode is set to Real-time passing vehicle statistics, Queried is from 00:00:00 of the
current day to the current time by default and cannot be modified.
Step 4 Set Statistical Method to By time, set View mode to Historical passing vehicle
statistics, click Year, Month, or Date, or click to set Queried, and click Search.
Figure 3-55 Historical passing vehicle statistics by month
local computer.
subject.
Source drop-down list box. You can also select Real-time passing vehicle statistics or
Historical passing vehicle statistics for View Mode. The other operations are similar
to those in 3, 4, and 5 in statistics by time.
----End
4 Domain Management
4.1 Introduction
A typical domain in an intelligent vision system (IVS) is a physical domain such as
surveillance systems of a campus or a city. Different domains, whether they are upper- and
lower-level domains or external domains, can be connected to each other as required. This
experiment is designed to help students understand complex networking configuration by
showing how to configure the connection to upper- and lower-level domains as well as
external domains.
4.1.2 Objectives
 Learn how to configure the connection between upper- and lower-level domains and
verify the implementation result.
 Understand how to configure the connection to an external domain and verify the
implement result.

4.2.1 Connecting Upper- and Lower-Level Domains
4.2.1.1 Configuring the External Management Network Plane
Configuring the External Management Network Plane for the Upper-Level Domain
If an upper-level domain is the CloudIVS 3000 or IVS3800 of V100R019C20 or later and the
system needs to connect to other systems through the Outer_OM (external management
plane) to form upper- and lower-level domains, you can refer to this section to configure
the external management plane. This experiment uses IVS3800 V100R019C50 as an
example.
Step 1 Log in to the CSP OM portal of the upper-level domain as the admin user.
Application Name > Network > External Management Network Plane Configuration.
Step 3 Click Edit, set External Management IP Address, Floating IP Address, Gateway IP
Address, and Subnet Mask for the BMU node, and click Save.
 You need to set Floating IP Address only when the BMU is deployed in two-node cluster
mode.
 Set External Management IP Address and Floating IP Address to those of the Outer_OM
reserved during network design.
 The operation can be performed by only one user at a time.
 Changing the IP address is a major change operation. Do not perform other operations before
the change takes effect, which may take 5 to 15 minutes.
----End
Configuring an External Management Plane for a Lower-Level Domain
Step 1 Log in to the CSP OM portal of the lower-level domain as the admin user.
Application Name > Network > External Management Network Plane Configuration.
Step 3 Click Edit, set External Management IP Address, Floating IP Address, Gateway IP
Address, and Subnet Mask for the BMU node, and click Save.
 You need to set Floating IP Address only when the BMU is deployed in two-node cluster
mode.
 Set External Management IP Address and Floating IP Address to those of the Outer_OM
reserved during network design.
 The operation can be performed by only one user at a time.
 Changing the IP address is a major change operation. Do not perform other operations before
the change takes effect, which may take 5 to 15 minutes.
Step 4 Configure a static route for surveillance domain cascading.

1. Click Add Route.
2. In the pop-up dialog box, configure routing for the network segment where the
external management IP address is located. Table 4-1 describes related parameters.
Table 4-1 Parameters for adding a route
Destination Destination subnet IP address of the external management plane

Subnet IP Address in the upper-level domain, for example, 192.168.0.0.
Currently, only network routes are supported. That is, you must
enter a network segment instead of a specific IP address for
routing.
Destination Destination subnet mask of the external management plane in the

Subnet Mask upper-level domain, for example, 255.255.0.0.
Gateway IP Next-hop network address of the route. Generally, it is the

Address gateway IP address of the current network.
Network Port Network port used for network communication. The default value
is eth4 and cannot be changed.
3. Click Add Route. In the dialog box that is displayed, click Yes.
A maximum of 128 routes can be added.
----End
4.2.1.2 Registering a Lower-Level Domain with the Upper-Level Domain
A lower-level domain is CloudIVS 3000 or IVS3800 with a version of V100R019C20 or later.
Step 1 Go to https://IP address:31943 and log in to the CSP OM portal of a lower-level

domain as the admin user.
Application Name > Connection > Surveillance Domain Cascading.
Step 3 Select Surveillance Domain.

Step 4 Set the IP address and port number of the platform in the upper-level domain. Table
4-2 describes related parameters.
IP Address  When the upper-level domain is the CloudVCN, enter the

external management floating IP address of the OM VM in the
upper-level domain.
To obtain the floating IP address, log in to the OMU portal of
the master server in the upper-level domain and choose System
Management > Local Domain Config > Network Config > Float
Ip Info.
 If the upper-level domain is the CloudIVS 3000 or IVS3800 and
the external service network is used for upper- and lower-level
domain connection, enter the external service IP address of the
BMU node in the upper-level domain. If the BMU is deployed in
two-node cluster mode, enter the external service floating IP
address of the BMU.
To obtain the IP address, log in to the CSP OM portal of the
upper-level domain as the admin user and choose Application
Configuration > Configuration Management > Configuration >
Application Name > Two-Node Cluster. Check the external
service IP address if the upper-level domain is V100R019C20 or
the external network address if the upper-level domain is
V100R019C30.
 If the upper-level domain is the CloudIVS 3000 or IVS3800 and
the external management network is used for upper- and
lower-level domain connection, enter the external management
IP address of the BMU node in the upper-level domain. If the
BMU is deployed in two-node cluster mode, enter the external
management floating IP address of the BMU node.
To obtain the IP address, log in to the CSP OM portal of the
upper-level domain as the admin user first. For upper-level
domain V100R019C10, choose Application Configuration >
Configuration Management > Configuration > Application
Name > Two-Node Cluster and view the external network IP
address of the BMU node. For upper-level domain
V100R019C20 or later, choose Application Configuration >
Configuration Management > Configuration > Application
Name > Network > External Management Network Plane
Configuration and view the external management IP address or
the floating IP address of the BMU node.
 If the upper-level domain is VCN3010 or VCN3020
V100R003C10SPC260, enter the IP address of the master server
in the upper-level domain. If the master server in the upper-
level domain is a VMU two-node cluster, enter the floating IP
address of the two-node cluster.
If NAT is configured, enter the post-NAT IP address.
Port  If NAT is not configured between the upper- and lower-level

domains, enter 9935.
 If NAT is configured between the upper- and lower-level
domains, enter the port number translated from port 9935.
Compatibility Select Compatible mode only when the upper-level domain is

mode CloudVCN.
Step 5 Click Apply to complete the connection between the upper- and lower-level domains.
Verification
If the upper-level domain is the CloudVCN named Domain-0001 and the lower-level
domain name is IVS System, perform the following steps to verify the result:
1. Log in to the OMU portal of the master server in the upper-level domain as the
admin user.
2. Choose System Management > Domain Node Config. If the added lower-level
domain is listed under System Domains, the upper- and lower-level domains are
successfully connected.
Figure 4-1 Querying lower-level domain information
On the OMU portal of the master server in the upper-level domain, you can view only the name
of the lower-level domain. To view details about the lower-level domain, log in to its CSP OM
portal.
If the upper-level domain is the CloudIVS 3000 or IVS3800 named Domain-0001 and the
lower-level domain name is IVS System, perform the following steps to verify the result:
3. Log in to the CSP OM portal of the upper-level domain as the admin user.
5. Click Surveillance Domain. If the added lower-level domain is listed under Lower-
Level Domains, the upper- and lower-level domains are successfully connected.

Step 6 If the upper-level domain is the VCN3010 or VCN3020 named Domain-0001 and the
lower-level domain name is IVS System, perform the following steps to verify the
result:
1. Log in to the OMU portal of the master server in the upper-level domain as the
admin user.
2. Choose System Management > Local Domain. If the added lower-level domain is
listed under System Domains, the upper- and lower-level domains are successfully
connected.
On the OMU portal of the master server in the upper-level domain, you can view only the name
of the lower-level domain. To view details about the lower-level domain, log in to its CSP OM
portal.
----End
4.2.1.3 Subscribing to Alarms in a Lower-Level Domain

After the connection between upper- and lower-level domains, a user of the upper-level
domain can see alarms in the lower-level domain. Different roles have different
permissions. Table 4-3 describes roles.
Table 4-3 Permissions for viewing alarms of the lower-level domain
User Role of the Can view alarms in the lower-level Require Manual
Upper-Level domain. Subscription to Service
Domain Alarms
System Can directly view alarms (including x

administrator service alarms and device alarms) of
the lower-level domain.
Common Can directly view device alarms √

operator (such as camera go-online and go-
offline) of the lower-level domain.
Senior operator √
If a common operator or a senior
operator needs to view service
alarms (such as motion detection
User Role of the Can view alarms in the lower-level Require Manual
Upper-Level domain. Subscription to Service
Domain Alarms
alarms) of the lower-level domain,
refer to this section to subscribe to
the alarms for the operator.
User-defined role If external domain management x

(with external permissions are assigned to the role,
domain a user with this role can directly
management view alarms (including service
permissions) alarms and device alarms) of the
lower-level domain or external
domain.
Step 2 Log in to the iClient of the upper-level domain as the admin user.
Step 3 Choose System Management > User Management > User Maintenance.
Step 4 In User Group List on the left, select the user group to which the upper-level domain
user who wants to subscribe to alarms belongs.
Step 5 On the far right side of the target user row, click and select Alarm Subscription.
Figure 4-4 Alarm subscription
Step 6 Perform the following steps to subscribe to alarms in the lower-level domain.
Figure 4-5 Subscribing to alarms in a lower-level domain
1. Select devices for which you want to subscribe to alarms in the lower-level domain.
You can select devices from Camera, Alarm Source, and External Alarm System.
2. Select By alarm type or By alarm severity.
3. Subscribe to alarms.
− If you select By alarm type, check alarm items as needed.
− If you select By alarm severity, configure alarm severity as needed.
4. Click Save.
----End
4.2.1.4 Verifying Domain Services

1. Log in to the iClient of the upper-level domain as the admin user.
2. Choose Basic Operations > Live.
3. Double-click an online camera in a lower-level domain from the camera list or drag
the online camera to a video pane.
If the live video can be properly played, the upper- and lower-level domain connection is
successfully configured.
4.2.2 Connecting to External Domains

4.2.2.1 Configuring the Connection Protocol for the Local Domain
Step 1 Log in to the CSP OM portal of the local domain as the admin user.
Application Name > Connection.
Step 3 Click the External Domain tab.

Step 4 Under Local Domain Connection Info, enter the local domain code in the text box of
the specific protocol and click Apply.
----End
4.2.2.2 Configuring External Domain Connection

Many protocols can be used for external domain connection, including GB/T 28181-2011,
GB/T 28181-2016, GB 35114, DB33, and Milestone. This experiment uses GB/T 28181 as an
example.
Before connecting two domains with each other, configure the local domain code and
external domain information on platforms in both domains and provide the local domain
code to the peer domain.
Configuring External Domain Connection Information in the Local Domain
Step 3 On the External Domain tab, click New to add an external domain.
Step 4 Set Connection Protocol to T28181-2011 or T28181-2016.
Table 3-4 and Table 3-5 describes these parameters.
Table 4-4 Basic configuration
Parameter Description Settings
External Name of an external You are advised to set this parameter based
Domain Name domain. on the external domain type or usage.
Connection The options are as Select T28181-2011 or T28181-2016.

Protocol follows: The GB 35114 protocol is applicable only to
 Milestone the Chinese mainland.
 T28181-2011
 T28181-2016
 DB33
 GB35114
Code Connection code of Enter the connection code of an external

an external domain. domain.
Password Inter-domain Enter the user password agreed between the

connection password. local domain and an external domain. The
passwords specified in the local domain and
Confirm The value must be external domain must be the same.
Password the same as that of
Password.
Register with Indicates whether to  To allow external domain users to view

External allow the local cameras shared by the local domain, select
Domain domain to register Yes.
with an external  To disallow external domain users to view
domain. cameras shared by the local domain, select
No.
 If the local domain functions as an upper-level

external domain and does not need to register
with a lower-level external domain, select No.
 If NAT is configured between the local domain
(IVS platform) and an external domain, the local
domain can be used only as the upper-level
domain, that is, the IVS platform does not need
to register with the external domain. In this case,
select No.
External IP address or domain If the external domain is the IVS3800, enter

Domain name of an external the external service IP address of the VCNAPI
IP/Foreign domain. node. If the VCNAPI is deployed in two-node
Domain cluster mode, enter the external service
floating IP address of the VCNAPI node.
 To obtain the IP address, log in to the CSP
OM portal of the external domain as the
admin user first. If the version of the
external domain is V100R019C10, choose
Application Configuration > Configuration
Management > Configuration >
Application Name > Two-Node Cluster and
view the external network address of the
VCNAPI node. If the version of the external
domain is V100R019C20, choose
view the external service address of the
VCNAPI node. If the version of the external
domain is V100R019C30, choose
view the external network address of the
VCNAPI node.

 If the external domain is the CloudVCN,
enter the external service floating IP
address of the PCG VM.
To obtain the IP address, log in to the
OMU portal of the external domain as the
admin user and choose System
Management > Local Domain Config >
Network Config > Float Ip Info.
 If the external domain is the VCN3010,
VCN3020, VCN510, VCN520, or VCN540,
enter the IP address of the master server.
If the master server is deployed in two-
node cluster mode, enter the floating IP
address of the master server.
 If the external domain is a Milestone
platform cluster, select the domain name-
based connection mode and enter the
Milestone domain name.
If NAT is configured for an external domain, the

preceding IP addresses must be replaced with the
post-NAT IP addresses.
Port Port number of an Enter the actual port number.

external domain. If the external domain is also an IVS platform,
the default port number is 5061. If NAT is
configured for the external domain, enter the
post-NAT port number.
Extended To enable the system Table 3-6 describes the function of each bit.
Configuration to be compatible
with third-party
platforms, set the The bits are numbered from left to right. For
required bit to 1. example, the seventh bit is the seventh bit starting
from the left.
Is IVS Platform Indicates whether the  If the connected platform is an IVS

platform is an IVS platform, select Yes.
platform.  To connect to another vendor's platform,
select No.
Authentication Authentication Use the default value.

Certificate certificate that is
used for
authentication by the
CA server when the

GB 35114 protocol is
used.
Encryption Encryption certificate Use the default value.

Certificate that is used for
authentication by the
CA server when the
GB 35114 protocol is
used.
Table 4-5 Advanced settings
Domain PTZ control priority assigned to an Enter a value ranging from 1 to

Priority external domain. When multiple 9.
users attempt to control a PTZ
camera at the same time, the user
with the highest priority can
operate the PTZ camera. The value
ranges from 1 to 32. Value 1
indicates the highest priority, and
value 32 indicates the lowest
priority.
Max. Sessions Maximum number of live video Enter a value ranging from 1 to
viewing channels and video 5000.
playback channels supported by
the external domain.
Devices in Number of devices carried in a Enter a value ranging from 1 to

Single SIP single SIP packet when the local 10.
Packet domain shares devices with an
external domain.
Character Set Character set used for inter- Select the character set agreed
domain connection. The options by both the local domain and an
are as follows: external domain.
UTF-8 The character sets specified in
GB2312 both domains must be the same.
GBK
Stream Type Media stream packaging protocol. The default value is PS.
Register Method for ensuring continuous  To allow the external domain

Periodically connection between the local to continuously connect to
the local domain using

domain and an external domain. registration messages, select
Yes.
 To allow the external domain
to continuously connect to
the local domain using
keepalive messages, select
No.
 If the local domain functions as

an upper-level external domain
and does not need to register
with a lower-level external
domain, select No.
 If NAT is configured between the
local domain (IVS platform) and
an external domain, the local
domain can be used only as the
upper-level domain, that is, the
IVS platform does not need to
register with the external
domain. In this case, select No.
Support Audio Indicates whether an external  If the external domain

domain supports audio functions. supports audio functions, set
this parameter to Yes.
 If the external domain does
not support audio functions,
set this parameter to No.
Differentiate Indicates whether to differentiate  If PU-based recordings are

Recording the storage location of external differentiated from server-
Storage domain recordings during external based recordings for the
Location domain recording search and external domain, set this
playback. parameter to Yes. In this case,
both PU-based and server-
based recordings of the
external domain are obtained
during external domain
recording search and
playback.
 If PU-based recordings are
not differentiated from
server-based recordings for
the external domain, set this
parameter to No. In this case,
only PU-based recordings of
the external domain are

obtained during external
domain recording search and
playback.
Query Indicates whether to query  To query information in the

Directory Level information in external domain external domain directories
by Level directories level by level. level by level, set this
parameter to Yes. In this case,
the system queries
information level by level,
from top to bottom.
 To query information in the
external domain directories
at a time, set this parameter
to No. In this case, the system
queries information in
directories of all levels at a
time.
Auto Switch Indicates whether to automatically  If automatic switching from

SIP to TCP switch from SIP to TCP. SIP to TCP is required, set this
parameter to Yes.
 If automatic switching from
SIP to TCP is not required, set
this parameter to No.
Service Type Type of the IVS recording that an  To allow an external domain
external domain can search for to search only for PU-based
during IVS recording search and recordings, select Device.
playback.  To allow an external domain
to search only for server-
based recordings, select
Server.
 To allow an external domain
to search for both PU-based
recordings and server-based
recordings, select All.
Alarm Indicates the mode for reporting If domain A is an IVS local

Reporting alarms generated by local domain domain platform and domain B
Mode devices. is a third-party external domain
platform, the alarm reporting
modes are described as follows:
 Notify after subscription:
External domain B subscribes
to alarms of devices in local

domain A. When a device in
local domain A generates an
alarm, local domain A reports
the alarm information to
external domain B.
 Always notify: External
domain B does not need to
subscribe to alarms of devices
in local domain A. When a
device in local domain A
generates an alarm, local
domain A automatically
reports the alarm information
to external domain B.
Support Indicates whether the connection  Yes: In a connection code,

Letters in code shared by the IVS platform to characters 1–6 and 11–13
Connection an external domain can contain must be digits, and the other
Code letters when the external domain characters can be digits or
connects to the IVS platform using letters.
GB/T 28181-2011 or GB/T 28181-  No: A connection code can
2016. contain only digits.
Enable NAT Indicates whether to enable NAT. The NAT function is disabled by
When an external domain default. You need to enable NAT
connects to the IVS platform only when the local domain (IVS
through the GB/T 28181-2011 or platform) is on an intranet that
GB/T 28181-2016 protocol, you is on a different network from
need to set this parameter. the external domain.
NetPosa Indicates whether an external  Yes: The 20-bit connection

Platform domain is a NetPosa platform. code of devices shared by the
When an external domain IVS platform to an external
connects to the IVS platform domain complies with the
through GB/T 28181-2011 or GB/T following encoding rule: first
28181-2016 and Is IVS Platform is 17 bits of the local domain
set to No, you need to set this code + 3-bit random number.
parameter.  No: The 20-bit connection
code of the device shared by
the IVS platform with the
external domain complies
with the GB/T 28181-2011 or
GB/T 28181-2016 encoding
rule.
Table 4-6 Bit description
Bit Description
1 When Service Type is set to All and the INVITE TO header field sent by the
third-party platform is a device code:
 If the first bit is set to 1, the IVS platform queries the PU-based recordings
when receiving a recording playback or download request from the third-
party platform.
− If the query result is not empty, the PU-based recordings are played
back or downloaded.
− If the query result is empty, the server-based recordings are played back
or downloaded.
 If the first bit is set to 0, the IVS platform directly plays back or downloads
PU-based recordings when receiving a recording playback or download
request from the third-party platform. If no PU-based recording is
available, the playback or download fails.
4 When the IVS platform requests live streams from a third-party platform and
the third-party platform sends an INVITE response that does not contain the
media decoding format:
 If this bit is set to 1, the IVS platform plays live video from the third-party
platform in H.265 format.
 If this bit is set to 0, the IVS platform plays live video from the third-party
platform in H.264 format.
5 When the IVS platform sends a control signaling authentication message to a

third-party platform after the IVS platform is successfully connected to the
third-party platform through the GB 35114 protocol:
 If this bit is set to 1, the nonce and algorithm parameters under Note in the
control signaling authentication message header are separated by a
comma (,).
 If this bit is set to 0, the nonce and algorithm parameters under Note in the
control signaling authentication message header are separated by a space.
6 When the IVS successfully registers with the third-party platform using GB/T
28181, the IVS sends device catalog information that contains the PTZType
field to the third-party platform.
 If this bit is set to 1 and the Extension Type parameter of the camera has a
value, the PTZType field is set to the type code corresponding to Extension
Type.
 If this bit is set to 1 and the Extension Type parameter of the camera does
not have a value, the PTZType field is set to the type code corresponding to
Camera Type.
Bit Description
 If this bit is set to 0, the PTZType field is set to the type code corresponding
to Camera Type regardless of whether the Extension Type parameter has a
value.
7 When the IVS successfully registers with the third-party platform using GB/T
28181, the IVS sends device catalog information that contains the ParentID
field to the third-party platform.
 For a device that belongs to a specific device group:
− If this bit is set to 1, the ParentID field contains both the IVS platform ID
and device group ID, which are separated by a slash (/). That is, the
value format of the ParentID field is IVS platform ID/Device group ID.
− If this bit is set to 0, the value of the ParentID field is in the format
Device group ID.
 If a device is directly subordinate to the IVS platform root directory, the
value of the ParentID field is in the format IVS platform ID, regardless of
the value of the seventh bit.
8 When a third-party platform requests video streams from the IVS platform (or
the IVS platform requests video streams from a third-party platform), and the
camera uses the TCP protocol:
 If this bit is set to 1, fields b=RS:0 and b=RR:0 are not included in the SDP
stream transmission message on the IVS platform.
 If this bit is set to 0, fields b=RS:0 and b=RR:0 are included in the SDP
stream transmission message on the IVS platform.
9 When the IVS platform requests live streams or recordings from a third-party
platform, both the signaling and the video streams that the third-party
platform returns to the IVS platform contain video encoding format
information:
 If this bit is set to 1, the IVS platform plays live video or recordings from
the third-party platform in the video encoding format of these video
streams.
 If this bit is set to 0:
If the video encoding format carried in the signaling is H.265, the IVS
platform plays the requested live video or recordings in the H.265 format. If
the video encoding format carried in the signaling is H.264, the live video
or recordings playing will fail.
 If the video encoding format carried in the signaling is H.264, the IVS
platform plays the requested live video or recordings in the encoding
format carried in video streams.
10 When the IVS platform requests media streams from a third-party platform:
 If this bit is set to 1, the default transmission protocol used to request
media streams from external devices is RTP over TCP Passive.
Bit Description
 If this bit is set to 0, the default transmission protocol used to request
media streams from external devices is RTP over UDP.
11 When the IVS platform successfully registers with a third-party platform using
GB/T 28181, the IVS sends device catalog information to the third-party
platform.
 If this bit is set to 1, all directory items and device items excluding the
administrative division catalog items must contain the CivilCode field, and
the value of CivilCode is the code of the actual parent catalog item.
 If this bit is set to 0, device catalog information is sent based on GB/T
28181.
2–3, Reserved.
12–32
Step 5 Click Save.

Configuring Local Domain Information in an External Domain
In an external domain, configure the local domain based on your configuration information
in Configuring the Connection Protocol for the Local Domain. Ensure that the configuration
options required to connect the local domain and the external domain are consistent.
----End
4.2.2.3 Configuring Device Sharing Between Domains

After two domains are connected to each other, the local domain can share devices with
the peer domain. For example, the local domain can share cameras with the peer domain
so that users in the peer domain can view live and recorded video from the cameras.
This section describes how to share devices on the IVS platform with an external domain.
How to share devices from an external domain with the IVS platform is subject to the
actual external domain platform.
Step 1 (Optional) Enable cloned device sharing. To share cloned cameras in the local
domain, perform the following steps:
A cloned camera can be shared only with an external domain connected through GB/T 28181-
2016. When sharing a cloned camera, you can view backup recordings but not live video.
1. Log in to the CSP OM portal as the admin user.
Application Name > Unified Configuration > Surveillance Platform.
3. Select the VCNSvcMgrService service.
4. Set ShareShadowDevSupport to true.
Figure 4-6 Setting ShareShadowDevSupport

Step 3 Choose System Management > Device Sharing > Share with External Domain.
Step 4 Share the devices in the local domain with the external domain.
Figure 4-7 Sharing devices with an external domain
1. Select the devices to be shared with the external domain.

2. Select the external domain.
3. Click Share Device. The shared devices are displayed in the device list on the right.
Step 5 (Optional) If the devices shared with the external domain still need to be shared with
other external domains, select the devices on the shared device list on the right, click
Share with Other Domains, select other external domains, and click OK.
Step 6 (Optional) Change the connection codes of shared devices.

 Changing a single connection code: On the shared device list on the right, double-
click the value of Connection Code of a shared device and change the connection
code.
 Changing connection codes in batches: Select the shared devices whose connection
codes are to be changed and click Export to export the shared device information as
a file to the local computer. Open the file, change the device connection codes in the
file, save the file, and click Import to import the file. The connection codes of the
shared devices are changed in batches.
You can change the connection codes of shared devices in batches only when external domains
are connected using the GB/T 28181-2011 or GB/T 28181-2016 protocol. If external domains are
connected using other protocols, the Import and Export buttons are unavailable.
----End
4.2.2.4 Configuring Resource Synchronization

Step 3 Click the External Domain tab.

Step 4 Select an external domain from the external domain list and click Synchronization.
----End
4.2.2.5 Subscribing to External Domain Alarms

When the GB/T 28181-2011, GB/T 28181-2016, or GB 35114 protocol is used to connect to
an external domain:
 If Alarm Reporting Mode is set to Notify after subscription, you need to perform the
task in this section to subscribe to alarms of external domain devices so that the
local domain can receive alarms generated by the external domain devices.
 If Alarm Reporting Mode is set to Always notify, the local domain can receive alarms
generated by the external domain devices without alarm subscription. In this case,
skip this task.
Step 1 Log in to the local domain iClient as the admin user.

Step 2 Choose System Management > Alarm Management > Inter-Domain Subscription.
Step 3 Click the connected external domain node to expand the tree of devices shared from
the external domain to the local domain.
Step 4 Select the external domain or devices to subscribe to and click Edit in the upper right
corner.
Step 5 In the dialog box that is displayed, set event subscription parameters and click OK.
Table 4-7 Parameters for editing event subscription
Subscribed Time range for event subscription.
Alarm Type The options are as follows:

 All
 Device
 Video
Start Severity Severity range of alarms to be subscribed.
End Severity The options are as follows:

 All
 Level-1
 Level-2
 Level-3
 Level-4
Step 6 Click Subscribe in the upper right corner. Inter-domain alarm subscription is
completed.
----End
4.2.2.6 Verifying Domain Services

You can perform a variety of operations on external domain devices, such as checking
devices and viewing live or record video from the devices. However, you cannot modify
external domain device parameters.
Prerequisites
The external domain forwarding function has been enabled for the MPUT node in the
external domain. The configuration is as follows:
Step 1 Log in to the CSP OM portal of the master server in domain A (provincial police
department) as the admin user.
Application Name > Local Domain > Forwarding.
Step 3 Under Node, select nodes for which you want to configure external domain
forwarding and click External Domain Forwarding next to Enable.
Only the MPUT node supports the forwarding function.
----End
Verifying Domain Services
Step 1 Log in to the iClient of the local domain as the admin user.
Step 2 Choose Basic Operations > Live.

Step 3 Double-click an online camera in an external domain or drag it to a video pane. If
live video from that camera is played, the external domain service is normal.
----End
5 Backup Management
5.1 Introduction
You can back up live video, historical recordings, or images on the server to the backup
domain as required to improve video data reliability. This section describes how to back up
video and images.
5.1.2 Objectives
 Understand how to back up video.
 Understand how to back up images.

5.2.1 Video Backup
Table 5-1 lists the types and application scenarios of video backup.
Table 5-1 Typical application scenarios
Backup Type Application Scenario
Live video Scheduled Some cameras monitor key areas, and the
backup backup surveillance video is important. Users can
configure a backup plan to automatically back up
live video within the backup task execution time
to other servers.
Manual backup When emergencies occur in the surveillance area

during live video viewing, users can manually back
up the live video to other servers, reducing the
probability of video loss.
Recording Scheduled If the available storage space of a server is

backup backup of insufficient and users do not want to delete the
server-based recordings stored on the server, they can
recordings configure a backup plan to automatically back up
historical recordings from the server to other
Backup Type Application Scenario

servers.
Manual backup When users find a valuable video clip during

of server-based playback, they can manually back up this video
recordings clip to other servers.
Scheduled If the available storage space of PUs is insufficient

backup of PU- and users do not want to delete the recordings
based recordings stored on the PUs, they can configure a backup
plan to automatically back up historical
recordings from PUs to other servers.
Manual backup When users find a valuable video clip during

of PU-based playback, they can manually back up this video
recordings clip to other servers.
5.2.1.1 Camera Clone

Before using the backup function, you need to clone cameras whose data needs to be
backed up to the target server. The cloned cameras are called shadow cameras. Shadow
cameras are displayed on the device list on the Device Management, Backup Management,
and Playback tab pages of the iClient of the master server in the backup domain.
Additionally, for each camera in the local domain, its shadow camera is named in the
format Original camera name_clone. A shadow camera does not support functions like
viewing live video other than backing up data and viewing backed up data.
5.2.1.1.1 Cloning a Camera in a Local Domain
Step 2 Choose System Management > Device Management > Main Devices.
Step 3 In the device tree on the left, select the node to which the camera to be cloned
belongs.
Figure 5-1 Selecting a node
Step 4 On the device list on the right, select the camera to be cloned and click Clone.
Figure 5-2 Cloning a camera
Step 5 Select an access domain and mount server.

Figure 5-3 Setting an access domain and mount server
Step 6 Click OK. The camera is cloned.

----End
Verification
Step 1 On the iClient home page, choose System Management > Device Management >
Main Devices.
Step 2 In the device tree on the left, select the target server.
Step 3 Check whether the shadow camera is displayed on the device list of the target server.
----End
5.2.1.1.2 Cloning a Camera in an External Domain

Step 2 Choose System Management > Device Management > External Domain Devices.
Step 3 In the device tree on the left, select the external domain node to which the camera
to be cloned belongs.
Step 4 On the device list on the right, select the camera to be cloned in the external domain
and click Clone.
Figure 5-4 Cloning a camera
Step 5 Select an access domain and mount server.

Figure 5-5 Setting an access domain and mount server
Step 6 Click OK. The camera is cloned.

----End
Verification
Step 1 On the iClient home page, choose System Management > Device Management >
Main Devices.
Step 2 In the device tree on the left, select the target server.
Step 3 Check whether the shadow camera is displayed on the device list of the target server.
----End
5.2.1.2 Setting Backup Parameters

Step 2 Choose System Management > Backup Management.
Step 3 Click Backup Settings.
Step 4 In the device tree on the left, select a shadow camera.
Step 5 Set backup parameters. Table 5-2 describes the parameters.
Table 5-2 Setting backup parameters
Recording Duration for storing backup recordings on the target server. The
Backup default value is 0, indicating that the system overwrites the earliest
Storage recordings when the storage space is full.
(days) In live network projects, this parameter is usually set to 7 or 30 days.
You can set this parameter based on the actual situation (for
example, disk capacity).
Server Backup Rate for backing up server-based recordings. The system can back up
Download recordings at 1x, 2x, 4x, or 8x the camera bit rate. This parameter is
Rate valid only for historical recordings stored on the backup server. The
live video backup function backs up live video of the current camera.
Therefore, the backup download rate is the transmission bit rate of
the current camera.
The recommended configurations are as follows:
 During off-peak hours, for example, at night, the backup rate can
be set to a higher value, for example, 4x or 8x.
 During peak hours, for example, at daytime, the backup rate can
be set to a smaller value, for example, 1x or 2x, to reduce the
recording backup bandwidth between the source server and the
target server and impact on the existing services.
PU Backup Rate for backing up PU-based recordings. The system can back up
Download recordings at 1x, 2x, 4x, or 8x the camera bit rate. This parameter is
Rate valid only for historical recordings stored on cameras.
The recommended configurations are as follows:
 During off-peak hours, for example, at night, the backup rate can
be set to a higher value, for example, 4x or 8x.
 During peak hours, for example, at daytime, the backup rate can
be set to a lower value, for example, 1x or 2x, to reduce the
recording backup download bandwidth and impact on the existing
services.
Step 6 Click Save.
To copy the backup parameter settings of the current shadow camera to other shadow cameras,
click Apply to Others.
----End
5.2.1.3 Live Video Backup

5.2.1.3.1 Configuring Scheduled Live Video Backup
If backup is interrupted on the target server due to a network fault, live video from
cameras on the source server cannot be backed up during network interruption.

Step 2 Choose System Management > Backup Management > Server-based Backup.
Step 3 Create a live video backup plan.
Figure 5-6 Configuring a live video backup plan
1. In the device tree on the left, select a shadow camera.

2. Set Backup Type to Live video and select the default value All for Backup Content.
3. In the Execution Time area, select Enable plan, set the backup execution frequency to
Daily or Weekly. Move your cursor to the slider under the timeline, press and hold
the left mouse button and drag the slider rightward to set a time period of backup
execution.
4. Click Save.
Step 4 (Optional) To copy the backup plan to multiple cameras in batches, click Apply to
Others, select the shadow cameras to which you want to copy the backup plan, and
click OK.
----End
Verification
Step 1 On the iClient home page, choose Basic Operations > Playback.
Step 2 Verify that the time segment of the backup recordings on the target server is the
same as that of the recordings to back up on the source server.
Figure 5-7 Verifying the backup result
----End
5.2.1.3.2 Configuring Manual Live Video Backup
If backup is interrupted on the target server due to a network fault, live video from
cameras on the source server cannot be backed up during network interruption.

Step 2 (Optional) Configure the video duration for manual live video backup.
1. Choose System Management > Personal Settings.

2. In the Recording and Download Settings area, set Default Clip Length.
3. Click Save.
Step 3 On the iClient home page, choose Basic Operations > Live.
Step 4 Right-click the camera for which you want to back up the live video and select
Manual Backup.
Figure 5-8 Manual backup
Step 5 On the camera list that is displayed, select a shadow camera and click OK. The
manual live video backup setting is complete.
----End
Verification
----End
Pausing Live Video Backup
Step 1 On the iClient home page, choose System Management > Backup Management >
Manual Recording Backup.

Step 3 On the All tab, select the backup tasks that you want to pause and click Paused.
----End
5.2.1.4 Video Recording Backup

5.2.1.4.1 Configuring Scheduled Backup of Server Recordings
Step 2 Choose System Management > Backup Management > Server-based Backup.
Step 3 Set up a server recording backup plan as described in the following figure:
Figure 5-10 Configuring a server recording backup plan

2. Set Backup Type to Recording and set Backup Content according to the actual
requirements.
execution.
4. In the Recording Segment area, set the start date for backing up server recordings
and drag the slider on the timeline to set the backup time segment.
The server recording backup function supports recording backup at 1x, 2x, 4x, or 8x the camera
bit rate. To ensure backup integrity, it is recommended that the recording duration to back up do
not exceed the multiple of the backup execution time segment. For example, if recordings are
backed up at 2x and the backup execution time segment is 30 minutes, the recording duration to
back up cannot exceed 1 hour.
5. Click Save.
Backup Type Set this parameter to Recording.
Backup Type of the historical server-based recordings to back up. This

Content parameter is mandatory when Backup Type is set to Recording.
 All: includes scheduled recordings, manual recordings, and alarm-
triggered recordings stored on the source server.
 Alarm-triggered recording: only alarm-triggered recordings.
Execution Time period during which backup tasks are scheduled to happen on
Time the target server.
For example, from 17:00 to 17:30 every day, the target server backs
up historical recordings stored on the source server.
Recording A specific time segment of the recorded video that needs to be backed
Segment up. This parameter is mandatory when Backup Type is set to
Recording.
For example, back up recordings in the time segment from 16:00 to
17:00 every day from the source server to the target server.
Start Date Start date of the historical server-based recordings to back up. This
parameter is mandatory when Backup Type is set to Recording.
For example, back up recordings generated on and after September
22, 2019 from the source server to the target server.
Apply to Copies the backup plan of the current shadow camera to other
Others shadow cameras.
Figure 5-11 Parameter description
----End
Verification
If backup is interrupted due to a network fault when the target server is executing backup, the
target server will continue to back up recordings that are not backed up during network
interruption after the network is recovered. For example, based on the backup plan configured in
3, from 17:00 to 17:30 every day, the target server backs up historical recordings of 16:00 to
17:00 every day from the source server. If the network where the target server resides is faulty at
17:00 on Monday, the backup is interrupted. From 17:00 to 17:30 on the day when the network is
recovered or the next day, the target server continues to back up historical recordings of 16:00 to
17:00 on Monday from the source server.
----End
5.2.1.4.2 Configuring Manual Backup of Server-based Recordings

Step 2 Choose Basic Operations > Playback.
Step 3 Configure manual backup of server-based recordings, as shown in the following
figure.
Figure 5-13 Setting manual backup of server-based recordings
1. Select a camera whose historical recordings are to be backed up in Cameras.

2. Set the recording backup time segment and recording type, click Advanced, and set
Storage Location to Server.
3. Click Search.
4. On the right of the recording segment found, click .
5. Drag the slider on the timeline of the recording found to select a recording segment
to back up.
6. In the pop-up box, click .
7. In the Manual Backup dialog box that is displayed, select the shadow camera and set
the backup type. Table 5-4 describes the parameters.
Figure 5-14 Selecting the backup type
Now Backs up selected recordings immediately. If the backup bandwidth

currently available is sufficient, click Now.
Later If this option is selected, you need to set Execution Time as needed. If the
backup bandwidth currently available is insufficient, click Later and wait
until you have enough bandwidth.
8. Click OK.
----End
Verification
interruption after the network is recovered.
----End
5.2.1.4.3 Configuring Scheduled Backup of PU-based Recordings

Prerequisites
Cameras support the PU-based recording function, and historical recordings have been
stored on PUs.
Procedure

Step 2 Choose System Management > Backup Management > PU-based Backup.
Step 3 Create a PU-based recording backup plan.
Figure 5-16 Configuring a PU recording backup plan

2. Set Backup Stream.
execution.
4. In the Recording Segment area, set the start date for backing up PU-based
recordings and drag the slider on the timeline to set the backup time segment.
The PU recording backup function supports recording backup at 1x, 2x, 4x, or 8x the camera bit
rate. To ensure backup integrity, it is recommended that the recording duration to back up do not
exceed the multiple of the backup execution time segment. For example, if recordings are backed
up at 2x and the backup execution time segment is 30 minutes, the recording duration to back
up cannot exceed 1 hour.
5. Click Save.
Table 5-5 describes the parameters of a PU-based recording backup plan.
Backup Recordings on the PU to be backed up.

Content The options are as follows:
All: includes scheduled recordings and manual recordings stored on
the PU.
Backup Stream used to back up PU-based recordings.

Stream
Execution Time segment for the target server to execute the backup.
Time For example, from 17:00 to 17:30 every day, the target server backs up
PU-based recordings stored on a certain camera on the source server.
Recording PU-based recordings in a time period from a camera that remains to

Segment be backed up.
For example, back up PU-based recordings from a camera on the
source server in the time segment from 16:00 to 17:00 every day to
the target server.
Start Date Start date of PU-based recordings to back up.

For example, back up recordings generated on and after September
22, 2019 from a camera on the source server to the target server.
Apply to Copies the backup plan of the current shadow camera to other
Others shadow cameras.
----End
Verification
interruption after the network is recovered. For example, based on the backup plan configured in
step 3, from 17:00 to 17:30 every day, the target server backs up historical recordings of 16:00 to
17:00 every day from the camera under the source server. If the network where the target server
resides is faulty at 17:00 on Monday, the backup is interrupted. From 17:00 to 17:30 on the day
when the network is recovered or the next day, the target server continues to back up PU-based
recordings of 16:00 to 17:00 on Monday from the camera on the source server.
----End
5.2.1.4.4 Configuring Manual Backup of PU-based Recordings

Cameras support the PU-based recording function, and historical recordings have been
stored on PUs.

Step 2 Choose Basic Operations > Playback.
Step 3 Configure the manual backup of PU-based recording, as shown in the following
figure.
Figure 5-19 Manually backing up PU-based recordings
1. In Cameras, select a camera whose historical recordings are to be backed up.

2. Set the recording backup time segment and recording type, click Advanced, and set
Storage Location to PU.
3. Click Search.
4. On the right of the recording segment found, click .
5. Drag the slider on the timeline of the recording found to select a recording segment
to back up.
6. In the pop-up box, click .
7. In the Manual Backup dialog box that is displayed, select the shadow camera and set
the backup type. Table 5-6 describes the parameters.
Figure 5-20 Selecting the backup type
Now Backs up selected recordings immediately. If the backup bandwidth

currently available is sufficient, click Now.
Later If this option is selected, you need to set Execution Time as needed. If the
backup bandwidth currently available is insufficient, click Later and wait
until you have enough bandwidth.
8. Click OK.
----End
Verification
interruption after the network is recovered.
----End
5.2.2 Image Backup

To meet the requirements of remote backup, users can back up images from one server to
other servers. For some important surveillance sites, users can store the images on both
the local server and other servers.
There are some configuration restrictions:
 Only the MPUR supports the backup function.
 If cameras are connected to a local domain, images can be backed up to other
servers in the local domain, domains at the same level, and domains at higher levels.
Table 5-7 describes different image backup types.
Table 5-7 Image backup
Backup Type Description
Live image Images captured by checkpoint cameras on the source server are
backup immediately stored on the destination server. The real-time backup
policy is full-process backup.
Types of data to be backed up:
 Full image: full images (panorama) captured by checkpoint
cameras.

 Partial image: partial images captured by checkpoint cameras.
 All: all captured images and structured data stored on the source
server. Structured data refers to the attribute data such as the
license plate, vehicle color, and vehicle type generated after the
camera analyzes the captured images.
Historical Images that have been stored on the source server are backed up to
backup the destination server.
Types of data to be backed up:
cameras.
 Partial image: partial images captured by checkpoint cameras.
 All: all captured images and structured data stored on the source
server. Structured data refers to the attribute data such as the
license plate, vehicle color, and vehicle type generated after the
camera analyzes the captured images.
5.2.2.1 Image Backup Configuration on the Current Platform

5.2.2.1.1 Cloning a Camera
For details on how to clone a camera, see section 5.2.1.1.1 "Cloning a Camera in a Local
Domain."
5.2.2.1.2 Setting Configuration Parameters
Step 2 Choose System Management > Backup Management.
Step 3 Click Backup Settings.
Step 5 Set backup parameters. Table 5-8 describes the parameters.
Table 5-8 Setting backup parameters
Image Backup Download Duration for storing backup images on the target
Rate server.
Step 6 Click Save.
To copy the backup parameter settings of the current shadow camera to other shadow cameras,
click Apply to Others.
----End
5.2.2.1.3 Configuring Backup Plans

Step 2 Choose System Management > Backup Management > Image Backup.
Create an image backup plan.
 Configure a historical image backup plan.
Figure 5-22 Configuring a historical image backup plan

2. Set Backup Type to Historical and set Backup Content based on the site
requirements.
execution.
4. In the Image Backup Period area, set the start date for backing up images and drag
the slider on the timeline to set the backup time segment.
5. Click Save.
Backup Type Click Historical.
Backup Content The options are as follows:

 All: all captured images and structured data stored on the
source server.
cameras.
 Partial image: face images or license plate images captured
by checkpoint cameras.
Execution Time Time period during which backup tasks are scheduled to
happen on the target server.
For example, from 17:00 to 17:30 every day, the target server
backs up historical recordings stored on the source server.
Image Backup Period Image backup time segment. Images that are captured by
checkpoint cameras in this time segment will be backed up
from the source server, as shown below. This parameter is
mandatory if Backup mode is set to Historical.
For example, back up checkpoint images in the time segment
from 16:00 to 17:00 every day from the source server to the
target server.
Start Date Start date of the checkpoint images to back up. This parameter
is mandatory if Backup mode is set to Historical.
For example, back up checkpoint images generated on and
after September 22, 2019 from the source server to the target
server.
Apply to Others Copies the backup plan of the current shadow camera to other
shadow cameras.
 Configure a live image backup plan.
Figure 5-24 Configuring a live image backup plan

7. Set Backup Type to Live video and set Backup Content based on the actual
requirements.
8. Click Save.
----End
5.2.2.2 Configuring Image Backup on a Third-Party Platform

Step 2 Choose System Management > Backup Management > Third-Party Platform Image
Backup.
Step 3 Select the backup target server and create a third-party platform image backup plan,
Figure 5-25 Configuring a third-party platform image backup plan
1. Set Backup Source NVR List to the third-party platform whose images need to be
backed up.
execution.
3. In the Image Backup Period area, set the start date for backing up images and drag
the slider on the timeline to set the backup time segment.
Backup Content Type of third-party platform images to back up.
Backup Source Source server of third-party platform images to back up.

NVR List
Execution Time Time segment for the target server to execute the backup.
For example, the target server backs up images stored on a third-
party platform from 17:00 to 17:30 every day.
Image Backup Time segment of images to be backed up from a third-party

Period platform.
For example, back up images in the time segment from 16:00 to
17:00 every day from a third-party platform to the target server.
Start Date Start date of the images to be backed up from a third-party

platform.
For example, back up images generated on and after September 22,
2019 from a third-party platform to the target server.
Apply to Others You can click Apply to Others to apply the current third-party
platform backup plan to other third-party platforms.
Step 4 Click Save.

----End
6 Cloud-Edge Collaboration
6.1 Introduction
In two-level IVS networking, users can utilize analysis resources of both the upper- and
lower-level IVS platforms to create analysis, search, and alert tasks across IVS platforms,
and subscribe to data on the lower-level IVS platform, implementing resource reuse, task
collaboration, and data sharing. Users can also set up an algorithm management channel
between upper- and lower-level algorithm repositories. Through this channel, the upper-
level algorithm repository can query the algorithm plug-in information of the lower-level
algorithm repository, and the lower-level algorithm repository can download and update
algorithm plug-ins from the upper-level algorithm repository. This enables the unified
management of the network-wide algorithm plug-ins and ensures the consistency of
intelligent analysis data throughout the network. This experiment walks you through
configuring algorithm, task, and resource collaboration to help you have a deeper
understanding of cloud-edge synergy.
6.1.2 Objectives
 Understand the concept and configuration method of algorithm collaboration.
 Understand task, resource, and data collaboration.

6.2.1 Algorithm Collaboration
Prerequisites
 Algorithm plug-ins have been uploaded to the upper-level algorithm repository.
 The upper- and lower-level algorithm repositories are connected properly.
6.2.1.1 External Management Network Plane Configuration

The configuration method is the same as that in domain management. For details, see
section 4.2.1.1 "Configuring the External Management Network Plane."
6.2.1.2 Lower-Level Algorithm Repository Configuration

6.2.1.2.1 Configuring Algorithm Repository Cascading
Algorithm collaboration between two IVS platforms is unidirectional. For example, if IVS
platform A is the lower-level algorithm repository and IVS platform B is the upper-level
algorithm repository, users cannot set IVS platform A to the upper-level algorithm
repository and IVS platform B to the lower-level algorithm repository at the same time.

Step 3 Click Algorithm Repository Cascading and set parameters for Upper-Level Algorithm
Repository, as shown in the following figure.
Figure 6-1 Configure algorithm repository cascading
Register Set this parameter to Yes.
User Account User account and password for accessing the upper-level algorithm
Password repository.
If the upper-level algorithm repository is IVS3800 V100R019C30, enter
the upper-level algorithm repository account that has the analysis
role.
 For security purposes, instead of using the admin account, you are advised to
create an upper-level algorithm repository account dedicated for algorithm
repository cascading.
 If a password validity period has been configured for the new account, you
need to regularly change the password to ensure account security. If the
password expires, algorithm repository cascading will fail.
Algorithm IP address of the upper-level algorithm repository.

Repository IP To obtain the IP address, log in to the CSP OM portal of the upper-
Address level algorithm repository as the admin user, choose Application
Configuration > Configuration Management > Configuration >
Application Name > Connection > Surveillance Domain Cascading >
Algorithm Repository Cascading, and view the value of IP Address in
the Local Algorithm Repository area. If NAT has been configured for
the upper-level analysis platform, the IP address is the post-NAT IP
address.
Algorithm Port number of the upper-level algorithm repository. The default

Repository value is 8443.
Port If NAT is configured for the upper-level algorithm repository, enter the
port number translated from port 8443.
Step 4 Click Apply to for the settings to take effect.

Step 5 Check whether the settings have taken effect.
2. Click Algorithm Repository. If the algorithm plug-ins provided by the upper-level
algorithm repository are properly displayed, the configuration is successful.
----End
6.2.1.2.2 Downloading an Algorithm Plug-in

Step 3 Click Algorithm Repository, set the plug-in type to VA or MCS, and view algorithms in
the algorithm repository.
For example, the following figure shows a VA plug-in.
Figure 6-2 Viewing VA algorithms
Step 4 Click Download next to an algorithm to download the algorithm from the algorithm
repository.
When the download is complete, the system displays a message indicating that the
download is successful.
Step 5 Click Local Algorithms and set the plug-in type to VA or MCS to check for the
downloaded algorithm plug-in.
If the algorithm plug-in exists on this tab page, the algorithm is successfully downloaded.
To delete the downloaded algorithm plug-in, click Delete next to it.
----End
6.2.1.2.3 Installing Algorithm Plug-ins

The procedure for installing algorithm plug-ins is the same as that described in section
2.2.5 "Installing algorithm plug-ins"
6.2.1.2.4 Checking the Algorithm Plug-in Version
Step 3 Click Local Algorithms and select a plug-in type to view the local algorithm list.
Step 4 Click Check Version. In the dialog box that is displayed, click Yes.
The lower-level algorithm repository initiates a request to the upper-level algorithm
repository for checking algorithm version updates in batches.
If a later algorithm version is available, the Update button is displayed in the Operation
column corresponding to the algorithm on the local algorithm list.
Step 5 Click Update next to an algorithm plug-in. The IVS automatically updates the
algorithm plug-in.
When updating an algorithm plug-in, the IVS uninstalls the existing algorithm plug-in
first, and then installs the later version of the plug-in. Before updating an algorithm plug-
in, ensure that no running intelligent analysis task uses this algorithm. Otherwise, the
corresponding intelligent analysis task will be interrupted.
----End
6.2.1.3 Upper-Level Algorithm Repository Configuration

6.2.1.3.1 Querying Plug-ins in the Lower-Level Algorithm Repository
Step 3 Click Algorithm Repository Cascading.

Step 4 In the Lower-Level Algorithm Repository area, select a domain node.
Step 5 Select a plug-in type, for example, VA.
Algorithm plug-ins in the lower-level algorithm repository are displayed.
Figure 6-3 Querying plug-ins in the lower-level algorithm repository
----End
6.2.1.3.2 Setting Flow Control Parameters
Batch algorithm plug-in download occupies network bandwidth. To reduce the impact of batch
algorithm plug-in download on services, you can set the flow control parameters, including the
maximum download bandwidth and maximum number of algorithm plug-ins that can be
concurrently downloaded, in the upper-level algorithm repository.

Step 3 Click Algorithm Repository Cascading.

Step 4 In the Local Algorithm Repository area, set Max. Download Bandwidth and Max.
Concurrent Downloads.
The value of Max. Download Bandwidth ranges from 1 to 5000, and the default value is
1000. The value of Max. Concurrent Downloads ranges from 1 to 16, and the default value
is 16.
Figure 6-4 Flow control configuration
Step 5 Click Apply.

----End
6.2.2 Task/Resource/Data Collaboration

Prerequisites
 Network connection has been established between adjacent upper- and lower-level
domains.
 Task collaboration, resource collaboration, and data collaboration support up to
three-level networking. The upper-level domain can manage a maximum of 63
lower-level domains, and the entire network supports a maximum of 200 domains.
 Users have the intelligent analysis task search and management as well as inter-
domain management permissions.
6.2.2.1 Cloud-Edge Synergy Configuration

6.2.2.1.1 Configuring Upper-Level Domain Information
Setting Upper-Level Domain Parameters
Step 2 Choose System Management > Domains > Local Domain.
Step 3 Set upper-level domain parameters. Table 6-2 describes the parameters.
Local Domain Name User-defined upper-level domain name.
Local Domain Code The value is generated by the system and cannot
be changed.
Register with Upper-Level Domain Select No.
User Name This parameter is left empty and cannot be

changed.
Password The value is generated by the system and cannot

be changed.
Upper-Level Domain IP This parameter is left empty and cannot be

changed.
Upper-Level Domain Port for Inter- This parameter is left empty and cannot be
Domain Communication changed.
Require NAT Traversal The default value is No and cannot be changed.
Description Enter description as required.
Step 4 Click Save.

----End
Configuring a User for Connecting the Upper- and Lower-Level Domains
Step 5 On the iClient home page, choose System Management > Domains > Inter-Domain
Accounts.
Step 6 A domain account with Domain Type set to Local Domain is the user account for
domain connection. You can click Change Password to change the password of this
account. The default password is huawei@123.
----End
6.2.2.1.2 Configuring Information for Registering a Lower-Level Domain with the

Upper-Level Domain
Step 1 Log in to the iClient of the lower-level domain as the admin user.
Step 3 Configure lower-level domain parameters. The following table describes the
parameters.
Local Domain Name User-defined lower-level domain name.
Local Domain Code The value is generated by the system and cannot be
changed.
Register with Upper- Select Yes.

Level Domain
User Name Enter the user name and password of the upper-level
domain for domain connection. For details about how to
Password obtain the user name and password, see section 6.2.2.1.1
"Configuring Upper-Level Domain Information."
Upper-Level Domain IP Enter the external service IP address of the NGINX node in
the upper-level domain.
To obtain the IP address, log in to the CSP OM portal of
the upper-level domain as the admin user, choose
Application Configuration > Configuration Management >
Configuration > Application Name > Two-Node Cluster.
If NAT is configured, enter the post-NAT IP address.
Upper-Level Domain  If NAT is not configured for the upper-level domain,

Port for Inter-Domain enter 443.
Communication  If NAT is configured for the upper-level domain, enter
the port number translated from port 443.
Require NAT Traversal  Yes: If the upper- and lower-level domains are on
different networks, select Yes.
 No: If the upper- and lower-level domains are on the
same network, select No.
Description Enter description as required.
Step 4 Click Save.

----End
6.2.2.1.3 Setting the Maximum Number of Inter-Domain Intelligent Analysis Task

Channels
Step 2 Choose System Management > Domains > Inter-Domain Accounts.
Step 3 Select the domain to be connected, for example, a domain whose Domain Type is
Upper-level domain, and click Set Permission.
A dialog box for setting the permission is displayed.
Step 4 Set the maximum number of inter-domain intelligent analysis task channels.
The maximum number of inter-domain intelligent analysis task channels is the maximum number
of cameras for which intelligent analysis tasks can be created by other domains through invoking
the local domain resources. For example, if the maximum number of inter-domain vehicle
recognition channels is set to 10 by the local domain for the upper-level domain, the upper-level
domain can invoke local domain resources to recognize vehicles from at most 10 cameras.
Step 5 Click OK.

----End
6.2.2.1.4 Verifying the Configuration

Step 1 Log in to the iClient of the lower-level domain as the admin user.
Step 3 Click Synchronize to synchronize the status information between domains.
If a synchronization success message is displayed, the connection between the upper- and
lower-level domains is normal.
----End
6.2.2.2 New Inter-Domain Intelligent Analysis Task

6.2.2.2.1 Creating an Inter-Domain Intelligent Analysis Task for Live Video from a
Camera
The procedure for creating an inter-domain intelligent analysis task for a camera is the
same as that for intelligent analysis task configuration, except that some parameter
settings are different. For example, you need to set the execution domain to a proper
upper-level domain or local domain.
Step 3 Click Cameras and select a camera.
Step 4 Create an intelligent analysis task for live video from the camera. Table 6-3 describes
the parameters.
To set intelligent analysis task parameters for cameras in batches, select multiple cameras
and select Apply to all.
Table 6-3 Intelligent analysis task parameters
Execution  If Upper-level domain is selected, the intelligent analysis task will be

Domain executed in the upper-level domain.
 If Home domain is selected, the execution domain of the intelligent
analysis task depends on the domain to which the selected camera
belongs. For example, if the selected camera belongs to the local
domain, the task will be executed in the local domain. If the camera
belongs to a lower-level domain, the task will be executed in the
lower-level domain.
If you will create an alert task for the camera, the execution domain of the alert
task must be the same as that of the intelligent analysis task.
Returned  If this parameter is set to No data returned, the intelligent analysis

Data Type result is not returned to the local domain, and all data and images in
the execution domain are retained.
 If this parameter is set to Structured data/Feature/Image URL, the
structured data, features, and image URLs generated by the
intelligent analysis task are returned to the local domain, and all
data and images in the execution domain are retained.
 If this parameter is set to Structured data/Feature/Image, the
structured data, features, and images generated by the intelligent
analysis task are returned to the local domain, and all data and
images in the execution domain are deleted.
Intelligent Select Vehicle recognition and select one or more vehicle recognition
Analysis algorithms. To use the image-based vehicle search function, select
Type Vehicle feature.
Fast Do not select this check box because inter-domain intelligent analysis
Analysis tasks do not support fast analysis.
Advanced  ROI parameters: You can specify an ROI. It is recommended that the
Settings ROI avoid areas without vehicles to reduce the false positive rate.
 Min. Plate Frame and Max. Plate Frame: Determine the sizes of
license plates to be captured.
enabled, the vehicle images recognized and pushed by intelligent
cameras are stored on the platform server. This parameter is invalid
for common cameras.
Click Finish.
----End
6.2.2.2.2 Creating an Inter-Domain Intelligent Analysis Task for a Video File

Uploading Video Files
Step 2 Click Uploads.
The system starts to upload the video file. You can view the uploaded video file on
----End
Creating an Inter-Domain Intelligent Analysis Task
Step 1 On the home page of the iClient, choose Basic Operations > Information Center.
Step 2 Click Uploaded Video.
video files, click New Analysis Task, and select Apply to all. Then, the settings of
intelligent analysis task parameters can apply for all the selected video files.
Step 4 Create an intelligent analysis task for the video file. Table 6-4 describes the
parameters.
Table 6-4 Intelligent analysis task parameters
Execution  If Upper-level domain is selected, the intelligent analysis task will be

Domain executed in the upper-level domain.
 If Home domain is selected, the execution domain of the intelligent
analysis task depends on the domain to which the selected camera
belongs. For example, if the selected camera belongs to the local
domain, the task will be executed in the local domain. If the camera
belongs to a lower-level domain, the task will be executed in the
lower-level domain.
If you will create an alert task for the camera, the execution domain of the alert
task must be the same as that of the intelligent analysis task.
Returned  If this parameter is set to No data returned, the intelligent analysis

Data Type result is not returned to the local domain, and all data and images in
the execution domain are retained.
 If this parameter is set to Structured data/Feature/Image URL, the
structured data, features, and image URLs generated by the
intelligent analysis task are returned to the local domain, and all
data and images in the execution domain are retained.
 If this parameter is set to Structured data/Feature/Image, the
structured data, features, and images generated by the intelligent
analysis task are returned to the local domain, and all data and
images in the execution domain are deleted.
Intelligent Select Vehicle recognition and select one or more vehicle recognition
Analysis algorithms. If you select huawei_cmv, Vehicle attributes is selected by
Type default. If you want to use the function of vehicle search by image,
select Vehicle features.
Fast Do not select this check box because inter-domain intelligent analysis
Analysis tasks do not support fast analysis.
Advanced  ROI parameters: You can specify an ROI. It is recommended that the
Settings ROI avoid areas without vehicles to reduce the false positive rate.
 Min. Plate Frame and Max. Plate Frame: Determine the sizes of
license plates to be captured.
enabled, the vehicle images recognized and pushed by intelligent
cameras are stored on the platform server. This parameter is invalid
for common cameras.

----End
6.2.2.3 Creating an Inter-Domain Alert Task

This section uses the creation of a vehicle alert task as an example to describe how to
create an inter-domain alert task.
Step 1 (Optional) View the recordings generated around the incident occurrence time to
obtain preliminary information about the target vehicle.
1. On the iClient home page, choose Basic Operations > Information Center.
2. Click Uploaded Video.
3. Click the Camera text box and select a camera near the incident location.
4. Set recording search criteria and click Search.
Figure 6-5 Searching for recordings
5. Specify a time segment that covers the incident occurrence time on the timeline of
the camera recording, hold down Ctrl, and click the timeline to view the recording.
6. Hold down the left mouse button and drag on the timeline to select a time segment
and click to view related information.
Figure 6-6 Viewing a recording

When viewing a recording, you can pause it and take snapshots, and then obtain vehicle
information, such as the license plate characters, vehicle color, license plate color, and
vehicle make, from the snapshots. You can search for vehicles based on the preliminary
information to obtain more accurate vehicle information, which helps you find the target
vehicle more accurately.
Step 2 (Optional) To create an alert on a vehicle in the vehicle library, create a vehicle
whitelist/blacklist first. For details, see section 3.2.4.1 "Vehicle Library."
Step 3 Configure a vehicle alert task.

1. Choose Intelligent Applications > Vehicle Alerts on the iClient home page.
2. Click New Alert Task and set alert task parameters, as shown in the following figure.
Figure 6-7 Configuring a vehicle alert task
Table 6-5 Vehicle alert task parameters
Alert Task Name Alert task name.
Active Time range for executing a vehicle alert task.
Alert Object Vehicle that the alert task targets. You can select either of the
following options:
 Vehicle: You must enter license plate characters (or upload a
license plate image). To create an alert task based on fuzzy
match, you can use an asterisk (*) to represent unknown
characters. The vehicle is automatically added to Temporary
Lists under Vehicle Library.
 List: You can select a vehicle blacklist or whitelist. The system
supports alerting based on fuzzy match. Therefore, the list can
contain fuzzy license plates [unknown characters are
represented by an asterisk (*)].
Approximate The vehicle or license plate recognition algorithm can provide the
License Plate recognition results of license plates whose similarities rank top 3.
 If Approximate License Plate is not selected, only the license
plate whose similarity ranks top 1 triggers the alarm.
 If Approximate License Plate is selected, license plates whose
similarities rank top 3 trigger the alarm.
Alert Level Set this parameter based on the importance and urgency level of
the alert task. The severity of alarms generated by an alert task
depends on the importance and urgency of the task. For example,
if this parameter is set to Critical, the severity of alarms generated
by this alert task is also critical.
Alarm Type  When listed detected: When the recognized vehicle matches the
vehicle specified by Alert Object, this type of alarm is
generated.
 When non-listed detected: When the recognized vehicle does
not match the vehicle specified by Alert Object, this type of
alarm is generated.
Alert Scope You can click the Alert Domain tab and select a checkpoint group
in a lower-level domain when creating an alert task.
Verification
On the iClient home page, choose Intelligent Applications > Vehicle Alerts and view the
status and details of each vehicle alert task, as shown in the following figure.
Figure 6-8 Vehicle alert page
----End
6.2.2.4 New Inter-Domain Search Task

This section uses the creation of a vehicle search task as an example to describe how to
create an inter-domain search task.
6.2.2.4.1 Searching Vehicles by Image
Step 1 On the home page of the iClient, choose Intelligent Applications > Vehicle Search.
Step 2 Click Search by Image.
Step 3 (Optional) To specify more search criteria, click More and set search criteria as
required. Table 6-6 describes the parameters.
Table 6-6 More search criteria
Period  Period during which the vehicle images are captured.

Search Select a lower-level domain for vehicle search.

Domain
 Inter-domain search is only supported between two adjacent domain levels.

 To search for faces, persons, and vehicles in the lower-level domain by the upper-
level domain when algorithms used in the two domains are different, you must
log in to the CSP OM portal, choose Application Configuration > Configuration
Management > Configuration > Application Name > Unified Configuration >
Analysis Platform, select VCMAPIService, and set Inter-domain retrieval is a
filtering algorithm to Yes.
Similarity Threshold of the similarity to the target for the search.
Algorithm Algorithm used for vehicle recognition and search.
Source Video source of vehicle images. The options are Camera, Video file, and
All.
Step 4 Upload or select a vehicle image.

Option 1: Drag a vehicle image to the search box. In the Upload Image dialog box that is
displayed, select the vehicle and click OK to start image search.
The uploaded vehicle image must meet the following requirements:

 The image format must be JPG, JPEG, DIB, BMP, or PNG.
 The image cannot exceed 5 MB, and the image resolution cannot exceed 4096 x
3000 pixels.
 The resolution of the selected vehicle area must range from 340 x 260 pixels to 1200
x 1200 pixels.
Option 2: Enter some or all characters of a license plate, a complete vehicle owner name,
or a complete vehicle owner ID number in the search box. Select a vehicle among those
found in the vehicle library.
Figure 6-9 Selecting a vehicle found in the vehicle

Step 5 The iClient automatically goes to the snapshot library (which contains vehicle images
extracted by vehicle feature recognition tasks) to search for the target vehicle. The
following figure shows the search results.
Figure 6-10 Image-based vehicle search results
----End
6.2.2.4.2 Filtering Vehicles by Criteria

Step 2 Click the Search by Criteria tab.
Step 3 Set filter criteria. Table 6-7 describes the parameters.
Table 6-7 Key filter criteria for vehicle search
License Plate License plate characters of the vehicle that is searched for. Fuzzy
search is supported, where the question mark (?) represents one
character, and the asterisk (*) is a wildcard representing zero or
multiple characters.
Unknown If you select this parameter, you cannot set License Plate, and the
plate iClient searches for vehicles without specific license plates.
Approximate The vehicle or license plate recognition algorithm may recognize

matches multiple approximate license plates for the same vehicle. The vehicle
information in the database includes the license plates with the
highest confidence and other approximate license plates.
 If Approximate matches is selected, the iClient compares the target
license plate with all license plates of each vehicle to find vehicles
with approximate license plates.
 If Approximate matches is not selected, the iClient only compares
the target license plate with the license plate with the highest
confidence.
Step 4 Click Search. The iClient automatically goes to the snapshot library (which contains
vehicle images captured by cameras or extracted by vehicle/license plate recognition
or pedestrian and vehicle data structuring tasks) to search for the target vehicle. The
following figure shows the search results.
The vehicle image on the right of the page is found in the vehicle library and contains
related vehicle information.
Figure 6-11 Vehicle search results
Step 5 (Optional) To obtain more accurate vehicle information, you can perform secondary
feature recognition on the found images.
Typically, secondary feature recognition applies to scenarios where the vehicle recognition
algorithm of the IVS platform is used to further recognize the vehicle images obtained through
metadata subscription. If the recognized vehicle information is inconsistent, the results obtained
from secondary feature recognition prevail. The analysis result of secondary feature recognition
overwrites the original vehicle metadata.
1. Select a vehicle search result.
2. Click Secondary Feature Recognition.
3. In the Select algorithm dialog box, click the algorithm used for vehicle analysis and
click OK.
4. Choose Intelligent Applications > Tasks to view the analysis progress of secondary
feature recognition.
Step 6 Click Vehicle Library to see search results.

----End
6.2.2.5 Subscribing to Inter-domain Data

Inter-domain data subscription enables data upload from a lower-level domain to the
upper-level domain.
Prerequisites
 Metadata subscription has been completed for cameras in a lower-level domain.
 Intelligent analysis tasks have been created for cameras in the lower-level domain,
and both the creation domain and execution domain of the tasks are the lower-level
domain. The tasks are being executed.
 If the upper-level domain uses V100R019C20 or a later version and the lower-level
domain uses a version earlier than V100R019C20, you must log in to the CSP OM
portal of the upper-level domain, choose Application Configuration > Configuration
Management > Configuration > Application Name > Unified Configuration, click the
Analysis Platform tab, select VCMPushDataProcCenterService from the Service drop-
down list box, and turn on Enable HTTP for Multi-level and Multi-domain Network.
Data can be pushed between domains only after Enable HTTP for Multi-level and
Multi-domain Network is turned on.
Procedure
Step 2 Choose System Management > Domains > Inter-Domain Data Subscription.
Step 3 Select a lower-level domain, set search criteria, and click Search.
Step 4 Click Subscribe to data.
Step 5 Click Common Subscription or Alarm Subscription.
Table 6-8 Subscription type
Type Description
Common Subscribes to the metadata generated by intelligent analysis

Subscription tasks.
Alarm subscription Subscribes to alarm metadata generated by face alert tasks or

vehicle alert tasks.
If Push Images Between Multi-level Domains is enabled, images in addition to metadata can be
subscribed to. To enable this function, log in to the CSP OM portal as the admin user, choose
Application Configuration > Configuration Management > Configuration > Application Name >
Unified Configuration > Analysis Platform, set Service to VCMPushDataProcCenterService, and
enable Push Images Between Multi-level Domains.
Step 6 Select a lower-level domain, set search criteria, and click Search.
Step 7 Select a camera in the search result and set Returned Data Type.
----End
6.3 Connection to the IVS1800

6.3.1 Network
The IVS1800 can be connected to the IVS3800 as an NVR. The following figure shows the
networking mode.
Figure 6-12 Connecting the IVS1800 to the IVS3800
Restrictions:
After the IVS1800 is connected to the IVS3800, you can only view live video and play back
recordings from cameras connected to the IVS1800.
The IVS3800 needs to proactively obtain the status of cameras connected to the IVS1800.
Currently, the IVS1800 cannot push camera status.
6.3.2 Connection Using ONVIF

6.3.2.1 Setting IVS1800 Parameters
Step 1 Log in to the OMU portal as the admin user.
Step 2 Select Maintenance > ONVIFConfig.
Step 3 Enable the ONVIF protocol.
Enable ONVIF Check the box before this parameter.
Onvif Authentication mode for connecting the IVS1800 to the IVS3800 or

AuthMethod IVS9000.
Digest
WSSE
Digest/WSSE
None: No authentication is required.
The WSSE authentication mode has security risks. If you select this
mode, the system prompts a message indicating that the system is
prone to attacks. For security purposes, you are advised to enable
authentication and use the Digest authentication mode.
Onvif Transmission protocol for connecting the IVS1800 to the IVS3800 or

Protocol Type IVS9000.
HTTP
HTTPS
HTTP/HTTPS
HTTP has security risks. If you select HTTP, the system prompts a
message indicating that the system is prone to attacks. For security
purposes, you are advised to select HTTPS.
Step 4 Choose Maintenance > ONVIFPassword.

Step 5 Set the ONVIF password.
User User name and password for connection through ONVIF. You are
Name/Password advised to create a complex password.
----End
6.3.2.2 Setting IVS3800 Parameters

Step 1 On the IVS3800 iClient login page, log in as the admin user.
Figure 6-13 Logging in to the IVS3800
Step 2 Choose System Management > Device Access.

Step 3 Select Manual Single Access and click Start.
Step 4 Connect to the IVS1800.
The following table describes the parameters. You only need to set the parameters listed
in the table.
Access Mode Select Video.
Device Name Device name displayed on the iClient. You are advised
to enter the installation location or surveillance area of
the device.
Driver Select ONVIF.

NVR List Cluster node to which an IVS1800 is connected.
User Make sure that the user name and password are the
Name/Password/Confirm same as those you set in Figure 6.3
Password
IP Address IP address of the IVS1800.
Device Login Port Access port of the device, which must be the same as
that on the camera side. You are advised to use the
default port number. If the port number has been
changed on the camera side, set this parameter to the
new port number.

----End
6.3.2.3 Verifying the Configuration

Step 1 Log in to the iClient of the IVS3800 as the admin user.
Step 2 Check whether the device is online.
1. Choose System Management > Device Management > Main Devices.
2. Select the IVS3800 server or cluster.
3. Check whether the IVS1800 status is Online in the Status column.

1. Choose Basic Operations > Live > Cameras.
2. Drag a camera connected to the IVS1800 to a live video pane. If the live video is
properly played, the IVS1800 is successfully connected to the IVS3800.
The camera name is displayed as IVS1800 access name 01***.

----End

HCIP-Intelligent Vision V1.0 Lab Guide

Uploaded by

Copyright:

Available Formats

You might also like

HCIP-Intelligent Vision V1.0 Lab Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

HCIP-Intelligent Vision V1.0 Lab Guide

Uploaded by

Copyright:

Available Formats

Huawei Intelligent Vision Certification Training

HCIP-Intelligent Vision V1.0

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Prorietary and Confidential

Huawei Certificate System

About This Document

Background Knowledge Required

Experiment Environment Overview

Device Model Software Version

Camera X series, M series, V100R019CX0

Device Model Software Version

PowerCube 500 S7006-300H1

Access switch S5700

Computer Internet Explorer/Google Chrome

Experiment Environment Preparation

Device Quantity Remarks

Camera 2 for each group

Laptop or desktop computer 1 for each group

Twisted pair 4 for each group

iClient/SDC Intelligent Management System (SiMS) tool 1

Preparing Installation Tools

Overview ............................................................................................................................................................................................ iii

6 Commissioning of a Facial Recognition Camera .................................................................43

1 Installation of the PowerCube 500

1.1.3 Site Types

Table 1-1 Configurations in the solar-grid hybrid scenario

Functional module S7006-300H1

Lithium battery A maximum of two CBM20E-N14A1 modules can be installed.

Pole Solar pole

PV module Two PV modules

Figure 1-1 Networking in the solar-grid hybrid scenario

1.1.4 Site Installation Procedure

Figure 1-2 Site types

1.2 Experiment Task

Figure 1-3 Integrated site installation flowchart

1.2.2 Installation Procedure

Step 1 Place the pole on a wooden case or a similar object.

Figure 1-4 Routing cables through the pole

Installing the battery cabinet and functional module (solar-only scenario)

 At least three people should work together during installation.

Figure 1-5 Installing the battery cabinet and functional module

Figure 1-6 Installing the battery cabinet and functional module

Routing cables through cantilevers

Figure 1-7 Routing cables through cantilevers

Figure 1-8 Installing cantilevers

2.1.3 Camera Installation Procedure

Figure 2-1 Camera installation flowchart

1.1.1.1 Installing a Box Camera

Step 2 Use screws to fix the wall-mount bracket to the wall.

Figure 2-2 Wall-mounted installation of a box camera

2.1.3.2 Installing a Bullet Camera

Figure 2-3 Beam-mounted installation of a bullet camera

2.1.3.3 Installing a PTZ Dome Camera

Figure 2-4 Pole-mounted installation of a PTZ dome camera

2.1.3.4 Installing a Fixed Dome Camera in the Ceiling

Figure 2-5 In-ceiling installation of a fixed dome camera

3 Installation of the PV Module, Lightning