JP2002526834A - Method and system for alternative internet resource identifiers and addresses - Google Patents

Abstract

(57) Abstract: A method and system that uses alternative resource identifiers instead of regular resource identifiers. The present invention uses software to immediately translate the alternative resource identifier into a regular resource identifier. The resources on the Internet are then accessed using conventional resource identifiers in a conventional manner and presented to the user.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001] This application was filed on September 29, 1998 and filed in US patent application Ser. No. 60 / 102,33.
Internet browser with URL conversion system (No. 3)
ternet Browser with URL Conversion S
ystem) ". FIELD OF THE INVENTION The present invention relates to the field of information transfer on the Internet and to various protocols associated with such information transfer. BACKGROUND OF THE INVENTION The present invention offers significant challenges and opportunities for traditional network service providers. The number of Internet users is growing exponentially, simulating network service providers to create new services that capture such new markets.

One successfully and widely publicized part of the Internet is the World Wide
Web. This World Wide Web is a worldwide HTTP (
Hypertext Transfer Protocol) A comprehensive set of interlinked hypertext documents residing on a server. Documents in the World Wide Web, called pages or web pages, are HTML (Hypertext Markup Language) identified by a URL (Universal Resource Locator) that specifies the particular machine and pathname that can access the file. ) And sent to the end user via the node under the hypertext transfer protocol. Code called tags embedded in an HTML document associates a particular word and image in the document with a URL so that the user can access another file that can go around the world on key press or mouse click. . These files contain text (in various fonts and styles), graphics images, movie files, and sounds, as well as Java applets, ActiveX controls, or other small files that execute when the user activates by clicking a link. It may include an embedded software program. Users who view web pages also see web pages
Using the links on the page, you can download files from an FTP site and send messages to other users via email. FIG.
2 is a picture of a screen of a conventional web browser.

[0003] At a conceptual level, the World Wide Web can be viewed as a vast bank of hyperlinked data. To gain access to the World Wide Web, users must embed the appropriate software on their computers,
You must obtain a network connection from your Internet access provider.

[0004] The URL identifier for a resource is the protocol used when accessing the resource ("http:" for world wide web pages, or F
"Ftp:" for the TP site), the name of the server where the resource resides,
And optionally a path to a resource (HTML document or file on the server). For example, in the URL, http://www.israeliinternet.com/thissubsite/sitecontents.html "http: //" identifies the hypertext transfer protocol and " www.israeliinte
rnet .com "is related to the web server name," thissubsite / "identifies the directory of the desired document," sitecontents.html "represents the document to read.

[0005] The name of the computer server that makes up the URL side of the resource must be registered by the appropriate government agency, not just selected by the server operator. Otherwise, many servers will have the same name, resulting in confusion. (Such confusion is analogous to the problem of several different radio stations all broadcasting simultaneously on the same frequency.) Each server name has a 32-bit IP address that identifies the host machine on the Internet. Related. Such an association is achieved through the use of another computer known as a domain name server (Siyan, K.
See Aranjit, "Inside TCP / IP, Third Edition" (New Riders Publishing, 1997).

For the purposes of this patent application, the URL recognized on the Internet is “
A server name that is called a "conventional URL" and that is recognized on the Internet is called a "conventional server name." For the purposes of this application, language, alphabetic characters and pictograms are based on the terms used in the specifications for the Unicode standard. "Unicode Standard Second Version (The Unicode Sta
ndard Version 2.0) "(Addison-Wesley, 1
998). For the purposes of this application, characters are defined as the smallest elements of a written language that have meaningful value, while emoticons represent the shapes that characters can have when they are created or represented.

[0007] Today, all conventional URLs use Latin characters, even if URLs are used in writing languages that do not use Latin characters. FIG. 12 is a screen shot of a Hebrew browser. Unfortunately, for users whose native writing language does not use Latin characters, direct access to Internet resources with traditional URLs is difficult because users must remember complex and unfamiliar words or characters. Have difficulty. In addition, conventional URLs must be provided in a particular syntax that is difficult for many users to understand, and even small errors that confuse "." With "," do not allow the user to access the desired resource. May result.

[0008] Somewhere in the World Wide Web, URLs that the user does not know
When trying to go to an address, the user must use a search engine. However, most people do not go online for two reasons. First, they have an overwhelming number of options each time. Second, they encounter too many irrelevant sites when using search engines.

In addition to this, many Internet users will enter a generic URL address for the product they are looking for. For example, a person looking for car insurance would enter the address "car inquiry" into his browser. As a result, the Internet address "car insuran"
The owner of "ce" will have a long line of consumers looking for car insurance. In summary, general URL addresses are useful because they are easy to remember. SUMMARY OF THE INVENTION It is an object of the present invention to provide a system and method for a user of a device whose writing language is not based on Latin characters to access an HTML page by inputting a resource identifier that does not include Latin characters into the device. is there.

[0010] Another object of the present invention is to provide a user of a device with a simpler or otherwise more desirable resource identifier than a conventional URL, by entering the device with HTML.
It is to provide a system and a method for accessing a page.

The present invention attempts to convert conventional URLs into identifiers that are familiar to the user. (Such familiar identifiers are "friendly"
”Identifier. ) Such a converted identifier will be displayed to the user. Internally, the device will continue to use the conventional URL, which will be used to access resources on the Internet. Similarly, all resource identifiers returned to the device as a result of the operation will be converted to identifiers that are familiar to the user.

The above and other objects and features of the present invention will become apparent from the following description of preferred embodiments provided with reference to the accompanying drawings. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Introduction The object of the present invention is to provide a more natural experience for the majority of the world's population that does not use Latin characters in the written language using the World Wide Web and email. Is to bring.

[0013] In particular, the present invention provides a method for converting a traditional URL to any native language used by web surfers.
To enable conversion. Users of the preferred embodiment of the present invention will be able to view web site addresses in their own writing language and use email addresses in their own writing language.

The present invention takes several different embodiments, each specialized for a particular situation. However, each embodiment relies on the conversion of alternative resource identifiers to regular resource identifiers. Thus, the hidden regular resource identifier is used to access resources on the Internet in a conventional manner. Conventional resource identifiers, hidden for user-friendly reasons, will be available if the user desires.

[0015] Such an approach is a common approach in software engineering. For example, storage devices, such as magnetic disks, can compress data stored on disk drives in a lossless manner so that the capacity appears to the user to be much larger than it actually is. When the user actually accesses the data, the data is instantly decompressed in a way that is hidden from the user for reasons of appearance. Although many more steps can result in delays, it is known in the art how to reduce the delay to an unknown time.

The present invention contemplates that the device uses a conventional resource identifier for accessing resources on the Internet, but presents an easily understandable resource identifier (ie, a friendly identifier) to the user. The device achieves such functionality by instantly converting friendly resource identifiers to regular resource identifiers. Such a conversion process is referred to herein as a conversion algorithm.

In the detailed description, two preferred embodiments of the conversion algorithm are disclosed. However, those skilled in the art will be able to generate other transform algorithms, and the disclosure of these two algorithms is not intended to limit the invention to only the disclosed algorithms. Conversion algorithm

Each normal type resource identifier, which is one resource identifier (consisting of Latin characters)
It is also well known that an algorithm that generates from can be constructed, and if this algorithm were applied to a resource identifier consisting of Hebrew characters, the original regular resource identifier consisting of Latin characters would be restored. 2. Mapping Algorithm Referring now to FIG. 2, a "mapping" algorithm for converting regular resource identifiers to friendly resource identifiers is shown. (Again, for the purposes of this preferred embodiment of the conversion algorithm, the non-Latin character set used is Hebrew.) In step 200, the regular resource identifier is entered into a database query. Can be At step 202, the database query is performed against a database of friendly resource identifiers. The record for each friendly identifier in the database will have a field indicating the regular resource identifier to which the friendly resource identifier is mapped. In step 204, the success of the query is evaluated. If the query produces a result, in step 206 the result is a friendly resource identifier.
If this query did not produce a result, it would indicate that a friendly resource identifier could not be obtained.

As an example of such an algorithm, a normal type resource identifier “http: //
/ Www. healthinsurance. com "is mapped to Hebrew characters.

An important important feature of the mapping algorithm is that any regular resource identifier can be mapped to any friendly resource identifier. Thus, it is possible to make a resource, which is only one of many web pages in the server, look like the default page (ie, start page) of the web server from its friendly resource identifier. Overview of the Preferred Embodiment of the Invention Conceptually, this is a two-way translation of a URL from and to any native language that Internet surfers can use. The user of the system may enter the web site address, e-mail address, and each of the other URLs at each incoming web site, as soon as the call arrives, or the resource identifier may appear in his email box or other software. As soon as you can see it in your own language. The system will also discriminate between addresses from the World Wide Web or if it is the owner of a native language web site. Both native language address systems are enabled at the same time. Thus, for a surfer, the only difference is that a portal system-based address user has a. com,. net,. co. il, or similarly no items.

With the present invention, a non-English speaking Internet user will not even need to have English characters on his keyboard. These users will be able to dial anywhere on the World Wide Web, including email, using their native language keyboard. The present invention allows each Internet user worldwide to use their usual mailing address in their own language as their e-mail address. The disclosed system will send and receive email from this address to any location on the web. In a portal-based system, there is a choice for an on-screen keyboard in each language. This allows users to use their mouse to click on native language addresses, emails, search engines and similar items, even when they are in a location where they do not have access to their native language keyboard.

The system in each language is locked at one site. This site will be a specific homepage in this language. Each Internet address in this language will be assigned to one subsite. To both web site owners as well as surfers' users, this subsite looks and acts as a home page. For example, when an individual Israeli obtains a Hebrew address, the system translates the Israeli address into a URL that appears after the normal address. In this case, the surfer that does not use the conversion system can access the Internet address “http://www.world.
durls. com / healthinsurance ",
Look at it and type in the key. An Israeli who uses the Hebrew translation system will dial after seeing the Hebrew address. The email is, in this example, healthsurance @ worlddurls. com. Obviously, the user of the conversion system will key in and view the email at the Hebrew address. The server side of the system will accept free websites and email applications. If the user only wants to link the address to his current web site, he only has to enter the current URL.

Additionally, the user may select a native language Internet address or an email account name. Once the Internet address or email user name is accepted, the user may enter different choices. At the end of the registration process, the system creates a web page or email account. At the subsite level, the internal name assignment system will work in a manner similar to the way it works in the direct translator of the system. For this reason, each web
Site owners are also automatically converted to their subsites using a two-tier conversion system, ie, a combination of words and letters. 1. Instant URL translation of Latin to native address system Locations that are not part of the portal address assignment system (ie, World
Surfers arriving at any web site located on the Wide Web)
You will see your own language in the URL box, not the Internet Protocol. When the surfer reaches the non-system user's web site, regardless of the portal or desktop-based options, the conversion algorithm runs. For example, “http: //www.h
healthsurance. com "address, the system returns" http
p: // www "and" .p. com ”(and“.
com ”) is separated. In this case, health i
nsurance. The system then uses the system's simple English / Hebrew dictionary to translate the words into the native language of the web surfer. The system then reverses the order of the Hebrew words so that "http: // www" and ".
com "and the address is displayed in the native language of the surfer.

Surfers can also key in addresses in their native language. The system then reverses the process. If the system cannot identify a word that is part of the address, the address will appear in Hebrew, but will appear in any character form using a character-by-character conversion system. When mixed, the system constructs addresses using both word and character units. This occurs irregularly when Latin characters perform one or more character conversions within the same address. This is because the relationship is constant in the character unit system, but the value of the character is fluid in the word conversion system. In Japanese with no letters, one embodiment of the present invention provides for each English letter to produce the sound of this letter or the sound so that surfers can recognize when a Japanese word is used to identify a non-English letter. Assign Japanese words as close as possible. 16 and 17 illustrate this conversion process. 2. Search Engine: All Internet Protocol-based search engines use English only. When users of the system search the World Wide Web using their native language, they insert the request into their own language. For example, as the user enters words, the system's normal English / Hebrew dictionary translates these words into English, or "insurance life". The system then reverses the order to life involvement, either searching for one or both configurations. Also, a two-tier conversion system is used. Thus, addresses and other Internet Protocol marks that use non-word characters can be identified as valid character marks, and / or both, or word marks, or a combination of both. Search for. Once the system finds the requested location,
You will have the option to view these in the URL form before translation of the user's native language or address. The system will also discriminate between addresses from the World Wide Web, or whether they are native language web site owners. Browser Preferred Embodiment System Structure As shown in FIG. 7, the preferred embodiment structure is a client computer 1000 that accesses the Internet. Computer server 2
000, which is also the Internet Web
Access the server 3000.

Referring now to FIG. 8, the client computer 1000 includes a CPU 405, a RAM 415, a ROM 420, a clock 435, and a video driver 42.
5, a video monitor 430, a communication port 440, an input device 445, and a data storage device 460.

According to FIG. 9, the computer server 2000 includes the CPU 505 and the RAM 5
15, a clock 53, a video monitor 530, and a communication port 50
4, an input device 545, a ROM 520, and a data storage device 560. Data storage 560 includes a database used to provide regular resource identifiers and friendly resource identifiers.

Similarly, as shown in FIG. 10, the web server 3000
RAM 615, ROM 620, clock 635, web software 640, data storage 650, video monitor 670, comment
It includes a port 660 and an input device 690. System Operation One preferred embodiment of the present invention is a browser coupled with software using two algorithms. When a user types a Hebrew resource identifier, the computer first converts the Hebrew resource identifier to a regular resource identifier. The algorithm for such a process is a conventional algorithm or a mapping algorithm.

In one embodiment, a browser user uses computer server 2000 as an Internet service provider that automatically downloads a mapping database to the browser. Alternatively, the mapping database in another embodiment is emailed to a browser that incorporates the new mapping into the existing database.

Operation of the system begins with the user of client computer 1000 entering a friendly resource identifier using non-Latin characters. Client computer 1000 constitutes a file consisting of information entered in non-Latin characters. The client computer 1000 processes the friendly resource locator using either a conversion algorithm or a mapping algorithm and contacts the web server 3000 for the appropriate HTML page. FIG. 9 is a screen shot of such a browser.

In another preferred embodiment, client computer 1000 contacts computer server 2000. Computer server 2000 then implements the conversion algorithm, and then passes the information back to client computer 100.
Return to 0 and the computer will then use this information to get an HTML page. In another preferred embodiment, server 2000 obtains the HTML page itself and then resends the HTML page to the user. Such a variation of the preferred embodiment uses a browser that uses speech recognition technology.

It is important to know that both transform algorithms are applicable. Usually, a mapping algorithm is used first. If the mapping algorithm was unsuccessful because no match was found, a (always successful) transformation algorithm will be executed. It is conceivable that the web site owner operates such that its conventional resource identifier is stored in a database of mapping algorithms to give a friendly resource identifier.

[0032] Not for HTML documents (like regular server names)
It should also be noted that the mapping algorithm succeeds for some of the resource identifiers. In this case, the mapping algorithm would be applied to the regular server name, and the regular algorithm would be applied to the rest of the resource identifier. Preferred Embodiment of the Invention in a Hosting System In a preferred embodiment of the hosting system, a computer server 2000 hosts HTML pages on the system. The user enters a friendly resource identifier for one of these hosted HTML pages. In a preferred embodiment, the client computer 1000 translates the friendly resource identifier into a suitable regular resource identifier. The client computer 1000 then goes to the computer server 2
Retrieve the appropriate HTML page from 000. In another preferred embodiment, client computer 1000 automatically contacts computer server 2000 when an unusual resource identifier is entered. Then, the computer server 2000 performs the conversion.

In any case, once Hebrew is entered, the appropriate HTML page will appear as a top-level web site, as shown in FIGS. 13, 14 and 15.

Although this HTML page can be used for a client computer 1000 that does not use the preferred embodiment, the resource identifier is “http: // www”.
.worldwideurls.com / bjifh-hjjm ”. A preferred embodiment of the invention in a portal system Portal is a well-known term for a directory of Internet resources. The portal server may be implemented in a portal system where all resource identifiers are friendly resource identifiers.The portal server uses a conventional algorithm or a mapping algorithm to
000 to retrieve the appropriate HTML document. Preferred Embodiments of the Invention in a Search Engine In yet another embodiment of the present invention, the friendly search conditions are converted to various conventional conditions using a conversion algorithm, and the Latin search words and the conventional search are converted. Be executed. The result is either a conventional algorithm or a mapping algorithm.
Returned to the browser using one of the algorithms. Email In another embodiment of the present invention, email addresses are mapped from Latin characters to non-Latin characters and vice versa. Either conventional addresses or mapped addresses are used. Therefore, a user whose writing language does not include Latin characters can use an e-mail using characters of the writing language. *** All quite different embodiments rely on the conversion of friendly resource identifiers to regular resource identifiers, but with reference to FIGS. 18 and 19, the present invention uses the services of a domain name server. Without adaptation, the friendly resource identifier may be adapted to be converted to a 32-bit IP address. *** The invention has been described with respect to particular embodiments, but those skilled in the art will appreciate that various changes and modifications can be made without departing from the spirit and scope of the invention as set forth in the appended claims. It will be clear that this is possible.

[Brief description of the drawings]

FIG. 1 is a flowchart showing a conversion algorithm.

FIG. 2 is a diagram illustrating a conversion algorithm.

FIG. 3 is a diagram showing a conversion algorithm.

FIG. 4 is a diagram showing a conversion algorithm.

FIG. 5 is a diagram showing a conversion algorithm.

FIG. 6 is a flowchart showing a mapping algorithm.

FIG. 7 is a block diagram showing a preferred embodiment of the system.

FIG. 8 is a block diagram showing one embodiment of a client computer.

FIG. 9 is a block diagram illustrating an embodiment of a computer server.

FIG. 10 is a block diagram showing one embodiment of a web server.

FIG. 11 is a screen shot showing a conventional English web browser.

FIG. 12 is a screen shot showing a conventional Hebrew web browser.

FIG. 13 is a screen shot showing a Hebrew web browser according to a preferred embodiment of the present invention.

FIG. 14 is a screen shot showing a Hebrew web browser which is another preferred embodiment of the present invention.

FIG. 15 is a screen shot showing a Hebrew web browser which is another preferred embodiment of the present invention.

FIG. 16 is a block diagram showing a transformation included in a preferred embodiment of the present invention.

FIG. 17 is a block diagram showing a transformation included in a preferred embodiment of the present invention.

FIG. 18 is a block diagram illustrating a transform included in another preferred embodiment of the present invention.

FIG. 19 is a block diagram illustrating a transform included in another preferred embodiment of the present invention.

──────────────────────────────────────────────────続 き Continuation of front page (81) Designated country EP (AT, BE, CH, CY, DE, DK, ES, FI, FR, GB, GR, IE, IT, LU, MC, NL, PT, SE ), OA (BF, BJ, CF, CG, CI, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG), AP (GH, GM, KE, LS, MW, SD, SL, SZ, UG, ZW), EA (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM), AE, AL, AM, AT, AU, AZ, BA, BB, BG, BR , BY, CA, CH, CN, CU, CZ, DE, DK, EE, ES, FI, GB, GD, GE, GH, GM, HR, HU, ID, IL, IN, IS , JP, KE, KG, KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MD, MG, MK, MN, MW, MX, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI, SK, SL, TJ, TM, TR, TT, UA, UG, US, UZ, VN, YU, ZA, ZW

Claims (23)

[Claims] 1. A method of using an alternative resource identifier instead of a normal resource identifier when accessing a resource on the Internet, wherein the alternative resource identifier is provided to a device capable of accessing the Internet. Converting the alternative resource identifier to a normal resource identifier; accessing a resource on the Internet using the normal resource identifier; and presenting the resource to a user. Method. 2. A computer system for providing a user request including a universal resource locator (URL) throughout a network, wherein the user is able to enter a non-Latin URL address.
Browser means operating on the computer system; receiving the non-Latin URL address from the browser means;
A conversion unit connected to the browser unit for converting the RL address into an intermediate URL address; and a transmission unit connected to the conversion unit for receiving the intermediate URL address and transmitting the intermediate URL address to the entire network. A computer system comprising: means. 3. The conversion means for converting the non-Latin URL address into an alphabetic text string; and concatenating a predetermined text string to the alphabetic text string to convert the intermediate URL address. 3. The computer system according to claim 2, comprising: generating means for generating. 4. The computer system according to claim 3, wherein said predetermined text string represents a homepage address of a unique management server in a network. 5. The computer system according to claim 4, wherein all user requests including the non-Latin URL address are directed to a homepage of the primary management server. 6. The computer system according to claim 5, wherein said intermediate URL address represents said subsite of said unique management server. 7. The computer system of claim 6, wherein said alphabetic text string includes letters and numbers. 8. A computer system for providing a user request including a URL to the entire network, the browser means operating on the computer system to enable the user to enter a general URL address; Converting means connected to the browser means for receiving the general URL address from the browser means and converting the general URL address to an intermediate URL address; and receiving the intermediate URL address and transmitting the intermediate URL address to the entire network. A transmission means connected to said conversion means for transmitting. 9. The conversion means for converting the general URL address into an English text string, and the intermediate URL address by concatenating a predetermined text string to the English text string. 9. The computer system according to claim 8, comprising: 10. The computer system according to claim 9, wherein said predetermined text string represents a homepage address of a unique management server in a network. 11. The computer according to claim 10, wherein all user requests including the general URL address are directed to a home page of the unique management server.
system. 12. The computer system according to claim 11, wherein said intermediate URL address represents a subsite of said home page of said unique management server. 13. The computer system of claim 12, wherein said alphabetic text string includes letters and numbers. 14. A method of translating a non-Latin URL address to an intermediate URL address in a computer system, the computer system providing a user request including a universal resource locator (URL) across a network. Receiving the non-Latin URL address; translating the non-Latin URL address to an intermediate URL address; and transmitting the intermediate URL address throughout the network. 15. The intermediate URL address by converting the non-Latin URL address to an alphanumeric text string, and concatenating a predetermined text string to the alphanumeric text string. The method of claim 14, comprising: generating. 16. The method of claim 15, wherein said predetermined text string represents a homepage address of a unique management server in the network. 17. The method of claim 16, wherein all user requests that include the non-Latin URL address are directed to the home page of the unique management server. 18. The method of claim 17, wherein said intermediate URL address represents a sub-site of said home page of said unique management server. 19. A method for translating a general URL address to an intermediate URL address in a computing system, the method comprising providing a user request including a universal resource locator (URL) to an entire network. Receiving the general URL address; translating the general URL address to an intermediate URL address; and transmitting the intermediate URL address throughout the network. 20. The method of claim 19, wherein the converting step comprises: converting the general URL address to an alphanumeric text string; and concatenating a predetermined text string to the alphanumeric text string to convert the intermediate URL address. 20. The method of claim 19, comprising: generating. 21. The method of claim 20, wherein said predetermined text string represents a homepage address of a unique management server in a network. 22. The method according to claim 21, wherein all user requests including the general URL address are directed to the unique management server home page. 23. The method of claim 22, wherein said intermediate URL address represents a sub-site of said home page of said unique management server.