WO2002063832A1 - A system and method for filtering unavailable devices in a presence and availability management system - Google Patents

A system and method for filtering unavailable devices in a presence and availability management system Download PDF

Info

Publication number
WO2002063832A1
WO2002063832A1 PCT/US2002/003478 US0203478W WO02063832A1 WO 2002063832 A1 WO2002063832 A1 WO 2002063832A1 US 0203478 W US0203478 W US 0203478W WO 02063832 A1 WO02063832 A1 WO 02063832A1
Authority
WO
WIPO (PCT)
Prior art keywords
individual
availability
network
subscriber
communication network
Prior art date
Application number
PCT/US2002/003478
Other languages
French (fr)
Inventor
Athanassios Diacakis
Daniel Cohen
Original Assignee
Personity, Inc.
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
Application filed by Personity, Inc. filed Critical Personity, Inc.
Priority to EP02709372A priority Critical patent/EP1364491A1/en
Publication of WO2002063832A1 publication Critical patent/WO2002063832A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/50Address allocation
    • H04L61/5038Address allocation for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/08Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087Inventory or stock management, e.g. order filling, procurement or balancing against orders
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/107Computer-aided management of electronic mailing [e-mailing]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04Real-time or near real-time messaging, e.g. instant messaging [IM]
    • H04L51/043Real-time or near real-time messaging, e.g. instant messaging [IM] using or handling presence information
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/48Message addressing, e.g. address format or anonymous messages, aliases
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00Network arrangements, protocols or services for addressing or naming
    • H04L61/45Network directories; Name-to-address mapping
    • H04L61/4505Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/2866Architectures; Arrangements
    • H04L67/30Profiles
    • H04L67/306User profiles
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/51Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/52Network services specially adapted for the location of the user terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/54Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40Network security protocols
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21Monitoring or handling of messages
    • H04L51/214Monitoring or handling of messages using selective forwarding
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer [OSI layer 7]

Definitions

  • the present invention relates generally to communications and, more particularly, to presence and availability management systems.
  • a presence and availability management system enables users to control their availability and how that is displayed to other users. Accordingly, users may select if they want to be available to any given person (or group of people) or not, as well as how that person (or group of people) may or may not contact them.
  • a presence and availability management service enables users to view the availability of their contacts and use that information to determine whether or not and how to initiate communications.
  • Presence and availability management services have two primary functions. First, to collect information from multiple sources to determine the presence and, according to user-defined preferences, the availability of a given person. For example, a presence and availability management service needs information on what communications network a user is on, and whether or not the user is reachable for each of the networks. Second, a presence and availability management service must distribute the availability information of a given person to interested individuals on a selective basis, according to a variety of user-defined preferences and settings.
  • a presence and availability management service provides users with the ability to configure an observer's access settings, thereby giving users the ability to control what contact information observers are allowed to view. Thus, users have the choice of what information is published to each of their observers.
  • the present invention is directed to a method for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information.
  • the method includes detecting whether the individual is present on at least one communication network and determining availability of the individual for each access level of a profile of the individual.
  • the method further includes publishing via a network the availability of the individual to the subscriber based on an access level of the subscriber and the presence information.
  • the method includes filtering the availability of the individual when it is detected that the individual is no longer present on the communication network.
  • the present invention is directed to a presence and availability (P&A) management server for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information.
  • the server includes a presence detection engine for detecting whether the individual is present on at least one communication network and an availability management engine in communication with the presence detection engine for publishing to the subscriber, via a network, communication network availability of the individual.
  • the server additionally includes an adaptive feedback module in communication with the presence detection engine and the availability management engine.
  • FIG. 1 is a block diagram of a presence and availability (P&A) management system according to one embodiment of the present invention
  • Figure 2 is an example of an availability profile according to one embodiment of the present invention.
  • Figure 3 is a diagram depicting what information subscribers at various access levels receive for the profile of Figure 2;
  • Figure 4 is a diagram of a P&A management server according to one embodiment of the present invention
  • Figure 5 is a diagram illustrating the process flow through the P&A management server of Figure 4 according to one embodiment of the present invention
  • Figure 6 is a diagram of the P&A management server according to one embodiment of the present invention
  • Figure 7 is a diagram illustrating the process flow through the P&A management server of Figure 6 according to one embodiment of the present invention.
  • Figure 8 is a screen shot of a subscriber according to one embodiment of the present invention.
  • Figure 9 is a diagram of a client terminal according to one embodiment of the present invention.
  • Figure 10 is a diagram of the process flow through the client terminal of Figure 9 according to one embodiment of the present invention.
  • Figure 11 is a diagram of a system with a secondary domain name server according to one embodiment of the present invention.
  • FIG 1 is a diagram of a presence and availability (P&A) management system 10 according to one embodiment of the present invention.
  • the system includes a P&A management server 12 in communication with a client terminal 22 via a network 16.
  • the client terminal 22 is sometimes referred to herein as "a client.”
  • the P&A management server 12 include a presence detection engine 18 and an availability management engine 20.
  • Profile information may be stored in a database 24 of the server 12.
  • the P&A management server 12 is in communication with at least one client terminal 22.
  • only one client terminal 22 is illustrated, although a number of other client terminals may also be in communication with the P&A management server 12 via the network 16.
  • the client terminal 22 is illustrated as a personal computer in Figure 1, although according to other embodiments the client terminal may be another type of communication device such as, for example, a wireless telephone (such as a WAP (Wireless Application
  • PDA personal digital assistant
  • the network 16 may be any connected system of, for example, communication lines, channels, and radio interfaces, used to exchange information between the P&A management server 12 and the client 22.
  • the network 16 may include, for example, the Internet, an intranet, the public switched telephone network (PSTN), or a wireless telephone or radio network.
  • PSTN public switched telephone network
  • the P&A management server 12 and client 22 may communicate via the network 16 using an open draft TCP/IP based protocol.
  • Presence is defined as the ability of an individual to access a particular communications network. For example, if a person is near a landline telephone or wireless telephone that is switched on, that person is "present” on a telephone network, i.e., the person is able to use the telephone network to communicate with other people also on the network. Conversely, if a person is not near a landline telephone or wireless telephone, or the wireless telephone is switched off, then that person is not present on a telephone network, and thus unable to communicate with others on the telephone network. Similarly, if a person uses an instant messaging (IM) application at a given point in time, the person is present on that instant messaging network.
  • IM instant messaging
  • the term "availability" is defined as the willingness of an individual who is present on one or more communications networks to be reached by one or more persons. Following the telephone network example above, if a person is near a landline or wireless telephone and has the intention or willingness to answer the phone when a particular person calls, the person is not only present but available on the telephone network. However, if the person is unwilling or unable to answer either phone when it rings, although present, the person is not available. It should be noted that a person needs to be present on a network in order to be available, yet the opposite is not necessarily true. In addition, presence is absolute. That is, a person is either present or not on a given network. However, availability depends on, e.g., other people, situations, circumstances, personal preferences, etc. For example, a person can be available to a first group of people, but unavailable to a separate group.
  • the system 10 employs a publisher-subscriber model.
  • an individual defines a P&A profile set, which is stored on the P&A management server 12.
  • the server publishes the change to each of the connected clients 22 that are subscribers of the individual's information.
  • the publisher-subscriber model enables subscribers to observe a particular individual's P&A information instantly.
  • a user of the client terminal 22 is typically referred to as "subscriber.”
  • subscriber is used synonymously with the term "observer.”
  • observer One instance, however, in which an observer is not the same as a subscriber is if someone requests an individual's P&A information just once, without placing a subscription for it.
  • the system 10 is illustrated as including only one server 12 and one client 22, although other embodiments of the present invention contemplate a distributed architecture including multiple management servers and multiple clients.
  • An individual user of the system 10 may initially configure his P&A profile settings in order to instruct the system 12 how his information is to be distributed.
  • the individual may configure their P&A management profile set according to the following steps. First, the individual is requested to enter information regarding each of the communication devices that the individual uses and a corresponding address for each of those devices. For example, the individual may have a landline telephone with a phone number and a computer workstation with an e-mail address. Second, the individual identifies and categorizes the people to whom he wants his information published. This allows individuals to select the "more important" people and to give them easier access, whereas the "less important" people are given minimum access, and undesirable groups of people are restricted from access altogether.
  • access levels may be referred to as "access levels.”
  • the individual may define a series of profiles that describe a situation that the individual may be in such as, for example, "at home,” “at office,” or “on the road.” Further, the individual may identify how he wishes to be communicated with for each profile and for each access level. In addition, where several modes of communication over one medium are possible, the individual may identify which mode is preferable.
  • an individual may have an office profile as indicated in Figure 2.
  • a subscriber with an access level of "Important” would receive the items marked “Yes” in the "Important” column, with the preference indicated (where appropriate), thereby making it very easy for "important" subscribers to communicate with the individual.
  • Persons in the "Normal” access level would receive less contact information than persons in the "Important” access level, and persons in the "Restricted” access level would receive even less contact information.
  • Persons in the "Blocked” access level would receive no contact information at all.
  • the individual may specify which persons belong to each access level for each profile.
  • subscribers in various access groups would have access to different information regarding the individual.
  • the individual may define other profiles for different situations such as, for example, "at home,” “on the road,” “meeting” and “vacation.”
  • the individual's profile for each of these situations may define a profile set.
  • an individual may configure his profile such that subscribers at certain access levels have access to the individual's P&A information at certain times. For example, the individual may configure his profile such that his boss has access to the individual's P&A while the individual is at work; his wife has access all the time; and his parents have access only on weekends while not at work. Accordingly, when the P&A management server 12 detects a change in, for example, the individual's situation, the P&A management server 12 consults the individual's defined rules and preferences (which may be stored by the P&A management server 12), and transmits the appropriate information to the clients 22 for subscribers to the individual's information based on the subscriber's access groups. The presence detection engine 18 may detect a change in the individual's situation, as described further hereinafter, or the individual may communicate the change to the management server 12 directly.
  • the server 12 transmits the individual's updated P&A information to the clients 22 for the individual's boss and spouse.
  • the information that the boss and spouse receive may be different based on their access levels, as discussed previously. For example, the boss may be informed of the individual's instant messaging information, but the individual's wife may not. When the individual returns home, the wife's information may be updated and the individual's parent may begin receiving information regarding the individual's
  • An individual may define his profile set, including his rules and preferences, via a user-interface in communication with the P&A management server 12.
  • the user-interface may comprise a graphical user interface (GUI) application loaded on a computer device in communication with the P&A management server 12.
  • GUI graphical user interface
  • the P&A management server 12 may store the profiles, rules and preferences in a database (not shown). For security purposes, access to an individual's profiles etc. may be based on verification of a user PIN, password or other security mechanism. Accordingly, an individual may modify his profile settings as necessary.
  • FIG 4 is a diagram of the P&A management server 12 according to one embodiment of the present invention.
  • the server 12 includes a presence detection engine 18 and an availability management engine 20.
  • the presence detection engine 18 may determine an individual's presence upon particular networks based on various inputs, as described further hereinbelow.
  • the presence detection engine 18 may transmit the presence information to the availability management engine 20, which in turn may determine the individual's availability based on the presence information as well as additional information, such as the individual's situation and defined rules and preferences.
  • the determined availability information may then be transmitted to subscribers of the individual's availability information via the network 16, as described previously.
  • the engines 18, 20 may be implemented as software code to be executed by a processor in the server 12 using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques.
  • the software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
  • the presence detection engine 18 may receive various inputs to determine, to the extent possible, the individual's presence.
  • One type of input that the presence detection engine 18 may use to help determine the individual's presence is time-based input 40. For example, based on time of day information and known scheduling/calendar information, the presence detection engine 18 may be able to determine an individual's presence. For example, if the individual had scheduled to be in his office from 9am to 5pm, the presence detection engine 18 may determine that during that time period the individual is present on the networks available to him in his office, which may be, for example, telephone and instant messaging.
  • user- location input 42 Another type of input that the presence detection engine 18 may use is user- location input 42.
  • User-location information may be supplied, for example, from a number of possible networks or devices in communication with the server 12.
  • the server 12 may include a radio receiver such that the presence detection engine 18 is in communication with radio networks including, for example, a Bluetooth network, that may communicate information relating to the individual's physical locale.
  • the server 12 may be in communication with a GPS receiver associated with the user.
  • the presence detection engine 18 may be in communication with Enhanced 911 (E-911) networks for possible user-location information.
  • E-911 Enhanced 911
  • the presence detection engine 18 may receive input from various hardware devices that may relate information regarding user location.
  • the presence detection engine 18 may receive information from cameras, such as security cameras located at a place of employment.
  • the camera information may relate information as to whether the individual is in the locale of his place of employment.
  • the presence detection engine 18 may receive input from sensors, such as pressure sensors, to help ascertain the locus of the individual.
  • the pressure sensors may be, for example, located in the office chair or the computer keyboard of the individual, thus providing information regarding the individual's locus.
  • the presence detection engine 18 may receive inputs from security equipment, such as active badge sensors, smart card sensors and/or magnetic card readers to help ascertain the location of the individual.
  • the presence detection engine 18 may be in communication with other networks/device to help determine presence information.
  • the presence detection engine 18 may be in communication with a SS7 network of the public switched telephone network (PSTN) to determine if the individual is present on a landline telephone such as, for example, the landline desk phone 44 in his office.
  • PSTN public switched telephone network
  • the presence detection engine 18 may be in communication with a service control point (SCP) of the SS7 network.
  • SCP service control point
  • the presence detection engine 18 may receive inputs from a Home Location Register (HLR) of a wireless telephone network to determine if the individual is present on his mobile phone 46.
  • the wireless telephone network may be, for example, an AMPS (Advanced Mobile Phone Service) network, a TACS (Total Access Communication
  • the presence detection engine 18 may also or instead of be in communication with a short messaging system center (SMS-C) of a short messaging system network or a gateway GPRS support node (GGSN).
  • SMS-C short messaging system center
  • GGSN gateway GPRS support node
  • the presence detection engine 18 may be in communication with a server of a computer network.
  • the presence detection engine 18 may also receive inputs from computer networks such as, for example, a local Ethernet, a LAN, a wireless LAN, a MAN, a WAN, or a TCP/IP network, to determine if the individual is present on such a network, such as via his personal computer (PC) 48. Similarly, the presence detection engine 18 may be in communication with communication networks to determine whether an individual is present on other devices such as, for example, a personal digital assistant (PDA) 50 or a pager 52. Based on the presence information on such devices 44-52, the presence detection engine 18 may determine additional information about the individual, such as the individual's status 54 on particular networks (such as on or off) or the individual's physical location 56. In addition, based on information regarding each of these devices 44-53 the presence detection engine 18 may determine the individual's current capabilities 58 such as, for example, whether he can receive voice information, data files, audio files, video files, etc.
  • computer networks such as, for example, a local Ethernet, a LAN,
  • the presence information ascertained by the presence detection engine 18 is communicated to availability management engine 20, which determines the individual's availability based thereon. To detennine the individual's availability, the availability management engine 20 may receive information transmitted by the individual regarding a change in their situation 60. Such a change in user situation may be communicated to the availability management engine 20 through a communication network such as, for example, an IP network, a telephone network, or a radio network.
  • the availability management engine 20 may consult the individual's rules and preferences to determine the individual's availability based on, for example, the presence information from the presence detection engine 18 and the individual's situation.
  • the individual's rules and preferences may be stored in a database 64, as illustrated in Figure 4, or may be stored with the profile information in the database 24. Additionally, the individual may specify the observers 62 who receive the individual's contact information. The observers may be specified according to, for example, a group basis or an individual basis.
  • the observer classification information may also be stored in a database, such as the profile database 24.
  • the availability information may then be published to the individual's subscribers (via the client terminals). Because the availability information is determined, in part, based on the presence information from the presence detection engine 18, the availability management engine 20 may modify the published contact information sent to subscribers based on the presence information if, for example, the individual's profile is inconsistent with the actual individual's presence. Thus, availability management engine 20 may be configured to take the presence information into account and cease from relaying the inconsistent contact information to subscribers.
  • FIG. 5 is a diagram of the process flow of the P&A management server 12 according to one embodiment of the present invention.
  • the process initiates at block 88 where the presence detection engine 18 ascertains presence information regarding the user as described previously.
  • the user's current profile is retrieved from the profile database 24 based on the current user situation.
  • the list of observers for each access level e.g., important, normal, restricted, work, blocked, etc. for the current profile is retrieved.
  • the availability management engine 20 may determine the user's availability for each access level based on the user's profile.
  • the availability information is distributed (published) to the subscribers of the information via the network 16 on a per access level basis.
  • the availability management engine 20 may first retrieve the appropriate profile based on the individual's situation. The individual's presence and availability information may then be filtered before it is published to the observers.
  • Figure 6 is a diagram of the P&A management server 12 according to such an embodiment.
  • the illustrated embodiment includes an adaptive feedback module 100, which may be implemented, for example, as software code to be executed by a processor of the server 12 using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques.
  • the software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
  • a computer readable medium such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
  • the adaptive feedback module 100 may monitor the published availability information and, if the information is, for example, inaccurate or unusable, make adjustments to either the presence detection engine 18 or the availability management engine 20 to ensure the integrity of the published availability information. For example, if the published availability information for an individual indicates that he is available on his mobile telephone, but if the last three times someone called the individual on his mobile telephone the individual did not answer, then the adaptive feedback module 100 may instruct the presence detection engine 18 of this condition such that the published availability information for the individual will not longer indicate mobile telephone availability to the appropriate access levels until there is evidence that the individual resumes usage of his mobile telephone. The adaptive feedback module 100 may determine whether the individual's availability information is, for example, inaccurate or unusable based on information received from the appropriate communication networks with which the P&A management server 12 interfaces, as described previously.
  • the adaptive feedback module 100 may offer the individual a suggestion that the individual has the option of choosing to accept or reject. For example, if the adaptive feedback module 100 determines that the individual has not answered his last three telephone calls although he is present on the network, the adaptive feedback module 100 may send the individual a message asking whether he wants to discontinue publishing whether he is available on the telephone network. In this way, the individual has the ability to tune his presence and availability information.
  • FIG 7 is a diagram of the process flow through the P&A management server 12 of Figure 6 according to such an embodiment.
  • the process initiates at block 102, where the availability management engine 20 retrieves the individual's profile based on the individual's present situation, as discussed previously.
  • the availability management engine 20 may retrieve the user-specified list of subscribers for each access level of the profile.
  • the availability management engine 20 may determine the availability of the user for each access level.
  • the presence detection engine 18 may ascertain the individual's presence on each of the monitored networks, as discussed previously. Based on this information, at block 108, the adaptive feedback module 100 may filter the individual's P&A information, as discussed previously. Next, at block 109, the P&A management server 12 may publish the information to each of the subscribers.
  • the P&A management server 12 may transmit the availability information to the subscriber at the client terminal 22.
  • Figure 8 is a screen shot of the information that may be displayed to a subscriber at a client terminal 22 according to one embodiment of the present invention. As illustrated, the subscriber may navigate the list of names in the right hand window ("Contacts Program") to access the P&A information regarding the highlighted individual in the left hand window ("Contact Properties").
  • the indicator in the right hand window adjacent to each listed individual may identify the availability means for the particular individual. For example, in Figure 8 Alex is available by telephone and instant messaging, but Tom is only available by telephone and Pete is only available by instant messaging.
  • the contact information in the left hand window may be updated based on availability information transmitted from the identified individual's P&A management server 12.
  • the P&A management server 12 may store individuals' P&A information profiles in the database 24.
  • individuals By storing the P&A information profiles on the server 12, individuals only need to send small amounts of information to the server 12 when changing their profile. For example, when an individual using a mobile device requests a switch to, for example, an "At Home” situation, the individual only needs to send a small amount of information via the mobile device instructing the server 12 to implement the "At Home” profile rather than having to send all the P&A information associated with the "At Home” situation, which may be considerably larger.
  • the server 12 may have the necessary information available when individuals switch profiles. Thus, individuals only need to let the server 12 know which situation profile they prefer.
  • Storing the P&A information profiles on the server 12 additionally reduces the amount of resources required to invoke a profile switch operation. This may be an important feature, particularly when mobile and/or handheld devices are used. This is because conventional mobile and handheld devices, in contrast to conventional computer workstations, do not have the capability to store and process large amounts of information in relatively brief time periods. Furthermore, by reducing the amount of information transmitted, the system 10 avoids slower response times, increased latency and in general improves the user's services and experience.
  • the display at the client terminal 22 may relate the various entries for an individual and merge them together as one entry. For example, with reference to Figure 8, there is one entry (indicator) for Alex, indicating that Alex is available on a telephone network and an IM network. This is indicated by the telephone icon and the IM icon next to Alex's name.
  • the single summary indicator may be a summary of the individual's availability, with the single summary indicator containing several different icons or states that convey the availability information.
  • the icons may indicate types of data the individual is available to receive such as, for example, text files, audio files, streaming audio files, video files, streaming video files, graphics files and streaming graphics files.
  • the single indicator may be used to indicate the network type that the individual is available on such as, for example, IM, telephone, facsimile, etc.
  • Other network types include a short messaging system (SMS) network, a voice over IP (VoIP) network, a paging network and a two-way paging network.
  • SMS short messaging system
  • VoIP voice over IP
  • the single indicator may indicate the device type that the individual is available one, such as, for example, wireless telephone, landline telephone, personal digital assistant (PDA), computer, etc.
  • PDA personal digital assistant
  • Other device types include a SMS phone, a pager, a two-way pager, a wireless PDA, a WAP phone, and a GPRS phone.
  • the single indicator may be used to indicate the availability of a group of people based on whether at least one person of the group
  • the single indicator may merge the availability of each individual of the group into one indicator that summarizes whether the sales staff is available.
  • the group may provide a service such as, for example, technical support, customer service, sales, etc.
  • the single indicator may indicate that the sales staff is available.
  • Any type of group may be used.
  • other groups include employees of a company, employees of a given department, field sales representative, customer relationship management employees.
  • Other groups include, for example, volunteers and members of a club or social group.
  • a large number of inputs for each of an individual's communications devices on the various networks may be processed using the presence detection engine 20 to determine the P&A status of that individual, thus allowing the results to be combined in a single availability indicator. For example, if John Doe has three telephone numbers (e.g., home, work and wireless) and is currently present and available on only one telephone network, the server 12 may notify subscribers of John Doe's information that he is present and available for telephone calls regardless of the particular telephone John Doe is currently capable of using.
  • the server 12 may notify subscribers of John Doe's information that he is present and available for telephone calls regardless of the particular telephone John Doe is currently capable of using.
  • FIG. 9 is a block diagram of the client terminal 22 according to one embodiment for realizing the single summary indicator described previously. As illustrated in Figure 9, the client terminal includes an indicator module 110 in communication with a user interface 112.
  • the indicator module 110 may be, for example, implemented as software code to be executed by a processor of the client terminal 22 using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques.
  • the software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-
  • RAM random access memory
  • ROM read only memory
  • magnetic medium such as a hard-drive or a floppy disk
  • optical medium such as a CD-
  • the user interface 112 may include, for example, a GUI (Graphical User Interface) or a GUI (Character-based user interface).
  • the indicator module 110 may receive availability information from one or more P&A management servers 12 and merge the contact information for each individual into a single summary indicator, as described previously in connection with
  • the indicator may identify the individual, such as by name, as illustrated in Figure 8.
  • the indicator generated by the indicator module 110 may indicate whether the individual is available to receive, for example, certain data content types.
  • the indicator for Jonathan identifies Jonathan by name and indicates that Jonathan is available to the subscriber to receive data content by telephone and instant messaging.
  • Figure 10 is a diagram of the process flow through the indicator module 110 according to one embodiment.
  • the process initiates at block 120, where the indicator module 110 receives the availability information of each individual to which the client is a subscriber (n individuals).
  • the client terminal receives the availability information for Alex, Jonathan, Kit, Corby, Cyndi, Tom, Pete, Roberto, Cecelia, as well as the individuals in the "Mint" folder.
  • the indicator module 110 may generate a single summary indicator for each of the n individuals.
  • the indicator module 110 may relate the various addresses for a given individual and merge them into a single summary indicator for each of the individuals, as illustrated in Figure 8.
  • a counter, k is set to equal 1.
  • the indicator module 110 may determine whether an address for each data content type (e.g., telephone, text (IM), video, graphic, audio, etc.) has been transmitted from the P&A management server 12. For a particular content type, if no address has been received, the process advances to block 128 where the indicator module 110 displays that individual k is not available for the particular content type. For example, with reference to Figure 8, the indicator for Tom indicates that Tom is not available to receive IM (text) data.
  • data content type e.g., telephone, text (IM), video, graphic, audio, etc.
  • the process advances to block 130 where the indicator module 110 may display that the individual is available to receive the particular data content type. This process may be repeated for each data content type.
  • the process advances to block 132, where k is set to equal k + 1. From block 132 the process advances to block 134 where it is determined whether k equals n. If so, the process is completed at block 136. If not, the process returns to block 124 where the process may be repeated for the next individual.
  • the indicator module 110 is illustrated as residing on the client terminal 22.
  • the indicator module 110 may reside, for example, on the P&A management server 12. According to such an embodiment, the P&A management server 12 may forward the indicator information via the network 16 to the client terminal 22 for display thereby.
  • the client 22 is a device of limited processing capability such as, for example, a WAP-enabled telephone.
  • embodiments of the present invention utilize a publisher-subscriber model. That is, the individual's availability information is published on an event-triggered basis to subscribers of the individual's availability information, rather than transmitted only when requested by the subscriber. Accordingly, changes in an individual's availability are broadcast instantly to subscribers of the individual's P&A information, assuming those subscribers satisfy the individual's rules and preferences regarding dissemination of his P&A information.
  • the P&A management server 12 may maintain the individual's profile settings.
  • the subscribers may be equipped with client software that allows the P&A information of various individuals to be displayed for the subscriber, such as illustrated in conjunction with Figure 8.
  • users of the P&A management system 10 may configure their P&A profiles to specify how their availability information is distributed. Individuals may accomplish this task by specifying a number of different access levels and situations. Subscribers of the individual's information are only provided with certain availability information depending on their access level and the situation.
  • the P&A profiles may be stored on the P&A management server 12 (such as in database 24). This obviates the need for individuals to re-transmit all their contact information each time their availability changes. Rather, the P&A management server 12 may determine the individual's availability based merely on the individual's profile and information regarding the individual's situation.
  • a subscriber at client terminal 22 may first attempt to communicate with an individual at client terminal 140 via one or more intermediate relay hosts 142.
  • One of the hosts 142 may be, for example, an instant messaging host or a presence and availability host.
  • the first relay host 142a may attempt to communicate with the second relay host 142b by, for example, resolving a record (such as an MX record for e-mail) for the second relay host 142b at a primary domain name server 144. If that fails, the first relay host 142a could attempt to resolve the record at a secondary domain name server 146.
  • the address for the record at the primary domain name server 144 may be a hierarchical extension of the address of the secondary domain name server 146, as described further herein.
  • domain name server includes both domain name servers for UNIX networks as well as Windows networks, commonly referred to as "WINS" (Windows Internet Naming Service).
  • the secondary domain name server 146 may include a resolver 148 and an IP address database 150.
  • the IP address database may include the IP address for the intermediate relay host 142b that the primary domain server 144 did not include.
  • the resolver 148 may respond with the address of the second intermediate relay host after interrogating the database 150.
  • the secondary domain name server 146 may supply the address directly to the first relay host 142a or, according to another embodiment, may supply it to the primary domain name server 144, which in turn may supply the address to the relay host 142a.
  • the first domain name server could direct the relay host 142a to the secondaiy domain name server 146, efg.com, to resolve im.abcd.com.resolver.efg.com.
  • the secondary domain name server 146 may be configured appropriately through a web-based interface and, when queried, would direct the relay host 142a to the appropriate server (to im.abcd.com in this example).
  • a query by email for example, may be sent to joe@abcd.com to determine whether the entry may be legitimately made.
  • the process just described is not limited to situations where a host does not know the address of another host.
  • the process may also be utilized to allow a client terminal (such as terminals 22 or 140) resolve the address of a host 142 and vice versa.
  • the primary domain name server 144 may be programmed to supply the address for the secondary domain name server 146 to the intermediate host 142 or client terminal.
  • the client terminal or intermediate host may be programmed with the address of the secondary domain name server 146 for when the primary domain name server 144 is not capable of resolving the request.

Abstract

A method for communicating communication network availability information regarding an individual to at least one subscriber (16) of the individual's availability information. According to one embodiment, the method includes detecting (18) whether the individual is present on at least one communication network and determining (20) availability of the individual for each access level of a profile of the individual. The method further includes publishing via a network the availability of the individual to the subscriber based on an access level of the subscriber and the presence information. In addition, the method includes filtering the availability of the individual when it is detected that the individual is no longer present on the communication network.

Description

A SYSTEM AND METHOD FOR FILTERING UNAVAILABLE DEVICES IN A PRESENCE AND AVAILABILITY MANAGEMENT SYSTEM
CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority under 35 U.S.C. § 119 to U.S. provisional patent application Serial No. 60/266,559, filed February 5, 2001, which is incorporated herein by reference.
BACKGROUND OF INVENTION Field of Invention
The present invention relates generally to communications and, more particularly, to presence and availability management systems.
Description of the Background A presence and availability management system enables users to control their availability and how that is displayed to other users. Accordingly, users may select if they want to be available to any given person (or group of people) or not, as well as how that person (or group of people) may or may not contact them. In addition, a presence and availability management service enables users to view the availability of their contacts and use that information to determine whether or not and how to initiate communications.
Presence and availability management services have two primary functions. First, to collect information from multiple sources to determine the presence and, according to user-defined preferences, the availability of a given person. For example, a presence and availability management service needs information on what communications network a user is on, and whether or not the user is reachable for each of the networks. Second, a presence and availability management service must distribute the availability information of a given person to interested individuals on a selective basis, according to a variety of user-defined preferences and settings.
In addition to those functions, conventional presence and availability management services have two secondary functions. First, to configure access control settings. A presence and availability management service provides users with the ability to configure an observer's access settings, thereby giving users the ability to control what contact information observers are allowed to view. Thus, users have the choice of what information is published to each of their observers. Second, to store user information to enable the use of the presence and availability management service regardless of the user's network device. By storing user information on the back-end of the presence and availability management system, the presence and availability management service enables users to utilize its services regardless of the user's network device as long as they have a device that is within a communications network. Thus, users can access the presence and availability management service if they are on a cellular phone, a handheld device or a computer workstation.
In a conventional presence and availability management enabled communications system, individuals must request the appropriate presence and availability information from the presence and availability management sub-system when they want to communicate with other individuals on the communications network. However, this model poses two issues. First, such systems do not make the presence and availability information about an individual continuously available to others. Thus, the user's interface cannot display the individual's presence and availability information on a continuous basis. Accordingly, users cannot simply quickly glance at a contact list to see who is available. Second, having to retrieve presence and availability information only when it is needed creates a delay at a critical point in time where user tolerance for it is low.
BRIEF SUMMARY OF THE INVENTION
In one general respect, the present invention is directed to a method for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information. According to one embodiment, the method includes detecting whether the individual is present on at least one communication network and determining availability of the individual for each access level of a profile of the individual. The method further includes publishing via a network the availability of the individual to the subscriber based on an access level of the subscriber and the presence information. In addition, the method includes filtering the availability of the individual when it is detected that the individual is no longer present on the communication network.
In another general respect, the present invention is directed to a presence and availability (P&A) management server for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information. According to one embodiment, the server includes a presence detection engine for detecting whether the individual is present on at least one communication network and an availability management engine in communication with the presence detection engine for publishing to the subscriber, via a network, communication network availability of the individual. The server additionally includes an adaptive feedback module in communication with the presence detection engine and the availability management engine.
BRIEF DESCRIPTION OF THE FIGURES Embodiments of the present invention are described in conjunction with the following figures, wherein:
Figure 1 is a block diagram of a presence and availability (P&A) management system according to one embodiment of the present invention;
Figure 2 is an example of an availability profile according to one embodiment of the present invention;
Figure 3 is a diagram depicting what information subscribers at various access levels receive for the profile of Figure 2;
Figure 4 is a diagram of a P&A management server according to one embodiment of the present invention; Figure 5 is a diagram illustrating the process flow through the P&A management server of Figure 4 according to one embodiment of the present invention; Figure 6 is a diagram of the P&A management server according to one embodiment of the present invention;
Figure 7 is a diagram illustrating the process flow through the P&A management server of Figure 6 according to one embodiment of the present invention; Figure 8 is a screen shot of a subscriber according to one embodiment of the present invention;
Figure 9 is a diagram of a client terminal according to one embodiment of the present invention;
Figure 10 is a diagram of the process flow through the client terminal of Figure 9 according to one embodiment of the present invention; and
Figure 11 is a diagram of a system with a secondary domain name server according to one embodiment of the present invention.
DETAILED DESCRIPTION OF THE INVENTION It is to be understood that the figures and descriptions of the following embodiments have been simplified to illustrate elements that are relevant for a clear understanding of the present invention, while eliminating, for purposes of clarity, other elements. For example, certain operating system details and modules of computer processing devices are not described herein. Those of ordinary skill in the art will recognize, however, that these and other elements may be desirable in a typical communications network. However, because such elements are well known in the art, and because they do not facilitate a better understanding of the present invention, a discussion of such elements is not provided herein.
Figure 1 is a diagram of a presence and availability (P&A) management system 10 according to one embodiment of the present invention. The system includes a P&A management server 12 in communication with a client terminal 22 via a network 16. The client terminal 22 is sometimes referred to herein as "a client." The P&A management server 12 include a presence detection engine 18 and an availability management engine 20. Profile information, as described further herein, may be stored in a database 24 of the server 12. The P&A management server 12 is in communication with at least one client terminal 22. In Figure 1, only one client terminal 22 is illustrated, although a number of other client terminals may also be in communication with the P&A management server 12 via the network 16. The client terminal 22 is illustrated as a personal computer in Figure 1, although according to other embodiments the client terminal may be another type of communication device such as, for example, a wireless telephone (such as a WAP (Wireless Application
Protocol)-enabled phone) or a wireless or connected personal digital assistant (PDA).
The network 16 may be any connected system of, for example, communication lines, channels, and radio interfaces, used to exchange information between the P&A management server 12 and the client 22. According to one embodiment, the network 16 may include, for example, the Internet, an intranet, the public switched telephone network (PSTN), or a wireless telephone or radio network. According to one embodiment, the P&A management server 12 and client 22 may communicate via the network 16 using an open draft TCP/IP based protocol.
As used herein, the term "presence" is defined as the ability of an individual to access a particular communications network. For example, if a person is near a landline telephone or wireless telephone that is switched on, that person is "present" on a telephone network, i.e., the person is able to use the telephone network to communicate with other people also on the network. Conversely, if a person is not near a landline telephone or wireless telephone, or the wireless telephone is switched off, then that person is not present on a telephone network, and thus unable to communicate with others on the telephone network. Similarly, if a person uses an instant messaging (IM) application at a given point in time, the person is present on that instant messaging network.
In addition, as used herein the term "availability" is defined as the willingness of an individual who is present on one or more communications networks to be reached by one or more persons. Following the telephone network example above, if a person is near a landline or wireless telephone and has the intention or willingness to answer the phone when a particular person calls, the person is not only present but available on the telephone network. However, if the person is unwilling or unable to answer either phone when it rings, although present, the person is not available. It should be noted that a person needs to be present on a network in order to be available, yet the opposite is not necessarily true. In addition, presence is absolute. That is, a person is either present or not on a given network. However, availability depends on, e.g., other people, situations, circumstances, personal preferences, etc. For example, a person can be available to a first group of people, but unavailable to a separate group.
According to one embodiment, the system 10 employs a publisher-subscriber model. According to such an embodiment, an individual defines a P&A profile set, which is stored on the P&A management server 12. When the individual transmits a change in profile to the server 12, the server publishes the change to each of the connected clients 22 that are subscribers of the individual's information. The publisher-subscriber model enables subscribers to observe a particular individual's P&A information instantly.
Hereinafter, a user of the client terminal 22 is typically referred to as "subscriber." Unless noted otherwise, the term "subscriber" is used synonymously with the term "observer." One instance, however, in which an observer is not the same as a subscriber is if someone requests an individual's P&A information just once, without placing a subscription for it. In Figure 1, the system 10 is illustrated as including only one server 12 and one client 22, although other embodiments of the present invention contemplate a distributed architecture including multiple management servers and multiple clients.
An individual user of the system 10 may initially configure his P&A profile settings in order to instruct the system 12 how his information is to be distributed. According to one embodiment, the individual may configure their P&A management profile set according to the following steps. First, the individual is requested to enter information regarding each of the communication devices that the individual uses and a corresponding address for each of those devices. For example, the individual may have a landline telephone with a phone number and a computer workstation with an e-mail address. Second, the individual identifies and categorizes the people to whom he wants his information published. This allows individuals to select the "more important" people and to give them easier access, whereas the "less important" people are given minimum access, and undesirable groups of people are restricted from access altogether. These different group levels may be referred to as "access levels." Third, the individual may define a series of profiles that describe a situation that the individual may be in such as, for example, "at home," "at office," or "on the road." Further, the individual may identify how he wishes to be communicated with for each profile and for each access level. In addition, where several modes of communication over one medium are possible, the individual may identify which mode is preferable.
For example, an individual may have an office profile as indicated in Figure 2. Thus, a subscriber with an access level of "Important" would receive the items marked "Yes" in the "Important" column, with the preference indicated (where appropriate), thereby making it very easy for "important" subscribers to communicate with the individual. Persons in the "Normal" access level would receive less contact information than persons in the "Important" access level, and persons in the "Restricted" access level would receive even less contact information. Persons in the "Blocked" access level would receive no contact information at all. The individual may specify which persons belong to each access level for each profile.
Accordingly, as illustrated in Figure 3, subscribers in various access groups would have access to different information regarding the individual. Similarly, the individual may define other profiles for different situations such as, for example, "at home," "on the road," "meeting" and "vacation." Collectively, the individual's profile for each of these situations may define a profile set.
As discussed, an individual may configure his profile such that subscribers at certain access levels have access to the individual's P&A information at certain times. For example, the individual may configure his profile such that his boss has access to the individual's P&A while the individual is at work; his wife has access all the time; and his parents have access only on weekends while not at work. Accordingly, when the P&A management server 12 detects a change in, for example, the individual's situation, the P&A management server 12 consults the individual's defined rules and preferences (which may be stored by the P&A management server 12), and transmits the appropriate information to the clients 22 for subscribers to the individual's information based on the subscriber's access groups. The presence detection engine 18 may detect a change in the individual's situation, as described further hereinafter, or the individual may communicate the change to the management server 12 directly.
Thus, with reference to the example mentioned previously, when the P&A management server 12 detects that the individual is at work, the server 12 transmits the individual's updated P&A information to the clients 22 for the individual's boss and spouse. The information that the boss and spouse receive, however, may be different based on their access levels, as discussed previously. For example, the boss may be informed of the individual's instant messaging information, but the individual's wife may not. When the individual returns home, the wife's information may be updated and the individual's parent may begin receiving information regarding the individual's
P&A (although it may not be the same as the wife's information depending on their access levels). The boss, however, will no longer have access to the individual's information.
An individual may define his profile set, including his rules and preferences, via a user-interface in communication with the P&A management server 12. According to one embodiment, the user-interface may comprise a graphical user interface (GUI) application loaded on a computer device in communication with the P&A management server 12. Once defined, the P&A management server 12 may store the profiles, rules and preferences in a database (not shown). For security purposes, access to an individual's profiles etc. may be based on verification of a user PIN, password or other security mechanism. Accordingly, an individual may modify his profile settings as necessary.
In the previous example, a change in the individual's physical location triggered situation changes, and thus a change of profile. It should be noted that other factors may trigger changes in the individual's profile including, for example, time of day and the individual's mood, as explained further hereinbelow.
Figure 4 is a diagram of the P&A management server 12 according to one embodiment of the present invention. As illustrated in Figure 4, the server 12 includes a presence detection engine 18 and an availability management engine 20. The presence detection engine 18 may determine an individual's presence upon particular networks based on various inputs, as described further hereinbelow. The presence detection engine 18 may transmit the presence information to the availability management engine 20, which in turn may determine the individual's availability based on the presence information as well as additional information, such as the individual's situation and defined rules and preferences. The determined availability information may then be transmitted to subscribers of the individual's availability information via the network 16, as described previously.
The engines 18, 20 may be implemented as software code to be executed by a processor in the server 12 using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
As illustrated in Figure 4, the presence detection engine 18 may receive various inputs to determine, to the extent possible, the individual's presence. One type of input that the presence detection engine 18 may use to help determine the individual's presence is time-based input 40. For example, based on time of day information and known scheduling/calendar information, the presence detection engine 18 may be able to determine an individual's presence. For example, if the individual had scheduled to be in his office from 9am to 5pm, the presence detection engine 18 may determine that during that time period the individual is present on the networks available to him in his office, which may be, for example, telephone and instant messaging.
Another type of input that the presence detection engine 18 may use is user- location input 42. User-location information may be supplied, for example, from a number of possible networks or devices in communication with the server 12. For example, the server 12 may include a radio receiver such that the presence detection engine 18 is in communication with radio networks including, for example, a Bluetooth network, that may communicate information relating to the individual's physical locale. In addition, the server 12 may be in communication with a GPS receiver associated with the user. According to another embodiment, the presence detection engine 18 may be in communication with Enhanced 911 (E-911) networks for possible user-location information.
In addition, the presence detection engine 18 may receive input from various hardware devices that may relate information regarding user location. For example, the presence detection engine 18 may receive information from cameras, such as security cameras located at a place of employment. Thus, the camera information may relate information as to whether the individual is in the locale of his place of employment. Additionally, the presence detection engine 18 may receive input from sensors, such as pressure sensors, to help ascertain the locus of the individual. The pressure sensors may be, for example, located in the office chair or the computer keyboard of the individual, thus providing information regarding the individual's locus. Furthermore, the presence detection engine 18 may receive inputs from security equipment, such as active badge sensors, smart card sensors and/or magnetic card readers to help ascertain the location of the individual. Additionally, the presence detection engine 18 may be in communication with other networks/device to help determine presence information. For example, the presence detection engine 18 may be in communication with a SS7 network of the public switched telephone network (PSTN) to determine if the individual is present on a landline telephone such as, for example, the landline desk phone 44 in his office. For example, the presence detection engine 18 may be in communication with a service control point (SCP) of the SS7 network. According to another embodiment, the presence detection engine 18 may receive inputs from a Home Location Register (HLR) of a wireless telephone network to determine if the individual is present on his mobile phone 46. The wireless telephone network may be, for example, an AMPS (Advanced Mobile Phone Service) network, a TACS (Total Access Communication
System) network, a UMTS (Universal Mobile Telecommunications System), a GSM network, a CDMA network, a TDMA network, a GPRS (General Packet Radio Service) network or a wireless CDPD (Cellular Digital Packet Data) network. According to other embodiments, the presence detection engine 18 may also or instead of be in communication with a short messaging system center (SMS-C) of a short messaging system network or a gateway GPRS support node (GGSN). According to another embodiment, the presence detection engine 18 may be in communication with a server of a computer network.
The presence detection engine 18 may also receive inputs from computer networks such as, for example, a local Ethernet, a LAN, a wireless LAN, a MAN, a WAN, or a TCP/IP network, to determine if the individual is present on such a network, such as via his personal computer (PC) 48. Similarly, the presence detection engine 18 may be in communication with communication networks to determine whether an individual is present on other devices such as, for example, a personal digital assistant (PDA) 50 or a pager 52. Based on the presence information on such devices 44-52, the presence detection engine 18 may determine additional information about the individual, such as the individual's status 54 on particular networks (such as on or off) or the individual's physical location 56. In addition, based on information regarding each of these devices 44-53 the presence detection engine 18 may determine the individual's current capabilities 58 such as, for example, whether he can receive voice information, data files, audio files, video files, etc.
The presence information ascertained by the presence detection engine 18 is communicated to availability management engine 20, which determines the individual's availability based thereon. To detennine the individual's availability, the availability management engine 20 may receive information transmitted by the individual regarding a change in their situation 60. Such a change in user situation may be communicated to the availability management engine 20 through a communication network such as, for example, an IP network, a telephone network, or a radio network. The availability management engine 20 may consult the individual's rules and preferences to determine the individual's availability based on, for example, the presence information from the presence detection engine 18 and the individual's situation. The individual's rules and preferences may be stored in a database 64, as illustrated in Figure 4, or may be stored with the profile information in the database 24. Additionally, the individual may specify the observers 62 who receive the individual's contact information. The observers may be specified according to, for example, a group basis or an individual basis. The observer classification information may also be stored in a database, such as the profile database 24.
The availability information may then be published to the individual's subscribers (via the client terminals). Because the availability information is determined, in part, based on the presence information from the presence detection engine 18, the availability management engine 20 may modify the published contact information sent to subscribers based on the presence information if, for example, the individual's profile is inconsistent with the actual individual's presence. Thus, availability management engine 20 may be configured to take the presence information into account and cease from relaying the inconsistent contact information to subscribers.
Figure 5 is a diagram of the process flow of the P&A management server 12 according to one embodiment of the present invention. The process initiates at block 88 where the presence detection engine 18 ascertains presence information regarding the user as described previously. At block 90, the user's current profile is retrieved from the profile database 24 based on the current user situation. At block 92, the list of observers for each access level (e.g., important, normal, restricted, work, blocked, etc.) for the current profile is retrieved.
At block 94, the availability management engine 20 may determine the user's availability for each access level based on the user's profile. At block 98 the availability information is distributed (published) to the subscribers of the information via the network 16 on a per access level basis.
According to another embodiment, the availability management engine 20 may first retrieve the appropriate profile based on the individual's situation. The individual's presence and availability information may then be filtered before it is published to the observers. Figure 6 is a diagram of the P&A management server 12 according to such an embodiment. The illustrated embodiment includes an adaptive feedback module 100, which may be implemented, for example, as software code to be executed by a processor of the server 12 using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-ROM.
The adaptive feedback module 100 may monitor the published availability information and, if the information is, for example, inaccurate or unusable, make adjustments to either the presence detection engine 18 or the availability management engine 20 to ensure the integrity of the published availability information. For example, if the published availability information for an individual indicates that he is available on his mobile telephone, but if the last three times someone called the individual on his mobile telephone the individual did not answer, then the adaptive feedback module 100 may instruct the presence detection engine 18 of this condition such that the published availability information for the individual will not longer indicate mobile telephone availability to the appropriate access levels until there is evidence that the individual resumes usage of his mobile telephone. The adaptive feedback module 100 may determine whether the individual's availability information is, for example, inaccurate or unusable based on information received from the appropriate communication networks with which the P&A management server 12 interfaces, as described previously.
According to one embodiment, the adaptive feedback module 100 may offer the individual a suggestion that the individual has the option of choosing to accept or reject. For example, if the adaptive feedback module 100 determines that the individual has not answered his last three telephone calls although he is present on the network, the adaptive feedback module 100 may send the individual a message asking whether he wants to discontinue publishing whether he is available on the telephone network. In this way, the individual has the ability to tune his presence and availability information.
Figure 7 is a diagram of the process flow through the P&A management server 12 of Figure 6 according to such an embodiment. The process initiates at block 102, where the availability management engine 20 retrieves the individual's profile based on the individual's present situation, as discussed previously. At block 104, the availability management engine 20 may retrieve the user-specified list of subscribers for each access level of the profile. Next, at block 106, based on the user's profile, the availability management engine 20 may determine the availability of the user for each access level.
At block 107, the presence detection engine 18 may ascertain the individual's presence on each of the monitored networks, as discussed previously. Based on this information, at block 108, the adaptive feedback module 100 may filter the individual's P&A information, as discussed previously. Next, at block 109, the P&A management server 12 may publish the information to each of the subscribers.
The P&A management server 12 may transmit the availability information to the subscriber at the client terminal 22. Figure 8 is a screen shot of the information that may be displayed to a subscriber at a client terminal 22 according to one embodiment of the present invention. As illustrated, the subscriber may navigate the list of names in the right hand window ("Contacts Program") to access the P&A information regarding the highlighted individual in the left hand window ("Contact Properties"). The indicator in the right hand window adjacent to each listed individual may identify the availability means for the particular individual. For example, in Figure 8 Alex is available by telephone and instant messaging, but Tom is only available by telephone and Pete is only available by instant messaging. The contact information in the left hand window may be updated based on availability information transmitted from the identified individual's P&A management server 12.
As discussed previously, according to one embodiment the P&A management server 12 may store individuals' P&A information profiles in the database 24. By storing the P&A information profiles on the server 12, individuals only need to send small amounts of information to the server 12 when changing their profile. For example, when an individual using a mobile device requests a switch to, for example, an "At Home" situation, the individual only needs to send a small amount of information via the mobile device instructing the server 12 to implement the "At Home" profile rather than having to send all the P&A information associated with the "At Home" situation, which may be considerably larger. By storing the P&A information profiles on the server 12, the server 12 may have the necessary information available when individuals switch profiles. Thus, individuals only need to let the server 12 know which situation profile they prefer.
Storing the P&A information profiles on the server 12 additionally reduces the amount of resources required to invoke a profile switch operation. This may be an important feature, particularly when mobile and/or handheld devices are used. This is because conventional mobile and handheld devices, in contrast to conventional computer workstations, do not have the capability to store and process large amounts of information in relatively brief time periods. Furthermore, by reducing the amount of information transmitted, the system 10 avoids slower response times, increased latency and in general improves the user's services and experience.
In conventional P&A management systems that support heterogeneous communications networks, a given person may appear several times in the subscriber's contact list - each time corresponding to an available address. For example, each phone number and IM address of a particular individual may be listed. According to an embodiment of the present invention, as illustrated in the "Contacts Program" window of Figure 8, the display at the client terminal 22 may relate the various entries for an individual and merge them together as one entry. For example, with reference to Figure 8, there is one entry (indicator) for Alex, indicating that Alex is available on a telephone network and an IM network. This is indicated by the telephone icon and the IM icon next to Alex's name. Thus, the single summary indicator may be a summary of the individual's availability, with the single summary indicator containing several different icons or states that convey the availability information. According to other embodiments, the icons may indicate types of data the individual is available to receive such as, for example, text files, audio files, streaming audio files, video files, streaming video files, graphics files and streaming graphics files. According to one embodiment, the single indicator may be used to indicate the network type that the individual is available on such as, for example, IM, telephone, facsimile, etc. Other network types include a short messaging system (SMS) network, a voice over IP (VoIP) network, a paging network and a two-way paging network. According to another embodiment, the single indicator may indicate the device type that the individual is available one, such as, for example, wireless telephone, landline telephone, personal digital assistant (PDA), computer, etc. Other device types include a SMS phone, a pager, a two-way pager, a wireless PDA, a WAP phone, and a GPRS phone.
According to another embodiment, the single indicator may be used to indicate the availability of a group of people based on whether at least one person of the group
(or some other threshold number of people from the group) is available. According to such an embodiment, when at least one individual from the group is available, the single indicator may merge the availability of each individual of the group into one indicator that summarizes whether the sales staff is available. For example, the group may provide a service such as, for example, technical support, customer service, sales, etc. Thus, for example, if at least one member of the sales staff is available, the single indicator may indicate that the sales staff is available. Any type of group may be used. For example, other groups include employees of a company, employees of a given department, field sales representative, customer relationship management employees. Other groups include, for example, volunteers and members of a club or social group.
Furthermore, a large number of inputs for each of an individual's communications devices on the various networks may be processed using the presence detection engine 20 to determine the P&A status of that individual, thus allowing the results to be combined in a single availability indicator. For example, if John Doe has three telephone numbers (e.g., home, work and wireless) and is currently present and available on only one telephone network, the server 12 may notify subscribers of John Doe's information that he is present and available for telephone calls regardless of the particular telephone John Doe is currently capable of using. Accordingly, when a subscriber wishes to contact Joe Doe via instant messaging, the server 12 provides the appropriate IM address to the subscriber, taking into account John Doe's preference settings for the subscriber's access group as stored, for example, in the rules and preferences database 64. Thus, embodiments of the present invention may provide a user-friendly interface allowing subscribers to contact individuals without having to be concerned about different communication devices, their addresses and capabilities. Subscribers may instead refer to a single summary indicator and use that information to initiate point-to-point contact. Figure 9 is a block diagram of the client terminal 22 according to one embodiment for realizing the single summary indicator described previously. As illustrated in Figure 9, the client terminal includes an indicator module 110 in communication with a user interface 112. The indicator module 110 may be, for example, implemented as software code to be executed by a processor of the client terminal 22 using any suitable computer language such as, for example, Java, C++ or Perl using, for example, conventional or object-oriented techniques. The software code may be stored as a series of instructions or commands on a computer readable medium, such as a random access memory (RAM), a read only memory (ROM), a magnetic medium such as a hard-drive or a floppy disk, or an optical medium such as a CD-
ROM. The user interface 112 may include, for example, a GUI (Graphical User Interface) or a GUI (Character-based user interface).
The indicator module 110 may receive availability information from one or more P&A management servers 12 and merge the contact information for each individual into a single summary indicator, as described previously in connection with
Figure 8, for display by the user interface 112. The indicator may identify the individual, such as by name, as illustrated in Figure 8. hi addition, as illustrated in Figure 8, the indicator generated by the indicator module 110 may indicate whether the individual is available to receive, for example, certain data content types. For example, with reference to Figure 8, the indicator for Jonathan identifies Jonathan by name and indicates that Jonathan is available to the subscriber to receive data content by telephone and instant messaging.
Figure 10 is a diagram of the process flow through the indicator module 110 according to one embodiment. The process initiates at block 120, where the indicator module 110 receives the availability information of each individual to which the client is a subscriber (n individuals). For example, with reference to Figure 8, the client terminal receives the availability information for Alex, Jonathan, Kit, Corby, Cyndi, Tom, Pete, Roberto, Cecelia, as well as the individuals in the "Mint" folder. At block 122, the indicator module 110 may generate a single summary indicator for each of the n individuals. For example, the indicator module 110 may relate the various addresses for a given individual and merge them into a single summary indicator for each of the individuals, as illustrated in Figure 8.
At block 124, a counter, k, is set to equal 1. At block 126, for individual k for which the client subscribes to contact information, the indicator module 110 may determine whether an address for each data content type (e.g., telephone, text (IM), video, graphic, audio, etc.) has been transmitted from the P&A management server 12. For a particular content type, if no address has been received, the process advances to block 128 where the indicator module 110 displays that individual k is not available for the particular content type. For example, with reference to Figure 8, the indicator for Tom indicates that Tom is not available to receive IM (text) data. Conversely, if at block 126 it is determined that an address has been received for the particular content type, the process advances to block 130 where the indicator module 110 may display that the individual is available to receive the particular data content type. This process may be repeated for each data content type. Once the availability of individual k has been determined for each data content type, the process advances to block 132, where k is set to equal k + 1. From block 132 the process advances to block 134 where it is determined whether k equals n. If so, the process is completed at block 136. If not, the process returns to block 124 where the process may be repeated for the next individual. In Figure 9, the indicator module 110 is illustrated as residing on the client terminal 22. According to other embodiments, the indicator module 110 may reside, for example, on the P&A management server 12. According to such an embodiment, the P&A management server 12 may forward the indicator information via the network 16 to the client terminal 22 for display thereby. Such an embodiment may be advantageous where, for example, the client 22 is a device of limited processing capability such as, for example, a WAP-enabled telephone.
In contrast to some prior P&A management systems, embodiments of the present invention utilize a publisher-subscriber model. That is, the individual's availability information is published on an event-triggered basis to subscribers of the individual's availability information, rather than transmitted only when requested by the subscriber. Accordingly, changes in an individual's availability are broadcast instantly to subscribers of the individual's P&A information, assuming those subscribers satisfy the individual's rules and preferences regarding dissemination of his P&A information. The P&A management server 12, as described previously, may maintain the individual's profile settings. In addition, the subscribers may be equipped with client software that allows the P&A information of various individuals to be displayed for the subscriber, such as illustrated in conjunction with Figure 8.
Additionally, according to one embodiment, users of the P&A management system 10 may configure their P&A profiles to specify how their availability information is distributed. Individuals may accomplish this task by specifying a number of different access levels and situations. Subscribers of the individual's information are only provided with certain availability information depending on their access level and the situation. In addition, the P&A profiles may be stored on the P&A management server 12 (such as in database 24). This obviates the need for individuals to re-transmit all their contact information each time their availability changes. Rather, the P&A management server 12 may determine the individual's availability based merely on the individual's profile and information regarding the individual's situation.
For individuals that have a presence and availability on the Internet or other types of IP networks, their domain name address is often an extension of a domain name server for an organization (e.g., an employer's corporate intranet). Consequently, communications with the individual may typically be established by resolving the domain name server for the organization. However, for certain services, individuals with addresses at those domain name servers are at the mercy of the system administrator to modify their address entries in order to use the new services. For example, an individual desiring to use a new instant messaging service through a corporate intranet would require the system administrator to add the appropriate address entry to the corporate intranet. Often system administrators are not inclined to do this.
According to an embodiment of the present invention, illustrated in Figure 11, this potential dilemma is addressed by providing a fallback resolution mechanism. For example, a subscriber at client terminal 22 may first attempt to communicate with an individual at client terminal 140 via one or more intermediate relay hosts 142. One of the hosts 142 may be, for example, an instant messaging host or a presence and availability host.
If one relay host 142a does not know the address for the next intermediate relay host 142b, the first relay host 142a may attempt to communicate with the second relay host 142b by, for example, resolving a record (such as an MX record for e-mail) for the second relay host 142b at a primary domain name server 144. If that fails, the first relay host 142a could attempt to resolve the record at a secondary domain name server 146. The address for the record at the primary domain name server 144 may be a hierarchical extension of the address of the secondary domain name server 146, as described further herein. As used herein, the term "domain name server" includes both domain name servers for UNIX networks as well as Windows networks, commonly referred to as "WINS" (Windows Internet Naming Service).
The secondary domain name server 146 may include a resolver 148 and an IP address database 150. The IP address database may include the IP address for the intermediate relay host 142b that the primary domain server 144 did not include. When directed to the secondary domain name server 146 by the primary domain name server 144, the resolver 148 may respond with the address of the second intermediate relay host after interrogating the database 150. The secondary domain name server 146 may supply the address directly to the first relay host 142a or, according to another embodiment, may supply it to the primary domain name server 144, which in turn may supply the address to the relay host 142a.
For example, if the hostname of the client terminal 140 isjoe@abcd.com, and Joe wanted to use a new instant messaging service that required the system administrator for the abcd.com domain name server 144 to add a DNS entry of im.abcd.com to point to the appropriate host 142b, but the system administrator refused to so modify the domain name server 144, the first domain name server could direct the relay host 142a to the secondaiy domain name server 146, efg.com, to resolve im.abcd.com.resolver.efg.com. The secondary domain name server 146 may be configured appropriately through a web-based interface and, when queried, would direct the relay host 142a to the appropriate server (to im.abcd.com in this example). According to one embodiment, a query, by email for example, may be sent to joe@abcd.com to determine whether the entry may be legitimately made.
The process just described is not limited to situations where a host does not know the address of another host. The process may also be utilized to allow a client terminal (such as terminals 22 or 140) resolve the address of a host 142 and vice versa.
The primary domain name server 144 may be programmed to supply the address for the secondary domain name server 146 to the intermediate host 142 or client terminal. According to other embodiment, the client terminal or intermediate host may be programmed with the address of the secondary domain name server 146 for when the primary domain name server 144 is not capable of resolving the request.
Although the present invention has been described herein with respect to certain embodiments, those of ordinary skill in the art will recognize that many modifications and variations of the present invention may be implemented. For example, with respect to Figure 12, additional hierarchical domain name servers may be utilized. The foregoing description and the following claims are intended to cover all such modifications and variations.

Claims

CLAIMSWhat is claimed is:
1. A method for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information, comprising: detecting whether the individual is present on at least one communication network; determining availability of the individual for each access level of a profile of the individual; publishing via a network the availability of the individual to the subscriber based on an access level of the subscriber and the presence information; and filtering the availability of the individual when it is detected that the individual is no longer present on the communication network.
2. The method of claim 1, wherein detecting whether the individual is present is performed after determining availability.
3. The method of claim 1 , wherein detecting whether the individual is present is performed prior to determining availability.
4. The method of claim 1, wherein: publishing includes publishing an address for the individual for the communication network; and filtering includes ceasing to publish the address when it is detected that the individual is no longer present on the communication network.
5. The method of claim 4, wherein detecting includes detecting whether the individual is present on a communication network consisting of a public switched telephone network, a computer network, and a wireless communication network.
6. The method of claim 5, further comprising retrieving the profile of the individual prior to publishing the availability.
7. The method of claim 6, further comprising: retrieving a second profile for the individual based on an input regarding a change in situation of the individual; determining updated availability of the individual for each access level of the second profile; and publishing the updated availability of the individual to the subscriber based on the access level of the subscriber and the presence information.
8. A method for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information, comprising: detecting whether the individual is present on a plurality of communication networks; determining availability of the individual for each access level of a profile of the individual; publishing via a network the availability of the individual to the subscriber based on an access level of the subscriber and the presence information; and filtering the availability of the individual when it is detected that the individual is no longer present on at least one of the plurality of communication networks.
9. The method of claim 8, wherein detecting whether the individual is present is performed after determining availability.
10. The method of claim 8, wherein detecting whether the individual is present is performed prior to determining availability.
11. The method of claim 8, wherein: publishing includes publishing an address for each of the plurality of communications networks; and filtering includes ceasing to publish the address for a first communication network when it is detected that the individual is no longer present on the first communication network.
12. The method of claim 11 , wherein detecting includes detecting whether the individual is present on a communication network consisting of a public switched telephone network, a computer network, and a wireless communication network.
13. The method of claim 12, further comprising retrieving the profile of the individual prior to determining availability of the individual.
14. The method of claim 13 , further comprising: retrieving a second profile for the individual based on an input regarding a change in situation of the individual; determining updated availability of the individual for each access level of the second profile; and publishing the updated availability of the individual to the subscriber based on the access level of the subscriber and the presence information.
15. A computer readable medium having stored thereon instructions which, when executed by a processor, cause the processor to: detect whether an individual is present on at least one communication network; publish, via a network, to a subscriber of the individual's network availability information whether the individual is available on the communication network; and filtering the individual's network availability information when it is detected that the individual is no longer present on the communication network.
16. The computer readable medium of claim 15, having further stored instructions which, when executed by the processor, cause the processor to: detect whether the individual is present on a plurality of communication networks; publish, via the network, to the subscriber of the individual's network availability information whether the individual is on the plurality of communication networks; and filtering the individual's network availability information when it is detected that the individual is no longer present on at least one of the communication networks.
17. The computer readable medium of claim 16, having further stored thereon instructions which, when executed by the processor, cause the processor to: publish an address for each of the plurality of communications networks; and cease to publish the address for a first communication network when it is detected that the individual is no longer present on the first communication network.
18. The computer readable medium of claim 17, wherein at least one of the communication network is selected from the group consisting of a public switched telephone network, a computer network, and a wireless communication network.
19. The computer readable medium of claim 18, having further stored thereon instructions which, when executed by the processor, cause the processor to publish to the subscriber whether the individual is available on each of the plurality of communication networks based on whether the individual is present on each of the plurality of communication networks and based on a profile of the individual.
20. The computer readable medium of claim 19, having further stored thereon instructions which, when executed by the processor, cause the processor to publish the individual's network availability information to the subscriber based on an access level of the subscriber in the profile of the individual.
21. The computer readable medium of claim 20, having further stored thereon instructions which, when executed by the processor, cause the processor to retrieve a second profile of the individual when an input regarding a change in situation of the individual is received.
22. A presence and availability management server for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information, comprising: a presence detection engine for detecting whether the individual is present on at least one communication network; an availability management engine in communication with the presence detection engine for publishing to the subscriber, via a network, a communication network availability of the individual; and an adaptive feedback module in communication with the presence detection engine and the availability management engine.
23. The presence and availability management server of claim 22, wherein the adaptive feedback module is for filtering the communication network availability when it is determined that the individual is no longer on the communication network.
24. The presence and availability management server of claim 23, wherein: the presence detection engine is for detecting whether the individual is present on a plurality of communication networks; the availability management engine is for publishing an address for each communication network for which the individual is available; and the adaptive feedback module is for ceasing to publish the address of the individual for a first communication network when it is determined that the individual is no longer present on the first network.
25. The presence and availability management server of claim 24, wherein at least one of the plurality of communication networks is selected from a group consisting of a public switched telephone network, a computer network, and a wireless communication network.
26. The presence and availability management server of claim 24, wherein the presence detection engine is in communication with an SS7 network of a public switched telephone network.
27. The presence and availability management server of claim 24, wherein the presence detection engine is in communication with a home location register of a wireless telephone network.
28. The presence and availability management server of claim 24, wherein the presence detection engine is in communication with a short messaging server center.
29. The presence and availability management server of claim 24, wherein the presence detection engine is in communication with a gateway GPRS support node (GGSN).
30. The presence and availability management server of claim 24, wherein the presence detection engine is in communication with a server of a computer network.
31. The presence and availability management server of claim 24, wherein the availability management engine is for publishing to the subscriber whether the individual is available on each of the plurality of communication networks based on whether the individual is present on each of the plurality of communication networks and based on a profile of the individual.
32. The presence and availability management server of claim 31 , wherein the server includes a database and wherein the profile of the individual is stored in the database.
33. The presence and availability management server of claim 32, wherein the availability management engine is for publishing to the subscriber whether the individual is available on the communication network based on an access level of the subscriber in the profile of the individual.
34. The presence and availability management server of claim 33, wherein a plurality of profiles is stored in the database, each profile corresponding to a different situation for the individual.
35. A presence and availability management server for communicating communication network availability information regarding an individual to at least one subscriber of the individual's availability information, comprising: first programmable means for detecting whether the individual is present on a plurality of communication networks; second programmable means for publishing to the subscriber, via a network, an address of the individual for each communication network for which the individual is available; and third programmable means for ceasing to publish the address of the individual for a first of the communication networks when it is determined that the individual is no longer present on the first communication network.
36. The presence and availability management server of claim 35, wherein the second programmable means is for publishing to the subscriber whether the individual is available on each of the communication networks based on whether the individual is present on each of the communication networks and based on a profile of the individual.
37. The presence and availability management server of claim 36, wherein the second programmable means is for retrieving the profile of the individual before the first programmable means detects whether the individual is present on the at least one communication network.
38. The presence and availability management server of claim 36, wherein the second programmable means is for retrieving the profile of the individual after the first programmable means detects whether the individual is present on the at least one communication network.
39. The presence and availability management server of claim 36, wherein the server includes a database and wherein the profile of the individual is stored in the database.
40. The presence and availability management server of claim 39, wherein a plurality of profiles is stored in the database, each profile corresponding to a different situation for the individual.
PCT/US2002/003478 2001-02-05 2002-02-05 A system and method for filtering unavailable devices in a presence and availability management system WO2002063832A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP02709372A EP1364491A1 (en) 2001-02-05 2002-02-05 A system and method for filtering unavailable devices in a presence and availability management system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US26655901P 2001-02-05 2001-02-05
US60/266,559 2001-02-05

Publications (1)

Publication Number Publication Date
WO2002063832A1 true WO2002063832A1 (en) 2002-08-15

Family

ID=23015076

Family Applications (4)

Application Number Title Priority Date Filing Date
PCT/US2002/003478 WO2002063832A1 (en) 2001-02-05 2002-02-05 A system and method for filtering unavailable devices in a presence and availability management system
PCT/US2002/003480 WO2002063489A1 (en) 2001-02-05 2002-02-05 A method of sending a communication from a first terminal to a second terminal via a host
PCT/US2002/003481 WO2002063898A1 (en) 2001-02-05 2002-02-05 Presence and availability management system
PCT/US2002/003479 WO2002063486A1 (en) 2001-02-05 2002-02-05 A method and device for displaying contact information in a presence and availability management system

Family Applications After (3)

Application Number Title Priority Date Filing Date
PCT/US2002/003480 WO2002063489A1 (en) 2001-02-05 2002-02-05 A method of sending a communication from a first terminal to a second terminal via a host
PCT/US2002/003481 WO2002063898A1 (en) 2001-02-05 2002-02-05 Presence and availability management system
PCT/US2002/003479 WO2002063486A1 (en) 2001-02-05 2002-02-05 A method and device for displaying contact information in a presence and availability management system

Country Status (3)

Country Link
US (5) US20020116461A1 (en)
EP (3) EP1368740A1 (en)
WO (4) WO2002063832A1 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101385314B (en) * 2006-02-13 2013-01-23 诺基亚公司 Method, device and system for representing network availability status information in presence information

Families Citing this family (305)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7010110B2 (en) * 1999-03-31 2006-03-07 Walker Digital, Llc Method and apparatus for monitoring telephone status
US9736209B2 (en) 2000-03-17 2017-08-15 Facebook, Inc. State change alerts mechanism
US7624172B1 (en) 2000-03-17 2009-11-24 Aol Llc State change alerts mechanism
US8132110B1 (en) * 2000-05-04 2012-03-06 Aol Inc. Intelligently enabled menu choices based on online presence state in address book
US7979802B1 (en) 2000-05-04 2011-07-12 Aol Inc. Providing supplemental contact information corresponding to a referenced individual
US9100221B2 (en) 2000-05-04 2015-08-04 Facebook, Inc. Systems for messaging senders and recipients of an electronic message
US8001190B2 (en) 2001-06-25 2011-08-16 Aol Inc. Email integrated instant messaging
US20020116461A1 (en) * 2001-02-05 2002-08-22 Athanassios Diacakis Presence and availability management system
US20030144862A1 (en) * 2001-04-24 2003-07-31 Peggy Smith Automated employment fulfillment system
ATE383026T1 (en) * 2001-05-11 2008-01-15 Nokia Corp MOBILE INSTANT MESSAGING AND PRESENCE SERVICE
US8868659B2 (en) * 2001-05-15 2014-10-21 Avaya Inc. Method and apparatus for automatic notification and response
US6697474B1 (en) * 2001-05-16 2004-02-24 Worldcom, Inc. Systems and methods for receiving telephone calls via instant messaging
US20020178227A1 (en) * 2001-05-25 2002-11-28 International Business Machines Corporation Routing instant messages using configurable, pluggable delivery managers
US7096232B2 (en) * 2001-06-06 2006-08-22 International Business Machines Corporation Calendar-enhanced directory searches including dynamic contact information
US7269627B2 (en) * 2001-07-27 2007-09-11 Intel Corporation Routing messages using presence information
US7035865B2 (en) * 2001-08-28 2006-04-25 International Business Machines Corporation Calendar-enhanced awareness for instant messaging systems and electronic status boards
US7349700B1 (en) 2001-08-30 2008-03-25 Aol Llc Communication system and method
US6920328B2 (en) * 2001-08-30 2005-07-19 Hewlett-Packard Development Company, L.P. Family calendar notification and tracking
US8644475B1 (en) 2001-10-16 2014-02-04 Rockstar Consortium Us Lp Telephony usage derived presence information
US7299286B2 (en) * 2001-12-27 2007-11-20 Nortel Networks Limited Personal user agent
EP2211520A3 (en) 2002-02-14 2010-11-10 Avaya Inc. Presence and availability tracking
US7206388B2 (en) * 2002-03-18 2007-04-17 Openwave Systems Inc. System and method for providing voice-activated presence information
US7227937B1 (en) * 2002-03-19 2007-06-05 Nortel Networks Limited Monitoring natural interaction for presence detection
US6658095B1 (en) 2002-03-19 2003-12-02 Nortel Networks Limited Customized presence information delivery
US7035923B1 (en) * 2002-04-10 2006-04-25 Nortel Networks Limited Presence information specifying communication preferences
US7139797B1 (en) * 2002-04-10 2006-11-21 Nortel Networks Limited Presence information based on media activity
US7349000B2 (en) * 2002-04-30 2008-03-25 Tandberg Telecom As Method and system for display of video device status information
FI114773B (en) * 2002-06-20 2004-12-15 Nokia Corp A method and apparatus for transmitting activity-based presence information
GB0219155D0 (en) * 2002-08-16 2002-09-25 Sleepydog Ltd Improvements relating to telecommunications
US7496631B2 (en) * 2002-08-27 2009-02-24 Aol Llc Delivery of an electronic communication using a lifespan
US7363345B2 (en) * 2002-08-27 2008-04-22 Aol Llc, A Delaware Limited Liability Company Electronic notification delivery mechanism selection based on recipient presence information and notification content
DE10241098A1 (en) * 2002-09-02 2004-03-25 Siemens Ag Method for displaying a list containing presence data
US7945846B2 (en) * 2002-09-06 2011-05-17 Oracle International Corporation Application-specific personalization for data display
US7941542B2 (en) 2002-09-06 2011-05-10 Oracle International Corporation Methods and apparatus for maintaining application execution over an intermittent network connection
US8165993B2 (en) 2002-09-06 2012-04-24 Oracle International Corporation Business intelligence system with interface that provides for immediate user action
US7899879B2 (en) 2002-09-06 2011-03-01 Oracle International Corporation Method and apparatus for a report cache in a near real-time business intelligence system
US8255454B2 (en) 2002-09-06 2012-08-28 Oracle International Corporation Method and apparatus for a multiplexed active data window in a near real-time business intelligence system
US7412481B2 (en) 2002-09-16 2008-08-12 Oracle International Corporation Method and apparatus for distributed rule evaluation in a near real-time business intelligence system
US7912899B2 (en) * 2002-09-06 2011-03-22 Oracle International Corporation Method for selectively sending a notification to an instant messaging device
US7401158B2 (en) 2002-09-16 2008-07-15 Oracle International Corporation Apparatus and method for instant messaging collaboration
US8392609B2 (en) 2002-09-17 2013-03-05 Apple Inc. Proximity detection for media proxies
US20040059781A1 (en) * 2002-09-19 2004-03-25 Nortel Networks Limited Dynamic presence indicators
US7376704B2 (en) 2002-09-24 2008-05-20 At&T Delaware Intellectual Property, Inc. Methods, systems, and products for converting between legacy systems
US7298836B2 (en) * 2002-09-24 2007-11-20 At&T Bls Intellectual Property, Inc. Network-based healthcare information systems
US7555108B2 (en) * 2002-10-01 2009-06-30 Nortel Networks Limited Presence information for telephony users
FR2845500B1 (en) * 2002-10-08 2005-07-08 France Telecom DEVICE FOR MANAGING USER PRESENCE INFORMATION FROM A PLURALITY OF PRESENCE MANAGEMENT SYSTEMS
US7065197B1 (en) 2002-10-23 2006-06-20 Cisco Technology, Inc. Status messaging using associated phone tags
US8965964B1 (en) 2002-11-18 2015-02-24 Facebook, Inc. Managing forwarded electronic messages
US7640306B2 (en) 2002-11-18 2009-12-29 Aol Llc Reconfiguring an electronic message to effect an enhanced notification
US7428580B2 (en) 2003-11-26 2008-09-23 Aol Llc Electronic message forwarding
US8005919B2 (en) 2002-11-18 2011-08-23 Aol Inc. Host-based intelligent results related to a character stream
US7899862B2 (en) 2002-11-18 2011-03-01 Aol Inc. Dynamic identification of other users to an online user
CA2506585A1 (en) 2002-11-18 2004-06-03 Valerie Kucharewski People lists
US8122137B2 (en) 2002-11-18 2012-02-21 Aol Inc. Dynamic location of a subordinate user
US7590696B1 (en) 2002-11-18 2009-09-15 Aol Llc Enhanced buddy list using mobile device identifiers
US8701014B1 (en) 2002-11-18 2014-04-15 Facebook, Inc. Account linking
US7023980B2 (en) 2002-12-04 2006-04-04 Avaya Technology Corp. Outbound dialing decision criteria based
DE10257454B4 (en) * 2002-12-09 2005-02-10 Siemens Ag Method for monitoring an application in a packet-switched network
US8335860B2 (en) * 2002-12-19 2012-12-18 Nokia Corporation Filtering application services
US20040122901A1 (en) * 2002-12-20 2004-06-24 Nortel Networks Limited Providing computer presence information to an integrated presence system
US7257218B2 (en) * 2002-12-30 2007-08-14 Nortel Networks Limited Presence enabled queue management
US7620170B2 (en) * 2002-12-31 2009-11-17 At&T Intellectual Property I, L.P. Computer telephony integration (CTI) complete customer contact center
US7356139B2 (en) 2002-12-31 2008-04-08 At&T Delaware Intellectual Property, Inc. Computer telephony integration (CTI) complete hospitality contact center
US7573999B2 (en) 2002-12-31 2009-08-11 At&T Intellectual Property I, L.P. Computer telephony integration (CTI) complete healthcare contact center
US7711810B2 (en) * 2003-01-03 2010-05-04 Nortel Networks Limited Distributed services based on presence technology
US7474741B2 (en) 2003-01-20 2009-01-06 Avaya Inc. Messaging advise in presence-aware networks
US7440567B2 (en) * 2003-01-27 2008-10-21 At&T Intellectual Property I, L.P. Healthcare virtual private network methods and systems
US7248688B2 (en) 2003-01-27 2007-07-24 Bellsouth Intellectual Property Corporation Virtual physician office systems and methods
US8149823B2 (en) 2003-01-27 2012-04-03 At&T Intellectual Property I, L.P. Computer telephony integration (CTI) systems and methods for enhancing school safety
US20040162844A1 (en) * 2003-02-13 2004-08-19 J. J. Keller & Associates, Inc. Driver management system and method
US7769811B2 (en) 2003-03-03 2010-08-03 Aol Llc Instant messaging sound control
US7191329B2 (en) 2003-03-05 2007-03-13 Sun Microsystems, Inc. Automated resource management using perceptron prediction
US7152157B2 (en) 2003-03-05 2006-12-19 Sun Microsystems, Inc. System and method for dynamic resource configuration using a dependency graph
US7613776B1 (en) 2003-03-26 2009-11-03 Aol Llc Identifying and using identities deemed to be known to a user
CA2525186A1 (en) * 2003-05-08 2004-11-18 Vimplicity Ltd. Methods and systems for instant voice messaging and instant voice message retrieval
US6970547B2 (en) * 2003-05-12 2005-11-29 Onstate Communications Corporation Universal state-aware communications
US9607092B2 (en) * 2003-05-20 2017-03-28 Excalibur Ip, Llc Mapping method and system
CA2526187C (en) 2003-05-20 2014-01-21 America Online, Inc. Presence and geographic location notification
EP1652368B1 (en) * 2003-07-14 2018-04-04 Cisco Technology, Inc. System and method for active mobile collaboration
US7653693B2 (en) 2003-09-05 2010-01-26 Aol Llc Method and system for capturing instant messages
US7302477B2 (en) * 2003-07-31 2007-11-27 International Business Machines Corporation Administration tool for gathering information about systems and applications including the feature of high availability
WO2005025181A1 (en) * 2003-08-29 2005-03-17 Siemens Aktiengesellschaft Method for supporting presence based services
GB0321424D0 (en) 2003-09-12 2003-10-15 Ericsson Telefon Ab L M Bearer setup in a multimedia service
US7403786B2 (en) * 2003-09-26 2008-07-22 Siemens Communications, Inc. System and method for in-building presence system
US7428417B2 (en) * 2003-09-26 2008-09-23 Siemens Communications, Inc. System and method for presence perimeter rule downloading
US8094804B2 (en) 2003-09-26 2012-01-10 Avaya Inc. Method and apparatus for assessing the status of work waiting for service
US7333819B2 (en) 2003-09-26 2008-02-19 Siemens Communications, Inc. System and method for global positioning system enhanced presence rules
US7202814B2 (en) * 2003-09-26 2007-04-10 Siemens Communications, Inc. System and method for presence-based area monitoring
US7224966B2 (en) * 2003-09-26 2007-05-29 Siemens Communications, Inc. System and method for web-based presence perimeter rule monitoring
US7848760B2 (en) * 2003-09-26 2010-12-07 Siemens Enterprise Communications, Inc. System and method for presence alarming
US7885665B2 (en) 2003-09-26 2011-02-08 Siemens Enterprise Communications, Inc. System and method for failsafe presence monitoring
US7606577B2 (en) * 2003-09-26 2009-10-20 Siemens Communications, Inc. System and method for alternative presence reporting system
US7546127B2 (en) * 2003-09-26 2009-06-09 Siemens Communications, Inc. System and method for centrally-hosted presence reporting
US7848761B2 (en) 2003-09-26 2010-12-07 Siemens Enterprise Communications, Inc. System and method for global positioning system (GPS) based presence
US7315746B2 (en) * 2003-09-26 2008-01-01 Siemens Communications, Inc. System and method for speed-based presence state modification
US20050198321A1 (en) * 2003-09-29 2005-09-08 Blohm Jeffrey M. Method and system for workgroup presence availability
US20050071271A1 (en) * 2003-09-29 2005-03-31 Siemens Information And Communication Networks, Inc. System and method for providing information regarding an identity's true availability
US20050071506A1 (en) * 2003-09-29 2005-03-31 Siemens Information And Communication Networks, Inc. System and method for mapping device context to identity context
US20050071361A1 (en) * 2003-09-29 2005-03-31 Siemens Information And Communication Networks, Inc. System and method for associating a device with a user
US20050071429A1 (en) * 2003-09-29 2005-03-31 Siemens Information And Communication Networks, Inc. System and method for mapping identity context to device context
US7813488B2 (en) * 2003-09-29 2010-10-12 Siemens Enterprise Communications, Inc. System and method for providing information regarding an identity's media availability
US20050108387A1 (en) * 2003-10-31 2005-05-19 Bingjun Li System and apparatus for a network management system using presence and instant message techniques
US6968185B2 (en) * 2003-11-05 2005-11-22 Interdigital Technology Corporation Mobile wireless presence and situation management system and method
US9118574B1 (en) 2003-11-26 2015-08-25 RPX Clearinghouse, LLC Presence reporting using wireless messaging
US8612522B1 (en) 2003-11-26 2013-12-17 Apple Inc. System and method for allowing an orginating user to use contact information in a prioritized list to contact a destination user
US7729688B2 (en) 2003-12-08 2010-06-01 Ipventure, Inc. Systems and processes to manage multiple modes of communication
US8443092B2 (en) * 2003-12-23 2013-05-14 Alcatel Lucent Presentity filtering for user preferences
US9398152B2 (en) 2004-02-25 2016-07-19 Avaya Inc. Using business rules for determining presence
US7734731B2 (en) * 2004-03-18 2010-06-08 Avaya Inc. Method and apparatus for a publish-subscribe system with third party subscription delivery
US20050209990A1 (en) * 2004-03-18 2005-09-22 Ordille Joann J Method and apparatus for a publish-subscribe system with access controls
DE102004013495B4 (en) * 2004-03-18 2006-11-23 Siemens Ag Method for controlling a multimodal communication application
US8229454B1 (en) 2004-03-22 2012-07-24 Avaya Inc. Personal location information management
JP4202309B2 (en) 2004-03-30 2008-12-24 富士通株式会社 Presence system and presence management method
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
US7953859B1 (en) 2004-03-31 2011-05-31 Avaya Inc. Data model of participation in multi-channel and multi-party contacts
US8239452B2 (en) * 2004-05-01 2012-08-07 Microsoft Corporation System and method for discovering and publishing of presence information on a network
US7607096B2 (en) * 2004-05-01 2009-10-20 Microsoft Corporation System and method for a user interface directed to discovering and publishing presence information on a network
US7698307B2 (en) 2004-05-01 2010-04-13 Microsoft Corporation System and method for synchronizing between a file system and presence of contacts on a network
US20050249152A1 (en) * 2004-05-04 2005-11-10 Krisztian Kiss Method for processing messages
US7769154B1 (en) 2004-06-09 2010-08-03 Avaya Inc. Aggregated perceived presence
US8099395B2 (en) * 2004-06-24 2012-01-17 Oracle America, Inc. System level identity object
US7797293B2 (en) * 2004-06-24 2010-09-14 Oracle America, Inc. Adaptive contact list
US7921163B1 (en) 2004-07-02 2011-04-05 Aol Inc. Routing and displaying messages for multiple concurrent instant messaging sessions involving a single online identity
US7983148B1 (en) 2004-07-12 2011-07-19 Avaya Inc. Disaster recovery via alternative terminals and partitioned networks
US8738412B2 (en) 2004-07-13 2014-05-27 Avaya Inc. Method and apparatus for supporting individualized selection rules for resource allocation
US20060036712A1 (en) * 2004-07-28 2006-02-16 Morris Robert P System and method for providing and utilizing presence information
US7593984B2 (en) * 2004-07-30 2009-09-22 Swift Creek Systems, Llc System and method for harmonizing changes in user activities, device capabilities and presence information
US7580837B2 (en) 2004-08-12 2009-08-25 At&T Intellectual Property I, L.P. System and method for targeted tuning module of a speech recognition system
US7818379B1 (en) 2004-08-31 2010-10-19 Aol Inc. Notification and disposition of multiple concurrent instant messaging sessions involving a single online identity
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
US20070198725A1 (en) * 2004-10-06 2007-08-23 Morris Robert P System and method for utilizing contact information, presence information and device activity
US20070198696A1 (en) * 2004-10-06 2007-08-23 Morris Robert P System and method for utilizing contact information, presence information and device activity
US7739246B2 (en) * 2004-10-14 2010-06-15 Microsoft Corporation System and method of merging contacts
US7669213B1 (en) 2004-10-28 2010-02-23 Aol Llc Dynamic identification of other viewers of a television program to an online viewer
US20060112177A1 (en) * 2004-11-24 2006-05-25 Microsoft Corporation Method and system for controlling access to presence information on a peer-to-peer basis
US20060168204A1 (en) * 2004-12-01 2006-07-27 Barry Appelman Mobile blocking indicators on a contact list
US9002949B2 (en) 2004-12-01 2015-04-07 Google Inc. Automatically enabling the forwarding of instant messages
US7730143B1 (en) 2004-12-01 2010-06-01 Aol Inc. Prohibiting mobile forwarding
US8060566B2 (en) 2004-12-01 2011-11-15 Aol Inc. Automatically enabling the forwarding of instant messages
US7242751B2 (en) 2004-12-06 2007-07-10 Sbc Knowledge Ventures, L.P. System and method for speech recognition-enabled automatic call routing
US20060149816A1 (en) * 2004-12-20 2006-07-06 Microsoft Corporation Method and system for providing notification when a user becomes available for communicating
US7356567B2 (en) 2004-12-30 2008-04-08 Aol Llc, A Delaware Limited Liability Company Managing instant messaging sessions on multiple devices
US7751551B2 (en) 2005-01-10 2010-07-06 At&T Intellectual Property I, L.P. System and method for speech-enabled call routing
EP1681830A1 (en) * 2005-01-14 2006-07-19 France Telecom Method and device for obtaining information relating to presence and availability of user
US20060190600A1 (en) * 2005-02-18 2006-08-24 Siemens Communications, Inc. Group based presence availability management
US20060198208A1 (en) * 2005-03-07 2006-09-07 Lantronix, Inc. Publicasting systems and methods
US7991774B2 (en) 2005-03-09 2011-08-02 Ricoh Company, Ltd. Notification processor that notifies information and position information manager
US8358762B1 (en) 2005-03-21 2013-01-22 Aol Inc. Conference calls and meetings via electronic messaging interface
US7353034B2 (en) 2005-04-04 2008-04-01 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
GB2425853A (en) * 2005-04-12 2006-11-08 Christopher Gare Presence information and location monitor
US8781081B2 (en) * 2005-04-21 2014-07-15 At&T Intellectual Property I, L.P. Presence management system
US7571228B2 (en) * 2005-04-22 2009-08-04 Microsoft Corporation Contact management in a serverless peer-to-peer system
US8036140B2 (en) 2005-04-22 2011-10-11 Microsoft Corporation Application programming interface for inviting participants in a serverless peer to peer network
US20060248184A1 (en) * 2005-04-29 2006-11-02 Alcatel System and method for managing user groups in presence systems
US20060248185A1 (en) * 2005-04-29 2006-11-02 Morris Robert P System and method for utilizing a presence service to advertise activity availability
US7809127B2 (en) 2005-05-26 2010-10-05 Avaya Inc. Method for discovering problem agent behaviors
US8825370B2 (en) * 2005-05-27 2014-09-02 Yahoo! Inc. Interactive map-based travel guide
US7657020B2 (en) 2005-06-03 2010-02-02 At&T Intellectual Property I, Lp Call routing system and method of using the same
US8005204B2 (en) 2005-06-03 2011-08-23 At&T Intellectual Property I, L.P. Call routing system and method of using the same
US7567553B2 (en) * 2005-06-10 2009-07-28 Swift Creek Systems, Llc Method, system, and data structure for providing a general request/response messaging protocol using a presence protocol
US7826965B2 (en) * 2005-06-16 2010-11-02 Yahoo! Inc. Systems and methods for determining a relevance rank for a point of interest
US8681751B2 (en) * 2005-07-11 2014-03-25 Nokia Corporation Method and apparatus for providing presence information in support of wireless communication services
US8392836B1 (en) 2005-07-11 2013-03-05 Google Inc. Presenting quick list of contacts to communication application user
US9479468B2 (en) 2005-07-11 2016-10-25 Google Inc. Presenting instant messages
US7779042B1 (en) 2005-08-08 2010-08-17 Avaya Inc. Deferred control of surrogate key generation in a distributed processing architecture
US20070042791A1 (en) * 2005-08-16 2007-02-22 Sbc Knowledge Ventures, L.P. Presence and availability management over a public communication network
US8751582B1 (en) * 2005-08-22 2014-06-10 Google Inc. Managing presence subscriptions for messaging services
US20070050507A1 (en) * 2005-08-24 2007-03-01 Nokia Corporation Context discovery for DNS names
US20070061396A1 (en) * 2005-09-09 2007-03-15 Morris Robert P Methods, systems, and computer program products for providing service data to a service provider
US20070073889A1 (en) * 2005-09-27 2007-03-29 Morris Robert P Methods, systems, and computer program products for verifying an identity of a service requester using presence information
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
WO2007047246A2 (en) * 2005-10-11 2007-04-26 Barry Appelman Enabling and exercising control over selected sounds associated with incoming communications
WO2007047535A1 (en) 2005-10-14 2007-04-26 Yahoo! Inc. Method and system for navigating a map
US20070088839A1 (en) * 2005-10-19 2007-04-19 Nortel Networks Limited Local time related presence automation and session control
US8787917B1 (en) 2005-10-24 2014-07-22 Avaya Inc. Selection of wireless network travel paths
US8942367B1 (en) * 2005-10-31 2015-01-27 At&T Intellectual Property Ii, L.P. Method and apparatus for routing a call in a communications network
US7991721B2 (en) 2005-11-07 2011-08-02 International Business Machines Corporation Differential availability determination and notification
US7941752B2 (en) * 2005-11-18 2011-05-10 Alcatel Lucent System and method for representation of user preference and policy in contact list
US8701017B2 (en) 2005-11-18 2014-04-15 Alcatel Lucent System and method for representation of presentity presence states for contacts in a contact list
US20070130323A1 (en) * 2005-12-02 2007-06-07 Landsman Richard A Implied presence detection in a communication system
US20070136197A1 (en) * 2005-12-13 2007-06-14 Morris Robert P Methods, systems, and computer program products for authorizing a service request based on account-holder-configured authorization rules
US20070150441A1 (en) * 2005-12-23 2007-06-28 Morris Robert P Methods, systems, and computer program products for associating policies with tuples using a pub/sub protocol
US7512880B2 (en) 2005-12-23 2009-03-31 Swift Creek Systems, Llc Method and system for presenting published information in a browser
US7669228B2 (en) * 2005-12-27 2010-02-23 Cisco Technology, Inc. System and method for changing network behavior based on presence information
US7673010B2 (en) * 2006-01-27 2010-03-02 Broadcom Corporation Multi user client terminals operable to support network communications
US7788188B2 (en) * 2006-01-30 2010-08-31 Hoozware, Inc. System for providing a service to venues where people aggregate
US8103519B2 (en) 2006-01-30 2012-01-24 Hoozware, Inc. System for marketing campaign specification and secure digital coupon redemption
US7856360B2 (en) 2006-01-30 2010-12-21 Hoozware, Inc. System for providing a service to venues where people aggregate
US20110093340A1 (en) * 2006-01-30 2011-04-21 Hoozware, Inc. System for providing a service to venues where people perform transactions
US9105039B2 (en) 2006-01-30 2015-08-11 Groupon, Inc. System and method for providing mobile alerts to members of a social network
US7587450B2 (en) * 2006-02-01 2009-09-08 Swift Creek Systems, Llc HTTP publish/subscribe communication protocol
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
US20070209081A1 (en) * 2006-03-01 2007-09-06 Morris Robert P Methods, systems, and computer program products for providing a client device with temporary access to a service during authentication of the client device
TW200735593A (en) * 2006-03-10 2007-09-16 Inventec Appliances Corp Communication exchange method between public switched telephone network (PSTN) and internet telephone network
JP2007255075A (en) * 2006-03-23 2007-10-04 Omron Corp Radio communication system and method, as well as portable radio communication device and method
US7945612B2 (en) * 2006-03-28 2011-05-17 Microsoft Corporation Aggregating user presence across multiple endpoints
US20070239869A1 (en) * 2006-03-28 2007-10-11 Microsoft Corporation User interface for user presence aggregated across multiple endpoints
CN101047523B (en) * 2006-03-29 2012-01-04 松下电器产业株式会社 Server and method for providing on-line person state
US9241038B2 (en) * 2006-05-23 2016-01-19 Microsoft Technology Licensing, Llc User presence aggregation at a server
US20070294397A1 (en) * 2006-06-16 2007-12-20 Microsoft Corporation Physical presence indication for a collaborative communication
JP4860365B2 (en) * 2006-06-19 2012-01-25 ソニー・エリクソン・モバイルコミュニケーションズ株式会社 Information processing device, information processing method, information processing program, and portable terminal device
US8842818B2 (en) * 2006-06-30 2014-09-23 Avaya Inc. IP telephony architecture including information storage and retrieval system to track fluency
US20080052377A1 (en) * 2006-07-11 2008-02-28 Robert Light Web-Based User-Dependent Customer Service Interaction with Co-Browsing
US8295206B2 (en) * 2006-07-20 2012-10-23 Avaya Inc. Rule-based system for determining user availability
US7680480B2 (en) * 2006-07-20 2010-03-16 Avaya Inc. Determining user availability based on a past event
US7680098B2 (en) * 2006-07-20 2010-03-16 Avaya Inc. Determining group availability on different communication media
US7616624B2 (en) * 2006-07-20 2009-11-10 Avaya Inc. Determining user availability based on the expected duration of a new event
US20080021998A1 (en) * 2006-07-20 2008-01-24 Rachel Wentink Presence-based resource locator
US8068847B1 (en) * 2006-08-09 2011-11-29 Avaya Inc. Method and apparatus for notifying a user of separation from a mobile device
US7936867B1 (en) 2006-08-15 2011-05-03 Avaya Inc. Multi-service request within a contact center
US8780925B2 (en) * 2006-08-17 2014-07-15 Fonality, Inc. Mobile use of a PBX system
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
US20080075066A1 (en) * 2006-09-11 2008-03-27 Avaya Technology Llc Presence-Based Manager of Displayable Messages
US20080069331A1 (en) * 2006-09-18 2008-03-20 Siemens Communications, Inc. Apparatus and method for intelligent call waiting
US20080082578A1 (en) 2006-09-29 2008-04-03 Andrew Hogue Displaying search results on a one or two dimensional graph
US7698648B2 (en) * 2006-10-23 2010-04-13 Microsoft Corporation Animation of icons based on presence
US10445703B1 (en) * 2006-10-30 2019-10-15 Avaya Inc. Early enough reminders
US20080147793A1 (en) * 2006-10-31 2008-06-19 Singh Munindar P Method And System For Coordinating A Synchronous Activity
US20080117921A1 (en) * 2006-11-20 2008-05-22 Morris Robert P Method And System For Presenting Command Information Associated With A Status
US20080126475A1 (en) * 2006-11-29 2008-05-29 Morris Robert P Method And System For Providing Supplemental Information In A Presence Client-Based Service Message
US9330190B2 (en) 2006-12-11 2016-05-03 Swift Creek Systems, Llc Method and system for providing data handling information for use by a publish/subscribe client
US8099084B2 (en) 2006-12-31 2012-01-17 Ektimisi Semiotics Holdings, Llc Method, system, and computer program product for creating smart services
US8150003B1 (en) 2007-01-23 2012-04-03 Avaya Inc. Caller initiated undivert from voicemail
US8693659B2 (en) * 2007-03-09 2014-04-08 Fonality, Inc. System and method for centralized presence management of local and remote users
US8098810B2 (en) 2007-03-09 2012-01-17 Fonality, Inc. Intelligent presence management in a communication routing system
US20080273678A1 (en) 2007-05-01 2008-11-06 Igor Balk Systems and methods for phone call management
US8379832B1 (en) 2007-05-03 2013-02-19 Fonality, Inc. Universal queuing for inbound communications
US20080285588A1 (en) 2007-05-16 2008-11-20 Unison Technologies Llc Systems and methods for providing unified collaboration systems with combined communication log
US20080285736A1 (en) 2007-05-16 2008-11-20 Unison Technolgies Llc Systems and methods for providing unified collaboration systems with conditional communication handling
US8711102B2 (en) * 2007-06-15 2014-04-29 Microsoft Corporation Graphical communication user interface with graphical position user input mechanism for selecting a display image
US20100185738A1 (en) * 2007-06-21 2010-07-22 Panasonic Corporation Information processing terminal, server, and presence distribution system
US10671600B1 (en) 2007-07-24 2020-06-02 Avaya Inc. Communications-enabled dynamic social network routing utilizing presence
KR101055109B1 (en) 2007-07-25 2011-08-08 엘지전자 주식회사 How to Move Sessions and How to Support Session Continuity
WO2009015412A1 (en) * 2007-07-27 2009-02-05 Eccosphere International Pty Ltd Communication between networked entities in a presence-based communication system
US20090037588A1 (en) * 2007-07-31 2009-02-05 Morris Robert P Method And System For Providing Status Information Of At Least Two Related Principals
US10097695B2 (en) 2007-08-10 2018-10-09 Fonality, Inc. System and method for providing carrier-independent VoIP communication
US8504534B1 (en) 2007-09-26 2013-08-06 Avaya Inc. Database structures and administration techniques for generalized localization of database items
US20100299615A1 (en) * 2007-09-28 2010-11-25 The Trustees Of Dartmouth College System And Method For Injecting Sensed Presence Into Social Networking Applications
CA2701423C (en) * 2007-10-02 2016-06-21 Ascendent Telecommunications, Inc. Method, apparatus and system for intelligent call routing
US20100046731A1 (en) * 2007-10-02 2010-02-25 Douglas Gisby Method, apparatus and system for use of presence and location information in intelligent call routing
US20090106677A1 (en) * 2007-10-19 2009-04-23 Giyeong Son Mechanism for publishing presence information within a presence service and user interface for configuring same
US8856182B2 (en) 2008-01-25 2014-10-07 Avaya Inc. Report database dependency tracing through business intelligence metadata
US8370148B2 (en) 2008-04-14 2013-02-05 At&T Intellectual Property I, L.P. System and method for answering a communication notification
ITMI20080825A1 (en) * 2008-05-07 2009-11-08 Paolo Borlenghi INTERPERSONAL COMMUNICATION SYSTEM
US20090307374A1 (en) * 2008-06-05 2009-12-10 Morris Robert P Method And System For Providing A Subscription To A Tuple Based On A Schema Associated With The Tuple
US9014016B2 (en) * 2008-06-20 2015-04-21 Microsoft Corporation Techniques to manage presence information based on routing rules
US8473733B2 (en) * 2008-10-14 2013-06-25 Research In Motion Limited Method for managing opaque presence indications within a presence access layer
US20100093328A1 (en) * 2008-10-15 2010-04-15 Research In Motion Limited Interworking Function with a Presence Access Layer to Provide Enhanced Presence Aspect Indications
US8103730B2 (en) * 2008-10-15 2012-01-24 Research In Motion Limited Use of persistent sessions by a presence access layer
US20100093366A1 (en) * 2008-10-15 2010-04-15 Research In Motion Limited Incorporating Non-Presence Information in the Calculation of Presence Aspects by a Presence Access Layer
US20100099387A1 (en) * 2008-10-16 2010-04-22 Research In Motion Limited Controlling and/or Limiting Publication Through the Presence Access Layer
US8751584B2 (en) * 2008-10-16 2014-06-10 Blackberry Limited System for assignment of a service identifier as a mechanism for establishing a seamless profile in a contextually aware presence access layer
US8386769B2 (en) * 2008-11-21 2013-02-26 Research In Motion Limited Apparatus, and an associated method, for providing and using opaque presence indications in a presence service
CN101448299B (en) * 2008-11-30 2011-01-19 中兴通讯股份有限公司 Terminal and method for avoiding interference
CN102257793A (en) * 2008-12-19 2011-11-23 爱立信电话股份有限公司 A method and arrangement for handling resource data
US8719386B2 (en) 2009-01-08 2014-05-06 Fonality, Inc. System and method for providing configuration synchronicity
US9235842B2 (en) 2009-03-02 2016-01-12 Groupon, Inc. Method for providing information to contacts without being given contact data
US10318922B2 (en) 2009-03-16 2019-06-11 Fonality, Inc. System and method for automatic insertion of call intelligence in an information system
US9443244B2 (en) 2009-03-16 2016-09-13 Fonality, Inc. System and method for utilizing customer data in a communication system
US9588803B2 (en) * 2009-05-11 2017-03-07 Microsoft Technology Licensing, Llc Executing native-code applications in a browser
US8793319B2 (en) * 2009-07-13 2014-07-29 Microsoft Corporation Electronic message organization via social groups
US20110022580A1 (en) * 2009-07-21 2011-01-27 Telefonaktiebolaget Lm Ericsson (Publ) Exchange of service capabilities in communication networks
EP2467820A4 (en) * 2009-08-21 2015-05-06 Samsung Electronics Co Ltd Method of managing contact item information, user device for executing the method, and storage medium thereof
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
TWI409692B (en) * 2009-10-29 2013-09-21 Mitac Int Corp Method of simultaneously displaying states of a plurality of internet communication software of a plurality of contacts in address books of and related communication device
US9516069B2 (en) 2009-11-17 2016-12-06 Avaya Inc. Packet headers as a trigger for automatic activation of special-purpose softphone applications
US9509791B2 (en) * 2010-01-07 2016-11-29 Oracle International Corporation Policy-based exposure of presence
US9467858B2 (en) 2010-02-05 2016-10-11 Oracle International Corporation On device policy enforcement to secure open platform via network and open network
CA2731745A1 (en) * 2010-02-15 2011-08-15 Research In Motion Limited Contact objects
JP5708168B2 (en) * 2010-06-16 2015-04-30 株式会社リコー Transmission terminal, transmission system, transmission method, and program for transmission terminal
US8407530B2 (en) 2010-06-24 2013-03-26 Microsoft Corporation Server reachability detection
CN102413223B (en) * 2010-09-24 2016-08-10 深圳富泰宏精密工业有限公司 Contacts entries merges and dividing method and system
US9413556B2 (en) * 2011-06-03 2016-08-09 Apple Inc. Unified account list
US20130117374A1 (en) * 2011-11-07 2013-05-09 Dms Network Llc Social Network with Blocked Network Users and Accessible Network Users
US20130145293A1 (en) * 2011-12-01 2013-06-06 Avaya Inc. Methods, apparatuses, and computer-readable media for providing availability metaphor(s) representing communications availability in an interactive map
US9374328B1 (en) * 2012-01-11 2016-06-21 Google Inc. Selective messaging using online presence information
US20130239005A1 (en) * 2012-03-06 2013-09-12 Microsoft Corporation Techniques for remote presence subscription
US9978238B2 (en) 2012-09-21 2018-05-22 Google Llc Visitor options at an entryway to a smart-home
US10332059B2 (en) 2013-03-14 2019-06-25 Google Llc Security scoring in a smart-sensored home
US9960929B2 (en) 2012-09-21 2018-05-01 Google Llc Environmental sensing with a doorbell at a smart-home
US9959727B2 (en) 2012-09-21 2018-05-01 Google Llc Handling visitor interaction at a smart-home in a do not disturb mode
US9626841B2 (en) * 2012-09-21 2017-04-18 Google Inc. Occupant notification of visitor interaction with a doorbell at a smart-home
US9652912B2 (en) 2012-09-21 2017-05-16 Google Inc. Secure handling of unsupervised package drop off at a smart-home
US9953514B2 (en) 2012-09-21 2018-04-24 Google Llc Visitor feedback to visitor interaction with a doorbell at a smart-home
US9881474B2 (en) 2012-09-21 2018-01-30 Google Llc Initially detecting a visitor at a smart-home
US9640055B2 (en) 2012-09-21 2017-05-02 Google Inc. Interacting with a detected visitor at an entryway to a smart-home
US9711036B2 (en) 2012-09-21 2017-07-18 Google Inc. Leveraging neighborhood to handle potential visitor at a smart-home
US10735216B2 (en) 2012-09-21 2020-08-04 Google Llc Handling security services visitor at a smart-home
US9600645B2 (en) 2012-09-21 2017-03-21 Google Inc. Smart invitation handling at a smart-home
US9998530B2 (en) * 2013-10-15 2018-06-12 Nicira, Inc. Distributed global load-balancing system for software-defined data centers
US20150178100A1 (en) * 2013-12-23 2015-06-25 International Business Machines Corporation Trigger based portable device morphing
US11436618B2 (en) * 2014-05-20 2022-09-06 [24]7.ai, Inc. Method and apparatus for providing customer notifications
US10555246B2 (en) * 2016-01-08 2020-02-04 Qualcomm Incorporated Sharing network feedback information using a device-to-device link
US10348892B2 (en) 2016-06-15 2019-07-09 International Business Machines Corporation Scheduling telephone calls
US10448204B2 (en) 2017-03-28 2019-10-15 Microsoft Technology Licensing, Llc Individualized presence context publishing
US11212166B2 (en) * 2017-08-29 2021-12-28 Disney Enterprises, Inc. Standardized remote access and set-up for electronic devices
CN112099857B (en) * 2020-08-25 2022-05-17 深圳市元征科技股份有限公司 Dormancy awakening method of electronic equipment and electronic equipment

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5497412A (en) * 1994-04-07 1996-03-05 Gte Telecommunication Services Incorporated Enhanced call delivery system for roaming cellular subscribers
US6081705A (en) * 1997-02-06 2000-06-27 Telefonaktiebolaget L/M Ericsson (Publ) Cellular telephone network support of international mobile station identity (IMSI)
US6154776A (en) * 1998-03-20 2000-11-28 Sun Microsystems, Inc. Quality of service allocation on a network
US6389457B2 (en) * 1998-05-29 2002-05-14 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device

Family Cites Families (104)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4313035A (en) * 1980-01-18 1982-01-26 Bell Telephone Laboratories, Incorporated Method of providing person locator service
US4740788A (en) * 1986-10-06 1988-04-26 Konneker Lloyd K Method of providing location dependent visitor dispatching service
US5251248A (en) * 1989-06-30 1993-10-05 Nippon Telegraph And Telephone Corporation Telephone network having personal numbers for position-independent
US5646839A (en) * 1990-05-29 1997-07-08 Mcic Communications Corporation Telephone-based personnel tracking system
CA2048306A1 (en) * 1990-10-02 1992-04-03 Steven P. Miller Distributed configuration profile for computing system
US5243645A (en) * 1990-11-01 1993-09-07 At&T Bell Laboratories Automatic system for forwarding of calls
US5239577A (en) * 1990-12-03 1993-08-24 Bell Communications Research, Inc. Network and method for providing cross-media connections
US5255306A (en) * 1991-01-10 1993-10-19 Bi Inc. Cellular interface unit for use with an electronic house arrest monitoring system
US5155689A (en) * 1991-01-17 1992-10-13 By-Word Technologies, Inc. Vehicle locating and communicating method and apparatus
US5208756A (en) * 1991-01-28 1993-05-04 Song Han L Vehicle locating and navigating system
US5315636A (en) * 1991-06-28 1994-05-24 Network Access Corporation Personal telecommunications system
US5329578A (en) * 1992-05-26 1994-07-12 Northern Telecom Limited Personal communication service with mobility manager
US5218367A (en) * 1992-06-01 1993-06-08 Trackmobile Vehicle tracking system
US5440620A (en) * 1992-08-28 1995-08-08 At&T Corp. Telecommunications system subscriber profile updating
JPH06188831A (en) * 1992-12-16 1994-07-08 Fujitsu Ltd Personal communication system
US5436963A (en) * 1992-12-30 1995-07-25 International Business Machines Corporation Telephone answering method and apparatus
US5428678A (en) * 1992-12-30 1995-06-27 International Business Machines Corporation Telephone calling method and apparatus
DE4310099C2 (en) * 1993-03-23 1997-09-04 Mannesmann Ag Path identification device
JP3425192B2 (en) * 1993-08-25 2003-07-07 富士通株式会社 Address information automatic setting processing method and address information setting device
IL111154A0 (en) * 1993-10-21 1994-12-29 Martino Ii John A Systems and methods for electronic messaging
US5436965A (en) * 1993-11-16 1995-07-25 Automated Systems And Programming, Inc. Method and system for optimization of telephone contact campaigns
JP2813536B2 (en) * 1993-11-19 1998-10-22 富士通株式会社 Camp-on communication management system
US5493692A (en) * 1993-12-03 1996-02-20 Xerox Corporation Selective delivery of electronic messages in a multiple computer system based on context and environment of a user
US5594782A (en) * 1994-02-24 1997-01-14 Gte Mobile Communications Service Corporation Multiple mode personal wireless communications system
GB2289149B (en) * 1994-05-02 1998-11-18 Ubique Ltd A co-presence data retrieval system
US6651050B2 (en) * 1994-05-02 2003-11-18 International Business Machines Corporation Co-presence data retrieval system which indicates observers of data
US6243714B1 (en) * 1997-04-11 2001-06-05 Ubique Ltd. Co-presence data retrieval system
US5546442A (en) * 1994-06-23 1996-08-13 At&T Corp. Method and apparatus for use in completing telephone calls
US5742905A (en) * 1994-09-19 1998-04-21 Bell Communications Research, Inc. Personal communications internetworking
US5754636A (en) * 1994-11-01 1998-05-19 Answersoft, Inc. Computer telephone system
US5592533A (en) * 1994-12-23 1997-01-07 Bell Atlantic Mobile Systems, Inc. Personal communication service registration system and method
US5550907A (en) * 1994-12-23 1996-08-27 Lucent Technologies Inc. Personal communication using intelligent terminals
US5577100A (en) * 1995-01-30 1996-11-19 Telemac Cellular Corporation Mobile phone with internal accounting
US5777989A (en) * 1995-12-19 1998-07-07 International Business Machines Corporation TCP/IP host name resolution for machines on several domains
US5742674A (en) * 1995-12-22 1998-04-21 At&T Corp. Automatic call-back system and method using data indicating best time to call
US5826039A (en) * 1995-12-29 1998-10-20 Lucent Technologies Inc. Universal connection point for resources and communication unrelated to a physical endpoint
US5767788A (en) * 1996-03-19 1998-06-16 Ness; James C. Computer aided dispatch and locator cellular system
US5802161A (en) * 1996-03-22 1998-09-01 Austin Logistics Inc. Method and system for optimized scheduling
US5774802A (en) * 1996-04-10 1998-06-30 Motorola Inc. Apparatus and method for billing in a wireless communication system
DE19617140C2 (en) * 1996-04-29 1999-07-15 Siemens Ag Radio station for sending and receiving digital information in a mobile communication system
US5872926A (en) * 1996-05-31 1999-02-16 Adaptive Micro Systems, Inc. Integrated message system
US5903845A (en) * 1996-06-04 1999-05-11 At&T Wireless Services Inc. Personal information manager for updating a telecommunication subscriber profile
US5901214A (en) * 1996-06-10 1999-05-04 Murex Securities, Ltd. One number intelligent call processing system
US5862331A (en) * 1996-06-21 1999-01-19 Sun Microsystems, Inc. Name service system and method for automatic updating on interconnected hosts
CA2180684C (en) * 1996-07-08 2001-08-21 Paul Erb Automatic call forwarding
IL119364A (en) * 1996-10-06 2000-11-21 Icq Inc Communications system
US5905789A (en) * 1996-10-07 1999-05-18 Northern Telecom Limited Call-forwarding system using adaptive model of user behavior
US6032175A (en) * 1996-10-17 2000-02-29 International Business Machines Corporation Enhanced directory services in compound wide/local area networks
US5930702A (en) * 1996-10-22 1999-07-27 At&T Corp. Personal mobility communication system
US5896448A (en) * 1996-12-17 1999-04-20 Bellsouth Corporation Method and apparatus for routing calls based on call success history
US5987113A (en) * 1996-12-23 1999-11-16 Northern Telecom Limited Long distance phone tag service
US6456852B2 (en) * 1997-01-08 2002-09-24 Trafficmaster Usa, Inc. Internet distributed real-time wireless location database
US5928325A (en) * 1997-02-24 1999-07-27 Motorola, Inc. Method of dynamically establishing communication of incoming messages to one or more user devices presently available to an intended recipient
US6125176A (en) * 1997-06-17 2000-09-26 At&T Corporation Method and system for routing calls based on conditions of electronic devices
US6023762A (en) * 1997-07-09 2000-02-08 Northern Telecom Limited Multi-view personalized communications agent
US6243451B1 (en) * 1997-10-09 2001-06-05 Alcatel Usa Sourcing, L.P. Service management access point
US6104799A (en) * 1997-10-24 2000-08-15 At&T Corp. Customer defined call setup
US5960442A (en) * 1997-11-12 1999-09-28 Genesys Telecommunications Laboratories, Inc. Real-time interactive directory
US6016512A (en) * 1997-11-20 2000-01-18 Telcordia Technologies, Inc. Enhanced domain name service using a most frequently used domain names table and a validity code table
US6138003A (en) * 1997-11-26 2000-10-24 Ericsson Inc. System and method for authorization of location services
US6018737A (en) * 1997-12-18 2000-01-25 Alcatel Usa Sourcing, L.P. Universal personal telecommunications service for an advanced intelligent network
EP0944004B1 (en) * 1998-03-18 2008-02-06 Sony Deutschland GmbH IRC name translation protocol
US6195698B1 (en) * 1998-04-13 2001-02-27 Compaq Computer Corporation Method for selectively restricting access to computer systems
US6104931A (en) * 1998-04-20 2000-08-15 Ericsson Inc. System and method for defining location services
US6134447A (en) * 1998-05-29 2000-10-17 Ericsson Inc. System and method for monitoring and barring location applications
SE521263C2 (en) * 1998-06-22 2003-10-14 Ericsson Telefon Ab L M Device and method for establishing connection between a first and second subscriber by means of a public register
US6157953A (en) * 1998-07-28 2000-12-05 Sun Microsystems, Inc. Authentication and access control in a management console program for managing services in a computer network
US6360102B1 (en) * 1998-09-10 2002-03-19 Ericsson Inc. System and method for defining a subscriber location privacy profile
US6195696B1 (en) * 1998-10-01 2001-02-27 International Business Machines Corporation Systems, methods and computer program products for assigning, generating and delivering content to intranet users
US6577865B2 (en) * 1998-11-05 2003-06-10 Ulysses Holdings, Llc System for intercept of wireless communications
US6332158B1 (en) * 1998-12-03 2001-12-18 Chris Risley Domain name system lookup allowing intelligent correction of searches and presentation of auxiliary information
US6871224B1 (en) * 1999-01-04 2005-03-22 Cisco Technology, Inc. Facility to transmit network management data to an umbrella management system
US6212392B1 (en) * 1999-02-26 2001-04-03 Signal Soft Corp. Method for determining if the location of a wireless communication device is within a specified area
US6463288B1 (en) * 1999-03-18 2002-10-08 Ericsson Inc. System and method for monitoring positioning requests for mobile subscribers
US6671259B1 (en) * 1999-03-30 2003-12-30 Fujitsu Limited Method and system for wide area network load balancing
US6336117B1 (en) * 1999-04-30 2002-01-01 International Business Machines Corporation Content-indexing search system and method providing search results consistent with content filtering and blocking policies implemented in a blocking engine
US6564261B1 (en) * 1999-05-10 2003-05-13 Telefonaktiebolaget Lm Ericsson (Publ) Distributed system to intelligently establish sessions between anonymous users over various networks
US6301609B1 (en) * 1999-07-07 2001-10-09 Lucent Technologies Inc. Assignable associate priorities for user-definable instant messaging buddy groups
US6282427B1 (en) * 1999-07-14 2001-08-28 Telefonaktiebolaget L M Ericsson (Publ) Selection of location measurement units for determining the position of a mobile communication station
US6640241B1 (en) * 1999-07-19 2003-10-28 Groove Networks, Inc. Method and apparatus for activity-based collaboration by a computer system equipped with a communications manager
US6807423B1 (en) * 1999-12-14 2004-10-19 Nortel Networks Limited Communication and presence spanning multiple access networks
US7337210B2 (en) * 2000-01-13 2008-02-26 International Business Machines Corporation Method and apparatus for determining availability of a user of an instant messaging application
US6697840B1 (en) * 2000-02-29 2004-02-24 Lucent Technologies Inc. Presence awareness in collaborative systems
US6839735B2 (en) * 2000-02-29 2005-01-04 Microsoft Corporation Methods and systems for controlling access to presence information according to a variety of different access permission types
US7043563B2 (en) * 2000-04-17 2006-05-09 Circadence Corporation Method and system for redirection to arbitrary front-ends in a communication system
US20020021307A1 (en) * 2000-04-24 2002-02-21 Steve Glenn Method and apparatus for utilizing online presence information
WO2001084812A2 (en) * 2000-05-03 2001-11-08 Daniel Schoeffler Method of enabling transmission and reception of communication when current destination for recipient is unknown to sender
US7562153B2 (en) * 2000-05-12 2009-07-14 AT&T Intellectual Property II, L. P. Method and apparatus for content distribution network brokering and peering
DE60125637T2 (en) * 2000-05-17 2007-10-04 International Business Machines Corp. System and method to detect the residence or availability of a telephone user and to publish the telephone number on the Internet
KR20030024678A (en) * 2000-05-22 2003-03-26 뉴.넷,아이엔씨. Systems and methods of accessing network resources
US20020065828A1 (en) * 2000-07-14 2002-05-30 Goodspeed John D. Network communication using telephone number URI/URL identification handle
US20020085701A1 (en) * 2000-10-30 2002-07-04 Parsons Eric W. Method and system for providing unified communication management based on presence information
US7870196B2 (en) * 2000-11-08 2011-01-11 Nokia Corporation System and methods for using an application layer control protocol transporting spatial location information pertaining to devices connected to wired and wireless internet protocol networks
WO2002043351A2 (en) * 2000-11-20 2002-05-30 At & T Wireless Services, Inc. Systems for providing wireless communication presence information
US6484130B2 (en) * 2000-11-29 2002-11-19 International Business Machines Corporation Office accessibility information provider
WO2002045344A2 (en) * 2000-11-30 2002-06-06 Message Machines, Inc. Systems and methods for routing messages to communications devices
KR20020044823A (en) * 2000-12-06 2002-06-19 이계철 Apparatus and Method for Providing communication service based on personal identifier in Internet network
US7957514B2 (en) * 2000-12-18 2011-06-07 Paltalk Holdings, Inc. System, method and computer program product for conveying presence information via voice mail
US6441752B1 (en) * 2000-12-30 2002-08-27 Mundi Fomukong Method and apparatus for locating mobile units tracking another or within a prescribed geographic boundary
US20020116461A1 (en) * 2001-02-05 2002-08-22 Athanassios Diacakis Presence and availability management system
US20030023690A1 (en) * 2001-07-26 2003-01-30 Sunit Lohtia Method and apparatus for providing selective delivery of notifications to users of multiple devices over a network
US20030048195A1 (en) * 2001-08-31 2003-03-13 Dirk Trossen Apparatus and method to sense and subscribe to presence information
US20030135624A1 (en) * 2001-12-27 2003-07-17 Mckinnon Steve J. Dynamic presence management
US7751826B2 (en) * 2002-10-24 2010-07-06 Motorola, Inc. System and method for E911 location privacy protection

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5497412A (en) * 1994-04-07 1996-03-05 Gte Telecommunication Services Incorporated Enhanced call delivery system for roaming cellular subscribers
US6081705A (en) * 1997-02-06 2000-06-27 Telefonaktiebolaget L/M Ericsson (Publ) Cellular telephone network support of international mobile station identity (IMSI)
US6154776A (en) * 1998-03-20 2000-11-28 Sun Microsystems, Inc. Quality of service allocation on a network
US6389457B2 (en) * 1998-05-29 2002-05-14 Research In Motion Limited System and method for pushing information from a host system to a mobile data communication device

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101385314B (en) * 2006-02-13 2013-01-23 诺基亚公司 Method, device and system for representing network availability status information in presence information

Also Published As

Publication number Publication date
EP1366631A4 (en) 2005-11-02
EP1364491A1 (en) 2003-11-26
WO2002063898A8 (en) 2002-11-14
US20020120687A1 (en) 2002-08-29
US20020116461A1 (en) 2002-08-22
US7246371B2 (en) 2007-07-17
US20020116336A1 (en) 2002-08-22
WO2002063486A1 (en) 2002-08-15
WO2002063489A1 (en) 2002-08-15
EP1366631A1 (en) 2003-12-03
EP1368740A1 (en) 2003-12-10
US20060259956A1 (en) 2006-11-16
US20020120774A1 (en) 2002-08-29
WO2002063898A1 (en) 2002-08-15

Similar Documents

Publication Publication Date Title
US7246371B2 (en) System and method for filtering unavailable devices in a presence and availability management system
US7206388B2 (en) System and method for providing voice-activated presence information
US6714519B2 (en) Communications availability
US9621502B2 (en) Enhanced buddy list interface
US7010292B2 (en) Method for providing communication information of a communication unit, and associated devices
KR100880811B1 (en) Value-added electronic messaging services and transparent implementation thereof using intermediate server
US7606864B2 (en) Setting and display of communication receipt preferences by users of multiple communication devices
US6807423B1 (en) Communication and presence spanning multiple access networks
JP4431000B2 (en) Method and apparatus for delivering an e-mail message with instructions indicating the presence of the sender
EP1348294B1 (en) Presence and session handling information
EP1549013B1 (en) Presentity filtering for user preferences
CN1794727B (en) Presence system and method for event-driven presence subscription
US20040098491A1 (en) Accessing presence information
EP1713234A1 (en) System and method for routing communication sessions based on priority, presence and preference information
EP1835665A1 (en) Method for providing presence information and apparatus thereof
JP2009177831A (en) Presence tracking, and name space interconnection techniques
US7730156B1 (en) Method and system for reporting changes in PIM data
CA2394317C (en) Presence management system using context information
WO2002037812A2 (en) Communications availability

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SD SE SG SI SK SL TJ TM TN TR TT TZ UA UG US UZ VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
DFPE Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101)
WWE Wipo information: entry into national phase

Ref document number: 2002709372

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2002709372

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP

WWW Wipo information: withdrawn in national office

Ref document number: 2002709372

Country of ref document: EP