OddMeta
Just another AI student
OddMeta
StreamingMedia

H.323 capability calculation for H.264 video

by |Published |5 comments

A sample packet of H.245 terminalCapabilitySet

sample H.264 terminalCapabilitySet
sample H.264 terminalCapabilitySet

Step 1: LEVEL(unsignedMin: 78 – Level 3.2)

H.264 Level: 3.2, we can find out the max capability of level 3.2 by referring to the H.264 level limitation table.

H.264 level limitation of level 3.2
H.264 level limitation of level 3.2

MaxMBPS: 216000MB/s

MaxFS: 5120MB/s

 

Calculate the resolution by the suggested MaxFS value: 5120*256 = 1280*1024, which mean resolution will be 1280*1024

Calculate the frame rate by the suggested MaxMBPS value: 216000/5120 = 42 fps

 

Step 2: CustonMaxFS (unsignedMin: 32)

Calculate the resolution by the customized frame rate: 32*256*256(2097152) > 1920 * 1080(2073600), which means the resolution could at least be 1920*1080.

 

Step 3: CustonMaxMBPS(unsignedMin: 486)

Calculate the frame rate by the customized MBPS: 486*500/ 32*256= 30 fps

 

P.S. It is using CustomMaxFS 32(32*256=8192) and CustomMaxMBPS 486(486*500 = 243000) in this sample capability, if you check into the level limitation table, you can find out that it’s similar to Level 4 or Level 4.1 rather than Level 3.2.

H.264 level limitation of level 4 and level 4.1
H.264 level limitation of level 4 and level 4.1

A sample implementation for it

sample implementation for calculation
sample implementation for calculation

Appendix

H.264 level limitation table
H.264 level limitation table
video resolution table
video resolution table

From a former colleague.

You may also like

Vendor ID, Product ID information in SIP
Published

Vendor ID, Product ID information in SIP

As you may know, to be a robust meeting entity, we must take good care of compatibility requirements for different facilities from different manufacturers. In H.323 protocol, we can use fields like Vendor ID, Product ID, Version ID in the signaling commands. But how to do this when you are using SIP protocol? Definitions in RFC 3261 20.35 Server    The Server header field contains information about the software used    by the UAS to handle the request.    Revealing the specific software version of the server might allow the    server to become more vulnerable to attacks against software that is    known to contain security holes. Implementers SHOULD make the Server    header field a configurable option.    Example:       Server: HomeServer v2 20.41 User-Agent    The User-Agent header field contains information about the UAC    originating the request.  The semantics of this header field are    defined in [H14.43].    Revealing the specific software version of the user agent might allow    the user agent to become more vulnerable to attacks against software    that is known to contain security holes.  Implementers SHOULD make    the User-Agent header field a configurable option. […]

A Simple Tutorial for WANem
Published

A Simple Tutorial for WANem

Being a networking related product developer, we always face issues which can not be easily reproducted in LAB(because in most cases we […]

Leave a comment

Your email address will not be published. Required fields are marked *

5 thoughts on “H.323 capability calculation for H.264 video”