VS:SVC - Revision history

Mhefeeda at 18:37, 2 July 2008

2008-07-02T18:37:15Z

Mhefeeda at 19:52, 26 June 2008

2008-06-26T19:52:45Z

Mhefeeda at 19:52, 26 June 2008

2008-06-26T19:52:15Z

Mhefeeda at 19:51, 26 June 2008

2008-06-26T19:51:29Z

Mhefeeda at 06:39, 26 June 2008

2008-06-26T06:39:05Z

Mhefeeda at 06:38, 26 June 2008

2008-06-26T06:38:00Z

Mhefeeda at 06:36, 26 June 2008

2008-06-26T06:36:42Z

Mhefeeda at 06:27, 26 June 2008

2008-06-26T06:27:13Z

Mhefeeda at 06:03, 25 June 2008

2008-06-25T06:03:23Z

Mhefeeda at 06:02, 25 June 2008

2008-06-25T06:02:59Z

New page

'''H.264/SVC Scalable Streams Management System'''

== Overview ==

A complete system for structuring, encoding, adapting, streaming, storing, and transcoding of video streams encoded by the state-of-the-art H.264/SVC coding standards.

== Ideas ==

* We want to create a system and/or API for handling SVC streams.

* Enhance our previous works in ToM 2008: http://www.cs.sfu.ca/~mhefeeda/Papers/tom08.pdf

* We want to demonstrate the benefits of the system for the administrators (ease and efficiency) and users (quality)

* Need to explore market needs and interest. What are the current practices for managing many video streams?

* Who can benefit from the system? VoD Systems, YouTube, Google Videos, CBC ...

== Links and References ==

* [http://www.videolan.org/developers/x264.html Decent Open Source H.264/AVC Encoder]

* Open Source SVC coders ??

* Other people doing this?

← Older revision		Revision as of 18:37, 2 July 2008
Line 1:		Line 1:
	'''H.264/SVC Scalable Streams Management System'''		'''H.264/SVC Scalable Streams Management System'''
		+
		+
		+	Back to the main [[VS:Video Semantics]]

@@ Line 44: / Line 44: @@
 * Open Source SVC coders: Reference Software Implementation
-* Schwarz et al., [ http://nsl.cs.sfu.ca/teaching/08/820/SMW07.pdf Overview of the Scalable Video Coding Extension of the H.264/AVC Standard], IEEE Transactions on Circuits and Systems for Video Technology, 17(9), Sep 2007
+* Schwarz et al., [http://nsl.cs.sfu.ca/teaching/08/820/SMW07.pdf Overview of the Scalable Video Coding Extension of the H.264/AVC Standard], IEEE Transactions on Circuits and Systems for Video Technology, 17(9), Sep 2007
 ** In the above reference, [40] presents an algorithm to control the bit rates of layers in SVC, [46] describes extracting substreams, [47] describes re-writing SVC streams to AVC streams.

@@ Line 33: / Line 33: @@
 * Assume we have a full quality scalable video stream, with temporal, spatial, and quality layers. Given a client with specific resources (screen resolution, estimated BW, CPU, battery), what is the best substream should we stream to that client? E.g., is it better to reduce the frame rate, resolution, or the PSNR quality? How about a mix? This is quite useful and could be a differentiating edge for our technology (good patent). Of course the right mix will depend on the terminal (PDA vs dialup desktop). This research problem will rely on previous works on subjective quality measures and user studies. Then, we design a systematic method for determining the best substream. This problem is also related to the previous one. I have not yet seen works on this problem. If we come up with a good solution for this problem, it could make a separate product by itself.
-* SVC peer-assisted Content Distribution Network (pCDN). This will extend my current pCDN system to support SVC streams. Research problems include: coordinating multiple senders with different substreams to serve a client. See our previous work on MPEG-4 FGS streams in TOMCCAP 2008. Another (academic) problem is analyzing the system stream capacity and average client quality with and without SVC. Analytic and/or simulation analysis is needed. In addition, we may be able to get real data from CBC after they start using our pCDN system, insha'a ALLAH.
+* SVC peer-assisted Content Distribution Network (pCDN). This will extend my current pCDN system to support SVC streams. Research problems include: coordinating multiple senders with different substreams to serve a client. See our previous work on MPEG-4 FGS streams in [http://www.cs.sfu.ca/~mhefeeda/Papers/tomccap08_fgs.pdf TOMCCAP 2008]. Another (academic) problem is analyzing the system stream capacity and average client quality with and without SVC. Analytic and/or simulation analysis is needed. In addition, we may be able to get real data from CBC after they start using our pCDN system, insha'a ALLAH.
 * Can we use SVC in live streaming, e.g., broadcasting popular sports event to many '''heterogeneous''' clients? Do we need multiple multicast trees? Other structures? Very interesting research problem as well.

@@ Line 29: / Line 29: @@
 == Research Problems (Papers and/or Patents) ==
-* Design an algorithm to compute the best way (how many layers, types of layers, size of each layer, etc) to encode an SVC stream for an expected client distribution.  Enhance our previous works in ToM 2008: http://www.cs.sfu.ca/~mhefeeda/Papers/tom08.pdf
+* Design an algorithm to compute the best way (how many layers, types of layers, size of each layer, etc) to encode an SVC stream for an expected client distribution.  Enhance our previous works in [http://www.cs.sfu.ca/~mhefeeda/Papers/tom08.pdf ToM 2008]. See also Schwarz and Wiegand, R-D Optimized Multi-Layer Encoder Control for SVC, In Proc. of IEEE ICIP 2007.
 * Assume we have a full quality scalable video stream, with temporal, spatial, and quality layers. Given a client with specific resources (screen resolution, estimated BW, CPU, battery), what is the best substream should we stream to that client? E.g., is it better to reduce the frame rate, resolution, or the PSNR quality? How about a mix? This is quite useful and could be a differentiating edge for our technology (good patent). Of course the right mix will depend on the terminal (PDA vs dialup desktop). This research problem will rely on previous works on subjective quality measures and user studies. Then, we design a systematic method for determining the best substream. This problem is also related to the previous one. I have not yet seen works on this problem. If we come up with a good solution for this problem, it could make a separate product by itself.
@@ Line 43: / Line 43: @@
 * Open Source SVC coders: Reference Software Implementation

@@ Line 22: / Line 22: @@
 * Other people working/using/pushing SVC
-** [http://www.vidyo.com Vidyo]: they are doing video conferencing using SVC. They sell complete systems. We would be selling backend software to enable SVC video conferencing, not complete systems. So, our library could be used by companies like Sony, Cisco, and others to enhance their video conference products. At a latter stage, we may do the same as Vidyo do and compete with them (on the price, may be).
+** [http://www.vidyo.com Vidyo]: they are doing video conferencing using SVC. They sell complete systems. We would be selling backend software to enable SVC video conferencing, not complete systems. So, our library could be used by companies like Sony, Cisco, and others to enhance their video conference products. At a latter stage, we may do the same as Vidyo and compete with them (on the price, may be).
 ** Some chip manufacturers (e.g., [http://www.dspdesignline.com/products/206902239 Stretch] have started producing products to process SVC streams.  Implies that SVC is a promising technology.

← Older revision		Revision as of 06:38, 26 June 2008
Line 24:		Line 24:
	** [http://www.vidyo.com Vidyo]: they are doing video conferencing using SVC. They sell complete systems. We would be selling backend software to enable SVC video conferencing, not complete systems. So, our library could be used by companies like Sony, Cisco, and others to enhance their video conference products. At a latter stage, we may do the same as Vidyo do and compete with them (on the price, may be).		** [http://www.vidyo.com Vidyo]: they are doing video conferencing using SVC. They sell complete systems. We would be selling backend software to enable SVC video conferencing, not complete systems. So, our library could be used by companies like Sony, Cisco, and others to enhance their video conference products. At a latter stage, we may do the same as Vidyo do and compete with them (on the price, may be).

−	** Some chip manufacturers (e.g., [http://www.dspdesignline.com/products/206902239 Stretch) have started producing products to process SVC streams. Implies that SVC is a promising technology.	+	** Some chip manufacturers (e.g., [http://www.dspdesignline.com/products/206902239 Stretch] have started producing products to process SVC streams. Implies that SVC is a promising technology.

@@ Line 12: / Line 12: @@
 * We want to demonstrate the benefits of the system for the administrators (ease and efficiency) and users (quality)
 * If we have the above SVC management system, we can do many things, e.g., video conference tools, streaming servers (out of the box), SVC-enabled peer-assisted content distribution networks, SVC mobile TV, ...
@@ Line 22: / Line 24: @@
 ** [http://www.vidyo.com Vidyo]: they are doing video conferencing using SVC. They sell complete systems. We would be selling backend software to enable SVC video conferencing, not complete systems. So, our library could be used by companies like Sony, Cisco, and others to enhance their video conference products. At a latter stage, we may do the same as Vidyo do and compete with them (on the price, may be).
-** Some chip manufacturers (e.g., Stretch) have started producing products to process SVC streams.
+** Some chip manufacturers (e.g., [http://www.dspdesignline.com/products/206902239 Stretch) have started producing products to process SVC streams.  Implies that SVC is a promising technology.
@@ Line 40: / Line 42: @@
 * [http://www.videolan.org/developers/x264.html x.264 -- Decent Open Source H.264/AVC Encoder]
-* Open Source SVC coders ??
+* Open Source SVC coders: Reference Software Implementation

@@ Line 9: / Line 9: @@
 == Ideas ==
-* We want to create a system and/or API for handling SVC streams.
+* We want to create a system and/or APIs for handling SVC streams.
-* Enhance our previous works in ToM 2008: http://www.cs.sfu.ca/~mhefeeda/Papers/tom08.pdf
+* We want to demonstrate the benefits of the system for the administrators (ease and efficiency) and users (quality)
-* We want to demonstrate the benefits of the system for the administrators (ease and efficiency) and users (quality)
+* If we have the above SVC management system, we can do many things, e.g., video conference tools, streaming servers (out of the box), SVC-enabled peer-assisted content distribution networks, SVC mobile TV, ...
 * Need to explore market needs and interest. What are the current practices for managing many video streams?
-* Who can benefit from the system?  VoD Systems, YouTube, Google Videos, CBC ...
+* Who can benefit from the system?  VoD Systems, YouTube, Google Videos, CBC, Nokia, Rogers (mobile TV), ...
@@ Line 25: / Line 41: @@
 * Open Source SVC coders ??