JP2001265693A - Load control system in web - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a system for enabling effective traffic control. SOLUTION: A web server system 100 in WWW is provided with a load measuring function 131 for judging the load condition of the web server system, an arranging ticket issuing function 132 for acquiring arranging number data from a prescribed storage area and generating and issuing arranging ticket data to which a series of arranging numbers are attached for respective processing requests from a web browser system, an arranging ticket confirming function 133 for acquiring the arranging ticket data from the web browser system and judging whether or not it is a receivable arranging ticket and a job processing function 135 for performing a prescribed processing requested from the web browser system in the case of the receivable arranging ticket.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a Web load control system for effectively controlling Web traffic using a Web server system and a Web browser system in a WWW system.

[0002]

2. Description of the Related Art Conventionally, the WWW (World Wide Web)
In the traffic control system that manages traffic in the (Web), if the website is crowded,
Traffic control has been performed such that access is accepted even if response is delayed, or access is rejected to suppress an increase in traffic.

[0003]

Further, in the event of congestion, a user can have a means for grasping how many queues his / her own access is waiting for, or how long to wait before turning. Had not been provided. As a result, there was a high possibility that the convenience of the congested Web server would be reduced or that traffic would be further deteriorated due to retries.

[0004] The present invention solves the problems of the conventional traffic control system as described above, and provides a system that enables more effective traffic control. It is an object of the present invention to provide a web traffic control system that can provide a user with information on the degree of congestion and the waiting time in such a case. Another object of the present invention is to provide, as another method, a traffic control system for the Web that can control traffic according to the access order when the Web site is crowded.

[0005]

In order to solve the above-mentioned problems, a Web server system according to claim 1 has a function of determining a load state of a Web server system in a Web server system in WWW, and a result of determining the load state. A function of acquiring serial number data from a predetermined storage area for each processing request from the Web browser system, generating and issuing serial number data with a series of serial numbers,
A function to acquire numbered ticket data from the Web browser system and determine whether it is an acceptable numbered ticket, and a function to perform predetermined processing requested from the Web browser system if the numbered ticket is acceptable. It is characterized by having.

According to a second aspect of the present invention, there is provided a URL for providing a function for generating and issuing the numbered ticket data to a Web browser system, and a numbered ticket which can acquire and accept the numbered ticket data from the Web browser system. The feature is that the URL for providing the function of determining whether or not to the Web browser system is different from the URL. The invention according to claim 3 is characterized in that the numbered ticket data is issued by a cookie that stores a numbered number and a password generated using a random number. The invention according to claim 4 requests the Web browser system, which has refused the use of the cookie, to input a user ID or an e-mail address and notifies the user of the reference number and a password generated using a random number by e-mail. It is characterized by:

According to a fifth aspect of the present invention, there is provided a Web browser system comprising:
In a WWW Web browser system, a function to save numbered ticket data consisting of data related to an access queue issued by a Web server system in a predetermined storage area, and to issue a desired processing request to the Web server system And a function of accessing the Web server system by attaching the obtained numbered ticket data.

According to a sixth aspect of the present invention, there is provided a Web load control system comprising the Web server system according to any one of the first to fourth aspects and a Web browser system according to the fifth aspect.

[0009] The invention described in claim 7 is the first invention.
6. A computer-readable recording medium that records a program executed in the system according to any one of 6.

[0010]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a block diagram showing the overall configuration of a traffic control system according to an embodiment of the present invention. The system according to the present embodiment includes three components: a web server system 100, a network 200, and a web browser system 300. The network 200 is a communication system such as a LAN (local area network) or the Internet, but the specific configuration is not particularly limited. Web browser system 3
00 may be one or more.

FIG. 2 shows the Web server system 1 shown in FIG.
FIG. 2 is a block diagram showing a system configuration of the system 00. In addition, what is necessary for a normal network, such as a firewall and a router, is omitted, and only those that are relevant in the description are described. The web server system 100 shown in FIG. 2 includes a plurality of http (HyperText Transfer P.) which are in charge of communication processing with the web browser systems 300, 300,.
(rotocol) The server 101, 101 and the Web that processes requests from the Web browser systems 300, 300,.
It comprises an application server 102 and a database server 103 as a storage location of data necessary for each process.

In the configuration of FIG. 2, the Web application server 102 is not used and the
A request from the Web browser system 300 can be processed by using a CGI (Common gateway interface) or the like. Also, without using the database server 103, the OS
A file system provided by the (operation system) can also be used. In FIG. 2, the optional database server 103 and Web application server 1
02 is shown surrounded by a wavy line. Also, http server 10
One or more units 101 may be provided.

Next, the system configuration of the Web browser system 300 shown in FIG. 1 will be described with reference to FIG. The components required for the ordinary network 200, such as routers, are omitted, and only components relevant to the description will be described.

The Web browser system 300 shown in FIG.
A Web browser 301, which is an application responsible for communication processing with the server system 100, screen display, and data input, and a URL (Uniform
Resource Locator), numbered ticket data 302 composed of data necessary for processing reference numbers and the like. The substance of the numbered ticket data 302 may be configured by using a "cookie" which is a file system provided by the Web browser 301 as a standard,
Add plug-in software to
The management may be performed using a file system provided by the OS.

Next, a functional configuration of the Web server system 100 shown in FIGS. 1 and 2 will be described with reference to FIG. The Web server system 100 shown in FIG. 4 has the following functions. For security functions that are generally required for the system and functions that are not required for explanation,
Omitted.

The functions include an http communication function 110, an integrated control function 120, a load measuring function 131, and a numbered ticket issuing function 13.
2, numbered ticket confirmation function 133, database function 140,
Message generation function 134 and business processing function 135
It is. The http communication function 110 is a function for realizing communication using the http protocol. The integrated control function 120 includes:
This function integrates each function to realize services as a Web server system. The load measurement function 131 is a function for determining the current load status of the entire Web server system 100. The numbered ticket issuing function 132 is provided in the database 1
This is a function of acquiring a serial number, which is a series of numbers, from 40 and generating numbered ticket data. The numbered ticket confirmation function 133 is
This function acquires numbered ticket data from the Web browser system 300 and determines whether the numbered ticket is acceptable. The database function 140 is a function for storing various data required for processing. The message generation function 134
This function is for generating a numbered ticket issued screen to be displayed on the Web browser system 300. And business processing function 1
Reference numeral 35 denotes a function corresponding to business processing such as order receiving processing.

Next, a functional configuration of the Web browser system 300 shown in FIGS. 1 and 3 will be described with reference to FIG. The Web browser system 300 shown in FIG. 5 has the following functions. In addition, the http communication function and html that the web browser system 300 itself has as standard equipment
(HyperText Markup Language) analysis, screen control, etc. are omitted, and Web browser standard functions 3
Explanation is made as 10.

The functions are the Web browser standard function 310, the integrated control function 320, the numbered ticket registration function 331,
A numbered ticket reference function 332 and a numbered ticket deletion function 333 are provided. The integrated control function 320 is a function for realizing a service as the Web browser system 300 by integrating each function. The numbered ticket registration function 331 is a function of saving numbered ticket data issued by the Web server system 100 in a file system. The numbered ticket reference function 332 is a function of referring to the numbered ticket data stored by the numbered ticket registration function 331 from the file system. The numbered ticket deletion function 333 is a function for deleting numbered ticket data from the file system in accordance with an instruction from the Web server system 100.

Next, processing in the Web server system 100 and the Web browser system 300 in FIG. 1 will be described with reference to FIG.

1. First, the processing of the Web server system 100 will be described.

1.1 Overall processing flow

In response to a request from the Web browser system 300, it is determined whether the request is a new request or a request with a numbered ticket (step 60 in FIG. 6).
2). If the request is a new request, the load status of the entire system is grasped using the load measurement function 131 (step 603 in FIG. 6). As a result, business processing is performed by the business processing function 135 only when it is determined that normal system operation is possible (step 604 in FIG. 6). On the other hand, if it is determined that the operation is impossible, the numbered ticket issuance function 132 performs a numbered ticket issuance process (step 605 in FIG. 6).

If the request is with a numbered ticket, the numbered ticket confirmation function 133 determines whether or not the numbered ticket should be processed based on the numbered number, the reservation time, and the like. After the priority is set higher (step 606 in FIG. 6), business processing is performed by the business processing function (step 604 in FIG. 6). If it is determined that the request is inappropriate, an appropriate message is generated using the message generation function for the request, and the process ends (step 607 in FIG. 6).

1.2 A method for determining whether a request is a new request or a request with a numbered ticket

In the Web system, there are several methods for adding data when sending a request, but any method may be used as long as the interface between the Web browser system 300 and the Web server system 100 matches. .

There are several methods for judging that a numbered ticket is attached, but any method may be used. For example, there is a method of determining that a numbered ticket is attached if the numbered number is attached.

1.3 Method of Determining Load Status of Entire System

The following data can be used to determine the load on the system. 2, the response time of the http server 101, the response time of the Web application server 102, and the response time of the database server 103. If these response times exceed a certain standard, it is determined that normal operation of the system is impossible. Note that the response time can be measured by using a logging function or the like provided as a standard in each server, but the description is omitted here.

1.4 How to issue a numbered ticket

The numbered ticket data is composed of the following element data. For example, a reference number, a URL of an http server for receiving a request based on a numbered ticket, a receivable time estimated based on a system load condition, and an expiration date.

1.4.1 Generation method of “reference number”

The serial number is generated by adding 1 to the previous serial number stored in the database 140. The database 140 is not necessarily required, and may be on a memory or various file systems.

1.4.2 Method of Generating URL of http Server to Accept Request Based on Numbered Ticket

This URL is used when the Web browser system 300 transmits a request with a numbered ticket. This U
The RL is different from the http server 101 that accepts a new request.
By setting the URL of the http server 101, the http server can be operated separately for a new case and a case with a numbered ticket, and effective load balancing can be realized particularly in a large-scale Web system. it can. This URL
May be the same as the URL of the http server that accepts the new request, but it is desirable to keep it separate.

1.4.3 Method of Generating Predicted Acceptable Time Based on System Load Status

There are mainly two methods for calculating the estimated acceptable time based on the load situation. One is a method of making predictions based on past results, and the other is a method of making predictions by performing simulations based on various data. To forecast based on past performance, investigate how long it takes to process a request and how it changes due to changes in load conditions from actual processing results By doing so, the relationship between the load situation and the unit processing time can be patterned and used as the predicted time.

If the unit processing time patterned for each load condition is known, the estimated acceptable reception time can be calculated by multiplying it by the number of requests waiting in the processing waiting state. The number of requests waiting in the processing waiting state is the sum of the following two types of requests.
The number of requests that actually make a request with a numbered ticket and are queued on the system, and the requests that have not yet been queued on the system but have been issued a numbered ticket and are waiting until the time Is the number of

When applying to actual processing, it is desirable to consider the probability that a numbered ticket has been issued but not actually accessed, etc., but the description thereof will be omitted.

Further, the above description is based on the http server 101 for receiving a request with a numbered ticket and the ht for receiving a new request.
Although the explanation has been made on the assumption that the tp server 101 is different, if these http servers are the same, the number of requests in the queue on the system needs to be calculated including new requests. . It is very difficult to predict how the new requirements will change, in which case the accuracy of the calculation results is expected to be significantly reduced. Therefore, it is desirable that the http server that receives a new request and the http server that receives a request with a numbered ticket be separated from the viewpoint of keeping the accuracy of prediction and from the viewpoint of load distribution.

Many studies have already been made on simulations, and the results of the simulations can be used to predict the possible processing time. Regarding the calculation method using the simulation technique, each document is referred to, and the description thereof is omitted.

1.5 How to determine if a numbered ticket is invalid

A numbered ticket, a reservation time set based on a prediction, an expiration date, and the like are set in the numbered ticket.
The following numbered tickets can clearly be judged invalid. A numbered ticket that has already been used and a numbered ticket that has expired. The extent to which the following numbered tickets are invalid depends on the system policy. -(1) Numbered tickets that have not reached the reservation time,
-(2) There is a case where there is an unprocessed number that is younger than the reference number.

2. Next, the processing of the Web browser system 300 will be described.

2.1 Overall Processing Flow

Using the numbered ticket reference function 332, it is confirmed whether there is a numbered ticket that has been acquired. If the numbered ticket has been acquired, the numbered ticket data is attached when transmitting the request to the Web server system (step 601 in FIG. 6). If the Web server system 100 determines that the transmitted numbered ticket is invalid, an error message is returned and displayed (step 608 in FIG. 6). When the business process is completed in the Web server system 100 (Step 604 in FIG. 6), the result of the business process is returned to the Web browser system 300. If the business process is based on a numbered ticket, the corresponding numbered ticket is deleted using the numbered ticket erasure function (step 610 in FIG. 6).

2.2 Numbered ticket registration function 331, numbered ticket reference function 332, numbered ticket deletion function 333

The file system for storing the numbered ticket data may be of any type (step 609 in FIG. 6). For example, a file system called "cookie" provided as standard by Web browser software may be used. A cookie is a file system created on the Web browser side in response to a request from the server, and is created only when the Web browser permits it by setting options. A cookie is created for each URL of the server, and each server can refer to, update, and delete only the cookies created by itself.

The cookie can be automatically deleted at the end of the communication or automatically after the expiration date. Text data can be recorded in cookies, and the format is arbitrary. One of the ways to access cookies easily is to use Javascript. Javascript is one of the scripting languages that can be embedded in ordinary html data.

The method of referring to the numbered ticket differs depending on the file system and the means for accessing the file system, and a description thereof will be omitted.

It should be noted that the numbered ticket data can be provided by using e-mail in addition to cookies. When issuing numbered ticket data using a cookie, by storing a password with a serial number and a random number in the cookie, it becomes possible to perform authentication processing for access to which the serial number is attached. For example, a user who has refused the use of a cookie is requested to input a user ID (identification code) or a mail address, and a web server system 100 is linked to a mail server to issue numbered ticket data using mail. To When using e-mail, the user is notified by e-mail of a reference number and a password using random numbers.

FIG. 7 is a system diagram showing a specific example of Web traffic control by issuing a numbered ticket in the present embodiment. Web server system 100a and mirror server 1
In the two web server systems 00b and 00b, the new reception URL (,) and the queue URL (,) are managed with different URLs, respectively, and have a common serial number by the common numbered ticket issuing function 132. Then, issue a numbered ticket and specify the URL for the queue so that the load is distributed among the server systems. In this case, the Web server 100a has four queues at the queue URL (), and the Web server 100b has the queue URL () at the 20th and 21st queues. () Has occurred. Therefore, numbered ticketing function 1
32 is the URL for the queue in the Web server 100b ()
And, in the Web browser system 300, "The numbered ticket has been issued due to congestion.
As there is a mirror site available, we took it there. Currently three customers are waiting. Your customer number is 22. It is expected to be available in about 10 minutes. We look forward to at http: //xxx.xx/xx/xxx/. "
Is transmitted so that the display is performed.

In the prior art, when the Web site is congested, the response must be accepted or rejected even if the response is delayed (see FIG. 9). On the other hand, according to the present embodiment, this situation can be improved by issuing a numbered ticket. For example, as shown in FIG. 8, it is possible to provide the user with information such as how many queues are in the queue, and how long to wait before turning. Then, if they become clear, for example, there is an effect that the service can be provided without missing the customer. In the example of Fig. 8, the URL for a new reception when congestion occurs
In addition to issuing the numbered ticket data in response to the access to the web browser, the display device of the Web browser system 300 displays the message "Notice from the system, we have issued a numbered ticket because it is very crowded.
Please press after 30. We will accept it immediately. "
Is displayed, and a link destination icon (“button”) for accessing by attaching the numbered ticket data to the queue URL (reference numeral 8 in FIG. 8).
01), the user can easily access a new URL.

A program for realizing the functions shown in FIGS. 4 and 5 is recorded on a computer-readable recording medium, and the program recorded on the recording medium is read by a computer system and executed. Construction management may be performed. Here, the “computer system” includes an OS and hardware such as peripheral devices.

The "computer system" is a WW
If the W system is used, a homepage providing environment (or display environment) is also included.

The "computer-readable recording medium" is a portable medium such as a floppy (registered trademark) disk, a magneto-optical disk, a ROM, a CD-ROM, or a storage device such as a hard disk built in a computer system. That means. Further, the “computer-readable recording medium” refers to a volatile memory (RAM) inside a computer system that becomes a server or a client when a program is transmitted through a network such as the Internet or a communication line such as a telephone line. And those holding programs for a certain period of time.

The above program may be transmitted from a computer system storing the program in a storage device or the like to another computer system via a transmission medium or by a transmission wave in the transmission medium. Here, the "transmission medium" for transmitting a program refers to a medium having a function of transmitting information, such as a network (communication network) such as the Internet or a communication line (communication line) such as a telephone line.

The above program may be a program for realizing a part of the functions described above. Furthermore, what can implement | achieve the function mentioned above in combination with the program already recorded on the computer system, and what is called a difference file (difference program) may be sufficient.

[0058]

According to the present invention, when a Web site is congested, information on the degree of congestion and the waiting time can be provided to the user.
Since traffic can be controlled, it is possible to perform more effective traffic control than before.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a Web system including a Web server system and a Web browser system according to the present invention.

FIG. 2 is a block diagram showing a configuration of a Web server system 100 of FIG.

FIG. 3 is a block diagram showing a configuration of a Web browser system 300 of FIG.

FIG. 4 is a block diagram showing a functional configuration of the Web server system 100 of FIG.

FIG. 5 is a block diagram showing a functional configuration of the Web browser system 300 of FIG.

FIG. 6 is a flowchart showing a processing procedure of the Web server system 100 and the Web browser system 300 of FIG. 1;

FIG. 7 is a system diagram showing a specific example of the process of FIG. 6;

FIG. 8 is a system diagram showing another specific example of the process of FIG. 6;

FIG. 9 is a system diagram showing traffic control processing in a conventional Web system.

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 Web server system 101 http server 102 Web application server 103 database server 131 load measurement (function) 132 numbered ticket issue (function) 133 numbered ticket confirmation (function) 134 message generation (function) 135 business process (function) 200 network 300 Web Browser system 301 Web browser 302 Numbered ticket data 331 Numbered ticket registration (function) 332 Numbered ticket reference (function) 333 Numbered ticket deletion (function)

Claims (7)

[Claims] In a Web server system in the WWW, a function of judging a load condition of a Web server system, and, in accordance with a result of the judgment of the load condition, for a processing request from a Web browser system, a serial number from a predetermined storage area A function that obtains data, generates and issues numbered ticket data with a series of serial numbers, a function that obtains numbered ticket data from a web browser system, and determines whether a numbered ticket is acceptable, and a function that accepts A web server system having a function of performing a predetermined process requested by the web browser system when the ticket is a simple numbered ticket. 2. A URL that provides a function of generating and issuing the numbered ticket data to a Web browser system;
2. The Web server according to claim 1, wherein a URL for obtaining the numbered ticket data from the browser system and providing a function for determining whether the numbered ticket is acceptable to the Web browser system is different from the URL. system. 3. The Web server system according to claim 1, wherein the numbered ticket data is issued by a cookie that stores a numbered number and a password generated by using a random number. 4. The Web browser system which rejects the use of the cookie is requested to input a user ID or an e-mail address, and is notified by e-mail of a serial number and a password generated by using a random number. The Web server system according to claim 3, wherein 5. A Web browser system in the WWW, a function of storing numbered ticket data consisting of data relating to an access queue issued by a Web server system in a predetermined storage area, and a request for a desired processing request to the Web server system. A web browser system having a function of accessing the web server system by attaching numbered ticket data issued at the time of performing. 6. The We according to claim 1, wherein
A web load control system, comprising: a b-server system; and the web browser system according to claim 5. 7. A computer-readable recording medium on which a program executed in the system according to claim 1 is recorded.