US 7,499,716 B2Grant
System and method for delivering information to a transmitting and receiving device
Issue Date:2009-03-03
•69 Claims
•13 Drawing Sheets
Abstract
The present invention provides systems and method for delivering information to a transmitting and receiving device. The device receives a notification alerting a user of the device that information is available to be obtained and, in some embodiments, providing a short description of the information. After receiving the notification at the device, the user can then use the device to obtain or otherwise act on the information at a time and at a place convenient to the user.
Metadata
Assignee
- Wireless Science, LLC
Inventor
- Richard J. Helferich
Application Information
Application Number:US 11/399,513
Filing Date:2006-04-07
Priority Date:1997-09-19
Art Unit:2618
Classifications
IPC:
H04Q7/00
Patent Drawings (13 sheets)
Description
[0001] This application is a continuation of U.S. patent application Ser. No. 09/688,282, filed on Oct. 13, 2000 (now U.S. Pat. No. 7,039,428), which is a divisional of U.S. patent application Ser. No. 08/933,344, filed on Sep. 19, 1997 (Now U.S. Pat. No. 6,253,061). The contents of the above referenced applications are incorporated herein by this reference.
Related Applications
[0002] Reference is made to the following patented patent applications: (1) Ser. No. 08/934,337 (now U.S. Pat. No. 6,259,892); (2) Ser. No. 08/934,143 (now U.S. Pat. No. 6,233,430); (3) Ser. No. 08/934,132 (now U.S. Pat. No. 6,087,956); (4) Ser. No. 09/860,954 (now U.S. Pat. No. 6,462,646); (5) Ser. No. 10/236,932 (now U.S. Pat. No. 6,696,921); (6) Ser. No. 09/688,321 (now U.S. Pat. No. 7,003,304); (7) Ser. No. 09/613,345 (now U.S. Pat. No. 6,459,360); (8) Ser. No. 11/049,869 (status: pending); (9) Ser. No. 11/050,775 (status: pending); (10) Ser. No. 11/082,913 (status: pending); (11) Ser. No. 11/081,611 (status: pending); (12) Ser. No. 11/082,872 (status: pending); and (13) Ser. No. 11/083,897 (status: pending).
Background of the Invention
[0003] 1. Field of the Invention
[0004] The present invention relates generally to systems and methods for selective paging and, more particularly, to paging systems and methods for selectively paging in response to messages received at a plurality of sources.
[0005] 2. Discussion of the Background
[0006] In general, a paging receiver can be classified into one of four categories: an alert or tone only paging receiver, a numeric paging receiver, an alphanumeric paging receiver, or a voice paging receiver. One common characteristic of all of these paging receivers is that they monitor the air waves and notify the user when their particular address has been detected. For the alert or tone only paging receiver, the paging receiver would generate a tone or beep when its address is detected. The other paging receivers, upon detecting their address, would additionally store a message associated with the address signal and display or play it to the user. The message for a numeric paging receiver would be a set of numbers, typically the calling person's telephone number, and the message for an alphanumeric paging receiver would be a set of numbers and/or letters. The user of an alphanumeric paging receiver could therefore receive a message in the form of a telephone number with some descriptive text. For the voice paging receiver, the message that is stored is a voice message that the user can later play to hear the message.
[0007] A paging receiver is typically a rather small electronic device and, accordingly, has a limited amount of memory for storing messages that have been received from a base station in a paging system. Because of the relatively small size of the memory, the paging receiver can store only a limited number of messages. A user can delete messages from memory but will oftentimes desire to save a message, such as temporarily until the user makes a note of the message or until he or she is able to respond to the page. The messages that are saved in memory, however, reduce the space in memory that is available to receive new messages. This demand on space in memory is increasing as the size of the messages continue to grow and as users receive a greater number of messages. Although more memory can be added to accommodate more messages, the added cost and space needed for extra memory runs counter to the desires to keep the paging receiver small and inexpensive. A need therefore exists for a paging receiver which can display and/or play messages while efficiently using memory.
[0008] In addition to the demand on paging receiver memory, paging systems will be challenged as greater numbers of pages are being transmitted and as the size of the transmitted messages increases. Initially, when paging systems were only concerned with transmitting address signals of the paging receivers, the size of each transmission by the paging systems was relatively small. Paging receivers and paging systems, however, have undergone tremendous advances with paging systems now transmitting messages which can be hundreds of kilobytes or greater in size in addition to the address signals. Additionally, many paging receivers are actually paging transceivers which transmit acknowledgment signals back through the paging system. The capacity of the paging systems are therefore being challenged not only by messages of increasing sizes but also by reply signals transmitted from the paging transceivers to the paging system. The future of paging systems is therefore tied to the ability of the paging systems to control the number and size of the data transmissions and to provide additional features without sacrificing the quality of service to the user.
[0009] As discussed above, many paging transceivers are able to issue a reply or acknowledgment back to the base station in response to a received message. If the base station does not receive this reply or acknowledgment, then the base station assumes that the message has not been received and will repeatedly transmit the message until the reply or acknowledgment is received. Due to the high power levels at which the base station transmits its paging signals, the signals are usually easily received by all paging transceivers located within the coverage area of the base station antenna. The paging transceivers, on the other hand, must operate at lower power levels and often cannot transmit signals at sufficiently high levels to reach the base station. For example, when a paging transceiver is located in a basement of a building, in a subway, or in an airplane, the paging transceiver may be unable to issue a reply that can reach the base station. As a result, the base station may continue to transmit a page to a paging transceiver and the paging transceiver will continue to receive the message but the base station cannot detect the reply being issued by the paging transceiver. This unnecessary transmission of duplicate messages and the ineffectual reply signals transmitted by the paging transceivers consume valuable resources of the paging system and of the paging transceiver.
[0010] For safety reasons, a user may at times have to turn off his or her paging transceiver. For instance, when the user is on an airplane, the transmissions from the paging transceiver can interfere with the instrumentation or communication within the cockpit of the plane. The paging transceiver therefore should not be operating within the plane or around other electronic equipment that are sensitive to interference from the signals transmitted by the paging transceiver. As another example, if the user is in an environment that contains electronic detonators for explosive materials, the signals transmitted by the paging transceiver could possibly trigger an explosion. The user therefore must turn his or her paging transceiver off to ensure that it does not transmit any reply or acknowledgment signals in response to a received page. Although it may be dangerous for the paging transceiver to issue a reply signal in these situations, the signals transmitted by the base station may at times be safely received by the paging transceiver. Since the paging transceiver automatically issues a reply in response to a received message, the paging transceiver must nonetheless be turned off so as to not pose a risk to the user. During these times that the paging transceiver must be turned off, the user unfortunately is unable to receive any page or message. A need therefore exists for a paging transceiver that can notify a user of a message without automatically generating a reply message or acknowledgment to the base station.
Summary of the Invention
[0011] The present invention solves the problems described above with methods and systems for selective paging. A paging system notifies a paging transceiver that a message has been received but does not initially transmit the associated message. The user, upon being notified of the message, can then download the entire message at a time convenient to the user, which allows the user to download messages at less expensive off-peak hours and allows the user to place the paging transceiver at a location where it can easily receive the message and reply to the message. Since the messages are not initially transmitted to the paging transceiver, the paging transceiver can receive and store a greater number of pages with minimal increase in the size of memory. Further, because entire messages are not automatically transmitted and since the user can position the paging transceiver to issue a sufficiently strong reply, traffic in the paging system can be controlled and actually reduced.
[0012] The system may transmit some identifying information about the page to the user without sending the entire message. For instance, the base station may identify the type of message, such as email, voice, or text, and also indicate the caller or other descriptive material about the message. The user can then determine the priority of the message and whether he or she wants to retrieve the message, play the message, erase the message, store the message, forward, reply, or otherwise act on the message. The user is also given control over the messages stored remotely from the paging transceiver and can erase or store these messages from the paging transceiver. The paging transceiver may have a timer for allowing the user to program the paging transceiver to perform a desired function on a message at a particular time.
[0013] The information initially sent to the user may also indicate the location of the stored message. For instance, the system paging a particular paging transceiver to notify it that a page has been received need not be the system actually storing the content of the message. Instead, a plurality of systems may store the contents of messages with one or more of the systems paging the paging transceiver. The paging transceiver would be provided sufficient information on the system storing the message so that it can communicate with this system. The system paging the paging transceiver can therefore act as a clearinghouse for other messaging systems by notifying a user of all messages received regardless of their source or type.
[0014] Accordingly, it is an object of the present invention to provide systems and methods for paging that conserve memory in paging transceivers.
[0015] It is another object of the present invention to provide systems and methods for paging that conserve valuable air time.
[0016] It is a further object of the present invention to provide systems and methods for paging that provide users with remote control over their messages.
[0017] It is yet another object of the present invention to provide systems and methods for paging that allow users to select when and how action should be taken on their messages.
[0018] It is yet a further object of the present invention to provide messaging systems and methods for notifying users of received messages.
[0019] It is also an object of the present invention to provide messaging systems and methods for providing control to users over messages stored at remote locations.
[0020] It is still another object of the present invention to provide messaging systems and methods that notify users of messages received from multiple sources.
Brief Description of the Drawings
[0021] The accompanying drawings, which are incorporated in and form a part of the specification, illustrate preferred embodiments of the present invention and, together with the description, serve to explain the principles of the invention. In the drawings:
[0022] FIG. 1 is a block diagram of a paging transceiver according to a preferred embodiment of the invention;
[0023] FIG. 2 is a more detailed block diagram of the transceiver in the paging transceiver of FIG. 1 ;
[0024] FIG. 3 is a block diagram of a communication system according to a preferred embodiment of the invention;
[0025] FIGS. 4A and 4B are flow charts depicting an exemplary set-up routine for establishing communications between the system of FIG. 3 and the transceiver of FIG. 1 ;
[0026] FIG. 5 is a flow chart depicting a paging process;
[0027] FIG. 6 a flow chart depicting of process of notifying a paging transceiver of an unread message;
[0028] FIG. 7 is a flow chart depicting a process of receiving a page at the paging transceiver of FIG. 1 ;
[0029] FIG. 8 is a flow chart depicting a process of selecting a function at the paging transceiver of FIG. 1 ;
[0030] FIG. 9 is a generic flow chart depicting a selective process performed at the paging transceiver of FIG. 1 for executing a desired function;
[0031] FIG. 10 is a block diagram of a paging system having multiple systems for storing messages; and
[0032] FIG. 11 is a diagram of a data transmission for the system in FIG. 10 .
Detailed Description of Preferred Embodiments
[0033] Reference will now be made in detail to preferred embodiments of the invention, non-limiting examples of which are illustrated in the accompanying drawings. With reference to FIG. 1 , a paging transceiver 100 according to a preferred embodiment of the invention comprises an antenna 1, a transceiver 2, a user interface 3, a controller 4, and a memory 5. The single antenna 1 is preferably used for both receiving and transmitting signals, although the paging transceiver 100 may comprise a separate antenna for transmitting signals and a separate antenna for receiving signals.
[0034] The transceiver 2 is connected to the antenna I and is for transmitting signals from the paging transceiver 100 and for receiving signals directed to the paging transceiver 100. The signals that may be transmitted to, or received from, the paging transceiver 100 include, but are not limited to, such signals as selective call signals, command data signals, signals corresponding to a message, and information data signals. The transceiver 2 may comprise a transceiver found in two way pagers or mobile radios and preferably comprises a transceiver commonly used in a portable mobile radiotelephone.
[0035] The transceiver 2 is connected to the user interface 3, which contains all necessary input and output devices. The user interface 3 includes a microphone, speaker, alert transducer, LED or LCD display, keypad, and necessary switches. The user interface 3 may also contain other types of input/output devices depending on the messaging application, such as a video display, camera, scanner, a printer, or a voice recognition device. The user interface 3 is not limited to these examples of user input/output devices but may comprise any input or output device which allows or assists communication between the user and the paging transceiver 100.
[0036] The transceiver 2 is connected to, and communicates with, the controller 4, which preferably comprises a digital signal processor (DSP) 4. The memory 5 is connected to the DSP 4 and is for storing messages or other types of information. The memory 5 may comprise static RAM, Dynamic RAM, Flash RAM, or any type of memory suitable for storing messages and allowing the retrieval of the messages. The amount of the memory 5 is preferably at least 4 MB for voice or text applications, although it may consist of a greater or lesser amount depending upon the specific message type application.
[0037] The transceiver 2, as shown in more detail in FIG. 2 , includes an antenna interface 20 connected to the antenna 1 The antenna interface 20 directs signals received from antenna 1 to a receiver section 21 of the paging transceiver 100 and directs signals transmitted from a transmit section 24 to the antenna 1. The antenna interface 20 is preferably a duplexer, however an antenna switch or other device may be utilized to provide signal isolation between the receiver and transmitter sections 21 and 24. Alternatively, if paging transceiver 100 includes two antennas 1 with one for transmitting signals and the other for receiving signals, the transceiver 2 would not require any type of antenna interface 20.
[0038] The receive section 21 includes a receiver 22 and a receiver frequency synthesizer 23. The receiver 22 is connected to the antenna 1 through antenna interface 20 and receives the signals directed to the paging transceiver 100. The receiver frequency synthesizer 23, based on an input from a processor 27, selects the frequency at which the receiver 22 receives signals. The received signals are passed from the receiver 22 to the processor 27.
[0039] The transmit section 24 includes a transmitter 25 for receiving signals from the processor 27. The transmit section 24 also includes a transmitter frequency synthesizer 26 connected to the transmitter 25 which, based upon an input from the processor 27, selects the transmit frequency for the transmitter 25. The signals output by the transmitter 25 are supplied to the antenna interface 20 and then to the antenna 1.
[0040] The processor 27 comprises a central processing unit (CPU) having internal memory and switching capabilities. The CPU 27, for instance, comprises all necessary RAM and ROM memory, signal and data switching circuitry, signal processing circuitry, I-O Ports, and all standard program instructions and stored options commonly utilized in portable cellular telephones. The standard cellular telephone program instructions and CPU 27 may be obtained from a variety of suppliers. For instance, the instructions may be obtained from Wireless Link Inc. of Sunnyvale, Calif. and the CPU 27 from GEC Plessey Semiconductor, Inc. of Scotts Valley, Calif.
[0041] The DSP 4 includes necessary I-O and program memory and are commonly utilized in cellular telephones. Any suitable DSP may be used in the paging transceiver 100. Alternatively, the controller 4 may comprise another type of electronic device, such as a codec or digital-to-analog/analog-to-digital conversion circuit or other type of modulator-demodulator including memory interface circuitry coupled to message memory 5 for reading and writing of messages.
[0042] The transceiver 2 also preferably includes a delay circuit 28. The delay circuit 28 may comprise a timer which informs the processor 27 of when a period of time has expired. The timer, for instance, may expire at a certain time of day, week, or month, or may expire a fixed period of time after a triggering event, such as one hour after the event. The time at which the timer 28 expires is preferably programmable through the user interface 3 and through processor 27. Additionally, the timer 28 preferably comprises a plurality of timers for notifying the processor 27 of when a plurality of different time periods have expired. Rather than a timer, the delay circuit 28 may alternatively operate to delay the occurrence of an event until a certain condition is satisfied. This condition, for instance, may be the strength of received signals or the receipt of a specified signal. The purpose of the timer 28 will become apparent from the description below.
[0043] With reference to FIG. 3 , a system 30 according to a preferred embodiment of the invention is interconnected to a base station 34, both of which are connected to the Public Switched Telephone Network (PSTN) or to other telephone company equipment 35. The system 30 comprises a paging terminal controller 31 which may comprise a controller circuit and associated memory having a database of subscriber listings and corresponding selective call address fields. The paging terminal controller 31 communicates with storage and retrieval unit 32 and correlates messages with subscriber listings. The storage and retrieval unit 32 may comprise a CPU or control circuit, message information and program memory, memory interface circuitry and a DSP with appropriate operational code for storage and retrieval of the desired messages. The input/output controller 33 contains all necessary input and output circuitry such as encoders and decoders, modems and required routing and control circuitry for communicating with the paging terminal controller 31, the storage and retrieval unit 32, the PSTN 35, and the base station 34.
[0044] A call setup routine 40 for establishing communication between the system 30 and base station 34 will now be described with reference to FIGS. 4A and 4B . At step 41, a connection, such as a telephone connection, is routed through the PSTN 35 or in the case of paging transceiver 100 the switch 36, to the input/output controller 33. The input/output controller 33 determines at step 42 whether the connection is with an automated signaling device or with a person. If the connection is with a person, then at step 48 the storage and retrieval unit 32 is activated to produce one or more voice responses during the call in order to guide the person throughout the process.
[0045] If, at step 42, the input/output controller 33 determines that the call is from a device, such as a paging transceiver 100 or computer terminal, data is exchanged between the paging transceiver 100 and system 30 at step 43. The type of data that may be exchanged includes, but is not limited to, the following types of data: identification data, command data, and information data. The data supplied from the PSTN 35 may also be exchanged at step 43 with this data including data for identifying the caller and subscriber, such as, for example, Caller ID and DNIS (Dialed Number Identification Service). Additionally, the data may be extracted from the base station 34. For example, the location of the paging transceiver 100 may be determined from a home location registry (HLR) and the HLR data may be utilized by the system 30 in order to determine the location of the paging transceiver 100, as opposed to having the paging transceiver 100 supply the location information to system 30.
[0046] After data is exchanged at step 43, the system 30 determines at step 44 whether an error occurred during the transmission between the system 30 and paging transceiver 100. If an error did occur, then at step 47 the process ends and the paging transceiver 100 is informed of the error. The error is preferably presented to the user in the form of status information produced at the user interface 3, such as with an alert tone or visual display on the LED or LCD display. An error may include, but is not limited to, the following errors: “system busy,” “wrong ID,” or “bill over due.” If no error is detected, as determined by the system 30 at step 44, a function is enabled and executed at step 45. The function, as will be described in greater detail below with reference to FIG. 8 , may be selected by the user from a group of available functions. At step 46, housekeeping functions are performed both at the paging transceiver 100 and at the system 30 and the call is terminated at step 47.
[0047] If the call is from a person as determined at step 42, then the caller is provided with a voice response at step 48 and, with reference to FIG. 4B , the caller is then verbally prompted at step 49 to enter information. At step 50, the caller sends data to the system 30, such as by pressing the telephone keypad to generate DTMF tones. The data that may be sent by the caller includes, but is not limited to, ID code, pass code, mail box number, and subscriber number. The system 30 may respond to voice commands from a caller by utilizing a readily available voice recognition system, such as those presently in use by the telephone company to except collect calls. At 51, the system 30 determines whether an error has occurred. If an error is detected, the caller may be given an opportunity to correct the error or, as shown, the process may end at step 56. If no error was detected by the system 30 at step 51, a message, such as a voice message, is recorded and stored in the storage and retrieval unit 32 at step 52. At step 53, the system 30 determines whether a return receipt or a reply message is requested. If a return receipt or reply message is requested, the return address is entered by the caller or optionally issued by the system 30 and is stored by the system 30 in the storage and retrieval unit 32 at step 54. The system 30, for instance, may detect the address signal of the incoming call and, by default, store this number as the return address. After the return address is stored at step 54 or if a return address is not requested, the stored message is cross referenced to selective call data corresponding to the intended paging transceiver 100 at step 55 . Also at step 55, a flag is set in a transmission stack file at the paging terminal controller 31 for subsequently transmitting selective call signals representative of the selective call data to the targeted paging transceiver 100. Housekeeping is performed by the system 30 and the call ends at step 56.
[0048] The base station 34, as shown in FIG. 3 , comprises a switch 36, a transceiver antenna 37, and a transceiver base station 38. In response to a received message, the system 30 passes control information to switch 36 for setting up a page call. The switch 36, for instance, may be a mobile telephone switching office (MTSO) for interfacing to the transceiver base station 38. In the send page mode, selective call signals having an address associated with the paging transceiver 100 are transmitted. The address may be an address code for a paging transceiver, a mobile telephone number (MIN) for a mobile radiotelephone, or type of identifying information for a communication device.
[0049] Command data and information data may also be communicated from the system 30 to the paging transceiver 100 through the base station 34. The command data and information data shall hereinafter be referred to as CI data, examples of which include the following: paging transceiver location, forward message, retrieve message, reply to message, paging transceiver ID, message identifiers, retrieval instructions, save message, erase message, message type, message length, time/date message received, system 30 ID, system 30 location, message address, message location, battery life, message identifier, format code, compression type, message age, message priority, alert codes, energy saving commands, memory status, program data, provisioning data, acknowledgment data and requests, function codes, sender name, current time, number of messages, mailbox number, phone number, return address, alpha numeric short messages, general command requests, group calls, and signal strength.
[0050] The address and command data and information may be transmitted over any suitable communication system. For instance, the data may be communicated over a paging system, a cellular system having short message service capabilities, such as GSM-SMS, a Cellular Digital Packet Data (CDPD) system, Personal Communications Services, or any other type of mobile radiotelephone system or communication system. Furthermore, the paging transceiver 100 preferably is able to communicate over more than one system, such as with both a paging network and a mobile radiotelephone network.
[0051] With reference to FIG. 5 , a flow diagram 60 for performing a page call is shown. At step 61, the system 30 locates the current message flag from its transmission stack within paging terminal controller 31 and communicates with base station 34 for setting up a page call. The base station 34 transmits selective call signals and CI data to the targeted paging transceiver 100. At step 62, the system 30 determines whether an acknowledgment (Ack) was received from the paging transceiver 100 indicating that the page call was received. If an acknowledgment was not received, then at step 70 the system 30 determines whether an acknowledgment is a system 30 option. If an acknowledgment is required, then at step 71 the system 30 assigns the page call a priority in the transmission stack and eventually returns to step 61 for re-transmission. If the acknowledgment is received at step 62, the system 30 sets an acknowledgment flag (Ack flag) corresponding to the stored message.
[0052] If an acknowledgment is not a system requirement, as determined at step 70, or after posting the acknowledgment flag at step 63, the system 30 sets a timer at step 64 and waits a period of time before proceeding to step 65. At step 65, the paging terminal controller 31 determines if the stored message has been read. If the message has been read, then at step 66 the system 30 posts a read flag in the subscriber data base to indicate that the message was delivered and read and at step 67 the process ends.
[0053] If, at step 65, the message had not been read, then at step 68 the system 30 determines the priority of the message and proceeds to step 69. If the priority is high, as determined at step 69, then at step 61 the page call is returned to the transmission stack at the designated priority level for re-transmission. If, on the other hand, the priority is not high as determined at step 69, then the message has a low priority and the process ends at step 67.
[0054] An alternate routine 80 for notifying a paging transceiver 100 that an unread message is waiting is shown in FIG. 6 . At step 81, the paging terminal controller 31 sorts through subscriber listings which have a corresponding unread and unnotified message in the storage and retrieval unit 32 and sends a page request to base station 34. At step 82, the switch 36 checks a home location registry (HLR) to determine the registered location and status of the remote paging transceiver 100. A page call is processed by transmitting selective call signals from transceiver base station 37 at step 82. If a page acknowledgment is desired for verification that the paging transceiver 100 recipient received the selective call signals, an Ack signal is manually or automatically transmitted from the paging transceiver 100 to base station 34 for storage in the subscriber database of paging terminal controller 31 at step 82.
[0055] At step 83, if an acknowledgement signal was received, a notified flag is set in the subscriber data base corresponding to the unread message stored in the storage and retrieval unit 32 and the paging process for the current unread message ends at step 84. If at step 83 an acknowledgment signal was not received, the message is assigned a new priority and the process is subsequently repeated. Optionally, a plurality of priorities may be assigned to acknowledged and not acknowledged unread messages so that the paging transceiver 100 is sent a number of calls until the message is read by the subscriber.
[0056] In the preferred embodiment, the base station 34 is part of a mobile radiotelephone network and the paging transceiver 100 is paged over the designated paging channel or the control channels of the network. In addition to paging the paging transceiver 100, the short messages or other data transmitted to the paging transceiver 100 are also preferably transmitted over the paging channel or control channels. Although the paging is preferably performed through a mobile radiotelephone network, the selective call signals may alternatively be routed to a paging system for transmitting an address code and CI data over an independent paging transmitter. In such a configuration, the paging transceiver 100 may be configured to have a separate paging receiver or transceiver compatible with the paging transmitter or paging transceiver. Since radio pager devices require much less energy than portable cellular telephones, a paging transceiver 100 configured with a low energy paging receiver would reduce energy required for receiving selective call signals and allow high energy circuitry of the paging transceiver 100 to be turned off until the user needs to retrieve or transmit messages. Other variations and modifications will be apparent to those skilled in the art.
[0057] A process 90 for receiving messages at a paging transceiver 100 is shown in FIG. 7 . A selective call signal including an address is received by receive section 21 of the transceiver 100 at step 91. At step 92, the demodulated signal is processed by the CPU 27 to compare the received address with an address code stored in the CPU 27 memory. If the received address code does not match the stored address, flow returns to step 91 and the transceiver 100 continues to monitor transmissions for its address. When the address corresponds to the pre-stored address code, as determined at step 92, the CPU 27 stores and processes any corresponding received CI data at step 93.
[0058] Next, at step 94, the CPU 27 determines if an acknowledgment transmission is required by the paging transceiver 100. The CPU 27 may always enable an acknowledgment in order to confirm at the system 30 or base station 34 that the selective call signals were received by the targeted paging transceiver 100. Alternatively, the CPU 27 may never enable an acknowledgment from the transceiver 100, which is useful in explosive environments where transmissions are dangerous and in environments where a reply from the paging transceiver 100 may cause harmful interference to other electronic equipment. The CPU 27 may, as another option, enable an acknowledgment only when acknowledgment data is contained within the received CI data, such as with a remote request. Finally, the CPU 27 may enable an acknowledgment in response to a user-enabled command.
[0059] Returning to step 94, if the paging transceiver 100 allows for an acknowledgment then at step 95 the CPU 27 determines whether the acknowledgment is required or if the acknowledgment is a user option. If the acknowledgment is required to be automatic, then an acknowledgment flag is set at step 97. If, on the other hand, the acknowledgment is not automatic but rather optional, then at step 96 the CPU 27 determines whether an acknowledgment has been enabled. If the acknowledgment has been enabled, then the acknowledgment flag is set in step 97.
[0060] At step 98, the CPU 27 determines whether short messages may be transmitted. Short messages may include CI data or any type of short coded message which was pre-stored by the user in the paging transceiver 100. If short messages are enabled, at step 99 the CPU 27 sets the short message flag. At step 100, the paging transceiver 100 transmits all flagged data, including CI data, to the base station 34 for processing by the system 30. The CPU 27 generates status information corresponding to received Cl data and passes any necessary user status information to the user interface 3 for visual and/or audible reception by the user. For example the user may hear an alert beep, feel an alert vibration, view an LCD indicating the number of unread messages, view an animated graphic display, hear a synthesized voice indicating that an urgent message is waiting, or receive other types of indications. At step 101, the CPU 27 performs house keeping functions and the routine ends.
[0061] FIG. 8 depicts a user function flow diagram 110 for user selectable function requests at the paging transceiver 100. At step 111, the user selects a function to be performed from available functions 112 to 117. These functions are exemplary functions that may be available and additional functions may exist. One or more of these functions are preferably selected through the user interface 3. One or more messages may be selected by the user to be forwarded to one or a plurality of addresses or recipients at step 112. Items such as messages and send message lists may be selected by scrolling through the message number or name. The selected messages for forwarding may reside at the paging transceiver 100 or at the system 30. The user may also select the function of saving a selected message at step 113. At step 114, selected messages are retrieved for reproduction and/or storage. At step 115, messages may be sent to one or a plurality of recipients, such as to another paging transceiver 100. At step 116, the selected message may be erased and at step 117, a reply may be sent to the originator of a selected message. With any of the functions selected at steps 112 to 117, the system 30 may act upon the entire information or, alternatively, may instead operate on only the message identifier. For instance, if the user selected the desired action of forwarding a message, the system 30 may send the entire message to a designated recipient or may instead send just the message identifier.
[0062] FIG. 9 depicts processing performed by the paging transceiver 100 in response to the selection of any one of the functions 112 to 117 shown in FIG. 8 . At step 131, the function is identified by the CPU 27 and other processing occurs prior to step 132 where the CPU 27 determines whether a call is required. If a call is not required to perform the function, then at step 133 the CPU 27 performs the requested function and the process ends at step 140.
[0063] If, on the other hand, a call is required, then at step 134 the CPU 27 next determines whether a call is already in progress. If a call is in progress, the CPU 27 exchanges data with the system 30 and base station 34 at step 135 and the function is performed or executed at step 136. The data that is exchanged at step 135 includes a request signal that is sent from the paging transceiver 100 to the system 30 specifying the desired action and the particular information or message. If a call is not in progress, then at step 137 the CPU 27 preferably asks the user if a call should be made and receives the user's feedback at step 138. If the user elects not to call, then a delay occurs at step 141 with delay circuit 28.
[0064] As discussed above, the delay circuit 28 may be a timer which expires at a set time, such as at 1:00 a.m., when traffic and costs are low or may expire after a period of time, such as 1 hour. The set time or the period of time may be programmed by the user or may be determined by default values. Additionally, the delay circuit 28 may operate to delay operation until the signal strength is above a certain threshold. The delay circuit 28, in this example, may therefore comprise a level detector and a comparator circuit for comparing the signal strength to the threshold level. The delay circuit 28 would therefore advantageously delay the paging transceiver 100 from initiating communication until signal strength is sufficiently high. Moreover, the delay circuit 28 may alternatively comprise a communication monitor circuit for determining when the paging transceiver 100 is communicating before performing a function. Also, the delay circuit 28 may detect transmissions and trigger a certain event in response to a received communication. As an example, if the paging transceiver 100 receives a certain type of message or a message from a particular source or individual, the paging transceiver 100 may automatically perform a programmed action. The paging transceiver 100 would therefore be able, for instance, to automatically forward all messages received from one recipient to a designated person.
[0065] After the timer 28 is triggered or if the user decides to call now, then at step 139 the CPU 27 sets up a call to the base station 34. Once a call is established, then processing proceeds to step 135 for the exchange of data and then to step 136 for the performance or execution of the function. At step 140, the process ends. The process shown in FIG. 9 is not limited to the performance of a single function but also represents the processing if the user selects a number of functions. For example, the user may select the functions of retrieving a message at step 114 and forwarding a message at step 112 and these functions may be performed in unison with each other or sequentially one after the other.
[0066] The paging transceiver 100 and system 30 may exchange status information during messaging calls initiated by the paging transceiver 100 or by selective call, such as page calls, initiated by the system 30. The status information may contain information corresponding to messages stored within the paging transceiver 100 or within the system 30. For example, if the system 30 erases a message that has resided in its memory for too long a period of time, such as an unsaved, read message, the system 30 may inform the paging transceiver 100 that the message no longer exists. If the message identifier stored in the paging transceiver 100 no longer corresponds to a message stored in the system 30 or in the paging transceiver 100, the CPU 27 removes the identifier for the no-longer existing message.
[0067] When the forward message function 112 is selected, flow proceeds to step 131 where the CPU 27 reads information pertaining to the message or plurality of messages selected by the user to be forwarded. The information may include a message identifier, location data, message length, message type, destination addresses, or other CI type data as previously described. At step 132, the CPU 27 determines whether the message cannot be forwarded without communicating with the system 30. At step 134, the CPU 27 determines if a call is in progress. If a call is in progress, CI data is exchanged at step 135 with the system 30 for forwarding messages. If the messages to be forwarded are located at the system 30, the messages are simply flagged for forwarding to the appropriate addresses. At step 136, the messages are forwarded and confirmation is communicated to the paging transceiver 100. If the message is not located at system 30, the message is transmitted from the paging transceiver 100 to system 30 at step 136 and the process ends at step 140. If at step 134, it is determined that a call is not in progress, the user is asked if the message should be forwarded now at step 137. If at step 138 the user selects yes, a call is established with system 30 at step 139 and flow continues as previously described. If at step 138 the user responds that a call should not be made, the CPU 27 keeps the forwarding information in memory for forwarding the message during a subsequent call with system 30 and a delay occurs at step 141 with delay circuit 28, as described above. After the delay, a call is established with system 30 at step 139 and flow continues as previously described. The process ends at step 140.
[0068] In operation, the user selects a message or messages to be forwarded and also selects a recipient for receiving the message. If the message resides at the system 30, the message is simply forwarded to the addressed recipient. If the message is located in the paging transceiver 100, the message is first transmitted to the system 30 at step 135 before it can be forwarded to the intended recipient. In order to conserve time, the system 30 will not accept receipt of a message from the paging transceiver 100 if the same message already exists at the system 30. The system 30 will simply perform the required function with the already present duplicate message.
[0069] If the function selected is the save message function 113, then at step 131 the message identifier to be saved is read by CPU 27. At step 132, the CPU 27 determines if the message identifier selected corresponds to a message already stored in message memory 5 and if the selected function can be processed off-line. If yes, at step 133 the CPU 27 sets a save message flag in order to protect the message stored in message memory 5 from being over-written and the process ends at step 140.
[0070] If at step 132 the CPU 27 determines that the message is not stored at the paging transceiver 100, then at step 134 the CPU 27 determines whether a call is in progress. If a messaging call is in progress, CI data instructing the system 30 to save the message is sent. The system 30 flags the stored message and sends a message saved acknowledgment to the paging transceiver 100 at step 136. The CPU 27 converts the acknowledgment to status information and informs the user that the message is saved at the system 30 and the process ends at step 140. If at step 134, it is determined that the paging transceiver 100 is not currently in communication with the system 30, the CPU 27 flags the message identifier for saving and the user is asked if the call should be made now at step 137. If no, at step 138 the flag is kept for transmission to system 30 at a later time. A delay occurs at step 141 with delay circuit 28 as described above. After the delay, a call is established with system 30 at step 139 and flow continues as previously described. Transmission to system 30 may also take place at a later time, such as during a selective call to the paging transceiver 100 or during a messaging call to system 30. If yes, then the CPU 27 sets up a call at step 139 for transmitting the save flag and CI data as previously described.
[0071] When the retrieve message function is selected at 114, then at step 131 the message identifiers corresponding to messages to be returned are read from the CPU 27 memory for retrieving the message. Additionally, the CPU 27 may read message location information, system ID information, address information, message length information, and/or message type information as previously described. At step 132, the CPU 27 determines the location of the message and determines if a call to system 30 is required. If the message is stored in message memory 5, then at step 133 the CPU 27 retrieves the message. The message, for instance, may be an audio message, visual message, text message, or electronic signal intended to be transferred to another device.
[0072] At step 132, if the message does not reside in message memory 5, the CPU 27 determines that a call is required to retrieve the message and, at step 134, determines if a call is in progress. If a call is in progress, CI data, such as which messages to retrieve, message length, message type, and message identifier, is exchanged at step 135. At step 136, the message is retrieved and simultaneously stored in message memory 5 by the DSP 4. The appropriate status information corresponding to the message is stored by the CPU 27 in its memory and the process ends at step 140. If at step 134 a call is not in progress, the user is asked if the call should be made now or if during another call at step 137. At step 138, if the user chooses to place the call, the call is set up at 139. If the user chooses to delay the call at step 141 until another session or some later time, the message is left flagged for retrieval at the next session or some later time and the process ends at step 140. With the timer 28, the message may be retrieved at a chosen time or a retrieval instruction may be sent from system 30 to paging transceiver 100 for causing the paging transceiver 100 to automatically retrieve a message or plurality of messages at a time designated by system 30. For example it may be desirable to have emergency weather information automatically retrieved during night-time hours when telephone line charges and air time charges are less expensive. The above described options may also be utilized for forwarding messages, erasing messages, saving messages, sending messages, and replying to messages as will be shown in more detail hereinafter.
[0073] With the send message function 115, in order to send a message, the message must first be stored at the paging transceiver 100 or at the system 30. The process of storing or recording messages is well know to those of ordinary skill in the art and accordingly will not be described in further detail. Examples of these devices are described in U.S. Pat. No. 4,602,129 to Matthew, et al., titled “Electronic Audio Communications System With Versatile Message Delivery,” and in U.S. Reissued Pat. No. Re. 34,976 to Helferich et al, titled “Analog/Digital Voice Storage Cellular Telephone,” both of which are incorporated herein by reference. The system 30 and paging transceiver 100 can record, store and retrieve a plurality of different types of messages as previously described depending on the application required.
[0074] If the send message function 115 is selected, the CPU 27 identifies the message to be sent and cross references it to the selected recipient address information. At step 132, the CPU 27 determines whether a call is required. The subsequent processing of sending a message should be apparent from the description above for forwarding a message and accordingly will not be duplicated in order to simplify description of the invention. The message to be sent may reside in the paging transceiver 100 or in the system 30. If the message resides in the system 30 and in the paging transceiver 100, the message in the system 30 corresponding to the CPU 27 message identifier will be sent in order to conserve air time. If the message does not reside in system 30, the message will be sent from the paging transceiver 100 to the system 30. If the message is to be sent from the paging transceiver 100, the message may be a pre-stored message or alternatively, the message may be transmitted to system 30 by paging transceiver 100 in real time during a call session between system 30 and paging transceiver 100.
[0075] If the erase message function is selected at step 116, the erase message function allows a user to erase messages stored at the system 30 or at the paging transceiver 100 depending on the mode of operation. A message may be erased at a paging transceiver 100 without erasing the message identifier. If a message is erased at the paging transceiver 100 and the identifier still exists in message memory 5, the message can be retrieved from the system 30. In order to remove a message identifier at the paging transceiver 100, the message must be erased at the system 30. This feature causes the user to manage the messages at the platform, thereby conserving memory space at the storage and retrieval unit 32. At step 131, the selected message to be erased is identified and the user is asked if the selected message in the paging transceiver is to be erased or if both copies of the message are to be erased. If the local message only is selected to be erased, the message identification information is kept and at step 133 the CPU 27 flags the message stored in memory 5 for erasure or overwriting. In other words, the message still exists but may be over-written by another message when memory space is required and, until then, may be retrieved from message memory 5. If at step 132 a decision was made to erase both copies of the message, then at step 134 the CPU 27 determines if a call is in progress. If yes, at step 135 the CI data is exchanged instructing system 30 to erase the message. At step 131, the system 30 transmits an acknowledgment that the message was erased, the CPU 27 flags the local message for erasure, the identifier is removed and both copies of the message and the identifiers are erased.
[0076] If at step 134 the CPU 27 determines that a call is not in progress, the CPU 27 at step 137 erases the local message and the user is asked if the system 30 copy of the message needs to be erased now. If the user responds yes, the call is established at step 139 and the process continues as previously described. If the user responds, the necessary flags are set for erasing the remote message during the next communication with system 30 after the delay of step 141 and the timer 28 is activated. The timer 28 may be utilized for a timed erase of the message stored at system 30.
[0077] The message reply function 117 is for sending a reply to an already received message. A reply message utilizes the same process as the send message function except that a return address is already correlated to the message targeted for a reply. During the send message function 115, the user is required to select an address or destination for the message to be sent In other words, the user must know the destination or address in advance. The message reply function 117 does not require that the user know the address of the recipient because the message being replied to has a corresponding return address. As with the send message function 115, a reply message may be sent in real time or it may be pre-recorded and stored in the paging transceiver 100 for transmission to system 30. Additionally, the reply transmission may be delayed for a set period of time as previously described with timer 28.
[0078] In summary, as discussed above with reference to FIGS. 5 and 6 , the system 30 does not transmit the entire message to the paging transceiver 100 but rather notifies the user that a message is waiting. The paging transceiver 100, as discussed above with reference to FIG. 7 , stores data associated with the page and possibly a short message. The user can then select a desired one of plurality of available functions, such as those shown in FIG. 8 , and the paging transceiver 100 will process the request in accordance with FIG. 9 .
[0079] With the system 30 and paging transceiver 100, the paging transceiver 100 can notify a user of a message without receiving the entire message. The user can then decide to act upon the message at a time convenient to the user. Rather than receiving the message with the alert, as occurs with conventional paging receivers, the user can control the time when he or she wants to receive a message and may even decide not to retrieve the message. After the user has been notified, the user can then control the paging transceiver 100 to retrieve the message from the system 30, to save the message at either the system 30 or paging transceiver 100, to forward the message to an indicated recipient, to reply to the message, or to erase the message from the paging transceiver 100 or from the system 30.
[0080] With paging transceiver 100, the user can position the paging transceiver in a desired location before initiating communication with the system 30. Thus, if the user is paged by system 30 while the user is in a subway, basement, or on an airplane, the user can postpone the delivery of the message until the paging transceiver 100 is in a better location to receive and reply to the message. Similarly, the user may be in an explosive environment or near sensitive electronic equipment and may postpone delivery of the message and a reply from the paging transceiver 100 until the user is out of the explosive environment or far enough away from the sensitive electronic equipment. The paging transceiver 100 and system 30 therefore give the user control over the messages stored in the system 30.
[0081] The paging transceiver 100 and system 30 conserve both valuable air time and also paging transceiver message memory 5. The system 30 does not automatically deliver each message to the intended paging transceiver 100 but instead allows the user to exercise control over the message. Since a message may be many bytes in length, perhaps kilobytes, megabytes, or even greater, the benefit to the system 30 and to the base station 34 in not having to transmit each message can be quite substantial. Also, since each message is not automatically delivered to the paging transceiver 100, the paging transceiver 100 does not become overloaded with messages and instead the user can choose to act on selective messages, such as by retrieving only certain messages. The user, additionally, may decide not to act on any of the messages through base station 34 and may call the system 30 through the PSTN 35, thereby bypassing the base station 34 and its associated charges and expenses.
[0082] The paging transceiver 100 and system 30 are not limited to voice messages in a paging system. Rather, the paging transceiver 100 and system 30 may operate with any type of message or information, including, but not limited to numeric messages, alphanumeric messages, voice or other audio messages, video messages, graphics or even data. The paging transceiver 100 may be a separate paging transceiver, may be integral with a mobile radiotelephone, or may be incorporated into other devices.
[0083] For instance, the paging transceiver 100 may be integrated into a portable radio, CD, or tape player. The paging transceiver 100 could receive messages from system 30 which indicate portions of songs that may be sampled by the user. The user may browse through a listing of available music and select a desired song. The paging transceiver 100 then communicates with the system 30 to retrieve the selected song and the user can then play the song at the paging transceiver 100.
[0084] As another example, the messages may be video messages which the user can browse through and select only desired messages. The paging transceiver 100 may be integral with a television set and the video messages may be promotions for new movies or shows. Alternatively, the paging transceiver 100 may be integral with a game console and the video messages may be clips of new games that are available with that game console. Other applications for the paging transceiver 100 and system 30 will be apparent to those skilled in the art.
[0085] The information or message available to a paging transceiver 100 need not be static but instead may be dynamic. In other words, when a paging transceiver 100 is alerted that information is available, the information may be updated or otherwise change from the time that the user was alerted. As an example, the user may receive a weather alert and by the time the user decides to receive the information the information would be updated to reflect current weather conditions. The identifier for the information therefore does not limit the content that may be stored as the information available to the user.
[0086] The system 30 is not limited to transmitting only one alert at a time to one paging transceiver 100. Instead, the system 30 may send a plurality of alerts to a single paging transceiver 100 and each of those alerts may be broadcast to a plurality of paging transceivers 100. For instance, the system 30 may broadcast information to a plurality of transceivers 100 that share a common set of numbers within their mobile identification numbers. If the system 30 sends a plurality of alerts to a paging transceiver 100, these alerts may be displayed by the user interface 3 and the user can scroll through and act upon the messages as desired.
[0087] As discussed above, the system 30 and paging transceiver 100 allows information to be remotely acted upon by the paging transceiver 100. The system 30, however, also allows users access to their information via conventional ways, such as the PSTN 35. Therefore, a user may receive the alert with a paging transceiver 100 and decide to call in through the PSTN 35 to listen or otherwise act upon the message. The system 30 preferably is connected to the Internet whereby users can also gain access and act upon their information via the Internet.
[0088] The paging transceiver 100 preferably alerts the user both when a message identifier signal has been received and when complete messages have been received. The alerts may comprise any suitable indication to inform the user that the paging transceiver 100 has received a communication, such as a tone, vibration, or visual display. The alerts for a received identifier and for a received message are preferably different so as to allow a user to easily differentiate between the two communications.
[0089] The example provided in FIG. 3 was a single system 30 for storing messages on behalf of a plurality of paging transceivers 100. The invention, however, may include any number of systems 30 for storing messages with each system 30 storing information for a transceiver 100 being considered a content provider. For instance, as shown in FIG. 10 , a messaging system 200 may comprise a plurality of systems 30 connected to the PSTN 35 with system 30A being associated with base station 34A and transceiver antenna 37A and system 30B being associated with base station 34B and transceiver antenna 37B. Although three systems 30 are shown, the system 200 may include any number of systems 30 and, although two base stations 34 are shown, each system 30 may be associated with a base station 34 and transceiver antenna 37 or only one of the systems 30 may be associated with a base station 34 and transceiver antenna 37. Furthermore, each system 30 need not include a paging terminal controller 31 or a storage unit 32. System 30C, for instance, may include a storage and retrieval unit 32 and input/output controller 33 but not a paging terminal controller 31 and may page the paging transceiver 100 through the paging terminal controller 31 in system 30A. Conversely, a system 30, such as system 30A, may include a paging terminal controller 31 and an input/output controller 33 but not a storage and retrieval unit 32. Further, the input/output controller 33 need not be a separate unit but may be incorporated into the paging terminal controller 31 if the system 30 does not include a storage and retrieval unit 32, or into the storage and retrieval unit 32, if the system 30 does not include a paging terminal controller 31. The systems 30 and base stations 34 may communicate with each other through the PSTN 35 or through links or lines other than or in addition to the PSTN 35, such as through an SS7 backbone of a wireless network or through the Internet.
[0090] Additionally, each of the base stations 34A and 34B may be part of a paging network but are preferably part of a cellular network. Either one or both of base stations 34A or 34B may page the paging transceiver and either one or both of the base stations 34A or 34B may deliver the contents of messages to the paging transceiver. Each of the systems 30A, 30B, and 30C may store messages on behalf of a user with the messages being of the same or different types. Furthermore, the messages stored within a single system 30 may be all the same type or may differ from each other.
[0091] As an example, system 30A may store voice mail messages and email messages directed to the user's office, system 30B may store voice mail messages directed to the user's home, and system 30C may store audio messages. The base station 34A acts as a clearinghouse for all messages delivered to the user to any of the systems 30 and pages the paging transceiver 100 whenever a message is received. Thus, when a voice mail message or email message is received at system 30A, the system 30A delivers a page to base station 34A which is then delivered to paging transceiver 100. When a voice message is received at system 30B, the system 30B sends information about the message to system 30A and system 30A then delivers a page to base station 34A for delivering the page to the paging transceiver 100. Similarly, when system 30C has an audio message it notifies system 30A and system 30A acts to have the page delivered to the paging transceiver 100.
[0092] An example of the data transmission 201 sent from system 30B or 30C to system 30A is shown in FIG. 11. The data transmission 201 includes system ID information for identifying the system 30 from a potential plurality of systems 30. The system ID information may be an address code or may comprise the telephone number of the system 30 and may be automatically captured by system 30A, such as from Caller ID or from DNIS information. The data message 201 also identifies the paging transceiver(s) 100, such as with an address code or MIN. For many systems 30, the message or information stored will often be for a single user whereby the transceiver ID would be the address code or MIN for that single paging transceiver 100. For other systems 30, however, the system 30 may want to broadcast a single message to a plurality of paging transceivers 100 whereby the transceiver ID may be a code that identifies a predefined group of paging transceivers 100.
[0093] The data transmission 201 also includes message information. The message information includes information identifying the message and preferably also includes information specifying the type of the message, the length of the message, and the message priority. The message identification may identify the message with a unique code, such as a number, or may specify the address in system 30 for the message. The message type advantageously indicates whether the message is a voice message, email message, audio message, video message, or text message. The message length indicates the size of the message and the message priority indicates the priority level of the message. For instance, the user can designate priorities based upon the telephone number of the caller leaving the message or the priority may be set by the caller. Although the data transmission 201 preferably includes this information, the data transmission 201 may include additional or fewer fields than the example provided in FIG. 11 .
[0094] The data transmission 201 also includes additional information that may be relayed and presented to the user. For instance, for many systems 30 that receive and store messages on behalf of the user, the additional descriptive information preferably comprises a return address for identifying the caller's telephone number to inform the user as to who left the message. For other systems 30 which may generate their own information, the additional information preferably describes the information available to the user. For instance, for a system 30 that allows users to sample songs, the additional information would indicate the title and the artist of the song and may also specify the cost to retrieve and play the song. Other uses of the additional information will be apparent to those skilled in the art.
[0095] The page sent to the paging transceiver 100 includes most, if not all, of the data transmission 201. The information transmitted to the paging transceiver 100, with reference to FIG. 7 , may be inserted into a short message transmitted to the user at step 98. From the system ID information, the paging transceiver 100 can determine which system 30 it needs to respond to in order to act upon a message. For instance, system 30A may page the paging transceiver 100 and indicate that system 30B has a stored message. If the user selects the retrieve message function, then the paging transceiver 100 can contact system 30B through base station 34B to retrieve the desired message. The paging transceiver 100 as discussed above may instead respond to base station 34A to retrieve the message and base station 34A would communicate with system 30B to retrieve or otherwise act upon the message.
[0096] The message information is used by the paging transceiver 100 to inform the user of the message or information stored at the system 30. The message type, length, priority, and additional descriptive material may be displayed or otherwise indicated to the user at the paging transceiver 100. From this information, the user can decide what type of action to take upon the message or information at the system 30.
[0097] As described with reference to FIG. 9 , a call to the system 30 may be required in order for the paging transceiver 100 to perform a desired function. If a call is required, the paging transceiver 100 relays information in the data transmission 201 to the system 30. If the paging transceiver 100 responds to a system 30 other than the one storing the message or information, the paging transceiver 100 identifies the system 30 storing the message or information and also identifies the message. As discussed above, the message may be identified in a number of ways, such as with a message code or by specifying the location in memory where the message is stored. The call to the system 30 would automatically provide the transceiver identification information to the system 30, although the paging transceiver 100 could provide this information with the other information provided to the system 30.
[0098] Upon receiving a call from the paging transceiver 100, the system 30 reads the transceiver identification and message information to find the information requested by the paging transceiver 100. The information obtained from the paging transceiver 100 at the system 30 and the transfer of the requested information to the paging transceiver occurs at step 135 in FIG. 9 .
[0099] The system 200 can present substantial cost savings to conventional paging systems. With a conventional paging system, the entire message is transmitted to the location of the paging transceiver 100. For instance, if the user's home base is in Chapel Hill, N.C., and the message originates in Chicago, Ill., then the message is typically sent over the PSTN 35 to the home base. With nationwide paging, the user may have traveled to San Diego, Calif. whereby the home base would then send the entire message from Chapel Hill to San Diego. With system 200, on the other hand, only the data transmission 201 is transmitted from Chicago to Chapel Hill and from Chapel Hill to San Diego. The actual message, in contrast, is sent directly from the storage facility in Chicago to San Diego, thereby reducing charges associated with the transfer between Chicago and Chapel Hill. Moreover, the data transmissions 201 between systems 30 may occur over the Internet. These transmissions, for instance, may be formatted according to the Voice Profile for Internet Mail (VPIM) and the addresses of the transceivers 100 may be determined from an open directory service, such as the Lightweight Directory Access Protocol (LDAP) or X.500.
[0100] The systems 30 and 200 allow a user to easily manage the multitude of messages that are commonly received every day. Conventionally, a user would have to call in to the office voice mail to retrieve voice messages, call home to retrieve voice messages sent to the house, and connect with the computer network at the office to retrieve email messages. Although paging systems have been used to notify a user that a voice mail message or other message has been received, the user would still have to call in to a separate system to actually retrieve the message. The system 200, on the other hand, enables a user to be notified of all messages, regardless of their type and regardless of their location and furthermore allows the user to selectively retrieve, save, erase or perform other functions on the messages. The systems 30 and 200 and paging transceiver 100, moreover, allow the user to exercise control over the remotely stored messages; the user can selectively store, save, retrieve, erase, forward, send or otherwise perform operations on messages stored at a remote location.
[0101] The forgoing description of the preferred embodiments of the invention has been presented only for the purpose of illustration and description and is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in light of the above teaching.
[0102] The embodiments were chosen and described in order to explain the principles of the invention and their practical application so as to enable others skilled in the art to utilize the invention and various embodiments and with various modifications as are suited to the particular use contemplated.
Claims
Post-issuance certificates present
The text shown below may not reflect later post-issuance changes.
What is claimed is:
1. A method of content communication, comprising:
receiving a notification at a cell phone, the notification at least identifying content intended for the cell phone and identifying the content's location, and identifying the type of content from among at least text, image, audio, and video content;
alerting a user of the cell phone that the notification has been received;
receiving input from the user indicating that the content should be downloaded to the cell phone;
generating a request signal including a request to download the content;
sending the request signal from the cell phone so that the desired content may be downloaded to the phone; and
receiving the desired content to the cell phone only in response to sending the request signal.
2. The method of claim 1, wherein identification of the content's location includes an address of a computer system.
3. The method of claim 1, further comprising the cell phone alerting the user to the receipt of the requested content.
4. The method of claim 1, wherein identification of the content's location includes a system identification.
5. The method of claim 1, wherein the request signal includes at least a portion of the notification.
6. The method of claim 5, wherein the request signal includes at least that portion of the notification that identifies the content's location.
7. The method of claim 1 further comprising receiving input from the user specifying a desired command to be performed on the content identified, wherein the desired command is chosen from a plurality of commands permanently stored in the cell phone.
8. The method of claim 7 wherein the plurality of commands permanently stored in the cell phone include at least one of the following: delete the content, forward the content to a specified recipient, save the content, or reply to the content.
9. The method of claim 7 further comprising generating and sending a request signal which includes the desired command from the cell phone so that the desired command may be performed on the content identified.
10. The method of claim 9 wherein the cell phone receives confirmation that the desired command was executed and alerts the user to receipt of the conformation, wherein the alert includes one or more of an audible sound, a vibration, or display of a image.
11. The method of claim 1 wherein the desired content received at the cell phone is deleted without deleting the notification.
12. The method of claim 1 wherein the content comprises a video message and wherein the cell phone is adapted to play the video message.
13. The method of claim 1 wherein the content comprises music and wherein the cell phone is adapted to play the music in response to a user input.
14. The method of claim 1 wherein the content comprises a game and wherein the cell phone is adapted to play the game in response to a user input.
15. A content communication system, comprising:
a memory configured to store content;
a memory controller including a processor coupled to the memory configured to cause a data signal to be directed to a cell phone, wherein the data signal includes an address identifier that identifies the cell phone, a content identifier that identifies the content and the content's location, and a type identifier that identifies the content's type;
wherein the memory controller is configured to direct the content corresponding to the content identifier from the memory to the cell phone only upon receiving a request from the cell phone to do so.
16. The system of claim 15, wherein the memory controller is configured to execute a command sent from the cell phone, the execution being performed on the content prior to the system directing the content to the cell phone and comprising at least one of the following: delete the content, forward the content to a specified recipient, save the content, or reply to the content.
17. The system of claim 15, wherein the content comprises at least one of the following: audio, voice, music, image, graphic, text, video, application or data.
18. The system of claim 15, wherein the cell phone communicates by at least one of the following: a global system for mobile communications network (GSM), a cellular packet data network, or a personal communications services network (PCS).
19. The system of claim 15, wherein the data signal comprises a plurality of address identifiers identifying a plurality of cell phones.
20. The system of claim 15, wherein the data signal comprises an address signal identifying a plurality of cell phones.
21. The system of claim 15, wherein the memory is coupled to the Internet.
22. The system of claim 15, wherein the content's location is identified based on an address of a computer system.
23. The system of claim 22, wherein the address of the computer system comprises an Internet address.
24. The system of claim 15, wherein the content's location is identified based on a system identification.
25. The system of claim 15 wherein the type of content identified by the type identifier is at least one of text, image, audio, or video.
26. The system of claim 15 wherein the content identifier and type identifier are separate identifiers.
27. The system of claim 15 wherein the memory controller is further configured to direct the content corresponding to the content identifier to the cell phone in a way that bypasses a notification system.
28. The system of claim 15 wherein the memory controller is configured to receive information from a home location registry.
29. The system of claim 28 wherein the memory controller is further configured to direct the content to the cell phone based at least in part on the information obtained from the home location registry.
30. A method that delivers content to an intended recipient, comprising:
storing in a memory available content for the intended recipient;
accessing a home location registry to obtain information about the intended recipient's cell phone;
causing a data signal to be directed to the cell phone, wherein the data signal includes an address identifier that identifies the cell phone, a content identifier that identifies the available content and the content's location, and a type identifier that identifies the content's type;
transmitting the available content corresponding to the content identifier to the cell phone upon receiving a request to do so.
31. The method of claim 30, further comprising performing an action requested by the cell phone on the available content prior to transmitting the available content to the cell phone comprising at least one of the following: delete the content, forward the content to a specified recipient, save the content, or reply to the content.
32. The method of claim 30, wherein the cell phone communicates by at least one of the following: a global system for mobile communications network (GSM), a cellular packet data network, or a personal communications services network (PCS).
33. The method of claim 30, wherein the available content comprises at least one of the following: audio, voice, music, image, graphical, text, video, application or data.
34. The system of claim 30, wherein the data signal comprises a plurality of address identifiers identifying a plurality of cell phones.
35. The method of claim 30, wherein the address identifier identifies a plurality of cell phones.
36. The method of claim 30, wherein at least part of the data signal is directed to the cell phone via the Internet.
37. The system of claim 30, wherein the content's location is identified based on an Internet location.
38. The system of claim 30, wherein the content's location is identified based on an address of a computer system.
39. The system of claim 38, wherein the address of the computer system comprises an Internet address.
40. The system of claim 30, wherein the content's location is identified based on a system identification.
41. The method of claim 30 wherein the type of content identified by the type identifier is at least one of text, image, audio, or video.
42. The method of claim 30 wherein the information obtained from the home location registry includes wireless network location of the cell phone.
43. The method of claim 30 further comprising receiving from the cell phone, prior to transmitting the available content to the cell phone, a command created at the cell phone including at least one of the following: delete the content, forward the content to a specified recipient, save the content, or reply to the content.
44. A wireless communication system, comprising:
a memory configured to store content;
a controller including a processor coupled to the memory configured to generate a notification that identifies the content, the content's location, and the content's type;
a radio transmitter coupled to an antenna and coupled to the memory and controller configured to send the notification to a cell phone;
a radio receiver coupled to the antenna and coupled to the memory and controller configured to receive a request to receive the content generated by the cell phone, wherein the request includes at least a portion of the notification;
wherein the radio transmitter is configured to send via the antenna the content corresponding to the notification to the cell phone only upon receiving a request from the cell phone to send it.
45. The system of claim 44, wherein the controller is configured to perform a command received from the cell phone on the content comprising at least one of the following: delete the content, forward the content to a specified recipient, save the content, or reply to the content.
46. The system of claim 44, wherein the cell phone communicates by at least one of the following: a global system for mobile communications network (GSM), a cellular packet data network, or a personal communications services network (PCS).
47. The system of claim 44, wherein the content comprises at least one of the following: audio, voice, music, image, graphical, text, video, application or data.
48. The system of claim 44, wherein the content's location is identified based on an address of a computer system.
49. The system of claim 48, wherein the address of the computer system comprises an Internet address.
50. The system of claim 44, wherein the content's location is identified based on a system ID.
51. A method of operating a cellular phone configured for media content retrieval and playback comprising:
(a) receiving a wireless notification of media content available for retrieval from a remote content storage system, the notification including information at least identifying the content and an address of the remote content storage system;
(b) sending a request to retrieve the content from the remote content storage system via a cellular network, the request including information at least identifying the content and the address of the remote content storage system;
(c) receiving the requested media content over the cellular network; and
(d) playing the media content.
52. The method of claim 51 wherein the media content is a song and the cellular phone is adapted to play the song.
53. The method of claim 51 wherein the media content is video and the cellular phone is adapted to play the video on a display of the cellular phone.
54. The method of claim 51 further comprising the cellular phone selecting a specific codec to enable decoding and playing of the media content.
55. The method of claim 51 further comprising cell phone receiving instructions via the cellular network regarding the media content and the cellular phone being configured to implement the received instructions.
56. The method of claim 51 wherein the notification further includes information identifying the type of media content.
57. The method of claim 51 further comprising alerting the user that a notification has been received and providing a second alert when the content associated with the notification is received by the cellular phone.
58. The method of claim 51 further comprising the cellular phone, prior to receiving the media content, instructing the remote content storage system, via the cellular network, to forward the media content to another.
59. The method of claim 51 further comprising:
(e) the notification identifying a plurality of available media content;
(f) requesting a select some of the plurality of available media content via the cellular network;
(g) receiving the select some of the available media content via the cellular network;
(h) accepting a user input selecting one of the select some of received media content.
60. The method of claim 59 further comprising receiving an indication of the cost to retrieve the media content and informing the user.
61. The method of claim 60 wherein the media content comprises songs.
62. The method of claim 51 further comprising receiving an indication of the cost to retrieve the media content and informing the user.
63. The method of claim 51 further comprising the notification informing of a plurality of samples of the media content.
64. The method of claim 63 wherein each one of the plurality of samples has an associated location identifier transmitted with the notification.
65. The method of claim 64 further comprising directing a request signal to a system corresponding to at least a selected one of the plurality of location identifiers received, the request signal including the at least one location identifier selected.
66. The method of claim 63 further comprising retrieving the samples of media content from the remote system via the cellular network.
67. The method of claim 66 further comprising retrieving the full media content from the remote content storage system via the cellular network, the full media content corresponding to at least a selected one of the samples of media content previously received.
68. The method of claim 51 further comprising:
(e) the notification informing of a list of available media content;
(f) retrieving the listing of available media content;
(g) allowing the user to browse through the listing of available media content and select at least a desired one of the listing;
(h) sending a request to retrieve the content associated with the at least selected one of the listing;
(i) receiving the media content corresponding to the at least selected one of the listing.
69. The method of claim 51 further comprising:
(e) storing at least some of the retrieved media content in the cellular phone;
(f) allowing the user to scroll through a listing of stored media content; and
(g) accepting a user selection of a select one from the list.
Patent Citations (648)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US2003576(A) | 1935-06-01 | Buhren | Applicant |
| US3118145(A) | 1964-01-01 | Nee | Applicant |
| US3794983(A) | 1974-02-01 | Sahin | Applicant |
| US4039761(A) | 1977-08-01 | Nicoud et al. | Applicant |
| US4042906(A) | 1977-08-01 | Ezell | Applicant |
| US4124773(A) | 1978-11-01 | Elkins | Applicant |
| US4371752(A) | 1983-02-01 | Matthews et al. | Applicant |
| US4412217(A) | 1983-10-01 | Willard et al. | Applicant |
| US4468813(A) | 1984-08-01 | Burke et al. | Applicant |
| US4480253(A) | 1984-10-01 | Anderson | Applicant |
| US4495647(A) | 1985-01-01 | Burke et al. | Applicant |
| US4549047(A) | 1985-10-01 | Brian et al. | Applicant |
| US4573140(A) | 1986-02-01 | Szeto | Applicant |
| US4602129(A) | 1986-07-01 | Matthews et al. | Applicant |
| US4640991(A) | 1987-02-01 | Matthews et al. | Applicant |
| US4644352(A) | 1987-02-01 | Fujii | Applicant |
| US4737979(A) | 1988-04-01 | Hashimoto | Applicant |
| US4769642(A) | 1988-09-01 | Davis et al. | Applicant |
| US4786902(A) | 1988-11-01 | Davis et al. | Applicant |
| US4807155(A) | 1989-02-01 | Cree et al. | Applicant |
| USH610(H) | 1989-03-01 | Focarile et al. | Applicant |
| US4811376(A) | 1989-03-01 | Davis et al. | Applicant |
| US4812843(A) | 1989-03-01 | Champion, III et al. | Applicant |
| US4821308(A) | 1989-04-01 | Hashimoto | Applicant |
| US4825456(A) | 1989-04-01 | Rosenberg | Applicant |
| US4837800(A) | 1989-06-01 | Freeburg et al. | Applicant |
| US4845491(A) | 1989-07-01 | Fascenda et al. | Applicant |
| US4853688(A) | 1989-08-01 | Andros et al. | Applicant |
| US4858232(A) | 1989-08-01 | Diaz et al. | Applicant |
| US4864301(A) | 1989-09-01 | Helferich | Applicant |
| US4868560(A) | 1989-09-01 | Oliwa et al. | Applicant |
| US4873520(A) | 1989-10-01 | Fisch et al. | Applicant |
| US4885577(A) | 1989-12-01 | Nelson | Applicant |
| US4897835(A) | 1990-01-01 | Gaskill et al. | Applicant |
| US4905003(A) | 1990-02-01 | Helferich | Applicant |
| US4942598(A) | 1990-07-01 | Davis | Applicant |
| US4961216(A) | 1990-10-01 | Baehr et al. | Applicant |
| US4965569(A) | 1990-10-01 | Bennett et al. | Applicant |
| US4975694(A) | 1990-12-01 | McLaughlin et al. | Applicant |
| US5003576(A) | 1991-03-01 | Helferich | Applicant |
| US5005013(A) | 1991-04-01 | Tsukamoto et al. | Applicant |
| US5007105(A) | 1991-04-01 | Kudoh et al. | Applicant |
| US5029199(A) | 1991-07-01 | Jones et al. | Applicant |
| US5040204(A) | 1991-08-01 | Sasaki et al. | Applicant |
| US5043721(A) | 1991-08-01 | May | Applicant |
| US5047763(A) | 1991-09-01 | Kuznicki et al. | Applicant |
| US5065423(A) | 1991-11-01 | Gaskill | Applicant |
| US5070536(A) | 1991-12-01 | Mahany et al. | Applicant |
| US5093659(A) | 1992-03-01 | Yamada | Applicant |
| US5093901(A) | 1992-03-01 | Cree et al. | Applicant |
| US5115233(A) | 1992-05-01 | Zdunek et al. | Applicant |
| US5117449(A) | 1992-05-01 | Metroka et al. | Applicant |
| US5128980(A) | 1992-07-01 | Choi | Applicant |
| US5128981(A) | 1992-07-01 | Tsukamoto et al. | Applicant |
| US5134724(A) | 1992-07-01 | Gehring et al. | Applicant |
| US5138311(A) | 1992-08-01 | Weinberg | Applicant |
| US5138312(A) | 1992-08-01 | Tsukamoto et al. | Applicant |
| US5140419(A) | 1992-08-01 | Galumbeck et al. | Applicant |
| US5146612(A) | 1992-09-01 | Grosjean et al. | Applicant |
| US5153903(A) | 1992-10-01 | Eastmond et al. | Applicant |
| US5159331(A) | 1992-10-01 | Park et al. | Applicant |
| US5159713(A) | 1992-10-01 | Gaskill et al. | Applicant |
| US5173688(A) | 1992-12-01 | DeLuca et al. | Applicant |
| US5175758(A) | 1992-12-01 | Levanto et al. | Applicant |
| US5177780(A) | 1993-01-01 | Kasper et al. | Applicant |
| US5182553(A) | 1993-01-01 | Kung | Applicant |
| US5185604(A) | 1993-02-01 | Nepple et al. | Applicant |
| US5192947(A) | 1993-03-01 | Neustein | Applicant |
| US5194857(A) | 1993-03-01 | Gomez | Applicant |
| US5212636(A) | 1993-05-01 | Nakazawa | Applicant |
| US5220366(A) | 1993-06-01 | King | Applicant |
| US5227774(A) | 1993-07-01 | Benoist | Applicant |
| US5239466(A) | 1993-08-01 | Morgan et al. | Applicant |
| US5239679(A) | 1993-08-01 | Murai | Applicant |
| US5241305(A) | 1993-08-01 | Fascenda et al. | Applicant |
| US5247700(A) | 1993-09-01 | Wohl et al. | Applicant |
| US5249230(A) | 1993-09-01 | Mihm, Jr. | Applicant |
| US5257307(A) | 1993-10-01 | Ise | Applicant |
| US5265033(A) | 1993-11-01 | Vajk et al. | Applicant |
| US5283818(A) | 1994-02-01 | Klausner et al. | Applicant |
| US5285426(A) | 1994-02-01 | Teodoridis | Applicant |
| US5285496(A) | 1994-02-01 | Frank et al. | Applicant |
| US5315635(A) | 1994-05-01 | Kane et al. | Applicant |
| US5329501(A) | 1994-07-01 | Meister et al. | Applicant |
| US5375161(A) | 1994-12-01 | Fuller et al. | Applicant |
| US5379031(A) | 1995-01-01 | Mondrosch et al. | Applicant |
| US5390362(A) | 1995-02-01 | Modjeska et al. | Applicant |
| US5396537(A) | 1995-03-01 | Schwendeman | Applicant |
| US5396547(A) | 1995-03-01 | Baals et al. | Applicant |
| US5398021(A) | 1995-03-01 | Moore | Applicant |
| US5402466(A) | 1995-03-01 | Delahanty | Applicant |
| US5406557(A) | 1995-04-01 | Baudoin | Applicant |
| US5410302(A) | 1995-04-01 | Dulaney, III et al. | Applicant |
| US5418835(A) | 1995-05-01 | Frohman et al. | Applicant |
| US5420922(A) | 1995-05-01 | Lundblad et al. | Applicant |
| USRE34976(E) | 1995-06-01 | Helferich et al. | Applicant |
| US5426422(A) | 1995-06-01 | Vanden Heuvel et al. | Applicant |
| US5426594(A) | 1995-06-01 | Wright et al. | Applicant |
| US5428663(A) | 1995-06-01 | Grimes et al. | Applicant |
| US5428784(A) | 1995-06-01 | Cahill, Jr. | Applicant |
| US5432839(A) | 1995-07-01 | DeLuca | Applicant |
| US5436960(A) | 1995-07-01 | Campana, Jr. et al. | Applicant |
| US5438611(A) | 1995-08-01 | Campana, Jr. et al. | Applicant |
| US5440559(A) | 1995-08-01 | Gaskill | Applicant |
| US5442706(A) | 1995-08-01 | Kung | Applicant |
| US5444671(A) | 1995-08-01 | Tschannen et al. | Applicant |
| US5448759(A) | 1995-09-01 | Krebs et al. | Applicant |
| US5452356(A) | 1995-09-01 | Albert | Applicant |
| US5455579(A) | 1995-10-01 | Bennett et al. | Applicant |
| US5455823(A) | 1995-10-01 | Noreen et al. | Applicant |
| US5457732(A) | 1995-10-01 | Goldberg | Applicant |
| US5463672(A) | 1995-10-01 | Kage | Applicant |
| US5473143(A) | 1995-12-01 | Vak et al. | Applicant |
| US5473667(A) | 1995-12-01 | Neustein | Applicant |
| US5475653(A) | 1995-12-01 | Yamada et al. | Applicant |
| US5475863(A) | 1995-12-01 | Simpson et al. | Applicant |
| US5475866(A) | 1995-12-01 | Ruthenburg | Applicant |
| US5479378(A) | 1995-12-01 | Yamada et al. | Applicant |
| US5479408(A) | 1995-12-01 | Will | Applicant |
| US5479472(A) | 1995-12-01 | Campana, Jr. et al. | Applicant |
| US5481255(A) | 1996-01-01 | Albert et al. | Applicant |
| US5483352(A) | 1996-01-01 | Fukuyama et al. | Applicant |
| US5483595(A) | 1996-01-01 | Owen | Applicant |
| US5485503(A) | 1996-01-01 | Diem | Applicant |
| US5487100(A) | 1996-01-01 | Kane | Applicant |
| US5487167(A) | 1996-01-01 | Dinallo et al. | Applicant |
| US5489894(A) | 1996-02-01 | Murray | Applicant |
| US5493692(A) | 1996-02-01 | Theimer et al. | Applicant |
| US5497373(A) | 1996-03-01 | Hulen et al. | Applicant |
| US5524009(A) | 1996-06-01 | Tuutijarvi et al. | Applicant |
| US5530438(A) | 1996-06-01 | Bickham et al. | Applicant |
| US5530930(A) | 1996-06-01 | Hahn | Applicant |
| US5544321(A) | 1996-08-01 | Theimer et al. | Applicant |
| US5550535(A) | 1996-08-01 | Park | Applicant |
| US5555376(A) | 1996-09-01 | Theimer et al. | Applicant |
| US5555446(A) | 1996-09-01 | Jasinski | Applicant |
| US5557659(A) | 1996-09-01 | Hyde-Thomson | Applicant |
| US5557749(A) | 1996-09-01 | Norris | Applicant |
| US5559862(A) | 1996-09-01 | Bhagat et al. | Applicant |
| US5561702(A) | 1996-10-01 | Lipp et al. | Applicant |
| US5564018(A) | 1996-10-01 | Flores et al. | Applicant |
| US5568540(A) | 1996-10-01 | Greco et al. | Applicant |
| US5572196(A) | 1996-11-01 | Sakumoto et al. | Applicant |
| US5572488(A) | 1996-11-01 | Yamada et al. | Applicant |
| US5579372(A) | 1996-11-01 | Astrom | Applicant |
| US5581366(A) | 1996-12-01 | Merchant et al. | Applicant |
| US5581593(A) | 1996-12-01 | Engelke et al. | Applicant |
| US5588009(A) | 1996-12-01 | Will | Applicant |
| US5590092(A) | 1996-12-01 | Fehnel | Applicant |
| US5592532(A) | 1997-01-01 | Koizumi et al. | Applicant |
| US5600703(A) | 1997-02-01 | Dang et al. | Applicant |
| US5603054(A) | 1997-02-01 | Theimer et al. | Applicant |
| US5604788(A) | 1997-02-01 | Tett | Applicant |
| US5608446(A) | 1997-03-01 | Carr et al. | Applicant |
| US5608786(A) | 1997-03-01 | Gordon | Applicant |
| US5611050(A) | 1997-03-01 | Theimer et al. | Applicant |
| US5623242(A) | 1997-04-01 | Dawson, Jr. et al. | Applicant |
| US5627525(A) | 1997-05-01 | Kudoh et al. | Applicant |
| US5630060(A) | 1997-05-01 | Tang et al. | Applicant |
| US5630207(A) | 1997-05-01 | Gitlin et al. | Applicant |
| US5631635(A) | 1997-05-01 | Robertson et al. | Examiner |
| US5631948(A) | 1997-05-01 | Bartholomew et al. | Applicant |
| US5633916(A) | 1997-05-01 | Goldhagen et al. | Applicant |
| US5635918(A) | 1997-06-01 | Tett | Applicant |
| US5636265(A) | 1997-06-01 | O'Connell et al. | Applicant |
| US5638369(A) | 1997-06-01 | Ayerst et al. | Applicant |
| US5644627(A) | 1997-07-01 | Segal et al. | Applicant |
| US5649305(A) | 1997-07-01 | Yoshida | Applicant |
| US5652789(A) | 1997-07-01 | Miner et al. | Applicant |
| US5654942(A) | 1997-08-01 | Akahane | Applicant |
| US5661782(A) | 1997-08-01 | Bartholomew et al. | Applicant |
| US5663703(A) | 1997-09-01 | Pearlman et al. | Applicant |
| US5668880(A) | 1997-09-01 | Alajajian | Applicant |
| US5675507(A) | 1997-10-01 | Bobo, II | Applicant |
| US5675627(A) | 1997-10-01 | Yaker | Applicant |
| US5678179(A) | 1997-10-01 | Turcotte et al. | Applicant |
| US5680442(A) | 1997-10-01 | Bartholomew et al. | Applicant |
| US5684859(A) | 1997-11-01 | Chanroo et al. | Applicant |
| US5694120(A) | 1997-12-01 | Indekeu et al. | Applicant |
| US5694454(A) | 1997-12-01 | Hill et al. | Applicant |
| US5696500(A) | 1997-12-01 | Diem | Applicant |
| US5699053(A) | 1997-12-01 | Jonsson | Applicant |
| US5703934(A) | 1997-12-01 | Zicker et al. | Applicant |
| US5706211(A) | 1998-01-01 | Beletic et al. | Applicant |
| US5710816(A) | 1998-01-01 | Stork et al. | Applicant |
| US5717742(A) | 1998-02-01 | Hyde-Thomson | Applicant |
| US5722071(A) | 1998-02-01 | Berg et al. | Applicant |
| US5724410(A) | 1998-03-01 | Parvulescu et al. | Applicant |
| US5726643(A) | 1998-03-01 | Tani | Applicant |
| US5737394(A) | 1998-04-01 | Anderson et al. | Applicant |
| US5737395(A) | 1998-04-01 | Irribarren | Applicant |
| US5742668(A) | 1998-04-01 | Pepe et al. | Applicant |
| US5745689(A) | 1998-04-01 | Yeager et al. | Applicant |
| US5751793(A) | 1998-05-01 | Davies et al. | Applicant |
| US5751814(A) | 1998-05-01 | Kafri | Applicant |
| US5752191(A) | 1998-05-01 | Fuller et al. | Applicant |
| US5761622(A) | 1998-06-01 | Priest | Applicant |
| US5768381(A) | 1998-06-01 | Hawthorne | Applicant |
| US5774803(A) | 1998-06-01 | Kariya | Applicant |
| US5778315(A) | 1998-07-01 | Proietti | Applicant |
| US5781857(A) | 1998-07-01 | Hwang et al. | Applicant |
| US5796394(A) | 1998-08-01 | Wicks et al. | Applicant |
| US5797091(A) | 1998-08-01 | Clise et al. | Applicant |
| US5802466(A) | 1998-09-01 | Gallant et al. | Applicant |
| US5805886(A) | 1998-09-01 | Skarbo et al. | Applicant |
| US5809130(A) | 1998-09-01 | Ayala | Applicant |
| US5809415(A) | 1998-09-01 | Rossman | Applicant |
| US5812639(A) | 1998-09-01 | Bartholomew et al. | Applicant |
| US5812671(A) | 1998-09-01 | Ross, Jr. | Applicant |
| US5812795(A) | 1998-09-01 | Horovitz et al. | Applicant |
| US5812865(A) | 1998-09-01 | Theimer et al. | Applicant |
| US5815800(A) | 1998-09-01 | Su et al. | Applicant |
| US5826191(A) | 1998-10-01 | Krishnan | Applicant |
| US5828882(A) | 1998-10-01 | Hinckley | Applicant |
| US5835089(A) | 1998-11-01 | Skarbo et al. | Applicant |
| US5838252(A) | 1998-11-01 | Kikinis | Applicant |
| US5841837(A) | 1998-11-01 | Fuller et al. | Applicant |
| US5845211(A) | 1998-12-01 | Roach, Jr. | Applicant |
| US5850594(A) | 1998-12-01 | Cannon et al. | Applicant |
| US5857020(A) | 1999-01-01 | Peterson, Jr. | Applicant |
| US5862325(A) | 1999-01-01 | Reed et al. | Applicant |
| US5864606(A) | 1999-01-01 | Hanson et al. | Applicant |
| US5870030(A) | 1999-02-01 | DeLuca et al. | Applicant |
| US5870454(A) | 1999-02-01 | Dahlen | Applicant |
| US5872847(A) | 1999-02-01 | Boyle et al. | Applicant |
| US5872926(A) | 1999-02-01 | Levac et al. | Applicant |
| US5875436(A) | 1999-02-01 | Kikinis | Applicant |
| US5878230(A) | 1999-03-01 | Weber et al. | Applicant |
| US5878351(A) | 1999-03-01 | Alanara et al. | Applicant |
| US5884159(A) | 1999-03-01 | Thro et al. | Applicant |
| US5884160(A) | 1999-03-01 | Kanazaki | Applicant |
| US5887249(A) | 1999-03-01 | Schmid | Applicant |
| US5889852(A) | 1999-03-01 | Rosecrans et al. | Applicant |
| US5892909(A) | 1999-04-01 | Grasso et al. | Applicant |
| US5893032(A) | 1999-04-01 | Maeda et al. | Applicant |
| US5895471(A) | 1999-04-01 | King et al. | Applicant |
| US5903723(A) | 1999-05-01 | Beck et al. | Applicant |
| US5905495(A) | 1999-05-01 | Tanaka et al. | Applicant |
| US5907805(A) | 1999-05-01 | Chotai | Applicant |
| US5909491(A) | 1999-06-01 | Luo | Applicant |
| US5913032(A) | 1999-06-01 | Schwartz et al. | Applicant |
| US5920826(A) | 1999-07-01 | Metso et al. | Applicant |
| US5924016(A) | 1999-07-01 | Fuller et al. | Applicant |
| US5928325(A) | 1999-07-01 | Shaughnessy et al. | Applicant |
| US5938725(A) | 1999-08-01 | Hara | Applicant |
| US5943397(A) | 1999-08-01 | Gabin et al. | Applicant |
| US5948059(A) | 1999-09-01 | Woo et al. | Applicant |
| US5951638(A) | 1999-09-01 | Hoss et al. | Applicant |
| US5961590(A) | 1999-10-01 | Mendez et al. | Applicant |
| US5961620(A) | 1999-10-01 | Trent et al. | Applicant |
| US5963618(A) | 1999-10-01 | Porter | Applicant |
| US5966652(A) | 1999-10-01 | Coad et al. | Applicant |
| US5974447(A) | 1999-10-01 | Cannon et al. | Applicant |
| US5974449(A) | 1999-10-01 | Chang et al. | Applicant |
| US5978837(A) | 1999-11-01 | Foladare et al. | Applicant |
| US5988857(A) | 1999-11-01 | Ozawa et al. | Applicant |
| US5991615(A) | 1999-11-01 | Coppinger et al. | Applicant |
| US5995597(A) | 1999-11-01 | Woltz et al. | Applicant |
| US6009173(A) | 1999-12-01 | Summer | Applicant |
| US6014559(A) | 2000-01-01 | Amin | Applicant |
| US6018654(A) | 2000-01-01 | Valentine et al. | Applicant |
| US6018657(A) | 2000-01-01 | Kennedy et al. | Applicant |
| US6021114(A) | 2000-02-01 | Shaffer et al. | Applicant |
| US6021190(A) | 2000-02-01 | Fuller et al. | Applicant |
| US6021433(A) | 2000-02-01 | Payne et al. | Applicant |
| US6026153(A) | 2000-02-01 | Fuller et al. | Applicant |
| US6026292(A) | 2000-02-01 | Coppinger et al. | Applicant |
| US6029065(A) | 2000-02-01 | Shah | Applicant |
| US6029171(A) | 2000-02-01 | Smiga et al. | Applicant |
| US6032039(A) | 2000-02-01 | Kaplan | Applicant |
| US6047053(A) | 2000-04-01 | Miner et al. | Applicant |
| US6052595(A) | 2000-04-01 | Schellinger et al. | Applicant |
| US6060997(A) | 2000-05-01 | Taubenheim et al. | Applicant |
| US6064879(A) | 2000-05-01 | Fujiwara et al. | Applicant |
| US6081703(A) | 2000-06-01 | Hallqvist | Applicant |
| US6087956(A) | 2000-07-01 | Helferich | Applicant |
| US6088127(A) | 2000-07-01 | Pieterse | Applicant |
| US6088717(A) | 2000-07-01 | Reed et al. | Applicant |
| US6091957(A) | 2000-07-01 | Larkins et al. | Applicant |
| US6097941(A) | 2000-08-01 | Helferich | Applicant |
| US6119167(A) | 2000-09-01 | Boyle et al. | Applicant |
| US6122484(A) | 2000-09-01 | Fuller et al. | Applicant |
| US6125281(A) | 2000-09-01 | Wells et al. | Applicant |
| US6128490(A) | 2000-10-01 | Shaheen et al. | Applicant |
| US6134325(A) | 2000-10-01 | Vanstone et al. | Applicant |
| US6134432(A) | 2000-10-01 | Holmes et al. | Applicant |
| US6138158(A) | 2000-10-01 | Boyle et al. | Applicant |
| US6144313(A) | 2000-11-01 | Nakano | Applicant |
| US6144671(A) | 2000-11-01 | Perinpanathan et al. | Applicant |
| US6145079(A) | 2000-11-01 | Mitty | Applicant |
| US6151443(A) | 2000-11-01 | Gable et al. | Applicant |
| US6151491(A) | 2000-11-01 | Farris et al. | Applicant |
| US6151507(A) | 2000-11-01 | Laiho et al. | Examiner |
| US6169883(B1) | 2001-01-01 | Vimpari et al. | Applicant |
| US6169911(B1) | 2001-01-01 | Wagner et al. | Applicant |
| US6175859(B1) | 2001-01-01 | Mohler | Applicant |
| US6178331(B1) | 2001-01-01 | Holmes et al. | Applicant |
| US6195564(B1) | 2001-02-01 | Rydbeck et al. | Applicant |
| US6205330(B1) | 2001-03-01 | Winbladh | Applicant |
| US6208839(B1) | 2001-03-01 | Davani | Applicant |
| US6212550(B1) | 2001-04-01 | Segur | Applicant |
| US6215858(B1) | 2001-04-01 | Bartholomew et al. | Applicant |
| US6216165(B1) | 2001-04-01 | Woltz et al. | Applicant |
| US6219694(B1) | 2001-04-01 | Lazaridis et al. | Applicant |
| US6230133(B1) | 2001-05-01 | Bennett, III et al. | Applicant |
| US6230188(B1) | 2001-05-01 | Marcus | Applicant |
| US6233318(B1) | 2001-05-01 | Picard et al. | Applicant |
| US6233430(B1) | 2001-05-01 | Helferich | Applicant |
| US6236804(B1) | 2001-05-01 | Tozaki et al. | Applicant |
| US6246871(B1) | 2001-06-01 | Ala-Laurila | Applicant |
| US6252588(B1) | 2001-06-01 | Dawson | Applicant |
| US6253061(B1) | 2001-06-01 | Helferich | Applicant |
| US6259892(B1) | 2001-07-01 | Helferich | Applicant |
| US6272532(B1) | 2001-08-01 | Feinleib | Applicant |
| US6278862(B1) | 2001-08-01 | Henderson | Applicant |
| US6282435(B1) | 2001-08-01 | Wagner et al. | Applicant |
| US6285745(B1) | 2001-09-01 | Bartholomew et al. | Applicant |
| US6285777(B2) | 2001-09-01 | Kanevsky et al. | Applicant |
| US6288715(B1) | 2001-09-01 | Bain et al. | Applicant |
| US6292668(B1) | 2001-09-01 | Alanara et al. | Applicant |
| US6298231(B1) | 2001-10-01 | Heinz | Applicant |
| US6301471(B1) | 2001-10-01 | Dahm et al. | Applicant |
| US6301513(B1) | 2001-10-01 | Divon et al. | Applicant |
| US6317594(B1) | 2001-11-01 | Gossman et al. | Applicant |
| US6321094(B1) | 2001-11-01 | Hayashi et al. | Applicant |
| US6321267(B1) | 2001-11-01 | Donaldson | Applicant |
| US6330244(B1) | 2001-12-01 | Swartz et al. | Applicant |
| US6333919(B2) | 2001-12-01 | Gaffney | Applicant |
| US6351523(B1) | 2002-02-01 | Detlef | Applicant |
| US6356939(B1) | 2002-03-01 | Dahl | Applicant |
| US6361523(B1) | 2002-03-01 | Bierman | Applicant |
| US6370389(B1) | 2002-04-01 | Isomursu et al. | Applicant |
| US6389457(B2) | 2002-05-01 | Lazaridis et al. | Applicant |
| US6401113(B2) | 2002-06-01 | Lazaridis et al. | Applicant |
| US6411827(B1) | 2002-06-01 | Minata | Applicant |
| US6418305(B1) | 2002-07-01 | Neustein | Examiner |
| US6421678(B2) | 2002-07-01 | Smiga et al. | Applicant |
| US6424841(B1) | 2002-07-01 | Gustafsson | Applicant |
| US6438585(B2) | 2002-08-01 | Mousseau et al. | Applicant |
| US6442243(B1) | 2002-08-01 | Valco et al. | Applicant |
| US6449344(B1) | 2002-09-01 | Goldfinger | Applicant |
| US6459360(B1) | 2002-10-01 | Helferich | Applicant |
| US6462646(B2) | 2002-10-01 | Helferich | Applicant |
| US6463463(B1) | 2002-10-01 | Godfrey et al. | Applicant |
| US6463464(B1) | 2002-10-01 | Lazaridis et al. | Applicant |
| US6501834(B1) | 2002-12-01 | Milewski et al. | Applicant |
| US6505237(B2) | 2003-01-01 | Beyda et al. | Applicant |
| US6510453(B1) | 2003-01-01 | Apfel et al. | Applicant |
| US6522879(B2) | 2003-02-01 | Myer et al. | Applicant |
| US6564249(B2) | 2003-05-01 | Shiigi | Applicant |
| US6567179(B1) | 2003-05-01 | Sato et al. | Applicant |
| US6580784(B2) | 2003-06-01 | Rodriquez et al. | Applicant |
| US6580787(B1) | 2003-06-01 | Akhteruzzaman et al. | Applicant |
| US6587681(B1) | 2003-07-01 | Sawai | Applicant |
| US6587693(B1) | 2003-07-01 | Lumme et al. | Applicant |
| US6597688(B2) | 2003-07-01 | Narasimhan et al. | Applicant |
| US6597903(B1) | 2003-07-01 | Dahm et al. | Applicant |
| US6611254(B1) | 2003-08-01 | Griffin et al. | Applicant |
| US6622147(B1) | 2003-09-01 | Smiga et al. | Applicant |
| US6625142(B1) | 2003-09-01 | Joffe et al. | Applicant |
| US6625642(B1) | 2003-09-01 | Naylor et al. | Applicant |
| US6636522(B1) | 2003-10-01 | Perinpanathan et al. | Applicant |
| US6636733(B1) | 2003-10-01 | Helferich | Applicant |
| US6662195(B1) | 2003-12-01 | Langseth et al. | Applicant |
| US6671715(B1) | 2003-12-01 | Langseth et al. | Applicant |
| US6694316(B1) | 2004-02-01 | Langseth et al. | Applicant |
| US6701378(B1) | 2004-03-01 | Gilhuly et al. | Applicant |
| US6728530(B1) | 2004-04-01 | Heinonen et al. | Applicant |
| US6741980(B1) | 2004-05-01 | Langseth et al. | Applicant |
| US6744528(B2) | 2004-06-01 | Picoult et al. | Applicant |
| US6744874(B2) | 2004-06-01 | Wu | Applicant |
| US6751453(B2) | 2004-06-01 | Schemers et al. | Applicant |
| US6760423(B1) | 2004-07-01 | Todd | Applicant |
| US6771949(B1) | 2004-08-01 | Corliss | Applicant |
| US6775264(B1) | 2004-08-01 | Kurganov | Applicant |
| US6775689(B1) | 2004-08-01 | Raghunandan | Applicant |
| US6779019(B1) | 2004-08-01 | Mousseau et al. | Applicant |
| US6779022(B1) | 2004-08-01 | Horstmann et al. | Applicant |
| US6792112(B1) | 2004-09-01 | Campbell et al. | Applicant |
| US6792544(B2) | 2004-09-01 | Hashem et al. | Applicant |
| US6807277(B1) | 2004-10-01 | Doonan et al. | Applicant |
| US6813489(B1) | 2004-11-01 | Wu et al. | Applicant |
| US6823225(B1) | 2004-11-01 | Sass | Applicant |
| US6826407(B1) | 2004-11-01 | Helferich | Applicant |
| US6832130(B2) | 2004-12-01 | Pintsov et al. | Applicant |
| US6868498(B1) | 2005-03-01 | Katsikas | Applicant |
| US6869016(B2) | 2005-03-01 | Waxelbaum | Applicant |
| US6871214(B2) | 2005-03-01 | Parsons et al. | Applicant |
| US6880079(B2) | 2005-04-01 | Kefford et al. | Applicant |
| US6886096(B2) | 2005-04-01 | Appenseller et al. | Applicant |
| US6892074(B2) | 2005-05-01 | Tarkiainen et al. | Applicant |
| US6912285(B2) | 2005-06-01 | Jevans | Applicant |
| US6912400(B1) | 2005-06-01 | Olsson et al. | Applicant |
| USRE38787(E) | 2005-08-01 | Sainton et al. | Applicant |
| US6938065(B2) | 2005-08-01 | Jain | Applicant |
| US6941349(B2) | 2005-09-01 | Godfrey et al. | Applicant |
| US6980792(B2) | 2005-12-01 | Iivonen et al. | Applicant |
| US6983138(B1) | 2006-01-01 | Helferich | Applicant |
| US6990587(B2) | 2006-01-01 | Willins et al. | Applicant |
| US7003308(B1) | 2006-02-01 | Fuoss et al. | Applicant |
| US7006459(B2) | 2006-02-01 | Kokot et al. | Applicant |
| US7013391(B2) | 2006-03-01 | Herle et al. | Applicant |
| US7017181(B2) | 2006-03-01 | Spies et al. | Applicant |
| US7020688(B2) | 2006-03-01 | Sykes, Jr. | Applicant |
| US7023967(B1) | 2006-04-01 | Andersson et al. | Applicant |
| US7031437(B1) | 2006-04-01 | Parsons et al. | Applicant |
| US7054905(B1) | 2006-05-01 | Hanna et al. | Applicant |
| US7058390(B2) | 2006-06-01 | Chikazawa | Applicant |
| US7062536(B2) | 2006-06-01 | Fellenstein et al. | Applicant |
| US7065189(B2) | 2006-06-01 | Wakabayashi | Applicant |
| US7068993(B2) | 2006-06-01 | Rai et al. | Applicant |
| US7076528(B2) | 2006-07-01 | Premutico | Applicant |
| US7082469(B2) | 2006-07-01 | Gold et al. | Applicant |
| US7082536(B2) | 2006-07-01 | Filipi-Martin | Applicant |
| US7088990(B1) | 2006-08-01 | Isomursu et al. | Applicant |
| US7092743(B2) | 2006-08-01 | Vegh | Applicant |
| US7100048(B1) | 2006-08-01 | Czajkowski et al. | Applicant |
| US7107246(B2) | 2006-09-01 | Wang | Applicant |
| US7113601(B2) | 2006-09-01 | Ananda | Applicant |
| US7113803(B2) | 2006-09-01 | Dehlin | Applicant |
| US7113979(B1) | 2006-09-01 | Smith et al. | Applicant |
| US7116762(B2) | 2006-10-01 | Bennett, III et al. | Applicant |
| US7116997(B2) | 2006-10-01 | Byers et al. | Applicant |
| US7133687(B1) | 2006-11-01 | El-Fishawy et al. | Applicant |
| US7146009(B2) | 2006-12-01 | Andivahis et al. | Applicant |
| US7149537(B1) | 2006-12-01 | Kupsh et al. | Applicant |
| US7149893(B1) | 2006-12-01 | Leonard et al. | Applicant |
| US7155241(B2) | 2006-12-01 | Helferich | Applicant |
| US7218919(B2) | 2007-05-01 | Vaananen | Applicant |
| US7289797(B2) | 2007-05-01 | Kato | Applicant |
| US7233655(B2) | 2007-06-01 | Gailey et al. | Applicant |
| US7251314(B2) | 2007-07-01 | Huang | Applicant |
| US7254384(B2) | 2007-08-01 | Gailey et al. | Applicant |
| US7286817(B2) | 2007-10-01 | Provost | Applicant |
| US2001/0005857(A1) | 2001-06-01 | Lazaridis et al. | Applicant |
| US2001/0005860(A1) | 2001-06-01 | Lazaridis et al. | Applicant |
| US2001/0005861(A1) | 2001-06-01 | Mousseau et al. | Applicant |
| US2001/0013071(A1) | 2001-08-01 | Lazaridis et al. | Applicant |
| US2001/0048737(A1) | 2001-12-01 | Goldberg et al. | Applicant |
| US2001/0054115(A1) | 2001-12-01 | Ferguson et al. | Applicant |
| US2002/0012323(A1) | 2002-01-01 | Petite | Applicant |
| US2002/0023131(A1) | 2002-02-01 | Wu et al. | Applicant |
| US2002/0029258(A1) | 2002-03-01 | Mousseau et al. | Applicant |
| US2002/0032658(A1) | 2002-03-01 | Oki et al. | Applicant |
| US2002/0035687(A1) | 2002-03-01 | Skantze | Applicant |
| US2002/0038298(A1) | 2002-03-01 | Kusakabe et al. | Applicant |
| US2002/0039419(A1) | 2002-04-01 | Akimoto et al. | Applicant |
| US2002/0049818(A1) | 2002-04-01 | Gilhuly et al. | Applicant |
| US2002/0052218(A1) | 2002-05-01 | Rhee | Applicant |
| US2002/0065887(A1) | 2002-05-01 | Paik et al. | Applicant |
| US2002/0065895(A1) | 2002-05-01 | Zhang et al. | Applicant |
| US2002/0087645(A1) | 2002-07-01 | Ertugrul et al. | Applicant |
| US2002/0091777(A1) | 2002-07-01 | Schwartz | Applicant |
| US2002/0091782(A1) | 2002-07-01 | Benninghoff | Applicant |
| US2002/0101998(A1) | 2002-08-01 | Wong et al. | Applicant |
| US2002/0107928(A1) | 2002-08-01 | Chalon | Applicant |
| US2002/0120696(A1) | 2002-08-01 | Mousseau et al. | Applicant |
| US2002/0120788(A1) | 2002-08-01 | Wang et al. | Applicant |
| US2002/0128036(A1) | 2002-09-01 | Yach et al. | Applicant |
| US2002/0138735(A1) | 2002-09-01 | Felt et al. | Applicant |
| US2002/0138759(A1) | 2002-09-01 | Dutta | Applicant |
| US2002/0156691(A1) | 2002-10-01 | Hughes et al. | Applicant |
| US2002/0178353(A1) | 2002-11-01 | Graham | Applicant |
| US2002/0181701(A1) | 2002-12-01 | Lee | Applicant |
| US2002/0194281(A1) | 2002-12-01 | McConnell et al. | Applicant |
| US2002/0194285(A1) | 2002-12-01 | Mousseau et al. | Applicant |
| US2003/0005066(A1) | 2003-01-01 | Lazaridis et al. | Applicant |
| US2003/0009698(A1) | 2003-01-01 | Lindeman et al. | Applicant |
| US2003/0037261(A1) | 2003-02-01 | Meffert et al. | Applicant |
| US2003/0048905(A1) | 2003-03-01 | Gehring et al. | Applicant |
| US2003/0050987(A1) | 2003-03-01 | Lazaridis et al. | Applicant |
| US2003/0055902(A1) | 2003-03-01 | Amir et al. | Applicant |
| US2003/0061511(A1) | 2003-03-01 | Fischer | Applicant |
| US2003/0078058(A1) | 2003-04-01 | Vatanen et al. | Applicant |
| US2003/0081621(A1) | 2003-05-01 | Godfrey et al. | Applicant |
| US2003/0088633(A1) | 2003-05-01 | Chiu et al. | Applicant |
| US2003/0097361(A1) | 2003-05-01 | Huang et al. | Applicant |
| US2003/0115448(A1) | 2003-06-01 | Bouchard | Applicant |
| US2003/0120733(A1) | 2003-06-01 | Forman | Applicant |
| US2003/0126216(A1) | 2003-07-01 | Avila et al. | Applicant |
| US2003/0126220(A1) | 2003-07-01 | Wanless | Applicant |
| US2003/0142364(A1) | 2003-07-01 | Goldstone | Applicant |
| US2003/0182575(A1) | 2003-09-01 | Korfanta | Applicant |
| US2003/0187938(A1) | 2003-10-01 | Mousseau et al. | Applicant |
| US2003/0191808(A1) | 2003-10-01 | Adler et al. | Applicant |
| US2003/0194990(A1) | 2003-10-01 | Helferich | Applicant |
| US2003/0204568(A1) | 2003-10-01 | Bhargava et al. | Applicant |
| US2003/0220979(A1) | 2003-11-01 | Hejl | Applicant |
| US2003/0222765(A1) | 2003-12-01 | Curbow et al. | Applicant |
| US2003/0235307(A1) | 2003-12-01 | Miyamoto | Applicant |
| US2003/0235308(A1) | 2003-12-01 | Boynton et al. | Applicant |
| US2003/0237082(A1) | 2003-12-01 | Thurlow | Applicant |
| US2004/0019780(A1) | 2004-01-01 | Waugh et al. | Applicant |
| US2004/0021889(A1) | 2004-02-01 | McAfee et al. | Applicant |
| US2004/0024824(A1) | 2004-02-01 | Ferguson et al. | Applicant |
| US2004/0030906(A1) | 2004-02-01 | Marmigere et al. | Applicant |
| US2004/0052340(A1) | 2004-03-01 | Joffe et al. | Applicant |
| US2004/0059598(A1) | 2004-03-01 | Wellons et al. | Applicant |
| US2004/0059914(A1) | 2004-03-01 | Karaoguz | Applicant |
| US2004/0060056(A1) | 2004-03-01 | Wellons et al. | Applicant |
| US2004/0073619(A1) | 2004-04-01 | Gilhuly et al. | Applicant |
| US2004/0078488(A1) | 2004-04-01 | Patrick | Applicant |
| US2004/0083271(A1) | 2004-04-01 | Tosey | Applicant |
| US2004/0083365(A1) | 2004-04-01 | Renier et al. | Applicant |
| US2004/0111478(A1) | 2004-06-01 | Gross et al. | Applicant |
| US2004/0111480(A1) | 2004-06-01 | Yue | Applicant |
| US2004/0116119(A1) | 2004-06-01 | Lewis et al. | Applicant |
| US2004/0122847(A1) | 2004-06-01 | Rodgers | Applicant |
| US2004/0122905(A1) | 2004-06-01 | Smith et al. | Applicant |
| US2004/0137884(A1) | 2004-07-01 | Engstrom et al. | Applicant |
| US2004/0137955(A1) | 2004-07-01 | Engstrom et al. | Applicant |
| US2004/0165727(A1) | 2004-08-01 | Moreh et al. | Applicant |
| US2004/0185877(A1) | 2004-09-01 | Asthana et al. | Applicant |
| US2004/0194116(A1) | 2004-09-01 | McKee et al. | Applicant |
| US2004/0196978(A1) | 2004-10-01 | Godfrey et al. | Applicant |
| US2004/0198348(A1) | 2004-10-01 | Gresham et al. | Applicant |
| US2004/0199669(A1) | 2004-10-01 | Riggs et al. | Applicant |
| US2004/0202327(A1) | 2004-10-01 | Little et al. | Applicant |
| US2004/0203642(A1) | 2004-10-01 | Zatloukal et al. | Applicant |
| US2004/0205106(A1) | 2004-10-01 | Adler et al. | Applicant |
| US2004/0205248(A1) | 2004-10-01 | Little et al. | Applicant |
| US2004/0205330(A1) | 2004-10-01 | Godfrey et al. | Applicant |
| US2004/0208296(A1) | 2004-10-01 | Aboujaoude et al. | Applicant |
| US2004/0212639(A1) | 2004-10-01 | Smoot et al. | Applicant |
| US2004/0221014(A1) | 2004-11-01 | Tomkow | Applicant |
| US2004/0221048(A1) | 2004-11-01 | Ogier | Applicant |
| US2004/0230657(A1) | 2004-11-01 | Tomkow | Applicant |
| US2004/0243677(A1) | 2004-12-01 | Curbow et al. | Applicant |
| US2004/0243844(A1) | 2004-12-01 | Adkins | Applicant |
| US2004/0243847(A1) | 2004-12-01 | Way | Applicant |
| US2004/0249768(A1) | 2004-12-01 | Kontio et al. | Applicant |
| US2004/0249895(A1) | 2004-12-01 | Way | Applicant |
| US2004/0249899(A1) | 2004-12-01 | Shiigi | Applicant |
| US2004/0252727(A1) | 2004-12-01 | Mousseau et al. | Applicant |
| US2004/0266441(A1) | 2004-12-01 | Sinha et al. | Applicant |
| US2005/0003809(A1) | 2005-01-01 | Kato | Applicant |
| US2005/0009502(A1) | 2005-01-01 | Little et al. | Applicant |
| US2005/0015455(A1) | 2005-01-01 | Liu | Applicant |
| US2005/0019634(A1) | 2005-01-01 | Legg | Applicant |
| US2005/0025172(A1) | 2005-02-01 | Frankel | Applicant |
| US2005/0025291(A1) | 2005-02-01 | Peled et al. | Applicant |
| US2005/0025297(A1) | 2005-02-01 | Finnigan | Applicant |
| US2005/0038863(A1) | 2005-02-01 | Onyon et al. | Applicant |
| US2005/0044160(A1) | 2005-02-01 | McElligott | Applicant |
| US2005/0055413(A1) | 2005-03-01 | Keohane et al. | Applicant |
| US2005/0058124(A1) | 2005-03-01 | Helferich | Applicant |
| US2005/0058260(A1) | 2005-03-01 | Lasensky et al. | Applicant |
| US2005/0060720(A1) | 2005-03-01 | Mayer | Applicant |
| US2005/0076109(A1) | 2005-04-01 | Mathew et al. | Applicant |
| US2005/0091329(A1) | 2005-04-01 | Friskel | Applicant |
| US2005/0099654(A1) | 2005-05-01 | Chen | Applicant |
| US2005/0099998(A1) | 2005-05-01 | Semper | Applicant |
| US2005/0102381(A1) | 2005-05-01 | Jiang et al. | Applicant |
| US2005/0108336(A1) | 2005-05-01 | Naick et al. | Applicant |
| US2005/0108359(A1) | 2005-05-01 | Hyder et al. | Applicant |
| US2005/0114652(A1) | 2005-05-01 | Swedor et al. | Applicant |
| US2005/0130361(A1) | 2005-06-01 | Maguire et al. | Applicant |
| US2005/0132010(A1) | 2005-06-01 | Muller | Applicant |
| US2005/0135681(A1) | 2005-06-01 | Schirmer | Applicant |
| US2005/0137009(A1) | 2005-06-01 | Vetelainen | Applicant |
| US2005/0138353(A1) | 2005-06-01 | Spies | Applicant |
| US2005/0141718(A1) | 2005-06-01 | Yu et al. | Applicant |
| US2005/0148356(A1) | 2005-07-01 | Ferguson et al. | Applicant |
| US2005/0163320(A1) | 2005-07-01 | Brown et al. | Applicant |
| US2005/0165740(A1) | 2005-07-01 | Kerr et al. | Applicant |
| US2005/0176451(A1) | 2005-08-01 | Helferich | Applicant |
| US2005/0180576(A1) | 2005-08-01 | Jevans | Applicant |
| US2005/0188024(A1) | 2005-08-01 | Singer | Applicant |
| US2005/0188045(A1) | 2005-08-01 | Katsikas | Applicant |
| US2005/0198143(A1) | 2005-09-01 | Moody et al. | Applicant |
| US2005/0198170(A1) | 2005-09-01 | LeMay et al. | Applicant |
| US2005/0198506(A1) | 2005-09-01 | Qi et al. | Applicant |
| US2005/0210064(A1) | 2005-09-01 | Caldini et al. | Applicant |
| US2005/0210106(A1) | 2005-09-01 | Cunningham | Applicant |
| US2005/0210246(A1) | 2005-09-01 | Faure | Applicant |
| US2005/0216587(A1) | 2005-09-01 | John | Applicant |
| US2005/0216735(A1) | 2005-09-01 | Huang | Applicant |
| US2005/0251558(A1) | 2005-11-01 | Zaki | Applicant |
| US2005/0257057(A1) | 2005-11-01 | Ivanov et al. | Applicant |
| US2005/0265551(A1) | 2005-12-01 | Hara | Applicant |
| US2005/0282525(A1) | 2005-12-01 | Adams et al. | Applicant |
| US2006/0013368(A1) | 2006-01-01 | LaBaw | Applicant |
| US2006/0019638(A1) | 2006-01-01 | Chui et al. | Applicant |
| US2006/0019639(A1) | 2006-01-01 | Adams et al. | Applicant |
| US2006/0020667(A1) | 2006-01-01 | Wang et al. | Applicant |
| US2006/0021038(A1) | 2006-01-01 | Brown et al. | Applicant |
| US2006/0021066(A1) | 2006-01-01 | Clayton et al. | Applicant |
| US2006/0026246(A1) | 2006-02-01 | Fukuhara et al. | Applicant |
| US2006/0029191(A1) | 2006-02-01 | Miller et al. | Applicant |
| US2006/0041505(A1) | 2006-02-01 | Enyart | Applicant |
| US2006/0041625(A1) | 2006-02-01 | Chen et al. | Applicant |
| US2006/0046720(A1) | 2006-03-01 | Toropainen et al. | Applicant |
| US2006/0047766(A1) | 2006-03-01 | Spadea | Applicant |
| US2006/0053202(A1) | 2006-03-01 | Foo et al. | Applicant |
| US2006/0068768(A1) | 2006-03-01 | Sanding et al. | Applicant |
| US2006/0069737(A1) | 2006-03-01 | Gilhuly et al. | Applicant |
| US2006/0072761(A1) | 2006-04-01 | Johnson et al. | Applicant |
| US2006/0074706(A1) | 2006-04-01 | Gilham | Applicant |
| US2006/0075027(A1) | 2006-04-01 | Zager et al. | Applicant |
| US2006/0080384(A1) | 2006-04-01 | Robinson et al. | Applicant |
| US2006/0090065(A1) | 2006-04-01 | Bush et al. | Applicant |
| US2006/0095510(A1) | 2006-05-01 | Rouse et al. | Applicant |
| US2006/0101119(A1) | 2006-05-01 | Qureshi et al. | Applicant |
| US2006/0133585(A1) | 2006-06-01 | Daigle et al. | Applicant |
| US2006/0135128(A1) | 2006-06-01 | Skoog | Applicant |
| US2006/0155698(A1) | 2006-07-01 | Vayssiere | Applicant |
| US2006/0155812(A1) | 2006-07-01 | Looman | Applicant |
| US2006/0168065(A1) | 2006-07-01 | Martin | Applicant |
| US2006/0168072(A1) | 2006-07-01 | Park | Applicant |
| US2006/0177015(A1) | 2006-08-01 | Skakkebaek et al. | Applicant |
| US2006/0182124(A1) | 2006-08-01 | Cole et al. | Applicant |
| US2006/0187897(A1) | 2006-08-01 | Dabbs et al. | Applicant |
| US2006/0190533(A1) | 2006-08-01 | Shannon et al. | Applicant |
| US2006/0194572(A1) | 2006-08-01 | Fresonke et al. | Applicant |
| US2006/0200528(A1) | 2006-09-01 | Pathiyal | Applicant |
| US2006/0217112(A1) | 2006-09-01 | Mo | Applicant |
| US2006/0218224(A1) | 2006-09-01 | Agrawal et al. | Applicant |
| US2006/0218244(A1) | 2006-09-01 | Rassmussen et al. | Applicant |
| US2006/0221916(A1) | 2006-10-01 | Taylor et al. | Applicant |
| US2006/0224893(A1) | 2006-10-01 | Sales et al. | Applicant |
| US2006/0230266(A1) | 2006-10-01 | Maes | Applicant |
| US2006/0233370(A1) | 2006-10-01 | Jung et al. | Applicant |
| US2006/0234680(A1) | 2006-10-01 | Doulton | Applicant |
| US2006/0239424(A1) | 2006-10-01 | Walter | Applicant |
| US2006/0240868(A1) | 2006-10-01 | Kaplan et al. | Applicant |
| US2006/0247962(A1) | 2006-11-01 | Harvey et al. | Applicant |
| US2006/0248148(A1) | 2006-11-01 | Timmins et al. | Applicant |
| US2006/0259558(A1) | 2006-11-01 | Yen | Applicant |
| US2006/0265660(A1) | 2006-11-01 | Hullot et al. | Applicant |
| US2006/0270461(A1) | 2006-11-01 | Won et al. | Applicant |
| US2006/0285533(A1) | 2006-12-01 | Divine et al. | Applicant |
| US2006/0286990(A1) | 2006-12-01 | Juan et al. | Applicant |
| US2007/0042747(A1) | 2007-02-01 | Sun | Applicant |
| US2007/0117541(A1) | 2007-05-01 | Helferich | Applicant |
| US2007/0162454(A1) | 2007-07-01 | D'Albora et al. | Applicant |
| EP631419 | 1994-12-01 | Applicant | |
| EP777394 | 1997-06-01 | Applicant | |
| EP831664 | 1997-09-01 | Applicant | |
| JP3232325 | 1991-10-01 | Applicant | |
| JP6245254 | 1994-09-01 | Applicant | |
| JP6-318899 | 1994-11-01 | Applicant | |
| JP8-228368 | 1996-09-01 | Applicant | |
| JP8336182 | 1996-12-01 | Applicant | |
| KR164369 | 1998-09-01 | Applicant | |
| WO97/08906 | 1997-03-01 | Applicant | |
| WO9731488 | 1997-08-01 | Applicant | |
| WO9858476 | 1998-12-01 | Applicant | |
| WO9965256 | 1999-12-01 | Applicant |
Non-Patent Literature (33)
- Khare, R., et al., “Scenarios for an Internet-Scale Event Notification Service (ISENS)”, Internet-Draft, Aug. 13, 1998, 18 pages.Applicant
- Siewiorek, D.P., et al., “Computer Structures: Principles and Examples”, McGraw-Hill Book Company, 1982, 21 pages.Applicant
- “Active Channel Server Frequently Asked Questions (FAQ)”, Microsoft Corporation, Q181161, 2006, 2 pages.Applicant
- Engst, A.C., “TidBITS#349/Oct. 14, 1996,” TidBITS Electronic Publishing, 1996, 10 pages.Applicant
- Engst, A.C., “The Real TidBITS Channel”, TidBITS Electronic Publishing, 1998, 4 pages.Applicant
- “Introduction to Active Channel Technology”, Microsoft Corporation, 2006, 5 pages.Applicant
- Gillay, C.Z., “Subscriptions, Channels, and Active Desktop”, TechNotes, Franklin, Beedle & Associates, Inc., 1999, pp. 1-6.Applicant
- Winnick Cluts, N., et al., “A Preview of Active Channel and the Active Desktop for Internet Explorer 4.0”, Microsoft Corporation, 1997, 13 pages.Applicant
- Anonymous, PatentAtlas, “Patent Cluster Tree Encompassing the Subject in Question: SAMPLE” (date unknown).Applicant
- Anonymous, usamobility.com, “ReFLEX Wireless Data Technology” (date unknown).Applicant
- International Preliminary Examination Report dated Jul. 10, 2001 (7 pages) PCT/US00/08261 Jul. 1, 2001.Applicant
- Statutory Invention Registration No. H610; Date: Mar. 7, 1989, Focarile et al.Applicant
- PLUS Patent Linguistics Utility Search Results for S/N 10445257, Searched Mar. 16, 2005.Applicant
- Anonymous, PatentAtlas, “Patent Cluster Tree Encompassing the Subject in Question: SAMPLE” (date unknown).Applicant
- “New Wyndmail version 1.5 features another first for wireless industry,” Busines Wire (Author Unknown) (Aug. 19, 1996).Applicant
- “WyndMail wireless e-mail now provides “Message Header Preview” for Apple Powerbook and MessagePad,” Business Wire (Author Unknown) (Jan. 9, 1997).Applicant
- Anonymous, “Envoy Wireless Communicator User's Guide,” Motorola, Inc. (1994).Applicant
- Anonymous, “General Magic OS Targets US, Japan,” Reed Business Information (1996).Applicant
- Anonymous, “MessagePad 2000: New Newton Exceeds Expectation,” TidBITS #379 (May 12,1997).Applicant
- Anonymous, “NETCOM and RadioMail form Strategic Alliance Enabling NETCOM Customers to Exchange Email, Send Faxes and Access Web Sites Wireless,” Business Wire (Dec. 11, 2006).Applicant
- Anonymous, “New Features of the Newton 2.0 Operating System,” Apple Computer, Inc. (1995).Applicant
- Anonymous, “New RadioMail Package Brings Maximum Affordability and Simplicity to Wireless Communications,” AllBusiness (Feb. 27, 1996).Applicant
- Anonymous, “Newton Apple MessagePad Handbook,” Apple Computer, Inc. (1995).Applicant
- Anonymous, “Newton Internet Enabler,” (1997).Applicant
- Anonymous, “Newton MessagePad (Original) Specs,” EveryMac.com (1996).Applicant
- Anonymous, “RadioMail Corporation Releases Wireless Internet Access Solution for CDPD Carriers,” Business Wire (Oct. 7, 1996).Applicant
- Anonymous, “Using E-Mail on Your Newton Device,” Apple Computer, Inc. (1997).Applicant
- Anonymous, “Sony Electronics Introduces Magic Link PIC-2000,” Business Wire (Oct. 30, 1995).Applicant
- Denise Shelton, “RadioMail can Find, Retrieve Web Pages,” CNET News (Jun. 4, 1996).Applicant
- Ira Brodsky, “Instant Gratification,” Telephone Online (Jan. 15, 1999).Applicant
- Mark Kellner, “Earthquake and RadioMail,” The Washington Times (Jan. 24, 1994).Applicant
- Mike Fine, “The AllPoints Wireless PC Card and RadioMail Service,” www.palmtoppaer.com (Date Unknown).Applicant
- Stuart Price, “Product Reviews: Eudora Pro for Newton 1.0,” MacUser (Dec. 22, 1996).Applicant