EP1549034B1 - Universal message delivery system - Google Patents

Universal message delivery system Download PDF

Info

Publication number
EP1549034B1
EP1549034B1 EP05005495A EP05005495A EP1549034B1 EP 1549034 B1 EP1549034 B1 EP 1549034B1 EP 05005495 A EP05005495 A EP 05005495A EP 05005495 A EP05005495 A EP 05005495A EP 1549034 B1 EP1549034 B1 EP 1549034B1
Authority
EP
European Patent Office
Prior art keywords
message
entity
handle
network
service
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP05005495A
Other languages
German (de)
French (fr)
Other versions
EP1549034A1 (en
Inventor
Mark Alan Jones
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
AT&T Corp
Original Assignee
AT&T Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority to US581141 priority Critical
Priority to US08/581,141 priority patent/US5742763A/en
Application filed by AT&T Corp filed Critical AT&T Corp
Priority to EP19960120760 priority patent/EP0782316B1/en
Publication of EP1549034A1 publication Critical patent/EP1549034A1/en
Application granted granted Critical
Publication of EP1549034B1 publication Critical patent/EP1549034B1/en
Anticipated expiration legal-status Critical
Application status is Expired - Lifetime legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/5307Centralised arrangements for recording incoming messages, i.e. mailbox systems for recording messages comprising any combination of audio and non-audio components
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42136Administration or customisation of services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42229Personal communication services, i.e. services related to one subscriber independent of his terminal and/or location
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/487Arrangements for providing information services, e.g. recorded voice services, time announcements
    • H04M3/493Interactive information services, e.g. directory enquiries ; Arrangements therefor, e.g. interactive voice response [IVR] systems or voice portals
    • H04M3/4931Directory assistance systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M11/00Telephonic communication systems adapted for combination with other electrical systems
    • H04M11/02Telephonic communication systems adapted for combination with other electrical systems with bell or annunciator systems
    • H04M11/022Paging systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2201/00Electronic components, circuits, software, systems or apparatus used in telephone systems
    • H04M2201/60Medium conversion
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M2203/00Aspects of automatic or semi-automatic exchanges
    • H04M2203/45Aspects of automatic or semi-automatic exchanges related to voicemail messaging
    • H04M2203/4509Unified messaging with single point of access to voicemail and other mail or messaging systems
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/38Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections
    • H04M3/382Graded-service arrangements, i.e. some subscribers prevented from establishing certain connections using authorisation codes or passwords
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/42008Systems for anonymous communication between parties, e.g. by use of disposal contact identifiers
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M3/00Automatic or semi-automatic exchanges
    • H04M3/42Systems providing special services or facilities to subscribers
    • H04M3/50Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
    • H04M3/53Centralised arrangements for recording incoming messages, i.e. mailbox systems
    • H04M3/533Voice mail systems
    • H04M3/53366Message disposing or creating aspects
    • H04M3/53375Message broadcasting

Description

    Background of the Invention
  • The present invention relates to a computer-based communication network service, and, more particularly, is directed to a system in which entities are represented by network presences associated with handle identifiers used as addresses.
  • Communication by messaging is becoming steadily more popular. Advantages of messaging relative to a personal conversation include more efficient use of communication capacity, that is, text based electronic mail requires far less channel capacity than an equivalent voice message; more time efficient due to less need for time consuming ritual social inquiries; opportunity for more careful composition; and capability of including various types of communication, that is, the message can be in a multimedia format including audio, video and/or text. Furthermore, if the message is broadcast, its composition effort is amortized across the recipients. Also, the message can be buffered when a recipient is unavailable or unwilling to receive the message immediately; the recipient has more time to plan their response; an electronic message is easy to capture and place in long term storage; and software can be used to assist in composing and organizing messages.
  • One problem with presently available forms of messaging is that it is necessary to determine and remember addressing information which is substantially unrelated to the identity of the recipient. Voice and facsimile messages require a telephone number. Electronic mail messages require an address usually comprising an assigned user name and electronic domain name, and possibly information indicating a communication service provider. Also, the format of an electronic mail address can differ depending on the communication provider.
  • Telephone numbers are difficult to remember, usually change when a person moves or switches jobs, can be obtained through a directory having only a very limited number of search fields and may lack privacy as it is fairly easy to associate address information with a telephone number.
  • Personal telephone numbers, such as the proposed AT&T 500/700 personal number services, assign a telephone number to a subscriber, and associate the assigned telephone number with a destination telephone number and, optionally, a backup telephone number having a voice recording and storage device. Callers call the assigned telephone number, and calls are automatically routed to the destination telephone number. If the destination telephone number does not accept the call, then the call is automatically routed to the backup telephone number. The destination telephone number may be changed frequently by the subscriber. These personal number services mask changes in the subscriber's telephone number, that is, allow a subscriber to have a single telephone number even while travelling or moving frequently, and provide increased privacy. However, the personal numbers are still difficult to remember, can be obtained through a directory having only a very limited number of search fields, are accessible through only one medium, and, due to reliance on a telephone number, are tied into a particular addressing infrastructure which has limited call management options.
  • Electronic mail addresses are often difficult to remember, usually change when a person switches jobs or communication carriers, and are difficult to obtain due to lack of universal directory services.
  • Another problem with presently available forms of messaging is that if someone is reachable by a variety of message types, e.g., voice mail, facsimile and electronic mail on several networks, a sender is not sure which type of message will be most effective at reaching the intended recipient.
  • A further problem with presently available forms of messaging is that there may be a conversion problem between an available sending device, such as a twelve-key telephone, and a preferred receiving device, such as a facsimile machine. Also, there may be a conversion problem between the form of the originating message, e.g., voice mail, and the preferred form of received message, e.g., electronic mail. Products for converting the form of the message, such as the AT&T INTUITY product for a PBX/LAN environment, have been introduced, but have not yet achieved widespread usage. A proposed Multipurpose Internet Multimedia Extension (MIME) specification for Internet electronic mail allows senders to provide content in multiple, alternative formats but conversion issues have not been resolved.
  • The publication L. Detweiler, "Identity, Privacy, and Anonymity on the Internet", 1993, XP-002322966 discusses a method for delivering messages in a communication network having the method steps as defined in the preamble of claim 1 of the appended claims.
  • Summary of the Invention
  • It is an object of the present invention to avoid conversion problems in methods of this kind between the form of the originating message and the preferred form of the received message.
  • This object in accordance with the present invention, is achieved by a method having the features of claim 1 of the appended claims.
  • When the sender provides selected attributes as an address, the delivery system replaces the selected attributes with an address of the network presence without disclosing the address to the sender. In another aspect of the invention, a software agent processes the delivered message in accordance with a processing preference included in the entity attributes.
  • It is not intended that the invention be summarized here in its entirety. Rather, further features, aspects and advantages of the invention are set forth in or are apparent from the following description and drawings.
  • Brief Description of the Drawings
    • Fig. 1 is a block diagram of a communications network according to the present invention; and
    • Fig. 2 is a block diagram showing the logical relationship of various services according to the present invention.
    Detailed Description
  • An entity is represented by at least one handle, described in detail below. Generally, a handle is a more abstract representation of the entity than is found in the prior art, and avoids the problems of prior art entity representations associated with their insufficiently abstract (i.e., too physical) nature. Each handle provides a distinct cyberpresence identifier for an entity.
  • Directory services, as described in the present disclosure, provide more flexibility than prior art directory services. When used with handles according to the present disclosure, directory services provide further enhanced flexibility. Generally, a network directory service provides information about entities and finds entities based on descriptive queries. Some of the directory information is publicly available, whereas other of the directory information is not publicly available but is usable by the directory service for dereferencing addresses. Entities specify the desired privacy level(s) of their directory information. The service provides one or more global and specialized network directories, which may be physically distributed across multiple hosts in the network.
  • Message composition and delivery services, as described in the present disclosure, provide more flexibility than prior art message composition and delivery services. When used with handles according to the present disclosure, message composition and delivery services provide further enhanced flexibility. Generally, message delivery services provide for specification of policies by entities as to the forwarding of messages to specific endpoints or to a universal message storage facility, notification of message receipt and retrieval of messages. Message notification and retrieval may be according to entity specified criteria, such as priority to particular senders or to particular subjects.
  • Message storage services, as described in the present disclosure, provide more flexibility than prior art message storage services. When used with handles according to the present disclosure, message storage services provide further enhanced flexibility.
  • An important feature of the present disclosure is the application to objects such as messages and cyberpresences of information retrieval techniques, such as vector space models, which have heretofore been applied only to documents. Generally, flexibility is accomplished by applying information retrieval techniques to objects, rather than by relying primarily on more structured database query techniques.
  • Network environment
  • Referring now to the drawings, and in particular to Fig. 1, there is illustrated a network which is generally assumed as the environment in the present disclosure. The network shown in Fig. 1 comprises a communication network 100, home host computers 200, service host computers 210, connection host computers 220, gateways to other networks such as a local area network (LAN) 230, software executed on the various computers, and customer premises equipment such as twelve-key telephone sets 300, personal computers 310, terminals, and pager networks 400. Although not specifically shown in Fig. 1, Internet connections and wireless transmission may be used in a network contemplated in the present disclosure.
  • As will be apparent to those of ordinary skill in the art, many different communication protocols may be employed in communicating between the various parts of the network, such as TCP/IP, X.25, ISDN, Ethernet, asynchronous line protocols and analog and/or digital voice transmission. Communication for transactional services are implemented in a secure, flexible remote procedure call (RPC). Also, as appropriate, authentication and encryption protocols are employed, for example, hypertext transfer protocol (HTTP) or secure socket layer (SSL) protocol.
  • Various divisions of communications capability between customer equipment and network equipment are encompassed by the network of Fig. 1. The network is assumed to provide processing capability for customer equipment which lacks sufficient processing capability to provide the functions described below. The specific type of software programming used to provide these functions is not critical.
  • In one case, the customer equipment comprises only a twelve-button telephone set. A user dials a connection host which is part of the network, such as the nearest connection host or a toll-free number providing access to a connection host. Using one or more of voice input and touch-tone input, the user establishes network access authority, such as by entering an identification code and password. The connection host verifies access authority with the user's home host, then makes appropriate network resources available to the user by, for example, presenting menus of choices to the user.
  • In another case, the customer equipment comprises a private host such as a personal computer and a modem. The user instructs the private host to establish a connection to a connection host. In this case, the connection host functions in a more limited manner than in the previously described situation where the customer premises equipment is a telephone set.
  • In yet another case, the customer equipment comprises a receive only pager network. A connection host somewhere in the network executes software on behalf of the pager network.
  • Handles
  • An entity may be a person, organization, corporation, department within a corporation, use (interest) group; or a set of entities. Alternatively, the entity may be a functional role, such as president of an organization.
  • An electronic presence is established for every entity which requires a public identity. The electronic presence is also referred to herein as a network presence or "cyberpresence". The electronic presence is identified by a handle. The network presence for an entity serves as a locus of publicly available information about the entity, as a point of connection to the entity, and as a centralized set of resources available to the entity. Physically, a network presence comprises an account on a home host computer, such as the home host computer shown in Fig. 1, the actual network resource usage associated with the account, the capability of using additional network resources and identification of the account in network directories. Typically, an account resides on a home host, but some accounts may reside on multiple hosts due to their resource usage.
  • An entity may have multiple network presences each of which is associated with a distinct handle. For example, an entity which is a person may have one network presence for activities related to their job, another network presence for activities related to their primary hobby, and yet another network presence for activities related to their other personal uses.
  • As used herein and in the claims, "handle" refers to a unique identifier registered with a universal directory network service for use by the entity. A handle represents an abstract entity, and does not correspond to a physical endpoint although it may be associated with one or more physical endpoints for various purposes, as described below. The handle functions as the network name of the entity, and also functions as the network address of the entity, but is not a physical end point address. An entity may have one or more handles each of which is associated with a network presence. Primarily for billing purposes, each handle is associated with a sponsor that is not necessarily the entity using the handle.
  • Handles permit decoupling of physical endpoints and delivery systems from the network presence for an entity. That is, a handle is not merely an address, it is a representation of an entity because it is associated with resource usage and availability for the entity.
  • Since a handle is unique at any point in time, it can be used as a universal address. Another important feature of a handle is its persistence, that is, its association with one using entity despite changes in the attributes associated with the entity, such as telephone number, address, employment affiliation or sponsor. If the entity is a group, then members or other attributes of the group may change over time, but the group (entity) still retains the handle. Similarly, if the entity is a person performing certain functions, e.g., the president of XYZ Company, then the person associated with the handle may change, but the handle persists; in this case, the handle is a referential expression describing a functional role.
  • Examples of handles are: "bigbear", "Jane_Farnsworth", "ATT", "usenet.rec.gardening", "empiricists", "president_XYZ" and so on. A handle is not a telephone number. A telephone number is a physical point which is associated with a varying number of users, whereas a handle is not a physical point, and is associated with only the entity represented by the handle. A handle may include alphabetic information which serves a mnemonic purpose.
  • Advantages of personally chosen handles, relative to handles assigned by a network authority, include memorability, that is, personally chosen handles have mnemonic value for message senders, individuality, ability to be descriptive or representative of a network persona or attributes of an entity, and ability to mask the identity of an entity.
  • Handles may eventually be reassigned, when the possibility of confusion between entities is deemed to be sufficiently low. For example, when an entity expires, such as a person dies or a corporation is dissolved, and a predetermined time has passed since expiration, the handle of the expired entity may become available for use by another entity.
  • Examples of entity attributes which may be associated with an individual's handle include password(s), name, address, preferred format for message reception, primary telephone number, forwarding telephone number, fax number, family members, employer, profession, hobbies and so on.
  • Examples of entity attributes which may be associated with an organization's handle include password(s), name, address, preferred format for message reception, telephone number, fax number, number of members, industry, products or services, annual sales, affiliated companies and so on.
  • As the name of a network presence for an entity, a handle is a logical place for an entity to obtain and/or offer network services. Generally, the network resources available to an entity include a personalized access point, information storage capacity, information access structures such as an "address book", a personalized set of message spaces, and convenient ways to access frequently used on-line services.
  • An "address book", as used herein and in the claims, is a personalized directory of frequently accessed message destinations for the entity, that is, a set of handles which identify entities. In other words, the objects in an address book are handles. An address book allows the entity to refer to other entities in a more convenient manner, such as by name, photograph, or nickname; thus, the address book hides the actual handles from the entity.
  • Since the attributes associated with a handle may change over time, it is preferred to locally store only the handles for an address book with respective temporal information such as date/time stamps. At each use of a handle, the address book automatically queries the directory service as to whether any attributes have changed since the timestamp of the handle. The address book locally stores any local information associated with the handle, such as the entity's nickname or relationship definition for the handle. The initial contents of the address book may be determined with reference to the sponsor of the entity.
  • A query can define a "special" address book of an entity's base (universal) address book, that is, the query restricts the set of handles in the special address book.
  • The entity can view a subset of the address book by specifying attributes of the objects in the desired subset. For example, a view of an address book may provide, for each entity, its name, face (or other) picture and telephone number.
  • An entity obtains services through its handle generally by subscribing to the service; such services are referred to herein and in the claims as "vendor services". Service providers, which may be third party vendors, the provider of the communication network or the provider of the network presence system, then add the service capabilities to the handle in an appropriate manner, such as by authorization to act on instructions from the handle, by adding choices to menu-driven interfaces accessible to the handle, or by adding functional capabilities to software agents associated with the handle. Examples of software agents are a message handling agent and a message storage agent, described below. Examples of vendor services are a message composition service, a calendar scheduling service and a software agent service. Fig. 1 shows a service host for third-party services in which the vendor offers a service directly from its own handle and other handles must explicitly communicate with the vendor's handle for the service.
  • An entity offers services through its handle by responding to requests directed to the handle. For example, the entity may add functional capabilities to one of the agents associated with its handle to provide a service to other handles. In some embodiments, for provision of certain services, the entity may make special billing arrangements with the network.
  • When the entity is accessible to at least one messaging service, the attributes of an entity include a physical endpoint to which messages are to be delivered. For example, when the entity is a pager network, the physical endpoint is the pager equipment. When the entity is an individual, the physical endpoint can be non-network equipment, such as a fax machine, or network storage.
  • When the entity is accessible to at least one messaging service, the attributes of an entity include a preferred media format for receiving messages. For example, when the entity is accessible by more than one message media format, such as fax, voice mail, textual electronic mail and multimedia electronic mail, the entity indicates the media format in which it prefers to receive messages in its "preferred reception media" attribute.
  • There are several differences between personal telephone numbers, such as the proposed AT&T 500/700 personal number services, and the handles of the present invention. The personal number services provide a customer with only a telephone number, that is, a completely numeric identifier which lacks mnemonic value, whereas the present handles may comprise alphanumeric information having mnemonic value. The personal number services must be associated with at least one destination telephone number for a customer, whereas the present handles need not be associated with a specific telephone number, instead, an entity may opt to have the network store its messages, and then the entity retrieves its messages from the network, for example, by a dial-in telephone call.
  • Directory services
  • The universal network directory service stores attributes associated with handles and responds to queries relating to the stored information to provide a very flexible searching ability. The directory service may be a vendor service.
  • When a directory user such as a message sender desires to know a handle for an entity, the sender provides sufficient descriptive information to uniquely identify the entity. In some cases, the sender interacts repeatedly with the directory service to uniquely identify the entity. For example, in response to the sender's provision of a person's name, city and state of residence, employer and profession, the directory service returns the requested handle.
  • In other situations, a directory user knows a handle and provides a query to the directory service to obtain one or more attributes associated with the handle. For example, a directory user may wish to know a daytime telephone number associated with a handle.
  • Handle attributes have privacy level information specified by the entity represented by the handle. In its simplest form, privacy level information simply indicates whether the attribute is publicly available or not publicly available, i.e, private. Therefore, entities may maintain essentially "unlisted" handles with no attribute information publicly available.
  • The directory service generally maintains indices of the attributes in a variety of hierarchical structures, and responds to structure sensitive queries.
  • Each of a directory query and a response thereto generated by the universal network directory service may contain multimedia depending on the kinds of interfaces and applications used. As used herein and in the claims, information in a multimedia format means information in at least two of an internal computer format such as binary format, text format such as ASCII, voice format and video format.
  • Entities and/or their respective sponsors have the ability to self-administer certain of the entity's attributes in accordance with preferences, such as password(s), preferred format for message reception, forwarding telephone number and privacy status of their attributes, using an automated administration procedure including a software program executed on at least one of the hosts of Fig. 1.
  • Handle attributes have authenticity information associated therewith. In its simplest form, authenticity information simply indicates who provided the attribute information. More complicated authenticity information indicates, for example, when the attribute information was provided. The authenticity information provides a basis for forming a trustworthiness opinion of the associated attribute information.
  • When the user of the directory service is a handle, additional flexibility is contemplated. Specifically, the information returned from the directory service may be automatically transferred to another service, such as a message composition service offered by a third-party vendor. For example, when a handle queries the directory service for all handles having specified attributes, such as:
    • (type of entity = individual),
    • (family members = at least one child), and
    • (address = NY or NJ)
    the resulting set of handles may be used as a set of addresses for a message broadcast by a message preparation service used by the handle.
  • In certain embodiments, an additional privacy designation of "secret" is available for information associated with a handle. This is useful for broadcasts prepared by a message preparation service to entities matching specified criteria, where the matching entities wish to remain unknown, for example, persons testing positive for a particular disease. In these cases, the entities may be interested in receiving information related to their attributes, but want their possession of such attributes to be masked from mass marketers and/or probes attempting to guess the information. If secret information is used to resolve a handle, then information identifying the receiving entity is withheld in any delivery receipts provided by the network to the sender or querying party.
  • Another example of additional flexibility when the user of the directory service is a handle is an updating service for an address book. The updating service may simply add the results of each directory query to the address book. Alternatively, the results of the directory query may automatically be transferred to the updating service, and then the updating service asks the entity associated with the handle using the directory whether and/or how to retain the results. As yet another alternative, a software agent associated with the handle may treat the results of the directory query as an information object to be processed in accordance with general policies specified by the entity for information objects, i.e., policies for information which is not limited to directory information.
  • Message composition and delivery services
  • A message composition service permits a message to be composed and associated with a destination query. That is, a message is sent to a destination query, rather than a specified endpoint. The destination query is of the form described earlier for the directory service.
  • A message delivery service provides delivery of the message to the objects satisfying the destination query associated with the message, with the objects typically being handles.
  • Messages are assumed to include content information and envelope information, such as sender, destination query determining the recipient(s), network transit history, arrival time, subject and priority. Senders are identified by their handles. Recipients are identified by the destination query, unless their identity is masked (see discussion below). Content information may comprise multimedia and interactive programs; notes from family, friends and business associates; electronic correspondence from businesses, government, associations and so on; electronic postcards; electronic letters; electronic newsletters and magazines; electronic advertising; electronic solicitations and so on.
  • When the sender knows the preferred media format for the recipient of the message, the sender can instruct the message delivery service to put the message, composed in one format, into the preferred format when technically feasible. For example, the message may be composed as text, and converted to voice using speech synthesis. As will be appreciated, the preferred media format for a message recipient can usually be determined from a query to the network directory service. Certain message preparation services are capable of automatically querying the directory service and using the query results for format conversion.
  • The message sender can require that it remain anonymous, for example, by composing a message with the sender explicitly identified as "anonymous" or by omitting sender information.
  • A message recipient can require that it remain anonymous. For example, if an entity has set all of its attribute information to non-public, it may receive broadcast messages to entities having its attributes, but the message delivery service will not provide an identifying delivery receipt to the message sender. However, the message sender may be informed that a delivery occurred, and possibly the number of messages that were delivered.
  • Message non-repudiability is provided when the sender requests that the message delivery service guarantee that the sender of the message is correctly identified. Non-repudiability is particularly useful for messages having financial consequences.
  • Message handling agents
  • When the recipient of a message is a handle, additional flexibility is contemplated. Specifically, the handle may subscribe to the services of a message handling agent (a type of software agent) which performs functions on behalf of the entity represented by the handle in accordance with attributes associated with the handle.
  • As used herein and in the claims, "software agent" refers to a software program usually executed by one of the host computers shown in Fig. 1. The software agent is a type of vendor service to which an entity may subscribe through its handle. The software agent has various capabilities, depending on its specific implementation, and is characterized by independent operation or agency operation. The software agent is event-driven. The software agent responds to events and carries out behavior in accordance with the event and environment, such as time of day. A software agent is capable of creating, transferring and deleting objects, invoking other vendor services, notifying, monitoring and keeping statistics.
  • Independent operation indicates that the software agent performs its functions generally independently of how and when its subscribing entity interacts with its network presence.
  • Agency operation indicates that the software agent operates on behalf of its subscribing entity, typically inheriting access authority and so on of the subscribing entity, in accordance with entity specified preferences usually recorded as attributes for the entity.
  • Examples of services provided by a message handling agent include notification of a new message, automatic forwarding of messages to endpoints (e.g., a copy to other handles or a message store), summarizing messages, sorting messages according to entity criteria (ex: priority, size, sender and/or subject), deleting messages according to entity criteria, storing messages according to entity criteria, converting the media format of a message, and preparing simple replies to certain formatted messages. That is, message handling agents exhibit context dependent behavior based on the sending and receiving equipment, the message's characteristics and the recipient's preferences.
  • In one case, a handle may have a "preferred message media format = text" associated therewith. The entity may then communicate a request such as "speak the contents of the most recent message to me" to its message handling agent. In this case, the message handling agent converts the media format of the message from text to voice, and forwards the voice message to a destination indicated by the entity, such as a telephone.
  • The message handling agent facilitates message enabled behavior. For example, the message handling agent may check the content of a message for a certain type of information, such as schedule related information, and automatically transfer such information to another service associated with the handle, such as a calendar program.
  • Message storage services
  • Prior art message storage services typically have a physical association between a mailbox, that is, a physical data file, and a message. A message storage service according to the present disclosure is not so limited. A mailbox is considered to be a set of messages which satisfy a query. By varying the attributes specified in the query, an entity can achieve various levels of mailbox granularity, from considering all the messages for which the entity has read permission (which may include messages received by other entities) to considering only a subset of the messages received by one entity such as itself. Additionally, a mailbox may have different message dispositions, such as who is notified of the mailbox query results.
  • A mailbox is defined by a query over a set of messages. An address book is defined by a query over a set of cyberpresences.
  • Typical prior art systems treat notifying a recipient of the arrival of a message as a procedural, event-driven process. For example, "do (x) when (y)" where "y" is the event of a message arrival.
  • The present disclosure contemplates a persistent query, that is, a query for which an entity maintains a continuing interest. The persistent query is a declarative representation depending on at least one property of an object, and is not event-driven. The query originator can assert the query at regular intervals (polling). For example, "if a message has status NEW or UNREAD then it is of interest".
  • The persistent query defining a set of objects is always consistent with the data against which it is asserted. The persistent query communicates data changes to objects interested in such changes. The persistent query can be implemented, for example, by having the target of the query notify the originator of the query when the response of the target changes.
  • A persistent query is useful when an entity has a need to know something. A software agent is useful for responding to events in a predetermined manner.
  • Notifying a recipient of the arrival of a message is a declarative process, that is, an entity is considered as submitting a persistent query, and when the present result of the persistent query invalidates or logically mismatches the previous result of the persistent query, the entity which submitted the query is notified. For example, if the entity has submitted a persistent query for "all stored unread messages addressed to my handle", and a new message has been stored since the last query was asserted, then the result of the previous query (no unread messages) is invalidated, so the a notification message (one unread message) is generated.
  • Message processing abilities are dependent upon the handle of the entity. For example, as a default, the handle for an entity has full read, write and modify ability for messages addressed to the handle. For particular types of messages addressed to an entity's handle, the entity may specify read, write and/or modify ability for other handles.
  • A mailbox according to the present disclosure can be considered a one time object when it is the result of a one time query, or can be considered a persistent object when it is the result of a persistent query. A mailbox which is the result of a persistent query is effectively continously updated. It will be appreciated that an entity can create multiple persistent mailboxes by communicating multiple persistent queries to the message storage service. Such an abstraction is stored as a convenience to an entity.
  • For example, when the entity is a paging system, the set of persistent queries might be "new messages for each of the users associated with the paging system entity".
  • The message storage service generates a message ID for each message and provides indexing services for message retrieval so that queries can be satisfied faster. For example, the message storage service may compute message properties such as usage statistics, creation time, message type, message size, current storage medium and so on. Practically and where possible, the message storage service simply extracts certain information from the message envelope as message properties (e.g., sender). If the message object is modified, such as by annotation, or deleted, the message storage service detects this or is notified by the modifier and updates the storage related properties.
  • The message storage service determines the storage policy for a message according to a general policy (not message specific) specified by a message recipient, including the current,storage medium (one of the message properties), and the message persistence, that is, when the message should be moved to archival storage. Finally, the message storage service actually stores the message.
  • In some embodiments, the message storage service responds to requests for message IDs for messages whose storage is not directly controlled by the service. Such messages, also referred to as "proxy objects", have message IDs and computed properties, and can be queried and retrieved through an interface with the direct controller of the storage of the proxy object. The software which directly controls storage of a proxy object is responsible for notifying the message storage service of message creation, modification and deletion events.
  • An example of usage of a proxy object is a message shared by several entities. The properties of the proxy object may differ by entity, such as whether the message has been read, or annotations appended thereto. The proxy object may be automatically assigned different priorities for different entities.
  • Message storage agents
  • When the user of the message store is a handle, additional flexibility is contemplated. Specifically, the handle may subscribe to the services of a message storage agent (a type of software agent) which performs functions on behalf of the entity represented by the handle in accordance with attributes associated with the handle.
  • Examples of services provided by a message storage agent include notifying an entity of a new message, deleting messages according to message specific entity criteria, archiving messages according to message specific entity criteria, and converting the media format of a message. The summary may include category, thread (relationship to other messages such as topic), content type, content and so on. Activities particularly suited to a message storage agent include archiving messages, aging messages, compressing message and placing messages in different virtual folders.
  • A message storage agent can assert a persistent query against a message store on behalf of an entity. This function is particularly useful when the entity is a paging system which otherwise expects to be in "receive only" type operation.
  • For example, a message storage agent might monitor a directory and provide notification of changes in the employer for a particular entity.
  • As another example, if a vendor service is providing a physical location, such as from a global positioning service, then the message storage agent could notify an entity of the location of another entity, such as a child of the first entity.
  • Fig. 2 shows the logical relationship of the above-described services. The network directory service 700, message composition service 710, message delivery service 720, message storage service 730, message handling agent 750 and message storage agent 760 each comprise software programs for execution by at least one of the host computers 200, 210, 220 shown in Fig. 1. The message storage media 740 shown in Fig. 2 comprises storage media, such as RAM or disk, associated with at least one of the host computers shown in Fig. 1.
  • A sending entity 500 communicates with the message composition service 710 to compose a message. Message composition may include interaction with the directory service 700. The sending entity 500 then instructs the message composition service 710 to transfer the composed message to the message delivery service 720, which delivers the message to its specified destination and provides various forms of reports on delivered messages to the sending entity 500.
  • Messages may be delivered in real time to a receiving entity 600, or may be delivered to the message storage service 730 logically associated with the message storage media 740. The message handling agent 750 generally operates on messages received from the message delivery service 720. The message storage agent 760 generally operates on messages placed on the message storage media 740 by the message storage service 730. The message handling agent 750 and message storage agent 760 operate on behalf of the receiving entity 600.

Claims (2)

  1. A method for delivering messages in a communication network, said method including the steps of:
    providing a network presence for an entity, said entity having predefined attributes;
    associating a handle to said network entity, said handle identifying said network presence and not corresponding to a physical network endpoint;
    delivering a message from a sender, said message indicating said handle as the destination; and
    processing the delivered message with a software agent in accordance with the predefined attributes of said entity
    CHARACTERISED IN THAT
    one of the predefined attributes is a preferred media format, and that the step of processing includes the step of:
    converting the media format of the delivered message into the preferred media format.
  2. The method as defined in claim 1, wherein another attribute of the preferred attributes is a processing preference of one of a notifying action, a forwarding action, a deleting action and a storing action.
EP05005495A 1995-12-29 1996-12-23 Universal message delivery system Expired - Lifetime EP1549034B1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
US581141 1995-12-29
US08/581,141 US5742763A (en) 1995-12-29 1995-12-29 Universal message delivery system for handles identifying network presences
EP19960120760 EP0782316B1 (en) 1995-12-29 1996-12-23 Universal message delivery system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
EP19960120760 Division EP0782316B1 (en) 1995-12-29 1996-12-23 Universal message delivery system

Publications (2)

Publication Number Publication Date
EP1549034A1 EP1549034A1 (en) 2005-06-29
EP1549034B1 true EP1549034B1 (en) 2007-08-22

Family

ID=24324050

Family Applications (2)

Application Number Title Priority Date Filing Date
EP19960120760 Expired - Lifetime EP0782316B1 (en) 1995-12-29 1996-12-23 Universal message delivery system
EP05005495A Expired - Lifetime EP1549034B1 (en) 1995-12-29 1996-12-23 Universal message delivery system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP19960120760 Expired - Lifetime EP0782316B1 (en) 1995-12-29 1996-12-23 Universal message delivery system

Country Status (5)

Country Link
US (1) US5742763A (en)
EP (2) EP0782316B1 (en)
JP (1) JPH09219724A (en)
CA (1) CA2192502C (en)
DE (4) DE69637221T2 (en)

Families Citing this family (156)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6515968B1 (en) 1995-03-17 2003-02-04 Worldcom, Inc. Integrated interface for real time web based viewing of telecommunications network call traffic
US6343115B1 (en) * 1996-02-13 2002-01-29 At&T Corp Method of announcing an internet call
US6704713B1 (en) * 1996-05-23 2004-03-09 Ita Investments, Llc Computer controlled event ticket auctioning system
US7747507B2 (en) * 1996-05-23 2010-06-29 Ticketmaster L.L.C. Computer controlled auction system
US6907405B2 (en) * 1996-05-23 2005-06-14 Ita Investments, Llc Computer controlled priority right auctioning system
US6473407B1 (en) 1997-09-05 2002-10-29 Worldcom, Inc. Integrated proxy interface for web based alarm management tools
US6301608B1 (en) * 1996-08-14 2001-10-09 At&T Corp. Method and apparatus providing personalized mailbox filters
US6243398B1 (en) * 1996-10-21 2001-06-05 Vocaltec Communications Ltd. System and method for personal multimedia communication over a packet switched network
US5946684A (en) 1997-02-18 1999-08-31 Ameritech Corporation Method and system for providing computer-network related information about a calling party
US5978806A (en) * 1997-02-18 1999-11-02 Ameritech Corporation Method and apparatus for communicating information about a called party to a calling party
JPH10268959A (en) * 1997-03-24 1998-10-09 Canon Inc Device and method for processing information
JP2001519130A (en) * 1997-04-15 2001-10-16 ブリティッシュ・テレコミュニケーションズ・パブリック・リミテッド・カンパニー Message Service
US6330079B1 (en) * 1997-09-08 2001-12-11 Mci Communications Corporation Integrated voicemail and faxmail platform for a communications system
US7058600B1 (en) 1997-09-26 2006-06-06 Mci, Inc. Integrated proxy interface for web based data management reports
US7225249B1 (en) * 1997-09-26 2007-05-29 Mci, Llc Integrated systems for providing communications network management services and interactive generating invoice documents
US6745229B1 (en) 1997-09-26 2004-06-01 Worldcom, Inc. Web based integrated customer interface for invoice reporting
US6381644B2 (en) * 1997-09-26 2002-04-30 Mci Worldcom, Inc. Integrated proxy interface for web based telecommunications network management
US6385644B1 (en) 1997-09-26 2002-05-07 Mci Worldcom, Inc. Multi-threaded web based user inbox for report management
US6714979B1 (en) 1997-09-26 2004-03-30 Worldcom, Inc. Data warehousing infrastructure for web based reporting tool
US6763376B1 (en) * 1997-09-26 2004-07-13 Mci Communications Corporation Integrated customer interface system for communications network management
US20080039052A1 (en) * 1999-06-02 2008-02-14 Knowles Andrew T Digital Message Processing System
US6983308B1 (en) 1998-11-19 2006-01-03 Openwave Systems, Inc. Mail synchronization of remote and local mail systems
US6351761B1 (en) 1998-12-18 2002-02-26 At&T Corporation Information stream management push-pull based server for gathering and distributing articles and messages specified by the user
WO2000043892A1 (en) * 1999-01-21 2000-07-27 Universal Music Group, Inc. Method and system for transmitting media information through a network
WO2000045574A1 (en) * 1999-01-29 2000-08-03 International Thinklink Corporation Apparatus and method for channel-transparent multimedia broadcast messaging
AU2350200A (en) * 1999-02-26 2000-09-14 Bellsouth Intellectual Property Corporation Methods and systems to provide a message in a messaging system without revealingan identity of the sending party
EP1155556A2 (en) * 1999-02-26 2001-11-21 BellSouth Intellectual Property Corporation Methods and systems for enabling a reply call to a voice mail message
US6882708B1 (en) 1999-02-26 2005-04-19 Bellsouth Intellectual Property Corporation Region-wide messaging system and methods including validation of transactions
US6681257B1 (en) 1999-02-26 2004-01-20 Bellsouth Intellectual Property Corporation Methods and system for determining message routing based on elements of a directory number
US6810113B1 (en) 1999-02-26 2004-10-26 Bellsouth Intellectual Property Corporation Methods and systems to make spoken name data available
US6628761B1 (en) 1999-02-26 2003-09-30 Bellsouth Intellectual Property Corporation Methods and systems allowing access to a messaging platform through a visited messaging platform
US7184535B1 (en) 1999-02-26 2007-02-27 Bellsouth Intellectual Property Corporation Methods and systems for releasing a voice mail system from a communication and further processing the communication
US6891931B1 (en) * 1999-02-26 2005-05-10 Bellsouth Intellectual Property Corporation Methods and systems for enabling return to same position in a review of messages in a voice mail system using tag or identifier stored in the voice mail system
US7283620B2 (en) * 1999-02-26 2007-10-16 At&T Bls Intellectual Property, Inc. Systems and methods for originating and sending a voice mail message to an instant messaging platform
JP3461750B2 (en) * 1999-03-04 2003-10-27 パナソニック コミュニケーションズ株式会社 Communication apparatus, communication method, and a method of registering a caller information
US7596606B2 (en) * 1999-03-11 2009-09-29 Codignotto John D Message publishing system for publishing messages from identified, authorized senders
CA2272739C (en) 1999-05-25 2003-10-07 Suhayya Abu-Hakima Apparatus and method for interpreting and intelligently managing electronic messages
US6240391B1 (en) * 1999-05-25 2001-05-29 Lucent Technologies Inc. Method and apparatus for assembling and presenting structured voicemail messages
US6842447B1 (en) 1999-06-14 2005-01-11 Mci, Inc. Internet protocol transport of PSTN-to-PSTN telephony services
US6247045B1 (en) * 1999-06-24 2001-06-12 International Business Machines Corporation Method and apparatus for sending private messages within a single electronic message
US6453034B1 (en) 1999-07-29 2002-09-17 Mci Worldcom, Inc. Method of and system for extending internet telephony over virtual private network direct access lines
US6735209B1 (en) * 1999-07-29 2004-05-11 Worldcom, Inc. Address definition for IP telephony services
US7069335B1 (en) * 1999-08-10 2006-06-27 Microsoft Corporation Method and system for exchanging messages between entities on a network comprising an actor attribute and a mandatory attribute in the header data structure
US8743892B2 (en) * 1999-11-08 2014-06-03 Verizon Business Global Llc Method and system for dynamic gateway selection in an IP telephony network
US6480588B1 (en) 1999-11-08 2002-11-12 Worldcom, Inc. Methods for providing prepaid telephony service via an internet protocol network system
US9281996B1 (en) 1999-11-08 2016-03-08 Verizon Patent And Licensing Inc. Method and system for dynamic gateway selection in an IP telephony network
US6434143B1 (en) * 1999-11-08 2002-08-13 Mci Worldcom, Inc. Internet protocol telephony voice/video message deposit and retrieval
US7860114B1 (en) 1999-11-08 2010-12-28 Verizon Business Global Llc Method and system for dynamic gateway selection in an IP telephony network
US6615236B2 (en) 1999-11-08 2003-09-02 Worldcom, Inc. SIP-based feature control
US6834341B1 (en) * 2000-02-22 2004-12-21 Microsoft Corporation Authentication methods and systems for accessing networks, authentication methods and systems for accessing the internet
US7032241B1 (en) 2000-02-22 2006-04-18 Microsoft Corporation Methods and systems for accessing networks, methods and systems for accessing the internet
US7065547B2 (en) * 2000-03-09 2006-06-20 Persels Conrad G Integrated on-line system with enchanced data transfer protocol
US7062535B1 (en) * 2000-04-03 2006-06-13 Centerpost Communications, Inc. Individual XML message processing platform
US7984104B1 (en) 2000-04-03 2011-07-19 West Corporation Method and system for content driven electronic messaging
AU4793401A (en) * 2000-04-03 2001-10-15 Juergen Stark Method and system for content driven electronic messaging
US7149896B1 (en) 2000-05-05 2006-12-12 Microsoft Corporation Methods and systems for providing security for accessing networks, methods and systems for providing security for accessing the internet
US7444669B1 (en) * 2000-05-05 2008-10-28 Microsoft Corporation Methods and systems for providing variable rates of service for accessing networks, methods and systems for accessing the internet
AU5384300A (en) * 2000-06-22 2002-01-02 Migration Systems Ag Data transfere device
US7143182B1 (en) 2000-08-08 2006-11-28 Cisco Technology, Inc. Smart secretary for routing call objects in a telephony network
US6823331B1 (en) 2000-08-28 2004-11-23 Entrust Limited Concept identification system and method for use in reducing and/or representing text content of an electronic document
JP2002117110A (en) * 2000-10-06 2002-04-19 Riso Kagaku Corp System and method for delivering media and information transmitter
US7379543B2 (en) * 2001-03-09 2008-05-27 Ayman, Llc. Universal point of contact identifier system and method
US7047280B2 (en) * 2001-03-15 2006-05-16 Hewlett-Packard Development Company, L.P. Network system and method for providing user-relative addressing
US7200556B2 (en) * 2001-05-22 2007-04-03 Siemens Communications, Inc. Methods and apparatus for accessing and processing multimedia messages stored in a unified multimedia mailbox
US7260607B2 (en) * 2001-08-02 2007-08-21 Siemens Communications, Inc. Methods and apparatus for performing media/device sensitive processing of messages stored in unified multimedia and plain text mailboxes
US7219129B2 (en) 2001-11-28 2007-05-15 Weissman Peter S Mail program for processing multiple email messages
US7167701B1 (en) * 2001-12-18 2007-01-23 Bellsouth Intellectual Property Corporation Voice mailbox with management support
EP2043326A3 (en) * 2002-02-14 2009-04-22 Avaya Technology Corp. Presence tracking and name space interconnection techniques
US7415417B2 (en) * 2002-03-15 2008-08-19 Avaya Technology Corp. Presence awareness agent
US7398209B2 (en) 2002-06-03 2008-07-08 Voicebox Technologies, Inc. Systems and methods for responding to natural language speech utterance
US7693720B2 (en) 2002-07-15 2010-04-06 Voicebox Technologies, Inc. Mobile systems and methods for responding to natural language speech utterance
US6707890B1 (en) 2002-09-03 2004-03-16 Bell South Intellectual Property Corporation Voice mail notification using instant messaging
US7475240B2 (en) * 2002-11-06 2009-01-06 Symantec Corporation System and method for add-on services, secondary authentication, authorization and/or secure communication for dialog based protocols and systems
US7023980B2 (en) * 2002-12-04 2006-04-04 Avaya Technology Corp. Outbound dialing decision criteria based
US9740988B1 (en) 2002-12-09 2017-08-22 Live Nation Entertainment, Inc. System and method for using unique device indentifiers to enhance security
US10366373B1 (en) 2002-12-09 2019-07-30 Live Nation Entertainment, Incorporated Apparatus for access control and processing
US9477820B2 (en) 2003-12-09 2016-10-25 Live Nation Entertainment, Inc. Systems and methods for using unique device identifiers to enhance security
US7474741B2 (en) * 2003-01-20 2009-01-06 Avaya Inc. Messaging advise in presence-aware networks
US8094804B2 (en) 2003-09-26 2012-01-10 Avaya Inc. Method and apparatus for assessing the status of work waiting for service
US7080104B2 (en) 2003-11-07 2006-07-18 Plaxo, Inc. Synchronization and merge engines
US8463627B1 (en) 2003-12-16 2013-06-11 Ticketmaster Systems and methods for queuing requests and providing queue status
US9398152B2 (en) * 2004-02-25 2016-07-19 Avaya Inc. Using business rules for determining presence
US7953859B1 (en) 2004-03-31 2011-05-31 Avaya Inc. Data model of participation in multi-channel and multi-party contacts
US8000989B1 (en) 2004-03-31 2011-08-16 Avaya Inc. Using true value in routing work items to resources
US7734032B1 (en) 2004-03-31 2010-06-08 Avaya Inc. Contact center and method for tracking and acting on one and done customer contacts
US7584123B1 (en) 2004-04-06 2009-09-01 Ticketmaster Systems for dynamically allocating finite or unique resources
US7769154B1 (en) 2004-06-09 2010-08-03 Avaya Inc. Aggregated perceived presence
US7983148B1 (en) 2004-07-12 2011-07-19 Avaya Inc. Disaster recovery via alternative terminals and partitioned networks
US7996471B2 (en) * 2004-07-13 2011-08-09 At&T Intellectual Property I, L.P. Electronic message distribution system
US8738412B2 (en) * 2004-07-13 2014-05-27 Avaya Inc. Method and apparatus for supporting individualized selection rules for resource allocation
US7949121B1 (en) 2004-09-27 2011-05-24 Avaya Inc. Method and apparatus for the simultaneous delivery of multiple contacts to an agent
US8234141B1 (en) 2004-09-27 2012-07-31 Avaya Inc. Dynamic work assignment strategies based on multiple aspects of agent proficiency
US9608929B2 (en) 2005-03-22 2017-03-28 Live Nation Entertainment, Inc. System and method for dynamic queue management using queue protocols
US7567653B1 (en) 2005-03-22 2009-07-28 Avaya Inc. Method by which call centers can vector inbound TTY calls automatically to TTY-enabled resources
MX2007011675A (en) * 2005-03-22 2008-11-04 Ticketmaster Apparatus and methods for providing queue messaging over a network.
US7562304B2 (en) * 2005-05-03 2009-07-14 Mcafee, Inc. Indicating website reputations during website manipulation of user information
US20060253582A1 (en) * 2005-05-03 2006-11-09 Dixon Christopher J Indicating website reputations within search results
US20060253584A1 (en) * 2005-05-03 2006-11-09 Dixon Christopher J Reputation of an entity associated with a content item
US8566726B2 (en) * 2005-05-03 2013-10-22 Mcafee, Inc. Indicating website reputations based on website handling of personal information
US7822620B2 (en) * 2005-05-03 2010-10-26 Mcafee, Inc. Determining website reputations using automatic testing
US8438499B2 (en) 2005-05-03 2013-05-07 Mcafee, Inc. Indicating website reputations during user interactions
US7765481B2 (en) 2005-05-03 2010-07-27 Mcafee, Inc. Indicating website reputations during an electronic commerce transaction
US9384345B2 (en) * 2005-05-03 2016-07-05 Mcafee, Inc. Providing alternative web content based on website reputation assessment
US7809127B2 (en) 2005-05-26 2010-10-05 Avaya Inc. Method for discovering problem agent behaviors
US7640160B2 (en) * 2005-08-05 2009-12-29 Voicebox Technologies, Inc. Systems and methods for responding to natural language speech utterance
US7779042B1 (en) 2005-08-08 2010-08-17 Avaya Inc. Deferred control of surrogate key generation in a distributed processing architecture
US7620549B2 (en) 2005-08-10 2009-11-17 Voicebox Technologies, Inc. System and method of supporting adaptive misrecognition in conversational speech
US7949529B2 (en) 2005-08-29 2011-05-24 Voicebox Technologies, Inc. Mobile systems and methods of supporting natural language human-machine interactions
EP1934971A4 (en) * 2005-08-31 2010-10-27 Voicebox Technologies Inc Dynamic speech sharpening
US7822587B1 (en) 2005-10-03 2010-10-26 Avaya Inc. Hybrid database architecture for both maintaining and relaxing type 2 data entity behavior
US7787609B1 (en) 2005-10-06 2010-08-31 Avaya Inc. Prioritized service delivery based on presence and availability of interruptible enterprise resources with skills
US7752230B2 (en) 2005-10-06 2010-07-06 Avaya Inc. Data extensibility using external database tables
US8285784B2 (en) 2005-11-08 2012-10-09 Alcatel Lucent Service creation via presence messaging
US20070124385A1 (en) * 2005-11-18 2007-05-31 Denny Michael S Preference-based content distribution service
MX2008010131A (en) * 2006-02-07 2009-07-22 Ticketmaster Methods and systems for reducing burst usage of a networked computer system.
US7406222B2 (en) * 2006-02-16 2008-07-29 Pavel Kornilovich Composite evanescent waveguides and associated methods
US8737173B2 (en) * 2006-02-24 2014-05-27 Avaya Inc. Date and time dimensions for contact center reporting in arbitrary international time zones
US8701196B2 (en) 2006-03-31 2014-04-15 Mcafee, Inc. System, method and computer program product for obtaining a reputation associated with a file
CA2651543C (en) * 2006-05-09 2016-02-16 Ticketmaster Apparatus for access control and processing
US8842818B2 (en) * 2006-06-30 2014-09-23 Avaya Inc. IP telephony architecture including information storage and retrieval system to track fluency
US7936867B1 (en) 2006-08-15 2011-05-03 Avaya Inc. Multi-service request within a contact center
US8391463B1 (en) 2006-09-01 2013-03-05 Avaya Inc. Method and apparatus for identifying related contacts
US8811597B1 (en) 2006-09-07 2014-08-19 Avaya Inc. Contact center performance prediction
US8938063B1 (en) 2006-09-07 2015-01-20 Avaya Inc. Contact center service monitoring and correcting
US7573996B1 (en) 2006-10-03 2009-08-11 Avaya Inc. Presence based callback
US8073681B2 (en) 2006-10-16 2011-12-06 Voicebox Technologies, Inc. System and method for a cooperative conversational voice user interface
US8150003B1 (en) 2007-01-23 2012-04-03 Avaya Inc. Caller initiated undivert from voicemail
US7818176B2 (en) 2007-02-06 2010-10-19 Voicebox Technologies, Inc. System and method for selecting and presenting advertisements based on natural language processing of voice-based input
EP1968295B1 (en) * 2007-03-05 2019-01-02 Brother Kogyo Kabushiki Kaisha Communication device
CA2695637C (en) * 2007-08-07 2016-07-26 Ticketmaster, Llc Systems and methods for providing resource allocation in a networked environment
US8504534B1 (en) 2007-09-26 2013-08-06 Avaya Inc. Database structures and administration techniques for generalized localization of database items
US8140335B2 (en) 2007-12-11 2012-03-20 Voicebox Technologies, Inc. System and method for providing a natural language voice user interface in an integrated voice navigation services environment
US8856182B2 (en) 2008-01-25 2014-10-07 Avaya Inc. Report database dependency tracing through business intelligence metadata
US8589161B2 (en) * 2008-05-27 2013-11-19 Voicebox Technologies, Inc. System and method for an integrated, multi-modal, multi-device natural language voice services environment
US9305548B2 (en) 2008-05-27 2016-04-05 Voicebox Technologies Corporation System and method for an integrated, multi-modal, multi-device natural language voice services environment
US8326637B2 (en) 2009-02-20 2012-12-04 Voicebox Technologies, Inc. System and method for processing multi-modal device interactions in a natural language voice services environment
CN101925024B (en) 2009-06-09 2013-02-27 中兴通讯股份有限公司 System and method for transferring upstream text message into multimedia message
US8301581B2 (en) * 2009-09-24 2012-10-30 Avaya Inc. Group compositing algorithms for presence
US8565386B2 (en) 2009-09-29 2013-10-22 Avaya Inc. Automatic configuration of soft phones that are usable in conjunction with special-purpose endpoints
US9171541B2 (en) 2009-11-10 2015-10-27 Voicebox Technologies Corporation System and method for hybrid processing in a natural language voice services environment
WO2011059997A1 (en) 2009-11-10 2011-05-19 Voicebox Technologies, Inc. System and method for providing a natural language content dedication service
US9516069B2 (en) 2009-11-17 2016-12-06 Avaya Inc. Packet headers as a trigger for automatic activation of special-purpose softphone applications
US9529842B2 (en) 2009-12-28 2016-12-27 International Business Machines Corporation Dynamically creating queries to find related records in a database
US9781170B2 (en) 2010-06-15 2017-10-03 Live Nation Entertainment, Inc. Establishing communication links using routing protocols
KR101909742B1 (en) 2010-06-15 2018-10-18 티켓마스터 엘엘씨 Methods and systems for computer aided event and venue setup and modeling and interactive maps
US9282185B2 (en) 2011-10-17 2016-03-08 At&T Intellectual Property I, L.P. System and method for callee-caller specific greetings for voice mail
US9042527B2 (en) 2011-10-17 2015-05-26 At&T Intellectual Property I, L.P. Visual voice mail delivery mechanisms
US9025739B2 (en) 2011-10-20 2015-05-05 At&T Intellectual Property I, L.P. System and method for visual voice mail in a multi-screen environment
US8515029B2 (en) 2011-11-02 2013-08-20 At&T Intellectual Property I, L.P. System and method for visual voice mail in an LTE environment
US8489075B2 (en) 2011-11-16 2013-07-16 At&T Intellectual Property I, L.P. System and method for augmenting features of visual voice mail
US20140379390A1 (en) 2013-06-20 2014-12-25 Live Nation Entertainment, Inc. Location-based presentations of ticket opportunities
US9898459B2 (en) 2014-09-16 2018-02-20 Voicebox Technologies Corporation Integration of domain information into state transitions of a finite state transducer for natural language processing
US9626703B2 (en) 2014-09-16 2017-04-18 Voicebox Technologies Corporation Voice commerce
EP3207467A4 (en) 2014-10-15 2018-05-23 VoiceBox Technologies Corporation System and method for providing follow-up responses to prior natural language inputs of a user
US9807096B2 (en) 2014-12-18 2017-10-31 Live Nation Entertainment, Inc. Controlled token distribution to protect against malicious data and resource access
WO2018023106A1 (en) 2016-07-29 2018-02-01 Erik SWART System and method of disambiguating natural language processing requests

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5345587A (en) * 1988-09-14 1994-09-06 Digital Equipment Corporation Extensible entity management system including a dispatching kernel and modules which independently interpret and execute commands
US5058152A (en) * 1989-12-12 1991-10-15 The Telephone Connection Anonymous interactive telephone system having direct connect feature
NZ269342A (en) * 1993-06-28 1998-05-27 Bellsouth Corp Mediating message traffic across advanced intelligent network interfaces
US5555376A (en) * 1993-12-03 1996-09-10 Xerox Corporation Method for granting a user request having locational and contextual attributes consistent with user policies for devices having locational attributes consistent with the user request
EP0675625A1 (en) * 1994-03-31 1995-10-04 Zucker, JoAnn Method of using telephone system to transmit certified messages
US5557320A (en) * 1995-01-31 1996-09-17 Krebs; Mark Video mail delivery system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
EP0782316B1 (en) 2005-03-16
DE69634473D1 (en) 2005-04-21
DE69637221D1 (en) 2007-10-04
CA2192502A1 (en) 1997-06-30
DE69637221T2 (en) 2008-05-21
CA2192502C (en) 1999-12-07
EP1549034A1 (en) 2005-06-29
DE69634473T2 (en) 2006-01-05
US5742763A (en) 1998-04-21
EP0782316A3 (en) 2000-05-24
JPH09219724A (en) 1997-08-19
EP0782316A2 (en) 1997-07-02

Similar Documents

Publication Publication Date Title
CA2477652C (en) Method and process for signaling, communication and administration of networked objects
US6282565B1 (en) Method and apparatus for performing enterprise email management
US6404762B1 (en) Universal messaging system providing integrated voice, data and fax messaging services to pc/web-based clients, including a session manager for maintaining a session between a messaging platform and the web-based clients
US7181495B2 (en) Method and system for filtering notification of e-mail messages
US8189759B2 (en) System and method for automatic call back using availability information
US6993561B2 (en) Method and apparatus for maintaining a unified view of multiple mailboxes
US9544427B2 (en) Methods, systems, and products for processing communications
EP0720333B1 (en) Message filtering techniques
US9251193B2 (en) Extending user relationships
US7027463B2 (en) System and method for multi-tiered rule filtering
US7512788B2 (en) Method and apparatus for anonymous group messaging in a distributed messaging system
US7302471B2 (en) Method for reducing the receipt of unsolicited bulk e-mail and providing anonymity to an email-user
USRE43284E1 (en) Method of triggering a transfer of data stored in a database
US7593925B2 (en) Method and system for locating contact information collected from contact sources
EP1142232B1 (en) Communications prioritizer
CA2436061C (en) System and method for facilitating communication using presence and communication system
US7907704B2 (en) Caching user information in an integrated communication system
CN100525255C (en) Value-added electronic messaging services and transparent implementation thereof using intermediate server
EP1177666B1 (en) A distributed system to intelligently establish sessions between anonymous users over various networks
US7484213B2 (en) Agent architecture employed within an integrated message, document and communication system
US6816884B1 (en) System and method for creating conversationally-styled summaries from digesting email messages
JP4499296B2 (en) The caller id and e-mail address for the integration Register
US6732156B2 (en) System for routing electronic mails
KR101511924B1 (en) Sender identification system and method
EP1013068B1 (en) Electronic mail distribution system for integrated electronic communications

Legal Events

Date Code Title Description
AC Divisional application (art. 76) of:

Ref document number: 0782316

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states:

Kind code of ref document: A1

Designated state(s): DE FR GB

17P Request for examination filed

Effective date: 20050314

AKX Payment of designation fees

Designated state(s): DE FR GB

AC Divisional application (art. 76) of:

Ref document number: 0782316

Country of ref document: EP

Kind code of ref document: P

AK Designated contracting states:

Kind code of ref document: B1

Designated state(s): DE FR GB

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 69637221

Country of ref document: DE

Date of ref document: 20071004

Kind code of ref document: P

ET Fr: translation filed
26N No opposition filed

Effective date: 20080526

PGFP Postgrant: annual fees paid to national office

Ref country code: FR

Payment date: 20101203

Year of fee payment: 15

PGFP Postgrant: annual fees paid to national office

Ref country code: GB

Payment date: 20101123

Year of fee payment: 15

PGFP Postgrant: annual fees paid to national office

Ref country code: DE

Payment date: 20101230

Year of fee payment: 15

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20111223

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20120831

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 69637221

Country of ref document: DE

Effective date: 20120703

PG25 Lapsed in a contracting state announced via postgrant inform. from nat. office to epo

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120703

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20111223

PG25 Lapsed in a contracting state announced via postgrant inform. from nat. office to epo

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120102