For intelligent device, you should configure the analysis engine of device
first, and then set rule, arming schedule, alarm linkage for a specific detection scene that
may trigger intrusion alarm.
Figure 1 Programming Flow of Configuring Intrusion Alarm for Intelligent
Device
-
Call NET_DVR_STDXMLConfig to pass through the request URL:
GET
/ISAPI/System/capabilities for getting the
device capability to check if the analysis engine configuration is
supported.
The device capability is returned in the message XML_DeviceCap by output parameter pointer (lpOutputParam).
If the node <isSupportIntelligentAnalysisEngines> is returned in the
message and its value is "true", it indicates that analysis engine
configuration is supported, you can continue to perform this step.
Otherwise, the analysis engine configuration is not supported by
device, please end this task.
- Optional:
Call NET_DVR_STDXMLConfig to pass through the request URL:
GET
/ISAPI/Intelligent/analysisEngines/<ID> for getting default or configured analysis
engine parameters for reference.
The analysis engine parameters is returned in the message XML_AnalysisEngine by output parameter pointer (lpOutputParam).
-
Call NET_DVR_STDXMLConfig to pass through the request URL:
PUT
/ISAPI/Intelligent/analysisEngines/<ID>, and set input parameter pointer (lpInputParam) to XML_AnalysisEngine for setting the analysis engine parameters.
-
Call NET_DVR_STDXMLConfig to pass through the request URL:
GET
/ISAPI/Intelligent/channels/<ID>/capabilities for getting
intelligent channel capability to check if intrusion detection is
supported.
The intelligent channel capability is returned in the message
XML_IntelliCap by output parameter pointer (lpOutputParam).
If the node <isFieldDetectionSupport> is returned in the message and
its value is "true", it indicates that intrusion detection is supported, you
can continue to perform this step.
Otherwise, the intrusion detection is not supported by device,
please end this task.
-
Configure intrusion detection rule for a detection scene by channel.
- Optional:
Call NET_DVR_STDXMLConfig to pass through the request URL:
GET
/ISAPI/Intelligent/channels/<ID>/behaviorRule/capabilities
for getting the intrusion detection rule capability.
The intrusion detection rule capability is returned in
the message XML_Cap_RuleInfo by output parameter pointer
(lpOutputParam).
- Optional:
Call NET_DVR_STDXMLConfig to pass through the request URL:
GET
/ISAPI/Intelligent/channels/<ID>/behaviorRule/<SID>/rule/<ID> for getting default or configured
intrusion detection rule for reference.
The intrusion detection rule parameters are returned in
the message XML_RuleInfo by output parameter pointer
(lpOutputParam).
-
Call NET_DVR_STDXMLConfig to pass through the request URL:
PUT
/ISAPI/Intelligent/channels/<ID>/behaviorRule/<SID>/rule/<ID>, and set input parameter pointer
(lpInputParam) to XML_RuleInfo for setting the intrusion detection rule
of a specific detection scene.
-
Configure alarm linkage for the intrusion detection of a detection scene by
channel.
- Optional:
Call NET_DVR_STDXMLConfig to pass through the request URL:
GET
/ISAPI/Intelligent/channels/<ID>/behaviorRule/<SID>/notifications for getting default or configured
intrusion alarm linkage parameters for reference.
The intrusion alarm linkage parameters are returned in
the message XML_RuleNotification by output parameter pointer
(lpOutputParam).
-
Call NET_DVR_STDXMLConfig to pass through the request URL:
PUT
/ISAPI/Intelligent/channels/<ID>/behaviorRule/<SID>/notifications, and set input parameter pointer
(lpInputParam) to XML_RuleNotification for setting the intrusion alarm linkage
of a specific detection scene.
Note:
To receive the alarm in the platform, the linkage action must be set to
"center" (upload to center).
-
Configure arming schedule for the intrusion detection of a detection scene by
channel.
- Optional:
Call NET_DVR_STDXMLConfig to pass through the request URL:
GET
/ISAPI/Intelligent/channels/<ID>/behaviorRule/<SID>/schedules for getting default or configured
intrusion arming schedule for reference.
The arming schedule are returned in the message XML_RuleSchedule by output
parameter pointer (lpOutputParam).
-
Call NET_DVR_STDXMLConfig to pass through the request URL:
PUT
/ISAPI/Intelligent/channels/<ID>/behaviorRule/<SID>/schedules, and set input parameter pointer
(lpInputParam) to XML_RuleSchedule for setting arming schedule of a
specific detection scene.
Note:
The above rules, arming schedule, and alarm linkage can also be configured by
logging in to device via web browser.
- Optional:
Receive intrusion alarm in arming mode (see Receive Alarm/Event in Arming Mode) or listening mode (see Receive Alarm/Event in Listening Mode) when alarm is triggered.
Call NET_DVR_Logout and NET_DVR_Cleanup to log out and release resources.