11 Registered Types

26.1423GPPDynamic and Interactive Multimedia Scenes (DIMS)Release 17TS

11.1 RTP Payload format MIME Type

Type name: video

Subtype name: richmedia+xml

Required parameters:

– Version-profile – A value between 0 and 255 specifying the profile of DIMS used, for example the value indicating Mobile Profile.

– Level – A value between 0 and 255 specifying the minimum DIMS level needed to be able to display the scene.

Optional parameters:

– stream-type – takes the value "primary" for primary streams (in which every random access point is a scene), and the value "secondary" for secondary streams. Secondary streams are not normally playable by themselves, outside the context of the scene(s) they are designed to update. The default value is "primary".

– contains-redundant – takes the value "main" if the stream contains only DIMS Units with is-redundant set to 0, the value "redundant" if the stream contains only DIMS Units with is-redundant set to 1, and takes the value "main+redundant" if both occur. Note that streams containing only redundant units must be linked to the matching stream carrying main DIMS Units (see subclause 7.3.4). The default value is "main+redundant".

– text-encoding – is a string enclosed in double-quotes with possible values taken the XML specification for character encoding in entities (e.g. subclause 4.3.3 of [25]). It describes the text encoding after the content has been decompressed (e.g. after deflating). The default value is "UTF-8" [9]. This field is only applicable if the content is transmitted as (possibly encoded) text.

– content-script-types – is a string enclosed in double-quotes that identifies the scripting languages used. It is formatted as a comma-separated list of MIME types [18] from the IANA registry, such as "application/ecmascript" (see [13]). It shall provide a complete listing of the script types that the terminal must support in order to process the stream. If this attribute is not present, the set of required script types is unknown. If this attribute contains the empty string, then the stream does not require any script processing.

– content-coding – this field provides the identification of the compression scheme. It is a string specifying the encoding (compression) format of the content. It is defined in the same way as the content-coding header in HTTP (subclause 3.5 of [12]). The default value is the empty string.

– useFullRequestHost takes the value "0" or "1"; the definition of this parameter is in subclause 5.5.2. The default value is "1".

– pathComponents takes a value between "0" and "15"; the definition of this parameter is in subclause 5.5.2. The default value is "15".

Encoding considerations:

– This media type is currently only defined for transport via RTP.

Security considerations:

– RTP packets using the payload format defined in the present document are subject to the security considerations discussed in the RTP specification [15] and any applicable RTP profile, e.g., AVP [21].

Interoperability considerations:

– None.

Published specification:

– 3GPP TS 26.142.

Applications that use this media type:

– DIMS Streaming applications.

Additional information:

– Magic number(s): None.

– File extension(s): None.

– Macintosh file type code(s): None.

Person and email address to contact for further information:

– Clinton Priddle.

– clinton.priddle@ericsson.com.

– Multimedia Technologies, Ericsson.

Intended usage:

– COMMON.

Restrictions on usage:

– None.

Author:

– 3GPP SA4 WG.

Change controller:

– 3GPP TSG SA.

11.2 ‘Codecs’ Parameter for 3GP files

When DIMS content is supplied in 3GP files which are identified by MIME type, the ‘codecs’ parameter defined in [14] may be used to indicate that DIMS content is present. The codecs parameter takes the sample entry name as defined above (that is, ‘dims’).

Annex A (normative):
Conformance Criteria

DIMS constructs scenes which are possibly updated over time. Conformant terminals shall support the delivery of the scenes and updates in formats specified in the ‘compression’ subclause above, and in the transport environments specified in the ‘transport’ subclause.

For the initial scene, a DIMS Scene can be extracted from the transport, and de-compressed if necessary, yielding an XML document. This XML is referred to here as the "initial DIMS document". Similarly, after all updates for a given instant have been applied to the scene tree, there is logically an XML document that is equivalent to the scene DOM tree; these are called "subsequent DIMS documents" here.

Initial and subsequent DIMS documents shall conform to all of:

– the conformance requirements in Appendix D of [1]; with the following exceptions:

– The conformance criteria in the SVG specification regarding codecs do not apply for the DIMS media type.

– Clause D.4 is not in scope for DIMS.

– Clause D.7 is not in scope for DIMS.

– the conformance requirements of the LASeR Commands and LASeR scene extensions as specified in [27] and [28]

– the limitations of the profile and level indications under which they are delivered.

Conformance of the DIMS extensions is for further study.

Annex B (informative):
Change history

Change history
Date	TSG #	TSG Doc.	CR	Rev	Subject/Comment	Old	New
2007-06	36	SP-070312			Approved at SA#36 Plenary		7.0.0
2007-09	37	SP-070632	0006	1	Technical corrections in the DIMS specification	7.0.0	7.1.0
2007-12	38	SP-070764	0007		Reference correction in the DIMS specification	7.1.0	7.2.0
2008-12	42				Version for Release 8	7.2.0	8.0.0
2009-06	44	SP-090247	0008	2	DIMS Mobile profile level 10 review and clarification	8.0.0	8.1.0
2009-09	45	SP-090569	0011		Clean-up corrections	8.1.0	8.2.0
2009-12	46				Version for Release 9	8.2.0	9.0.0
2011-03	51				Version for Release 10	9.0.0	10.0.0
2012-09	57				Version for Release 11	10.0.0	11.0.0
2014-09	65				Version for Release 12	11.0.0	12.0.0
2015-12	70				Version for Release 13	12.0.0	13.0.0

Change history
Date	Meeting	TDoc	CR	Rev	Cat	Subject/Comment	New version
2017-03	75					Version for Release 14	14.0.0
2018-06	80					Version for Release 15	15.0.0
2020-07	–	–	–	–	–	Update to Rel-16 version (MCC)	16.0.0
2022-04	–	–	–	–	–	Update to Rel-17 version (MCC)	17.0.0