Multi-activity venue automation

By integrating itinerary management, participant identification, access control, payment management and scoring systems in multiple event venues, the inefficiency of site automation management is solved, and efficient user experience and automated management are achieved.

CN118940870APending Publication Date: 2024-11-12亚当 J 爱泼斯坦
View PDF 8 Cites 0 Cited by

Patent Information

Application Number
CN202410979099.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2018-04-10
Filing Date
2018-09-14
Publication Date
2024-11-12

AI Technical Summary

Technical Problem

The prior art is difficult to effectively manage and automate participant interactions in multiple event venues, including itinerary generation, event booking, access control, payment management and scoring, resulting in inefficiency and poor user experience.

Method used

Designed a site automation environment, integrating itinerary management system, participant identification system, access control system, payment management system and scoring system, and implementing automated management through computer networks, including automatic itinerary generation, event booking, payment processing and scoring tracking , ensuring smooth experience for participants on the venue.

Benefits of technology

Improve the efficiency and user experience of multiple event venues, reduce downtime between participants, reduce operator errors, realize automated event access and ratings, and enhance the degree of automation of site management.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118940870A_ABST
    Figure CN118940870A_ABST
Patent Text Reader

Abstract

A venue automation environment is disclosed in which various forms of automation and user integration may be managed across one or more activities of one or more venues. The venue automation and integration may include automation of various stages in which participants participate, including before, during, and after visiting one or more venues and participating in one or more activities of the venues. Site automation and integration may include automatic journey generation, activity subscription, participant identification, access control, payment management, scoring, media capture (e.g., audio, photo, and video), and site management.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of U.S. Patent Application No. 62 / 558,607, filed on September 14, 2017, entitled “Parking Lot with Automated Event Access and Scoring System,” U.S. Patent Application No. 62 / 655,440, filed on April 10, 2018, entitled “Customized Itineraries for Multiple Event Venues,” and U.S. Patent Application No. 62 / 655,438, filed on April 10, 2018, entitled “Photo, Video, and Data Package for Multiple Event Venues,” the entire disclosures of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates generally to venues for participating in multiple sports and related activities, and more particularly to automated aspects of participant interaction at such multi-activity venues. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] This description refers to the following drawings, in which like reference numerals are used in different drawings to indicate like or similar components.

[0005] Figure 1 is a schematic diagram depicting a field automation environment according to certain aspects of the present disclosure.

[0006] Figure 2 is a schematic diagram depicting a field automation environment associated with a field in accordance with certain aspects of the present disclosure.

[0007] Figure 3 is a schematic diagram depicting an automated event access and scoring system for a venue automation environment in accordance with certain aspects of the present disclosure.

[0008] Figure 4 is a schematic diagram depicting a trip management system according to certain aspects of the present disclosure.

[0009] Figure 5 is a flow chart depicting a process for generating an itinerary according to certain aspects of the present disclosure.

[0010] Figure 6 is a flow chart depicting a process for updating various information based on activity usage data in accordance with certain aspects of the present disclosure.

[0011] Figure 7 is a flow chart depicting a process for dynamically updating an itinerary according to certain aspects of the present disclosure.

[0012] Figure 8 is a schematic diagram illustrating a media management system according to certain aspects of the present disclosure

[0013] Fig. 9 is a simplified block diagram depicting a computer system according to certain aspects of the present disclosure that may include components of the various systems and devices described herein.

[0014] Fig.10 is a schematic diagram depicting a customized trip display on a computing device in accordance with certain aspects of the present disclosure. DETAILED DESCRIPTION

[0015] Certain aspects and features of the present disclosure relate to a venue automation environment in which various forms of automation and user integration can be managed across one or more events at one or more venues. Venue automation and integration can include automation of different stages of participant engagement, including visiting one or more venues and before, during, and after participating in one or more events at the venues. Venue automation and integration can include automatic itinerary generation, event booking, participant identification, access control, payment management, scoring, media capture (e.g., audio, photo, and video), and venue management.

[0016] A venue may include a range of activities, such as within a nearby distance or confined within a single physical property, although this may not always be the case. As used herein, the term venue may refer to a venue related to sports, such as a location that provides participation in one or more sports or sports-related activities. However, in some cases, a venue may also refer to a location that provides participation in other activities, such as a water slide, amusement facilities or other activities or experiences, such as in the case of a water park or an amusement park. In some cases, all activities of a venue may be confined to a single property, such as a single continuous property (e.g., a single restricted land area or a single restricted building or a complex of connected buildings). In some cases, multiple activities may be located in separate properties, such as in the case of a multi-sport competition, where a first activity (e.g., an activity based on swimming) can be conducted at a first location (e.g., a swimming pool facility), and a second activity (e.g., an activity based on running) can be conducted at a second location away from the first location (e.g., a track located in another part of a town away from a swimming pool facility). Therefore, a venue can indicate a single property, although this need not be the case.

[0017] Activity can be any suitable event that an individual can participate in. In some cases, activity can be an activity related to sports, such as sports or activities related to one or more sports in some way, although the situation is not always the case. As used herein, participation or participation can include major participation (for example, the individual participates in activities by himself, such as personal swimming) or minor participation (for example, the individual guides another person to participate in activities, such as the participant takes his or her dog to participate in a canine obstacle course). In some cases, activity includes passive events, in which the participant mainly plays a passive role in the experience activity. The example of such passive events can include the participant watching a video and the participant taking amusement facilities (for example, amusement park rides). In some cases, activity includes active events, in which the participant mainly plays an active role in the execution of activities. The example of such active events can include rock climbing, running, skiing, archery, etc. In some cases, activity can include leisure or rest activities, such as rest time (for example, in order to relax or sleep), meal time (for example, in a specific restaurant or other dining place), or other such activities. In some cases, activity can be skill-based or ability-based activities, in which the skill level, natural ability or other characteristics of the participant determine or substantially determine the success of the participant when performing the activity. Examples of skill-based or ability-based activities include rock climbing, biking, bowling, and skiing. In some cases, an activity may be a neutral activity, in which the skill level, natural ability, or other characteristics of a participant do not determine or substantially determine the participant's success in performing the activity. Examples of neutral activities include watching a movie, playing a game of chance, and riding a roller coaster.

[0018] In some cases, the activity is part of an action, extreme sports entertainment or theme park or other venue. Some non-limiting examples of activities may include one or more of the following: white water rafting, kayaking, surfing, participating in a lazy river, river or other water slide (e.g., in a water tube, kayak, canoe board or other watercraft), downhill or cross-country skiing, snowboarding, bobsleigh skiing, skateboarding, mountain biking, cyclocross, participating in joint training for a team sports league, zip lining, rock climbing, bungee jumping, via ferrata, extreme sledding, bobsleigh, participating in obstacle courses (e.g., involving obstacles such as fire, water, mud, electricity, height, etc.), etc.

[0019] The location for the event may be pre-selected based on the particular topography or terrain requirements of the various events held within the location (e.g., mountains or hills suitable for skiing located near or adjacent to relatively flat terrain suitable for activities such as surfing, river rafting, etc.).

[0020] In some cases, activities can be scored. For example, a race can be scored based on the total time to complete the race or the duration of a certain activity.

[0021] Activities can be single-player or multi-player. In single-player activities, an individual can participate in the activity on their own and can be scored accordingly. In multi-player activities, an individual can participate in the activity with multiple individuals, each of whom can be scored individually and / or can be scored together as a team.

[0022] In some cases, an activity can be designed to optionally or always follow a previous activity. For example, a rock climbing activity (e.g., a first activity) may include four walls that terminate at a platform from which another activity (e.g., a second activity) such as bungee jumping or zip lines can be performed. In this example, if there is another way to access the platform to participate in the second activity, the second activity can be considered to preferentially follow the first activity (e.g., it may be convenient to participate in the second activity immediately after the first activity, but participating in the first activity is not necessary for participating in the second activity). However, if there is no other way to access the platform to participate in the second activity without first participating in the first activity, the second activity can be considered to be a mandatory follow-up activity to the first activity. In such cases, participants must first participate in the first activity before they can participate in the second activity. In some cases, if they wish to participate in the first activity, they may be required to participate in the second activity, although this may not always be the case (e.g., in the case of rock climbing, participants can descend to the starting point of the rock climbing activity after completing the activity without having to participate in the second activity).

[0023] As described in further detail below, the generation of an itinerary may include determining whether a second activity is preferred to follow a first activity and / or whether the second activity is a mandatory subsequent activity to the first activity, and then using this determination to schedule the first and / or second activities. For example, if a participant is unable or does not wish to attend a particular activity, or if a particular activity cannot be scheduled for any other reason, the itinerary management system may explicitly exclude certain other activities based on their mandatory relationship to the particular activity.

[0024] In some cases, information (e.g., photos, videos, or data such as ratings) can be grouped in priority and / or mandatory linked subsequent activities. For example, a participant's live participation in a first activity can automatically switch to live participation in a second activity without further interaction. In another example, participation in a first activity and one or more mandatory subsequent activities can be grouped together for rating purposes and presented as a set of separate ratings for each activity and / or as a single rating for a group of activities.

[0025] In some cases, multiple activities can be grouped together using similar equipment or clothing to be preferentially (e.g., sequentially) performed together. For example, multiple water activities that require participants to wear swimwear can be arranged sequentially and / or separately from earlier or later activities that require different clothing. In another example, multiple activities that require specific equipment (e.g., footwear, skis, helmets, etc.) can be arranged sequentially and / or separately from activities that do not require the equipment. In some cases, itinerary generation can be linked to an inventory management system to ensure that the number of people scheduled to participate in a certain activity does not exceed the number of equipment available for rent or borrowing. For example, if the current inventory of available helmets is only 20, including or excluding any reserve inventory, such as unplanned participant arrivals, the itinerary management system can intentionally arrange no more than 20 participants at a time to perform activities that require helmets. In some cases, the itinerary management system can use current data from the inventory management system (e.g., the number of helmets currently available for borrowing), especially when generating itineraries for that date or a date approaching. However, in some cases, the itinerary management system can use predicted data (e.g., the predicted number of helmets available for borrowing based on historical data and / or other information), especially when generating itineraries for future dates or times.

[0026] Any combination of the systems disclosed herein may be embodied on one or more computers (e.g., servers), whether or not located at the same location. In some cases, a particular system may be embodied on multiple computers at different levels of the hierarchy, from a multi-venue level (e.g., computers associated with multiple venues), to a single venue level (e.g., computers associated with a single venue), to a multi-activity level (e.g., computers associated with a group of activities), to a single activity level (e.g., computers associated with a single activity). Computers located in venues (e.g., in each activity) may facilitate the reception and transmission of data associated with venues and activities, including historical data (e.g., usage data), participant ratings, participant identification information, captured video or other media, or other data. In some cases, computers located in venues (e.g., in each activity) may perform some or all of the actions necessary for the various functions of the various systems disclosed herein. In some cases, certain functions of the various systems may be performed by a centralized server, which may include one or more computers located at or away from the venue.

[0027] Specific details are given herein to provide a thorough understanding of the embodiments. However, it will be appreciated by those skilled in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be presented as components in block diagram form to avoid obscuring the embodiments in unnecessary detail. In other cases, well-known circuits, processes, algorithms, structures, and techniques may be presented without unnecessary detail to avoid obscuring the embodiments.

[0028] Also, it should be noted that various embodiments may be described as processes depicted as flow charts, flow diagrams, data flow diagrams, structure diagrams, or block diagrams. Although flow charts may describe operations as sequential processes, many operations may be performed in parallel or simultaneously. In addition, the order of operations may be rearranged. A process may terminate when its operations are completed, but may have additional steps not included in the figure. A process may correspond to a method, function, program, subroutine, subprogram, etc. When a process corresponds to a function, its termination corresponds to the function returning to the calling function or main function.

[0029] The term "machine-readable storage medium" or "computer-readable storage medium" includes, but is not limited to, portable or non-portable storage devices, optical storage devices, and various other media capable of storing, containing or carrying instructions and / or data. Machine-readable media may include non-transitory media that can store data and does not include carrier waves and / or transient electronic signals that are propagated wirelessly or through wired connections. Examples of non-transitory media may include, but are not limited to, disks or tapes, optical storage media such as compact disks (CDs) or digital versatile disks (DVDs), flash memories, memories, or storage devices. A computer program product may include code and / or machine-executable instructions that may represent any combination of a program, function, subroutine, program, routine, subroutine, module, software package, class, or instruction, data structure, or program statement. A code segment may be connected to another code segment or hardware circuit by transmitting and / or receiving information, data, variables, parameters, or memory contents. Information, variables, parameters, data, etc. may be transmitted, forwarded, or transmitted by any suitable means including memory sharing, message passing, token passing, network transmission, etc.

[0030] In addition, the embodiments may be implemented by hardware, software, firmware, middleware, microcode, hardware description language, or any combination thereof. When implemented in software, firmware, middleware, or microcode, the program code or code segments that perform the necessary tasks (e.g., a computer program product) may be stored in a machine-readable medium. (Multiple) processors may perform the necessary tasks.

[0031] The systems depicted in some figures may be provided in various configurations. In some embodiments, the system may be configured as a distributed system, where one or more components of the system are distributed over one or more networks in a cloud computing system.

[0032] These illustrative examples are given to introduce the reader to the general subject matter discussed herein and are not intended to limit the scope of the disclosed concepts. The following section describes various additional features and examples with reference to the accompanying drawings, wherein like numbers indicate like elements, and directional descriptions are used to describe the illustrative embodiments, but as with the illustrative embodiments, they should not be used to limit the present disclosure. The elements included in the illustrations herein may not be drawn to scale.

[0033] Figure 1 is a schematic diagram depicting a venue automation environment 100 according to certain aspects of the present disclosure. The venue automation environment 100 can be associated with one or more venues, each of which can contain one or more activities (e.g., events). In some cases, the venue automation environment 100 is associated with multiple venues. In some cases, each venue contains multiple activities.

[0034] The venue automation environment 100 may include an automation management system 102, which itself may include multiple subsystems that can facilitate various automations across the venue and any associated activities. Each system in the automation management system 102 may interact with one or more other systems to implement automations that can improve venue efficiency, improve participant enjoyment of the venue, or otherwise provide marketing benefits to the venue in which the automation management system 102 is included.

[0035] The trip management system 104 can handle automatic trip generation. Automatic trip generation can include generating customized trips (e.g., timetables) for participants of multiple activity venues. The trip management system 104 can be embodied on one or more computers. Each trip can include the time, time slot, or time window for the participant to participate in one or more activities at the venue. Participants can prepare the entire activity trip before or when arriving at the venue, thereby simplifying the participant's visit to the venue. The trip can be prepared by or for the participant. In some cases, the trip can be automatically generated based on the participant's preferences and / or other participant data such as demographic data (e.g., age, place of residence or other demographics) or stored activity history. A participant identification system (e.g., an automatic participant identification system) can be used to identify participants at the venue and / or activity to ensure that the participant is authorized to use or participate in the venue and / or activity. In some cases, the trip can be dynamically generated based on historical and / or field data from one or more venues. In some cases, the itinerary may be dynamically updated based on updated information from the venue to minimize downtime for activities within the venue (e.g., utilizing activities that are not currently in use) or to account for planned or unplanned maintenance and / or closures (e.g., automatically updating a participant itinerary when an activity is interrupted, or automatically updating the order of activities in a participant itinerary to move participants off a selected path within the venue). The itinerary management system 104 may interact with other systems disclosed herein to facilitate automation of itinerary generation, updating, and / or other itinerary management functions.

[0036] In some cases, generating an itinerary may include generating a schedule of multiple activities across a single venue or across multiple venues. A itinerary may be limited to one day or may extend beyond one day.

[0037] Itineraries may be generated based on participant criteria (e.g., user-provided preferences). Examples of criteria may include prioritizing one activity over another, prioritizing one activity to be performed later than or immediately after another at a certain time of day, prioritizing less strenuous activities in the afternoon, prioritizing participating in a particular activity with another participant or group of participants, prioritizing participating in a particular activity shortly after or shortly before another participant or group of participants participating in that activity, physical disabilities or limitations, or other such types of user-provided criteria.

[0038] In some cases, itinerary generation may also be based on other participant data, such as data collected and stored by the venue. For example, participant data may include historical activity data indicating a venue or another venue that a participant has visited in the past. Examples of such historical activity data may include the number of times a participant has participated in a particular activity, trends in past participation in activities (e.g., performing certain activities in a particular order or performing certain activities in certain months of the year), past rating information (e.g., some participants may like to participate in activities that are more challenging to the participant, while some participants may like to participate in activities in which the participant performs well), categories of past activities (e.g., water sports, high-speed activities, or other categories), ratings received by the participant after performing the activity, social media information associated with the participant and the activity (e.g., a participant shares a video of himself participating in the activity and tags the venue), or other historical information. In some cases, participant data may also include other stored information about the participant, such as previously received criteria and / or preferences, membership in a team or group, associations with other participants, and / or current location (e.g., if location information is shared with the venue).

[0039] In some cases, the participant data may include demographic data and / or demographically derived data (e.g., psychographic data) that may be used to inform itinerary generation. In some cases, the participant data may be pre-populated with demographic data and / or demographically derived data, such as when an account is created or in the early stages of the itinerary generation process, even if there is no available historical activity data of the participant's past visits to any venues.

[0040] In some cases, the participant data may include inference data. Inference data may include inferences and / or related data generated based on participant criteria, participant data, and / or participant input. For example, participants may submit answers to questions that are unrelated or seemingly unrelated to the venue and / or the venue's activities, which may be stored as inference data and used to generate inferences to help guide itinerary generation. In some cases, the collected feedback may be used to improve future inference generation based on the collected inference data. For example, if it is found that most participants who answer "yes" to "Do you like spicy food?" happen to like a certain set of activities, then the itinerary management system 104 may select this set of activities for new users who answer "yes" to the same question. In some cases, the inference data may include the results of a personality test, such as the results of a Myers & Briggs personality test (e.g., provided by a participant).

[0041] In some cases, itineraries can be generated to emphasize or weaken the possibility of spectators watching participants. For example, if a participant does not like spectators, the itinerary generated for the participant may include activities at times when many spectators are not expected to appear at the event site or near the event (e.g., early or late in the day, or adjacent empty slots in the event schedule). In some cases, participants who like spectators may have itineraries generated so that participants are expected to perform activities at times when spectators are expected to be at the event site or near the event. In some cases, rating data can be used to identify high-performance participants. Itineraries for high-performance participants can be generated so that participants participate in specific activities, where participants perform well when spectators are expected to be at the event site or near the event. In some cases, generating itineraries for participants may include generating suggestions for spectators of activities that participants expect to enjoy. In such cases, suggestions can be general (e.g., notifications indicating that participants like to watch specific activities), or can be suggestions for specific time slots or time windows (e.g., entries on the participant's itinerary for watching specific high-performance participants participating in specific activities at a specific time on that day).

[0042] In some cases, itinerary generation may also be based on schedules associated with venues and / or activities within the venue. For example, schedules associated with several activities may be accessed (e.g., current appointments from other participants) so that an optimized schedule can be generated for the participants. The optimized schedule may prioritize locations (e.g., performing nearby activities in succession), prioritize overall duration (e.g., selecting activities to minimize downtime between activities), or prioritize other aspects. In some cases, a schedule of activities may be accessed to determine potential downtime, and attempts may be made to schedule participants during that downtime to minimize the amount of downtime.

[0043] In some cases, itinerary generation may also be based on activity models. Activity models may be designed to estimate various aspects of one or more activities in a venue. For example, an activity model may be used to predict the time a participant will attend a particular activity before another participant attends that activity. In another example, an activity model may be used to predict queue lengths for participants who do not have an established itinerary (e.g., participants who visit an event and wait in line to attend without scheduling a time slot). In some cases, a venue model may be used in addition to or in lieu of an activity model. In an example, a venue model may be used to predict how long it may take a participant to travel from an activity to another activity, or when the busiest times of the day or the busiest days of the year may occur.

[0044] The itinerary may include packages that can be selected by the participant. For example, a "land lovers" package may include a selection of activities that do not involve water, while a "speed" package may include a variety of racing and high-speed activities. Once a package is selected, an itinerary may be generated that includes the activities in the package.

[0045] Once the itinerary is generated, it may optionally be presented for approval, rejection, or modification. In some cases, a fee may be charged upon approval of the itinerary. In some cases, a discount or other benefit may be offered if the participant is willing to accept the itinerary without making any modifications.

[0046] The generated and / or approved itinerary can be used to update the schedule associated with the activities in one or more venues, thereby ensuring that the activity schedule is kept up to date in a dynamic and / or real-time manner. In addition, the generated and / or approved itinerary can be used to dynamically and / or in real-time update the participant data (e.g., a list of commonly selected activities).

[0047] In some cases, the itinerary may be updated in real time based on different circumstances of the event, venue, or participant. For example, if an event is running behind schedule or maintenance must be performed, a modification to the participant's itinerary may be proposed or forced. Such modifications may include changing the time, date, or event. In some cases, if an event is underutilized, a modification proposal may be sent to the participant suggesting that they attend the event at a specific time. In another example, if a participant is behind his or her schedule or misses an event, a modification may be proposed or forced to change the participant's itinerary. If a modification is proposed, the participant may accept, reject, or further modify the proposed modification. If a modification is forced, the participant may be allowed to suggest further modifications that may be approved or rejected by the itinerary generation system, or the participant itinerary may be changed without further action by the participant.

[0048] In some cases, an itinerary may include activity entries across multiple venues, whether nearby or not. For example, multiple venues may be located within sufficient distance to visit each venue in a single day or a multi-day trip. In such cases, an itinerary may be generated that includes activities from multiple venues. In some cases, a participant may provide a travel plan that can be used to generate a multi-venue itinerary (e.g., between venues or between locations where venues may be located). For example, a participant who is in Florida on the first day and will be in Las Vegas on the second day may request an itinerary that includes one or more venues in Florida on the first day and one or more venues in Las Vegas on the second day.

[0049] The reservation system 106 can handle automatic activity reservations. The reservation system 106 can be embodied on one or more computers. The reservation system 106 can be associated with, or be part of, a travel management system. Automatic reservations can include automatically suggested reservation times for participants to attend specific activities, thereby avoiding participants from spending too much time in line. The automatic reservation system 106 can be integrated with the travel management system to access the participant's itinerary and suggest reservation times based on the participant's itinerary, thereby suggesting adjacent time reservation times for participants when attending nearby activities, or automatically deleting or weakening available reservation times that may conflict with the participant's current itinerary (for example, the time required to travel between activities is longer than the expected time difference between activities). The reservation system 106 can interact with other systems disclosed herein to facilitate automation of activity reservations.

[0050] The participant identification system 108 can handle automatic participant identification. The participant identification system 108 can be embodied on one or more computers. The participant identification system 108 can include multiple sensors located at the venue (including the venue's activities) that can obtain participant identification information (e.g., participant keys) and use it to determine identifiers associated with participants. The participant identification system 108 can use the participant identification information to identify when a participant participates in a particular activity, when a participant is expected to participate in a particular activity, and even the identity of the participant (e.g., the actual identity or anonymous identity using an identifier associated with the participant). The participant identification system 108 can identify the participant by comparing the participant identification information with a participant registration database. In some cases, the participant identification information can be an identifier (e.g., a password) obtained by an electronic, wireless, visual or other sensor. In some cases, the participant identification information can be biometric information, such as a fingerprint or a recognizable facial pattern. The participant identification information can be obtained by any number of sensor devices, such as a camera, a radio frequency identification (RFID) scanner, a fingerprint scanner, a Bluetooth tracker, a near field connection (NFC) equipment, or any other suitable sensor equipment. In some cases, the participant identification system 108 can interact with a device provided by the venue (e.g., a bracelet or badge) to identify the participant. In some cases, the participant identification system 108 may interact with a device provided by a participant (e.g., a participant's smartphone) to identify the participant. In some cases, participant identification may interact with the participant (e.g., through facial recognition, voice recognition, or the participant inputting an identifier) ​​to identify the participant. In some cases, the participant identification system 108 may automatically identify the participant without the participant actively providing identification. In some cases, the participant identification system 108 may automatically identify the participant without the participant interacting, except that the participant appears at the event (e.g., in a specific area of ​​the event, such as a queue). In some cases, the participant identification system 108 may provide automatic identification of the participant, thereby enabling other systems to perform automated tasks specific to the participant. In some cases, the participant management system may determine that the participant is part of a group or team. In some cases, the participant identification system 108 may interact with other systems disclosed herein to facilitate participant identification.

[0051] In some cases, the trip can be used to update the participant identifier information. The participant identifier information can be referred to as key information, and the participant identifier can be used as a key to identify and / or authenticate the participant. As described herein, a key can be any type of physical or non-physical (e.g., digital) information that a participant can use to identify himself at an event or venue. Examples of suitable keys can include a name, an identification number, a barcode, a radio frequency identification tag, a digital signature, a digital certificate, or other such information. A computer in a venue, such as a computer at an event, can read the key and allow the participant to enter the event. For example, a key containing an RFID tag can include an identifier thereon that can be used to identify the participant to an RFID reader. In some cases, the participant's biometric data can be used as an identifier (e.g., a fingerprint, retina, or facial scan). In some cases, if a key associated with the trip entry is received at the time of trip entry, entry is allowed. In some cases, if a key associated with the trip entry is received at the time of trip entry, entry through a quick entrance may be allowed. Receiving a key at the time of trip entry can include receiving a key within a specified period indicated by the trip or within a time window before, after, or around the specified period. The key associated with the trip entry can be a key associated with a participant who plans to participate in the event at the specified period.

[0052] In some cases, a participant may have a static key that may be used for multiple visits and / or multiple trips. In such cases, updating the key information may include updating the information at the venue or event to ensure that entry can be provided when the key is received. However, in some cases, a new key may be generated for each trip and / or each activity in a trip. In such cases, updating the key information may include providing the key to the participant or associating the key with the participant's account.

[0053] The access control system 110 can handle automatic access control. The access control system 110 can be embodied on one or more computers. The automatic access control can interact with the participant identification system to determine the identity of the participant (e.g., the participant identifier), and then authorize or deny the authorized participant's access to the required resources. In some cases, the automatic access control authorizes or denies access without any user interaction other than the user's presence. Access control can authorize or deny access to the venue, the activity in the venue, or any other resource associated with the venue. In some cases, the automatic access control can use the participant's identity to automatically determine whether the participant has a reservation (e.g., through a reservation system), automatically determine whether the participant has paid for access to the required activity, and if not, initiate payment (e.g., through the payment management system 112), automatically check and / or update the participant's itinerary (e.g., through the itinerary management system 104), and / or automatically provide access to media data associated with the venue, activity, and / or participant. In some cases, authorizing access to an activity may include automatically customizing the activity for the user, such as automatically adjusting the difficulty level, power level, or resistance level of the equipment; automatically providing participant information (e.g., name, title, photo, and / or avatar) to the activity (e.g., to be displayed in or incorporated into the activity), automatically selecting equipment appropriate for the participant, or performing any other appropriate customization. In some cases, the access control system 110 may interact with other systems disclosed herein to facilitate authorizing or denying access (e.g., to a venue, an activity, or any other resource associated with a venue).

[0054] Certain aspects and features of the present disclosure relate to automatic payment management. Automatic payment management can be performed by a payment management system 112, which can be embodied on one or more computers. The payment management system 112 can store payment data associated with a participant. The payment data can include historical purchases, offers, coupons, stored payment methods, or other payment-related data. When a participant is at the venue, the payment management system 112 can interact with other systems to automate payments. For example, a participant can simply walk up to an event and begin participating in the event, at which point a participant identification system can identify the participant and provide the participant identification to the payment management system 112, which can process the necessary payments without interrupting the participant's participation in the event. In some cases, processing payments can include deducting credits associated with a participant's historical purchases. In some cases, processing payments can include initiating a new payment using a payment method selected by the participant (e.g., a credit card). In some cases, the payment management system 112 can communicate with equipment at the event to provide feedback (e.g., audio, visual, or tactile) to indicate information associated with the payment processing, such as an indication of a successful payment, an indication of a failed payment, an indication of a remaining credit, an indication that the remaining credit is below a threshold, an indication of the payment amount, or an indication of an available offer for the participant (e.g., a discounted bundle offer available as a result of the participant's participation in a given event). In some cases, the payment management system 112 can interact with other systems disclosed herein to facilitate management of participant payments.

[0055] Scoring system 114 can handle automatic scoring. Scoring system 114 can be embodied on one or more computers. Automatic scoring can include automatically tracking the scoring of one or more participants, and for example, using a participant identifier to associate the tracked scoring with the participant. In some cases, scoring system 114 can interact with a participant identification system to automatically detect participants participating in a particular activity. The scoring of the activity can be automatically, manually, or partially automatically tracked. For example, a sensor, timer, or other equipment can be associated with an activity that automatically triggers a scoring event (e.g., a basketball falls into a basket to score a shot, a button is pressed at the top of a climbing wall to trigger a timer to stop, or a machine vision system tracks a ski jump to calculate the height of the jump) and is set. In some cases, the activity scoring can be completely manual and based on manual input (e.g., by a referee or an activity operator). In some cases, the activity scoring can be partially automatic, including manual input for confirming or providing additional information to supplement the automatically acquired scoring or indicators. In some cases, scoring system 114 can interact with other systems disclosed herein to facilitate scoring management associated with participants.

[0056] In some cases, when using the participant identification system to detect and / or identify a participant or a team of participants, the participant identification system can transmit identification information to the scoring system 114, thereby facilitating the performance of the participants in the activity (e.g., completion time, duration, travel distance or some other indicators) to be automatically scored. In some cases, the scoring system 114 may include a scoring sensor associated with the activity. In some cases, the scoring system 114 is fully automatic, recording the performance of the participant and storing it. In some cases, operator control may be necessary, but the automatic scoring recorder can automatically pair the operator input with the identification information of the participant, thereby facilitating the operator's input to be paired with the participant. The operator's input may be the scoring of a particular activity, or may be other inputs for generating activity scoring.

[0057] The scoring system 114 may automatically score and / or rank participants participating in one or more activities across one or more venues.

[0058] In some cases, in combination with various systems and / or automation disclosed herein (e.g., in combination with automatic identification of participants, access control using participant identifiers, and automatic scoring of activities and associating scores with participant identifiers) activities and / or venues can be operated quickly with reduced or minimized downtime between participants and reduced or minimized operator errors. In addition, automatic scoring can minimize or eliminate the operator interaction necessary to record scores for a particular event. The automatic event access and scoring system 114 can allow the performance of participants in one or more activities across multiple activities to be recorded, displayed, ranked, summarized, and compared, analyzed, and / or stored with the past performance of other users or participants. For example, the performance of a participant in one or more activities can be stored and compared with subsequent or previous performances of the same or different participants in one or more activities. The scoring information can be displayed on any suitable display media, such as display monitors located throughout the venue or away from the venue, live streams (e.g., accessible via the Internet), or via a smart phone.

[0059] The media management system 116 can handle automatic media capture (e.g., audio, photos, and videos). Automatic media capture can include automatically and dynamically generating customized photos, videos, and / or other media data based on the participation of participants in one or more activities at one or more venues. The media management system 116 can be embodied on one or more computers. The media management system 116 can interact with a media capture subsystem associated with the venue. The media capture subsystem can incorporate any number of computers, cameras, sensors, data recording equipment, or other equipment throughout the venue (including the venue's activities). For example, cameras and data recording equipment can be set throughout the venue (including the venue's activities) to capture photos, videos, and / or other media data associated with participants. The media management system 116 can identify photos, videos, and / or other media data associated with participants and bring all media data together. In some cases, compiled videos, photo streams, and / or other output media data can be automatically and dynamically generated for a single activity or multiple activities, which can be used by participants. In some cases, participants can live broadcast photos, videos, and / or other media content while participating in an activity. The system can automatically make decisions and inferences based on the progress of the participants in the activity to change the camera angle or other data sources. The media management system 116 may interact with other systems disclosed herein to facilitate automation of media capture.

[0060] Cameras and other data recording equipment (e.g., scoring sensors) can be located throughout the venue, including on participants or spectators. Cameras can record photos and / or video data, while other data recording equipment can record other types of data, such as scoring or other indicators. In some cases, additional audio sensors (e.g., microphones) can be used to provide audio data for video data or in addition to video data. In an example, a climbing wall may include multiple cameras, such as cameras mounted on helmets, overhead cameras, wide-angle cameras facing the climbing wall, and one or more cameras built into the wall and facing outward, and data recording equipment (e.g., a timer for timing the climb of a participant and a button at the top of the wall that can be actuated by a participant to stop the timer). A computer or other video processing equipment may store feeds from each device (e.g., camera and timer). In some cases, only a compilation of data is stored, rather than a feed from each device.

[0061] In some cases, the device may be worn by the user and / or provided by the user. For example, a heart rate sensor may be used to track a participant's heart rate during a particular activity. Such a heart rate sensor may be provided by the venue and may feed data directly to a computer at or associated with the venue. However, in some cases, the heart rate sensor may be a user-provided device, such as a participant's smartwatch. In such cases, an application or other integration may allow the participant to share heart rate data with a computer at or associated with the venue.

[0062] Metadata may be generated that associates the received participant identifiers with the photo, video, and / or audio data. In some cases, multiple sensors located at the activity may track participants, such as through radio frequency identification triangulation or other techniques. In some cases, multiple participants may participate in a single activity at the same time. In such cases, tracking or other techniques may be used to associate specific device feeds with individual participants. In some cases, mobile cameras may be used to track participants by analyzing tracking data or motion capture data.

[0063] In some cases, the computer can transmit photos, videos and / or other data instantly on a network such as the Internet. In some cases, this type of live broadcast can be integrated with a social media platform to allow a participant to have the opportunity to broadcast his or her participation in an activity to friends and family. The live broadcast can include real-time data from all data sources, and can also include an automatic compilation stream. The automatic compilation stream can include automatic fade-in and fade-out or switch between cameras to keep the participant or the participant's action in the field of view when the participant participates in the activity. For example, in a climbing wall, motion capture, pressure sensors, light sensors or other technologies can be used to automatically determine which cameras to use when the participant advances along the route. In some cases, a stream (such as a video stream or a photo stream) can include other data, such as timer data, heart rate data, scoring information or other indicators and other data associated with the participant's participation in the activity.

[0064] In some cases, photos, videos and / or other data may be stored for transmission to or access by participants after completing an activity and / or leaving a venue. The data may be stored for a predetermined period of time or indefinitely. The data may be stored as a complete feed from each device and / or compiled data (e.g., a compiled video or photo collection). The system may automatically generate compiled data by processing the various feeds from each device. For example, a compiled video may be generated simply by analyzing the motion and other qualities (e.g., exposure and / or color) of the video feed from each camera. In some cases, additional or alternative data (e.g., data from a pressure sensor, proximity sensor, light sensor, acoustic sensor, etc.) synchronized with the video feed may be used to identify which camera is used for a particular segment of the compiled video. A compiled video may be made for each activity, a collection of activities (e.g., similar activities), or an entire visit to a venue or multiple venues.

[0065] In some cases, a participant can interact with the system to select, approve, reject, and / or modify various clips to create his or her own compilation video. In some cases, a participant can access or receive various data, including videos, photos, and / or other data. The data can be transmitted on hardware (e.g., on a memory stick or digital video disc DVD) or over a network (e.g., via email or website access over the Internet).

[0066] In some cases, multiple participants may be associated with a team or group (e.g., a family). In such cases, the system may provide access to feeds and / or compiled videos to individual members of the team or group. For example, parents may be able to access data for themselves and their children. In some cases, the system may generate a compiled video that includes clips from multiple participants associated with a team or group (e.g., per event, per multiple events, or per venue or multiple venues). For example, a soccer team participating in a soccer event may receive a compiled video containing clips from some or all of the participants on the team.

[0067] In some cases, the system may automatically generate comparison data, such as comparing videos, photos, or other data (e.g., heart rate graphs). The comparison may be based on the current participant data and the data being compared. The data being compared may be past data for the participant (e.g., comparing a video from a last visit to a venue or an earlier participation in the event that day) or may be data for another participant (e.g., comparing videos of multiple people on a team or between a participant and the participant with the highest score that week). In another example, a participant in a golf driving event may receive an automatically compiled video showing a slow-motion video of his or her current drive compared side-by-side with a previous drive from an earlier visit to the event (e.g., last week, last month, or last year).

[0068] The venue management system 118 can handle automatic venue management. The venue management system 118 can be embodied on one or more computers. The venue management system 118 can facilitate the interaction between multiple systems, such as the participant identification system and the access system. Each venue can have its own venue management system 118, but in some cases, a single venue management system 118 can be associated with more than one venue. The venue management system 118 can facilitate the coordination of various computers, sensors, cameras, and other equipment associated with multiple activities in the venue. In some cases, when the various systems disclosed herein are implemented locally at the venue, the venue management system 118 can facilitate local coordination of data flows between these systems. However, when one or more systems disclosed herein are implemented away from the venue, the venue management system 118 can facilitate the interaction between the device at the venue and any system away from the venue and the data flow between them. For example, the itinerary generation system can be embodied on a remote server, which can be particularly suitable for efficient access through a web browser when the participant plans to go to the venue in the future. In this example, the venue management system 118 can store a copy of the participant's itinerary at an appropriate time (e.g., on the day or during the time when the participant is scheduled to be at the venue), so that any request to access the participant's itinerary can be quickly processed locally. In some cases, the venue management system 118 may interact with other systems disclosed herein to facilitate managing a particular venue.

[0069] Figure 22 is a schematic diagram depicting a field automation environment 200 associated with a field 202 according to certain aspects of the present disclosure. Field 202 is schematically depicted in a top view, which includes five activities: activity A 204, activity B 206, activity C 208, activity D 210, and activity E 212. Any number of activities may be used, including one or more. Computer A 220 is associated with activity A 204, computer B 222 is associated with activity B 206, computer C 224 is associated with activity C 208, computer D 226 is associated with activity D 210, and computer E 228 is associated with activity E 212. In some cases, a computer associated with an activity may be associated with more than one activity. Field computer 230 may be associated with field 202 as a whole. The computers 220, 222, 224, 226, 228, 230 may receive and transmit information about participants, itineraries, scoring data, media (e.g., photos or videos), schedules, information about the activities 204, 206, 208, 210, 212, information about the venue 202, participant identification data, biometric data, or other data to each other and / or to the server 214. Each of the computers 220, 222, 224, 226, 228, 230 may be coupled to cameras, scoring equipment, sensors, and other devices for acquiring various types of data (e.g., biometric data, scoring data, photos, videos, etc.). Figure 1 The automated management system 102 may be embodied at least in part on one or more computers 220 , 222 , 224 , 226 , 228 , 230 and / or server 214 .

[0070] Server 214 can be a computer located at venue 202 or remote from venue 202. In some cases, server 214 can be implemented on any computer 220, 222, 224, 226, 228, 230, or can be its own computer or computer array. Server 214 can include data storage 216 for storing information necessary to perform any automation disclosed herein, such as information related to participants, itineraries, participant identification data, schedules, activities 204, 206, 208, 210, 212, venue 202, participant identification data, photos, video data, scoring data, biometric data, or other data. In some optional cases, server 214 can be further associated with additional venue 218, which can include its own computer similar to venue 202. Any number of additional venues 218 can be used. Additional venues 218 can be located near venue 202 or remote from venue 202.

[0071] The venue 200 may include any combination of a travel management system, a reservation system, a participant identification system, an access control system, a payment management system, a rating system, a media management system, and a venue management system, for example, Figure 1 The itinerary management system 104, the reservation system 106, the participant identification system 108, the access control system 110, the payment management system 112, the rating system 114, the media management system 116 and the venue management system 118 are included in the embodiment.

[0072] Figure 3 is a schematic diagram depicting an automated event access and scoring system 300 according to certain aspects of the present disclosure. The event access and scoring system 300 incorporates aspects of a participant identification system that operates through the use of user tags (e.g., user 1 tag 330, user 2 tag 338, and user 3 tag 340). Any number of user tags may be used. In some cases, the tags are housed in a wristband, ticket, smartphone, housing, etc. Each user tag is assigned to a participant. Thus, any interaction performed using a particular user tag may be associated with the corresponding participant. The user tags may be read by a tag reader (e.g., tag reader A 332, tag reader B 342, and tag reader Z 352 associated with activity A 336, activity B 346, and activity Z 356, respectively). Any number of tag readers may be used. In some cases, each activity in a venue may have its own associated tag reader, although this may not always be the case. In some cases, an activity may have no tag reader. In some cases, an activity may have multiple tag readers. Although Figure 3 The tags and tag readers depicted in embody certain techniques for participant identification, but the tags and tag readers may be replaced with other participant identification equipment, such as a camera, a Bluetooth tracker, a biometric scanner, an alphanumeric input panel, a barcode scanner, or any other suitable participant identification equipment.

[0073] like Figure 3As depicted, the user 1 tag 330 is held near a tag reader A332 associated with an activity A336. The tag reader A332 may interact with an access system 360 to determine whether a participant associated with the user 1 tag 330 is allowed access to the activity A336. In some cases, an optional payment system 362 may be accessed to deduct credit, initiate payment, or otherwise authorize access to an activity associated with a past, current, or future payment. In some cases, a reservation system 364 may be accessed to determine whether the activity A336 is available to the participant associated with the user 1 tag 330, or whether the activity is booked by another participant at the time. In some cases, the reservation system 364 may indicate that the participant associated with the user 1 tag 330 is scheduled to perform the activity at the time, in which case the reservation system 364 may facilitate authorized access. In some cases, the reservation system 364 may be coupled to the tag readers 332, 342, 362 to allow a participant to reserve a time slot for participating in an associated activity, thereby allowing the participant to participate in other activities rather than waiting in line to participate in a particular activity.

[0074] After granting access to activity A 336, the user can begin participating in the activity. An automatic scoring recorder A 334 associated with activity A 336 can automatically begin tracking scores or other indicators associated with the participant's participation in the activity. The scores or other indicators can be provided to a scoring system 368, which can store the scores with associated participant identifiers (e.g., "user 1," "user 2," "user 3") in a table 370 or other suitable database. Thus, the participant's score can be automatically associated with the participant. As disclosed herein, the automatic scoring recorder can include any suitable sensor, timer, or other equipment necessary to track the scores or other indicators associated with a given activity.

[0075] In some cases, granting access to activity A 336 can cause an optional media management system 366 to automatically begin recording media (e.g., photos or videos) associated with a participant's participation in activity A 336. As disclosed herein, the media management system 336 can automatically capture photos, videos, or other media data associated with a participant. In some cases, the automatically captured media data can be associated or otherwise associated with a score or other metric from a scoring system 368. For example, appropriate scoring information can be automatically incorporated into the media data, such as by overlaying it on a photo or video. In such instances, a video of a participant participating in an activity can be automatically incorporated into a real-time scoreboard or scoreboard overlaid on the video.

[0076] After or before engaging in activity A 336, scanning of User 1 tag 330 by tag reader B 342 or tag reader Z 352 may control access to activity B 346 or activity Z 356, respectively, and initiate automatic scoring by automatic scoring recorder B 344 or automatic scoring recorder Z 354, respectively.

[0077] Figure 4 is a schematic diagram depicting a trip management system 200 according to certain aspects of the present disclosure. The server 214 may be Figure 2 4. Server 414 may include data storage 416 and may be accessed via a network 432, such as a wide area network, such as the Internet or a cloud. Venue computer 430 may be coupled to network 432 to communicate with server 414 to share various information as described herein. In some cases, venue computer 430 may be coupled to computers 420, 422, 424, 426, 428, each of which may be associated with an activity at the venue (e.g., similar to Figure 2 In some cases, computers 420, 422, 424, 426, 428 may relay information to server 414 via venue computer 430, although this is not necessarily the case.

[0078] Through the network 432, the server 414 can be accessed to generate the itinerary. The participant device 436 is Figure 4 436, but any other suitable device may be used, such as a personal computer, tablet, kiosk (e.g., at a venue or a partner location), etc. A participant may interact with a participant device 436 to cause server 414 to generate a participant itinerary 438, which may optionally be stored on the participant device 436. In addition, participant device 436 may store a participant key 440 (e.g., a participant identifier or participant identification information) associated with the participant, with the participant itinerary 438, and / or with individual entries of the participant itinerary 438. A participant may interact with participant device 436 before visiting a venue (e.g., to generate an itinerary for a planned visit), during a visit to a venue (e.g., to update or modify an itinerary), or after leaving a venue (e.g., to review past itineraries or information such as ratings associated with participating in an activity).

[0079] In some cases, an agent device 434 may be used to access server 414 via network 432. Agent device 434 may be any suitable device, such as a personal computer, smartphone, tablet, kiosk, etc. The participant may interact with the agent in person or remotely (e.g., online or by phone) to cause the agent to generate a participant itinerary 442 for the participant. The agent may also generate a participant key 444 to be physically and / or digitally transmitted to the participant.

[0080] Figure 5 is a flow chart depicting a process 500 for generating an itinerary according to certain aspects of the present disclosure. At box 502, participant criteria are received. The participant criteria may be received by accessing a database or receiving input from the participant. The participant criteria may include preferences, package selections, disabilities or limitations, or other criteria. At box 504, participant data is accessed. The participant data may include historical data or other data accessible to the itinerary management system (e.g., stored in a database of the itinerary management system or accessible through a third-party website) that is associated or associable with the participant.

[0081] At block 506, an event schedule for the selected one or more venues may be accessed. The event schedule may include information about when the event is open and / or available, as well as information about when the event is occupied by other participants.

[0082] At block 508, an activity model for the venue may be accessed. The activity model may be used to generate predictions and inferences for individual activities, groups of activities, and / or the entire venue.

[0083] At block 510, a proposed itinerary may be generated for the participant. Generating the proposed itinerary may include using participant criteria. In some cases, generating the proposed itinerary may include using one or more of participant data, event schedule information, event forecasts, or venue forecasts. In some cases, generating the proposed itinerary may include using other information as disclosed herein. The itinerary may be generated to optimize various factors, such as participant criteria, participant preferences, activity usage, activity downtime, venue usage, participant itineraries within the venue (e.g., to optimize foot traffic), or other factors.

[0084] At block 512, the proposed itinerary may be sent to the participant. The proposed itinerary may be sent physically (e.g., by paper) or digitally (e.g., by email or other Internet traffic). At optional block 514, modifications to the proposed itinerary may be received. In an example, the participant may wish to change the itinerary generated at block 510, such as to add or cancel an activity or change the time of an activity.

[0085] At box 516, an activity payment transaction may be initiated and / or the itinerary may be finalized. In the case where payment is not required or otherwise accepted (e.g., at the venue entrance or using a prepaid ticket), box 516 may include finalizing the itinerary, such as receiving confirmation from the participant. However, in some cases, a payment transaction may be initiated at box 516. The payment transaction may include the total cost for entering the venue, the cost of each activity, the cost associated with the rental equipment for participating in any activity, and / or other costs. In some cases, a payment transaction (e.g., payment processing) must be completed before the itinerary is finalized. In some cases, a payment transaction may be initiated but not completed before the itinerary is finalized (e.g., if payment will be collected at a later time). In some cases, initiating a payment transaction may include making a partial payment.

[0086] Once the itinerary is finalized, whether or not after payment, various final actions may occur, such as the actions at blocks 518, 520, and 522. At block 518, the venue's activity schedule may be updated based on the entries in the finalized itinerary. Updating the activity schedule may include reserving a specific time slot for the activity so that the time slot is associated with the participant. At block 520, key information may be updated. Updating the key information may include updating information stored by the itinerary management system, the venue, or the activity, or updating key information stored by the participant. In some cases, updating the key information includes updating permissions associated with an existing key. In some cases, updating the key information includes generating one or more new keys. At block 522, participant data may be updated. For example, the participant data may be updated using activities selected for the itinerary, activities deleted from the itinerary, or any other interactions with or information about the participant available from other parts of process 500.

[0087] Figure 6 6 is a flow diagram depicting a process 600 for updating various information based on activity usage data in accordance with certain aspects of the present disclosure. At block 602, activity usage data may be received. Receiving activity usage data may include receiving any information associated with the activity and / or participation of a participant in the activity, such as the number of individuals in a queue, ratings earned by a participant in the activity, metrics associated with wear and / or maintenance of equipment for the activity, or any other such information associated with use of the activity.

[0088] After receiving the activity usage data at block 602, the activity schedule may optionally be updated at block 604. For example, information indicating future maintenance needs received at block 602 may result in time being reserved on the activity schedule for maintenance.

[0089] After receiving activity usage data at block 602, activity models may optionally be updated at block 606. For example, if the data received at block 602 regularly indicates that participants are spending more time participating in an activity than expected, any models associated with the activity may be updated to provide more accurate predictions.

[0090] After receiving the activity usage data at block 602, the participant data may optionally be updated at block 608. For example, if the data received at block 602 indicates that a participant scored highly at a particular activity, the participant data associated with the participant may be updated to reflect the rating earned, reflect high performance at the activity, and / or reflect an inference that the participant enjoyed the activity.

[0091] In some cases, after receiving the activity usage data at block 602, other information may be updated.

[0092] Figure 7 700 for dynamically updating an itinerary according to certain aspects of the present disclosure. Dynamic updates of a participant's itinerary may be initiated automatically upon receipt of new or updated information (e.g., as described with reference to blocks 702, 704, 706), may be performed periodically according to a schedule, or may be initiated on demand upon request (e.g., by a participant or venue representative). Dynamic updates may be performed to provide suggestions to improve the participant's experience, to provide necessary updates (e.g., due to delays or maintenance), or otherwise.

[0093] One or more of blocks 702, 704, 706 may initiate a dynamic update of a participant's itinerary. At block 702, an updated activity schedule may be received. The updated activity schedule may indicate that an activity is no longer available for a particular time slot, or that an activity is now free during a time slot (e.g., a previously desired time slot). At block 704, participant activity usage data may be received. In an instance, the participant activity usage data may include a start time at which a participant begins a first activity. In this instance, the start time and expected duration of the first activity may lead to an inference that the participant may not be able to maintain his or her itinerary, thereby facilitating an update. Other instances may be used. At block 706, any activity data may be received, such as a participant score, information indicating a need for future maintenance requirements, or any other such information.

[0094] At block 708, the participant itinerary may be accessed. The itinerary may be used to determine whether any modifications are desired and / or necessary. At block 710, proposed and / or mandatory modifications to the participant itinerary may be generated and / or sent. The modifications may be based on one or more updated activity schedules received at block 702, the participant activity usage data received at block 704, and / or the activity data received at block 706, although other information may also be used. For example, location information may be accessed to suggest an itinerary based on the participant's current location.

[0095] At optional block 712, confirmation of the proposed modification may be received.

[0096] Once the itinerary modification is sent and / or confirmed, various final actions may occur, such as the actions at blocks 714, 716, and 718. At block 714, the event schedule for the venue may be updated based on the entries in the modified itinerary. Updating the event schedule may include reserving a specific time slot for the event so that the time slot is associated with the participant. At block 716, key information may be updated. Updating the key information may include updating information stored by the itinerary management system, the venue, or the event, or updating key information stored by the participant. In some cases, updating the key information includes updating permissions associated with an existing key. In some cases, updating the key information includes generating one or more new keys. At block 718, participant data may be updated. For example, participant data may be updated by confirming or rejecting the proposed modification or any other interaction with the participant or information about the participant available from other parts of process 700.

[0097] Figure 8 is a schematic diagram depicting a media management system 800 according to certain aspects of the present disclosure. The server 814 may be Figure 2 814. The server 814 may include a data store 816 and may be accessed via a network 832, such as a wide area network, such as the Internet or a cloud. A venue computer 830 may be coupled to the network 832 to communicate with the server 814 to share various information as described herein. In some cases, the venue computer 830 may be coupled to computers 820, 822, 824, 826, 828, each of which may be associated with an activity at the venue (e.g., similar to Figure 2820, 222, 224, 226, 228). In some cases, the computers 820, 822, 824, 826, 828 may relay information to the server 814 via the venue computer 830, although this is not necessarily the case. The computer 828 is depicted as being coupled to two cameras 840 and a sensor 842 (e.g., a heart rate sensor or a sensor associated with a timer). The computer 828 may receive photo and / or video data via the cameras 840 and may receive other data via the sensors 842. Each of the computers 820, 822, 824, 826, 828, 830 may be coupled to any number of cameras and other sensors, similar to those depicted for the computer 828.

[0098] Through the network 832, the server 814 can be accessed to retrieve photos, videos and / or other data. Figure 8 836, but any other suitable device may be used, such as a personal computer, tablet computer, kiosk (e.g., at a venue or collaborative location), etc. Participants may interact with participant device 836 to access and / or download photos, videos, and / or other data from server 814, such as participant recordings 838 or other participant data 840. In some cases, server 814 may provide participant recordings 838 as a compiled video, etc. In other cases, server 814 may provide separate feeds from multiple cameras, allowing a participant to mix his or her own compiled video at a later time. In some cases, a participant may interact with server 814 using participant device 836 to provide instructions or requests on how a compiled video or other product will be generated.

[0099] In some cases, a viewer device 834 may be used to access the server 814 via the network 832. The viewer device 834 may be any suitable device, such as a personal computer, a smart phone, a tablet computer, a kiosk, etc. The viewer may access historical and / or live photos, videos, and / or other data from one or more activities in which the participant participated. For example, the depicted viewer device 834 displays photos or videos and displays text that may be automatically generated metrics and / or ratings of the participants participating in the activity (e.g., the current height climbed on the climbing wall). In some cases, the viewer device 834 may access a feed (e.g., live or historical) of a particular participant by providing a key, which may be provided to the viewer by the participant.

[0100] Fig. 9 980 is a simplified block diagram depicting a computer system 980 according to certain aspects of the present disclosure, which may include components of the various systems and devices described herein. For example, the computer system 980 may be a network device or server as described herein, such as Figure 2 Server 214, Figure 2 Computer 230, 220, 222, 224, 226, 228 or Figure 2 234, 236. In some cases, a computing device may include some or all of the components of a computer system 980. The computer system 980 may include one or more processors 982 that communicate with a plurality of peripheral subsystems via a bus subsystem 984. These peripheral subsystems may include a storage subsystem 986 (including a memory subsystem 988 and a file storage subsystem 990), a user interface input device 992, a user interface output device 994, and a network interface subsystem 996.

[0101] The bus subsystem 984 may provide a mechanism for allowing the various components and subsystems of the computer system 980 to communicate with each other as intended. Although the bus subsystem 984 is schematically shown as a single bus, in some cases the bus subsystem may utilize multiple busses.

[0102] The processor 982, which may be implemented as one or more integrated circuits (e.g., conventional microprocessors or microcontrollers), controls the operation of the computer system 980. One or more processors 982 may be provided. These processors may include single-core or multi-core processors. In some cases, the processor 982 may execute various programs in response to program code, and may maintain multiple programs or processes that are executed simultaneously. At any given time, some or all of the program code to be executed may reside in the processor 982 and / or the storage subsystem 986. Through appropriate programming, the processor 982 may provide the various functions described above.

[0103] The network interface subsystem 996 provides an interface with other computer systems and networks. The network interface subsystem 996 is used to receive data from the computer system 980 and send the data to the interface of other systems. For example, the network interface subsystem 996 can make the computer system 980 connected to one or more devices through the Internet. In some cases, the network interface 996 may include a radio frequency (RF) transceiver component for accessing a wireless voice and / or data network (e.g., using cellular phone technology, advanced data network technology such as 3G, 4G or EDGE, WiFi (IEEE 802.11 series standards, or other mobile communication technologies or any combination thereof), a GPS receiver component and / or other components. In some cases, the network interface 996 can provide a wired network connection (e.g., Ethernet) in addition to or in place of a wireless interface.

[0104] The user interface input device 992 may include a keyboard, a pointing device such as a mouse or trackball, a touchpad or touch screen incorporated into a display, a scroll wheel, a click wheel, a dial, buttons, switches, a keypad, an audio input device, a microphone, an eye gaze system, and other types of input devices. Generally, the use of the term "input device" is intended to include all possible types of devices and mechanisms for inputting information to the computer system 980. For example, in many smart phones, the user input device 992 may include one or more buttons provided by the smart phone, a touch screen that can display a soft keyboard, a digital peripheral interface, a built-in microphone, etc.

[0105] The user interface output device 994 may include a display subsystem, indicator lights, or non-visual displays such as audio output devices, etc. The display subsystem may be a cathode ray tube (CRT), a flat panel device such as a liquid crystal display (LCD), a projection device, a touch screen, etc. In general, the use of the term "output device" is intended to include all possible types of devices and mechanisms for outputting information from the computer system 980. For example, a flat panel screen may be used to display a soft keyboard.

[0106] The storage subsystem 986 provides a computer-readable storage medium for storing basic programming and data structures that provide the functionality of various aspects disclosed herein. The storage subsystem 986 can be implemented (for example) using any combination of disks, flash memory, or any other storage medium, and can include volatile and / or non-volatile storage devices as needed. Software (programs, code modules, instructions) that provide the above-mentioned functions when executed by the processor can be stored in the storage subsystem 986. These software modules or instructions can be executed by the processor 982. The storage subsystem 986 can also provide a repository for storing data used in accordance with the present disclosure. The storage subsystem 986 can include a memory subsystem 988 and a file / disk storage subsystem 990.

[0107] The memory subsystem 988 may include a plurality of memories including a main random access memory (RAM) 998 for storing instructions and data during program execution and a read only memory (ROM) 999 in which fixed instructions are stored. The file storage subsystem 990 may provide persistent (non-volatile) memory storage for program and data files and may include a hard drive, a floppy disk drive and associated removable media, a compact disk read-only memory (CD-ROM) drive, an optical drive, removable media cartridges, and other similar memory storage media.

[0108] Computer system 980 can be of various types, including a personal computer, a portable device (e.g., a smartphone, a tablet, etc.), a workstation, a network computer, a mainframe, a kiosk, a server, or any other data processing system. Due to the ever-changing nature of computers and networks, Fig. 9 The description of the computer system 980 depicted in FIG. 1 is intended only as a specific example. Fig. 9 Many other configurations are possible with more or fewer components of the depicted systems.

[0109] Fig.10 1 is a schematic diagram depicting a customized itinerary display 1000 on a computing device 1002 according to certain aspects of the present disclosure. Computing device 1002 can be any suitable computing device, such as a tablet, a smartphone, a kiosk, or other computing device. Customized itinerary display 1000 can display information about a participant's customized itinerary. In some cases, customized itinerary display 1000 can be interactive and can allow editing, updating, or otherwise interacting with a participant's customized itinerary.

[0110] In some cases, the customized itinerary display 1000 may include a map portion 1004 and a schedule portion 1006. The map portion 1004 may display a map 1008 of the venue, which may include any number of activities. The schedule portion 1006 may display schedule information related to the participant's customized itinerary.

[0111] exist Fig.10 , the schedule portion 1006 may display participant information 1012 (e.g., name, participant identifier, photo or avatar, or other appropriate information). The schedule portion 1006 may display a schedule 1010, which may present the various items on the participant's itinerary in order. The schedule 1010 may include any suitable information for multiple itinerary items, such as itinerary item numbers 1014, time slots 1016, activity names 1018, and optional activity logos. In some cases, the schedule 1010 may include only scheduled activities, although in some cases the schedule 1010 may include free time slots. In some cases, the schedule 1010 may display suggested activities for the participant, such as suggested activities that the participant may enjoy and / or activities located near existing itinerary items that also have open time slots.

[0112] The map portion 1004 may include a custom map 1008 having an indicator 1022 for one or more activities and / or itinerary items in the itinerary. Each indicator 1022 may be associated with an activity and / or itinerary item, such as by displaying a number or other identifier associated with an itinerary item number 1014 of the activity. In some cases, the indicator 1022 and the itinerary item number 1014 may be a sequential number associated with the sequence of activities and / or itinerary items on the custom itinerary. Each indicator 1022 may be presented on the custom map 1008 at a location associated with an entrance, a starting point, a queue, or other locations associated with the associated activity. Therefore, participants may browse the custom map 1008 and the indicator 1022 to quickly determine the planned path of the participant throughout the venue. In some cases, the indicator 1022 may include other visual perception features (e.g., a small clock, color coding, size, shadow, emphasis) that may indicate a sequence or time slot associated with the activity indicated by the indicator 1022. In some cases, as the participant completes each activity and / or over time, the indicator 1022 and trip item number 1014 may be dynamically updated so that the next instant activity and / or trip item is associated with a particular number (eg, 1 or 2).

[0113] In some cases, the custom map 1008 may also present a participant location indicator 1024 that shows the participant's current location in the venue. In some cases, the custom map 1008 may also present one or more path overlays 1026 that indicate the general paths that participants can take between activities and / or itinerary items.

[0114] In the above description, various aspects of the present disclosure are described with reference to the specific embodiments of the present disclosure, but those skilled in the art will recognize that the present disclosure is not limited thereto. The various features and aspects of the above invention may be used alone or in combination. In addition, without departing from the broader spirit and scope of the present description, the embodiments may be used in any number of environments and applications other than those described herein. Therefore, the description and the accompanying drawings are considered to be illustrative rather than restrictive.

[0115] In the foregoing description, for the purpose of illustration, the method is described in a specific order. It should be understood that in alternative embodiments, the method may be performed in a different order than described. It should also be understood that the above method may be performed by hardware components, or may be implemented in the order of machine executable instructions, which may be used to enable a machine (e.g., a general or special processor or a logic circuit programmed with these instructions) to perform these methods. These machine executable instructions may be stored on one or more machine-readable media, such as a CD-ROM or other type of optical disk, a floppy disk, a ROM, a RAM, an electrically programmable read-only memory EPROM, an electrically erasable read-only memory EEPROM, a magnetic card or an optical card, a flash memory, or other types of machine-readable media suitable for storing electronic instructions. Alternatively, these methods may be performed by a combination of hardware and software.

[0116] Where components are described as being configured to perform certain operations, such configuration may be achieved, for example, by designing electronic circuits or other hardware to perform the operations, by programming programmable electronic circuits (e.g., a microprocessor or other suitable electronic circuits) to perform the operations, or any combination thereof.

[0117] The above description of the embodiments, including the illustrated embodiments, is presented for the purpose of illustration and description only and is not intended to be exhaustive or to limit the precise form disclosed. For those skilled in the art, various modifications, adaptations, and uses thereof will be apparent.

[0118] As used below, any reference to a series of examples should be understood to refer to each of the examples separately (eg, "Example 1 -Example 4" should be understood to refer to "Example 1, 2, 3, or 4").

[0119] Example 1 is a system comprising: one or more data processors; and a non-transitory computer-readable storage medium containing instructions that, when executed on the one or more data processors, cause the one or more data processors to perform operations including: using a participant identification system to detect a participant identifier associated with a participant attempting to participate in an event at a multi-event venue; using the detected participant identifier to determine that the participant is allowed to access the event; receiving scoring information associated with the participant's participation in the event; automatically associating the scoring information with the participant identifier; and storing the associated scoring information and participant identifier.

[0120] Example 2 is the system of example 1, wherein receiving the scoring information comprises automatically initiating a scoring system and automatically receiving the scoring information from a set of scoring sensors.

[0121] Example 3 is a system described in Example 1 or Example 2, wherein the operation further includes: automatically recording media data associated with the participant's participation in the activity; automatically associating the recorded media data with the participant identifier; and storing the associated recorded media data and participant identifier.

[0122] Example 4 is the system of example 3, wherein automatically associating the recorded media data with the participant identifier further comprises automatically associating the recorded media data with the rating information and storing the associated recorded media data with the rating information.

[0123] Example 5 is the system of example 4, wherein the operations further comprise automatically editing the recorded media data using the rating information.

[0124] Example 6 is the system described in Examples 3-5, wherein automatically recording media data associated with the participant's participation in the activity includes automatically switching between multiple recording devices during the participant's participation in the activity, wherein automatically switching between the multiple recording devices includes selecting a desired recording device from the multiple recording devices based on received sensor input.

[0125] Example 7 is the system of examples 1-6, wherein determining that the participant is allowed to access the activity includes initiating payment associated with participating in the activity using the detected participant identifier.

[0126] Example 8 is the system of examples 1-7, wherein determining that the attendee is allowed to access the activity comprises accessing a reservation system to confirm that a reservation associated with the attendee identifier and the activity exists at a given time.

[0127] Example 9 is the system of examples 1-8, wherein the operations further include: accessing a customization database and retrieving a participant customization using the participant identifier; and customizing the participant's participation in the activity using the participant customization.

[0128] Example 10 is the system of examples 1-9, wherein the activity is exercise.

[0129] Example 11 is the system of examples 1-10, wherein the activity is a skill-based or competency-based activity.

[0130] Example 12 is a computer-implemented method comprising: using a participant identification system to detect a participant identifier associated with a participant attempting to participate in an event at a multi-event venue; using the detected participant identifier to determine that the participant is permitted to access the event; receiving scoring information associated with the participant's participation in the event; automatically associating the scoring information with the participant identifier; and storing the associated scoring information and participant identifier.

[0131] Example 13 is the method of example 12, wherein receiving the scoring information comprises automatically initiating a scoring system and automatically receiving the scoring information from a set of scoring sensors.

[0132] Example 14 is the method described in Example 12 or Example 13, further comprising: automatically recording media data associated with the participant's participation in the activity; automatically associating the recorded media data with the participant identifier; and storing the associated recorded media data and participant identifier.

[0133] Example 15 is the method of example 14, wherein automatically associating the recorded media data with the participant identifier further comprises automatically associating the recorded media data with the rating information, and storing the associated recorded media data with the rating information.

[0134] Example 16 is the method of example 15, further comprising automatically editing the recorded media data using the rating information.

[0135] Example 17 is the method described in Examples 14-16, wherein automatically recording media data associated with the participant's participation in the activity includes automatically switching between multiple recording devices during the participant's participation in the activity, wherein automatically switching between the multiple recording devices includes selecting a desired recording device from the multiple recording devices based on received sensor input.

[0136] Example 18 is the method of examples 12-17, wherein determining that the participant is allowed to access the activity includes initiating payment associated with participating in the activity using the detected participant identifier.

[0137] Example 19 is the method of examples 12-18, wherein determining that the participant is allowed to access the activity comprises accessing a reservation system to confirm that a reservation associated with the participant identifier and the activity exists at a given time.

[0138] Example 20 is the method of examples 12-19, further comprising: accessing a customization database and retrieving a participant customization using the participant identifier; and customizing the participant's participation in the activity using the participant customization.

[0139] Example 21 is the method of examples 12-20, wherein the activity is exercise.

[0140] Example 22 is the method described in examples 12-21, wherein the activity is a skill-based or competency-based activity.

[0141] Example 23 is a computer program product tangibly embodied in a non-transitory machine-readable storage medium, comprising instructions configured to cause a data processing device to perform operations including: using a participant identification system to detect a participant identifier associated with a participant attempting to participate in an event at a multi-event venue; using the detected participant identifier to determine that the participant is permitted to access the event; receiving scoring information associated with the participant's participation in the event; automatically associating the scoring information with the participant identifier; and storing the associated scoring information and participant identifier.

[0142] Example 24 is the computer program product of example 23, wherein receiving the scoring information comprises automatically initiating a scoring system and automatically receiving the scoring information from a set of scoring sensors.

[0143] Example 25 is a computer program product of Example 23 or Example 24, wherein the operation further includes: automatically recording media data associated with the participant's participation in the activity; automatically associating the recorded media data with the participant identifier; and storing the associated recorded media data and participant identifier.

[0144] Example 26 is the computer program product of Example 25, wherein automatically associating the recorded media data with the participant identifier further comprises automatically associating the recorded media data with the rating information, and storing the associated recorded media data with the rating information.

[0145] Example 27 is the computer program product of example 26, wherein the operations further comprise automatically editing the recorded media data using the rating information.

[0146] Example 28 is a computer program product of Examples 25-27, wherein automatically recording media data associated with the participant's participation in the activity includes automatically switching between multiple recording devices during the participant's participation in the activity, wherein automatically switching between the multiple recording devices includes selecting a desired recording device from the multiple recording devices based on received sensor input.

[0147] Example 29 is the computer program product of examples 23-28, wherein determining that the participant is allowed to access the activity includes initiating a payment associated with participating in the activity using the detected participant identifier.

[0148] Example 30 is the computer program product of examples 23-29, wherein determining that the participant is allowed to access the activity comprises accessing a reservation system to confirm that a reservation associated with the participant identifier and the activity exists at a given time.

[0149] Example 31 is the computer program product of examples 23-30, wherein the operations further comprise: accessing a customization database and retrieving a participant customization using the participant identifier; and customizing the participant's participation in the activity using the participant customization.

[0150] Example 32 is the computer program product of Examples 23-31, wherein the activity is exercise.

[0151] Example 33 is the computer program product of examples 23-32, wherein the activity is a skill-based or competency-based activity.

[0152] Example 34 is a system comprising: one or more data processors; and a non-transitory computer-readable storage medium containing instructions that, when executed on the one or more data processors, cause the one or more data processors to perform operations including: receiving preferences associated with participating in one or more of a plurality of activities at a multi-event venue, wherein the preferences are associated with a participant; automatically generating an itinerary using the received preferences, wherein the itinerary includes reservations for the plurality of activities; associating the itinerary with a participant identifier, wherein the participant identifier is associated with the participant; storing the itinerary, wherein storing the itinerary includes using the reservation to reserve time slots associated with a plurality of activities at the multi-event venue; receiving a request to participate in one of the plurality of activities during one of the time slots, wherein the participation request includes the participant identifier; and approving the participation request, wherein approving the participation request includes using the itinerary to determine that the participant identifier is associated with the one of the time slots and the one of the plurality of activities.

[0153] Example 35 is the system of example 34, wherein automatically generating an itinerary includes scheduling a first activity immediately before a subsequent activity, wherein an exit of the first activity is associated with an entrance of the subsequent activity.

[0154] Example 36 is the system of example 34 or example 35, wherein automatically generating an itinerary includes scheduling a first activity immediately before a subsequent activity, wherein equipment used during participation in the first activity is also used for participation in the subsequent activity.

[0155] Example 37 is the system of Examples 34-36, wherein the participant identifier is associated with a group having multiple participants, wherein an existing itinerary is associated with at least one of the multiple participants, and wherein automatically generating the itinerary includes accessing the existing itinerary.

[0156] Example 38 is the system of Examples 34-37, wherein the operations further include: identifying a proposed modification to the itinerary; sending a request to modify the itinerary based on the proposed modification; receiving an approval associated with the request to modify the itinerary; and updating the itinerary with the proposed modification upon receiving the approval.

[0157] Example 39 is a computer-implemented method comprising: receiving preferences associated with participating in one or more of a plurality of activities at a multi-event venue, wherein the preferences are associated with a participant; automatically generating an itinerary using the received preferences, wherein the itinerary includes reservations for the plurality of activities; associating the itinerary with a participant identifier, wherein the participant identifier is associated with the participant; storing the itinerary, wherein storing the itinerary includes using the reservation to reserve a time slot associated with a plurality of activities at the multi-event venue; receiving a request to participate in one of the plurality of activities during one of the time slots, wherein the participation request includes the participant identifier; and approving the participation request, wherein approving the participation request includes using the itinerary to determine that the participant identifier is associated with the one of the time slots and the one of the plurality of activities.

[0158] Example 40 is the method of example 39, wherein automatically generating the itinerary includes scheduling a first activity immediately before a subsequent activity, wherein an exit of the first activity is associated with an entrance of the subsequent activity.

[0159] Example 41 is the method of example 39 or example 40, wherein automatically generating the itinerary includes scheduling a first activity immediately before a subsequent activity, wherein equipment used during participation in the first activity is also used for participation in the subsequent activity.

[0160] Example 42 is the method described in Examples 39-41, wherein the participant identifier is associated with a team having multiple participants, wherein an existing itinerary is associated with at least one of the multiple participants, and wherein automatically generating the itinerary includes accessing the existing itinerary.

[0161] Example 43 is the method of Examples 39-42, further comprising: identifying a proposed modification to the itinerary; sending a request to modify the itinerary based on the proposed modification; receiving an approval associated with the request to modify the itinerary; and updating the itinerary with the proposed modification upon receiving the approval.

[0162] Example 44 is a computer program product tangibly embodied in a non-transitory machine-readable storage medium, comprising instructions configured to cause a data processing device to perform operations including: receiving preferences associated with participation in one or more of a plurality of activities at a plurality of event venues, wherein the preferences are associated with a participant; automatically generating an itinerary using the received preferences, wherein the itinerary includes reservations for the plurality of activities; associating the itinerary with a participant identifier, wherein the participant identifier is associated with the participant; storing the itinerary, wherein storing the itinerary includes using the reservation to reserve a time slot associated with a plurality of activities at the plurality of event venues; receiving a request to participate in one of the plurality of activities during one of the time slots, wherein the participation request includes the participant identifier; and approving the participation request, wherein approving the participation request includes using the itinerary to determine that the participant identifier is associated with the one of the time slots and the one of the plurality of activities.

[0163] Example 45 is the computer program product of example 44, wherein automatically generating an itinerary includes scheduling a first activity immediately before a subsequent activity, wherein an exit of the first activity is associated with an entrance of the subsequent activity.

[0164] Example 46 is the computer program product of example 44 or example 45, wherein automatically generating an itinerary includes scheduling a first activity immediately before a subsequent activity, wherein equipment used during participation in the first activity is also used for participation in the subsequent activity.

[0165] Example 47 is the computer program product of Examples 44-46, wherein the participant identifier is associated with a team having multiple participants, wherein an existing itinerary is associated with at least one of the multiple participants, and wherein automatically generating the itinerary includes accessing the existing itinerary.

[0166] Example 48 is the computer program product of Examples 44-47, wherein the operations further include: identifying a proposed modification to the itinerary; sending a request to modify the itinerary based on the proposed modification; receiving an approval associated with the request to modify the itinerary; and updating the itinerary with the proposed modification upon receiving the approval.

Claims

1. A system comprising: one or more data processors; and A non-transitory computer-readable storage medium containing instructions that, when executed on the one or more data processors, cause the one or more data processors to perform operations including: receiving preferences associated with participation in one or more of a plurality of events at a multi-event venue, wherein the preferences are associated with a participant; automatically generating an itinerary using the received preferences, wherein the itinerary includes reservations for the plurality of activities; associating the trip with a participant identifier associated with the participant; storing the itinerary, wherein storing the itinerary comprises using the reservation to reserve time slots associated with the plurality of events at the multi-event venue; receiving a request to participate in one of the plurality of activities during one of the time slots, wherein the participation request includes the participant identifier; as well as The participation request is approved, wherein approving the participation request includes determining, using the itinerary, that the participant identifier is associated with the one of the time slots and the one of the plurality of activities. 2 . The system of claim 1 , wherein automatically generating the itinerary comprises scheduling a first activity immediately before a subsequent activity, wherein an exit of the first activity is associated with an entrance of the subsequent activity. 3 . The system of claim 1 , wherein automatically generating the itinerary comprises scheduling a first activity immediately before a subsequent activity, wherein equipment used during participation in the first activity is also used for participation in the subsequent activity.

4. The system of claim 1, wherein the participant identifier is associated with a group having a plurality of participants, wherein an existing itinerary is associated with at least one of the plurality of participants, and wherein automatically generating the itinerary comprises accessing the existing itinerary.

5. The system of claim 1, wherein the operations further comprise: identifying proposed modifications to the itinerary; sending a request to modify the itinerary based on the proposed modification; receiving an approval associated with the request to modify the itinerary; and The itinerary is updated with the proposed modification upon receipt of the approval.

6. A computer-implemented method comprising: receiving preferences associated with participation in one or more of a plurality of events at a multi-event venue, wherein the preferences are associated with a participant; automatically generating an itinerary using the received preferences, wherein the itinerary includes reservations for the plurality of activities; associating the trip with a participant identifier associated with the participant; storing the itinerary, wherein storing the itinerary comprises using the reservation to reserve time slots associated with the plurality of events at the multi-event venue; receiving a request to participate in one of the plurality of activities during one of the time slots, wherein the participation request includes the participant identifier; as well as The participation request is approved, wherein approving the participation request includes determining, using the itinerary, that the participant identifier is associated with the one of the time slots and the one of the plurality of activities. 7 . The method of claim 6 , wherein automatically generating the itinerary comprises scheduling a first activity immediately before a subsequent activity, wherein an exit of the first activity is associated with an entrance of the subsequent activity.

8. The method of claim 6, wherein automatically generating the itinerary comprises scheduling a first activity immediately prior to a subsequent activity, wherein equipment used during participation in the first activity is also used to participate in the subsequent activity.

9. The method of claim 6, wherein the participant identifier is associated with a group having a plurality of participants, wherein an existing itinerary is associated with at least one of the plurality of participants, and wherein automatically generating the itinerary comprises accessing the existing itinerary.

10. The method according to claim 6, further comprising: identifying proposed modifications to the itinerary; sending a request to modify the itinerary based on the proposed modification; receiving an approval associated with the request to modify the itinerary; and The itinerary is updated with the proposed modification upon receipt of the approval.

11. A computer program product tangibly embodied in a non-transitory machine-readable storage medium, comprising instructions configured to cause a data processing apparatus to perform operations comprising: receiving preferences associated with participation in one or more of a plurality of events at a multi-event venue, wherein the preferences are associated with a participant; automatically generating an itinerary using the received preferences, wherein the itinerary includes reservations for the plurality of activities; associating the trip with a participant identifier associated with the participant; storing the itinerary, wherein storing the itinerary comprises using the reservation to reserve time slots associated with the plurality of events at the multi-event venue; receiving a request to participate in one of the plurality of activities during one of the time slots, wherein the participation request includes the participant identifier; as well as The participation request is approved, wherein approving the participation request includes determining, using the itinerary, that the participant identifier is associated with the one of the time slots and the one of the plurality of activities.

12. The computer program product of claim 11, wherein automatically generating the itinerary comprises scheduling a first activity immediately before a subsequent activity, wherein an exit of the first activity is associated with an entrance of the subsequent activity.

13. The computer program product of claim 11, wherein automatically generating the itinerary comprises scheduling a first activity immediately prior to a subsequent activity, wherein equipment used during participation in the first activity is also used to participate in the subsequent activity.

14. The computer program product of claim 11, wherein the participant identifier is associated with a team having a plurality of participants, wherein an existing itinerary is associated with at least one of the plurality of participants, and wherein automatically generating the itinerary comprises accessing the existing itinerary.

15. The computer program product of claim 11, wherein the operations further comprise: identifying proposed modifications to the itinerary; sending a request to modify the itinerary based on the proposed modification; receiving an approval associated with the request to modify the itinerary; and The itinerary is updated with the proposed modification upon receipt of the approval.

Citation Information

Patent Citations

  • Real-time event feedback

    US20130231760A1

  • System and method for determining a duration for user activities based on social-network events

    US20140122483A1

  • System and method for enhanced event participation

    US20140358632A1

  • Automated mall concierge

    US20150369611A1

  • Facial recognition for event venue cameras

    US20160073010A1