L.2.2 Video element

26.2343GPPProtocols and codecsRelease 17Transparent end-to-end Packet-switched Streaming Service (PSS)TS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

L.2.2.1 Inclusion of the video element in SVG content

The video element should be included within a "switch" element. The feature string for video could be

1. http://www.w3.org/TR/SVG12/feature#3GPPTransformedVideo

2. the feature string for video is http://www.w3.org/TR/SVG12/feature#3GPPVideo

3. or the alternate representation of a "video" element could be an image.

EXAMPLE:

The above example shows a transformed video. If the PSS client supports "TransformedVideo", the video shall be transformed, if not, a video-enabled PSS client shall display the video without scaling and rotation ("pinned"). Finally, an image shall be displayed if neither one of the above cases is possible at the PSS client.

L.2.2.2 Transformation of video

SVG Tiny 1.2 supports the video element and proper rendering requires video to be subject to transformation just like any other graphics object. This implies that any arbitrary transform can be applied to embedded video content. Dynamic transformation of video content is an expensive operation and therefore would largely (and negatively) impact the frame rate of animated SVG content. This feature is also known to be very complex to be supported among most of the current mobile devices.

SVG Tiny 1.2 does not require transformed video. As a consequence transform video is optional. When optionally applied to video elements, the following transformations and the animations thereof are applicable in increasing complexity order:

1. Translation of the video element shall be applied.

2. Rotation of video by 90°/-90° degrees is permitted.

3. Scaling of the video element is permitted.

NOTE: PSS clients may decide not to apply scaling through the transformBehavior attribute.

Dynamic transformation of video content should be avoided. Overlaying graphics on video content is considered a very expensive operation and may have significant consequences, such as lack of synchronization and degraded output quality and performance.

The video rendering features are highly dependent on the host capabilities and one may expect potential differences between implementations. Content creators should be very cautious when dealing with such functionality.