as a preliminary matter , it will readily be understood by one having ordinary skill in the relevant art (“ ordinary artisan ”) that the present invention has broad utility and application . furthermore , any embodiment discussed and identified as being “ preferred ” is considered to be part of a best mode contemplated for carrying out the present invention . other embodiments also may be discussed for additional illustrative purposes in providing a full and enabling disclosure of the present invention . moreover , many embodiments , such as adaptations , variations , modifications , and equivalent arrangements , will be implicitly disclosed by the embodiments described herein and fall within the scope of the present invention . accordingly , while the present invention is described herein in detail in relation to one or more embodiments , it is to be understood that this disclosure is illustrative and exemplary of the present invention , and is made merely for the purposes of providing a full and enabling disclosure of the present invention . the detailed disclosure herein of one or more embodiments is not intended , nor is to be construed , to limit the scope of patent protection afforded the present invention , which scope is to be defined by the claims and the equivalents thereof . it is not intended that the scope of patent protection afforded the present invention be defined by reading into any claim a limitation found herein that does not explicitly appear in the claim itself . thus , for example , any sequence ( s ) and / or temporal order of steps of various processes or methods that are described herein are illustrative and not restrictive . accordingly , it should be understood that , although steps of various processes or methods may be shown and described as being in a sequence or temporal order , the steps of any such processes or methods are not limited to being carried out in any particular sequence or order , absent an indication otherwise . indeed , the steps in such processes or methods generally may be carried out in various different sequences and orders while still falling within the scope of the present invention . accordingly , it is intended that the scope of patent protection afforded the present invention is to be defined by the appended claims rather than the description set forth herein . additionally , it is important to note that each term used herein refers to that which the ordinary artisan would understand such term to mean based on the contextual use of such term herein . to the extent that the meaning of a term used herein — as understood by the ordinary artisan based on the contextual use of such term — differs in any way from any particular dictionary definition of such term , it is intended that the meaning of the term as understood by the ordinary artisan should prevail . furthermore , it is important to note that , as used herein , “ a ” and “ an ” each generally denotes “ at least one ,” but does not exclude a plurality unless the contextual use dictates otherwise . thus , reference to “ a picnic basket having an apple ” describes “ a picnic basket having at least one apple ” as well as “ a picnic basket having apples .” in contrast , reference to “ a picnic basket having a single apple ” describes “ a picnic basket having only one apple .” when used herein to join a list of items , “ or ” denotes “ at least one of the items ,” but does not exclude a plurality of items of the list . thus , reference to “ a picnic basket having cheese or crackers ” describes “ a picnic basket having cheese without crackers ”, “ a picnic basket having crackers without cheese ”, and “ a picnic basket having both cheese and crackers .” finally , when used herein to join a list of items , “ and ” denotes “ all of the items of the list .” thus , reference to “ a picnic basket having cheese and crackers ” describes “ a picnic basket having cheese , wherein the picnic basket further has crackers ,” as well as describes “ a picnic basket having crackers , wherein the picnic basket further has cheese .” referring now to the drawings , in which like numerals represent like components throughout the several views , the preferred embodiments of the present invention are next described . the following description of the preferred embodiment ( s ) is merely exemplary in nature and is in no way intended to limit the invention , its application , or uses . fig1 is a block diagram of a communication system 10 in accordance with a preferred embodiment of the present invention . as shown therein , the communication system 10 includes at least one transmitting device 12 and at least one receiving device 14 , one or more network systems 16 for connecting the transmitting device 12 to the receiving device 14 , and an automatic speech recognition (“ asr ”) system 18 , including an asr engine . transmitting and receiving devices 12 , 14 may include cell phones 21 , smart phones 22 , pdas 23 , tablet notebooks 24 , various desktop and laptop computers 25 , 26 , 27 , and the like . one or more of the devices 12 , 14 , such as the illustrated imac and laptop computers 25 , 26 , may connect to the network systems 16 via wireless access point 28 . the various transmitting and receiving devices 12 , 14 ( one or both types of which being sometimes referred to herein as “ client devices ”) may be of any conventional design and manufacture . fig2 is a block diagram of a communication system 60 in accordance with another preferred embodiment of the present invention . this system 60 is similar to the system 10 of fig1 , except that the asr system 18 of fig1 has been omitted and the asr engine has instead been incorporated into the various transmitting devices 12 , including cell phones 61 , smart phones 62 , pdas 63 , tablet notebooks 64 , various desktop and laptop computers 65 , 66 , 67 , and the like . it will be appreciated that the illustrations of fig1 and 2 are intended primarily to provide context in which the inventive features of the present invention may be placed . a more complete explanation of one or more system architectures implementing such systems is provided elsewhere herein , in the incorporated applications and / or in the incorporated appendices attached hereto . furthermore , in the context of text messaging , the communication systems 10 , 60 each preferably includes , inter alia , a telecommunications network . in the context of instant messaging , the communications systems 10 , 60 each preferably includes , inter alia , the internet . fig3 is a block diagram illustrating communications between two users 32 , 34 via a portion of the communication system 10 of fig1 . as shown therein , a first user 32 , sometimes referred to herein as a “ transmitting user ,” is communicating with a second user 34 , sometimes referred to herein as a “ receiving user ,” by way of respective transmitting and receiving devices 12 , 14 . more particularly , the transmitting user 32 uses his transmitting device 12 to initiate text messages that are transmitted to , and received by , the receiving user 34 via her receiving device 14 . in the context of text messaging , the transmitting user 32 may send text messages , using his transmitting device 12 , via sms , and the receiving user 34 receives text messages , sent via sms , on her receiving device 14 . in the context of instant messaging , the transmitting user 32 may send instant messages , via an im client , using his transmitting device 12 , and the receiving user 34 receives instant messages , via an im client , on his receiving device 14 . in at least some embodiments , the transmitting user 32 in fig3 may generate text messages by speaking into his transmitting device 12 and causing his utterances to be converted to text for communicating to the receiving device 14 . one or more systems and methods for carrying out such a process are described , for example , in the aforementioned u . s . patent application pub . no . us 2007 / 0239837 , but are at least partially described herein . more particularly , fig4 may be understood to be a block diagram of an exemplary implementation of the system 10 of fig1 . in this implementation , the transmitting device 12 is a mobile phone , the asr system 18 is implemented in one or more backend servers 160 , and the one or more network systems 16 include transceiver towers 130 , one or more mobile communication service providers 140 ( operating or joint or independent control ) and the internet 150 . the backend server 160 is or may be placed in communication with the mobile phone 12 via the mobile communication service provider 140 and the internet 150 . the mobile phone has a microphone , a speaker and a display . a first transceiver tower 130 a is positioned between the mobile phone 12 ( or the user 32 of the mobile phone 12 ) and the mobile communication service provider 140 , for receiving an audio message ( v 1 ), a text message ( t 3 ) and / or a verified text message ( v / t 1 ) from one of the mobile phone 12 and the mobile communication service provider 140 and transmitting it ( v 2 , t 4 , v / t 2 ) to the other of the mobile phone 12 and the mobile communication service provider 140 . a second transceiver tower 130 b is positioned between the mobile communication service provider 140 and mobile devices 170 , generally defined as receiving devices 14 equipped to communicate wirelessly via mobile communication service provider 140 , for receiving a verified text message ( v / t 3 ) from the mobile communication service provider 140 and transmitting it ( v 5 and t 5 ) to the mobile devices 170 . in at least some embodiments , the mobile devices 170 are adapted for receiving a text message converted from an audio message created in the mobile phone 12 . additionally , in at least some embodiments , the mobile devices 170 are also capable of receiving an audio message from the mobile phone 12 . the mobile devices 170 include , but are not limited to , a pager , a palm pc , a mobile phone , or the like . the system 10 also includes software , as disclosed below in more detail , installed in the mobile phone 12 and the backend server 160 for causing the mobile phone 12 and / or the backend server 160 to perform the following functions . the first step is to initialize the mobile phone 12 to establish communication between the mobile phone 12 and the backend server 160 , which includes initializing a desired application from the mobile phone 12 and logging into a user account in the backend server 160 from the mobile phone 12 . then , the user 32 presses and holds one of the buttons of the mobile phone 12 and speaks an utterance 36 , thus generating an audio message , v 1 . at this stage , the audio message v 1 is recorded in the mobile phone 12 . by releasing the button , the recorded audio message v 1 is sent to the backend server 160 through the mobile communication service provider 140 . in the exemplary embodiment of the present invention as shown in fig4 , the recorded audio message v 1 is first transmitted to the first transceiver tower 130 a from the mobile phone 12 . the first transceiver tower 130 a outputs the audio message v 1 into an audio message v 2 that is , in turn , transmitted to the mobile communication service provider 140 . then the mobile communication service provider 140 outputs the audio message v 2 into an audio message v 3 and transmits it ( v 3 ) to the internet 150 . the internet 150 outputs the audio message v 3 into an audio message v 4 and transmits it ( v 4 ) to the backend server 160 . the content of all the audio messages v 1 - v 4 is identical . the backend server 160 then converts the audio message v 4 into a text message , t 1 , and / or a digital signal , d 1 , in the backend server 160 by means of a speech recognition algorithm including a grammar algorithm and / or a transcription algorithm . the text message t 1 and the digital signal d 1 correspond to two different formats of the audio message v 4 . the text message t 1 and / or the digital signal d 1 are sent back to the internet 150 that outputs them into a text message t 2 and a digital signal d 2 , respectively . the digital signal d 2 is transmitted to a digital receiver 180 , generally defined as a receiving device 14 equipped to communicate with the internet and capable of receiving the digital signal d 2 . in at least some embodiments , the digital receiver 180 is adapted for receiving a digital signal converted from an audio message created in the mobile phone 12 . additionally , in at least some embodiments , the digital receiver 180 is also capable of receiving an audio message from the mobile phone 12 . a conventional computer is one example of a digital receiver 180 . in this context , a digital signal d 2 may represent , for example , an email or instant message . it should be understood that , depending upon the configuration of the backend server 160 and software installed on the mobile phone 12 , and potentially based upon the system set up or preferences of the user 32 , the digital signal d 2 can either be transmitted directly from the backend server 160 or it can be provided back to the mobile phone 12 for review and acceptance by the user 32 before it is sent on to the digital receiver 180 . the text message t 2 is sent to the mobile communication service provider 140 that outputs it ( t 2 ) into a text message t 3 . the output text message t 3 is then transmitted to the first transceiver tower 130 a . the first transceiver tower 130 a then transmits it ( t 3 ) to the mobile phone 12 in the form of a text message t 4 . it is noted that the substantive content of all the text messages t 1 - t 4 may be identical , which are the corresponding text form of the audio messages v 1 - v 4 . upon receiving the text message t 4 , the user 32 verifies it and sends the verified text message v / t 1 to the first transceiver tower 130 a that in turn , transmits it to the mobile communication service provider 140 in the form of a verified text v / t 2 . the verified text v / t 2 is transmitted to the second transceiver tower 130 b in the form of a verified text v / t 3 from the mobile communication service provider 140 . then , the transceiver tower 130 b transmits the verified text v / t 3 to the mobile devices 170 . in at least one implementation , the audio message is simultaneously transmitted to the backend server 160 from the mobile phone 12 , when the user 32 speaks to the mobile phone 12 . in this circumstance , it is preferred that no audio message is recorded in the mobile phone 12 , although it is possible that an audio message could be both transmitted and recorded . such a system 10 may be utilized to convert an audio message into a text message . in at least one implementation , this may be accomplished by first initializing a transmitting device so that the transmitting device is capable of communicating with a backend server 160 . second , a user 32 speaks to or into the client device 12 so as to create a stream of an audio message . the audio message can be recorded and then transmitted to the backend server 160 , or the audio message can be simultaneously transmitted to the backend server 160 through a client - server communication protocol . streaming may be accomplished according to processes described elsewhere herein and , in particular , in fig4 and accompanying text , of the aforementioned u . s . patent application pub . no . us 2007 / 0239837 . the transmitted audio message is converted into the text message in the backend server 160 . the converted text message is then sent back to the client device 12 . upon the user &# 39 ; s verification , the converted text message is forwarded to one or more recipients 34 and their respective receiving devices 14 , where the converted text message may be displayed on the device 14 . incoming messages may be handled , for example , according to processes described elsewhere herein and , in particular , in fig2 and accompanying text , of the aforementioned u . s . patent application pub . no . us 2007 / 0239837 . still further , in at least one implementation , one or both types of client device 12 , 14 may be located through a global positioning system ( gps ); and listing locations , proximate to the position of the client device 12 , 14 , of a target of interest may be presented in the converted text message . furthermore , in converting speech to text , speech transcription performance indications may be provided to the receiving user 34 in accordance with the disclosure of u . s . patent application ser . no . 12 / 197 , 213 , entitled “ continuous speech transcription performance indication ,” which , together with any corresponding patent application publications thereof , is incorporated herein by reference . additionally , in the context of sms messaging , the asr system preferably makes use of both statistical language models ( slms ) for returning results from the audio data , and finite grammars used to post - process the text results , in accordance with the disclosure of u . s . patent application ser . no . 12 / 198 , 112 , entitled “ filtering transcriptions of utterances ,” which , together with any corresponding patent application publications thereof , is incorporated herein by reference . this is believed to result in text messages that are formatted in a way that looks more typical of how a human would have typed the text message using a mobile device . fig5 is a block diagram of a communication device 50 , such as a cell phone 21 or other mobile communication device , that is equipped with a physical phenomenon detection unit 80 in accordance with a preferred embodiment of the present invention . the communication device 50 may include a control unit 52 , a duplex radio 54 that includes a duplexer 56 with antenna ( not shown ), a receiver 58 , and a transmitter 60 , a signal level detector 62 , a voice processing unit 64 , a microphone / speaker unit 66 that includes a microphone and one or more speakers , a memory system 68 , a ring signal generator 70 , a display unit 72 , and optionally , a key input unit 74 having one or more key elements . although many of these elements may be generally conventional , each element is described in some detail hereinbelow so as to provide a better understanding of the operation of the physical phenomenon detection unit 80 in controlling one or more functions of the communication device 50 . it will be appreciated that the communication device 50 described and illustrated herein may be utilized as either or both of a transmitting device 12 and a receiving device 14 . furthermore , it will be appreciated that although a transmitting device 12 of the type described and illustrated in fig5 and accompanying text may be utilized to communicate with a receiving device 14 of the same type , a transmitting device 12 of the type described and illustrated in fig5 and accompanying text may also be utilized for communications with a conventional receiving device 14 ( that is , with a receiving device 14 that is not equipped with , or does not utilize , a physical phenomenon detection unit 80 ), and likewise that a receiving device 14 of the type described and illustrated in fig5 and accompanying text may also be utilized for communications with a conventional transmitting device 12 ( that is , with a transmitting device 12 that is not equipped with , or does not utilize , a physical phenomenon detection unit 80 ). returning to fig5 , the memory system 68 includes a read only memory ( rom ) for storing control data required for the operation of the control unit 52 , a nonvolatile memory for storing data to be stored or removed , such as phone numbers or the like , under the control of the user , and a random access memory ( ram ) for temporarily storing data generated during operation of the control unit 52 . for incoming communications , the duplexer 56 receives incoming radio signals via the antenna and outputs them to the receiver 58 . the receiver 58 outputs voice signals to the signal level detector 62 and outputs data to the control unit 52 , which then causes the ring tone generator 70 to generate a predetermined ring tone . the signal level detector 62 determines the intensity of the voice signal and delivers that information to the control unit 52 and provides the voice signal to the voice processing unit 64 . the voice processing unit 64 decodes the signal received from the reception unit 58 and outputs the decoded signal to the speaker in the microphone / speaker unit 66 . data transmissions are handled by the control unit 52 which displays text messages , photos , and the like to the user via the display unit 72 . for outgoing voice transmissions , the voice processing unit 64 receives the user &# 39 ; s voice , which has been converted into an electric signal by the microphone , encodes the electric signal , and outputs the encoded signal to the transmission unit 60 via the signal level detector 62 . the signal level detector 62 determines the intensity of the outgoing voice signal , delivers that information to the control unit 52 , and provides the voice signal to the transmission unit 60 . under the control of the control unit 52 , the transmission unit 60 outputs a transmission signal , corresponding to the encoded signal received from the voice processing unit 64 , to the duplexer 56 via a set channel , and the transmission signal is then transmitted via the antenna . when a user wishes to make a call , the user selects a desired phone number from the memory system 68 or inputs a number via manipulation of one or more of the key elements of the key input unit 74 , and an outgoing call signal corresponding to the selected number is transmitted . connection may be established with a corresponding receiving device 14 , and voice communication carried out with the user 34 of that device 14 , through the duplexer 56 , the radio receiver and transmitter 58 , 60 , the voice processing unit 64 and the microphone / speaker unit 66 . when a call signal is received by the communication device 50 , a ring signal is generated through the ring signal generation unit 70 under the control of the control unit 52 , and a voice call can be accomplished , by the manipulation of one or more of the key elements of the key input unit 74 in response to the ring signal , through the duplexer 56 , the radio transmission and reception units 58 , 60 , the voice processing unit 64 and the microphone / speaker unit 66 . outgoing text communications may be generated in any one of at least two ways . more particularly , text messages may be keyed in manually by the user 32 using the one or more key elements 74 in a conventional manner , or text messages may be created using a speech recognition methodology . such a methodology is described , for example , in the aforementioned u . s . pub . no . us 2007 / 0239837 , wherein an utterance 36 produced by the user 32 is received by the microphone , processed by the voice processing unit 64 and recorded in the memory system 68 , all under the control of the control unit 52 , and then transmitted to the asr system 18 via the duplex radio 54 . the asr engine converts the utterance 36 to text and transmits the text message back to the originating communication device 50 where it is received by the duplex radio 54 and handled as described previously . upon receipt of the transcribed text message , the control unit 52 presents the message to the user 32 via the display unit 72 for verification and editing as necessary , and upon approval by the user 32 , the finalized text message is deemed to be ready to transmit to a destination communication device such as the receiving device 14 described previously . if not already selected , the user 32 selects a desired phone number or other destination address from the memory system 68 or inputs a number or other address via the one or more key elements of the key input unit 74 , and an outgoing message signal corresponding to the number or address is transmitted . the physical phenomenon detection unit 80 can be implemented using any suitable phenomenon detector or sensor 84 , such as an ir proximity sensor , an inductive proximity sensor , capacitive proximity sensor , magnetic proximity sensor or photoelectric proximity sensor detecting proximity , an ambient light sensor detecting light , a geomagnetic sensor detecting earth magnetism , a single - axis or multi - axis gyroscope detecting inclination , an accelerometer detecting acceleration , a vibration detector detecting vibration , or the like , including any such detector or sensor device described in any of the patent applications incorporated by reference herein . such detectors and sensors may sense phenomena relative to one or more than axis , or may sense phenomena only within a particular range such as inclination from 45 ° to 90 °. the detection unit 80 is preferably located inside the housing of the communication device 50 , though in some embodiments the detection unit 80 may be external . the detection unit 80 may further incorporate more than one sensor 84 ; the various sensors 84 may be of the same type or of different types . in at least some embodiments , an interface unit 82 receives one or more input signals from each sensor 84 in the detection unit 80 and uses predetermined logic to provide one or more output signals to the control unit 52 . alternatively , the control unit 52 is programmed or otherwise arranged to sort through the signals provided by an interface unit 82 . further , in at least some embodiments , multiple detection units 80 are provided , each communicatively connected to the control unit 52 by a separate interface unit 82 . in still other embodiments , no interface unit 82 is provided , and the control unit 52 receives signals directly from each detection unit 80 . the communication device 50 described above may allow the user 32 to execute a “ push to talk ” function using two different methods . if a key input unit 74 having one or more key elements is provided , then a user 32 wishing to make an utterance 36 that is to be recognized and converted into text may use a generally conventional method in which the user 32 , 34 merely presses or otherwise triggers one or more key element in the key input unit 74 just before speaking , and either pressing the same button again , releasing the button if it was held , or pressing a different button , as applicable , when the user 32 , 34 is finished speaking typically , the “ push to talk ” function is functionally implemented in the communication device 50 by activating the microphone and subsequently deactivating the microphone , with any utterance 36 that the microphone receives , while activated , is recorded , transmitted or the like . however , other device functions could instead or additionally be activated , such as a recording function , a transmitting function , or the like . whether or not the key input unit 74 is provided or includes a designated or selectable physical button or buttons for carrying out the “ push to talk ” function , the physical phenomenon detection unit 80 offers a second method wherein the user 32 manipulates the position , orientation , or any other detectable physical state of the communication device 50 , or more particularly of the detection unit 80 , so as to trigger the detection unit 80 in a predetermined way . for example , the detection unit 80 may utilize an ir proximity sensor 84 that is tuned to detect the heat from a user &# 39 ; s face , such as might be detected if the device 50 was held against the user &# 39 ; s face while speaking into the microphone of the device 50 , and to cause a first signal to be generated and sent , via the interface unit 82 , to the control unit 52 when the sensor 84 detects the appropriate amount of heat and to generate a second signal when the communication device 50 is moved away from the user &# 39 ; s face . using such a detection unit 80 , the user 32 may , when he or she is ready to trigger the recognition of a particular utterance 36 , move the communication device 50 against his or her face , to a natural speaking position , to initiate the “ push to talk ” function and subsequently remove the communication device 50 from his or face to terminate the “ push to talk ” function . in another example , if the detection unit 80 utilizes a multi - axis tilt sensor 84 that is preset to cause a first signal to be generated and sent , via the interface unit 82 , to the control unit 52 when the communication device 50 is moved so it is approximately vertical relative to a first axis and somewhat tilted ( e . g ., at a 30 °- 45 ° angle ) relative to a second axis , and to generate a second signal when the communication device 50 is moved out of that position , then the user 32 may , when he or she is ready to trigger the recognition of a particular utterance 36 , move the communication device 50 into the described position or orientation to initiate the “ push to talk ” function and subsequently remove the communication device 50 from that position or orientation to terminate the “ push to talk ” function . it will be apparent that any position or orientation ( or in the case of other types of sensors 84 , the occurrence of any suitable physical phenomenon ) may be selected to initiate and terminate the “ push to talk ” function , though the selected position , orientation or other phenomenon should preferably be selected to be convenient for the user 32 to move or enter , and more preferably should be relatively natural and intuitive for the user 32 . for example , the above - described physical position or orientation ( approximately vertical relative to a first axis and somewhat tilted relative to a second axis ) may be selected to approximate the position or orientation a cell phone 21 is often held by a user 32 when the user 32 is holding the cell phone 21 to his ear and is speaking into the cell phone 21 . it will be appreciated that any of the movements or other physical triggering means described in any of the referenced applications may likewise be utilized . for example , the user may move the communication device 50 in a certain predetermined way in space to activate the “ push to talk ” function and the same or different predetermined way to deactivate the “ push to talk ” function . further , it will be appreciated that a first physical phenomenon may be utilized to place the communication device into a “ standby ” state wherein a second physical phenomenon , subsequent to the first , activates the “ push to talk ” function . of course , the communication device 50 may alternatively be placed into the “ standby ” state using the key elements of the key input unit 74 , if provided , or using a touch screen or other means . notably , the speech to be recognized may be a voice command for the device 50 , an utterance 36 to be converted to text , a message to be transcribed , or any other known or future - developed speech recognition application , including those mentioned previously . for example , fig1 a and 18b are block diagrams illustrating the use of an utterance as a voice command to control a communication device 12 of fig1 and fig2 , respectively . in particular , an utterance may be recognized indirectly , via the asr system 18 of fig1 and 18a , or directly , by the asr - equipped communication device of fig2 and 18b . in either case , the physical phenomenon detection unit 80 may be utilized to control the acquisition of the utterance by the communication device 50 , as described previously . an utterance 36 may be converted to text in accordance , for example , with the disclosure of the aforementioned u . s . pub . no . us 2007 / 0239837 . the device 50 preferably presents an indication to the user 32 , for purposes of verification , that the particular speech recognition operation being carried out has been carried out successfully . for example , for voice commands , the device 50 preferably communicates audibly with the user 32 to verify that the device 50 correctly understood the command . for speech - to - text conversions made using one of the systems illustrated in fig1 - 3 , the converted text message is preferably presented to the user 32 on the display unit 72 . of course , other means for verification may be used , and in some cases , verification is not required or may utilized only at the user &# 39 ; s option . one commercial implementation of the foregoing principles utilizes the yap ® and yap9 ™ service ( collectively , “ the yap service ”), available from yap inc . of charlotte , n . c . the yap service includes one or more web applications and a client device application . the yap web application is a j2ee application built using java 5 . it is designed to be deployed on an application server like ibm websphere application server or an equivalent j2ee application server . it is designed to be platform neutral , meaning the server hardware and os can be anything supported by the web application server ( e . g . windows , linux , macos x ). fig6 is a block diagram of the system architecture of the yap commercial implementation . with reference to fig6 , the operating system may be implemented in red hat enterprise linux 5 ( rhel 5 ); the application servers may include the websphere application server community edition ( was - ce ) servers , available from ibm ; the web server may be an apache server ; the ctts servlets may include ctts servlets from loquendo , including us / uk / es male and us / uk / es female ; the grammar asp may be the latest websphere voice server , available from ibm ; suitable third party ads may be provided by google ; a suitable third party im system is google talk , available from google ; and a suitable database system is the db2 express relational database system , available from ibm . fig7 is a block diagram of the yap ear of fig6 . the audio codec jars may include the voiceage amr jar , available from voiceage of montreal , quebec and / or the qcelp jar , available from qualcomm of san diego , calif . the yap web application includes a plurality of servlets . as used herein , the term “ servlet ” refers to an object that receives a request and generates a response based on the request . usually , a servlet is a small java program that runs within a web server . servlets receive and respond to requests from web clients , usually across http and / or https , the hypertext transfer protocol . currently , the yap web application includes nine servlets : correct , debug , install , login , notify , ping , results , submit , and tts . each servlet is described below in the order typically encountered . the communication protocol used for all messages between the yap client and yap server applications is http and https . using these standard web protocols allows the yap web application to fit well in a web application container . from the application server &# 39 ; s point of view , it cannot distinguish between the yap client midlet and a typical web browser . this aspect of the design is intentional to convince the web application server that the yap client midlet is actually a web browser . this allows a user to use features of the j2ee web programming model like session management and https security . it is also an important feature of the client as the midp specification requires that clients are allowed to communicate over http . more specifically , the yap client uses the post method and custom headers to pass values to the server . the body of the http message in most cases is irrelevant with the exception of when the client submits audio data to the server in which case the body contains the binary audio data . the server responds with an http code indicating the success or failure of the request and data in the body which corresponds to the request being made . preferably , the server does not depend on custom header messages being delivered to the client as the carriers can , and usually do , strip out unknown header values . fig8 is a typical header section of an http request from the yap client . the yap client is operated via a user interface ( ui ), known as “ yap9 ,” which is well suited for implementing methods of converting an audio message into a text message and messaging in mobile environments . yap9 is a combined ui for sms and web services ( ws ) that makes use of the buttons or keys of the client device by assigning a function to each button ( sometimes referred to as a “ yap9 ” button or key ). execution of such functions is carried out by “ yaplets .” this process , and the usage of such buttons , are described elsewhere herein and , in particular , in fig9 a - 9d , and accompanying text , of the aforementioned u . s . patent application pub . no . us 2007 / 0239837 . usage process — install : installation of the yap client device application is described in the aforementioned u . s . patent application pub . no . us 2007 / 0239837 in a subsection titled “ install process ” of a section titled “ system architecture .” usage process — notify : when a yap client is installed , the install fails , or the install is canceled by the user , the notify servlet is sent a message by the phone with a short description . this can be used for tracking purposes and to help diagnose any install problems . usage process — login : when the yap midlet is opened , the first step is to create a new session by logging into the yap web application using the login servlet . preferably , however , multiple login servers exist , so as a preliminary step , a request is sent to find a server to log in to . exemplary protocol details for such a request can be seen in fig9 . an http string pointing to a selected login server will be returned in response to this request . it will be appreciated that this selection process functions as a poor man &# 39 ; s load balancer . after receiving this response , a login request is sent . exemplary protocol details for such a request can be seen in fig1 . a cookie holding a session id is returned in response to this request . the session id is a pointer to a session object on the server which holds the state of the session . this session data will be discarded after a period determined by server policy . sessions are typically maintained using client - side cookies , however , a user cannot rely on the set - cookie header successfully returning to the yap client because the carrier may remove that header from the http response . the solution to this problem is to use the technique of url rewriting . to do this , the session id is extracted from the session api , which is returned to the client in the body of the response . this is called the “ yap cookie ” and is used in every subsequent request from the client . the yap cookie looks like this : all requests from the client simply append this cookie to the end of each request and the session is maintained : usage process — submit : after receiving a session id , audio data may be submitted . the user presses and holds one of the yap - 9 buttons , speaks aloud , and releases the pressed button . the speech is recorded , and the recorded speech is then sent in the body of a request to the submit servlet , which returns a unique receipt that the client can use later to identify this utterance . exemplary protocol details for such a request can be seen in fig1 . one of the header values sent to the server during the login process is the format in which the device records . that value is stored in the session so the submit servlet knows how to convert the audio into a format required by the asr engine . this is done in a separate thread as the process can take some time to complete . the yap9 button and yap9 screen numbers are passed to the submit server in the http request header . these values are used to lookup a user - defined preference of what each button is assigned to . for example , the 1 button may be used to transcribe audio for an sms message , while the 2 button is designated for a grammar based recognition to be used in a web services location based search . the submit servlet determines the appropriate “ yaplet ” to use . when the engine has finished transcribing the audio or matching it against a grammar , the results are stored in a hash table in the session . in the case of transcribed audio for an sms text message , a number of filters can be applied to the text returned from the asr engine . such filters may include , but are not limited to , those shown table 3 . notably , after all of the filters are applied , both the filtered text and original text are returned to the client so that if text to speech is enabled for the user , the original unfiltered text can be used to generate the tts audio . usage process — results : the client retrieves the results of the audio by taking the receipt returned from the submit servlet and submitting it as a request to the results servlet . exemplary protocol details for such a request can be seen in fig1 . this is done in a separate thread on the device and a timeout parameter may be specified which will cause the request to return after a certain amount of time if the results are not available . in response to the request , a block of xml is preferably returned . exemplary protocol details for such a return response can be seen in fig1 . alternatively , a serialized java results object may be returned . this object contains a number of getter functions for the client to extract the type of results screen to advance to ( i . e ., sms or results list ), the text to display , the text to be used for tts , any advertising text to be displayed , an sms trailer to append to the sms message , etc . usage process — tts : the user may choose to have the results read back via text to speech . this can be an option the user could disable to save network bandwidth , but adds value when in a situation where looking at the screen is not desirable , like when driving . if tts is used , the tts string is extracted from the results and sent via an http request to the tts servlet . exemplary protocol details for such a request can be seen in fig1 . the request blocks until the tts is generated and returns audio in the format supported by the phone in the body of the result . this is performed in a separate thread on the device since the transaction may take some time to complete . the resulting audio is then played to the user through the audioservice object on the client . preferably , tts speech from the server is encrypted using corrected block tiny encryption algorithm ( xxtea ) encryption . usage process — correct : as a means of tracking accuracy and improving future sms based language models , if the user makes a correction to transcribed text on the phone via the key elements of the key input unit 74 before sending the message , the corrected text is submitted to the correct servlet along with the receipt for the request . this information is stored on the server for later use in analyzing accuracy and compiling a database of typical sms messages . exemplary protocol details for such a submission can be seen in fig1 . usage process — ping : typically , web sessions will timeout after a certain amount of inactivity . the ping servlet can be used to send a quick message from the client to keep the session alive . exemplary protocol details for such a message can be seen in fig1 . usage process — debug : used mainly for development purposes , the debug servlet sends logging messages from the client to a debug log on the server . exemplary protocol details can be seen in fig1 . usage process — logout : to logout from the yap server , an http logout request needs to be issued to the server . an exemplary such request would take the form : “/ yap / logoutjsessionid = 1234 ”, where 1234 is the session id . user preferences : in at least one embodiment , the yap website has a section where the user can log in and customize their yap client preferences . this allows them to choose from available yaplets and assign them to yap9 keys on their phone . the user preferences are stored and maintained on the server and accessible from the yap web application . this frees the yap client from having to know about all of the different back - end yaplets . it just records the audio , submits it to the server along with the yap9 key and yap9 screen used for the recording and waits for the results . the server handles all of the details of what the user actually wants to have happen with the audio . the client needs to know what type of format to utilize when presenting the results to the user . this is accomplished through a code in the results object . the majority of requests fall into one of two categories : sending an sms message , or displaying the results of a web services query in a list format . notably , although these two are the most common , the yap architecture supports the addition of new formats . based on the foregoing information , it is readily understood by those persons skilled in the art that the present invention is susceptible of broad utility and application . many embodiments and adaptations of the present invention other than those specifically described herein , as well as many variations , modifications , and equivalent arrangements , will be apparent from or reasonably suggested by the present invention and the foregoing descriptions thereof , without departing from the substance or scope of the present invention . accordingly , while the present invention has been described herein in detail in relation to its preferred embodiment , it is to be understood that this disclosure is only illustrative and exemplary of the present invention and is made merely for the purpose of providing a full and enabling disclosure of the invention . the foregoing disclosure is not intended to be construed to limit the present invention or otherwise exclude any such other embodiments , adaptations , variations , modifications or equivalent arrangements ; the present invention being limited only by the claims appended hereto and the equivalents thereof . although specific terms are employed herein , they are used in a generic and descriptive sense only and not for the purpose of limitation .