BG106247A - Communication systems and methods by different communication applications employing addressing string formats - Google Patents

Abstract

The invention relates to systems and methods for providing addressing string formats associated system implementations to minimize the number of different addressing strings used for communication across different communication applications. The systems and the method receive a valid address string that can be inputted into a communication application, selected from a collection of communication applications wherein the same address string can be inputted for any selected communication application. 77 claims, 3 figures

Description

TECHNICAL FIELD

The present invention generally relates to 25 address sequences of data (strings) used by various communication applications for communication.

BACKGROUND OF THE INVENTION

Currently, users of most communications applications, such as telephone, email (email) or Internet sites (pages) 5 need to enter a predefined address sequence of data into a communication application to establish the desired communication with the intended recipients. For example, an email application user must enter an address sequence in the form of 10 predefined email (such as johdoe@address.com) to send an email to the recipient.

The address string is generally intended to be a 15 sequence of components with alpha-numeric or other human-recognizable and / or machine-recognizable characters. Such address sequences can typically be of any length or component type, but their exact configurations are usually predefined by 20 service providers of the communication application. For example, in the case of a telephone, the address string used is a telephone number whose length and digital sequence are often established by the telephone service provider. Similarly, in the case of an Internet25 address, the predefined Uniform Resource Locator (URL) is typically used by the Internet user to access the desired network address.

The use of some address sequences (strings), such as telephone numbers, to establish communication with another location through a communication environment is widely known in the art. But the latest technological advances, especially in the computer network and telecommunications fields, are the result of the introduction of a number of new and / or different forms of communication. For example, communication using e-mail, web pages (addresses), or other 10 communications application such as fax are among those previously unavailable alternatives to telephone calling.

However, the increase in communication paths is reflected in an unwanted corresponding increase in the number and 15 types of address strings associated with each such form of communication. In addition, the underlying technologies used to implement such diverse communications applications typically require the user to introduce an address string that is completely unique to the technology 20 in order to function and derive the desired advantage from the communication application. Even communications applications of the same type, but with different formats, such as e-mail applications through two different e-mail service providers, often require 25 different strings to be used. For example, an entity that has e-mail accounts (accounts) with two or more e-mail service providers is the only receiving entity, which will nevertheless have two or more associated e-mail addresses for each service provider.

One problem with the existing approach of assigning a single address string to a user of a communication application is the generation of multiple address strings for a single recipient (subscriber). For example, when attempting to communicate with a hypothetical John Doe recipient who has an e-mail, web page, and telephone, the end user must often know and correctly remember the distinctive address strings associated with each such application to identify communication with John Doe using this application. Thus, the user must correctly type eg johndoe@address.com/johndoe in order to send Doe an email, 15 enter an often long and difficult to remember URL string such as http.7 / www.address.com / johndoe to access the Doe World Wide Web Page and enter a phone number into a telephone system to establish telephone communication with Doe.

The requirement for the end user to know and remember correctly the individual address strings is further annoying than the use of prior art domain names as addresses on 25 pages of the World Wide Web. A domain name, such as www.uspto.gov, is a form of address string that is generally intended to include human-readable characters and / or numbers to help the user find and recall the correct address string. Once implemented in the communication application, the Domain Name Server (DNS) system converts the domain name to a standard digital address according to Internet Protocol (IP), such as 255.100.1.0 for use on the internal network.

However, implementing domain names as address strings is not without its drawbacks. Domain names have evolved over time, making them harder to remember. In addition, there are a total of 10 shortcomings in standards regarding spelling conventions to be followed when compiling a domain name or even in what language they appear. Because domain names are often registered for legal recognition, such a lack of standards often makes it necessary to register a domain name in a number of ways to cover the different languages and / or spelling changes in each language in which the domain name will be used.

In addition, since there are 20 relatively limited number of words to create a domain name for practical purposes, legal units such as a trademark are discussed, followed by the illegal accumulation of domain names in violation of cyberspace laws.

DNS is also restricted in processing errors or variations in domain name input, such as those caused by misspellings or errors, such as entering a underscore instead of a dash in addresses.

These errors or variations often cause the DNS to be unable to recognize and / or mis-analyze the address string, which causes the user to fail to connect to the required location on the DNS-based system. Additionally, the DNS-based system 5 is very limited to Internet addresses and does not address the issue of multiple address strings for other communications applications such as e-mail and telephone numbers.

Recent attempts to troubleshoot some address strings revolve around combining address strings using Unified Messaging Systems, such as Microsoft's Exchange Server and MCl's Onebox.com delivery system. However, these attempts are far from solving the problem of multiple address strings for a user for various reasons. First, the approach of the message system revolves around sending a message via fax, voice box, etc. However, this does not allow direct calling and 20 person-to-person calls, as with a standard voice call on a telephone system. Second, messaging systems are primarily designed to function as a telephone service, such as a fax, voice box, etc. and have yet to address the problem of the multiple address strings of 25 other applications such as email and URLs.

SUMMARY OF THE INVENTION

Accordingly, it is an object of the present invention to address the disadvantages of the prior art.

It is an object of the present invention to provide systems for receiving a valid 5-data address string (string) that can be entered into a communication application selected from a collection of different types of communication applications, wherein the same address string can be validly entered for each selected communication application from this collection.

It is another object of the present invention to provide methods for obtaining an address string in the format of a telephone number introduced into at least one communication application selected from a collection of different types of 15 communication applications, wherein the same address string can be validly entered for each selected communication application from the collection.

It is also an object of the present invention to provide methods for obtaining an address string introduced into two or more communication applications selected from a collection of different types of communication applications, wherein the same address string may be validly introduced for any of the communication applications of this collection.

Yet another object of the present invention is to provide systems and methods for generating a valid Internet communication application web address by receiving as input information at least one input string distinguishing between valid components and invalid components in the input string and forming at least one valid internet address for internet-

communication application of valid components.

It is another object of the present invention to provide methods for converting an address string to a predetermined internet or e-mail address format by receiving as input information at least 10 one entered alphanumeric address string and re-alternating the input string to an output string a string in a format different in sequence from the address string introduced, wherein the outgoing string is in a predetermined format for an Internet or email address based on the 15 communes used cationic application.

It is also an object of the present invention to provide methods for managing domain name servers essentially by transferring a server for one domain name 20 to serve one or more domain names at a sublevel (sub), wherein each of the sub domain names is represented by at least one digital or alpha-numeric string in the form of a telephone number.

It is another object of the present invention to provide systems and methods for converting an address string to a predetermined corresponding number, recognizing digital end identifiers in output information after converting, and rearranging the converted output information based on established digital end identifiers for a predetermined hierarchical format .

In accordance with these and other objects, the present invention provides for address string formats and associate system implementations to minimize the number of different address strings used to communicate through different communication 10 applications.

In a first embodiment, the present invention is a system for communicating through at least one communication medium. The system includes an incoming slave system 15 (subsystem) for receiving the address string, the address string being a valid format recognized by the incoming subsystem and introduced into at least one communication application selected from a collection of different communication applications, wherein the same address string 20 may be introduced for each selected communication application from the collection.

In another aspect of the first embodiment, the present invention is a method of communication through at least one 25 communication medium. The method involves accepting an address string in the form of a telephone number and entering it into at least one communication application selected by a collection of communication applications, wherein the same address string can be entered for any selected communication application from the collection.

In yet another aspect of the first embodiment, the present invention is a method of communicating through at least 5 one communication medium. The method involves receiving an address string introduced into two or more communication applications selected from a collection of different communication applications, wherein the same address string is introduced for each selected communication application 10 of the collection.

In a second embodiment, the present invention is a method and system for generating a valid Internet address for a communication application for the Internet. The method and system 15 include accepting as input the at least one input string distinguishing between valid components and invalid components in the input string and forming at least one valid Internet communication application address from the valid components.

In the third application, the present invention is a method of converting an address string to a predetermined format for an Internet address or email address. The method involves accepting as input the at least one entered address string 25, the address string including a plurality of alphanumeric characters, rearranging the input string into an output string in a format different from that of the entered address string, wherein the output string is predetermined Internet format or email address based on the communication application used.

In a fourth embodiment, the present invention is a method for managing domain name servers. The method essentially involves assigning at least one domain name server to serve one or more sub-domain names, each sub-domain name being represented by at least one string of digits in a telephone number format.

© 10

In a fifth embodiment, the present invention is a method and system for organizing an address string. The method and system include accepting as valid input a valid address string with at least one component, wherein the component is a 15 element alpha-numeric series, converting each of the address string components to a predetermined corresponding digit, recognizing digital end identifiers in the converted components and © rearrange component conversions based on 20 established end identifiers according to a predefined hierarchical format.

In one embodiment, the present invention includes, but is not limited to, implementation in the form of a 25 computer-specific executable software code introduced into the end user and / or server (s) within the domain name or email server specified essentially to the top level. The software acts to accomplish some or all of the foregoing embodiments of the present invention.

This summary is intended to be readily understood by the invention. A more complete picture of the invention can be achieved by referring to the following detailed description of its preferred embodiment and the drawings.

EXPLANATIONS OF THE FIGURES Attached

Below, without limitation of the invention, a number of exemplary embodiments are described in any way with reference to the accompanying drawings. The figures provided herein are mentioned in the description to better illustrate the functions of the exemplary embodiments of the claimed invention. Accordingly, they are not intended to be a comprehensive list of the various embodiments of the present invention.

FIG. 1.0 illustrates a common method whereby a user enters requests into an input device in the form of a 20 input string;

FIG. 1.1 shows an example of the prior art of multiple different user requests that are introduced into composite input devices using a multiple different input string system;

FIG. 1.2 illustrates a business card template showing three separate ways according to the prior art of the business card holder connection technique;

FIG. 1.3 illustrates an example of a business card showing ι i i

I

a method of contacting the business card holder according to the claimed invention;

FIG. 1.4 shows an example of multiple different user requests that are entered into constituent different 5 input devices using the single input string system of the claimed invention;

FIG. 3.0 illustrates aspects of the claimed invention as being realized according to the prior art systems having a telephone and 10 worldwide network;

FIG. 2.0 is a flowchart illustrating in greater detail the actions of the claimed invention in a worldwide network environment;

FIG. 3.2 illustrates aspects of the claimed 15 invention as implemented for prior art systems by electronic mail;

FIG. 2.1 is a flowchart illustrating in greater detail the actions of the claimed invention in an email environment.

EXAMPLES FOR THE IMPLEMENTATION OF THE INVENTION

The systems and methods of the present invention are, in principle, implemented to minimize the number of different address strings introduced by 25 users for communication through various communication applications.

Referring in particular to the drawings of FIG. 1.0 illustrates a method by which user inputs are converted into machine-friendly form. As shown in FIG. 1, user impact 100, such as a World Wide Web Access Request (WWW), is introduced into an input device 101, such as a 5 browser (search engine), in the form of an input string 102.

FIG. 1.1 gives further examples of the general approach illustrated in FIG. 1.0. In particular, FIG. 1.1 illustrates four different user effects 110-113, which are introduced 10 into four different input devices using four different input string systems. In Example 110, user impact is a request for a telephone connection that uses a telephone number as an input string. In Example 111, user impact is a request for access to a site in WWW 15 that uses a WWW address string according to prior art as an input string. In Example 112, user impact is a request for email correspondence that uses prior art email strings according to prior art as an inbound 20 string. In Example 113, similar user effects are requests through other communication applications such as fax, File Transfer Protocol, etc., using appropriate prior art access methods such as input string for 25 each communication application.

FIG. 1.2 illustrates in the context of business card 120 a problem related to the prior art approach to the need to use a multiple different input string system. As shown in FIG. 1.2, John Doe is introduced as a typical business card holder that can be reached through three different communication applications on 5 phones 121, the worldwide network 122, and email 123. The requirement to enter multiple different input string systems for each communication application determines that the business card shows each of the three different ways of contacting the card holder. The disadvantage associated with such a 10 approach is that a user who wants to contact John

Doe, must introduce a different address string for each communication application used. Additionally, if the business card becomes inaccessible to the user, the user will typically have to access the memory when re-calling the address strings to connect to the user's business card and must use three different address strings (one for each type of communication application), which Reduces the chances of the user to make every correct call. This problem becomes especially acute in 20 circumstances, when only one form of the listed communication applications is accessible to the user. For example, a user may be able to redial Doe's phone number, but not the email address that may require the user to send an important 25 conversations.

FIG. 1.3 illustrates an example of a business map shown in FIG. 1.2 but employing new features of the claimed invention to minimize the number of input strings required. As illustrated in the example, using only one input string 125 is sufficient for the business card holder to be connected using any of the three listed 5 communications applications for telephone, worldwide network or email.

FIG. 1.4 further shows the features of the claimed invention as illustrated in Example 10 for the business map of FIG. 1.3. In particular, FIG. 1.4 illustrates four different user effects 126-129 for connecting John Doe, which are introduced using only one input string system. In Example 126, consumer impact is a request for a telephone connection to the 15 John Doe telephone number (here 18005551234IPN) as an input string. "IPN" is a suffix that can be entered as three additional digits 4, 7 and 6, respectively corresponding to the three letters "I", "P" and "N" of a standard telephone keypad. In Example 127 20, a user action is a request to access the Doe WWW page using the claimed string of the claimed invention as an input string. In Example 128, a user action is a request for an email conversation with John Doe using the email address provided to Doe 25 as an input string. In Example 129, such user actions are requests through other communication applications intended to be within the scope of the claimed invention, such as fax, File Transfer Protocol, and the like. When using appropriate access methods as an input string for any communication application.

The actions of an embodiment of the invention are now disclosed in greater detail starting with FIG. 3.0. 5 FIG. 3.0 illustrates embodiments of the present invention that have been used for simplicity of image in a telephone system or in a worldwide network environment.

As shown in FIG. 3.0 The user chooses whether to 10 contact John Doe via phone or world class.

When selecting telephone system 320, the user enters an input string in the form of a telephone number in telephone 321. For better demonstration, the actions of the exemplary input string according to the invention 15 18005551234IPN from the John Doe business card are used throughout the exemplary embodiment of the present the invention of FIG. 3.0. The user enters the initial digits by simply selecting the correct number from the telephone keypad. The suffix "IPN" is entered 20 as three additional digits 4, 7 and 6, respectively, corresponding to the letters "I", "P" and "N" on a standard telephone keypad. The additional numbers "467" do not affect the initial string, as they are subsequently abandoned as unnecessary numbers according to the protocols for the 25 telephone system implemented in the telephone 321, the telephone network 323 or any other means intended for this purpose. The standard telephone connection protocols are then followed to connect the user to the intended 325 telephone, here John Doe's telephone.

When selecting the computer system 302, the user enters the input string, which is in the form of a telephone number, into the appropriate input location of the 5 user software supporting the desired communication application, such as the Uniform Resource Locator input box of the WWW communication application.

Currently, although some prior art communications applications 10 may recognize an input string, which is in the form of a telephone number, they are limited to a specifically registered input string format with any change in name required for new registration. For example, a 15 flower sales website registered as 1-800flowers would be recognized as different from 1800flowers that the user may have mistakenly entered while trying to reach the website and as a result fail the user to connect to the intended The present invention addresses this problem by implementing IPNS logic 322 to convert an input string, which is in the form of a telephone number, into a valid identifiable input format for Internet addressing, such as allowed variations and errors introduced 25 string. Details of the IPNS logic 322 software are further discussed in connection with FIG. 2.0 below.

As illustrated in FIG. 3.0 IPNS logic 322 may be implemented or as a user end in the form of

client software 316 that supports IPNS logic 322, or it can be implemented as a server end, such as a system database at a server level 311, or both, as illustrated by process 317. A system database server is usually a domain name server (DNS) or similar system.

DNS domain operations or a similar system are widely known to those skilled in the art.

In one aspect of this embodiment, the user address string is introduced into the user software 316, which supports IPNS logic 322. The entered address string is then converted through user IPNS logic 322 to the user end in a valid recognizable internet addressing format. The converted input data is then sent over the Internet to a suitable system database server 319 or 311, as shown by circuits 318 or 317. The server 319 or 311 would sequentially convert the input string to an Internet Protocol (IP) address of the intended computer or network device 307, 20 following existing protocols, and returning the IP address to the user software 316. The user software would then use the IP address to divert the user to the target computer or network device 307 targeted for access. zhasht desired WWW-place here page of John Doe.

In another aspect of this embodiment, the user's address string is introduced into software 308 according to prior art which does not support

IPNS logic 322. Existing custom software

308 would then trace the existing resolving Internet address protocols and forward the address string to a suitable system database server 311 that supports IPNS logic 322. Then the entered address string 5 is converted from IPNS logic 322 to the server into a valid Internet address input format, which is then converted to Internet Protocol (IP) for the address of the computer or network device 307 you are looking for, following existing protocols. The IP address is then returned to the user software 10 316. The consumer software 316 would then use the IP address to direct the user to a searchable computer or network device 307 that supports the desired WWW site, in this case the Doe page.

Referring in particular to FIG. 2.0 now features of IPNS logic 322 are revealed in greater detail. In the functional diagram of FIG. 2.0 shows the sequence of the process in the IPNS logic block 322.

In step 200, the user-entered address string is introduced into the IPNS logic block 322. For a better view of the features of the invention, the example address string is 1800JKL1234. IPN is used throughout the exemplary description of the present invention in connection with FIG. 2.

In step 203, the portion of the address string that describes the domain name for which the name server is intended is removed. Thus, part of the IPNS sequence in

the entered address string is identified and separated from the rest of the entered address string. For example, in the case of 1800JKL1234.IPN a string introduced is removed "IPN", which results in the identification and separation of 5 IPNS series 1800JKL1234 as output.

In step 204, the values of each of the characters in IPNS-

the series are converted into system (s) or system (s) defined values. In Example 10, the values are converted according to the following table, which is essentially based on a telephone keyboard configuration:

is converted to 0 is converted to 1

The 2aBAVAC is converted to 2

3defDEF is converted to 3

4ghuGHU is converted to 4

5jklJKL is converted to 5

6mnoMNO is converted to 6

7pqrsPQRS is converted to 7

8tuvTUV is converted to 8

9wxyzWXYZ converted to 9

All other characters not included in the conversion table, such as dashes or lower dashes, are simply ignored. For example, the IPNS sequence 1800JKL1234 will be converted to 18005551234.

One advantage of the foregoing feature of the present invention is that variations and errors, such as inserting a lower dash instead of a dash, are filtered through the conversion process. For example, if 5 users entered 1-800-JKL 1234, the correct 18005551234 would still be converted. This way, the DNS-based system according to prior art, which is often error-prone, such variations and errors will not cause DNS to recognize and / or incorrectly resolve the address string and, as a consequence, to fail the user's intention to connect to the intended destination.

In step 205, the order in which (in total from left 15 to right) the characters, fields, or combinations of the two are presented in the converted IPNS sequence is rearranged into a new configuration from right to left. For example, the converted IPNS sequence 18005551234 will be rearranged at 43215550081.

In step 206, the reordered IPNS sequence is segmented (split) according to a variable data-managed segmentation format. The segmentation format is used to determine the number of areas within 25 sequences and the length of the number of characters in each area, with a view to inserting dots (ie ".") Between areas in the sequence. An example of a segmentation format is 4-3-4 format, in which the IPNS sequence number is segmented from right to left, first into a group of four outermost digits, then the next three, followed by the last four. A point is then inserted between each segmented group. For example, the IPNS sequence reordered in 43215550081 will be segmented in 4-3-4 format 5 to 4321.555.0081. Segmentation is also management data and recognizes digital end identifiers, such as country code or area codes, so that, in the case of different IPNS sequences entered, one following the telephone number of a foreign 10 country may a different segmentation format will be used. In an exemplary embodiment, the different segmentation formats can be modified so that the formatting organization settings can be made when desired or necessary. Additionally, various 15 segmentation formats are stored in the IPNS processor recovery database.

In step 207, the removed portion of the address string in step 203, which described a domain name that is controlled by 20 name servers, is now reassigned to the reordered segmented IPNS sequence. The result is to restore the input string in a format that is compatible with the underlying communication technology and addressing system. For example, 4321.555.0081 has been restored to 4321.555.0081.ipn.

In accordance with step 207, the name server can process the output string 209 as if it were an original DNS question, in accordance with DNS protocols. If no string alias information is found, then the name server must send to the DNS analyzer the data that present the new string as the normal name for the original domain being searched, in addition to any analysis data belonging to the new DNS address.

It should be noted that the various steps and specific order of the preceding operations are provided as exemplary only and any process using one or more of the disclosed established approaches from which a string is obtained, 10 compatible with the desired output string format 209 is provided be within the scope of the claimed invention.

FIG. 3.2 illustrates another embodiment of the present 15 invention used in an email (email) environment.

As illustrated, custom software products 366 and 358 are connected to a custom email server 350 that interacts with an Internet address analysis system, such as system database servers 319 or 311, 20 using IPNS logic 322 to execute Internet Protocol (IP) for the address of the requested e-mail server 355. The requested e-mail server 355 receives and processes the e-mail address using IPNS Email logic to convert the address to a standard e-mail address and then 25 forward the e-mail to the recipient through the horse ur 371.

It will now be disclosed in greater detail the embodiment illustrated in FIG. 3.2. For a better view of the features of the invention, an example input string is

1800JKL1234. IPN is used throughout the detailed description of the present invention in connection with FIG. 3.2 and FIG. 2.1.

Starting at step 348, the user, based on the availability or choice of new or existing software, enters an input string, which is in the form of a telephone number at the appropriate location of the new user software 366 or the existing user software 358, both supporting email communication applications and are connected to a custom email server 350. For example, a user enters the address string "1-800-555-1234.ipn" or "18005551234.ipn" in a box ("send to:") on an email program affecting a computer that is connected to Internet.

Currently, prior art email protocols do not typically recognize an input string, which is in the form of a phone number, as valid input because of the lack of a string character. The present invention solves this problem 20 by implementing one or more IPNS conversion logic 351, IPNS logic 322, and IPNS Email logic 356. The IPNS logic 322 used to communicate email is the same as the IPNS logic disclosed to FIG. 2.0 with respect to the embodiment for the World 25 Network illustrated in FIG. 3.0. The details of the

IPNS Email logic is further discussed in connection with FIG. 2.1 below.

In the exemplary embodiment illustrated in FIG. 3.2 and following loop 365, IPNS logic 322 is implemented in the user software 366 and converts the input string, which is in the form of a telephone number, directly into a valid recognizable incoming web address format. Due to the 5 requirements of existing email protocols, converted input addresses must in principle include an "©" symbol and at least one character or user software will generally not accept input to begin the address parsing process. The IPNS converter logic 10 351 then converts the IPNS logic output 322 to a valid recognizable input format for Internet e-mail addressing by affixing a "©" symbol and at least one character for the user software to begin the address parsing process. Unlike the system of 15, however, in the address string of the present invention, the "@" symbol and the accompanying character are included only to give a type of telephone address string to a valid address in accordance with existing email protocols, so that the process of 20 address analysis can be initialized. One advantage of the previous sign is that the user no longer needs to enter an email address with an "@" symbol.

The new user software 366 will then send 25 converted inputs to the custom email server 350. As some user software applications accept the user input address string without the "©" symbol and send them to their custom email server 350 for address analysis, the server for consumer email 350 may also include IPNSconvertor logic 351 for converting IPNS logic output 322 to a valid recognizable input format for Internet email addressing by placing "@" 5 character and at least one character. The custom e-mail server 350 will then send the input data over the internet to a suitable system database server 319 or 311, as shown by loops 368 or 369. The system database server is usually a domain name server (DNS) or similar 10 system , whose functions are widely known to those skilled in the art. The DNS server 319 or 311 sequentially converts the input string to an Internet Protocol (IP) address on the email server that supports the recipient email service (here John Doe) according to existing protocols and returns the IP15 address to the client software 366. The server for user email 350, it will then use the IP address to further forward the user packets of the email address string to the IP destination, which generally belongs to the requested email server 355, which supports the recipient's 20 email service.

In another embodiment of FIG. 3.2 the user address string is introduced into prior art 258 software software 358 that does not support IPNS logic 322. Due to the requirements of the existing email protocols, the user-entered address must include a character and at least one character or user software in principle will not accept the input to initialize the address analysis process. Unlike the prior art systems, however, in the address string of the present invention, the symbol and the accompanying character are included simply to give the 5 telephone address string a valid address in accordance with existing email protocols, so the process of address analysis can be initialized. Thus, the user does not need to know any predetermined character sequence in order to 10 enter the previous character, as in principle any arbitrary entered character would now suffice. For example, the example input string 18005551234 entered. An IPN from John Doe's business card will be entered in the form of:

<any character (S)> @ 18005551234.IPN

Existing user software 358 would then follow the existing Internet address analysis protocols and send the address string to the server for 20 user email 350, which would then forward it to a suitable database server that supports IPNS logic 322. At some stage, before entering into IPNS logic 322, the character and all previous characters are generally separated from the part of the domain name (here IPNS25 sequence), following the existing email protocols. For example, in the case of <any character (s)> @ 18005551234.IPNS IPNS sequence only

18005551234 would be preserved. The IPNS sequence is then converted using the IPNS logic 322 to the server for valid Internet Input Input Format Recognition, then converted to an Internet Protocol (IP) address on the email server that supports the recipient email service (here John Doe), following 5 existing protocols. The IP address goes back to the custom email server 350, which would then use the IP address to send the email packets further with the user address string to the IP address location, generally located in the requested email server 355, 10 which supports the recipient email service.

In the search server 355 IPNS-Email-logic

356 converts the custom address string into a standardized email address of the intended recipient. The requested 15 e-mail server 355 then sends the e-mail message to the requested recipient.

FIG. 2.1 further illustrates the processing sequence in IPNS-Email-logic 356. In step 213 20, the incoming data 210 is recognized as an email message containing a valid address format and transferred (loaded) to IPNS-Email-logic 356. A valid address format may be or a phone number format, such as 18005551234.IPN, or one using a 25 conventional character such as <any character (π)> @ 18005551234.ΙΡΝ. In this way, IPNS logic 356 can convert addresses arriving either from new user software 366 or from user software according to the prior art 358.

In step 214, the user address string is converted to a standardized email address 214 by an email server to determine the email address 5 to which the message is to be sent. For example, the user-entered string string 18005551234.ipn or <arbitrary character (s)> @ 18005551234.IPN is converted to J-Doe@someisp.com, where J-Doe@someisp.com is a functioning email account (account) by which John Doe 10 receives his email.

In step 215, the email is forwarded to the standardized email found.

In one embodiment, the object's email server

355 includes a database containing a list of incoming email addresses and their corresponding standardized email addresses. The database is then queried through IPNS-Email Logic 356 in Step 214 for the compliance of the 20 incoming email addresses with their respective standardized emails. If a standardized email address is detected, the flow continues to step 215, where the process of sending the email to the standardized email address via the email server in accordance with DNS, SMTP, POP and / or relevant standards or protocols, if any, is initialized. such. If a standardized email address is not detected, the target server's e-mail server 355 signals to other relevant email servers in the network of incorrect addresses in accordance with DNS, SMTP, POP and / or relevant

. r standards or protocols, if any.

Thus, as disclosed above, an IPNS address, such as 1-800-555-1234.ipn, can be used to make a phone call, a web page, and send an email.

In one embodiment of the present invention, at least one domain name in the domain name system 10 is essentially (preferably 100%) assigned to serve IPNS addresses. The system responsible for the domain name is also organized to ensure that IPNS addresses are used in part for actual standard communication with the requested group directly by telephone, for 15 access to a web page in connection with the requested recipient and for sending an email to the intended recipient. Organization features also include electronic or conventional user publications and administrative directories of all possible permutations 20 (changes) to permissible address strings and user parameters in the system. The User and Administration Guide will disclose the creation of eligible address strings in the form of a phone number in the assigned domain.

The assigned domain is also sufficiently sophisticated to recognize and process IPNS addresses that may contain additional, human-understandable modifiers, such as indicators of an extension of a telephone number or trademark of a company in a particular position within the address string range . For example, by introducing the extension "321" in the format 1-234-5678900x321.ipn, the communication or request for a web page 5 would be directed to the telephone number or web page of the person or division intended to be in extension 321, in this number in the organization or functions assigned to the system of the present invention. Another example would be: 1-324-567-8900 * Roger. IPN. This address string 10 will direct a communication or request for a web page or email to a phone, email or web page of a specific person or section intended to be in the extension designated "Roger" in that number as managed in the system.

The address string could also be extended by the addition of some valid trademark owned by the owner of the telephone number, which is reflected by a telephone-like string. For example, a valid address that the system could recognize could be 20: 1-800-555-1234.McDonalds.ipn or McDonalds.1800-555-1234.ipn.

The address string can also be expanded to include point-delimited subdomains before or after the 25 string, in a form similar to a phone number of one of the following types:

iii) () tax (.) iv) (.) pager (.)

v) () cell (.) vi) (.) message (.) vii) (.) instant-message (.) viii) (.) chat (.) ix) (,) ftp (.)

x) () g ° Pher (.) xi) (.) e-mail (.) [redundant, but could be used] xii) (.) web-page (.) (redundant, but could be used) xiii) etc.

Subsequently, other delimited subdomains may also be added. For example, valid addresses that the system might recognize could be: 1234-567-8900.fax.ipn or fax.1-234-5676-8900.ipn. In this case, 15 processing the domain would indicate that the incoming data is a fax. Domain processing alone would act as a "router" in this case for

adjusting the final destination of any communication or request for information.

The domain responsible system further processes IPNSs in accordance with error-corrected or programmed algorithms that facilitate system usability. The processing partially involves 25 loading of custom address processing programs in a domain name server

The responsible domain is also provided with proper administration and technical services to ensure that it functions properly. Proper responsible domain administration includes, but is not limited to, setting up management software to allow a representative of the responsible domain to collect, enter, and store information from a new user at.

A database containing a standardized email address of a user is used to convert one or more repetitions of an address string, similar to a telephone number into a standardized email address and / or website address 10 selected by the user. In this way, the representative of the responsible domain or the user could quickly modify the relevant elements of the database. For example, an email sent to a specific address string similar to a phone number may be forwarded to 15 standardized email addresses over a period of time or as a major change in the subscriber profile.

Finally, domain representatives or subscribers could, by using the software, add or delete 20 modifiers to the underlying IPNS address, if any, such as in each case an IPNS address with a different modifier to convert to a different standardized email address.

It is noted that the foregoing various embodiments of the present invention are illustrated separately occasionally, with a view to simplifying the schemes and related description of the details. Any process or system utilizing one or more of the disclosed embodiments is intended to be within the scope of the claimed invention.

Other embodiments and advantages of the present invention will be apparent to those skilled in the art in the disclosure and implementation of the invention disclosed herein. It is to be understood that the description and the examples will be considered exemplary only, with the actual scope and nature of the invention as defined in the following claims.

Claims (77)

1. Communication system through at least one 5 communication environment, the system comprising: a plurality of incoming subsystems for receiving an address string, the address string having a valid format recognizable by the incoming subsystems and being implemented in at least one communication application selected from a collection of different ® 10 types of communication applications, characterized in that the same address string can be validly entered for each selected communication application from the collection. System according to claim 1, characterized in that the address string is connected to at least one receiving object. The system of claim 1, further comprising: © 20 the recognition subsystem for recognizing the entered address string in a different format than the format used by the selected communication application, and a conversion subsystem for converting the different format into at least one format used by the 25 selected communication application. System according to claim 1, characterized in that the system further comprises: a selective subsystem for determining at least one communication medium based on the selected communication application, and a communication subsystem for establishing communication based on the address string through the designated 5 communication environment. 5. A system according to claim 4, wherein the communication medium is homogeneous and / or multiple heterogeneous media. • 10 System according to claim 1, characterized in that the collection of different communication applications includes communication applications of the same type and / or of the same type, but in different formats. System according to claim 3, characterized in that the conversion subsystem further comprises: retransmission subsystem for relaying each component of the address string to a corresponding, © 20 predefined number; a segmentation subsystem for segmenting the transmitted components into at least one sub-sequence according to a predetermined segmentation format .; re - ordering subsystem of 25 segmented components in an output string, in a format different in sequence from the address string introduced, wherein the output string is in a predefined reordered format and analyzing the decomposition subsystem 30 reordered strings in the appropriate valid address format. System according to claim 7, characterized in that the corresponding valid address format is 5 used to establish communication with a place in the World Wide Web. System according to claim 1, characterized in that it is a collection of different communication applications 10 includes communication applications of the same type and / or of the same type, but in different formats. A system according to claim 9, wherein the communication application is a means for 15 search for resources on the web (browser). System according to claim 9, characterized in that the communication application is a telephone service. 20 12. The system of claim 9, wherein the communication application is an email application. The system of claim 7, characterized 25 in that the conversion system further comprises: transmission subsystem for transmission of the introduced string to a compliance subsystem based on the corresponding valid address format, such as the subsystem 30 for compliance is to match the entered address string Ο 10 φ 20 to at least one valid email address, wherein the valid email address is used to retransmit communication to the destination of the valid email address. System according to claim 7, characterized in that the conversion subsystem further comprises: a conversion subsystem for converting a valid address format to a valid email address format, the valid email address format consisting of a valid address format preceded by the "©" symbol and at least one character. 15. A method of communication through at least one communication medium, wherein the method includes: accepting an 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, characterized in that the same address string can be validly entered for each selected communication application from the collection. 16. A method according to claim 15, wherein the method further comprises: determining at least one communication environment based on the selected communication application and establishing communication through the particular communication environment. A method according to claim 16, characterized in 30 that the communication medium is homogeneous and / or a plurality of heterogeneous media. 18. The method of claim 15, wherein the collection of different communication applications includes communication applications of the same type and / or of the same type, but in different formats. 19. The method of claim 18, wherein the communication application is a worldwide web browser (browser). 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 email application. 22. The method of claim 15, wherein receiving the address string further includes: recognizing the entered address string in a different format than the format used by the selected communication application, and converting the different format into at least one format used by the selected communication application. 23. The method of claim 22, wherein the transformation further includes: CTMCS transmission of each address string component to a corresponding predetermined number, segmenting the transmitted components into at least one sub sequence according to a predetermined 5 segmentation format; rearranging the segmented components into an output string with a different format of a series of introduced address strings, wherein the output string is in a predetermined format of reordering, and F 10 parsing the reordered string in the appropriate valid address format. 24. The method of claim 23, wherein the corresponding valid address format is addressable 15 World Wide Web Page Format. A method according to claim 23, characterized in that the address string is connected to at least one receiving module. Q 20 26. The method of claim 23, further comprising: transmission of the introduced string based on the corresponding valid address format, and 25 accepting the transmitted input string and matching the input string to at least one valid email address, wherein the valid email address is used for relay communication to the destination of the valid email address. The method of claim 23, characterized in Ф 10 ф 20 that the conversion also includes: converting a valid address format to a valid email address format, in which the valid email address format contained in the valid address format is preceded by a character and at least one character. 28. A method of communication through at least one communication medium, the method comprising: accepting an address string introduced in a plurality of communication applications selected from a collection of different types of communication applications, characterized in that the same address string can be validly entered for each selected communication application in the collection. 29. The method of claim 28, further comprising: determining at least one communication track based on the selected communication applications and establishing communication through the designated communication environment. 30. The method of claim 28, wherein receiving the address string further includes: recognizing the entered address string in a different format than the format used by the selected communication application, and converting the different format into at least one format used by the selected communication application. 31. The method of claim 30, wherein the transformation further comprises transmitting each address string component to a corresponding predetermined number, segmenting the transmitted components into at least one 5 sub-sequence according to a predetermined segmentation format, rearranging the segmented components into output string with a different layout format than the input address string, wherein the output string is in a predefined format of reordering, and decomposition of reorder the regular string in the appropriate valid address format. 32. The method of claim 31, wherein the corresponding valid address format is a web site 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 connected to at least one receiving module. 35. The method of claim 30, wherein the conversion further includes: transmission of the input string entered, based on the corresponding valid address format, and 30 Accepting the Incoming String Transmitted and Matching • 10 the entered string to at least one valid email address, wherein the valid email address is used to transmit the destination to the valid email address. 36. The method of claim 30, wherein the conversion further includes: converting the valid address format to a valid email format, wherein the valid email format contains a valid address format preceded by a character and at least one character. 37. A method for generating a valid Internet address for an Internet communications application, the method comprising: accepting as input of at least one input string, distinguishing between valid components and invalid components in the input string, forming at least one valid internet address for the Internet communication application from valid components. 38. The method of claim 37, wherein the valid component is a second-tier Internet address string for the Internet communication application. 39. The method of claim 37, wherein the string introduced includes access commands to a particular site (page) of the World Wide Web. 40. The method of claim 37, wherein said string includes commands for sending an e-mail to a specific email address. The method of claim 37, characterized in 5 that the string introduced includes commands for establishing a telephone connection to a particular telephone number over the Internet or a conventional telephone line. 42. System for generating a valid internet address 10 for an Internet communications application, wherein the system includes: input subsystem for receiving as input to at least one input string, processor subsystem for distinguishing between 15 valid components and invalid components in the introduced string, and a configuration subsystem for forming at least one valid Internet address for the Internet communication application of valid components. 43. The system of claim 42, wherein the valid component is a second-tier Internet address string for the Internet communication application. 25 44. The system of claim 42, wherein the string introduced includes commands for accessing a particular page of the World Wide Web. The system of claim 42, characterized 30 in that the string entered includes commands to send © 10 an email to a specific email address. The system of claim 42, wherein the introduced string includes commands for establishing a telephone connection to a particular telephone number over the Internet or a conventional telephone line. 47. A method of converting an address string to a predetermined internet address format, the method comprising: receiving as input the at least one entered address string, the address string including multiple alphanumeric characters, and rearranging the entered string into an output string in a format different from the entered address string, wherein the output string is in a predetermined internet address format. 48. The method of claim 47, wherein the sub-arrangement further includes: segmenting the introduced string into at least one second-level string, and sequentially re-assembling a second-level sequence based on a corresponding predetermined hierarchical format, wherein the string format is in a predetermined Internet address format. 49. The method of claim 45, wherein the segmentation involves dividing the introduced string into a second-level string, in the form of digital © 10 segments per telephone number. 50. A method for converting an entered email address into an internet email format, the method comprising: accepting as input the at least one e-mail address string entered, the address string including a plurality of alpha-numeric characters, and converting the entered address string to an output string, wherein the output string is in a predetermined email address format. The method of claim 50, wherein the conversion further includes: rearrange the introduced string into an output string in a format different in sequence from the entered address string. The method of claim 48, wherein the rearrangement further includes: segmenting the introduced string into at least one second-level string, and sequentially re-assembling the second-string sequence based on a corresponding predetermined hierarchical format, wherein the format string is in a predefined Internet email format. 53. A method for operating domain name servers, the method comprising: essentially assigning at least one domain name server to serve one or more subordinate domain names, wherein each subordinate domain name is represented by at least one string of digits in the form of a telephone number. 54. The method of claim 53, wherein the method further comprises: organizing domain name servers to ensure that string strings are valid and linking the initial domain name to at least one domain name of the desired destination through at least one communication application, and providing domain name administrative services to accurately administer the name servers domain name. 55. The method of claim 53, wherein the at least one domain name server is a top-level domain name server. 0 20 56. The method of claim 54, wherein the address processing application is a custom search engine (browser) for the World Wide Web. 25 The method of claim 54, wherein the address processing application is an e-mail application program. The method of claim 54, characterized in 30 that the address processing application is a consumer telephone service. The method of claim 54, wherein the communication application is a browser for 5 World Wide Web. 60. The method of claim 54, wherein the communication application is a telephone service. © 10 The method of claim 54, wherein the communication application is an e-mail application. The method of claim 54, characterized in 15 that the organization of the domain name server includes providing a directory containing a complete list of permutations of a valid string of numbers. 63. The method of claim 62, wherein the reference is an end-user reference. 64. The method of claim 62, wherein the directory is an administrative directory. 25 65. The method of claim 53, wherein the domain name server is operated by a telephone service provider. 66. A method for converting an address string, such as 30 the method includes: receiving as inputs a valid address string having at least one component, wherein the component is an alpha-numeric group element, converting each said component of the 5 address string into a predetermined corresponding number, recognizing digital end identifiers in the converted components, and rearranging the converted components, 9 Based on established digital end identifiers according to a predefined hierarchical format. 67. The method of claim 66, wherein the transformation further comprises: converting each non-digit part of the address string component into a corresponding digit or symbol, grouped in the format as represented on the 20 selective buttons on a telephone. 68. The method of claim 66, wherein the predetermined hierarchical format is a hierarchical telephone system format. 69. The method of claim 66, wherein the alpha-numeric series includes any human and / or machine-recognizable characters. 70. The method of claim 66, wherein the end identifiers are geographical identifiers. A method according to claim 70, characterized in 5 that the geographical identifier is a country code. 72. An address string conversion system, the method comprising: 10 an input subsystem for receiving as inputs a valid address string with at least one component, wherein the component is an element of an alpha-numeric series, a conversion subsystem for converting each component of the address string into a pre- 15 a corresponding mapping number, a recognition subsystem for identifying end identifiers in the converted components, and a re-subsystem for rearranging the converted components based on recognized digital 20 end identifiers according to a predefined hierarchical format. 73. The system of claim 72, wherein the converter subsystem converts the 25 non-digit portion of the address string component into a corresponding digit or symbol, grouped in the form shown on the telephone dial buttons. 74. The system of claim 72, characterized 30 in that the predetermined hierarchical format is a hierarchical format of a telephone system. 75. The system of claim 72, wherein the alpha-numeric series includes any 5 human and / or machine recognizable characters. 76. The system of claim 72, wherein the final identifier is a geographical identifier. 77. The system of claim 76, wherein the geographical identifier is a country telephone code.