Restroom queue management

This application claims the priority benefit of U.S. provisional application No. 62/023,501, filed on Jul. 11, 2014 and titled “Restroom Management System Controlled By Stadium Owners,” the disclosure of which is incorporated herein by reference.

The present invention relates generally to facility management. More specifically, the present invention relates to selective information delivery based on user location.

Venue management currently has a variety of options for directing traffic to restroom facilities. Management can post signs directing attendees to the closet facility. Management can also provide restroom information on a website or on a map at the venue.

It is difficult, however, to manage restroom traffic when most attendees use restrooms at the same time. Attendees may prefer to use restrooms during breaks in the game because there is ample time to stand in a long line for the restroom. It is also difficult to manage restroom traffic when most attendees prefer to use the closest restroom. Attendees may decide to use the closest restroom on the assumption that other restrooms have the same wait time and will require additional travel time.

There is a need in the art for improved systems and methods for managing restroom traffic.

One exemplary method for managing restroom traffic describes receiving facility line data at one or more line sensors. The one or more line sensors are located at a venue. The method also describes receiving facility occupancy data at one or more occupancy sensors. The one or more occupancy sensors are located at the venue. The method also describes processing the line data to provide line information for input into a database. The line information is associated with the venue. The method also describes processing the occupancy data to provide occupancy information for input into the database. The occupancy information is associated with the venue. The method also describes transmitting the line information and occupancy information to a user device having an event app associated with the venue.

One exemplary system for managing restroom traffic provides one or more line sensors, one or more occupancy sensors, and a processor. The one or more line sensors receive facility line data. The line sensors are located at a venue. The one or more occupancy sensors receive facility occupancy data. The occupancy sensors are located at the venue. Execution of instructions stored in the memory by the processor performs a set of operations. The operations include processing the line data to provide line information for input into a database. The line information is associated with the venue. The operations also include processing the occupancy data to provide occupancy information for input into the database. The occupancy information is associated with the venue. The operations also include transmitting the line information and occupancy information to a user device having an event app associated with the venue.

One exemplary non-transitory computer-readable storage medium is also described, the non-transitory computer-readable storage medium having embodied thereon a program executable by a processor to perform an exemplary method for managing restroom traffic. The exemplary program method describes receiving facility line data at a venue. The program method also describes receiving facility occupancy data at the venue. The program method also describes processing the line data to provide line information for input into a database. The line information is associated with the venue. The program method also describes processing the occupancy data to provide occupancy information for input into the database. The occupancy information is associated with the venue. The program method also describes transmitting the line information and occupancy information to an event app associated with the venue.

FIG. 1 illustrates a system for managing restroom traffic.

FIG. 2 illustrates an event restroom app graphical user interface.

FIG. 3 illustrates a ticket database table.

FIG. 4 illustrates a restroom database table.

FIG. 5 illustrates a method for providing occupancy information.

FIG. 6 illustrates a method for providing line information.

FIG. 7 illustrates a method for providing wait time information.

FIG. 8 illustrates a method for managing restroom traffic.

The present invention includes systems and methods for managing restroom traffic at an event venue. Sensors at restroom facilities receive line and occupancy data and transmit the data to a system for processing. The system generates information regarding a wait time, line length, and occupancy for each facility at the event venue. The generated information is transmitted to an event application (“app”) associated with a ticket and a seat for an event at the venue. The event app provides the generated information to a user through a user device display. The system also generates information regarding travel time to each facility from the associated seat and transmits the information to the user device for display. The system can notify the user when the combined travel time and wait time for a facility falls below a threshold set in the app by the user.

Restroom traffic can be managed for entertainment or cultural events that are presented at a theatre, gymnasium, stadium, or other facility to a group of people. Such events include a wide variety of sporting events such as football (American and Global), baseball, basketball, soccer, ice hockey, lacrosse, rugby, cricket, tennis, track and field, golf, cycling, motor sports such as automobile or motorcycle racing, horse racing, Olympic games, and the like; cultural events such as concerts, music festivals, plays, the opera, and the like; religious events; and more permanent exhibitions such as museum, historic home, and the like.

FIG. 1 illustrates a system 100 for managing restroom traffic. The system 100 of FIG. 1 includes a mobile device 105 , a communication network 120 (e.g., Internet), at least one camera line counter 125 , at least one door counter 130 , a restroom data system 135 , and a restroom system 195 . The mobile device 105 includes a means of communication 110 and an event restroom application (“app”) 115 . The restroom system 195 includes a ticket software 140 , a restroom activity software 145 , a ticket database 160 , a restroom app database 165 , a restroom database 170 , a controller software 190 , a means of communication 175 , and a restroom broadcast software 180 . The controller software 190 controls the restroom activity software 145 , the ticket software 140 , and the restroom broadcast software 180 . The ticket database 160 includes one or more ticket database tables. The restroom database 170 includes one or more restroom database tables.

Each camera line counter 125 collects restroom line data for a corresponding restroom. The camera line counter 125 includes a camera placed on the door jamb or inside or outside the restroom. The camera line counter 125 counts the number of people in line and sends line data to the restroom data system 135 . Each door counter 130 collects restroom occupancy data for a corresponding restroom. The door counter 130 includes a counter placed on the door jamb or inside or outside the restroom. The door counter 130 counts the number of people entering and leaving the restroom and sends occupancy data to the restroom data system 135 . The door counter 130 can include one or more lasers and one or more detectors. Both camera line counter data and door counter data are associated with a timestamp indicating when the data was collected and a restroom identification indicating the restroom from which the data was collected. The restroom data system 135 processes the line and occupancy data for transfer to the restroom activity software 145 .

The restroom activity software 145 processes the real-time line data to provide information indicating whether there is no line or whether a restroom line is “Long,” “Medium,” or “Short.” The restroom activity software 145 also processes the real-time occupancy data to provide occupancy information indicating whether a restroom occupancy is “Full,” “75%,” “50%,” or “25%.” The restroom activity software 145 provides occupancy information based on the number of facilities and the number of occupied facilities in a restroom. Restroom facilities can include stalls and urinals. The restroom activity software 145 also provides wait time information for a restroom using the processed line and occupancy data. The restroom activity software 145 transfers the wait time, and processed line and occupancy information along with the associated restroom identification and timestamp information to the restroom database 170 .

The restroom broadcast software 180 receives wait time, line information, and occupancy information from the restroom database 170 and broadcasts the information to the event restroom app 115 each minute. The restroom broadcast software 180 also broadcasts travel time information for each restroom based on the distance between a restroom and a seat of an event ticket-holder. The restroom broadcast software 180 broadcasts information to the event restroom app 115 using the means of communication 175 .

A mobile device user can purchase the event restroom app 115 when the user purchases an event ticket. The event restroom app 115 is associated with the event ticket and the corresponding seat at the event. Upon purchase of the event restroom app 115 , the ticket software 140 updates the ticket database 160 to show an app associated with a particular seat was purchased. Each event restroom app 115 in the restroom app database 165 is also associated with a particular venue. The user can then download the event restroom app 115 from the restroom app database 165 . The ticket software 140 populates an event restroom app graphical user interface with a code identifying the ticket associated with the app 115 . The event restroom app is only available for use for the associated event and is only enabled for the associated event.

FIG. 2 illustrates an event restroom app graphical user interface (GUI) 200 . The event restroom app GUI 200 of FIG. 2 includes a map 205 , a legend 210 , a ticket identification code display 215 , an information table 225 , a table key 230 , and an alarm option 235 . The map 205 provides the current location of the app user and locations of restrooms. The ticket identification code display includes an enabled indicator 220 . The ticket software 140 populates the ticket identification code display 215 with a code identifying the ticket associated with the event restroom app 115 . The enabled indicator 220 will show whether the app is enabled.

The information table 225 includes restroom type information 240 , occupancy information 250 , line information 255 , wait time information 260 , and travel time 265 for each restroom. Restroom type information 240 can indicate whether a restroom is for men or women. Occupancy information from the restroom software 195 is used to provide occupancy information 250 in the information table 225 . Occupancy information 250 indicates to what extent a restroom is occupied. Line information 255 can indicate whether there is no line or whether a line for a restroom is long, medium, or short. Wait time information 260 can indicate how much time a user needs to wait in line to use the restroom. Travel time information 265 can indicate the amount of time required for a user to walk to the restroom from the user's current location.

The information table 225 and map 205 identify each restroom with the same identification label 245 (e.g., R 1 , R 2 , R 3 , Rn). An event restroom app GUI user can use the table key 230 to read information such as abbreviations in the information table 225 .

An event restroom app user can set a restroom alarm using the alarm option 235 . A user who, for example, wants to spend less than 10 minutes walking to and waiting for the restroom can input “10 min.” into the alarm option 235 . The alarm option input is transferred to the restroom broadcast software 180 . The broadcast software processes travel time and wait time information for each restroom at the event to identify a restroom with a combined travel time and wait time that is less than or equal to the alarm option input. The event restroom app 115 will set off an alarm to notify the user when the combined travel time and wait time is estimated to be less than ten minutes. The alarm can be in the form of a text message delivered to the mobile device 105 .

FIG. 3 illustrates a ticket database table 300 . The ticket database table 300 of FIG. 3 includes seat identification information 310 and event restroom app purchase information 315 . App purchase information 315 indicates whether an event restroom app associated with the corresponding seat was purchased. Upon purchase of the event restroom app 115 , the ticket software 140 updates the ticket database 300 to show an app associated with a particular seat was purchased. The restroom broadcast software 180 uses the ticket database table 300 to identify the seat location of an event restroom app user. The restroom broadcast software 180 uses the location information to generate travel time information to the app user. The restroom broadcast software 180 also uses location information to identify the venue and corresponding restrooms associated with the event restroom app 115 . The restroom broadcast software 180 broadcasts travel time, wait time, and line and occupancy information for restrooms associated with the event restroom app 115 .

FIG. 4 illustrates a restroom database table 400 . The restroom database table 400 of FIG. 4 includes restroom identification information 405 , timestamp information 410 , line information 415 , occupancy information 420 , and wait time information 425 . Line information 415 , occupancy information 420 , and wait time information 425 from the restroom activity software 145 is recorded in the restroom database table 400 for each minute for each restroom. The timestamp information 410 provides the time at which the corresponding camera line counter 125 and door counter 130 collected data used to derive the corresponding line information 415 , occupancy information 420 , and wait time information 425 . The restroom identification information 405 identifies the restroom. The restroom identification information 405 can be customized for each event. For example, the line was long, the occupancy was full, and there was a 10 minute wait for restroom “R 1 ” at time 1 : 00 .

FIG. 5 illustrates a method 500 for providing occupancy information. At block 505 of FIG. 5 , the restroom activity software 145 loads data from the door counter 130 of a particular restroom. At block 510 , the restroom activity software 145 processes the loaded door counter data to calculate the number of people who entered the restroom. At block 515 , the restroom activity software 145 processes the loaded door counter data to calculate the number of people who exited the restroom. At block 520 , the restroom activity software 145 calculates occupancy of the restroom by subtracting the number of people who exited the restroom from the number of people who entered the restroom. At block 525 the restroom activity software 145 outputs “Full” when there are more than 30 people occupying the restroom. At block 530 , the restroom activity software 145 outputs “75%” when there are more than 20 people occupying the restroom and less than 31 people occupying the restroom. At block 535 , the restroom activity software 145 outputs “50%” when there are more than 15 people occupying the restroom and less than 21 people occupying the restroom. At block 540 , the restroom activity software 145 outputs “25%” when there are more than 10 people occupying the restroom and less than 16 people occupying the restroom. The restroom activity software 145 outputs “Empty” when there are not more than 10 people occupying the restroom.

At block 570 the restroom activity software saves the occupancy output to the restroom database 170 . At block 575 , the method 500 repeats after 1 minute. The restroom activity software provides occupancy information based on the number of occupied facilities in relation to the number of facilities provided in a restroom.

FIG. 6 illustrates a method for providing line information. At block 605 of FIG. 6 , the restroom activity software 145 loads data from the camera line counter 125 of a particular restroom to determine the number of people in line for the restroom. At block 610 , the restroom activity software 145 outputs “Long” when there are more than 20 people in line for the restroom. At block 615 , the restroom activity software 145 outputs “Medium” when there are more than 10 people in line for the restroom and less than 21 people in line for the restroom. At block 620 , the restroom activity software 145 outputs “Short” when there are more than 5 people in line for the restroom and less than 11 people in line for the restroom. At block 625 , the restroom activity software 145 outputs “None” when there are less than 6 people in line for the restroom.

At block 650 the restroom activity software 145 saves the line information output to the restroom database 170 . At block 655 , the method 600 repeats after 1 minute. The restroom activity software provides line information based on the number of facilities provided in a restroom in relation to the number of people in line for the restroom.

FIG. 7 illustrates a method 700 for providing wait time information. At block 705 of FIG. 7 , the restroom activity software 145 loads line information and occupancy information generated from camera line counter data and door counter data. At block 710 , the restroom activity software 145 outputs “5 minutes” when the line is “Short” and the occupancy is “Full.” At block 715 , the restroom activity software 145 outputs “10 minutes” when the line is “Long.” The restroom activity software 145 also outputs “10 minutes” when the occupancy is “Full.” At block 720 , the restroom activity software 145 outputs “5 minutes” when the line is “Medium.” The restroom activity software 145 also outputs “5 minutes” when the occupancy is “50%” or “75%.” At block 725 , the restroom activity software 145 outputs “None” when the line is “None” and the occupancy is less than 25%. At block 730 , the restroom activity software 145 outputs “2 minutes” when the line is “None.” The restroom activity software 145 also outputs “2 minutes” when the occupancy is less than 50%. At block 735 , the restroom activity software 145 saves the wait time output to the restroom database 170 .

FIG. 8 illustrates a method 800 for managing restroom traffic. The method 800 includes, at block 805 , providing the system 100 for managing restroom traffic. The method 800 includes, at block 810 , supplying a real-time data regarding a number of people in line for a restroom and a restroom occupancy for the restroom. The method 800 includes, at block 815 , processing the line data and occupancy data using the restroom activity software 145 . The method 800 includes, at block 820 , transferring the processed line data and occupancy data to the restroom database 170 . The method 800 includes, at block 825 , allowing a mobile device user to purchase the event restroom app 115 , uploading the event restroom app 115 , and updating the ticket database 160 with the purchase. The method 800 includes, at block 830 , generating restroom travel time and sending restroom information to the event restroom app 115 for display. The method 800 can also include, at block 835 , allowing an event restroom app user to set a restroom alarm and alerting the user when the combined travel time and wait time for a restroom is under a predetermined threshold set by the user.

While various flow diagrams provided and described above may show a particular order of operations performed by certain embodiments of the invention, it should be understood that such order is exemplary (e.g., alternative embodiments can perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

The foregoing detailed description of the technology herein has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the technology to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the technology and its practical application to thereby enable others skilled in the art to best utilize the technology in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the technology be defined by the claim.