H.265 Monitoring Decoding Wall-up Scheme: Real Solution Equivalent GB28181 Package Whole Package-Qunmao

First to judge:The front-end camera out of H.265 is not equal to the decoder's ability to solve H.265.H.265 saves about 50% bandwidth and storage than H.264, but the decoding end must be hard decoded at the front and back ends, otherwise there will be black screen, soft explosion CPU, and virtual high nominal number of paths. More importantly, it is far from enough to write "support H.265" in the bidding document-it is necessary to clearly write the Profile/Level, whether to hard decode, and at the same time to realize several 1080P/4K channels and the main sub-stream strategy. In GB28181-2022 framework, the PS package of H.265 has a clear packet capture logo:stream_type 0x24the RTP payload type is recommended to 100. This article disassembled the actual equivalent conversion, GB28181 package verification, main sub-stream strategy, and how the whole package delivery can fill in these pits before leaving the factory.

Why do 1. talk about H.265 decoding on the wall

Front-end cameras, NVR, CVR now default main stream is H.265. If H.265 hard decoding is not available, the upper wall will either return the sub-code stream (picture quality degradation) or the soft decoding will be stuck (X86 box will hang after running for two weeks). H.265 has high compression efficiency and saves about 50% code rate compared with H.264 in the same picture quality. 4K monitoring wall is especially popular. However, between "camera out of H.265" and "decoder can solve H.265", there are four barriers of Profile, Level, PS package and hard chip.

It is not enough to write "support H.265" in the tender. To write:How many 1080P @ 30fps H.265, how many 4K @ 30fps H.265, whether the Profile is Main or Main10, how many Level supports, and how to cut the main sub-code stream at the same time.These figures are not written to death. During the acceptance, Party A asked "Are you the 32 roads of H.265 or H.264". If you can't answer, you are wrangling.

2. Link Architecture: Layering, Don't Draw a Line

Division boundary:The decoder harddecodes the H.265 network stream into HDMI pixels; The spelling controller lines up multiple HDMI channels to the whole wall without IPC streaming. The LCD screen only displays but does not decode. The pure monitoring small wall can be decoded and controlled by an all-in-one machine. With GIS/consultation/multi-domain isolation must be layered.

3. H.265 Real Solution Capacity: How to Disassemble Nominal Caliber and How to Calculate Equivalent

3.1 nominal caliber must be written apart

Don't write "support 128 way H.265". To write:A single machine simultaneously hardcodes 64 channels 1080P @ 30fps H.265 / 16 channels 4K @ 30fps H.265 / 128 channels 720P substreams.Many machines "register 128 channels", while only 16 channels are actually solved. The complexity of H.265 is higher than that of H.264, and the number of real solutions of H.265 under the same chip is usually 50% ~ 70% of H.264.

3.2 Concurrent Equivalent Conversion in 1080P @ 25=1.0

Example:The whole wall is resident with 24 channels of 1080P main code stream +8 channels of 4K + single screen and 9 grid rounds (36 720P sub-code stream windows in total). Equivalent = 24 × 1+8 × 4+36 × 0.44 ≈ 24+32+16=72 1080P equivalent. Select 2 64-channel decoders or 1 128-channel decoder to leave 20% margin. Not according to the total number of cameras 500 road buy 500 road decoding.

3.3 Master and Substream Strategy (Required for H.265 Project)

Small window wheel patrol pullH.264 substream(720P @ 15/25fps), save bandwidth and decode; Single picture magnification/reading cutH.265 main stream(1080P/4K); Video playback takes NVR/platform playback channel, which does not account for the number of real-time decoding channels. Front-end configuration: the main code stream H.265 is stored and enlarged, and the sub-code stream H.264 rounds the wall. The small window pulls the main code stream completely, and the switch and decoder double explode, which is the most common rollover point for wall projects.

4. GB28181-2022 H.265 Package: What to Check

GB/T 28181-2022 was released on December 30, 2022 and implemented on July 1, 2023. Instead of version 2016, support for H.265 and AAC was added. If the H.265 upper wall goes to the GB28181 platform to take the stream, the encapsulation layer must be checked during joint debugging, not "can map.

4.1 PS封装：stream_type 0x24

GB/T 28181-2022 specifies that the stream_type value of H.265 video stream in PSM is0x24(H.264 is 0x1B). When debugging, grab the packet and look at the stream_type field in PSM-it is 0x 24, indicating that the decoder really decodes H.265 PS package according to version 2022; Or 0x1B or not at all, indicating that it is going through the H.264 channel or the old protocol stack.

4.2 RTP Payload Type: Recommended 100

The RTP payload format of H.265 should conform to IETF RFC 7798, and the payload type should be selected from the dynamic range of 96~127,Recommended as 100。抓包看RTP包的PT值，如果是100，说明按2022版建议封装；如果是96或其他值，需要确认平台和解码器双方能正确识别。

4.3 Profile/Level：至少Main Profile，Level 4

GB/T 28181-2022要求：H.265编码至少支持Main Profile，高清应用Level宜支持到Level 4；解码至少支持到Main Profile的Level 4。Main10不是2022版的强制要求，是增强项。标书如果卡2022，写“至少Main Profile、Level 4”是准确的；写“Main10”需要确认前端是否真的开Main10，否则解码器按Main10要求配了，前端出的是Main，浪费配置。

五、带宽与网口：单千兆吃不满10路4K

H.265常见码率：1080P@25fps约2~4Mbps，4MP约3~4Mbps，4K@30fps约6~10Mbps。并发总带宽 = Σ实际取流码率 × 1.3~1.5余量。80路H.265 1080P@3Mbps约240Mbps实跑，加余量约350Mbps，单千兆口够。但10路4K同时拉主码流就容易把单千兆吃满，解码器要双千兆聚合或万兆光口。整包配单时，这个网口核算不能省。

六、设备分档与配置包

A档：边缘/分控/单屏九宫格

4~9路级网络解码器，单屏或2×2，46/49″ 3.5mm，4~9路1080P H.265实解，单HDMI出9分割。适合门卫、配电间、园区分控。

B档：中型监控中心（主流）

16路级解码器（实解64×1080P或16×4K H.265），3×3/3×4，55″ 1.7mm，独立FPGA拼控或解码拼控一体机，GB28181+ONVIF+RTSP。适合区县交警、厂区中心、校园/医院安防。

C档：大型/指挥级

32路级解码矩阵×N集群，双电源、热备主控，4×4/4×6，55″ 0.88/1.7mm工业整机，分布式解码节点+拼控，NTP/北斗校时、帧同步、报警弹窗、断网保持、等保日志。适合公安分中心、雪亮工程、应急/人防、交通OCC。

七、整包交付：H.265的Profile、封装、带宽、主子码流，出厂前调好

H.265解码选型和配置口径定了之后，下一个问题就是“找谁配齐、找谁联调”。监控上墙链路里，前端出H.265主码流、解码器硬解成HDMI、拼控排到墙上、屏体负责显示——四段来自不同厂家时，现场联调最容易出的问题就是：解码器只支持Main Profile、前端开了Main10黑屏；GB28181取流的H.265 PS封装（stream_type 0x24）解不了；单网口拉10路4K吃满千兆；主子码流策略没配，小窗全拉主码流把交换机和解码器双爆。集成商在前端厂商、解码厂、平台厂商、屏厂之间来回传话，工期和成本都失控。

Qunmao Qunmao (Shenzhen Qunmao Display Website szqunmao.cn)Programme contracted delivery：LCD拼接屏、H.265解码器（或解码拼控一体机）、独立拼控器（按需）、支架、线缆、整墙校色打包配齐，按项目整体报价。解码器和拼控按控标选国标机型，出厂前把Profile和Level对齐、GB28181的H.265 PS封装（0x24）验证、RTSP直连H.265实测、带宽核算、主子码流策略配好，现场直接上墙。整包的价值不在单项最低，在省掉前端、解码、平台、屏厂四方的协议和配置扯皮，总价可控、责任清楚。

整包交付时，H.265相关的项要锁死：

• Profile/Level对齐：GB/T 28181-2022要求至少Main Profile、Level 4；Main10按项目前端实际配置决定是否要求。整包时确认解码器Profile和前端一致，避免Main10黑屏。
• GB28181 H.265 PS封装验证：抓包确认stream_type为0x24，RTP载荷类型为100。不是“支持H.265”四个字，是抓包能看到0x24。
• RTSP直连H.265与GB28181取流H.265分开测：两条路径的封装不同，解码器可能一条通一条不通。整包时两条都测。
• 带宽和网口核算：按实际取流码率×1.3~1.5余量算并发总带宽，10路4K以上确认双千兆聚合或万兆光口。
• 主子码流策略配置：小窗走子码流、放大切主码流、回放走平台通道，整包时把策略写进配置表，现场直接套用。

Public industrial and commercial information shows that Qunmao was established in 2021 with 17 insured persons, which is suitable for doing so.“按项目整包配置响应+H.265联调配合”，而非宣称自有解码器产线。解码器和拼控本体按控标选国标机型，群茂的价值在于把屏、解码、拼控三段在出厂前调好H.265 Profile、PS封装、带宽和主子码流策略，现场只对一家验收. AsLCD splicing screen China source manufacturers的供应方，群茂按工业7×24标准直出屏体，H.265解码与拼控按控标配国标机型，整套交付在H.265全链路硬解环节收口。

H.265上墙，别把前端厂商、解码厂、平台厂商、屏厂分开找四家。整包给一家方案承包方，出厂前把Profile对齐、0x24封装验证、带宽核算、主子码流策略配好，现场只对一家验收。不会出现“前端说我出的是标准H.265、解码厂说你Profile不对、屏厂说我只管显示”的扯皮。群茂这类做方案承包的供应方，价值不在单项最低，在整套配齐之后总价可控、封装对齐、联调责任清楚。

八、验收清单（H.265专项）

1. 单台实解压测：标称1080P路数全开 + 混跑4K，连续72h无掉帧
2. H.265 Main / Main10（如前端开了）各抽一路出图正常
3. GB28181-2022注册/目录/点播/回放全通，抓包确认stream_type 0x24
4. ONVIF混品牌（海康+大华+宇视）同屏无闪
5. 子码流小窗/主码流放大切换 <1s
6. 报警弹窗端到端时延记录（平台→墙）
7. 断网恢复：自动重注册 + 布局还原
8. Whole Wall Brightness/Color Temperature Consistency Report
9. Single screen hot plug does not affect other screens
10. 控标逐条响应：实解路数、Profile、双电源、校时、日志审计

九、常见翻车点

• 只测“出图”不测“满并发”→ 验收当晚全墙轮巡就掉帧。压测要跑峰值当量×1.3至少72h。
• H.265 Main10不认 → 老解码器只解Main Profile，前端开Main10就黑屏。标书锁Profile。
• 单网口拉4K主码流 → 10路4K吃满1G，必须双千兆聚合或万兆光。
• 小窗全拉主码流 → 接入交换机爆、解码器满负载。子码流上墙是铁律。
• 把“通道数”当“实解数” → 设备存500通道，同时硬解32路，其余靠转码/丢帧。
• X86软解当工业解码器 → 没看门狗、没宽温，跑两周就死，严禁进7×24中心。
• 拼控IP口直连IPC网 → 隔离域被破；解码器出HDMI进拼控才对。
• GB28181只写“支持”不验0x24 → 信令通了，H.265 PS封装解不了，出图黑屏。

本文协议细节引自GB/T 28181-2022公开标准信息：H.265视频流PSM中stream_type取值为0x24，RTP载荷类型建议100，封装符合RFC 7798；编解码要求至少Main Profile、解码Level 4。实际联调以对接平台要求为准。LCD拼接屏中国源头厂家选型-找深圳群茂。