1. Universal noun

   API       Application programming interface

   ASR      Automatic speech recognition

   GRXML Grammar XML

   MRCP   Media resource control protocol

   RTCP    Real time control protocol

   RTP      Real time transport protocol

   SIP       Session initiation protocol

   TTS       Text-to-speech

   URI       Universal resource identifier

   XML      Extensible markup language

2. System noun

   IMS30 iFLY MRCP Server 3.0

   iSP21  iFLY Speech Platform 2.1

   iSP20  iFLY Speech Platform 3.0

3. Component noun

   MRS

    MRCP Server, offers media resource control service.

  MRC

    MRCP Client, responsible for client application and MRS communication.

   MCT

    Traditional MRCP Client, to offer MRC based TTS interface for client application.

   MRM

    MRCP Resource Management Server mainly offers load balance function.

    IMS30 system components include:

   MRCPv2 server

   Integration interface of engine TTS and ASR

   Client of MRCPv2 / v1

   Test, demo and management tool

    The network structure of IMS30 platform under typical network environment as follows:

IMS3.0 platform is designed to operate on the hundred mega/ kilomega Ether LAN supporting TCP / IP protocol. On the SIP protocol-based facilities such as SIP proxy server and SIP registration server, IMS30 operation needs the support of ISP protocol. Watcher Client is a standard webpage browser, can be connected to any MRS to check its running status.

Neither SIP component nor TTS / ASR engine is a part of IMS30.
IMS30 platform can operate on multiple subnetworks, if appropriate SIP gateway and SIP position server are offered in the network. MRCP 's Resource Channel is a single-broadcasting based on TCP, which can be connected and communicated across multiple network sections. The only restriction is, if RTP 's Media Channel is a multiple broadcasting based on UDP, the Router among network sections under intercommunication must support multiple broadcasting retransmission.