CZ20014251A3 - Systems and methods for communicating across various communication applications using single address strings - Google Patents

Abstract

Systems and methods are disclosed for providing addressing strings formats and associated system implementations to minimize the number of different addressing strings used for communicating across different communication applications. The systems and methods receive a valid address string that can be inputted into a communication applications selected from a collection of communication applications wherein the same address string can be inputted for any selected communication application from that collection.

Description

Systems and methods of communication in different applications using single communication address strings

Related Applications

This application claims priority from US provisional applications:

1. Serial No 60 / 137,137 entitled “Addressing system with error correction for Internet, telephone and other communication systems using a single universal address string, filed on

May 27, 1999

2. Serial No 60 / 138,927, entitled "Error-corrected Addressing System for Internet, Telephone and Other Communication Systems Using a Single Universal Address Chain", filed June 11, 1999, and

3. Serial No. 60 / 153,426 entitled "Error-corrected Addressing System for Internet, Telephone and Other Communication Systems Using a Single Universal Address String", filed September 10, 1999.

The text of each of these applications is incorporated herein by reference.

Technical field

The present invention generally relates to address strings used in various communication applications for communication purposes.

BACKGROUND OF THE INVENTION

Currently, users of most communication applications, such as a telephone, e-mail or Internet website, are required to insert a predetermined address string into the communication application to effect the desired communication with the intended recipient. For example, an email application user must enter an address string in the form of a predetermined email address, such as iohndoe@address.com. to send a message to the recipient.

It is generally assumed that an address string is a sequence of components having alphanumeric or other characters recognizable by a human and / or machine. Such address sequences may generally be of any length or type of components, but their exact arrangements are usually predetermined by the service provider in the communication application. For example, in the case of a telephone, the address string used is a telephone number whose length and sequence of digits are often given by the telephone service provider. Similarly, in the case of Internet websites, a predetermined Uniform Resource Locator (URL) is typically used to access an Internet user to a desired page.

The use of certain address strings, such as telephone numbers, to establish communication with another location through a communication medium is well known. However, recent technological advances, particularly in the field of computer networks and telecommunications, have resulted in the emergence of many new and / or different forms of communication. For example, communications using e-mail, www sites, or other communications applications such as facsimia are among the previously unavailable alternatives to telephone calling.

• · * · φ · φ φφφφφφφ «φφφφφ

However, an increase in the number of communication methods results in an undesirable corresponding increase in both the number and types of address strings associated with each such communication form. In addition, the underlying technologies used to implement such diverse communication applications typically require the user to enter an address string that is largely specific to these technologies in order to operate and benefit from the communication applications. Even communication applications of the same type, but with different formats, such as an email application at two different email service providers, often require the use of different address strings. For example, an individual who has an email account with two or more email service providers is a single receiving entity that will nevertheless have two or more assigned email addresses, usually in the form of a single email address for each service provider.

One problem of the existing approach of assigning one address string to a user for each communication application is the generation of multiple address strings for a single recipient. For example, when attempting to communicate with a hypothetical recipient (John Doe) having an email, www page, and telephone, the end user often needs to know and remember exactly the different address strings belonging to each application in order to communicate with that recipient using that application. For example, the user must correctly enter iohndoe@address.com. in order to send the recipient an e-mail, insert a often long and difficult URL string such as http: //www.address.cpm/iohndoe. to access the recipient's website and enter the phone number in the telephone system if he / she wants to communicate with the recipient by telephone.

The requirement for the end user to know and remember the individual address strings is further aggravated by the use of domain names as web addresses. A domain name such as www.uspto.gov is in the form of an address string that is generally designed to include human-recognizable characters and / or numbers to assist the user in searching and / or remembering

• v • · 44 • <4 4 4 * • 44 4 4 4 • * · • 4 4 4 4 44 4444

to the correct address string. Once a domain name is inserted into a communication application, the system domain name (DNS) server converts that domain name into a standard Internet Protocol (IP) digital address, such as 255.100.1.0, for internal network use.

However, the implementation of domain names as address strings is not without drawbacks. Domain names become increasingly longer over time, making them more difficult to remember. In addition, there is a general lack of standards regarding adherence to spelling conventions when compiling a domain name or even in what language they should be. Because domain names are often registered for legal recognition, such a lack of standards implies the need to register a domain name in many ways to include different language and / or spelling variations in each language in which the domain name is to be used.

In addition, because for practical reasons there is a relatively limited number of words to create a domain name, legal consequences such as trademark disputes and illegal accumulation of domain names in violation of rules and occupation of domains (cybersquatting) arise.

The Domain Name Server (DNS) also has limited options for handling errors or changes in the embedded domain name that are caused by misspellings or errors such as inserting an underscore instead of a hyphen in the address. These errors or changes often cause DNS to not recognize and / or incorrectly decide on the address string, resulting in user failure to establish the desired connection in the DNS-based system. Moreover, the DNS-based system is largely confined to Internet web addresses and does not address the problem of multiple address strings for other communications applications such as e-mail and phone numbers.

«0 0 0 000 0 0 0 0

0 · · · ·

0 000 * 000 0 »0 000 000

000 0 00 000 00 000 ·

Recent attempts to tackle the problem of multiple address strings have revolved around unifying address strings using unified messaging systems such as Microsoft's Exchange Server and MCI's Onebox.com messaging system. However, for several reasons, these attempts do not meet expectations in solving the problem of multiple address strings for users. First, the message delivery system is based on sending a message via fax, voicemail, etc. However, this does not allow direct calling and connection to a person by standard voice call as in the telephone system. Second, message delivery systems are primarily designed for the operation of a telephone service such as fax, voicemail, and the like, and still do not address the problem of multiple address strings of other applications such as e-mail and URLs.

It is therefore an object of the present invention to overcome the shortcomings of the above-mentioned prior art.

SUMMARY OF THE INVENTION

One object of the present invention is to provide systems for receiving a valid address string that can be inserted in a communication application selected from a set of different types of communication applications, wherein the same address string can be validly inserted for any communication application selected from that set.

It is another object of the present invention to provide methods for receiving an address string in a telephone number format embedded in at least one communication application selected from a set of different types of communication applications, wherein the same address string can validly be inserted for any communication application selected from that set.

4 4 4 4

444 4 · 4,444 «4,444

Another object of the present invention is to provide methods for receiving an address string embedded in two or more communication applications selected from a set of different types of communication applications, wherein the same address string can be validly embedded for any communication application from that set.

Yet another object of the present invention is to provide systems and methods for generating a valid Internet address for an Internet communications application, wherein at least one insert string is received as input, a distinction is made between valid and invalid elements in the insert string, and at least one valid internet address for internet communication application.

It is a further object of the present invention to provide methods for converting an address string into a predetermined Internet or email address format, wherein at least one alphanumeric embedded address string is received as input, and the embedded string is reordered in an output string with an order format different from the embedded address string wherein the output string is in a predetermined Internet or e-mail address format, based on the communication application used.

It is a further object of the present invention to provide such methods of operation of domain name servers, wherein substantially at least one domain name server is allocated to handle one or more lower level domain names, each of these lower level domain names being represented by at least one numeric or alphanumeric string in the domain. phone number format.

It is a further object of the present invention to provide systems and methods for mapping an address string to a predetermined corresponding number, recognizing numerical categorical identifiers in the mapped output, and reordering the mapped output based on * 4 4 44 4444

4 4 4. 44

444 4 «4 4« · «« 4444 recognized numerical categorical identifiers into a predetermined hierarchical format.

Accordingly, these and other objects are achieved in the present invention by creating address string formats and implementing an associated system, in order to minimize the number of different address strings used for communications in different communication applications.

In a first embodiment, the present invention is a system for communicating via at least one communication medium. The system includes an input subsystem for receiving an address string, wherein the address string has a valid format recognizable by the input subsystem and is embedded in at least one communication application selected from a set of different communication applications, wherein the same address string can be inserted for any selected communication application from the file.

In another aspect, an object of the first embodiment of the present invention is a method of communication via at least one communication medium. The method comprises receiving an address string having a telephone number format and inserted into at least one communication application selected from a set of different communication applications, wherein the same address string may be inserted for any selected communication application from the file.

In yet another aspect of the first embodiment of the invention, it is a method of communicating via at least one communication medium, the method comprising receiving an address string embedded in two or more communication applications selected from a plurality of different communication applications, the same address string being embedded for any selected communication application from file.

fc 4 4

4 * 4444

In a second embodiment of the present invention, it is a method and system for generating a valid Internet address for an Internet communication application. The method and system include receiving at least one embedded string as input, distinguishing between valid components and invalid components in the embedded string, and creating at least one valid Internet address from the valid components for the Internet communication application application.

In a third embodiment of the present invention, it is a method of converting an address string into a predetermined Internet or email address format. The method includes receiving at least one embedded address string as an input, wherein the address string comprises a set of alphanumeric characters, reordering the embedded string into an output string with a different order format than the input address string, wherein the output string is in a predetermined Internet or e-mail address format based on the communication application used.

In a fourth embodiment of the invention, it is a method of operating domain name servers. The method comprises substantially allocating at least one domain address server to servicing one or more lower-level domain names, each of these lower-level domain names being represented by at least one numeric or alphanumeric string in a telephone number format.

In a fifth embodiment of the present invention, the method and system is an address string mapping system. The method and system include receiving as a valid address string input, the string having at least one component that is a member of an alphanumeric file, mapping each of the components of said address string to a predetermined corresponding number, recognizing numerical categorical identifiers in the mapped components and reordering mapped components. component based on recognized numeric ft ftftftft ftftftft · ftftft · ftft ftftft ftftftft ftft ftftft ftftft ftft ft ftft ftftft ftft ftftftft categorical identifiers according to a predetermined hierarchical format.

In one exemplary embodiment, the invention includes, but is not limited to, execution in the form of specific computer executable software code located at the end user and / or neo in the server (s) in a dedicated top-level domain name or e-mail server. The software operates to carry out some or all of the above-described embodiments of the present invention.

This brief overview has been presented for a quick understanding of the nature of the invention. The invention will be better understood by reference to the following detailed description of the preferred embodiment and the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

Numerous exemplary embodiments of the invention are described below together with the accompanying drawings, but the invention is not limited to these embodiments. In order to better illustrate exemplary embodiments of the claimed invention, reference is made to the drawings in the description. It is not an exhaustive list of various embodiments of the present invention.

Giant. 1.0 illustrates a general method in which a user enters requests into an input device in the form of an input string.

Giant. 1.1 shows an example of simultaneous execution of multiple different user requests that are embedded in multiple different input devices using multiple different input chain systems.

«♦

Giant. 1.2 illustrates an example business card depicting the known three different methods for contacting the business card holder.

Fig. 1.3 is an example of a business card showing a method of contacting the holder of the business card in accordance with the claimed invention.

Giant. 1.4 shows an example of multiple different user requests that are input to multiple different input devices using a single system input chain according to the invention.

Giant. 3.0 illustrates aspects of the claimed invention when the invention is implemented in existing systems having a telephone and a WWW,

Fig. 2.0 is a flowchart showing in more detail the operation of the present invention in a WWW environment.

Giant. 3.2 illustrates aspects of the claimed invention when the present invention is implemented in existing e-mail systems.

Fig. 2.1 is a flowchart illustrating in more detail the operation of the present invention in an electronic mail environment.

DETAILED DESCRIPTION OF THE INVENTION

The systems and methods of the present invention are generally implemented to minimize the number of different address strings that are inserted by users to communicate through different communication applications.

Giant. 1.0 illustrates a method in which user input is translated into a machine-usable form. As shown in Fig. 1.0, the user action 100, such as a request for access to a location, is at 4.

Web, embedded in an input device 101, such as a web crawler, in the form of an input string 102.

Fig. 1.1 shows further examples of the general solution shown in Fig. 1.0. Giant. 1.1 illustrates in particular four different user actions 110-113 that are embedded in four different input devices using four different system input strings. In the example action 110, the user action is a telephone connection request, using the telephone number as the input string. In the example of action 111, the user action is a web access request that uses the current WWW address string as the input string. In the example of user action 112, the action is an e-mail correspondence request using the current e-mail address string as the input string. Similarly, in the example of user action 113, request actions through other communication applications, such as facsimile, file transfer protocol (FTP), etc., use appropriate prior art access methods as an input string for each communication application.

Giant. 1.2 illustrates, by way of example, a business card 120, one problem associated with the prior art approach where multiple different system input strings have to be used. As shown in Figure 1.2, the hypothetical John Doe represents a typical business card holder that can be connected to three different communication applications, by telephone 12 via WWW 122 and via email 123, Requesting a different system input string for each communication application means that the business card displays each of three different ways to contact the business card holder. The disadvantage associated with such access is that a user wishing to contact John Doe must enter a different address string for each communication application used. In addition, when a business card is unavailable to a user, the user must resort to remembering the address strings for contacting the business card holder. The need to use three different address strings (one for each communication application type) reduces the chances 9 9 9 9 9 9

9 9 9 9 9 • 9 999 99 9999 users to remember each string correctly. This problem becomes particularly important when only one possible form of communication application is available to the user. For example, a user is able to remember John Doe's phone number, but not the email address he needs at the moment to send an important message.

Giant. 1.3 illustrates an example of the business card of FIG. 1.2, but utilizing the novel features of the present invention which consist in minimizing the number of input strings required. As shown in the example, using only one input string 125 is sufficient for the business card holder to be contacted using one of the aforementioned methods of communication, that is, by telephone, web or e-mail.

Giant. 1.4 further demonstrates the features of the present invention as shown in the business card example of FIG. 1.3. Giant. 1.4 illustrates in particular four different actions 126-129 of the user to contact John Doe that enter four different input devices but use only one system input string. In the case of action 126, the user action is a call request to John Doe using his phone number as the input string (18005551234IPN in this example). The suffix "IPN" can be entered as three separate digits 4, 7 and 6, which correspond respectively to the letters "I", "P" and "N" on the standard telephone keypad. In the case of action 127, the user action is a request to access the John Doe's Web page, using the address string of the present invention as the input string. In the case of action 128, the user action is a request for email correspondence with John Doe using his email address string as the input string. In the example of action 129, similar actions of the user of the request are through other communication applications believed to fall within the scope of the claimed invention, such as facsimile, file transfer protocol, etc., using the appropriate «« ”'· ♦”' · · ' Access methods as an input string for each communication application.

Starting with Figure 3.0, an operation according to one embodiment of the invention will now be described in more detail. Giant. 3.0 illustrates embodiments of the present invention that are used for simplicity in a telephone system or a Web environment.

As shown in Figure 3.0, the user chooses to contact John Doe via telephone or WWW. In selecting the telephone system 320, the user inserts an input string in the form of a telephone number into the telephone device 321. For a better demonstration of the operation of the invention, a detailed input string 180055512341PN from a John Doe business card is used. The user enters the initial digits by simply selecting the correct number on the telephone keypad. The suffix "IPN" is inserted as three separate digits 4, 7 and 6, which correspond to the letters "I", "P" and "N" on the standard telephone keypad. The additional digits "467" will not affect the start string as they are gradually neglected as redundant digits in accordance with the telephone system protocols implemented in the telephone device 321, the telephone network 323 or other device intended for such purpose. Thereafter, standard telephone connection protocols are followed to connect the user to the target telephone device 325 here with the John Doe telephone.

When selecting a computer system 302, a user enters an input string, which is in the form of a telephone number, into the appropriate entry point of the client software supporting the desired communication application, such as the single source tag (URL) input field of the web communication application.

Although some existing Internet communication applications may currently recognize an input string that is in the form of a phone number, these applications are limited to a specific

Registr φ φ φ φ φ φ φ φ φ registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr registr For example, a flower sales website registered as 1-800-flowers will be identified as different from the 1800 flower, which the user may mistakenly insert while trying to access the website. This may result in the user failing to reach the desired location. The present invention solves this problem by implementing IPNS logic 322 to convert an input string, which is in the form of a telephone number, into a validly recognizable Internet addressing input format, while allowing for changes and errors in the inserted string. The details of the IPNS logic 322 software are discussed further in conjunction with Figure 2.0.

As shown in Fig. 3.0, IPNS logic 322 may be located either at the user end in the form of client software 316 supporting IPNS logic 322 or may be implemented on the server side, such as server level 311 of the system database, or both, as shown. route 317 in the flowchart. A system database server is typically a domain name server (DNS) or similar system. The operation of a DNS or similar system is well known to those skilled in the art.

In one embodiment of this arrangement, the user address string is embedded in the client software 316. which supports IPNS logic 322. The embedded address string is then converted by the client IPNS logic 322 at the client end to a validly recognizable Internet address input format. The converted input is then sent via the Internet to the appropriate system database server 319 or 311, as shown in paths 318 or 317. By contrast, server 319 or 311 may map an input string to an Internet Protocol (IP) address of the destination computer or network device 307 and return the IP address to the client software 316. The client software 316 can then use the IP address to bring the user to the designated destination computer or network device 307 • 0 • φ v »·» · φ

• 0 φ φ φ

• Φ 0 ·

Φ 0

Φ Φ Φ 0 0

0 · 0000 supporting the desired web site, here the John Doe website.

In another embodiment of this embodiment, the user address string is embedded in the original software 308 that does not support IPNS logic 322. Existing client software 308 then passes the address string to the appropriate system database server 311 that supports IPNS logic 322. according to existing Internet address recognition protocols. then the IPNS logic 322 in the server is converted to a validly recognizable Internet addressing input format and then mapped to an Internet protocol (IP) address of the destination computer or network device 307 according to existing protocols. The IP address is then returned to client software 316, client software 316 then can use the IP address to direct the user to the designated destination computer or network device 307 supporting the desired Web site, here John Doe's Web site.

The operation of the IPNS logic 322 will now be described in more detail with reference to Fig. 2.0. In the flowchart, Figure 2.0 shows the sequence of processes within the IPNS logic unit 322.

In step 200, the user-entered address string enters the IPNS logic unit 322. For a better demonstration of the operation of the invention, the FIG. Simple input string 1800JKL1234.IPN is used.

In step 203, the portion of the address string that describes the domain name for which the name server is relevant is removed. In this way, a portion of the IPNS sequence within the inserted address string is identified and is separated from the rest of the inserted address string. For example, in the case of the input string 1800JKL1234.IPN, "IPN" is separated and as a result the identified and separated IPNS sequence of 1800JKL1234 is left.

In step 204, the value of each character within the IPNS sequence is translated into values defined by the system (s) or system administrator (s). In an exemplary embodiment, the values are translated in accordance with the following table, which is based essentially on a telephone keypad configuration.

• · * • ·· ♦ Φ ’· · • · • * • «· • ·· Φ ♦ «* ·· * ·· ····

0 is translated to 0 1 is translated to 1 2abcABC is translated to 2 3defDEF is translated to 3 4ghiGHI is translated to 4 SjkIJKL is translated to 5 6mnoMNO is translated to 6 7pqrsPQRS is translated to 7 8tuvTUV is translated to 8 9wxyzWXYZ is translated to 9 All the others non-characters included

table, such as dashes and underscores, are simply ignored. For example, the IPNS sequence 1800JKL1234 is translated to 18005551234.

One advantage of the foregoing feature of the invention is that changes and errors such as inserting an underscore instead of a dash are filtered out in the translation process. For example, if the user entered 1-800-JKL_1234, this address would still be translated into the correct sequence 18005551234. In today's DNS-based system, which is often error-sensitive, such changes and errors will not result in DNS not recognizing and / or incorrectly decodes the address string and does not cause the user not to be connected to the requested location.

In step 205, the order in which characters, fields, or combinations thereof (mostly left to right) is presented in the translated IPNS sequence is reordered into a new right-to-left configuration.

· Fcfc fcfc fcfc fcfc fc fcfcfc fcfc fcfcfcfc

For example, the translated IPNS sequence 18005551234 will be new sorted to form 43215550081.

In step 206, the reordered IPNS sequence is segmented according to a data-driven variable segmentation format. The segmentation format is used to determine the number of fields in the sequence and the length of each field in the number of characters for the purpose of inserting dots {i.e. ".") Between fields in the sequence. An example of a segmentation format is the 4-3-4 format, where the IPNS sequence number is segmented from right to left, first to a group of four right-most digits, then to the subsequent three, followed by the last four. The dot is then inserted between each segmented group. For example, the newly sorted IPNS sequence 43215550081 will be segmented using 4-3-4 to 4321.555.0081. Segmentation is also data-driven and recognizes numerical categorical identifiers such as country number or area codes, so that in the case of embedded IPNS sequences having a different format, such as those having a foreign country telephone number format, a different segmentation format may be used. In the exemplary embodiment, the different segmentation formats are changeable so that adaptation to the formatting settings can be made as desired or desired. In addition, various segmentation formats are stored in a database where they can be retrieved using the IPNS processor,

In step 207, the portion of the address string separated in step 203 that describes the domain name for which the name server is critical is now reconnected to the newly ordered segmented IPNS sequence. The result is the reconstruction of the input chain into a format that is compatible with the underlying communication technology and addressing system used. For example, 4321.555.0081 is converted to 4321.555.0081.ipn.

In step 207, the name server is allowed to process the output string 209 as if it were the original DNS query according to the DNS protocols.

If no alternative information is found for the string, it can

• ·· • »« · • * on · • · • ·· • ·· ♦ · • Φ v v • · • * • «· • • < • ·· · • ··· ·· ····

then send the name server data to the DNS recognizer that presents the new string as the canonical name for the original domain queried, in addition to any recognition data belonging to the new DNS address.

It should be noted that the various steps and the specific order of the above operations were meant merely as an example, and any procedure using one or more of the routines described above that provides a string consistent with the desired output string format 209 is considered within the scope of the claimed invention.

Giant. 3.2 depicts another embodiment of the present invention used in an e-mail environment. As shown, the client software 366 and 358 are coupled to a client e-mail server 350 that is connected to an Internet address recognition system such as a system database. servers 319 or 311 using IPNS logic 322 to obtain an address in the Internet protocol (IP) of the destination e-mail server 355. The destination e-mail server 355 receives and processes the addresses of e-mail messages using the IPNS e-mail logic 356 to resolve the address to the canonical email address, and then forwards the email message to the recipient via path 371.

The embodiment shown in Figure 3.2 will now be described in more detail. For a better demonstration of the operation of the invention, a single input string 1800JKL1234.IPN is used throughout the detailed description of the present invention in FIG. 3.2 and later in FIG. 2.1.

At step 348, based on the availability or selection of new or existing software, the user inserts an input string, which is in the form of a telephone number, into the appropriate location of either new client software 366 or existing client software 358, both supporting an email communication application and with a client email server 350. For example, a user would enter the address string "1800-555-1234.ipn" or "18005551234.ipn" in the box ("send to:")

• φφφ · ΦΦ * • · on · ♦ Φ Φ Φ * Φ Φ * «· • • φ • · φ Φ * • Φ * • · φ ΦΦΦ · ·· ΦΦΦ * · ····

an email program running on a computer that's connected to the Internet. The currently used e-mail protocols generally do not recognize the input string, which is in the form of a telephone number, as valid input due to the absence of a symbol in the string. The present invention solves this problem by implementing one or more IPNS transfer logic 351, IPNS logic 322, and IPNS email logic 356. The IPNS logic 322 used for the e-mail communication application is the same as the IPNS logic described in Figure 2.0 in conjunction with the WWW embodiment, which is shown in Fig. 3.0. The details of the IPNS email logic software 356 are further described in connection with Figure 2.1.

In the exemplary embodiment of FIG. 3.2 and following path 365, the IPNS logic 322 is located in the client software 366 and converts the input string, which is in the form of a telephone number, directly into a validly recognizable Internet addressing input format. As a result of the requirements of existing e-mail protocols, the translated embedded address must generally contain a symbol and at least one character or client software will generally not accept input to initiate the address recognition process. The IPNS conversion logic 351 then converts the output of the IPNS logic 322 to a validly recognizable Internet e-mail addressing input format by appending a symbol and at least one character so that the client software initiates the address recognition process. However, unlike existing systems, a symbol and an accompanying feature are included in the address string of the present invention only to make the phone address string appear as a valid address according to existing e-mail protocols so that the address recognition process can be initiated. One advantage of the preceding feature is that the user no longer needs to enter an email address that has a symbol

The new client software 366 may then send the converted input to the client email server 350. Because some client software applications accept user input address strings without a symbol and pass it to the client email server 350 for address recognition, it may the client email server 350 also includes IPNS conversion logic 351 for converting the output of IPNS logic 322 to a validly recognizable Internet e-mail address input format by assigning a symbol and at least one character. The client e-mail server 350 then sends Internet access to the appropriate system database server 319 or 311. As shown in paths 368 or 369. The system database server is typically a domain name server (DNS) or a similar system known to one skilled in the art. The DNS server 319 or 311 maps the input string to an address in the Internet protocol (IP) of the email server that supports the recipient's email service (here John Doe) according to existing protocols and returns the IP address to the client software 366. The client email server 350 then uses the IP address to send the e-mail packet along with the user's address string to an IP address location, generally belonging to the destination e-mail server 355. which supports the e-mail service for the recipient.

According to another aspect of the embodiment of Fig. 3.2, the user's address string is embedded in existing existing client software 358. which does not support IPNS logic 322. Due to the requirements of existing email protocols, the user entered address must include a symbol and at least one character, otherwise to initiate the address recognition process. In contrast to current systems, however, a symbol and an accompanying feature are included in the address string of the present invention only to make the phone address string appear as a valid address according to existing e-mail protocols so that the address recognition process can be initiated. Thus, the user does not need to know any specific preset character sequences to be inserted before the symbol, since any arbitrary character input will now suffice. For example, a sample input string

18005551234.IPN from John Doe's business card is inserted in the format:

»· *

• <any character (s)> @ 18005551234.IPN.

The existing client software 358 will then follow the existing Internet address recognition protocols and send the address string to the client e-mail server 350, which will then forward it to the appropriate system database server 319 that supports IPNS logic 322. At some step before entering IPNS logic 322, the symbol and all preceding characters are generally separated from the domain name portion (here the IPNS sequence) according to existing e-mail protocols. For example, in the case of <any character (s)> @ 18005551234.IPN, only the IPNS sequence of 18005551234.IPN remains. The IPNS sequence is then converted by the server's IPNS logic 322 to a validly recognizable input addressing format and then mapped to an Internet protocol (IP) address of an e-mail server that supports the recipient's e-mail service (here John Doe) according to existing protocols. The IP address returns to the client e-mail server 350, which then uses this IP address to send the e-mail packets along with the user's address string to an IP address, typically belonging to the destination e-mail server 355. which supports the e-mail service for recipient.

At the destination e-mail server 355, the IPNS e-mail logic 356 maps the user's address string to the canonical e-mail address of the designated recipient. The destination e-mail server 355 then sends an e-mail message to the designated recipient.

Giant. 2.1 further illustrates the operation within the IPNS email logic 356. In step 213, incoming data 210 is recognized as an email address containing a valid address format and moved to the IPNS email logic 356. The valid address format may be either a phone number format, such as 18005551234.IPN, or a format using a common @ symbol such as <any character / characters> @ 18005551234.IPN. In this way, IPNS e-mail logic 356 can map addresses • ftp ftft ftft ftft ftft ftft ftftftft coming either from the new client software 366 or from the existing client software 358.

In step 214, the e-mail server maps the user's address string to the canonical e-mail address 214 to determine the e-mail address to which the message is to be sent. For example, the user-entered address string 18005551234.ipn or <any character / characters> @ 18005551234.lPN is mapped to jL Doe@someisp.com. where J-Doe@someisp.com is a working email account where John Doe receives incoming email.

In step 215, the e-mail message is sent to the found canonical e-mail address.

In an exemplary embodiment, the destination e-mail server 355 includes a database that includes a list of incoming e-mail addresses and their corresponding canonical e-mail addresses. The database is then interrogated by the IPNS email logic 356 at step 214 to map the incoming addresses to their corresponding canonical email addresses. When the canonical email address is found, proceed to step 215. wherein the email server initiates the process of sending the email to the canonical email address in accordance with DNS, SMTP, POP and / or relevant standards or protocols, if any ,. If a canonical e-mail address is not found, the destination e-mail server 355 notifies other relevant e-mail servers on the network of an incorrect address in accordance with DNS, SMTP, POP and / or relevant standards or protocols, if any.

Accordingly, one IPNS address, such as 1-800-555-1234.ipn, can be used to make a phone call, access the website, and send an email.

In one exemplary embodiment of the present invention, at least one domain in the domain name system is substantially (s) (444 444444 preferably at 100%) dedicated to service IPNS addresses. The dedicated domain name system is also arranged to ensure that IPNS addresses are usable for real standard communication with the designated party directly by telephone, for accessing the web page related to the designated recipient, and for sending an e-mail message to the designated recipient. The organizational feature also includes the electronic or conventional publication of user and administrative manuals of all possible permutations of allowed address strings and user parameters in the system. The user and administrative manual describes the composition of allowed address strings in the format of a phone number in a dedicated domain.

The dedicated domain is also sufficiently sophisticated to recognize and process IPNS addresses that may include additional human readable modifiers such as internal phone number indicators or a company trademark element at a defined location within an address string. 234-567-8900x321. Ipn, the connection or request for a web page will be directed to the telephone or web page of the person or department to which line 321 is located at the number of the organization or enterprise participating in the system of the present invention. Another example might be: 1-234-5678900 * Roger.lPN. This address string will route a connection or request to access a web page or e-mail to a person's phone, e-mail, or web page, or to a department to which the internal line assigned "Roger" at this number is assigned.

The address string can also be extended by adding any valid trademark of the phone number owner, which is represented by a phone-like string. For example, valid addresses that the system can recognize may be: 1-800-5551234.Mc.Donalds.ipn or McDonalds.1-800-555-1234.ipn.

• 9

The address string can also be extended by inserting dot-separated subdomains of one of the following types before or after a phone-like string:

(t) fax (.)

(.) pager (.) (,) cell (.) (,) message (.) (,) instant-message (.)

() chat (.)

ft. (.)

(.) gopher (.) (,) e-mail (.) / redundant but can be used / (Jwebsite (.) / redundant but can be used / etc)

Over time, it will be possible to use other dot-separated subdomains. For example, valid addresses recognized by the system may be: 1-234-5678900.fax.ipn or fax. 1-234 5676-8900.ipn. In this case, domain processing will indicate that the input data was a fax. In this case, domain processing alone will act as a router to correct the final determination of any communication or request for information.

In addition, the dedicated domain system handles IPNS addresses in accordance with a coded and programmed error correction algorithm that facilitates system usability. Processing includes introducing custom address processing utilities in a dedicated domain name server within that domain, introducing a custom email utility in the dedicated email server, and ensuring that the dedicated email server is available to the dedicated domain name system.

• · · 4 4 4 · · 44 444 4 «4444

The dedicated domain is also provided with appropriate administrative and technical services to ensure its proper functioning. Appropriate management of a dedicated domain includes, but is not limited to, setting up management software that allows a representative of that dedicated domain to collect, input, and store information from a subscriber with a new address. A database that contains a canonical e-mait address of a subscriber is used to map one or more repetitions of a telephone-like address string to a canonical email address and / or to a web page address selected by the subscriber. In this way, the dedicated domain representative or subscriber will be able to quickly change the relevant elements of the database. For example, an e-mail sent to a specific address string similar to a phone number may be redirected to another canonical e-mail address for a period of time or as a basic change to a subscriber profile.

Finally, domain representatives or subscribers are able to add or delete modifiers in the base IPNS address using the software, if any, such as when each case of an IPNS address with a different modifier must be mapped to a different email address.

It should be noted that the various embodiments of the present invention have been shown sometimes separately to simplify diagrams and the corresponding description of embodiments. Any method or system using one or more of the above embodiments is considered to be part of the claimed invention.

Other embodiments and advantages of the present invention will be apparent to those skilled in the art from consideration of the specification or operation of the invention described herein. It is expected that the description and examples will be considered as exemplary embodiments only, with the scope and inventive idea being determined by the following claims.

Claims (77)

1. A system for communicating via at least one communication medium comprising a plurality of input subsystems for receiving an address string, the address string having a valid format recognizable by these input subsystems and embedded in at least one communication application selected from a set of different types of communication applications , where the same address string can be validly entered for any selected communications application from this file. The system of claim 1, wherein the address string is associated with at least one recipient entity. The system of claim 2, wherein the input subsystem further comprises a recognition subsystem for recognizing an embedded address string having a different format from the format used by the selected communications application and a mapping subsystem for converting the different format to at least one format used by the selected communications application. The system of claim 1, wherein the system further comprises a selection subsystem for determining at least one communication medium based on the selected communication application and a communication subsystem for establishing address string based communication via the designated communication medium. System according to claim 4, characterized in that the communication medium is homogeneous and / or consists of a plurality of heterogeneous media. · * * * * * * * * * * * · · · · · · · · · · System according to claim 1, characterized in that the set of different communication applications comprises communication applications of the same type and / or of the same type, but with different formats. 7. The system of claim 3, wherein the mapping subsystem further comprises an interleaving subsystem for translating each address string component into a corresponding predetermined number, a segmenting subsystem for segmenting the translated components into at least one subgroup according to a predetermined segmenting format, arranging the segmented components into an output string with an order format different from the inserted address string, wherein the output string is in a predetermined new order format, and a partitioning subsystem for breaking the new order string into the corresponding valid address format. The system of claim 7, wherein the corresponding valid address format is used to establish communication with a location on the worldwide network (www). System according to claim 1, characterized in that the set of different communication applications comprises communication applications of the same type and / or of the same type, but with different formats. The system of claim 9, wherein the communication application is a specification of the location of the resource on the www. The system of claim 9, wherein the communication application is a telephone service. The system of claim 9, wherein the communication application is an electronic mail application. The system of claim 7, wherein the mapping system further comprises a transport subsystem for transmitting the inserted string 44 4 « 4 44 4 4 4 4 • • 4 • • 4 · 4 »4 4 44 «44 44 4444 to a matching subsystem based on the corresponding valid address format, the matching subsystem designed to accommodate an inline string of at least one valid email address, the valid email address being used to retransmit communication to the location with that valid email address. The system of claim 7, wherein the mapping subsystem further comprises a conversion subsystem for converting a valid address format to a valid email address format, wherein the valid email address format comprises a valid address format that is preceded by a symbol and at least one character. 15. A method of communicating via at least one communication medium, the method comprising receiving an address string having a telephone number format and embedded in at least one communication application selected from a set of different types of communication applications, wherein the same address string can be validly entered for any selected communications application from this file. 16. The method of claim 15, wherein the method further comprises determining at least one communication medium based on the selected communication application and establishing communication via the designated communication medium. Method according to claim 16, characterized in that the communication medium is homogeneous and / or consists of a plurality of heterogeneous media. Method according to claim 15, characterized in that the set of different communication applications comprises communication applications of the same type and / or of the same type, but with different formats. 19. The method of claim 18, wherein the communication application is a specification of the location of the resource on the www. φ φ · · · · · · φ φφ Φ · <Φ 20. The method of claim 18 wherein the communication application is a telephone service. 21. The method of claim 18 wherein the communication application is an electronic mail application. 22. The method of claim 15, wherein receiving the address string further comprises recognizing the inserted address string having a different format from the format used by the selected communications application and mapping the different format to at least one format used by the selected communications application. 23. The method of claim 22, wherein the mapping further comprises translating each component of the address string to a corresponding predetermined number, segmenting the translated components into at least one subgroup according to a predetermined segmentation format, rearranging the segmented components into an output string with an order format different from an inserted address string, wherein the output string is in a predetermined new order format, and breaking the new order string into the corresponding valid address format. 24. The method of claim 23, wherein the corresponding valid address format is an Internet website address format. 25. The method of claim 15, wherein the address string is associated with at least one recipient entity. 26. The method of claim 23, wherein the mapping further comprises transmitting the inserted string based on the corresponding valid address format, receiving the transmitted input string, and matching the inserted string to at least one valid e30 mail address, wherein the valid email address is used for retransfer communication to a location with this valid email address. The method of claim 23, wherein the mapping further comprises converting a valid address format to a valid email address format, wherein the valid email address format comprises a valid address format preceded by a symbol and at least one character. 28. A method of communicating via at least one communication medium, said method comprising receiving an address string embedded in a plurality of communication applications, wherein the same address string can be validly embedded for any selected communication application from said file. 29. The method of claim 28, wherein the method further comprises determining at least one communication medium based on the selected communication application and establishing communication via the designated communication medium. 30. The method of claim 28, wherein receiving the address string further comprises recognizing an inserted address string having a different format from the format used by the selected communications application and mapping the different format to at least one format used by the selected communications application. 31. The method of claim 30, wherein the mapping further comprises translating each component of the address string to a corresponding predetermined number, segmenting the translated components into at least one subgroup according to a predetermined segmentation format, rearranging the segmented components into an output string with an order format different from of the inserted address string, where this output string is • φ · * · • · φ · • · • · · · · · · · · · · · · In a predetermined new order format, and breaking the new order string into the corresponding valid address format. 32. The method of claim 31, wherein the corresponding valid address format is an Internet website address format. 33. The method of claim 31, wherein the corresponding valid address format is an Internet e-mail address format. 34. The method of claim 31, wherein the address string is associated with at least one recipient entity. 35. The method of claim 30, wherein the mapping further comprises transmitting the inserted string based on the corresponding valid address format, receiving the transmitted input string, and matching the inserted string to at least one valid email address, wherein the valid email address is used for retranslation. Communicate to a location with this valid email address. 36. The method of claim 30, wherein the mapping further comprises converting a valid address format to a valid email address format, wherein the valid email address format is a valid address format preceded by a symbol and at least one character. 37. A method for generating a valid Internet address for an Internet communication application, the method comprising receiving at least one insertion input string, distinguishing between valid and invalid components in the insertion string, and forming at least one valid Internet address for the Internet communication application from valid component. 38. The method of claim 37, wherein the valid component is a subset of an Internet address string for an Internet communication application. ♦ * «·· 39. The method of claim 37, wherein the insert string includes commands for accessing a specific location on the global network. 40. The method of claim 37, wherein the insert string includes commands for sending an electronic message to the specified e-mail address. 41. The method of claim 37, wherein the insert string comprises commands for establishing a telephone contact with a particular telephone number via the Internet or a conventional telephone line. 42. A system for generating a valid Internet address for an Internet communication application, the system comprising an input subsystem for receiving at least one input string, a processor subsystem for distinguishing between valid and invalid components in the input string, and a configuration subsystem for creating at least one. valid Internet addresses for Internet communication applications from valid components. 43. The system of claim 42, wherein the valid component is a subset of an Internet address string for an Internet communication application. 44. The system of claim 42, wherein the insert string includes commands for accessing a specific location on the global network. 45. The system of claim 42, wherein the insert string includes commands for sending an electronic message to the specified e-mail address. • · · * 46. The system of claim 42, wherein the insert string includes commands for establishing a telephone contact with a particular telephone number via the Internet or a conventional telephone line. 47. A method for converting an address string into a predetermined Internet address format, the method comprising receiving at least one inserted input address string, wherein the address string comprises a plurality of alphanumeric characters, rearranging the input string into an output string with a different order format from an inline address string, wherein the output string is in a predetermined Internet address format. 48. The method of claim 47, wherein the reordering further comprises segmenting the inserted string into at least one substring and sequentially rearranging said substrings based on a corresponding predetermined hierarchical format, wherein the format string is in a predetermined Internet address format. 49. The method of claim 45, wherein the segmentation comprises splitting the inserted string into substrings in a number field format in a telephone number. 50. A method for converting an embedded e-mail address into an Internet e-mail address format, the method comprising receiving at least one embedded e-mail address entry string, wherein the address string comprises a plurality of alphanumeric characters and converting the e-mail string into an output string , where the output string is in a predetermined email address format. • »00 0» 0 0 · 0 · 0 ·· 000 0 * 0000 51. The method of claim 50, wherein the conversion further comprises reordering the inserted string into an output string with an order format different from the inserted address string. 52. The method of claim 48, wherein the reordering further comprises segmenting the inserted string into at least one substring and sequentially rearranging said substrings based on a corresponding predetermined hierarchical format, wherein the format string is in a predetermined Internet email address format. 53. A method for operating domain name servers, the method comprising essentially allocating at least one domain name server to handle one or more lower level domain names, wherein each lower level domain name is represented by at least one string of numbers in a telephone number format . 54. The method of claim 53, wherein the method further comprises arranging domain name servers such that the number strings are valid and associate the default domain name with at least one domain name of the intended destination using at least one communication application, utilizing a processing utility addresses to process number strings into at least one format used by the at least one communications application and provide domain name management services to properly manage domain name servers. 55. The method of claim 53, wherein the at least one domain name server is a top-level domain name server. fc · fc * fcfc 56. The method of claim 54, wherein the address processing utility is adapted to specify the location of the resource at www. 57. The method of claim 54, wherein the address processing utility is a customized e-mail utility. 58. The method of claim 54, wherein the address processing utility is an adapted function of the telephone service, 59. The method of claim 54 wherein the communication application is a specification of the location of the resource on the www. 60. The method of claim 54, wherein the communication application is a telephone service. 61. The method of claim 54, wherein the communication application is an electronic mail application. 62. The method of claim 54, wherein the organization of the domain name server comprises providing a manual listing all permutations of a valid string of numbers. 63. The method of claim 62, wherein said manual is an end user manual. 64. The method of claim 62, wherein said manual is an administrative manual. 65. The method of claim 53, wherein the domain name server is operated by a telephone service provider. 66. A method for mapping an address string, the method comprising receiving an input valid address string having at least one component, wherein the component is a member of an alphanumeric file, mapping each component from the address string to a predetermined corresponding number, recognizing numerical categorical identifiers in mapped components and re-ordering these mapped components based on recognized numerical categorical identifiers according to a predetermined hierarchical format. 67. The method of claim 66, further comprising mapping each non-numeric portion of the address string component to a corresponding number or symbol associated in a format that is depicted on the telephone keypad buttons. 68. The method of claim 66, wherein the predetermined hierarchical format is a hierarchical format of a telephone system. 69. The method of claim 66, wherein the alphanumeric set includes all human and / or machine recognizable characters. 70. The method of claim 66, wherein the categorical identifier is a geographical identifier. 71. The method of claim 70, wherein the geographical identifier is a country telephone number. 72. An address string mapping system, the system comprising an input subsystem for receiving an input valid address string having at least one component, wherein the component is a member of an alphanumeric file, a mapping subsystem for mapping each component from an address string to a predetermined corresponding number , a recognition subsystem for recognizing numerical categorical identifiers in the mapped components, and a re-ordering subsystem for reassembling flfl flfl based on the recognized numerical categorical identifiers according to a predetermined hierarchical format 73. The system of claim 72, wherein the mapping subsystem maps each non-numeric portion of an address string component to a corresponding number or symbol associated in a format that is depicted on the telephone keypad buttons. 74. The system of claim 72 wherein the predetermined hierarchical format is a hierarchical format of a telephone system. 75. The system of claim 72, wherein the alphanumeric set includes all human and / or machine recognizable characters. 76. The system of claim 72, wherein the categorical identifier is a geographical identifier. 77. The system of claim 76, wherein the geographical identifier is a country telephone number.