Web site, information communication terminal, robot search engine response system, robot search engine registration method, and storage medium and program transmission apparatus therefor

[0001] 1. Field of the Invention

[0002] The present invention relates to a system according to which an information site, provided on a communication network, issues different responses in accordance with the types of the sources of access request transmissions.

[0003] 2. Discussion of Related Art

[0004] Presently, there are many sites on the Internet whereat information on a variety of subjects is available; but not all these sites can be freely accessed, some of them have established membership requirements and limit access to members only, while others grant access only to those users who are willing to pay a browsing fee.

[0005] On the Internet to search sites and to efficiently locate and assemble desired information, most users rely on the use of search engines.

[0006] FIG. 17 is a diagram of an information search for which a search engine is being employed.

[0007] As is shown in FIG. 17, a search engine 210 collects information scattered across the Internet and assembles it to form a URL list, or it initiates a search upon the receipt of a search request from a user terminal 220, to which it transmits the results of the search. For a search, various search methods are used, such as one where a keyword is used or one that is based on parsing performed in accordance with categories.

[0008] Further, methods for obtaining information using search engines include one whereby information is registered on a list in accordance with a request from a site, and one that uses a robot search engine to mechanically visit sites and obtain information.

[0009] A robot search engine will now be described.

[0010] In a robot search engine, software called a robot, a crawler or a spider (hereinafter referred to simply as a robot) uses HTTP to collect search targets, HTML documents, from web servers, and provides a full document, keyword based search service for the collected results. The activities of a typical robot will now be specifically described.

[0011] 1. Selects one uncollected URL from a URL listing of HTML documents.

[0012] 2. Transmits an HTTP request to a WWW server in order to obtain an HTML document from the selected URL.

[0013] 3. Generates for the HTML document, once it has been obtained, an index and an abstract, and either stores them in a storage device, or abandons them.

[0014] 4. Detects the URL of the HTML document, once it has been obtained, using a hyperlink in the HTML document.

[0015] 5. Adds the detected URL to the URL list in 1.

[0016] 6. Returns to 1 if an URL in the URL list has not yet been collected.

[0017] This processing is used to control the robot and move it from URL to URL.

[0018] Since robot search engines usually do not have the right of access for the sites at which only limited access is permitted, the engines can not enter such sites to retrieve information. Therefore, even when the information required by a user is available at a specific site, so long as only limited access to the site is permitted, attempts by the robot search engine to retrieve information from the site will be rebuffed, and the user in question will not be able to find the site using the robot search engine. This state is shown in FIG. 18.

[0019] From the viewpoint of the site, since its URL is not acquired and added to a list of available sites by the robot search engine, the information it can provide will not be fully advertised.

[0020] As one method for advertising a site to an audience of unspecified users, the site may be registered on a URL list by a robot search engine and may then be registered with a search engine for the creation, using manpower, of a category list and a home page to be employed as an advertisement, or a banner advertisement may be prepared.

[0021] As is described above, when a site on the Internet permits only limited access, a robot search engine that does not have the right of access can not retrieve any information from the site. Thus, the information can not be added to a URL list maintained by the robot search engine, and a user who requires that information will not be able to depend on the robot search engine to search for and acquire the information he or she requires. Therefore, since a site for which only limited access is permitted will not be registered in the URL list of the robot search engine, the existence of the information at the site will not be advertised.

[0022] Further, as is described above, in addition to the registration of a site in the URL list of a robot search engine, a method is available whereby human labor is utilized to prepare a URL list and to register a site with a search engine, and another method is available for the setting up of an advertisement home page or the creation of a banner advertisement.

[0023] However, robot search engines are widely employed for searching for desired information on the Internet, and using them to register information on URL lists is a very effective advertising means.

[0024] Furthermore, for the two advertising methods described above, labor is required to register sites on search engines and to set up homepages and create banner advertisements. And in addition, each time the information available at a site is to be updated, the site issues a notification to that effect and manual labor must be is employed for the updating. But since a robot search engine can automatically access a site and obtain information, the requirement for labor to perform these activities can be eliminated.

[0025] Therefore, even though a robot search engine can not acquire information at a site whereat access is limited, metadata (a keyword concerning information) can be provided for the information the robot search engine seeks, and the advertising effects available with the robot search engine can be provided.

[0026] Further, if a user, who like a robot search engine does not possess the right of access for a site whereat only limited access is permitted, transmits via a browser an access request to the site, and metadata, such as a message used to describe the information, is provided, even though actual access was not permitted, a beneficial advertisement effect can be expected.

[0027] It is, therefore, one object of the present invention to provide metadata, for information that is available at a site whereat only limited access is permitted, upon the receipt by the site of an access request from a robot search engine.

[0028] It is another object of the present invention to enable the selective provision of appropriate information, by a site whereat only limited access is permitted, consonant with the access rights of the source of a request for information.

[0029] To achieve the above objects, according to the present invention, a web site provided in a communication network comprises: a data manager, for storing information to be provided across the communication network; a transmission source determiner, for ascertaining the type of a transmission source from which an access request is received; and a response unit, for acquiring, from the data manager, information that is correlated with the type of the transmission source obtained in accordance with the determination made by the transmission source determiner, and for generating and returning a response that is consonant with the type of the transmission source of the access request, wherein the data manager stores main information, for which access is limited, and metadata, which is information describing the main information, and wherein, as the result of the determination by the transmission source determiner, when the transmission source of the access request has no right of access for the main information, the response unit obtains metadata that is then used to generate a response.

[0030] With this configuration, the metadata concerning the main information can be provided the robot in a robot search engine or a user who possesses no access rights.

[0031] When the transmission source of the access request identified by the transmission source determiner is a robot in a robot search engine that is launched across the communication network, the response unit generates a response, as metadata, that includes a keyword concerning the main information.

[0032] This configuration is preferable because the keyword necessary to prepare a keyword index in the search engine can also be obtained for main information for which access is limited.

[0033] The transmission source determiner includes a user agent register in which the robot, of the robot search engine, which is launched across the communication network, and a user agent header that the robot adds to the access request are registered as correlating with each other. When the contents of the user agent header added to the access request that is received are registered in the user agent register, the transmission source determiner determines the transmission source of the access request to be the robot of the robot search engine.

[0034] This configuration is preferable because metadata consisting of a keyword can be provided for the robot of a famous search engine.

[0035] The transmission source determiner includes a user register in which each access right of a user for the main information is registered. When a user ID, provided as cookie information, together with the access request that is received, is registered in the user register, the transmission source determiner notifies the response unit of the range of the access rights of the user that is indicated in the user register. In accordance with the range of the access rights of the user, which is received from the transmission source determiner, the response unit generates a response, as metadata, that includes text data for describing the contents of the main information that is requested by the access request.

[0036] This configuration is preferable because a description of the contents of the main information can be provided a user who does not have access rights.

[0037] According to the present invention, a web site established in a communication network comprises: a data manager, for storing subscription information to be provided across the communication network; a transmission source determiner, for determining whether a user who is the transmission source of an access request has paid a fee for the subscription information; and a response unit, for transmitting, in accordance with the determination made by the transmission source determiner, the subscription information to a user who has paid the fee for the subscription information, and instead of the subscription information, transmitting at no cost a description of the subscription information to a user who has not paid the fee.

[0038] This configuration is preferable because a description of the contents of the subscription information can be provided at no cost to the user who has not paid the fee for the subscription information.

[0039] According to the present invention, an information communication terminal is provided for accessing an information site on a communication network, and for obtaining information available at the information site, whereto a request, together with identification information for the information communication terminal, is transmitted to acquire the information; and whereat, when the information that is requested falls in an access right range that, for the information communication terminal, is set in accordance with the identification information, the information is provided by the information site, and when the information that is requested does not fall in the access right range, metadata, which is information describing the information available at the information site, is provided.

[0040] According to the present invention, the following robot search engine response system can be provided. Specifically, the robot search engine response system comprises: a transmission source determiner, for analyzing an access request received by a web server provided on a communication network, and for identifying the transmission source of the access request; and a response unit, for transmitting, when the transmission source of the access request identified by the transmission source determiner is a robot of a robot search engine, a keyword concerning the web page source to the robot instead of a web page source requested by the access request.

[0041] According to the present invention, the following robot search engine registration method can be provided for a web site provided along a communication network. Specifically, a robot search engine registration method comprises the steps of: mechanically accessing a web site via a communication network and obtaining a web page source stored at the web site; accepting an access request from a robot of a robot search engine that prepares a web page search list; and transmitting to the robot, instead of a web page source requested by the access request, a keyword concerning the web page source.

[0042] According to the present invention, a storage medium is provided on which input means of a computer stores a computer-readable program that permits the computer to perform: a process for analyzing an access request received by a web server that is provided on a communication network and for determining a transmission source of the access request; and a process for, when the transmission source of the access request is a robot of a robot search engine, transmitting a keyword concerning a web page source to the robot instead of the web page source contained in the access request.

[0043] With this configuration, the computer that installs the program can transmit a keyword string, instead of the web page source, in accordance with the access request issued by the robot of the robot search engine.

[0044] According to the present invention, a program transmission apparatus comprises: storage means for storing a program; and transmission means for reading the program from the storage means and transmitting it.

[0063] The preferred embodiment of the present invention will now be described in detail while referring to the accompanying drawings.

[0064] FIG. 1 is a diagram showing the configuration of a network environment wherein a web site is connected in accordance with the embodiment.

[0065] In FIG. 1, a web site 10 provides an information provision service in accordance with the embodiment. An ordinary robot search engine 20 mechanically accesses the web site 10, obtains information such as a keyword and registers it in a URL list. A user terminal 30 employs an incorporated web browser 31 to access the web site 10 via a communication network 100, or to access the search engine 20 and search for a web page that includes desired information. The communication network 100 is a network system based on the Internet, such as the WWW (World Wide Web) or an intranet, across which information is exchanged.

[0066] In FIG. 1, only the web site 10 and the robot search engine 20 that implement the embodiment are shown.

[0067] Actually, other general web sites and search engines, which register the URLs of web sites on URL lists, using manpower, in accordance with requests from the sites, are connected to the communication network 100. For the user terminals 30, access right relative to the web site 10 differ depending on the user. As will be described later, the web site 10 copes with the each user terminal 30 in accordance with its access rights. The functions of the user terminal 30 are carried out by various types of information communication terminals, including workstations, personal computers, other computer systems and PDAs (Personal Digital Assistants). The access rights for the web site 10 depend not on the apparatus constituting the user terminal 30 and the type of the web browser 31, but on the user of the user terminal 30.

[0068] FIG. 2 is a diagram for explaining the configuration for this embodiment of the web site 10.

[0069] In FIG. 2, the web site 10 comprises: a web server 11, for providing a service via the communication network 100; a user agent determination module 12, for determining the sender of an access request received by the web server 11; a user agent register 13; a user register 14; an official response generation module 15, for generating a response in accordance with the type of the sender of the access request; a preview response generation module for a guest user 16; a preview response generation module for a non-registered user 17; a response generation module for a search engine 18; and a data management system 19, for storing information provided by the web site 10.

[0070] With this arrangement, the web server 11 provides a file or data upon receipt of an HTTP request (access request) from the user terminal 30 or the search engine 20. The web server 11 can be constructed using ordinary server hardware.

[0071] The user agent determination module 12 is mounted on the web server 11 using a CGI (Common Gateway Interface) or a Java servlet, and determines the transmission source of the HTTP request that is received by the web server 11. For this determination, a method for referring to the User-Agent header of the HTTP request is employed.

[0072] Generally, the header information called the User-Agent header is added to the HTTP request, and in the header information a character string is set as a self-statement employed by a user agent to identify himself or herself. For example, in the case of the Netscape Navigator of Netscape Communications, the User-Agent header shown in FIG. 3 is added. In this header, a value “Mozilla/4.7[ja] (Win98, I)” is placed on the third row, and indicates that “Netscape browser version 4.7, Japanese edition, was operated on the Microsoft OS, Windows 98”.

[0073] Similarly, for the HTTP request issued by the robot in the robot search engine 20, so long as the web site 10 knows the contents of the User-Agent header added by the robot, all the web site 10 must do to determine the identity of the transmission source of the HTTP request is examine the User-Agent header of the HTTP request. Generally, since the contents of the User-Agent headers of the robots of popular, frequently used search engines are known, it is possible, by referring to the User-Agent header, for the transmission source of an HTTP request to be identified as the robot of a predetermined search engine. Further, when the contents of a User-Agent header are not known to the web site 10 or when the HTTP request does not include a User-Agent header, the user agent may be a “malicious” user agent that issues many requests in a short period of time, and imposes an excessive load on the web server 11, and the request may be simply rejected.

[0074] Further, when the HTTP request is issued by the web browser 31 of the user terminal 30, the user agent determination module 12 can employ the user ID that is received with the HTTP request as cookie information for a more accurate parsing of the transmission source of the HTTP request. When the parsing of the transmission source of the HTTP request is performed in detail, it is possible to return different information, depending on the source, and to deal with the HTTP request closely. To what degree the transmission source of the HTTP request is to be parsed can be arbitrarily determined, and depends on the management policy of the web site 10 and the type and the contents of the information to be provided. For example, the user ID may not be employed for determination, and only the robot of the search engine 20 may be identified and dealt with differently. It should be noted that the method whereby the user ID for the cookie information is employed to identify the access rights of the user is merely an example, and the access rights may be examined after the user enters the registration number or completes the registration, or pays the fee.

[0075] In the following explanation, which will now be given for this embodiment, it is assumed that an official user who possesses full access rights for the information stored in the data management system 19 of the web site 10, a guest user who possesses partial access rights, a non-registered user who has no access rights, and the robot of the search engine 20 are distinguished from each other.

[0076] The User-Agent header is registered and held in the user agent register 13. Then, when the web server 11 receives an HTTP request, the user agent determination module 12 examines the user agent register 13 to find the User-Agent header to be added to the HTTP request. If the User-Agent header has been registered in the user agent register 13, the transmission source of the HTTP request is determined to be the robot of the search engine 20.

[0077] The search engines 20 can be differentiated by ranking User-Agent headers and registering them in the user agent register 13 in accordance with the ranks to which they are assigned. Thus, for example, for the robot (A) of a search engine 20 having a high rank, information may be returned for each access, while for the robot (B) of a search engine 20 having a low rank, access requests may be rejected, information may be returned only once every several accesses, or only a small amount of information may be returned. For ranking, an arbitrary ranking reference may be employed, such as the number of users of a search engine 20 or whether a search engine 20 is an integral part of a web site 10.

[0078] A user ID transmitted as cookie information is registered and held in the user register 14 in accordance with the access rights that are possessed by each user. Then, when the web server 11 receives an HTTP request, the user agent determination module 12 examines the user register 14 to find the user ID that as cookie information was received with the HTTP request. Whether or not the user ID has been registered in the user register 14 is determined, and when it has been registered, the contents of the access rights possessed by the user are examined. It should be noted that the user register 14 is not a requisite component. When all that is required is a determination as to whether the transmission source of the HTTP request is a robot of the search engine 20, only the user agent register 13 need be referred to, and the user register 14 need not be prepared.

[0079] The official response generation module 15 obtains from the data management system 19 all the information, including the information to be accessed, that is requested in the HTTP request, and generates a reply for the transmission source of the HTTP request.

[0080] The preview response generation module for a guest user 16 obtains only that information which is mentioned in the HTTP request and is stored in the data management system 19, and for which the access rights are possessed by a guest user. Further, the preview response generation module for a guest user 16 also obtains for the guest user metadata describing the official content of the obtained information, and generates a response to the transmission source of the HTTP request.

[0081] The preview response generation module for a non-registered user 17 obtains, from the data management system 19, the metadata for a non-registered user who does not possess access rights, and generates a response to the transmission source of the HTTP request.

[0082] The response generation module for a search engine 18 obtains, from the data management system 19, the metadata for the robot of the search engine 20, and generates a response to the robot that is the transmission source of the HTTP request.

[0083] The contents of the information obtained by the response generation modules 15 and 18 and the responses generated thereby will be described later. In this embodiment, four kinds of response generation modules are provided in accordance with the kinds of HTTP request transmission sources, but the generation modules are not limited to these four. Especially for modules other than the official response generation module 15, more generation modules may be provided in accordance with the range of the access rights that is accurately set, or conversely, only a single response module may be employed to deal with an HTTP request transmission source that does not have access rights.

[0084] The data management system 19 stores information (including digital content and a service) for a service to be provided by the web site 10. The information stored in the data management system 19 is main information 19a to be provided by the web site 10 and metadata 19b describing the main information 19a.

[0085] The main information 19a includes information for which access is limited and information for which access is not limited. Only a user who possesses access rights can acquire or read the information for which access is limited, while all users can acquire or read the information for which access is not limited. The access rights can be set in various ways, such as for an official user who is permitted to access all information for which access is limited, or a guest user who is permitted to access information with the provision that only a part of the information will be made available, or that the quality of the content will be reduced.

[0086] The metadata 19b is provided instead of the main information 19a for a user who does not possess the access rights required for the main information 19a for which access is limited. The metadata 19b includes an explanation of the contents of the main information 19a, a keyword concerning the main information 19a or a message explaining how to request the access rights required to acquire or to read the main information 19a, and is mainly text.

[0087] The main information 19a and the metadata 19b will now be described by using specific examples.

[0088] Assume that the main information 19a is educational material for studying the theory of relativity in physics, and includes an explanatory statement, static image data, moving image data and voice data, and that only an official user is permitted to access the three kinds of data other than the static image data, and that both an official user and a quest user are permitted to access the static image data.

[0089] In this case, the metadata 19b includes: a statement that the educational material package has been prepared for the study of the theory of relativity and that it includes an explanatory statement, static images, moving images and voices; keywords concerning the theory of relativity, such as “Einstein”, “velocity”, “light” and “gravity”; a method (a registration method or a fee payment method) by which access rights to read these data contents may be obtained; and a link to a page for accepting the conditions establishes to obtain access rights.

[0090] Further, the metadata 19b can include a message for a guest user indicating that the only information provided a guest user is static image data, an official user registration method and a link to a registration page.

[0091] In addition, if permission is granted for lower quality static image data to be provided a non-registered user, the metadata 19b may include a message stating that image data having a higher quality can be provided for a guest user or an official user.

[0092] FIG. 4 is a flowchart for explaining the processing for the embodiment.

[0093] In FIG. 4, when the web server 11 of the web site 10 receives an HTTP request (step 401), the user agent determination module 12 determines the type of user agent that represents the transmission source of the HTTP request (step 402). When the User-Agent header is examined by referring to the user agent register 13 and the user agent of the HTTP request is identified and is the robot of the search engine 20, program control is shifted to the response generation module for a search engine 18.

[0094] First the response generation module for a search engine 18 extracts from the data management system 19 the metadata 19b describing the information at the URL for which the HTTP request was submitted (step 403). In this case, since the metadata 19b is to be released to the robot of the search engine 20, the keywords constitute the main contents of the metadata 19b.

[0095] Then, the response generation module for a search engine 18 employs the metadata 19b to generate a response and transmits it via the web server 11 to the robot of the search engine 20, which is the transmission source of the HTTP request (step 404). Specifically, the response is an HTML document in which the keywords obtained at step 403 are enumerated.

[0096] When it is ascertained at step 402 that the user agent of the HTTP request is not the robot of the search engine 20, the user agent determination module 12 obtains the cookie information from the transmission source of the HTTP request (step 405), and employs the user ID in the cookie information to determine the type of user (the presence/absence of the access rights and their range) (step 406). This means that all the HTTP requests having a User-Agent header that has not yet been registered in the user agent register 13 are treated as though they were transmitted by the web browser 31 of the user terminal 30. The transmission source of the HTTP request could be a robot of the search engine 20 that has not been registered in the user agent register 13. However, even in this case, the robot of the search engine 20 will be regarded as a non-registered user, and at the least, a response including information such as the keywords is returned to the search engine 20, so that no particular inconvenience occurs.

[0097] When a user whose identification is based on cookie information has not yet registered in the user register 14, and when the cookie information has not been set, this user is identified as a non-registered user, i.e., a user who does not possess access rights to the main information 19a that is stored in the data management system 19 and for which access is limited. Thus, program control is shifted to the preview response generation module for a non-registered user 17.

[0098] First, the preview response generation module for a non-registered user 17 extracts from the data management system 19 the metadata 19b describing the information at the URL for which the HTTP request was submitted (step 407). In this case, since the metadata 19b is to be released to the non-registered user, the metadata 19b includes the keywords, the explanatory statement for the main information 19a, and the method to be used to obtain the access rights (the registration method).

[0099] Next, the preview response generation module for a non-registered user 17 employs the metadata 19b to generate a response, and transmits it via the web server 11 to the user terminal 30 of the non-registered user, the transmission source of the HTTP request (step 408). Specifically, the response is an HTML document including the explanatory statement and the keywords obtained at step 407, and a link to a page whereat a guest user registration will be accepted.

[0100] Assume that the non-registered user who issued the HTTP request shifts to the page whereat, in accordance with the response from the web site 10, an application for a guest user registration will be accepted, and applies for registration as a guest user (step 409). This registration application is transmitted as an HTTP request to the preview response generation module for a non-registered user 17, and the preview response generation module for a non-registered user 17, registers, in the user register 14, the user ID of the non-registered user as a guest user (step 410) and transmits an HTTP response to the user terminal 30 of the pertinent user in order to issue cookie information, which includes the user ID (step 411).

[0101] If, at step 406, the user ID of the cookie information obtained from the HTTP request has been registered as a guest user in the user register 14, it is ascertained that the transmission source of the HTTP request is a guest user, and program control shifts to the preview response generation module for a guest user 16.

[0102] First, the preview response generation module for a guest user 16 extracts, from the data management system 19, the metadata 19b describing the information at the URL that for which the HTTP request was submitted (step 412). In this case, since the metadata 19b is to be released to the guest user, the metadata 19b includes the keywords, an explanatory statement concerning the main information 19a, and method to be used to register as an official user. Following this, the preview response generation module for a guest user 16 employs the metadata 19b to generate a response, and transmits it via the web server 11 to the user terminal 30 of the guest user, the transmission source of the HTTP request (step 413). Specifically, the response is an HTML document which includes the explanatory statement and the keywords acquired at step 407, and a link to the page whereat a registration application for an official user is accepted (user registration).

[0103] Assume that the guest user who issued the HTTP request shifts to the page whereat, in accordance with the response from the web site 10, a user registration will be accepted, and applies for registration (step 414). This registration application is transmitted as an HTTP request to the preview response generation module for a guest user 16, and the preview response generation module for a guest user 16 registers in the user register 14, as an official user, the user ID of the guest user (step 415). Thereafter, the pertinent user is treated as an official user who possesses access rights for all the main information 19a.

[0104] When, at step 406, the user ID of the cookie information obtained from the HTTP request has been registered in the user register 14 as an official user, it is ascertained that the transmission source of the HTTP request is an official user, and program control is thereafter shifted to the official response generation module 15. The official response generation module 15 then obtains, from the data management system 19, the information at the URL for which the HTTP request was submitted (step 416), and transmits the information via the web server 11 to the user terminal 30 of the user that is the transmission source of the HTTP request (step 417).

[0105] In this manner, a response is generated in accordance with the transmission source of the HTTP request and the range of the access rights, and is transmitted to the transmission source. Therefore, a user who possesses the access rights for the main information 19a can obtain all the requested main information 19a, and a user who does not have the access right obtains the metadata 19b describing the requested main information 19a. A user who has a partial access right for the main information 19a obtains both the main information 19a within the range permitted for those access rights, and the metadata 19b describing the portion of the main information 19a for which the user does not hold possess the access rights. Since the information describing the main information 19a for which the user does not have access rights can be obtained as the metadata 19b, and the user can receive an index to use to determine whether he or she should acquire further access rights.

[0106] The robot of the search engine 20 can obtain the metadata 19b consisting of keywords for the main information 19a for which access is limited. Therefore, for a user who employs the search engine 20 the web site 10 can provide the information describing the main information 19a or can use it as an advertisement for the main information 19a.

[0107] A specific example for the embodiment will now be described. In this embodiment, a subscription service for providing, across the Internet, educational material for distance education for registered users is employed as an example.

[0108] At a web site 10, www.dummy.com, of the provider of this service, HTML documents for education material, which is a web page source, are provided via a web server 11. The education material includes links to the material elements of images, movies and narrations. That is, the education material and the element materials form the main information 19a. An educational material file and material element files are so arranged that a web browser 31 of a user terminal 30 can refer to them by using the following URLs.

• [0109] Educational material: http://www.dummy.com/edu.html
• [0110] Images: http://www.dummy.com/image.gif
• [0111] Movies: http://www.dummy.com/movie.mov
• [0112] Narrations: http://www.dummy.com/narration.au

[0113] Metadata 19b, wherein an overview, keywords, a category name and an importance level are written as text are prepared for the educational materials and the material elements. The definition of the importance level will be described later.

[0114] FIG. 5 is a diagram showing the metadata 19b for the educational material and the material elements.

[0115] Assume that the user agent that accesses the education material is a robot of a search engine 20 or the web browser 31 of the user terminal 30 of the user. When the transmission source of the HTTP request is the robot of the search engine 20, the robot cyclically visits the site www.dummy.com, obtains the URL of the educational material edu.html, and employs an HTTP response to prepare a keyword index for a search. Generally, the keyword extraction means differs at the site of the search engine. While this embodiment does not depend on this means, typical keyword extraction means used by a robot are well known in most cases. Therefore, it is preferable that an HTTP response be so prepared that a keyword can be easily extracted by the robot. For example, a keyword may be inserted in a title tag, or in the first paragraph.

[0116] When the transmission source of the HTTP request is the web browser 31 of the user terminal 30, the presence/absence of access rights and the range of the access rights are examined and a corresponding process is performed, depending on whether it is for a non-registered user, a guest user or a registered user. User IDs and passwords of users are registered in the user register 14 of the web site 10. A guest user is a user who employs a user ID that is so prepared that an overview of the educational material and part of its contents are provided as a sample to solicit user registration.

[0117] Under the above condition, when the web server 11 of the web site 10 receives an HTTP request for the acquisition of the education material, the web server 11 transmits the HTTP request to the user agent determination module 12.

[0118] The user agent determination module 12 refers to the user agent register 13 and the user register 14, and identifies the requested URL and the user type. Assume that an HTTP request shown in FIG. 6 is received via the web server 11 and refers to the education material edu.html. In order to identify the user type, the user agent identification information (<User#Agent>) written in the User-Agent header field on the second row and the cookie information (userid=<User#ID>) written in the Cookie head field on the fifth row are employed.

[0119] First, the user agent register 13 is examined in order to distinguish the robot of the search engine 20 from the web browser 31 of the user terminal 30. FIG. 7 is a diagram showing an example user agent register 13 in this case. The client identification information <User#Agent> written adjacent to the User-Agent tag in the HTTP request in FIG. 6 is compared with the user agent register 13 to determine whether the transmission source of the HTTP request is the robot of the search engine 20 or the web browser 31 of the user terminal 30. As is described above, since the user agent of the search engine 20 or the web browser 31 are frequently employed and are usually well known, the transmission sources of almost all the HTTP requests can be identified as either the robot or the web browser 31 by examining the user agent register 13.

[0120] When the transmission source of the HTTP request is the web browser 31 of the user terminal 30, the user register 14 is employed to identify the user type based on the access rights. FIG. 8 is diagram showing an example user register 14. The user ID <User#ID>, which is written as cookie information adjacent to the User#ID tag in the HTTP request in FIG. 6, is compared with the user register 14, and the user type is identified. Thus, when the cookie information is not included in the HTTP request, the user can be identified as a non-registered user; when the cookie information, i.e., the user ID, is included in the HTTP request and is registered as a guest user in the user register 14, the user can be identified as a guest user; and when the user ID is registered as a registered user, the user can be identified as a registered user.

[0121] The user agent determination module 12 calls up a response generation module in accordance with the type of the transmission source of the HTTP request, or the user type of the transmission source. That is, the response generation module for a search engine 18 is called up when the transmission source is the robot of the search engine 20; the preview response generation module for a non-registered user 17 is called up when the transmission source is the web browser 31 and is used by a non-registered user; the preview response generation module for a guest user 16 is called up when the transmission source is the web browser 31 and is used by a guest user; and the official response generation module 15 is called up when the transmission source is the web browser 31 and is used by a registered user.

Hereinafter, these individual cases are described.

[0122] 1) When the transmission source of the HTTP request is the robot of the search engine 20:

[0123] When the transmission source of the HTTP request is the robot of the search engine 20, the user agent determination module 12 transmits the requested URL to the response generation module for a search engine 18. The response generation module for a search engine 18 searches for the metadata 19b that correspond to the material elements included in the document at the URL, and generates an HTTP response that includes only the keywords and the category name. The HTTP response is then transmitted, via the web server 11, to the robot of the search engine 20 that is the transmission source of the HTTP request.
An example, HTTP response for this case is shown in FIG. 9.

[0124] At the site of the search engine 20, the robot of the search engine 20 extracts the keywords from the text adjacent to the <body> tag in the HTTP request, prepares a keyword index and creates the URL list.

[0125] An example URL list in this case wherein the URLs and corresponding keywords are entered is shown in FIG. 10.

[0126] The search engine 20 receives a keyword that is entered by a user who employs the search engine 20 to search for desired information, and examines the keyword index to find the URL that includes the pertinent keyword. As the search result, an example HTTP response shown in FIG.11, which includes as a link the obtained URL, is prepared and is transmitted to the web browser 31 of the user.

[0127] 2) When the transmission source of the HTTP request is the web browser 31 of the user terminal 30:

[0128] When the transmission source of the HTTP request is the web browser 31, the user agent determination module 12 obtains the cookie information from the transmission source, and examines the user register 14 to determine the type of the user that issued the HTTP request. When the cookie information is not set, or when the user is not found in the user register 14, the pertinent user is identified as non-registered.

[0129] 2-1) When the transmission source of the HTTP request is a non-registered user:

[0130] When the user is identified as non-registered, the user agent determination module 12 transmits, to the preview response generation module for a non-registered user 17, the URL of requested educational material and an instruction for the generation of a response for the non-registered user. The preview response generation module for a non-registered user 17 then searches for the metadata 19b that corresponds to the element materials that are referred to at the designated URL, and generates an HTTP response that presents as a sample an overview of the educational material and part of its contents, and that includes an advertisement for soliciting user registration. The HTTP response is then transmitted to the web browser 31 of the user terminal 30, which is the transmission source of the HTTP request.

[0131] An example HTTP response in this case is shown in FIG. 12.

[0132] In the HTTP response in FIG. 12, ad.html included in the tag on the ninth row is the URL of a document that includes the sample of the educational material and an advertisement for soliciting user registration, and includes a form for issuing to a non-registered user the account of a guest user. When the user clicks on the hyperlink that is displayed by the web browser 31 using the tag on the ninth row, the display is shifted to the page ad.html, so that the user can submit the guest user application. This application is then transmitted as an HTTP request to the preview response generation module for a non-registered user 17. Thereafter, the preview response generation module for a non-registered user 17 registers a new user ID (hereinafter referred to as “anderson”) in the user register 14, and transmits an HTTP response to the web browser 31 in order to issue cookie information that includes this user ID.

[0133] An example HTTP response for issuing the cookie information is shown in FIG. 13. Upon the receipt of the HTTP response, the web browser 31 stores, as its own user ID, the value userid=anderson in the Set-Cookie header field on the fourth row.

[0134] Since the registration of the guest user has been completed, the user register 14 in FIG. 8 is updated as is shown in FIG. 14.

[0135] 2-2) When the transmission source of the HTTP request is a guest user:

[0136] When the user who is now registered as guest user “anderson” issues an HTTP request to access the URL for educational material, the cookie information is included in the HTTP request, and the user agent determination module 12 examines the cookie information to obtain the client identification information for the transmission source. When as a result of an examination of the user register 14 “anderson” is identified as a guest user, the user agent determination module 12 transmits, to the review response generation module for a guest user 16, the URL of the requested education material and an instruction for the generation of a response to the guest user. The preview response generation module for a guest user 16 then searches for the metadata 19b that correspond to the individual material elements at the URL that are referred to, and generates an HTTP response including only the URL that corresponds to the material element whose importance level is lower than a predetermined reference. Then, the HTTP response is transmitted to the web browser 31 of the user terminal 30, the transmission source of the HTTP request.

[0137] An example HTTP response in this case is shown in FIG. 15.

[0138] The importance level is an index value used to determine whether the main information 19a is included in the range of the access rights possessed by the user. That is, when the importance level, such as the metadata 19b shown in FIG. 5, is set for the main information 19a (education material: B, static image: C, movie: A, narration: B, where the importance level is reduced in alphabetical order with A being the highest), only the main information 19a that is equal to or lower than importance level B is transmitted to the guest user in response to an HTTP request. The metadata 19b concerning this information is transmitted instead of the main information 19a, which has an importance level A.

[0139] Therefore, when the user tries to access the URL of edu.html, i.e., when an HTTP request for edu.html is issued, in the example in FIG. 15 the importance level A of the movie is higher than reference B, and an HTTP response includes metadata 19b “Abstract” instead of the URL of the movie itself. This HTTP response also includes contact.html including a user registration form.

[0140] When the user enters the user ID and the password in the user registration form and returns it via the web browser 31, the user agent determination module 12 adds the user ID and the password pair to the user register 14 as a registered user. An example user register 14 in this case is shown in FIG. 16.

[0141] 2-3) When the transmission source of the HTTP request is a registered user:

[0142] When the transmission source of the HTTP request is a registered user, the user agent determination module 12 transmits, to the official response generation module 15, the URL of the requested education material and an instruction for the generation of a response to the registered user. The official response generation module 15 distributes edu.html to the requesting source as an HTTP response.

[0143] As is described above, when access rights are designated for the main information 19a stored in the web site 10, and when the HTTP request for accessing the main information 19a is received from a user agent who does not possess the access rights, the web site 10 can transmit, as an HTTP response, the metadata 19b describing the main information 19a, instead of the main information 19a. Thus, since the web site 10 can provide the HTTP request transmission source information concerning the main information 19a, the acquisition of the access rights for the main information 19a can be requested. Even when the transmission source of the HTTP request is a user who does not possess access rights, at the least, information can be obtained for explaining the contents of the main information 19a. Thus, no case occurs wherein no information is acquired, and if needed, access rights can be acquired to obtain the main information 19a.

[0144] Furthermore, when the transmission source of the HTTP request is the robot of the robot search engine 20, the metadata 19b, describing the main information 19a that can not originally be accessed, can be obtained, so that the main information 19a can be added to the search list. Therefore, the main information 19a can be searched for by the search engine 20, and for the web site 10, the main information 19a can be advertised.

[0145] In the above example, the user obtains access rights for the main information 19a by user registration. However, this embodiment can be applied for a case wherein the main information 19a is provided by the payment of a fee.

[0146] That is, when an appropriate subscription system is employed and when access to the main information 19a is permitted for a user who has paid an information charge (a browsing fee, etc.), instead of the main information 19a, the metadata 19b for the main information 19a would be transmitted to a user who did not pay the fee. In this case, the user agent determination module 12 would determine whether or not the transmission source of the HTTP request was a user who had paid the charge for the main information 19a.

[0147] With this system, the web site 10 can advertise the main information 19a, which is subscription information, and the user can, at the least, obtain at no cost information concerning the subscription information.

[0148] As is described above, according to the present invention, metadata concerning information for which access is limited can be provided in accordance with an access request issued by a robot search engine to a site that limits access.

[0149] Furthermore, according to the present invention, appropriate information can be selectively provided, by a site that limits access, in accordance with the access right of the source that issues an access request for information for which access is limited.

Description of the Symbols is repeated herein for quick reference.

• [0150] 10: Web site
• [0151] 11: Web server
• [0152] 12: User agent determination module
• [0153] 13: User agent register
• [0154] 14: User register
• [0155] 15: Official response generation module
• [0156] 16: Preview response generation module for guest user
• [0157] 17: Preview response generation module for non-registered user
• [0158] 18: Response generation module for search engine
• [0159] 19: Data management system
• [0160] 19a: Main information
• [0161] 19b: Metadata
• [0162] 20: Search engine
• [0163] 30: User terminal
• [0164] 31: Web browser

[0165] Having described embodiments of the invention it is noted that modifications and variation can be made by persons skilled in the art in light of the above teachings. It is therefore to be understood that changes may be made in the particular embodiments of the invention disclosed which are within the scope and spirit of the invention as defined by the appended claims.