From 6808e79a6268f85c21c771d516136d41654c6f58 Mon Sep 17 00:00:00 2001 From: Sriram Bhetanabottla Date: Tue, 10 Mar 2026 13:39:24 +0700 Subject: [PATCH 1/2] updates for av1 codec feature support --- doc/Streaming.xml | 21 ++++++++++++++++++++- wsdl/ver10/schema/onvif.xsd | 6 ++++-- 2 files changed, 24 insertions(+), 3 deletions(-) diff --git a/doc/Streaming.xml b/doc/Streaming.xml index 92a7d7ca8..fdf215014 100644 --- a/doc/Streaming.xml +++ b/doc/Streaming.xml @@ -280,6 +280,8 @@ <> IETF RFC 8285, A General Mechanism for RTP Header Extensions <> + RTP Payload Format For AV1 + <> GZIP file format specification version 4.3 <> Apple Computer Inc. RTSP over HTTP, Tunneling QuickTime RTSP and RTP over HTTP @@ -521,6 +523,10 @@ Efficient XML Interchange Format + + OBU + Open Bitstream Unit, related to AV1 bistream format. + @@ -568,6 +574,11 @@ HEVC [ISO23008-2] + + + AV1 [AOM AV1 Bitstream & Decoding Process Specification] + + and for the following audio codecs: @@ -625,6 +636,8 @@ RTP The Real-time Transport Protocol provides real-time transfer for media streams between two end points. The RTP protocol provides support for re-ordering, de-jittering and media synchronization. All media streams transferred by the RTP protocol shall conform to [RFC 3550], [RFC 3551], [RFC 3984], [RFC 7798], [RFC 3016] or [RFC 3640], and JPEG over RTP (see Section ). + For AV1 video transported over RTP, the RTP payload format defined in [RTP Payload + Format for AV1] shall be used.
RTP header @@ -708,7 +721,10 @@ 0/1 - The usage shall be conform to related RFCs (e.g. [RFC 3984] for H.264 Video) or to this standard e.g “JPEG over RTP” (see Section ) or RTP streaming of metadata (see Section ). + The usage shall be conform to related RFCs (e.g. [RFC 3984] for H.264 + Video) or to this standard e.g “JPEG over RTP” (see Section ) or RTP Payload Format For AV1 or RTP streaming of + metadata (see Section ). @@ -876,6 +892,9 @@ The WebService based methods require to support the Synchronization Point request as defined in the section “Synchronization Point” of the ONVIF Media Service Specification. In addition it is recommended to support the PLI messages as described in [RFC 4585] in order to allow receivers as defined in the ONVIF Receiver Service Specification to request a Synchronization Point. For H.264 and H.265 Video the SPS/PPS header shall be sent in-band if these have been changed during the transmission. + For AV1 video, the device shall generate a Key Frame in response to a synchronization + point request. If the Sequence Header OBU changes during transmission, it shall be sent + in-band prior to or together with the Key Frame.
JPEG over RTP diff --git a/wsdl/ver10/schema/onvif.xsd b/wsdl/ver10/schema/onvif.xsd index d1737ffa3..ba1dce978 100755 --- a/wsdl/ver10/schema/onvif.xsd +++ b/wsdl/ver10/schema/onvif.xsd @@ -1036,6 +1036,7 @@ IN NO EVENT WILL THE CORPORATION OR ITS MEMBERS OR THEIR AFFILIATES BE LIABLE FO + @@ -1044,10 +1045,11 @@ IN NO EVENT WILL THE CORPORATION OR ITS MEMBERS OR THEIR AFFILIATES BE LIABLE FO - + - + + From 611f43918a8f3bab272ec89ee7fe567643f40c91 Mon Sep 17 00:00:00 2001 From: Sriram Bhetanabottla Date: Tue, 10 Mar 2026 13:58:17 +0700 Subject: [PATCH 2/2] added av1 spec reference --- doc/Streaming.xml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/doc/Streaming.xml b/doc/Streaming.xml index fdf215014..ff5036fec 100644 --- a/doc/Streaming.xml +++ b/doc/Streaming.xml @@ -244,8 +244,7 @@ IETF RFC 2435, RFC2435 - RTP Payload Format for JPEG-compressed Video <> IETF RFC 3016, RTP Payload Format for MPEG-4 Audio/Visual Streams - + <> IETF RFC 3550, RTP: A Transport Protocol for Real-Time Applications <> IETF RFC 3551, RTP Profile for Audio and Video Conferences with Minimal Control @@ -280,6 +279,8 @@ <> IETF RFC 8285, A General Mechanism for RTP Header Extensions <> + AV1 Bitstream and Decoding Process Specification + <> RTP Payload Format For AV1 <> GZIP file format specification version 4.3