JP2006259783A - Web site waiting state management/display system, and waiting state management/display program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a waiting state management/display system for a Web site capable of inducing access waiting, and saving manual re-accessing. <P>SOLUTION: A guidance server 03 is provided for carrying out management of visitors, a waiting visitor DB 91 is provided for storing data of waiting visitors, a message DB 93 is provided for storing a guide note, an apology server 04 is connected to the message DB 93, and an update interval DB 92 is provided for storing an update time interval for updating an apology image plane. When a present access number is a Web server processing limit user number or more, the data of the waiting visitors is stored in the waiting visitor DB 91, the apology image plane including the guide note stored in the message DB 93 and the number of waiting visitors stored in the visitor DB 91 is sent to a user terminal, the waiting visitor DB 91 is referred to at every update time interval to update the visitor data, and the apology server updates the apology image plane on the basis of the updated visitor data. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a waiting state management / display system and a waiting state management / display program for a website via a network such as the Internet, and in particular, automatically guides a user to wait for access to the website and manually accesses the user. The present invention relates to a waiting state management / display system and a waiting state management / display program for a website that can be re-accessed by the system.

  In recent years, various contents such as a shopping / ticket reservation / information search service using a website have been provided with the spread of the Internet communication network. The website of the prior art is crowded with the users who access when the number of accesses exceeds the predetermined number because there is a possibility that the web server goes down when the user access is concentrated due to popularity. A process of notifying the user to make an access after waiting is adopted.

Such notification is described in, for example, the electronic library website of the JPO and the following patent documents. For example, in Patent Document 1 below, when access is concentrated beyond a predetermined number of accesses, a user who issues a numbered ticket with a valid period to an accessor (user) and possesses a numbered ticket within the valid period Describes a technique for restricting the number of accesses by directing to a target page when accessing again, and Patent Document 2 assigns an access permission date and time according to priority to the accessing user, and the time The technology to automatically connect to the server or notify by mail or browser when the server load decreases is described.
JP 2003-173319 A JP 2003-242110 A

  Although the technology described in Patent Document 1 can reduce the concentration of access by issuing numbered tickets, the user still has to access manually, and is restricted by the expiry date arbitrarily decided, and always aware of time. There was a problem that the convenience on the user side was lacking. Furthermore, although the technique described in Patent Document 2 can reduce access concentration by assigning access permission dates and times or notifying when the server load decreases, there is a lack of real-time performance in e-mail notifications, and there is a specific means for notifying the browser immediately. It is not described, and the current information is not updated and displayed in real time on the screen, so the user's desire to know accurate information cannot be satisfied, and it causes stress. .

  In a simple notification system, the user is notified that the site is busy, but the user recognizes the number of accesses and how long it will take. As a result, there has been a problem that it becomes an early winner structure in which only users who access in a timely manner can be connected.

  It is an object of the present invention to eliminate the problems caused by the prior art, and to manage and display a waiting state of a website that automatically guides waiting for access to the website and eliminates manual re-access by the accessor. It is to provide a system and a waiting status management / display program.

  In order to achieve the above object, the present invention provides a website waiting status management / display system for websites connected to a group of web servers corresponding to a plurality of contents from user terminals of a plurality of visitors via an Internet communication network. A guidance server for managing visitors, a waiting visitor database for storing data of waiting visitors connected to the guidance server, a message database for storing guidance texts for waiting visitors, and the message database An apology server for creating an apology screen to be transmitted to the user terminal, and an update interval database for storing an update time interval for updating the apology screen, wherein the guide server has a current access count of the web server group It is determined whether the number of processing limit users is greater than or equal to the number of processing limit users. Awaiting visitor data is stored in the waiting visitor database, and an apology screen including the guidance sentence stored in the message database by the apology server and the number of waiting visitors stored in the visitor database is sent to the user terminal, The guidance server updates the visitor data of the visitor data with reference to the waiting visitor database at each update time interval stored in the update interval database, and the apology server is updated based on the updated visitor data. The first feature is that the apology screen is updated and transmitted to the user terminal.

  In the website waiting status management / display system, a guidance server compares a current time with a re-access time by a re-visitor. When the comparison difference time is larger than an update time interval, The second feature is that the visitor data of the visitor is deleted. In these website waiting status management / display systems, the guidance server reads the current waiting visitor number, the order of guidance, and the current order from the waiting visitor database. A third feature is that a predicted waiting time calculated from the number of waiting people and the guidance rank is calculated, and the apology server includes the number of waiting visitors, the order of guidance, the current waiting number of people and the predicted waiting time in the apology screen, In any one of the website waiting status management / display systems, the update interval of the apology screen is waited from the waiting visitor database. Shorter as the guide order is early visitor of user data, and the fourth, characterized in that the longer the slow visitors.

  Furthermore, this system manages the visitor who accesses the web server group corresponding to the plurality of contents from the user terminals of the plurality of visitors via the Internet communication network, and stores an update time interval for updating the apology screen. A guidance server connected to the interval database, a waiting visitor database for storing waiting visitor data connected to the guidance server, a message database for storing guidance text for the waiting visitor, and a connection to the message database A website waiting status management / display program for a website comprising an apology server, a function for determining whether the current access count is greater than or equal to the processing limit user count of the web server group to the guidance server, and the determination When the number of users exceeds the processing limit, waiting for the waiting visitor data A function for storing in the database, a function for transmitting an apology screen including the guidance text stored in the message database to the apology server and the number of waiting visitors stored in the visitor database, and the guidance server, Executing a function of updating the visitor data by referring to the waiting visitor database at each update time interval, and a function of causing the apology server to update the apology screen based on the updated visitor data. Is the fifth feature.

In the web site waiting state management / display program, the present invention provides the guide server with a function for comparing a current time with a re-access time by a re-visitor, and when the comparison difference time is larger than an update time interval. A sixth feature is that a function of deleting visitor data of the re-visitor from the visitor database is executed, and in this website waiting state management / display program, the guide server receives the waiting visitor database from the visitor database. A function for calculating a predicted waiting time calculated from the current number of waiting visitors, the guidance order, the current waiting number and the guidance order, and the apology server displays the number of waiting visitors, the guidance order, and the current waiting number on the apology screen. According to a seventh aspect of the present invention, a function for including a predicted waiting time is executed. Fraud and mitigating risk update interval of the apology screen shorter as the waiting visitor guidance order is earlier visitors wait visitor data from a database, and eighth features of the thereby perform the functions longer slower visitors.

  In the present invention, the guidance server automatically guides the user when he / she can access the website by referring to the waiting visitor database and guiding the visitor with an apology screen in which the congestion state is updated. It saves the trouble of accessing again, and also displays the current number of visitors waiting and the guidance order of the user on the apology screen, and automatically updates it in real time. Can satisfy the desire. Furthermore, the present invention makes the apology renewal interval shorter for visitors with earlier guidance order and longer for visitors with later guidance order, so that visitors with earlier guidance order will be immediately guided to the website, and visitors with later guidance order will be later. The load on the apology server can be reduced by lengthening the update interval.

Hereinafter, a website waiting state management / display system and a waiting state management / display program according to an embodiment of the present invention will be described in detail with reference to the drawings. FIG. 1 is a diagram for explaining a computer system to which a website waiting state management / display program according to an embodiment of the present invention is applied, FIG. 2 is a diagram showing a functional configuration of this system, and FIG. 3 is a waiting state management A flowchart for explaining the overall operation of the display program, FIG. 4 is a flowchart for explaining waiting visitor presence / absence determination processing according to this embodiment, and FIG. 5 is a diagram for explaining new visitor guidance processing according to this embodiment. FIG. 6 is a flowchart for explaining apology screen creation processing according to the present embodiment, and FIG. 7 is a diagram illustrating an example of a display screen according to the present embodiment.
<Description of configuration>

  As shown in FIG. 1, a computer system to which a website waiting state management / display system according to the present invention is applied includes a web site connected to a plurality of terminals of users who are visitors via an internet network. The website according to the present embodiment includes a plurality of web server groups 02 that provide various contents, an apology (Sorry) server 04 for displaying an apology message and current waiting visitor information to the user at the time of congestion, And a guide server 03 that guides the user to wait for access to the website when the load is congested to manage waiting visitors, and a load load balancer 01 that distributes the load by distributing access to the server when the load is congested Has been.

As shown in FIG. 2, the functional configuration of the website according to the present embodiment includes the website information acquisition unit 301 in which the guidance server 03 acquires the current number of accesses from the load balancer 01 and the web server group 02. A waiting visitor database (hereinafter referred to as DB) 91 for storing information on waiting visitors, waiting visitor information is acquired from the waiting visitor DB 91, new waiting visitors are added, waiting visitor information is updated, etc. The waiting visitor information management unit 302, the update interval management unit 303 that determines the update interval of the screen displayed to each user according to the number of waiting visitors, and the update interval that stores the update interval in the update interval management unit 303 Waiting visitor presence / absence for determining whether the DB 92 and the waiting visitor's present state are kept waiting at regular intervals (hereinafter, presence / absence determination) A judgment unit 305, and the apology server 04 stores a message DB 93 for storing a plurality of messages such as various guidance / apology for the user, and a screen creation unit 401 for creating a message for the user with reference to the message DB 93. The guide server 03 receives the web access 001 from the user terminal 00, and the apology server 04 responds to various messages according to the degree of congestion.
<Description of operation>
<Whole visitor monitoring>

  Now, the website waiting state management / display system configured as described above, when a visitor accesses the website from the user terminal 00 (step 0001), as shown in FIG. The guidance server 03 obtains the current number of accesses from the load balancer 01 and the web server group 02 (step 3001), and next refers to the waiting visitor queue stored in the waiting visitor DB 91 to wait for the current waiting time. The number of visitors is acquired (step 3002).

  Next, the guidance server 03 determines whether or not the current number of waiting visitors (number of accesses) acquired in step 3002 is greater than or equal to a predetermined maximum number of accesses (step 3003), and is less than or equal to the maximum number of accesses (No ), It is then determined whether or not the number of waiting visitors is “0” or more (step 3004). If it is “0” or more, control for guiding the access to the web server group 02 is executed (step 3005). To do. That is, this embodiment guides the access to the web server group 02 when the number of accesses is equal to or less than the maximum value and there are no waiting visitors.

  If it is determined in step 3004 that the number of waiting visitors is “0” or less, this process determines whether or not the queue is the front visitor (step 3005), and determines that the visitor is the front visitor. In this case, it is guided to the web server (step 3007), and the process of deleting from the waiting visitor queue is executed.

  If it is determined in step 3003 that the number of waiting visitors is equal to or greater than the maximum number of accesses, or if it is determined in step 3005 that it is not the first visitor in the queue, the guidance server 03 determines whether the visitor is a new visitor. (Step 3009), if it is determined that the visitor is a new visitor, a unique ID is newly assigned and registered in the wait visitor DB 91 (step 3010), and the number of wait visitors acquired from the wait visitor DB 91 is determined. The determination of the update period (step 3011) is sequentially executed. That is, in the case of a new visitor, the guidance server 03 assigns an ID to the visitor, registers it in the waiting visitor DB 91, and executes a process for determining the update interval. The determination of the update interval in the step 3011 is made shorter for the waiting visitors with the earlier guidance order.

  If it is determined in step 3009 that the visitor is not a new visitor, the guidance server 03 updates the last access date / time of the visitor (step 3013), the number of visitors acquired from the waiting visitor DB 91, and the current guidance. Updates of update intervals (step 3014) are sequentially executed in order. That is, when the guidance server 03 is not a new visitor, it updates the access date and time at which the visitor attempted to access the previous time and executes a process for determining the update interval. Note that the determination method in step 3009 may be a method of sending the URL including its visitor ID at the second and subsequent accesses, and the contents of the update interval DB 92 are shown in the lower right of FIG. As described above, the visitor queue is composed of the items of visitor ID / update interval in seconds / initial access date / time / closed to last access, and the visitor queue is composed of a correspondence table of guidance order and visitor ID.

  Next to steps 3011 and 3014, the guidance server 03 calculates the expected waiting time for both new and existing visitors based on the current number of waiting visitors (step 3012), (1) visitor ID, and (2) waiting visitor. The number, (3) guidance order, (4) update interval, and (5) waiting time are passed to the apology server 04, and the process is terminated (step 3015). The calculation formula for the calculation in step 3012 is, for example, “expected waiting time = visitor average stay time × (guide order of the visitor−1)”.

  The apology server 04 that has received (1) the visitor ID, (2) the number of waiting visitors, (3) the order of guidance, (4) the update interval, and (5) the waiting time from the guidance server 03 sends the received message Based on this, an apology message for the user is created with reference to the message DB 93, and the operation is performed so as to be returned to the user terminal 00.

  As described above, the website waiting state management / display system according to the present embodiment determines whether or not the user who made the access is a new access when there is an access from the user and the number of accesses is larger than the predetermined maximum number of accesses. In the case of a new one, it is registered in the waiting visitor DB 91, and the waiting time and waiting number corresponding to the number of waiting visitors are responded to the new and already accessed users as a message.

As described above, this website waiting status management / display system notifies an already accessed user of a message such as a waiting time at the time of accessing again. It is also possible to interrupt the access again, and check for non-visited visitors every certain time, and perform visitor presence / absence determination process processing 3100 for deleting visitor information without re-accessing after a certain time, This process will be described next with reference to FIG.
<Deleting new visitor monitoring>

  This waiting visitor presence / absence determination process is automatically executed on the guidance server 03 at regular intervals, and the number of waiting visitors is acquired from the waiting visitor DB 91 as shown in FIG. 3101), it is determined whether or not the acquired number of waiting visitors is greater than “0” (step 3102). When the number of waiting visitors is “0”, the process is terminated, and the number of waiting visitors is “0”. When it is larger, the following loop processing is performed for each waiting visitor.

  In this process, the update interval and the last access date / time of the waiting visitor are acquired from the update interval DB 92 (step 3104), and whether the difference between the current time and the last access date / time of the system is larger than the update interval (time). If the time difference is larger than the update interval (when there is no re-access after the update interval time) in step 3105, the waiting visitor data is stored in the waiting visitor DB 91 and A process of deleting from the update interval DB 92 (step 3106) and a process of updating the waiting visitor DB 91 and the update interval DB 92 (step 3107) when the process is completed for all the waiting visitors. It is desirable that the update interval time of the update interval DB 92 is set such that the update interval becomes shorter as the visitor has a faster guide order by referring to the update interval master 3108 according to the guide order of the waiting visitor DB 91.

In this way, the system checks for non-existing visitors (users who do not re-access) at regular intervals, and deletes visitor information without re-access after a certain period of time, thereby monitoring waiting visitors. Efficiency can be improved. Therefore, the load on the guidance server can be reduced.
<Deleting new visitor monitoring>

The website waiting status management / display system provides guidance to new visitors when they are busy, and this new visitor guidance process will be described with reference to FIG. In this process, when a new visitor visits, a process for obtaining the number of waiting visitors from the waiting visitor DB 91 (step 3201) and a process for determining a unique visitor ID for the new visitor (step 3201). 3202), processing for adding this new visitor data to the end of the waiting visitor queue of the waiting visitor DB 91 (step 3203), and referring to the update interval master of the update interval DB 92 based on the current number of waiting visitors. (A) the waiting visitor ID corresponding to the waiting visitor queue, (b) the update interval, (c) the date and time when the visitor first accessed (initial access date and time), and (d) A process of adding four types of data of the date and time when the visitor last accessed (last access date and time) is executed. The last access date and time is initially stored at the same time as the initial access date and time, but is updated each time the visitor automatically accesses every update interval.
<Guidance apology processing>

  As described above, this system displays a plurality of messages such as various guidance / apology for the user to a visitor when the server is congested. This process will be described with reference to FIG.

  This guidance apology processing is performed by the apology screen creation unit 401 in the apology server 04. As shown in FIG. 6, (1) visitor ID (2) number of waiting visitors (3) guidance order (4) update Interval (5) Processing to acquire the waiting time from the guidance server 03 (Step 3301), (5) Processing to acquire the message according to the waiting time from the message DB 93 (Step 3302), and (1) to (5) ) And the information message and the like are synthesized (step 3303), and the created apology screen is returned to the visitor (step 3304).

  As shown in FIG. 7, this apology screen displays a message instructing to wait on the screen as it is on the screen example 402 displayed on the browser, and the waiting visitor ID as “customer ID”. In addition, by displaying the current waiting number and the current guidance order of the waiting visitor, the waiting situation is notified to the visitor in real time. In addition, the expected waiting time is displayed from the current guidance order and the average staying time of the visitors so that the waiting time as a guide can be understood. Furthermore, it is possible to follow a visitor by displaying a message that matches the waiting time from the initial access to the present. This apology screen is automatically updated at every update interval, and it is desirable to update these pieces of information in real time.

  It is also desirable to prepare an interface screen 403 that is minimized so as not to interfere with other work during the waiting time. The minimized screen 403 displays only important data such as the current guidance order and waiting time, which is also updated and displayed in real time.

  In this way, in this embodiment, by displaying the waiting order and the expected waiting time for the waiting visitors, information that can be connected if the visitor accesses next is displayed. It is possible to reduce useless re-access and to prevent a reduction in the number of accesses due to a visitor giving up.

  Since the present invention can keep track of the waiting state such as when the user has accessed, how many minutes have passed, and when he has left, the website administrator can check trends such as the average waiting time of the user. It can also be used as an information source for server enhancement.

The figure for demonstrating the computer system with which the website waiting condition management and display program by one Embodiment of this invention is applied. The figure which shows the function structure of the said computer system. The flowchart for demonstrating the whole operation | movement of the waiting condition management and display program by this embodiment. The flowchart for demonstrating waiting visitor presence / absence determination processing by this embodiment. The flowchart for demonstrating the new visitor guidance process by this embodiment. The flowchart figure for demonstrating the apology screen creation process by this embodiment. The figure which shows the example of a display screen by this embodiment.

Explanation of symbols

  00: User terminal, 01: Load load balancer, 02: Web server group, 03: Guide server, 04: Apology server, 301: Website information acquisition unit, 302: Visitor information management unit, 303: Update interval management unit, 305: Absence determination unit, 401: Apology screen creation unit, 402: Screen example, 403: Interface screen.

Claims (8)

A website waiting status management / display system for a website connected to a group of web servers corresponding to a plurality of contents from user terminals of a plurality of visitors via an Internet communication network,
A guidance server for managing visitors, a waiting visitor database for storing data of waiting visitors connected to the guidance server, a message database for storing guidance texts for waiting visitors, and a connection to the message database An apology server for creating an apology screen to be transmitted to the user terminal, and an update interval database for storing an update time interval for updating the apology screen,
The guide server determines whether or not the current number of accesses is equal to or greater than the processing limit number of users of the web server group, and when the determination is equal to or greater than the processing limit number of users, the waiting visitor data is stored in the waiting visitor database. Storing and sending an apology screen containing the guidance sentence stored in the message database by the apology server and the number of waiting visitors stored in the visitor database to the user terminal,
The guidance server updates the visitor data of the visitor data with reference to the waiting visitor database at each update time interval stored in the update interval database, and the apology server is updated based on the updated visitor data. A website waiting state management / display system characterized by updating an apology screen and transmitting it to a user terminal.   The guide server compares the current time with the re-access time by the re-visitor, and deletes the re-visitor's visitor data from the visitor database when the comparison difference time is larger than the update time interval. The website waiting state management / display system according to claim 1.   The guidance server calculates a predicted waiting time calculated from the current waiting visitor number, the guidance order, the current waiting number, and the guidance order from the waiting visitor database, and the apology server displays the number of waiting visitors on the apology screen. 3. The website waiting state management / display system according to claim 1 or 2, further comprising a guide order, a current waiting number, and a predicted waiting time.   4. The wait status management system for a website according to claim 3, wherein the update interval of the apology screen is shorter for a visitor whose guidance order of waiting visitor data is earlier from the waiting visitor database and longer for a later visitor. Display system. A guide server for managing visitors of websites connected to a group of web servers corresponding to a plurality of contents from user terminals of a plurality of visitors via an Internet communication network, and a waiting visitor connected to the guide server A waiting visitor database for storing data, a message database for storing guidance text for the waiting visitor, an apology server connected to the message database and creating an apology screen to be transmitted to the user terminal, and an apology screen is updated. A website waiting status management / display program of a website waiting status management / display system comprising an update interval database for storing update time intervals,
A function for determining whether the current access count is greater than or equal to the processing limit user count of the web server group in the guide server, and when the determination is greater than the processing limit user count, the waiting visitor data is stored in the waiting visitor database. A function of storing, a function of transmitting an apology screen including a guide sentence stored in the message database and the number of waiting visitors stored in the visitor database to the user terminal to the apology server,
Causing the guidance server to execute a function of updating visitor data by referring to the waiting visitor database at each update time interval, and a function of an apology server to update an apology screen based on the updated visitor data Website waiting status management / display program characterized by executing functions.   A function of comparing the current time with a re-access time by a re-visitor in the guidance server, and deleting the re-visitor's visitor data from the visitor database when the comparison difference time is larger than an update time interval 6. The website waiting state management / display program according to claim 5, wherein a function for executing the function is executed. A function for calculating a predicted waiting time calculated from the waiting visitor database and the current waiting visitor number, the guidance order, the current waiting number of persons, and the guidance rank from the waiting visitor database, and the apology server displays the waiting visitor on the apology screen. 7. The website waiting state management / display program according to claim 5, wherein a function for including a number, a guidance order, a current waiting number of persons, and a predicted waiting time is executed. 8. The website according to claim 7, wherein a function is executed to make the update interval of the apology screen shorter for a visitor whose guidance order of waiting visitor data is earlier from the waiting visitor database and longer for a later visitor. Wait status management / display program.

Images