POE suit implementation method based on NVR and IPC

Abstract

The application provides a POE set implementation method based on NVR and IPC, comprising setting a unique UID information for each NVR and IPC device in the production process of the NVR and IPC device; setting the UID information of each IPC device into each channel of the NVR device, and presetting the UID information of the corresponding NVR device in each IPC device; after the NVR device is started, configuring double IP addresses of the inner network and the outer network on the network port; using the interface of the LAN Switch chip, dividing the NVR inner network and the IPC network port of the LAN Switch into VLAN1 as the inner network, and dividing the NVR outer network and the outer network port of the LAN Switch into VLAN2 as the external LAN interface; the NVR device automatically searches the IPC device in the inner network, and automatically adds the searched IPC device into the corresponding channel according to the preset UID information, and completes the automatic networking. The application realizes the plug and play networking of the set device through the device pre-binding, double IP address allocation, VLAN isolation and automatic broadcast search mechanism, and guarantees the inner network safety and the device management efficiency.

Description

Technical Field

[0001] This invention relates to the field of security monitoring technology, specifically to a PoE suite implementation method based on NVR and IPC, which is suitable for security monitoring scenarios with centralized management of multiple devices. Background Technology

[0002] Network video recorders (NVRs) and network cameras (IPCs) are two commonly used core networking products for security monitoring. IPCs are primarily used to convert real-time optical and audio information into audio and video data and transmit it to the backend recorder for recording and storage, facilitating real-time viewing and post-event playback to investigate past incidents. Typically, multiple IPCs are connected to one or more NVRs in a network configuration, which is relatively complex and requires specialized knowledge. Each IPC is usually equipped with a wired power supply and a network cable.

[0003] After the emergence of PoE (Power Over Ethernet, standard IEEE 802.3af) technology, people considered reducing the power supply peripherals of each IPC, using only network cables for power supply and data transmission, simplifying on-site installation. Initially, this was done with PoE switches, and later it evolved into integrating PoE-related chips (PoE power supply chips, LAN switch chips) into NVR devices, further simplifying equipment and construction. IPC devices only need to be connected to the LAN switch port of the NVR to form a network. Currently, in the industry, it is common to further simplify the process by bundling multiple IPC devices and NVR devices into a package for easier operation and management.

[0004] However, there are also some problems. For example, there may be IP conflicts or inability to obtain IPs among numerous IPC devices and devices within the local area network, which requires certain management costs. Secondly, IPCs accessing the Internet will also expose them to the external network, leading to security issues such as attacks.

[0005] To simplify networking, the industry is gradually adopting PoE technology, which enables both power supply and data transmission via network cables. Typical solutions include: PoE switch + NVR + IPC: The PoE switch powers the IPCs, and the NVR connects to the IPCs via the switch. However, this requires additional switch configuration, increasing cost and management complexity. NVR with integrated PoE: The PoE power supply chip and LAN switch chip are integrated into the NVR, and IPCs are directly connected to the NVR's network port. However, manual configuration of IP addresses and device associations is still required, and internal network devices are susceptible to external interference.

[0006] Therefore, the existing technology has the following drawbacks: Manual configuration is inefficient: users need to set the IP address, channel association and other parameters of each IPC one by one, which is cumbersome. High security risks: IPCs communicate directly with external networks, making them vulnerable to attacks or unauthorized access; Poor device compatibility: Non-kit devices may be mistakenly added to the network, leading to resource conflicts or management chaos. Summary of the Invention

[0007] To address the shortcomings of existing technologies, this invention provides a PoE suite implementation method based on NVR and IPC. Through device pre-binding, dual IP address allocation, VLAN isolation, and automatic broadcast search mechanism, it enables plug-and-play networking of the suite devices while ensuring intranet security and device management efficiency.

[0008] The present invention achieves the above objectives through the following technical solutions: A PoE suite implementation method based on NVR and IPC includes: Kit device marking steps: During the production process of NVR and IPC devices, a unique UID information is set for each NVR and IPC device; at the factory, the UID information of each IPC device is set into each channel of the NVR device, and the corresponding NVR device UID information is preset in each IPC device; Network configuration and VLAN segmentation steps: After the NVR device is started, configure dual IP addresses for the internal network and the external network on the network port; using the interface of the LAN Switch chip, divide the NVR internal network and the LAN Switch IPC network port into VLAN1 as the internal network, and divide the NVR external network and the LAN Switch external network port into VLAN2 as the external LAN interface. Self-organizing network steps: The NVR device automatically searches for IPC devices in the intranet and adds the found IPC devices to the corresponding channels according to the preset UID information, thus completing the automatic networking.

[0009] According to the PoE suite implementation method based on NVR and IPC provided by the present invention, after the NVR device is started, two independent IP addresses are automatically configured on the network port, namely an internal network IP address and an external network IP address; the external network IP address is allocated dynamically or statically and exposed to the user for the user to configure network parameters; the internal network IP address is set as a static IP address, and the configuration interface is not exposed to the user, but is only automatically managed by the internal system of the NVR device.

[0010] According to the present invention, a PoE suite implementation method based on NVR and IPC is provided. During the initialization process, the NVR device software loads the driver and upper-layer application interface of the LAN Switch chip, and realizes the configuration and management of the LAN Switch function by calling the control interface provided by the chip. The NVR device software uses the LAN Switch chip interface to divide the NVR intranet and the LAN Switch IPC network port into the same VLAN, namely VLAN1, as the intranet environment. This intranet environment is used for data communication between the packaged devices, isolates external network interference, and ensures secure interaction between the IPC device and the NVR device. The NVR device software uses the LAN Switch chip interface to divide the NVR's external network and the LAN Switch's external network port into another VLAN, namely VLAN2, as an external LAN interface. This external LAN is used for communication between the NVR device and the external network, exposing the external IP for user configuration, while maintaining the independence of VLAN1. The NVR device is only allowed to communicate with the preset IPC device through VLAN1, and external devices are prohibited from directly accessing internal network resources.

[0011] According to the present invention, a PoE suite implementation method based on NVR and IPC is provided. After the NVR device is initialized, it starts the Dynamic Host Configuration Protocol (DHCP) service on a preset internal network IP address. The DHCP service is only open to the IPC device bound in the suite and refuses to respond to IP allocation requests from unauthorized external devices. After the IPC device is connected to the LAN switch port of the NVR device via a network cable, it automatically sends a DHCP request to the internal network. The DHCP service of the NVR device assigns an internal network IP address, subnet mask and default gateway to the IPC device, ensuring that the IPC device and the NVR device are on the same subnet. After the IPC device obtains the internal network IP address, the NVR device actively searches for and identifies the IPC device through the internal network, and verifies the device's legitimacy based on the preset UID information; Once the verification is successful, the NVR device will automatically add the IPC device to the corresponding channel and establish an audio and video data transmission connection to enable real-time monitoring, video recording and storage, and remote operation.

[0012] Specifically, the NVR device is only allowed to communicate with the IPC device via an IP address assigned by the internal network DHCP service, and external devices are prohibited from accessing the internal network by forging IP addresses or illegally accessing the internal network; the internal network communication data between the IPC device and the NVR device is isolated through VLAN 1 to avoid exposure to the external network and reduce the risk of being attacked.

[0013] According to the PoE suite implementation method based on NVR and IPC provided by the present invention, in the self-organizing network step, after the NVR device completes the internal network DHCP service configuration and VLAN division, it starts an independent broadcast search thread in the background. This thread periodically sends a broadcast search message of a preset format in the internal network VLAN1. The message contains the unique identifier of the NVR device and the search request type.

[0014] According to the PoE suite implementation method based on NVR and IPC provided by the present invention, when the IPC device in the same intranet VLAN1 continuously listens to the broadcast port, after receiving the search message from the NVR device, it parses the NVR_UID in the message; IPC devices verify whether the NVR_UID matches their own pre-defined associated NVR_UID; If a match is successful, the IPC device sends a response message to the NVR via unicast or broadcast. The response message includes at least its own IP address, UID, device model, and status information. After receiving the response message from the IPC device, the NVR device extracts the UID information and compares it with the locally stored list of package device UIDs; If the UID exists in the list, the NVR device determines the target channel according to the preset channel mapping rules and binds the IP address, MAC address and communication parameters of the IPC device to the corresponding channel; After completing the channel configuration of all matching IPCs, the NVR device sends a connection establishment command to each IPC device to start real-time monitoring, video recording and storage, and remote control functions. If the expected IPC response is not received, the NVR device records information about the unnetworked devices and prompts the user to check the device status through logs or the interface.

[0015] According to the PoE suite implementation method based on NVR and IPC provided by the present invention, before the NVR device leaves the factory or during user initialization configuration, the unique UID information of each IPC device is bound to a specific channel of the NVR device through a management interface or a dedicated configuration tool; wherein, the binding relationship is stored in the non-volatile memory of the NVR in the form of key-value pairs, in the format: {channel number: IPC_UID}; the NVR device also generates its own unique identifier NVR_UID and embeds it into the system firmware; Before the IPC device leaves the factory, the NVR_UID of the target NVR device is written into the IPC's storage module using a programming tool, forming an NVR_UID whitelist. When the IPC device starts up, it automatically loads the whitelist into memory and only allows responses to networking requests initiated by NVR_UIDs in the whitelist.

[0016] According to the present invention, a PoE suite implementation method based on NVR and IPC is provided, wherein the NVR device periodically sends broadcast search packets in VLAN1 of the internal network, and the packet header carries its own NVR_UID and search instructions; After receiving the broadcast, the IPC device parses the NVR_UID in the packet header and compares it with the locally stored NVR_UID whitelist. If a match is successful, the IPC device sends a response packet to the NVR via unicast, which includes its own IPC_UID, IP address, and device status. After receiving the response, the NVR device queries the locally stored {channel number: IPC_UID} mapping table; If the IPC_UID in the response packet exists in the mapping table, the NVR device will automatically bind the IP address of the IPC device to the corresponding channel and initialize the audio and video stream transmission parameters.

[0017] According to the PoE suite implementation method based on NVR and IPC provided by the present invention, the UID field in the broadcast search packet and response packet adopts symmetric encryption or asymmetric encryption, and the key is pre-installed in the NVR and IPC devices; the NVR device embeds a dynamically generated token in each search packet, and the IPC device needs to calculate the hash value of the token and its own UID and then return it; the NVR device verifies the legality of the hash value to prevent forged device responses; The IPC response packet contains a timestamp and a sequence number. The NVR device refuses to accept duplicate or expired response data.

[0018] According to the PoE suite implementation method based on NVR and IPC provided by the present invention, if the UID responded by the IPC device is not found in the mapping table of the NVR device, the NVR device records an exception log and prompts the user "not bound to device" through the management interface; If the NVR device receives a search request for a non-whitelisted NVR_UID, the IPC device will discard the data packet directly and will not return any response.

[0019] Therefore, compared with the prior art, the POE suite implementation method based on NVR and IPC proposed in this invention has the following beneficial effects: 1. This invention uses VLAN technology to restrict the NVR and IPC networking to the internal network (VLAN1), logically isolating them from the external LAN (VLAN2). This effectively blocks external devices from directly accessing the IPC, avoiding security risks such as port scanning, brute-force attacks, and DDoS attacks caused by IP exposure. Compared to traditional solutions where IPCs directly access the external network, expanding the attack surface, this invention's internal network isolation forces attackers to bypass two network layers, significantly increasing the security threshold.

[0020] 2. Both the NVR and IPC are pre-defined with unique UIDs (device identifiers) at the factory. When networking, bidirectional UID authentication is required: the NVR only responds to IPC requests with the pre-bound UID; the IPC only responds to search commands from the pre-bound NVR, rejecting unauthorized device access. This invention uses UID binding for hardware-level authentication, resulting in higher security.

[0021] 3. Users do not need to manually configure the IP address, subnet mask, or channel association of the IPCs. The NVR can automatically complete the network setup: broadcast search for IPC devices in the intranet; verify the validity of the IPC's UID; add the IPC to the corresponding channel according to the pre-binding relationship and start audio and video transmission. Therefore, this invention achieves "plug and play" and greatly shortens the network setup time.

[0022] 4. The NVR enables DHCP service within the intranet, automatically assigning static IP ranges (e.g., 192.168.1.100-199) to IPCs, avoiding IP conflicts and manual assignment errors. Compared to traditional solutions that rely on external DHCP servers or manual IP configuration, resulting in high management complexity, this invention integrates DHCP service, reducing network environment requirements. Furthermore, this invention integrates PoE functionality into the NVR, requiring only a single network cable for power supply and data transmission, saving on switch costs.

[0023] 5. This invention uses NVR to solidify the LAN switch chip configuration process, automatically divides VLANs and assigns IPs, eliminating the need for administrators to manually configure switch parameters (such as port VLANs, Trunk mode, etc.), significantly reducing the skill requirements for technical personnel, allowing ordinary operators to complete the deployment, and greatly improving management efficiency.

[0024] 6. This invention uses static mapping between the NVR channel and IPC UID to allow only bound devices to access the network, preventing unauthorized devices (such as IPCs searched by other NVRs) from mistakenly joining the network and avoiding resource conflicts and data leakage risks. When the NVR detects an IPC without a bound UID during the network setup process, it automatically records a log and prompts "Unbound Device" through the management interface, facilitating quick troubleshooting.

[0025] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments. Attached Figure Description

[0026] Figure 1 This is a flowchart of an embodiment of a PoE suite implementation method based on NVR and IPC according to the present invention.

[0027] Figure 2 This is a network diagram of the NVR and IPC devices in an embodiment of the PoE suite implementation method based on NVR and IPC of the present invention.

[0028] Figure 3 This is a network flowchart of NVR and IPC devices in an embodiment of the PoE suite implementation method based on NVR and IPC of the present invention. Detailed Implementation

[0029] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0030] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0031] See Figures 1 to 3 This embodiment provides a method for implementing a PoE suite based on NVR and IPC, including: Kit device marking steps: During the production process of NVR and IPC devices, a unique UID information is set for each NVR and IPC device; at the factory, the UID information of each IPC device is set into each channel of the NVR device, and the corresponding NVR device UID information is preset in each IPC device; Network configuration and VLAN segmentation steps: Power on the NVR and IPC respectively and connect them to the network cable to obtain their respective IP addresses; after the NVR device starts up, configure dual IP addresses for the internal network and the external network on the network port; using the interface of the LAN Switch chip, divide the NVR internal network and the IPC network port of the LAN Switch into VLAN1 as the internal network, and divide the NVR external network and the external network port of the LAN Switch into VLAN2 as the external LAN interface. Self-organizing network steps: The NVR device automatically searches for IPC devices within the intranet and adds the found IPC devices to the corresponding channels based on the preset UID information, completing automatic network formation and enabling plug-and-play image output without considering the complex surrounding network environment. VLAN segmentation achieves isolation between the intranet and the extranet, reducing security risks.

[0032] In this embodiment, after the NVR device is started, two independent IP addresses are automatically configured on the network port: an internal IP address and an external IP address. The external IP address is assigned dynamically or statically and exposed to the user for configuring network parameters (such as subnet mask, gateway, DNS, etc.). The internal IP address is set to a static IP address and is not exposed to the user for configuration. It is only managed automatically by the internal system of the NVR device.

[0033] By configuring dual IP addresses, logical isolation between the intranet (static IP) and the extranet (user-configured IP) is achieved; the NVR only allows interaction with the IPC devices in the bundled package via the intranet IP, and rejects intranet access requests from extranet IP or other unauthorized devices to prevent external attacks or unauthorized device access.

[0034] During the initialization process, the NVR device software loads the LAN switch chip driver and upper-layer application interface, and configures and manages the LAN switch functions by calling the control interface provided by the chip. The NVR device software uses the LAN Switch chip interface to divide the NVR intranet and the LAN Switch IPC network port into the same VLAN, namely VLAN1, as the intranet environment. This intranet environment is used for data communication between the packaged devices, isolates external network interference, and ensures secure interaction between the IPC device and the NVR device. The NVR device software uses the LAN Switch chip interface to divide the NVR's external network and the LAN Switch's external network port into another VLAN, namely VLAN2, as an external LAN interface. This external LAN is used for communication between the NVR device and the external network, exposing the external IP for user configuration, while maintaining the independence of VLAN1. The physical isolation between VLAN1 and VLAN2 achieves logical separation between the internal network (packaged device) and the external network (external network), reducing the risk of external attacks. The NVR device only allows communication with the preset IPC device through VLAN1, and prohibits external devices from directly accessing internal network resources.

[0035] In this embodiment, after initialization, the NVR device starts the Dynamic Host Configuration Protocol (DHCP) service on a preset internal network IP address to provide IP address allocation services for IPCs, forming an internal network environment. This allows the IPCs to be searched, added, displayed, and operated by the NVR after obtaining an IP address. This DHCP service is only open to IPC devices within the bound package and refuses to respond to IP allocation requests from unauthorized external devices. After the IPC device is connected to the LAN switch port of the NVR device via a network cable, it automatically sends a DHCP request to the internal network. The DHCP service of the NVR device assigns an internal network IP address, subnet mask and default gateway to the IPC device, ensuring that the IPC device and the NVR device are on the same subnet. After the IPC device obtains the internal network IP address, the NVR device actively searches for and identifies the IPC device through the internal network, and verifies the device's legitimacy based on the preset UID information; Once the verification is successful, the NVR device will automatically add the IPC device to the corresponding channel and establish an audio and video data transmission connection to enable real-time monitoring, video recording and storage, and remote operation.

[0036] Specifically, the NVR device is only allowed to communicate with the IPC device via an IP address assigned by the internal network DHCP service, and external devices are prohibited from accessing the internal network by forging IP addresses or illegally accessing the internal network; the internal network communication data between the IPC device and the NVR device is isolated through VLAN 1 to avoid exposure to the external network and reduce the risk of being attacked.

[0037] During the self-organizing network process, after completing the internal network DHCP service configuration and VLAN division, the NVR device starts an independent broadcast search thread in the background. This thread periodically sends broadcast search messages in a preset format in the internal network VLAN1. The message contains the unique identifier of the NVR device (such as NVR_UID) and the search request type.

[0038] When an IPC device in the same intranet VLAN1 continuously listens to the broadcast port, it receives a search message from an NVR device and parses the NVR_UID in the message. IPC devices verify whether the NVR_UID matches their own pre-defined associated NVR_UID; If a match is successful, the IPC device sends a response message to the NVR via unicast (target IP is the NVR's internal network IP) or broadcast. The response message includes at least its own IP address, UID, device model, and status information. After receiving the response message from the IPC device, the NVR device extracts the UID information and compares it with the locally stored list of package device UIDs; If the UID exists in the list, the NVR device determines the target channel according to the preset channel mapping rules and binds the IP address, MAC address and communication parameters of the IPC device to the corresponding channel. For example, after the NVR with IP address 10.0.0.1 receives the response from the IPC with IP address 10.0.0.10 and the UID is the preset value, it automatically adds it to the channel and initializes the audio and video streaming connection.

[0039] After completing the channel configuration of all matching IPCs, the NVR device sends a connection establishment command to each IPC device to start real-time monitoring, video recording and storage, and remote control functions. If the expected IPC response is not received, the NVR device records information about the unnetworked devices and prompts the user to check the device status through logs or the interface.

[0040] Before the NVR device leaves the factory or during user initial configuration, the unique UID information of each IPC device is bound to the specific channel of the NVR device through the management interface or dedicated configuration tool. The binding relationship is stored in the NVR's non-volatile memory in the form of key-value pairs, with the format: {channel number: IPC_UID}, for example: {channel 1: IPC_UID_001, channel 2: IPC_UID_002}. The NVR device also generates its own unique identifier NVR_UID and embeds it into the system firmware, which serves as the benchmark for subsequent IPC device verification. Before the IPC device leaves the factory, the NVR_UID of the target NVR device is written into the IPC's storage module (such as EEPROM or Flash) using a programming tool to form an NVR_UID whitelist. When the IPC device starts up, it automatically loads the whitelist into memory and only allows responses to networking requests initiated by NVR_UIDs in the whitelist.

[0041] In this embodiment, the NVR device periodically sends broadcast search packets in VLAN1 of the internal network, with the packet header carrying its own NVR_UID and search instructions; After receiving the broadcast, the IPC device parses the NVR_UID in the packet header and compares it with the locally stored NVR_UID whitelist. If a match is successful, the IPC device sends a response packet to the NVR via unicast, which includes its own IPC_UID, IP address, and device status. After receiving the response, the NVR device queries the locally stored {channel number: IPC_UID} mapping table; If the IPC_UID in the response packet exists in the mapping table, the NVR device automatically binds the IP address of that IPC device to the corresponding channel and initializes the audio and video stream transmission parameters. Example: After receiving a response with IPC_UID_001, the NVR assigns its IP address to the channel and starts a real-time monitoring task.

[0042] In this embodiment, the UID field in the broadcast search packet and response packet uses symmetric encryption (such as AES-128) or asymmetric encryption (such as RSA-2048), and the key is pre-installed in the NVR and IPC devices; the NVR device embeds a dynamically generated token in each search packet, and the IPC device needs to calculate the hash value of the token and its own UID and then return it; the NVR device verifies the legality of the hash value to prevent forged device responses; The IPC response packet contains a timestamp and a sequence number. The NVR device refuses to accept duplicate or expired response data.

[0043] If the UID responded by the IPC device is not found in the mapping table of the NVR device, the NVR device records an exception log and prompts the user with "Not bound to device" through the management interface; If the NVR device receives a search request for a non-whitelisted NVR_UID, the IPC device will discard the data packet directly and not return any response.

[0044] In summary, this invention, through collaborative innovation of software and hardware, enables intelligent networking and plug-and-play image generation while ensuring the core functions of the security monitoring system (such as real-time recording and remote access). It does not require consideration of the complex surrounding network environment. At the same time, VLAN segmentation achieves isolation between the internal and external networks, reducing security risks. It systematically solves the problems of weak security, complex configuration, and high cost of traditional PoE networking solutions, and has significant economic benefits and social value.

[0045] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0046] The above embodiments are merely preferred embodiments of the present invention and should not be construed as limiting the scope of protection of the present invention. Any non-substantial changes and substitutions made by those skilled in the art based on the present invention shall fall within the scope of protection claimed by the present invention.

Claims

1. A method for implementing a PoE suite based on NVR and IPC, characterized in that, include: Kit device labeling steps: During the production process of NVR and IPC devices, assign a unique UID information to each NVR and IPC device; At the factory, the UID information of each IPC device is set into each channel of the NVR device, and the corresponding UID information of the NVR device is preset in each IPC device; Network configuration and VLAN segmentation steps: After the NVR device is started, configure dual IP addresses (internal and external) on the network port; Using the interface of the LAN Switch chip, the NVR intranet and the LAN Switch IPC port are divided into VLAN1 as the intranet, and the NVR external network and the LAN Switch external network port are divided into VLAN2 as the external LAN interface. Self-organizing network steps: The NVR device automatically searches for IPC devices in the intranet and adds the found IPC devices to the corresponding channels according to the preset UID information, thus completing the automatic networking.

2. The method according to claim 1, characterized in that: After the NVR device starts up, it automatically configures two independent IP addresses on the network port: an internal IP address and an external IP address. The external IP address is assigned dynamically or statically and exposed to the user for network parameter configuration. The internal IP address is set to a static IP address and does not provide a configuration interface to the user; it is managed automatically by the internal system of the NVR device.

3. The method according to claim 1, characterized in that: During the initialization process, the NVR device software loads the LAN switch chip driver and upper-layer application interface, and configures and manages the LAN switch functions by calling the control interface provided by the chip. The NVR device software uses the LAN Switch chip interface to divide the NVR intranet and the LAN Switch IPC network port into the same VLAN, namely VLAN1, as the intranet environment. This intranet environment is used for data communication between the packaged devices, isolates external network interference, and ensures secure interaction between the IPC device and the NVR device. The NVR device software uses the LAN Switch chip interface to divide the NVR's external network and the LAN Switch's external network port into another VLAN, namely VLAN2, as an external LAN interface. This external LAN is used for communication between the NVR device and the external network, exposing the external IP for user configuration, while maintaining the independence of VLAN1. The NVR device is only allowed to communicate with the preset IPC device through VLAN1, and external devices are prohibited from directly accessing internal network resources.

4. The method according to claim 1, characterized in that: After initialization, the NVR device starts the Dynamic Host Configuration Protocol (DHCP) service on the preset internal network IP address. This DHCP service is only open to IPC devices within the bound package and refuses to respond to IP allocation requests from unauthorized external devices. After the IPC device is connected to the LAN switch port of the NVR device via a network cable, it automatically sends a DHCP request to the internal network. The DHCP service of the NVR device assigns an internal network IP address, subnet mask and default gateway to the IPC device, ensuring that the IPC device and the NVR device are on the same subnet. After the IPC device obtains the internal network IP address, the NVR device actively searches for and identifies the IPC device through the internal network, and verifies the device's legitimacy based on the preset UID information; After successful verification, the NVR device automatically adds the IPC device to the corresponding channel and establishes an audio and video data transmission connection to enable real-time monitoring, video recording and storage, and remote operation. Specifically, the NVR device is only allowed to communicate with the IPC device via an IP address assigned by the internal network DHCP service, and external devices are prohibited from accessing the internal network by forging IP addresses or illegally accessing the internal network; the internal network communication data between the IPC device and the NVR device is isolated through VLAN 1 to avoid exposure to the external network and reduce the risk of being attacked.

5. The method according to claim 1, characterized in that: During the self-organizing network process, after completing the internal network DHCP service configuration and VLAN division, the NVR device starts an independent broadcast search thread in the background. This thread periodically sends broadcast search messages in a preset format in the internal network VLAN1. The message contains the unique identifier of the NVR device and the search request type.

6. The method according to claim 5, characterized in that: When an IPC device in the same intranet VLAN1 continuously listens to the broadcast port, it receives a search message from an NVR device and parses the NVR_UID in the message. IPC devices verify whether the NVR_UID matches their own pre-defined associated NVR_UID; If a match is successful, the IPC device sends a response message to the NVR via unicast or broadcast. The response message includes at least its own IP address, UID, device model, and status information. After receiving the response message from the IPC device, the NVR device extracts the UID information and compares it with the locally stored list of package device UIDs; If the UID exists in the list, the NVR device determines the target channel according to the preset channel mapping rules and binds the IP address, MAC address and communication parameters of the IPC device to the corresponding channel; After completing the channel configuration of all matching IPCs, the NVR device sends a connection establishment command to each IPC device to start real-time monitoring, video recording and storage, and remote control functions. If the expected IPC response is not received, the NVR device records information about the unnetworked devices and prompts the user to check the device status through logs or the interface.

7. The method according to claim 1, characterized in that: Before the NVR device leaves the factory or during user initial configuration, the unique UID information of each IPC device is bound to the specific channel of the NVR device through the management interface or dedicated configuration tool. The binding relationship is stored in the NVR's non-volatile memory in the form of key-value pairs, with the format: {channel number: IPC_UID}. The NVR device also generates its own unique identifier NVR_UID and embeds it into the system firmware. Before the IPC device leaves the factory, the NVR_UID of the target NVR device is written into the IPC's storage module using a programming tool, forming an NVR_UID whitelist. When the IPC device starts up, it automatically loads the whitelist into memory and only allows responses to networking requests initiated by NVR_UIDs in the whitelist.

8. The method according to claim 7, characterized in that: The NVR device periodically sends broadcast search packets in VLAN 1 of the internal network, with the packet header carrying its own NVR_UID and search instructions; After receiving the broadcast, the IPC device parses the NVR_UID in the packet header and compares it with the locally stored NVR_UID whitelist. If a match is successful, the IPC device sends a response packet to the NVR via unicast, which includes its own IPC_UID, IP address, and device status. After receiving the response, the NVR device queries the locally stored {channel number: IPC_UID} mapping table; If the IPC_UID in the response packet exists in the mapping table, the NVR device will automatically bind the IP address of the IPC device to the corresponding channel and initialize the audio and video stream transmission parameters.

9. The method according to claim 8, characterized in that: The UID field in the broadcast search packet and response packet uses symmetric or asymmetric encryption, and the key is pre-installed in the NVR and IPC devices. The NVR device embeds a dynamically generated token in each search packet, and the IPC device needs to calculate the hash value of the token and its own UID and then return it. The NVR device verifies the validity of the hash value to prevent forged device responses. The IPC response packet contains a timestamp and a sequence number. The NVR device refuses to accept duplicate or expired response data.

10. The method according to claim 9, characterized in that: If the UID responded by the IPC device is not found in the mapping table of the NVR device, the NVR device records an exception log and prompts the user "Not bound to device" through the management interface; If the NVR device receives a search request for a non-whitelisted NVR_UID, the IPC device will discard the data packet directly and not return any response.

Images