Nothing Special   »   [go: up one dir, main page]

WO2001099341A1 - Systeme d"adressage unifie - Google Patents

Systeme d"adressage unifie Download PDF

Info

Publication number
WO2001099341A1
WO2001099341A1 PCT/SG2001/000126 SG0100126W WO0199341A1 WO 2001099341 A1 WO2001099341 A1 WO 2001099341A1 SG 0100126 W SG0100126 W SG 0100126W WO 0199341 A1 WO0199341 A1 WO 0199341A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
platform
database
identifier
name
Prior art date
Application number
PCT/SG2001/000126
Other languages
English (en)
Inventor
Dennis Choo Han Goh
Balmik Singh Soin
Dinesh Singh Bhatia
Original Assignee
Dennis Choo Han Goh
Balmik Singh Soin
Dinesh Singh Bhatia
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 Dennis Choo Han Goh, Balmik Singh Soin, Dinesh Singh Bhatia filed Critical Dennis Choo Han Goh
Priority to AU2001274792A priority Critical patent/AU2001274792A1/en
Publication of WO2001099341A1 publication Critical patent/WO2001099341A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4555—Directories for electronic mail or instant messaging
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/48—Message addressing, e.g. address format or anonymous messages, aliases
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. TPC [Transmission Power Control], power saving or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0296—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level switching to a backup power supply
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present invention relates to a system or method of addressing for messaging over various electronic messaging platforms.
  • the system provides the user with a simplified method to remember and enter the different addresses that exists for each addressee under different messaging platform.
  • Each of these messaging platforms have their own unique addressing system. For example, (country code)+(area code)+(phone number) for telephones, fax and SMS; xxx@yyy.com for emails; a string of numbers for ICQ, etc.
  • (country code)+(area code)+(phone number) for telephones, fax and SMS; xxx@yyy.com for emails; a string of numbers for ICQ, etc.
  • An object of the invention is to provide a system that would enable a user to more easily send messages to a recipient, without needing the user to memorise each possible address for the recipient.
  • a further object is to provide such a system for a user to be able to send a message from one platform to at least one different platform.
  • the present invention provides in one aspect a method of addressing an electronic message wherein an address of an intended recipient includes: a platform identifier to identify which message platform the electronic message is to be sent to; and a name identifier to identify the name of the recipient.
  • the address may further include a modifier to separate said platform identifier and said name identifier.
  • the modifier may further determine which database to obtain the newest recipient from. It is envisaged that the platform identifier will ideally be a string of 3 characters.
  • the present invention provides a system for sending electronic messages to at least one message platform, said system including an addressing system wherein said addressing system receives and processes recipient addresses, said recipient address including: a platform identifier to identify which message platform the electronic message is to be sent to; and a name identifier to identify the name of the recipient.
  • the address may further include a modifier to separate said platform identifier and said name identifier.
  • Figure 1 shows how an actual messaging platform address may be constructed from the subject addressing system.
  • Figure 2 shows an alternative method of accessing the database.
  • the mutli-messaging platform addressing system of the present invention allows a user to:
  • the address of any user on any messaging platform under the present system includes a platform identifier, the addressee's name and a modifier to denote the database used in the system to extract the actual messaging address. That is, the address may take the form:
  • the identifier may be used to identify the messaging platform for transmitting the message, as well as the address in the addressee record to use.
  • the identifier may be any unique string of text that is recommended to be easily remembered and entered into any device. For example:
  • the modifier may be used to identify a database to be used to retrieve the platform address of the addressee based on the name.
  • the modifier may be used to distinguish between a central or shared database, a personal database, and any other database.
  • the modifiers may be used as follows: Database Modifier central/shared ? personal !
  • the addressee name may be used to identify the name of the record in the appropriate database to use to retrieve the platform address.
  • a person may be listed in another users personal address book under a different name from the central database name. Accordingly, examples of addresses under the present system for a user name "John” could have his Email, SMS, Fax, Telephone (voice) and ICQ addresses referred to as em ⁇ John, smsIJohn, faxUohn, voxUohn and icqlJohn respectively if using the sender's personal address book and emi?John, sms?John, fax?John, vox?John and icq?John respectively if using the central database.
  • the modifier could be any character and not just "! and "?”.
  • the system may also be implemented without the need for a modifier.
  • the platform identifier would be standardised to a predefined character length, such that the system will be aware that the first (or last) n letters are identifiers and the n+ 1 st character onwards is the user name.
  • the system may allow the user to also maintain a personal address book. The user is then able to use this personal address book when the name of the recipient under the central database is not found to be easy to remember by the sender. In such a case, the sender can enter a more easily remembered alias of the recipient into his personal address book and use the appropriate modifier, "! in this example, to instruct the system to use his personal address book to extract the correct address without causing a conflict with a possible similar name under the central database.
  • the system may be set up such that the personal address book is a separate database which the user is required to maintain.
  • the personal address book could contain a series of pointers to the relevant entry in the central database.
  • a private address book alone that is, without a global address book could be implemented.
  • the platform identifiers and modifiers chosen are important to the design of the present system as they are part of the design to make remembering and inputting of multiplatform addresses easy. Characters used for identifiers and modifiers should be easily accessible on a mobile phone without any special keystrokes as well as easy to remember.
  • the text input box when entering an address normally defaults to alphabets which make it easier to input alphabets rather than numbers. Special characters (not alphabet or number) will preferably be included to separate the identifiers from the usemame to denote where the identifier stops and where the username begins in the address.
  • the said special separators also denote which database the actual user address should be extracted from. On a mobile phone, ".”,”,”, "?", and "! are usually the most accessible special characters and should ideally be used as should be alphabets for identifiers and usemames instead of numbers.
  • the system will also enable a sender to message a user on a platform even when the sender does not have the recipient's address on that platform.
  • the sender will be able to deduce the address for the recipient. For example, if the sender only knows the name of the recipient, then the sender merely has to input the platform identifier and database modifier followed by the recipient's name and the sender will be able to send the message. However if the sender only knows the recipient's email but wanted to send a fax, then the sender would have to take the additional step to search for the addressee's name in the central database based on the email address.
  • the sender then Inputs the platform identifier for fax and the database modifier for the central database followed by the name.
  • the recipient can set different access rights to any of his addresses for any other user on the system so that even if his name was found on the central database through a publicly available email, the sender will not be able to send him a fax if the fax address was confidential and the sender was not given access rights.
  • the system could include a further feature whereby a user would be allowed to attempt to send a message to a person via one platform without necessarily knowing the name of the person, but provided that person's address or another platform is known. For example, if a user only had a fax number the user could try to e-mail the recipient by entering eml?651234567 (where 651234567 is the fax number) and the system will search and match a record with fields matching either an SMS, Fax or Phone address and return the e-mail address if one exists, and if the user has been given proper access rights. This may be better exemplified by reference to Figure 2. If we assume that the user wishes to send an email message having only the intended recipients facsimile number, then the message request 12 may be as follows:
  • the system searches 13 the database for any field containing "651234567". In this case, the central database is searched due to the use of the "?" modifier. In some cases, it is possible that the system will locate multiple records 18 matching the search criteria. For example, a company may have a number of employee's on the system all of whom have the same facsimile number. If the system does locate multiple records 18, then this list of records is returned to the sender to select the appropriate record. Once the appropriate record has been selected by the sender, the system then searches 19 for the appropriate address. In this case, if we assume that the fax number 651234567 matches John's record which was selected by the sender then the system searches for John's email address due to the identifier "eml":
  • the system locates only a single record, for example "John” was found to have a facsimile 651234567, then the system searches the database for the appropriate address based on the identifier, in this case John's * email address.
  • the system then replaces the actual address with the original address entered in the "TO" field 16, and forwards the message to the appropriate server.
  • the message is forwarded to the email server.
  • the system then enables the appropriate server to forward the message 17. Again in this case the email server forwards the email via the Internet.
  • access rights could be set up on 2 levels. Namely, an access option to view and send to the actual address and another access option to be able to send to the address but not view. This allows some level of privacy as the actual address is not known by the sender. If the recipient later decides he does not want messages from a particular sender, he can remove the "send" access and the sender has no way of finding alternative means to message the recipient since he does not have the actual address. To use the present addressing system, a user will need to use an appropriate multi-platform messaging system or a single platform messaging system integrated with the Unified Addressing System.
  • a sender To specify a particular recipient's address on any platform, a sender first types in the platform identifier, (eg eml for Email, sms for short text messaging, fax for facsimile and so on) followed by the appropriate database modifier to indicate to the system which database he wishes to use to extract the address (eg "?" for central database and "! for personal address book) and finally the recipient's name that is kept in the personal address book or central database as the case may be. The sender then proceeds to compose a message as he normally would on that particular platform or device and send the message upon completion. It will be understood that the identifier need not be a "?” or "!, but rather any symbol could be used.
  • the identifier be capable of separating the addressee's name from the platform identifier. If one system is such that the user is allowed to maintain a personal address book, then the identifier also needs to be able to indicate which address book is to be consulted, the personal address book or the system address book. Alternatively, as mentioned previously an identifier may not be necessary if only one database is used, however, it would still be recommended for ease of reading.
  • the system could also be implemented such that the personal database will be consulted first, and if no match is found for the addressee name, the system will then consult the system address book.
  • the system may be adapted to accept either an addressee's name or their actual address.
  • the system could analyse the address, to thereby register whether an actual address has been inputted or, alternatively, a different modifier could be used.
  • a modifier could be used to force the system to use a particular address. This could be advantageous when it is known that the user is temporarily at a different address.
  • the message is then sent from the appropriate device via whatever protocols that are employed by the device (eg WAP on WAP phones, HTTP on personal computers or other internet devices, etc.) through an internet connection (wireline or wireless) to the server on which the subject system is implemented.
  • the present system is deployed as a software engine on the system server which processes the information received from the user and accesses the relevant database on the database server that contains the names and their various platform addresses as well as access level settings.
  • the system splits the addressee field (usually the "TO:" field in a messaging platform) into a list of each platform address types.
  • the system works out what type of address it is from the unique platform identifier for instance eml for email, sms for SMS, fax for Fax, and so on.
  • the platform identifier will be 3 characters long, although an alternative coding system could equally be adopted once the system has identified the platform to send the message to the system.
  • calls the relevant database personal address book of a user or the central database
  • the relevant database personal address book of a user or the central database
  • the relevant database personal address book of a user or the central database
  • the system When a personal address book is specified, then the system will look up the database (personal address book) set up by the sender that is indicated in the "FROM" field of the message. Once the database has been identified, it is queried by the system for the record belonging to the recipient based on the name specified. It then extracts the actual platform address in the record from the relevant field in the record based on the platform specified in the identifier. The system then checks the database of the recipient to verify that the sender has been given appropriate access rights to usage of that platform address. If the sender does not have proper access rights, then the transaction is aborted and the sender is sent an error message.
  • the database personal address book
  • a message request 1 is received by the system. This message may for example be: TO: eml?john faxljohn
  • the user wishes to send an email to John using the record from the central database, and also a fax to John using the record on the users personal database.
  • the system may analyse each of the addresses in the "TO" field in turn. For example, the system will first consider processing "eml?john”. In doing so the system invokes a search 2, for a record with the name "John” which is housed on the central database as indicated by the modifier "?". Once the record "John" has been found on the central database, the system then searches for an address 3 which matches the identifier. In this case, an email address for John is searched for.
  • the email server sends out the message 6 through the appropriate channels.
  • the email server sends out the email message via the Internet.
  • the system may then consider the next entry in the "TO" field from the original message, namely "faxljohn”. Because of the "! modifier, the system searches 7 the personal database for records with the name "John". Once the record "John" has been located in the personal address book, the system then searches 8 for the appropriate address. In the present example, the system searches for a facsimile number given the "fax" identifier. Once the appropriate address has been located 9, this address is replaced 10 in the original "TO" field of the message and forwarded to the appropriate server. In the present example, the message is sent to the fax server. The appropriate server then forwards the message through appropriate means 11. Again in the present example, the fax server dials the fax number and sends out the facsimile through PSTN.
  • the message has been sent as requested by the user.
  • an email and a facsimile have been sent to John from David.
  • the email address was taken from the central database, and the facsimile number from the users personal database.
  • the system server identifies addresses used under the unified addressing system to belong to a particular messaging platform based on the unique platform identifier assigned to it.
  • the system server identifies the appropriate database to search for the actual platform address of the addressee based on the database modifier specified in the unified address format.
  • the system server searches the database identified in (2) for a record with name specified in the unified addressing format.
  • the system server extracts the actual platform address from the record found in (3) from the field that coincides with the messaging platform identified in (1).
  • the sender has appropriate access to the actual platform address, then the actual platform address is substituted into the "TO" field of the message and the entire message with the substituted address is sent to the relevant messaging server (email to email server, fax to fax server, etc.).
  • the messaging server formats the message into data in the relevant protocol of that messaging platform and uses the appropriate transmission channel and protocol to send the message (emails sent in SMTP over internet while faxes are sent via fax protocol over normal telephones and so on).
  • the preferred embodiment of the present invention will provide: (1) A standardised and centralised system of addressing users of various messaging platforms which is more intuitive and easier to remember than presently available systems. (2) A method or system of addresses for various messaging platforms that is easier to input on a mobile phone. (3) A method or system of allowing a user to message another user on any platform if the recipient's address is forgotten by or unknown to the sender or if the sender's personal address book is not available to him. The system will allow for confidentiality of a user's addresses if he chooses to keep them available only to an "allowed" audience but not to the general public.
  • the present invention will provide a system that enables a user to easily obtain, remember and input any user's address on any messaging platform from any communication device, especially on a mobile phone, by simply typing in a short identifier of a particular messaging platform and the usemame of the addressee, the latter of which will remain unchanged for all platforms.
  • a user with username John will have his Email, SMS, Fax and ICQ addresses referred to as eml?John, sms?John, fax?John, icq?John respectively.
  • Identifiers can be created for all existing as well as future messaging platforms.
  • a special character, in this case a "?” acts as a separator for the identifier and username as well as a modifier to allow retrieval of address information from a central database or a user customised address book.
  • the preferred embodiment provides a system to enable a user to easily obtain any other user's address on any messaging platform, if the user has been given appropriate access by the second user, input it easily (especially a mobile phone) on an appropriate device without first having been required to obtain it, store it and retrieve it.
  • users under the present system will each enter all of their own addresses of the platforms that they can be contacted on into the central database of the system so that other users need not create a separate address book by first having to obtain the addresses and inputting it into their personal address book.
  • the system will be configured such that the user will be allowed to keep certain addresses confidential, but may allow certain authorised people to access and retrieve those confidential addresses.
  • the system allows the user to simply enter an easy to remember identifier of any messaging platform and the username of the intended recipient and send off the message without needing to know, or at least recall, the actual address of the recipient on that messaging platform which may be difficult to remember and/or difficult to input, especially on a mobile phone.
  • the recipient's username is found to be difficult to remember by the sender, as in the case where a username is not his real name or a more easily remembered alias
  • the sender can set up his personal address book to address the recipient based on a name that the sender finds easier to remember, without causing conflicts in the central database.
  • the system would be able to identify which database to use in retrieving the correct platform address of the recipient by using modifiers to denote whether the sender is referring to the recipient's name on the central database or on the sender's personal address book.
  • the format of the present addressing system should be easy to input in all devices especially the mobile phone.
  • the sender In entering any platform address of a recipient, the sender is likely to be given the following options:
  • the sender may enter the platform identifier, the appropriate modifier of the database to be used and the username on the central database or personal address book whichever the case may be.
  • the sender may select a username and platform address from the sender's personal address book.
  • the sender may enter the actual platform address in the appropriate format.
  • the user may access the system via a mobile phone and any other internet-enabled or appropriately-enabled device over WAP or other suitable network.
  • the present invention is unique in that it enables a user to message another user on any electronic messaging platform without having to remember or even knowing the actual platform address of the recipient.
  • the said system allows the sender to intuitively enter an address under the said system and send a message to the intended audience just by knowing their username or any one of their actual platform addresses.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

La présente invention concerne un procédé d"adressage de message électronique dans lequel une adresse d"un destinataire prévu comprend: un identificateur de plate-forme permettant d"identifier la plate-forme de message où le message électronique doit être envoyé, et un identificateur de nom permettant d"identifier le nom du destinataire
PCT/SG2001/000126 2000-06-21 2001-06-21 Systeme d"adressage unifie WO2001099341A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2001274792A AU2001274792A1 (en) 2000-06-21 2001-06-21 Unified addressing system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
AUPQ8275 2000-06-21
AUPQ8275A AUPQ827500A0 (en) 2000-06-21 2000-06-21 Unified addressing system

Publications (1)

Publication Number Publication Date
WO2001099341A1 true WO2001099341A1 (fr) 2001-12-27

Family

ID=3822342

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SG2001/000126 WO2001099341A1 (fr) 2000-06-21 2001-06-21 Systeme d"adressage unifie

Country Status (2)

Country Link
AU (1) AUPQ827500A0 (fr)
WO (1) WO2001099341A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004057884A1 (fr) * 2002-12-23 2004-07-08 Intellprop Limited Dispositif pour services telecommunications et procedes utiles dans la messagerie de telephonie mobile
EP1802056A1 (fr) * 2005-12-22 2007-06-27 Research In Motion Limited Système d'adressage unifié
US7904099B2 (en) * 2005-12-22 2011-03-08 Research In Motion Limited Unified addressing

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1987007801A1 (fr) * 1986-06-02 1987-12-17 American Telephone & Telegraph Company Systeme de communication ayant une messagerie unifiee
WO1997033413A1 (fr) * 1996-03-04 1997-09-12 British Telecommunications Public Limited Company Systemes de messagerie
JPH10154075A (ja) * 1996-11-25 1998-06-09 Nec Corp 移動エージェントのアドレス管理方法および移動エージェント装置
WO1999017504A1 (fr) * 1997-09-29 1999-04-08 Ericsson Inc. Application de messagerie presentant plusieurs capacites d'interface
WO2000041366A1 (fr) * 1998-12-31 2000-07-13 Michael Voticky Dispositif d'affectation de priorites pour communications

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1987007801A1 (fr) * 1986-06-02 1987-12-17 American Telephone & Telegraph Company Systeme de communication ayant une messagerie unifiee
WO1997033413A1 (fr) * 1996-03-04 1997-09-12 British Telecommunications Public Limited Company Systemes de messagerie
JPH10154075A (ja) * 1996-11-25 1998-06-09 Nec Corp 移動エージェントのアドレス管理方法および移動エージェント装置
WO1999017504A1 (fr) * 1997-09-29 1999-04-08 Ericsson Inc. Application de messagerie presentant plusieurs capacites d'interface
WO2000041366A1 (fr) * 1998-12-31 2000-07-13 Michael Voticky Dispositif d'affectation de priorites pour communications

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
PATENT ABSTRACTS OF JAPAN *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004057884A1 (fr) * 2002-12-23 2004-07-08 Intellprop Limited Dispositif pour services telecommunications et procedes utiles dans la messagerie de telephonie mobile
AU2003290302B2 (en) * 2002-12-23 2008-10-09 Intellprop Limited Telecommunications services apparatus and methods in mobile telephony messaging
EP1802056A1 (fr) * 2005-12-22 2007-06-27 Research In Motion Limited Système d'adressage unifié
US7904099B2 (en) * 2005-12-22 2011-03-08 Research In Motion Limited Unified addressing
US8204526B2 (en) 2005-12-22 2012-06-19 Research In Motion Limited Unified addressing

Also Published As

Publication number Publication date
AUPQ827500A0 (en) 2000-07-13

Similar Documents

Publication Publication Date Title
US7010572B1 (en) System for handling electronic mail
US7774409B2 (en) Providing common contact discovery and management to electronic mail users
US6101320A (en) Electronic mail communication system and method
US5968117A (en) Device and system to facilitate accessing electronic mail from remote user-interface devices
US7499976B2 (en) Warning and avoidance of sending email messages to unintended recipients
EP0854655B1 (fr) Serveur-client de communication multi-format et méthode correspondante
USRE43284E1 (en) Method of triggering a transfer of data stored in a database
EP1169842B1 (fr) Messagerie anonyme au moyen de telephones mobiles
US11522823B2 (en) Method and apparatus for storing email messages
US20020188690A1 (en) System and method for checking and correcting electronic mail address
US20060288298A1 (en) System, method and technique for enabling users to interact with address fields of messaging applications
US20060129696A1 (en) Systems and methods for communicating across various communication applications using single address strings
JP2002330234A (ja) 電話と電子メールの連携システム及び連携方法
US20020173300A1 (en) Method and system for completing incomplete addressing data sent to a communication device
US20030191647A1 (en) Method & system for managing web pages, and telecommunications via multilingual keywords and domains
EP2020644A1 (fr) Système et procédé de réponse automatique à un message envoyé vers un utilisateur sur un serveur de courrier électronique
WO2001099341A1 (fr) Systeme d"adressage unifie
JP2004040304A (ja) 電子メールアドレス管理方法およびプログラム、電子メール端末装置
CA2375536A1 (fr) Systemes et methodes de communication parmi plusieurs applications variees utilisant une simple branche d'adresses
JP2002183002A (ja) 訂正候補のドメイン名を通知するサーバ装置、およびこのサーバ装置により通知された訂正候補のドメイン名を利用するクライアントコンピュータ、およびこのクライアントコンピュータ上で動作するプログラムを記録した記録媒体、および訂正候補のメールアドレスを通知するメールサーバ
AU748502C (en) System for handling electronic mail
EP1172976A1 (fr) Procédé de transfert de données stockées sur une base de données
JP3712113B2 (ja) 迷惑メール防止システム、迷惑メール防止方法、及び迷惑メール防止用プログラム
KR100575731B1 (ko) 전화번호 검색을 위한 이동통신 단말기 및 이를 이용한 전화번호 검색 방법
JP2024033654A (ja) 情報処理装置、情報処理方法及びコンピュータプログラム

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 CR CU CZ DE DK DM DZ 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 PL PT RO RU SD SE SG SI SK SL TJ TM TR TT TZ UA UG US UZ VN YU ZA 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 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 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)
REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP