The whole process of video "cloud, edge, and end" supports H.265, which means lower traffic cost and higher video quality, and the computing pressure is on the edge

As a new generation of security video encoding technology, H.265 encoded video is compared with H.264 of the same source. The bit rate of H.265 video is 610kbps, the file size is 3.10MB, and the bit rate of H.264 video reaches 1183kbps. The file size is also 6.01MB. The H.265 (HEVC) standard can save 40% to 45% of the code rate compared to the H.264 standard. At the same time, domestic security manufacturers have popularized equipment based on the H.265 encoding algorithm. From the perspective of market performance, H.265 technology has brought many new opportunities to the security industry.

Video terminal equipment supports H.265

At present, most of the security cameras IPC and network hard disk video recorder NVR on the market already support the H.265 encoding format. The popularity of H.265 has brought a lot of progress to the network transmission and storage of video, and the network consumption is lower. , Storage space consumption is also less, of course, the complex computing power requirements for front-end video equipment have also increased, and most of the computing power requirements for this entire process may be on the front-end equipment and client playback, and the others belong to In the process of decapsulation, except for the AI ​​analysis part, most of the other parts will not produce H.265 codec consumption, so in this way, H.265 is still very cost-effective;

Video edge computing device supports H.265

Similarly, according to the previously designed "cloud, edge, end" formula, if there is a need for edge computing, then edge computing services and gateway devices need to have H.265 processing capabilities, when there are not many access channels In this case, you can use the CPU soft codec method to analyze the H.265 video. If there are more channels and the analysis frequency is higher, then not only a dedicated GPU device must be used, but also multiple GPU cards may be required. Simultaneous analysis;

  • When the edge computing gateway is used as a data transfer gateway, it does not involve the H.265 encoding and decoding process, so it does not consume computing power;
  • When the edge computing gateway needs to perform edge computing analysis, it will use the corresponding GPU card for analysis and calculation, and solve the computing problem through hardware;

Video cloud service supports H.265

As we all know, whether it is the relatively long RTSP/Onvif protocol, the later national standard GB/T28181 protocol, and the extended support of the RTMP alliance protocol, all of them support H.265 in the RTP/AVP section. At present, most of the Haikang, Dahua and Univision cameras both support H.265 national standard output. Therefore, on the device side, H.265 support is completely fine, so the main problem lies in the support of the video cloud platform;

At present, most video platforms can support H.265, but in the fields of H5 live broadcast, visualization, and Internet video, H.265 has not yet been fully popularized. Most of them are still H.264. The practice of many platforms is to get H.265. After that, perform the process of transcoding H.264 again, and then perform client-side playback. This process consumes more resources.

RTSP, Onvif, RTMP, GB28181, Ehome, SDK access all support H.265, EasyNVR, EasyDSS, EasyGBS, EasyCVR, all support H.265 access and output, and more importantly, H5 output.

Protocol support:

  • EasyDSS: File-on-demand and RTMP streaming protocol;
  • EasyNVR: RTSP/Onvif protocol;
  • EasyGBS: GB/T28181 protocol;
  • EasyCVR: All of the above;

Taking the national standard GB28181 as an example, after continuous R&D and iteration, we have summarized a very effective and H.265-supported video cloud platform solution development process. According to this process, it is relatively simple to develop a similar Video services such as EasyGBS:
use standard GB/T 28181 protocol to access video to video cloud services;
video cloud services use the RTMP push streaming H.265 form defined by the domestic CDN alliance to push to the corresponding RTMP streaming media server;
RTMP streaming The media server undergoes synchronous protocol conversion, and synchronously outputs: RTMP, RTSP, HTTP-FLV, HLS (m3u8) protocols; the
client uses MSE+WASM, compatible with H.264 and H.265 video playback;

Video client supports H.265

For a long time before, if you want to display H.265 camera video on the H5 side, developers need to go to the source to change the camera’s encoding format from H.265 to H.264, so as to achieve the H5 side plug-in-less large screen Visualization function, but this will cause a very troublesome problem. In the project, we spent a lot of money to purchase H.265 cameras in order to reduce bandwidth consumption and storage costs. However, when it is actually used, it is necessary Changing back to H.264, this approach is obviously not a long-term solution;

Later, we tried to use transcoding to dynamically convert H.265 video to H.264 during the visualization process, and then perform large-screen visualization. Although this temporarily solved the problem, the video was converted in real time. The encoding process not only produces delays, but also consumes a large amount of the computing power of the machine, especially when transcoding in high-definition. Basically, the machine cannot support the transcoding after a few channels. Therefore, in this case, later It is not a solution to the problem, although there are still manufacturers doing this;

With the support of wasm technology by major browsers and the affirmation of wasm standard by w3c, wasm technology can perfectly solve the problem of supporting H.265 encoding format in security visualization scenes. The characteristic of WebAssembly technology is to adopt The front-end decoding method of js/c/c++ decodes and plays real-time video. This is very consistent with the current popular concept of edge computing. Although it is only decoding calculation, the support of wasm for video decoding calculation may be just the beginning of H5 video edge computing. !

At present, our EasyNVR (access to RTSP/Onvif streaming), EasyDSS (access to RTMP push streaming), EasyGBS (access to national standard GB/T28181 equipment), EasyCVR (access to various public/private protocols), have fully supported wasm Technology, especially support for audio and video encoding formats such as H.265, PCMA/PCMU!

Conclusion

With its higher compression ratio, faster processing speed, better adaptability and robustness, H.265 has been rapidly developed and promoted in the field of security monitoring. I believe that in the near future, H.265 will definitely be able to use it. Advanced technology advantages bring more new opportunities to the security industry.

Guess you like

Origin blog.csdn.net/xiejiashu/article/details/106874268