Enhanced MRCP Protocol for Speech Engine Allocation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The Media Resource Control Protocol (MRCP) lacks features for session control management, media management, reliable sequencing and delivery, and server or resource addressing, which are essential for efficient communication and resource allocation in telephony applications, leading to inefficiencies and processing delays.

Innovation Solution

An enhanced messaging protocol that includes telephone call identification and audio source/sink information, allowing for turn-based allocation of speech engines and enabling end-to-end call tracing, with message formats that specify a call identifier and audio Uniform Resource Identifiers (URIs) for efficient communication between speech engines and media converting components.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If MRCP protocol is used for media resource control, then speech engine allocation and control is enabled, but processing delays occur and efficiency is reduced due to lack of session control management and reliable sequencing

Engineering Contradiction:
Improvespeech engine utilization efficiencyVSAvoidprocessing delays
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent applies preliminary action by establishing session control management and reliable sequencing mechanisms before media resource allocation occurs. The enhanced MRCP protocol pre-defines message formats with sequence numbers, timing parameters, and session identifiers that prepare the system for efficient resource allocation and reduce processing delays during actual speech engine utilization.

Inventive Principle:
Principle #10Preliminary action

2Ease of operation

If MRCP protocol is used for media resource control, then communication with media resources is enabled, but call tracing and debugging capabilities are insufficient due to lack of session control management

Engineering Contradiction:
Improvecall tracing capabilityVSAvoidcall identity information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent applies feedback by incorporating session control management that provides comprehensive call tracing capabilities. The enhanced protocol includes message formats with session identifiers, sequence numbers, and timing information that feed back through the system, enabling complete end-to-end call tracing and debugging while preserving all call identity information.

Inventive Principle:
Principle #23Feedback

3Reliability

If traditional MRCP message format is used, then simple media resource control is achieved, but reliable sequencing and delivery of media messages is not ensured

Engineering Contradiction:
Improvemessage delivery reliabilityVSAvoidmessage format complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent applies segmentation by dividing the enhanced MRCP message format into distinct functional components: session control fields, sequence numbering fields, timing parameters, and media resource control fields. This segmentation allows the protocol to provide reliable sequencing and delivery through structured message formats while maintaining manageable complexity through modular organization of control elements.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7552225B2Enhanced media resource protocol messages
Publication Date: 2009.06.23 MICROSOFT TECHNOLOGY LICENSING LLC
  • US7552225B2 patent drawing
  • US7552225B2 patent drawing
  • US7552225B2 patent drawing

AI summary

A communication system can include a telephony application server and at least one speech engine, where the system uses a standardized messaging protocol that specifies a standard for media resources. The telephony application server can have at least one voice server component. The speech engines can be allocated to handle requests for the voice server component on a per turn basis. The standardized messaging protocol can define a message format for request messages sent from the voice server component to a selected speech engine, a message format for response messages sent from the speech engine to the voice server component, and a message format for event messages sent from the speech engine to the voice server component. Each message format can include a field for a call identifier.