Media Resource Control Protocol: Difference between revisions

Revision as of 11:35, 11 January 2008

Latest revision as of 08:35, 26 July 2022

(39 intermediate revisions by 30 users not shown)

Line 1:

{{short description|Audio communication protocol}}

'''MRCP''' is the '''Media Resource Control Protocol''' proposed to the [[IETF]]. It is a communication protocol which allows speech servers to provide various speech services (such as [[speech recognition]] and [[speech synthesis]]) to its clients. Typically, this means the server software will be running on one computer and clients can send MRCP messages to the server over a network, usually on top of another protocol, such as [[RTSP]] or [[Transmission Control Protocol|TCP]].

{{primary sources|date=September 2011}}

'''Media Resource Control Protocol''' ('''MRCP''') is a communication protocol used by speech servers to provide various services (such as [[speech recognition]] and [[speech synthesis]]) to their clients. MRCP relies on another protocol, such as [[Real Time Streaming Protocol]] (RTSP) or [[Session Initiation Protocol]] ([[Session Initiation Protocol|SIP]]) for establishing a control session and audio streams between the client and the server.

ItMRCP isuses ina the samesimilar style of clear-text signaling as [[HTTP]] and many other Internet protocols, wherein which each message contains 3 sections: a first-line, a header and a body. The first line indicates the type of message as well as information such as response codes. The header contains a number of lines, each in the format '''<nowiki><header>: <data></nowiki>'''. The body, whose length is specified by the header, contains the details of the message.

Like HTTP, MRCP hasuses requestsa request (usually issued by the client) and responses,response whichmodel. Responses may simply acknowledge receipt of the request or give other information regarding its processing. For example, an MRCP client may request to send some audio [[data]] for processing (say, for speech recognition), to which the server could respond with a message containing a suitable [[TCP and UDP port|port number]] to send the data, (since MRCP does not have support for audio data specifically, as this would have to be handled by some other protocol, such as [[Real-time Transport Protocol|RTP]] (RTP).

ThereMRCP areprotocol twoversion versions2 ofhas thebeen MRCPapproved protocolas an [[Request for Comments|RFC]]. Version 2 uses [[Session Initiation Protocol|SIP]] asfor managing sessions and audio streams between the controlserver protocoland the clients, whereas version 1 usesdid [[Realnot Timespecify Streamingthe Protocol|RTSP]]underlying protocol.

MRCP has been adopted by a wide range of commercial speech servers, such as [[Verbio Technologies]], [https://vernacular.ai/viva Skit.ai's VIVA], [[Microsoft Speech Server]], [[LumenVox Speech Engine]], [[ReadSpeaker]] speechServer MRCP, [[Nuance Communications|Nuance]] Recognizer and Vocalizer, Sestek TTS, Sestek Call Steering as well as commercial [[Interactive Voice Response]] software such as Blueworx Voice Response..

==External links==

* RFC{{IETF RFC|4463|link=no}}, A Media Resource Control Protocol (MRCP)

* {{IETF RFC|6787|link=no}}, Media Resource Control Protocol version 2 (MRCPv2)

* [http://www.ietf.org/internet-drafts/draft-ietf-speechsc-mrcpv2-15.txt MRCP version 2 IETF draft specification, version 15] <!-- This url is subject to changes -->

* [http://www.unimrcp.org UniMRCP], An open source cross-platform MRCP implementation

[[Category: Internet protocols]]

[[Category:Application layer protocols]]

{{compu-soft-stub}}

{{multimedia-software-stub}}

[[de:Media Resource Control Protocol]]