Traversal between Private and Public networks of VCN30X0

Hello Friends,

Let's have a brief knowledge about Traversal between Private and Public networks of VCN30X0

Introduction to VCN30X0:

VCN30X0 is Huawei’s Video Cloud Network products series that contains VCN3010 & VCN3020. VCN is a complete image and video management solution from Huawei for security, surveillance and observation usages. In addition it also provides a comprehensive services for video data storage, forwarding, access & analysis. VCN3010 and VCN3020 have almost same architecture and feature except the media transfer rate that is 512Mbps and 1024Mbps for VCN3010 and VCN3020 respectively. VCN30X0 series uses Centralized management of nodes with the help of Media Processing Unit (MPUs) & Video Management Unit (VMUs) in either of single or multi-network topology. Huawei VCN30X0 also has the capability of integration with third part network. That broadens the scope use cases of this series of products.

Overview of NAT configurations for VCN30X0

As discussed earlier, due to broad scope & third party connectivity needs, VCN30X0 requires conversion of Private IP (IPv4 header) to public IP address. This is done through Network Access Translation (NAT) technology. This helps in connection and secure working of surveillance devices in access or public network with back end servers, both lying in different networks.

For instance, a camera is deployed in one institution and the server deployed on another. The two networks shall not be able to communicate unless a NAT device, such as a firewall or router, translates the server address, to and from.

Traversal between Private and Public Networks

VCN 30X0 uses two types of NAT implementation mechanisms. First one is NAT based upon IP address translation, whereas, second one is IP address plus port translation.  NAT based upon IP address translation is a one-to-one IP translation mechanism that converts one private IP address to a public IP address. With the help of this mapping technique, a user in private network can access the servers through a public IP.

Configurations for first type (i-e NAT based upon IP address) is done with use of Putty Tool. If Camera and the servers are connected in NAT mode, MPU IP address is mapped on public network. On the other hand, in case of clusters, cluster gateway IP is mapped on public IP. Configurations can authenticated through access to camera web systems.

For IP plus ports translation type of NAT, many-to-one address translation is done is which multiple private IPs are translated into a single public IP address. In addition, both IPs and Ports are translated simultaneously. Server’s internal ports numbers can be used for required scenarios’ selection. A camera can access the server using GB/T 28181 protocol. Like the case of NAT based upon IP address translation, IPs & ports translation configuration can be performed using Putty Tool and can be verified with the help camera web system by setting up the IP address of the server.

While configuring any of the above mentioned NAT traversal, it is kept in consideration that media streams can be transmitted TCP mode only. Furthermore, NAT traversal of clients is taken into consideration only in case of client-Platform NAT traversal and OMU portal or video wall etc. are not considered. These precaution are specific for Client-Platform NAT traversal configurations.

Hope you enjoyed this, I will be sharing more topics soon. You can share feedback and suggestions in comments or leave a private message.

Thanks!