US 7,020,132 B1Grant

Scalable architecture for transmission of messages over a network

Issue Date:2006-03-28

•20 Claims

•9 Drawing Sheets

Abstract

A method and apparatus is disclosed for delivering messages that utilizes a message queue and a router/filter within a private data network. The private network is connected to an external data network such as the Internet, and has separate outbound resource servers to provide a high degree of scalability for handling a variety of message types.

Metadata

Assignee

j2 Global Communications, Inc.

Inventors

Anand Narasimhan
Yaacov Shemesh
Amit Kumar

Application Information

Application Number:US 10/393,227

Filing Date:2003-03-20

Priority Date:1998-06-12

Art Unit:2667

Classifications

IPC:

H04L12/66

Patent Drawings (9 sheets)

Description

[0001] This is a continuation of Ser. No. 09/097,307, now U.S. Pat. No. 6,597,688 filed on Jun. 12, 1998.

Background of the Invention

[0002] 1. Field of the Invention

[0003] The present invention relates to the field of message receipt/transmission and delivery using computer, phone, wireless and other communications networks. Specifically, the present invention relates to the transmission of e-mail messages which may be text only, text plus an audio file, text plus a video file, text plus a fax file or any combination thereof to a phone, pager or fax machine or other receiving device suitable for the message content, over appropriate communications networks using an architecture which enables easy expansion to handle additional message traffic as well as to connect to additional communications networks, including networks which do not presently exist which may become available in the future.

[0004] 2. Description of Related Art

[0005] Voice and data communications systems such as the public switched telephone network (PSTN) are currently used to transfer image and text data transmitted by facsimile (“fax”) machines in addition to the normally carried voice traffic. These faxed images are usually transmitted through the PSTN and received for printout or storage of the image on a destination fax machine or computer for the use by the recipient.

[0006] In U.S. Pat. No. 6,208,638 entitled Method and Apparatus for Transmission and Retrieval of Facsimile and Audio Messages Over a Circuit or Packet Switched Network, it is disclosed that to provide for the receipt and transmission of audio and fax information by a first user over a circuit switched network such as the public switched telephone network (PSTN) to a second user over a packet switched network such as the Internet, a communications server is connected both to the circuit switched network and a packet switched network.

[0007] The communications server contains resources to receive and process incoming audio and facsimile calls from the circuit switched network into a format suitable for transmission over the packet switched network to the second user's address. In addition, a link is first determined between the second user's address on the circuit switched network and the second user's address on the packet switched network, and then an appropriate route to the second user's address on the packet network is determined. With the system being maintained in a distributed and redundant fashion, reliable receipt and transfer of all messages is ensured. A copy of the specification and drawings of U.S. Pat. No. 6,208,638 is attached hereto.

[0008] However, the architecture utilized as described in U.S. Pat. No. 6,208,638 is not easily scalable to handle increasingly higher levels of message traffic or to easily connect to networks in addition to the PSTN and the Internet. FIG. 1 shows the essence of the architecture of U.S. Pat. No. 6,208,638. An e-mail message is passed to an outbound resource 11 (communications server 550 in U.S. Pat. No. 6,208,638) which converts the e-mail message to a fax format or to audio for transmission to a fax machine or telephone connected to the PSTN. A database 13 stores customer information necessary for processing of messages (an unnumbered part of communications server 550 in U.S. Pat. No. 6,208,638 which is also contained in database server 595 in U.S. Pat. No. 6,208,638). After processing of an e-mail message by outbound resource 11, a fax or voice mail message is sent over the PSTN or more generally, a generalized switched telephone network (GSTN) which includes cellular telephone networks as well as the PSTN. Optionally, a pager message may also be sent informing a user of the fax which has been sent or availability of a voice mail message as described in U.S. Pat. No. 6,073,165 entitled Processing and Forwarding Messages From a Computer Network to a Forwarding Service.

Summary of the Invention

[0009] A method and apparatus is disclosed for delivering messages that utilizes a message queue and a router/filter within a private data network. The private network is connected to an external data network such as the Internet, and has separate outbound resource servers to provide a high degree of scalability for handling a variety of message types.

Brief Description of the Drawings

[0010] FIG. 1 is a block diagram of a prior art architecture which performs the functions, but not the scalability of the architecture of the present invention.

[0011] FIG. 2 is a block diagram illustrating the architecture of the present invention.

[0012] FIG. 3 is a block diagram showing the data/control flow through message queue 21, router/filter 23 and database 27.

[0013] FIG. 4 (4a and 4b) is a flow diagram of the processing performed by router/filter 23.

[0014] FIG. 5 is a system diagram of a network containing a message server.

[0015] FIG. 6 is a block diagram illustrating the message server.

[0016] FIG. 7 is a flow diagram illustrating some operations.

Detailed Description of the Invention

[0017] The present invention provides a method and apparatus for allowing the receipt and transmission of audio, video and fax information between a circuit switched network and a packet switched network. For purposes of explanation, specific embodiments are set forth to provide a thorough understanding of the present invention. However, it will be understood by one skilled in the art, that the invention may be practiced without these details. Further, although the present invention is described through the use of circuit switched and packet switched networks, most, if not all, aspects of the invention apply to all networks in general. Moreover, well-known elements, devices, process steps and the like are not set forth in detail in order to avoid obscuring the present invention.

[0018] Referring now to FIG. 2, e-mail messages for a customer are sent to/through an external data network 15 (e.g., the Internet) and routed to an appropriate SMTP/HTTP (or SHTTP) server 17 as determined by a domain name server (DNS) 18 according to well known techniques. The e-mail message may be a text message or it may include a file, the content of which may be audio, video or bitmapped (e.g., a fax) or other data. Again, the techniques for creating and sending e-mail messages with these characteristics are well known.

[0019] A processing server 19, which includes a message queue 21 and a router/filter 23 first verifies that the message is from or is to a customer using information in database 27. After successful verification, the message is broken into fragments (in the case of files with multiple attachments) and written to message queue 21. Router/filter 23 obtains messages from the message queue and handles least call routing/billing/prioritization/filtering of messages. Filtering is primarily for notification messages for pager delivery. After billing verification and determination of a least cost route, the message is assigned to one or more outbound resources 31 for delivery to the intended recipient by a method or methods selected by the customer as previously recorded in database 27.

[0020] In the case of faxes, the outbound resource is a server which dials the destination fax number and sends the fax.

[0021] In the case of voice messages, the outbound resource is a server which dials the destination telephone number and plays the voice message.

[0022] In the case of notification messages, the outbound resource is a server which dials out to the paging terminal or delivers the notification message through any appropriate paging gateway.

[0023] After the message (in whatever form) has been delivered, a receipt with details and an error log (if any) is sent back via a secure protocol to the message queue 21.

[0024] The receipt/error log messages are then processed by the router/filter which interfaces with a billing system (not shown) for customer account update.

[0025] FIG. 3 is a block diagram showing the data/control flow through message queue 21, router/filter 23 and database 27 using information contained in the following tables as explained with reference to FIGS. 4a and 4b.

[0026]

TABLE 1

Message Queue Table


MESSAGE_ID	This is a unique number
	assigned to each message
	that arrives in the system.
RESOURCE_ID	Unique number assigned to
	each Outbound Resource
RESOURCE_TYPE	Each Resource is identified
	by the type of messages
	it can deliver (e.g., FAX,
	VOICE, NOTIFY, etc.)
RESOURCE_ADDRESS	Location of the Resource
	(such as IP address)
MESSAGE_TO_EMAIL_ADDRESS	To: address of the message
MESSAGE_FROM_EMAIL_ADDRESS	From: address of the
	message
MESSAGE_LOCATION	Location of actual message
	on the Message Queue 21
MESSAGE_SIZE	Size of the message in
	bytes
MESSAGE_PRIORITY	Priority of the message
	(e.g., low, medium, high)
MESSAGE_CREATION_DATE	Timestamp identifying the
	date/time that the message
	was received by the system
MESSAGE_EXPIRY_DURATION	Amount of time after which
	the message becomes stale
MESSAGE_SCHEDULED_DATE	Scheduled delivery time-
	stamp for the message
MESSAGE_STATUS	Current status of the mes-
	sage (Active, Pending,
	Sent, etc.)
MESSAGE_ESTIMATED_COST	Estimated cost for the de-
	livery of the message
CUSTOMER_KEY	Unique number identifying
	the customer in the
	database
MESSAGE_PART_OF_BROADCAST	Flag identifying if the
	message is part of a larger
	broadcast list waiting to be
	delivered
BROADCAST_ID	Unique number identifying
	a broadcast list
COVERPAGE_ID	Unique number identifying
	a coverpage (if any) for
	a fax
MESSAGE_SUBJECT	Subject line of the message
	to be delivered
MESSAGE_DURATION	Duration of the message
	(delivery time of fax, or
	delivery time for a voice
	message, etc.)
MESSAGE_RATE	Rate for message delivery
	(dollars per second, etc.)
MESSAGE_SEND_DATE	Actual timestamp identify-
	ing when the message was
	delivered
MESSAGE_REMOTE_CSID	Identifier of the fax
	machine to which a FAX
	message was delivered
MESSAGE_TYPE	Type of message (e.g.,
	FAX, VOICE,
	NOTIFICATION, etc.)
RESOURCE_COMMUNICATION_TYPE	Protocol used to communi-
	cate with the resource
	(HTTP, SHTTP, etc.)
MESSAGE_LANGUAGE_CODE	Language used for delivery
	of a receipt or response,
	based on settings in the
	customer table
MESSAGE_PAGES	Number of pages of a
	message (used primarily for
	a fax)

[0027]

TABLE 2

File Type Table


FILETYPE_MESSAGE_TYPE	Identifier of a message type (FAX,
	VOICE, etc.)
FILETYPE_RESOURCE_TYPE	Identifier to determine a resource that
	can handle a particular file type
FILETYPE_EXTENSION	The filename extension that identifies
	a file type (e.g., WAV, TIF, JFX,
	AU, GSM, etc.)

[0028]

TABLE 3

Customer Table


CUSTOMER_KEY	Unique number identifying a customer in the
	database
FIRSTNAME	First name of customer
LASTNAME	Last name of customer
COMPANY	Company name of customer
ADDRESSLINE1	Company address
ADDRESSLINE2	Company address
CITY	Company city
MAILREGION	Company state or equivalent
MAILCODE	Zipcode or equivalent
COUNTRY	Company country
WORKNUMBER	Customer work phone number
HOMENUMBER	Customer home phone number
EMAILADDRESS	Email address of customer
COLLECTIONMETHOD	Collection method such as Credit card,
	Debit, etc.
BILLTYPE	e.g., Customer, Demo, free, corporate, etc.
STATUS	Status of customer, Active, Inactive, etc.
LANGUAGECODE	Language of customer, English, German, etc.
CURRENCYCODE	Currency for billing the customer, US
	Dollars, Pound Sterling, etc.

[0029]

TABLE 4

Currency Table


	FORMAT	Currency label
	CURRENCY_SYMBOL	Symbol for currency

[0030]

TABLE 5

Notification Table


CUSTOMERKEY	Unique number identifying a customer in the
	database
PAGERTYPECODE	Code to determine the kind of pager service
BBSNUMBER	Modem number for pager notification delivery,
	based on the pager type
PAGERNUMBER	Identifier number of the pager unit
PIN	PIN code for the pager unit
DISPLAYTYPE	Display type of the pager (numeric, alphanumeric,
	etc.)

[0031]

TABLE 6

Response_email Table


RESPONSE_ID	Unique ID for a response/receipt
	message to be sent to a customer
REPONSE_SUBJECT	Subject line of the response message
RESPONSE_FROM_EMAIL	From: line of the response message
RESPONSE_BODY	Actual text of the response message

[0032]

TABLE 7

Resource Table


RESOURCE_ID	Unique identifier for the
	resource
RESOURCE_TYPE	Type of resource (FAX,
	VOICE, etc.)
RESOURCE_STATUS	Status of resource (Active,
	Inactive, etc.).
RESOURCE_QUEUE_STATUS	Status of the Queue, num-
	ber of messages in queue
RESOURCE_TIME_ZONE	Time zone for the resource
RESOURCE_QUEUE_MAX	Maximum size of the re-
	source queue
RESOURCE_ADDRESS	Address of the resource (IP
	address, etc.)
RESOURCE_NAME	Name of the resource
RESOURCE_EXPIRY_DURATION	Expiry duration for any
	message sent to the speci-
	fied resource
RESOURCE_QUEUE_IN_STATUS	Number of messages wait-
	ing to be delivered by the
	resource
RESOURCE_COMMUNICATION_TYPE	Method used to communi-
	cate with resource (HTTP,
	SHTTP, etc.)

[0033]

TABLE 8

Resource Rates Table


RESOURCE_ID	Unique identifier for the resource
RESOURCE_PREFIX	Any digits to be dialed before an
	actual number
RESOURCE_CITY_NAME	Name of destination city for the
	message to be delivered
RESOURCE_PROVIDER_RATE	Rate for a particular city (dollars per
	second, etc.)
RESOURCE_MAX_DIGITS	Max number of digits allowed to be
	dialed
RESOURCE_AREA_CODE	Area code for the particular city

[0034] FIGS. 4a and 4b are a flow diagram of the processing performed by router/filter 23 using Tables 1–8. When a message is received it is placed into message queue 21 which is simply a storage area, the specifics of which, including the mechanism for placing the message into the queue are well known. Certain details concerning the message are also stored in a message queue table (Table 1). In step 41, router/filter, which is a computer program running on processing server 19, polls the message queue table for pending requests as determined by the existence of an active message in the message status field. If no message is found, after a system defined delay, the message queue table is again polled (step 43). Once a message has been found in the table, processing continues with step 45 by determining the message type using the message_type field in Table 1 and the file type information in Table 2. The customer is then validated using information in Table 3 in step 47. In step 49, currency information for the customer is obtained from Table 4. The message is then filtered for possible pager notification using the information in Table 5 in step 51. In step 53, Table 7 is used to check for available resources to deliver the message. In step 55, the rates of available resources are checked to determine the least cost resource using Table 8. Then in step 59, the message is delivered using the determined least cost resource. After the message has been delivered, or after an error in the delivery has occurred, in step 59, a response/receipt is composed using Table 6. In step 61, the response or receipt is delivered to the sender. The system then begins the process over again at step 41.

[0035] As noted above outbound resource 31 is equivalent to communications server 550 as described in U.S. Pat. No. 6,208,638. The modifications made to outbound resource to enable it to operate in a system having an architecture as described herein are as follows.

[0036] These changes will be described with reference to the message structure of received messages.

Message Structure

[0037] Each field has a value following an ‘=’ sign and is terminated by a newline character. The exception to this is the “Message” field where a newline immediately follows the “=” sign and the actual message follows on the next line.

[0038] The fields of a message are as follows:

- [0039] Password=
[0040] MessagelD=
[0041] MessageStatus=
[0042] MessageSentTimeStamp=
[0043] Message Duration=
[0044] MessageLength=
[0045] Message RemoteCSID=
[0046] MessageSourceCSID=
[0047] MessageAttachStatus=
[0048] MessageDestination=
[0049] ResourcelD=
[0050] ResourceStatus=
[0051] ResourceLastCommTimeStamp=
[0052] ResourceExpiryDuration=
[0053] ResourceQueuelnStatus=
[0054] ResourceQueueOutStatus=
[0055] ResourceChannelMax=
[0056] ResourceChannelStatus=
[0057] MessageBoundary=
[0058] Message=

[0059] In the following explanation of the above fields, the text in brackets at the end indicates the entity providing the value for the field in the forward/reverse direction (i.e., from router/filter 23 (RF) to outbound resource 31 (RESOURCE), and from RESOURCE to RF, respectively). “NA” indicates that no value is applicable, and the text “NA” is used to populate the field. “Same” indicates that the same value is used in the reverse direction, i.e, the RESOURCE does not modify the value; it only echoes the value it receives in that field.

[0060] Password—There is a fixed password pair for each RESOURCE and RF combination. RESOURCE stores the RF password in a flat text password file in a directory (jfaxom), and RF stores the RESOURCE password in the database. (RF/RESOURCE).
[0061] MessageID—Unique ID, per message, generated by RESOURCE. (RESOURCE/Same).
[0062] MessageStatus—Code indicating current status of the message. See Status codes below. (RF/RESOURCE)
[0063] MessageSentTimeStamp—Time stamp indicating date/time the message was delivered to the final destination by RESOURCE. (NA/RESOURCE)
[0064] MessageDuration—Time (in seconds) to transmit message from RESOURCE. (NA/RESOURCE)
[0065] Messagelength—Number of pages transmitted by RESOURCE. (NA/RESOURCE)
[0066] MessageRemoteCSID—called subscriber identification (CSID) of fax machine to which message was transmitted. (NA/RESOURCE)
[0067] MessageSourceCSID—Source CSID. This may be customized per customer. (RF/Same)
[0068] MessageAttachStatus—Value of “A” indicates a message is attached for delivery. (RF/RESOURCE)
[0069] MessageDestination—Destination phone number. (RF/Same)
[0070] ResourceID—Unique ID, per resource, stored in the database. (RF/Same)
[0071] ResourceStatus—Code indicating the current status of the resource, i.e., whether it is active or not. RF uses this to determine whether further messages should be sent to RESOURCE for delivery. See Status codes below. (NA/RESOURCE)
[0072] ResourceLastCommTimeStamp—Date/time of last communication between RF and RESOURCE. (RF/RESOURCE)
[0073] ResourceExpiryDuration—Life of message (in minutes) on RESOURCE. If a message has not been delivered to the final destination by RESOURCE within this amount of time, the message is considered “expired” and is discarded.
[0074] ResourceQueueInStatus—Number of messages waiting to be processed in an Inbox directory on RESOURCE. (NA/RESOURCE)
[0075] ResourceQueueOutStatus—Number of messages waiting to be processed in an Outbox directory on RESOURCE. (NA/RESOURCE)
[0076] ResourceChannelMax—Number of channels available for use on RESOURCE. (NA/RESOURCE)
[0077] ResourceChannelStatus—Channel activity status, e.g., 0000000111000001, where 0's indicate an idle channel and 1's indicate a busy channel. (NA/RESOURCE)
[0078] MessageBoundary—Text for MIME boundary. (RF/NA)
[0079] Message—Actual MIME message sent by RF. If MessageAttachStatus=NA, no message follows this tag.

[0080] All fields are NA if not used.

Date fields are expressed in MMDDYYhhmmss format.

[0081] Resource Status Codes are:

[0082] A—Active
[0083] I—Inactive

[0084] Message Status Codes are:

[0085] P—Pending
[0086] H—On Hold
[0087] D—Deferred
[0088] R—Ready for sending to RESOURCE
[0089] X—Exchanged, i.e., sent to RESOURCE but not acknowledged by it.
[0090] A—Sent to RESOURCE and acknowledged by it.
[0091] S—Sent (i.e., receipt for final delivery received from RESOURCE)

[0092] Normal sequence for Message delivery by RESOURCE is:

[0093] RF receives a request in its queue (message queue 21).
[0094] RF sends the message to RESOURCE.
[0095] RESOURCE gets message, authenticates password, and creates a new message in the Inbox directory.
[0096] RESOURCE acknowledges receipt of message.
[0097] RESOURCE processes the message in Inbox (MessageStatus=A, MessageAttachStatus=A).
[0098] RESOURCE moves message to a Process directory for further processing.
[0099] RESOURCE finishes processing message and delivers it to final destination.
[0100] RESOURCE removes the message from the Process directory.
[0101] RESOURCE creates a message in Outbox directory. (MessageStatus=S). If a “reply message” is to be delivered to the original sender, MessageAttachStatus=A, else MessageAttachStatus=NA. MessageID remains the same in either case.
[0102] RESOURCE delivers receipt (with “reply message,” if applicable) to RF.
[0103] RF receives the message and puts it in the Queue for database processing.

[0104] Processing server 19 with the above described functionality may be implemented using readily available systems such as a Windows NT server or a UNIX server. Database 27 may be implemented as a database server using readily available systems such as a Windows NT server or a UNIX server running, for example a SQL database.

[0105] What follows is a detailed description of FIGS. 5–7 which set forth a method and apparatus for allowing the receipt and transmission of audio and fax information between a circuit switched network and a packet switched network, as described in U.S. Pat. No. 6,208,638. For purposes of explanation, specific embodiments are set forth to provide a thorough understanding of the present invention. However, it will be understood by one skilled in the art, from reading this disclosure, that the invention may be practiced without these details. Further, although the system is described through the use of circuit switched and packet switched networks, most, if not all, aspects apply to all networks in general.

[0106] FIG. 5 contains a block diagram illustrating an embodiment of a system containing a communications server 550 connected to a circuit switched network 530 and a wide area network (WAN) 580. In an embodiment, the circuit switched network 530 is a circuit switched network such as the PSTN while WAN 580 is a packet switched network such as the Internet. It is to be noted that circuit switched network 530 can also be a network such as the generalized switched telephone network (GSTN), which encompasses PSTN networks, cellular telephone networks, and the other networks with which they are in communication.

[0107] Communications server 550 is connected to circuit switched network 530 via a switch 540 and to WAN 580 through the use of a router 585. As described in further detail below, in an embodiment, switch 540 and router 585 are interfaced to communications server 550 using two separate hardware interfaces. In an alternate embodiment, switch 540 and router 585 can be interfaced to communications server 550 through the use of one hardware unit.

[0108] Connected to circuit switched network 530 is both a telephone unit 510 and a facsimile unit 520. Telephone unit 510 is a standard telephone capable of converting audio signals into electrical signals suitable for transmission over circuit switched network 530. Similarly, facsimile unit 520 is a standard facsimile machine capable of transmitting and receiving facsimile messages over circuit switched network 530. Each of these devices can be connected to circuit switched network 530 using either wired or wireless technology.

[0109] Connected to WAN 580 is a database server 595, a system management unit 597, a mail server 560, and a client 590. Each of these systems communicate with each other and with communications server 550 via WAN 580 using such protocols such as simple network management protocol (SNMP) and hyper-text transport protocol (HTTP)—packetized using a protocol such as the transmission control protocol/internet protocol (TCP/IP).

[0110] In an embodiment, each one of database server 595, system management unit 597, mail server 560, and client 590, are stand-alone computers or workstations containing the hardware and software resources to enable operation. In alternate embodiments, the functions provided by each one of database server 595, system management unit 597, mail server 560, and client 590, are provided by any number of computer systems.

[0111] In an embodiment, mail server 560 is a server providing e-mail receipt and transmission using a protocol such as the simple mail transfer protocol (SMTP) and post office protocol (POP). Moreover, client 590 is configured to be able to communicate over WAN 580 using SMTP or POP in order to retrieve e-mail from mail server 560 or another suitably configured server.

[0112] System management unit 597 communicates with communications server 550 to monitor: (1) the processes on communications server 550; (2) the status of the trunk line connected to communications server 550; and (3) the connection between the various servers connected to WAN 580. As described below, if any processes on communications server 550 or connection to the circuit switched network 530 is interrupted, system management unit 597 can allocate resources, or cause the re-routing of a call or message via one or more redundant resources or connections, ensuring that the call or message is routed to the final destination.

[0113] Communications server 550 contains user data needed to receive and route incoming messages received from circuit switched network 530. The same information is also stored on database server 595. In an embodiment, communications server 550 stores an inbound address, a set of final destination addresses; and an account status for each user. The inbound address corresponds to the telephone number assigned to the user. As further discussed below, the inbound address is the number that a message sender dials on telephone unit 510 or facsimile unit 520 to leave a message for the user. The set of final destination address contain one or more e-mail addresses where the user account status information indicates whether the inbound address is either active and or inactive—i.e, whether the user is able to receive messages using the system.

[0114] Database server 595 stores a duplicate copy of the inbound address, the set of final destination addresses; and the account status for each user. Database server 595 also stores additional information for each user such as mailing address and billing information which are not used in the operation of the present invention but are note herein for completeness only. Thus, the information that is stored on communications server 550 is a subset of the information that is stored on database server 595, and if communications server 550 were to become inoperable or otherwise unable to handle incoming messages, database server 595 can configure another communications server to accept those calls.

[0115] In an embodiment, system management unit 597 is responsible for monitoring the status of communications server 550 and re-assigning the users being handled by communications server 550 if communications server malfunctions or becomes overloaded with incoming calls. In the former case, system management unit 597 would re-assign all users being handled by communications server 550 to another communications server. In the latter case, system management unit 597 would only off-load the only those incoming calls for which communications server 550 does not have the available resources to process.

[0116] FIG. 6 is a block diagram of communications server 550 configured in accordance with an embodiment containing a processor 651 coupled to a memory subsystem 653 through the use of a system bus 655. Also coupled to system bus 655 is a network interface 656; a trunk interface 652; and a set of fax/voice processing resources 654. Set of fax/voice processing resources 654 and trunk interface 652 are also coupled to a bus 657.

[0117] Bus 657 is a bus that supports time division multiplex access (TDMA) protocols to optimize the flow of real time traffic between set of fax/voice processing resources 654 and trunk interface 652.

[0118] Memory subsystem 653 is used to store information and programs needed by communications server 550. The functioning of memory subsystems in computer design are well known to those of ordinary skill in the art and thus will not be further discussed herein.

[0119] In an embodiment, trunk interface 652 is a trunk line interface, such as a T-1 or E-1 line, to switch 540 and can handle up to 24 channels of communications. Trunk line signaling is well known to those of ordinary skill in the art of telecommunication and thus will not be further discussed herein except as necessary for describing the invention.

[0120] Set of fax/voice processing resources 654 are made up of multiple fax/voice processing cards. Each of these processing cards contain processing units which are capable of receiving and transmitting facsimiles according to established protocols, and which are capable of digitizing voice or other audio data, also according to established protocols. In an embodiment, there are three fax/voice processing cards in set of fax/voice processing resources 654, each fax/voice processing card containing eight processing units capable of handling a channel from trunk interface 652. Thus, communications server 550 can communicate on twenty-four channels concurrently.

[0121] The storage of destination addresses on both circuit switched network 530 and WAN 580 is controlled by a database located either on communications server 550 or on database server 595. Keeping this information separate from communications server 550 allows communications server 550 to be a resource that can be allocated on demand. Hence, a number of communications servers could be used, along with one or more database servers, to allow a fully redundant and scalable system. In addition, system management unit 597 monitors the status and connection of all the communication and database servers.

[0122] FIG. 7 is a flow diagram illustrating the operations of an embodiment of the present invention when a call originating from a source on the circuit switched network 530. For example, either telephone unit 510 or facsimile unit 520 can initiate the call.

[0123] In block 700, an incoming call signal is received by communications server 550 from switch 540. The incoming call signal is initiated by telephone unit 510 or facsimile unit 520 over circuit switched network 530 and is routed to communications server 550 via switch 540. Communications server 550 detects the incoming call signal using trunk interface 652. Operation would continue with block 702.

[0124] Continuing with block 702, trunk line interface unit 652, in addition to receiving signals to indicate that there is an incoming call from switch 540, also receives signals indicating the circuit destination address of the incoming call. The destination address is captured by trunk interface 652 and is determined by trunk line signaling using mechanisms such as direct-inward-dial, or dual tone multifrequency (DTMF) tones.

[0125] Continuing with block 704, to determine whether or not to process the incoming call, processor 651 searches the list of inbound addresses contained in memory subsystem 653 for the destination address. If processor 651 finds the destination address in the inbound address list, processor 651 will then look up the account status for the user who owns the inbound address to determine if the account of that user is a valid user account. In an alternate embodiment, the validation is performed through the use of a database maintained by a separate entity such as database server 595. If the account is found to be inactive, communications server 651 will play a prepared message indicating that the number to which the incoming message was sent is an invalid account.

[0126] In block 706, once the validity of the user account has been established, processor 651 will attempt to allocate one fax/voice processing resource from set of fax/voice processing resources 654 and also determine the availability of other resources required for the receipt and processing of the incoming call. These other resources include the processing capacity of processor 651, the storage capacity of memory subsystem 653.

[0127] If it is determined that the appropriate resources are not available, then the call will be routed to a different communications server that is capable of allocating the necessary resources. The routing of calls is accomplished by trunk line signaling via switch 540 and is managed by system management unit 597.

[0128] Also, it should be noted that the call will only come from switch 540 to communications server 550 if there are no problems with the line. Otherwise the call will get routed to a different communications server. In an embodiment, fault detection and correction happens in one of two ways. First, on the telephone network side, switch 540 can be set up to independently route a call to another line if it is determined that one of the lines is bad. Second, if communications server 550 detects that the trunk line coming into trunk interface 652 is down, communications server 550 will notify system management unit 597 to reallocate the users for whom communications server 550 is responsible onto another communications server. Thus, system management unit 597 will transfer the duplicate user information contained in database server 595 into a different communications server.

[0129] In block 708, communications server 550 “answers” the incoming call by having trunk interface 652 go “off-hook” on the trunk line.

[0130] In block 710, if the fax/voice processing resource of set of fax/voice processing resources 654 which is processing the call determines that the incoming call is a fax transmission, then operation will continue with block 712. Otherwise, operation will continue with block 714. For example, if the call is a fax, a fax protocol is initiated, and the fax is received by one of the fax/voice processing resources of set of fax/voice processing resources 654. If the call is a voice call, the voice is recorded by one of the fax/voice processing resources of set of fax/voice processing resources 654.

[0131] In block 712, the fax/voice processing resource of set fax/voice processing resources 654 responsible for processing the incoming call will perform the fax transfer and store the incoming message as a temporary file in memory subsystem 653. In an embodiment, the incoming fax is saved into a file which follows the group 3 facsimile file format. Operation will then continue with block 716.

[0132] In block 714, where it is determined that the incoming message is an audio message, the fax/voice processing resource of set of fax/voice processing resources 654 allocated to process the call will initiate an audio recording of the incoming voice message. In an embodiment, the audio message is digitized and stored in memory subsystem 653 as a temporary file in a pulse code modulated format. After the incoming call has been digitized and stored, operation will then continue with block 716.

[0133] In block 716, trunk interface 652 will terminate the call. Operation will then continue with block 718.

[0134] In block 718, the incoming message, which has been stored as a temporary file in memory subsystem 653, is processed by processor 651. In an embodiment, the temporary file is processed according to the type of the incoming call. If the incoming call was a fax transmission, then the temporary file, which has been stored as a group 3 facsimile file, will be converted into a file which follows the tagged image file format (TIFF), or a format that is suitable for transmission over WAN 580. Optionally, the temporary fax file can also be compressed at this stage. If the incoming call was an audio message, then the temporary file would be compressed using a compression scheme such as the scheme defined in the global system for mobile-communications (GSM) standard. In alternate operations, compressing and other processing of the incoming message is performed as the same time the incoming message is being received and being placed in memory subsystem 653.

[0135] In block 720, communications server 550 uses the inbound address to determine the set of final destination addresses, which are destinations on WAN 580 (i.e., the packet switched network), to send the processed incoming message. Communications server 550 then sends an electronic mail (e-mail) with the processed incoming message as an attachment to all the destinations in the set of final destination addresses.

[0136] For example, the e-mail containing the attachment is transferred to, and stored in, a server such as mail server 560, The e-mail is then retrieved by client 590 whenever the user wishes. In an alternate embodiment, client 590 can retrieve the e-mail directly from communications server 550, without the storing operation of mail server 560.

[0137] While the present invention has been particularly described with reference to the various figures, it should be understood that the figures are for illustration only and should not be taken as limiting the scope of the invention. Many changes and modifications may be made to the invention, by one having ordinary skill in the art, without departing from the spirit and scope of the invention.

Claims

Post-issuance certificates present

The text shown below may not reflect later post-issuance changes.

What is claimed is:

1. A system for supporting a message delivery service, comprising:

a server coupled to communicate with a plurality of first outbound resources and a database server, over an internal packet-switched data network, the database server containing account information on customers of the message delivery service, the server implements a router-filter and a message queue,

the message queue to store a request message received from a customer of the message delivery service over an external packet-switched data network,

the router-filter to obtain a request message from the queue, validate said request message by accessing the account information in the database server, and determine to which of the plurality of first outbound resources to assign said request message,

each of the first resources being capable of converting an input request message into a format capable of being received by a fax machine over a circuit switched network.

2. The system of claim 1 wherein the internal data network is a private data network.

3. The system of claim 2 wherein the external data network is the Internet.

4. The system of claim 3 wherein the request message is received from the customer via one of a mail transport protocol server and a hypertext transport protocol server on the Internet.

5. The system of claim 1 wherein the router-filter is to prioritize a plurality of request messages that have been obtained from the queue and that are assigned to an outbound resource.

6. The system of claim 1 wherein the router-filter is to determine which of the plurality of first outbound resources to assign said request message to, based on which resource offers the least cost of delivering said request message.

7. The system of claim 1 wherein the router-filter is to generate an error message that indicates an error in delivering said request message as reported by the outbound resource to which said request message was assigned.

8. The system of claim 1 further comprising:

a plurality of second outbound resources each being capable of converting an input request message into a format capable of being played back to a telephone over a circuit switched network, wherein the router-filter is to determine to which of the first and second resources said request message is to be assigned, based on a message type of said request matching a capability of one of a first resource and a second resource.

9. The system of claim 1 further comprising:

a plurality of second outbound resources each being capable of converting an input request message into a format capable of being transmitted to a paging terminal over one of (1) a circuit switched network and (2) a paging gateway over an external packet-switched network, wherein the route-filter is to determine to which of the first and second resources said request message is to be assigned, based on a message type of said request matching a capability of one of a first resource and second resource.

10. The system of claim 1 wherein a location of each outbound resource is given by an Internet Protocol address.

11. The system of claim 1 wherein the message is received from the customer via one of a mail transport protocol server and a hypertext transport protocol server on the Internet.

12. The system of claim 1 wherein a protocol used by the router-filter to communicate with the plurality of outbound resources is one of HTTP and SHTTP.

13. The system of claim 1 wherein the router-filter is to send a MIME message.

14. An article of manufacture for supporting a message delivery system, comprising:

a machine accessible medium containing data that, when accessed by a machine, cause a server to communicate with an outbound resource and a database all as part of an internal packet-switched data network, the server to store a request message received from a customer of the message delivery service over an external packet switched data network, verify that the request message is from the customer using information in the database, and assign said request message to the resource which converts data associated with said request message into a format capable of being received by a fax machine over a circuit switched network.

15. The article of manufacture of claim 14 wherein the medium includes further data which allows the request message to be received from a customer over the Internet.

16. The article of manufacture of claim 14 wherein the medium includes further data which, when executed by the machine, cause the server to determine which of a plurality of first outbound resources to assign said request message to, based on which resource offers the least cost of delivering said request message.

17. A method comprising:

receiving an email message from an external packet data network;

performing a database lookup in an internal packet data network to correlate the email message with a user account;

verifying within the internal network the email message is associated with a valid user account;

performing within the internal network one of a least cost routing calculation, a billing calculation, a prioritization calculation, and a message filtering operation;

converting within the internal network the email message into a fax format for transmission to a machine; and

transmitting the converted email message into a public switched telephone network to a destination telephone number.

18. A method comprising:

receiving an email message from the Internet;

performing within an internal packet data network a database lookup to correlate the email message with a user account;

determining within the internal packet data network if the email message passes a filter screening criterion;

converting the email message into a fax format for transmission to a fax machine; and

transmitting the converted email message into a public switched telephone network to a destination telephone number.

19. A method comprising:

receiving an email message from the Internet;

performing a database lookup within an internal packet data network to correlate the email message with a user account;

queuing the email message within the internal packet data network;

reading the queued message based on a prioritized ordering rule within the internal packet data network;

converting the read message into a fax format for transmission; and

transmitting the converted message into a public switched telephone network to a destination telephone number associated with the user account.

20. A method comprising:

receiving in an internal packet data network an email message from the Internet;

correlating the email message with a user account in the internal packet data network;

queuing email the message in the internal packet data network;

performing a routing operation to determine a destination to forward the email message;

converting the routed message into a fax format; and

transmitting the converted message into a public switched telephone network to a destination telephone number associated with the user account and determined in said routing.

Patent Citations (56)

Patent	Date	Inventor	Cited By
US4941170(A)	1990-07-01	Herbst	Applicant
US5115326(A)	1992-05-01	Burgess et al.	Applicant
US5193110(A)	1993-03-01	Jones et al.	Applicant
US5333266(A)	1994-07-01	Boaz et al.	Applicant
US5339156(A)	1994-08-01	Ishii	Applicant
US5406557(A)	1995-04-01	Baudoin	Applicant
US5479411(A)	1995-12-01	Klein	Applicant
US5487100(A)	1996-01-01	Kane	Applicant
US5513126(A)	1996-04-01	Harkins et al.	Applicant
US5561703(A)	1996-10-01	Arledge et al.	Applicant
US5568536(A)	1996-10-01	Tiller et al.	Applicant
US5568540(A)	1996-10-01	Greco et al.	Applicant
US5579472(A)	1996-11-01	Keyworth, II et al.	Applicant
US5604788(A)	1997-02-01	Tett	Applicant
US5608786(A)	1997-03-01	Gordon	Applicant
US5621727(A)	1997-04-01	Vaudreuil	Applicant
US5675507(A)	1997-10-01	Bobo, II	Applicant
US5712907(A)	1998-01-01	Wegner et al.	Applicant
US5740231(A)	1998-04-01	Cohn et al.	Applicant
US5742668(A)	1998-04-01	Pepe et al.	Applicant
US5742905(A)	1998-04-01	Pepe et al.	Applicant
US5758088(A)	1998-05-01	Bezaire et al.	Applicant
US5761201(A)	1998-06-01	Vaudreuil	Applicant
US5761396(A)	1998-06-01	Austin et al.	Applicant
US5765033(A)	1998-06-01	Miloslavsky	Applicant
US5812786(A)	1998-09-01	Seazholtz et al.	Applicant
US5870454(A)	1999-02-01	Dahlen	Applicant
US5937161(A)	1999-08-01	Mulligan et al.	Applicant
US5940476(A)	1999-08-01	Morganstein et al.	Applicant
US5991292(A)	1999-11-01	Focsaneanu et al.	Examiner
US5999525(A)	1999-12-01	Krishnaswamy et al.	Applicant
US5999594(A)	1999-12-01	Mizoguchi et al.	Applicant
US5999965(A)	1999-12-01	Kelly	Examiner
US6020980(A)	2000-02-01	Freeman	Applicant
US6025931(A)	2000-02-01	Bloomfield	Applicant
US6073165(A)	2000-06-01	Narasimhan et al.	Examiner
US6185603(B1)	2001-02-01	Henderson et al.	Applicant
US6208638(B1)	2001-03-01	Rieley et al.	Examiner
US6212550(B1)	2001-04-01	Segur	Applicant
US6215858(B1)	2001-04-01	Bartholomew et al.	Applicant
US6216173(B1)	2001-04-01	Jones et al.	Applicant
US6246983(B1)	2001-06-01	Zou et al.	Applicant
US6259533(B1)	2001-07-01	Toyoda et al.	Applicant
US6263064(B1)	2001-07-01	O'Neal et al.	Applicant
US6330079(B1)	2001-12-01	Dugan et al.	Applicant
US6339591(B1)	2002-01-01	Migimatsu	Applicant
US6341160(B1)	2002-01-01	Tverskoy et al.	Applicant
US6350066(B1)	2002-02-01	Bobo, II	Applicant
US6356356(B1)	2002-03-01	Miller, Jr. et al.	Applicant
US6359881(B1)	2002-03-01	Gerszberg et al.	Examiner
US6510438(B1)	2003-01-01	Hasegawa	Applicant
US6564321(B1)	2003-05-01	Bobo, II	Applicant
US6597688(B1)	2003-07-01	Narasimhan et al.	Applicant
GB2024561(A)	1980-01-01		Applicant
GB2157117(A)	1985-10-01		Applicant
JP406164645	1994-06-01		Applicant

Non-Patent Literature (18)

jFax Personal telecomTM, http://www.jfax.net/, Dec. 4, 1994 4:57 p.m. (pp.1-2); and www.jfax.net/software.htm, Dec. 4, 1996 5:22 p.m. (pp.1-2).Applicant
Oracle & NT Software Library, Faxmail Networks for Windows v5.13 Fax over a network; Search results of online search, Dec. 5, 1996 12:03 p.m. (pp. 1-3).Applicant
Alta Vista Search, SHAREWARE.COM: Search results, Dec. 5, 1995 11:41 a.m. (pp. 1-2).Applicant
YahooTM Internet Life, vol. 3, No. 1, Jan. 1997 “Cooltools” (p. 73).Applicant
NetScan KOFAX, http://www.netscan.kofax.com/, Dec. 13, 1006 4:09 p.m. (pp. 103); http://www.netscan.kofax.com/brochure.html, Dec. 13, 1996 4:13 p.m. (pp. 1-4); and http://www.netscan.kofax.com/brochure2.html, Dec. 13, 1996 4:23 p.m. (pp. 1-3).Applicant
Electronics, Jan. 18 1979 (379-100), S9054 0063 (pp. 69-70).Applicant
“Unified Messaging Solutions On the Road”, Mar. 7, 1995, Computer Telephony Expo, Dallas Texas.Applicant
j2 Global Communications, Inc. v. Venali, Inc. United States District Court Central District of California, Case No. CV04-01172 DDP (AjWx), Defendant Venali, Inc.'s Objections and Responses to Plaintiff j2 Global Communications, Inc.'s First Set of Interrogatories (Nos. 1-7) (19 pages).Applicant
“Guide to Intelligent Least Cost Routing”, RightFAX, Inc. Tucson, Arizona, USA (1997) (pp. 1-17).Applicant
“Guide to Internet Faxing”, RightFAX, Inc., Tucson, Arizona, USA (1997) (pp. 1-16).Applicant
“Rightfax Ships Internet Connectivity Module for Lan Fax Software”, RightFAX News Research, RightFAX, Inc., Tucson, Arizona, USA, Feb. 10, 1997 (2 pages).Applicant
“RightFAX Poised for Internet Faxing”, Right FAX News Release, RightFAX, Inc., Tucson, Arizona, USA, May 27, 1997 (2 pages).Applicant
“RightFAX Introduces New Fax Server Designed for the Enterprise”, RightFAX News Research, RightFAX, Inc., Tucson, Arizona, USA, May 27, 1997 (3 pages).Applicant
Brett Mendel, “Net Faxing Awaits Its Day”, LAN Times, Dec. 9, 1996, v13 n27 p. 25 (2 pages).Applicant
Paul Kinnucan, “What's New in the Fax World”, Systems Integration, Feb. 1990, v23 n2 p. 50(7) (4 pages).Applicant
Lyle Deixler, “Fax Forges Ahead”, Teleconnect, Nov. 1996, v14 n11 p. 52(12) (5 pages).Applicant
Fax Solutions, LAN Times, Sep. 23, 1996, v13 n21 p. 123(5) (10 pages).Applicant
Tomaru, “Electronic Mails Systems”, 1983, Japan Annual Review in Electronics, Computers and Telecommunications, vol. 9, Telecomminication Technology, pp. 283-290.Applicant

US 7,020,132 B1Grant

Scalable architecture for transmission of messages over a network

Issue Date:2006-03-28

•20 Claims

•9 Drawing Sheets

Abstract

Metadata

Assignee

j2 Global Communications, Inc.

Inventors

Anand Narasimhan
Yaacov Shemesh
Amit Kumar

Application Information

Application Number:US 10/393,227

Filing Date:2003-03-20

Priority Date:1998-06-12

Art Unit:2667

Classifications

IPC:

H04L12/66

Patent Drawings (9 sheets)

Description

[0001] This is a continuation of Ser. No. 09/097,307, now U.S. Pat. No. 6,597,688 filed on Jun. 12, 1998.

Background of the Invention

[0002] 1. Field of the Invention

[0004] 2. Description of Related Art

Summary of the Invention

Brief Description of the Drawings

[0010] FIG. 1 is a block diagram of a prior art architecture which performs the functions, but not the scalability of the architecture of the present invention.

[0011] FIG. 2 is a block diagram illustrating the architecture of the present invention.

[0012] FIG. 3 is a block diagram showing the data/control flow through message queue 21, router/filter 23 and database 27.

[0013] FIG. 4 (4a and 4b) is a flow diagram of the processing performed by router/filter 23.

[0014] FIG. 5 is a system diagram of a network containing a message server.

[0015] FIG. 6 is a block diagram illustrating the message server.

[0016] FIG. 7 is a flow diagram illustrating some operations.

Detailed Description of the Invention

[0020] In the case of faxes, the outbound resource is a server which dials the destination fax number and sends the fax.

[0021] In the case of voice messages, the outbound resource is a server which dials the destination telephone number and plays the voice message.

[0022] In the case of notification messages, the outbound resource is a server which dials out to the paging terminal or delivers the notification message through any appropriate paging gateway.

[0023] After the message (in whatever form) has been delivered, a receipt with details and an error log (if any) is sent back via a secure protocol to the message queue 21.

[0024] The receipt/error log messages are then processed by the router/filter which interfaces with a billing system (not shown) for customer account update.

[0026]

TABLE 1

Message Queue Table


MESSAGE_ID	This is a unique number
	assigned to each message
	that arrives in the system.
RESOURCE_ID	Unique number assigned to
	each Outbound Resource
RESOURCE_TYPE	Each Resource is identified
	by the type of messages
	it can deliver (e.g., FAX,
	VOICE, NOTIFY, etc.)
RESOURCE_ADDRESS	Location of the Resource
	(such as IP address)
MESSAGE_TO_EMAIL_ADDRESS	To: address of the message
MESSAGE_FROM_EMAIL_ADDRESS	From: address of the
	message
MESSAGE_LOCATION	Location of actual message
	on the Message Queue 21
MESSAGE_SIZE	Size of the message in
	bytes
MESSAGE_PRIORITY	Priority of the message
	(e.g., low, medium, high)
MESSAGE_CREATION_DATE	Timestamp identifying the
	date/time that the message
	was received by the system
MESSAGE_EXPIRY_DURATION	Amount of time after which
	the message becomes stale
MESSAGE_SCHEDULED_DATE	Scheduled delivery time-
	stamp for the message
MESSAGE_STATUS	Current status of the mes-
	sage (Active, Pending,
	Sent, etc.)
MESSAGE_ESTIMATED_COST	Estimated cost for the de-
	livery of the message
CUSTOMER_KEY	Unique number identifying
	the customer in the
	database
MESSAGE_PART_OF_BROADCAST	Flag identifying if the
	message is part of a larger
	broadcast list waiting to be
	delivered
BROADCAST_ID	Unique number identifying
	a broadcast list
COVERPAGE_ID	Unique number identifying
	a coverpage (if any) for
	a fax
MESSAGE_SUBJECT	Subject line of the message
	to be delivered
MESSAGE_DURATION	Duration of the message
	(delivery time of fax, or
	delivery time for a voice
	message, etc.)
MESSAGE_RATE	Rate for message delivery
	(dollars per second, etc.)
MESSAGE_SEND_DATE	Actual timestamp identify-
	ing when the message was
	delivered
MESSAGE_REMOTE_CSID	Identifier of the fax
	machine to which a FAX
	message was delivered
MESSAGE_TYPE	Type of message (e.g.,
	FAX, VOICE,
	NOTIFICATION, etc.)
RESOURCE_COMMUNICATION_TYPE	Protocol used to communi-
	cate with the resource
	(HTTP, SHTTP, etc.)
MESSAGE_LANGUAGE_CODE	Language used for delivery
	of a receipt or response,
	based on settings in the
	customer table
MESSAGE_PAGES	Number of pages of a
	message (used primarily for
	a fax)

[0027]

TABLE 2

File Type Table


FILETYPE_MESSAGE_TYPE	Identifier of a message type (FAX,
	VOICE, etc.)
FILETYPE_RESOURCE_TYPE	Identifier to determine a resource that
	can handle a particular file type
FILETYPE_EXTENSION	The filename extension that identifies
	a file type (e.g., WAV, TIF, JFX,
	AU, GSM, etc.)

[0028]

TABLE 3

Customer Table


CUSTOMER_KEY	Unique number identifying a customer in the
	database
FIRSTNAME	First name of customer
LASTNAME	Last name of customer
COMPANY	Company name of customer
ADDRESSLINE1	Company address
ADDRESSLINE2	Company address
CITY	Company city
MAILREGION	Company state or equivalent
MAILCODE	Zipcode or equivalent
COUNTRY	Company country
WORKNUMBER	Customer work phone number
HOMENUMBER	Customer home phone number
EMAILADDRESS	Email address of customer
COLLECTIONMETHOD	Collection method such as Credit card,
	Debit, etc.
BILLTYPE	e.g., Customer, Demo, free, corporate, etc.
STATUS	Status of customer, Active, Inactive, etc.
LANGUAGECODE	Language of customer, English, German, etc.
CURRENCYCODE	Currency for billing the customer, US
	Dollars, Pound Sterling, etc.

[0029]

TABLE 4

Currency Table


	FORMAT	Currency label
	CURRENCY_SYMBOL	Symbol for currency

[0030]

TABLE 5

Notification Table


CUSTOMERKEY	Unique number identifying a customer in the
	database
PAGERTYPECODE	Code to determine the kind of pager service
BBSNUMBER	Modem number for pager notification delivery,
	based on the pager type
PAGERNUMBER	Identifier number of the pager unit
PIN	PIN code for the pager unit
DISPLAYTYPE	Display type of the pager (numeric, alphanumeric,
	etc.)

[0031]

TABLE 6

Response_email Table


RESPONSE_ID	Unique ID for a response/receipt
	message to be sent to a customer
REPONSE_SUBJECT	Subject line of the response message
RESPONSE_FROM_EMAIL	From: line of the response message
RESPONSE_BODY	Actual text of the response message

[0032]

TABLE 7

Resource Table


RESOURCE_ID	Unique identifier for the
	resource
RESOURCE_TYPE	Type of resource (FAX,
	VOICE, etc.)
RESOURCE_STATUS	Status of resource (Active,
	Inactive, etc.).
RESOURCE_QUEUE_STATUS	Status of the Queue, num-
	ber of messages in queue
RESOURCE_TIME_ZONE	Time zone for the resource
RESOURCE_QUEUE_MAX	Maximum size of the re-
	source queue
RESOURCE_ADDRESS	Address of the resource (IP
	address, etc.)
RESOURCE_NAME	Name of the resource
RESOURCE_EXPIRY_DURATION	Expiry duration for any
	message sent to the speci-
	fied resource
RESOURCE_QUEUE_IN_STATUS	Number of messages wait-
	ing to be delivered by the
	resource
RESOURCE_COMMUNICATION_TYPE	Method used to communi-
	cate with resource (HTTP,
	SHTTP, etc.)

[0033]

TABLE 8

Resource Rates Table


RESOURCE_ID	Unique identifier for the resource
RESOURCE_PREFIX	Any digits to be dialed before an
	actual number
RESOURCE_CITY_NAME	Name of destination city for the
	message to be delivered
RESOURCE_PROVIDER_RATE	Rate for a particular city (dollars per
	second, etc.)
RESOURCE_MAX_DIGITS	Max number of digits allowed to be
	dialed
RESOURCE_AREA_CODE	Area code for the particular city

[0036] These changes will be described with reference to the message structure of received messages.

Message Structure

[0038] The fields of a message are as follows:

- [0039] Password=
[0040] MessagelD=
[0041] MessageStatus=
[0042] MessageSentTimeStamp=
[0043] Message Duration=
[0044] MessageLength=
[0045] Message RemoteCSID=
[0046] MessageSourceCSID=
[0047] MessageAttachStatus=
[0048] MessageDestination=
[0049] ResourcelD=
[0050] ResourceStatus=
[0051] ResourceLastCommTimeStamp=
[0052] ResourceExpiryDuration=
[0053] ResourceQueuelnStatus=
[0054] ResourceQueueOutStatus=
[0055] ResourceChannelMax=
[0056] ResourceChannelStatus=
[0057] MessageBoundary=
[0058] Message=

[0060] Password—There is a fixed password pair for each RESOURCE and RF combination. RESOURCE stores the RF password in a flat text password file in a directory (jfaxom), and RF stores the RESOURCE password in the database. (RF/RESOURCE).
[0061] MessageID—Unique ID, per message, generated by RESOURCE. (RESOURCE/Same).
[0062] MessageStatus—Code indicating current status of the message. See Status codes below. (RF/RESOURCE)
[0063] MessageSentTimeStamp—Time stamp indicating date/time the message was delivered to the final destination by RESOURCE. (NA/RESOURCE)
[0064] MessageDuration—Time (in seconds) to transmit message from RESOURCE. (NA/RESOURCE)
[0065] Messagelength—Number of pages transmitted by RESOURCE. (NA/RESOURCE)
[0066] MessageRemoteCSID—called subscriber identification (CSID) of fax machine to which message was transmitted. (NA/RESOURCE)
[0067] MessageSourceCSID—Source CSID. This may be customized per customer. (RF/Same)
[0068] MessageAttachStatus—Value of “A” indicates a message is attached for delivery. (RF/RESOURCE)
[0069] MessageDestination—Destination phone number. (RF/Same)
[0070] ResourceID—Unique ID, per resource, stored in the database. (RF/Same)
[0071] ResourceStatus—Code indicating the current status of the resource, i.e., whether it is active or not. RF uses this to determine whether further messages should be sent to RESOURCE for delivery. See Status codes below. (NA/RESOURCE)
[0072] ResourceLastCommTimeStamp—Date/time of last communication between RF and RESOURCE. (RF/RESOURCE)
[0073] ResourceExpiryDuration—Life of message (in minutes) on RESOURCE. If a message has not been delivered to the final destination by RESOURCE within this amount of time, the message is considered “expired” and is discarded.
[0074] ResourceQueueInStatus—Number of messages waiting to be processed in an Inbox directory on RESOURCE. (NA/RESOURCE)
[0075] ResourceQueueOutStatus—Number of messages waiting to be processed in an Outbox directory on RESOURCE. (NA/RESOURCE)
[0076] ResourceChannelMax—Number of channels available for use on RESOURCE. (NA/RESOURCE)
[0077] ResourceChannelStatus—Channel activity status, e.g., 0000000111000001, where 0's indicate an idle channel and 1's indicate a busy channel. (NA/RESOURCE)
[0078] MessageBoundary—Text for MIME boundary. (RF/NA)
[0079] Message—Actual MIME message sent by RF. If MessageAttachStatus=NA, no message follows this tag.

[0080] All fields are NA if not used.

Date fields are expressed in MMDDYYhhmmss format.

[0081] Resource Status Codes are:

[0082] A—Active
[0083] I—Inactive

[0084] Message Status Codes are:

[0085] P—Pending
[0086] H—On Hold
[0087] D—Deferred
[0088] R—Ready for sending to RESOURCE
[0089] X—Exchanged, i.e., sent to RESOURCE but not acknowledged by it.
[0090] A—Sent to RESOURCE and acknowledged by it.
[0091] S—Sent (i.e., receipt for final delivery received from RESOURCE)

[0092] Normal sequence for Message delivery by RESOURCE is:

[0093] RF receives a request in its queue (message queue 21).
[0094] RF sends the message to RESOURCE.
[0095] RESOURCE gets message, authenticates password, and creates a new message in the Inbox directory.
[0096] RESOURCE acknowledges receipt of message.
[0097] RESOURCE processes the message in Inbox (MessageStatus=A, MessageAttachStatus=A).
[0098] RESOURCE moves message to a Process directory for further processing.
[0099] RESOURCE finishes processing message and delivers it to final destination.
[0100] RESOURCE removes the message from the Process directory.
[0101] RESOURCE creates a message in Outbox directory. (MessageStatus=S). If a “reply message” is to be delivered to the original sender, MessageAttachStatus=A, else MessageAttachStatus=NA. MessageID remains the same in either case.
[0102] RESOURCE delivers receipt (with “reply message,” if applicable) to RF.
[0103] RF receives the message and puts it in the Queue for database processing.

[0129] In block 708, communications server 550 “answers” the incoming call by having trunk interface 652 go “off-hook” on the trunk line.

[0133] In block 716, trunk interface 652 will terminate the call. Operation will then continue with block 718.

Claims

Post-issuance certificates present

The text shown below may not reflect later post-issuance changes.

What is claimed is:

1. A system for supporting a message delivery service, comprising:

the message queue to store a request message received from a customer of the message delivery service over an external packet-switched data network,

each of the first resources being capable of converting an input request message into a format capable of being received by a fax machine over a circuit switched network.

2. The system of claim 1 wherein the internal data network is a private data network.

3. The system of claim 2 wherein the external data network is the Internet.

4. The system of claim 3 wherein the request message is received from the customer via one of a mail transport protocol server and a hypertext transport protocol server on the Internet.

5. The system of claim 1 wherein the router-filter is to prioritize a plurality of request messages that have been obtained from the queue and that are assigned to an outbound resource.

8. The system of claim 1 further comprising:

9. The system of claim 1 further comprising:

10. The system of claim 1 wherein a location of each outbound resource is given by an Internet Protocol address.

11. The system of claim 1 wherein the message is received from the customer via one of a mail transport protocol server and a hypertext transport protocol server on the Internet.

12. The system of claim 1 wherein a protocol used by the router-filter to communicate with the plurality of outbound resources is one of HTTP and SHTTP.

13. The system of claim 1 wherein the router-filter is to send a MIME message.

14. An article of manufacture for supporting a message delivery system, comprising:

15. The article of manufacture of claim 14 wherein the medium includes further data which allows the request message to be received from a customer over the Internet.

17. A method comprising:

receiving an email message from an external packet data network;

performing a database lookup in an internal packet data network to correlate the email message with a user account;

verifying within the internal network the email message is associated with a valid user account;

performing within the internal network one of a least cost routing calculation, a billing calculation, a prioritization calculation, and a message filtering operation;

converting within the internal network the email message into a fax format for transmission to a machine; and

transmitting the converted email message into a public switched telephone network to a destination telephone number.

18. A method comprising:

receiving an email message from the Internet;

performing within an internal packet data network a database lookup to correlate the email message with a user account;

determining within the internal packet data network if the email message passes a filter screening criterion;

converting the email message into a fax format for transmission to a fax machine; and

transmitting the converted email message into a public switched telephone network to a destination telephone number.

19. A method comprising:

receiving an email message from the Internet;

performing a database lookup within an internal packet data network to correlate the email message with a user account;

queuing the email message within the internal packet data network;

reading the queued message based on a prioritized ordering rule within the internal packet data network;

converting the read message into a fax format for transmission; and

transmitting the converted message into a public switched telephone network to a destination telephone number associated with the user account.

20. A method comprising:

receiving in an internal packet data network an email message from the Internet;

correlating the email message with a user account in the internal packet data network;

queuing email the message in the internal packet data network;

performing a routing operation to determine a destination to forward the email message;

converting the routed message into a fax format; and

transmitting the converted message into a public switched telephone network to a destination telephone number associated with the user account and determined in said routing.

Patent Citations (56)

Patent	Date	Inventor	Cited By
US4941170(A)	1990-07-01	Herbst	Applicant
US5115326(A)	1992-05-01	Burgess et al.	Applicant
US5193110(A)	1993-03-01	Jones et al.	Applicant
US5333266(A)	1994-07-01	Boaz et al.	Applicant
US5339156(A)	1994-08-01	Ishii	Applicant
US5406557(A)	1995-04-01	Baudoin	Applicant
US5479411(A)	1995-12-01	Klein	Applicant
US5487100(A)	1996-01-01	Kane	Applicant
US5513126(A)	1996-04-01	Harkins et al.	Applicant
US5561703(A)	1996-10-01	Arledge et al.	Applicant
US5568536(A)	1996-10-01	Tiller et al.	Applicant
US5568540(A)	1996-10-01	Greco et al.	Applicant
US5579472(A)	1996-11-01	Keyworth, II et al.	Applicant
US5604788(A)	1997-02-01	Tett	Applicant
US5608786(A)	1997-03-01	Gordon	Applicant
US5621727(A)	1997-04-01	Vaudreuil	Applicant
US5675507(A)	1997-10-01	Bobo, II	Applicant
US5712907(A)	1998-01-01	Wegner et al.	Applicant
US5740231(A)	1998-04-01	Cohn et al.	Applicant
US5742668(A)	1998-04-01	Pepe et al.	Applicant
US5742905(A)	1998-04-01	Pepe et al.	Applicant
US5758088(A)	1998-05-01	Bezaire et al.	Applicant
US5761201(A)	1998-06-01	Vaudreuil	Applicant
US5761396(A)	1998-06-01	Austin et al.	Applicant
US5765033(A)	1998-06-01	Miloslavsky	Applicant
US5812786(A)	1998-09-01	Seazholtz et al.	Applicant
US5870454(A)	1999-02-01	Dahlen	Applicant
US5937161(A)	1999-08-01	Mulligan et al.	Applicant
US5940476(A)	1999-08-01	Morganstein et al.	Applicant
US5991292(A)	1999-11-01	Focsaneanu et al.	Examiner
US5999525(A)	1999-12-01	Krishnaswamy et al.	Applicant
US5999594(A)	1999-12-01	Mizoguchi et al.	Applicant
US5999965(A)	1999-12-01	Kelly	Examiner
US6020980(A)	2000-02-01	Freeman	Applicant
US6025931(A)	2000-02-01	Bloomfield	Applicant
US6073165(A)	2000-06-01	Narasimhan et al.	Examiner
US6185603(B1)	2001-02-01	Henderson et al.	Applicant
US6208638(B1)	2001-03-01	Rieley et al.	Examiner
US6212550(B1)	2001-04-01	Segur	Applicant
US6215858(B1)	2001-04-01	Bartholomew et al.	Applicant
US6216173(B1)	2001-04-01	Jones et al.	Applicant
US6246983(B1)	2001-06-01	Zou et al.	Applicant
US6259533(B1)	2001-07-01	Toyoda et al.	Applicant
US6263064(B1)	2001-07-01	O'Neal et al.	Applicant
US6330079(B1)	2001-12-01	Dugan et al.	Applicant
US6339591(B1)	2002-01-01	Migimatsu	Applicant
US6341160(B1)	2002-01-01	Tverskoy et al.	Applicant
US6350066(B1)	2002-02-01	Bobo, II	Applicant
US6356356(B1)	2002-03-01	Miller, Jr. et al.	Applicant
US6359881(B1)	2002-03-01	Gerszberg et al.	Examiner
US6510438(B1)	2003-01-01	Hasegawa	Applicant
US6564321(B1)	2003-05-01	Bobo, II	Applicant
US6597688(B1)	2003-07-01	Narasimhan et al.	Applicant
GB2024561(A)	1980-01-01		Applicant
GB2157117(A)	1985-10-01		Applicant
JP406164645	1994-06-01		Applicant

Non-Patent Literature (18)

jFax Personal telecomTM, http://www.jfax.net/, Dec. 4, 1994 4:57 p.m. (pp.1-2); and www.jfax.net/software.htm, Dec. 4, 1996 5:22 p.m. (pp.1-2).Applicant
Oracle & NT Software Library, Faxmail Networks for Windows v5.13 Fax over a network; Search results of online search, Dec. 5, 1996 12:03 p.m. (pp. 1-3).Applicant
Alta Vista Search, SHAREWARE.COM: Search results, Dec. 5, 1995 11:41 a.m. (pp. 1-2).Applicant
YahooTM Internet Life, vol. 3, No. 1, Jan. 1997 “Cooltools” (p. 73).Applicant
NetScan KOFAX, http://www.netscan.kofax.com/, Dec. 13, 1006 4:09 p.m. (pp. 103); http://www.netscan.kofax.com/brochure.html, Dec. 13, 1996 4:13 p.m. (pp. 1-4); and http://www.netscan.kofax.com/brochure2.html, Dec. 13, 1996 4:23 p.m. (pp. 1-3).Applicant
Electronics, Jan. 18 1979 (379-100), S9054 0063 (pp. 69-70).Applicant
“Unified Messaging Solutions On the Road”, Mar. 7, 1995, Computer Telephony Expo, Dallas Texas.Applicant
j2 Global Communications, Inc. v. Venali, Inc. United States District Court Central District of California, Case No. CV04-01172 DDP (AjWx), Defendant Venali, Inc.'s Objections and Responses to Plaintiff j2 Global Communications, Inc.'s First Set of Interrogatories (Nos. 1-7) (19 pages).Applicant
“Guide to Intelligent Least Cost Routing”, RightFAX, Inc. Tucson, Arizona, USA (1997) (pp. 1-17).Applicant
“Guide to Internet Faxing”, RightFAX, Inc., Tucson, Arizona, USA (1997) (pp. 1-16).Applicant
“Rightfax Ships Internet Connectivity Module for Lan Fax Software”, RightFAX News Research, RightFAX, Inc., Tucson, Arizona, USA, Feb. 10, 1997 (2 pages).Applicant
“RightFAX Poised for Internet Faxing”, Right FAX News Release, RightFAX, Inc., Tucson, Arizona, USA, May 27, 1997 (2 pages).Applicant
“RightFAX Introduces New Fax Server Designed for the Enterprise”, RightFAX News Research, RightFAX, Inc., Tucson, Arizona, USA, May 27, 1997 (3 pages).Applicant
Brett Mendel, “Net Faxing Awaits Its Day”, LAN Times, Dec. 9, 1996, v13 n27 p. 25 (2 pages).Applicant
Paul Kinnucan, “What's New in the Fax World”, Systems Integration, Feb. 1990, v23 n2 p. 50(7) (4 pages).Applicant
Lyle Deixler, “Fax Forges Ahead”, Teleconnect, Nov. 1996, v14 n11 p. 52(12) (5 pages).Applicant
Fax Solutions, LAN Times, Sep. 23, 1996, v13 n21 p. 123(5) (10 pages).Applicant
Tomaru, “Electronic Mails Systems”, 1983, Japan Annual Review in Electronics, Computers and Telecommunications, vol. 9, Telecomminication Technology, pp. 283-290.Applicant