Information processing method, information processing system, information processing device, and program

Abstract

To provide an information processing method and the like that can limit the number of persons accommodated in an event hall.SOLUTION: An information processing method according to one aspect comprises: counting the number of entering persons who are authenticated through reception terminals for an event; counting the number of exiting persons from the event; calculating the number of staying persons within the event hall on the basis of the counted number of entering persons and the counted number of exiting persons; determining whether the number of persons into the event reaches the limiting number of persons on the basis of the calculated number of staying persons; and refusing authentication through the reception terminals when the number of persons reaches the limiting number of persons.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present invention relates to an information processing method, an information processing system, an information processing device, and a program. [Background technology]

[0002] There is a technology that uses a visitor identification code to check in visitors (entrants) when they arrive at a facility or event venue. For example, Patent Document 1 discloses a visitor management system that reads a visitor identification code printed on a letter brought by the visitor and registers the read visitor identification code in a visitor database. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2006-99786 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, the invention disclosed in Patent Document 1 has a problem in that when there are restrictions on holding an event (such as capacity or maximum number of people), it is not possible to limit the number of people that can be accommodated at the event venue.

[0005] One aspect of the present invention is to provide an information processing method and the like that makes it possible to limit the number of people that can be accommodated at an event venue. [Means for solving the problem]

[0006] An information processing method according to one aspect comprises tallying the number of entrants authenticated through a reception terminal for an event, tallying the number of people leaving the event, calculating the number of people staying in the event venue based on the tallied numbers of entrants and exits, determining based on the calculated number of people staying in the event whether the limit for the number of people permitted to enter the event has been reached, and rejecting authentication through the reception terminal if the limit has been reached. Effect of the Invention

[0007] One aspect is that event venues will be able to limit capacity. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is an explanatory diagram showing an overview of an visitor reception system. [Diagram 2] FIG. 2 is a block diagram showing an example of the configuration of a server. [Diagram 3] FIG. 13 is an explanatory diagram illustrating an example of a record layout of an event DB. [Figure 4] FIG. 2 is an explanatory diagram showing an example of the record layout of an attendee DB and an entrance / exit management DB. [Diagram 5] 2 is a block diagram showing an example of the configuration of an entrance reception terminal. FIG. [Figure 6] FIG. 2 is an explanatory diagram illustrating the operation of the visitor reception system. [Figure 7] FIG. 13 is an explanatory diagram showing an example of a display screen of the number of people staying in a venue of an event and the congestion state. [Figure 8] FIG. 13 is an explanatory diagram showing an example of an admission reception screen. [Figure 9] 13 is a flowchart showing a processing procedure when performing authentication through the entrance reception terminal. [Figure 10] 13 is a flowchart showing a processing procedure when performing authentication through the entrance reception terminal. [Figure 11] 13 is a flowchart showing a processing procedure for outputting the number of people staying in a venue and a congestion state. [Figure 12]13 is a flowchart showing a processing procedure when accepting admission based on the second limit number of people. [Figure 13] 13 is an explanatory diagram showing an example of a display screen for admission restriction or admission restriction lift notification; FIG. [Figure 14] 13 is a flowchart showing a processing procedure for transmitting a notification of admission restriction or admission restriction lifting. [Figure 15] FIG. 13 is a block diagram showing an example of the configuration of a server according to a fourth embodiment. [Figure 16] 13 is an explanatory diagram showing an example of the record layout of an attendee DB, an entrance / exit management DB, and a sub-event DB in embodiment 4. FIG. [Figure 17] FIG. 1 is an explanatory diagram showing an example of an event and a sub-event held within the venue of the event. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, the present invention will be described in detail with reference to the drawings showing embodiments thereof.

[0010] (Embodiment 1) The first embodiment relates to a form in which admission to an event is accepted based on a limit on the number of people who can enter the event. Fig. 1 is an explanatory diagram showing an overview of an attendee acceptance system. The system of this embodiment includes a management device 1, an admission acceptance terminal 2, and a display device 3, and each device transmits and receives information via a network N such as the Internet.

[0011] The management device 1 is an information processing device that processes, stores, and transmits / receives various types of information. The management device 1 is, for example, a server device, a personal computer, etc. In this embodiment, the management device 1 is a server device, and for the sake of brevity, will be referred to as server 1 below.

[0012] The entrance reception terminal 2 is a terminal device that reads an entrance code describing an entrance ID, which is an identifier for an entrance to an event, and obtains and displays the number of people staying in the event venue. The entrance reception terminal 2 is an information processing device, such as a smartphone, a tablet, a terminal device equipped with a dedicated reading module capable of reading codes, or a fixed-installed code reading terminal that reads codes.

[0013] For example, the entrance reception terminal 2 reads the code to check the admission of visitors based on the number of visitors limited for each event, such as an exhibition event where multiple exhibitors set up booths. Note that the event is not limited to an exhibition event, and may be other events such as a lecture or live music concert. The entrance reception terminal 2 is operated, for example, by the event organizer, and reads the code at a specified reception desk installed at the event venue. For example, the entrance reception terminal 2 is lent to a person in charge of the event organizer when the event is held, and is returned after the event is over.

[0014] The display device 3 is a display device that displays the congestion status within the event venue based on the number of people staying there. The display device 3 is, for example, a liquid crystal display or an organic EL (electroluminescence) display. If the display device 3 has a built-in speaker, it can play audio data such as the congestion status within the event venue or a notification when entry resumes. For example, the display device 3 may be installed at the entrance to the event venue to inform visitors of the congestion status within the venue.

[0015] In this embodiment, the server 1 pre-registers (stores) information about attendees (applicants) entering the event in association with attendee identification information, and issues an attendee code containing the attendee identification information to the attendee in advance.

[0016] When the entrance reception terminal 2 reads the entrance identification information from the entrance code issued by the server 1 to the entrance, it transmits authentication information including the read entrance identification information to the server 1. The server 1 calculates the number of people staying in the event venue and judges whether or not the calculated number of people staying reaches the limit number of people allowed to enter the event. When the server 1 determines that the number of people staying has reached the limit number, it transmits refusal information to the entrance reception terminal 2 to reject authentication (entry reception) through the entrance reception terminal 2. When the server 1 determines that the number of people staying has not reached the limit number, it judges whether or not to permit entry of the entrance person based on the authentication information.

[0017] If the server 1 determines that entry is permitted, it acquires attendee information. The server 1 transmits the number of people staying in the event venue and the acquired attendee information to the entrance reception terminal 2. The entrance reception terminal 2 receives and displays the number of people staying and the attendee information transmitted from the server 1. If the server 1 determines that entry is not permitted, it transmits an error message to the entrance reception terminal 2 including a message to the effect that entry is not permitted. The entrance reception terminal 2 receives and displays the error message transmitted from the server 1.

[0018] 2 is a block diagram showing an example of the configuration of the server 1. The server 1 includes a control unit 11, a storage unit 12, a communication unit 13, an input unit 14, a display unit 15, a reading unit 16, a large-capacity storage unit 17, and a clock unit 18. Each component is connected by a bus B.

[0019] The control unit 11 includes an arithmetic processing device such as a CPU (Central Processing Unit), an MPU (Micro-Processing Unit), and a GPU (Graphics Processing Unit), and performs various information processing, control processing, and the like related to the server 1 by reading and executing a control program 1P stored in the storage unit 12. Note that, although the control unit 11 is described in Fig. 2 as being a single processor, it may be a multiprocessor.

[0020] The storage unit 12 includes memory elements such as RAM (Random Access Memory) and ROM (Read Only Memory), and stores the control program 1P or data required for the control unit 11 to execute processing. The storage unit 12 also temporarily stores data required for the control unit 11 to execute arithmetic processing. The communication unit 13 is a communication module for performing communication-related processing, and transmits and receives information between the entrance reception terminal 2, the display device 3, etc. via the network N.

[0021] The input unit 14 is an input device such as a mouse, a keyboard, a touch panel, or a button, and outputs received operation information to the control unit 11. The display unit 15 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 11.

[0022] The reading unit 16 reads the portable storage medium 1a including a CD (Compact Disc)-ROM or a DVD (Digital Versatile Disc)-ROM. The control unit 11 may read the control program 1P from the portable storage medium 1a via the reading unit 16 and store it in the mass storage unit 17. The control unit 11 may also download the control program 1P from another computer via a network N or the like and store it in the mass storage unit 17. Furthermore, the control unit 11 may read the control program 1P from the semiconductor memory 1b.

[0023] The mass storage unit 17 includes a recording medium such as an HDD (Hard disk drive) or an SSD (Solid State Drive). The mass storage unit 17 includes an event DB (database) 171, an attendee DB 172, and an entrance / exit management DB 173. The event DB 171 stores information related to events. The attendee DB 172 stores information related to attendees. The entrance / exit management DB 173 stores information related to entrance / exit of the event.

[0024] In this embodiment, the storage unit 12 and the large-capacity storage unit 17 may be configured as an integrated storage device. The large-capacity storage unit 17 may be configured with a plurality of storage devices. Furthermore, the large-capacity storage unit 17 may be an external storage device connected to the server 1.

[0025] Clock unit 18 is a circuit that keeps track of time or elapsed time, etc., and provides the control unit 11 with the timekeeping result in response to a request from control unit 11. Clock unit 18 also provides a timer function. The timer function is a function that notifies control unit 11 when a preset time has elapsed since a start command was received. Alternatively, the timer function is a function that responds to an inquiry from control unit 11 as to whether a preset time has elapsed since a start command was received.

[0026] In this embodiment, the server 1 is described as being one information processing device, but the processing may be distributed among a plurality of devices, or the server 1 may be configured as a virtual machine.

[0027] 3 is an explanatory diagram showing an example of a record layout of the event DB 171. The event DB 171 stores an event ID column, an event name column, an event location column, an event date column, an event start time column, an event end time column, an application start date and time column, an application end date and time column, a reception start time column, a reception end time column, and an admission limit number column.

[0028] The event ID column stores a unique event ID to identify each event. The event name column stores the name of the event. The venue column stores the location where the event is held. The date column stores the date on which the event is held. The start time column stores the start time of the event. The end time column stores the end time of the event. The application start date and time column stores the start date and time for applying for the event. The application end date and time column stores the end date and time for applying for the event. The acceptance start time column stores the start time for accepting applications for the event. The acceptance end time column stores the end time for accepting applications for the event. The admission limit column stores the limit on the number of people allowed to enter the event.

[0029] FIG. 4 is an explanatory diagram showing an example of the record layout of the visitor DB 172 and the entrance / exit management DB 173. As shown in FIG. The attendee DB 172 stores an attendee ID column, an event ID column, an attendee number column, a name column, a company name column, an attribute column, an application status column, and a reception status column. The attendee ID column stores an attendee ID that is uniquely specified to identify each attendee. The event ID column stores an event ID that specifies the event. The attendee number column stores the number of attendees who have entered an event according to one attendee ID. One attendee ID can be used by multiple attendees (multiple people) at the same time.

[0030] The name column stores the name of the attendee. The company name column stores the name of the company to which the attendee belongs. The attribute column stores attribute information according to the attributes of the attendee. For example, if the event is a product exhibition, the attribute information can be expressed as "VIP (Very Important Person) member," "customer who purchased product A," etc. The application status column stores the application status for entry to the event. For example, "applied," "cancelled," etc. are stored in the application status column. The reception status column stores the reception status of the attendee. For example, "entered," "not received," etc. are stored in the reception status column.

[0031] The entrance / exit management DB173 stores an event ID column, a visitor ID column, an entrance date / time column, a visitor number column, an exit date / time column, and an exit number column. The event ID column stores an event ID that identifies an event. The visitor ID column stores a visitor ID that identifies a visitor. The entrance date / time column stores information on the date and time when a visitor entered. The visitor number column stores the number of visitors who entered an event according to one visitor ID.

[0032] The exit date and time column stores the date and time when an exiting person (attendee who is to be exited) exited the event. The exiting person number column stores the number of people who exited the event. When one attendee uses one attendee ID, the exiting person number column stores "1." Also, when multiple attendees use one attendee ID at the same time, the exiting person number column stores the actual number of people who exited corresponding to that attendee ID.

[0033] The above-mentioned storage formats of each DB are merely examples, and other storage formats may be used as long as the relationships between the data are maintained.

[0034] 5 is a block diagram showing an example configuration of the entrance reception terminal 2. The entrance reception terminal 2 includes a control unit 21, a storage unit 22, a communication unit 23, an input unit 24, a display unit 25, an imaging unit 26, a code reading unit 27, and a speaker 28. Each component is connected by a bus B.

[0035] The control unit 21 includes an arithmetic processing unit such as a CPU, an MPU, etc., and performs various information processing, control processing, etc. related to the entrance reception terminal 2 by reading and executing a control program 2P stored in the storage unit 22. Note that, although the control unit 21 is described as a single processor in FIG. 5, it may be a multiprocessor. The storage unit 22 includes memory elements such as RAM and ROM, and stores the control program 2P or data, etc., required for the control unit 21 to execute processing. The storage unit 22 also temporarily stores data, etc., required for the control unit 21 to execute arithmetic processing.

[0036] The communication unit 23 is a communication module for performing communication-related processing using a wireless wide area network (WAN) or the like, and transmits and receives information to and from the server 1 or the like via the network N. The input unit 24 may be a keyboard, a mouse, or a touch panel integrated with the display unit 25. The display unit 25 is a liquid crystal display, an organic EL display, or the like, and displays various information according to instructions from the control unit 21.

[0037] The photographing unit 26 is, for example, a photographing device such as a CCD (Charge Coupled Device) camera or a CMOS (Complementary Metal Oxide Semiconductor) camera. The photographing unit 26 may be composed of multiple photographing devices. The photographing unit 26 may not be built into the entrance reception terminal 2, but may be externally connected directly to the entrance reception terminal 2 and configured to be capable of photographing. The code reading unit 27 is a read-only module for reading two-dimensional codes, one-dimensional codes, etc. The speaker 28 is a device that converts an electrical signal into sound.

[0038] FIG. 6 is an explanatory diagram for explaining the operation of the visitor reception system. First, the reception process for admission to an event will be explained. The admission reception terminal 2 reads visitor identification information from a visitor code issued to a visitor who has entered the event. The visitor code is, for example, a two-dimensional code, a one-dimensional code, etc. Alternatively, it may be a form of reading a code stored in an IC tag (Integrated Circuit Tag), an RFID tag (Radio Frequency Identifier Tag), an RFID chip (microchip), etc. A two-dimensional code is a display type code that has information in the horizontal and vertical directions, as opposed to a one-dimensional code that has information only in the horizontal direction. Representative two-dimensional codes are, for example, QR Code (registered trademark), DataMatrix (registered trademark), or VeriCode (registered trademark). An example of a one-dimensional code is a barcode. In this embodiment, an example will be explained in which a two-dimensional code is read. The visitor identification information is, for example, a visitor ID for identifying a visitor. Note that the visitor identification information is not limited to a visitor ID, and may be, for example, information for fingerprint authentication or face authentication.

[0039] When the entrance reception terminal 2 reads the entrance ID from the entrance code, it transmits authentication information including the entrance ID and the event ID to the server 1. The server 1 counts the number of visitors to the event from the entrance number sequence in the entrance / exit management DB 173 based on the received event ID, and counts the number of people leaving the event from the exit number sequence in the entrance / exit management DB 173.

[0040] The server 1 calculates the number of people staying in the event venue based on the total number of visitors and people leaving. The number of people staying is calculated by subtracting the number of people leaving from the number of visitors, and is expressed by the following formula (1). Number of visitors = Number of visitors - Number of visitors leaving …(1)

[0041] The server 1 acquires the limit number of people who can enter the event from the event DB 171 based on the event ID. The server 1 judges whether the number of people entering the event has reached the limit number based on the calculated number of people staying and the acquired limit number. When the server 1 judges that the number of people staying has reached the limit number, it transmits refusal information to the entrance reception terminal 2 to reject authentication (entry reception) through the entrance reception terminal 2. The entrance reception terminal 2 receives the refusal information transmitted from the server 1 and outputs it on a screen. The refusal information may be, for example, a notification message including the fact that entry reception is not possible due to the entrance restriction, or a message ID for identifying the notification message. The refusal information may be an audio signal including the fact that entry reception is not possible. In this case, the entrance reception terminal 2 outputs the audio signal including the fact that entry reception is not possible transmitted from the server 1 through the speaker 28.

[0042] If the server 1 determines that the number of visitors has not reached the limit, it determines whether or not to permit entry of the visitor based on the authentication information. For example, the server 1 determines whether or not the visitor is a duplicate visitor. Specifically, the server 1 acquires the reception status of the visitor from the visitor DB 172 based on the event ID and visitor ID. If the server 1 determines that the acquired reception status is "already entered," it determines that there is a duplicate entry. If the server 1 determines that the acquired reception status is "not applied for," it determines that there is no duplicate entry.

[0043] If the server 1 determines that the visitor is not a duplicate visitor, it determines to permit entry. In this case, the server 1 updates the reception status column of the visitor DB 172 to "entered" based on the event ID and visitor ID. The server 1 stores the entry date and time and the number of visitors (the number of visitors corresponding to the visitor ID) in the entrance and exit management DB 173 in association with the event ID and visitor ID.

[0044] Server 1 acquires attendee information from attendee DB 172 based on the attendee ID. The attendee information includes the attendee's name, the name of the company to which the attendee belongs, or the attendee's attributes (for example, VIP member, customer who purchased product A, etc.). Server 1 transmits the number of people staying in the event venue and the acquired attendee information to admission reception terminal 2. Admission reception terminal 2 receives the number of people staying and the attendee information transmitted from server 1. Admission reception terminal 2 displays the received number of people staying and attendee information on its screen.

[0045] If the server 1 determines that the visitor has entered twice, it determines that the visitor is not permitted to enter. In this case, the server 1 does not transmit visitor information to the entrance reception terminal 2, and transmits an error message to the entrance reception terminal 2 indicating that the visitor is not permitted to enter. The entrance reception terminal 2 receives and displays the error message transmitted from the server 1.

[0046] The process for determining whether to permit entry is not limited to the process for determining whether duplicate entries have occurred described above. For example, if a paid event is held, a process for determining the payment status (e.g., unpaid, paid, or cancellation / refund after payment, etc.) may be performed. If the server 1 determines that the payment status is paid, it permits entry to the visitor. In an event that allows duplicate entries, the process for determining whether duplicate entries have occurred described above may be omitted.

[0047] In the present embodiment, an example has been described in which the authentication process based on the number of visitors is executed on the server 1 side, but this is not limiting and the process may be executed on the entrance reception terminal 2 side. In this case, the entrance reception terminal 2 acquires the number of visitors in the venue of the event and the limit number of people who can enter the event from the server 1 based on the event ID. If the entrance reception terminal 2 determines that the number of visitors has reached the limit number, it rejects authentication through the entrance reception terminal 2. If the entrance reception terminal 2 determines that the number of visitors has not reached the limit number, it permits authentication through the entrance reception terminal 2 and transmits authentication information including the visitor ID and the event ID to the server 1. The server 1 determines whether or not to permit the visitor to enter based on the authentication information transmitted from the entrance reception terminal 2, similar to the above-mentioned process.

[0048] Next, the process of accepting exit from an event will be described. In FIG. 6, there is an exit acceptance terminal 4 that accepts exit from an event. The exit acceptance terminal 4 is, for example, a smartphone, a tablet, a terminal device provided with a dedicated reading module capable of reading codes, or an information processing device such as a fixed-type code reading terminal that reads codes. The entrance acceptance terminal 2 or the exit acceptance terminal 4 may be a stationary code reading terminal equipped with a gate. By using a stationary code reading terminal equipped with a gate, it is possible to realize unmanned entrance and exit acceptance.

[0049] When a person who has entered an event leaves the event, the exit reception terminal 4 accepts the person's exit from the event. For example, the exit reception process is carried out by reading a QR code, similar to the entrance reception process.

[0050] Specifically, the exit reception terminal 4 reads the visitor ID capable of identifying the visitor to be exited from the visitor code. The exit reception terminal 4 transmits exit information including the read visitor ID to the server 1. The server 1 receives the exit information transmitted from the exit reception terminal 4. The server 1 associates the exit date and time and the number of exiting persons (the number of visitors corresponding to the visitor ID at the time of entry) with the visitor ID contained in the received exit information, stores them in the entry / exit management DB 173, and terminates the exit reception process.

[0051] Note that when multiple visitors use one visitor ID at the same time, only some of the multiple visitors may exit the event. In this case, for example, the exit reception terminal 4 accepts input of the actual number of people exiting for the read visitor ID. The exit reception terminal 4 transmits the visitor ID and the accepted actual number of people exiting to the server 1. The server 1 stores the actual number of people exiting in the entrance / exit management DB 173 in association with the visitor ID.

[0052] When the server 1 receives information about an event exit, the server 1 updates the number of people staying in the event venue based on the latest number of people leaving. Specifically, the server 1 counts the number of people entering the event and the number of people leaving the event from the entrance / exit management DB 173 based on the event ID. The server 1 recalculates the number of people staying in the event venue based on the counted number of people entering and leaving using the above-mentioned formula (1).

[0053] The counting process is not limited to the above. For example, the number of people leaving the event may be counted by automatically detecting people (people leaving) using a photographing device installed at the exit (gate) of the event venue. Alternatively, the number of people leaving the event may be counted by detecting people leaving using an infrared sensor, a heat-sensitive sensor, or the like.

[0054] In this embodiment, the entrance reception process and the exit reception process are performed on different terminals, but the present invention is not limited to this. For example, the entrance reception process and the exit reception process may be performed on the same terminal.

[0055] Next, a process of outputting the number of people staying in the venue and the congestion state in the venue to the display device 3 will be described. The server 1 outputs the number of people staying in the event venue and the congestion state in the venue determined based on the number of people staying at every predetermined time interval (e.g., 30 seconds or 1 minute) to the display device 3. The server 1 may also output the number of people staying in the event venue and the congestion state in real time to the display device 3.

[0056] Specifically, the server 1 calculates the number of people staying in the event venue, and judges the congestion state in the venue based on the calculated number of people staying. For example, the server 1 may judge the congestion state into four stages, "not crowded (entry allowed)", "slightly crowded", "crowded", and "full", based on the congestion level assigned to the number of people staying. When the limit number of people who can enter event A is 200, for example, if the number of people staying is less than 160, the congestion state is "not crowded (entry allowed)". If the number of people staying is 160 or more and less than 180, the congestion state is "slightly crowded". If the number of people staying is 180 or more and less than 200, the congestion state is "crowded". If the number of people staying reaches 200, the congestion state is "full".

[0057] Alternatively, the congestion status may be determined based on the ratio between the number of visitors and the limited number of visitors (capacity). For example, when the number of visitors is 60% or less of the capacity, the congestion status is "not crowded (entry allowed)". When the number of visitors is 60% or more of the capacity and 80% or less of the capacity, the congestion status is "slightly crowded". When the number of visitors is 80% or more of the capacity and less than 100% of the capacity, the congestion status is "crowded". When the number of visitors is 100% of the capacity, the congestion status is "full".

[0058] The server 1 transmits, at predetermined time intervals or in real time, the calculated number of visitors in the event venue and the congestion state determined based on the number of visitors to the display device 3. The display device 3 receives the number of visitors and the congestion state transmitted from the server 1, and displays the received number of visitors and the congestion state on the screen (FIG. 7).

[0059] FIG. 7 is an explanatory diagram showing an example of a display screen showing the number of people staying in an event venue and the congestion status. FIG. 7A is an explanatory diagram showing an example of a display screen in which the congestion status is "entry permitted". As an example of congestion levels set in four stages assigned to the number of people staying described above, when the number of people staying is 150, the server 1 determines that the congestion status is "entry permitted". The server 1 transmits the number of people staying in the event venue and the congestion status of "entry permitted" to the display device 3. The display device 3 receives the number of people staying and the congestion status transmitted from the server 1 and displays them on the screen (FIG. 7A).

[0060] Fig. 7B is an explanatory diagram showing an example of a display screen in which the congestion status is "full". If the number of visitors is 200, the server 1 determines that the congestion status is "full". The server 1 transmits the number of visitors in the event venue and the congestion status that is "full" to the display device 3. The display device 3 receives the number of visitors and the congestion status transmitted from the server 1 and displays them on the screen (Fig. 7B).

[0061] The display device 3 communicates with the server 1 at a predetermined time interval or in real time to obtain the latest number of visitors and congestion status, and updates the obtained latest number of visitors and congestion status on the screen. In this way, it is possible to always inform visitors of the latest congestion status within the event venue.

[0062] 8 is an explanatory diagram showing an example of the entrance reception screen. The entrance reception screen is a display screen that accepts the entrance of visitors through the entrance reception terminal 2. The entrance reception screen includes a visitor number display field 11a, a switching button 11b, an object 11c, and an update button 11d.

[0063] The number of visitors display field 11a is a display field for displaying the number of people staying at the event venue. The switch button 11b is a button for switching the reading mode. The reading modes include a code reading mode for reading an attendee code, and a direct input mode for directly inputting an attendee ID (attendee ticket ID). The object 11c is a button or text field for accepting the attendee ID. In the direct input mode, the object 11c is a text field for inputting the attendee ID. In the code reading mode, the object 11c changes to a button for reading a two-dimensional code. The update button 11d is a button for updating the number of visitors.

[0064] When the attendee reception system is started or the reception screen is initially displayed, the entrance reception terminal 2 obtains the latest number of visitors in the event venue from the server 1 and displays it on the screen. Specifically, the entrance reception terminal 2 transmits an event ID to the server 1. Based on the event ID transmitted from the entrance reception terminal 2, the server 1 counts the number of visitors to the event and the number of visitors leaving the event from the entrance and exit management DB 173. Based on the counted number of visitors and the number of visitors leaving, the server 1 calculates the number of visitors using the above-mentioned formula (1). The server 1 transmits the calculated number of visitors to the entrance reception terminal 2. The entrance reception terminal 2 receives the number of visitors transmitted from the server 1 and displays the received number of visitors in the visitor number display field 11a.

[0065] In the code reading mode, when the admission reception terminal 2 receives a touch (click) operation of the switching button 11b, the object 11c changes from a two-dimensional code read button in the code reading mode to a text field in the direct input mode. In the direct input mode, when the admission reception terminal 2 receives a touch operation of the switching button 11b, the object 11c changes from a text field in the direct input mode to a two-dimensional code read button in the code reading mode.

[0066] When the entrance reception terminal 2 reads the entrance code by the object 11c in the reading mode, or when the entrance reception terminal 2 acquires the entrance ID input by the object 11c in the direct input mode, the entrance reception terminal 2 transmits authentication information including the entrance ID and the event ID to the server 1. The server 1 counts the number of entrances to the event and the number of exits from the event from the entrance and exit management DB 173 based on the received event ID. The server 1 calculates the number of people staying in the event venue using the above-mentioned formula (1) based on the counted number of entrances and exits. The server 1 judges whether the calculated number of people staying has reached the limit number stored in the event DB 171. When the server 1 judges that the number of people staying has reached the limit number, the server 1 transmits refusal information to the entrance reception terminal 2 to reject authentication through the entrance reception terminal 2. The entrance reception terminal 2 receives the refusal information transmitted from the server 1 and outputs it to the screen. The refusal information may be, for example, a notification message including a notice that admission is not possible due to an admission restriction.

[0067] If the server 1 determines that the number of visitors has not reached the limit, it determines whether or not to permit entry of the visitor based on the authentication information. If the server 1 determines to permit entry, it acquires visitor information (such as the visitor's name, the name of the company to which the visitor belongs, or the visitor's attributes) from the visitor DB 172 based on the visitor ID. The server 1 transmits the number of visitors in the event venue and the acquired visitor information to the entrance reception terminal 2. The entrance reception terminal 2 receives the number of visitors and the visitor information transmitted from the server 1. The entrance reception terminal 2 displays the received number of visitors and visitor information on the screen.

[0068] When the server 1 determines that entry is not permitted, it does not transmit the visitor information to the entrance reception terminal 2, and transmits an error message including the fact that entry is not permitted to the entrance reception terminal 2. The entrance reception terminal 2 receives and displays the error message transmitted from the server 1.

[0069] When the admission reception terminal 2 receives a touch operation of the update button 11d, it acquires the latest number of visitors in the event venue from the server 1, similar to the above-mentioned process of acquiring the number of visitors. The admission reception terminal 2 displays the acquired latest number of visitors in the visitor number display field 11a. The admission reception terminal 2 may automatically update the number of visitors displayed on the screen by reacquiring the number of visitors from the server 1 at a predetermined time interval (for example, 5 minutes) without going through the update button 11d. If the congestion situation in the event venue is "crowded" or "full", the admission reception terminal 2 may shorten the time interval for updating the number of visitors. For example, the predetermined time interval is shortened from 5 minutes to 3 minutes. The admission reception terminal 2 may acquire the number of visitors from the server 1 in real time without going through the update button 11d, and display the acquired number of visitors in the visitor number display field 11a.

[0070] 9 and 10 are flow charts showing the processing procedure when performing authentication through the entrance reception terminal 2. The control unit 21 of the entrance reception terminal 2 reads an attendee code (e.g., a QR code) issued to an attendee who has entered an event, via the photographing unit 26 or the code reading unit 27 (step S201). The control unit 21 acquires an attendee ID from the read attendee code (step S202). The control unit 21 transmits authentication information including the attendee ID and the event ID to the server 1 via the communication unit 23 (step S203). The control unit 11 of the server 1 receives the authentication information transmitted from the entrance reception terminal 2 via the communication unit 13 (step S101).

[0071] Based on the received event ID, the control unit 11 counts the number of people entering the event from the entry and exit management DB 173 of the mass storage unit 17 (step S102), and counts the number of people leaving the event from the exit management DB 173 (step S103). Based on the counted number of people entering and leaving, the control unit 11 calculates the number of people staying in the event venue using the above-mentioned formula (1) (step S104). Based on the event ID, the control unit 11 obtains the limit number of people who can enter the event from the event DB 171 of the mass storage unit 17 (step S105). Note that the order of the processing of steps S102 to 105 is not limited, and for example, the control unit 11 may first perform the processing of step S105 (obtaining the limit number of people) and then perform the processing of step S102.

[0072] The control unit 11 judges whether the calculated number of visitors reaches the limit number of people who can enter the event (step S106). When the control unit 11 judges that the number of visitors reaches the limit number (YES in step S106), it transmits refusal information (for example, a notification message or message ID including the fact that entry is not accepted) that rejects authentication through the entrance reception terminal 2 to the entrance reception terminal 2 via the communication unit 13 (step S107). The control unit 21 of the entrance reception terminal 2 receives the refusal information transmitted from the server 1 via the communication unit 23 (step S204), and displays the received refusal information on the display unit 25 (step S205).

[0073] When the control unit 11 determines that the number of visitors has not reached the limit (NO in step S106), it determines whether or not to permit entry of the visitor based on authentication information including the visitor ID and event ID, etc. (step S108). For example, it checks whether the visitor has entered twice, and permits entry of the visitor if there is no double entry.

[0074] When the control unit 11 determines that the visitor is not permitted to enter (NO in step S108), it transmits an error message including the fact that the visitor is not permitted to enter to the entrance reception terminal 2 via the communication unit 13 (step S109). The control unit 21 of the entrance reception terminal 2 receives the error message transmitted from the server 1 via the communication unit 23 (step S206), and displays the received error message on the display unit 25 (step S207).

[0075] When the control unit 11 determines that the visitor should be permitted to enter (YES in step S108), it updates the visitor DB 172 and the entrance / exit management DB 173 in the mass storage unit 17 (step S110). Specifically, the control unit 11 updates the reception status column in the visitor DB 172 to "entered" based on the event ID and visitor ID. Based on the event ID and visitor ID, the control unit 11 obtains from the visitor DB 172 the number of visitors corresponding to the visitor ID. The control unit 11 associates the entry date and time and the obtained number of visitors in the entrance / exit management DB 173 with the event ID and visitor ID.

[0076] Based on the attendee ID, the control unit 11 acquires attendee information including the attendee's name, the name of the company to which the attendee belongs, or the attendee's attributes from the attendee DB 172 (step S111). The control unit 11 transmits the number of people staying in the event venue and the acquired attendee information to the entrance reception terminal 2 via the communication unit 13 (step S112). The entrance reception terminal 2 receives the number of people staying and the attendee information transmitted from the server 1 via the communication unit 23 (step S208). The control unit 21 displays the received number of people staying and the attendee information on the display unit 25 (step S209) and ends the process.

[0077] 11 is a flowchart showing the process for outputting the number of people staying in the venue and the congestion state. The control unit 11 of the server 1 determines whether or not a predetermined time (e.g., one minute) has elapsed via the clock unit 18 (step S121). If the control unit 11 determines that the predetermined time has not elapsed (NO in step S121), the control unit 11 waits. If the control unit 11 determines that the predetermined time has elapsed (YES in step S121), the control unit 11 calculates the number of people staying in the event venue based on the number of people entering and leaving (step S122).

[0078] The control unit 11 determines the congestion state in the venue based on the calculated number of visitors (step S123). For example, the control unit 11 may determine the congestion state based on the congestion level assigned to the number of visitors. The control unit 11 transmits the calculated number of visitors and the determined congestion state to the display device 3 via the communication unit 13 (step S124). The display device 3 receives the number of visitors and the congestion state transmitted from the server 1 (step S321), displays the received number of visitors and congestion state (step S322), and ends the process. Note that the process is not limited to outputting the number of visitors and the congestion state in the venue to the display device 3 at predetermined time intervals, and the server 1 may output the number of visitors and the congestion state in the venue to the display device 3 in real time.

[0079] According to this embodiment, by accepting entry based on the number of people staying in the venue and the limited number of people allowed to enter, if there are restrictions on holding the event (occupancy rate, maximum number of people, etc.), it is possible to limit the number of people that can be accommodated in the event venue.

[0080] According to this embodiment, when the number of people in the venue reaches the limit of the number of people who can enter, it is possible to temporarily suspend the admission reception.

[0081] According to this embodiment, when the number of people in the venue falls below the limit of the number of people who can enter, it is possible to resume admission reception.

[0082] According to this embodiment, it is possible to output the number of people staying in the venue and the congestion state to the display device 3 in real time.

[0083] (Embodiment 2) The second embodiment relates to a form in which entry to an event is accepted based on a second limit number of people who can enter the event. The second limit number of people (the number of people at which entry acceptance is resumed) is a number smaller than the first limit number of people that is set based on the limit number of people who can enter the event (first limit number of people). Note that a description of the contents that overlap with the first embodiment will be omitted.

[0084] In the first embodiment, when the number of people staying in the event venue reaches the first limit number of people who are allowed to enter, admission is restricted (admission acceptance is temporarily suspended), and when the number of people staying in the venue falls below the first limit number, the admission restriction is lifted (admission acceptance is resumed). In the present embodiment, when the number of people staying in the venue reaches the first limit number, admission is restricted, and when the number of people staying in the venue falls below the second limit number, the admission restriction is lifted. For example, when the second limit number is 80% of the first limit number, the second limit number is 80 people (100 x 0.8) when the first limit number is 100 people.

[0085] The entrance reception terminal 2 transmits authentication information including an attendee ID and an event ID to the server 1. The server 1 calculates the number of people staying in the event venue based on the number of attendees and the number of people leaving. The server 1 determines whether the number of people staying in the event venue has reached a first limit. If the server 1 determines that the number of people staying in the venue has reached the first limit, it transmits refusal information to the entrance reception terminal 2 to reject authentication (entrance reception) through the entrance reception terminal 2.

[0086] As people leave the event, the number of people staying in the event venue decreases. The server 1 calculates the latest number of people staying in the event venue at a predetermined time interval or in real time. The server 1 acquires the second limit number of people who can enter the event. For example, if the second limit number of people is stored in the storage unit 12, the server 1 acquires the second limit number of people from the storage unit 12. Alternatively, if a calculation rule for the second limit number of people is stored in the storage unit 12, the server 1 acquires the calculation rule for the second limit number of people from the storage unit 12 and calculates the second limit number of people based on the acquired calculation rule for the second limit number of people. For example, if the calculation rule for the second limit number of people is "second limit number of people: 80% of the first limit number of people", the second limit number of people is calculated as 80 people for the first limit number of people of 100 people. The setting of the second limit number of people can be changed from the server 1, the entrance reception terminal 2, or another information processing device.

[0087] The server 1 determines whether or not the admission restriction can be lifted based on the latest calculated number of visitors and the second limit number of visitors. Specifically, when the server 1 determines that the number of visitors is equal to or less than the second limit number of visitors, it determines that the admission restriction can be lifted. When the server 1 determines that the admission restriction can be lifted, it transmits a message including the effect that the admission restriction has been lifted to the entrance reception terminal 2. In this way, because the second limit number of visitors is set to be smaller than the first limit number of visitors, the admission restriction can be lifted once the event venue has become sufficiently vacant.

[0088] 12 is a flow chart showing the processing procedure when accepting admission based on the second number limit. The control unit 11 of the server 1 receives authentication information including an admission ID and an event ID transmitted from the admission acceptance terminal 2 via the communication unit 13 (step S131). The control unit 11 calculates the number of people staying in the event venue based on the number of admissions and the number of exits (step S132). The control unit 11 obtains the first number limit that is permitted to enter the event from the event DB 171 in the mass storage unit 17 (step S133).

[0089] The control unit 11 determines whether the calculated number of visitors has reached the first limit (step S134). If the control unit 11 determines that the number of visitors has not reached the first limit (NO in step S134), it executes the processes of steps S141 to S145. Note that the processes of steps S141 to S145 are the same as the processes of steps S108 to S112, and therefore a description thereof will be omitted.

[0090] When the control unit 11 determines that the number of people staying has reached the first limit number (YES in step S134), it transmits refusal information to the entrance reception terminal 2 via the communication unit 13 to reject authentication through the entrance reception terminal 2 (step S135). The control unit 11 determines whether or not a predetermined time (e.g., 2 minutes) has elapsed (step S136). When the control unit 11 determines that the predetermined time has not elapsed (NO in step S136), the control unit 11 waits. When the control unit 11 determines that the predetermined time has elapsed (YES in step S136), it recalculates the number of people staying in the event venue based on the number of people entering and leaving (step S137).

[0091] The control unit 11 acquires the second limit number of people who can enter the event (step S138). For example, if the calculation rule for the second limit number of people is stored in the storage unit 12, the control unit 11 acquires the calculation rule for the second limit number of people from the storage unit 12 and acquires the second limit number of people based on the acquired calculation rule for the second limit number of people. The control unit 11 judges whether the recalculated number of people visiting is equal to or less than the second limit number of people (step S139). If the control unit 11 judges that the number of people visiting exceeds the second limit number of people (NO in step S139), the process returns to step S136. If the control unit 11 judges that the number of people visiting is equal to or less than the second limit number of people (YES in step S139), the control unit 11 transmits a message including the fact that the admission restriction has been lifted to the admission reception terminal 2 via the communication unit 13 (step S140), and returns to the process of step S131.

[0092] According to this embodiment, it is possible to accept entry to the event based on the second limit number of people who are permitted to enter the event.

[0093] According to this embodiment, the second limit on the number of people allowed to enter the event is set lower than the first limit on the number of people allowed to enter the event, making it possible to avoid large numbers of attendees gathering in the event venue.

[0094] (Embodiment 3) The third embodiment relates to a form in which a notification of admission restriction or admission restriction lifting (admission resumption) is output to the admission reception terminal 2. Note that a description of the contents that overlap with the first and second embodiments will be omitted. When admission restriction to an event is implemented, a notification of the admission restriction is transmitted to the admission reception terminal 2. Also, when admission restriction to an event is lifted, a notification of the admission restriction lifting is transmitted to the admission reception terminal 2.

[0095] Fig. 13 is an explanatory diagram showing an example of a display screen for a notification of admission restriction or admission restriction lifting. Note that the same reference numerals are used for the contents that overlap with Fig. 8, and the description will be omitted. The display screen for the notification includes a notification dialog 11e. The notification dialog 11e is a dialog for displaying a notification of admission restriction or admission restriction lifting. The notification includes a notification message, the number of people staying, or the limit on the number of people (capacity), etc.

[0096] The server 1 monitors the admission reception status at a predetermined time interval or in real time. Specifically, for example, when the server 1 determines that a predetermined time (for example, 5 minutes) has elapsed, it counts the number of people entering the event and the number of people leaving the event from the admission / exit management DB 173 based on the event ID. The server 1 calculates the number of people staying in the event venue based on the counted number of people entering and the number of people leaving. The server 1 determines whether admission to the event has been restricted based on the calculated number of people staying and the limit on the number of people who can enter the event. When the server 1 determines that admission has been restricted, it transmits a notification of the admission restriction to the admission reception terminal 2. The admission reception terminal 2 receives the notification of the admission restriction transmitted from the server 1 and displays it in the notification dialog 11e.

[0097] When admission to an event is restricted, the server 1 recalculates the number of people staying in the event venue after a predetermined time (e.g., 3 minutes) has elapsed. The server 1 determines whether the admission restriction has been lifted based on the recalculated number of people staying and the limit number of people who can enter. If the server 1 determines that the admission restriction has been lifted, it transmits a notification of the admission restriction lift to the admission reception terminal 2. The admission reception terminal 2 receives the notification of the admission restriction lift sent from the server 1 and displays it in the notification dialog 11e. As shown in the figure, a notification message including the fact that the admission restriction has been lifted, such as "Admission has resumed," the number of people staying, and the limit number of people (capacity) are displayed in the notification dialog 11e.

[0098] 14 is a flowchart showing the processing procedure when sending a notification of admission restriction or admission restriction lifting. The control unit 11 of the server 1 acquires the limit number of people who can enter the event from the event DB 171 based on the event ID (step S151). The control unit 11 determines whether or not a predetermined time has elapsed (step S152). If the control unit 11 determines that the predetermined time has not elapsed (NO in step S152), the control unit 11 waits.

[0099] When the control unit 11 determines that a predetermined time has elapsed (YES in step S152), it calculates the number of people staying in the event venue (step S153). Based on the calculated number of people staying and the limit number of people who can enter the event, the control unit 11 determines whether or not entry to the event has been restricted (step S154). Specifically, when the calculated number of people staying reaches the limit number of people who can enter, the control unit 11 determines that entry to the event has been restricted.

[0100] When the control unit 11 determines that admission to the event is not restricted (NO in step S154), the process returns to step S152. When the control unit 11 determines that admission to the event is restricted (YES in step S154), the control unit 11 transmits a notification of admission restriction including a notification message, the number of people staying, or the limited number of people, to the entrance reception terminal 2 via the communication unit 13 (step S155).

[0101] The control unit 21 of the entrance reception terminal 2 receives the admission restriction notification transmitted from the server 1 through the communication unit 23 (step S251). The control unit 21 displays the received admission restriction notification on the display unit 25 (step S252).

[0102] After executing the process of step S155, the control unit 11 of the server 1 determines whether or not a predetermined time has elapsed (step S156). If the control unit 11 determines that the predetermined time has not elapsed (NO in step S156), the control unit 11 waits. If the control unit 11 determines that the predetermined time has elapsed (YES in step S156), the control unit 11 recalculates the number of people staying in the event venue (step S157).

[0103] The control unit 11 judges whether the admission restriction has been lifted based on the recalculated number of people staying and the limit number of people who can enter (step S158). Specifically, the control unit 11 judges that the admission restriction to the event has been lifted if the recalculated number of people staying does not reach the limit number of people who can enter. If the control unit 11 judges that the admission restriction has not been lifted (NO in step S158), it returns to the processing of step S156. If the control unit 11 judges that the admission restriction has been lifted (YES in step S158), it transmits a notice of admission restriction lift including a notification message, the number of people staying, or the limit number of people, etc. to the entrance reception terminal 2 via the communication unit 13 (step S159).

[0104] The control unit 21 of the entrance reception terminal 2 receives the admission restriction lift notification transmitted from the server 1 via the communication unit 23 (step S253). The control unit 21 displays the received admission restriction lift notification on the display unit 25 (step S254).

[0105] According to this embodiment, by outputting a notification of admission restriction or admission restriction lift to the admission reception terminal 2, it becomes possible for the person in charge of the event or the secretariat to grasp the admission reception situation within the venue in real time.

[0106] (Embodiment 4) The fourth embodiment relates to a form in which admission to a sub-event held in the venue of an event is accepted based on a limit on the number of people who can enter the sub-event. Note that a description of the contents that overlap with the first to third embodiments will be omitted.

[0107] Fig. 15 is a block diagram showing an example of the configuration of the server 1 of the fourth embodiment. The same reference numerals are used for the same contents as in Fig. 2, and the description thereof will be omitted. The mass storage unit 17 stores a sub-event DB 174. The sub-event DB 174 stores information about sub-events held within the event venue.

[0108] 16 is an explanatory diagram showing an example of the record layout of the visitor DB 172, the entrance / exit management DB 173, and the sub-event DB 174 in the embodiment 4. Note that a description of the contents that overlap with FIG.

[0109] The attendee DB 172 includes a sub-event ID column, a sub-event application status column, and a sub-event reception status column. The sub-event ID column stores a sub-event ID that uniquely identifies a sub-event held within the event venue. The sub-event application status column stores the application status for admission to the sub-event. The sub-event reception status column stores the reception status of the sub-event for the attendee.

[0110] The entrance / exit management DB 173 includes a sub-event ID column, which stores a sub-event ID that uniquely identifies a sub-event held within the venue of the event.

[0111] The sub-event DB 174 stores an event ID column, a sub-event ID column, a sub-event name column, and an admission limit column. The event ID column stores an event ID for identifying an event. The sub-event ID column stores a sub-event ID for uniquely identifying a sub-event held within the event venue. The sub-event name column stores the name of the sub-event. The admission limit column stores the limit on the number of people allowed to enter the sub-event.

[0112] FIG. 17 is an explanatory diagram showing an example of an event and a sub-event held within the venue of the event. An attendee who enters an event reads an attendee code at a predetermined reception desk installed at the event venue, receives admission authentication, and enters the event venue. After that, the attendee participates in each sub-event (for example, an exhibition booth or a seminar within the event). As shown in the figure, sub-event A and sub-event B are held within the event venue. Here, the organizer (exhibitor) of each sub-event also receives a sub-event admission reception terminal 5 from the event organizer and reads an attendee code. Then, the admission reception terminal 5 for each sub-event determines whether or not to permit authentication through the admission reception terminal 5 for each sub-event based on the limit number of people who can enter each sub-event. Note that the hardware configuration of the admission reception terminal 5 for the sub-event is similar to that of the admission reception terminal 2, so a description thereof will be omitted.

[0113] Specifically, the admission reception terminal 5 for the sub-event reads the admission ID from the admission code issued to the admission person. The admission code may be a code that can be commonly used for the event or the sub-event, or may be a code issued for each sub-event. When the admission reception terminal 5 for the sub-event reads the admission ID from the admission code, it transmits authentication information including the admission ID, the event ID, and the sub-event ID to the server 1. The server 1 receives the authentication information transmitted from the admission reception terminal 5 for the sub-event. Based on the received event ID and sub-event ID, the server 1 counts the number of admissions to the sub-event from the admission number sequence in the entrance / exit management DB 173, and counts the number of exiting people from the sub-event from the exiting people sequence in the entrance / exit management DB 173.

[0114] The server 1 calculates the number of people staying in the venue of the sub-event using the formula (1) in the first embodiment based on the counted number of people entering and leaving. The server 1 acquires the limit number of people who can enter the sub-event from the sub-event DB 174 based on the event ID and the sub-event ID. The server 1 determines whether the calculated number of people staying at the sub-event reaches the acquired limit number of people for the sub-event. If the server 1 determines that the number of people staying at the sub-event reaches the limit number, it transmits refusal information to the admission reception terminal 5 for the sub-event to reject authentication (admission reception) via the admission reception terminal 5 for the sub-event.

[0115] If the server 1 determines that the number of visitors to the sub-event has not reached the limit, it determines whether or not to permit the visitor to enter based on the authentication information transmitted from the sub-event admission reception terminal 5. Note that the admission admission determination process is the same as in the first embodiment, and therefore a description thereof will be omitted.

[0116] In addition to the above-mentioned limit on the number of people who can enter the sub-event (first limit on the number of people), a second limit on the number of people who can enter each sub-event may be set. In this case, admission to each sub-event is accepted based on the second limit on the number of people who can enter each sub-event. Specifically, when the number of people staying at the sub-event reaches the first limit on the number of people, admission is restricted, and when the number of people staying at the sub-event falls below the second limit on the number of people, the admission restriction is lifted. Note that the admission acceptance process using the second limit on the number of people is the same as in the second embodiment, and therefore a description thereof will be omitted.

[0117] As in the first embodiment, a display device 3 is installed at the entrance of the event to inform visitors of the congestion status within the event venue. The display device 3 displays on a screen the number of visitors and the congestion status within the event venue transmitted from the server 1 at predetermined time intervals or in real time. In this embodiment, there are multiple display devices 6 for sub-events that can inform visitors of the congestion status of each sub-event. For example, a display device 6 for sub-events may be installed at the entrance of each sub-event.

[0118] The display device 6 for sub-events, which is installed at the entrance of each sub-event, displays on its screen the number of visitors and the congestion status of that sub-event transmitted from the server 1 at predetermined time intervals or in real time. Specifically, for example, the server 1 calculates the number of visitors to each sub-event at each predetermined time interval, and determines the congestion status of each sub-event based on the calculated number of visitors. The server 1 transmits the number of visitors and the congestion status of each sub-event to the display device 6 for sub-events, which is installed at the entrance of each sub-event. The display device 6 for each sub-event receives the number of visitors and the congestion status of that sub-event transmitted from the server 1, and displays them on its screen.

[0119] Incidentally, the number of people staying in the event venue and the congestion state, and the number of people staying in each sub-event and the congestion state may be displayed on the display device 3 without installing a display device 6 for the sub-event.

[0120] According to this embodiment, admission to each sub-event held within the event venue is accepted based on the limited number of people permitted to attend each sub-event, making it possible to limit the number of people that can be accommodated at each individual sub-event.

[0121] The embodiments disclosed herein are illustrative in all respects and should not be considered as limiting. The scope of the present invention is defined by the claims, not by the above meaning, and is intended to include all modifications within the scope and meaning equivalent to the claims. [Explanation of symbols]

[0122] 1 Management device (server) 11 Control section 12 Storage section 13. Communications Department 14 Input section 15 Display 16 Reading unit 17 Mass storage 171 Event DB 172 Attendee DB 173 Entrance / Exit Management DB 174 Sub-event DB 18 Clock section 1a Removable storage media 1b Semiconductor memory 1P control program 2. Admission reception terminal 21 Control section 22 Memory section 23 Communications Department 24 Input section 25 Display section 26 Photography Department 27 Code reader 28 Speaker 2P control program 3 Display device 4. Exit reception terminal 5. Admission reception terminal for sub-events 6 Display device for sub-events

Claims

1. An information processing method executed by an information processing device that manages an event where admission of visitors is accepted by a reception terminal, comprising: a step of counting the number of visitors whose entry has been accepted by the reception terminal as a number of visitors; tallying the number of people leaving the event; calculating the number of people staying in the venue of the event at predetermined intervals based on the counted number of visitors and the number of people leaving; determining whether or not a limit on the number of people that can enter the event has been reached based on the calculated number of people; a step of notifying the reception terminal of a refusal of the admission reception when the limit number of people has been reached; Calculating a congestion level of the event based on the calculated number of visitors; Varying the predetermined interval for calculating the number of visitors according to the degree of congestion; An information processing method comprising:

2. outputting the degree of congestion and the number of visitors to a display terminal; The information processing method according to claim 1 , further comprising:

3. An update object for updating the number of visitors is arranged on the screen of the display terminal, A step of reacquiring the number of visitors by accepting an operation on the update object. The information processing method according to claim 2 , further comprising:

4. The step of calculating the number of visitors at each predetermined interval includes a step of updating the number of visitors based on the number of people leaving the event.

4. The information processing method according to claim 1.

5. A second limit on the number of people is obtained, which is smaller than the limit on the number of people set based on the limit on the number of people; a step of permitting the admission acceptance by the reception terminal when the number of visitors becomes equal to or less than the second number of visitors after the number of visitors reaches the limit and the admission acceptance by the reception terminal is rejected; The information processing method according to claim 1 , further comprising:

6. Furthermore, when admission of attendees to a sub-event held in the venue of the event is accepted by a reception terminal of the sub-event, the number of attendees at the sub-event is acquired, determining whether or not a limit on the number of people permitted to enter the sub-event has been reached based on the acquired number of visitors; a step of notifying the reception terminal of the sub-event of the refusal of the admission reception when the limit number of people has been reached; The information processing method according to claim 1 , further comprising:

7. An information processing system comprising: a code reading terminal that reads a two-dimensional code or a barcode; and a management device that manages attendee information relating to attendees entering an event, The code reading terminal serves as a unit for accepting visitors, A first reading unit that reads a code describing the visitor ID of the visitor; a first transmission unit that transmits authentication information including the visitor ID read by the first reading unit, The management device includes: a first receiving unit that receives the authentication information transmitted by the first transmitting unit; a first determination unit that determines whether or not to permit entry of the attendee based on the number of people staying in a venue of the event and the authentication information received by the first receiving unit; a second transmission unit that transmits the visitor information to the code reading terminal when the first determination unit determines that entry is permitted, The code reading terminal comprises: A second receiving unit that receives the visitor information transmitted by the second transmitting unit; a first display unit that displays the visitor information received by the second receiving unit; Equipped with The management device includes: a first counting unit that counts the number of people who are permitted to enter the event based on the attendee information transmitted to the code reading terminal by the second transmission unit as an attendee number; A second counting unit that counts the number of people leaving the event; a calculation unit that calculates the number of people staying in a venue of the event at predetermined intervals based on the number of visitors counted by the first counting unit and the number of people leaving the venue counted by the second counting unit, The first determination unit determines whether the number of visitors calculated by the calculation unit has reached a limit of the number of visitors that can enter the event, When the first determination unit determines that the number of people staying has reached the limit number, the second transmission unit transmits, to the code reading terminal, refusal information for refusing the entrance acceptance by the code reading terminal; and When the number of visitors has not reached the limit, the first determination unit determines whether or not to permit entry of the visitor based on the authentication information received by the first receiving unit, and when it is determined that entry is permitted, transmits the visitor information to the code reading terminal, and when it is determined that entry is not permitted, transmits an error message including a message that entry is not permitted to the code reading terminal, and in the code reading terminal, the second receiving unit receives the error message, and the first display unit displays the error message received by the second receiving unit, The management device includes: A calculation unit that calculates a congestion level of the event based on the calculated number of visitors; A variable unit that varies the predetermined interval for calculating the number of visitors according to the degree of congestion; An information processing system comprising:

8. The information processing system includes: A display device is provided that displays the degree of congestion in the venue based on the number of people staying in the venue of the event. In the management device, The second transmission unit transmits the number of visitors and the congestion degree calculated by the calculation unit to the display device, The display device includes: A third receiving unit that receives the number of visitors and the congestion degree transmitted by the second transmitting unit; a second display unit that displays the number of visitors and the congestion degree received by the third receiving unit; The information processing system according to claim 7 .

9. Multiple sub-events will be held within the venue of the event, the information processing system includes a plurality of code reading terminals for the sub-events, The code reading terminal for the sub-event serves as a section for accepting the admission of the attendees, A second reading unit that reads a code describing the visitor ID of the visitor; a third transmission unit that transmits authentication information including the visitor ID read by the second reading unit, The first receiving unit receives the authentication information transmitted by the third transmitting unit, the first counting unit counts the number of people permitted to enter the sub-event based on the attendance information being transmitted to the code reading terminal for the sub-event by the second transmission unit, as the number of attendees of the sub-event; The second counting unit counts the number of people leaving the sub-event, the calculation unit calculates the number of visitors to the sub-event based on the number of visitors counted by the first counting unit and the number of visitors exiting the sub-event counted by the second counting unit; the first determination unit determines whether the number of visitors to the sub-event calculated by the calculation unit has reached a limit of the number of visitors that can enter the sub-event; When the first determination unit determines that the number of visitors has reached the limit number, the second transmission unit transmits refusal information to the code reading terminal for the sub-event, refusing the admission acceptance by the code reading terminal for the sub-event; The code reading terminal for the sub-event comprises: a fourth receiving unit that receives the rejection information transmitted by the second transmitting unit; a third display unit that displays the rejection information received by the fourth receiving unit, the first determination unit, when the number of visitors has not reached the limit number, determines whether or not to permit entry to the sub-event based on the authentication information received by the first reception unit; When the first determination unit determines that entry to the sub-event is permitted, the second transmission unit transmits the attendee information to the code reading terminal for the sub-event; The fourth receiving unit receives the visitor information transmitted by the second transmitting unit, The third display unit displays the visitor information received by the fourth receiving unit.

9. The information processing system according to claim 8.

10. An information processing device for managing an event in which admission of visitors is accepted by a reception terminal, comprising: a first counting unit that counts the number of visitors whose entry has been accepted by the reception terminal as a number of visitors; A second counting unit that counts the number of people leaving the event; a calculation unit that calculates the number of people staying in a venue of the event at predetermined intervals based on the number of visitors counted by the first counting unit and the number of people leaving the venue counted by the second counting unit; a determination unit that determines whether the number of visitors calculated by the calculation unit reaches a limit of the number of visitors that can enter the event; a transmission unit that transmits, when the determination unit determines that the number of visitors has reached the limit, refusal information indicating a refusal of the entrance reception by the reception terminal to the reception terminal; A calculation unit that calculates a congestion level of the event based on the calculated number of visitors; A variable unit that varies the predetermined interval for calculating the number of visitors according to the degree of congestion; Equipped with the determination unit, when the number of visitors has not reached the limit, determines whether or not to permit entry of the visitor based on authentication information including the visitor ID transmitted from the reception terminal; 23. An information processing apparatus comprising:

11. A computer for managing an event where admission of visitors is accepted by a reception terminal, comprising: tallying up the number of visitors whose entry has been accepted by the reception terminal as the number of visitors; Counting the number of people leaving the event; Calculating the number of people staying in the event venue at each predetermined interval based on the collected number of visitors and the number of people leaving the event venue; determining whether the calculated number of visitors reaches a limit of the number of visitors that can enter the event; When it is determined that the number of people staying has reached the limit number, refusal information indicating a refusal of the entry reception by the reception terminal is transmitted to the reception terminal; If it is determined that the number of visitors has not reached the limit, a determination is made as to whether or not to permit entry of the visitor based on authentication information including a visitor ID transmitted from the reception terminal; Calculating the degree of congestion at the event based on the calculated number of visitors; The predetermined interval for calculating the number of visitors is varied according to the degree of congestion. A program that executes a process.

Images