KR20150140298A - Smart Navigation Services - Google Patents

Abstract

We present a smart search technique. The technique may include performing a request for a network resource over a search service and the Internet, wherein the request includes command data provided by a search client and the command data includes an entity name and a keyword. The technique may include obtaining a network locator corresponding to an entity name and a keyword from at least one search service database. The technique may further comprise providing a network locator in response to receiving via the Internet.

Description

Smart Navigation Services {Smart Navigation Services}

This application is a continuation-in-part of U.S. Patent Application No. 14 / 176,723, entitled " Smart Search Service, " filed February 10, 2014, The provisional patent application filed in the US provisional application No. 61 / 809,377, the provisional patent application filed in the US provisional application No. 61 / 811,234 entitled " Hope Resource Search " on Apr. 12, 2013, Priority is claimed on U.S. Provisional Patent Application Serial No. 61 / 820,391, entitled " Smart Search in Common Name Space ", the disclosure of which is incorporated herein by reference in its entirety have.

The present invention relates to the search for network resources. More particularly, it is a particular embodiment to provide a method for searching network resources without using standard domain name system ("DNS") resolution processing or standard search methods. Other specific embodiments may use standard DNS resolution processing.

According to various embodiments, a computer-implemented method of providing a search service is disclosed. The method includes receiving a request for a search service and a network resource over the Internet, wherein the request includes command data provided by a search client and the command data includes an entity name and a keyword do. The method of the present invention may include obtaining a network locator corresponding to an entity name and a keyword from at least one database of search services.

The various optional features of an embodiment of the present invention may include the following.

 The search service may not be a domain name system search service because the search service may be acting for a namespace that is different from the domain name space. The command data may be derived from an instruction string that includes an abutting name space identifier. The name space marker can be something like @, fb, in "." The search client can select a search service based on the name space marker. The command data may be derived from a command string that includes setting a keyword boundary around the keyword. The keyword boundary settings can be displayed as #,!, ".", $, |.

The method of the present invention may include receiving an Internet Protocol address corresponding to a network locator from a database of a domain name system service provider and providing an internet protocol address. The search client can analyze the command data and build the request. The method may further comprise receiving the network locator, the entity name and the keyword by the search service, and storing the network locator in association with the entity name and the keyword. The method may include receiving, by the search service, a proof of ownership of the entity name.

The method includes the steps of obtaining a request fragment for a network resource that is an instruction name and data fragment with a keyword fragment, the entity name including an instruction fragment provided by a search client in a search service over the Internet prior to the receiving step; Obtaining a plurality of possible keywords that are at least partially matched to at least one keyword marker fragment from at least one database of search services; And providing a plurality of possible keywords in response to being obtained by the Internet.

The method includes the steps of obtaining a request fragment for a network resource that is a fragment of an entity name with an entity name including an instruction fragment provided by a search client in a search service over the Internet prior to the receiving step; Obtaining a plurality of possible entity names corresponding to at least one entity name fragment from at least one database of search services; And providing a plurality of entity names that are possible in response to being obtained by the Internet.

 The method includes receiving a second request for a network resource that is a second instruction data having a second entity name including a second instruction provided by a search client in a search service over the Internet, The second entity name is not included in at least one database as an entity name, and the second entity name appears in a third-party name space corresponding to the third-party service; Obtaining content corresponding to a second entity name from a third party service; And providing a network locator for the resource containing the content in response to being obtained by the Internet.

The entity name can be included in at least one database as an entity name, and the keyword can not be included in at least one database with respect to the entity name. Thus, the obtaining step may include searching at least one database in relation to the entity name for the second keyword related to the keyword. The network locator can also correspond to the entity name and the second keyword. The method includes receiving an entity name that is not contained in at least one database as an entity name after receiving a request for a network resource and storing the entity name as at least one entity name And the step

The method includes receiving a second request for a network resource including a second entity name provided by a search client and a second command having a second keyword in a search service over the Internet; Mapping a second request to a third entity name and a third keyword; Obtaining a second network locator corresponding to a third entity name and a third keyword from at least one database of the search service; And providing a second network locator in response to receiving a second request by the Internet. The search client may include a web browser. The search client can perform the mobile device.

A search service system is disclosed in accordance with various embodiments. The system includes an Internet operatively coupled to one or more server computers and operable to receive command data including requests for network resources over the Internet, requests including command data provided to a search client, entity names and keywords, Is set. The method also includes at least one database operatively associated with the one or more servers, and wherein the at least one database stores network locators in association with entity names and keywords. The method also includes at least one electronic processor configured to provide a network locator from a search client over the Internet.

The various alternative embodiments described above include the following. The search service may not be a domain name system search service. The command data may be derived from a command string that includes a namespace adjacent to the entity name. The name space marker can be something like @, fb, in "." The command data may be derived from a command string that includes setting a keyword boundary around the keyword. The keyword boundary settings can be displayed as #,!, ".", $, |. The system may include at least one processor configured to receive from the database of the domain name system service provider an internet protocol address corresponding to the network locator and to provide an internet protocol address.

The system may include at least one processor configured to receive the network locator, the entity name and the keyword by the search service, and to store the network locator in association with the entity name and the keyword. The at least one processor may further include at least one processor configured to perform receiving the proof of ownership of the entity name.

The system comprising: obtaining a request fragment for a network resource which is an instruction name and data fragment with a keyword fragment, the entity name including an instruction fragment provided by a search client in a search service over the Internet prior to the receiving step; Obtaining a plurality of possible keywords that are at least partially matched to at least one keyword marker fragment from at least one database of search services; And at least one processor configured to perform providing a plurality of possible keywords in response to being obtained by the Internet.

The system comprising: obtaining a request fragment for a network resource that is a fragment of an entity name with a fragment of an entity name including an instruction fragment provided by a search client in a search service over the Internet prior to an accepting step; Obtaining a plurality of possible entity names corresponding to at least one entity name fragment from at least one database of the search service; And at least one processor configured to perform providing a plurality of possible entity names in response to being obtained by the Internet.

The system includes a second request for a network resource, the second instruction data having a second entity name including a second instruction provided by a search client in a search service over the Internet, Th entity name is not contained in at least one database as an entity name and the second entity name appears in a third party name space corresponding to the third party service; Obtaining content corresponding to a second entity name from a third party service; And at least one processor configured to perform providing a network locator for resources including content in response to being obtained by the Internet.

The entity name may be included in at least one database as an entity name and the keyword may be associated with an entity name for a second keyword associated with the keyword so as not to be included in at least one database with respect to the entity name, At least one processor is set up for retrieval, and the network locator is made to correspond to the entity name and the second keyword. Wherein at least one processor is configured to receive a request for a network source that is not contained in at least one database with an entity name and is configured to write an entity name and that is also included in at least one database Is set to be able to provide an entity name of < RTI ID = 0.0 >

The system includes receiving a second request for a network resource including a second entity name provided by a search client and a second command having a second keyword in a search service over the Internet; Mapping a second request to a third entity name and a third keyword; Obtaining a second network locator corresponding to a third entity name and a third keyword from at least one database of the search service; And at least one processor configured to perform providing a second network locator in response to receiving a second request by the Internet. The search client may include a web browser.

According to various embodiments, a method of performing using a computer system is disclosed. The method includes receiving, by a search client, a command string including an entity name and a keyword; Converting a request including an entity name and a keyword from a command string to a request for a resource; Providing a request for a resource to a search service via the Internet; And obtaining a network locator corresponding to the entity name and the keyword from the search service.

The various optional features of an embodiment of the present invention may include the following.

The search service may not be a domain name system search service. The command string may include an abutting namespace identifier in the entity name. The name space marker can be something like @, fb, in "." The method of the present invention may select a search service based on a namespace marker. The command string may include setting a keyword boundary around the keyword. The keyword boundary settings can be displayed as #,!, ".", $, |.

The method includes: requesting an internet protocol address corresponding to a network locator; Receiving an internet protocol address associated with the network locator; And retrieving an internet protocol address. The derivation may include analyzing the command string and building the request. The method includes: requesting an Internet Protocol address corresponding to a network locator from a domain name system service provider; And automatically retrieving the Internet Protocol address. The method may include receiving a request to display a network locator and providing a network locator for display. The method may include providing a visual indication at the same time as receiving the entity name in the field of the search client.

A system of the present invention is disclosed in accordance with various embodiments. The system comprises: receiving by a search client a command string comprising an entity name and a keyword; Deriving a request for a resource from a command string, the request comprising an entity name and a keyword; Providing a request for a resource as a search service over the Internet; And obtaining a network locator corresponding to the entity name and the keyword from the search service.

The various alternative embodiments described above include the following. The search service may not be a domain name system search service. The command string may include a namespace adjacent to the entity name. The name space marker can be something like @, fb, in "." At least one processor may be further configured to select a search service based on a namespace marker.

The command string may include a keyword boundary around the keyword. Keyword boundary settings can be #,!, ".", $, |. Requesting an Internet Protocol address in connection with the network locator; Receiving an Internet Protocol address associated with the network locator; And retrieving an internet protocol address from the at least one processor. At least one processor can be further configured to retrieve the instruction string and build the request. The at least one processor requesting an Internet Protocol address corresponding to the network locator from a domain name system service provider; And automatically searching for an Internet Protocol address. At least one processor receiving a request to display a network locator; May be further set to perform providing a display of the network locator. At least one processor may be further configured to provide a visual indication at the same time as receiving the entity name on the search client side.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments of the invention and are provided to provide a description of the principles of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 is a diagram illustrating an exemplary keyword search system in connection with certain disclosed embodiments.
2 is a flow diagram illustrating an exemplary process performed by a keyword management server in connection with certain disclosed embodiments.
3 illustrates an exemplary interface provided by a keyword resolution server that enables creation, modification, and deletion of keyword-to-web page mappings to content providers associated with certain disclosed embodiments.
4 is a flow diagram illustrating an exemplary method for resolving a user-provided keyword associated with a particular disclosed embodiment through a content provider-detail web page.
5 is a list of example URLs containing URL keywords associated with a particular disclosed embodiment.
6 is an exemplary HTTP request resulting from a URL input that includes a URL keyword associated with a particular disclosed embodiment.
Figure 7 is an exemplary HTTP response from a keyword-enabled web server associated with a particular disclosed embodiment.
8 is an exemplary URL for a URL keyword resolution request associated with a particular disclosed embodiment;
9 is an exemplary URL corresponding to a keyword-specific-web page mapping content provider associated with a particular disclosed embodiment.
10 is an exemplary performance diagram associated with certain disclosed embodiments.
11 is an exemplary implementation of keyword / URL mapping on the server side in connection with certain disclosed embodiments.
Figure 12 is an exemplary implementation of keyword / URL mapping on the client side in connection with certain disclosed embodiments.
13 is an exemplary performance diagram of keyword / URL mapping using HTTP redirect.
Figure 14 is a flow diagram illustrating an exemplary brand management process performed by a brand management component of a keyword management server in connection with certain disclosed embodiments.
Figure 15 is an exemplary interface provided by a keyword resolution server in which a content provider associated with a particular disclosed embodiment is capable of managing brand-based keyword mappings.
Figure 16 is an exemplary interface provided by a keyword resolution server that enables participation of third party brand-based keyword mappings in connection with certain disclosed embodiments.
Figure 17 illustrates an embodiment of a system and method for retrieving from agents to desired network resources consistent with the principles of the present invention.
18 is a flowchart illustrating a method from the aspect of a search service according to various embodiments.
19 is a flow chart illustrating a method from the aspect of an agent in accordance with various embodiments.
Figure 20 illustrates an exemplary computer system used to perform embodiments consistent with the present invention.

SUMMARY OF THE INVENTION The present invention provides a method, system, computer readable medium and article of manufacture through a direct search from an agent to a network that has been requested by a user. The present invention also provides a method, system, computer readable medium, and article of manufacture capable of enabling a user to search for and connect to desired network resources without having to know or input accurate domain names, URIs, URLs, etc. corresponding to desired network resources .

For example, when a web site selling a product such as a shoe is searched from a desired network resource, the behavior of a conventional Internet user is described as an embodiment. In this embodiment, it is assumed that the user requires the purchase of a shoe from a particular website of the seller, known as the virtual seller Gimbels. To do this, the user presses the enter key to search for "gimbel shoes " using an omnibar in a browser that uses the usual first type search bar or generally lists the characteristics of the desired article. The browser then passes these characteristics to the string of search engines and returns many results to display on the browser. In these conventional scenarios, the sales broker and domain owner, Gimbel, often can not control what is displayed to the user through the search engine, which means that the search engine has a number of Gimbel- And display goods such as sandals instead of shoes, or display pages that are not needed among Gimbel's web sites, and can also display search engine-related parts that are not related to search paid by the advertiser. It is because. Similar to the conventional scenario, the user can not access the network resources representing the web page of Gimbel that sells shoes precisely because the search engine skips the connection of the Gimbel web page and leads to connection to a plurality of web pages not related to Gimbel .

Various embodiments are possible in accordance with the present invention, and it will help domain owner entities such as Gimbel to guide search results in more detail and map one or more network resources that are adjusted or operated by the entities to respond, And the like.

One. URL Based smart search

1 is a diagram illustrating an exemplary URL keyword resolution system 100 for performing embodiments of the present invention including exemplary system components. The components are arranged but deformable. The URL keyword resolution server 120 comprises a processor 122, a memory 123, an input / output (I / O) device (not shown) and a storage device 121. The URL keyword resolution server 120 may operate in various ways. For example, the URL keyword resolution server 120 may be a conventional computer, a server, a mainframe computer, or a combination thereof. The URL keyword resolution server 120 communicates with each other via a network 115 connection. For example, the connection may be a direct communication connection, a LAN, a WAN, or other suitable interconnect. The network 115 includes the Internet. The URL keyword resolution server 120 may be used alone or as a subsystem that is part of a larger system such as, for example, a legacy domain registration system.

The processor 122 may be one or more processors, for example, a Pentium or Xeon microprocessor manufactured by Intel Corporation, a Turion family manufactured by AMD, or various processors manufactured by Sun Microsystems. The memory 123 may include one or more storage devices that are modified to store information needed by the processor 122 to perform certain functions in connection with the embodiments disclosed herein. The storage device 121 may be a volatile, non-volatile, magnetic, semiconductor, tape, optical, erasable, non-removable or other form of storage device or computer readable medium.

In one embodiment, the memory 123 may include one or more keyword resolution programs or sub-programs 124 loaded into the storage device 121 or other area, When executed by the keyword resolution server 120, may perform various procedures, operations, or processes. For example, the memory 123 may include a keyword registry program that authenticates a domain name and allows a domain name controller to set and maintain a keyword for a domain name; A keyword resolution program for matching a keyword / domain name in combination with a target URL, and receiving a user request for resolving one or more keywords in a domain for providing a user with a target URL; An integrated support program that connects with other programs and allows normal database use, provides a normal user interface, performs basic administrative tasks such as storing user input, and provides user guidance and help; And a brand management program that allows the domain name controller to provide a third party with keywords for the domain. The memory 123 may also include a program that performs operations with other functions, such as programs that provide communication support or Internet access.

The method system and manufacturing apparatus according to embodiments of the present invention are not limited to separate programs or computers for carrying out the present invention. For example, the memory 123 may be configured as a keyword resolution program 124 for performing various functions when performed by the processor 122. [ For example, the memory 123 may include a single program 124 for performing the function of the keyword resolution system or a program 124 including a plurality of programs. The processor 122 may also execute one or more programs that reside remotely from the URL keyword resolution server 120. For example, the URL keyword resolution server 120 may connect to one or more remote programs when performing functions related to embodiments of the present invention.

The memory 123 may be modified with an operating system (not shown) that performs various functions already known for performing by the URL keyword resolution server 120. [ For example, the operating system may be a Microsoft Windows, Unix, Linux, Solaris, Apple computer operating system, a personal digital assistant operating system such as Microsoft CE, or other operating system. The selection of the operating system is user selectable, which is not particularly important.

The URL keyword resolution server 120 may include one or more I / O devices (not shown) capable of accepting and / or transmitting data by a URL keyword resolution server. The I / O device may include one or more digital and / or analog communication input / output devices 120, such as a URL keyword resolution server 120, for communicating with other machines and devices, such as a web server 140 or client computer 150, . ≪ / RTI > The URL keyword resolution server 120 can receive data from an external machine and a device via an I / O device, and can transmit data to an external machine and a device. The variations and numbers of the input and / or output devices integrated in the I / O device can be changed appropriately according to the particular type.

The URL keyword resolution server 120 may be coupled to communicate with one or more data stores 130 via, for example, a network 115. The data store 130 may include one or more files or databases 131 of stored information and may be accessed and managed via the URL keyword resolution server 120. As an example, the database may include an Oracle database, a Sybase database or other related database, or an irrelevant database such as HBase or Cassandra. The database or other file may contain data and information related to the domain name, keywords for the domain name, description, statistics and other data related to the keywords. Embodiments of the present invention systems and methods do not limit a specific database.

The URL keyword resolution server 120 may be coupled to communicate with one or more client computers 150 via the network 115. The client computer 150 may include a processor 151, a memory 152, a URL keyword resolution server 120, and / or a web browser 153 that can communicate with the web server 140. The client computer 150 may be connected to communicate with the web server 140 via the network 115. In a specific embodiment, the URL keyword resolution server 120 may transmit data to the processor 151 and the web browser 153, and the web browser 153 may display the data as a keyword registration interface. In certain embodiments, the client computer 150 may communicate with the web server 140 using the HTTP protocol to query and display the web page provided by the web server 140. In certain embodiments, the client computer 150 may send URL and keyword data to the URL keyword resolution server 120 and may receive the target URL data corresponding to the URL indicated by the content provider in a particular domain / keyword pair have.

Web server 140 may be owned or operated by a content provider or a domain name controller. It may also store web pages and Internet resources associated with one or more domain names. The web server 140 may include a processor 142, a storage device 141, and a memory 143. The storage device 141 may be in the form of a boltile or non-boltile, a magnetic, a semiconductor, a tape, an optical device, a removable, non-erasable or other storage device, or a computer readable medium. It may also contain data to display each web page. In an embodiment of the present invention, the memory 143 may include one or more server programs capable of responding to and receiving HTTP requests; One or more server-side scripts 145 for providing an active web page; And one or more keyword resolution programs 146 for resolving and receiving requests for URL / keyword pairs. Each program may be loaded from, for example, storage 141 or loaded elsewhere.

2 is a flow diagram illustrating an exemplary process performed by a keyword management server corresponding to an embodiment of the present invention. The keyword resolution service provider provides most of the technology infrastructure in which the content provider can perform the URL keyword function corresponding to the present invention. For example, a keyword resolution service provider may provide an interface, such as the interface depicted in FIG. 3, to a content provider to register and manage a URL keyword to use the keyword management server.

In step 205, after the user logs in the keyword management interface 300 on behalf of the content provider, the keyword management server receives the domain name (including path or query string information) from the user indicating domain name for which the user wishes to register the keyword . The domain name identifies the control authority of the Internet resource. The domain name is often the host name that identifies the website. For example, acmecorp.cc is the domain name used by Acme Corporation. The domain name is registered in the domain name registrar in order to acquire the exclusive right to use the Internet resource related to the domain name.

In step 210, for the sake of security, the keyword management server may first request the user to authenticate the input domain name indicating the right to register the keyword. For example, a keyword management server can create a meta tag for a user that can be inserted into a domain's home page. Such meta tags have the form "<meta name =" keyword-verification "content =" djkaoieiosldisa "/>". The keyword management server stores the domain name and the value of the content field in a database or other file. After the meta tag is inserted into the homepage, the user can go back to the authentication process. The keyword management server checks the homepage of the domain to detect the existence of the meta tag. If the meta tag exists and has a content value matching the value stored by the keyword management server, the user can be authenticated to control the domain name.

In yet another embodiment, the user may be required to configure the CNAME record within the Domain Name System (DNS). The DNS record stores information used to resolve Internet address requests to physical resources. The CNAME record is refined with aliases of domain names with different domain names. The keyword management server instructs the domain name controller, for example, to add CNAME Text of "www.resolvecom.com" to the CNAME Host and "djkaoieiosldisa" to the DNS. The keyword management server can store the CNAME Host together with the domain name in the local database. After the CNAME record is established, the user returns to the authentication procedure. The keyword management server queries the DNS to search the CNAME Host. If the domain is found and matches the CNAME Host record, the user will be authenticated as the owner of the domain name.

For authentication of the domain name, the keyword management server in step 215 may allow the domain name controller to provide a keyword for the domain. The keyword management server may provide an interface as shown in FIG. 3, which allows the content provider or the domain name controller to set the keywords. The keyword is associated with the domain name and the keyword management server displays the current domain name 305 on the interface. As shown in FIG. 3, the keyword management server may receive at least the keyword 310 and the URL 315 from the domain name controller to form a keyword-URL pair. The URL can identify a specific web page that the domain name controller wants to find in relation to the keyword. Accordingly, a properly formatted request in the domain name 305 will also include a keyword 310 that the user can automatically redirect to the URL 315.

The URL 315 may be part of a web page in the host of the domain 305, but it need not be. The URL 315 may be an address associated with a web page of a domain selected by the domain name controller. After receiving the keyword and URL, the keyword management server can store the keyword-URL pair in the database or other file. The keyword-URL pair is associated with the current domain name 305.

In addition to this information, the keyword management server may collect additional information or metadata related to keywords, e.g., via the icon 320. Such additional information may include, but is not limited to, a description of the URL or a description of the keyword. The URL description may be a business description of the URL selected by the domain name controller. This description can be used for keyword statistics reporting and other reports generated by the keyword management server.

The interface may include a brand management component that allows the domain name controller to allow one or more third parties that do not own the domain to provide keywords for the domain. For example, the user can press a button 350 to request a keyword management server to create a presentation list of a third party. The keyword management server may display this list to the domain name controller. The domain name controller may also provide a keyword management server that is not present on the generated list to the proposed third party. The brand management component is described in further detail below.

The keyword-URL pair can be mapped in the location. Locations can be detailed with zip code, state, region code, county, geo-location code, or other local markers. For example, a domain name controller might want to display another web page for a website for visitors who live in Hawaii than a website for visitors who live in Minnesota. The keyword resolution server can receive codes regarding geographical locations from GPS-based devices and website visitors can use the IP address sources of website visitors to determine their location. The keyword resolution server may use this information to select a keyword-URL pair. The location information allowed on the domain name controller is for local advertising promotions and allows the website visitor to send appropriate local data directly.

The keywords have associated metadata devices. For example, such devices are personal digital assistants (PDAs), smart phones, laptops, tablets, and the like. Such a device allows a keyword resolution server to redirect web pages to a web site visitor using the appropriate device type. For example, a domain with one web page for a mobile device such as a PDA or smart phone can provide another web page for all of the other devices. The keyword resolution server may be modified according to the usage pattern of the device that determines the type of the device indicating the keyword resolution request for the provided domain / keyword and selects the appropriate keyword-URL pair.

The keyword management server may use the keyword form 325 of FIG. 3 to identify the keyword location or device. For example, the R-shaped keyword may not be associated with any location or device. On the other hand, the L-shaped keyword may be a keyword related to a certain position, and the D-shaped keyword may be related to a device related to the keyword.

In step 220, after the content provider or the domain name controller registers, transforms, or deletes the keyword mapping as needed, the user can request the keyword management server by pressing the button 330 so that the keyword management server can generate the client-performing program. At this time, the user-executable program embeds a content provider HTTP response that allows the user-provided URL keyword as described below to be detected and resolved. Then, in step 225, the client-executing program is, for example, a JavaScript program and can be located and copied within the server logic of the content provider and displayed to the user.

FIG. 14 is a flow diagram illustrating an exemplary brand management process performed by a brand management component of a keyword management server according to an embodiment of the present invention. In step 1410, the keyword management server may receive an instruction of the brand management participation information, which enables a third party to provide a keyword for the domain name when the user wants to participate in the brand management instead of the content provider such as the domain name controller will be. The user may submit the brand management participation information to the keyword management server by clicking the button 350 of the keyword management interface 330 or may submit it using another known method capable of transmitting the brand management participation information to the keyword management server. The click of the button 350 is to redirect the user from the keyword management interface 300 to the domain owner brand management interface. An exemplary domain owner brand management interface is shown in FIG. The domain owner brand management interface is separate from the keyword management interface in this exemplary embodiment, while the brand management interface and the domain owner keyword management interface may be combined into a single interface or may be separated into two or more interfaces.

In step 1420, the keyword management server may generate a recommended third party list. This list is automatically generated from third parties who are interested in participating in brand management that provided information to the domain name registry or keyword management server. This list may be displayed to the user via a domain owner brand management interface, such as section 1510 of interface 1500 shown in FIG. The domain name controller can review the list of accessible third parties and select one or more third parties with the ability to make suggestions in the brand-based keyword mapping for the domain. If the domain name controller does not wish to display these third parties in the section 1510, the domain name controller may enter the name of the third party using one or more text boxes 1515. The domain name controller may submit a selection of a third party to the keyword management server. For example, the domain name controller may submit a selection to the keyword management server by clicking button 1514 via interface 1500. [

In step 1430, the keyword management server may receive the domain name controller selection of one or more third parties. The keyword management server may receive selection of one or more third party domain name controllers using any known method of receiving data.

In step 1440, the keyword management server may transmit the third party selection information to the third party. Third party selection information may include information relating to the domain name as a third party's authority to submit the proposed brand-based keyword mapping. For example, the third party selection information may include the domain name, the domain name owner, the type of site, and the date and time under the approval of a third party. The keyword management server may display third party selection information on a third party brand management interface such as an exemplary third party brand management interface as shown in FIG.

As shown in FIG. 16, the third party brand management interface may include sections 1610, 1620, 1630, 1640 and 1650. The keyword management server may display a domain name that has recently been granted authority to perform a brand-based keyword mapping in a section 1610. The keyword management server may also display one or more participant names in section 1620 that accommodate one or more of the third party brand-based keyword mappings. The keyword management server may display the section 1630 which allows the input of the suggested URL and the proposed keyword to a third party by pushing the button 1632 and submitting the brand-based keyword mapping to the user will be. According to the embodiment shown in Figure 16, the third party "Alpha Corp." submits the URLs associated with the keywords "Alpha,""AlphaWidgets," and "Alpha Merger" to the domain name controller "Acmecorp.com." .

The keyword management server may display the keywords approved by one or more domain names in section 1640 and display the brand-based keyword mapping rejected by one or more domain name controllers in section 1650. Although not shown in FIG. 16, section 1650 may include the reason that the domain name controller rejected the brand-based keyword mapping. For example, the domain name controller may reject brand-based keyword mappings because the keywords or related URLs are not appropriate. In other cases, the brand name controller may reject the brand-based keyword mapping because the keyword is already in use by another user or is being used by another third party.

Returning to FIG. 14, at step 1450, the keyword management server receives a brand-based mapping from a third party. For example, a third party may enter keyword 1634 and associated URL 1636 (shown in FIG. 16) and submit a brand-based keyword mapping to the keyword management server by pressing submit button 1632. If the third party wishes to change the brand-based keyword mapping, the third party may submit the new mapping to the keyword management server for approval again by the domain name owner. The domain name controller may review each modified keyword mapping or "opt out" for approval by a trusted third party. In addition, the domain name controller may refuse to provide keyword mapping to a third party at any time.

In step 1460, the keyword management server may send a brand-based keyword mapping to the domain name controller. The keyword management server may display the brand-based keyword mapping on the domain owner brand management interface, such as section 1520 of the brand management interface 1500 of FIG. The domain name controller must decide whether to accept or reject the brand-based keyword mapping. As shown in FIG. 15, if the domain name controller accepts keyword mapping, the domain name controller must select a button corresponding to "yes &quot;. If the domain name controller rejects the keyword mapping, shall. Although not shown in FIG. 15, the domain name controller may provide a comment indicating why the domain name controller has chosen to decline the keyword mapping, and may also provide another keyword or associated URL to the keyword management server or a third party have. In addition, the domain name controller can automatically select a request for the keyword management server to compare the name of the third party with the presented keyword. If the name of the third party and the presented keyword are similar or identical, the domain name controller should instruct the keyword management server to accept the keyword mapping automatically. Similarly, the domain name controller causes the keyword management server to automatically reject the proposed keyword mapping if the name of the third party does not match the keyword. If the keyword matches the forbidden keyword list generated by the keyword management server and / or the domain name controller, this also causes the keyword mapping to be automatically rejected.

In step 1470, the keyword management server may accept or reject the brand-based keyword mapping based on the selection of the domain name controller. Once the keyword is accepted or rejected, the keyword management server notifies the third party. For example, the keyword management server may display information relating to approval or rejection of a brand-based keyword mapping on a third-party brand management interface 1600, such as section 1640 or section 1650.

In step 1480, the keyword management server stores the brand-based keyword mappings approved by the domain name controller in the brand-based keyword registry database. The brand-based keyword mapping allows the client to access the web page directly in response to a user-supplied URL keyword that is the same as or similar to the keyword in the brand-based keyword mapping. The brand-based keyword registry database includes brand-based keyword mapping, such as third-party entities, whether third parties are authorized to automatically update brand-based keyword mappings, statistical information, and various information related to brand- Additional relevant information can be stored.

Although FIG. 14 illustrates a process performed using specific steps, embodiments of the present invention need not perform all of the steps shown in FIG. 14, and may perform steps in a different order as needed, have.

4 is a flow diagram depicting an exemplary method for providing a web page directly to a client in response to a user-provided URL keyword in connection with a particular embodiment of the present invention. In the embodiment depicted in FIG. 4, a client 410 such as an end user sends an HTTP request for a web page associated with the URL to the content provider server 420 (step 411).

For example, as depicted in FIG. 5, the user may enter the URL 510 "http: //www.newnews.eom/#earthquake" into the address field of the browser. This is because the browser is transmitted to the host web server 420 having the domain name "www.newnews.com " through the HTTP GET request 600 as shown in FIG. More specifically, in response to a user-specific URL 510, a request is sent from the user's browser to the root '/' directory from the web server 420 hosting the "www.newnews.com" domain name 620 via the HTTP request 600 And request a corresponding resource 610. Typically, the web server may be modified for transmission of HTML file defaults such as "index.html" in response to a request for a root directory.

The URL 510 may include a resource string 510a and a keyword 510b indicated by a pound or hash symbol "# &quot;. The technique of separating URL keywords using hash symbols is similar to the use of URL fragment markers for syntactic purposes, which are defined in detail in the Internet Engineering Task Force's RFC 3986 URL.

In conventional methods, a fragment marker is used to identify a particular section within an HTML page received from a web server, and if given to an HTML page, the browser is specified to be able to search the section directly. For example, within the HTML text of a web page, the creator of the web page can physically distinguish the content of the web page from the web page with an "overview" section, an "analysis" section, and a "conclusion" section. The author can also place HTML anchor tags such as <a href="#introduction">','<ahref="#analysis">',and'<ahref="#conclusion">') in front of the content in the corresponding section . If the user requests a URL containing a fragment marker such as "#analysis", then there must be an HTML anchor tag for the "#analysis" fragment marker, and the user browser will not only download and display the HTML of the referenced HTML document It will automatically scroll directly to the section of the HTML document that is preceded by the "#analysis" fragment marker. Thus, conventional fragment markers are processed entirely within the web browser, which does not include the specific resource 610 for the browser HTTP request 600 in the web server, as shown in FIG. And is processed after the content is inquired by the HTTP request 600. [ Conventional use of fragment markers also does not generate additional HTTP requests and only displays what content is returned to the user after determining what content is returned when allowing execution within the browser.

As described in more detail below, the syntax of the fragment marker can be used instead of indicating a URL keyword corresponding to the present invention. This is because the fragment marker 510b "#earthquake" does not point to a browser with the initial scrolling focus on the section of the web page anchored by the user with the text "earthquake " Is directly requested from the content provider server 420 that responds to the web page regardless of the specific web page. Thus, it may be a web page different from the originally requested web page. There is a case where a content provider uses a fragment marker as an anchor of an initial page as well as a method of providing a specific web page directly to a user. The content provider and / or the keyword resolution service may determine whether an anchor or a keyword takes precedence. For example, the keyword resolution service automatically prioritizes the anchor if there is no contradiction in the keyword, and the keyword is preferred if the contradiction exists. Thus, the client can directly access a specific web page.

Successive users of a particular embodiment may have heard of a recent major event related to an earthquake in some foreign country. Therefore, users may want more information on these events from the www.newnews.com website. However, as a first search destination, it is possible to search a document providing information on a scientific summary of an earthquake or a historical summary of an earthquake, rather than a home page of newnews.com, or to search for a recent earthquake information Or may attempt to search through the sub-directory. This is also necessary to know if the user does not have enough information about the relevant country or where to start searching. The user can simply specify the basic domain name 510a and the keyword 510b for searching a topic in the URL.

By allowing the browser to make an HTTP request for a basic domain name / keyword combination, the user can provide a web server hosting the www.newnews.com domain name to the user to provide the user with a particular web page of the NewNews content provider It is a request. For example, after a NewNews content provider recognizes an important earthquake in a foreign country, the editor of the site may create a web page detailing all the relevant information that the user considers desirable. At this time, It is possible to provide approximate information about the user. The web page provided by the assignment and creation of a URL, such as URL 315 in FIG. 3, may be a new keyword "earthquake" for the www.newnews.com domain name associated with URL 315, To the keyword system interface 300 that registered the keyword.

5 shows another potential form of a URL to which a keyword is added according to the embodiment of the present invention. For example, a keyword (here "anvil") as a preferred embodiment at URL 520 may be embedded in some form of URL on a browser that provides sufficient information according to the HTTP request. Therefore, there is no scheme or mechanism (here "http") and the root directory "/" symbol can be omitted between the domain name and the keyword. In the embodiment of the URL 520, the user enters a domain name of an online merchant (here "acmecorp.cc") to make a request for a particular type of item purchase (here "anvil") on a content provider- To the keyword.

As indicated in the URL 530, the keyword may include unacceptable URL characteristics, such as a space, where the URI performs the encoding operation before sending the HTTP response, which may be a word or non-ASCII attribute To encode a specific nature, such as. In the embodiment of the URL 530, the user may use the domain name of the local business (here "momandpopshop &quot;) to request a content provider-indication web page of information on a particular promotion or event .com ") keywords.

As indicated in the URL 540, the keyword may allow wildcards, regular expressions, or other characteristics for flexible string matching of the keyword, Alternative keywords may be included so that they can be distinguished by a landmark. The URL 540 may not be directly associated with the domain name, but may be placed in a directory structure or other path within the URL. The keywords placed in the path are adjusted in several ways. For example, a keyword gives preference over other path information, which means that if a keyword is found in any path in the URL, it can not simply be ignored.

Optionally, the path preceded by the keyword may define a range or provide an associated namespace for the keyword. For example, a content provider may create a first web page for the "admission" keyword placed in the "/ students / undergraduate /" path of the URL (for example, providing admission information for undergraduate students) You can create a second web page for the "admission" keyword placed in the "/ students / graduate /" path (for example, if you provide admission information for graduate students). A similar technique may be employed by a content provider providing a "vanity" URL within a single domain name of various other companies or organizations. For example, for Facebook.com, which provides vanity URLs such as "www.facebook.com/cocacola" or "www.facebook.com/toyota", the same keyword (for example, "# 2011challenge") would be "/ cocacola Quot; path "or" / toyota "path.

In an embodiment of the URL 540, a user may select a specific topic (here "admissions") in the domain name (here "www.vanderbilt.edu") or other nonprofit organization A keyword may be appended to request general information (e.g., a content table) from a content provider-directed web page.

As indicated in URL 550, the keyword may be appended to or appended to the query string in the URL. Similar to the URL 540, the query string in the URL 550 may be ignored after the keyword is detected, or the name space may be provided therein such that the keyword has a distinct or specific meaning. In a particular embodiment, the URL query string is used to determine which webpage (e. G., &Lt; / RTI &gt;&lt; RTI ID = 0.0 &gt;Lt; RTI ID = 0.0 &gt; a &lt; / RTI &gt; In an embodiment of the URL 550, a user may request an online information service provider ("site &quot;) to request a content provider-directed web page that provides status or real- .netops.globalsecuritiestrade.org ") can be attached to the domain name.

As indicated in URL 550, the keyword may be appended to a domain name that includes multiple sub-domain names. Also, similar to the path of the URL 540, the specificity preceding the domain name may define a namespace within a keyword that has a distinct or specific meaning. For example, the content provider may direct the first web page about the keyword "ETFs" if the more common second level domain name "globalsecuritiestrade.org" (e.g. providing general merchandise information for the ETF) ETFs "if there is a sub-domain that provides a real-time trade price for a more specific sub-domain" netops.globalsecuritiestrade.org "or another sub-domain within a sub- To a second web page about &lt; / RTI &gt; On the other hand, FIG. 5 shows a top level domain, a second level domain having a fragment marker and a keyword subsequent to the highest level domain, a third level domain, and a fourth level domain, which is an embodiment of the present invention. The domain can also perform fragment markers and keywords, and perform fragment markers within URLs that contain one or more of these level domains.

A plurality of keywords 560a, 560b, and 560c may be placed in the URL as shown in the URL 560. [ As an example of the URL 560, the user may attach multiple keywords to the domain name of the online merchant to request one or more content provider-directed web pages for a particular article name. Various techniques may be employed to process a plurality of keywords, the method comprising: providing a web page responsive to a first keyword for directing a web page to determine whether there is a match for each keyword; Assigning order priority to various keywords and providing web page instructions for top ranked keywords in the URL; Or a special keyword combination (e.g., a first web page for keyword 560a, a second web page for keyword 560b, a third web page for keyword 560c, and a fourth web page for a combination of keywords 560a, 560b, and 560c) And providing a specific web page mapping for the web page.

Other techniques or syntaxes can be used to identify URL keywords. For example, the URL keyword is "$", "|" Or "@ &quot;, which is not valid for a URL character unless converted to hexadecimal form. However, since such a character or the like may be used in the URL to qualify a file name or a valid path, it may be desirable to use it in some embodiments instead of a hash symbol. This is because most web browsers have been modified to omit fragment markers identified by hash symbols in HTTP requests. Thus, there is no risk to web servers that do not provide functionality for domain-specific keywords, which makes it possible to attempt to locate a file that actually contains the keyword text within the file name.

The URL keyword of the present invention may include international or special characters such as those not allowed in URLs in other cases. This is because such a character can be simply converted to a hexadecimal form by the user's browser prior to the transmission of the HTTP request. For example, a content provider, such as a book seller who wants to create a keyword web page for a resume writing book, can create a keyword using the appropriate international character, which allows the user to see that the "#resume" This keyword can easily be expressed by the user's browser when the HTTP request is made by the URI to be encoded as "# r% C3% A9sum% C3% A9".

Returning to step 421 of FIG. 4, the content provider server 420 receives the HTTP request 610 and responds by sending an HTTP response 700 as depicted in FIG. The HTTP response 700 includes both the header information 710 and the payload data 720. At this point, the content provider server 420 is notified that the keyword "www (510) " is not included in the HTTP request 600 because the keyword 510b is not included in the HTTP request 600, .newnews.com / "might actually not be aware of whether it was a request for a root web page in www.newnews.com or simply for specifying a domain name for domain-specific keywords. Therefore, the content provider server 420 transmits the payload 720 including the HTML text for "index.html &quot; on the server.

However, in order to allow for the possibility that the client 410 has been requested a domain specific keyword, the content provider server 420 may generate a request for a domain-specific keyword in the HTML document / payload 720, such as, for example, And may include positive client-executable code. In the exemplary embodiment, the client-executable code is included in the "<head>" section, while the client-executable code is included anywhere in the HTML document. The client-executing code may include JavaScript or other client-running program 721b, and their contents are provided directly by the content provider server 420. [ On the other hand, the content provider server 420 links to only a program file located in another server such as the keyword resolution server 430. Using this approach, the client 410 can create an individual HTTP request to the keyword resolution server 430 for the program file specified by the link 721a, which once the program file is received, Can be performed.

In step 412, the client 410 determines which script contained in the "<head>" section 721, for example, before retrieving or providing any content in the "<body>" section 722 of the HTML document 720 To execute a client-executing program such as a browser rule on whether to execute the client-executing program. The client executing program can check any URL keyword that the user has included in the requested URL. For example, if the keyword is a fragment marker, the client-executing program can access such a fragment marker because the client-executing program can be executed in the client 410 against the content provider server 420. In the embodiment of the URL 510, the client-executing program can identify the fragment marker "#earthquake" as a domain-specific keyword.

In step 412, the client-executing program sends a request for a URL for a specific content provider-directed web page to the client 410 through a web page or keyword for the keyword through a response confirming the presence of one or more domain- The individual keyword resolution server 430 to perform an individual HTTP request. For example, as depicted in FIG. 8, in the case of the URL 510, the client 410 may perform an HTTP GET request to the keyword resolution server 430 using the URL 800. The URL 800 includes a domain name 810 of the keyword resolution server; A path 820 of the server-side script on the keyword resolution server 430 that can perform the keyword-lookup operation; And a query string 830 in which both the original URL 830a and the domain specific keyword 830b requested by the client are specified.

For example, the client-executing program may perform synchronous or asynchronous HTTP requests to the keyword resolution server 430 using techniques known in the art, such as Asynchronous JavaScript and XML (AJAX) or JQuery. A client-executable program can use the HTML "<IFrame>" element or the HTML "<script>" element to make HTTP requests to the keyword resolution server, which is targeted directly at the URL hosted by the resolution server. A chapter having a skill in the art will appreciate the means by which domain-specific keywords may be provided to the keyword resolution server 430 for resolution through other means of providing a user-requested URL.

In step 431, the keyword resolution server 430 may determine if any particular web page is specified on the content provider web site for the requested keyword, and thereby provide the client with a target URL corresponding to the particular web page again will be. For example, in the case of the URL 510, the keyword resolution server 430 may provide the client 410 with the URL 900 as shown in FIG. 9, 315). &Lt; / RTI &gt; The content provider server 420 may provide the client 410 with the URL 900 as a simple text string within the AJAX response. The keyword resolution server 430 may redirect the URL 900 to the client 410 using the HTTP 301 or the redirect 302, for example.

In step 413, the client 410 may perform a new HTTP request to the content provider server 420 for the target URL provided by the keyword resolution server. For example, the client 410 may make an HTTP request to the content provider server 420 for a web page associated with the URL 900. Also in response, the content provider server 420 may provide an HTTP response that includes HTML text for the web page specified by the URL 900. [ Accordingly, the content provider provides the client 410 with the web page pointed out for the keyword "earthquake &quot;. The client is able to receive and display the web page specified by the URL 900 within the main browser window for the user to confirm and interact with it.

The above technique for providing a content provider-directed web page in response to user specific keywords has additional advantages and processing advantages. The client can request the domain specific web page using an existing browser program without requiring a modification or increase in the functionality of the browser program such as browser plug-in or add-on. In order to implement the present invention, a user has the ability to include a fragment marker in a URL, and only a basic function for executing a user executing program such as JavaScript is required in the browser.

The content provider can perform a domain specific keyword function that responds to HTTP through only a slight modification of the existing server-side script or program. In particular, the content provider is required to include only a small amount of client-executable code within each web page in the domain for a content provider wishing to provide domain specific keyword functionality. The content provider can also leave it on the client browser and leave it to the associated keyword resolution server to perform the keyword resolution work. In fact, if the content provider includes a client-run program within an HTTP response for the web page, the content provider's server may request the client for a particular web page in response to the domain-specific keyword request or in response to the previous keyword resolution Regardless of the program. Since the content provider server always returns any requested web page along with the client-run keyword resolution program, the content provider can be assured that the client requesting the web page to actually perform the web page receives the web page, As a means for specifying a domain namespace for a URL keyword, a client that simply requests a web page can provide a client-executing program necessary for keyword resolution.

Similarly, using the syntax of the fragment marker specified by the domain-specific keyword, the user performs an HTTP request including a URL keyword to any content provider without the risk of generating a server response error regardless of whether or not the content provider can provide the keyword can do. Because the browser does not send fragments marker text to the web server, the insertion of domain-specific URL keywords in the HTTP request to the web server does not cause the web server to generate any errors related to the keyword and simply replace the web page of the URL without a fragment marker Downloaded and displayed. In addition, if a user wants to specify a domain-specific keyword for a web page that is not instructed by a content provider, the keyword resolution server provides an empty string in response to the resolution query, and only the web page of the base URL is downloaded And display.

In the case of a keyword found corresponding to the content provider-instruction web page, the execution code for requesting resolution of the keyword and redirecting the client to the resolved target URL is "<head>" of the original HTML document returned from the content provider server. Section, so this code can be done before the original HTML document occurs. Thus, the user can only view the originally requested HTML document at all for a short time, but can only be displayed to the user directly visiting the web page related to the keyword.

In addition, the use of a separate keyword resolution server in addition to the keyword management interface 300 allows the non-skilled employees of the content provider to create or modify keyword-to-web page mappings directly from the business without involvement of employees having the same skills as IT professionals To give permission. This saves money because content providers themselves can manage keywords without requiring special IT knowledge. Content is also rapidly changing and existing conventional search techniques may be required for IT professionals and are required for web server re-transformation.

In yet another embodiment, the content provider itself may act as a keyword resolution service provider. In particular, after confirmation of one or more URL keywords, a client-run program provided to the client by the content provider server may instruct the client to provide the content provider with a content provider- You can request a query for an instruction web page.

The present invention does not limit the situation only when a user manually types a domain-specific keyword in a URL. On the other hand, domain-specific keywords may be included within the requested URL in the same way as specified within hyperlinks existing in HTML documents, and may be included in a "bookmark" search provided by a web server, such as the HTTP Redirect format, . &Lt; / RTI &gt;

The invention allows a user to have a typical representation such as a wildcard or "engineer * &quot;, which can be resolved in the sense of" engineer, "" engineers, "" engineering, "" engineering schools, In some embodiments, if there is a sufficient number of potential resolutions for a wildcard or typical presentation keyword, the user can expedite the list of selections.

Those skilled in the art can host the resources hosted by each URL by a separate web server, even if the original requested base URL of step 411 as well as the target URL of step 413 are hosted by the same content provider . &Lt; / RTI &gt; Also, while primarily described herein as the "domain-specific" keyword, those of skill in the art will be able to extend the concept to provider-specific keywords. For example, if a content provider owns and hosts two different domain names "zulumail.tv" and "zmail.tv", both domains can be connected directly to the same hosting server or hosted on the same web server. have. The content provider may also direct a single web page for the keyword "#forwarding " whether or not the user asks for it as part of the respective domain-based URL. "http://zulumail.tv/#forwarding" and "http://zmail.tv/#forwarding" can all be resolved to the URL "HTTP://zmail.tv/user_options/mail_handling/automatic_forwarding.htm" It is because.

Similarly, the concepts of the present invention are established to allow for the first content provider to point to another content provider's web page for a given keyword. For example, if a large number of small weather-related Web sites are dependent on a larger service provider that can provide weather information in real-time, content providers responsible for each small website may be able to use a larger And may direct a web page hosted by a content provider.

This means that the particular web page indicated for a given keyword is not limited by the content provider in this way. However, as described in connection with FIG. 2, the content provider may be restricted and refers to being able to designate a keyword for a website or domain that neither possesses nor controls or has rights. Also, a given content provider-assigned keyword is only meaningful within a particular domain name, which may include a URL path, a query string, and / or a port number.

There are also a number of execution options for embodiments of the keyword / URL mapping of the present invention. 10, the user 1010 may enter a direct URL search, such as "example.com # keyword, " which may be retrieved from the browser 1020 via example 1020. &lt; com server 1030 to send an HTTP GET request. A GET request from the browser 1020 may request a resource corresponding to the root "/ " directory from the server 1030 hosting the" example.com " In general, the web server may send a default HTML file such as "index.html," in response to a request for a root directory, and may request a keyword resolution program such as JavaScript code and a keyword / URL mapping together. The browser 1020 performs a keyword resolution program for determining a URL to be mapped to a keyword and a mapped URL. The browser 1020 sends a request to the server 1030 for the mapped URL page and in response to the request the server sends back to the target page (e.g., the page associated with the keyword). In contrast, the content provider server may request a resolution of a keyword from a separate server, such as a keyword resolution server, or may direct a resolution request to a client.

Keyword / URL mapping can be performed in a variety of ways. For example, keyword / URL mapping can be done on the server side or on the cloud-based or client side. FIG. 11 shows an exemplary method of performing keyword / URL mapping performed on the server side. As shown in FIG. 11, there is an Internet user 1110, a browser 1020, a server 1130, and a keyword registry 1140. The keyword registry 1140 may be modified by the domain owner 1150 in relation to the domain owner 1150 associated with the keyword at a particular web site within the domain and may be a separate server or a part of the server 1130 itself. Additionally, the brand-based registry (not shown) may be a separate or combined keyword registry 1140.

As shown in FIG. 11, the user 1110 may input a URL direct search such as "example.com # keyword," The browser 1120 can interpret "#" as another character, for example, "@", which is requested on the server side using keywords and new characters. The server 1130 may communicate with the keyword registry 1140 to determine the URL mapping of the keywords. The server 1130 can also send a default HTML file such as "index.html," in response to a request, for example, with a keyword resolution program such as JavaScript code. The browser 1120 sends a request to the server 1130 for the mapped URL page and the server returns the target page in response to the request.

FIG. 12 illustrates a method of performing keyword / URL mapping performed on the client side. 12, the user 1210 may enter a direct search URL such as "example.com # keyword," in the browser 1220, which causes the browser 1220 to send an HTTP You can perform a GET request. A GET request from browser 1220 in response to a user specific URL direct search may request a resource corresponding to the root "/ " directory from server 1230 hosting the" example.com & Typically, the web server sends a default HTML file, such as "index.html," in response to a root directory request, along with a keyword resolution program such as JavaScript code and a keyword / URL mapping request. The browser 1220 performs a keyword resolution program that communicates with the cloud infrastructure 1240 that includes the keyword registry 1242. The cloud infrastructure 1240 will determine the URL to which the keyword is to be mapped and the mapped URL and sends the URL mapped to the browser 1220. The browser 1220 sends a request from the server 1230 for the mapped URL page and then the server returns the target page in response to the request.

The keyword / URL mapping may be performed entirely on the client side. In certain embodiments, the client may maintain a local file system or database for resolution of the URL keyword, which is more reliable than the content provider or any other third resolution service provider that resolves the keyword / URL mapping. For example, HTML 5 allows client-executable code, such as JavaScript, to access queries in the local database to query data or content. A client-run program received from a content provider is a local database that looks up a mapping between a keyword and a URL and is reliable. Once a URL associated with the URL is installed, a browser can be directly connected to the URL, You can cut out the request. In yet another embodiment, the client-executable code may itself create a local file system or a database for URL keyword resolution.

In another embodiment, the URL keyword resolution operation can be performed entirely on the server side without depending on the client according to the execution of the client execution code. For example, as shown in FIG. 13, the user 1310 may enter a URL direct search such as "example.com # keyword," in the browser 1320. Unless the URL keyword is restricted by a character other than a hash symbol (e.g., the "@" character), the keyword is transmitted to the content provider server 1330 as part of the client's initial HTTP request 1320, unlike the fragment marker . The content provider server 1330 can identify the keyword, for example, and also determines an appropriate URL mapping for the keyword and redirects the appropriate URL of the keyword to the client 1320 (e.g., using the HTTP (301) redirect command) will be. This is because the client 1320 proceeds without relying on the execution of the client-executable code. Meanwhile, the content provider server may request a resolution or request a resolution of a keyword from a separate server such as a keyword resolution server.

In another embodiment, the client-run program, the keyword resolution server, or the content provider server may provide any default option if the client requests a keyword that is not created or directed by the content provider. For example, in response to a request for a keyword that does not exist, the client can simply provide the web page identified by the base URL of the initial HTTP request. Meanwhile, the client may be provided with a JavaScript alert web page or may convey other types of notifications to a user requesting a keyword that does not exist. The user can be provided with a potential list of existing keywords, which allows a user to request a keyword by avoiding a non-existing search term. The user can be provided with a list of conventional web pages generated using a conventional keyword search technique. If you select a matchable keyword from this list, the user will be able to select it more easily.

In another embodiment, if a user enters a hashtag in a keyword request to a content provider, a hash module may be provided for the list of available keyword modules in relation to a particular domain. For example, the hash module may be a browser add-on or a plug-in that determines in real time whether or not the user enters a hash tag in the address field of the browser. If so, the autocomplete module will communicate with one or more content providers, a client-executing program, a keyword resolution server, or a content provider server for determining whether or not a keyword is associated with a particular domain. As more alphanumeric characters are entered into the browser by the user, the list of available keywords related to a particular domain will become narrower. If a domain related keyword exists, the hash module will generate a pop-up list containing these keywords. If there is no keyword associated with the domain, the hash module will redirect the user to the search service page.

In another embodiment, a smart search module may be provided to a user if a particular domain is capable of keyword smart search. For example, the smart search module searches domains entered in the search window in real time, verifies the add-on or plug-in to the browser, and communicates with one or more content providers, client-run programs, keyword resolution servers, To determine the existence of a particular domain for a related keyword. The smart search module may then display an indication of a domain associated with the keyword, for example, by changing the color of the search box or by inserting a particular graphic of the browser or associated web page.

In addition to providing the keyword management interface and / or keyword resolution service, the resolution service provider may allow the content provider to access various information and statistics about the requested keyword resolution from the client. For example, the interface 300 of FIG. 3 may provide the user and / or the content provider with multiple views and / or downloads of each created keyword requested from the client. In another embodiment, the resolution service provider can track how many keywords have been used and can determine who uses the keyword, what type of keyword is used, what the visited website is, and various information And the like can be tracked. The interface 300 can also provide information about the number of times a request for a variety of nonexistent keywords is made by the user so that the content provider can determine the need to create additional keywords according to user demand. Information on such nonexistent keywords as well as information due to misspelling of existing keywords may be included. This information may be used by a content provider to generate a keyword having a homepage or a misspelling of an existing keyword And thus allows the enhancement of the allowed wildcard or regular expression matching function.

Resolution service providers also enable malware removal security scanning. Because there are so many websites accessible on the Internet, it is impossible to scan all of the malware. However, because the resolution service provider is aware of the URL associated with a particular keyword, the resolution service provider may use the malicious code detection and scanning method disclosed in U.S. Patent Nos. 12 / 982,508 and 12 / 982,540, for example, You can decide if the code has been removed. The disclosures of these patents are incorporated herein by reference in their entirety. Thus, when a user enters a direct search URL such as "example.com # keyword," the user will be provided with the highest level of assurance that the URL is safe from the browser and thus will not include malicious content.

In yet another embodiment, one or more content providers, client-run programs, and keyword resolution server content provider servers automatically optimize a particular web site based on such client verification infrastructure. For example, the client-running program may prompt the user to use a user device (e.g., a mobile phone) that conforms to the specific device specification of the web site. The client performing program automatically optimizes the web site using the method disclosed in, for example, U.S. Patent Application No. 13 / 078,680 entitled " System Apparatus and Method for Mobile Device Detection "issued Apr. 1, 2011, The disclosures of which are incorporated herein by reference in their entirety.

2. Namespace-based Smart Search

Various embodiments consistent with the present invention may use the name from a generic namespace that includes a non-DNS (rather than URL) namespace. This means that even if the disclosed embodiment is one or more namespaces at the same time, it can operate any namespace. In general, the namespace contains the name, and the name owner has authority for the namespace (or subspace), which authority may in some cases be delegated. The namespace can be public or private and can be hierarchical or horizontal. In particular, non-limiting embodiments of the namespace are as follows.

A collection of all top-level domains forms a namespace. It also forms a namespace through a collection of all the domain names - for example, all second-level domains in a top-level domain, third-level domains, all subdomains, and so on. The term 'domain' in the 'domain name' refers to the fact that each name has its owner and has the authority for 'space' associated with the name. In a conventional DNS having a hierarchical structure, the name owner has authority to any subdomain under the domain. For example, the owner of "example.com" is "a.example.com", "b.example.com" . The name owner can delegate the authority of this subdomain to the other party, but the owner of the name has authority over the delegated 'domain'.

There are many DNS namespaces rather than DNS. For example, the TWITTER namespace is a horizontal public namespace, not DNS. TWITTER is the smallest blog service that allows users to share short messages to their followers. Each TWITTER account has its own name or is managed via a string starting with the "@" character, for example "@example_brand".

Other embodiments of the namespace include the FACEBOOK namespace and the LINKEDIN namespace. Regarding these resources, users can typically retrieve the example user page by typing the specified URL's input format, specifically http://www.facebook.com/example_user_name or http://www.linkedin.com/example_user_name. have. The format of these URLs provides a namespace of all names in the form example_user_name for accounts that exist in each resource.

 Another namespace is the email address space. The disclosed embodiment herein discloses that if a general user has an email address of &quot; user@example.com &quot;, a command string of the form &quot;user@example.com&quot; &quot; Allows you to browse the same information.

 Yet another embodiment is a namespace defined by a reduced URL. Reduced URLs are adopted as abbreviated forms of long, complex URLs. This is usually in the form of 'name / code', where 'name' is the short domain name and 'code' is a short string representing a specific reference to the entire URL. The input in the form of 'bitly: name / code! keyword' may be a process of providing a search service in such a way that it can browse additional information about a short URL or a resource referring to it according to the embodiments disclosed herein.

An embodiment of a private name space includes a list of users in a company and a list of resources and / or devices in a local area network, such as a user's home.

For the sake of clarity, various embodiments are described in this specification assuming that the owner of the brand (e.g., Gimbels) is the owner of the domain corresponding to the brand (gimbels). However, the present invention is not limited to the above description, and it is possible to apply the present invention outside the description.

17 shows an example of a system 1700 for retrieving desired network resources by an agent 1710 to which the principles of the present invention are applied. A complementary method will be described with reference to Fig. As shown, the system 1700 comprises an agent 1710 that communicates with the search service 1780 and a user 1705 that communicates with the agent 1710.

In various embodiments, the user 1705 may provide input search data 1751 that shapes and details or describes the desired network resource, and input (e.g., an input) to refine or select at least one existing proposal 1714 Lt; RTI ID = 0.0 &gt; 1726 &lt; / RTI &gt; The user may enter search data 1751, for example, by typing the relevant field or by clicking on a link with a phrase that is compatible with each other, or by talking to a microphone capable of capturing voice reminiscent of the data It can be detailed. One example of the input search data 1751 is a character string of 'gimbels shoes'. In one embodiment, user 1705 may be a human user and may be a computer system programmed to perform the functions of providing input search data 1751 and input data 1726.

Thus, user 1705 may be a computer or a performing computer code. Such a user may provide any of the input search data 1751, the proposed selection data 1771, and the input data 1726, or a combination thereof. For example, a performing computer code (e.g., an application) may provide search data 1751 to a search service 1780 in an automated manner to enable searching for content related to one or more defined keywords in an automated manner. Such a performing computer code does not require human contact when providing search data to a search service.

In various embodiments, the agent 1710 (which is also referred to as a search client and which is yet another example of the agent 1710) is capable of interacting with the user 1705 and the search system 1780 as shown herein . In some embodiments, the agent 1710 may be connected by network locators 1735-1737 or by network location data 1772 to interact with the detailed network resources. The agent 1710 may accept, receive, obtain, or access data entered from the user 1705 and may authorize, receive, obtain, or access the proposed data 1762 and network location data 1772 from the search service 1780 can do. The user 1705 may input the character to the agent 1710, for example, by typing a character in a related field or clicking a connection of a provided character or inputting a voice. For voice input, the original voice data can be converted into a character string that can be used in embodiments of the present invention using known techniques, wherein various types of devices are needed, including the agent 1710, the search service 1780, Or a separate computer capable of communicating with agent 1710 and / or search service 1780 in communication.

In addition, in connection with voice input, the user 1705 may employ a start-up operation to activate the voice interface if the start word is spoken aloud. The start word can be, for example, 'at' or some other namespace prefix. The agent 1710 may generally output, transmit, publish, or deploy a connection associated with the proposed data 1762 and network location data 1772 for the user 1705 and may include search data 1751 ), And the suggestion selection data 1771, as described above. The various embodiments of agent 1710 may also perform other functions.

In various embodiments, agent 1710 may be implemented through software, firmware, hardware, or a combination thereof. In certain embodiments, the agent 1710 may be a plug-in or add-on to a browser, an independent application, another program (e.g., a browser plug-in), or another service (e.g., a web service). Agent 1710 may reside within a search application (e.g., a browser) within a mobile device, such as a smart phone. Agent 1710 may be separate from a web browser, an interface or a variation within the web browser or a modification of the web browser address bar. In one embodiment, the agent 1710 may be performed within the client computer or within the web browser described in Section 1 above. More specifically, the agent 1710 may include all or part of the shape, function, intercommunication, performance details, code, algorithms, architecture, structure and characteristics of the web browser disclosed in Section 1.

In various embodiments, search service 1780 can be any one that can interact with agent 1710 and user 1705 as described herein. The retrieval service 1780 is generally capable of accepting, receiving, obtaining, or accessing input data from a user 1705 and is capable of accepting, receiving, retrieving, and retrieving retrieval data 1751 and proposed selection data 1771 from the agent 1710, It is possible to obtain or access it. Search service 1780 may generally output, transmit, publish, or deploy access for proposed data 1762 and network location data 1772 for agent 1710.

In various embodiments, search service 1780 may be performed through software, firmware, hardware, or a combination thereof. In certain embodiments, the search service 1780 may be a plug-in or add-on to an independent application, a server application, another program (e.g., a browser plug-in), or another service (e.g., a web service).

In some embodiments, the search service 1780 and agent 1710 may perform separate computer systems and may communicate with each other via a network (not shown) such as the Internet or a combination of the Internet and a wireless telephone network. In yet another embodiment, the search service 1780 and the agent 1710 may be executed in the same computer system, or may use separate programs or use the same program. In one embodiment, the search service 1780 may be performed within the URL keyword resolution server described in Section 1 above or as a server. More specifically, search service 1780 may include all or part of the shape, function, intercommunication, performance details, code, algorithms, architecture, structure, and characteristics of the URL keyword resolution server disclosed in Section 1.

As shown in the embodiment of FIG. 17, system 1700 may include an entity representation 1720 that is referenced, accessed and used by search service 1780 and agent 1710. In one embodiment, the entity indication 1720 may be performed as the content of the stored keyword mapping and / or keyword registry database published in section 1 above. The entity indication 1720 includes all or part of the shape, function, intercommunication, performance details, code, algorithms, architecture, structure and characteristics of the content of the keyword mapping and / or keyword registry database disclosed in Section 1 can do.

In various embodiments, an entity means any entity that has the authority or interest to control or control a network resource, e.g., a domain or a namespace. Gimbels is an entity because, through the above embodiment of the user-case, it is because it owns a brand of "Gimbels" (perhaps a trademark). Also, because 'Gimbels' is the registrant of the domain, it has the right to control the domains that are classified as '.gimbels', which detail network resources such as Gimbels web pages. The entity may be a content provider and / or a domain name controller as described in Section 1 above. In some embodiments, the entity may be a name owner or an agent of the name owner, where the term &quot; name owner &quot; refers to an entity that generally refers to a user or is primarily associated with a name. The name owner is also the person who registered the name in the given namespace. Depending on the intellectual property alignment, the 'name owner' may not have legal ownership of the name, but is primarily interested in promoting the use of the name to prove relevant information and services. In some embodiments, generic entity names such as 'zoo' may be associated with a particular entity through various techniques, such as a name auction. This is because generic names have associated entities.

In some embodiments, the entity representation 1720 may be stored in one or more databases (e.g., one or more directories). Such a database may be included in the first column entity name, for example, from the third party namespace. Thus, the first column entry for the entity name 'gimbels' would be '@gimbels', which corresponds to the Twitter namespace, 'fb: gimbels', which corresponds to the Facebook namespace, and '.gimbels' . &Lt; / RTI &gt; These inputs may be contained within the same entity display database or within a separate entity display database or in separate tables within one or more databases. In an embodiment using a separate database or table for each namespace, the namespace markers may be omitted from each database or entity name stored with the table instead of displaying a specific namespace.

In various embodiments, for example, an entity, such as a name owner, may include search data 1751 with certain characteristics, such as being associated with or mapped to an entity or having corresponding entity identification (ID) data 1752 (e.g., an entity name) Directs, directs, or refines the generated or returned proposal data 1762 for the search service 1780 to the search service 1780. In some embodiments, entity details or related instructions may be stored or appear within the entity representation 1720 and may also affect the functionality of the mapping 1782, the mapping 1784, and / or the lookup 1787. In some embodiments, the entity may manipulate the entity representation 1720 and / or the functionality of the mapping 1782, the mapping 1784 and / or the lookup 1787, which may include proposal data 1762 and / 1772 occurs very frequently when the search service 1780 is operating. In another embodiment, proposed data 1762 for creating or returning non-entities in accordance with the characteristics of the search data 1751 can be directly connected, installed, directed, or refined to the search service 1780. In some embodiments, the proposed data 1762 includes one or more keywords or keywords. The term 'keyword' can be, for example, 'shoeonsale' or a combination of many distinct words.

As illustrated in FIG. 17, each column 1731-1734 of the entity indication 1720 may include data associated with or displaying different entities. It may represent n entities as shown. As shown, the first leftmost column of each column may contain a marker for the entity, and in this example column 1731 begins with the entity marker 'Entity 1' and column 1732 begins with the entity marker 'Entity 2' Start. In one embodiment, the entity marker is a name from the namespace. The second column after each column may contain the number of proposals and network locators 'm' related to the entity indication in the first column. Thus, in this embodiment, there is one to many (e.g., 1 to m) relationships between each entity and the associated proposals and network locators.

Items 1735 through 1737 in FIG. 17 represent an extension or additional detail of the last two columns 1734 of the row for 'entity n' 123. Items 1735 through 1737 indicate that there are 'm' network locators and up to 'm' network resources displayed for entity n. As indicated, items 1735 through 1737 include one or more suggestions (which may be keywords) in the left column associated with the network locator in the right column, respectively. For example, entry 1735 for entity n 1723 includes one or more 'suggestions' 1724 for 'network locator 1' 1725. Therefore, there is one relation (one or more) between the proposal and the associated network locator in this embodiment (for example, > = 1 to 1).

In various embodiments, the network locator (e.g., 'network locator 1' 1725) is sufficient data to allow agent 1710 and / or user 1705 to locate network resources and / or information, Is sufficient data to allow user 1710 and / or user 1705 access to network resources. Examples of network locators may include URL, URI, URN, IP address, and DNS A record. Proposals (eg, 'proposal' 1724) in various embodiments are data or code that suggests or describes network resources that can be accessed using the network locator associated with the proposal. In some embodiments, the suggestion may include or enable the display of words, images, video, etc. that a person (e.g., user 1705) may cause to induce, think, ponder or associate corresponding network resources. The proposal includes an application comprising proposal data 1762 transmitted within the proposal data 1762 operated by the agent 1710 and / or an application activated by the search service 1780 for creation of the application. In some embodiments, the proposed data 1762 includes one or more keywords or keywords. One embodiment of the proposal relates to a network locator pointing to a Gimbels sales web page (e.g., a network locator such as "http://www1.gimbels.com/shop/clothing/shoes") for purchasing shoes. gimbels.shoes' character. Another embodiment of the proposal may be a character of the 'shoes' associated with the network locator pointing to the entity name of 'Gimbels' and the Gimbels sales web page for purchasing the shoes.

The term &quot; provisioning &quot; as used herein refers to a process whereby an entity (e.g., a title owner) creates, updates, and deletes entity display entries and stores a set of management services . The provisioning interface can be performed using, for example, a web page.

In some embodiments, before allowing the owner of the provisioning name associated with the entity representation data, the name owner needs to prove that he is the true owner, and there are various techniques for this. For a particular implementation, the name owner must indicate that it is the true owner in relation to the name of the entity in question. This can be accomplished, for example, when the name owner first establishes an authentication credential, such as when signing an account associated with a search service. For example, if the namespace consists of an email address, the confirmation message can be sent to a specific email address. It may indicate ownership of the email address as evidence of successful receipt of the confirmation message (e.g., by reply email or by receiving specific data at a URL within the email message). In another embodiment, if the namespace is one of the social networks (e.g., Facebook), the name owner is able to log in to the search service using the credential from the social network, indicating that it is the owner of the corresponding name. The mechanism for indicating the owner of the domain name is well known in the field of domain name management and can be used for the provisioning operation described herein.

Provisioning within the Twitter namespace can be accomplished using existing true twittering techniques. This allows the Twitter user to authenticate the Twitter user by automatically transmitting proof that the tweet is the owner of the associated name when the Twitter user attaches a message to the service. Thus, the provisioning of the search service through direct tweets can accept true requests to update the information within the search service entity representation. For example, a tweet from '@example_brand' to 'provisioning_operation' in the format 'update #news <URL>' or Twitter 'direct message' would update the network locator associated with '@ example_brand # news' to '<URL>' Can be used for. Consecutive to this embodiment, in any embodiment, no web interface or email is required, but only a direct tweet to the provisioning operation. The 'tweet' channel in the provisioning operation can be composed of a wide set of instructions, including the setting of the new entity name, keyword, and network locator.

Provisioning of social networks such as Facebook or Linkedin can be achieved by 'sharing' content with specific keywords through specific purpose applications within their respective environments.

In various embodiments, the entity representation 1720 may be performed through a number of well known methods in computer science, including directories, databases, data structures, lookup tables, arrays, records, linear codes, Also, in various embodiments, the entity indication 1720 may be performed as part of the search service 1780 and may be performed through a variety of methods well known in the computer science within a separate database system as a separate service. Its exact performance is not critical to the present invention.

An embodiment 1700 of the system shown in FIG. 17 for operation is described with reference to a shoe sales case embodiment as described below. In this embodiment, the user 1705 is a person who accesses or interacts with the merchant Gimbels web page to purchase shoes. To that end, the user 1705 performs input of search data 1751 (referred to as a 'command string') through the agent 1710 to any data 1751 that generally describes what is desired. The user 1705 can be a human or a programmed computer and the command string 1751 can be obtained by typing in the field or clicking on a link or talking to a microphone. The agent 1710 may have a network locator for the search service that is strictly coded through the software. In some embodiments, the user 1705 may type in the character string as the search data 1751 input via the agent 1710. [ In certain embodiments, the user 1705 may enter 'gimbels shoes', '@gimbels! Shoes', 'gimbels.shoes', '.gimbels! Shoes' in the omniba of the search bar or browser containing the agent 1710 . The agent 1710 may provide search data 1751 to the search service 1780. Thus, the agent 1710 can process the syntax of the search data 1751 to derive a request message to the search service.

In some embodiments, agent 1710 may provide search data 1751 in accordance with its input order (e.g., one character at a time). In yet another embodiment, the agent 1710 may provide a portion, section, or other portion of the search data 1751 and may include a specific name space identifier, a dreammeter, a starting character, a symbol, or the like (e.g., a period '. ',' Slash '/', 'colon': ', space'',' @ ','! ',' Fb ',' in ' Separation is possible. For example, in one embodiment, the input data of 'gimbels.shoes' can provide data for two parts, 'gimbels' and 'shoes', by recognizing '.' As a run meter or a starting character. In another embodiment, the command string '@ gimbels! Shoes' may provide the search service 1780 in two parts, 'gimbels' and 'shoes', according to the instructions in the associated namespace Is displayed). In another embodiment, the command string '@ gimbels! Shoes' simultaneously provides the character search service 1780 and the search service 1780 forms and accumulates the final command string. In some embodiments, the dreaming character may or may not be traversed. However, in another embodiment, the command string '@ gimbels! Shoes' may for example be the first' @ ', then' @g ', then' @gi ', then'gim'Quot;, or the like, to the search service 1780 by repeating a plurality of command strings with the final version being the final version. In this embodiment, the agent 1710 may provide search data 1751 as part of the search service 1780 as a whole.

In one embodiment, the agent 1710 can derive a query string derived from the input command string to handle the syntax of the command string and send it to the search service as a request. In one embodiment, the search data 1751 'example_brand # news' may be switched to 'example_navigation_service.com/lookup?name=%40example_brand&keyword=news' for transmission of the search service, for example. name ','% 40 'means'@', but this is not allowed as part of the usual URL). An advantage of this embodiment is that the syntax evolves continuously and the resolution is probably due to the connectivity of the search service 1780, which is more than one.

In some embodiments, agent 1710 may map search data 1751 directly to a traditional URL having a particular format. For example, the command string 'example_brand # news' may be converted to 'twitternavigator.net/example_brand/news' to be sent as a request to the search service 1780 and may be resolved using traditional DNS, although it is not shown in Figure 17 . In this embodiment, the search service may be performed as a collection of web services corresponding to different syntaxes, e.g., one of the Twitter names, one of the Facebook names.

In one embodiment, the agent 1710 determines based on the syntax whether the input search data 1751 is a traditional URL. In this case, the agent 1751 may process it using a traditional DNS system, or the agent 1719 may process it through a smart search command string, such as in the manner described herein.

Other embodiments of manipulating the command string syntax may be performed through a combination of the above exemplary embodiments according to the format and format of the retrieval data.

In embodiments in which the agent 1710 provides the search service with the beginning of the command string before the user completes the input of all the command strings, the agent 1710 suggests an entity name corresponding to the already entered portion of the entire entity name Lt; / RTI &gt; This may cause the agent 1710 to deliver to the search service 1780 the first segment of the entity name such that the entity name was entered by the user. The search service 1780 may provide the agent 1710 with a list of entity names beginning with the same or similar to the beginning segment of the character based on the matching of the beginning segment to the content of the entity display 1720. [ The agent can receive the list and display or present all or a portion of the list content to the user, for example, with a menu or a drop-down menu. The user 1705 may select all or a portion of the entity names presented in the menu in a conventional manner, e.g., by clicking. Clicking on the proposed entity name in any embodiment may automatically cause access to the field of all or some of the entity names as well as the associated namespace marker symbol. In one embodiment, the agent 1710 once generated communicates with the search service 1780 so that it can present or obtain a list of keywords associated with the selected entity name to the user 1705. These options are described below.

Consider providing the partial string '@thenew' to the agent 1710 as an embodiment to complete the entity name through the provided proposal. If the search service 1780 is configured to provide partial data, the agent can supply partial data to the search service 1780. The search service may match the partial string of '@thenew' with one or more entity names, for example '@thenewyorktimes' and '@thenewyorkyankees'. Search service 1780 may also provide agent 1710 with the completion of '@thenewyorktimes', '@thenewyorkyankees' and '@thenewyork'. The first two proposals use the actual entity name stored in the search service 1780, while the third proposal is a proposed partial completion that can be accomplished through one or more methods that can arrive at the stored entity name. Agent 1710 may present three proposed finished items to user 1705 in the form of a pop-up menu, for example.

On the other hand, the user can select one of the first two proposals. The method is, for example, to present the user 1705 with a list of keywords associated with the selected entity name described herein below. On the other hand, if the user selects the third proposed finished item, it can be determined whether it can be completed by either '@thenewyorktimes' or '@thenewyorkyankees'. Search service 1780 may respond to user 1705 by providing these suggestions for agent 1710 presenting, for example, a pop-up menu. At this point, the user 1705 may select a suggestion and, for example, the agent 1710 may successively provide the user 1705 with the obtained obtained from the search service 1780 as a proposed finished product for the keyword . The step of providing the entity name suggestion as described in this paragraph may be a mutual embodiment that provides partial data from the agent 1710 to the search service 1780 and the final entity name may be selected by the user 1705 Can be accompanied by a number of interactions before they occur.

Note that the embodiment is not strictly limited to the beginning segment completion in terms of providing the entity name suggestion in response to the provided entity name. Thus, in some embodiments, the agent 1710 and the search service 1780 interact with each other to provide the user 1705 with the '@gimbels' and '@bimbals'', Assuming that'@bimbals' is the entity name provisioned with the search service 1780. Various known techniques can be used to perform matching, such as limited editing distance sensing, for example.

In some embodiments, the agent 1710 may provide an indication of a keyword and / or offer associated with the entered or selected entity name or entity identification. This is to cause the agent 1712 to pass an input of the entity name contained in the entity indication 1720 to the user, such as when the user enters a command string. This embodiment is particularly suited for performing search data 1751 to a search service 1780 in a section or other portion, such as the agent 1710 provides entity identification at the same time as the input of the keyword meter. will be. Embodiments of the instructions may include changing the color of the input field of the agent 1710, such as changing the background color of the browser omni-bar from white to green. (E.g., a beep) or supply a list of keywords that are present in the entity indication 1720 associated with the entered entity name. As a variant of the supply of listings, a format for presenting a preview page to the user may be employed, where the preview page presents the entity name along with the associated provisioned keyword. Upon receiving the search data 1751, the search service 1780 processes the data by separating the data into classification data, split data, search data, or search data 1751 into the ID data 1752 and the supplemental data 1753. In some embodiments, supplemental data 1753 may be, for example, one or more keywords that are associated with a keyword dreamer character or are, for example, symbols such as '!'. In some embodiments, all or some of suggestions 1724-1728 may be keywords. In some embodiments, the search data 1751 may be separated by the agent 1710 before being received by the search service 1780. In various embodiments, the entity ID data 1752 is sufficient data to allow the search service 1780 and the 'entity n' 1723 is associated with at least one corresponding entity indication (as indicated by arrow 1783 in FIG. 17) (1782), or otherwise authorize the entity of the &lt; / RTI &gt;

The search service 1780 may provide the entity ID data 1752 'gimbels.' To the marker .gimbels' in the first column of the entity representation 1720, (1782). In this embodiment, the markers '.gimbels' in the entity representation 1720 are the highest level domain managed by the seller Gimbels, which is the registrant, and the search service 1720 maps 'gimbels.' To this. This means that when the exact character string match matches 'gimbels', the starting character '.' . As another example, if the entity name '@gimbels' of the search service 1780 for the command string '@gimbels! Shoes' is included in the first column of the entity display 1720 from the search data 1751 to the marker @gimbels Which can be attributed to the name space identifier '@'. Various known techniques or algorithms can be used to map the entity ID data 1752 to the entity identifier 1723 through various performance methods, thereby enabling one or more entity identifiers 1723 to be precisely matched or In correspondence with the entity ID data 1752 in the entity indication 1720 in a corresponding manner. In addition, various performing techniques can be used to limit mapping according to the identification of the user 1705, for example, when the user 1705 using the mobile device passes through the agent 1710, And / or mapping to a namespace such as, for example, an entity identifier 1723, and / or to a suggestion 1724, such as a keyword. For example, a network locator 1725 corresponding to a mobile device version of a Gimbels sales web page for shoe purchasing. Accurate performance of the mapping disclosed herein is not essential.

The search service 1780 may provide the supplementary data 1753 with one or more suggestions associated with the entity identifier 'entity n' 1723 in order to map the entity ID data 1752 to the entity identifier ' You can then perform the mapping. In various embodiments, supplemental data 1753 may be data sufficient to allow search service 1780 to attempt verification or mapping to 1784 or may be an entity n 1723 corresponding to supplemental data 1753 (e.g., keyword) Is sufficient data to determine at least one proposal related to &lt; / RTI &gt; In the illustrated embodiment, search service 1780 maps supplemental data 1753 to suggestions 1724 and 1728 (e.g., keywords), as indicated by arrows 1785 and 1786. As another example, the search service may use the keyword 'shoes' as supplemental data 1753 for the input command string '@ gimbels! Shoes' and in this embodiment the keyword 'shoes' is stored in the entity representation 1720 (1784) to the proposal (1724 or 1728) 'shoes'. This is because the keyword string 'shoes' and the alternative string 'shoes' exactly match each other.

If we describe the functionality of the present invention in succession to the previously described example case, the search service 1780 may provide the supplementary data 1753 'shoes' to the proposal 1724 'gimbels.shoes' associated with the entity identifier 'gimbels' And may also map the supplemental data 1753 'shoes' to the proposal 1728 'gimbels.shoes-on-sale' associated with the entity identifier 'gimbels' in the entity representation 1720 . In one embodiment, the search service 1780 maps the supplemental data 1753 of one or more keyword types to a suggestion of one or more keyword formats associated with an entity name 1723 already entered in the entity representation 1720 (1784). Various implementations are possible using various techniques and algorithms known in the art for mapping 1784, particularly partial character matching, etc., and such implementation may be limited as per user's 1705 acknowledgment. Implementation of exactly the same mappings herein is not necessarily required.

As shown in the embodiment of FIG. 17, the search service 1780 sends a proposal 1728 mapped to agent 1710 as proposal data 1762. In various embodiments, the proposed data 1762 is data indicative of a mapped suggestion, such as, for example, proposal 1724 and proposal 1728 within the entity representation 172, which allows the user 1705 to digitize, visualize, It can be presented in other ways. As previously described, proposed data 1762 in certain embodiments may include executable code that can be processed by agent 1710, or the like. In some embodiments, the proposed data 1762 may be customized to be presented by a device capable of hosting the user agent 1710. Continuing with the previous embodiment, the search service 1780 may send suggestion data 1762 including a string 'gimbels.shoes' and a string 'gimbels.shoes-on-sale'. Keep in mind that the completion of strict segments is the only way to complete a proposal for a keyword. Other ways of determining a partial match are also available. For example, if a user provides '@gimbels! Skoes' to the agent 1710, the embodiment matches the '! Skoes' partial string with '! Shoes' using a known match technique, for example, .

 Upon receiving the proposal data 1762, the agent 1710 may present the proposal data to the user 1705 and the user 1705 may select at least one of the proposals 1714. Continuing with the use embodiment, the browser performed by the agent 1710 may use the proposed data 1762 'gimbels.shoes' and 'gimbels.shoes-on-sale' as a selectable list or drop-down menu, May display a selection of one suggestion using the touch screen or mouse as indicated by data entry 1726. [ Further, the processing method of the present invention is repeatedly performed until a completed proposal is provided for the partial entity name. Examples of methods that a user may use to select or select items from a selectable list or drop-down menu, such as those known as user interface techniques, include placing a mouse pointer on a desired menu item and selecting the left mouse button Click on the mouse button. A variety of other computer science known techniques for allowing one or more selections or permutations that may be used by the user to represent various data selections or to be performed 1714 may be used, The implementation is not necessarily required for the present invention.

Upon entry of the recognized entity name, entity identification, or other namespace identification in any of the embodiments, the agent 1710 may be associated with the entered entity name to provide the user with a keyword suggestion within a menu, such as, for example, a drop- May provide some or all of the keyword suggestions list present in the entity display 1720. [ The user 1705 may select a keyword presented to the menu within the traditional method, for example, by clicking on it. Selection of a presented keyword in an embodiment is performed automatically by inputting a field related to the keyword as well as associated with the driving character, which may also be performed by the search service 1780 in the form of a request, for example search data 1751, The selected entity name and the selected keyword can be transferred. In a particular embodiment, the user may enter '@gimbels' in the field of agent 1710 and agent 1710 may forward this information to search service 1780. The search service 1780 may respond to a list of related proposals (keywords), which may be used by the agent 1710 to select, for example, 'shoes', 'men`s clothes', 'woman`s clothes' You can display it to users within a drop-down menu that includes the same. Accordingly, the user can be presented with a plurality of proposed keywords corresponding to the inputted entity name. Upon receipt of the list from the search service 1780, the presence of an entry for the entity name is confirmed and the agent 1710 provides an instruction to recognize the entity name, for example, the color of the input field changes from gray to blue can do.

The agent 1710 sends the offer selection data 1771 to the search service 1780 based on the user's input 1726 indicating the selection of the proposed offer. In various embodiments, the proposed selection data 1771 corresponds to one of the suggestions already sent to the agent 1710 within the proposed data 1762. In the embodiment shown in FIG. 17, the search service 1780 may lookup the offer selection data 1771 or look for a corresponding offer in the entity display 1720 indicated by arrow 1788. The search service 1780 can identify the network locator corresponding to the lookup proposal as shown in the embodiment of Figure 17 and the 'network locator m' 1729 corresponds to the proposal 1728, Or a network locator for the agent 1710 in the same column.

In some embodiments, the search service 1780 may provide a network locator to the agent 1710 at the same time that the network locator provides a suggestion, for example, as part of the offer data 1762. In certain embodiments, the agent 1710 may be configured to send, for example, the offer selection data 1771 with the search client 1780 to obtain a network locator corresponding to the offer selected by the user, and network location data 1772 It does not require additional communication such as receiving. However, in some embodiments the agent 1710 may send data to a search service 1780 that indicates what network locator the user has selected.

As described above, in some embodiments, limited mappings may be used depending on the identity of the user 1705. [ Thus, the agent 1710 may use (1727) context data such as network location data 1716 and provide 1772 to the search service 1781. This is done automatically and does not require user input. The search service 1780 may look up network location data 1716 either in a lookup 1787 or in association with an offer 1728 matched within the entity representation 1720 as well as geometrically close to the agent 1710 based on the context data Lt; RTI ID = 0.0 &gt; 1737 &lt; / RTI &gt; Some embodiments may accomplish this by storing a plurality of rows containing a proposal 1728 consisting of a different pair of network locators corresponding to different regions or network regions. In an alternative embodiment, the search service 1780 may provide the agent 1770 with a plurality of network locators with information reflecting geographical or network regions. In this embodiment, the agent 1710 may use the aggregated information to select the closest network locator geometrically or locally.

In some embodiments, the context data may be supplied by the agent 1710 along with the initial search data. For example, the search service 1780 may receive a string of generic entity names such as '@ zoo' along with geopolitical information as part of the search data 1751. The search service 1780 matches this entity ID with the multiple entities 1723 to select the one closest to the provided geopolitical data. In an alternative embodiment, the search service 1780 provides multiple network locators of the agent 1710 and the agent 1710 selects the closest network locator based on the context data.

Note that the network location data 1716 is a form of context data with available embodiments. Other types of context data include language format, authentication information, IP address, reputation data, username / password, encryption scheme, hardware key, geopolitical information, fingerprint verification, password package using a private / public key authentication scheme, , A product or assigned ID, a security information certificate, or a user identification or machine identification information. These and more detailed embodiments are described in detail in U.S. Patent Application No. 13 / 828,070, filed March 14, 2013, entitled &quot; Appropriate Names Resolution &quot;, the contents of which are incorporated herein by reference in their entirety have.

 If the user 1705 selects 'gimbels.shoes' from the drop-down menu and the search service 1780 searches the proposal of 'gimbels.shoes' in the entity indicator 1720 for lookup 1787) and searches for 'http://www1.gimbels.com/shop/clothing/shoes' as the corresponding network locator. Search service 1780 sends a string of 'http://www1.gimbels.com/shop/clothing/shoes' in network location data 1772.

As shown in FIG. 17, the agent 1710 uses the network location data 1772 for various purposes. In various embodiments, the agent 1710 can use the network location data 1772 to retrieve, directly connect, interact, or otherwise connect to network resources indicated or identified by the network location data 1772. In one embodiment, where the network locator 1725-1729 is transmitted along with the proposals 1724-1728 within the proposal data 1762, the agent 1710 may select a corresponding proposal, such as a keyword, The agent 1710 can automatically discover, directly connect, interact, or connect to network resources indicated or identified by the network locator.

Gimbels The agent 1710 can extract the string 'http://www1.gimbels.com/shop/clothing/shoes' from the network location data 1772 and enter it via the browser . The browser can resolve the string like any other URL and can provide a corresponding Gimbels web page for the user 1705 to purchase shoes. For example, the browser may contact the domain name server and retrieve such Internet Protocol address to obtain an Internet Protocol address corresponding to the network location data.

Gimbels Example The conclusion of the case is that an agent 1710, such as a browser, can selectively display a combination of an entity name and a proposal (e.g., a keyword). Such a display can be done through a search bar or an omniva. In some embodiments, the agent may display a network locator 1725-1729 or network location data 1772, such as, for example, a URL within a search bar or an omnibo of a browser. In some embodiments, the agent 1710 may toggle between displays or between an entity name and a suggestion (e.g., keyword) combination, or between a network locator or network location data, such as a URL. This toggling may be initiated by user input, such as, for example, the user 1705 activates a softkey that has been depressed. An embodiment may display both an entity name and a proposal (e.g., a keyword) combination and network locator or network location data.

In general, any embodiment may employ redirection. In this embodiment, if the user 1705 selects or inputs a command string containing the entity ID data 1752 (e.g., the entity name including the namespace identifier) to the agent 1710, (1780) and the search service (1780) performs the redirection using the same specific format. Redirection is performed under the provisioning preference of the entity name owner (eg namespace owner). The preferences may reflect time-sensitivity or other specific relevance. For example, the user may enter '@gimbels! Shoes' towards the search bar of the browser provided by the agent 1710. Agent 1710 sends a request corresponding to search service 1780 (e.g., by search data 1750). The search service 1780 may match or map the requested data to different data corresponding to different command strings, such as, for example, '@ gimbels! Shoes_on_sale_January_2014'. This mapping can be refined by the name owner himself and can be made invisible to the user. Search service 1780 may provide agent 1710 with appropriate matching data (e.g., network locator 1725-1729). This data can be supplied with data that reflects the original command string ('' @ gimbels! Shoes '' in this case, which means that the redirection is invisible to the user, or data that reflects a new command string (here '@ gimbels! Shoes_on_sale_January_2014' To provide it together.

Some embodiments perform error handling in a variety of ways. This means that the search service may request in a variety of ways including entity names (e.g., entity ID data 1752) and / or keywords (e.g., supplemental data 1753) that do not exist within the entity representation 1720 For example search data 1751). If the search service 1780 has received a request that includes an entity name present in the name display 1720 of the search service 1780 but the name and keyword combination do not exist, the search service 1780 may perform the following actions Can be performed. The return of the network locator for the error page, the return of the network locator for the associated name and keyword combination, the automatic correction to the associated name and combination of keywords, the redirection of the associated name and keyword combination, or the corresponding And attempts to search for keyword content. Each of these methods involves determination through preference of the name owner (or user) using known techniques. Error handling can provide editing of various keyword sets for the name owner. The name owner may map according to the rules detailed by the name owner if the search service 1780 receives a request that includes a keyword associated with a certain characteristic (e.g., a synonym that characterizes a particular keyword or keyword equivalent to SOUNDEX) have.

When the search service 1780 receives a request that does not exist in the entity display 1720 but contains a name (e.g., entity ID data 1752) that is in a namespace, the search service 1780, in addition to the options described above, RTI ID = 0.0 &gt; 1780 &lt; / RTI &gt; can return search results to the network locator from the namespace. For example, if a user enters '@gimbels! Shoes' and '@gimbels' that are present in the Twitter namespace but not in the search service entity display 1720, then the search service may include a Twitter page (e.g., Blog entries, etc.) as '@ gimbels' or 'shoes'. The page may include an informational message that provides the name owner with an opportunity to register the keyword with the search service 1780. [ Similar result pages may be constructed together in different namespaces.

If the search service 1780 receives a request that includes a name (e.g., entity ID data 1752) that does not exist within the entity representation 1720 or within another namespace, the search service 1780 may either The network locator for the proposal can be returned.

One of ordinary skill in the art will recognize that the components and detailed methods of performing the system 1700 are simplified embodiments presented for brevity and accuracy in the description herein. Other components, performance details, and variations may be used. For example, proposal data 1762 or location data 1772 may include an error code or other indication in a suitable location if the mapping or lookup fails or direct search service 1780 can not return the expected response. Many other variations are possible.

18 is a flow diagram illustrating a method from a search service perspective in accordance with various embodiments. The method of FIG. 18 may be performed by the search service disclosed herein. More specifically, the method of FIG. 18 may be performed by the search service 1780 of FIG. 17 or by the URL keyword resolution server described in Section 1 above.

At block 1802, the search service receives a request from a network resource. In some embodiments, the request includes an entity name and a keyword. The request may include indicating a namespace identifier or a namespace associated with the entity name. The request may be received, for example, from an agent, such as agent 1710 of FIG. It can also be received from a client computer or a web browser as described in Section 1. The agent may entice the request from the command string entered by the user as described herein. A search service may obtain a request from an agent over a network such as the Internet. The search service may receive all or a portion of the request at once, as described in Section 2 above.

At block 1804, the search service may obtain a constant resource locator or other network locator (e.g., one or more network locators 1725-1729) corresponding to the request received at block 1802. In some embodiments, the search service may obtain a certain resource locator from one or more databases or directories, such as, for example, a database containing one or more entity representations, or may be stored in a data store 130, Can be obtained from one or more databases. The search service may perform a match between the entity name received in block 1802 and the entity name stored in the database and may also perform matching between the stored keywords in association with the entity name matched with the received keyword in block 1802 have. The matching of entity names and / or keywords may be an exact match or may use empirical or other outline matching techniques. Once matched, the search service can retrieve a corresponding constant resource locator (or other network locator) from the database, such as from the same column of matched entity names and keywords.

At block 1806, the search service provides a constant resource locator (or other network locator) to the requestor, e.g., an agent. This can be caused by a search service that sends certain network locators to the requestor over a network such as the Internet. In some embodiments, the search service may also provide one or both of the suggested entity names and suggestions for supplemental data, e.g., keywords.

19 is a flow chart illustrating a method from an agent's point of view according to various embodiments. The method of FIG. 19 may be performed by an agent disclosed herein. More specifically, the method of FIG. 19 may be performed by a client computer or a web browser as described in Section 1 above or performed by the agent 1710 of FIG.

At block 1902, the agent may receive the command string, for example, by a user clicking on a link or by a user entering an area such as a search bar or an Omni bar. The command string may include an entity name and a keyword. The command string may further include an entity name and a namespace identifier and / or a keyword and a keyword drier.

At block 1904, the agent draws a request for network resources from the command string received at block 1902. [ Agents can extract entitlements and keywords using known techniques to attract requests to analyze the command string. The request may include an entity name, a keyword, and a namespace identifier corresponding to the entity name.

At block 1906, the agent may provide a request for network resources to the search service over a network such as the Internet. The search service may be, for example, the search service 1780 of FIG. 17 and may be the URL keyword resolution server disclosed in Section 1 above. To transfer the request, the agent can directly forward the request to a certain resource locator or other network locator encrypted with the agent software.

At block 1908, the agent obtains a certain resource locator or other network locator corresponding to the request provided at block 1906. [ The agent may obtain a constant resource locator from the search service, which may be obtained from one or more databases to find out whether the agent itself matches the entity name and keywords disclosed herein. When an agent obtains a certain resource locator, it can perform an action, such as searching for a resource identified by a certain resource locator.

The embodiments disclosed herein are capable of various modifications. For example, the search service is not limited to handling entity names and keyword combinations. On the other hand, a search service may be a combination of two or more entity names (e.g., forming a hierarchy) or two or more keywords (presumed to have proper ownership of at least one keyword) Can be handled. Considering a keyword as a namespace defined by a name owner, a search service may provide a way to provision or lookup information about a combination of one or more names that are refined by at least one name owner.

Another variation is how the search service 1780 can perform either physically or logically. In some embodiments, the search service 1780 may provide various cases of lookup operations (e.g., distributed servers) to enhance applicability while maintaining a balance for each case. An embodiment may use a front end service of a search service 1780 that interfaces with an agent 1710 and may use a back end service that holds an entity display entry similar to a DNS conceptual structure of an iterative and authoritative name server. The front-end service may cache the directory entry in order to respond quickly to the request. The agent 1710 itself may also store an entity display entry in its cache. The authenticity of the data and the authentication mechanism of the data origin can be applied in a manner similar to DNSSEC. Similar operation selections can be applied to the proposal and provisioning operations.

Another variation relates to how agent 1710 can operate. In addition to the search results display, the user can seek to see if the agent 1710 can present additional guidance (as directed by the name owner). The suggestion of the entered name and keyword is a form of feedback. The confirmation that the user has recognized or entered the registered name is a separate one. The user interface associated with browser-based agent 1710 is a key and iconic representation of the present invention as disclosed herein. Thus, the user interface may represent voice, introduction of applications and / or display of initial results in a browser window or other interface. In particular, the relationship with the user is not limited to an 'address bar' or the like. Intermediate feedback may be provided at different program locations, such as provided at the end of the interface, where the final web page or other content is where the user enters the search data directly.

 Another variation relates to the alphabet alternatives. The present specification describes the standard English alphabet, but the present invention is not limited thereto. Embodiments include, but are not limited to, Chinese Chinese characters (e.g., Chinese characters, simplified Chinese characters), Japanese alphabets (kanji, hiragana, katakana), Korean, Hindi, Cyrillic, Tagalog, Tamil, Hungarian, Portuguese, Spanish, French), Urdu, Greek, Hebrew, Armenian, and Arabic. Both the entity name and the keyword can be represented by one or a combination of various alphabets. For example, valid syntax is possible via the following command string: Decorator is the name of the entity in China and 'decoratif' is the keyword in French. Note that in this embodiment, the entity name and the keyword may be different alphabets.

In general, search engines crawl the web to view and store search results. The search engine may be augmented to search the search service space for identifying the edited network locator. This search engine can specifically identify the search results that occur corresponding to the edited network locator. For example, a search engine can receive queries that match various links. The search engine can provide these links to the user as a result of the web page. Some of the links may be edited links that are shaped by the entity. In such an embodiment, the search engine may provide differentiated entities from other links, for example by presenting different color fronts, sizes, locations, and so on. As a specific embodiment, the embodiments used herein will be described in succession, and the user can type 'gimbels shoes' into the search engine query field. The search engine can provide a results page that contains various links, such as new information on blogging on shoe-related blogs, such as the link 'http://www1.gimbels.com/shop/clothing/shoes' You can provide a Gimbels entity by shaping it as a network locator associated with a command string such as '@ gimbels! Shoes'. In this way, the search space can be expanded through an integrated database from the search service. The latter link in the result page is distinct from other links mentioned herein.

In some embodiments, the search service adds network locators or returns other content. In this embodiment, the entity indication 1720 may include a separate field (e.g., one or more columns) for storing content related to the entity name and keyword. The search service may obtain content (by the user selecting a corresponding proposal) from a direct lookup or appropriate entity representation within the existing content, and may query the content using an appropriate network locator stored within the entity representation. In another variation, the search service may return the content from the user himself or herself, and at this time, an agent searching for the network locator is not required and the content may be retrieved.

In some embodiments, the agent 1710 may use the image in all or part of the search data 1751. The image may be in any of a variety of formats such as, for example, bitmap, GIF, JPEG, MPEG, and the like. In certain embodiments, an image may be used to generate entity ID data 1752, supplemental data 1753, or both, using various mechanisms. For example, the agent 1710 itself, the search service 1780, or a separate system may obtain an image from the agent 1710 or the search service 1780, respectively, and may convert the image to a character string using a known technique The character string can be provided to a search service, and a processing method thereof is disclosed in this specification,

As a clear example, the user 1705 may obtain an image of a company logo, such as, for example, a Gimbels logo in the JPEG format. The user may directly forward the logo to the agent 1710 using, for example, a graphical user interface. The agent 1710 may provide an image to the search service 1780 and may use a known image recognition technique to match the image with the character string 'gimbels.' The search service may process the string gimbels' The search service may act as if it directly receives a string such as, for example, a match of this string with the edited namespace identifier, and may provide a list of matched keyword suggestions for the agent to display to the user.

Please note that the use of images is not limited to entity verification. For example, a user may type &quot; @gimbels &quot; in the field of agent 1710 and the user may directly send an image of the shoe to the agent when the agent displays a list of suggestions. The agent 1710 may recognize the image using its own known techniques and may provide the image to the search service 1780 for performing the recognition function. Either way, the search service can respond as if he had received the string '@ gimbels! Shoes' directly.

Some embodiments may use pairs of namespace identifier characters and / or pairs of keyword drinker characters, for example '[' paired with ']', '{' paired with '} or' (paired with ''. Examples of suitable command string syntaxes in some embodiments may include, for example, {gimbels} (shoes), @gimbels (shoes), (gimbels) shoes, and the like.

3. Computer system performance

20 is a block diagram of an exemplary computer system or data processing system 2000 that may be used to perform embodiments consistent with the present invention. Other components and / or arrangements are available. In some embodiments, computer system 2000 may be used to perform search services 1780 as shown in FIG. Also, for example, the search service may operate alone or as part of a larger search system. In various embodiments, the computer system 2000 may be used to perform the agent 1710 shown in FIG.

The computer system 2000 may include a number of components such as, for example, a central processing unit (CPU) 2005, a memory 2010, an input / output (I / O) device 2025, and a non-volatile storage device 2020 . &Lt; / RTI &gt; The system 2000 can be performed in various ways. For example, as an integrated platform such as a workstation, a server, a personal computer, a tablet computer, a laptop, a smartphone, and the like. As a variation thereof, components 2005, 2010, 2020 and 2025 may be connected and communicating via a local data bus and may be connected to a database, such as a separate database system, for example, via an external I / O connection. The I / O component 2025 may be coupled to an external device via a direct interconnect, such as, for example, a connection line or a local WiFi connection, and may be coupled to a local area network (LAN) or wide area network (WAN) And can be connected through the same network. The system 2000 may be used alone or may be a partial system in a larger system.

CPU 2005 may be one or more known processing devices, such as, for example, a microprocessor of the Xeon family type manufactured by Intel Corporation of Santa Clara, Calif. The memory 2010 may be one or more solid state storage devices and may be implemented by a CPU 2005 that performs certain functions, methods, operations, and processes in connection with the embodiments of the present invention, Lt; / RTI &gt; The storage device 2020 may be a volatile or non-volatile storage device, magnetic, semiconductor, tape, optical or other type of storage device or computer readable storage medium, and may include long term storage in the form of CD, DVD,

As shown in the illustrated embodiment, memory 2010 includes one or more programs or partial programs 2015 that are loaded into storage device 2020 or loaded into a remote system (not shown). Procedures, functions, processes, or methods corresponding to the present invention when performed by the CPU 2005. [ Optionally, the CPU 2005 may execute one or more programs remotely located from the system 2000. For example, the system 2000 can access one or more remote programs via the network 2035 and perform functions or methods related to performing the embodiments of the present invention when performing remote programs.

In one embodiment, the memory 2010 may include a program 2015 that performs intercommunication, mapping, or lookup functions as described for the search service 1780. In yet another embodiment, the memory 2010 is a communication service, such as the one described for the search service 1780, And a program 2015 for performing search and connection functions. In yet another embodiment, the memory 2010 may include a program 2015 for receiving, obtaining and providing functions as shown in Fig. In yet another embodiment, the memory 2010 may include a program 2015 for receiving, attracting, providing and obtaining functions as shown in Fig. In some embodiments, the memory 2010 may include other programs or applications for performing other methods or processes that provide the functionality of the present invention. For example, the memory 2010 may include a program that allows an owner to interface with an entity owner or namespace owner to modify the entity indication 1720 for its entity ID or namespace.

The memory 2010 may be modified for other programs (not shown) not related to the invention and / or for an operating system (not shown) for performing some functions of a field already known when performed by the CPU 2005 . Examples of such operating systems may be Microsoft Windows, Unix, Linux, Apple Computer Operating System, or other operating system. The selection of the operating system is not critical to the present invention as far as it relates to the use of the operating system.

The I / O device 2025 may include one or more input / output devices that allow data to be received and / or transmitted by the system 2000. For example, the I / O device 2025 may include a keyword, a touch screen, a mouse, or one or more input devices similar thereto, and may allow input of data from a user, such as the user 105. The I / O device 2025 may also include one or more output devices such as a display screen, a CRT monitor, an LCD monitor, a plasma display, a printer, a speaker device, and the like. Such an output device is presented to a user and enables data to be output. The I / O device 2025 includes one or more digital and / or analog communication input / output devices capable of digitally intercommunicating with other machines or devices operating as, for example, web servers within the computer system 2000 can do. Other variations and / or multiple input and / or output devices may be incorporated into the I / O device 2025 and used.

As shown in the embodiments, the system 2000 can access a network 2035, such as the Internet, a cellular network, a private network, a substantial private network, or other network, and includes an agent 1710 ) Or to a variety of systems and computer devices, including desktop computers, smart phones, tablet computers, or laptop computers for the user 1705 upon installation of the server computer. In general, the system 2000 can input data from external machines and devices via the network 2035 and output data from external machines and devices.

A database 2030 may be used in combination with the system 2000. As shown in the embodiment, a single database outside the system 2000 can be used. In another embodiment, the database may be hosted by system 2000. The database may be used to manage or store data to perform systems and methods corresponding to the present invention. For example, the database 2030 may include an entity indication 1720 of the system 1700. In general, the database 2030 may store information that is accessed and / or managed through the system 2000. As an example of such an embodiment, these databases are Oracle databases. It can be a Sybase database or other related database. However, the method of the system according to the present invention is not limited to a separate data structure or database, and any database or data structure can be used.

It is to be understood that the above description is intended to be illustrative and not in a limiting sense. In general, systems capable of performing the proposed techniques can be in a wide variety of forms. Variations in various settings and performances are also possible. For example, the resources described in singular may be plural, and the resources described as being aggregated may be distributed. Also, resources described as being multiple or distributed may be combined with each other. It should be understood that the scope of this technique is thus limited only by the following claims.

Claims (30)

I) receiving a request for a network resource including search services and command data including an entity name and a keyword provided by a search client over the Internet;
Ii) obtaining a network locator corresponding to an entity name and a keyword from at least one database of the search service; And
Iii) providing a network locator in response to receipt via the Internet;
The method comprising the steps &lt; RTI ID = 0.0 &gt; of: &lt; / RTI &gt;
The method of claim 1, wherein the search service is not a domain name system search service.
2. The method of claim 1, wherein the command data is derived from a command string comprising a namespace identifier adjacent to an entity name.
4. The method of claim 3, wherein the name space identifier is selected from the group consisting of @, fb, in and ". &Quot;.
2. The method of claim 1, wherein the search client selects a search service based on a namespace identifier.
3. The method of claim 1, wherein the command data is derived from a command string comprising a keyword dreamer adjacent to the keyword.
7. The method according to claim 6, wherein the keyword drier is selected from the group consisting of #,!, ". &Quot;, $ and |.
2. The method of claim 1, further comprising: obtaining an internet protocol address corresponding to a network locator from a database of a domain name system service provider; And providing an internet protocol address.
I) one or more server computers configured to receive requests over the Internet for network resources including command data including entity names and keywords provided by the search client and operably connected to the Internet;
Ii) at least one database operatively connected to one or more servers storing network locators associated with the entity names and keywords; And
Iii) at least one electronic processor configured to provide a network locator to a search client over the Internet;
/ RTI &gt;
10. The system of claim 9, wherein the search service is not a domain name system search service.
10. The system of claim 9, wherein the command data is derived from a command string comprising a namespace identifier adjacent to an entity name.
12. The system of claim 11, wherein the name space identifier is selected from the group consisting of @, fb, in and ". &Quot;.
10. The system of claim 9, wherein the command data is derived from a command string comprising a keyword dreamer adjacent to the keyword.
14. The system of claim 13, wherein the keyword meter is selected from the group consisting of #,!, ". &Quot;, $ and |.
10. The system of claim 9, wherein the system comprises: a function of obtaining an internet protocol address corresponding to a network locator from a database of a domain name system service provider; And a function of providing an internet protocol address. &Lt; Desc / Clms Page number 19 &gt;
I) receiving a command string including an entity name and a keyword by a search client;
Ii) deriving a request including an entity name and a keyword for the resource from the command string;
Iii) providing a request for resources to a search service over the Internet; And
Iv) obtaining a network locator corresponding to the entity name and the keyword from the search service;
&Lt; / RTI &gt;
17. The method of claim 16, wherein the search service is not a domain name system search service.
17. The method of claim 16, wherein the command string comprises a namespace identifier adjacent to an entity name.
19. The method of claim 18, wherein the namespace identifier comprises a symbol selected from the group consisting of @, fb, in and ". &Quot;.
17. The method of claim 16, wherein the method further comprises selecting a search service based on a namespace identifier.
17. The method of claim 16, wherein the command string comprises a keyword dreamer adjacent to the keyword.
22. The method of claim 21, wherein the keyword modifier comprises a symbol selected from the group consisting of #,!, ". &Quot;, $ and |.
17. The method of claim 16, further comprising: requesting an internet protocol address associated with a network locator;
Receiving an internet protocol address associated with the network; And
Retrieving an internet protocol address;
&Lt; / RTI &gt;
I) means for receiving, by a search client, a command string including an entity name and a keyword;
Ii) means for deriving a request including an entity name and a keyword for the resource from the command string;
Iii) means for providing a request for resources to a search service over the Internet; And
Iv) means for obtaining a network locator corresponding to an entity name and a keyword from the search service;
Wherein the at least one processor is configured to perform at least one of:
25. The system of claim 24, wherein the search service is not a domain name system search service.
25. The system of claim 24, wherein the command string comprises a namespace identifier adjacent to an entity name.
27. The system of claim 26, wherein the namespace identifier comprises a symbol selected from the group consisting of @, fb, in and ". &Quot;.
25. The system of claim 24, wherein the at least one processor is further configured to perform a search service selection based on a namespace identifier.
25. The system of claim 24, wherein the command string comprises a keyword dreamer adjacent to the keyword.
30. The method of claim 29, wherein the keyword modifier comprises a symbol selected from the group consisting of #,!, ". &Quot;, $ and |.

Images