Patent Grant
7162474
The invention relates to communications between parties, and in particular to a system and method facilitating a recipient party to control such communications. The invention also relates to a directory for use in such communications.
Many people now have various different communication devices at their disposal, such as, for example, so-called plain old telephone service (POTS) devices, mobile telephone devices, personal computers (PC) and hand-held computers. This variety of devices may complicate communications to the extent that, in order to communicate with a recipient party, an initiating party needs to know what devices the recipient party has, which of those devices is currently active and an address or location mechanism for each device. In other words, the initiating party needs to know about what is termed “the presence” of the recipient party.
Directories are available, particularly through the Internet, which provide contact details for individuals. However, the sheer number of these directories can be a problem, both from the point of view of data entry/maintenance and from the point of view of searching for a contact. Moreover, according to how widespread the contact details are to be disseminated and to whom they will be available, there may be a reluctance on the part of a contact to use a directory, or to use it to only a limited extent, because, for instance, of security concerns and the value which included details may have; for example, the addresses may be used for the purpose of compiling sales targetting lists. Allied to this is the fact that the contacts have no control over the use of details and whilst, on the one hand, they may wish to make them available in the interest of promoting communications, they may at the same time potentially expose themselves to unwanted contacts. This, as much as anything, is borne out of the fact that the contact has little if any control over existing communication routes, such as POTS or postal services. For such routes, there may be only two opposite extreme choices for the contact: either the valuable details are given out or they are withheld altogether. For example, not placing a telephone number in a telephone directory is an option, but legitimate initiating parties are then hampered from making contact. The purpose of a directory is undermined if it is not comprehensive and definitive. The problems associated with directories also apply to other instances in which someone may provide contact details, such as with a publication.
An object of the invention is to improve communications between parties. Another object of the invention is to give the recipient party control over such communications.
According to a first aspect, the invention provides a presence system comprising a database storing a plurality of entries each relating to a recipient party, wherein each entry is stored according to a unique identifier assigned to the corresponding recipient party and each entry includes at least one rule specifying a manner of communications between the corresponding recipient party and an initiating party, wherein the system manages communications between an initiating party and a recipient party according to the or each appropriate rule.
The presence system according to the first aspect of the invention effectively acts as an intermediary between an initiating party and a recipient party. Within the system, each recipient party enters contact details, of the type typically entered into a contact directory, but access to the details is controlled by the system. According to the identity of the initiating party, the details may or may not be released, or only certain details may be released. The dissemination of details is controlled according to the or each rule entered for the initiating party concerned. Therefore, the recipient party is given control over details disclosed such that they are more inclined to include details of themselves, thereby enabling the directory to be comprehensive and definitive. Moreover, the unique identifier is issued as an address for the recipient party, but it has no value in the sense that it does not enable an initiating party to make direct contact with the corresponding recipient party, merely to direct a request to communicate to the system, which then invokes the or each relevant rule specifying the manner of communication between the initiating and recipient parties. Thus, again, control over the communications rests with the recipient party.
Typically, the presence system may be realised as a server connected to an appropriate network, with the server hosting the database. Interaction between an initiating party and the database may be in the same way as interaction with an Internet web site and the server may generate data which various different initiating party Internet enabled devices may process. Alternatively, associated closely with the server may be a data conversion module for converting data from an initiating party device into a form which the server may process, and for converting data from the server into a form which the initiating party device may process. For instance, the module may comprise an analogue to digital conversion module, say, for voice to HTML conversion. In response to a request from an initiating party to communicate, the server may generate data which, when processed at an initiating party device, results in the opening of a communications application. Alternatively, the data may result in one or more instructions or notifications at the initiating party device. The data is dictated by the or each rule in the relevant recipient party entry for the initiating party requesting to communicate.
Initially, a recipient party will access the system to request inclusion on the database. Having been accepted for inclusion, a recipient party will be provided with a security mechanism, such as password, for accessing the database entry relating to them. They can then enter and maintain contact and other details contained in their entry.
The database may be queried by an initiating party and, in response to a query, the database may return the unique identifier. The query may take the form of use of known recipient party details which the database may compare with contact details it contains. A query may take the form of use of the unique identifier to obtain other details about the corresponding recipient party. The database may return the details in accordance with the or each rule for the initiating party which may specify whether and, if so, what information should be disclosed to the recipient party.
Each entry may include details of the communication devices at the disposal of the corresponding recipient party, and the or each rule may specify to which device communications from an initiating party should be directed. The system may periodically notify known initiating parties of their status in relation to the recipient party, that is, which recipient party device is available for communicating at that time.
Each entry may include details of know initiating parties, and there may be at least one rule specified for each known initiating party as well as a default rule for every other initiating party.
According to a second aspect, the invention provides a method of communicating between an initiating party and a recipient party comprising assigning to the recipient party a unique identifier and making at least one rule specifying the manner of communications between an initiating party and the recipient party, wherein the unique identifier is used to direct a request for communications from an initiating party to a system which manages communications between the initiating party and the recipient party in accordance with the or each rule.
According to a third aspect, the invention provides a directory comprising a plurality of entries each relating to a recipient party, wherein each entry is stored according to a unique identifier assigned to the corresponding recipient party and each entry includes at least one rule specifying a manner of communications between the corresponding recipient party and an initiating party.
According to a fourth aspect, the invention provides a directory comprising a plurality of entries each relating to a recipient party, wherein each entry is stored according to a unique identifier assigned to the corresponding recipient party and each entry includes at least one rule specifying which details from the entry may be disclosed to an initiating party.
With reference to
The system 4 is accessible in the manner of an Internet web site. Using a suitable Internet enabled device, any recipient party 6 may apply for use of the system 4. Stored within the database 10 are a plurality of entries each relating to a recipient party. At the time of acceptance for inclusion in the database 10, the system 4 assigns to each recipient party a unique identifier typically of the form name.for.individual @ presence.system.location.address. The prefix of the identifier is used as the key field in the database 10 for each entry, that is, the entry is stored according to the prefix and, subsequently, the prefix is used to access the relevant entry. Once accepted for inclusion, a recipient party may access their entry for details entry and for maintenance and updating purposes as illustrated in Step 10 of
Each entry includes details typically stored in contact directories such as name, address, telephone number, occupation, nationality, hobbies etc or any other details which enables a recipient party to be identified.
Each recipient party 6 may have several communication devices, all capable of connecting to the network 2, such as a POTS handset 14, a WAP mobile telephone 16, a PC 18 and a hand held computer 20. At any one time, primarily according to location and activity, one of more of the devices 14, 16, 18, 20 may be active for contacting the recipient party 6. Each recipient party 6 enters into their entry the details of the various devices 14, 16, 18, 20 they have available. A recipient party 6 may continually update their entry as to which device is currently active.
Each recipient party 6 may enter into their entry the identity of a number of known initiating parties 8. Against each initiating party, one or more rules may be entered, specifying the manner of communications between each known initiating party 8 and the recipient party 6, such as the device though which the initiating party may contact the recipient party, the form of the communication within the options available through the device, such as, for example, voice or text messaging, and the timeframe within which the rule is to apply. In other words, the rules enable the recipient party 6 to control how any initiating party communicates 8 with them. The recipient party 6 may also specify default rules applicable to all unknown initiating parties 8. The system 4 periodically communications to each known initiating party its status in relation to the recipient party
Individual rules may be altered at any time according to changes of circumstances affecting individual initiating parties 8 or may be globally altered, say, to account for circumstances which affect all initiating parties 8 such as unavailability due to illness.
Each initiating party 8 may have several communication devices, all capable of connecting to the network 2, such as a POTS handset 22, a WAP mobile telephone 24, a PC 26 and hand held computer 28. An initiating party 8 will fall into one of two categories: Either it will know the unique identifier for the recipient party 6, and it may use this to make contact with the recipient party as illustrated in Step 12 of
The process of determining the unique identifier involves an initiating party 8 accessing and querying the system 4. In the event that the initiating party 8 wishes to communicate using the PC 26, a WAP mobile telephone 24, a hand held computer 28 or any other Internet enabled device, the system 4 is accessed in the manner of accessing a web site. In response, a search page is downloaded to the device 24, 26, 28. The page includes various blank boxes or input ports into which the initiating party 8 may insert query criteria, that is, what it knows of the recipient party's personal details. The system 4 will return any matches, possibly more than one according to the specificity of the query criteria. In the case of multiple matches, there will be an option to select one of the or further to hone the query criteria. One or more matches may be stored in a communications application loaded on to the device 24, 26, 28 for later use. Alternatively, a match may be used straight away. Use may be on a “click to call” basis with the unique identifier presented as a link on a further downloaded page. From information stored within the device 24, 26, and 28 the identity of the initiating party 8 is sent to the system 4. The identity is compared with the identities of known initiating parties 8 included in the recipient party's entry. If a known initiating party is determined, the communication rules applicable to that party are invoked. If the initiating party is unknown, the default rules are invoked. Data is returned to the initiating party's device 24, 26, 28 according to the invoked rules as illustrated in step 18 of
The data may result in the opening at the initiating party's device 24, 26, 28 of the communications application appropriate to the manner of communication dictated by the rule. For example, if the rule applicable to that subscriber at this particular time is “communicate by e-mail”, the data may be processed at the subscriber device, resulting in an e-mail application, being opened: A message window may be automatically generated, made ready with the appropriate address. Once the message has been composed, it is sent. The recipient party 6 can, as with any other e-mail message, choose how to receive the message, that is, it could be downloaded as text or “listened to” via a text to audio conversion mechanism of the type now widely available.
Alternatively, the data may result in the opening of an SMS text managing application at the initiating party device 24, 26, 28, which enables the initiating party 8 to dispatch a text message to the recipient party.
Further alternatively, at least in the case that the initiating party is using a PC 26 or WAP mobile telephone 24, the data may result in the opening of a voice calling application. The voice call may be directed to the current voice calling device 14, 16, 18, 20 of the recipient party or may be directed to a voice mail message caching facility, for later access.
In the event that the initiating party 8 is using a POTS device 22, access to the directory server may be gained by dialling into a data conversion module 12 acting as a voice to data conversion facility. This enables the recipient party search criteria to be input verbally. This is achieved through a series of verbal prompts which the facility 12 puts to the initiating party 8. The unique identifier for the recipient party 6 is either relayed to the initiating party verbally, say for it to use with an alternative device, or the facility 12 gives verbal prompts of further actions such as “press 1 to call, press 2 to store”. A “call” response relays the identity of the initiating party 8 to the system 4. The identity is compared with the identities for the known subscribers stored in the recipient party's entry and the appropriate communication rules are invoked. If the rule is to communicate by voice, the initiating device 22 is connected to the specified voice device 14, 16, 18, 20 of the recipient party 6. If the rule is to communicate by non-voice, the voice recognition facility 12 translates a message spoken by the initiating party 8 into data and relays the data to the specified device 16, 18, 20 of the recipient party 6.
| Number | Name | Date | Kind |
|---|---|---|---|
| 3816668 | Giesken | Jun 1974 | A |
| 4602129 | Matthews et al. | Jul 1986 | A |
| 4740788 | Konneker | Apr 1988 | A |
| 5197092 | Bamburak | Mar 1993 | A |
| 5200994 | Sasano et al. | Apr 1993 | A |
| 5206901 | Harlow et al. | Apr 1993 | A |
| 5283856 | Gross et al. | Feb 1994 | A |
| 5373549 | Bales et al. | Dec 1994 | A |
| 5432841 | Rimer | Jul 1995 | A |
| 5608786 | Gordon | Mar 1997 | A |
| 5652789 | Miner et al. | Jul 1997 | A |
| 5696900 | Nishigaya | Dec 1997 | A |
| 5737011 | Lukacs | Apr 1998 | A |
| 5742668 | Pepe et al. | Apr 1998 | A |
| 5742905 | Pepe et al. | Apr 1998 | A |
| 5768513 | Kuthyar et al. | Jun 1998 | A |
| 5802253 | Gross et al. | Sep 1998 | A |
| 5870549 | Bobo, II | Feb 1999 | A |
| 5896128 | Boyer | Apr 1999 | A |
| 5917489 | Thurlow et al. | Jun 1999 | A |
| 5946386 | Rogers et al. | Aug 1999 | A |
| 5951638 | Hoss et al. | Sep 1999 | A |
| 5974465 | Wong | Oct 1999 | A |
| 6006253 | Kumar et al. | Dec 1999 | A |
| 6021428 | Miloslavsky | Feb 2000 | A |
| 6023762 | Dean et al. | Feb 2000 | A |
| 6058178 | McKendry et al. | May 2000 | A |
| 6094681 | Shaffer et al. | Jul 2000 | A |
| 6101531 | Eggleston et al. | Aug 2000 | A |
| 6104799 | Jain et al. | Aug 2000 | A |
| 6147977 | Thro et al. | Nov 2000 | A |
| 6148328 | Cuomo et al. | Nov 2000 | A |
| 6157945 | Balma et al. | Dec 2000 | A |
| 6175858 | Bulfer et al. | Jan 2001 | B1 |
| 6185565 | Meubus et al. | Feb 2001 | B1 |
| 6243398 | Kahane et al. | Jun 2001 | B1 |
| 6243714 | Shapiro et al. | Jun 2001 | B1 |
| 6247043 | Bates et al. | Jun 2001 | B1 |
| 6286029 | Delph | Sep 2001 | B1 |
| 6301339 | Staples et al. | Oct 2001 | B1 |
| 6301609 | Aravamudan et al. | Oct 2001 | B1 |
| 6310947 | Polcyn | Oct 2001 | B1 |
| 6330317 | Garfinkel | Dec 2001 | B1 |
| 6333973 | Smith et al. | Dec 2001 | B1 |
| 6350066 | Bobo, II | Feb 2002 | B1 |
| 6356934 | Delph | Mar 2002 | B1 |
| 6360252 | Rudy et al. | Mar 2002 | B1 |
| 6370233 | Bennett, III et al. | Apr 2002 | B1 |
| 6397259 | Lincke et al. | May 2002 | B1 |
| 6404762 | Luzeski et al. | Jun 2002 | B1 |
| 6424841 | Gustafsson | Jul 2002 | B1 |
| 6430604 | Ogle et al. | Aug 2002 | B1 |
| 6437818 | Ludwig et al. | Aug 2002 | B1 |
| 6438583 | McDowell et al. | Aug 2002 | B1 |
| 6438585 | Mousseau et al. | Aug 2002 | B1 |
| 6445694 | Swartz | Sep 2002 | B1 |
| 6457060 | Martin et al. | Sep 2002 | B1 |
| 6510461 | Nielsen | Jan 2003 | B1 |
| 6564321 | Bobo, II | May 2003 | B1 |
| 6584314 | Haumont et al. | Jun 2003 | B1 |
| 6594354 | Kelly | Jul 2003 | B1 |
| 6606647 | Shah et al. | Aug 2003 | B1 |
| 6609128 | Underwood | Aug 2003 | B1 |
| 6628194 | Hellebust et al. | Sep 2003 | B1 |
| 6807423 | Armstrong et al. | Oct 2004 | B1 |
| 20020114431 | McBride et al. | Aug 2002 | A1 |
| 20020120696 | Mousseau et al. | Aug 2002 | A1 |
| Number | Date | Country |
|---|---|---|
| WO 9934628 | Jul 1999 | WO |
