JP2002082854A - Method for using non-alphanumeric address - Google Patents

Abstract

PROBLEM TO BE SOLVED: To achieve an address notation by using graphics and native language by making it possible to use non-alphanumeric characters in the address of an Internet homepage without newly installing an application into a client computer and without needing large change and cost in a server on a Web. SOLUTION: When the non-alphanumeric characters are inputted as the address to request access to the homepage, script for converting the non- alphanumeric characters into a communicable sentence state is sent back as the results of the request, and the connection to the homepage is requested again with the communicable address converted by the script.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

FIELD OF THE INVENTION The present invention relates to the use of non-alphanumeric addresses on Internet homepages.

[0002]

2. Description of the Related Art Conventionally, in order to represent the location (address) of a home page on the Internet, it has been decided to use alphanumeric characters (ASCII) due to browser restrictions. This is due to the fact that the Internet system was more advanced than English-speaking countries. If 7 bits are used, all alphanumeric notation is possible, the server processes the address requested for connection, returns a numerical IP address indicating the location of the address as a result, and directs it to the IP address. WEB by requesting connection
It is possible to access the location of the home page intended above. If a connection request is made to an address that contains non-alphanumeric characters, the address will not be sent, or it will be sent as a different alphanumeric character, depending on the type of browser, and it will say "address not found", A home page at a different alphanumeric address happens to be displayed. However, people in countries that do not regularly use alphanumeric characters have a strong desire to obtain addresses using their own characters. For this reason, a non-alphanumeric address (hereinafter referred to as a non-alphanumeric address) is prepared in advance in a computer used by a client (abbreviated as a client computer) or a dedicated application in a server, and a non-alphanumeric address is prepared. , Or received a request for connection (short, request)
Make a request to the server with the corresponding alphanumeric address by comparing it with the prepared conversion table, or enable the non-alphanumeric address to be sent to the server and return the corresponding IP address as a result, Methods that can be used are also contemplated.

However, in such a method, it is necessary to prepare a dedicated application in the client computer, and it is necessary to install such an application in all the existing client computers even if it is a new client computer. Is extremely costly and time consuming, making it virtually impossible.

[0004]

SUMMARY OF THE INVENTION An object of the present invention is to use non-alphanumeric characters such as Japanese, Korean, Chinese, Arabic, and Russian without installing a new application or the like on a client computer. To make the address available.

[0005]

According to the present invention, in order to achieve the above object, the present invention enables communication of a non-alphanumeric address when a request for connection to the non-alphanumeric address is issued on the Internet. Provide a conversion server that attaches a conversion script that converts to an address using characters and returns it as a result to the client computer, and when a request for connection to the non-alphanumeric address is issued from the client computer,
The conversion script is attached and returned as a result to the client computer, the non-alphanumeric address is converted to a communicable state by the conversion script by the client computer, and a new request is issued again. I have.

[0006]

FIG. 1 is a block diagram of an embodiment to which the above-described invention is applied. (1) A client computer,
(2) is a root name server, (3) is a conversion server,
In (4), the non-alphanumeric characters are returned to the client computer (1) as a result, with the converted IP address converted to communicable characters by the conversion script incorporated in the result returned from the conversion server (3). Is a DNS server, and (5) is a host server for connection purposes. FIG. 2 is a flowchart for explaining the processing step S of the embodiment to which the present invention is applied.

[0007] The client computer (1)
The processing performed between the servers (2) to (5) connected to the server and the WEB will be described with reference to FIGS. First, in step S1, if there is a request 1 by the client computer (1) to connect to a non-alphanumeric character, for example, Japanese, an address such as "something company / food", the non-alphanumeric character is correctly displayed on the WEB. Since it is not sent and the corresponding non-alphanumeric address is not on the WEB, first, as shown in step S2, the root name server (2) receives a connection request for the non-alphanumeric address as the result 1 as shown in step S2. As a result, an address (IP address) indicating the location of the conversion server (3) is returned to the client computer (1). Then, the client computer (1) is connected to the conversion server (3) as a request 2 as shown in step S3. In step S4, assuming that there is a request from the client computer (1) to connect to a non-alphanumeric address, the conversion server (3) sends a conversion script for converting the non-alphanumeric characters to communicable characters to the client computer (1). Result 2
Will be returned. In step S5, the client computer (1) processes the conversion script, converts the non-alphanumeric characters requested by the client computer into communicable characters, and sends the converted address to the DNS server (4).
In step S6, the DNS server (4) requests the connection by the client computer (1), that is, the host server (5), as in the related art, because the converted address is a communicable character. I representing the location of
The P address is sent as the result 3 to the client computer (1). In step S7, the client computer (1) makes the request 4
At step 6, a connection request is sent to the IP address of the host server (5) sent from the DNS server (4). Step S8
Then, the host server (5) sends the data of the address requested by the client computer (1), that is, the "food" file (page data of the main body) of "Some One Corporation" to the client computer (1). 4
Will be sent back. If you want to process the currently used alphanumeric and non-alphanumeric addresses on the same server,
If the address of the transfer destination is incorporated in the result 4 described above, the present invention can be applied to a virtual server. Further, when the domain portion is a conventional alphanumeric character and the file portion is specified with a non-alphanumeric address, for example, when an address such as “COMPANY.JP/food” is specified, the root name server (2 ) Performs the same processing as before, and returns, for example, the IP address of “COMPANY.JP” as a result. After that, "COMPANY.JP"
If a conversion server (3) is provided in the host server and a non-alphanumeric address is converted by a script, the same processing as described in the embodiment can be performed.

As described above, even if there is a connection request for a non-alphanumeric address that cannot be communicated with the current browser, the root name server (2) will say, "This is a connection for a non-alphanumeric address. Automatically returns the IP address of the conversion server (3) as a result, and uses languages from around the world and some graphics as addresses without installing a special application on the client computer (1). It is possible to do. Further, if the conversion server (3) and the DNS server (4) in which the converted address is registered in advance are integrated, one computer can be placed on the WEB without changing the current WEB configuration. It becomes possible only by providing. Also, if the conversion server (3) does not return the result by incorporating the conversion script in the result each time, but returns the result by incorporating the location address of the conversion script, the client computer (1) once accessing the location address of the conversion script can Since the address and the conversion script are memorized in the cache, it is not necessary to send the conversion script every time, and the load on the conversion server (3) is reduced.

Next, another embodiment of the present invention will be described with reference to FIG. As in the processing shown in step S41, instead of result 2 in step S4, in result 2 of step S41, a non-alphanumeric address can be inserted into request data such as form data or cookie data in the conversion script, and communication can be performed. The state is set, and a script for performing a process for newly issuing a request is incorporated and returned to the client computer (1). In the subsequent step S51, the client computer (1) requests the analysis server (6) shown in FIG. 1 by including the non-alphanumeric address in part or all of the request data such as form data or cookie data according to the script. Send as 3A. In the process of step S61, the analysis server (6) analyzes the non-alphanumeric address included in the form data or the cookie data, and if the analysis server (6) itself has the text data of the address, the analysis server (6) deletes the text. Or return the address of the target host server (5) if it does not have it as the result 3A. Therefore, when the target body data is returned from the analysis server (6), a series of processing is completed. Otherwise, the destination host server (5) address returned as the result 3A in step S71 is returned. The connection request is issued as the request 4A, and the text data is returned from the target host server (5) as the result 4A in step S81. Similar effects can be obtained by such processing.

[0010]

As described above, according to the present invention, the address indicating the location of the Internet home page, which can be displayed only by alphanumeric characters, can be increased without installing a special application on the client computer. There is an effect that non-alphanumeric characters can be used as an address with only a few facilities and a slight change of the WEB system without providing a separate facility on the WEB. In addition, there is a great effect that the current browser can be used as it is without changing the current browser even in the world trend of using double-byte characters.

[0011]

[Brief description of the drawings]

FIG. 1 is a configuration diagram as an embodiment.

FIG. 2 is a flowchart showing a process.

FIG. 3 is a flowchart illustrating a process according to another embodiment.

[Explanation of symbols]

 (1) Client computer (2) Root name server (3) Conversion server (4) DNS server (5) Host server (6) Analysis server

Claims (6)

[Claims] When a request for connection to a non-alphanumeric address is issued on the Internet, a conversion script for converting the non-alphanumeric address into a communicable state is attached and returned as a result to a client computer. If a request for connection to the non-alphanumeric address is issued from a client computer, the conversion script is attached to the request to the non-alphanumeric address and a result is sent to the client computer. Returned as
The method of using a non-alphanumeric address, wherein the client computer converts the non-alphanumeric address into a communicable state by the conversion script and issues a new request again. 2. When the client computer issues a non-alphanumeric address, the IP address of the conversion server is changed.
The method according to claim 1, further comprising a server for returning the address as a result. 3. The server according to claim 1, wherein said conversion server is integrated with a server in which a converted address converted by a conversion script sent from said conversion server is registered in advance. Usage of non-alphanumeric addresses as described in. 4. The non-alphanumeric character according to claim 1, wherein a result address returned by the conversion server to the client computer includes a location address where the conversion script is located. Address usage. 5. The non-alphanumeric address according to claim 1, wherein said non-alphanumeric address is converted into an address using communicable characters by said conversion script. how to use. 6. The method according to claim 1, wherein the conversion script converts the non-alphanumeric address into part or all of request data such as form data or cookie data. Usage of the described non-alphanumeric address.