Intelligent voice converter

[0002] This application is related to and claims the benefit of co-pending applications Ser. No. 09/658,771, entitled “Voice Integrated System”; Ser. No. 09/658,781, entitled “Intelligent Voice Bridging”; and Ser. No. 09/659,233, entitled “Message Store Architecture”, all filed Sep. 11, 2000, the disclosures of which are incorporated herein by reference.

[0003] The present invention relates to the field of transcoding of voice data. Transcoding is the process of converting one format of the voice data into another.

[0004] Internet telephony, known as voice over IP (VOIP) is becoming a realistic, cost effective alternative to the traditional public switched telephone networks (PSTNs).

[0005] In general, most VOIP applications use a voice encoding format that is different from the voice encoding format used by PSTN networks. Because of the different voice formats used, many of the functionalities that exist for PSTN are not available to VOIP applications unless the functionality is built directly into the VOIP application.

[0006] Voice converters and transcoders (VCs) that convert voice data from one format to another are known and can be used to convert data supplied by a VOIP application to PSTN format to allow the VOIP application to utilize PSTN functionalities such as automatic speech recognition (ASR) and text to speech conversion (TTS). The VC can also convert the output of a PSTN functionality to VOIP format. Existing VCs provide such a service by using dedicated DSP resources. A dedicated DSP resource is an entity that is allocated to the voice channel at the very beginning of a process and remains allocated as long as the channel is in use. The DSP resources used to perform transcode operation are full duplex. Both PSTN as well as VOIP networks are also full duplex in nature. Hence to handle a full duplex network a full duplex DSP resource was created, dedicated and used.

[0007] Although almost all of the DSP resources are full duplex in nature, most human interaction is half-duplex in the nature and most of the applications operate based on this half-duplex interaction. For example, almost all of the users who use telecommunication applications such as voice mail and informational services applications do not talk as well as listen at the same time. Accordingly, it is not necessary for an application to dedicate and allocate DSP resources for the entire duration of the application.

[0008] Based on the above observations, all of these existing applications use the DSP resource to less than 50% of the their capabilities. From this it is evident that a improved voice converter that can utilize the DSP resources more effectively and efficiently is required. Further more such a system must be capable of handling huge number of subscribers.

[0009] By virtue of this invention it is now possible to economically mix and match various functional components from VOIP and PSTN networks.

[0010] According to one aspect of the present invention, method and a mechanism allows transcoding and scheduling two independent voice data streams from two distinct and different subscriber on to the same full duplex DSP resource.

[0011] In one embodiment the voice converter waits for a request for conversion resource on TCP/IP. Based on the type of transcoding that was requested it will allocate a half-duplex resource, perform a transcode operation, and send output data over a UDP interface.

[0012] According to another aspect of the invention, look-ahead buffers are utilized to mask network latency and provide a continuous stream of data to the DSP resources.

[0013] According to another aspect of the invention, data is transferred in packets having session numbers. The session numbers are utilized to identify different data streams using a single DSP resource.

[0014] A further understanding of the nature and advantages of the invention herein may be realized by reference to the remaining portions of the specification and the attached drawings.

[0015] FIG. 1 is a block diagram of a distributed client/server telecommunication system coupled to a managed VOIP network;

[0016] FIG. 2 is block diagram and flow chart of a preferred embodiment of the invention; and

[0017] FIG. 3 is a block diagram of the packet format used by a preferred embodiment.

[0018] FIG. 1 shows a distributed client server system, which is used to provide telecommunication application services to subscribers over managed VOIP network. This system is disclosed in the commonly assigned, co-pending application entitled INTEGRATED VOIP SYSTEM, which is hereby incorporated by reference for all purposes. This diagram shows the use of a voice converter to integrate TTS and ASR subsystems.

[0019] VC (Voice Converter): VC is a server that can convert one voice data format into another. For this particular embodiment the VC converts pulse code modulation (PCM) voice data (PSTN type data) into G723.1 format (VOIP type data) and vice versa.

[0020] GAS (Gateway Access Server): GAS is the server that runs the telecommunication applications. It has a functional component called voice bridging that enables external systems and features to be integrated into the data path of the application running on the GAS.

[0021] TTS (Text To Speech Server): The TTS server is responsible for converting text into speech that can be played to the user. Some of the applications that use this feature implement listening to email and other text based content from the phone.

[0022] ASR (Automatic Speech Recognition): The ASR server is responsible for recognition of voice data sent to it and translating it to text that is sent back to the requester.

[0023] Existing TTS and ASR servers have been designed to provide functionality to PSTNs and therefore are designed to process voice data in PCM format. Accordingly, a VOIP application requires a VC to utilize these resources.

[0024] The art of transcoding using standard DSP resources, such as chip sets manufactured by Texas Instruments, is well known and will not be addressed in detail here. The intelligent voice converter of the present embodiment, enables VOIP applications to efficiently use external functional modules like TTS and ASR. In the following, an upstream resource transcodes a VOIP data format, such as G723.1 or G729 etc., to standard PSTN format, such PCM, and a downstream resource transcodes standard PSTN formats to VOIP formats.

[0025] FIG. 2 is a block diagram of a preferred embodiment of the Voice Converter (VC) architecture and design. In FIG. 2, a TCP/IP and UDP/IP API (application program interface) 22 couples a VOIP application to an UP Stream Resource Manager (USRM) 24 and to a Down Stream Resource Manager (DSRM) 26. The USRM and DSRM are coupled to a block 28 of digital signal processor (DSP) resources. Each DSP resource 30 is full-duplex and includes an upstream half-duplex block 32 and a downstream half-duplex block 34.

[0026] The TCP/IP and UDP/IP API 22 utilizes a TCP port to call the voice converter command port. The voice converter command port will wait on the TCP/IP socket for a request. When the command port receives the request it will analyze the request and will identify whether the request is an upstream request or if it is a down stream request. At this point the voice converter command port will dispatch the request to either the upstream resource manager or to the down stream resource manager.

[0027] As stated above, each of the DSP resources 30 is divided into two parts; the upstream resource 32 and a down stream resource 34. Each of these resources is a half-duplex channel which together form a full duplex DSP resource. Each of the two half-duplex resources 32 and 34 are assigned to a respective resource manager 24 and 26 where each resource manager maintains a table indicating the availability of each half-duplex resource so that an available resource can be scheduled to satisfy application transcoding requests.

[0028] Upstream Resource Manager

[0029] The upstream resource manager is responsible for keeping track of up stream DSP resource availability and scheduling. The USRM waits for application requests for up stream conversion and accepts a request if resources are available. The USRM then receives a first buffer of voice data from the application for conversion, keeps the first buffer of data in a look-ahead buffer, and then waits for one more voice data buffer for conversion. After receiving a minimum of two voice buffers filled with data the USRM will forward data to the upstream resource to start the conversion.

[0030] A look-ahead buffer is kept because, once the conversion is started on a DSP resource, buffers must continually be fed to the DSP. As described above, the DSP resource is designed for use with a PSTN. In the PSTN data is supplied at a continuous rate so that the DSP resource is designed to output data at a continuous rate. If no data is received the DSP resource outputs silence frames. Thus, if, for any reason, the next buffer is not ready because of network latency etc. then the DSP will start generating silence frames as the output and the DSP resource will always output data at continuous bit rate. Silence frames can cause the transcoded voice to be unintelligible to a listener. The look-ahead cache buffer will mask any network latency in receiving data, always making sure that enough data is available to feed to the DSP and hence ensuring the quality of transcoded voice.

[0031] Down Stream Resource Manager

[0032] The downstream resource manager is responsible for keeping track of the down stream DSP resource availability and scheduling. Very similar to the upstream resource manager, the down stream resource manager will also wait for the application request for downstream conversion, accepts the conversion request, and identifies an available downstream DSP resources and schedules the downstream on to the DSP resource. Prior to scheduling it maintains a one look ahead buffer to mask any network latency.

[0033] System Operation

[0034] The operation of the preferred embodiment depicted in FIG. 2 will now be described. Signaling commands from an application are sent to the TCP/IP and UDP/IP interface 22 and all data is sent on UDP. The operation of the USRM will be described first.

[0035] The TCP/IP and UDP/IP interface 22 forwards a request from an application to the USRM 24 (arrow 2). The USRM checks its resource availability table to determine which upstream resources are available to service the request. The USRM 24 then schedules an available upstream resource and provides data in VOIP format to the scheduled upstream resource (arrow 10). The USRM 24 also connects (arrow 11) the scheduled upstream DSP resource output back to the UDP stream that sends transcoded data back to the requesting application.

[0036] For example, if the requesting application is utilizing the ASR resource then the received voice data in VOIP format is transcoded to PCM format by the upstream resource and sent back to the application for ASR processing.

[0037] The operation of the DSRM 26 will now be described. The TCP/IP and UDP/IP interface 22 forwards a request from an application to the DSRM 26 (arrow 3). The DSRM 26 checks its resource availability table to determine which downstream resources are available to service the request. The DSRM 26 then schedules an available downstream resource and provides data in PCM format to the scheduled resource (arrow 7). The DSRM 26 also connects the scheduled downstream DSP resource output back to the UDP stream that sends transcoded data back to the requesting application.

[0038] For example, if the requesting application is utilizing TTS services then PCM data output by the TTS is transcoded to VOIP data and sent back to the requesting application.

[0039] Note in this example in FIG. 2, the upstream and downstream resources are scheduled as the two-half duplex blocks of a single DSP resource. Thus, twice the performance is gained from on DSP resource so that only a fraction of the DSP resources required by existing systems are required.

[0040] The voice converter uses TCP/IP as the command and control channel. Some commands supported in the embodiment include the following

[0041] 1. Upstream conversion start

[0042] 2. Upstream conversion stop

[0043] 3. Upstream conversion cancel

[0044] 4. Downstream conversion start

[0045] 5. Downstream conversion stop

[0046] 6. Downstream conversion cancel

[0047] The voice converter sends actual voice data using UDP. The format of the packet is shown in FIG. 3. The packet consists of sequence number that is used to re-arrange packets if they get out of order on the data stream. The packet also has a session flag that is used to keep track of the voice sessions.

[0048] By using the session numbers associated with the segments of the voice the application and the voice converter will take care of packets that have higher latency. For example if a user is listening to email. Then the application will play the header with session number one “1”. Then the application will continue to play the body of the email and use session number two “2” for it. The advantage of using the session ID is the fact that the application can use multiple simultaneous streams for different sessions. In a given session all packets sent for that session will have same session number.

[0049] The invention has now been described with reference to the preferred embodiments. Alternatives and substitutions will now be apparent to persons of skill in the art. For example, different VoIP encoding schemes such as G.726 or CELP encoding may be utilized. Also, commands and data may be exchanged using network protocols other than UDP or TCP/IP. Accordingly, it is not intended to limit the invention except as provided by the appended claims.