Tech-invite3GPP-SpecsFeaturesEntitiesInterfacesSBIsIdentifiersTi+Search in Tech-invite

21222324252627282931323334353637384‑5x
Top   in Index   Prev   Next

TS 26.114 (SA4)
Multimedia Telephony Service for IMS (MTSI) –
Media Handling and Interaction

use "3GPP‑Page" to get the Word version
use "ETSI‑search" to get the PDF version
the ToC, based on the Word version, is reproduced for a better overview
V16.3.0 (Wzip)2019/09  431 p.
V15.7.0 (PDF)2019/09  411 p.
V14.11.02019/09  406 p.
V13.10.02019/09  380 p.
V12.17.0  2019/06  315 p.
V11.12.0  2016/09  277 p.
V10.11.0  2016/09  275 p.
V9.15.0  2016/09  233 p.
V8.15.0  2016/09  169 p.
V7.17.0  2012/06  127 p.

Rapporteur:  Dr. Jung, Kyunghun

Multimedia Telephony Service for IMS (MTSI), here also referred to as Multimedia Telephony, is a standardized IMS telephony service that builds on the IMS capabilities to establish multimedia communications between terminals within and in-between operator networks. The terminals connect to the IMS using either a fixed access network or a 3GPP access network.
The objective of defining a service is to specify the minimum set of capabilities required in the IP Multimedia Subsystem to secure multi-vendor and multi-operator inter-operability for Multimedia Telephony and related Supplementary Services. The objective also includes defining procedures for inter-working between different clients and networks.
The user experience of multimedia telephony is expected to be equivalent to or better than corresponding circuit-switched telephony services. Multimedia telephony also exploits the richer capabilities of IMS. In particular, multiple media components can be used and dynamically added or dropped during a session.
The present document specifies a client for the Multimedia Telephony Service for IMS (MTSI) supporting conversational speech (including DTMF), video and text transported over RTP with the scope to deliver a user experience equivalent to or better than that of Circuit Switched (CS) conversational services using the same amount of network resources. It defines media handling (e.g. signalling, transport, jitter buffer management, packet-loss handling, adaptation), as well as interactivity (e.g. adding or dropping media during a call). The focus is to ensure a reliable and interoperable service with a predictable media quality, while allowing for flexibility in the service offerings. The present document describes two client types:
  • An MTSI client in terminal which uses a 3GPP access (LTE, HSPA, or EGPRS) to connect to the IMS. These clients are described in Clauses 5 - 17 and Annexes A - M.
  • An MTSI client in terminal which uses a fixed access (corded interface, fixed-wireless interface, e.g. Wi-Fi, Bluetooth or DECT/NG DECT) to connect to the IMS. These clients are described in Clause 18.
MTSI clients using 3GPP access and MTSI clients using fixed access have many common procedures for the media handling. This specification aligns the media handling by using cross references whenever possible. This does not mean that 3GPP terminals must support fixed access, nor does it mean that fixed terminals must support 3GPP access.
The scope includes maintaining backward compatibility in order to ensure seamless inter-working with existing services available in the CS domain, such as CS speech and video telephony, as well as with terminals of earlier 3GPP releases. In addition, inter-working with other IMS and non-IMS IP networks as well as traditional PSTN is covered.
The client may also support the IMS Messaging service and Group 3 facsimile transmission. The scope therefore also includes media handling for non-conversational media using MSRP and UDPTL-based Facsimile over IP (FoIP). The specification is written in a forward-compatible way in order to allow additions of media components and functionality in releases after Release 7.
NOTE 1: MTSI clients can support more than conversational speech, video and text, which is the scope of the present document. See TS 22.173 for the definition of the Multimedia Telephony Service for IMS.
NOTE 2: TS 26.235 and TS 26.236 do not include the specification of an MTSI client, although they include conversational multimedia applications. Only those parts of TS 26.235 and TS 26.236 that are specifically referenced by the present document apply to Multimedia Telephony Service for IMS.
NOTE 3: The present document was started as a conclusion from the study in TR 26.914 on optimization opportunities in Multimedia Telephony for IMS (TR 22.973).
NOTE 4: For ECN, the present specification assumes that an interface enables the MTSI client to read and write the ECN field. This interface is outside the scope of this specification.

short Table of Contents for  TS 26.114  Word version:   16.3.0

each title links to the equivalent title in the full ToC

 

Here   Top

 

1  Scope Word-p. 17
2  ReferencesWord-p. 17
3  Definitions and abbreviationsWord-p. 24
4  System descriptionWord-p. 27
5  Media codecsWord-p. 30
6  Media configurationWord-p. 34
7  Data transportWord-p. 63
8  Jitter buffer management in MTSI clients in terminalsWord-p. 81
9  Packet-loss handlingWord-p. 86
10  AdaptationWord-p. 92
11  Front-end handlingWord-p. 116
12  Inter-workingWord-p. 117
13Void
13a  Media types, codecs and formats used for MSRP transportWord-p. 130
14  Supplementary servicesWord-p. 130
15  Network preference management objectWord-p. 131
16  Quality of Experience [R8]Word-p. 145
17  Management of Media Adaptation [R9]Word-p. 162
18  MTSI client in terminal using fixed access [R12]Word-p. 193
19  Additional bandwidth information [R13]Word-p. 198
A  Examples of SDP offers and answersWord-p. 206
B  Examples of adaptation scenariosWord-p. 282
C  Example adaptation mechanisms for speechWord-p. 283
D  Reference delay computation algorithmWord-p. 301
E  QoS profilesWord-p. 303
F (Normative)  Void
G (Normative)  DTMF eventsWord-p. 337
H  Network Preference Management Object Device Description FrameworkWord-p. 341
I  QoE Reporting Management Object Device Description Framework [R8]Word-p. 342
J  Media Adaptation Management Object Device Description Framework [R9]Word-p. 343
K  Computation of b=AS for AMR and AMR-WB [R10]Word-p. 344
L (Normative)  Facsimile transmission [R11]Word-p. 354
M  IANA registration information for SDP attributes [R12]Word-p. 359
N  Computation of b=AS for Video Codec [R12]Word-p. 364
O  IANA registration information for RTP Header Extensions [R12]Word-p. 365
P  Video packet loss handling operation principles and examples [R12]UpWord-p. 366
Q  Computation of b=AS for EVS [R12]Word-p. 370
R  IANA registration information for RTCP Feedback Message Types [R13]Word-p. 374
S (Normative)  Multi-party Multimedia Conference Media Handling [R13]Word-p. 375
T  SDP examples for Multi-party Multimedia Conference Media Handling [R13]Word-p. 385
U  IANA registration information for media types [R14]Word-p. 406
V  Delay Adaptation and Example Uses of DBI Signaling [R16]Word-p. 407
W (Normative)  Coverage and Handoff Enhancements using Multimedia Error Robustness (CHEM) [R16]Word-p. 414
X  Example Maximum Packet Loss Rate (Max. PLR) Values for Setting CHEM Handover Thresholds [R16]Word-p. 419
Y  Change historyWord-p. 426

Up   Top