Content for TS 23.333 Word version: 18.1.0
1…
4
5…
5.8…
5.12…
5.14…
5.20…
5.24…
6…
6.1.8…
6.2…
6.2.3…
6.2.4…
6.2.5
6.2.6…
6.2.7…
6.2.8…
6.2.9…
6.2.10…
6.2.10.2.7
6.2.10.3…
6.2.11…
6.2.13…
6.2.13.2.6…
6.2.14…
6.2.15…
6.2.16…
6.2.18…
6.2.19…
6.2.19.3…
6.2.20…
6.2.21…
6.2.22…
6.2.23
6.2.24…
7
8…
8.11…
8.20
8.21
8.22
8.23…
8.30…
8.39…
8.45…
8.56…
6.2.16 Coordination of Video Orientation
6.2.17 Support of generic image attributes
6.2.17.1 General
6.2.17.2 Indication of generic image attributes
...
...
6.2.16 Coordination of Video Orientation |R12| p. 127
Figure 6.2.16.1 shows the message sequence chart example for indicating extended RTP header for the Coordination of Video Orientation (CVO).
When the MRFC requests the IMS resources from the MRFP, the MRFC may optionally request the MRFP to support the RTP header extension capability as defined in RFC 5285.
6.2.17 Support of generic image attributes |R12| p. 128
6.2.17.1 General p. 128
The MRFC and the MRFP may support the media-level SDP image attribute defined in RFC 6236 as required by TS 26.114.
If the MRFP and the MRFC support the negotiation of the image size and if the MRFC receives the SDP image attribute(s) "a=imageattr" then the MRFC may send the generic image attribute parameter to the MRFP when seizing or modifying a termination.
The list of image sizes per payload type supported by the MRFP shall be preconfigured in the MRFC. If the image sizes received within an SDP body on the Mr interface are not all supported by the MRFP then the MRFC shall only send the list of corresponding MRFP supported image sizes to the MRFP. If no image size is supported by the MRFP, the MRFC shall not send the generic image attribute parameter to the MRFP.
6.2.17.2 Indication of generic image attributes p. 128
The MRFC may include the generic image attributes to the MRFP. The example sequence is shown in Figure 6.2.17.2.1.
Figure 6.2.17.2.1: Request to reserve IMS resources with generic image attribute
(⇒ copy of original 3GPP image)
(⇒ copy of original 3GPP image)
