Foreword

26.1403GPPMedia formats and codecsMultimedia Messaging Service (MMS)TS

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

This Technical Specification has been produced by the 3^rd Generation Partnership Project (3GPP).

The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:

Version x.y.z

where:

x the first digit:

1 presented to TSG for information;

2 presented to TSG for approval;

3 or greater indicates TSG approved document under change control.

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.

z the third digit is incremented when editorial only changes have been incorporated in the specification;

The 3GPP Multimedia messaging service (MMS) specification consists of three 3GPP TSs; 3GPP TS 22.140, 3GPP TS 23.140 and the present document. The TS 3GPP TS 22.140 [22]provides a set of requirements which shall be supported for the provision of non real-time multimedia messaging service, seen primarily from the subscriber’s and service providers’ points of view. The TS 23.140 [23] identifies the functional capabilities and information flows needed to support the MMS. The present document provides the details of media types, formats and codecs used by the MMSservice

The issue of codecs ad for MMS services has been addressed initially in TS 23.140, owned by the 3GPP T2 group. During the TSG-T WG2 group meeting in Edinburgh in September 2001, the TSG-T WG2 group sent a Liaison statement (S4-AHP040) to the 3GPP SA WG4 group, requesting that the responsibility for the specification of codecs and formats to be used in MMS services is transferred to SA WG4 group starting with Release 5.

After the SA WG4 group agreed to take over this responsibility, and the present document is the result of such commitment on Release 6.

For the sake of interoperability and alignment it is important there is no contradiction between the recommendations made in the present document and in the 26.234 specification [14].