WO2008048061A1 - Procédé de traitement d'une adresse internet en langage natif et support de stockage destiné à sauvegarder un programme pour la mise en oeuvre de ce procédé - Google Patents

Procédé de traitement d'une adresse internet en langage natif et support de stockage destiné à sauvegarder un programme pour la mise en oeuvre de ce procédé Download PDF

Info

Publication number
WO2008048061A1
WO2008048061A1 PCT/KR2007/005116 KR2007005116W WO2008048061A1 WO 2008048061 A1 WO2008048061 A1 WO 2008048061A1 KR 2007005116 W KR2007005116 W KR 2007005116W WO 2008048061 A1 WO2008048061 A1 WO 2008048061A1
Authority
WO
WIPO (PCT)
Prior art keywords
address
server
keyword
client terminal
suffix
Prior art date
Application number
PCT/KR2007/005116
Other languages
English (en)
Inventor
Tae Soo Kim
Jong Ho Won
Hyeon Geun Bang
Suk Moon Lee
Original Assignee
Netpia.Com, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from KR1020060116308A external-priority patent/KR100751889B1/ko
Priority claimed from KR1020060118640A external-priority patent/KR100761978B1/ko
Application filed by Netpia.Com, Inc. filed Critical Netpia.Com, Inc.
Priority to JP2009533250A priority Critical patent/JP2010515112A/ja
Priority to EP07833425A priority patent/EP2076849A1/fr
Priority to CN2007800391893A priority patent/CN101553804B/zh
Publication of WO2008048061A1 publication Critical patent/WO2008048061A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/95—Retrieval from the web
    • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]

Definitions

  • the present invention relates to a method of processing a keyword, and more particularly, to a method of processing a keyword using a DNS suffix.
  • a keyword service is an Internet access service enabling users to use or search for
  • Korean text, English text and numbers such as a person's name, a company name, a product name, a service name, a telephone number, a cellular phone number, a day to be remembered, etc., as an Internet address.
  • keyword service is provided by the present Applicant.
  • a method of providing such a keyword service is disclosed in, for example, Korean
  • the system comprises a database storing keywords and Uniform Resource Locators (URLs) or Internet Protocol (IP) addresses corresponding to the keywords, a Domain Name system (DNS) server and a keyword server.
  • URLs Uniform Resource Locators
  • IP Internet Protocol
  • DNS Domain Name system
  • a text string transferred from a client terminal to the DNS server through a web browser is received, it is determined whether the text string is a URL or a keyword, the text string is transferred to the DNS server when it is a URL, and the text string is transferred to the keyword server when it is a keyword, thereby processing a keyword.
  • a conventional OS may not transfer an input access word to the DNS server, for example, when the input access word is not a fully-qualified domain name.
  • the keyword cannot be processed.
  • Internet Explorer 7.0 when a DNS query fails, e.g., because an input access word is not a fully-qualified domain name, the DNS query is changed into a search query to a search website, e.g., "search.msn.com", and transferred to the corresponding search server, and the access word is not transferred to the DNS server. Therefore, when the plug-in program for processing a keyword is not installed, it is not possible to use the keyword. Disclosure of Invention Technical Problem
  • OS Operating System
  • DNS Domain Name system
  • IP Internet Protocol
  • Text string is a generic term for groups of characters input into a client terminal to access a webpage.
  • the term indicates general URLs, e.g., "kipo.go.kr”, “DDD.kr” and “DDD.DD”, keywords other than URLs, e.g., "DDD” and "DDD”, etc., that can be input into an address window or a search window of a web browser.
  • URL denotes a directory, a file, etc., as well as a domain name, e.g.,
  • IP address denotes a physical address for computer systems connected with the Internet to identify each other that conforms to Internet Protocol version 4 (IPv4) regulations, Internet Protocol version 6 (IPv6) regulations, and so on.
  • IPv4 Internet Protocol version 4
  • IPv6 Internet Protocol version 6
  • a method of processing a keyword by which a text string input into an address window of a web browser of a client terminal is processed to function as an Internet address, comprises: a query message reception step of receiving a query message including the text string transferred from the client terminal to a DNS server; a keyword determination step of determining whether or not the text string is a keyword using a suffix included in the query message; and a server address return step of transferring a URL or an IP address of a Native Language Internet Address (NLIA) server converting the text string into an Internet address to the client terminal when it is determined that the text string is a keyword.
  • NLIA Native Language Internet Address
  • the keyword determination step it is checked whether a suffix coinciding with the suffix included in the query message exists in a suffix database storing at least one suffix except an official domain name extension processed by a DNS system, and it is determined that the text string is a keyword when the suffix of the query message exists in the suffix database.
  • a method of processing a keyword by which a text string input into an address window of a web browser of a client terminal is processed to function as a search word, comprises: a query message reception step of receiving a query message including the text string transferred from the client terminal to a DNS server; a keyword determination step of determining whether or not the text string is a keyword using a suffix included in the query message; and a server address return step of transferring a URL or an IP address of a search server to the client terminal when it is determined that the text string is a keyword.
  • the keyword determination step it is checked whether a suffix coinciding with the suffix included in the query message exists in a suffix database storing at least one suffix except an official domain name extension processed by a DNS system, and it is determined that the text string is a keyword when the suffix of the query message exists in the suffix database.
  • the search server may need to have a receiving program to receive the text string input into the client terminal and return a search result when the client terminal accesses the search server using the URL or IP address of the search server.
  • the suffix included in the query message may be assigned to the client terminal during a process in which a Dynamic Host Configuration Protocol (DHCP) server assigns an IP address through DHCP, and may vary according to DHCP servers or groups of a plurality of DHCP servers.
  • DHCP Dynamic Host Configuration Protocol
  • the suffix included in the query message may be assigned to the client terminal while a terminal configuration program changes a terminal configuration.
  • the suffix may vary according to terminal configuration programs or groups of a plurality of terminal configuration programs.
  • the keyword determination step may further comprise the steps of: transferring the query message to the DNS server when the suffix included in the query message does not exist in the suffix database; and receiving a response from the DNS server and determining that the text string is a keyword when the response is an error message.
  • a method of processing a keyword by which a text string input into an address window of a web browser of a client terminal is processed to function as an Internet address, comprises: a step of receiving a response transferred from a DNS server to the client terminal in response to a query message including the text string input into the address window of the web browser of the client terminal and transferred to the DNS server; a step of determining that the text string is a keyword when the response is an error message; and a server address return step of returning a URL or an IP address of an NLIA server converting the text string into an Internet address to the client terminal when it is determined that the text string is a keyword.
  • a system for processing a keyword using a suffix comprises: an NLIA server database for storing a URL or an IP address of an NLIA server; an NLIA database for matching an address keyword with a URL or an IP address and storing the address keyword and the URL or IP address; a relay server accessed using, as a part of an Internet address, a suffix set by a program executed in a client terminal, a user or a DHCP server, and when a query including an input keyword to which the set suffix is added is received from the client terminal, extracting the URL or IP address of the NLIA server from the NLIA server database and returning the URL or IP address to the client terminal; and the NLIA server for receiving the query including the input keyword from the client terminal, and when an address keyword matching the input keyword exists in the NLIA database, returning a URL or an IP address corresponding to the address keyword to the client terminal.
  • the system may further comprise a relay NLIA database for matching an address keyword with a URL or an IP address and storing the address keyword and the URL or IP address, and the relay server may search the relay NLIA database, transfer a URL or an IP address corresponding to the address keyword matching the input keyword included in the query to the client terminal when the address keyword matching the input keyword exists in the relay NLIA database, and extract and return the URL or IP address of the NLIA server to the client terminal when the address keyword matching the input keyword does not exist in the relay NLIA database.
  • a relay NLIA database for matching an address keyword with a URL or an IP address and storing the address keyword and the URL or IP address
  • the relay server may search the relay NLIA database, transfer a URL or an IP address corresponding to the address keyword matching the input keyword included in the query to the client terminal when the address keyword matching the input keyword exists in the relay NLIA database, and extract and return the URL or IP address of the NLIA server to the client terminal when the address keyword matching the input keyword does not exist in
  • the NLIA server database may store URLs or IP addresses of a plurality of NLIA servers, and the relay server may classify the query input from the client terminal and return a URL or an IP address of an NLIA server which may vary according to the classified query to the client terminal.
  • a system for processing a keyword using a suffix comprises: a search server database for storing a URL or an IP address of a search server; and a relay server accessed using, as a part of an Internet address, a suffix set by a program executed in a client terminal, a user or a DHCP server, and when a query including an input keyword to which the set suffix is added is received from the client terminal, extracting the URL or IP address of the search server from the search server database and then returning the URL or IP address to the client terminal.
  • the system may further comprise a search keyword database for storing an address keyword, and the relay server may search the search keyword database, and when a search keyword matching the input keyword exists in the search keyword database, search the search server database and return a URL or an IP address of a specific search server to the client terminal.
  • a search keyword database for storing an address keyword
  • the relay server may search the search keyword database, and when a search keyword matching the input keyword exists in the search keyword database, search the search server database and return a URL or an IP address of a specific search server to the client terminal.
  • the search server database may store URLs or IP addresses of a plurality of search servers, and the relay server may classify the query input from the client terminal and return a URL or an IP address of a search server which may vary according to the classified query to the client terminal.
  • a method of processing a keyword using a suffix comprises the steps of: accessing a relay server using, as a part of an Internet address, a suffix set by a specific program executed in a client terminal, a user or a DHCP server, and when a query to which the set suffix is added is received from the client terminal, extracting a URL or an IP address of an NLIA server from an NLIA server database storing URLs or IP addresses of NLIA servers, and returning the URL or IP address to the client terminal; and receiving, at the NLIA server having an NLIA database matching an address keyword with a URL or an IP address and storing the address keyword and the URL or IP address, the query from the client terminal accessing the NLIA server using the extracted URL or IP address of the NLIA server, searching the NLIA database, and when an address keyword matching a keyword included in the query exists in the NLIA database, returning a URL or an IP address c orresponding to the address
  • a method of processing a keyword using a suffix comprises the steps of: receiving, at a relay server accessed using, as a part of an Internet address, a suffix set by a specific program executed in a client terminal, a user or a DHCP server, a query including the set suffix from the client terminal; searching, at the relay server, an NLIA server database storing a URL or an IP address of an NLIA server to extract the URL or IP address of the NLIA server; and returning, at the relay server, the extracted URL or IP address of the NLIA server to the client terminal.
  • a method of processing a keyword using a suffix comprises the steps of: when a relay server accessed using, as a part of an Internet address, a suffix set by a specific program executed in a client terminal, a user or a DHCP server receives a query including the set suffix from the client terminal, determining that the query is about a keyword; searching, at the relay server, a search server database storing a URL or an IP address of a search server to extract a URL or an IP address of a specific search server; and returning, at the relay server, the extracted URL or IP address of the search server to the client terminal.
  • a recording medium storing a program for executing a method of processing a keyword using a suffix is provided.
  • a method of processing a keyword using a suffix according to the present invention can be implemented in a computer-readable recording medium in the form of computer code.
  • the computer-readable recording medium may be any recording device storing data that can be read by computer systems.
  • the computer-readable recording medium may be a read-only memory
  • ROM read-only memory
  • RAM random-access memory
  • CD-ROM compact disk read-only memory
  • magnetic tape a hard disk, a floppy disk, a mobile storage device, a nonvolatile memory (flash memory), an optical data storage device, and so on.
  • the recording medium may be carrier waves, e.g., transmission over the Internet.
  • the above-described method for processing a keyword using a suffix according to the present invention can be implemented as a proxy module in a DNS server and may also be stored in any recording medium to perform the method during a process in which a keyword is transferred from a client terminal to the DNS server.
  • a text string i.e., a keyword
  • a text string input into an address window may be a keyword other than a URL or an IP address.
  • a specific web browser or an OS may not transfer the keyword to a DNS server according to conventional art.
  • the keyword is transferred to a DNS server so that the keyword can function as an Internet address or a search word.
  • a DNS server local DNS server
  • system management for a keyword service can be facilitated, and various modifications can be made independent of the DNS server.
  • a service category can be expanded and various forms of cooperation can be established.
  • a method of assigning a specific suffix using a DHCP server of an ISP among the exemplary embodiments of the present invention, it is possible to use a text string input into an address window as an Internet address or a search word without installing a program on a client, classify service according to DHCP servers, and perform expanded management using the classified service.
  • an easily managed suffix is selected and used. Thus, there is no actual limit to expansion or change in determining whether or not a text string is a keyword or providing an additional service.
  • FIG. 1 illustrates a constitution of a keyword service system according to an exemplary embodiment of the present invention
  • FIG. 2 is a flowchart showing a method of processing a keyword according to an exemplary embodiment of the present invention
  • FIGS. 3 and 4 illustrate network configuration check screens of a case in which a
  • FIG. 5 illustrates a constitution of a keyword service system according to another exemplary embodiment of the present invention
  • FIG. 6 illustrates a screen in which a DNS suffix is manually set in a client terminal
  • FIG. 7 is a flowchart showing a method of processing a keyword according to another exemplary embodiment of the present invention
  • FIG. 8 is a flowchart showing a method of processing a keyword according to yet another exemplary embodiment of the present invention
  • FIG. 9 illustrates a constitution of a keyword service system according to yet another exemplary embodiment of the present invention.
  • FIG. 10 illustrates a constitution of a keyword service system according to yet another exemplary embodiment of the present invention
  • FIG. 10 is a flowchart showing a method of processing a keyword according to still another exemplary embodiment of the present invention.
  • FIG. 11 is a flowchart showing a method of processing a keyword according to still another exemplary embodiment of the present invention.
  • FIG. 12 is a flowchart showing a method of processing a keyword according to still another exemplary embodiment of the present invention. Mode for the Invention
  • FIG. 1 illustrates a constitution of a keyword service system according to an exemplary embodiment of the present invention.
  • a client terminal 100 is connected with a Domain Name system
  • DNS Native Language Internet Address
  • NLIA Native Language Internet Address
  • the NLIA server 200 is connected with a database 250, and the DNS server 140 has a proxy module 142.
  • a keyword e.g., "DDD”
  • URL Uniform Resource Locators
  • the proxy module 142 is included in the DNS server 140.
  • the proxy module 142 may be implemented in a network path between the client terminal 100 and the DNS server 140 in the form of a server, a module, and so on.
  • the proxy module 142 having the above mentioned functions can be implemented in various ways regardless of its form. For convenience, descriptions below will be based on the proxy module 142 illustrated in FIG. 1.
  • the proxy module 142 checks whether or not the text string is a keyword using a suffix included in the query message. More specifically, the proxy module 142 has a suffix database storing at least one suffix except an official domain name extension processed by a DNS system, and checks whether a suffix coinciding with the suffix included in the query message exists in the suffix database. When it is determined that the suffix of the query message exists in the suffix database, the proxy module 142 determines that the text string is a keyword.
  • Suffixes stored in the suffix database are, for example, ".realname", ".keyword”,
  • a suffix by which a text string is considered as a keyword may be constantly found, and the suffix database may be updated with the suffix. According to such a method, it is possible to stably determine whether or not a text string is a keyword by simply changing the suffix database even when a system, such as an Operating System (OS), etc., is changed, a configuration is changed by an Internet service provider (ISP), and so on.
  • OS Operating System
  • ISP Internet service provider
  • a suffix may be inserted in a text string input into a web browser by a web browser or an OS.
  • a suffix may be inserted in "www.yahoo.com”, “yahoo.com” following “www.” may be a suffix, and in "DD1.DD2", “DD2” may be a suffix.
  • DNS suffix function that can be used in a commercialized OS, such as DOS, Linux, Windows 3.0, Windows 98, Windows 2000, Windows XP, etc.
  • a predetermined suffix may be inserted when a text string is input into a web browser.
  • the client terminal [61] According to an exemplary embodiment of the present invention, the client terminal
  • a Dynamic Host Configuration Protocol (DHCP) server may assign the predetermined suffix to the client terminal 100 during a process of assigning an Internet Protocol (IP) address through DHCP.
  • IP Internet Protocol
  • a terminal configuration program may assign a specific suffix to the client terminal 100 while changing a terminal configuration. Different suffixes may be assigned according to terminal configuration programs or groups of a plurality of terminal configuration programs.
  • an Internet address i.e., a URL or an IP address
  • the NLIA server 200 converting a text string into an Internet address is transferred to the client terminal 100.
  • the client terminal 100 receiving the Internet address of the NLIA server 200 transfers the text string to the NLIA server 200, and the NLIA server 200 receives the text string and processes an Internet address corresponding to the text string. More specifically, the NLIA server 200 searches for the text string in the NLIA database 250 matching an address keyword with an Internet address and storing the address keyword and the Internet address. When it is determined that an address keyword matching the text string exists in the NLIA database 250, the NLIA server 200 transfers an Internet address, i.e., a URL or an IP address, corresponding to the address keyword to the client terminal 100. The client terminal 100 receiving the Internet address accesses the corresponding webpage.
  • an Internet address i.e., a URL or an IP address
  • address keywords and Internet addresses corresponding to the keywords are previously matched and stored. For example, an address keyword "DDD(BlueHouse)" and an Internet address "www.president.go.kr" are matched with each other and stored. Meanwhile, when an address keyword matching the text string does not exist in the NLIA database 250, the NLIA server 200 converts the text string into a search query to a specific search server and transfers the search query to the client terminal 100. The client terminal 100 receiving the search query accesses the specific search server and the corresponding webpage.
  • the NLIA server 200 may transfer an Internet address, i.e., a URL or an IP address, of a specific search server or a search query to the client terminal 100 when an address keyword matching the text string does not exist in the NLIA database 250.
  • an Internet address i.e., a URL or an IP address
  • FIG. 2 is a flowchart showing a method of processing a keyword according to an exemplary embodiment of the present invention.
  • a query message including the text string is transferred from the client terminal 100 to the DNS server 140, and the proxy module 142 of the DNS server 140 receives the query message (step 101).
  • the proxy module 142 of the DNS server 140 determines whether or not the text string is a keyword using a suffix included in the received query message. More specifically, the proxy module 142 checks whether a suffix coinciding with the suffix included in the query message exists in a suffix database storing at least one suffix except an official domain name extension processed by a DNS system. When a suffix coinciding with the suffix included in the query message exists in the suffix database, the proxy module determines that the text string is a keyword (step 103).
  • a URL or an IP address of the NLIA server 200 converting a text string into an Internet address is transferred to the client terminal 100 (step 105), and then the client terminal 100 accesses the NLIA server 200 (step 107).
  • the query message is transferred to the DNS server 140 (step 110). Subsequently, a response message is received from the DNS server 140 to which the query message is transferred, and it is determined whether or not the text string is an error message (step 112). When the response message is not an error message, the proxy module 142 of the DNS server 140 does not process the received response message (step 114). On the other hand, when the response message is an error message, it is determined that the text string is a keyword, and the process proceeds to step 105.
  • a method by which a client terminal adds a predetermined suffix to a text string will be described below with reference to a case in which a terminal configuration program changes a terminal configuration and another case in which an IP address is assigned by a DHCP server.
  • a terminal configuration program may be installed together with another program, such as a toolbar, etc., or may function as a part of another program to change a terminal configuration of the client terminal 100.
  • the terminal configuration program may be installed on the client terminal 100 in various ways without limitation.
  • the terminal configuration program may be downloaded from the NLIA server 200 or a specific website.
  • the terminal configuration program functions to assign a predetermined DNS suffix to the client terminal.
  • the DNS suffix may be, for example, "realname", “nlia” and, "nlia.com”.
  • a DNS suffix may be assigned using a function of a commercialized OS, such as DOS, Linux, Windows 3.0, Windows 98, Windows 2000, Windows XP, etc.
  • FIGS. 3 and 4 illustrate network configuration check screens of Windows XP in a case of a DNS suffix not being set and in another case of a DNS suffix "realname" being set, respectively.
  • FIG. 3 "Connection-specific DNS Suffix" is not set, and in FIG. 4, "Connection- specific DNS Suffix” is set to "realname”.
  • a DNS suffix indicates all of a main DNS suffix, a connection DNS suffix, and a DNS suffix input into a suffix search list.
  • FQDN Fully- Qualified Domain Name
  • An FQDN denotes a domain name including a final host name. For example, an FQDN "www.yahoo.com.” is divided into a host name "www" and a domain name "yahoo.com”.
  • FIG. 5 illustrates a constitution of a keyword service system according to another exemplary embodiment of the present invention, in which a DHCP server 150 is included.
  • a client terminal 100 receives an IP address using the DHCP server 150 from an ISP
  • network data including an IP address of the client terminal 100, a subnet mask, a DNS suffix, a gateway, an IP address of a DNS server, etc.
  • a predetermined text string e.g., "realname”
  • the assigned DNS suffix is used as described above.
  • a DNS suffix may be manually set by a user in a client terminal.
  • FIG. 6 illustrates a screen in which a DNS suffix is manually set in a client terminal.
  • FIG. 6 illustrates a method of setting a DNS suffix using "DNS suffix" function of, for example, Internet Explorer 6.0 that is a commercialized web browser of Microsoft Corporation.
  • FIG. 7 is a flowchart showing a method of processing a keyword according to another exemplary embodiment of the present invention.
  • a DNS suffix is assigned to the client terminal 100 (step
  • the step of assigning a DNS suffix to the client terminal 100 may be performed by a terminal configuration program installed on the client terminal 100, or the DNS suffix may be assigned together with an IP address when an ISP assigns IP addresses to respective client terminals using the DHCP server 150.
  • OS determines whether the text string is a fully-qualified name (step 205). Such a determination process is performed by, for example, a basic function of the OS.
  • the OS checks whether "DNS suffix" function has been set.
  • "DNS suffix" function has been set, the OS adds a set DNS suffix to the text string and transfers the text string to the DNS server 140 (step 209).
  • "DNS suffix" function may use a general function of an OS. In the present invention, it is possible to process a keyword using "DNS suffix" function at an OS level.
  • a general OS such as Windows XP, etc.
  • the general OS directly transfers the text string to the DNS server 140 (step 207).
  • the DNS server 140 determines whether the suffix included in a transferred query message exists in a suffix database (step 211). The determination is performed by whether a suffix corresponding to the DNS suffix exists in the suffix database. For example, when a DNS suffix "realnmae" is assigned to the client terminal 100, it is determined whether or not the suffix "realname" exists in the suffix database.
  • the DNS server 140 performs a general process (step 213).
  • the DNS server 140 determines that the text string is a keyword and transfers an Internet address of an NLIA server 200 to the client terminal 100 (step 215).
  • steps 110 and 112 of FIG. 2 may be performed when it is determined that the suffix does not exist in the suffix database.
  • the client terminal 100 accesses the NLIA server 200 using the transferred Internet address of the NLIA server 200 and transfers the text string to the NLIA server 200 (step 217).
  • the DNS server 140 may transfer the text string input into the client terminal 100 except the DNS suffix or the text string including the DNS suffix.
  • the NLIA server 200 searches for an Internet address corresponding to the text string except the DNS suffix in an NLIA database 250.
  • the NLIA server 200 checks whether an address keyword corresponding to the text string exists in the NLIA database matching an address keyword and an Internet address and storing the address keyword and the Internet address (step 219). When it is determined that an address keyword matching the text string exists in the NLIA database, the NLIA server 200 returns an Internet address corresponding to the address keyword to the client terminal 100 (step 221). The client terminal 100 can access the corresponding webpage using the received Internet address, i.e., a URL or an IP address. Meanwhile, when it is determined that an address keyword matching the text string does not exist in the NLIA database 250, the NLIA server 200 converts the text string into a search query to a specific search server and transfers the search query to the client terminal 100.
  • FIG. 8 is a flowchart showing a method of processing a keyword according to yet another exemplary embodiment of the present invention.
  • a text string is input into an address window of a web browser of the client terminal 100, and a query message including the text string is transferred from the client terminal 100 to the DNS server 140 (step 301). Then, the DNS server 140 transfers a response message to the client terminal 100 in response to the query message.
  • the proxy module 142 of the DNS server 140 receives the response message (step 303).
  • the proxy module 142 of the DNS server receiving the response message determines whether the response message is an error message (step 305). When it is determined that the response message is not an error message and the response message is processed as it is without an additional process (step 311).
  • this exemplary embodiment is described with reference to a case in which a DNS suffix is assigned to a client terminal using a method in which a plug-in program installed on the client terminal inputs a value into a registry and another case in which a DNS suffix is assigned to a client terminal together with an IP address when an ISP assigns IP addresses to respective client terminals through DHCP.
  • the above-described exemplary embodiments relate to a method of checking whether a suffix coinciding with a suffix included in a text string transferred from a client terminal exists in a suffix database, and processing the text string as a keyword when the suffix exists in the suffix database.
  • the method has many advantages in comparison with conventional art but cannot satisfy various requirements of an ISP, an administrator of a name server, etc.
  • a proxy module of a DNS server (local
  • FIG. 9 illustrates a constitution of a keyword service system according to yet another exemplary embodiment of the present invention.
  • a client terminal 1100 is connected with a DNS server 1150, an
  • the NLIA server 1200 is connected with an NLIA database 1210, and the DNS server 1150 is connected with a relay server 1160.
  • the DNS server 1150 performs a resolution process using the query message according to general resolution procedures.
  • the resolution process is for obtaining a URL or an IP address corresponding to the query message, and the URL or IP address is transferred to the client terminal 1100.
  • the DNS server 1150 transfers a query to the relay server 1160 using a suffix included in a text string during the resolution process, and the relay server 1160 determines that the text string is a keyword when the query is received. This will be described in further detail below.
  • the DNS server 1150 first requests a root name server (not shown in the drawing) for data.
  • the DNS server 1150 repeatedly inquires to the root name server and secondary name servers of the root name server until a result desired by the client terminal 1100 is received. For example, when the client terminal 1100 inquires about "www.abc.com", the DNS server 1150 inquires of a root name server (not shown) about a name server managing ".com” and then inquires of the first secondary name server managing ".com” about an IP address of a name server managing "abc.com” according to a query result value received from the root name server.
  • the first secondary name server informs the DNS server 1150 of the IP address of the second secondary name server managing "abc.com". And, the DNS server 1150 accesses the second secondary name server to obtain information on IP address of "www.abc.com” and transfer the information to the client terminal 1100.
  • a query is transferred to the relay server 1160 based on a general resolution technique of the DNS server 1150 using a suffix as a part of an Internet address.
  • a suffix may be manually set by a user, set in a client terminal by a DHCP server, or set by a terminal configuration change program.
  • a predetermined condition is satisfied by a web browser or an OS after a suffix is set, the suffix is inserted in an input text string.
  • DNS suffix "DNS suffix" function that can be used in a commercialized OS, e.g., DOS, Linux, Windows 3.0, Windows 98, Windows 2000, Windows XP, etc.
  • a predetermined suffix can be inserted when a text string is input into a web browser.
  • the inserted suffix serves to render the DNS server 1150 to send a query to the relay server 1160.
  • a predetermined condition e.g., a keyword
  • the suffix is added to the text string, and the text string is transferred.
  • the DNS server 1150 sends a query to the relay server 1160 of "nlias.net” according to a general resolution process.
  • a suffix may have a service identifier according to an ISP and a program type or an identifier according to an area and a language.
  • a suffix e.g., "1. nlias.net”, “2.nlias.net” and “kt.nlias.net” has a form of "a service identifier, a relay server domain”.
  • Different service identifiers may be set according to a name of an ISP and a type of a terminal configuration program assigning a suffix.
  • a suffix e.g., "kr.nlias.net and "jp.nlias.net” has a form of "a local/language identifier, a relay server domain”.
  • the client terminal 1100 may add a predetermined suffix to a keyword.
  • the client terminal 1100 may determine whether or not an input text string includes ".”, whether or not the input text string is a fully-qualified name, etc., using a function of a web browser, e.g., above-described "DNS suffix" function, and add a suffix when the input text string does not have a general URL form.
  • the predetermined suffix may be assigned to the client terminal 1100 during a process in which a DHCP server assigns an IP address through DHCP.
  • a terminal configuration program may assign a specific suffix to the client terminal 1100 while changing a terminal configuration.
  • the suffix may be assigned differently according to terminal configuration programs or groups of a plurality of terminal configuration programs.
  • a user may change a configuration of his/her client terminal 1100 to add a suffix.
  • the punycode is a method of changing a non- ASCII code character with an ASCII code character, e.g., xn— BCQTESQRF, to use non- ASCII code characters in a conventional Internet system based on the ASCII code.
  • a relay server will be described in detail below.
  • the relay server 1160 processes the received query using a method described below.
  • the relay server 1160 has an NLIA server database
  • the relay server 1160 extracts a URL or an IP address of the NLIA server 1200 from the NLIA server database 1182 and returns the URL or IP address to the client terminal 1100.
  • the relay server 1160 determines that the received query is a keyword and processes it. Since the relay server 1160 mechanically responds to all queries, the processing speed increases. A suffix is added to the input keyword by a program executed in the client terminal 1100, a user or a DHCP server, and the client terminal 1100 accesses the corresponding webpage using the keyword as a part of an Internet address.
  • the relay server 1160 further has a relay NLIA database 1184 in which address keywords and URLs or IP addresses are matched and stored.
  • the relay server 1160 searches the relay NLIA database 1184, and when an address keyword matching the input keyword included in the query exists in the relay NLIA database 1184, transfers a URL or an IP address corresponding to the address keyword to the client terminal 1100.
  • the relay server 1160 may extract a URL or an IP address of the NLIA server 1200 from the NLIA database 1182 and return the URL or IP address to the client terminal.
  • the relay server 1160 has a search server database
  • the client terminal 1100 accesses the relay server 1160 using, as a part of an Internet address, a suffix set by a program executed in the client terminal 1100, a user or a DHCP server, and transfers a query including an input keyword to which the set suffix is added to the relay server 1160. Then, the relay server 1160 extracts a URL or an IP address of the search server 1300 from the search server database 1186 and return the URL or IP address to the client terminal 1100.
  • the relay server 1160 may have a search keyword database 1188 storing search keywords and search the search keyword database 1188.
  • the relay server 1160 may search the search server database 1186 and return a URL or an IP address of a specific search server to the client terminal 1100.
  • the relay server 1160 may extract the URL or IP address of the NLIA server 1200 from the NLIA server database 1182 and return the URL or IP address to the client terminal 1100.
  • the relay server 1160 may add various functions using "keyword” section.
  • the relay server 1160 may store URLs or IP addresses of a plurality of NLIA servers in the NLIA server database 1182.
  • the relay server 1160 may classify the query input from the client terminal 1100, for example, according to an identifier included in the query and return a URL or an IP address of an NLIA server which may vary according to the classified query to the client terminal 1100.
  • the relay server 1160 may store URLs or IP addresses of a plurality of search servers in the search server database 1186.
  • the relay server 1160 may classify the query input from the client terminal 1100, for example, according to an identifier included in the query and return a URL or an IP address of a search server which may vary according to the classified query to the client terminal 1100.
  • the NLIA server 1200 searches the NLIA database 1210 in which address keywords and URLs or IP addresses are matched and stored to check whether an address keyword matching the input text string exists in the NLIA database 1210.
  • the NLIA server 1200 transfers an Internet address, i.e., a URL or an IP address, corresponding to the address keyword to the client terminal 1100.
  • the client terminal 1100 receiving the Internet address accesses the corresponding webpage.
  • the NLIA server 1200 may return the Internet address of the search server 1300 to the client terminal 1100.
  • the NLIA server 1200 may have a search keyword database (not shown).
  • the NLIA server may check whether a search keyword matching the input text string, i.e., the keyword, exists in the search keyword database, and transfer the Internet address of the designated search server 1300 to the client terminal 1100 when it is checked that a search keyword matching the input text string exists in the search keyword database.
  • the NLIA server 1200 may return an Internet address of a designated search server which may vary according to the service identifiers.
  • the NLIA server 1200 may convert an Internet address, i.e., a URL or an IP address, of a specific search server into a query and transfer the query to the client terminal 1100.
  • the NLIA server 1200 may inverse-transform the punycode.
  • the relay server 1160 or the NLIA server 1200 returns the Internet address of the search server 1300 to the client terminal 1100, the client terminal 1100 accesses the search server 1300.
  • the search server 1300 may provide a search list corresponding to the input text string, i.e., keyword.
  • the relay server 1160 directly responds to the search server 1300, a value transferred using host information other than a search query is processed. This is because a field containing a value input by a user must be analyzed to extract the value during a data transfer process in order to obtain the value input by the user when the relay server 1160 returns the Internet address, i.e., the IP address, of the search server 1300.
  • 1300 may inverse-transform the punycode.
  • FIG. 10 is a flowchart showing a method of processing a keyword according to still another exemplary embodiment of the present invention.
  • a domain, e.g., "nlias.net" of the relay server 1160 is assigned as a suffix (step 1101).
  • an identifier as well as the domain may be added to the suffix as described above.
  • the DNS server 1150 inquire, i.e., access, to the specific relay server 1160 using the suffix when the DNS server 1150 inquires according to the general resolution technique.
  • the query is transferred to the relay server 1160 using the suffix set by a program executed in the client terminal 1100, a user or a DHCP server.
  • step 1103 When a text string is input into an address window of a web browser of the client terminal 1100 (step 1103), the client terminal 1100 adds the suffix to the text string and transfers a query message to the DNS server 1150.
  • the DNS server 1150 receiving the query message performs a resolution process (step 1105).
  • the process in which the client terminal 1100 adds the suffix to the text string is performed by a basic function of an OS. More specifically, the OS determines whether or not the input text string is a fully-qualified name. When it is determined that the input text string is not a fully-qualified name, the OS checks whether "DNS suffix" function is set. When “DNS suffix" function is set, the OS adds the set DNS suffix to the text string and transfers the text string to the DNS server 1150.
  • "DNS suffix" function can use a general function of an OS, and a keyword can be processed using "DNS suffix" function in an OS level according to an exemplary embodiment of the present invention.
  • a general OS such as Windows XP, etc.
  • the OS directly transfers the text string to the DNS server.
  • the query is transferred to the relay server 1160 due to the added suffix, and the relay server 1160 receives the query (step 1107).
  • the relay server 1160 receiving the query returns an Internet address of the NLIA server 1200 or the search server 1300 to the client terminal 1100 (step 1109).
  • the relay server 1160 determines and processes the query as a keyword.
  • the client terminal 1100 receiving the Internet address accesses the NLIA server
  • the NLIA server 1200 checks whether an address keyword matching the input text string, i.e., the keyword, exists in the NLIA database 1210.
  • the NLIA server 1200 transfers an Internet address, i.e., a URL or an IP address, corresponding to the address keyword to the client terminal 1100.
  • the client terminal 1100 receiving the Internet address accesses the corresponding webpage.
  • the NLIA server 1200 returns the Internet address of the search server 1300 to the client terminal 1100.
  • the relay server 1160 returns the Internet address of the search server 1300 to the client terminal 1100
  • the client terminal 1100 accesses the search server 1300
  • the search server 1300 provides a search list corresponding to the input text string, i.e., the keyword.
  • FIG. 11 is a flowchart showing a method of processing a keyword according to still another exemplary embodiment of the present invention. For convenience, differences from the exemplary embodiment of FIG. 7 will be mainly described below.
  • a domain of the relay server 1160 is assigned as a suffix (step 1201).
  • a text string is input into an address window of a web browser of the client terminal 1100 (step 1203)
  • the client terminal 1100 adds the suffix to the text string and transfers a query message to the DNS server 1150.
  • the DNS server 1150 receiving the query message performs a resolution process (step 1205).
  • the query is transferred to the relay server 1160 due to the added suffix, and the relay server 1160 receives the query (step 1207).
  • the relay server 1160 checks whether an address keyword matching the input text string, i.e., the keyword, exists in the relay NLIA database 1184 in which address keywords and URLs or IP addresses are matched and stored (step 1209). When it is checked that an address keyword matching the text string exists in the relay NLIA database 1184, the relay server 1160 transfers an Internet address, i.e., a URL or an IP address, corresponding to the address keyword to the client terminal 1100 (step 1211). The client terminal 1100 receiving the Internet address accesses the corresponding webpage (step 1213).
  • the relay server 1160 returns the Internet address of the NLIA server 1200 or the search server 1300 to the client terminal 1100 (step 1215).
  • the client terminal 1100 receiving the Internet address accesses the NLIA server 1200 or the search server 1300 (step 1216).
  • FIG. 12 is a flowchart showing a method of processing a keyword according to still another exemplary embodiment of the present invention. For convenience, differences from the exemplary embodiment of FIG. 10 will be mainly described below.
  • a domain of the relay server 1160 is assigned as a suffix (step 1301).
  • the client terminal 1100 adds the suffix to the text string and transfers a query message to the DNS server 1150.
  • the DNS server 1150 receiving the query message performs a resolution process (step 1305).
  • the query is transferred to the relay server 1160 due to the added suffix, and the relay server 1160 receives the query (step 1307).
  • the relay server 1160 receiving the query checks whether a search keyword matching the input text string exists in the search keyword database 1188 storing search keywords (step 1309).
  • the relay server 1160 transfers a URL or an IP address of a specific search server to the client terminal 1100 (step 1311).
  • the client terminal 1100 receiving the URL or IP address accesses the corresponding webpage.
  • the relay server 1160 extracts a URL or an IP address of the NLIA server 1200 from the NLIA server database 1182 and returns the URL or IP address to the client terminal 1100 (step 1315).
  • this exemplary embodiment is described with reference to a case in which a DNS suffix is assigned to a client terminal using a method in which a plug-in program installed on the client terminal inputs a value into a registry and another case in which a DNS suffix is assigned to a client terminal together with an IP address when an ISP assigns IP addresses to respective client terminals through DHCP.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne un procédé et un système de traitement d'un mot-clé au moyen d'un suffixe et un support d'enregistrement assurant le stockage d'un programme pour la mise en oeuvre de ce procédé et de ce système. Le procédé comprend une étape de réception de message d'interrogation consistant à recevoir un message d'interrogation comprenant une chaîne de texte transférée d'un terminal client à un serveur de système de noms de domaine (DNS), une étape de détermination de mot-clé consistant à déterminer si la chaîne de texte est un mot-clé au moyen d'un suffixe inclus dans le message d'interrogation, ainsi qu'une étape de retour d'addresse de serveur consistant à transférer au terminal client une adresse URL ou une adresse IP d'un serveur d'adresses Internet en langage natif (NLIA) convertissant la chaîne de texte en une adresse Internet ou en un mot de recherche, s'il est déterminé que la chaîne de texte est un mot-clé.
PCT/KR2007/005116 2006-10-21 2007-10-19 Procédé de traitement d'une adresse internet en langage natif et support de stockage destiné à sauvegarder un programme pour la mise en oeuvre de ce procédé WO2008048061A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
JP2009533250A JP2010515112A (ja) 2006-10-21 2007-10-19 キーワードの処理方法及びそれを実行するためのプログラムを記録した記録媒体
EP07833425A EP2076849A1 (fr) 2006-10-21 2007-10-19 Procédé de traitement d'une adresse internet en langage natif et support de stockage destiné à sauvegarder un programme pour la mise en oeuvre de ce procédé
CN2007800391893A CN101553804B (zh) 2006-10-21 2007-10-19 处理本土语言因特网地址的方法及保存执行该方法的程序的存储介质

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
KR10-2006-0102620 2006-10-21
KR20060102620 2006-10-21
KR1020060116308A KR100751889B1 (ko) 2006-10-21 2006-11-23 자국어 인터넷주소의 처리 방법 및 이를 실행하기 위한프로그램을 기록한 기록매체
KR10-2006-0116308 2006-11-23
KR10-2006-0118640 2006-11-28
KR1020060118640A KR100761978B1 (ko) 2006-11-28 2006-11-28 키워드 처리 시스템, 키워드 처리 방법 및 이를 실행하기위한 프로그램을 기록한 기록매체

Publications (1)

Publication Number Publication Date
WO2008048061A1 true WO2008048061A1 (fr) 2008-04-24

Family

ID=40691359

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/005116 WO2008048061A1 (fr) 2006-10-21 2007-10-19 Procédé de traitement d'une adresse internet en langage natif et support de stockage destiné à sauvegarder un programme pour la mise en oeuvre de ce procédé

Country Status (4)

Country Link
EP (1) EP2076849A1 (fr)
JP (1) JP2010515112A (fr)
CN (1) CN101553804B (fr)
WO (1) WO2008048061A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103188257A (zh) * 2011-12-28 2013-07-03 北京东土科技股份有限公司 一种实现dhcp客户端与服务器安全交互的装置
RU2679549C2 (ru) * 2013-11-11 2019-02-11 Адаллом, Инк. Брокер и прокси обеспечения безопастности облачных услуг

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR19980064882A (ko) * 1998-06-01 1998-10-07 조관현 인터넷 주소의 자국어 표기 서비스 시스템
US6578088B2 (en) * 1996-08-29 2003-06-10 Hitachi, Ltd. Automatic address distributing system
EP1333647A2 (fr) * 2002-01-29 2003-08-06 Samsung Electronics Co., Ltd. Procédé et appareil pour la gestion de noms de domaines
US7020602B1 (en) * 2000-08-21 2006-03-28 Kim Ki S Native language domain name registration and usage

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2000020444A (ja) * 1998-06-26 2000-01-21 Bariafurii:Kk 機能拡張装置および機能拡張方法ならびに機能拡張プログラムを記録した記録媒体
CN1367417A (zh) * 2001-01-21 2002-09-04 黄宏权 一种通用中英文数码网址或域名
WO2005067406A2 (fr) * 2004-01-13 2005-07-28 Ktfreetel Co., Ltd Procede et dispositif pour se connecter un service internet sans fil a l'aide d'une chaine

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6578088B2 (en) * 1996-08-29 2003-06-10 Hitachi, Ltd. Automatic address distributing system
KR19980064882A (ko) * 1998-06-01 1998-10-07 조관현 인터넷 주소의 자국어 표기 서비스 시스템
US7020602B1 (en) * 2000-08-21 2006-03-28 Kim Ki S Native language domain name registration and usage
EP1333647A2 (fr) * 2002-01-29 2003-08-06 Samsung Electronics Co., Ltd. Procédé et appareil pour la gestion de noms de domaines

Also Published As

Publication number Publication date
CN101553804A (zh) 2009-10-07
JP2010515112A (ja) 2010-05-06
EP2076849A1 (fr) 2009-07-08
CN101553804B (zh) 2013-02-13

Similar Documents

Publication Publication Date Title
JP7045104B2 (ja) データを処理する方法、装置、及びコンピュータプログラム、並びに階層ドメインネームシステムのゾーンファイル
US20060218289A1 (en) Systems and methods of registering and utilizing domain names
KR20010103670A (ko) 쉐도우 콜백 기능을 갖는 메시지 에일리어싱 기능을이용한 네트워크상의 정보 엑세스 방법 및 시스템
KR100385083B1 (ko) 리얼네임에 의한 인터넷상 컴퓨터 네트워크 접속방법 및 그 컴퓨터 네트워크 시스템
CN114205330A (zh) 域名解析方法、域名解析装置、服务器以及存储介质
KR100433982B1 (ko) 리얼 네임을 이용한 웹 페이지 접속 시스템 및 그 방법
JP3889667B2 (ja) リアルネームによるインターネット上コンピューターネットワーク接続方法及びそのコンピューターネットワークシステム
EP2076849A1 (fr) Procédé de traitement d'une adresse internet en langage natif et support de stockage destiné à sauvegarder un programme pour la mise en oeuvre de ce procédé
KR20080086096A (ko) 키워드 처리시스템, 키워드 처리방법 및 이를 실행시키기위한 프로그램을 기록한 기록매체
KR100464583B1 (ko) 키워드 네임을 이용한 유알엘 매핑 시스템 및 그 방법
US20040267748A1 (en) System for accessing web page using real name and method thereof
KR100723577B1 (ko) 키워드 처리시스템, 키워드 처리방법 및 이를 실행시키기위한 프로그램을 기록한 기록매체
KR100338666B1 (ko) 다국어를 이용한 웹 페이지 접속 시스템 및 그 방법
WO2005093999A1 (fr) Systemes et procedes d'enregistrement et d'utilisation de noms de domaine
KR100761978B1 (ko) 키워드 처리 시스템, 키워드 처리 방법 및 이를 실행하기위한 프로그램을 기록한 기록매체
KR100751889B1 (ko) 자국어 인터넷주소의 처리 방법 및 이를 실행하기 위한프로그램을 기록한 기록매체
US10659424B2 (en) Determining status of domain name registration
WO2002013057A1 (fr) Resolution d'adresses reseau
KR20050099943A (ko) 웹 페이지 접속 시스템 및 그 방법
KR100464582B1 (ko) 자국어 키워드 네임을 이용한 웹 페이지 접속 시스템 및그 방법
KR100732975B1 (ko) 웹 페이지 접속 시스템 및 그 방법
WO2008072886A1 (fr) Procede et systeme de connexion internet au moyen d'un mot-cle base sur dns
KR20080082700A (ko) 키워드의 처리 방법 및 이를 실행하기 위한 프로그램을기록한 기록매체
KR20090000282A (ko) 키워드 처리 시스템, 키워드 처리 방법 및 이를 실행하기위한 프로그램을 기록한 기록매체
KR20010075446A (ko) 대안의 인터넷 리소스 식별자 및 주소를 위한 방법 및시스템

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200780039189.3

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07833425

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2009533250

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2007833425

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE