JP5135165B2 - Content server system, content server, and client computer - Google Patents

Description

  The present invention relates to a content server system, a content server, and a client computer having a function of performing name resolution in advance.

In general, a plurality of computers represented by the World Wide Web (WWW) or the like provide computers on the Internet (hereinafter referred to as “content servers”) and computers used by users who receive the services. In an environment existing as a “client” (hereinafter referred to as “client”), a computer on the Internet has an identification code (hereinafter referred to as “ID”) called an Internet Protocol (IP) address (hereinafter referred to as “IP address”). And using the IDs identified from each other for communication. The IP address is represented by a combination of several numbers such as 10.1.2.2.3 and 192.168.0.1.
The IP address represented by this combination of numbers is suitable for processing by a computer, but a computer user (user) identifies a partner computer (hereinafter referred to as “node”) with which communication is performed. Is an identification code that is very difficult to handle.

Therefore, in order to make it easier for the user to identify the node with which communication is performed, an identifier attached to a network or node existing on the Internet is, for example, www. example. An identifier called a domain name composed of a combination of words that can be easily identified by the user such as “com” is used.
However, this domain name is an expression that can be easily identified by the user, but cannot be used as it is as an identification code processed by the computer, and is identification information that is difficult to use.

  In this way, the representations of identification information that can be easily identified by the computer and the user are different from each other, and as a method for resolving this problem and allowing both the computer and the user to recognize each other, the domain name and the IP address are associated A mechanism (a mechanism for associating this domain name with an IP address is called “name resolution”) is disclosed.

  Non-Patent Document 1 and Non-Patent Document 2 disclose a mechanism called a domain name service (DNS). This domain name service associates the IP addresses of a plurality of computers on a network with domain names, and a server (hereinafter referred to as “DNS server”) that holds the associated name information (name information database) is a client Alternatively, it is a mechanism for responding to name resolution requests from nodes on the network. In this name information database, a single DNS server does not manage all the name information on the network, but a plurality of DNS servers each hold a part of the name information database, and each DNS server is on the network. In response to name resolution requested in collaboration with

  Name resolution in Non-Patent Document 1 and Non-Patent Document 2 will be described. FIG. 22 shows a communication procedure of content using a DNS server. In FIG. 22, when a request for content provided by the content server 1 is generated from the user, the client first performs name resolution, and in process 1, the client makes an inquiry about the name information of the content server 1 from the client to the DNS server. Then, the IP address of the content server 1 is inquired using the domain name of the content server 1 as a name resolution request message. Subsequently, the DNS server that has received the name information inquiry from the client makes a response to the name information inquiry, that is, the IP address of the content server 1. Note that the next process 2 cannot be performed until the process 1 is completed.

  Subsequently, in processing 2, the client requests content from the content server 1 using the IP address corresponding to the domain name obtained from the DNS server (communication to the content server 1 is performed for the first time), and the content server 1 transfers the requested content. Thereby, the content requested by the user can be obtained.

  Subsequently, when a request for the content provided by the content server 2 is generated from the user, a content request is made to the content server 2 after name resolution is performed in the same manner as described above in the processing 3 and processing 4, and the user Get the requested content.

The communication speed experienced by the user in communication on the Internet is not only the transfer speed related to the transfer of the requested content, but also the total time including the communication and processing time related to name resolution performed before transferring the content. Become. This name resolution process is a process that is always necessary when the content server from which the user is provided with the content is different, and needs to be performed before starting the transfer of the target content. This is because even if the communication speed related to the transfer of the target content is improved, if the time required for the name resolution processing has not improved, the user does not necessarily experience the improvement in the communication speed. It is not possible.
Also, when the number of clients increases, the load on the DNS server increases due to name resolution processing that is performed in advance when content is requested from the user.

Therefore, in Non-Patent Document 1 and Non-Patent Document 2, the name information that has been queried is held (cached) in a DNS server or a storage means with a fast response speed provided in the client, and thereafter, the same content server A method for speeding up the name resolution process by using the name information held in the storage means having a high response speed is also disclosed. However, when name information is not held in the client, that is, when the request is for a content server that requests content for the first time, it is necessary to perform new name resolution processing when a request for content occurs.
As described above, the time required for the name resolution processing becomes an overhead in the request and transfer of the original target content, which causes a reduction in the communication speed experienced by the user.

  In order to avoid a decrease in the transfer speed experienced by the user as described above, in Patent Document 1, as shown in FIG. 23, for example, a content server that may be requested by the user in the future is automatically set as follows. It is specified based on link information to other content described in the currently presented content. Thereafter, name resolution of the identified content server is performed in advance (prefetch access) to acquire the content, and the acquired content is held (cached) by the client. When a request for content is generated from the user, the transfer overhead related to the name resolution processing required after the content request is generated by presenting the content acquired by the client in advance. And a method for improving the communication speed experienced by the user by reducing the time until the content is presented to the user (this method is referred to as “prefetch”) is disclosed.

Also, in Patent Document 1, as shown in FIG. 24, the content is not acquired by the client but acquired via a server (hereinafter referred to as “cache server”) that holds the content requested by the user. This cache server automatically acquires the content by performing name resolution in advance based on the currently presented content and the user profile information, etc., as in the above-described prefetch access. Is held (cached). When a request for content is generated from the user, the content acquired by the cache server in advance is presented to improve the communication speed experienced by the user, similar to the above-described prefetch access. A method is disclosed.
P. Mockapetris, “Domain Names-Concepts and Facilities,” IETF RFC 1034, 1987. P. Mockapetris, “Domain Names—Implementation and Specification,” IETF RFC 1035, 1987. JP 2001-101061 A

  However, in the method in Patent Document 1, the name resolution processing performed at the time when a content request is generated becomes unnecessary by performing the name resolution processing in advance, and the total number of processing is the same. . That is, since the number of communications for obtaining name information performed on the DNS server is the same, there is a problem that the communication load of the DNS server cannot be reduced.

  In addition, the name information inquiry cycle to the DNS server that is automatically performed by the client or the cache server is much shorter than the cycle in which the user requests the content, and thus there is a possibility that a plurality of name information inquiries may occur simultaneously. Yes, the communication load of the DNS server cannot be reduced. By this, when the communication load of the DNS server is large and it takes time to answer the requested name information, name resolution is not completed in advance, and the overhead time until content is acquired is reduced. There is a problem that the user cannot experience the improvement in communication speed.

  In addition, if the content requested by the user is different from the content acquired in advance, that is, if name resolution fails in advance, it is necessary to perform name resolution again, thus reducing the overhead time until content is acquired. There is also a problem that the user cannot experience the improvement in communication speed.

  The present invention has been made on the basis of the above problem recognition, and reduces the time required for name resolution in an environment where there are a plurality of content servers providing services on the Internet and clients receiving the services. And it aims at providing the content server system which a user can experience the improvement in communication speed by reducing the communication load with respect to a DNS server.

In order to solve the above problems, a content server system of the present invention includes one or more content servers that provide content, one or more client computers that use the provided content, the content server, and the In a content server system in which one or a plurality of DNS servers that store name information in which a client computer's domain name is associated with an IP address are connected to a network, the content server is based on the first content that the client computer has. The content analysis means for specifying another content server that provides the second content referred to by the first content, and the name information of the other content server specified by the content analysis means are acquired from the DNS server. Name solution Means information storage means for storing the first content and the name information of the other content server acquired by the name resolution means in association with each other, and the client computer that has requested transmission of the first content in the first content, and a content transmission unit configured to send said name information of the other contents server stored in the name information storing means, wherein the client computer is received from the content server The name information cache means for storing the name information of the other content server and the name information cache means when using the second content referred to by the first content received from the content server. Based on the stored name information of the other content server Characterized in that it comprises a content request means for requesting the second content to another content server, the.

Further, the content transmission unit of the present invention, sends the link information indicating that the name information of the other contents server to the name information storage means is stored, the content request means, from said content server based on the received pre-Symbol link information, requests transmission of the name information stored in the content server, and wherein the.

Further, the content transmission unit of the present invention transmits the name information of the other contents server stored in the name information memory means together with the first content, characterized in that.

The content server of the present invention is a content server connected to a network and providing content. The content server provides other content that is referred to by the first content based on the first content that the content server has. Content analysis means for specifying a content server, name information of the other content server specified by the content analysis means, a name that associates the domain name and IP address of the content server and the client computer that uses the provided content A name resolution unit that acquires information from a DNS server that stores information; a name information storage unit that stores the first content and the name information of the other content server acquired by the name resolution unit in association with each other; The client that requested transmission of the content of 1 The computer, and the first content, characterized in that it and a content transmission unit configured to send said name information of the other contents server stored in the name information storage means.

Further, the content transmission unit of the present invention, to send link information indicating that the name information of the other contents server to the name information storage means is stored, characterized in that.

Further, the content transmission unit of the present invention transmits the name information of the other contents server stored in the name information memory means together with the first content, characterized in that.

The client computer of the present invention is connected to a network and uses the content provided from the content server. The client computer uses the second content referred to by the first content held by the content server itself received from the content server. Name information cache means for storing name information of other content servers that provide content, and the name information cache means when using the second content referred to by the first content received from the content server Content request means for requesting the second content from the other content server based on the name information of the other content server stored in the content server, wherein the content request means is received from the content server. Said Content based on the link information indicating that the name information in the server is stored, to request the transmission of the name information stored in the content server, and wherein the.

The client computer of the present invention is connected to a network and uses the content provided from the content server. The client computer uses the second content referred to by the first content held by the content server itself received from the content server. Name information cache means for storing name information of other content servers that provide content, and the name information cache means when using the second content referred to by the first content received from the content server on the basis of the name information stored the other content server, and a content request means for requesting the second content to the another content server, the content request means, said from the content server First Storing pre Symbol name information to the name information cache unit received with Ceiling, characterized in that.

According to the present invention, the content server can acquire name information related to the content provided by the content server, provide the content, and simultaneously provide the related name information when the content is requested. At the same time, other related contents can be requested based on the acquired name information.
In this way, the name resolution performed before the transfer of the target content is reduced in response to the content request from the client, and the number of name information inquiries to the DNS server that is performed when performing the name resolution is reduced. Thus, it is possible to provide a content server system that allows the user to experience an improvement in communication speed.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an example of the overall configuration of the content server system according to the present embodiment. In FIG. 1, a content server system 1 is composed of content servers 10-1, 10-2, 10-3, DNS servers 20-1, 20-2, and client machines 30-1, 30-2, 30-3. Are connected via a network 40 such as a WAN (Wide Area Network) / LAN (Local Area Network).

Content servers 10-1, 10-2, and 10-3 (hereinafter referred to as “content server 10” collectively) provide services (contents) in response to requests from other computers connected to the network 40. Server.
DNS servers 20-1 and 20-2 (hereinafter referred to as “DNS server 20” collectively) hold name information in which the IP addresses of a plurality of computers connected to the network 40 are associated with domain names. In response to a name resolution request from a computer on the network 40, the server answers the name information it holds.

  Client machines 30-1, 30-2, and 30-3 (hereinafter referred to as “client machine 30” when collectively referred to) are computers used by users who receive provision of services (contents). The client machine 30 requests content from the content server 10 connected to the network 40 in response to an operation by the user. If the name resolution is not completed when the content is requested, name information is requested from the DNS server 20 connected to the network 40.

  1 shows an example in which three content servers 10 and three client machines 30 and two DNS servers 20 are connected to the network 40, but the present invention is not limited to this. The number of content servers 10, client machines 30, and DNS servers 20 to be connected is not specified.

<First Embodiment>
Hereinafter, the content server system in the present embodiment will be described. FIG. 2 is a block diagram showing the configuration of the content server system in the present embodiment. In FIG. 2, the content server system 100 includes an HTTP (Hyper Text Transfer Protocol) server 10, a DNS server 20, and a client machine 30, which are connected via a network 40.

  The HTTP server 10 includes contents 110-1, 110-2, 110-3 (hereinafter referred to as “content 110” when collectively expressed), a content analysis unit 120 (content analysis means), and a name information database (DB) 130 (name). An information storage unit), a name resolution unit 140 (name resolution unit), and a content communication unit 150. The DNS server 20 includes a name response unit 21. The client machine 30 includes a name resolution unit 310, a name information cache 320 (name information cache means), and a client communication unit 330.

  In the content server system 100 of FIG. 2, the HTTP server 10, the DNS server 20, and the client machine 30 connected to the network 40 will be described as one unit, but a plurality of HTTP servers are used. The same applies when the DNS server 20 and the client machine 30 are connected to the network 40.

  The HTTP server 10 is a content server that provides the content 110 via the network 40. When the content 110 is requested from the client machine 30 via the network 40, the HTTP server 10 provides the requested content 110 in the own HTTP server 10. The HTTP server 10 manages name information related to the content 110 in the HTTP server 10 and other content included in the content 110.

  The content 110 is possessed by the HTTP server 10 provided in response to a request from the client machine 30, for example, a description of a document, an embedding of an image, or a description associated with (hyperlinked) other files to be referred to. These are content files such as HTML (Hyper Text Markup Language) files and image files. Note that there is no limitation on other content associated (linked) with the content 110, and, for example, another content in the own HTTP server 10 or content provided by another content server is linked.

  The name information DB 130 is a database that stores information related to other content linked to the content 110 of the HTTP server 10 itself. The name information DB 130 stores a content management table 131, a name information table 132, and name information files 133-1, 133-2, and 133-3 (hereinafter referred to as “name information file 133” when collectively expressed). .

  The content management table 131 is a file for managing the content 110 possessed by the HTTP server 10 itself. The content management table 131 stores the state of the content 110 (for example, new creation, modification, deletion, etc.) of the HTTP server 10 itself and the name information file 133 corresponding to the content 110 in association with each other.

  The name information table 132 is a file for recording information of other contents linked to the contents 110 of the HTTP server 10 itself. In the name information table 132, the domain name of other content linked to the content 110 owned by the HTTP server 10 itself, the content 110 (extraction source content) linked to the domain, and the IP corresponding to the domain name are stored. The address and the expiration date of the link for the IP address are stored in association with each other.

  The name information files 133-1, 133-2, and 133-3 are files that indicate link destination information linked to the contents 110-1, 110-2, and 110-3. Each name information file 133 stores the IP address of other content linked to the corresponding content 110, the domain name corresponding to the IP address, and the expiration date of the link for the IP address in association with each other. Has been.

  The content analysis unit 120 is a block that analyzes the name information of the content 110 possessed by the HTTP server 10 itself and other content linked to the content 110. The content analysis unit 120 extracts (lists up) link information (for example, a linked domain name) described in the content 110 that is changed when any of the content 110 is newly created, modified, or deleted. The content management table 131 and the name information file 132 in the name information DB 130 are created or updated. In addition, the content analysis unit 120 notifies the name resolution unit 140 that the content management table 131 and the name information file 132 in the name information DB 130 have been changed.

  The name resolution unit 140 is a block that performs name resolution according to the content management table 131 in the name information DB 130 input from the content analysis unit 120 and the change information of the name information file 132. The name resolution unit 140 creates a name information file according to the state of the content 110 in the content management table 131 in the name information DB 130 created or updated by the content analysis unit 120 (for example, newly created, modified, deleted, etc.). The domain name listed in 132 is not completely resolved, and the domain name is resolved. The name resolution by the name resolution unit 140 is performed by outputting a name information inquiry request to the DNS server 20 to the content communication unit 150.

  The name resolution unit 140 updates the name information table 132 based on the name information obtained from the content communication unit 150. In addition, the name resolution unit 140 updates the name information file 133 corresponding to each content 110 based on the updated name information table 132.

The content communication unit 150 is connected to the DNS server 20 and the client machine 30 connected via the network 40 in response to a request for content from the client machine 30 and a name information inquiry request input from the name resolution unit 140. This block performs communication.
In response to a content request from the client machine 30, the content communication unit 150 transmits the content 110 that the HTTP server 10 has via the network 40. For example, when the content 110-1 is requested from the client machine 30, the requested content 110-1 is transmitted via the network 40. When a plurality of contents are requested from the client machine 30, it is also possible to transfer a plurality of contents corresponding to the contents 110 that the client machine 30 has, for example, the contents 110-1 and 110-2.

Further, when the content communication unit 150 transmits the content 110 requested from the client machine 30, the name information file 133 corresponding to the content 110 to be transmitted is transmitted in association with the client machine 30 in a format that can be acquired. The transmission method in which the content 110 and the name information file 133 are associated is performed by adding information indicating that the name information file 133 exists in the content 110.
Further, the content communication unit 150 makes a name information inquiry to the DNS server 20 via the network 40 in response to the name information inquiry request input from the name resolution unit 140, and returns a name information response from the DNS server 20. Tell the name resolution unit 140.

The DNS server 20 is a server that answers name information that has been inquired through the nutwork 40.
The name response unit 21 is a block that answers an IP address corresponding to the domain name for which the DNS server 20 has been inquired.

  The client machine 30 is a computer used by a user who receives provision of the content 110 possessed by the HTTP server 10 via the network 40. When making a content request to the HTTP server 10, the client machine 30 first checks whether or not the name resolution process has been completed, and if the name resolution process has been completed, the client machine 30 has been resolved. The content is requested according to the name information. If the name resolution processing has not been completed, first, in order to perform name resolution processing, a name resolution inquiry is made to the DNS server 20, and a content request is made after the name resolution processing is completed.

  The client communication unit 330 is a block that communicates with the HTTP server 10 and the DNS server 20 via the network 40. In order to request content from the HTTP server 10, the client communication unit 330 first performs name resolution processing. When performing a name resolution process, the client communication unit 330 requests name information from the DNS server 20 connected to the network 40 and stores the acquired name information in the name information cache 320. The client communication unit 330 does not perform name resolution processing when the name information cache 320 already has name information when the client machine 30 requests content from the HTTP server 10.

  The client communication unit 330 makes a content request to the HTTP server 10 according to the name resolution processing result. When the client machine 30 makes a request for content to the HTTP server 10, the client communication unit 330 makes a request for the content 110 to the HTTP server 10 connected to the network 40, and uses an interface (not shown) for the acquired content 110. And presenting it to the user who uses the client machine 30 through the name resolution unit 310.

Further, the client communication unit 330 makes a request for the name information file 133 to the HTTP server 10 in response to a request for acquisition of the name information file 133 from the name resolution unit 310, and sends the acquired name information file 133 to the name information cache 320. To remember.
Further, when the client communication unit 330 requests to provide another content linked to the acquired content 110, if the name information cache 320 already has an IP address of another content to be requested, Without making a name resolution inquiry to the server 20, a content request is made directly to another content server.

The name resolution unit 310 is a block that performs name resolution for another content linked to the content 110 input from the client communication unit 330.
The name resolution unit 310 checks whether the content 110 input from the client communication unit 330 includes information indicating that the corresponding name information file 133 exists, and the name information file 133 exists. Is included, the client communication unit 330 is requested to acquire the name information file 133. When the information indicating that the corresponding name information file 133 exists in the content 110 is not included, the client communication unit 330 is not requested to acquire the name information file 133.

The name information cache 320 is a block that stores name information acquired by the client machine 30.
The name information cache 320 stores name information acquired from the DNS server 20 by name resolution processing and name information of the name information file 133 acquired from the HTTP server 10, and is connected to the network 40 from the client machine 30. When the content is acquired from the content server, the client communication unit 330 refers to the content.

Next, in the content server system 100 of this embodiment, a processing procedure performed by the HTTP server 10 for analyzing the name information of the content 110 owned by the HTTP server 10 itself and other content linked to the content 110 will be described. To do. FIG. 3 is a flowchart illustrating a processing procedure in which the content analysis unit 120 analyzes name information of the content 110.
Note that the content analysis unit 120 monitors the status of new creation, modification, and deletion of the content 110 held by the own HTTP server 10 and registers the content management table 131 in the name information DB 130, but the name of the content 110 in FIG. In the analysis of information, it is assumed that the content management table 131 has already been registered and the content 110 has been changed.

  FIG. 4 shows an example of the registered content management table 131. The content management table 131 shown in FIG. 4 includes the content name of the content 110 owned by the HTTP server 10 itself, the state of the content 110 (for example, new creation, modification, deletion, etc.), and the name information file 133 corresponding to the content 110. Is an associated file. 4, the content name of the content 110 that the HTTP server 10 has is content 110-1 = index. html, content 110-2 = index2. html, content 110-3 = index3. The name information file 133-2 (index2-nameinfo) and the name information file 133-3 (index3-nameinfo) are associated with the contents 110-2 and 110-3, respectively.

  Further, the contents 110-1 and 110-2 are corrected (state = “newly created / modified”), and the content 110-3 is deleted (state = “deleted”). In the state of the content 110, new creation and modification are not distinguished, but can be registered separately.

  First, when the state of the content 110 held by the HTTP server 10 is updated and the content management table 131 is changed, the content analysis unit 120 indicates that the content management table 131 indicates “new creation / correction” in step S101. It is confirmed whether or not there is any content, and if there is a state indicating “new creation / correction” in the content management table 131, the process proceeds to step S102. On the other hand, if there is no state indicating “new creation / correction” in the content management table 131, the process proceeds to step S109.

  Subsequently, in step S102, the content analysis unit 120 extracts all expressions referring to other content included in the content 110-1 indicating “new creation / correction” in the content management table 131. For example, in the example of an HTML file representing an expression referring to other content included in the content 110-1 shown in FIG. 5, the A tag (line a in FIG. 5) showing a hyperlink to the other content is shown. “Www.example.com/index.html” and “www.abc.com/img.jpg” shown in the img tag (line b in FIG. 5) indicating image embedding are extracted. Is done.

  Subsequently, in step S103, the content analysis unit 120 obtains a domain name, for example, “www.example.com” and “www.abc.com” in FIG. List up. In the domain name list, only one duplicate domain name is listed. In addition, when a reference is made to the same domain name of the own HTTP server 10, that is, another content in the own HTTP server 10, the list is not listed. For example, when the domain name of the own HTTP server 10 is “www.abc.com”, the domain name listed in FIG. 5 is only “www.example.com”.

  Subsequently, the content analysis unit 120 confirms whether or not the listed domain name is registered in the name information table 132 in step S104. If the domain name is not registered in the name information table 132, the process proceeds to step S105. If the domain name is registered in the name information table 132, the process proceeds to step S106.

  FIG. 6 shows an example of the registered name information table 132. The name information table 132 shown in FIG. 6 associates the listed domain name, the content name from which the domain name is extracted, the IP address corresponding to the domain name, and the expiration date of the IP address. File. In FIG. 6, three domain names (“www.example.com”, “www.def.co.jp”, and “www.ddd.co.jp”) have already been listed and extracted. The original contents are all contents 110-2 (index2.html). In addition, all the domain names listed have not yet been associated with IP addresses, and their expiration dates have not been set.

  Subsequently, if the domain name listed in step S104 is not registered in the name information table 132 in step S104, the content analysis unit 120 extracts the domain name listed in the name information table 132 and the extraction source in step S105. Register the content and set the expiration date to the current time.

  If the listed domain name is registered in the name information table 132 in step S104, the content analysis unit 120 adds the extraction source to the domain name registered in the name information table 132 in step S106. Content is added (if the source content of the domain name already listed is registered, it is overwritten, but the content of the final name information table 132 is not changed). Note that a new expiration date is not set for a domain name already registered in the name information table 132.

  FIG. 7 shows an example of the name information table 132 obtained by analyzing the name information. The name information table 132 shown in FIG. 7 is a file in which processing related to the domain names listed on the name information table 132 shown in FIG. 6 is executed. In FIG. 7, the newly listed domain name (“www.abc.com”) is registered in step S105 as the source content as content 110-1 (index.html) and the expiration date as the current time. Yes. Further, the domain name already registered (“www.example.com”) indicates that the content 110-1 (index.html) is added as the extraction source content in step S106.

  Subsequently, in step S107, the content analysis unit 120 confirms whether or not the registration processing for all the domain names listed in the name information table 132 has been completed, and processes all the domain names listed. If is completed, the process proceeds to step S108. If all the domain names listed have not been processed, the process returns to step S104, and the registration process of the domain name in the name information table 132 is repeated.

  Subsequently, in step S108, the content analysis unit 120 confirms whether or not the processing for all the contents in which the content management table 131 indicates “new creation / correction” has been completed, and for all the contents. When the process is completed, the process proceeds to step S109. If all the contents have not been processed, the process returns to step S102 to repeat the domain name listing and the registration process to the name information table 132.

  Subsequently, in step S101, the content analysis unit 120 determines that there is no content in which the content management table 131 indicates “new creation / correction”, or in step S108, the content management table 131 displays “new creation”. If the processing for all the contents indicating “correction” has been completed, in step S109, the content management table 131 confirms whether or not there is any content indicating “deleted”. If there is a state indicating “delete” in the content management table 131, the process proceeds to step S110. If there is no state indicating “deleted” in the content management table 131, the name information analysis processing is completed.

  Subsequently, in step S110, the content analysis unit 120 confirms whether or not the deleted content 110, for example, the content 110-3 is registered in the extraction source content of the name information table 132. If it is registered in the extraction source content, the process proceeds to step S111. If it is not registered in the extraction source content of the name information table 132, the process proceeds to step S114.

Subsequently, when the deleted content 110 is registered in the extraction source content of the name information table 132 in step S110, the content analysis unit 120 deletes the deleted content 110 as the extraction source content in step S111. It is checked whether there is any other content referring to the domain name, and if it is referred from other content, the process proceeds to step S112. If no other content is referenced, the process proceeds to step S113.
For example, when the content 110-3 is deleted, the content 110-1 or 110-2 which is other content refers to the domain name referred to by the deleted content 110-3. If the content 110-1 or 110-2, which is another content, is not referred to, the process proceeds to step S113.

  Subsequently, in step S111, if the content analysis unit 120 refers to the domain name in which the deleted content 110 is registered as the source content, other content refers to the deleted content in step S112. 110 is deleted from the content extracted from the name information table 132.

  In step S111, the content analysis unit 120 determines that the deleted content 110 is deleted in step S113 if no other content refers to the domain name in which the deleted content 110 is registered as the extraction source content. Deletes the domain name referenced by the name information table 132 from the registration.

  Subsequently, in step S114, the content analysis unit 120 confirms whether or not the update processing of the name information table 132 for all the deleted contents 110 is completed, and the processing for all the deleted contents 110 is completed. If yes, the process proceeds to step S115. If all the deleted contents 110 have not been processed, the process returns to step S110, and the deletion process of the deleted contents 110 from the name information table 132 is repeated.

  Subsequently, in step S115, the content analysis unit 120 confirms whether or not the processing for all the contents in which the content management table 131 indicates “deleted” is completed, and the processing for all the contents is completed. If so, the name information analysis process is completed. If processing for all the contents has not been completed, the process returns to step S109 to repeat the registration status confirmation of the deleted content 110 and the deletion processing from the name information table 132.

  As described above, linked domain names can be listed from the state of new creation, modification, deletion, or the like of the HTML file that is the content 110 of the own HTTP server 10. Further, the extraction status from the content 110 of the own HTTP server 10 can be managed based on the listed domain names.

  In step S102 of the present embodiment, for example, all other contents linked using the HTML file shown in FIG. 5 are extracted. However, the contents 110 are linked to the HTML file of the contents 110. By recording access analysis and access records for other contents in advance, it is possible to extract only information of other contents that have been accessed more than the predetermined number of times or the order of the most frequently accessed times. As a result, it is possible to perform only processing for another content that is actually frequently accessed, so that the efficiency of name information analysis processing can be increased.

Next, in the content server system 100 according to the present embodiment, a processing procedure performed by the HTTP server 10 for performing the name resolution processing for the content 110 subjected to the name information analysis processing and the association processing for another content will be described. . FIG. 8 is a flowchart showing a processing procedure in which the name resolution unit 140 performs name resolution of the content 110 and association with another content.
FIG. 9 shows an example of the name information table 132 obtained by analyzing the name information. The name information table 132 shown in FIG. 9 is a file whose name information analysis processing is completed with respect to the name information table 132 shown in FIG.

The name resolution and the process of associating with another content in this embodiment are based on the registered content management table 131 shown in FIG. 4 and the name information table 132 obtained by analyzing the previous information shown in FIG. A case where processing is performed will be described. In FIG. 9, all domain names are subject to name resolution since the expiration date of all domain names is “current time”.
Note that the name resolution and the association with another content in the present embodiment are processes performed periodically or when the name information table 132 is updated.

  First, in step S201, the name resolution unit 140 determines whether there is a domain name whose expiration date in the updated name information table 132 is a time (including the current time) before the current time. If there is a domain name whose expiration date is earlier than the current time (including the current time), the process proceeds to step S202. If there is no domain name whose expiration date is earlier than the current time (including the current time), the process proceeds to step S207.

  Subsequently, in step S202, the name resolution unit 140 outputs, to the content communication unit 150, a request for name information for a domain name whose expiration date is before the current time (including the current time). . In response to the name information request from the name resolution unit 140, the content communication unit 150 inquires the name response unit 21 of the DNS server 20 via the network 40 for the name information, and sends the obtained name information to the name resolution unit 140. Output.

Subsequently, in step S203, the name resolution unit 140 determines whether the requested name information has been obtained. If the requested name information cannot be obtained, the process proceeds to step S204. If the requested name information is obtained, the process proceeds to step S205.
Note that whether or not the requested name information has been obtained can be determined based on a single inquiry result, but can also be determined based on a plurality of inquiry results.

  Subsequently, if the requested name information cannot be obtained in step S203, the name resolution unit 140 invalidates the IP address corresponding to the domain for which the requested name information was not obtained in step S204, and sets the expiration date. Set to a predetermined value.

  Subsequently, if the requested name information is obtained in step S203, and if the IP address and the expiration date are set in step S204, the name resolution unit 140 performs processing in step S205. For the name, the name information obtained from the content communication unit 150, the IP address information set in step S204, and the expiration date information are registered in the name information table 132.

  Subsequently, in step S206, the name resolution unit 140 confirms whether or not the registration processing of the IP address information and the expiration date information is completed in the name information table 132 for all domain names, and the name If all the domain names recorded in the information table 132 have been processed, the process proceeds to step S207. If all the domain names recorded in the name information table 132 have not been processed, the process returns to step S202, and the name information is inquired, and the name information including the IP address information and the expiration date information. The registration process to the table 132 is repeated.

  FIG. 10 shows an example of the name information table 132 whose name has been resolved. The name information table 132 shown in FIG. 10 is a file in which IP addresses related to domain names listed in the name information table 132 shown in FIG. 9 are registered and the expiration date is updated. In FIG. 10, domain names (“www.example.com”, “www.abc.com”, and “www.def.co.jp”) are obtained in step S203 when the requested name information is obtained. The IP address is registered and the expiration date is updated. The domain name (“www.ddd.co.jp”) is determined in advance at the expiration date because the requested name information is not obtained in step S203 and the IP address is invalidated in step S204. Value (current time + 1800 (seconds)) is registered.

  Subsequently, in step S207, the name resolution unit 140 confirms whether or not there is a content in which the content management table 131 indicates “new creation / modification”, and the content management table 131 displays “new creation / modification”. If there is a state indicating “correction”, the process proceeds to step S208. If there is no state indicating “new creation / correction” in the content management table 131, the process advances to step S217.

  Subsequently, in step S208, the name resolution unit 140 selects a content information table 133-1 (index-nameinfo) corresponding to the content 110 indicating “newly created / modified” in the content management table 131, for example, the content 110-1. Initialization, that is, the contents of the name information file 133-1 are deleted. If the name information file 133-1 corresponding to the content 110-1 does not exist, a new name information file 133-1 is created.

  Subsequently, in step S209, the name resolution unit 140 registers the domain name referred to by the content 100-1 corresponding to the name information file 133-1 in the name information table 132 and completes the name resolution. That is, if the IP address corresponding to the corresponding domain name in the name information table 132 is registered, the process proceeds to step S210. If no IP address corresponding to the corresponding domain name in the name information table 132 is registered, the process proceeds to step S211.

  Subsequently, in step S210, the name resolution unit 140 adds the corresponding domain name in the name information table 132, the IP address corresponding to the domain name, and the expiration date of the domain name to the name information file 133-1.

  FIG. 11 shows an example of the name information file 133-1 (index-nameinfo). In FIG. 11, the name information file 133-1 includes information on an IP address and an expiration date related to the domain names (“www.example.com” and “www.abc.com”) referred to by the corresponding content 110-1. It is an included file.

  Subsequently, in step S211, the name resolution unit 140 confirms whether or not the processing for all contents in which the content management table 131 indicates “new creation / correction” has been completed, and for all contents. When the process is completed, the process proceeds to step S212. If the processing for all contents has not been completed, the process returns to step S209, and the process of adding the domain name, IP address, and expiration date to the name information file 133 is repeated.

  FIG. 12 shows an example of the name information file 133-2 (index2-nameinfo). In FIG. 12, the name information file 133-2 includes an IP address and an expiration date related to the domain names (“www.example.com” and “www.def.co.jp”) referenced by the corresponding content 110-2. A file that contains information. Note that the domain name (“www.ddd.co.jp”) referred to by the content 110-2 is not recorded in the name information file 133-2 because the requested name information was not obtained in step S203.

  Subsequently, in step S212, the name resolution unit 140 checks whether there is information (domain name, IP address, expiration date) added to any name information file 133, and any name information file If information is added to 133, the process proceeds to step S213. If no information is added to any name information file 133, the process proceeds to step S215.

  Subsequently, when information is added to any of the name information files 133 in step S212, the name resolution unit 140 adds a link to the name information file 133-1 corresponding to the content 110-1 in step S213. create. For example, in the example of an HTML file representing an expression referring to another content included in the content 110-1 shown in FIG. 13, the meta tag (line c in FIG. 13) showing the link to the name information file 133 is shown. The link information related to the name information file 133-1 (index-nameinfo) is added.

  In addition, when the link information regarding the name information file 133 is already registered in the HTML file, the link information regarding the name information file 133 is overwritten by adding the link information regarding the name information file 133 in the HTML file. If link information related to the name information file 133 is not registered, link information related to the current name information file 133 is newly created.

  Note that the link information related to the name information file 133 can be added by, for example, a method described using a meta tag in the HEAD area of the HTML file shown in FIG. 13, or a method described as a comment in another arbitrary location. However, the present invention is not limited to this, and any method can be applied as long as the client machine 30 that acquired the content 110-1 can determine that the corresponding name information file 133 exists. Can do.

Subsequently, in step S214, the name resolution unit 140 registers the name information file 133-1 in the information related to the content 110-1 in the content management table 131, and changes the status related to the content 110-1 in the content management table 131. Initialization proceeds to step S219.
The name information file 133 is registered in the content management table 131. If the name information file 133 is already registered in the content management table 131, the current name information file 133 is overwritten and registered. If the name information file 133 is not registered, the current name information file 133 is newly registered.

If no information is added to any name information file 133 in step S212, the name resolution unit 140 deletes the link to the name information file 133 corresponding to the content 110 in step S215. For example, when the content 110-3 is deleted, the link related to the corresponding name information file 133-3 (index3-nameinfo) is deleted.
The link information related to the name information file 133 is deleted when the link information related to the name information file 133 is already registered in the HTML file, the link information related to the current name information file 133 is deleted and stored in the HTML file. If link information related to the name information file 133 is not registered, nothing is done.

Subsequently, in step S216, the name resolution unit 140 deletes the registration of the name information file 133 from the information regarding the content 110 in the content management table 131, initializes the state regarding the content 110 in the content management table 131, The process proceeds to S219. For example, when the content 110-3 is deleted, the registration of the name information file 133-3 (index3-nameinfo) corresponding to the content 110-3 is deleted.
Note that the registration of the name information file 133 in the content management table 131 is performed by deleting the registration of the current name information file 133 when the name information file 133 is already registered in the content management table 131. If the name information file 133 is not registered in the management table 131, nothing is done.

  In step S207, if the content management table 131 does not indicate “newly created / modified”, the name resolution unit 140 indicates that the content management table 131 indicates “deleted” in step S217. It is confirmed whether or not there is content, and if there is a state indicating “deleted” in the content management table 131, the process proceeds to step S218. If the content management table 131 does not indicate “delete”, the process advances to step S219.

  Subsequently, in step S218, the name resolution unit 140 deletes the name information file 133 of the deleted content 110, deletes the information of the content 110 in the content management table 131, and proceeds to step S219.

  Subsequently, in step S219, the name resolution unit 140 checks whether or not the processing for all contents whose state of the content management table 131 has been updated is completed. Complete the process of resolving and associating with another content. If processing for all contents has not been completed, the process returns to step S207 to create the name information file 133 corresponding to the content 110 whose state in the content management table 131 has been updated, and the content 110 and name information file. The process of 133 is repeated.

FIG. 14 shows an example of the content management table 131 whose name has been resolved. The content management table 131 shown in FIG. 14 has a name information file 133-1 (index-nameinfo) corresponding to the content 110-1 (index.html) in step S214 compared to the content management table 131 shown in FIG. Is newly registered, and the name information file 133-2 (index2-nameinfo) corresponding to the content 110-2 (index2.html) has already been registered in the content management table 131 shown in FIG. Therefore, the name information file 133-2 created this time has been updated.
On the other hand, the name information file 133-3 (index3-nameinfo) corresponding to the content 110-3 (index3.html) is deleted by step S216.
It also indicates that the state of all content has been initialized.

  As described above, name resolution of the content 110 held by the own HTTP server 10 is performed, and the association with other contents referred to by the content 110 held by the own HTTP server 10 is managed by the name information file 133. Can do.

  In step S202 of the present embodiment, the name information request for the domain name is not performed by sequentially requesting name information for each domain name, but a plurality of domain names are collectively resolved. In other words, when considering the DNS server 20 having a tree-type structure, the domain name having the same upper domain name that is likely to be processed by the same DNS server 20 is collected and a request for name resolution is made. It can also be done. For example, the domain names (“www.example.com” and “www.abc.com”) having the same upper domain name from all the domain names that perform name resolution on the domain name shown in FIG. ) To make a name resolution request. Also, domain names (“www.def.co.jp” and “www.ddd.co.jp”) having the same upper domain name “.co.jp” are put together and a name resolution request is made. As a result, the efficiency of name information inquiries made to the DNS server 20 can be improved.

If a plurality of IP addresses are included in the name information corresponding to the domain name obtained in step S202 of this embodiment, all the IP addresses are registered in the name information table 132. In step S210, for a domain name in which a plurality of IP addresses are registered in the name information table 132, the IP address randomly selected when adding the IP address corresponding to the domain name to the name information file 133 Can be added to the name information file 133. In this way, by randomly adding an IP address to the name information file 133, when another content is referenced from the content 110 of the HTTP server 10, the access load is distributed to another content server. It can be controlled on the HTTP server 10 side.
All the IP addresses can be added to the name information file 133. In this case, the client machine 30 controls the distribution of the access load with respect to another content server.

Next, a processing procedure for acquiring content performed by the client machine 30 in the content server system 100 according to the present embodiment will be described. FIG. 15 is a flowchart illustrating a processing procedure for the client machine 30 to acquire the content 110.
Note that the case where the client machine 30 in the present embodiment acquires the content 110-1 including the HTML file shown in FIG. 13 in the HTTP server 10 will be described.

First, in step S301, the control unit (not shown) of the client machine 30 confirms whether there is a request for content, for example, the content 110-1 of the HTTP server 10, from the user, and there is a request for the content 110-1. If so, the process proceeds to step S302. If there is no request for the content 110-1, the processing for acquiring the content is completed.
The request for the content 110-1 from the user is, for example, the location of the requested content 110-1 via the interface (not shown) of the client machine 30 to application software such as a web browser that displays the requested content 110-1. This is done by inputting an address indicating.

  Subsequently, in step S <b> 302, the control unit (not illustrated) of the client machine 30 determines whether name information corresponding to the requested domain name of the content 110-1 is registered in the name information cache 320 in the client machine 30. If the name information corresponding to the requested content 110-1 is registered in the name information cache 320, the process proceeds to step S304. If the name information corresponding to the requested content 110-1 is not registered in the name information cache 320, the control unit (not shown) of the client machine 30 outputs a request for name information to the client communication unit 330, and the step The process proceeds to S303.

  Subsequently, in step S303, the client communication unit 330 makes an inquiry about name information to the name response unit 21 of the DNS server 20 via the network 40 in accordance with a name information request from a control unit (not shown) of the client machine 30. The obtained name information (IP address) is registered in the name information cache 320.

Subsequently, in step S304, the control unit (not shown) of the client machine 30 issues an acquisition request for the content 110-1 from the HTTP server 10 to the client based on the name information (IP address) registered in the name information cache 320. Output to the communication unit 330.
Further, the client communication unit 330 requests the content 110-1 from the HTTP server 10 via the network 40 in accordance with a request for name information from a control unit (not shown) of the client machine 30, and acquires the content 110- acquired from the HTTP server 10. 1 is presented to the user of the client machine 30 via an interface (not shown) and is output to the name resolution unit 310.

  Subsequently, in step S305, the name resolution unit 310 includes link information to the name information file 133-1 in the content 110-1 acquired from the HTTP server 10, for example, the meta tag (FIG. 13). (c line) confirms whether or not the name information file 133-1 (index-nameinfo) is included, and if the link information to the name information file 133-1 is included, the name information file 133-1 Is output to the client communication unit 330, and the process proceeds to step S306. If the link information to the name information file 133-1 is not included, the processing for acquiring the content 110-1 is completed.

  Subsequently, in step S306, the client communication unit 330 requests the name information file 133-1 from the HTTP server 10 via the network 40 in accordance with the request for the name information file 133-1 from the name resolution unit 310, and the HTTP server. 10 to obtain the name information file 133-1.

Subsequently, in step S307, the client communication unit 330 registers the domain name, IP address, and expiration date included in the acquired name information file 133-1 in the name information cache 320 and completes the process.
If the previous information cache 320 contains already registered information, it can be overwritten with the information contained in the name information file 133-1. Also, the information contained in the name information file 133-1 is not overwritten, but both information can be registered and used separately when accessing the content server next time.

If the name information file 133-1 includes a plurality of IP addresses, only one IP address can be registered in the name information cache 320. Also, all IP addresses can be registered in the name information cache 320.
When a user requests content having a domain name in which a plurality of IP addresses are registered in the name information cache 320, by randomly selecting an IP address, the access load on the content server can be distributed. The client machine 30 can control.

As described above, when the content 110-1 including the link information to the name information file 133-1 is acquired, the name information file 133-1 is separately acquired and stored in the name information cache 320. By registering, when the client machine 30 requests another content, it is possible to request another content without performing name resolution again.
That is, the name information included in the name information file 133-1 linked to the content 110-1 is a content that is frequently accessed from the content 110-1 by reading a hyperlink or an image, or the like. Name information that is likely to have been accessed more than a given number of times, and was requested more quickly by reducing name resolution processing when actually accessing these other content Different content can be provided to the user.

Next, a communication procedure performed in the content server system 100 of this embodiment will be described. FIG. 16 is a diagram showing a content communication procedure in the content server system 100.
Note that the case where the client machine 30 in the present embodiment acquires the content 110-1 including the HTML file shown in FIG. 13 from the HTTP server 10 will be described.

  First, in the process 1, the HTTP server 10 communicates with the DNS server 20 to perform name resolution processing of the content server 2 referred to by the content 110 held by the HTTP server 10 itself in advance. Register information. A name information file corresponding to the content 110 is created and associated with the content 110.

Subsequently, when a request for the content 110-1 of the HTTP server 10 is generated from a user of the client machine 30, in a process 2, the client machine 30 communicates with the DNS server 20 to perform name resolution processing for the HTTP server 10. Do.
Subsequently, in process 3, the client machine 30 acquires the content 110-1 from the HTTP server 10 and presents it to the user of the client machine 30.
Subsequently, in the process 4, the client machine 30 acquires the name information file 133-1 from the HTTP server 10 based on the link information to the name information file 133 included in the content 110-1, and the name information cache 320 is obtained. Register with.

  Subsequently, when a request for another content held by the content server 2 referred to by the content 110-1 of the HTTP server 10 is generated from a user of the client machine 30, the client machine 30 performs name resolution processing in processing 5. Instead, the content is acquired from the content server 2 and presented to the user of the client machine 30.

  As described above, by acquiring the name information file 133-1 and registering the name information of the content server 2 in advance, the content of the content server 2 is acquired without performing name resolution processing, and the client machine Therefore, the user of the client machine 30 can experience an improvement in communication speed.

Even when the number of client machines 30 increases, the name resolution process performed in the content server system 100 is performed for the name resolution process from the HTTP server 10 and the HTTP server 10 performed first from the client machine 30. Since only the name resolution process is performed, the communication load on the DNS server 20 can be reduced.
Further, the communication load on the DNS server 20 can be reduced regardless of the position where the client machine 30 on the network 40 is connected.

Second Embodiment
The content server system according to the second embodiment of the present invention will be described below. The configuration of the content server system in the second embodiment is the same as the configuration of the content server system of the first embodiment shown in FIG. 2, but the configuration after the name resolution processing performed by the HTTP server 10 is different. The process of associating with the content of the content is different.

  Next, in the content server system 100 according to the second embodiment, a processing procedure for performing name resolution processing for the content 110 that has been subjected to name information analysis processing and processing for associating with another content performed by the HTTP server 10. explain. FIG. 17 is a flowchart illustrating a processing procedure in which the name resolution unit 140 performs name resolution of the content 110 and association with another content.

In the second embodiment, the name resolution and the association with another content are performed by the registered content management table 131 shown in FIG. 4 and the name information table 132 obtained by analyzing the previous information shown in FIG. A case where processing is performed based on the above will be described. In the content server system 100 of the second embodiment, since the name information file 133 is not created, the contents registered in the name information file shown in FIG. 4 are not used. In FIG. 9, all domain names are subject to name resolution since the expiration date of all domain names is “current time”.
Note that the name resolution and the association with another content in the present embodiment are processes performed periodically or when the name information table 132 is updated.

First, in step S401 to step S406, the name resolution unit 140, as in the flowchart of FIG. 8 (step S201 to step S206), the name information inquiry and the name information of the IP address information and the expiration date information Registration processing to the table 132 is performed to obtain the name information table 132 shown in FIG.
Do.

  Subsequently, in step S407, the name resolution unit 140 confirms whether or not there is content in which the content management table 131 indicates “new creation / modification”, and the content management table 131 stores “new creation / revision”. If there is a state indicating “correction”, the process proceeds to step S408. If there is no state indicating “new creation / correction” in the content management table 131, the process advances to step S413.

  Subsequently, the name resolution unit 140, in step S408, refers to the content 110 indicating “new creation / correction” in the content management table 131, for example, the other content included in the content 110-1 illustrated in FIG. In the example of the HTML file representing, the link information related to the name information file 133-1 (index-nameinfo) indicated by the meta tag (line c in FIG. 13) indicating the link to the name information file 133 is initialized. . That is, if there is a description of the meta tag in the HTML file, the description is deleted, and if there is no description of the meta tag, nothing is done.

  Subsequently, in step S409, the name resolution unit 140 registers the domain name referred to by the content 100-1 corresponding to the name information file 133-1 in the name information table 132 and completes the name resolution. That is, if the IP address corresponding to the corresponding domain name in the name information table 132 is registered, the process proceeds to step S410. If the IP address corresponding to the corresponding domain name in the name information table 132 is not registered, the process proceeds to step S411.

  Subsequently, in step S410, the name resolution unit 140 adds name information including the corresponding domain name in the name information table 132, the IP address corresponding to the domain name, and the expiration date of the domain name to the content 110-1. To do. For example, in the example of the HTML file describing the name information of other content included in the content 110-1 shown in FIG. 18, a meta tag is used in the HEAD area, and the name of domain name = “www.example.com” is used. A meta tag indicating information (line d in FIG. 18) and a meta tag indicating name information of domain name = “www.abc.com” (line e in FIG. 18) are added.

  Subsequently, in step S411, the name resolution unit 140 confirms whether or not the processing for all the contents in which the content management table 131 indicates “new creation / correction” has been completed, and for all the contents. When the process is completed, the process proceeds to step S412. If processing for all the contents has not been completed, the process returns to step S409 to repeat additional processing for the domain name, IP address, and expiration date for the content 110.

  Subsequently, in step S412, the name resolution unit 140 initializes the state relating to the content 110 in the content management table 131, and proceeds to step S415.

  If the content management table 131 does not indicate “newly created / modified” in step S407, the name resolution unit 140 indicates that the content management table 131 indicates “deleted” in step S413. It is confirmed whether or not there is content, and if there is a state indicating “delete” in the content management table 131, the process proceeds to step S414. If the content management table 131 does not indicate “delete”, the process advances to step S415.

  Subsequently, in step S414, the name resolution unit 140 deletes the information on the deleted content 110 from the content management table 131, and the process proceeds to step S415.

  Subsequently, in step S415, the name resolution unit 140 checks whether or not the processing for all contents whose state of the content management table 131 has been updated is completed. Complete the process of resolving and associating with another content. If the processing for all the contents is not completed, the process returns to step S407, and the process of associating the name information with the content 110 whose state of the content management table 131 is updated is repeated.

  FIG. 19 shows an example of the content management table 131 whose name has been resolved. The content management table 131 illustrated in FIG. 19 indicates that the state of all the contents is initialized with respect to the content management table 131 illustrated in FIG.

  As described above, the name resolution of the content 110 held by the own HTTP server 10 is performed, and name information is added to the content 110, whereby another content referred to by the content 110 held by the own HTTP server 10 is referred to. Can be managed.

Next, a processing procedure for acquiring content performed by the client machine 30 in the content server system 100 according to the second embodiment will be described. FIG. 20 is a flowchart showing a processing procedure for the client machine 30 to acquire the content 110.
Note that the case where the client machine 30 in the second embodiment acquires the content 110-1 including the HTML file shown in FIG. 18 from the HTTP server 10 will be described.

First, the control unit (not shown) of the client machine 30 and the client communication unit 330 acquire the content 110-1 from the HTTP server 10 in steps S501 to S504, as in the flowchart of FIG. 15 (steps S301 to S304). Then, the information is presented to the user of the client machine 30 via an interface (not shown) and output to the name resolution unit 310.
Do.

  Subsequently, in step S505, the name resolution unit 310 adds the domain information to the name information, for example, the meta tag shown in FIG. 18 (d line and e line in FIG. 18) in the content 110-1 acquired from the HTTP server 10. Whether name information including a name, an IP address corresponding to the domain name, and an expiration date of the domain name is included is checked. If name information is included, the process proceeds to step S506. If the name information is not included, the processing for acquiring the content 110-1 is completed.

Subsequently, in step S506, the client communication unit 330 registers the domain name, IP address, and expiration date included in the content 110-1 in the name information cache 320 and completes the process.
If the previous information cache 320 contains already registered information, it can be overwritten with the information contained in the name information file 133-1. Also, the information contained in the name information file 133-1 is not overwritten, but both information can be registered and used separately when accessing the content server next time.

As described above, when the content 110-1 including the name information is acquired, by registering the name information obtained from the content 110-1 in the name information cache 320, the client machine 30 When requesting another content, it is possible to request another content without performing name resolution again.
As a result, the number of name information inquiries to the DNS server 20 is not related to the number of contents requested from the client machine 30 connected to the network 40. That is, the name resolution processing is performed only when content is first requested from the client machine 30 and when the content held by the HTTP server 10 is changed.
As a result, access to the DNS server 20 can be reduced, and the load on the DNS server 20 can be reduced.

  Further, the client machine 30 can present the requested content to the user only in the time for acquiring the actually requested content when the user requests the content.

Next, a communication procedure performed in the content server system 100 according to the second embodiment will be described. FIG. 21 is a diagram showing a content communication procedure in the content server system 100.
Note that the case where the client machine 30 in the second embodiment acquires the content 110-1 including the HTML file shown in FIG. 18 in the HTTP server 10 will be described.

  First, in the process 1, the HTTP server 10 communicates with the DNS server 20 to perform name resolution processing of the content server 2 referred to by the content 110 held by the HTTP server 10 itself in advance. Register information. In addition, name information is added to the content 110.

Subsequently, when a request for the content 110-1 of the HTTP server 10 is generated from a user of the client machine 30, in a process 2, the client machine 30 communicates with the DNS server 20 to perform name resolution processing for the HTTP server 10. Do.
Subsequently, in process 3, the client machine 30 acquires the content 110-1 from the HTTP server 10 and presents it to the user of the client machine 30. Further, the client machine 30 registers the name information included in the content 110-1 in the name information cache 320.

  Subsequently, when a request for another content held by the content server 2 referred to by the content 110-1 of the HTTP server 10 is generated from a user of the client machine 30, the client machine 30 performs name resolution processing in processing 4. Instead, the content is acquired from the content server 2 and presented to the user of the client machine 30.

  As described above, by registering the name information of the content server 2 in the content 110-1 in advance, the content of the content server 2 is acquired without performing name resolution processing, and the user of the client machine 30 is notified. Since it can be presented, the user of the client machine 30 can experience an improvement in communication speed.

Even when the number of client machines 30 increases, the name resolution process performed in the content server system 100 is performed for the name resolution process from the HTTP server 10 and the HTTP server 10 performed first from the client machine 30. Since only the name resolution process is performed, the communication load on the DNS server 20 can be reduced.
Further, the communication load on the DNS server 20 can be reduced regardless of the position where the client machine 30 on the network 40 is connected.

  Further, since the client machine 30 can acquire the name information at the same time as acquiring the content 110-1, the amount of data to be acquired increases, but the network 40 by each device performed in the content server system 100. An increase in the number of accesses (sessions) can be prevented.

  As described above, according to the best mode for carrying out the present invention, when a client machine acquires content, it is possible to acquire name information related to another content referred to by the acquired content. . This can reduce the name resolution processing that is performed when acquiring the content of another content server referenced by the acquired content. Can be provided to users.

  Further, by reducing the name resolution processing, it is possible to reduce access to the DNS server, and even when the number of client machines connected to the network of the content server system of this embodiment increases, Since the name information possessed can be used, the communication load of the DNS server 20 can be reduced.

The present invention is effective for a content server system that sequentially accesses HTTP servers referred to by content as shown in the embodiment.
In addition, the search server or the like is particularly effective when the search result content (HTML) includes reference information for a plurality of domains.

  In the present embodiment, the prefetch access for performing the content server name resolution in advance and the method using the cache server for holding the content acquired by the prefetch access are not used. By using prefetch access and a cache server in the system, the content can be presented to the user even faster.

  In addition, as for the association between the name information and the content in the present embodiment, an example in which the link information indicating that the name information file exists or the description similar to the name information file is added in the content is shown. In addition to presenting information in an embedded form, a method of presenting a name information file as a related file simultaneously with the presentation of content may be used.

  The embodiment of the present invention has been described above with reference to the drawings. However, the specific configuration is not limited to this embodiment, and includes various modifications within the scope of the present invention. It is.

It is the block diagram which showed the example of the whole structure of the content server system by embodiment of this invention. It is the block diagram which showed the structure of the content server system in the 1st Embodiment of this invention. It is the flowchart which showed the process sequence which analyzes name information in the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the content management table registered into the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the HTML file showing the expression which refers to the other content contained in the content of the 1st Embodiment of this invention. It is the figure which showed an example of the name information table registered into the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the name information table by which name information was analyzed in the content server of the 1st Embodiment of this invention. It is the flowchart which showed the process sequence which performs name resolution and the correlation with another content in the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the name information table by which name information was analyzed in the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the name information table by which name resolution was carried out in the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the name information file produced in the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the name information file produced in the content server of the 1st Embodiment of this invention. It is the figure which showed an example of the HTML file showing the expression which refers to the other content contained in the content of the 1st Embodiment of this invention. It is the figure which showed an example of the content management table by which name resolution was carried out in the content server of the 1st Embodiment of this invention. It is the flowchart which showed the process sequence which performs content acquisition and name resolution in the client machine of the 1st Embodiment of this invention. It is the figure which showed the communication procedure of the content in the content server system in the 1st Embodiment of this invention. It is the flowchart which showed the process sequence which performs name resolution and the correlation with another content in the content server of the 2nd Embodiment of this invention. It is the figure which showed an example of the HTML file which described the name information of the other content contained in the content of the 2nd Embodiment of this invention. It is the figure which showed an example of the content management table by which name resolution was carried out in the content server of the 2nd Embodiment of this invention. It is the flowchart which showed the process sequence which performs content acquisition and name resolution in the client machine of the 2nd Embodiment of this invention. It is the figure which showed the communication procedure of the content in the content server system in the 2nd Embodiment of this invention. It is the figure which showed the communication procedure of the content using the conventional DNS server. It is the figure which showed the communication procedure of the content by the prefetch using the conventional DNS server. It is the figure which showed the communication procedure of the content by the cache server using the conventional DNS server.

Explanation of symbols

1,100 content server system 10-1, 10-2, 10-3 content server 20, 20-1, 20-2 DNS server 30, 30-1, 30-2, 30-3 client machine 40 network 10 HTTP server 110, 110-1, 110-2, 110-3 Content 120 Content analysis unit (content analysis unit) 130 Name information database (name information storage unit) 131 Content management table 132 Name information table 133, 133-1, 133-2 , 133-3 Name information file 140 Name resolution unit (name resolution unit) 150 Content communication unit 21 Name response unit 310 Name resolution unit 320 Name information cache (name information cache unit) 330 Client communication unit

Claims (8)

One or more content servers that provide content, one or more client computers that use the provided content, the content server, and name information that associates domain names and IP addresses of the client computers In a content server system in which one or more DNS servers that are connected to a network are
The content server
Content analysis means for identifying another content server that provides the second content referred to by the first content based on the first content owned by the device;
Name resolution means for obtaining name information of the other content server identified by the content analysis means from the DNS server;
Name information storage means for storing the first content and the name information of the other content server acquired by the name resolution means in association with each other;
The first of the client computer that requested the transmission of the content, and the first content, and a content transmission unit configured to send said name information of the other contents server stored in the name information storing means,
With
The client computer is
Name information cache means for storing the name information of the other content server received from the content server;
When using the second content referred to by the first content received from the content server, based on the name information of the other content server stored in the name information cache means, the other content Content request means for requesting the second content from a content server;
A content server system comprising: The content transmission means includes
Sends the link information indicating that the name information of the other contents server to the name information storage means is stored,
The content request means includes
Based on the previous SL link information received from the content server to request transmission of the name information stored in the contents server,
The content server system according to claim 1. The content transmission means includes
Transmitting the name information of the other content server stored in the name information storage means together with the first content ;
The content server system according to claim 1. In a content server connected to a network and providing content,
Content analysis means for identifying another content server that provides the second content referred to by the first content based on the first content owned by the device;
The name acquired from the DNS server that stores the name information associated with the domain name and IP address of the content server and the client computer that uses the provided content, as the name information of the other content server specified by the content analysis means A solution,
Name information storage means for storing the first content and the name information of the other content server acquired by the name resolution means in association with each other;
The first of the client computer that requested the transmission of the content, and the first content, and a content transmission unit configured to send said name information of the other contents server stored in the name information storing means,
A content server comprising: The content transmission means includes
Name information of the other content server to send link information indicating that it is stored in the name information storing means,
The content server according to claim 4. The content transmission means includes
Transmitting the name information of the other content server stored in the name information storage means together with the first content ;
The content server according to claim 4. In a client computer connected to a network and using content provided from a content server,
Name information cache means for storing name information of other content servers that provide the second content referred to by the first content of the content server itself received from the content server;
When using the second content referred to by the first content received from the content server, based on the name information of the other content server stored in the name information cache means, the other content Content request means for requesting the second content from a content server;
Equipped with a,
The content request means includes
Requesting transmission of the name information stored in the content server based on link information indicating that the name information is stored in the content server received from the content server;
A client computer characterized by that. In a client computer connected to a network and using content provided from a content server,
Name information cache means for storing name information of other content servers that provide the second content referred to by the first content of the content server itself received from the content server;
When using the second content referred to by the first content received from the content server, based on the name information of the other content server stored in the name information cache means, the other content Content request means for requesting the second content from a content server;
With
The content request means includes
Storing pre Symbol name information received together with the first content from the content server to the name information cache unit,
Features and be torque client computer that.

Images