WO2008066249A1 - Système et procédé de traitement d'un mot-clé et support de stockage pour stocker un programme d'exécution associé - Google Patents

Système et procédé de traitement d'un mot-clé et support de stockage pour stocker un programme d'exécution associé Download PDF

Info

Publication number
WO2008066249A1
WO2008066249A1 PCT/KR2007/005117 KR2007005117W WO2008066249A1 WO 2008066249 A1 WO2008066249 A1 WO 2008066249A1 KR 2007005117 W KR2007005117 W KR 2007005117W WO 2008066249 A1 WO2008066249 A1 WO 2008066249A1
Authority
WO
WIPO (PCT)
Prior art keywords
query
network information
http
keyword
address
Prior art date
Application number
PCT/KR2007/005117
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
Application filed by Netpia.Com, Inc. filed Critical Netpia.Com, Inc.
Priority to CN2007800506007A priority Critical patent/CN101595479B/zh
Priority to JP2009539173A priority patent/JP5292639B2/ja
Publication of WO2008066249A1 publication Critical patent/WO2008066249A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H04L61/301—Name conversion
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F17/00—Digital computing or data processing equipment or methods, specially adapted for specific functions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]

Definitions

  • the present invention relates to a method and system for processing a keyword using network information.
  • a method of processing a native language Internet address has been disclosed whereby a client computer accesses the corresponding webpage when a native language Internet address is input in the form of a keyword to access the Internet site.
  • An example of the method has been disclosed in Korean Patent Registration No. 317059, filed by the applicant of this patent application. More specifically, the patent discloses a method installing a proxy module in a Domain Name System (DNS) server and another method installing a native language processing program on a client computer.
  • DNS Domain Name System
  • DNS Domain Name System
  • IP Internet Protocol
  • a system for processing a keyword using network information comprises: an identifier database for storing at least one input location identifier; and a query determination device for receiving a Hypertext Transport Protocol (HTTP) query among the network information transferred from the client terminal, determining whether an input location identifier stored in the identifier database exists in Uniform Resource Information (URI) of a header of the HTTP query, and determining that the HTTP query is a query about a keyword input into an address window of a client web browser when an input location identifier stored in the identifier database exists in URI of a header of the HTTP query.
  • HTTP Hypertext Transport Protocol
  • a system for processing a keyword using network information by which network information transferred from a client terminal to a specific server is received and processed on a network, comprises: a host information database for storing information on at least one host; and a query determination device for receiving an HTTP query among the network information transferred from the client terminal to the specific server, determining whether host information of a header of the HTTP query is stored in the host information database, and determining that the HTTP query is a query about a keyword input into an address window of a client web browser when host information of a header of the HTTP query is stored in the host information database.
  • the system may further comprise: a network information retrieval device for determining that the network information transferred from the client terminal to the specific server is an HTTP query and transferring the network information to the query determination device when destination port data of a header of the network information is for an HTTP query.
  • the system may further comprise: an IP database for storing at least one IP address; and a network information retrieval device for determining whether a destination IP address of a header of the network information transferred from the client terminal to the specific server is stored in the IP database, and transferring the network information to the query determination device when a destination IP address of a header of the network information is stored in the IP database.
  • the query determination device may determine that the network information is an HTTP query when destination port data of a header of the network information transferred from the network information retrieval device is for an HTTP query.
  • a system for processing a keyword using network information by which network information transferred from a client terminal to a specific server is received and processed on a network, comprises: a suffix/domain database for storing a specific suffix or a specific domain; and a query determination device for receiving a DNS query among the network information transferred from the client terminal to the specific server, and determining that the DNS query is a query about a keyword input into an address window of a client web browser when the specific suffix or the specific domain stored in the suffix/domain database is included in the DNS query.
  • a system for processing a keyword using network information by which network information transferred from a client terminal to a specific server is received and processed on a network, comprises: a domain identifier database for storing an identifier indicating a domain name; and a query determination device for receiving a DNS query among the network information transferred from the client terminal to the specific server, determining whether the identifier stored in the domain identifier database is included in query field data of the DNS query, and determining that the DNS query is a query about a keyword input into an address window of a client web browser when the identifier stored in the domain identifier database is not included in query field data of the DNS query.
  • a method of processing a keyword using network information comprises the steps of: receiving an HTTP query among the network information transferred from the client terminal to the specific server; determining whether an input location identifier stored in an identifier database including at least one identifier exists in the HTTP query, and determining that the HTTP query is a query about a keyword input into an address window of a client web browser when an input location identifier stored in the identifier database exists in the HTTP query; and transferring an IP address or a Uniform Resource Locator (URL) of a Native Language Internet Address (NLIA) server or a search server to the client terminal in response to the HTTP query, the NLIA server returning an IP address or a URL corresponding to a specific keyword and the search server returning a search result for a specific keyword.
  • NLIA Uniform Resource Locator
  • a recording medium storing a program for executing the above described method of processing a keyword.
  • a method of processing a keyword according to an exemplary embodiment of 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), a random- access memory (RAM), a compact disk read-only memory (CD-ROM), a 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.
  • text string denotes every kind of input information that can be input into an address window or a search window of a web browser.
  • the term includes general URLs, keywords, e.g., Korean text, English text and numbers, other than URLs, and so on.
  • URL denotes a directory, a file, etc., as well as a domain name, e.g., "/ htm/index.html", indicating an address of various information provided by a computer system connected to the Internet.
  • IP address denotes a physical address for computer systems connected to the Internet to identify each other and 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 value input into a search window and the value input into an address window have the same domain.
  • a DNS server alone, it is not possible to distinguish the value input into the address window from the value input into the search window when a native language Internet address is processed using the value input into the address window.
  • the value is received and processed on a network to efficiently solve the conventional problem.
  • a native language Internet address is processed at a location in which data flows are aggregated.
  • many terminals can simultaneously process a native language Internet address.
  • a native language Internet address can be processed without modifying a system of a client or a DNS server, etc., or adding a system to the same.
  • FIG. 1 is a block diagram of an entire Internet service providing system employing a system for processing a keyword according to an exemplary embodiment of the present invention
  • FIG. 2 is a block diagram for describing a system for processing a keyword according to an exemplary embodiment of the present invention
  • FIG. 3 is a block diagram of the keyword processing system of FIG. 2 according to an exemplary embodiment of the present invention.
  • FIGS. 4 to 7 are flowcharts of a method of processing a keyword according to various exemplary embodiments of the present invention. Mode for the Invention
  • FIG. 1 is a block diagram of an entire Internet service providing system employing a system for processing a keyword according to an exemplary embodiment of the present invention.
  • a personal computer (PC) system 10 installed in each home and a company/agency computer system 12 connected to the Internet via a local area network (LAN) established in a predetermined organization, e.g., a school or a company, access a router 30 through an access network, such as a Public Switched Telephone Network (PSTN)/Integrated Services Digital Network (ISDN) 22, a Digital Subscriber Line (xDSL) 24, a wireless network 26 or a leased line 28 like a Hybrid Fiber-Coaxial (HFC) cable.
  • PSTN Public Switched Telephone Network
  • ISDN Integrated Services Digital Network
  • xDSL Digital Subscriber Line
  • the router 30 accesses an Internet Service Provider (ISP) 50 through a system 40 for processing a keyword.
  • ISP Internet Service Provider
  • the keyword processing system 40 is illustrated as a separate system between the router 30 and the ISP 50, but may be included in the router 30 or the ISP 50.
  • the keyword processing system 40 mainly functions to receive and process on a network data transferred via the network from the router 30 or a hub at which data is transferred via the Internet and crowded. Therefore, the keyword processing system 40 can be installed anywhere at which it is possible to achieve such an object.
  • the keyword processing system 40 may receive data transferred through a network using a mirroring method or a proxy method.
  • the mirroring method is a method of copying data at a network switch, e.g., a Layer
  • L7 switch etc.
  • the network switch uses a specific port.
  • packet mirroring is performed using a function of a switch, much load may be placed on the switch, and thus a network tap may be used.
  • the proxy method is a method of additionally installing proxy equipment in the middle of a network and thereby proceeding to a next step only when data passes through the proxy server. Since it is possible to proceed to a next step only when data is completely processed by a proxy server, processing of the data is ensured.
  • a network information retrieval device monitors network data transferred by the mirroring method or the proxy method.
  • a considerable load is placed on the keyword processing system 40 to process the data.
  • the entire network may slow down, or the process effect of the keyword processing system 40 may deteriorate. Consequently, it is preferable to distinguish and process necessary data only.
  • Various headers attached to data may be analyzed to first distinguish data to be processed according to whether the data is transferred from a specific server, what kind of communication protocol is used, whether the data is a response or a query, and so on. Next, it may be determined whether the data is a keyword. In addition, it is possible to directly determine whether or not the data is a keyword without the first distin- guishment process, and various modifications also can be made.
  • FIG. 2 is a block diagram for describing a system for processing a keyword according to an exemplary embodiment of the present invention
  • FIG. 3 is a block diagram of the keyword processing system of FIG. 2 according to an exemplary embodiment of the present invention.
  • a client terminal 100 is connected to a keyword processing system 40 on a network path.
  • the keyword processing system 40 is connected to a Domain Name System (DNS) server 140 and a Native Language Internet Address (NLIA) server 200 through the Internet 60, respectively.
  • DNS Domain Name System
  • NLIA Native Language Internet Address
  • the keyword processing system 40 may access a search server 300.
  • the keyword processing system 40 comprises a query determination device 44 and a database 46, and may further comprise a network information retrieval device 42.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • Application layer Telnet, FTP, e-mail, etc.
  • Transport layer TCP, UDP
  • IP IP
  • ICMP ICMP
  • IGMP IGMP
  • Link layer Device driver, NIC
  • Application layer a detailed function used for actual communication is performed. While user data generated from Application layer passes through Transport layer, Network layer and Link layer, data of the respective layers are added to the user data. As a result, complete communication data, i.e., an Ethernet frame, is constructed (see Table 2).
  • Ethernet IP TCP(UDP) Application Ethernet header header header data trai ler
  • An Ethernet header constructed in this way includes Media Access Control (MAC) addresses that are hardware addresses of destination and source Local Area Network (LAN) cards, and so on.
  • An IP header includes IP addresses of the source and destination, a protocol type and so on.
  • a TCP (User Datagram Protocol (UDP)) header includes information on a communication port for the corresponding service.
  • Application data is actual communication data and includes a header section indicating a type and a characteristic of the communication data.
  • a service port for TCP or UDP communication As a service port for TCP or UDP communication, well-known ports 1 to 1023, such as Hypertext Transport Protocol (HTTP): 80, File Transfer Protocol (FTP): 23, Telnet: 21, Post Office Protocol version 3 (POP3): 110, etc., rather than an arbitrary communication port are mostly used.
  • HTTP Hypertext Transport Protocol
  • FTP File Transfer Protocol
  • POP3 Post Office Protocol version 3
  • a type of data using a well- known port without analyzing entire communication data. For example, when a destination port number of a TCP header is 53, the corresponding data is a DNS query. On the other hand, when a destination port number of a TCP header is 80, the cor- responding data is an HTTP query.
  • the query determination device 44 receives an HTTP query among network information transferred from the client terminal 100. Then, the query determination device 44 determines whether an input location identifier stored in an identifier database 46a exists in URI of a header of the HTTP query, and determines that the HTTP query is a query about a keyword input into an address window of a client web browser.
  • An input location identifier will be described below.
  • a text string e.g., a keyword, other than a general URL query
  • an address window of, for example, Internet Explorer 7.0 it is converted into a query and transferred to a search server.
  • a domain of the search server 300 that converts a text string input into the address window of the web browser into a query and transfers the query is set to be the same as that of the search server 300 that converts a search word input into a search window of a webpage into a query and transfers the query.
  • the queries of the both cases are very similar to each other but have a different part, i.e., "OPNSCH" and "QBRE".
  • the part is stored as an identifier in the identifier database 46a, and the query determination device 44 determines whether an input location identifier stored in the identifier database 46a exists in URI of a header of an HTTP query.
  • the query determination device 44 determines that the HTTP query is a query about a keyword input into the address window of the client web browser.
  • input location identifiers stored in the identifier database 46a are text strings by which it is determined whether a keyword is a text string input into an address window or a search window of a client web browser.
  • the input location identifiers may be different according to search engines, and previously selected by a system builder or administrator to construct the identifier database 46a.
  • URI host information
  • data such as "Accept”, “Encoding”, “Host”, etc.
  • a field name information
  • a URI section may be distinguished to be a value between the two spaces of an HTTP header.
  • a host information section has a form of "HOST: "
  • a part beginning with "HOST:” may be detected to distinguish the host information section.
  • “Method” is information such as “GET”, “POST”, etc.
  • “Version” is information such as "HTTP/1.1", etc.
  • An example of an HTTP header is shown in Table 3.
  • the query determination device 44 stores information on at least one host in a host information database 46c.
  • the query determination device 44 receives an HTTP query among network information transferred from the client terminal and determines whether host information included in the HTTP query is stored in the host information database 46c.
  • the query determination device 44 determines that the HTTP query is a query about a keyword input into an address window of a client web browser.
  • host information database 46c In the host information database 46c, host information indicating a specific server, e.g., "auto.search.msn.com" is stored.
  • the identifier database 46a may store at least one input location identifier and also host information matching the input location identifier. More specifically, the query determination device 44 first determines whether host information of an HTTP query header is stored in the identifier database 46a. When it is determined that host information of an HTTP query header is stored in the identifier database 46a, the query determination device 44 second determines whether an input location identifier stored to match the host information exists in URI. When the input location identifier exists in URI, the query determination device 44 determines that the HTTP query is a query about a keyword input into a client web browser.
  • the keyword processing system 40 may have the network information retrieval device 42.
  • the network information retrieval device 42 may determine that the network information is an HTTP query and transfer the network information to the query determination device 44.
  • the database 46 may include an IP database 46b storing at least one IP address.
  • the network information retrieval device 42 may determine whether a destination IP address of a header of network information transferred from the client terminal 100 is stored in the IP database 46b, and transfer the network information to the query determination device 44 when the destination IP address is stored in the IP database 46b.
  • the query determination device 44 may determine that the network information is an HTTP query when destination port data of a header of the network information transferred from the network information retrieval device 42 is for an HTTP query.
  • an IP address included in the IP database 46b is an IP address of a DNS server or a specific server, and the IP database 46b is constructed by a system builder or administrator.
  • the query determination device 44 receives a DNS query among network information transferred from the client terminal 100.
  • the query determination device 44 determines that the DNS query is a query about a keyword input into an address window of a client web browser.
  • the keyword processing system 40 may include the network information retrieval device 42 which determines that the network information is a DNS query and transfers the network information to the query determination device 44 when destination port data of a header of the network information transferred from the client terminal 100 is for a DNS query. For example, when a destination port number of a UDP or TCP header is 53, it may be determined that the corresponding network information is an Internet address query to a DNS server.
  • the suffix/domain database 46d may store at least one suffix except an official domain name extension processed by a DNS system.
  • the suffix/domain database 46d may store a domain name of a specific server, e.g., "auto.search.msn.com", to determine that all DNS queries destined for the specific server are keywords.
  • a suffix may be assigned to the client terminal 100 during a process in which a Dynamic Host Configuration Protocol (DHCP) server assigns an IP address through DHCP.
  • DHCP Dynamic Host Configuration Protocol
  • a specific suffix may be assigned to the client terminal 100 while a terminal configuration program changes a terminal configuration.
  • a suffix may be assigned to the client terminal 100 according to a setting of a user. Detailed descriptions on a case of using a suffix database has been disclosed in Korean Patent Application No. 10-2006-118640, filed by the present Applicant.
  • the query determination device 44 receives a DNS query among network information transferred from the client terminal 100 and stores domain identifiers indicating domain names in a domain identifier database 46e.
  • the domain identifier database 46e is highly likely to be used.
  • the query determination device 44 receives a DNS query among network information transferred from the client terminal 100 and determines whether an identifier stored in the domain identifier database 46e is included in query field data of the DNS query. When an identifier stored in the domain identifier database 46e is not included in the query field data, the query determination device 44 determines that the DNS query is a query about a keyword input into an address window of a client web browser.
  • Domain identifiers stored in the domain identifier database 46e may be ".”, "www”, “http://” and general Top Level Domains (TLDs), such as “.com", “.net”, and so on.
  • TLDs Top Level Domains
  • According to a method of determining whether an input text string is a keyword using, for example, ".” it is determined that an input text string is a keyword when the domain identifier ".” is not included in the text string, and it is determined that an input text string is not a keyword when the domain identifier ".” is included in the text string.
  • a DNS query to be processed in first analysis of network data is distinguished, a content of the data is checked to analyze whether the data has a specific form, and thereby it is determined whether or not the DNS query is a query about a keyword.
  • a DNS query comprises a header, a question field, an answer field, etc., and the question field among these is used for the determination.
  • Table 4 Table 4
  • the database 46 may additionally have the IP database 46b storing at least one IP address.
  • the network information retrieval device 42 determines whether a destination IP address of a header of network information transferred from the client terminal 100 is stored in the IP database 46b.
  • the network information retrieval device 42 transfers the network information to the query determination device 44, and the query determination device 44 determines that the network information is a DNS query when destination port data of a header of the network information transferred from the network information retrieval device 42 is for a DNS query.
  • the query determination device 44 determines that an HTTP query or a DNS query is a query about a keyword input into an address window of a client web browser, it transfers an IP address or a URL of the NLIA server 200 returning an IP address or a URL corresponding to a specific keyword or the search server 300 returning a search result for a specific keyword, to the client terminal 100 in response to the HTTP or DNS query.
  • the keyword processing system 40 returns an Internet address of the NLIA server 200 to the client terminal 100
  • the client terminal 100 receives the Internet address and accesses the NLIA server 200 using the obtained Internet address.
  • the client terminal 100 transfers information on an input text string to the NLIA server 200.
  • the NLIA server 200 receives the text string and processes an Internet address corresponding to the text string. More specifically, the NLIA server 200 first searches an NLIA database matching an address keyword with an Internet address and storing the address keyword and the Internet address.
  • NLIA server 200 returns an Internet address corresponding to the address keyword to the client terminal 100.
  • the client terminal 100 receiving the Internet address accesses the corresponding webpage.
  • an address keyword and an Internet address corresponding to the keyword 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.
  • 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 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.
  • the NLIA server 200 may convert 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 receives the Internet address and accesses the search server 300 using the obtained Internet address.
  • the client terminal 100 accesses the search server 300, it provides a search list corresponding to the input text string (keyword).
  • the query determination device 44 when it responds to an HTTP query or a DNS query transferred to a specific server, it may transfer a reset signal corresponding to the query to the client terminal 100, the specific server, or the client terminal 100 and the specific server.
  • the reset signal may be considered as a connection close command to terminate communication between the client terminal 100 and the specific server.
  • UDP communication there is no function of maintaining a connection, and thus an additional operation is not required after the query determination device 44 responds to a query.
  • TCP communication the flow of all data is controlled after a connection is established, which is different from UDP communication. Thus, only actual data (DNS request) is processed while a connection with the specific server is maintained, and then a reset (RST) packet is transferred to both the client terminal 100 and the specific server to close the connection.
  • An input keyword may be converted into a punycode when a web browser determines that an input text string is a keyword.
  • the keyword may be converted into a punycode, or the text string may be converted into a punycode after a suffix is added to the text string. For example, when a port value of a UDP header or a TCP header is 53, it is determined that an input text string is DNS query data, and then it is determined whether or not the input text string is a keyword according to a content of the DNS query data.
  • the text string may be determined to be a keyword when the text string has been converted into a punycode.
  • FIG. 4 is a flowchart of the method of processing a keyword according to an exemplary embodiment of the present invention.
  • the keyword processing system 40 receives the network data on the network (step 103). As described above, the data can be received by the mirroring method or the proxy method.
  • an HTTP query is first distinguished on the basis of a type of the data, and so on (step 105). More specifically, various headers attached to the data are analyzed, and it is determined whether it is required to determine whether or not the data is a keyword, thereby distinguishing an HTTP query to be processed. For example, when a destination port number of a TCP header of the transferred data is 80, it is determined that the data is an HTTP query to be processed. In this case, a process of distinguishing an HTTP query using data IP address transferred via the network may be additionally performed.
  • an IP address or a URL of the NLIA server 200 or the search server 300 is transferred to the client terminal 100 in response to the HTTP query (step 109).
  • the NLIA sever 200 returns an IP address or a URL corresponding to a specific keyword
  • the search server 300 returns a search result for a specific keyword.
  • the client terminal 100 receiving the IP address or URL of the NLIA server 200 or the search server 300 accesses the corresponding webpage (step 111).
  • the keyword processing system 40 does not process the HTTP query and transfers the network data as it is (step 120).
  • FIG. 5 is a flowchart showing a method of processing a keyword according to another exemplary embodiment of the present invention.
  • the keyword processing system 40 receives the network data on the network (step 203).
  • an HTTP query is first distinguished on the basis of a type of the data, and so on (step 205). More specifically, various headers attached to the data are analyzed, and it is determined whether it is required to determine whether or not the data is a keyword, thereby distinguishing an HTTP query to be processed. For example, when a destination port number of a TCP header of the transferred data is 80, it is determined that the data is an HTTP query to be processed.
  • the query determination device 44 receives the HTTP query among network information transferred from the client terminal 100 and determines whether host information of a header of the HTTP query is stored in the host information database 46c (step 207). When it is determined that host information of a header of the HTTP query is stored in the host information database 46c, the query determination device 44 determines that the HTTP query is a query about a keyword input into an address window of a client web browser.
  • FIG. 6 is a flowchart showing a method of processing a keyword according to yet another exemplary embodiment of the present invention.
  • the keyword processing system 40 receives the network data on the network (step 303).
  • a DNS query is first distinguished on the basis of a type of the data, and so on (step 305). More specifically, various headers attached to the data are analyzed, and it is determined whether it is required to determine whether or not the data is a keyword, thereby distinguishing a DNS query to be processed. For example, when a destination port number of a TCP header or a UDP header of the transferred data is 53, it is determined that the data is a DNS query to be processed.
  • an IP address or a URL of the NLIA server 200 or the search server 300 is transferred to the client terminal 100 in response to the DNS query (step 309).
  • the client terminal 100 receiving the IP address or URL accesses the corresponding webpage (step 311).
  • the DNS query is not processed (step 320).
  • FIG. 7 is a flowchart showing a method of processing a keyword according to yet another exemplary embodiment of the present invention.
  • the keyword processing system 40 receives the network data on the network (step 403).
  • a DNS query is first distinguished on the basis of a type of the data, and so on (step 405). More specifically, various headers attached to the data are analyzed, and it is determined whether it is required to determine whether or not the data is a keyword, thereby distinguishing a DNS query to be processed.
  • the query determination device 44 determines whether an identifier stored in the domain identifier database 46e and indicating a domain name is included in the DNS query transferred from the client terminal 100 (step 407).

Abstract

L'invention concerne un système et un procédé de traitement d'un mot-clé au moyen d'une information réseau. Le système reçoit une demande de protocole de transfert hypertexte (HTTP) dans une information réseau émise par un terminal client, il détermine si un identifiant de localisation d'entrée stocké dans une base de données d'identifiants existe en information de ressource universelle (URI) dans un en-tête de la demande HTTP, et il définit la demande HTTP comme étant une demande relative à une entrée de mot-clé dans une fenêtre d'adresse d'un navigateur Web client lorsqu'un identifiant de localisation d'entrée stocké dans la base de données d'identifiants existe dans l'URI d'un en-tête de la demande HTTP.
PCT/KR2007/005117 2006-12-01 2007-10-19 Système et procédé de traitement d'un mot-clé et support de stockage pour stocker un programme d'exécution associé WO2008066249A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN2007800506007A CN101595479B (zh) 2006-12-01 2007-10-19 关键词的处理系统和方法以及储存其执行程序的储存媒体
JP2009539173A JP5292639B2 (ja) 2006-12-01 2007-10-19 キーワード処理システム、キーワード処理方法、及びそれを実行するためのプログラムを記録した記録媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020060121026A KR100723577B1 (ko) 2006-12-01 2006-12-01 키워드 처리시스템, 키워드 처리방법 및 이를 실행시키기위한 프로그램을 기록한 기록매체
KR10-2006-0121026 2006-12-01

Publications (1)

Publication Number Publication Date
WO2008066249A1 true WO2008066249A1 (fr) 2008-06-05

Family

ID=38278776

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2007/005117 WO2008066249A1 (fr) 2006-12-01 2007-10-19 Système et procédé de traitement d'un mot-clé et support de stockage pour stocker un programme d'exécution associé

Country Status (4)

Country Link
JP (1) JP5292639B2 (fr)
KR (1) KR100723577B1 (fr)
CN (1) CN101595479B (fr)
WO (1) WO2008066249A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107844488A (zh) * 2016-09-18 2018-03-27 北京京东尚科信息技术有限公司 数据查询方法和装置
CN112242981A (zh) * 2019-07-19 2021-01-19 西安中兴新软件有限责任公司 一种网站过滤的方法和装置
US20220255910A1 (en) * 2015-01-09 2022-08-11 Verisign, Inc. Registering, managing, and communicating with iot devices using domain name system processes

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR19980064882A (ko) * 1998-06-01 1998-10-07 조관현 인터넷 주소의 자국어 표기 서비스 시스템
KR20010035390A (ko) * 2001-02-09 2001-05-07 장충엽 인터넷 자연어 주소입력 접속 시스템 및 그것의 방법
KR20010112080A (ko) * 2000-06-08 2001-12-20 주진용 웹브라우저의 ｕｒｌ 입력창을 이용한 검색 시스템 및 그검색 방법
KR20040014744A (ko) * 2002-08-10 2004-02-18 주식회사 아이콘랩 패턴을 이용한 유알엘 제공 서비스 시스템 및 방법, 및이를 이용한 정보자원에 접근하는 방법
KR20060093306A (ko) * 2005-02-21 2006-08-24 (주)넷피아닷컴 로컬 도메인 네임 시스템 및 이를 이용한 서비스 제공 방법

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1246780C (zh) * 1998-02-09 2006-03-22 拿丕业互联网有限公司 因特网实名计算机网络连接方法及其计算机网络系统
KR20030024296A (ko) * 2001-09-17 2003-03-26 (주)넷피아닷컴 리얼 네임을 이용한 웹 페이지 접속 시스템 및 그 방법
KR20030024295A (ko) * 2001-09-17 2003-03-26 (주)넷피아닷컴 리얼 네임을 이용한 검색 시스템 및 그 방법
US7219090B2 (en) * 2003-04-25 2007-05-15 Overture Services, Inc. Method and system for blending search engine results from disparate sources into one search result
US20080281816A1 (en) * 2003-12-01 2008-11-13 Metanav Corporation Dynamic Keyword Processing System and Method For User Oriented Internet Navigation
KR100867176B1 (ko) * 2005-03-10 2008-11-06 한국전자통신연구원 디지털 콘텐츠 제공 시스템에서의 광고 구간 식별 방법
US8200696B2 (en) * 2005-05-26 2012-06-12 International Business Machines Corporation Presenting multiple possible selectable domain names from a URL entry

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR19980064882A (ko) * 1998-06-01 1998-10-07 조관현 인터넷 주소의 자국어 표기 서비스 시스템
KR20010112080A (ko) * 2000-06-08 2001-12-20 주진용 웹브라우저의 ｕｒｌ 입력창을 이용한 검색 시스템 및 그검색 방법
KR20010035390A (ko) * 2001-02-09 2001-05-07 장충엽 인터넷 자연어 주소입력 접속 시스템 및 그것의 방법
KR20040014744A (ko) * 2002-08-10 2004-02-18 주식회사 아이콘랩 패턴을 이용한 유알엘 제공 서비스 시스템 및 방법, 및이를 이용한 정보자원에 접근하는 방법
KR20060093306A (ko) * 2005-02-21 2006-08-24 (주)넷피아닷컴 로컬 도메인 네임 시스템 및 이를 이용한 서비스 제공 방법

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220255910A1 (en) * 2015-01-09 2022-08-11 Verisign, Inc. Registering, managing, and communicating with iot devices using domain name system processes
CN107844488A (zh) * 2016-09-18 2018-03-27 北京京东尚科信息技术有限公司 数据查询方法和装置
CN112242981A (zh) * 2019-07-19 2021-01-19 西安中兴新软件有限责任公司 一种网站过滤的方法和装置

Also Published As

Publication number Publication date
JP5292639B2 (ja) 2013-09-18
JP2010522908A (ja) 2010-07-08
CN101595479B (zh) 2012-10-10
CN101595479A (zh) 2009-12-02
KR100723577B1 (ko) 2007-05-31

Similar Documents

Publication Publication Date Title
CA2408233C (fr) Dispositif de surveillance d'utilisation de reseau et procede associe
US9332020B2 (en) Method for tracking machines on a network using multivariable fingerprinting of passively available information
US8762573B2 (en) Reverse DNS lookup with modified reverse mappings
WO2018107784A1 (fr) Procédé et dispositif de détection de canevas web
US7624142B2 (en) System and method for processing packets according to user specified rules governed by a syntax
JP4354294B2 (ja) ネットワーク・セグメントが互いに異なる複数のネットワークに接続されたゲートウェイ装置、およびｉｐパケットを転送するためのプログラムおよび方法
US7814204B1 (en) Method of and system for analyzing the content of resource requests
US20070177499A1 (en) Network connectivity determination
US20100138921A1 (en) Countering Against Distributed Denial-Of-Service (DDOS) Attack Using Content Delivery Network
KR20040068365A (ko) 네트워크 라우팅 디바이스를 자동으로 구성하는 방법
US7907543B2 (en) Apparatus and method for classifying network packet data
US20130080629A1 (en) Method and apparatus for detecting devices on a local area network
US7440466B2 (en) Method, apparatus and system for accessing multiple nodes on a private network
WO2008066249A1 (fr) Système et procédé de traitement d'un mot-clé et support de stockage pour stocker un programme d'exécution associé
KR20080086096A (ko) 키워드 처리시스템, 키워드 처리방법 및 이를 실행시키기위한 프로그램을 기록한 기록매체
KR20080050182A (ko) 키워드 처리시스템, 키워드 처리방법 및 이를 실행시키기위한 프로그램을 기록한 기록매체
KR100761984B1 (ko) 자국어 인터넷주소의 처리방법 및 이를 실행시키기 위한프로그램을 기록한 기록매체
CN117692512A (zh) 一种数据处理方法、装置、相关设备及存储介质
JPH08191326A (ja) ネットワーク構成の認識方法
WO2008050970A1 (fr) Procédé de traitement d'adresse internet en langage natif et support de stockage pour le stockage d'un programme pour l'exécution dudit procédé
KR20090000131A (ko) 자국어 이메일주소 처리시스템, 자국어 이메일주소처리방법 및 이를 실행시키기 위한 프로그램을 기록한기록매체
KR20090000069A (ko) 이메일주소의 처리방법 및 이를 실행시키기 위한프로그램을 기록한 기록매체

Legal Events

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

Ref document number: 200780050600.7

Country of ref document: CN

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

Ref document number: 07833426

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2009539173

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07833426

Country of ref document: EP

Kind code of ref document: A1