US20010011303A1 - System and method for managing multimedia messaging platforms - Google Patents
System and method for managing multimedia messaging platforms Download PDFInfo
- Publication number
- US20010011303A1 US20010011303A1 US08/944,668 US94466897A US2001011303A1 US 20010011303 A1 US20010011303 A1 US 20010011303A1 US 94466897 A US94466897 A US 94466897A US 2001011303 A1 US2001011303 A1 US 2001011303A1
- Authority
- US
- United States
- Prior art keywords
- messaging
- platform
- messaging platform
- master
- network
- 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.)
- Granted
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/5307—Centralised arrangements for recording incoming messages, i.e. mailbox systems for recording messages comprising any combination of audio and non-audio components
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/06—Message adaptation to terminal or network requirements
- H04L51/066—Format adaptation, e.g. format conversion or compression
-
- 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
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N1/00—Scanning, transmission or reproduction of documents or the like, e.g. facsimile transmission; Details thereof
- H04N1/00127—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture
- H04N1/00204—Connection or combination of a still picture apparatus with another apparatus, e.g. for storage, processing or transmission of still picture signals or of information associated with a still picture with a digital computer or a digital computer system, e.g. an internet server
- H04N1/00209—Transmitting or receiving image data, e.g. facsimile data, via a computer, e.g. using e-mail, a computer network, the internet, I-fax
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
- H04L69/08—Protocols for interworking; Protocol conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M2201/00—Electronic components, circuits, software, systems or apparatus used in telephone systems
- H04M2201/60—Medium conversion
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/0024—Services and arrangements where telephone services are combined with data services
- H04M7/0051—Services and arrangements where telephone services are combined with data services where the data service is a multimedia messaging service
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
- H04N2201/0008—Connection or combination of a still picture apparatus with another apparatus
- H04N2201/0065—Converting image data to a format usable by the connected apparatus or vice versa
- H04N2201/0067—Converting to still picture data
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N2201/00—Indexing scheme relating to scanning, transmission or reproduction of documents or the like, and to details thereof
- H04N2201/0008—Connection or combination of a still picture apparatus with another apparatus
- H04N2201/0065—Converting image data to a format usable by the connected apparatus or vice versa
- H04N2201/0068—Converting from still picture data
Definitions
- This invention relates to the management of messaging platforms that are interconnected to form a wide-area network.
- a messaging system as shown in U.S. Pat. No. 5,568,540 to Greco et. al. enables a user to receive messages having a voice mail format either through a telephone or through a personal computer (“PC”) coupled to a local area network (LAN). It also provides a graphical user interface (“GUI”) on the PC to select which voice mail messages to receive and in what order.
- GUI graphical user interface
- the messaging system in Greco is a stand-alone system and thus, does not provide the advantages of linking to other similar messaging systems or of using interconnected messaging systems to provide distributed messaging.
- the present invention also provides a cost tracking feature when delivering messages between messaging platforms that are owned by different entities. This avoids the need for use agreements between messaging platform owners and owners of networks which are connected to the messaging platforms.
- the cost for each network message delivery is measured in tokens.
- Each messaging platform on the messaging network has a token pool.
- Each owner of a messaging platform is charged for the cost of the tokens.
- the originating messaging platform debits a selected number of tokens from its token pool, while each time an inbound network message delivery occurs, a selected number of tokens are credited to the token pool held by a target messaging platform.
- FIG. 1 is a schematic block diagram of a messaging management system in a presently preferred embodiment of the present invention.
- FIG. 2A is a block diagram of a global routing table in accordance with a preferred embodiment of the present invention.
- FIG. 2B is a block diagram of a local area routing table in accordance with a preferred embodiment of the present invention.
- FIG. 3 is a block diagram showing the addition of a messaging platform to the messaging network in accordance with a preferred embodiment of the present invention.
- FIG. 4 is a flow chart of the steps taken by a master platform when monitoring messaging platforms on the messaging network in accordance with a preferred embodiment of the present invention.
- FIG. 6B is a block diagram showing the activation of a messaging platform in accordance with a preferred embodiment of the present invention.
- FIG. 7 is a schematic block diagram of a messaging management system having a post office feature in accordance with a preferred embodiment of the present invention.
- FIG. 8 is a block diagram showing the delivery of information from an information source to a mailbox corresponding to a subscriber in accordance with a preferred embodiment of the present invention.
- the present invention may be used with co-pending U.S. patent application Ser. No. 08/853,290 filed May 9, 1997, entitled, “APPARATUS AND METHOD FOR PROVIDING MULTIMEDIA MESSAGING BETWEEN DISPARATE MESSAGING PLATFORMS,” hereinafter referred to as the (“multimedia messaging invention”).
- multimedia messaging invention The complete disclosure of the foregoing patent application is hereby incorporated herein by reference as if set forth fully herein.
- a messaging network 10 enables a user 12 to send or receive a message to or from another user 14 using the multimedia services provided by a messaging platform 16 connected to messaging network 10 .
- Messaging network 10 uses a switched backbone 18 such as the Internet, enabling messaging platform 16 to send or receive multimedia messages with another messaging platform on messaging network 10 such as remote messaging platform 20 . This provides global messaging at very low cost.
- each messaging platform may also individually connect to local networks such as a public switch telephone network 22 , 24 , 26 (PSTN) which may be connected to messaging devices such as telephones 28 , 30 , 32 and/or fax machines 34 , 36 , 38 ; a private branch exchange 40 , 42 , 44 (PBX) which may also connect to a messaging device such as a telephone 46 , 48 , 50 ; or a privately administered LAN and/or WAN 52 , 54 , 56 which may connect to messaging devices that include a computer terminal 58 , 60 , 62 or personal computer 64 , 66 , 68 running a browser program.
- PSTN public switch telephone network 22 , 24 , 26
- PBX private branch exchange 40 , 42 , 44
- These networks
- the present invention provides a cost tracking scheme when delivering messages between messaging platforms that are owned by different entities. This avoids the need for complex use agreements between messaging platform owners and owners of networks which are connected to the messaging platforms.
- the messaging platforms on messaging network 10 are managed by at least one master platform 70 .
- Every master platform on the messaging network 10 contain a master global routing table and every messaging platform on the messaging network contains a global routing table.
- Master platform 70 maintains a master global routing table 72 for an assigned group of messaging platforms, such as messaging platforms 16 and 20 , by editing a messaging platform entry within master global routing table 72 that corresponds to a messaging platform having a status change.
- Master platform 70 maintains content consistency, through a microprocessor system running under program control or an equivalent device, between master global routing table 72 and global routing tables 74 and 76 so that master platform 70 and messaging platforms 16 and 20 each rely on the same messaging platform entries within the global routing tables.
- master platform 70 sends an UPDATE message to messaging platforms 16 and 20 , enabling messaging platforms 16 and 20 to update their global routing tables 74 and 76 through a microprocessor system running under program control or an equivalent device.
- the UPDATE message includes at least one messaging platform entry that was modified by master platform 70 .
- the messaging platform entry is used by messaging platforms 16 and 20 to update a corresponding entry in their global routing tables 74 and 76 , respectively.
- Host ID 84 is a unique identifier for every messaging platform added to the messaging network. Host ID 84 may further include additional identifiers such as a domain name 90 ; a name recording file 92 ; and/or a network address or equivalent 94 .
- Operational status 85 defines the operational state of a messaging platform as determined by the master platform assigned to the messaging platform. It is presently contemplated that operational status 85 has either an in-operation (ACTIVATED) or a non-operational (DEACTIVATED) state. Changing the state of operation status 85 is further discussed below.
- Operation schedule 86 defines the operation window for a messaging platform.
- Operation schedule 86 includes a daily operation period 96 and an hourly operation period 98 .
- Daily operation period 96 has a format that includes a start time and an end time in units of hours that are separated by a dash. For example, a daily operation period that starts from 8 AM and ends at 6 PM would be indicated as “08-18.” Similarly, a round-the-clock operation would be indicated as “00-23.”
- Hourly operation period 98 defines the hourly operation window for a messaging platform.
- Hourly operation period 98 has a format that includes a start time and an end time in units of minutes that are separated by a dash. For example, an hourly operation period 98 that starts every fifteen minutes beyond the hour and ends at every half-hour would be indicated as “15-30,” while full hourly operation would be indicated as “00-59.”
- Domain name 90 defines a unique network name for messaging platform that corresponds to the messaging platform entry. For a messaging platform that uses the Internet as its switched backbone, domain name 90 corresponds to a TCP/IP network address and complies with the convention for naming a host node, such as a messaging platform, on the Internet.
- permanent IP address field 87 contains a permanent IP address or similar network address.
- Area of operation 88 may be defined using a local network routing table 100 , which is a variable length table but could have any format that is suitable for storing a variable amount of information.
- the type of information held by local network routing table 100 is dependent on the type of local network connection that a particular messaging platform is capable of supporting besides a messaging network connection.
- a local network routing table that corresponds to that messaging platform through its messaging platform entry would include a list of telephone number prefix digits.
- the telephone numbers listed in local network routing table 100 enable an originating messaging platform to determine which messaging platform can provide service to those telephone numbers by cross-referencing a destination telephone number with the messaging platform entries in the originating platform's global routing table.
- Token pool 89 has an initial value that may vary according to the amount sought by an owner of each new messaging platform added. The use of token pool 89 in the present invention will be further described below.
- FIG. 2B shows a local network routing table 101 having prefix digits 102 which correspond to a list of telephone numbers.
- prefix digits 102 may include a country code 103 and area code 104 , or may further include an office digit code 106 to further define the range of numbers that can be called.
- Local network routing table 101 enables an originating messaging platform to determine which remote messaging platform is capable of delivering a user message at an area of operation.
- the originating messaging platform cross-references the user message address, which may be in the form of a telephone number, with every local network routing table contained in the messaging platform's global routing table.
- a fax originating from an originating messaging platform in Hong Kong may have a fax destination number having a country code of “1” and an area code of “510”.
- the originating platform cross-references the fax number with its local network routing table to determine which remote messaging platform on the messaging network can service that country and area code. More specifically, originating messaging platform can then determine which messaging platform entry to use in order to obtain delivery information such as the domain name of the remote messaging platform and its hours of operation.
- name recording file 92 contains a voice recording of the name of a messaging platform.
- Name recording file 92 may be in any suitable digitized file format such as a .WAV file or similar digitized audio file format.
- FIG. 3 is a process chart showing the addition of a messaging platform to the messaging network in accordance with a preferred embodiment of the present invention.
- the addition of a new messaging platform 122 on messaging network 10 begins by requesting an add operation from a system administrator 124 of master platform 70 .
- the add operation includes a registration process that requires system administrator 124 to receive registration information 126 pertaining to new messaging platform 122 .
- Registration information 126 includes a preferred name 128 , a permanent IP address 130 or an indication 132 whether new messaging platform 122 will have a dynamically assigned IP address, a domain name 134 (if any), and an initial token amount 136 to fill token pool 89 .
- Initial token amount 136 may vary among new messaging platforms added to messaging network 10 according to the amount sought by the owner of each new messaging platform. Initial token amount 136 held by a messaging platform at any given time may be replenished through a master platform upon request, as will be described in detail below.
- a local network routing table 138 and/or an operation schedule 140 may also be provided to system administrator 124 .
- system administrator 124 creates a new messaging platform entry 142 corresponding to new messaging platform 122 in master global routing table 72 .
- New messaging platform entry 142 includes registration information 126 and a unique node ID 144 .
- a name recording file 146 may also be created by system administrator 124 and included with new messaging platform entry 142 in master global routing table 72 , if the new messaging platform is intended for connection to a telephone network such as telephone network 26 .
- a system administrator 148 for new messaging platform 122 is provided configuration information 150 which includes assigned node ID 144 and an IP address 152 of master platform 70 .
- Configuration information 150 may also include a password 154 that master platform 70 will recognize as unique to new messaging platform 122 .
- system administrator 148 configures new messaging platform 122 to have configuration information 150 .
- new messaging platform 122 sends an installation request 156 which includes node ID 144 , and a password 154 if implemented, to master platform 70 .
- Master platform 70 will recognize node ID 144 as pertaining to new messaging platform 122 based on corresponding messaging platform entry 142 in master global routing table 72 and performs step 120 h.
- master platform 70 downloads a copy of master global routing table 72 to new messaging platform 122 .
- step 120 i global routing tables 74 and 76 for messaging platforms 16 and 20 on messaging network 10 are updated by master platform 70 to include a messaging entry corresponding to new messaging platform 122 .
- Master platform 70 sends an UPDATE message to messaging platforms 16 and 20 which trigger messaging platforms 16 and 20 to include the new messaging platform entry in their global routing tables 74 and 76 , respectively.
- a master platform monitors its assigned messaging platforms and updates its master global routing table in response to the monitoring function.
- a QUERY message includes a command type, a node ID, and password (if applicable) that corresponds to the sending messaging platform.
- Deactivation includes the following steps.
- master platform 70 which may be under software program control or equivalent means, is directed by master platform administrator 124 to update the entry corresponding to messaging platform 16 in master global routing table 72 to reflect a DEACTIVATED operational status.
- FIG. 6B is a block diagram showing the activation of a messaging platform in accordance with a preferred embodiment of the present invention.
- each messaging platform upon receiving the UPDATE message, updates their global routing tables at the entry corresponding to messaging platform 16 to reflect an in-operation status.
- deleting a messaging platform such as messaging platform 16 includes the following steps.
- the master platform updates the global routing tables of all messaging platforms that are to remain on the network (and which are assigned to the master platform) by sending a DELETE message to each of its assigned messaging platforms on messaging network 10 .
- a DELETE message includes at least one messaging platform entry that was deleted from master global routing table 72 by master platform 70 .
- the messaging platform entry is used by messaging platforms to determine which entry in their global routing tables to delete.
- each messaging platform updates their global routing tables by deleting the entry corresponding to messaging platform 16 using the messaging platform entry received from the DELETE message.
- every network message delivery which includes using: 1) a switched network which forms the backbone for messaging network 10 such as switched backbone 18 ; 2) a network which imposes an outside use fee such as telephone network 22 ; and 3) a destination messaging platform such as messaging platform 16 used to complete the messaging transaction, will have a delivery cost.
- a switched network which forms the backbone for messaging network 10 such as switched backbone 18 ; 2) a network which imposes an outside use fee such as telephone network 22 ; and 3) a destination messaging platform such as messaging platform 16 used to complete the messaging transaction.
- a delivery cost For example, an owner of destination messaging platform in San Francisco, Calif., may incur a telephone transmission charge for transmitting a fax originating from a messaging platform in Hong Kong, China to a recipient in San Jose, California.
- the present invention imposes a cost for each network message delivery.
- each messaging platform added to messaging network 10 begins with a token pool having an initial amount of tokens. Each owner of a messaging platform is charged for the cost of the tokens. Each time a network message delivery is initiated, the originating messaging platform debits a selected number of tokens from its token pool, while each time an inbound network message delivery occurs, a selected number of tokens are credited to the token pool held by a target messaging platform. Each messaging platform performs the debiting and crediting functions under software control or equivalent means.
- the master platform Upon a request for replenishment, the master platform sends an INFO message to the corresponding messaging platform which updates the token pool of that messaging platform. It is presently contemplated that an owner of a new messaging platform purchases an initial token pool amount at the time the new messaging platform is added to the network. Additional tokens may then be purchased for replenishing any depleted amounts.
- a messaging platform such as messaging platform 170 may have a dial-up connection 172 to messaging network 174 via its switched backbone such as the Internet 176 . Since dial-up connection 172 may not be continuous, messages sent between messaging platform 170 and Internet 176 may be delayed. For example, messaging platform 178 may send a delivery-confirmed status message 180 to messaging platform 170 to confirm delivery of a user message 182 sent from messaging platform 170 . If messaging platform 170 has a disconnected dial-up connection 172 , delivery-confirmed confirming status message 180 will not arrive until dial-up connection 172 is re-established, which would be attempted during the operational period defined for messaging platform 170 .
- master platform 184 When master platform 184 receives confirming message 180 from messaging platform 178 , it stores confirming message 180 in a memory store location 186 corresponding to messaging platform 170 (mailbox slot) and tags confirming message 180 for delivery the next time messaging platform 170 is scheduled to re-connect. Master platform 184 determines the appropriate time to deliver the reply message by referencing messaging platform entry 188 corresponding to messaging platform 170 in master global routing table 190 .
- a messaging platform having a dedicated connection receives status messages directly from the replying messaging platform such as messaging platform 178 in FIG. 7.
- Replying messaging platform 178 distinguishes between messaging platforms having a dedicated or dial-up connections by referencing global routing table 192 .
- messaging platform 204 contacts its assigned master platform such as master platform 184 by sending a SUBSCRIBE request to master platform 184 .
- master platform 184 requests service from information source 200 by providing service information 208 received from subscriber 205 .
- master platform 184 creates a storage location that corresponds to subscriber 205 in a memory store 186 for holding any information received from information source 200 that matches service information 208 entered by subscriber 205 in step 206 b .
- the SUBSCRIBE request includes a command type, a node ID corresponding to messaging platform 204 , a mailbox ID corresponding to subscriber 205 , and a password (if applicable).
- the subscribe request may include a command type that instructs master platform 184 to request that information source 200 provide the information sought in service information 208 that was chosen by subscriber 205 in step 206 b .
- step 206 h is performed.
- master platform stores any information received from source 200 in memory store 186 .
- Master platform 184 does not send the stored information to a corresponding subscriber's messaging platform 204 until master platform 184 determines that messaging platform 204 has an in-operation status.
- master platform 184 may refer to its master global routing table to find a messaging platform entry that defines the profile for messaging platform 204 to determine whether messaging platform 204 has an in-operation status based on the operation schedule listed in messaging platform entry.
- the present invention may use a master platform 212 dedicated solely for the handling messages originating from information sources outside the messaging network such as from information source 214 .
- Master platform 212 may be configured to receive information through any of its network interfaces such as through its switched backbone interface 176 or through an interface supporting a dedicated connection to information source 214 .
- step 206 i the information received by master platform 184 is received by messaging platform 204 which converts the information to have delivery format 210 prior to delivery.
- messaging platform 204 delivers the information to mailbox 202 , which corresponds to subscriber 205 , using delivery format 210 .
Abstract
Description
- This application is a continuation-in-part of co-pending U.S. patent application Ser. No. 08/853,290 filed May 9, 1997, entitled, “APPARATUS AND METHOD FOR PROVIDING MULTIMEDIA MESSAGING BETWEEN DISPARATE MESSAGING PLATFORMS.” The complete disclosure of the foregoing patent application is hereby incorporated herein by reference as if set forth fully herein.
- 1. Field of the Invention
- This invention relates to the management of messaging platforms that are interconnected to form a wide-area network.
- 2. Background
- A messaging system as shown in U.S. Pat. No. 5,568,540 to Greco et. al., enables a user to receive messages having a voice mail format either through a telephone or through a personal computer (“PC”) coupled to a local area network (LAN). It also provides a graphical user interface (“GUI”) on the PC to select which voice mail messages to receive and in what order. However, the messaging system in Greco is a stand-alone system and thus, does not provide the advantages of linking to other similar messaging systems or of using interconnected messaging systems to provide distributed messaging.
- Accordingly, it would be desirable to integrate messaging platforms distributed on a switchable communications backbone such as the Internet, or equivalent network such as a wide area corporate intranet, and connected to different area networks so as to provide global yet low cost messaging.
- Moreover, it would be desirable to monitor each messaging platform and administer the addition, deletion, and updating of a messaging platform in response to a status change to the messaging platform so that each messaging platform is aware of the status change.
- In addition, it would be desirable to minimize the complexity that would result if every independent owner of a messaging platform had to contract with every other independent owner of a messaging platform in order to deliver a message within a certain service area served by a messaging platform by imposing a cost tracking scheme on each messaging platform that uses the switched backbone to send a message to another messaging platform for delivery to the service area.
- Furthermore, it would be desirable to provide a feature that manages a status message destined for a messaging platform which does not have an active connection to the switched backbone so that the status message is promptly delivered to the messaging platform the next time it re-establishes a connection to the switched network and results in a message confirming delivery of the status message to the messaging platform.
- Last, it would be desirable to include an information delivery service that delivers a message from at least one source outside of the messaging network to a subscriber via the subscriber's messaging platform regardless of whether the messaging platform has a dedicated or dial-up connection.
- The present invention manages a messaging network having messaging platforms interconnecting through a switched backbone such as the Internet. Each messaging platform may be independently owned and may also connect to local networks that may be independently owned. A master platform maintains a master global routing table having a messaging platform profile for every messaging platform established on the messaging network. Each messaging platform holds a global routing table which includes a current version of the master global routing table. The master platform monitors each messaging platform on the messaging network and administers the addition, deletion, and updating of messaging platforms by modifying its master global routing table in the event the master platform encounters changes to the status of the messaging platforms. In the event that the master global routing table is updated, the global routing table held by each messaging platform is also updated, ensuring version consistency between the master global routing table and each of the global routing tables. This enables the master platform and each messaging platform to determine the operational status of another messaging platform.
- Also, since the messaging platforms may be independently owned and are designed to receive and deliver messages through a variety of networks that may impose surcharges, the present invention also provides a cost tracking feature when delivering messages between messaging platforms that are owned by different entities. This avoids the need for use agreements between messaging platform owners and owners of networks which are connected to the messaging platforms. The cost for each network message delivery is measured in tokens. Each messaging platform on the messaging network has a token pool. Each owner of a messaging platform is charged for the cost of the tokens. Each time a network message delivery is initiated, the originating messaging platform debits a selected number of tokens from its token pool, while each time an inbound network message delivery occurs, a selected number of tokens are credited to the token pool held by a target messaging platform.
- The present invention also includes a post office function that enables a master platform to receive and store a status message destined for a messaging platform which does not have an active connection to the messaging network or is in a non-operational state. The present invention also includes an information delivery service that delivers a message from at least one source outside of the messaging network to a subscriber via the subscriber's messaging platform regardless of whether the messaging platform has a dedicated or dial-up connection.
- FIG. 1 is a schematic block diagram of a messaging management system in a presently preferred embodiment of the present invention.
- FIG. 2A is a block diagram of a global routing table in accordance with a preferred embodiment of the present invention.
- FIG. 2B is a block diagram of a local area routing table in accordance with a preferred embodiment of the present invention.
- FIG. 3 is a block diagram showing the addition of a messaging platform to the messaging network in accordance with a preferred embodiment of the present invention.
- FIG. 4 is a flow chart of the steps taken by a master platform when monitoring messaging platforms on the messaging network in accordance with a preferred embodiment of the present invention.
- FIG. 5 is a flow chart of the steps taken by a messaging platform as part of the monitoring of the network by a master platform in accordance with a preferred embodiment of the present invention.
- FIG. 6A is a block diagram showing the deactivation of a messaging platform in accordance with a preferred embodiment of the present invention.
- FIG. 6B is a block diagram showing the activation of a messaging platform in accordance with a preferred embodiment of the present invention.
- FIG. 6C is a block diagram showing the deletion of a messaging platform in accordance with a preferred embodiment of the present invention.
- FIG. 7 is a schematic block diagram of a messaging management system having a post office feature in accordance with a preferred embodiment of the present invention.
- FIG. 8 is a block diagram showing the delivery of information from an information source to a mailbox corresponding to a subscriber in accordance with a preferred embodiment of the present invention.
- In the following description, a preferred embodiment of the invention is described with regard to preferred process steps and data structures. Those skilled in the art would recognize after perusal of this application that embodiments of the invention can be implemented using circuitry in a microprocessor adapted to the particular process steps and data structures, and that implementation of the process steps and data structures described herein would not require undue experimentation or further invention.
- The present invention may be used with co-pending U.S. patent application Ser. No. 08/853,290 filed May 9, 1997, entitled, “APPARATUS AND METHOD FOR PROVIDING MULTIMEDIA MESSAGING BETWEEN DISPARATE MESSAGING PLATFORMS,” hereinafter referred to as the (“multimedia messaging invention”). The complete disclosure of the foregoing patent application is hereby incorporated herein by reference as if set forth fully herein.
- To further enhance the description of the various features of the present invention, “Service Communication Platform,” Release 2.0, available from Carnel Connection, Inc. located at 41432 Christy Street, Fremont, Calif., 94538 is also incorporated herein by reference as if set forth fully herein.
- FIG. 1 is a schematic block diagram of a messaging management system in a presently preferred embodiment of the present invention.
- As seen in FIG. 1, a
messaging network 10 enables auser 12 to send or receive a message to or from another user 14 using the multimedia services provided by amessaging platform 16 connected tomessaging network 10.Messaging network 10 uses a switchedbackbone 18 such as the Internet, enablingmessaging platform 16 to send or receive multimedia messages with another messaging platform onmessaging network 10 such asremote messaging platform 20. This provides global messaging at very low cost. - Besides the switched
backbone 18, each messaging platform may also individually connect to local networks such as a publicswitch telephone network telephones fax machines private branch exchange telephone WAN computer terminal personal computer - The present invention manages
messaging network 10 by monitoring the current availability of each existing messaging platform and administering the addition, deletion, and updating of messaging platforms onmessaging network 10. The master platforms and messaging platforms described herewith contain a programmable control means such as a microprocessor system running under program control or an equivalent device to perform these functions. - Also, since the messaging platforms may be independently owned and are designed to receive and deliver messages through a variety of networks that may impose surcharges, the present invention provides a cost tracking scheme when delivering messages between messaging platforms that are owned by different entities. This avoids the need for complex use agreements between messaging platform owners and owners of networks which are connected to the messaging platforms.
- In accordance with a presently preferred embodiment of the present invention, the messaging platforms on
messaging network 10 are managed by at least onemaster platform 70. Every master platform on themessaging network 10 contain a master global routing table and every messaging platform on the messaging network contains a global routing table.Master platform 70 maintains a master global routing table 72 for an assigned group of messaging platforms, such asmessaging platforms Master platform 70 maintains content consistency, through a microprocessor system running under program control or an equivalent device, between master global routing table 72 and global routing tables 74 and 76 so thatmaster platform 70 andmessaging platforms - In response to an applicable event such as the status change discussed above,
master platform 70 sends an UPDATE message tomessaging platforms messaging platforms master platform 70. The messaging platform entry is used bymessaging platforms - FIG. 2A is a block diagram of a global routing table in accordance with a preferred embodiment of the present invention.
- A global routing table80 as used in the present invention contains a corresponding
messaging platform entry 82 for each messaging platform onmessaging network 10. Each messaging platform entry includes fields that may point to or include the following: ahost ID 84; anoperational status 85; anoperation schedule 86; a permanent Internet Protocol (IP) address 87 (if applicable); an area ofoperation 88, and atoken pool 89. -
Host ID 84 is a unique identifier for every messaging platform added to the messaging network.Host ID 84 may further include additional identifiers such as adomain name 90; a name recording file 92; and/or a network address or equivalent 94. -
Operational status 85 defines the operational state of a messaging platform as determined by the master platform assigned to the messaging platform. It is presently contemplated thatoperational status 85 has either an in-operation (ACTIVATED) or a non-operational (DEACTIVATED) state. Changing the state ofoperation status 85 is further discussed below. -
Operation schedule 86 defines the operation window for a messaging platform.Operation schedule 86 includes adaily operation period 96 and anhourly operation period 98.Daily operation period 96 has a format that includes a start time and an end time in units of hours that are separated by a dash. For example, a daily operation period that starts from 8 AM and ends at 6 PM would be indicated as “08-18.” Similarly, a round-the-clock operation would be indicated as “00-23.” -
Hourly operation period 98 defines the hourly operation window for a messaging platform.Hourly operation period 98 has a format that includes a start time and an end time in units of minutes that are separated by a dash. For example, anhourly operation period 98 that starts every fifteen minutes beyond the hour and ends at every half-hour would be indicated as “15-30,” while full hourly operation would be indicated as “00-59.” -
Domain name 90 defines a unique network name for messaging platform that corresponds to the messaging platform entry. For a messaging platform that uses the Internet as its switched backbone,domain name 90 corresponds to a TCP/IP network address and complies with the convention for naming a host node, such as a messaging platform, on the Internet. - In the event that the messaging platform entry corresponds to a messaging platform having a dedicated connection to the switched backbone, permanent
IP address field 87 contains a permanent IP address or similar network address. - Area of
operation 88 may be defined using a local network routing table 100, which is a variable length table but could have any format that is suitable for storing a variable amount of information. The type of information held by local network routing table 100 is dependent on the type of local network connection that a particular messaging platform is capable of supporting besides a messaging network connection. When a messaging platform is configured to also support a telephone network, a local network routing table that corresponds to that messaging platform through its messaging platform entry would include a list of telephone number prefix digits. The telephone numbers listed in local network routing table 100 enable an originating messaging platform to determine which messaging platform can provide service to those telephone numbers by cross-referencing a destination telephone number with the messaging platform entries in the originating platform's global routing table. -
Token pool 89 has an initial value that may vary according to the amount sought by an owner of each new messaging platform added. The use oftoken pool 89 in the present invention will be further described below. - FIG. 2B shows a local network routing table101 having
prefix digits 102 which correspond to a list of telephone numbers. As presently contemplated,prefix digits 102 may include acountry code 103 andarea code 104, or may further include anoffice digit code 106 to further define the range of numbers that can be called. - Local network routing table101 enables an originating messaging platform to determine which remote messaging platform is capable of delivering a user message at an area of operation. The originating messaging platform cross-references the user message address, which may be in the form of a telephone number, with every local network routing table contained in the messaging platform's global routing table.
- For example, a fax originating from an originating messaging platform in Hong Kong may have a fax destination number having a country code of “1” and an area code of “510”. The originating platform cross-references the fax number with its local network routing table to determine which remote messaging platform on the messaging network can service that country and area code. More specifically, originating messaging platform can then determine which messaging platform entry to use in order to obtain delivery information such as the domain name of the remote messaging platform and its hours of operation.
- Returning to FIG. 2A, name recording file92 contains a voice recording of the name of a messaging platform. Name recording file 92 may be in any suitable digitized file format such as a .WAV file or similar digitized audio file format.
-
Network address field 94 holds a permanent IP address, or an equivalent type of network address that is applicable to the type of switched backbone used, of a messaging platform if the messaging platform has a permanent connection to the messaging network. Otherwise, network address field contains an indication that the messaging platform corresponding to the messaging platform entry is configured for dialup connection to the messaging network. - Adding Messaging Platforms
- FIG. 3 is a process chart showing the addition of a messaging platform to the messaging network in accordance with a preferred embodiment of the present invention.
- Referring to FIGS.1-3, at
step 120 a the addition of anew messaging platform 122 onmessaging network 10 begins by requesting an add operation from a system administrator 124 ofmaster platform 70. Atstep 120 b, the add operation includes a registration process that requires system administrator 124 to receiveregistration information 126 pertaining tonew messaging platform 122.Registration information 126 includes apreferred name 128, a permanent IP address 130 or an indication 132 whethernew messaging platform 122 will have a dynamically assigned IP address, a domain name 134 (if any), and an initialtoken amount 136 to filltoken pool 89. - Initial
token amount 136 may vary among new messaging platforms added tomessaging network 10 according to the amount sought by the owner of each new messaging platform. Initialtoken amount 136 held by a messaging platform at any given time may be replenished through a master platform upon request, as will be described in detail below. - As additional sub-steps to step120 b, a local network routing table 138 and/or an
operation schedule 140 may also be provided to system administrator 124. - At
step 120 c, system administrator 124 creates a newmessaging platform entry 142 corresponding tonew messaging platform 122 in master global routing table 72. Newmessaging platform entry 142 includesregistration information 126 and aunique node ID 144. - As an additional sub-step in
step 120 c, aname recording file 146 may also be created by system administrator 124 and included with newmessaging platform entry 142 in master global routing table 72, if the new messaging platform is intended for connection to a telephone network such astelephone network 26. - At
step 120 d, once newmessage platform entry 142 has been created on master global routing table 72, a system administrator 148 fornew messaging platform 122 is providedconfiguration information 150 which includes assignednode ID 144 and anIP address 152 ofmaster platform 70.Configuration information 150 may also include apassword 154 thatmaster platform 70 will recognize as unique tonew messaging platform 122. - At
step 120 e, system administrator 148 configuresnew messaging platform 122 to haveconfiguration information 150. - At
step 120 f, in response to enteringconfiguration information 150,new messaging platform 122 establishes a connection withmaster platform 70 using masterplatform IP address 152, enablingmaster platform 70 to respond by providingnew messaging platform 122 with applicable information. - More specifically at
step 120 g,new messaging platform 122 sends aninstallation request 156 which includesnode ID 144, and apassword 154 if implemented, tomaster platform 70.Master platform 70 will recognizenode ID 144 as pertaining tonew messaging platform 122 based on correspondingmessaging platform entry 142 in master global routing table 72 and performs step 120 h. - At
step 120 h,master platform 70 downloads a copy of master global routing table 72 tonew messaging platform 122. - At step120 i, global routing tables 74 and 76 for
messaging platforms messaging network 10 are updated bymaster platform 70 to include a messaging entry corresponding tonew messaging platform 122.Master platform 70 sends an UPDATE message tomessaging platforms messaging platforms - Monitoring Messaging Platforms
- FIG. 4 is a flow chart of the steps taken by a master platform when monitoring messaging platforms on the messaging network in accordance with a preferred embodiment of the present invention.
- Through a microprocessor system running under program control or an equivalent device, a master platform monitors its assigned messaging platforms and updates its master global routing table in response to the monitoring function.
- At
step 160 a, a messaging platform sends a HELLO message to its assigned master platform at selected intervals over a given time schedule. For a messaging platform having a dedicated connection, the selected intervals may be at any selected interval such as every half-hour on the half-hour, 24 hours each day. This selected interval of 30 minutes may be varied and is not intended to limit the present invention in anyway. For a messaging platform having a dial-up connection to the switched backbone, the messaging platform only sends HELLO messages while having a messaging network connection and during the operation schedule defined by the messaging platform's daily and hourly operation periods. - As presently contemplated, a HELLO message includes a command type, node ID, and password (if applicable) that corresponds to the sending messaging platform. The HELLO message may also include additional information pertaining to the messaging platform such as its current token pool balance.
- At
step 160 b, if the HELLO message from the messaging platform is not received by its assigned master platform within an amount of time of the scheduled time (selected wait time) to receive the HELLO message, step 160 c is performed. - At
step 160 c, the master platform will send a QUERY message to the late messaging platform. It is presently contemplated that the selected wait time be no more than ten (10) minutes beyond the scheduled time to receive a HELLO message. - A QUERY message includes a command type, a node ID, and password (if applicable) that corresponds to the sending messaging platform.
- At
step 160 d, if the late messaging platform does not respond within the selected wait time,step 160 e is performed. Atstep 160 e, the master platform changes the status of the non-responding messaging platform to a non-operational status and alerts the master platform system administrator of the non-operational status of the non-responding messaging platform. In addition, the master platform returns to step 160 c and sends another QUERY message to the late messaging platform with a selected wait time. - If at
step 160 b, the assigned master platform receives a HELLO message from the messaging platform within the selected wait time, step 100 f is performed. At step 100 f, the assigned master platform replies with an acknowledge message (ACK). - FIG. 5 is a flow chart of the steps taken by a messaging platform as part of the monitoring of the network by a master platform in accordance with a preferred embodiment of the present invention.
- At
step 162 a, if the HELLO message, which was sent by the messaging platform, is not responded to with an ACK message by the messaging platform's assigned master platform within a selected wait time,step 162 b is performed. - At
step 162 b, the messaging platform sends another HELLO message. It is presently contemplated that the particular messaging platform has a selected wait time of 10 minutes before sending another HELLO message. The amount of wait time is not considered to be limiting in anyway but may be varied to response to the processing loads incurred by a given master and messaging platform so as to optimize system performance. - At
step 162 c, if the assigned master platform does not respond to the second HELLO message, step 162 d is performed. Atstep 162 d, the messaging platform may keep sending a HELLO message each time the wait time expires by returning to set 162 b. The messaging platform instep 162 d may also send an alert message to the particular messaging platform's system administrator. - Returning to step162 a, if the HELLO message is responded to with an ACK by the master platform within a selected wait time,
step 162 e is performed. Atstep 162 e, the messaging platform sends another HELLO message to the master platform according to a schedule defined for the messaging platform. - Similarly in
step 162 c, if the assigned master platform does respond to the second HELLO message within a selected wait time,step 160 e is performed so that the messaging platform sends another HELLO message according to a schedule defined for the messaging platform. - Activating/Deactivating a Messaging Platform
- FIG. 6A is a block diagram showing the deactivation of a messaging platform in accordance with a preferred embodiment of the present invention.
- Referring to FIGS. 1 and 6A, in the event that a messaging platform such as
messaging platform 16 has a non-operational status for any significant amount of time, such as one hour, master platform administrator 124 can choose to deactivatemessaging platform 16 frommessaging network 10. - Deactivation includes the following steps. At step164 a,
master platform 70, which may be under software program control or equivalent means, is directed by master platform administrator 124 to update the entry corresponding tomessaging platform 16 in master global routing table 72 to reflect a DEACTIVATED operational status. - At
step 164 b,master platform 70 sends an UPDATE message to each of its assigned messaging platforms onmessaging network 10. The UPDATE message includes the entry corresponding tomessaging platform 16 that reflects an DEACTIVATED operational status in master global routing table 72. - In an alternative embodiment of the present invention, through a microprocessor system running under program control or an equivalent device,
master platform 70 may be configured to update automatically the entry corresponding tomessaging platform 16 in master global routing table 72 to reflect a DEACTIVATED operational status when messaging platform does not respond as described above. This helps minimize the need for any intervening action by master platform administrator 124, if desired. - At step164 c, upon receiving the UPDATE message, each messaging platform updates their global routing tables at the entry corresponding to
messaging platform 16 to reflect a DEACTIVATED operational status. - FIG. 6B is a block diagram showing the activation of a messaging platform in accordance with a preferred embodiment of the present invention.
- Activating a messaging platform is similar to the steps outlined immediately above. At
step 166 a,master platform 70 updates the entry corresponding tomessaging platform 16 in master global routing table 72 to reflect an in-operation status, as shown in FIG. 6B. - At
step 166 b,master platform 70 also sends an UPDATE message to each of its assigned messaging platforms onmessaging network 10. The UPDATE message includes the entry corresponding tomessaging platform 16 that reflects an in-operation status in master global routing table 72. - At step166 c, upon receiving the UPDATE message, each messaging platform updates their global routing tables at the entry corresponding to
messaging platform 16 to reflect an in-operation status. - Deleting a Messaging Platform
- FIG. 6C is a block diagram showing the deletion of a messaging platform in accordance with a preferred embodiment of the present invention.
- As shown in FIGS. 1 and 6C, deleting a messaging platform such as
messaging platform 16 includes the following steps. - At
step 168 a,master platform 70 deletes the entry corresponding tomessaging platform 16 from master global routing table 72. - At
step 168 b, the master platform updates the global routing tables of all messaging platforms that are to remain on the network (and which are assigned to the master platform) by sending a DELETE message to each of its assigned messaging platforms onmessaging network 10. - As presently contemplated, a DELETE message includes at least one messaging platform entry that was deleted from master global routing table72 by
master platform 70. The messaging platform entry is used by messaging platforms to determine which entry in their global routing tables to delete. - At
step 168 c, each messaging platform updates their global routing tables by deleting the entry corresponding tomessaging platform 16 using the messaging platform entry received from the DELETE message. - Tokens
- Referring to FIG. 1, every network message delivery which includes using: 1) a switched network which forms the backbone for
messaging network 10 such as switchedbackbone 18; 2) a network which imposes an outside use fee such astelephone network 22; and 3) a destination messaging platform such asmessaging platform 16 used to complete the messaging transaction, will have a delivery cost. For example, an owner of destination messaging platform in San Francisco, Calif., may incur a telephone transmission charge for transmitting a fax originating from a messaging platform in Hong Kong, China to a recipient in San Jose, California. In order to minimize the complexity that would result if every independent owner of a messaging platform had to contract with every other independent owner of a messaging platform in order to deliver a message within a certain service area, the present invention imposes a cost for each network message delivery. - The cost for each network message delivery is measured in tokens. As described above, each messaging platform added to
messaging network 10 begins with a token pool having an initial amount of tokens. Each owner of a messaging platform is charged for the cost of the tokens. Each time a network message delivery is initiated, the originating messaging platform debits a selected number of tokens from its token pool, while each time an inbound network message delivery occurs, a selected number of tokens are credited to the token pool held by a target messaging platform. Each messaging platform performs the debiting and crediting functions under software control or equivalent means. - Replenishing Tokens
- If the entire token pool held by a messaging platform falls below a selected threshold amount such as when the token pool may soon be depleted or is depleted, the pool is replenished centrally by using its assigned master platform to provide additional tokens. Depletion of the entire pool of tokens for a given messaging platform ceases all network message deliveries by that messaging platform until its token pool is replenished. A microprocessor running under program control or equivalent device in the messaging platform determines whether it may request delivery of a user message via the messaging network. The token pool may be replenished by purchasing additional tokens through a request for replenishment to its assigned master platform or by gaining tokens from future inbound network message deliveries.
- Upon a request for replenishment, the master platform sends an INFO message to the corresponding messaging platform which updates the token pool of that messaging platform. It is presently contemplated that an owner of a new messaging platform purchases an initial token pool amount at the time the new messaging platform is added to the network. Additional tokens may then be purchased for replenishing any depleted amounts.
- As presently contemplated, an INFO message includes a command type and the node ID and password (if applicable) of the sending messaging platform. For example, the INFO message command type may include a token update command and a value for specifying a replenishment amount. The receiving messaging platform interprets an INFO message having a command type of token update by updating its token pool by the value specified in the command type.
- Master Platform Post Office Feature
- The present invention may also include a post office function for handling a message that is intended for a message platform that is in a non-operational state (target messaging platform) such as a messaging platform having a dial-up connection that is not within its operation schedule. The message is routed to a master platform which stores the message. The master platform delivers the message to the target messaging platform when the master platform determines that the target messaging platform has an in-operation status.
- For example, referring to FIG. 7, a messaging platform such as
messaging platform 170 may have a dial-upconnection 172 tomessaging network 174 via its switched backbone such as theInternet 176. Since dial-upconnection 172 may not be continuous, messages sent betweenmessaging platform 170 andInternet 176 may be delayed. For example,messaging platform 178 may send a delivery-confirmedstatus message 180 tomessaging platform 170 to confirm delivery of auser message 182 sent frommessaging platform 170. Ifmessaging platform 170 has a disconnected dial-upconnection 172, delivery-confirmed confirmingstatus message 180 will not arrive until dial-upconnection 172 is re-established, which would be attempted during the operational period defined formessaging platform 170. Also,messaging platform 178 will not receive a confirming message frommessaging platform 170 that delivery-confirmedstatus message 180 has been received until dial-upconnection 172 has been established. Consequently, a status message intended for a messaging platform having a non-operational status at the time of delivery is instead routed tomaster platform 184 by the messaging platform that was requested to deliver a user message to a local area such asmessaging platform 178. -
Messaging platform 178 determines whethermessaging platform 170 can receive the delivery-confirmedstatus message 180 by referring to global routing table 192. If the messaging platform entry in global routing table 192 indicates the inability ofmessaging platform 170 to receive delivery-confirmedstatus message 180,messaging platform 178 routes delivery-confirmedstatus message 180 tomaster platform 184. The inability to receive status messages may be indicated, for example, by an operation schedule that shows a messaging platform is not within its operation window such as its daily and/or hourly operation period. - When
master platform 184 receives confirmingmessage 180 frommessaging platform 178, it stores confirmingmessage 180 in amemory store location 186 corresponding to messaging platform 170 (mailbox slot) andtags confirming message 180 for delivery the nexttime messaging platform 170 is scheduled to re-connect.Master platform 184 determines the appropriate time to deliver the reply message by referencingmessaging platform entry 188 corresponding tomessaging platform 170 in master global routing table 190. - Unlike a messaging platform having a dial-up connection or a connection that has been interrupted, a messaging platform having a dedicated connection receives status messages directly from the replying messaging platform such as
messaging platform 178 in FIG. 7. Replyingmessaging platform 178 distinguishes between messaging platforms having a dedicated or dial-up connections by referencing global routing table 192. - As an alternative embodiment, a
status message 194 may be sent directly bymessaging platform 178 to themessaging platform 170 as an email. However, if dial-upconnection 172 has not yet been re-established,status message 194 will not be delivered tomessaging platform 170 but will be held by theservice provider 196 until dial-upconnection 172 is re-established. Unlike in the first embodiment, this approach does not specifically provide for a confirmation of receipt bymessaging platform 170 sinceservice provider 196 may not provide a confirmation of receipt ofstatus message 194 bymessaging platform 170 once dial-upconnection 172 has been re-established. - Information Delivery
- Referring to FIGS. 7 and 8, the above described post office feature may be enhanced to include delivering
information 198 from at least oneinformation source 200 outside ofmessaging network 174 to amailbox 202 provided bymessaging platform 204.Messaging platform 204 has been configured to providemailbox 202 which corresponds to a subscriber 205. - At
step 206 a, subscriber 205 logs on tomessaging platform 204 to subscribe to an information delivery service provided by the messaging network. Logging on tomessaging platform 204 may be accomplished through atelephone 206 sincemessaging platform 204 is configured to provide a telephone interface capable of interpreting subscriber-entered information made through a DTMF generator such as through a telephone keypad. To ensure proper information delivery, subscriber 205 is prompted for a mail box ID and/or password for identification purposes. - At
step 206 b, subscriber 205 providesservice information 208 by selecting aninformation type 209, adelivery period 210 that defines how ofteninformation type 208 is to be delivered, and adelivery format 211.Service information 208 is provided through a service menu that is presented to subscriber 205 bymessaging platform 204. The service menu provides a list of available services thatmessaging platform 204 has been configured to provide to its supported users. One of the services listed may include the information delivery service discussed herein. The service menu may also include additional services that are discussed in the present invention as well as services discussed in the multimedia messaging invention, which is incorporated herein by reference. Once the information delivery service is chosen, subscriber 205 is presented with a sub-menu that lists the information types that the messaging network has been configured to provide under that service. - For example, the sub-menu lists information types such as stocks, sports, and weather that may be selected by subscriber205 through a telephone keypad (or equivalent DTMF generator). The button depressed reflects the position of the information type selected in the sub-menu, i.e, depressing a “1” chooses an information type of stocks, while depressing a “2” chooses an information type of sports. For an information type of stocks,
messaging platform 204 also prompts subscriber 205 to enter a stock symbol using the telephone keypad in the manner outlined in the multimedia messaging invention, which is incorporated herein by reference. - Besides providing an
information type 209 selection, subscriber 205 is also prompted for adelivery period 210, anddelivery format 211 which are entered using the telephone keypad. In accordance with a present embodiment of the present invention,delivery format 211 includes an email, fax, or voice format. - At
step 206 c, afterstep 206 b is complete,messaging platform 204 contacts its assigned master platform such asmaster platform 184 by sending a SUBSCRIBE request tomaster platform 184. In response,master platform 184 requests service frominformation source 200 by providingservice information 208 received from subscriber 205. In addition,master platform 184 creates a storage location that corresponds to subscriber 205 in amemory store 186 for holding any information received frominformation source 200 that matchesservice information 208 entered by subscriber 205 instep 206 b. - The SUBSCRIBE request includes a command type, a node ID corresponding to
messaging platform 204, a mailbox ID corresponding to subscriber 205, and a password (if applicable). For example, the subscribe request may include a command type that instructsmaster platform 184 to request thatinformation source 200 provide the information sought inservice information 208 that was chosen by subscriber 205 instep 206 b. - At
step 206 d, ifservice information 208 includes anemail delivery format 211, step 206 e is performed. Otherwise step 206 f is performed. Atstep 206 e, messaging platform converts any information received frominformation source 200 that corresponds to serviceinformation 208 entered by subscriber 205 into a message having an email format and delivers the message tomailbox 204 which corresponds to subscriber 205. - At
step 206 f, if subscribingmessaging platform 204 has an in-operation status, such as when it has a viable connection to the switchedbackbone 176, step 206 g is performed. Atstep 206 g, any information received fromsource 200 that corresponds to the subscription information requested is forwarded tomessaging platform 204 bymaster platform 184. - If at
step 206 f, subscribingmessaging platform 204 has a non-operational status, step 206 h is performed. Through a microprocessor system running under program control or equivalent device master platform performs the following steps. Atstep 206 h, master platform stores any information received fromsource 200 inmemory store 186.Master platform 184 does not send the stored information to a corresponding subscriber'smessaging platform 204 untilmaster platform 184 determines thatmessaging platform 204 has an in-operation status. For example,master platform 184 may refer to its master global routing table to find a messaging platform entry that defines the profile formessaging platform 204 to determine whethermessaging platform 204 has an in-operation status based on the operation schedule listed in messaging platform entry. - In an alternative embodiment, the present invention may use a
master platform 212 dedicated solely for the handling messages originating from information sources outside the messaging network such as frominformation source 214.Master platform 212 may be configured to receive information through any of its network interfaces such as through its switchedbackbone interface 176 or through an interface supporting a dedicated connection toinformation source 214. - At
step 206 i, the information received bymaster platform 184 is received bymessaging platform 204 which converts the information to havedelivery format 210 prior to delivery. - At
step 206 j,messaging platform 204 delivers the information tomailbox 202, which corresponds to subscriber 205, usingdelivery format 210. - While illustrative embodiments and applications of this invention have been shown and described, it would be apparent to those skilled in the art that many more modifications than have been mentioned above are possible without departing from the inventive concepts set forth herein. The invention, therefore, is not to be limited except in the spirit of the appended claims.
Claims (61)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/944,668 US6381633B2 (en) | 1997-05-09 | 1997-10-06 | System and method for managing multimedia messaging platforms |
US10/053,826 US7010574B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
US10/053,827 US7177908B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/853,290 US5974449A (en) | 1997-05-09 | 1997-05-09 | Apparatus and method for providing multimedia messaging between disparate messaging platforms |
US08/944,668 US6381633B2 (en) | 1997-05-09 | 1997-10-06 | System and method for managing multimedia messaging platforms |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/853,290 Continuation-In-Part US5974449A (en) | 1997-05-09 | 1997-05-09 | Apparatus and method for providing multimedia messaging between disparate messaging platforms |
Related Child Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/053,826 Continuation US7010574B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
US10/053,827 Continuation US7177908B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
Publications (2)
Publication Number | Publication Date |
---|---|
US20010011303A1 true US20010011303A1 (en) | 2001-08-02 |
US6381633B2 US6381633B2 (en) | 2002-04-30 |
Family
ID=35966385
Family Applications (3)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US08/944,668 Expired - Lifetime US6381633B2 (en) | 1997-05-09 | 1997-10-06 | System and method for managing multimedia messaging platforms |
US10/053,827 Expired - Lifetime US7177908B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
US10/053,826 Expired - Lifetime US7010574B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
Family Applications After (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/053,827 Expired - Lifetime US7177908B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
US10/053,826 Expired - Lifetime US7010574B1 (en) | 1997-05-09 | 2002-01-18 | System and method for managing multimedia messaging platforms |
Country Status (1)
Country | Link |
---|---|
US (3) | US6381633B2 (en) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
GB2395394A (en) * | 2002-11-08 | 2004-05-19 | Hewlett Packard Co | Voice mail network where changes to one voicemail system are recorded centrally at an administrator and used to update other voicemail system databases |
US20040120480A1 (en) * | 2002-12-24 | 2004-06-24 | Didcock Clifford Neil | Flexible distributed/centralaized architecture for voice/unified messaging system |
EP1434415A1 (en) * | 2002-12-24 | 2004-06-30 | Avaya UK | Flexible distributed/centralized architecture for voice/unified messaging system |
US6810114B2 (en) | 2001-07-10 | 2004-10-26 | Hewlett-Packard Development Company, L.P. | System for updating a voicemail network |
US20040243722A1 (en) * | 2001-08-31 | 2004-12-02 | Yasunori Matsui | Network connection apparatus, connection system, and network connection method |
US20050111634A1 (en) * | 2003-09-17 | 2005-05-26 | Didcock Clifford N. | Optimal call coverage method and apparatus |
US20050198111A1 (en) * | 2002-05-21 | 2005-09-08 | Lamb Peter C. | Distributed transaction event matching |
US20080215467A1 (en) * | 2001-05-11 | 2008-09-04 | Accenture Global Services Gmbh | Digital content subscription conditioning system |
US20090082044A1 (en) * | 1998-08-06 | 2009-03-26 | Fujitsu Limited | Text messaging system and method |
US7895123B1 (en) | 2001-06-12 | 2011-02-22 | Accenture Global Services Limited | Digital content publication |
US9935831B1 (en) * | 2014-06-03 | 2018-04-03 | Big Switch Networks, Inc. | Systems and methods for controlling network switches using a switch modeling interface at a controller |
US11115212B1 (en) * | 2016-11-15 | 2021-09-07 | Teradata Us, Inc. | Multi-processing node connection in a data store system via encrypted password |
US11196844B1 (en) * | 2020-11-17 | 2021-12-07 | Accenture Global Solutions Limited | Multi-platform service management system |
US11616725B1 (en) * | 2021-06-30 | 2023-03-28 | Amazon Technologies, Inc. | Hierarchical token buckets |
Families Citing this family (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6381633B2 (en) * | 1997-05-09 | 2002-04-30 | Carmel Connection, Inc. | System and method for managing multimedia messaging platforms |
US6895558B1 (en) * | 2000-02-11 | 2005-05-17 | Microsoft Corporation | Multi-access mode electronic personal assistant |
US8265663B2 (en) * | 2002-12-17 | 2012-09-11 | Nokia Corporation | Messaging services for pre-pay users |
DE10335432B4 (en) * | 2003-07-31 | 2007-11-29 | Nokia Siemens Networks Gmbh & Co.Kg | Method for transmitting messages between communication terminals |
WO2005015893A2 (en) * | 2003-08-05 | 2005-02-17 | Spooner David A | Information display system and method |
US7568007B2 (en) * | 2004-09-29 | 2009-07-28 | International Business Machines Corporation | System and method for supporting instant messaging in disconnected modes |
KR100746848B1 (en) * | 2005-10-25 | 2007-08-08 | (주)이홈 | System for multimedia note transmission using concept of group ware |
US20070130288A1 (en) * | 2005-12-02 | 2007-06-07 | Inter-Tel, Inc. | Distributed communication through media services |
US8582450B1 (en) * | 2009-09-30 | 2013-11-12 | Shoretel, Inc. | Status reporting system |
US8589264B2 (en) * | 2009-10-19 | 2013-11-19 | International Business Machines Corporation | Token licensing mapping costs to enabled software tool features |
Family Cites Families (102)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4747126A (en) * | 1985-02-20 | 1988-05-24 | A T & E Corporation | Voice mail system on magnetic tape |
US5261080A (en) * | 1987-08-21 | 1993-11-09 | Wang Laboratories, Inc. | Matchmaker for assisting and executing the providing and conversion of data between objects in a data processing system storing data in typed objects having different data formats |
US5031206A (en) | 1987-11-30 | 1991-07-09 | Fon-Ex, Inc. | Method and apparatus for identifying words entered on DTMF pushbuttons |
US5049873A (en) * | 1988-01-29 | 1991-09-17 | Network Equipment Technologies, Inc. | Communications network state and topology monitor |
US5481698A (en) * | 1988-09-28 | 1996-01-02 | Hitachi Ltd. | Computer system and job executing method |
US5109486A (en) * | 1989-01-06 | 1992-04-28 | Motorola, Inc. | Distributed computer system with network and resource status monitoring |
US5115362A (en) | 1989-02-16 | 1992-05-19 | Pioneer Electronic Corporation | Cassette changer for tape player |
JPH039430A (en) * | 1989-06-06 | 1991-01-17 | Fujitsu Ltd | Register allocation system for compiler |
US5039980A (en) * | 1990-01-26 | 1991-08-13 | Honeywell Inc. | Multi-nodal communication network with coordinated responsibility for global functions by the nodes |
JPH0477873A (en) * | 1990-07-13 | 1992-03-11 | Fujitsu Ltd | Method for preparing global net of hierarchization functional block |
US5224156A (en) * | 1990-07-19 | 1993-06-29 | Electronic Modules, Inc. | Method and apparatus for facsimile enhancement |
US5377191A (en) | 1990-10-26 | 1994-12-27 | Data General Corporation | Network communication system |
US5260990A (en) * | 1991-04-30 | 1993-11-09 | Boston Technology, Inc. | Multiple integrations unit for coupling different switching systems to a message storage system |
US5627764A (en) * | 1991-10-04 | 1997-05-06 | Banyan Systems, Inc. | Automatic electronic messaging system with feedback and work flow administration |
US5530740A (en) | 1991-10-28 | 1996-06-25 | Contigram Communications Corporation | System and method for integrating voice, facsimile and electronic mail data through a personal computer |
US5737395A (en) | 1991-10-28 | 1998-04-07 | Centigram Communications Corporation | System and method for integrating voice, facsimile and electronic mail data through a personal computer |
US5349636A (en) | 1991-10-28 | 1994-09-20 | Centigram Communications Corporation | Interface system and method for interconnecting a voice message system and an interactive voice response system |
US5838458A (en) | 1992-02-25 | 1998-11-17 | Tsai; Irving | Method and apparatus for linking designated portions of a received document image with an electronic address |
US5333266A (en) | 1992-03-27 | 1994-07-26 | International Business Machines Corporation | Method and apparatus for message handling in computer systems |
US5577202A (en) * | 1992-08-24 | 1996-11-19 | Trw Inc. | Message handling system for automated gateway between first and second handling systems wherein first envelope is added to a second envelope respectively without changing text |
US5517556A (en) * | 1992-09-18 | 1996-05-14 | Vmx, Inc. | Call processing system with facsimile processing |
US5581749A (en) * | 1992-12-21 | 1996-12-03 | Thedow Chemical Company | System and method for maintaining codes among distributed databases using a global database |
US5479411A (en) | 1993-03-10 | 1995-12-26 | At&T Corp. | Multi-media integrated message arrangement |
US5754306A (en) * | 1993-06-15 | 1998-05-19 | Hewlett-Packard Company | System and method for a communication system |
CA2100533C (en) * | 1993-06-22 | 2004-05-25 | Duncan Wayne Lee | Method and system for synchronizing computer mail user directories |
EP0631419B1 (en) | 1993-06-22 | 1996-03-27 | Vmx Inc. | An electronic mail system having integrated voice messages |
US5715393A (en) * | 1993-08-16 | 1998-02-03 | Motorola, Inc. | Method for remote system process monitoring |
US5475737A (en) | 1993-09-17 | 1995-12-12 | Bell Atlantic Network Services, Inc. | Toll saver for centralized messaging systems |
US5841978A (en) * | 1993-11-18 | 1998-11-24 | Digimarc Corporation | Network linking method using steganographically embedded data objects |
US5809237A (en) * | 1993-11-24 | 1998-09-15 | Intel Corporation | Registration of computer-based conferencing system |
JPH07162454A (en) | 1993-12-03 | 1995-06-23 | Fujitsu Ltd | Method and device for electronic mail linkage |
US6070196A (en) * | 1994-02-02 | 2000-05-30 | Mitsubishi Semiconductor America, Inc. | Protocol converter controller having distributed architecture |
US5845090A (en) * | 1994-02-14 | 1998-12-01 | Platinium Technology, Inc. | System for software distribution in a digital computer network |
US5675507A (en) | 1995-04-28 | 1997-10-07 | Bobo, Ii; Charles R. | Message storage and delivery system |
US5557539A (en) * | 1994-06-13 | 1996-09-17 | Centigram Communications Corporation | Apparatus and method for testing an interactive voice messaging system |
US5835743A (en) * | 1994-06-30 | 1998-11-10 | Sun Microsystems, Inc. | Application binary interface and method of interfacing binary application program to digital computer |
JPH0832618A (en) | 1994-07-14 | 1996-02-02 | Hitachi Ltd | Voice mail system and voice mail exchange device |
US5689550A (en) * | 1994-08-08 | 1997-11-18 | Voice-Tel Enterprises, Inc. | Interface enabling voice messaging systems to interact with communications networks |
US5608643A (en) * | 1994-09-01 | 1997-03-04 | General Programming Holdings, Inc. | System for managing multiple dispensing units and method of operation |
US5515098A (en) * | 1994-09-08 | 1996-05-07 | Carles; John B. | System and method for selectively distributing commercial messages over a communications network |
US5621727A (en) | 1994-09-16 | 1997-04-15 | Octel Communications Corporation | System and method for private addressing plans using community addressing |
US5740231A (en) * | 1994-09-16 | 1998-04-14 | Octel Communications Corporation | Network-based multimedia communications and directory system and method of operation |
US5754636A (en) * | 1994-11-01 | 1998-05-19 | Answersoft, Inc. | Computer telephone system |
US6275869B1 (en) * | 1994-11-22 | 2001-08-14 | Eastman Kodak Company | System for network communication of image information between imaging devices according to multiple protocols |
US5638424A (en) * | 1994-11-30 | 1997-06-10 | Texas Instruments Incorporated | Telephone voice mail delivery system |
US5608874A (en) * | 1994-12-02 | 1997-03-04 | Autoentry Online, Inc. | System and method for automatic data file format translation and transmission having advanced features |
CA2139081C (en) | 1994-12-23 | 1999-02-02 | Alastair Gordon | Unified messaging system and method |
US5633916A (en) | 1994-12-30 | 1997-05-27 | Unisys Corporation | Universal messaging service using single voice grade telephone line within a client/server architecture |
US5557320A (en) * | 1995-01-31 | 1996-09-17 | Krebs; Mark | Video mail delivery system |
WO1996027266A1 (en) | 1995-02-28 | 1996-09-06 | Philips Electronics N.V. | Telecommunication system |
US5790793A (en) * | 1995-04-04 | 1998-08-04 | Higley; Thomas | Method and system to create, transmit, receive and process information, including an address to further information |
US5638431A (en) * | 1995-05-01 | 1997-06-10 | Mci Corporation | Calling card validation system and method therefor |
JPH08314836A (en) * | 1995-05-19 | 1996-11-29 | Hitachi Ltd | Managing service object providing method |
GB2301735B (en) * | 1995-06-02 | 1999-07-28 | Dsc Communications | Message handling in a telecommunications network |
US5691980A (en) * | 1995-06-07 | 1997-11-25 | General Electric Company | Local communication network for power reduction and enhanced reliability in a multiple node tracking system |
JP3088269B2 (en) * | 1995-07-26 | 2000-09-18 | 日本電気通信システム株式会社 | Computer network system and operating system version management method |
US6408331B1 (en) * | 1995-07-27 | 2002-06-18 | Digimarc Corporation | Computer linking methods using encoded graphics |
US6311214B1 (en) * | 1995-07-27 | 2001-10-30 | Digimarc Corporation | Linking of computers based on optical sensing of digital data |
US5813009A (en) * | 1995-07-28 | 1998-09-22 | Univirtual Corp. | Computer based records management system method |
US5734828A (en) * | 1995-08-30 | 1998-03-31 | Intel Corporation | System for accessing/delivering on-line/information services via individualized environments using streamlined application sharing host and client services |
US5647002A (en) | 1995-09-01 | 1997-07-08 | Lucent Technologies Inc. | Synchronization of mailboxes of different types |
US6047323A (en) * | 1995-10-19 | 2000-04-04 | Hewlett-Packard Company | Creation and migration of distributed streams in clusters of networked computers |
US5793763A (en) * | 1995-11-03 | 1998-08-11 | Cisco Technology, Inc. | Security system for network address translation systems |
US5740362A (en) | 1995-11-06 | 1998-04-14 | International Business Machines Corporation | Management of network distributed agents in a distributed computing environment |
US5680443A (en) * | 1995-11-08 | 1997-10-21 | At & T | Smart messages and smart macros for telecommunications relay service (TRS) and operator services for deaf (OSD) |
IL115967A (en) | 1995-11-12 | 1999-05-09 | Phonet Communication Ltd | Network based distributed pbx system |
EP0781068A1 (en) * | 1995-12-20 | 1997-06-25 | International Business Machines Corporation | Method and system for adaptive bandwidth allocation in a high speed data network |
SE515901C2 (en) * | 1995-12-28 | 2001-10-22 | Dynarc Ab | Resource management, plans and arrangements |
US5812795A (en) | 1996-01-19 | 1998-09-22 | Lucent Technologies Inc. | Automatic addressing of messages and message components of different media |
US6065047A (en) * | 1996-01-24 | 2000-05-16 | America Online, Inc. | System for providing subscriber with access to a content area customized for the combination of subscriber's responses to topic prompt, subtopic prompt, and action prompt |
US5781186A (en) | 1996-02-02 | 1998-07-14 | Lucent Technologies Inc. | Arrangement for specifying presentation of multimedia message components |
US5918018A (en) * | 1996-02-09 | 1999-06-29 | Secure Computing Corporation | System and method for achieving network separation |
US5734820A (en) * | 1996-03-11 | 1998-03-31 | Sterling Commerce, Inc. | Security apparatus and method for a data communications system |
JP3001410B2 (en) * | 1996-03-28 | 2000-01-24 | 日本電気テレコムシステム株式会社 | Automatic detour routing method |
US5727156A (en) * | 1996-04-10 | 1998-03-10 | Hotoffice Technologies, Inc. | Internet-based automatic publishing system |
US5828837A (en) * | 1996-04-15 | 1998-10-27 | Digilog As | Computer network system and method for efficient information transfer |
US5931909A (en) * | 1996-04-19 | 1999-08-03 | Sun Microsystems, Inc. | System for multiple-client software installation and upgrade |
US5805203A (en) * | 1996-05-21 | 1998-09-08 | Jsm Co., Inc. | Time division, multiplexed, shared bandwidth communication system |
US5745689A (en) | 1996-05-23 | 1998-04-28 | Electronic Data Systems Corporation | System and method for providing pager services to users of a computer network |
US5708699A (en) * | 1996-05-29 | 1998-01-13 | At&T | Hybrid access architecture for voice messaging systems |
US5822526A (en) * | 1996-06-03 | 1998-10-13 | Microsoft Corporation | System and method for maintaining and administering email address names in a network |
US20030061270A1 (en) * | 1996-06-13 | 2003-03-27 | Tetsujiro Suzuki | Electronic mail system with mail content class designation |
US5812668A (en) * | 1996-06-17 | 1998-09-22 | Verifone, Inc. | System, method and article of manufacture for verifying the operation of a remote transaction clearance system utilizing a multichannel, extensible, flexible architecture |
US5903726A (en) * | 1996-06-26 | 1999-05-11 | Mci Communications Corporation | System using portion of a short message payload to identify short message service types and delivering the message if user subscribes to the services |
US6031978A (en) * | 1996-06-28 | 2000-02-29 | International Business Machines Corporation | System, method and program for enabling a client to reconnect to a same server in a network of computer systems after the server has moved to a different network address |
US5812773A (en) * | 1996-07-12 | 1998-09-22 | Microsoft Corporation | System and method for the distribution of hierarchically structured data |
US5870556A (en) * | 1996-07-12 | 1999-02-09 | Microsoft Corporation | Monitoring a messaging link |
EP0972247B1 (en) * | 1996-08-02 | 2004-03-17 | Hewlett-Packard Company | Method and apparatus for allowing distributed control of shared resources |
US5881292A (en) * | 1996-09-26 | 1999-03-09 | Microsoft Corporation | Dynamic versioning system for multiple users of multi-module software system |
US5978840A (en) * | 1996-09-26 | 1999-11-02 | Verifone, Inc. | System, method and article of manufacture for a payment gateway system architecture for processing encrypted payment transactions utilizing a multichannel, extensible, flexible architecture |
US6233318B1 (en) * | 1996-11-05 | 2001-05-15 | Comverse Network Systems, Inc. | System for accessing multimedia mailboxes and messages over the internet and via telephone |
US6014644A (en) * | 1996-11-22 | 2000-01-11 | Pp International, Inc. | Centrally coordinated communication systems with multiple broadcast data objects and response tracking |
US5841839A (en) | 1996-12-06 | 1998-11-24 | Fogg; Shawn D. T. | Integrated telephone switching apparatus for fully integrating multiple business telephone systems with a single voice mail system |
US5794039A (en) | 1996-12-18 | 1998-08-11 | Unisys Corp. | Method for abstracting messages of various protocols into objects for storage in a database |
US5930471A (en) * | 1996-12-26 | 1999-07-27 | At&T Corp | Communications system and method of operation for electronic messaging using structured response objects and virtual mailboxes |
US5974122A (en) * | 1997-01-27 | 1999-10-26 | Ameritech Corporation | Method and telecommunication system for transmitting a facsimile message |
US5974449A (en) * | 1997-05-09 | 1999-10-26 | Carmel Connection, Inc. | Apparatus and method for providing multimedia messaging between disparate messaging platforms |
US6381633B2 (en) * | 1997-05-09 | 2002-04-30 | Carmel Connection, Inc. | System and method for managing multimedia messaging platforms |
US6330079B1 (en) * | 1997-09-08 | 2001-12-11 | Mci Communications Corporation | Integrated voicemail and faxmail platform for a communications system |
US5926463A (en) * | 1997-10-06 | 1999-07-20 | 3Com Corporation | Method and apparatus for viewing and managing a configuration of a computer network |
US6363411B1 (en) * | 1998-08-05 | 2002-03-26 | Mci Worldcom, Inc. | Intelligent network |
US6298126B1 (en) * | 1997-12-16 | 2001-10-02 | At&T Corp. | Method and apparatus for controlling rating of calls to pay services |
-
1997
- 1997-10-06 US US08/944,668 patent/US6381633B2/en not_active Expired - Lifetime
-
2002
- 2002-01-18 US US10/053,827 patent/US7177908B1/en not_active Expired - Lifetime
- 2002-01-18 US US10/053,826 patent/US7010574B1/en not_active Expired - Lifetime
Cited By (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090082044A1 (en) * | 1998-08-06 | 2009-03-26 | Fujitsu Limited | Text messaging system and method |
US20080215467A1 (en) * | 2001-05-11 | 2008-09-04 | Accenture Global Services Gmbh | Digital content subscription conditioning system |
US9449299B2 (en) | 2001-05-11 | 2016-09-20 | Accenture Global Services Limited | Digital content subscription conditioning system |
US7505936B2 (en) | 2001-05-11 | 2009-03-17 | Accenture Global Services Gmbh | Digital content subscription conditioning system |
US7895123B1 (en) | 2001-06-12 | 2011-02-22 | Accenture Global Services Limited | Digital content publication |
US20110047079A1 (en) * | 2001-06-12 | 2011-02-24 | Du L Garren | Digital content publication |
US6810114B2 (en) | 2001-07-10 | 2004-10-26 | Hewlett-Packard Development Company, L.P. | System for updating a voicemail network |
US20040243722A1 (en) * | 2001-08-31 | 2004-12-02 | Yasunori Matsui | Network connection apparatus, connection system, and network connection method |
US7484009B2 (en) * | 2001-08-31 | 2009-01-27 | Sony Corporation | Network connection apparatus, connection system, and network connection method |
US7552205B2 (en) * | 2002-05-21 | 2009-06-23 | Accenture Global Services Gmbh | Distributed transaction event matching |
US20050198111A1 (en) * | 2002-05-21 | 2005-09-08 | Lamb Peter C. | Distributed transaction event matching |
GB2395394B (en) * | 2002-11-08 | 2005-12-07 | Hewlett Packard Co | System for updating a voicemail network |
GB2395394A (en) * | 2002-11-08 | 2004-05-19 | Hewlett Packard Co | Voice mail network where changes to one voicemail system are recorded centrally at an administrator and used to update other voicemail system databases |
EP1434415A1 (en) * | 2002-12-24 | 2004-06-30 | Avaya UK | Flexible distributed/centralized architecture for voice/unified messaging system |
US7272214B2 (en) | 2002-12-24 | 2007-09-18 | Avaya Uk | Flexible distributed/centralized architecture for voice/unified messaging system |
US20040120480A1 (en) * | 2002-12-24 | 2004-06-24 | Didcock Clifford Neil | Flexible distributed/centralaized architecture for voice/unified messaging system |
US20050111634A1 (en) * | 2003-09-17 | 2005-05-26 | Didcock Clifford N. | Optimal call coverage method and apparatus |
US7231022B2 (en) | 2003-09-17 | 2007-06-12 | Avaya Uk | Optimal call coverage method and apparatus |
US9935831B1 (en) * | 2014-06-03 | 2018-04-03 | Big Switch Networks, Inc. | Systems and methods for controlling network switches using a switch modeling interface at a controller |
US11115212B1 (en) * | 2016-11-15 | 2021-09-07 | Teradata Us, Inc. | Multi-processing node connection in a data store system via encrypted password |
US11196844B1 (en) * | 2020-11-17 | 2021-12-07 | Accenture Global Solutions Limited | Multi-platform service management system |
US11616725B1 (en) * | 2021-06-30 | 2023-03-28 | Amazon Technologies, Inc. | Hierarchical token buckets |
Also Published As
Publication number | Publication date |
---|---|
US6381633B2 (en) | 2002-04-30 |
US7177908B1 (en) | 2007-02-13 |
US7010574B1 (en) | 2006-03-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6381633B2 (en) | System and method for managing multimedia messaging platforms | |
JP3967384B2 (en) | Method and system for extended addressing planning | |
US5740230A (en) | Directory management system and method | |
EP0781482B1 (en) | Network-based multimedia communications and directory system and method of operation | |
US20040082348A1 (en) | System and method for sending SMS and text messages | |
US6411684B1 (en) | Network-based multimedia communications and directory system and method of operation | |
US7715857B2 (en) | Methods and systems for enhanced directory assistance using wireless messaging protocols | |
US7200413B2 (en) | Methods and system for enhanced directory assistance using wireless messaging protocols | |
CA2374161C (en) | Voice messaging system | |
US6970546B2 (en) | Intelligent remote caller ID | |
US7680259B2 (en) | Rule-based intelligent call forwarding | |
US9295104B2 (en) | Telecommunication system and method for transferring SMS messages between terminals and intelligent network services | |
WO2008094519A1 (en) | System and method for communicating messages using alias addressing | |
US7392297B2 (en) | Message processing scheme for realizing unified handling and management of messages using a portable message processing device | |
US20080242327A1 (en) | System and method for sending sms and text messages | |
US8121625B2 (en) | System for enabling communication between computers and mobile telephones | |
WO2002082837A1 (en) | Message distribution system | |
JP2006067362A (en) | Wap gateway and control method of wap gateway |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: CARMEL CONNECTION, INC., CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:CHANG, JACK H.;TONG, RAYMOND L.;REEL/FRAME:012616/0853 Effective date: 19971002 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
FEPP | Fee payment procedure |
Free format text: PAT HOLDER NO LONGER CLAIMS SMALL ENTITY STATUS, ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: STOL); 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 |
|
AS | Assignment |
Owner name: CALUMET KEWEENAW LLC, CALIFORNIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CARMEL CONNECTION, INC.;REEL/FRAME:015530/0630 Effective date: 20041004 |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FPAY | Fee payment |
Year of fee payment: 12 |
|
AS | Assignment |
Owner name: ZARBANA DIGITAL FUND LLC, DELAWARE Free format text: MERGER;ASSIGNOR:CALUMET KEWEENAW LLC;REEL/FRAME:037219/0372 Effective date: 20150811 |