US5274696A - Protocol for transmitting messages in a network - Google Patents
Protocol for transmitting messages in a network Download PDFInfo
- Publication number
- US5274696A US5274696A US07/680,952 US68095291A US5274696A US 5274696 A US5274696 A US 5274696A US 68095291 A US68095291 A US 68095291A US 5274696 A US5274696 A US 5274696A
- Authority
- US
- United States
- Prior art keywords
- site
- sending
- receiving
- message
- sites
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Lifetime
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/53—Centralised arrangements for recording incoming messages, i.e. mailbox systems
- H04M3/533—Voice mail systems
- H04M3/53325—Interconnection arrangements between voice mail systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
Definitions
- the present invention pertains to a method for delivering messages among sites of a network of store-and-forward messaging system sites using telephone lines.
- Embodiments of the present invention advantageously satisfy the above-identified need in the art and provide a method for transmitting voice messages, user names --alphabetic and/or spoken, and network addresses among sites of a network of store-and-forward messaging system sites using telephone lines.
- the inventive method for transmitting data messages and voice signals between a sending store-and-forward messaging systems site and a receiving store-and-forward messaging site of a network of store-and-forward messaging systems which are connected by one or more telephone lines comprises the steps of: (a) placing a telephone call form the sending site to the receiving site to a predetermined telephone number over one of the telephone lines; (b) connecting data transmission and reception apparatus to the telephone lines at the sending site and the receiving site; (c) exchanging predetermined control commands and data messages using the data transmission and reception apparatus at the sending and receiving sites, the predetermined control commands specifying the communications procedure; (d) disabling the data transmission and reception apparatus from exchanging control commands and data messages and connecting voice transmission and reception apparatus to the telephone line at the sending site and the receiving site; (e) transmitting voice signals between the sending and receiving sites using the voice transmission and reception apparatus at the sending and receiving sites; (f) enabling the data transmission and reception apparatus for exchanging control commands and data messages at the sending site and the receiving site; (g) exchanging delivery information using
- FIG. 1 is an block diagram of a network of store-and-forward messaging system sites.
- FIG. 2 shows control commands and responses exchanged in accordance with the present invention by two communicating voice store-and-forward messaging sites of the network shown in FIG. 1.
- FIG. 1 shows network 90 which utilizes an embodiment of the present invention.
- network 90 which utilizes an embodiment of the present invention.
- FIG. 2 shows network 90 which utilizes an embodiment of the present invention.
- Network 90 is comprised of voice store-and-forward messaging system sites 10 l to 10 n .
- Each of store-and-forward messaging system sites 10 l to 10 n interacts with local users and is comprised of a local database 20 l to 20 n , respectively. Further, as is shown in FIG. 1, each of store-and-forward system sites 10 l to 10 n has a communications connection with predetermined ones of the other store-and-forward messaging system sites in network 90.
- network 90 may also be embodied in a manner wherein private branch exchanges are utilized so that any site may contact any other site via, for example, the public telephone network. Embodiments of the present invention provide the mechanism whereby the transactions described below occur.
- the message sender's local store-and-forward messaging system site In one type of message transfer transaction which is carried out over network 90, whenever a message sender at a first store-and-forward messaging system site addresses a message recipient at a second store-and-forward messaging system site by name and the message recipient's name is not stored in the message sender's local database, the message sender's local store-and-forward messaging system site requires the message sender to address the message recipient by numeric address. Then, the message sender's local store-and-forward messaging system site transmits the message, for example, a voice message, to the local store-and-forward message system site of the message recipient along with the message sender's alphabetic name and a flag which indicates that the message recipient's name is unknown to the sending system site.
- the message sender's local store-and-forward messaging system site transmits the message, for example, a voice message, to the local store-and-forward message system site of the message recipient along with the message sender's alphabetic name and a
- the receiving system site sends a communication to the sending system site to: (a) request a spoken record of the message sender's name if the message recipient's system site does not have the message sender's name in its local database and (b) transmit the message recipient's alphabetic and spoken name.
- both the sender's and recipient's system sites update their local databases with the sender's and the recipient's alphabetic and spoken names, respectively.
- both the sender's and recipient's system sites now know the sender's and recipient's names and name entry and name confirmation can be used the next time a message is addressed to the same recipient and name entry and name confirmation for the message sender can also be used by users of the original message recipient's system site.
- the message sender may address a message recipient by either name or telephone number. Then, when the message sended's local store-and-forward message system transmits a message to the local store-and-forward message system site of the message recipient, both the message recipient's alphabetic name and telephone number are transmitted to the message recipient's system site. In response, the message recipient's system site verifies the message recipient's alphabetic name and telephone number and the message may not be accepted unless both match. This provides a measure of security in case the recipient is a person with the same name as a user who has previously left the system.
- FIG. 2 shows the control commands and responses exchanged by two communicating voice store-and-forward messaging system sites during a typical session.
- a session is established when site "i" makes a telephone call to a reserved access number at site"j".
- the answering site, site "j" knows that this telephone call is a network call which is being made by another voice store-and-forward messaging site, site "i", as opposed to, for example, a telephone call which is being made by a user, because the call is being made to a reserved access telephone number.
- the telephone call may go over public switched telephone lines or over private lines.
- the communicating sites perform a line test to ensure that the quality of the line is adequate for the session. If the line passes the test, then the two sites connect modems to the line. Although a line test is not essential, it is highly recommended, to ensure that voice signals which are delivered across the network remain of high quality. Those of ordinary skill in the art understand that there are many methods which are well known to those of ordinary skill in the art for performing a line test.
- the sites exchange control commands and responses in a manner which will be described in detail below in connection with FIG. 2.
- the sites at predetermined times during a session, the sites "turn-off" the modems and the communicating sites exchange voice signals over the line.
- the voice signals may relate to a voice message being delivered from one user to another or they may relate to a spoken name.
- the sites "turn-on" the modems to permit the sites to exchange verification of delivery notifications and to move on to the next user message or name.
- a session ends when either site, generally the sending site hangs up by, for example, going on-hook. The other site will disconnect because it will detect the remote modem dropping--for example, it detects a carrier fault--or because the telephone network signals the far end disconnect, whichever occurs first.
- the protocol used for communication between sites is comprised of four (4) layers.
- the first or bottom layer i.e., the physical layer is where mechanical, electrical, functional, and procedural characteristics are defined to access a physical medium, for example, a telephone line.
- the next or second layer i.e., the data link layer, provides for reliable transfer of information across the physical layer by sending blocks of data, referred to as frames, along with synchronization, error control, and flow control.
- the second layer also supervises transitions from: (a) line test stage to modem; (b) from modem to voice; and (c) voice to modem.
- the first two layers are well known to those of ordinary skill in the art.
- FIG. 2 shows the control commands and responses which reside at the session and application layers.
- the session layer provides a structure for communication between applications and, as such, it establishes, manages, and terminates connections, i.e., sessions, between message delivery applications.
- the application layer carries out exchanges of user messages and names using services provided by the bottom layers.
- sending site "i” generates a "Connect command” whenever the bottom layers notify it that the link is ready, i.e., receiving site "j" has answered, the line test has been performed and passed, and the modem is on line.
- a “Connect command” comprises the following information: (a) protocol version number used by sending site “i” so that sites which utilize older versions of the protocol can communicate--for example, if the protocol version numbers of sending site “i” and receiving site “j” are different, the older protocol is used; (b) channel number, i.e., port, being used by sending site “i” for this session--this is needed to route received application layer commands and responses to the proper process, i.e., the software task that is handling this particular session; (c) flag to indicate whether sending site “i” will permit receiving site “j” to turn the connection around after sending site “i” has finished sending all its voice messages, so that receiving site “j” can "piggyback," i.e., send, its own messages during the same call --the “piggyback” feature is decided solely by sending site “i”; (d) flag which indicates whether sending site "i” will exchange names with receiving site "j”--if one site is willing to exchange, but not the other, the latter wins; (
- a “Connect response” comprises the following information: (a) protocol version number used by receiving site “j”; (b) channel number being used by receiving site “j” for this session; (c) flag which indicates whether receiving site “j” will exchange names with sending site “i”; (d) status code which indicates whether receiving site “j” will accept the call or a reason why it cannot; (e) identification of receiving site “j”; and (f) identification of receiving node.
- the byte format for this command is set forth in detail in the Appendix.
- the first command of a repeating set is a "Record command" which is sent from sending site "i" to receiving site "j".
- the "Record command” comprises the following information: (a) message sender's network address and message recipient's network address; (b) message recipient's name if it is available at sending site "i"--This is sent so that receiving site "j" can verify that both the message recipient's network address and name match a profile of a message recipient.
- receiving site "j” in response to the "Record command," sends back a "Record response” which comprises the following information: (a) status code, indicating whether receiving site "j" will accept the message or the reason why it cannot.
- Some possible reasons for not accepting the message are: (i) the message recipient is not valid one, (ii) the message recipient's mailbox is full, and (iii) so forth; (b) a flag indicating whether the message sender's name was added to the database at receiving site "j"; (c) a flag indicating whether receiving site "j" wishes to receive the spoken name of the message sender and whether it intends to send the spoken name of the message recipient; (d) name of the message recipient, if sending site "i” did not include it in the "Record command” because sending site "i” did not have it and the communicating sites negotiated during session establishment that user names would be exchanged.
- the byte format for this command is set forth in detail in the Appendix.
- next step in the communication depends on the particular "Record command” and "Record response” exchanged in a particular case.
- line 240 of FIG. 2 shows a portion of a communication wherein the next step comprises sending site “i" transmitting the message sender's spoken name to receiving site "j". This transmittal is accomplished when site “i" and site “j" switch off their modems and, then, sending site “i” transmits the message sender's spoken name while receiving site “j” receives and records it. Once the recording is completed, site “i” and site “j” switch their modems back on so that receiving site “j” may acknowledge successful or non-successful reception. As shown at line 250 of FIG.
- Site "i” and site “j” may decide, based on the "Record command” and "Record response” sent previously, to transmit the spoken name for the message recipient. To do that, they just repeat the two steps outlined above, reversing roles, as shown by lines 260 and 270 of FIG. 2. If this is not appropriate, these steps are skipped.
- a voice message is transmitted in a manner which is similar to the manner in which the spoken names were transmitted. Note that these steps may also be skipped. This would occur, for example, in cases such as: (a) delivery of a "return receipt"--which "return receipt” has no associated voice message; (b) delivery of a message for which receiving site "j" already has the recording; or (c) duplicate delivery of a previously sent message.
- a variation of the above-described repeating set of commands and responses is used whenever sending site "i" wishes to "export” a selected list of subscriber names, alphabetic and spoken, to receiving site "j".
- the "Record command” specifies that this is a "name only” message. Then, only a “Record command”, “Record response”, optionally the message sender's spoken name, and "Stop response” are exchanged.
- sending site “i” After sending site “i” has finished delivering everything it intended to deliver, control of the connection reverts back to the session layer.
- sending site “i” has two options. First, it goes on-hook, i.e., "hangs up", to signal the end of the call or, second, it sends a "Piggyback command” having no parameters. The byte format for this command is set forth in detail in the Appendix. If sending site “i” sends a "Piggyback command”, then receiving site “j” determines whether it has any messages to deliver to sending site "i”. If it does, receiving site “j” responds by transmitting a "Connect command” to initiate a session from the beginning, except with roles reversed and in the opposite direction. Otherwise, receiving site “j” responds to the "Piggyback command” by going on-hook.
- a digital signal processor is used to provide the above-described functions which relate to a modem.
- DSP digital signal processor
- any channel i.e., port
- any channel i.e., port
- the same board used in PhoneMail for voice processing using DSP techniques provides modem emulation and line test functions used at the beginning of a network message delivery session, i.e., the same hardware is used to run the DSP code needed for voice processing, modem emulation, and line testing. This permits one to utilize any port for intersite message delivery.
- a DSP may perform the following functions: originate modem, answer modem, originate line test, and answer line test. Further, it should be clear to those of ordinary skill in the art as to how these functions may be emulated by a DSP. This may be performed as follows. First, a sending site would command its DSP subsystem to start emulating an originate modem on the channel being used for a particular connection. The recipient site commands its DSP subsystem to emulate an answer modem. For example, both DSP subsystems might emulate a Bell System 103 modem. Once the respective DSP subsystems report "carrier detect," the above-described data exchange takes place. Of course, those of ordinary skill in the art recognize that, just as with a standalone modem, it is possible to get a "carrier fault" at any time during the connection which would cause the connection to be dropped.
- transitions occur from "modem” mode to "voice playback/recording” mode and then back to “modem” mode. This occurs as follows. First, receiving site “j” drops its carrier, i.e., stops sending the carrier tone. Second, sending site “i” detects a carrier fault, stops its own modem, and starts playing back a voice message. Third, receiving site “j” starts recording as soon as it detects that the carrier from sending site “i” has dropped. Fourth, as receiving site “j” is recording, it constantly monitors the incoming voice signal to detect the end thereof and the beginning of a modem carrier. Fifth, whenever sending site “i” reaches the end of the voice message, it turns on its answer modem, i.e., it puts carrier on the line. Lastly, receiving site “j” stops recording and starts its own originate modem.
- embodiments of the present invention may be fabricated utilizing a stand-alone, off-the-shelf modem along with hardware needed to switch it in and out of the line, the fabrication of which hardware is well known to those of ordinary skill in the art, so that voice can be sent over the same line.
- embodiments of the present invention may be fabricated utilizing a stand-alone, off-the-shelf modem and wherein parallel calls are made from sending site to receiving site. In one such embodiment, one call will carry the voice signals and the other call will carry data transmission, i.e., commands and responses, using the modem.
- embodiments of the present invention may be fabricated utilizing DTMF tone generators and detectors for sending commands and responses as an alternative to the use of modems or modem emulators.
- embodiments of the present invention may be fabricated utilizing an alternative protocol such as, for example, wherein the message sender's spoken name and voice message are sent in one transmission, but separated by a predetermined tone.
- ⁇ X ⁇ denotes information that is not relevant
- decimal numbers under diagrams indicate an offset, in bytes, from the beginning of a message to the start of the field
- a "node” is one of possibly multiple systems which are tightly connected in a Local Area Network (LAN) in one location and a "site” is either a single node or a multi-node (LAN) which is part of a loosely coupled network of systems in different geographical locations
- LAN Local Area Network
- each digit occupies 4 bits; the first digit resides in the 4 least significant bits of the first byte, the second digit in the 4 most significant bits, the third digit in the 4 least significant bits of the second byte, and so forth. If the address consists of an odd number of digits, then the last byte looks like: llllnnn, where nnnn is the last digit. If the address consists of an even number of digits, then the last byte is hexadecimal FF.
- the first letter uses the 5 least significant bits, the second letter the next 5 bits, the third letter the next 5 bits, and the remaining bit (the most significant bit in the 2 bytes) is set to zero. Then we continue with the second 2 bytes, and so forth. When all letters have been encoded, then the remaining bits in the last 2 bytes are set to 1.
- Site Num Sending site number. Currently a value between one (1) and fifty (50)
- Node Num Sending node number; currently a value between one (1) and eight (8).
- Site Num Receiving site number; currently a value between one (1) and fifty (50)
- Node Num Receiving node number; currently a value between one (1) and eight (8).
- Msg Code This indicates the type of voice message being delivered from sender to recipient. Currently used values are:
- Format is 000edcba where ⁇ a ⁇ is the least significant bit. Each one of the bits is one (1) if the corresponding option was requested by the sender of the message; otherwise it is zero (0)
- ⁇ b ⁇ This is a forwarded message.
- ⁇ c ⁇ This is a private message (may not be forwarded by recipient)
- Urgent delivery is being requested message should be placed at the front of the queue of incoming messages in the recipient's mailbox
- VoiceID Unique identification code for each recorded voice file. Each is 4 bytes long.
- Sender Name Disposition Informs the sending site about disposition of received alphabetic name of message sender. Possible values are:
- “Stop” response (5 bytes long): ##STR5## Status Code: May be zero (0) meaning voice file was received without errors and message has been delivered to recipient; or three (3), four (4), six (6), eight (8), or ten (10), with same meanings as defined for "Record” response.
Abstract
Description
Claims (6)
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/680,952 US5274696A (en) | 1991-04-05 | 1991-04-05 | Protocol for transmitting messages in a network |
EP19920105367 EP0507226A3 (en) | 1991-04-05 | 1992-03-27 | Protocol for transmitting messages in a network |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US07/680,952 US5274696A (en) | 1991-04-05 | 1991-04-05 | Protocol for transmitting messages in a network |
Publications (1)
Publication Number | Publication Date |
---|---|
US5274696A true US5274696A (en) | 1993-12-28 |
Family
ID=24733180
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US07/680,952 Expired - Lifetime US5274696A (en) | 1991-04-05 | 1991-04-05 | Protocol for transmitting messages in a network |
Country Status (2)
Country | Link |
---|---|
US (1) | US5274696A (en) |
EP (1) | EP0507226A3 (en) |
Cited By (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1995015046A1 (en) * | 1993-11-26 | 1995-06-01 | Octel Communications Corporation | Exchange of information between interconnected voicemail systems |
US5434914A (en) * | 1992-12-31 | 1995-07-18 | At&T Corp. | Name translation in communications networks |
US5479498A (en) * | 1990-12-11 | 1995-12-26 | Octel Communications Corporation | Digital line card having universal port for upgrading electronic messaging system |
US5509061A (en) * | 1993-05-28 | 1996-04-16 | Siemens Aktiengesellschaft | Method for storing messages in networked message memory units |
US5519766A (en) * | 1992-09-18 | 1996-05-21 | Boston Technology, Inc. | Message length reporting system for telephone communication system |
US5530739A (en) * | 1991-03-20 | 1996-06-25 | Fujitsu Limited | Mail center management system |
US5608783A (en) * | 1993-07-15 | 1997-03-04 | Siemens Business Communication Systems, Inc. | Methods and apparatus for coordinating and controlling the operation of AMIS analog voice messaging system networks in response to message delivery session status signals |
US5625675A (en) * | 1994-07-14 | 1997-04-29 | Hitachi, Ltd. | Voice mail communication system |
US5631948A (en) * | 1994-12-05 | 1997-05-20 | Bell Atlantic Network Services, Inc. | Voice mail communication with call blocking |
US5661782A (en) * | 1994-12-05 | 1997-08-26 | Bell Atlantic Network Services, Inc. | Voice mail communication with call blocking |
US5675631A (en) * | 1993-05-11 | 1997-10-07 | Siemens Business Communication Systems, Inc. | Methods for providing enhanced addressing capability in voice messaging system networks |
US5680442A (en) * | 1994-12-05 | 1997-10-21 | Bell Atlantic Network Services, Inc. | Voice mail communication with call blocking |
US5684862A (en) * | 1995-05-24 | 1997-11-04 | Advance Systems Development Company, L.C. | Telephone voice message store and forward method |
US5687220A (en) * | 1994-10-31 | 1997-11-11 | Worldvoice Inc. | Telephonic voice message transmission control method |
US5787153A (en) * | 1995-09-29 | 1998-07-28 | Unisys Corporation | System for incremental redistribution of telephony applications computing workload |
US5812639A (en) * | 1994-12-05 | 1998-09-22 | Bell Atlantic Network Services, Inc. | Message communication via common signaling channel |
US5963618A (en) * | 1996-04-26 | 1999-10-05 | International Business Machines Corp. | Voice processing system |
US6125113A (en) * | 1996-04-18 | 2000-09-26 | Bell Atlantic Network Services, Inc. | Internet telephone service |
US6173043B1 (en) | 1994-10-31 | 2001-01-09 | Worldvoice Licensing, Inc. | Telephonic voice message transmission control method |
US6201857B1 (en) * | 1995-03-20 | 2001-03-13 | Six Sigma, Ltd. | Combination telephone and voice-mail transceiver |
US6208717B1 (en) | 1997-03-03 | 2001-03-27 | Unisys Corporation | Method for migrating or altering a messaging system |
US6215858B1 (en) | 1994-12-05 | 2001-04-10 | Bell Atlantic Network Services, Inc. | Analog terminal internet access |
US6285745B1 (en) | 1994-12-05 | 2001-09-04 | Bell Atlantic Network Services, Inc. | Analog terminal internet access |
WO2001095156A1 (en) * | 2000-06-06 | 2001-12-13 | Pitney Bowes Inc. | Messaging system having recipient profiling |
US6438218B1 (en) | 1996-04-18 | 2002-08-20 | Robert D. Farris | Internet telephone service |
US6522727B1 (en) | 1995-03-08 | 2003-02-18 | Comverse, Inc. | System for archiving voice mail messages |
US6590877B1 (en) * | 1997-12-24 | 2003-07-08 | Casio Computer Co., Ltd. | Data transmission device |
US6647277B1 (en) * | 1994-02-24 | 2003-11-11 | Gte Wireless Service Corporation | Radiotelephone operating method with connected NPA dialing analysis |
US6681001B1 (en) | 1996-02-14 | 2004-01-20 | Nortel Networks Limited | Computer integrated telecommunications systems and methods |
US6690773B1 (en) | 2000-06-06 | 2004-02-10 | Pitney Bowes Inc. | Recipient control over aspects of incoming messages |
US6810113B1 (en) * | 1999-02-26 | 2004-10-26 | Bellsouth Intellectual Property Corporation | Methods and systems to make spoken name data available |
US20050111632A1 (en) * | 2003-11-21 | 2005-05-26 | Mci, Inc. | Systems and methods for providing portable voicemail services |
US7058586B1 (en) | 2000-06-06 | 2006-06-06 | Pitney Bowes Inc. | Information delivery system for providing senders with a recipient's messaging preferences |
US20080263221A1 (en) * | 2007-04-17 | 2008-10-23 | Bea Systems, Inc. | System and method for store-and-forward for highly available message production |
US7546305B2 (en) * | 2001-04-13 | 2009-06-09 | Oracle International Corporation | File archival |
US7664097B2 (en) | 1996-04-18 | 2010-02-16 | Verizon Services Corp. | Telephone service via networking |
US7813332B1 (en) | 1997-03-19 | 2010-10-12 | Verizon Services Corp. | Voice call alternative routing through PSTN and internet networks |
US7817619B1 (en) | 1996-12-18 | 2010-10-19 | Verizon Services Corp. | Internet long distance telephone service |
US7830860B2 (en) | 1997-03-11 | 2010-11-09 | Verizon Services Corp. | Packet data network voice call quality monitoring |
US7948968B2 (en) | 1997-09-16 | 2011-05-24 | Verizon Communications Inc. | Network session management |
US8379531B2 (en) | 1996-04-18 | 2013-02-19 | Verizon Services Corp. | Telephony communication via varied redundant networks |
US8938062B2 (en) | 1995-12-11 | 2015-01-20 | Comcast Ip Holdings I, Llc | Method for accessing service resource items that are for use in a telecommunications system |
US9191505B2 (en) | 2009-05-28 | 2015-11-17 | Comcast Cable Communications, Llc | Stateful home phone service |
US9264546B2 (en) * | 1996-11-15 | 2016-02-16 | Rpx Corporation | Voice message transmission and playback |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6005922A (en) * | 1996-11-12 | 1999-12-21 | Nortel Networks Corporation | Voice mail system and method of inter-voice mail system communication |
WO2000059195A1 (en) * | 1999-03-25 | 2000-10-05 | Glenayre Electronics, Inc. | Spoken name confirmation in a networked voice mail processing system |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4790003A (en) * | 1987-04-27 | 1988-12-06 | American Telephone And Telegraph Company, At&T Information Systems | Message service system network |
US4933967A (en) * | 1989-06-01 | 1990-06-12 | At&T Company | Automatically-effected move of a subscriber between electronic message service systems in a network |
US5029200A (en) * | 1989-05-02 | 1991-07-02 | At&T Bell Laboratories | Voice message system using synthetic speech |
US5113430A (en) * | 1990-10-01 | 1992-05-12 | United States Advanced Network, Inc. | Enhanced wide area audio response network |
Family Cites Families (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4580016A (en) * | 1984-09-24 | 1986-04-01 | Vmx, Inc. | Method and apparatus for checking the integrity of a communications channel in a voice store and forward system |
-
1991
- 1991-04-05 US US07/680,952 patent/US5274696A/en not_active Expired - Lifetime
-
1992
- 1992-03-27 EP EP19920105367 patent/EP0507226A3/en not_active Withdrawn
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4790003A (en) * | 1987-04-27 | 1988-12-06 | American Telephone And Telegraph Company, At&T Information Systems | Message service system network |
US5029200A (en) * | 1989-05-02 | 1991-07-02 | At&T Bell Laboratories | Voice message system using synthetic speech |
US4933967A (en) * | 1989-06-01 | 1990-06-12 | At&T Company | Automatically-effected move of a subscriber between electronic message service systems in a network |
US5113430A (en) * | 1990-10-01 | 1992-05-12 | United States Advanced Network, Inc. | Enhanced wide area audio response network |
Cited By (61)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5479498A (en) * | 1990-12-11 | 1995-12-26 | Octel Communications Corporation | Digital line card having universal port for upgrading electronic messaging system |
US5530739A (en) * | 1991-03-20 | 1996-06-25 | Fujitsu Limited | Mail center management system |
US5519766A (en) * | 1992-09-18 | 1996-05-21 | Boston Technology, Inc. | Message length reporting system for telephone communication system |
US5434914A (en) * | 1992-12-31 | 1995-07-18 | At&T Corp. | Name translation in communications networks |
US5764733A (en) * | 1993-05-11 | 1998-06-09 | Siemens Business Communication Systems, Inc. | Apparatus for providing enhanced addressing capability in voice messaging system networks |
US5675631A (en) * | 1993-05-11 | 1997-10-07 | Siemens Business Communication Systems, Inc. | Methods for providing enhanced addressing capability in voice messaging system networks |
US5509061A (en) * | 1993-05-28 | 1996-04-16 | Siemens Aktiengesellschaft | Method for storing messages in networked message memory units |
US5608783A (en) * | 1993-07-15 | 1997-03-04 | Siemens Business Communication Systems, Inc. | Methods and apparatus for coordinating and controlling the operation of AMIS analog voice messaging system networks in response to message delivery session status signals |
US5572578A (en) * | 1993-11-26 | 1996-11-05 | Lin; Frank C. H. | Exchange of information between interconnected voice mail systems |
WO1995015046A1 (en) * | 1993-11-26 | 1995-06-01 | Octel Communications Corporation | Exchange of information between interconnected voicemail systems |
US6647277B1 (en) * | 1994-02-24 | 2003-11-11 | Gte Wireless Service Corporation | Radiotelephone operating method with connected NPA dialing analysis |
US5625675A (en) * | 1994-07-14 | 1997-04-29 | Hitachi, Ltd. | Voice mail communication system |
US5687220A (en) * | 1994-10-31 | 1997-11-11 | Worldvoice Inc. | Telephonic voice message transmission control method |
US8433043B2 (en) | 1994-10-31 | 2013-04-30 | Worldvoice Licensing, Inc. | Telephonic voice message transmission control method |
US6697459B2 (en) | 1994-10-31 | 2004-02-24 | Worldvoice Licensing, Inc. | Telephonic voice message transmission control method |
US20040228458A1 (en) * | 1994-10-31 | 2004-11-18 | Finnigan Paul F. | Telephonic voice message transmission control method |
US7221744B2 (en) | 1994-10-31 | 2007-05-22 | Worldvoice Licensing, Inc. | Telephonic voice message transmission control method |
US6173043B1 (en) | 1994-10-31 | 2001-01-09 | Worldvoice Licensing, Inc. | Telephonic voice message transmission control method |
US5812639A (en) * | 1994-12-05 | 1998-09-22 | Bell Atlantic Network Services, Inc. | Message communication via common signaling channel |
US6215858B1 (en) | 1994-12-05 | 2001-04-10 | Bell Atlantic Network Services, Inc. | Analog terminal internet access |
US6285745B1 (en) | 1994-12-05 | 2001-09-04 | Bell Atlantic Network Services, Inc. | Analog terminal internet access |
US5661782A (en) * | 1994-12-05 | 1997-08-26 | Bell Atlantic Network Services, Inc. | Voice mail communication with call blocking |
US5680442A (en) * | 1994-12-05 | 1997-10-21 | Bell Atlantic Network Services, Inc. | Voice mail communication with call blocking |
US5631948A (en) * | 1994-12-05 | 1997-05-20 | Bell Atlantic Network Services, Inc. | Voice mail communication with call blocking |
US6522727B1 (en) | 1995-03-08 | 2003-02-18 | Comverse, Inc. | System for archiving voice mail messages |
US6201857B1 (en) * | 1995-03-20 | 2001-03-13 | Six Sigma, Ltd. | Combination telephone and voice-mail transceiver |
US5684862A (en) * | 1995-05-24 | 1997-11-04 | Advance Systems Development Company, L.C. | Telephone voice message store and forward method |
US5787153A (en) * | 1995-09-29 | 1998-07-28 | Unisys Corporation | System for incremental redistribution of telephony applications computing workload |
US8938062B2 (en) | 1995-12-11 | 2015-01-20 | Comcast Ip Holdings I, Llc | Method for accessing service resource items that are for use in a telecommunications system |
US6681001B1 (en) | 1996-02-14 | 2004-01-20 | Nortel Networks Limited | Computer integrated telecommunications systems and methods |
US6438218B1 (en) | 1996-04-18 | 2002-08-20 | Robert D. Farris | Internet telephone service |
US7664097B2 (en) | 1996-04-18 | 2010-02-16 | Verizon Services Corp. | Telephone service via networking |
US6125113A (en) * | 1996-04-18 | 2000-09-26 | Bell Atlantic Network Services, Inc. | Internet telephone service |
US8379531B2 (en) | 1996-04-18 | 2013-02-19 | Verizon Services Corp. | Telephony communication via varied redundant networks |
US5963618A (en) * | 1996-04-26 | 1999-10-05 | International Business Machines Corp. | Voice processing system |
US8553681B2 (en) | 1996-06-26 | 2013-10-08 | Verizon Services Corp. | Telephone service via packet-switched networking |
US9264546B2 (en) * | 1996-11-15 | 2016-02-16 | Rpx Corporation | Voice message transmission and playback |
US7817619B1 (en) | 1996-12-18 | 2010-10-19 | Verizon Services Corp. | Internet long distance telephone service |
US6208717B1 (en) | 1997-03-03 | 2001-03-27 | Unisys Corporation | Method for migrating or altering a messaging system |
US7830860B2 (en) | 1997-03-11 | 2010-11-09 | Verizon Services Corp. | Packet data network voice call quality monitoring |
US7813332B1 (en) | 1997-03-19 | 2010-10-12 | Verizon Services Corp. | Voice call alternative routing through PSTN and internet networks |
US7948968B2 (en) | 1997-09-16 | 2011-05-24 | Verizon Communications Inc. | Network session management |
US9215254B1 (en) | 1997-09-16 | 2015-12-15 | Verizon Patent And Licensing Inc. | Network session management for telephony over hybrid networks |
US8976782B1 (en) | 1997-09-16 | 2015-03-10 | Verizon Patent And Licensing Inc. | Network session management for telephony over hybrid networks |
US6590877B1 (en) * | 1997-12-24 | 2003-07-08 | Casio Computer Co., Ltd. | Data transmission device |
US6810113B1 (en) * | 1999-02-26 | 2004-10-26 | Bellsouth Intellectual Property Corporation | Methods and systems to make spoken name data available |
US7058586B1 (en) | 2000-06-06 | 2006-06-06 | Pitney Bowes Inc. | Information delivery system for providing senders with a recipient's messaging preferences |
US7412401B2 (en) | 2000-06-06 | 2008-08-12 | Pitney Bowes Inc. | Messaging system having recipient profiling |
US20060247966A1 (en) * | 2000-06-06 | 2006-11-02 | Pitney Bowes Inc. | Messaging system having recipient profiling |
US20100306332A1 (en) * | 2000-06-06 | 2010-12-02 | Pitney Bowes Inc. | Information delivery system for providing senders with a recipient's messaging preferences |
US20060229934A1 (en) * | 2000-06-06 | 2006-10-12 | Pitney Bowes Inc. | Information delivery system for providing senders with a recipient's messaging preferences |
US7072845B1 (en) | 2000-06-06 | 2006-07-04 | Pitney Bowes Inc. | Messaging system having recipient profiling |
US8630883B2 (en) | 2000-06-06 | 2014-01-14 | Pitney Bowes Inc. | Information delivery system for providing senders with a recipient's messaging preferences |
WO2001095156A1 (en) * | 2000-06-06 | 2001-12-13 | Pitney Bowes Inc. | Messaging system having recipient profiling |
US6690773B1 (en) | 2000-06-06 | 2004-02-10 | Pitney Bowes Inc. | Recipient control over aspects of incoming messages |
US7546305B2 (en) * | 2001-04-13 | 2009-06-09 | Oracle International Corporation | File archival |
US7177406B2 (en) * | 2003-11-21 | 2007-02-13 | Mci, Llc | Systems and methods for providing portable voicemail services |
US20050111632A1 (en) * | 2003-11-21 | 2005-05-26 | Mci, Inc. | Systems and methods for providing portable voicemail services |
US8275905B2 (en) * | 2007-04-17 | 2012-09-25 | Oracle International Corporation | System and method for store-and-forward for highly available message production |
US20080263221A1 (en) * | 2007-04-17 | 2008-10-23 | Bea Systems, Inc. | System and method for store-and-forward for highly available message production |
US9191505B2 (en) | 2009-05-28 | 2015-11-17 | Comcast Cable Communications, Llc | Stateful home phone service |
Also Published As
Publication number | Publication date |
---|---|
EP0507226A3 (en) | 1993-08-25 |
EP0507226A2 (en) | 1992-10-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5274696A (en) | Protocol for transmitting messages in a network | |
EP0311647B1 (en) | Message service system network | |
EP0210221B1 (en) | Integrated message service system | |
RU2120701C1 (en) | Method which provides users with possibility of real-time update of call route choosing functions | |
US5631950A (en) | Transmission of data message during silent intervals of ringing for selection of terminal equipment | |
EP0255325B1 (en) | Call transfer between a message service system and a telephone switching system | |
CA1244921A (en) | Integrated message service system | |
US4755985A (en) | Method and apparatus for facilitating moves and changes in a communication system | |
CN1128477A (en) | Personal mobile communication system | |
US20050238003A1 (en) | Method and telecommunication system for transmission of a message | |
EP0698325B1 (en) | Telemetry arrangement | |
JPS61274552A (en) | Communication equipment | |
JPS58182343A (en) | Informing system of network information | |
JPS62112453A (en) | System for connecting integrated mail equipment | |
KR100710937B1 (en) | Continuity testing in communication networks | |
JP2709459B2 (en) | Callee response signal transmission method | |
JPS60157363A (en) | Exchange control system | |
JP2754816B2 (en) | Facsimile dialing method | |
JP3031960B2 (en) | Facsimile communication method | |
JP2889370B2 (en) | ISDN communication network system | |
KR101303380B1 (en) | System and method for providing chatting service in public switched telephone network | |
JPS62195958A (en) | Automatic answering recording system | |
JPS63166356A (en) | Dial-in connection facsimile call system | |
JPH08181792A (en) | Line connection time control system for interest index board system | |
JPH06132874A (en) | Message communication system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ROLM SYSTEMS, 4900 OLD IRONSIDES DR., SANTA CLARA, Free format text: ASSIGNMENT OF ASSIGNORS INTEREST.;ASSIGNOR:PERELMAN, ROBERTO;REEL/FRAME:005675/0260 Effective date: 19910401 |
|
AS | Assignment |
Owner name: ROLM COMPANY, CALIFORNIA Free format text: CHANGE OF NAME;ASSIGNOR:ROLM SYSTEMS;REEL/FRAME:006617/0272 Effective date: 19920928 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REMI | Maintenance fee reminder mailed | ||
FEPP | Fee payment procedure |
Free format text: PETITION RELATED TO MAINTENANCE FEES FILED (ORIGINAL EVENT CODE: PMFP); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PETITION RELATED TO MAINTENANCE FEES GRANTED (ORIGINAL EVENT CODE: PMFG); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REIN | Reinstatement after maintenance fee payment confirmed | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
SULP | Surcharge for late payment | ||
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 19971231 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
PRDP | Patent reinstated due to the acceptance of a late maintenance fee |
Effective date: 19980904 |
|
REFU | Refund |
Free format text: REFUND - PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: R1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FPAY | Fee payment |
Year of fee payment: 12 Year of fee payment: 8 |
|
AS | Assignment |
Owner name: ROLM COMPANY, INC.,CALIFORNIA Free format text: CERTIFICATE OF INCORPORATION;ASSIGNOR:ROLM COMPANY;REEL/FRAME:024218/0818 Effective date: 19940829 |
|
AS | Assignment |
Owner name: SIEMENS ROLM COMMUNICATIONS INC.,CALIFORNIA Free format text: CERTIFICATE OF AMENDMENT TO CERTIFICATE OF INCORPORATION;ASSIGNOR:ROLM COMPANY, INC.;REEL/FRAME:024233/0593 Effective date: 19940930 |
|
AS | Assignment |
Owner name: SIEMENS BUSINESS COMMUNICATION SYSTEMS, INC.,CALIF Free format text: CHANGE OF NAME;ASSIGNOR:SIEMENS ROLM COMMUNICATIONS INC.;REEL/FRAME:024244/0257 Effective date: 19961001 |
|
AS | Assignment |
Owner name: SIEMENS INFORMATION AND COMMUNICATION NETWORKS, IN Free format text: MERGER;ASSIGNOR:SIEMENS BUSINESS COMMUNICATION SYSTEMS, INC.;REEL/FRAME:024244/0679 Effective date: 19980930 |
|
AS | Assignment |
Owner name: SIEMENS COMMUNICATIONS, INC.,FLORIDA Free format text: MERGER;ASSIGNOR:SIEMENS INFORMATION AND COMMUNICATION NETWORKS, INC.;REEL/FRAME:024263/0817 Effective date: 20040922 Owner name: SIEMENS COMMUNICATIONS, INC., FLORIDA Free format text: MERGER;ASSIGNOR:SIEMENS INFORMATION AND COMMUNICATION NETWORKS, INC.;REEL/FRAME:024263/0817 Effective date: 20040922 |
|
AS | Assignment |
Owner name: SIEMENS ENTERPRISE COMMUNICATIONS, INC.,FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIEMENS COMMUNICATIONS, INC.;REEL/FRAME:024294/0040 Effective date: 20100304 Owner name: SIEMENS ENTERPRISE COMMUNICATIONS, INC., FLORIDA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:SIEMENS COMMUNICATIONS, INC.;REEL/FRAME:024294/0040 Effective date: 20100304 |
|
AS | Assignment |
Owner name: WELLS FARGO TRUST CORPORATION LIMITED, AS SECURITY Free format text: GRANT OF SECURITY INTEREST IN U.S. PATENTS;ASSIGNOR:SIEMENS ENTERPRISE COMMUNICATIONS, INC.;REEL/FRAME:025339/0904 Effective date: 20101109 |
|
AS | Assignment |
Owner name: UNIFY INC. (F/K/A SIEMENS ENTERPRISE COMMUNICATION Free format text: TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS;ASSIGNOR:WELLS FARGO TRUST CORPORATION LIMITED, AS SECURITY AGENT;REEL/FRAME:037564/0703 Effective date: 20160120 |
|
AS | Assignment |
Owner name: UNIFY INC., FLORIDA Free format text: RELEASE BY SECURED PARTY;ASSIGNOR:WELLS FARGO TRUST CORPORATION LIMITED;REEL/FRAME:037661/0781 Effective date: 20160120 |