JP2003296489A - Event support judging method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide information for helping users to judge the value of an object event (attraction or the like), not only the information about condition of a line, to a user. <P>SOLUTION: The number of people waiting in a line, length of the line, and waiting time of users in relation to an object event are input, and support/ non-support (satisfied/unsatisfied) of the users in relation to the object event per each waiting time is input, and a change of support ratio in relation to waiting time is computed to store as the support ratio change information. When judging support ratio, waiting time at the predetermined time point is input, and the support ratio change information is read out to output the support ratio of the object event in relation to waiting time at the predetermined time point. <P>COPYRIGHT: (C)2004,JPO

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a system for judging the approval rating of an event based on the queue of spectators at an event or attraction and the satisfaction level of the user after the event.

[0002]

2. Description of the Related Art Japanese Patent Laid-Open No. 1996-1 has been proposed as a prior art in which a waiting time for an event or the like to enter a facility is shown to a customer.
There is a publication of 23374.

In this prior art, a plurality of optical sensors are arranged along the queue of the facility, the length of the queue is determined by the detection signal of the optical sensors, the waiting time is calculated, and the waiting time is calculated. It is displayed for convenience of the user.

Further, Japanese Patent Application Laid-Open No. 1996-16658 aims to eliminate dissatisfaction with the waiting time by giving points according to the waiting time.

Further, in Japanese Patent Laid-Open No. 1999-308344, when a predetermined time arrives in order to effectively utilize the waiting time, the user's mobile phone or PDA (Pesroal Data Assist) is used.
ant) has received a call to notify the admission permission.

As described above, in the past, there existed a plurality of devices that objectively judge the queues regarding events and provide the information.

[0007]

Generally, at an event or attraction of an amusement park facility, the user tends to judge entrance to the attraction based on the attraction of the attraction and the length of the queue.

In this regard, the length of the queue can be recognized by the user as objective information, but there is no way to judge the attraction of the attraction itself.

That is, in each of the above-mentioned prior arts, although objective information about the queue is collected, "the user's post-experience information that it was good or bad to line up was ignored.

[0010] For example, from a psychological point of view, a person has a self-defense instinct for an event that he is forced to respond to the result of the effort he has made, "I should be satisfied because I have made such an effort". It is said that a certain amount of effort tends to be more satisfied than the result without effort to work.

That is, although objective information such as a queue can be obtained, the subjective information of the user after the experience can only be heard by the user after grasping the user after the experience. It was

That is, in the conventional technology, objective information can be provided to a user who is uncertain whether or not to participate in an attraction, but subjective information (that is, information regarding attraction to an attraction) cannot be provided. There wasn't.

The present invention has been made paying attention to such a point, and by collecting the state information of the queue and the result information (satisfaction level) of the user after the experience, the target event (event) is collected. Or attractions, etc.).

[0014]

According to the present invention, the number, length or waiting time of the queue of the user for the target event is input in advance by using a computer system, and the user of each waiting time is entered. Support / dissatisfaction (satisfaction / dissatisfaction may be performed) for the target event is input, and a change in the support rate with respect to the waiting time is calculated and stored as support rate change information. When determining the approval rating, a waiting time at a predetermined time is input, the approval rating change information is read out, and the approval rating of the target event for the waiting time at the predetermined time is output. Is.

By displaying this approval rating to the user, it becomes reference information for determining whether the user is lined up in the queue, that is, whether to enter the event.

Further, the present invention is effective when event venues or attractions that must be lined up on a vast site are scattered.

That is, if the approval rating for each event is displayed in addition to the queue status, the user can easily select the next event venue or attraction, and selectively and efficiently go around the event or attraction. It becomes possible. In such a case, the approval rating of each event and each attraction is the center (server).
It is desirable that the information on the approval rating be centrally managed by PDA and be distributed to the PDA owned by the users who move in the vast premises.

Also, for the operator, by knowing the change in the waiting time and the approval rating for the attraction, it is possible to restrict the entrance of the user and to specify the time (for example, waiting for 3 hours at the present time, but 40 minutes if 4 hours later) It becomes possible to wait and wait for a high approval rate to enter the facility.)
It is possible to realize efficient operation management such as.

Further, since the operator can calculate the approval rating for each attraction, it can be used as a reference for designing the layout of attractions on the premises.

[0020]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Before describing specific embodiments, the concept of the present invention will be described with reference to FIGS. Figure 2
FIG. 3 is a conceptual diagram for explaining a general waiting action. Here, a general “waiting action” means an action in a “waiting line” in order to experience a certain event. The “queuing” is a queue for waiting when a user who wants to experience more events than a predetermined amount of time appears. There may be no queue, but conceptually it can always be thought of as being. Therefore, we consider that the “process up to event experience” is always performed. “Wait time” is the time it takes to experience the target event after it begins to be queued. The "target event" is generally a service (for example, attraction) provided. "Judgment material" is knowledge for "whether the person who is considering experiencing the target event" to judge whether or not to experience the target event. The "action judgment" is to judge whether or not a person experiences the target event based on the judgment material. Regarding the waiting action here, it is assumed that the target event does not have an absolute value, and that the waiting action is for an event that has a "choice of choice" for obtaining value. Therefore, action judgment is required. The "experienced person" is
It is the person who experienced the event (the user immediately after experiencing it). FIG. 24 is a conceptual diagram illustrating a human behavior determination model. This figure is a model associated with the execution / non-execution of a person's action, and explains the action determination of FIG. 23 in detail. Here, "internal judgment of a person" is a part corresponding to "thinking / consciousness", and it is judged whether or not to act under the influence of "external information" or "internal desire". “Internal desire” is roughly divided into “physiological desire” and “mental desire”, and they interact with each other. In addition to “internal desire”, “personal preference element”, “mental state element”, “body state element”, etc., influence the “behavior determination”. "Experience / experience" the result of "action judgment" and accumulating "knowledge" which is a part of "external information" is called "learning function". The “select to experience” or “select not to experience” in FIG. 23 corresponds to “execution” or “non-execution” in FIG. 24, respectively. FIG. 25 is a conceptual diagram illustrating a conventional problem. As for the queue, as mentioned above, there were many cases in which the “state of the queue” (image) and the “waiting time” were acquired and provided from the “queue”.
However, “waiting” and “waiting time” are only objective information. This objective information has a problem in that it does not include subjective information such as "whether it is good to wait in line or not (whether it is worth waiting in line)". For the target event, "Contents of the target event"
Is generally provided by the “target event provider”. This information is one-sided information from the provider side and rarely includes subjective information from the experience side. In order to make "action judgments" (subjective judgments) that determine whether or not you will be in a queue, the live voice of the experience person (that is, subjective information) about how you actually felt in a queue is essential. That is not the case. FIG. 26 is a conceptual diagram illustrating a psychological effect on the waiting time. “Information provision” in FIG. 25 described above
Then, the "waiting time" is information that is highly important for "action judgment". That is, the shorter the “waiting time” is, the more the “action judgment” of “execution” is prompted. However, people's line of mind is not always satisfied if the time is short. FIG. 26 shows such a psychological effect. People consciously or unconsciously "evaluate" the obtained "results". This "evaluation" is usually performed based on the "expectation" that was assumed before obtaining the "result". "Effort" generates "self-defense instinct" such as "I should be satisfied because I have tried so much" with respect to the obtained "result". "Self-defense instinct" acts to increase "satisfaction" with respect to "evaluation", and tends to be more satisfied than "result" obtained without "effort". In the case of a queue, "effort" is to wait in line. Therefore, the value of the target event accompanied by the queue must be evaluated by the "satisfaction" finally obtained after going through the process of the target event experience including the "waiting action". This corresponds to the "subjective information" whose necessity is explained in FIG. In other words, if "satisfaction" is collected and provided as "subjective information", it becomes information that enables "action judgment" that cannot be obtained only from "waiting time". FIG. 27 is a diagram for explaining the basic concept of the present invention. The present invention provides "subjective information" in addition to the "objective information" provided by the conventional system on the premise of what has been described with reference to FIGS.
It supports the judgment of those who do. The “subjective information” is a collection of subjective judgments whether the “experiencer of the target event” was good or bad immediately after experiencing the target event. "Experiencer's subjective judgment" is a more accurate judgment material by indicating how long the person's line-up belongs. Therefore, subjective judgments of goodness and badness are aggregated for each waiting time of the experienced person and provided as a "support rate" for each waiting time. The person who makes the "action judgment"
By comparing the time you will be waiting for with the "support rating" collected for each hour, you will be able to more accurately judge whether it is worth waiting in the queue. As a result of the “action judgment”, the person who chooses to “execute” is the “experiencer of the target event” after experiencing the target event.
As to provide subjective judgment. The “subjective information” can be used as information for the source of the target event to grasp the satisfaction level of the user.

[0021]

First Embodiment Next, a more specific embodiment of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing a first embodiment of the present invention.

In the figure, the matrix length detecting device is a device for detecting the matrix length. For example, photosensors are arranged at predetermined distances on both side surfaces of the matrix, and the photosensor detects the matrix length. It was done like this. This detection data is output to the waiting information management server.

The image pickup device is, for example, a CCD camera, and outputs the state of the photographed queue as video data to the waiting information management server.

The support / non-support input device is a switch installed at the exit of the event venue which is the target event, and is a switch for a user who has experienced this event to input support / non-support for this event. Is. The experience user may directly operate this switch, or the operator may input support / non-support based on the result of the questionnaire. Further, the exit gate may be divided into "support" and "non-support", and the support or non-support may be detected depending on which gate the experienceer passes through. In addition, an imaging device is installed near the exit, the display of the person who is leaving the attraction is photographed, image analysis is performed, it is determined whether or not the attraction is satisfied, and support or non-support is determined. Good.
The support / non-support data thus obtained is also output to the waiting information management server.

The waiting information management server is composed of a computer system and has a waiting information database. In this waiting information database, changes in approval rating with respect to waiting time are recorded as approval rate change information.

The waiting information management server calculates the waiting time, calculates the approval rating, and manages the waiting time. For example, the waiting time can be obtained by measuring the actual queue length from the image data of the queue length detection device and the image pickup device, and simulating the waiting time for this queue length. The support rate is calculated in association with the waiting time.

The information acquisition / display device is, for example, a PDA owned by a user or a mobile phone with a display function, and can be connected to an information management server via a network or the like.

In the figure, first, the waiting information management server calculates the waiting time based on the information obtained from the queue detecting device and the image pickup device.

Next, the support / non-support information input by the experienced user of the target event is registered in the waiting information database in association with the waiting time. At this time,
Regarding the waiting time for each user, the waiting time may be heard for each experienced user and input to the waiting information management server, or the waiting time simulated by the waiting information management server itself as described above. May be used.

Next, the waiting information management server calculates the ratio of support / disapproval of the target event by a large number of users for each waiting time, and uses this as a supporting ratio for each waiting time to change the supporting ratio of the waiting information database. Record as information.

Next, when a request is accepted from the information acquisition / display terminal device possessed by the user who is thinking of participating in the event via the network, the waiting information management server causes the queue length at that time to be the same. A simulated waiting time is calculated from the information obtained from the detection device or the imaging device, and the support rate corresponding to this waiting time is read from the support rate change information of the waiting information database.

The read support rate is returned to the user's information acquisition / display terminal via the network as support rate data.

The information acquisition / display terminal that has received the support rate information converts the information into visible information and displays it as a numeric value or a graph of the support rate. At this time, the line length, the line image, or the simulated waiting time may also be displayed on the information acquisition / display device.

FIG. 2 is a block diagram showing the hardware configuration of the waiting information management server.

The waiting information management server is composed of a general-purpose computer system, and has an arithmetic unit composed of a central processing unit (CPU), a memory unit, a communication unit, an MM input / output unit, and an external storage device management unit. It is composed of.

The MM (Man Machin) input / output unit is an interface unit with the server operator, and an input device and an output device can be connected. As an input device, a keyboard, a numeric keypad, a mouse, a bar code reader and the like (not shown) are connected. Further, a display, a printer, or the like is connected as the output device.

The communication section is a section for controlling communication with an external network.

The external storage device management unit has a function of controlling input / output of data on / from various storage media. As a storage medium, a hard disk, a flexible disk, a CD-ROM, a CD-R, a DVD-RO
Any of M, DVD-RAM, magnetic card, IC card, etc. may be used. Processing programs and waiting information databases are stored in these storage media. Here, the processing program is a program for causing the waiting information management server to function, and includes an operating system (OS) and a control program for the waiting information database. These processing programs are appropriately read into the memory unit and executed by the arithmetic unit.

In the waiting information database, information on waiting time and support rate and support rate change information calculated thereby are recorded.

FIG. 3 is a block diagram showing the hardware configuration of the information acquisition / display terminal.

The information acquisition / display terminal is composed of a PDA, a mobile phone, a portable personal computer or the like carried by the user as described above.

In the figure, the functions of the arithmetic unit, the memory unit, the communication unit, the external storage device management unit, the MM input / output unit and the like are the same as those of the above-mentioned waiting information management server, and therefore their explanations are omitted.

The input device connected to the MM input / output unit is preferably a numeric keypad, a handwritten character recognition pad, a small keyboard, etc. in consideration of being portable. It is also desirable that the output device is a small device such as an LCD display.
Also, the external storage device is preferably a small memory device such as a flash memory or a RAM.

The communication section is preferably an interface compatible with a wireless or infrared communication system,
It is also possible to use a PHS data communication interface, a wireless LAN, or a Bluetooth system interface.

FIG. 4 is a block diagram showing the hardware configuration of the support / non-support input device.

The support / non-support input device is a terminal device installed at the exit of the attraction venue, and a general-purpose personal computer or the like can be used.

In the figure, the functions of the arithmetic unit, the memory unit, the communication unit, the external storage device management unit, the MM input / output unit, etc. are the same as those of the above-mentioned waiting information management server, and therefore their explanations are omitted.

The input device connected to the MM input / output unit may be a push button meaning "support" or "non-support" as long as it can selectively input support / non-support. When the operator verbally receives the impression of the instruction / non-support from the experience user at the exit, the input device may use a keyboard or a numeric keypad. Furthermore, the exit gate is divided into “support” and “non-support”, and an optical sensor and a gate switch are provided for each, so that the supporter and the non-supporter can be detected depending on which gate the experience person leaves. Good.

FIG. 5 is a block diagram showing all the functions of this embodiment.

That is, when the queue length information is input to the waiting information management server from the queue length detecting device, this information is converted into waiting time. Specifically, this conversion can be calculated by sampling in advance how many waiting users exist within the predetermined length of the queue and calculating the number of people who can accommodate the attraction and the time required for the experience. .

Next, this waiting time is stored in the waiting information database.

On the other hand, the support / non-support information of the experience user obtained from the support / non-support input device is also recorded in the waiting information database of the waiting information management server. At this time, in the waiting information database, the distribution of the approval rating based on the change in the waiting time is calculated and recorded as the approval rate change information.

On the other hand, the video data taken by the image pickup device is input to the waiting information management server. Although not shown, the waiting time may be calculated by analyzing the image data from the image pickup device.

Next, when the user requests information regarding a particular attraction from the waiting information management server through the waiting time information acquisition / display terminal possessed by the user, the waiting information management server waits at that time. The time is read from the waiting information database, and the approval rating corresponding to the waiting time is read out from the approval rate change information. Then, together with the video data obtained from the imaging device, these pieces of information are returned to the waiting information acquisition / display terminal. That is,
At the waiting information acquisition / display terminal, the current approval rating of the attraction and the image data in the queue are received, and these are sent to the liquid crystal display (LC) through the MM input / output unit.
The image is displayed visually on the display device of D).

FIG. 6 is a flow chart (1) showing the processing procedure of the waiting information management server.

In the figure, the procedure for processing the data inputted by the arithmetic unit of the waiting information management server from the queue length detecting device is extracted from the functions explained in FIG.

The arithmetic unit of the waiting information management server receives the preset acquisition timing (step 6).
01, 602, 603), and the matrix length information is read from the matrix length detection device (604). Specifically, the specific length of the matrix is detected depending on which of the optical sensors arranged on both sides of the matrix receives or blocks light.

Next, this matrix length is converted into a waiting time (605). This conversion process is performed as described above, for example,
This can be calculated by sampling in advance how many waiting users are present within a predetermined length of the queue and calculating the number of people who can accommodate the attraction and the time required for the experience.

Then, the waiting time obtained above is recorded in the waiting information database (606).

FIG. 7 is a flowchart (2) showing the processing procedure of the waiting information management server.

The figure shows the processing of input data mainly from the support / non-support input device extracted from the functions described in FIG.

As shown in the figure, the waiting information management server waits for an input from the supporting / not supporting input device (701 to 701).
703), when there is an input, the information is read (70
4). Then, the waiting time of the experience user who inputs the acquired information is calculated (705). This calculation may be performed by subtracting the experience time of the attraction and reading the waiting time when the user enters the attraction from the waiting information database. In addition, when the support / non-support input device inputs support or non-support, the user may input the waiting time.

Next, the support / non-support information obtained from the support / non-support input device is stored in the waiting information database in association with the waiting time (706).

FIG. 8 is a flowchart (3) showing the processing procedure of the waiting information management server.

In the figure, the processing of the data inputted from the waiting information acquisition / display terminal is mainly extracted from the functions explained in FIG.

When the waiting information acquisition / display terminal makes a request (801 to 804), the waiting information management server establishes a connection with the waiting information acquisition / display terminal in the communication section (805). For this connection, for example, a communication protocol based on the PHS data communication method can be used.

Next, the arithmetic unit of the waiting information management server reads out information on the current waiting time from the waiting information database (806). Then, the support rate corresponding to the waiting time is read from the support rate change information in the waiting information database (807).

Next, video data is input from the image pickup device (808). Then, the waiting time, the approval rating, and the video data obtained by these are returned to the waiting information acquisition / display terminal (809).

Furthermore, when a connection disconnection request is issued from the information acquisition / display terminal, the system enters a standby state (810 →
802).

FIG. 9 is a flowchart showing the processing procedure of the waiting information acquisition / display terminal.

This figure mainly extracts the processing of the arithmetic unit of the waiting information acquisition / display terminal from the functions described in FIG.

When the waiting information acquisition request is made through the MM input / output unit by the input operation from the user (901 to 904), the operation unit of the waiting information acquisition / display terminal sends the waiting information management server to the waiting information management server. A request for waiting information acquisition is transmitted (905). Specifically, the operation of the waiting information acquisition / display terminal is realized by the user performing an input operation on the PDA functioning as the information acquisition / display terminal through the touch panel connected to the MM input / output.

Upon establishing the connection with the waiting information management server, the communication unit of the waiting information acquisition / display terminal receives the information from the waiting information management server transmitted in step 809 of FIG. 8 (907 to 909). ). That is, the waiting time, the support rate, and the video data are received.

Next, the arithmetic unit displays the received information on a liquid crystal display (LCD) or the like through the MM input / output unit (910). At this time, the waiting time and the support rate may be displayed as a graph together with the image in the waiting state.

When the user makes a termination request through the MM input / output unit, a connection disconnection request is transmitted to the waiting information management server (911, 912).

FIG. 10 is a flow chart showing the processing procedure of the support / non-support input device.

The figure mainly extracts the processing of the arithmetic unit of the supporting / unsupporting input device from the functions described in FIG.

When there is a support or non-support input by the push button connected to the MM input / output unit, the arithmetic unit of the support / non-support input device reads this support or non-support information, It is transmitted to the waiting information management server (1004, 1005).

FIG. 11 is a diagram for explaining the outline of the series of processes described above in an easy-to-understand manner.

That is, as described with reference to FIG. 5, the supporting / unsupporting input device is installed near the exit of the attraction,
Here, the experience person of the attraction is made to input the support or non-support of the attraction. When selecting the support or non-support, the exit gate may be divided into “support” or “non-support” and the support or non-support may be detected depending on which the experienceer passes through, as described above. .

The PC in the figure represents a waiting information management server, and the waiting information acquisition / display terminal of the user is composed of a PDA. Communication between this PDA and PC is realized by data communication by PHS telephone. It is supposed to be done.

On the screen of the information acquisition / display terminal, as shown on the right side of the figure, the support rate for the waiting time is displayed together with the video data of the attraction taken by the image pickup device at that time. Has become. By thus displaying the image of the queue and the support rate in the form of a graph, the user can easily determine whether or not to join the queue of the attraction.

[0083]

Second Embodiment FIG. 12 is an explanatory view showing the concept of the second embodiment of the present invention.

This embodiment is a specific mode when the present invention is carried out in a theme park.

The figure shows a case where attractions (A to D) are scattered in a vast site.

In this embodiment, the theme park is
Any attractions and event venues that are subject to queues may be scattered in the vast grounds, and may be amusement parks such as amusement parks, exhibitions, and trade fairs.

FIG. 13 is a detailed description of the second embodiment, in which the attraction to be experienced next is selected from among the attractions (A to D) scattered by the users who visit the theme park. It shows the state you are trying to.

At this time, the center of the theme park (waiting information management server) notifies the user of the image of the queue of each attraction (A to D), the waiting time, and the approval rating for each attraction. It is like this.

In this way, since the user can obtain the waiting information of each attraction on the vast site, it becomes possible to accurately select the attraction to be experienced next, and the theme park experience with high satisfaction is possible. Becomes That is, the user can make the next action judgment by receiving the judgment support by the waiting information from the center (waiting information management server) during the waiting time. This has the effect of turning a tedious wait into a fun time to ponder your next plan.

FIG. 14 is a block diagram showing a hardware configuration embodying the second embodiment.

In the figure, the image pickup device is a CCD camera, and the state of the photographed matrix is output as video data to a waiting information management server connected to each image pickup device.

The matrix length detecting device is a device for detecting the matrix length. For example, optical sensors are arranged at predetermined distances on both sides of the matrix and the matrix length is detected by the optical sensors. Is. This detection data is output to the waiting information management server.

The support / non-support input device is a switch installed at the exit of the event venue which is the target event, and is a switch for a user who has experienced this event to input support / non-support for this event. Is. The experience user may directly operate this switch, or the operator may input support / non-support based on the result of the questionnaire. Further, the exit gate may be divided into "support" and "non-support", and the support or non-support may be detected depending on which gate the experienceer passes through. In addition, an imaging device is installed near the exit, the display of the person who is leaving the attraction is photographed, image analysis is performed, it is determined whether or not the attraction is satisfied, and support or non-support is determined. Good.
The support / non-support data thus obtained is also output to the waiting information management server.

The waiting information management server is composed of a computer system provided for each attraction,
It has a waiting information database. In this waiting information database, changes in approval rating with respect to waiting time are recorded as approval rate change information.

The waiting information management server calculates the waiting time, calculates the approval rating, and manages the waiting time. For example, the waiting time can be obtained by measuring the actual queue length from the image data of the queue length detection device and the image pickup device, and simulating the waiting time for this queue length. The support rate is calculated in association with the waiting time.

The information acquisition / display device is, for example, a PDA owned by a user or a mobile phone with a display function, and can be connected to a waiting information management server via a network.

In the figure, first, the waiting information management server calculates the waiting time based on the information obtained from the queue detecting device and the image pickup device.

Next, the support / non-support information input by the experienced user of the target event is registered in the waiting information database in association with the waiting time. At this time,
Regarding the waiting time for each user, the waiting time may be heard for each experienced user and input to the waiting information management server, or the waiting time simulated by the waiting information management server itself as described above. May be used.

Next, the waiting information management server calculates the support / disapproval ratio of a large number of users to the target event for each waiting time, and uses this as a supporting ratio for each waiting time to change the supporting ratio of the waiting information database. Record as information.

Next, when a request is accepted from the information acquisition / display terminal device possessed by the user who is thinking of participating in the event via the network, the waiting information management server determines that the queue length at that point in time. A simulated waiting time is calculated from the information obtained from the detection device or the imaging device, and the support rate corresponding to this waiting time is read from the support rate change information of the waiting information database.

The read support rate is returned to the user's information acquisition / display terminal via the network as support rate data.

The information acquisition / display terminal that has received the support rate information converts the information into visible information and displays it as a numerical value or a graph of the support rate. At this time, the line length, the line image, or the simulated waiting time may also be displayed on the information acquisition / display device.

In this embodiment, the waiting information management servers are connected to each other by the network network in the park, and the target event information management server (center server) for integrally managing the attractions is connected to this network in the park. ing. The target event information management server has a function of receiving and managing information on the waiting time and approval rate of the waiting information database of the waiting information management server of each attraction via the in-park network.

FIG. 15 is a block diagram showing the hardware configuration of the target event information management server.

In the figure, the target event information management server is composed of a general-purpose computer system, and is composed of an arithmetic unit composed of a central processing unit (CPU), a memory unit, a communication unit, an MM input / output unit and an external unit. The storage device management unit.

The MM (Man Machin) input / output section is an interface section with the server operator, and an input device and an output device can be connected. As an input device, a keyboard, a numeric keypad, a mouse, a bar code reader and the like (not shown) are connected. Further, a display, a printer, or the like is connected as the output device.

The communication section is a section for controlling communication with the above-mentioned park network.

The external storage device manager has a function of controlling input / output of data on / from various storage media. As a storage medium, a hard disk, a flexible disk, a CD-ROM, a CD-R, a DVD-RO
Any of M, DVD-RAM, magnetic card, IC card, etc. may be used. Processing programs and target event information databases are stored in these storage media. Here, the processing program is a program for operating the waiting information management server,
This also includes an operating system (OS) and a control program for the waiting information database. These processing programs are appropriately read into the memory unit and executed by the arithmetic unit.

The target event information database stores the waiting time of each attraction (A to D), the average support rate, the content of the target event (attraction), and the like.

The waiting information management server, information acquisition / display terminal, and support / non-support input device in this embodiment are the same as those described in FIGS. 2, 3 and 4 of the first embodiment. Therefore, the description is omitted.

FIG. 16 is an explanatory diagram for explaining the function of this embodiment.

The waiting information management server of each attraction reads the waiting time, the photographing data of the queue, etc. from the waiting information database in response to the request from the target event management server. In addition, the support rate is read and the average support rate is calculated. Then, at least the waiting time and the average support rate regarding the attraction are transmitted to the target event information management server.

The target event information management server stores the waiting time information and the average support rate received from the waiting information management server in the target event information database.

When the target event information management server receives the content information for each attraction from the organizer, administrator or user via the MM input / output unit, this content information is also stored in the target event information database. For example, if the target event is an attraction such as a roller coaster, the explanation document for the target event is photo information, and the content information includes the fear level, the target age, the target height, and the impression of the experience person. These contents information is HTM
It can be stored in the target event information database of the target event information management server as a text file in L (Hyper Text Mark-up Language) format, an image file, and a moving image file.

When a target event information management server makes a request for a target event through the MM input / output unit from another user through the information acquisition / display terminal, the target event information database waits or averages based on this request. Read information such as rate.

Then, the read information is returned to the information acquisition / display terminal through the MM input / output unit.

FIG. 17 is a flow chart showing the processing procedure (input of content information) of the arithmetic unit of the target event information management server.

The calculation unit of the target event information management server uses the MM from the information acquisition / display terminal of the organizer, manager or user.
When the content information of the target event is input through the input / output unit (1701-1703), the target information is read and stored in the target event information database.

FIG. 18 is a flow chart showing the processing procedure (input from the waiting information management server) of the calculation unit of the target event information management server.

When the information acquisition timing from the waiting information management server arrives at the target event information management server (18
01 to 1803), and requests the waiting information management server to transmit the waiting time of the attraction managed by the waiting information management server and the average approval rating information to the target event information management server (1805). When the waiting time and the average approval rating information have been received from the waiting information management server, these pieces of information are stored in the target event information database. Such steps 1805 to 1808
Repeat the above process for all waiting information management servers,
When the information is acquired from all the waiting information management servers, the processing is completed (1804).

FIG. 19 is a flow chart showing the processing procedure (information acquisition / information transmission to the display terminal) of the calculation unit of the target event information management server.

When the information acquisition request from the information acquisition / display terminal is sent through the MM input / output unit (1901-1903), the target event information management server accepts this target event information request (information request regarding attraction). Establish connection with information acquisition / display terminal (1904, 190)
5).

Next, the arithmetic unit of the target event information management server reads out the waiting time information, the average approval rating, and the content information of one target event (attraction) from the target event information database (1906 to 1909). , And returns these information to the information acquisition / display terminal (1910). The content information may be returned only when the information acquisition / display terminal requests detailed information.

Then, when these pieces of information are returned for all target events (attractions) in the park, the processing is completed after waiting for disconnection from the information acquisition / display terminal (1909, 1911).

Note that in step 1909 in the flow of FIG. 19, information such as waiting time information for all target events (attractions) is returned to the information acquisition / display terminal, but this is the target that the user wants to experience. This is to make it easier to select an event (attraction), and it is not necessary to return the waiting time information for all target events, and it is necessary to select the target event (attraction) when the user requests information acquisition. Of course, only the waiting time information or the like regarding the selected target event may be returned.

FIG. 20 is a flowchart showing the processing procedure of the arithmetic unit of the waiting information management server provided for each target event.

The arithmetic unit of the waiting information management server receives the information acquisition request from the target event management server from the MM input / output unit via the in-park network (2001 to 20).
03), the current waiting time information is read from the waiting information database (2004, 2005).

Next, all supporting / unsupporting information is read from the waiting information database, and the average supporting rate of the target event (attraction) managed by the waiting information management server is calculated (2006).

Then, the waiting time information and the average support rate read out above are transmitted to the target event information management server (2
007).

FIG. 21 is a flowchart showing the processing procedure of the arithmetic unit of the information acquisition / display terminal.

When the arithmetic unit of the information acquisition / display terminal receives the acquisition request of the target event information from the user through the MM input unit (2101 to 2104), the arithmetic unit of the information acquisition / display terminal notifies the waiting event information management server via the in-park network. An information acquisition request is transmitted (2105), and a connection with the target event information management server is established (2106).

When the information is received from the target event information management server, the information is displayed on the display device or the like through the MM input / output unit.

FIG. 22 is an explanatory diagram for explaining a concrete operation of the second embodiment.

As shown in the figure, the user uses his or her own PDA (information acquisition / display terminal) to carry out each attraction (target event: here, haunted house, roller coaster, ferris wheel, rapid slide). For example), it is possible to know the waiting time and the average approval rating as shown on the right side of the figure. For details, see the HTML (Hyper Text Mark
-up Language) format information. By specifying this detail, the detailed information stored in the waiting information management server of each attraction can be downloaded to the PDA and displayed. .

According to the present invention, the state information of the queue and the support rate of the user after the experience are collected and the information is used while the next target event is being selected or waiting time is spent. By providing the information to the person concerned, it is possible to raise expectations for the target event and also to efficiently manage the target event situation.

[Brief description of drawings]

FIG. 1 is a block diagram showing a first embodiment of the present invention.

FIG. 2 is a block diagram showing a hardware configuration of a waiting information management server.

FIG. 3 is a block diagram showing a hardware configuration of an information acquisition / display terminal.

FIG. 4 is a block diagram showing a hardware configuration of a supported / unsupported input device.

FIG. 5 is a block diagram showing all functions of the first embodiment.

FIG. 6 is a flowchart (1) showing a processing procedure of the waiting information management server.

FIG. 7 is a flowchart (2) showing a processing procedure of the waiting information management server.

FIG. 8 is a flowchart (3) showing a processing procedure of the waiting information management server.

FIG. 9 is a flowchart showing the processing procedure of the waiting information acquisition / display terminal.

FIG. 10 is a flowchart showing a processing procedure of a support / non-support input device.

FIG. 11 is a diagram for explaining an outline of a series of processes of the first embodiment in an easy-to-understand manner.

FIG. 12 is an explanatory diagram showing the concept of the second embodiment of the present invention.

FIG. 13 is a more detailed explanatory diagram of the second embodiment.

FIG. 14 is a block diagram showing a hardware configuration that embodies the second embodiment.

FIG. 15 is a block diagram showing a hardware configuration of a target event information management server according to the second embodiment.

FIG. 16 is an explanatory diagram of all functions of the second embodiment.

FIG. 17 is a flow diagram (1) showing a processing procedure of an arithmetic unit of the target event information management server of the second embodiment.

FIG. 18 is a flow chart (2) showing the processing procedure of the calculation unit of the target event information management server of the second embodiment.

FIG. 19 is a flowchart (3) showing the processing procedure of the calculation unit of the target event information management server of the second embodiment.

FIG. 20 is a flowchart showing a processing procedure of an arithmetic unit of the waiting information management server according to the second embodiment.

FIG. 21 is a flowchart showing a processing procedure of an arithmetic unit of the information acquisition / display terminal according to the second embodiment.

FIG. 22 is an explanatory diagram for explaining a specific operation of the second embodiment.

FIG. 23 is a conceptual diagram illustrating a general “waiting action”.

FIG. 24 is a conceptual diagram illustrating a human behavior determination model.

FIG. 25 is a conceptual diagram illustrating conventional problems.

FIG. 26 is a conceptual diagram illustrating a psychological effect on waiting time.

FIG. 27 is a diagram for explaining the basic concept of the present invention.

   ─────────────────────────────────────────────────── ─── Continued front page    (72) Inventor Atsushi Shimizu             Shiokyo-ku, Kyoto-shi, Kyoto Prefecture             801 Kudo-cho Omron Co., Ltd. (72) Inventor Keiichi Tamai             Kyoto Prefecture Kyoto City Shimogyo-ku Kizuyabashi Dori Nishitoin East Entrance             606, Higashishiokojicho Omron Softou             Inside (72) Inventor Hirofumi Fukumoto             Kyoto Prefecture Kyoto City Shimogyo-ku Kizuyabashi Dori Nishitoin East Entrance             606, Higashishiokojicho Omron Softou             Inside

Claims (4)

[Claims] 1. The number of people, the length or the waiting time of the user's queue for the target event is input in advance, and the support value for the target event of the user for the wait time is input, and the support rate for the wait time. Change is calculated and stored as support rate change information, and by inputting the waiting time at a predetermined time point, the support rate change information is read and the support rate of the target event for the waiting time at the predetermined time point is output. Event support judgment method. 2. A means for inputting the number, length or waiting time of a queue of a user for a target event, a means for inputting a support value for the target event of the user for the waiting time, and the waiting time. Support rate change information storage means for calculating and storing a change in the support rate for the target event, and a support rate of the target event at the predetermined time by referring to the support rate change information for a waiting time input at a predetermined time point. An event support judging device comprising a reading means and a means for outputting the support ratio read out above. 3. The number of people, the length, or the waiting time of the queue of the user for the target event is accepted, the support value for the target event of the user for the wait time is accepted, and the support for the wait time is accepted. The rate change is calculated and stored as support rate change information, and by inputting the waiting time at a predetermined time point, the support rate change information is read and the support rate of the target event for the waiting time at the predetermined time point is output. A computer executable program. 4. An event support judgment system comprising a server that calculates a support rate for a target event and a terminal device that receives information on the support rate, wherein the server is a queue of a user for the target event. Means for inputting the number of people, length or waiting time, means for inputting a support value for the target event of the user for the waiting time, and support rate change for calculating and storing a change in the support rate for the waiting time Information and means for reading out the support rate value of the target event at the predetermined time by referring to the support rate change information for the waiting time input at a predetermined time point, and transmitting the support rate value read out at the above And a unit for receiving the support rate value from the server, and a unit for displaying the received support rate value.