Total conversation

In telecommunication, Total Conversation encompasses the use of a Total Conversation service which is defined in ITU-T recommendation F.703 as “An audiovisual conversation service providing bidirectional symmetric real-time transfer of motion video, text and voice between users in two or more locations”.

In simple terms, a Total Conversation service allows people in two or more locations to:-

• See each other;
• hear each other; and
• send text to each other,

all in real-time.

Application of Total Conversation

• Conference call for businesses will need to use audio and text and may use video to share documents.
• Deaf people using sign language would be more than satisfied to call each other or to call a Video Relay Service using text and video.
• Hard of hearing people need to access a Text Relay Service with an audio plus text call in order to be able to speak but also to receive captions.
• Text only call might be convenient in situation when audio communication is not permitted or dangerous such as an hostage situation or during a music concert.
• Support and hot line might be contacted with an audio only call and add a video stream if the user needs to show the actual issue he or she is facing on a device.

Total Conversation and Universal Design

Total Conversation is a straightforward application of Universal Design principles applied to telecommunication field. This concept brings communication services to the broadest range of population including deaf people, hard or hearing people but also people who have speech impairment and also ... regular users. It is an enhancement of call services that provides a better experience to all.

Implementation of the concept

Available implementations

A number of European companies including Aupix, IVèS and but also Orange Labs produced implementations. These are mostly used to provide Relay Services for deaf people.

The REACH112 European Project

The REACH112 include most of these companies mentioned above and several European companies offering services to deaf people as well as Emergency services. It is named after the "112" number which is the European emergency number like the 911 in the USA. The purpose of the project is to establish pilots in five countries in order to test Total Conversation on the field with several thousands users and for three usages:

• European wide person to person calls
• Total Conversation Relay Services for deaf people
• Total Conversation used for emergency calls.

One of the important outcome of the project is the delivery of a technical document describing how Total Conversation should be implemented. This is done in the deliverable D3.2 Platform Specification. This document targets the videophone manufacturers but also the telecommunication regulators and people working on next generation emergency services (NG 112 in Europe)

Purpose of these specifications

These specifications describe:

• An interconnection interface between Total Conversation Service Providers including Relay Services.
• A user to network interface for videophone manufacturers.
• A call interface for Next Generation Emergency Services in Europe Europe including an information sharing capability.

Technical protocols used by Total Conversation are

• Session Initiation Protocol for call signalling,
• T.140 with an RFC 4103.
• Video codecs H.263 and preferably H.264.
• Use of Common Alerting Protocol to share information with Emergency Services.

Total Conversation defines three basic services

• seamless multimedia person to person calls including the ability to call regular telephone users.
• the ability to invoke a relay service by deaf or hard of hearing persons,
• the ability to call emergency services in Total Conversation mode.

Conversation Totale and IP Multimedia Subsystem

Total Conversation basically provide a multi-media call services. . IP Multimedia Subsystem (IMS) and MMTEL, too ! Why is there a new standard.

Firstly, Total Conversation can be defined as a pragmatic selection of existing standards related to (Session Initiation Protocol with the selection of audio, video and text codecs. It is a private initiative of services provider and technology vendors seeking interoperability in the broadtest sense.

Secondly, this can apply to existing and deployed SIP platform rather than future or next generation networks.

Thirdly, IMS is much more ambitious and define a whole architecture, including all internal interfaces and billing and physical infrastructure. Theses standards are more suitable for large telecommunication operators and their equipment vendors. This complexity has consequences:

• Very little UMTS release 5 networks fully supporting IMS are in production
• Multimedia call services defined by MMTEL are not translated in actual usable services on the market. An industry led initiative called Rich Communication Suite finally plans to do this .. when IMS will be rolled out in the networks.
• Rolling out a Total Conversation services needs investments that are very reduced compared to the IMS equivalent. However, both standard are close enough that interoperability between the two is an easy task.

External links

• Session Initiation Protocol (SIP)
• MMTEL Forum