HRP20010967A2 - Systems and methods for communicating across various communcation applications using single address strings - Google Patents

Description

Related patent applications

This patent application claims priority from the U.S. of preliminary applications: 1) serial number 60/137,137, entitled "Addressing systems for error correction for the Internet, telephone and other communication systems using a universal unique address sequence (one-address sequence), received on May 27, 1999; 2) serial number 60/138,927, entitled "Error Correcting Addressing Systems for Internet, Telephone, and Other Communications Systems Using a Single Address Array," received Jun. 11, 1999; and 3) Serial No. 60/153,426, entitled “Error Correcting Addressing Systems for Internet, Telephone, and Other Communications Systems Using a Unique Universal Address String,” filed Sep. 10, 1999. The text of each of those applications is incorporated herein by reference.

Field of invention

The present invention is directed to address strings used by various communication applications for communication.

Background of the invention

Nowadays, users of most communication applications such as telephones, electronic mail (e-mail) or Internet web pages are required to provide the communication application with input information about a previously determined address string in order to establish the desired communication link with the desired recipient. For example, a user of an e-mail application must enter an address string in the form of a predetermined e-mail address such as johndoe@address.com in order to send an e-mail message to a specific recipient.

An address string is generally assumed to be a sequence of components having alpha-numeric or other human and/or machine recognizable characters. Such address strings can generally be of any length or component type, but their exact configuration is usually predetermined by the service provider of a particular communication application. For example, in the case of a telephone, the address string used is a telephone number whose length and order of digits are often determined by the telephone service provider. In a similar way, in the case of Internet web pages, to access the desired Internet web page, the Internet user usually uses a previously determined unique address of the data source (URL-Uniform Resource Locator).

The use of some address strings, such as telephone numbers, to establish communication with another location via a communication medium is well known in the prior art. Recent technological progress, especially in computer networks and in the field of telecommunications, has resulted in the introduction of numerous new and/or different forms of communication. For example, e-mail communications, worldwide such as http://www.address.com/johndoe to access Doe's website and enter a telephone number into the telephone system to establish a telephone connection with Doe.

The requirements that some end user must know and correctly remember separate address strings are further complicated by the current use of domain names as web page addresses. A domain name, such as www.uspto.gov. is a form of address string that is generally designed to include human-recognizable characters (letters) and/or numbers to assist the user in searching for and/or recalling the correct address string. After entering into the communication application, the DNS system (Domain Name Server: computer server that matches the IP address with the domain name and vice versa; eg, hereinafter DNS) converts the domain name into a standard Internet Protocol (IP) numerical address such as 255.100. 1.0 for internal network use.

Using domain names as address strings is not without its drawbacks, however. Domain names have become longer over time, making them harder to remember. In addition, there is a general lack of standards to determine which spelling conventions should be followed when composing domain names, or even in which language they should appear. Since domain names are often registered for the purpose of legal recognition, the lack of such standards often leads to the need to register domain names in numerous and varied ways to accommodate the different linguistic and/or writing variants in each language in which the domain name will be used.

In addition, given that for practical reasons there is a relatively limited number of words with which to create a domain name, this has led to legal discrepancies and disputes over available websites, or other communication applications such as fax, represent some of such previously unavailable alternatives. a phone call.

The increase in the number of communication modes has, in any case, resulted in an undesired corresponding increase in both the number and types of address strings associated with each such form of communication. In addition, said technologies used to implement such various communication applications typically require the user to set an input address string that is largely unique (characteristic) to that technology in order to run the particular communication application and achieve the desired benefit thereof. Even communication applications of the same type but with different formats, such as e-mail applications from two different e-mail service providers, often require the use of different address strings. For example, a person who has e-mail boxes (accounts) with two or more e-mail service providers is only one recipient who will nevertheless have two or more associated e-mail addresses, usually in the form of one e-mail address for each service provider.

One problem with the current approach of assigning a unique string per user and per communication application is the creation of multiple address strings for a single recipient. For example, in attempting to establish a connection with a hypothetical John Doe recipient using electronic mail (e-mail), the World Wide Web, and telephone, some end user must often know and correctly remember the various address strings associated with each such application in order to establish communications with John Doe using a specific application. So, the user should correctly enter, for example, johndoe@address.com to send an e-mail to Doe, enter the Often long and difficult to remember URL string of trademarks and illegal cumulation of domain names in violation of Internet laws.

DNS is also limited in handling errors or variations in input domain names such as those caused by misspellings or address errors, such as inserting an underscore ( _ ) used to underline a word instead of a hyphen ( - ). These errors or variations often cause DNS to fail to recognize and/or resolve the address string incorrectly, resulting in an error connecting the user to the intended destination in a DNS-based system. In addition, the DNS system is largely limited to Internet web addresses and does not address the problem of multiple address strings for other communication applications such as electronic addresses (e-mails) or telephone numbers.

More recent attempts to solve the problem of multiple address strings have revolved around consolidating address strings using Unified Messaging Systems such as Microsoft's Exchange Server and MCI's Onebox.com messaging system. These attempts, however, were insufficient to solve the problem of a large number of address strings per user for several reasons. First, the messaging system is widely used to send messages via fax, voice mailbox, and so on. In any case, this does not allow direct calling of a certain person with a standard voice call as in the telephone system. Second, messaging systems are mainly designed for telephone services such as fax, voicemail, etc., and still do not address the multiple address string problem of other applications such as e-mail and URLs (unique data source addresses).

Therefore, the objective of the present invention is to address the following shortcomings of the current state of the art.

Objectives and Summary of the Invention

One object of the invention of the present invention is to provide systems for receiving valid address strings that can be used as input to a communications application selected from among various types of communications applications, wherein the same address string can be fully used for input to any communications application selected from that collection application.

A further object of the present invention is to provide means (procedures) for receiving an address string in telephone number format entered into at least one communication application selected from a collection of different types of communication applications, wherein the same address string can be used as input to any selected communication application from and collections.

Another object of the present invention is to provide systems and procedures for forming a valid Internet address for an Internet communication application by accepting as input at least one input string, for distinguishing between valid components and invalid components in the input string, and for forming at least one valid Internet address for the Internet communication application from valid components.

A further object of the present invention is to provide methods for converting an address string into a predetermined Internet or e-mail address format by accepting as input at least one input address string of alpha-numeric characters and reordering the input string into an output string with a different format order from the input address string, where the output string is in a predetermined format of an Internet address or email address based on the communication application used.

A further object of the present invention is to provide DNS operation procedures for dealing with one or more sub-levels of a domain name, each sub-level of a domain name being represented by at least one numeric or alphanumeric string in telephone number format.

Another goal of the present invention is to provide systems and procedures for mapping one address string into a previously determined corresponding number, recognizing numerical categorical identifiers in the mapped output form, and reordering the developed output based on the recognized numerical categorical identifiers into a previously determined hierarchical format.

Accordingly, the above and other objectives are achieved in the subject invention by providing an address string format and the application of associated systems to minimize the number of different address strings used for communication through various communication applications.

In the first embodiment, the subject invention is a system for communication 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 recognized by the input system and entered into at least one communication application selected from a collection of different communication applications, wherein the same address string can be entered for any communication application from the collection .

In another aspect of the first embodiment, the subject invention is a method for communication via at least one communication medium. The method includes receiving an address string having the form of a telephone number and entered into at least one communication application selected from a collection of different communication applications, wherein the same address string can be entered for any selected communication application from the collection.

In a further aspect of the first embodiment, the subject invention is a method for communication via at least one communication medium. This method includes receiving a single address string entered into at least two or more communication applications selected from a collection of different communication applications, wherein the same address entries are made for any selected communication application from the collection.

In another embodiment, the subject invention is a procedure for creating a valid Internet address for a communication application via the Internet. The method and system include accepting as input data at least one input string, distinguishing valid from invalid components of the entered string, and forming from valid components at least one valid Internet address for the Internet communication application.

In the third embodiment, the subject invention is a process for converting an address string into a previously determined form of an Internet address or an e-mail address. The method includes accepting as input at least one input address string, which address string includes multiple alpha-numeric characters, reordering the input string, and converting it to an output string with a format different from the input string, indicated by said output string being in a predetermined Internet address or email address format based on the communication application used.

In a fourth embodiment, the subject invention is a method for working with DNS. The process basically involves assigning at least one DNS to serve one or more sub-levels of a domain name, each sub-level of a domain name being represented by at least one numeric string in the form of a telephone number.

In the fifth embodiment, the subject invention is a method and system for mapping an address string. The method and system include accepting as input a valid address string with at least one component, wherein said component is a member of an alphanumeric set, mapping each component of said address string to a previously determined corresponding number, recognizing numeric categorical identifiers (tags) in the mapped components, and reordering mapped components in accordance with the previously determined hierarchical format.

In one exemplary embodiment, the subject invention includes, but is not limited to, an application in the form of a computer executable program (code), characteristic of the present invention, existing at the end user and/or on the server(s) within the substantially associated above DNS or e-mail server (server) level. The program works to achieve some or all of the aforementioned embodiments of the subject invention.

This summary is provided so that the nature of this invention may be quickly understood. The subject invention will be fully understood by following the following detailed description of its recommended embodiments and the accompanying drawings.

Brief description of the drawing

Without limiting this invention in any way, several examples of embodiments of the invention are described below in connection with the attached drawings. In the text of the specification, reference is made to the given figure numbers in order to better illustrate the operation of embodiments of the present invention being applied for. These embodiments should in no case be considered as the final number of possible different embodiments of the subject invention.

Figure 1.0 shows the general process by which the user enters requests into the input device in the form of an input string.

Figure 1.1 gives an example, from the prior art, with multiple different user requests entered into multiple different input devices using multiple different input array systems.

Figure 1.2 shows a sample of a business card that shows three different ways of contacting the holder (owner) of the business card.

Figure 1.3 shows an example of a business card on which the method of contacting the holder of the business card according to the present invention is shown.

Figure 1.4 provides an example of multiple different user requests being entered into multiple different input devices using a unique input string in accordance with the present invention.

Figure 3.0 shows various aspects of the subject invention applied to existing systems with a telephone and a World Wide Web program.

Figure 2.0 is a flow diagram showing more detailed modes of operation of the subject invention in a World Wide Web environment.

Figure 3.2 shows aspects of the subject invention applied to existing electronic mail systems.

Figure 2.1 is a flow diagram that shows in more detail how the subject invention works in an electronic mail environment.

Detailed performance description

The systems and procedures of the subject invention are mainly applied in order to reduce to a minimum the number of different address strings that the user enters for the purpose of communicating through various communication applications.

Following the drawings in more detail, Figure 1.0 shows the process by which the input data entered by the user is translated into a machine-processable form. As shown in Fig. 1, a user's step 100, such as a request to access a location on the World Wide Web (WWW), is entered as an input string 102 into an input device 101 such as a Web browser.

SI. 1.1 gives further examples of the general approach shown in si. 1.0. In more detail, you. 1.1 shows four different user steps 110-113 being entered into four different input devices using four input arrays of different systems. In example 110, the user step is a request to establish a telephone connection using a telephone number as an input string. In example 111, the user step is a request to access a WWW location using the previous WWW address string as an input string. In example 112, the user's step is a request to establish a correspondence connection via e-mail using the previous e-mail address string as an input string. In example 113, similar user steps are requests via other communication applications such as telefax, file transfer protocol, etc. using the corresponding previous access procedures as the input string for each communication application.

Figure 1.2 shows in the context of the business card 120, one problem related to the current approach that requires the use of multiple input strings for different systems. As shown in Fig. 1.2, John Doe represents a typical business card holder who can be contacted via three different communication applications or via telephone 121, World Wide Web 122 and e-mail 123. The requirement to enter several different input strings for each communication application requires that each of the three different ways to contact the owner of the business card must be indicated on the business card. The disadvantage associated with such an approach is that a user wishing to contact John Doe must enter a different address string for each communication application used. In addition, if the business card is not available to the user at some point, he has to remember the address strings to contact the owner of the business card, and the fact that he has to use three different address strings (one for each type of communication application) reduces the user's chance to remember each string correctly . This problem is especially emphasized in circumstances when the user has only one of the mentioned applications at his disposal. For example, a user might remember Doe's phone number, but not the email address that the user needs at some point to forward an important letter.

Figure 1.3 gives an example of the business card shown in Fig. 1.2 but which uses the new characteristics of the reported invention in minimizing the necessary input strings. As shown in the example, the use of only one input string 125 is sufficient to contact the owner of the business card using any of the three mentioned communication applications, resp. telephone, World Wide Web or e-mail.

Figure 1.4 further shows the characteristics of the invention as shown in the example of the business card from Figure 1.3. Specifically, Fig. 1.4 shows four different user steps 126-129 for contacting John Doe being entered into four different input devices but using only one input string to the system. In Example 126, the user's step is a request to establish a telephone connection with John Doe, using the obtained Doe's telephone number (here 18005551234IPN) as the input string. The suffix "IPN" can be entered as three additional digits each corresponding to the letters "I", "P" and "N" on a standard telephone keypad. In Example 127, the user's step is to request access to Doe's WWW location using an address string according to the invention protected herein as an input string. In Example 128, the user step is a request to establish a correspondence with John Doe via e-mail using the obtained e-mail address string as the input string. In Example 129, similar steps are required by other communication applications assumed to be within the scope of the claimed invention, such as fax, file transfer protocol, etc., using appropriate access procedures as input strings for each communication application.

Furthermore, the mode of operation of one embodiment of the subject invention is described in more detail, starting with Fig. 3.0. Figure 3.0 shows embodiments of the subject invention used in a telephone system or World Wide Web environment for ease of display.

As shown in Figure 3.0, the user chooses whether to contact John Doe via telephone or the World Wide Web.

When selecting the telephone system 320, the user enters an input string in the form of a telephone number into the telephone 321. To better illustrate the operation of the subject invention, the sample input string 18005551234IPN from John Doe's business card is used throughout the detailed description of the subject invention relating to Sl. 3.0. The user enters the initial digits by simply selecting the correct number on the telephone dial. The suffix "IPN" is entered as three additional digits 4, 7 and 6, each corresponding to the letters "I", "P" and "N" on a standard telephone keypad. The additional digits "476" do not affect the initial sequence as they are subsequently discarded as redundant digits in accordance with the telephone system protocols applicable to the telephone set 321, the telephone network 323 or some other set intended for such purposes. Standard telephone connection protocols are then followed to connect the user to the target telephone 325, in this case John Doe's telephone.

In the case of computer system selection 302, an input string that is in the form of a telephone number is entered by the user into an appropriate input location of the user's program that supports the desired communication application, such as a URL input box (unique data source address) on a WWW communication application.

Although some current Internet communication applications can recognize an input string that is in the form of a telephone number, they are currently limited to specific registered forms of the input string, with each name variation requiring a new registration. For example, a website selling flowers registered as 1-800-flowers would be recognized as different from 1800flowers which a user might mistakenly enter while trying to access the website and this could result in the user being denied connection to the desired destination. The present invention approaches solving this problem by applying an IPNS logic circuit 322 to convert an input string that is in the form of a telephone number into an Internet address input format that will be recognized as valid, while at the same time tolerating variations and errors in the input string. Details of the IPNS logic program 322 are discussed below in connection with Figure 2.0.

As shown in Figure 3.0, the IPNS logic 322 may reside either on the user side in the form of a user program 316 that supports the IPNS logic 322, or may be implemented on the server side such as the database server system layer 311, or both. parties, as shown in flow diagram 317. The database server system is typically a DNS (Domain Name Server) or similar system. The operation of DNS or similar systems is well known to those skilled in the art.

In one aspect of this embodiment, the user's address string is entered into the user's program 316 that supports IPNS logic 322. The user-side IPNS logic 322 then converts the entered address string into an Internet address input format that will be recognized as valid. The converted input is then sent over the Internet to the appropriate database server system 319 or 311 as shown by paths 318 or 317. The servers 319 or 311 then map the input string to an Internet Protocol (IP) address of the target computer or network device 307 following existing protocols and return IP address to the user's program 316. The user's program 316 then uses the IP address to direct the user to a target computer or network device 307 that supports the desired WWW location, in this case John Doe's website.

In another aspect of this embodiment, the user's address string is entered into the prior art program 308 that does not support the IPNS logic circuit 322. The existing user's program 308 then follows existing Internet address resolution protocols and forwards the address string to the appropriate database server system 311 which supported by IPNS logic circuit 322. The entered address string is then converted by IPNS logic circuit 322 at the server into an Internet address input format that will be recognized as valid, then mapped to an Internet Protocol (IP) address of the target computer or network device 307 respecting existing protocols . The IP address is then returned to the user's program 316. The user's program 316 will then use the IP address to direct the user to the desired target computer or network device 307 that supports the desired WWW location, in this case John Doe's website.

Referring now to Figure 2.0, the mode of operation of the IPNS logic circuit 322 is described in more detail. In the flow diagram, si. 2.0 shows the sequence of operations within the IPNS logic circuit 322.

In step 200, the address string entered by the user is entered into the IPNS logic circuit 322. In order to better illustrate the operation of this invention, in the following text the sample input string 1800JKL1234.IPN is used throughout the detailed description of the subject invention referring to Figure 2.

In step 203, the portion of the address string that describes the domain name for which the domain name server is responsible is removed. In this way, part of the IPNS sequence within the input address string is identified and distinguished from the rest of the entered input string. For example, in the case of the 1800JKL1234.IPN input string, the "IPN" is removed, leaving as output the identified and extracted IPNS sequence 1800JKL1234.

In step 204, the values of each of the characters within the IPNS sequence are converted to system or system administrator defined values. In one exemplary embodiment, the values are converted according to the following table which is mainly based on the telephone dial (keypad) configuration:

0 turns into 0

1 turns into 1

2abcABC turns into 2

3defDEF converts to 3

4ghiGHI turns into 4

5jklJKL turns into 5

6mnoMNO turns into 6

7pqrPQR turns into 7

8tuvTUV turns into 8

9wxyzWXYZ turns into 9

Any other characters not included in the conversion table such as hyphens and underscores are simply ignored. For example, the IPNS sequence 1800JKL1234 will be converted to 18005551234.

One advantage of the above features of the present invention is that variations and errors such as inserting an underscore instead of a hyphen to separate words are filtered out in the conversion process. For example, if the user entered 1-800-JKL_1234, it would still translate into the correct sequence 18005551234. That way, in a system based on the current type of DNS, which is often prone to errors, such variations and errors will not lead to to the point that DNS does not recognize and/or resolves the address string incorrectly and the user fails to connect to the desired destination.

In step 205, the order in which characters, fields, or combinations thereof are presented (generally from left to right) in the converted IPNS sequence is re-determined and changed to a new right-to-left configuration. For example, the converted IPNS sequence 18005551234 will be changed to 43215550081.

In phase 6, the reordered IPNS sequence is partitioned according to the variable segmentation format (division) of the managed data. The segmentation format is used to specify the number of fields within a sequence, and the length in characters of each field for the purpose of inserting periods (ie ".") between fields within the sequence. One example of a segmentation format is the 4-3-4 format, where the IPNS sequence number is separated from right to left, first in a group of four digits that are the most right, then the next three followed by the last four. A period is then inserted between each separate group. For example, an IPNS sequence reordered in 43215550081 will be split in a 4-3-4 format in4321.555.0081. Segmentation is also data-driven and recognizes numeric categorical identifiers such as country code or local area code, so if you enter IPNS sequences of a different format, such as those that follow the format of a foreign country's telephone number, a different segmentation format may be used. In the exemplary embodiment, the various segmentation formats are variable so that adjustments can be made in the formatting setup program as desired or as needed. In addition, the different segmentation formats are stored in the database so that the IPNS processor can find them again.

In step 207, the part of the address string that was removed in step 203, which described the domain name for which the name server is responsible, is now added back to the segmented IPNS sequence with the order changed. The result is the reconstruction of the input string into a format that is compatible with the appropriate communication technology and addressing system. For example, 4321.555.0081 is reconstructed to 4321.555.0081.ipn.

Following stage 207, the name server is enabled to process the output string 209 as if it were an original DNS query, in accordance with DNS protocols. If no different information is found for the string, then the name server should send to DNS data representing the new string as the formal name for the source domain being looked up, in addition to any resolution data belonging to the new DNS address.

It should be noted that the various stages and specific order of the foregoing operations are provided by way of example only, and any procedure using one or more of the disclosed routines that results in a string conforming to the desired output string format 209 is considered to be within the scope of the invention claimed and protected herein.

Figure 3.2 shows another embodiment of the subject invention used in the electronic mail (e-mail) environment. As shown, the user programs 366 and 358 are connected to the user's e-mail server 350 which is connected to an Internet address resolution system such as a database system server 319 or 311 using IPNS logic circuit 322 for the purpose of obtaining an Internet Protocol (IP) address. target e-mail server 355. The target e-mail server 355 receives and processes the e-mail message address using IPNS E-mail logic circuit 356 to convert the address to a formal e-mail address, and then forwards the e-mail message to the recipient via path 371.

In the following text, the version shown in Figure 3.2 will be processed in more detail. In order to better illustrate the operation of this invention, in the following text the sample input array 1800JKL12341PN is used throughout the detailed description of the part of the subject invention that refers to Figure 3.2 and later to Figure 2.1.

Beginning at step 348, the user, depending on the availability or selection of a new or existing program, enters an input string that is in the form of a telephone number into the appropriate slot of either the new access program 366 or the existing access program 358, both of which support the electronic mail communication application. and are connected to the e-mail server 350. For example, the user enters the address string " 1-800-555-1234.ipn" or "18005551234.ipn" in the field ("Send to:") of the e-mail program that is launched on a computer connected to the Internet. Existing e-mail protocols generally do not recognize a phone number as a valid input due to the absence of the "@" symbol in the string. The present invention approaches solving this problem by implementing one or more IPNS converter logic 351, IPNS logic 322, and IPNS e-mail logic 356. The IPNS logic 322 used for the electronic mail communication application is the same as the IPNS logic disclosed in FIG. 2.0 related to the World Wide Web implementation shown in Figure 3.0.

The details of the IPNS e-mail logic program 356 are further processed in relation to Figure 2.1.

In the embodiment shown as an example in Fig. 3.2 and following path 365, the IPNS logic circuit 322 is permanently placed in the access program 366 and converts the input string which is in the form of a telephone number directly into a validly recognizable Internet address input format. Due to the requirements of existing e-mail protocols, the converted input address must generally include the "@" symbol and at least one character or the access program will generally not accept the input to initiate the address resolution process. The IPNS converter logic 351 then converts the output from the IPNS logic 322 into a validly recognized Internet e-mail address input format by appending the "@" symbol and at least one character to the access program to initiate the address resolution process. However, unlike the previous systems, in the address string of the subject invention the symbol "@" and the accompanying sign are included only to give the telephone address string the appearance of a valid address in accordance with existing e-mail protocols, so that the address resolution process can be started. One advantage of the previous feature is that the user no longer has to enter an email address that has an "@" symbol.

The new access program 366 would then send the converted input to the access e-mail server 350. Because some access program applications accept the user's input address string without the "@" symbol and pass it to their access e-mail server 350 for address resolution, the access e-mail mail server 350 may also include IPNS conversion logic 351 for converting output from IPNS logic 322 to a validly recognized Internet e-mail address input format by appending the "@" symbol and at least one character. The access e-mail server 350 will then send the input over the Internet to the appropriate database system server 319 or 311, as shown in tracks 368 or 369. The database system server is typically a DNS (computer domain name server) or similar system, whose mode of operation is well known to those skilled in the art. The DNS server 319 or 311 would then map the input string to the Internet Protocol (IP) address of the e-mail server that supports e-mail service for the recipient (here, John Doe) according to existing protocols and return the IP address to the access program 366. The access e-mail server 350 then uses the IP address to forward the e-mail packet along with the user's address string to a destination IP address that generally belongs to the target e-mail server 355 that supports e-mail service for the recipient.

In another aspect of the embodiment of Figure 3.2, the user's address string is entered into an existing older generation access program 358 that does not support the IPNS logic circuit 322. Due to the requirements of existing email protocols, the user's entered address must include the "@" symbol and at least one character. or the access program will generally not accept the input to initiate the address resolution process. However, unlike the previous systems, in the address string from the subject invention the symbol "@" and the accompanying character are included only to give the telephone address string the appearance of a valid address in accordance with existing e-mail protocols, so that the address resolution process can be started . The user does not need to know any specific pre-determined order of characters to insert before the "@" symbol, as entering any character of choice would now generally be sufficient. For example, given as a sample the input string 18005551234.IPN from John Doe's business card will be entered in the form:

<optional character(s)>@18005551234.IPN.

The existing access program 358 will then follow the existing Internet address resolver and forward the address string to the access e-mail server 350 which will then forward it to the appropriate server 319 of the database system supporting the IPNS logic circuit 322. At some stage prior to entry into the IPNS logical circuit 322, the symbol "@" and all characters preceding it are generally separated from the part indicating the domain name (here the IPNS sequence) in accordance with existing e-mail protocols. For example, in the case of an input string given in the form <optional character(s)>@18005551234.IPN, only the IPNS sequence 18005551234.IPN will remain. The IPNS sequence is then converted by the IPNS logic circuit 322 on the server into a validly recognized Internet address input format, after which it is mapped in accordance with existing protocols to the Internet Protocol (IP) address of the e-mail server that supports e-mail service for the recipient (here, John Doe ). The IP address is returned to the access e-mail server 350 which then uses the IP address to forward the e-mail packet along with the user's address string to the destination IP address, which generally belongs to the target e-mail server 355 that supports e-mail service for the recipient.

At the target e-mail server 355, the IPNS logic circuit 356 maps the user's address string to the formal e-mail address of the intended recipient. The destination e-mail server 355 then forwards the e-mail message to the intended recipient.

Figure 2.1 further shows the flow of the process within the IPNS e-mail logic circuit 356. In step 213, the input data 210 is recognized as an e-mail message containing a valid address format, and is loaded into the IPNS e-mail logic circuit 356. The valid address format it can be either in the form of a telephone number such as 18005551234.IPN, or in a form that uses the common "@" symbol such as <optional character(s)>@18005551234.IPN. In this way, the IPNS e-mail logic circuit 356 can map addresses coming from either the new access program 366 or the older generation access program 358 .

In step 214, mapping of the user's address string to a formal e-mail address 214 is performed by the e-mail server computer in order to determine the e-mail address to which the message should be forwarded. For example, a user-entered address string 18005551234.ipn or <optional character(s)>@18005551234.IPN is mapped to L Doe@>someisp.com. where J-Doe@someisp.com is a valid online username or e-mail box where John Doe receives incoming e-mail.

In step 215, the e-mail message is forwarded to the found formal e-mail address.

In one exemplary embodiment, the destination computer e-mail server 355 includes a database containing a list of incoming e-mail addresses and their corresponding formal e-mail addresses. Next, the IPNS e-mail logic circuit 356 in step 214 sends a request to the database to map the incoming e-mail addresses to their corresponding formal e-mail address. If a formal e-mail address is found, step 215 continues where the email server begins the process of sending an e-mail message to the formal e-mail address in accordance with DNS, SMTP, POP, and/or appropriate applicable standards or protocols, if such exist. If a formal e-mail address is not found, the target e-mail server 355 sends an alert to other important servers on the network about the existence of an incorrect address in accordance with DNS, SMTP, POP, and/or the appropriate applicable standards or protocols, if any.

So, as stated above, a single IPNS address, such as 1-800-555-1234.ipn, can be used to make a phone call, access a website, and send an electronic message.

In an example of one embodiment of the subject invention, at least one domain within the domain name system is mainly (preferably 100%) allocated to serving IPNS addresses. The allocated domain name system is also organized to ensure that IPNS addresses are usable, in part for actual standard communication with the requested party directly by telephone; to access a website associated with the intended recipient; and for sending an e-mail message to the target recipient. The characteristic of this organization is that it also includes electronic or conventional publications of user and administrative manuals of all possible permutations of allowed address strings and parameters for use within the system. The user and administration manual describes the creation of allowed address strings in the form of a telephone number within an assigned domain.

The assigned domain is also sophisticated enough to recognize and process IPNS addresses that may contain additional human-readable modifiers such as telephone number extension indicators or an element to indicate a company's trademark at a specific position within the address string. For example, entering the extension "321" in the form 1-234-567-8900x321.ipn would direct a communication or request for a web page to the phone number or web page of the person or department designated to be on that 321 extension of said telephone number. number within the organization or company that subscribed to the system of the subject invention. Another example might be 1-234-567-8900*Roger.IPN. That address string would direct a communication or request to access a website or send electronic mail to the telephone, e-mail address or website of a particular person or department designated to be at the extension given as "Roger" at the specified number designated within the system.

The address string could also be extended by adding any trademark insignia owned by the phone number holder that is mapped to a string that looks like a phone number. For example, valid addresses that the system might recognize might be: 1-800-555-1234.McDonalds.ipn or McDonalds.1-800-555-1234.ipn.

The address string can -also be upgraded by including dot-separated sub-domains before or after a string that looks like a phone number of one of the following types:

iii) (.)fax(.)

iv) (.)pager(.)

v) (.)cell(.)

vi) (.)message(.)

vii) (.)instant-message(.)

viii) (.)chat(.)

ix) (.)ftp(.)

x) (.)gopher(.)

xi) (.)e-mail(.)(redundant, but can be used)

xii) (.)web-page(.)(redundant, but can be used)

xiii) etc.

Other dot-separated sub-domains may also be added over time. For example, valid addresses that the system might recognize could be: 1-234-567-8900.fax.ipn OR fax.1-234-567-8900.ipn. In this case, domain processing would indicate that the incoming data is a fax message. Domain processing itself would in this case act as a "router" to the correct final destination of any communication or request for information.

In addition, the system of assigned domains processes IPNS addresses in accordance with coded and programmed error correction algorithms that enable the use of the system. The processing includes, in part, the loading of common (customer) address processing utilities into the assigned domain name server computer within that domain; loading common e-mail utilities into the assigned domain name server computer; -te ensuring that the assigned e-mail server is accessible to the assigned domain name system.

The assigned domain is also equipped with appropriate administrative and technical services to ensure its proper functioning. Proper management of assigned domain names includes, but is not limited to, adjusting (installing) driver packages to enable the assigned domain representative to collect, enter, and store information obtained from subscribers with a new address. The database containing the subscriber's formal e-mail address is used to map one or more repetitions of the address string similar to the telephone number to the subscriber's chosen formal e-mail address and/or website. In this way, the representative of the assigned domain or the subscriber would have the possibility to quickly change the important elements of the database. For example, an e-mail message sent to a particular address string that has a form similar to a phone number can be redirected to a different e-mail address for a period of time or as a basic change to the subscriber profile.

Finally, the domain representative or subscribers would have the ability, using the program, to add or delete modifiers of the base IPNS address, if any, such as those that have a different modifier for each IPNS address subclass to map to a different formal email address.

It should be noted that the aforementioned different embodiments of the subject invention have been described separately for the sake of simplicity of the diagrams and corresponding specification descriptions. Any process or system utilizing one or more of the disclosed embodiments is deemed to be within the scope of the claimed and protected invention.

Other embodiments and advantages of the subject invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The specification and given embodiments are to be considered as examples only, while the true scope and spirit of this invention is indicated by the following claims.

Claims (77)

1. A system for communication via at least one communication medium, whereby the said system includes: multiple input sub-systems for receiving an address string, wherein the address string has a valid format recognized by said input sub-systems and which is entered into at least one communication application selected from a collection of different types of communication communications, indicated that the same address string can be validly entered for any communication selected from the specified collection. 2. System from Patent Claim 1, characterized in that said address string is associated with at least one recipient. 3. The system from Claim 1, wherein the input sub-system further includes: a subsystem for recognizing said input address string having a format different from that used by said selected communication application. a subsystem for converting said different format into at least one format used by said selected communication application. 4. The system from Patent Claim 1, wherein said system further includes: a selector subsystem for determining at least one communication medium based on the selected communication application; and a communication sub-system for establishing communication that is based on the address sequence of the sequence through the specified communication system. 5. System from Patent Claim 4, characterized in that said communication medium is a homogeneous medium and/or several heterogeneous media. 6. System from Patent Claim 1, characterized in that said collection of different communication applications includes communication applications of the same type and/or of the same type but different formats. 7. The system of Claim 3, wherein said mapping sub-system further includes: a translation (conversion) sub-system that translates each component of said address string into a corresponding predetermined number; a segmentation sub-system for separating said translated components into at least one sub-set in accordance with a previously determined separation (segmentation) format; a subsystem for reordering said separate components to produce an output array whose order is different from said input address array order, wherein said output array is in a predetermined reordered format; and a resolution subsystem that resolves the specified reordered string into the appropriate valid address format. 8. The system of Claim 7, characterized in that the corresponding valid address format is used to establish communication with the World Wide Web location. 9. System from Patent Claim 1, characterized in that said collection of different communication applications includes communication applications of the same type and/or of the same type but different formats. 10. The system from Patent Claim 9, characterized by the fact that the specified communication application is a world wide web locator (address) of the data source. 11. System from Patent Claim 9, characterized in that the specified communication application is a system of telephone services. 12. System from Patent Claim 9, characterized in that the specified communication application is an electronic mail application. 13. The system of Claim 7, wherein said mapping sub-system further includes: transmission subsystem for transferring the specified input string to the corresponding subsystem based on the specified corresponding valid address format, wherein the specified corresponding subsystem should associate the specified input string with at least one valid e-mail address, indicated that the specified e -e-mail address is used to communicate with the destination of the specified valid e-mail address. 14. The system of Claim 7, wherein said mapping subsystem further includes: a converter subsystem for converting said valid address format to a valid e-mail address format, wherein said valid e-mail address format consists of said valid address format preceded by an @ symbol and at least one character. 15. Procedure for communication via at least one communication medium, whereby the specified procedure includes: receiving one address string in the form of a telephone number and entered into at least one communication application selected from a collection of different types of communication applications, indicated that the same address string can be validly entered for any communication application from said collection. 16. The procedure from Patent Claim 15, wherein the said procedure further includes: determining at least one communication medium based on the selected communication application; and establishment of communication through the specified communication medium. 17. The method from Patent Claim 16, characterized in that said communication medium is a homogeneous medium and/or several heterogeneous media. 18. System from Patent Claim 15, characterized in that said collection of different communication applications includes communication applications of the same type and/or of the same type but different formats. 19. The system from Patent Claim 18, characterized by the fact that the specified communication application is a world wide web locator (address) of the data source. 20. System from Patent Claim 18, characterized in that said communication application is a system of telephone services. 21. System from Patent Claim 18, characterized in that said communication application is an electronic mail application. 22. The system of Claim 15, wherein said receiving of the address string further includes: recognizing said input address string having a format different from that used by said selected communication application; and mapping said different format to at least one format used by said selected communication application. 23. The system from Patent Claim 22, wherein said mapping further includes: translating (converting) each component of the specified address string into a corresponding previously determined number; separation (segmentation) of said translated components into at least one subset in accordance with a previously determined separation (segmentation) format; reassembly in a changed order of the specified separated components into an output array whose order is different from the order of the specified input address array, indicated by the fact that is the specified output string in the pre-specified permuted format; and parsing the specified reordered string into the appropriate valid address format. 24. The method from Patent Claim 23, characterized in that the specified corresponding valid address format corresponds to the address format of the Internet web page. 25. The method from Patent Claim 15, characterized in that the address string is associated with at least one recipient. 26. The system from Patent Claim 23, wherein said mapping further includes: transmitting said input string based on said respective valid address format; and receiving said transmitted input string and associating said input string with at least one valid e-mail address, wherein said e-mail address is used to communicate with the destination of said valid e-mail address. 27. The system from Patent Claim 23, wherein said mapping further includes: converting the specified valid address format into a valid e-mail address format, characterized in that the specified valid e-mail address format consists of the specified valid address format preceded by the @ symbol and at least one character. 28. Procedure for communication via at least one communication medium, whereby the specified procedure includes: receiving a single address string in multiple communication applications selected from a collection of different types of communication applications, provided that the same address string can be validly entered for any communication application from said collection. 29. The procedure from Patent Claim 28, wherein said procedure further includes: determining at least one communication medium based on the selected communication application; and establishment of communication through the specified communication medium. 30. The system of Patent Claim 28, wherein said receiving of the address string further includes: recognizing said input address string having a format different from that used by said selected communication application; and mapping said different format to at least one format used by said selected communication application. 31. The system from Patent Claim 30, wherein said mapping further includes: translating (converting) each component of the specified address string into a corresponding previously determined number; separation (segmentation) of said translated components into at least one subset in accordance with a previously determined separation (segmentation) format; reassembling in a changed order the said separated components into an output string whose order is different from the order of the said input address string, indicated by the fact that the said output string is in the format of a previously determined changed order; and parsing the specified reordered string into the appropriate valid address format. 32. The method from Patent Claim 31, characterized in that the specified corresponding valid address format corresponds to the address format of the Internet web page. 33. The method from Patent Claim 31, characterized in that the specified corresponding valid address format corresponds to the address format of Internet e-mail. 34. The method from Patent Claim 31, characterized in that said address string is associated with at least one recipient. 35. The system from Patent Claim 30, wherein said mapping further includes: transmitting said input string based on said respective valid address format; and receiving said transmitted input string and associating said input string with at least one valid e-mail address, indicated that said e-mail address is used to communicate with the destination of said valid e-mail address. 36. The system from Patent Claim 30, wherein said mapping further includes: converting said valid address format into a valid e-mail address format, characterized in that said valid e-mail address format consists of said valid address format preceded by the @ symbol and at least one character. 37. Procedure for creating a valid Internet address for an Internet communication application, whereby the specified procedure includes: receiving as input at least one input array; distinguishing between valid components and invalid components in said input string; and forming at least one valid Internet address for the specified Internet communication application from the specified valid components. 38. The method from Patent Claim 37, characterized in that the specified valid component represents a sub-string of one Internet address for the specified Internet communication application. 39. The method of Claim 37, characterized in that said input string includes commands to access a specified location on the world wide web. 40. The method from Patent Claim 37, characterized in that said input string includes commands for sending an electronic message to a specified e-mail address. 41. The method from Patent Claim 37, characterized in that said input string includes commands for establishing telephone contact with a specified telephone number via the Internet or a conventional telephone line. 42. A system for creating a valid Internet address for an Internet communication application, whereby the said system includes: an input subsystem for receiving as input at least one input array; a processing subsystem for determining the difference between valid and invalid components in said input array; and configuration subsystem for forming from valid components at least one valid Internet address for the specified Internet communication application. 43. The system from Patent Claim 42, characterized in that the specified valid address is a subset of the string of one Internet address for the specified Internet communication application. 44. The system of Claim 42, wherein said input string includes commands to access a specified location on the world wide web. 45. The system of Patent Claim 42, characterized in that said input string includes commands for sending an electronic message to a specified electronic mail address. 46. The system from Patent Claim 42, characterized in that said input sequence includes commands for establishing a telephone contact with a specified telephone number via the Internet or a conventional telephone line. 47. The procedure for converting an address string into a previously determined Internet address format, wherein the following procedure includes: receiving as input at least one input address string, wherein said address string includes a plurality of alphanumeric characters; and determining the reordering of the specified input string and forming it into an output string with an order format different from the order of the specified input address string, indicated by the fact that the specified output string is in a previously determined Internet address format. 48. The system from Patent Claim 47, wherein the specified determination of the new order further includes: separating (segmenting) said input string into at least one subset of the string; reassembling in a reordered manner said subsets based on a corresponding predetermined hierarchical format, wherein said array is in a predetermined Internet address format. 49. The method of Patent Claim 45, characterized in that said segmentation includes splitting said input string into subsets of the string in the format of numeric fields in the telephone number. 50. The procedure for converting an incoming e-mail address into the Internet e-mail address format, wherein said procedure includes: receiving as input at least one input email address string, wherein said address string includes multiple alpha-numeric characters; and converting said input string into an output string, indicated by the fact that the output string is in a previously determined electronic mail address format. 51. The procedure from Patent Claim 50, wherein said conversion further includes: determining the reordering of said input array and shaping it into an output array with an order format different from the order of said input address array. 52. The procedure from Patent Claim 48, whereby the specified determination of the new order further includes: separating (segmenting) said input string into at least one subset of the string; and reassembling in a reordered manner said subsets based on a corresponding predetermined hierarchical format, wherein said array is in a predetermined Internet address format. 53. A process for operating a domain name server computer, wherein said process includes: assigning substantially at least one domain name server to handle one or more sub-levels of the domain name, wherein each said sub-level of the domain name is represented by at least one sequence of numbers in the form of a telephone number. 54. The procedure from Patent Claim 53, where I state the procedure further includes: arranging said domain name servers to ensure that said number sequences are valid and to associate the source domain name with at least one target destination domain name via at least one communication application; providing administrative services for said domain name to properly manage said domain name servers. 55. The method from Patent Claim 53, characterized in that at least one specified domain name server is a top-level domain name server. 56. The method of Patent Claim 54, characterized in that said address processing utility is a common world wide web unique data source address. 57. The method of Patent Claim 54, characterized in that said address processing utility is a common electronic mail utility. 58. The method of Patent Claim 54, characterized in that said address processing utility is a common telephone service system. 59. The procedure from Patent Claim 54, characterized in that the specified communication application is a unique world wide web address of the data source. 60. The method from Patent Claim 54, characterized in that the specified communication application is a system of telephone services. 61. The method from Patent Claim 54, characterized in that said communication application is an electronic mail application. 62. The method of Patent Claim 54, characterized in that said organization of said domain name server includes a manual containing a specification of all permutations of said valid sequence of numbers. 63. The procedure from Patent Claim 62, indicated by the fact that the mentioned manual means a manual for the end user. 64. The procedure from Patent Claim 62, indicated by the fact that the mentioned manual means an administrative manual. 65. The method from Patent Claim 53, characterized in that said domain name server is managed by a telephone service provider. 66. A method for mapping an address string, which method includes: receiving as input at least one input address string, wherein said address string includes a plurality of alphanumeric characters; mapping each of said components of said address string to a previously determined corresponding number; recognition of numerical categorical identifiers in said mapped components; and determination of the new order of the listed mapped components based on the recognized numerical categorical ones identifiers in accordance with the previously determined hierarchical format. 67. The procedure from Patent Claim 66, wherein said mapping further includes: mapping the non-numeric portion of said component of said address string to a corresponding number or symbol grouped in the format represented on the telephone dial keys. 68. The method from Patent Claim 66, characterized in that the previously determined hierarchical format indicates the hierarchical format of the telephone system. 69. The method from Patent Claim 66, characterized in that the specified alpha-numeric set includes all characters recognizable by man and/or machine. 70. The method from Patent Claim 66, characterized in that the specified categorical identifier is a geographical identifier. 71. The procedure from Patent Claim 70, characterized by the fact that the specified geographical identifier is the country's characteristic telephone area code. 72. An address string mapping system, wherein said system includes: an input subsystem for receiving as input a valid address string having at least one component, said component being a member of an alpha-numeric set; a subsystem for mapping each said component of said address string to a predetermined corresponding number; a subsystem for recognizing numerical categorical identifiers in said mapped components; and a subsystem for reordering said mapped components based on recognized numerical categorical identifiers in accordance with a predetermined hierarchical format. 73. The system of claim 72, wherein said mapping subsystem maps each non-numeric portion of said component of said address string to a corresponding number or symbol grouped in a format as represented on telephone dial keys. 74. The system from Patent Claim 72, characterized in that the previously determined hierarchical format indicates the hierarchical format of the telephone system. 75. System from Patent Claim 72, characterized in that said alpha-numeric set includes all human and/or machine recognizable characters. 76. System from Patent Claim 72, characterized in that the specified categorical identifier is a geographic identifier. 77. The system from Patent Claim 76, characterized in that the specified geographical identifier is the country's characteristic telephone area code.