Voice activated push-to-talk device and method of use
Claim Score by NHIP
Abstract
An push-to-talk wireless communication device and method of facilitating a push-to-talk call are disclosed. The wireless communication device includes a voice recognition module that allows a user to establish and carry out a push-to-talk call through voice commands. The voice recognition module facilitates a push to talk call by establishing a push-to-talk call in response to a voice command. During the call, the voice recognition module identifies predetermined code words from the audio stream and manages the push-to-talk call functions accordingly.
Term
Term ended
Projected expiry passed 7 February 2025, 1.6 years ago.
- Priority and filed
- Published
- Projected expiry
- Today
25 claims: 3 independent, 22 dependent
- 1A wireless communication device for facilitating a voice controlled push-to-talk call, comprising:a push-to-talk module configured to establish a push-to-talk call, manage an active push-to-talk call, and terminate an established push-to-talk call;and a voice recognition module configured to receive an audio segment, parse the audio segment to identify a voice command, analyze the voice command to determine a push-to-talk command, and instruct the push-to-talk module to execute the push-to-talk command.
- 10Broadest claimClaim Score 81, broad(NHIP)A method for facilitating a voice controlled push-to-talk call on a wireless communication device, comprising:initiating a voice recognition mode on a wireless communication device;receiving an audio segment;parsing the audio segment to determine a voice command;identifying the voice command as a push-to-talk command;and executing the push-to-talk command.
- 18A computer readable medium having stored thereon one or more sequences of instructions for causing one or more microprocessors to perform the steps for facilitating a voice controlled push-to-talk call on a wireless communication device, the steps comprising:initiating a voice recognition mode on a wireless communication device;receiving an audio segment;parsing the audio segment to determine a voice command;identifying the voice command as a push-to-talk command;and executing the push-to-talk command.
Independent claims3
60 paragraphs in 5 sections, as filed
FIELD OF THE INVENTION
0001The present invention generally relates to wireless communications and more specifically relates to facilitating push-to-talk communication between wireless communication devices.
BACKGROUND OF THE INVENTION
0002Conventional systems and methods for managing push-to-talk (“PTT”) communications over a wireless communication network require a user make many button presses in connection with managing the user's presence and availability for PTT communications and in connection with establishing and carrying out a PTT call. Additionally, a user must interact with the user interface, including both the display screen and the keyboard/buttons on the wireless communication device. These conventional systems and methods present severe disadvantages in situations where a user needs to operate the wireless communication device in a hands free mode, for example when driving an automobile.
0003The market for PTT wireless communication devices has therefore presented to the wireless communication industry a specific need for a safer hands free PTT capability. Meeting this need, however, presents significant challenges due to the inherent interaction that is required in “push”-to-talk communications. Therefore, what is needed is a system and method that facilitates hands free PTT communications between wireless communication devices.
SUMMARY OF THE INVENTION
0004Accordingly, a hands free push-to-talk wireless communication device and method of facilitating a hands free push-to-talk call are provided. The wireless communication device includes a voice recognition module that allows a user to establish and carry out a push-to-talk call through voice commands. The voice recognition module facilitates a push to talk call by establishing a push-to-talk call in response to a voice command and during the call identifying predetermined code words from the audio stream and carrying out those push-to-talk call functions accordingly.
0005Other features and advantages of the present invention will become more readily apparent to those of ordinary skill in the art after reviewing the following detailed description and accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
0006The details of the present invention, both as to its structure and operation, may be gleaned in part by study of the accompanying drawings, in which like reference numerals refer to like parts, and in which:
0007<figref idref="DRAWINGS">FIG. 1</figref> is a network diagram illustrating an example wireless communication system configured to facilitate push-to-talk calls according to an embodiment of the present invention;
0008<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating an example wireless communication device according to an embodiment of the present invention;
0009<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram illustrating an example process for establishing a push-to-talk call through voice activation;
0010<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram illustrating an example process for facilitating an established push-to-talk call through voice activation;
0011<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram illustrating an exemplary wireless communication device that may be used in connection with the various embodiments described herein; and
0012<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram illustrating an exemplary computer system as may be used in connection with various embodiments described herein.
DETAILED DESCRIPTION OF THE INVENTION
0013Certain embodiments as disclosed herein provide for a wireless communication device capable of establishing and carrying out push-to-talk (“PTT”) calls through voice activation. For example, one method as disclosed herein allows for the user of a PTT enabled wireless communication device to provide a voice command that causes the wireless communication device to establish a PTT call. Furthermore, during the call the user can provide voice commands that control the PTT communication session.
0014After reading this description it will become apparent to one skilled in the art how to implement the invention in various alternative embodiments and alternative applications. However, although various embodiments of the present invention will be described herein, it is understood that these embodiments are presented by way of example only, and not limitation. As such, this detailed description of various alternative embodiments should not be construed to limit the scope or breadth of the present invention as set forth in the appended claims.
0015<figref idref="DRAWINGS">FIG. 1</figref> is a network diagram illustrating an example wireless communication system <b>10</b> configured to facilitate push-to-talk calls. The system <b>10</b> comprises a plurality of wireless communication devices (also referred to as “wireless devices” and “handsets”) such as handsets <b>20</b> and <b>30</b>. The handsets are communicatively coupled with a wireless communication network <b>35</b> via a plurality of base stations such as base stations <b>40</b> and <b>50</b>. Also connected to the wireless communication network <b>35</b> are a plurality of packet data service nodes (“PDSN”) such as PDSNs <b>60</b> and <b>70</b>. Each PDSN preferably is configured with a data storage area such as data storage areas <b>62</b> and <b>72</b>.
0016The wireless communication network <b>35</b> can also be communicatively coupled with other communication networks such as network <b>90</b>. In one embodiment, wireless communication network <b>35</b> is a code division multiple access 2000 (“CDMA2000”) network, the specification for which is published by the 3rd Generation Partnership Project 2 (“3GPP2”), which is incorporated herein by reference in its entirety. For example, wireless communication network <b>35</b> may be a CDMA2000 Release A network. Network <b>90</b> can be any of a large variety of networks such as a circuit switched telephone network or a packet data network such as the Internet. In the illustrated embodiment, a PTT server <b>80</b> is communicatively coupled with the PDSNs and the handsets via network <b>90</b>. Alternatively, the PTT server <b>80</b> can be part of or connected directly to the wireless communication network <b>35</b>. PTT server <b>80</b> is configured with a data storage area <b>82</b>.
0017As will be understood by those skilled in the art, packet data communications over the wireless communication network <b>35</b> are routed throughout the network and beyond (e.g., to network <b>90</b>) by the plurality of PDSNs such as PDSN <b>60</b> and PDSN <b>70</b>. In one embodiment, PTT calls are packet data communications that use voice over internet protocol (“VoIP”) technology to carry voice between handsets as packet data. Alternative embodiments may employ alternative mechanisms to carry out a PTT call. All such mechanisms fall within the scope and spirit of the present invention.
0018<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram illustrating an example wireless communication device <b>20</b> according to an embodiment of the present invention. In the illustrated embodiment, the handset <b>20</b> comprises a voice recognition (“VR”) module <b>100</b> and a PTT module <b>110</b>. The VR module <b>100</b> is configured to identify audio commands received in the audio channel from the microphone and execute those commands. In one embodiment, the VR module <b>100</b> may be configured to prompt the user for confirmation prior to the execution of all commands or a subset of the commands. Advantageously, the VR module <b>100</b> can be capable of self training. In one embodiment, the VR module <b>100</b> may employ a listening algorithm that consumes low power. Additionally, the VR module <b>100</b> can be trained to learn the universe of PTT related commands. For example, a user may train the VR module <b>100</b> to understand all of the commands that the user may enter through interaction with the user interface such as group management (adding to groups, deleting groups, etc.) and user preferences (setting user availability, setting user presence, etc.).
0019The VR module <b>100</b> is communicatively coupled with the PTT module <b>110</b> so that when PTT related commands are identified by the VR module <b>100</b>, those commands can be passed to the PTT module <b>110</b> for execution. The PTT module <b>110</b> is configured to establish PTT calls that are initiated by the handset or received by the handset. The PTT module <b>110</b> is also configured to manage active PTT calls and manage PTT presence information on the wireless communication network (not shown). PTT presence information is generally maintained by the wireless communication network to provide information about the handsets that are currently available for PTT communication.
0020<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram illustrating an example process for establishing a PTT call through voice activation. Initially, in step <b>200</b>, the voice recognition mode on the handset is initiated. For example, voice recognition mode can be initiated by launching the VR module that was previously described with respect to <figref idref="DRAWINGS">FIG. 2</figref>. In one embodiment, initiation of the VR mode may be carried out by the user selecting a specific command through the user interface. For example, the user may scroll through the menu system and make a selection to initiate the VR mode. Alternatively, the VR mode may be initiated by the press of a button or a combination of buttons. Other methods to initiate the VR mode may also be employed.
0021Once the VR mode has been initiated, the VR module proceeds to listen to incoming audio from the audio channel that is received by the microphone. This audio is parsed by the VR module and the parsed audio segments are examined to determine if a predetermined command has been issued. In one embodiment a PTT call command is one of the predetermined commands that the VR module is capable of identifying. For example, a user may set up his/her personal VR system to identify the word CALL as the command to initiate a voice call. In such an embodiment, the same user may also set up his/her personal VR system to identify the word TALK as the command to initiate a PTT call. In alternative embodiments, various audio segments may be employed as the PTT call command.
0022Accordingly, in step <b>210</b>, the VR module identifies the PTT call command from the audio channel. In one embodiment, the VR module may request a confirmation in step <b>220</b> from the user that a PTT call command has been issued. This request may take the form of an audio signal such as a beep, a double beep, a customized audio segment, or synthesized speech.
0023If the user confirms that a PTT command has been issued, or if no such confirmation is required, the VR module next establishes a PTT call as shown in step <b>230</b>. In one embodiment, the VR module may pass a command to a PTT module, such as the PTT module previously described with respect to <figref idref="DRAWINGS">FIG. 2</figref>, to cause the PTT module to initiate the PTT call.
0024<figref idref="DRAWINGS">FIG. 4</figref> is a flow diagram illustrating an example process for facilitating an established PTT call through voice activation. Initially, in step <b>300</b>, the PTT call is established, for example by the process previously described with respect to <figref idref="DRAWINGS">FIG. 3</figref>. Once the PTT call is established, the VR module, such as the VR module previously described with respect to <figref idref="DRAWINGS">FIG. 2</figref>, begins to receive the audio stream, for example from the audio channel that is fed by the microphone on the handset. In one embodiment, the VR module continuously receives audio from the audio channel.
0025Next, in step <b>320</b>, the VR module parses the audio stream. The parsing may be carried out by procedures that break the audio stream into audio segments pursuant to a segmentation algorithm. For example, when a certain decibel level identified as no sound is met for a certain period of time, then a break in the audio stream is identified, where two consecutive breaks in the audio stream define either an audio segment or a no-audio segment. Audio segments can then be processed by the VR module to determine if they correlate to a predetermined audio command. The general operation of a VR module will be well understood by one having skill in the art.
0026With respect to the established PTT call, the VR module can be dynamically trained or configured to provide PTT specific commands to a PTT module such as the PTT module previously described with respect to <figref idref="DRAWINGS">FIG. 2</figref>. The VR module can also be trained for other PTT related commands such as commands related to adding to groups, setting user preferences and the like. In step <b>330</b>, the VR module analyzes audio segments that have been parsed from the audio stream to determine if an audio segment is a predefined PTT code word. If an audio segment is not a code word, the VR module continues parsing the received audio stream and analyzing parsed audio segments. If, however, an audio segment is identified as a PTT code word, the VR module executes the PTT command. In one embodiment, the VR module sends a signal to the PTT module to cause the PTT module to execute the particular PTT command. After execution of the PTT command, the VR module continues to receive, parse, and analyze the audio stream for PTT related code words.
Example Embodiment
0027In an example embodiment, a voice enabled PTT call may proceed in the following way. The VR module is activated by the user of the handset. The user speaks “TALK_JOE” into the microphone on the handset. The VR module receiving the audio stream from the microphone parses the audio segment TALK and determines that it is a PTT code word corresponding to the initiate PTT call command. The VR module additionally parses the audio segment JOE from the audio stream and determines that the JOE audio segment corresponds to the phone book entry on the handset for Joe Smith. The VR module obtains the necessary information for Joe Smith from the phone book entry and provides the PTT module with a communication instructing the PTT module to initiate a PTT call to Joe Smith. The PTT module then establishes the PTT call with Joe Smith.
0028In one embodiment, establishing the PTT call with Joe Smith causes an audible beep or chirp sound to be played through a speaker on the handset to indicate to the user that the call has been established. Alternative indicators may also be employed such as vibrating the handset, illuminating a portion of the handset (e.g., LED or display), or a different type of audio (e.g., synthesized speech).
0029Once the call has been established, the initiating user speaks into the phone without the need to depress any button or buttons during the speak time. When the initiating user is through speaking, the user speaks a code word that is received by the VR module. For example, the code word for when a user is finished speaking may be “OVER” or something similar.
0030In one embodiment, the VR module is configured to distinguish between spoken words that are used as a code word or are part of conversational speech. Continuing the same example above, the user may speak the word “OVER” as part of the conversation and then subsequently speak the work “OVER” again as a code word. The VR module is advantageously trained to differentiate between the different contextual uses of the word “OVER.” For example, the VR module may be trained to recognize a code word that is preceded by a certain amount of quiet input or followed by a certain amount of quiet input, or both. In such an embodiment, the conversational use of the word “OVER” would be either preceded or followed by (or both) other words and other sounds that are part of the conversational speech. When the user desires to use the code word “OVER” the user can pause for a predetermined amount of time before or after speaking the code word. Alternatively, the user may pause for a predetermined amount of time both before and after speaking the code word.
0031In alternative embodiments, the VR module may be sophisticated enough to differentiate between spoken code words and conversational use of the code word based on other factors such as the length of time during which the code word is spoken, the decibel level of the spoken code word, the enunciation of the code word, and other factors that allow the spoken code word to be differentiated from a conversational use of the code word.
0032Code words such as the initiate call code word, the end speaking code word, and others can be predetermined and dynamically learned by the VR module. Advantageously, different code words may be employed by different users for the same function. With respect to the PTT functionality, code words can be assigned to all off the various PTT functions including (but not limited to): initiate PTT call; begin speaking; end speaking; end PTT call; set presence, set availability, and group management, just to name a few. Other typical VR module functions such as phone book entry lookups can also be employed during PTT calls.
0033When the initiating user has finished speaking, the VR module receives the code word and instructs the PTT module to notify the recipient that the initiating user is finished speaking. The recipient may then proceed to speak in the normal course and when finished, the initiating user's handset receives a notice that the recipient is finished speaking. This notice can be provided to the initiating user through an audible beep or other type of signal. The PTT communication volley may then proceed until the conversation is completed and then the PTT call may be terminated. For example, the initiating can speak the words “END TALK” and those words are received by the VR module and an instruction is sent from the VR module to the PTT module to terminate the PTT call. In this fashion, a voice controlled PTT call can be established and carried out.
0034<figref idref="DRAWINGS">FIG. 5</figref> is a block diagram illustrating an exemplary wireless communication device <b>450</b> that may be used in connection with the various embodiments described herein. For example, the wireless communication device <b>450</b> may be used in conjunction with a PTT enabled handset <b>20</b> or <b>30</b> as previously described with respect to <figref idref="DRAWINGS">FIGS. 1 and 2</figref>. However, other wireless communication devices and/or architectures may also be used, as will be clear to those skilled in the art.
0035In the illustrated embodiment, wireless communication device <b>450</b> comprises an antenna <b>452</b>, a multiplexor <b>454</b>, a low noise amplifier (“LNA”) <b>456</b>, a power amplifier (“PA”) <b>458</b>, a modulation circuit <b>460</b>, a baseband processor <b>462</b>, a speaker <b>464</b>, a microphone <b>466</b>, a central processing unit (“CPU”) <b>468</b>, a data storage area <b>470</b>, and a hardware interface <b>472</b>. In the wireless communication device <b>450</b>, radio frequency (“RF”) signals are transmitted and received by antenna <b>452</b>. Multiplexor <b>454</b> acts as a switch, coupling antenna <b>452</b> between the transmit and receive signal paths. In the receive path, received RF signals are coupled from a multiplexor <b>454</b> to LNA <b>456</b>. LNA <b>456</b> amplifies the received RF signal and couples the amplified signal to a demodulation portion of the modulation circuit <b>460</b>.
0036Typically modulation circuit <b>460</b> will combine a demodulator and modulator in one integrated circuit (“IC”). The demodulator and modulator can also be separate components. The demodulator strips away the RF carrier signal leaving a base-band receive audio signal, which is sent from the demodulator output to the base-band processor <b>462</b>.
0037If the base-band receive audio signal contains audio information, then base-band processor <b>462</b> decodes the signal and converts it to an analog signal. Then the signal is amplified and sent to the speaker <b>464</b>. The base-band processor <b>462</b> also receives analog audio signals from the microphone <b>466</b>. These analog audio signals are converted to digital signals and encoded by the base-band processor <b>462</b>. The base-band processor <b>462</b> also codes the digital signals for transmission and generates a base-band transmit audio signal that is routed to the modulator portion of modulation circuit <b>460</b>. The modulator mixes the base-band transmit audio signal with an RF carrier signal generating an RF transmit signal that is routed to the power amplifier <b>458</b>. The power amplifier <b>458</b> amplifies the RF transmit signal and routes it to the multiplexor <b>454</b> where the signal is switched to the antenna port for transmission by antenna <b>452</b>.
0038The baseband processor <b>462</b> is also communicatively coupled with the central processing unit <b>468</b>. The central processing unit <b>468</b> has access to a data storage area <b>470</b>. The central processing unit <b>468</b> is preferably configured to execute instructions (i.e., computer programs or software modules) that can be stored in the data storage area <b>470</b>. Computer programs or software modules can also be received from the baseband processor <b>462</b> and stored in the data storage area <b>470</b> or executed upon receipt. Such computer programs, when executed, enable the wireless communication device <b>450</b> to perform the various functions of the present invention as previously described.
0039In this description, the term “computer readable medium” is used to refer to any media used to provide executable instructions (e.g., software and computer programs) to the wireless communication device <b>450</b> for execution by the central processing unit <b>468</b>. Examples of these media include the data storage area <b>470</b>, microphone <b>466</b> (via the baseband processor <b>462</b>), antenna <b>452</b> (also via the baseband processor <b>462</b>), and hardware interface <b>472</b>. These computer readable mediums are means for providing executable code, programming instructions, and software to the wireless communication device <b>450</b>. The executable code, programming instructions, and software, when executed by the central processing unit <b>468</b>, preferably cause the central processing unit <b>468</b> to perform the inventive features and functions previously described herein.
0040The central processing unit is also preferably configured to receive notifications from the hardware interface <b>472</b> when new devices are detected by the hardware interface. Hardware interface <b>472</b> can be a combination electromechanical detector with controlling software that communicates with the CPU <b>468</b> and interacts with new devices.
0041<figref idref="DRAWINGS">FIG. 6</figref> is a block diagram illustrating an exemplary computer system <b>550</b> that may be used in connection with the various embodiments described herein. For example, the computer system <b>550</b> may be used in conjunction with a PDSN or PTT server as previously described with respect to <figref idref="DRAWINGS">FIG. 1</figref>. However, other computer systems and/or architectures may be used, as will be clear to those skilled in the art.
0042The computer system <b>550</b> preferably includes one or more processors, such as processor <b>552</b>. Additional processors may be provided, such as an auxiliary processor to manage input/output, an auxiliary processor to perform floating point mathematical operations, a special-purpose microprocessor having an architecture suitable for fast execution of signal processing algorithms (e.g., digital signal processor), a slave processor subordinate to the main processing system (e.g., back-end processor), an additional microprocessor or controller for dual or multiple processor systems, or a coprocessor. Such auxiliary processors may be discrete processors or may be integrated with the processor <b>552</b>.
0043The processor <b>552</b> is preferably connected to a communication bus <b>554</b>. The communication bus <b>554</b> may include a data channel for facilitating information transfer between storage and other peripheral components of the computer system <b>550</b>. The communication bus <b>554</b> further may provide a set of signals used for communication with the processor <b>552</b>, including a data bus, address bus, and control bus (not shown). The communication bus <b>554</b> may comprise any standard or non-standard bus architecture such as, for example, bus architectures compliant with industry standard architecture (“ISA”), extended industry standard architecture (“EISA”), Micro Channel Architecture (“MCA”), peripheral component interconnect (“PCI”) local bus, or standards promulgated by the Institute of Electrical and Electronics Engineers (“IEEE”) including IEEE 488 general-purpose interface bus (“GPIB”), IEEE 696/S-100, and the like.
0044Computer system <b>550</b> preferably includes a main memory <b>556</b> and may also include a secondary memory <b>558</b>. The main memory <b>556</b> provides storage of instructions and data for programs executing on the processor <b>552</b>. The main memory <b>556</b> is typically semiconductor-based memory such as dynamic random access memory (“DRAM”) and/or static random access memory (“SRAM”). Other semiconductor-based memory types include, for example, synchronous dynamic random access memory (“SDRAM”), Rambus dynamic random access memory (“RDRAM”), ferroelectric random access memory (“FRAM”), and the like, including read only memory (“ROM”).
0045The secondary memory <b>558</b> may optionally include a hard disk drive <b>560</b> and/or a removable storage drive <b>562</b>, for example a floppy disk drive, a magnetic tape drive, a compact disc (“CD”) drive, a digital versatile disc (“DVD”) drive, a multi-media card (“MMC”) or other solid state storage device, etc. The removable storage drive <b>562</b> reads from and/or writes to a removable storage medium <b>564</b> in a well-known manner. Removable storage medium <b>564</b> may be, for example, a floppy disk, magnetic tape, CD, DVD, etc.
0046The removable storage medium <b>564</b> is preferably a computer readable medium having stored thereon computer executable code (i.e., software) and/or data. The computer software or data stored on the removable storage medium <b>564</b> is read into the computer system <b>550</b> as electrical communication signals <b>578</b>.
0047In alternative embodiments, secondary memory <b>558</b> may include other similar means for allowing computer programs or other data or instructions to be loaded into the computer system <b>550</b>. Such means may include, for example, an external storage medium <b>572</b> and an interface <b>570</b>. Examples of external storage medium <b>572</b> may include an external hard disk drive or an external optical drive, or and external magneto-optical drive.
0048Other examples of secondary memory <b>558</b> may include semiconductor-based memory such as programmable read-only memory (“PROM”), erasable programmable read-only memory (“EPROM”), electrically erasable read-only memory (“EEPROM”), or flash memory (block oriented memory similar to EEPROM). Also included are any other removable storage units <b>572</b> and interfaces <b>570</b>, which allow software and data to be transferred from the removable storage unit <b>572</b> to the computer system <b>550</b>.
0049Computer system <b>550</b> may also include a communication interface <b>574</b>. The communication interface <b>574</b> allows software and data to be transferred between computer system <b>550</b> and external devices (e.g. printers), networks, or information sources. For example, computer software or executable code may be transferred to computer system <b>550</b> from a network server via communication interface <b>574</b>. Examples of communication interface <b>574</b> include a modem, a network interface card (“NIC”), a communications port, a PCMCIA slot and card, an infrared interface, and an IEEE 1394 fire-wire, just to name a few.
0050Communication interface <b>574</b> preferably implements industry promulgated protocol standards, such as Ethernet IEEE 802 standards, Fiber Channel, digital subscriber line (“DSL”), asynchronous digital subscriber line (“ADSL”), frame relay, asynchronous transfer mode (“ATM”), integrated digital services network (“ISDN”), personal communications services (“PCS”), transmission control protocol/Internet protocol (“TCP/IP”), serial line Internet protocol/point to point protocol (“SLIP/PPP”), and so on, but may also implement customized or non-standard interface protocols as well.
0051Software and data transferred via communication interface <b>574</b> are generally in the form of electrical communication signals <b>578</b>. These signals <b>578</b> are preferably provided to communication interface <b>574</b> via a communication channel <b>576</b>. Communication channel <b>576</b> carries signals <b>578</b> and can be implemented using a variety of wired or wireless communication means including wire or cable, fiber optics, conventional phone line, cellular phone link, wireless data communication link, radio frequency (RF) link, or infrared link, just to name a few.
0052Computer executable code (i.e., computer programs or software) is stored in the main memory <b>556</b> and/or the secondary memory <b>558</b>. Computer programs can also be received via communication interface <b>574</b> and stored in the main memory <b>556</b> and/or the secondary memory <b>558</b>. Such computer programs, when executed, enable the computer system <b>550</b> to perform the various functions of the present invention as previously described.
0053In this description, the term “computer readable medium” is used to refer to any media used to provide computer executable code (e.g., software and computer programs) to the computer system <b>550</b>. Examples of these media include main memory <b>556</b>, secondary memory <b>558</b> (including hard disk drive <b>560</b>, removable storage medium <b>564</b>, and external storage medium <b>572</b>), and any peripheral device communicatively coupled with communication interface <b>574</b> (including a network information server or other network device). These computer readable mediums are means for providing executable code, programming instructions, and software to the computer system <b>550</b>.
0054In an embodiment that is implemented using software, the software may be stored on a computer readable medium and loaded into computer system <b>550</b> by way of removable storage drive <b>562</b>, interface <b>570</b>, or communication interface <b>574</b>. In such an embodiment, the software is loaded into the computer system <b>550</b> in the form of electrical communication signals <b>578</b>. The software, when executed by the processor <b>552</b>, preferably causes the processor <b>552</b> to perform the inventive features and functions previously described herein.
0055Various embodiments may also be implemented primarily in hardware using, for example, components such as application specific integrated circuits (“ASICs”), or field programmable gate arrays (“FPGAs”). Implementation of a hardware state machine capable of performing the functions described herein will also be apparent to those skilled in the relevant art. Various embodiments may also be implemented using a combination of both hardware and software.
0056Furthermore, those of skill in the art will appreciate that the various illustrative logical blocks, modules, circuits, and method steps described in connection with the above described figures and the embodiments disclosed herein can often be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled persons can implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the invention. In addition, the grouping of functions within a module, block, circuit or step is for ease of description. Specific functions or steps can be moved from one module, block or circuit to another without departing from the invention.
0057Moreover, the various illustrative logical blocks, modules, and methods described in connection with the embodiments disclosed herein can be implemented or performed with a general purpose processor, a digital signal processor (“DSP”), an ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be any processor, controller, microcontroller, or state machine. A processor can also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
0058Additionally, the steps of a method or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium including a network storage medium. An exemplary storage medium can be coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can also reside in an ASIC.
0059From the above description of exemplary embodiments of the invention, it is manifest that various techniques can be used for implementing the concepts of the present invention without departing from its scope. Moreover, while the invention has been described with specific reference to certain embodiments, a person of ordinary skill in the art would recognize that changes could be made in form and detail without departing from the spirit and the scope of the invention. The described exemplary embodiments are to be considered in all respects as illustrative and not restrictive. It should also be understood that the invention is not limited to the particular exemplary embodiments described herein, but is capable of many rearrangements, modifications, and substitutions without departing from the scope of the invention.
Contents5
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8971217B2 | Cited by | United States of America | Search report |
| US10142802B2 | Cited by | United States of America | Applicant |
| WO2018087567A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US8442578B2 | Cited by | United States of America | Search report |
| US10187759B2 | Cited by | United States of America | Applicant |
| US9912706B2 | Cited by | United States of America | Applicant |
| US2010009719A1 | Cited by | United States of America | Pre-grant |
| EP2146491A1 | Cited by | European Patent Office (EPO) | Search report |
| US8428654B2 | Cited by | United States of America | Applicant |
| US2007280254A1 | Cited by | United States of America | Pre-grant |
| US9204263B2 | Cited by | United States of America | Applicant |
| US10110430B2 | Cited by | United States of America | Applicant |
| US2008002667A1 | Cited by | United States of America | Pre-grant |
| US9392421B2 | Cited by | United States of America | Applicant |
| WO2013177020A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2011095916A1 | Cited by | United States of America | Pre-grant |
| US9674694B2 | Cited by | United States of America | Applicant |
| WO2013177020A2 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| WO2010078386A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2008045256A1 | Cited by | United States of America | Pre-grant |
| US2008012701A1 | Cited by | United States of America | Pre-grant |
| US10462003B2 | Cited by | United States of America | Applicant |
| US9560099B2 | Cited by | United States of America | Applicant |
| US7894849B2 | Cited by | United States of America | Search report |
| US10924339B2 | Cited by | United States of America | Applicant |
| WO2016191653A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| US2005209858A1 | Cites | United States of America | Pre-grant |
| US2005239487A1 | Cites | United States of America | Pre-grant |
| US2006268750A1 | Cites | United States of America | Pre-grant |
| US5148471A | Cites | United States of America | Pre-grant |
| US5371901A | Cites | United States of America | Pre-grant |
| US5792204A | Cites | United States of America | Pre-grant |
| US6167255A | Cites | United States of America | Pre-grant |
| US6212408B1 | Cites | United States of America | Pre-grant |
| US6449496B1 | Cites | United States of America | Pre-grant |
| US6535743B1 | Cites | United States of America | Pre-grant |
| US6553223B1 | Cites | United States of America | Pre-grant |
| US6554707B1 | Cites | United States of America | Pre-grant |
| US6681124B2 | Cites | United States of America | Pre-grant |
2 priority claims, no other members on record
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 5320705 | United States of America | A | |
| US20050053207 | – | – | – |
83 transactions on the USPTO file
Abandoned after 3 non-final rejections, 3 final rejections, 2 RCEs and 1 appeal.
- Non-final rejections
- 3
- Final rejections
- 3
- RCEs
- 2
- Appeals
- 1
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Email NotificationEML_NTR | EML_NTR | |
| Mailing of Abandonment after Board of AppealsAbandonedMABN10 | MABN10 | |
| Abandonment after Board of AppealsAbandonedABN10 | ABN10 | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail BPAI Decision on Appeal - AffirmedMAPDA | MAPDA | |
| BPAI Decision - Examiner AffirmedAPDA | APDA | |
| Email NotificationEML_NTR | EML_NTR | |
| Docketing Notice Mailed to AppellantAP_DK_M | AP_DK_M | |
| Assignment of Appeal NumberAPAS | APAS | |
| Email NotificationEML_NTR | EML_NTR | |
| Mail Reply Brief Noted by ExaminerMRBNE | MRBNE | |
| Appeal Awaiting BPAI DocketingAPWD | APWD | |
| Reply Brief Noted by ExaminerRBNE | RBNE | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Reply Brief FiledAPRB | APRB | |
| Exam. Ans. Review CompletePACC | PACC | |
| Electronic ReviewELC_RVW | ELC_RVW | |
| Email NotificationEML_NTF | EML_NTF | |
| Mail Examiner's AnswerMAPEA | MAPEA | |
| Examiner's Answer to Appeal BriefAPEA | APEA | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Appeal Brief Review CompleteAPBR | APBR | |
| Appeal Brief FiledAP.B | AP.B | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Appeals conf. Proceed to BPAIMAPCP | MAPCP | |
| Pre-Appeals Conference Decision - Proceed to BPAIAPCP | APCP | |
| Request for Pre-Appeal Conference FiledAP.C | AP.C | |
| Notice of Appeal FiledN/AP | N/AP | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Mail Advisory Action (PTOL - 303)MCTAV | MCTAV | |
| Advisory Action (PTOL-303)CTAV | CTAV | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Examiner Interview Summary Record (PTOL - 413)EXIN | EXIN | |
| Response after Final ActionA.NE | A.NE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Disposal for a RCE / CPA / R129AbandonedABN9 | ABN9 | |
| Request for Continued Examination (RCE)RCEX | RCEX | |
| Workflow - Request for RCE - BeginBRCE | BRCE | |
| Mail Final Rejection (PTOL - 326)Final rejectionMCTFR | MCTFR | |
| Final RejectionFinal rejectionCTFR | CTFR | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| Response after Non-Final ActionA... | A... | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Information Disclosure Statement consideredIDSC | IDSC | |
| Reference capture on IDSRCAP | RCAP | |
| Information Disclosure Statement (IDS) FiledM844 | M844 | |
| Information Disclosure Statement (IDS) FiledWIDS | WIDS | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| IFW TSS Processing by Tech Center CompleteTSSCOMP | TSSCOMP | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Return from OIPEWROIPE | WROIPE | |
| Application Return TO OIPEROIPE | ROIPE | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Cleared by OIPE CSRL194 | L194 | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
4 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Information on status: application discontinuationABANDONED -- AFTER EXAMINER'S ANSWER OR BOARD OF APPEALS DECISIONSTCB | STCB | |
| AssignmentAS | AS | |
| AssignmentAS | AS | |
| AssignmentAS | AS |
Numbers
- Publication
- 20060178159
- Publication, DOCDB
- 2006178159
- Publication, EPODOC
- US2006178159
- Application
- 11053207
- Application, DOCDB
- 5320705
- Application, EPODOC
- US20050053207
Titles
- English
- Voice activated push-to-talk device and method of use
Classification
- CPC, 7
- H04M1/271
- H04L65/1016
- H04L65/4061
- H04M2250/74
- H04W4/10
- H04W76/45
- H04M1/72403
- IPC, 1
- H04B7 00
- USPC, 2
- 455518000
- 455519000