The various embodiments of the invention relate to the field of unified messaging through circuit and packet data networks.

Unified messaging has emerged to address the need for combining the delivery of different types of messages using a single interface. For example, US Patent No. 6,208,638, Rieley et. al., describes a method and apparatus for transmission and retrieval of information such as facsimile and audio messages over circuit and packet switched networks, specifically via the use of electronic mail. An incoming message (voice or fax) sent over a circuit switched network is transmitted over a packet switched network, by receiving an incoming call signal along with an inbound address, determining a user account and a final address on the packet network that are associated with the inbound address, and sending a processed form of the incoming message to an email box of the user. Another reference is US Patent No. 6,073,165, Narasimhan, et. al. which describes the use of filtering methods for processing electronic messages based on pre-defined filtering rules, and forwarding filtered messages to a receiving destination.

EP 1 104 964 discloses a unified instant messaging system that enables the nearly real-time transmission of messages.

EP 1 175 075 discloses a unified communications automated personal name addressing system.

WO 99/18716 discloses a system and method for storing and delivering messages.

Changtao Qu et al. disclose an implementation of an enterprise-level groupware system based on the J2EE platform and the WebDAV protocol.

WO 01/67622 discloses a system for messaging across cellular and public data networks. The system determines whether a recipient user is currently signed on to the system.

Although the above described patented techniques are quite effective in supporting a message delivery service, improvements are needed to provide a wider range of services.

One aspect of the invention is to provide a system according to claim 1 further having characteristics according to claims 2 to 47,

Another aspect of the invention is to provide a system according to claim 48 further having characteristics according to claims 49 to 57.

One embodiment of the present invention provides a method according to claim 58 further having characteristics according to claims 59 to 62.

Fig.1 shows a system for communication between networked objects, including an end-user interface device.

Fig. 2 shows an illustration of the elements of a preferred embodiment of an end-user interface device.

Fig. 3 illustrates the transport of facsimile messages to an end-user interface device or other object, via a multiplicity of transports, including electronic mail and instant messaging.

Fig. 4 illustrates the flow of signaling information between various elements of a preferred embodiment of the invention, for purposes of message delivery or disposition, routing, and handling of various aspects of communication between one or more end-users or elements of the invention.

Fig. 5 illustrates how a representation language can be used for the definition of the content and structure of the message or communication and any sub-components of the message or other related communication, and characteristics for determining the disposition of a message or communication, as used by a preferred embodiment of the invention.

Fig. 6 illustrates how descriptive rules and representation methods can be used for determining and managing the distribution and routing of messages and other communication to one or more end-users.

Fig. 7 shows a block diagram of another embodiment of the invention for supporting a message delivery service.

Fig.1 illustrates a preferred embodiment of the invention, wherein end-user devices, including telephones 120, 122, data telephones 121, facsimile (fax) devices 130,132, and computers 140,141,143, and other communication devices are connected to one or more networks, including circuit switched networks 100, data networks 110, 111 or other networks, via switching or routing elements that serve to direct and route data, these elements including circuit switches 101 or data network routers 150,151. The system further comprises one or more communication servers 160,161 that interface with one or more networks, such as circuit switched networks and data networks, through connections such as trunk interfaces 115, 116 or other physical or logical connections. In the preferred embodiment, interface 115 is an E1 or T1 interface capable of carrying several simultaneous data or voice connections. Such connections are well known in the prior art. Further, the system of the present invention includes databases 170, 171, call management system units 190, media gateways 152,153, storage systems 192, directory systems 194, and security systems for protection of data across networks, including systems such as firewalls 159. In the preferred embodiment, storage system 192 is an email storage system, or other data storage and archival system, physically or logically accessible over a data network, through standard network protocols, including but not limited to SMTP, POP, and IMAP. Directory system 194 may be any standard or proprietary directory system that provides information accessible over a data network, said information including but not limited to user information, profiles, addresses, calendars, and accessible through a variety of protocols, including but not limited to LDAP.

Fig. 2 describes the logical components of an end user device. Here, an end user uses application 240 to communicate or interact with other elements across a network, such as the ones shown in Fig. 1. Application Interface 235 may be a standardized interface that allows one or more applications to interact with the rest of the system components. Application Manager 232 performs the function of managing various applications, scheduling resources and connectivity with other elements of the system. Session Manager 230 is responsible for the management and administration of communication sessions, between one or more end user devices, or other elements of the system of the invention, a session being described as any communication or interaction, of a pre-specified or unspecified duration, structured or unstructured, supervised or unsupervised by one or more elements of the system of the present invention. Security unit 225 is responsible for handling of security for all aspects of communication, including signaling and data interchange between one or more elements of the invention, and being further responsible for various aspects of security, including but not limited to authentication, integrity, confidentiality, protection, and key management. Unit 225 may also interact with other security elements (not shown) accessible on a data network (110, 111). Monitoring unit 220 is responsible for the monitoring of various system elements, to ensure that performance metrics and other parameters that measure and ensure system performance are adhered to, and reported to locations that can further determine and administer their upkeep. Protocol adapters 245 include one or more interfaces to one or more protocols, standard or proprietary, that may be used for the exchange of signaling or data information across networks, and between similar or dissimilar end-users and other elements of the system of the present invention. These include, but are not limited to POP, IMAP, SMTP, LDAP, SQL, and SIP. Further, numerous applications are available in the art that further describe interfaces to these applications. Interfaces between these applications and the system of the invention are labeled as Enterprise Application Adapters 275. Network stack 215 describes these elements of the system that provide connectivity to a data network, through one or more communication protocols, for the exchange of signaling or other data information. Physical layer 210 describes the physical medium of the end-user interface, through which an end-user communicates.

Fig. 3 illustrates an embodiment of the invention, wherein a fax message is sent through the various network elements, and communicated with one or more end-users. Here, fax machine 326 is used to initiate a telephone call through switching unit 328 connected to circuit switched network unit 310. This call is transmitted through trunk interface unit 312, to a media gateway 330. Unit 330 may first digitize the call signaling information (if not done already) and then sends the call signaling information to call management system 340. The system 340 authenticates the call as a valid call intended for a specified end user, e.g. a customer of a message delivery service that operates the system 340, based on an inbound address specified by the calling fax machine, which dialed a specific telephone number in order to place the telephone call. This inbound address is identified as being associated with or assigned to one or more specified end-users e.g., customers of the message delivery system.

Unit 340 also determines where the incoming call should be routed, for delivery to an end-user, or to one or more locations specified by an end-user, or through a system of defining rules. Once unit 340 has made a determination on the proper routing of the incoming call, this call is routed to a specified communication server 342 where it is processed. Simultaneously, or unrelated to these events, unit 340 also determines whether the end-user that is the intended recipient of the fax incoming call, is connected on one or more end-user devices that are capable of receiving the fax message, or any information pertaining to the fax. In an embodiment of the invention, unit 340 determines how an end-user is available, through an instant messaging client end-user device. Such an end-user can be available on computer unit 322 that is running an instant message client program. In that case, status messages pertaining to the receipt of the fax message may be sent to unit 322.

Unit 322, and in particular via the instant messaging client program, may then request further information pertaining to the received fax message, and may even further request a routing of the fax message to one or more other end-user devices. For example, the end-user may request that a copy of the fax be sent to his instant messaging client, along with an additional copy of the fax being sent to his email storage system. This request is sent to unit 340, which further instructs communication server 342 to send a copy of the fax message to unit 322, along with a further copy to message storage unit 336, which represents the email storage unit specified by the end-user.

In the process described by Fig. 3, a system of signaling makes it possible for the interchange of data. This signaling flow is shown in Fig. 4, illustrating the same example as in Fig. 3. Here, an incoming call from unit 326 causes an incoming call signal to be sent to unit 330, which further routes the information to call management system unit 340. Unit 340 determines the appropriate routing for the incoming call, and signals the media gateway unit 330 to redirect the incoming call to communication server unit 342. Unit 342 accepts the incoming call, and hence, communication is established between units 326 and 342, allowing the receipt of the fax message by unit 342. In this process, unit 340 remains on the path of the signaling information, and is aware of the status of the message being received.

Unit 340 may signal to one or more end-users to determine whether they are connected and available to receive messages or other communication. This signaling may be accomplished through one or more protocols, including the use of an instant messaging protocol. Through this process, unit 340 determines that unit 322 is available to receive messages. Hence, it further directs status messages pertaining to the received fax message to unit 322. Subsequently, unit 322 signals via an instant messaging protocol, to unit 340, requesting that a copy of the fax message be sent to it, and further requesting that a copy of the fax be sent to a specified email address. Unit 340 then instructs unit 342 to transmit a copy of the fax, via an instant messaging protocol, to unit 322. Further, it instructs unit 342 to send a copy of the fax message via SMTP to a message storage unit 336.

The process of signaling and communication described in the embodiment of Fig. 3 and Fig. 4 can be enhanced with the use of security methods, wherein, utilizing the unit 225 of Fig. 2, communication between one or more elements of the invention can be authenticated and encrypted. Further, within the network protocols that enable transmission of signals and data across a data network, such as implemented in the network stack 215 of Fig. 2, IPsec, a known set of protocols in the art, for network security, is overlaid upon the communication of Fig. 3 and Fig. 4 via unit 225. Communication between some or all elements within the data network can be secured through the use of such security methods.

Within the system of the invention, communication, messages or documents that are to be transmitted from one or more elements of the network to another sometimes require to be translated or modified, either in their content, or in their signaling methods, or otherwise encapsulated in a way that permits their transmission across one or more networks, protocols or other media. The embodiment described here permits such operations to be performed, wherein rules or other directives are interpreted by the call management system 190 of Fig. 1 or within the session manager 230 of Fig. 2, or the communication server 342 of Fig. 3 or Fig. 4. One or more representation languages described further below may also represent these translations, adaptations or encapsulations, or directives.

One of several signaling mechanisms may be used to establish communication such as those described in Fig. 3 and Fig. 4. In one embodiment, a representation language is utilized to specify information pertaining to the incoming message. Specifically, Fig. 5 illustrates use of this language. Here, a number of element tags (such as 410, 420, 430, 440, 432, 434, 442, 444, 446, 448) are used to specify specific elements of the message, along with specific attributes (412, 414, 422) that further describe each element tag. Specifically, tag 410 describes that an incoming call was received from location phone number 12125551212, with a specified destination phone number (or inbound address) of 13235551313, and that the call was received at 11:19 GMT-7:00 hours. Tag 420 specifies that the received message is required to be sent to a destination email address joe@mywork.net. There is also tag 430 which describes more information about the customer who is the intended recipient of the incoming message. This includes information such as the customer ID (tag 432), and an authentication PIN number (tag 434). Another tag 440 describes that the message received has a unique identifier "192.168.1.101-98-0.p64", and that the message is a voice message, of a pre-specified format 7, and that its duration is 67 seconds. Information described in this format provides instructions to one or more elements of the invention, allowing them to determine how best to process and route a message.

The representation language shown in Fig. 5 can also be used to determine routing and disposition of calls and messages. This aspect is described in Fig. 6, through the use of tags and attributes. Here, tag 510 describes the instructions that follow as pertaining to the handling of a call. Starting with tag 520, this tag describes that the instructions pertain to calls received on behalf of destination address 13235551313@j2.com, and that a timeout period of 7 seconds is prescribed for the following rules. Next, tag 530 describes the rules further specified within the structure of the 7-second timeout description. Here, if a call is received from phone number 12125551212 (specified by tag 532), then the call should be routed to a destination phone number 13238609200 (specified by tag 534). Otherwise, the call should be routed to destination phone 13235551313 (specified by tag 539). Further, tag 540 specifies that if the called number (also reflected in tag 520) is busy, then the incoming call should be redirected (specified by tag 542) to a destination 13235551313@commserver2.com, which may be an alternate server (or media gateway) on the data network to receive and process the call.

Instructions of the format specified in Fig. 5 and Fig. 6, are illustrative of the representations and signaling methods used by the system of the invention.

The invention described above lies in systems and processes for communication of not just messages, but also documents, or other information or interaction between one or more networked objects on circuit and packet data networks. The means for representation of various communication types include content description and disposition rules, delivery and routing descriptions and rules, conversion and translation descriptions and rules, and methods for interactions and for administration over one or more network types, through one or more communication protocol types, to one or more destination types.

Turning now to Fig. 7, a block diagram of another embodiment of the invention for supporting a message delivery service is shown. This figure will be used to describe both inbound and outbound services, where the inbound service delivers a received voice, facsimile or other type of message, originating in a telephone circuit switched network 704, is delivered to an end user machine 708 or 712. The outbound service allows an audio, video, fax, or other type of message to originate in a data network, e.g. via an instant messaging network 716, a corporate data network 720, and a "public" data network such as the Internet 724, where the messages are then translated into a format suitable for playback or display by either a telephone, facsimile machine or other receiver that can be accessed via the telephone circuit switched network 704.

The translation between the circuit switched network 704 and the message delivery service data network 728 is performed using a media gateway 732. The media gateway 732 may digitize incoming analog phone or fax call signals. In addition, the gateway 732 may translate a message that may be received in multiple packets through the data network 728 into a format suitable for fax-tone transmission to a facsimile device 736, or suitable for transmission to a land phone or a mobile phone 744 that may not be accessible directly through the data network 728. A call management system 748 as a node of the message delivery service data network 728 serves to manage the inbound and outbound services, so that messages from incoming calls are delivered to the appropriate end user machine 708 or 712, as well as the reverse in which messages originating from an end user machine on a data network are transmitted to the non-data network receivers.

Fig. 7 also is used to describe an embodiment of the invention in which the DAV protocol, in particular, WebDAV, is used for the leg of the message delivery route that ends or originates with the end user machine. As an example, consider an incoming call signal which includes a message, directed to an inbound address of a registered end user. The media gateway 732 digitizes the message, and sends the message as a MIME e-mail message to a translation gateway 752. There, the message is further translated and sent to a DAV file store 756, in a DAV document format. An end user, via a DAV client program 760, may then access the file and play back or display the message. This assumes that the end user or her DAV client program was previously notified by the message delivery service that an inbound message has been received on her behalf. This type of notification may be performed using SIP, where a client program that has an SIP address registered with the message delivery service is contacted by a server of the message delivery service and may, for example, display a pop-up box on the end user's machine 712 stating that an incoming message has been received. The user may then instruct her client program to retrieve the message off the DAV file store 756.

Note that although in Fig. 7 the DAV file store 756 is shown as a node of the message delivery service network 728, an alternative would be to provide the DAV file store 756 as a node of the corporate data network 720. In that case, the end user's machine 712 would be a node of the corporate data network 720 and could have access to the DAV file store 756 though a secure connection maintained by the user's corporation or organization.

A further advantage of the DAV mechanism for the end-user leg of the communication path is that the tags of the mark-up language shown in Figs. 5 and 6 (e.g. XML tags which are attached to a document that contains the message) can be reused by the DAV mechanism, as an attribute of the file containing the message. In a particular scenario, one of the XML tags may include a docket number that is conventionally used by law firms to associate a document or task with a particular client and/or matter. Thus, the end user could add the docket number as an attribute of the DAV file that contains the message which she has recognized to be associated with the docket number. In this manner, the user may search the DAV file store 756 for messages that are associated with a given docket number. This feature allows the message delivery service to provide more focused billing information to the end user, sorting the incoming and outgoing messages by their docket numbers. This feature may be very attractive for business end users, and particularly those in the legal field which need to associate each communication with a certain client and/or matter number, for purposes of billing. It can therefore be appreciated that the use of DAV in the message delivery service architecture described above provides a much more flexible interface for the end user than e-mail.

For purposes of explanation, specific embodiments were set forth to provide a thorough understanding of the present invention. However, these embodiments merely illustrate the principles of the invention. Furthermore, all examples and conditional language that have been recited herein are principally intended expressly to be only for pedagogical purposes to aid the reader in understanding the principles of the invention and the concepts contributed by the inventors to furthering the art, and are to be construed as being without limitation to such specifically recited examples and conditions. Moreover, all statements herein reciting principles, aspects, and embodiments of the invention, as well as specific examples thereof, are intended to encompass both structural and functional equivalents thereof. Additionally, it is intended that such equivalents include both currently known equivalents as well as equivalents developed in the future, i.e., any elements developed that perform the same function, regardless of structure.
Thus, for example, it will be appreciated by those skilled in the art that the block diagrams herein represent conceptual views of illustrative circuitry embodying the principles of the invention. Similarly, it will be appreciated that any flow charts, flow diagrams, pseudocode and the like represent various processes which may be substantially represented in computer readable medium and so executed by a computer or processor, whether or not explicitly shown.

The functions of the various elements shown in the figures, including functional blocks labeled as "processors" or "servers" may be provided through the use of dedicated hardware as well as hardware capable of executing software in association with appropriate software. When provided by a processor, server or computer, the functions may be provided by a single dedicated processor, by a single shared processor, or by a plurality of individual processors, some of which may be shared. Moreover, explicit use of the term "processor", "server", or "computer" should not be construed to refer exclusively to hardware capable of executing software, and may implicitly include, without limitation, digital signal processor (DSP) hardware, read-only memory (ROM) for storing software, random access memory (RAM), and nonvolatile storage. Other hardware and/or software, conventional and/or custom, may also be included.

In the claims below, any element expressed as a means for performing a specified function is intended to encompass any way of performing that function including, for example, a) a combination of circuit elements which performs that function or b) software in any form, including, therefore, firmware, microcode or the like, combined with appropriate circuitry for executing that software to perform the function. The invention as defined by such claims resides in the fact that the functionalities provided by the various recited means are combined and brought together in the manner which the claims call for. Applicant thus regards any means, which can provide these functionalities as being equivalent to those shown herein.