Golf event management system with score and location tracking

Abstract

A score tracking system can include a tracking module, a companion device, and a location system. The tracking module may be configured to be carried by a player participating in a golf tournament. The companion device may be configured to receive an input corresponding to a stroke event, the input including a timestamp corresponding to the occurrence of the stroke event. The location system can collect or receive location data used by the location system to include or generate a plurality of sets of location coordinates. Each set of location coordinates corresponds to the position of the tracking module at a specified time. The location system can pair the timestamp with a set of location coordinates corresponding to the position of the tracking module at the time of the occurrence of the stroke event.

Description

[Technical Field]

[0001] The present disclosure relates to golf event management, including score and location tracking systems and methods that are generally adaptable to multiple network infrastructures. background

[0002] Managing the play of a golf tournament while tracking the detailed location and score of every shot requires complex behind-the-scenes operations, made even more difficult by the diversity of course locations and infrastructure. For example, before each PGA Tour event, each golf course is mapped, creating a digital image of each hole. This image is used as background information to calculate the precise location and distance between two coordinates (e.g., the tee box and the player's first shot, or the shot location and the hole location). The PGA Tour uses this mapping data in conjunction with its ShotLink system to collect the location and score of every ball on every shot for every round. In addition to pre-tournament mapping, the ShotLink system also utilizes complex and costly infrastructure that takes days to set up and tear down and must be transported between events. Successful operation of the ShotLink system also relies on a volunteer workforce of up to 350 people per event. The tournament data provided by the ShotLink system has proven valuable to fans and players alike. However, the time, expense, and infrastructure required to operate the ShotLink system make it impractical for use in lower-level tournaments.

[0003] What is needed is a system and method for providing golf event management that provides accurate tracking operations in a portable design, reduces setup time and personnel, and is widely adaptable to course conditions and infrastructure. Summary of the Invention

[0004] In a first aspect, the score tracking system includes a tracking module and one or both of an application and a location system. In one example, the tracking module and one or both of the application and location tracking system can be according to any example, configuration, or embodiment described herein. In one example, the tracking module may be configured to be carried by a player participating in a golf tournament. The application may be configured to interface a scoring operation to a user via a user interface of a companion device. The companion device may be separate from the tracking module and configured to receive input via the user interface indicating the occurrence of a stroke event. This input enables the application to set a timestamp corresponding to the occurrence of the stroke event. In one configuration, the stroke event includes an address and a ball hit. In the above or another configuration, the interface includes an indicator configured to be pressed to indicate that the player is addressing the ball and to be held until the player hits the ball to indicate that the ball has been hit. In examples including a location system, the location system may be configured to collect or receive location data. The location data may include multiple sets of location coordinates or may be used by the location system to generate multiple sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a specified time. In one example, the location system may be configured to pair a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time of the stroke event.

[0005] In any of the above or other examples of the first aspect, the position of the tracking module at the time of the stroke event can be used as a proxy for the position of the ball of the player carrying the tracking module due to the previous stroke.

[0006] In any of the above or other examples of the first aspect, the tracking module may be configured to operate as a beacon in a location network. In a further example, the location network utilizes ultra-wide band positioning.

[0007] In any of the above or other examples of the first aspect, the tracking module can be configured to transmit the location data to a location system.

[0008] In any of the above examples or other examples of the first aspect, the location system may be configured to receive location data from a location network, and the location network may be configured to calculate multiple sets of location coordinates.

[0009] In any of the above or other examples of the first aspect, the location data collected or received by the location system includes position specific data that the location system uses to calculate location coordinates.

[0010] In any of the above or other examples of the first aspect, the multiple sets of location coordinates consist of sets of GPS coordinates.

[0011] In any of the above or other examples of the first aspect, the multiple sets of location coordinates consist of sets of ultra-wideband positioning coordinates.

[0012] In any of the above or other examples of the first aspect, the tracking module may be configured to collect location data at a first predefined interval and transmit the collected location data to the location system at a second predefined interval, the second interval being greater than the first interval.

[0013] In any of the above or other examples of the first aspect, the location system may be configured to divide holes on a golf course into zones, each zone corresponding to a range of location coordinates, and the location system may be configured to determine a current zone in which the tracking module is located from multiple sets of location coordinates.

[0014] In any of the above or other examples of the first aspect, the companion device may be configured to be carried by a scorer accompanying a group of players that includes the player, and the companion device may be configured to receive inputs corresponding to stroke events of all players in the group.

[0015] In any of the above or other examples of the first aspect, the stroke event includes a ball hit, and the position of the tracking module at the time of the stroke event can be used as a proxy for the position of the ball of the player carrying the tracking module due to the previous stroke.

[0016] In any of the above or other examples of the first aspect, the tracking module operates as a beacon in a location network. In one configuration, the location network utilizes ultra-wideband positioning.

[0017] In a second aspect, a score tracking method includes receiving input from a companion device corresponding to stroke events of a player participating in a golf tournament. The input can include a timestamp corresponding to the occurrence of the stroke event. The method can further include collecting or receiving location data by a location system. The location data can correspond to a location of a tracking module carried by the player. The location data can include multiple sets of location coordinates or can be used to generate multiple sets of location coordinates, each set of location coordinates corresponding to the location of the tracking module at a specified time.

[0018] In one example, a first embodiment of the second aspect includes pairing a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred. The companion device may include an interface configured to receive input corresponding to the stroke event. The stroke event may include an address and a ball hit. The interface may include an indicator configured to be pressed to indicate that the player is addressing the ball and to be held until the player hits the ball to indicate that the ball has been hit.

[0019] In one example, a second embodiment of the second aspect includes pairing a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time of the occurrence of a stroke event, which can be entered into a companion device by a scorer watching live video of the golf tournament.

[0020] In one example, a third embodiment of the second aspect includes pairing a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time of the occurrence of a stroke event, which can be entered into the companion device by a scorer watching a video replay of the golf tournament.

[0021] In one example, the second aspect includes any combination of the first, second, or third embodiments.

[0022] In any of the above examples of the second aspect, the companion device can be carried by a scorer accompanying a group of players including the player, and the companion device can receive inputs corresponding to stroke events of all players in the group.

[0023] In any of the above or other examples of the second aspect, the tracking module may be configured to transmit the location data to a location system.

[0024] In any of the above or other examples of the second aspect, the location tracking system may be configured to receive location data from a location network, and the location network may be configured to calculate multiple sets of location coordinates.

[0025] In any of the above or other examples of the second aspect, the location data collected or received by the location system includes position specific data that the location system uses to calculate location coordinates.

[0026] In any of the above or other examples of the second aspect, the multiple sets of location coordinates consist of sets of GPS coordinates.

[0027] In any of the above or other examples of the second aspect, the multiple sets of location coordinates consist of sets of ultra-wideband positioning coordinates.

[0028] In any of the above or other examples of the second aspect, the tracking module may be configured to collect location data at a first predefined interval and transmit the collected location data to the location system at a second predefined interval, the second interval being greater than the first interval.

[0029] In any of the above or other examples of the second aspect, the method includes dividing holes on the golf course into zones, each zone corresponding to a range of location coordinates, and determining a current zone in which the tracking module is located from the multiple sets of location coordinates.

[0030] In any of the above or other examples of the second aspect, the stroke event includes a ball hit, and the position of the tracking module at the time the stroke event occurs may be used as a proxy for the position of the ball of the player carrying the tracking module due to the previous stroke.

[0031] In any of the above or other examples of the second aspect, the tracking module acts as a beacon in the location network.

[0032] In any of the above or other examples of the second aspect, the tracking module may be configured to transmit the location data to a location system.

[0033] In a third aspect, a score tracking method includes collecting or receiving location data by a location system. The location data may correspond to the location of a tracking module carried by a player participating in a golf tournament. The location data may include multiple sets of location coordinates or be used to generate multiple sets of location coordinates, each set of location coordinates corresponding to the location of the tracking module at a specified time during play of the golf tournament. In one configuration, the method may include receiving an indication of the occurrence of a stroke event associated with a player, the indication being entered into the companion device by a scorer carrying a companion device and viewing the player carrying the tracking module. In one configuration, the method may also include receiving or generating a timestamp corresponding to the time the indication of the occurrence of the stroke event was entered into or received from the companion device by the scorer. In one configuration, the method may include pairing the timestamp with the set of location coordinates corresponding to the location of the tracking module at the time the stroke event occurred.

[0034] In a fourth aspect, the score tracking system includes a tracking module and one or both of an application and a location system. The tracking module may be configured to be carried by a player participating in a golf tournament. The application may be configured to interface a scoring operation to a user via a user interface of a companion device. The companion device may be separate from the tracking module and configured to receive input via the user interface indicating the occurrence of a stroke event. The input may cause the application to set a timestamp corresponding to the occurrence of the stroke event. The location system may be configured to collect or receive location data. The location data may include multiple sets of location coordinates or be used by the location system to generate multiple sets of location coordinates. Each set of location coordinates corresponds to the position of the tracking module at a specified time. The location system may be configured to pair a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time of the stroke event.

[0035] In an example of the third or fourth aspect, the sets of location coordinates correspond to the position of the tracking module over a period of time, with each set of location coordinates corresponding to a predefined time interval within the period of time.

[0036] In the above or another example of the third or fourth aspect, the tracking module may be configured to receive location signals from a plurality of beacons positioned around the golf course. In one configuration, the location data includes parameters of the location signals that the location system uses to calculate a set of location coordinates. In one configuration, the tracking module utilizes the parameters of the location signals to calculate its position and transmits its position as location data to the location system.

[0037] In any of the above or other examples of the third or fourth aspects, the tracking module may be configured to output a location signal that is used by the tracking module to calculate location data.

[0038] In any of the above or other examples of the third or fourth aspects, the tracking module may be configured to output location signals that are received by a plurality of beacons positioned around the golf course to calculate location data corresponding to the position of the tracking module.

[0039] In any of the above or other examples of the third or fourth aspects, the location data may be transmitted to the location system from one or more beacons positioned around the golf course configured to receive location signals transmitted by the tracking module to track the location of the tracking module.

[0040] In any of the above or other examples of the third or fourth aspects, the timestamp corresponds to the time when an indication of the occurrence of a stroke event is input into the companion device, and the companion device generates the timestamp and transmits the timestamp to the location system.

[0041] In any of the above or other examples of the third or fourth aspects, the indication of the occurrence of a stroke event includes an identification of a tracking module assigned to the player.

[0042] In any of the above or other examples of the third or fourth aspects, the indication of the occurrence of a stroke event includes an identification of the player carrying the tracking module.

[0043] In any of the above or other examples of the third or fourth aspects, the method includes receiving location data and an indication of a scoring event corresponding to a plurality of tracking modules carried by each of different players competing in the golf tournament, or the system is configured to receive location data and an indication of a scoring event corresponding to a plurality of tracking modules carried by each of different players competing in the golf tournament.

[0044] In any of the above or other examples of the third or fourth aspects, a single companion device may be configured to receive an indication of a score event associated with multiple players, each carrying a separate tracking module. In one configuration, the location data and the indication of the score event include identification data, including an identification of the player carrying the tracking module or an identification number of the tracking module carried by the player. In a further configuration, pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred includes matching the respective identification data.

[0045] In any of the above or other examples of the third or fourth aspects, the stroke event includes a ball hit, and the position of the tracking module at the time the stroke event occurs is used as a proxy for the position of the ball of the player carrying the tracking module due to the previous stroke.

[0046] In any of the above or other examples of the third or fourth aspects, the tracking module operates as a beacon in the location network.

[0047] In any of the above or other examples of the third or fourth aspects, the location network utilizes ultra-wideband positioning.

[0048] In any of the above or other examples of the third or fourth aspects, the tracking module may be configured to transmit the location data to a location system.

[0049] In any of the above or other examples of the third or fourth aspects, the location tracking system may be configured to receive location data from a location network, and the location network may be configured to calculate multiple sets of location coordinates.

[0050] In any of the above or other examples of the third or fourth aspects, the location data collected or received by the location system includes position identification data that the location system uses to calculate location coordinates.

[0051] In any of the above or other examples of the third or fourth aspects, the multiple sets of location coordinates consist of sets of GPS coordinates.

[0052] In any of the above or other examples of the third or fourth aspects, the plurality of sets of location coordinates comprises sets of ultra-wideband positioning coordinates.

[0053] In any of the above or other examples of the third or fourth aspects, the tracking module may be configured to collect location data at a first predefined interval and transmit the collected location data to the location system at a second predefined interval, the second interval being greater than the first interval.

[0054] In any of the above or other examples of the third or fourth aspects, the method may include dividing holes on the golf course into zones, each zone corresponding to a range of location coordinates, and determining a current zone in which the tracking module is located from the multiple sets of location coordinates, or the system is configured to divide holes on the golf course into zones, each zone corresponding to a range of location coordinates, and determining a current zone in which the tracking module is located from the multiple sets of location coordinates.

[0055] In a fifth aspect, a score tracking system can include a tracking module, a companion device, and a location system. The tracking module can be configured to be carried by a player participating in a golf tournament. The companion device can be configured to receive input corresponding to a stroke event, where the input can include a timestamp corresponding to the occurrence of the stroke event. The location system can collect or receive location data that includes multiple sets of location coordinates or that is used by the location system to generate multiple sets of location coordinates. Each set of location coordinates corresponds to the position of the tracking module at a specified time. The location system can pair a timestamp with the set of location coordinates that corresponds to the position of the tracking module at the time the stroke event occurred.

[0056] In one example of the fifth aspect, the stroke event includes a ball hit, and the position of the tracking module at the time the stroke event occurs is used as a proxy for the position of the ball of the player carrying the tracking module due to the previous stroke.

[0057] In the above or another example of the fifth aspect, the tracking module operates as a beacon in a location network, which may utilize ultra-wideband positioning.

[0058] In any of the above or other examples of the fifth aspect, the tracking module is configured to transmit the location data to a location system.

[0059] In any of the above or other examples of the fifth aspect, the location system is configured to receive location data from a location network, and the location network is configured to calculate a plurality of sets of location coordinates.

[0060] In any of the above or other examples of the fifth aspect, the location data collected or received by the location system includes position identification data that the location system uses to calculate location coordinates.

[0061] In any of the above or other examples of the fifth aspect, the plurality of sets of location coordinates consists of sets of GPS coordinates.

[0062] In any of the above or other examples of the fifth aspect, the plurality of sets of location coordinates comprises sets of ultra-wideband positioning coordinates.

[0063] In any of the above or other examples of the fifth aspect, the tracking module is configured to collect location data at a predefined first interval and transmit the collected location data to the location system at a predefined second interval, the second interval being greater than the first interval.

[0064] In any of the above or other examples of the fifth aspect, the location system may be configured to divide holes in the golf course into zones, each zone corresponding to a range of location coordinates, and the location system may determine a current zone in which the tracking module is located from multiple sets of location coordinates.

[0065] In any of the above or other examples of the fifth aspect, the companion device includes an interface configured to receive input corresponding to a stroke event. The stroke event may include an address and a ball hit. The interface may include an indicator configured to be pressed to indicate that the player is addressing the ball and to be held until the player hits the ball to indicate that the ball has been hit.

[0066] In any of the above or other examples of the fifth aspect, the companion device is configured to be carried by a scorer accompanying a group of players including the player, and the companion device may be further configured to receive inputs corresponding to stroke events of all players in the group.

[0067] In a sixth aspect, a score tracking method includes receiving, from a companion device, input corresponding to a stroke event of a player participating in a golf tournament, the input including a timestamp corresponding to the occurrence of the stroke event; collecting or receiving, by a location system, location data, the location data corresponding to the position of a tracking module carried by the player, the location data including or used to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a specified time; and pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

[0068] In one example of the sixth aspect, the stroke event includes a ball hit, and the position of the tracking module at the time of the stroke event is used as a proxy for the position of the ball of the player carrying the tracking module due to the previous stroke.

[0069] In the above or another example of the sixth aspect, the tracking module operates as a beacon in a location network. In one configuration, the location network utilizes ultra-wideband positioning.

[0070] In any of the above or other examples of the sixth aspect, the tracking module is configured to transmit the location data to a location system.

[0071] In any of the above or other examples of the sixth aspect, the location tracking system is configured to receive location data from a location network, the location network being configured to calculate a plurality of sets of location coordinates.

[0072] In any of the above or other examples of the sixth aspect, the location data collected or received by the location system includes position identification data that the location system uses to calculate location coordinates.

[0073] In any of the above or other examples of the sixth aspect, the multiple sets of location coordinates consist of sets of GPS coordinates.

[0074] In any of the above or other examples of the sixth aspect, the plurality of sets of location coordinates comprises sets of ultra-wideband positioning coordinates.

[0075] In any of the above or other examples of the sixth aspect, the tracking module is configured to collect location data at a first predefined interval and transmit the collected location data to the location system at a second predefined interval, the second interval being greater than the first interval.

[0076] In any of the above or other examples of the sixth aspect, the method further includes dividing holes on the golf course into zones, each zone corresponding to a range of location coordinates, and determining a current zone in which the tracking module is located from the multiple sets of location coordinates.

[0077] In any of the above or other examples of the sixth aspect, the companion device can include an interface configured to receive input corresponding to a stroke event. The stroke event can include an address and a ball hit. The interface can include an indicator configured to be pressed to indicate that the player is addressing the ball and to be held until the player hits the ball to indicate that the ball has been hit.

[0078] In any of the above or other examples of the sixth aspect, the companion device is carried by a scorer accompanying a group of players including the player, and the companion device receives inputs corresponding to stroke events of all players in the group.

[0079] In any of the above or other examples of the sixth aspect, stroke events are entered into the companion device by a scorer watching live video of the golf tournament.

[0080] In any of the above or other examples of the sixth aspect, stroke events are entered into the companion device by a scorer watching a video replay of the golf tournament. [Brief explanation of the drawings]

[0081] The novel features of the described embodiments are set forth with particularity in the appended claims. The described embodiments, however, both as to organization and mode of operation, may best be understood by reference to the following description taken in conjunction with the accompanying drawings, in which:

[0082] FIG. 1 illustrates a schematic of the hardware and network functionality of an STTM system, according to various embodiments described herein;

[0083] FIG. 2 illustrates schematically various elements of an STTM system and operating environment components according to various embodiments described herein;

[0084] FIG. 3 illustrates a zone function for location tracking according to various embodiments described herein;

[0085] 4A and 4B show various views of a tracking module according to various embodiments described herein, with FIG. 4A showing a face-on view and FIG. 4B showing a side view;

[0086] FIG. 4C is a perspective view of a tracking module according to various embodiments described herein;

[0087] FIG. 4D illustrates various components of a tracking module according to various embodiments described herein;

[0088] FIG. 5A provides a summary list of tracking modules loaded into a device management system and their associated locations, according to various embodiments described herein;

[0089] FIG. 5B illustrates an exemplary user interface generated by a device management system to provide tracking module management functionality and present device management data for loaded tracking modules, according to various embodiments described herein;

[0090] FIG. 5C illustrates a device allocation user interface that allows a user to perform device allocation operations according to various embodiments described herein;

[0091] FIG. 6A illustrates a grouping engine user interface including a grouping management panel according to various embodiments described herein;

[0092] FIG. 6B illustrates a grouping presentation by segments according to various embodiments described herein;

[0093] FIG. 6C illustrates a segment profile management interface including example data elements of a segment profile along with definitions of options for editing the data elements and creating new segments, according to various embodiments described herein;

[0094] FIG. 6D illustrates a revision editor interface configured to adjust tee times using a “revise based on offset” methodology or a “revise using reference time” methodology, according to various embodiments described herein;

[0095] FIG. 6E illustrates a player status editor interface according to various embodiments described herein;

[0096] FIG. 6F illustrates a round engine interface comprising a round management panel, according to various embodiments described herein;

[0097] FIG. 6G illustrates a round engine interface for creating playoffs, according to various embodiments described herein;

[0098] FIG. 7A illustrates a menu screen of the ST application, according to various embodiments described herein;

[0099] FIG. 7B illustrates a player description selection screen for the ST application, according to various embodiments described herein;

[0100] FIG. 7C illustrates a description category selection screen for the ST application, according to various embodiments described herein;

[0101] FIG. 7D illustrates a description characteristic selection screen for a selected description category of the ST application, according to various embodiments described herein;

[0102] FIG. 7E illustrates a summary player details screen of the ST application according to various embodiments described herein;

[0103] FIG. 7F illustrates the selection of a “Select a Club” function from the Groups screen of the ST application, according to various embodiments described herein;

[0104] FIG. 7G illustrates the selection of “Iron” from the club selection screen of the ST application, according to various embodiments described herein;

[0105] FIG. 7H illustrates an interface for directing a "shot hit" using the ST application, according to various embodiments described herein;

[0106] FIG. 7I illustrates an “in the hall” prompt for the ST application, according to various embodiments described herein;

[0107] FIG. 7J illustrates a group screen displaying strokes recorded after the score indicates "shot hit" using the ST application, according to various embodiments described herein;

[0108] FIG. 7K illustrates the selection of a “Start Location” function from a group screen of the ST application, according to various embodiments described herein;

[0109] FIG. 7L illustrates a selection of available descriptive characteristics for selection on the “Start Location” screen of the ST application, according to various embodiments described herein;

[0110] 7M and 7N show group screens illustrating the transition of the "Starting Location" from the "Fairway" back to the "Starting Location" after directing a "Shot Hit" using the ST application, according to various embodiments described herein;

[0111] FIG. 7O illustrates a group page with the first two players having finished the hole and the third player on the green, according to various embodiments described herein;

[0112] FIG. 7P illustrates recording a provisionally recorded second shot from the tee according to various embodiments described herein;

[0113] 7Q-7S illustrate a user interface of the ST application illustrating the workflow for recording a provisional shot that is ultimately used to result in the recording of a penalty stroke, according to various embodiments described herein;

[0114] 7T-7V illustrate a user interface of the ST application illustrating the workflow for recording a penalty drop and indicating that the dropped ball is in play, according to various embodiments described herein;

[0115] FIG. 8A illustrates a presentation block user interface of a data management tool of a data management system including a tool component within the presentation block, according to various embodiments described herein;

[0116] FIG. 8B illustrates a group scorecard interface of a data management tool according to various embodiments described herein;

[0117] FIG. 8C illustrates a Team Player stroke details component of the data management tool according to various embodiments described herein;

[0118] FIG. 8D illustrates a stroke event review viewer of the data management tool, according to various embodiments described herein;

[0119] FIG. 8E illustrates a present all groups component of a data management tool according to various embodiments described herein;

[0120] FIG. 8F illustrates an example interface for a data discrepancy panel component of a data management tool, according to various embodiments described herein;

[0121] FIG. 8G illustrates a presentation block user interface showing connections between presentation blocks of tool components according to various embodiments described herein;

[0122] FIG. 9A illustrates a first verification user interface of a verification system configured for blind verification according to various embodiments described herein; and

[0123] FIG. 9B illustrates a second verification user interface of the verification system presenting scoring data for one or more groups according to various embodiments described herein. DETAILED DESCRIPTION OF THE INVENTION

[0124] This description describes various embodiments of a score tracking and tournament management system, sometimes referred to herein as an STTM (Score Tracking and Tournament Management) system. The STTM system can include various systems, components, and modules configured to provide a lightweight platform for score tracking and tournament data management. Data collection can be unobtrusive to participating players while providing accurate, detailed data about their games and performance. Management functions can be provided on-site, off-site, or in a hybrid configuration. Pre-round and in-round tournament and score management functions can be automated and adaptable to various tournament structures, significantly reducing costs and personnel time, while employing customizable setup rules and profiles that integrate multiple tournament processes, such as player grouping, tee times, score collection, location tracking, error correction, and score verification. The STTM system can be utilized to provide tournament scoring, organizational management, and / or scoring system functionality, which can be utilized to provide in-depth data and feedback to players and other stakeholders, in real time or with a delay.

[0125] While some embodiments of the STTM system described herein may incorporate or utilize advanced infrastructure, the STTM system may be provided in a broadly applicable, flexible package configured for portability, allowing for limited infrastructure utilization with minimal impact on the quantity, quality, and accuracy of the final data product and / or the functionality available through tournament management support and its use. The STTM system's flexible architecture may be scalable, retractable, and / or modular to fit available infrastructure and resources with minimal variance in data quality. For example, although various aspects of the STTM system are described herein as providing integrated functionality or operations, the systems, components, and modules of the STTM system are not limited to combined use. Indeed, the systems, components, and modules described herein may be utilized individually or integrated individually with known or future-developed systems.

[0126] The operations described herein can be performed in association with one or more electronic user devices. For example, computer-readable instructions, when stored in a memory and executed by a processor, can cause the user device to perform the operations described herein. The memory and / or processor can be local or remote to the user device. The user device can include one or more tracking modules, one or more companion devices 12, and / or one or more management devices. The user device can include any suitable dedicated or multipurpose electronic computing device and system, such as a mainframe, server, computer, dedicated device, desktop, laptop, tablet, smart device / phone, personal data assistant, or the like. When utilized to collect live event data, the companion device will typically be a handheld tablet, smart device / phone, personal data assistant, or dedicated handheld device.

[0127] An STTM system can include, incorporate, and / or communicate with a user device that executes applications to perform the operations described herein. The user device can interface a user with the operation of the STTM system. For example, a user device can be configured to access, execute, run, or emulate one or more STTM system applications and / or services. The applications and services are stored in local and / or remote memory and executed by local and / or remote processors. In some embodiments, the applications, services, etc. are provided in whole or in part in a cloud computing environment (e.g., SaaS, DCaaS, DaaS, PaaS, iPaaS, IaaS, etc.).

[0128] 1 and 2, the STTM system 10 may include a score tracking system 20 configured to track the location and / or scoring of a competition, such as the scoring of a golf tournament, and a management system 20 that manages the operation of the STTM system 10, which may include its components, such as devices and elements.

[0129] STTM system 10 may include or incorporate various devices, including one or more of tracking module 11, companion device 12, management device 13, and / or location elements, such as location network 14 or global satellite communications infrastructure 15. STTM system 10 may include or incorporate a communications network 17 configured to transmit system data to, from, or between components of STTM system 10 to perform the operations of STTM system 10 described herein. In various embodiments, communications network 17 may include or be operatively networked with one or more location elements.

[0130] The tracking module 11 may comprise a user device configured to be carried by a competitive player or to be located near a competitive player during play. The tracking module 11 may include a memory containing instructions and a processor that executes the instructions from the memory to perform various operations performed by the tracking module 11. In certain embodiments, the processor may be hardware, software, or a combination thereof. In some embodiments, the tracking module 11 may also include an interface 11a (see, for example, FIG. 4C ) that may enable scorers, players, and / or other users to interact with various applications, such as a score tracking application, which may be referred to as an ST application, and / or operations running on the tracking module 11, such as location signals and / or location calculation processes, and to interact with STTM system components, devices, systems, and / or elements thereof. In certain embodiments, the tracking module 11 may be and / or include a computer, any type of sensor, a laptop, a set-top box, a tablet device, a phablet, a server, a mobile device, a smartphone, a smartwatch, and / or any other type of computing device, and / or any combination thereof. The tracking module 11 may be configured to perform various location operations. For example, tracking module 11 may be configured to track its location and / or communicate location information to the STTM system and / or location elements. Tracking module 11 may be configured for location tracking utilizing various techniques and location schemes described herein. For example, in some embodiments, tracking module 11 is configured to obtain GPS coordinates corresponding to its location and transmit such coordinates to a system, such as an STTM system device or management system 20, as described herein.In these or other embodiments, the tracking module 11 may operate as a beacon in the location network 14. The tracking module 11 may be configured to communicate with various location elements, such as the location network 14 and / or location services, to transmit data constituting location data, which may include positioning data that can be utilized to determine the location of the tracking module 11. The location data may also include a timestamp corresponding to the time to which the location data pertains. The tracking module 11 may be configured to communicate data, such as location data and / or positioning data, over various communication networks 17, such as a mesh network, a local network, a cloud computing network, an IMS network, a VoIP network, a security network, a VoLTE network, a wireless network, an Ethernet network, a satellite network, a broadband network, a cellular network, a private network, a cable network, the Internet, an intranet, an Internet Protocol network, an MPLS network, a content delivery network, a near field communication network, or any combination thereof. The tracking module 11 may be configured to communicate directly with location elements, such as the location network 14, the global satellite communications infrastructure 15, or the like, over various communication networks 17, or indirectly via another STTM system device or network device.For example, in one embodiment, tracking module 11 may utilize companion device 12 or management device 13 to transmit data directly to devices, elements, associated networks and / or location elements of STTM system 10 via one or more communications networks 17, and / or transmit signals to access various network-based, web-based, cloud-based, and / or online services and content, such as those available on the Internet, on other devices, and / or on various computing systems.

[0131] The companion device 12 may be configured to communicate with, define, identify, and / or organize scoring data, which may include location data, associated with the tracking module 11. Additionally or alternatively, the companion device 12 may be utilized to collect and / or track other athletic data. The companion device 12 may be utilized by a user to access data, content, services, and / or to perform various other tasks and functions of the STTM system 10. As one example, a user may utilize the companion device 12 to transmit signals to access various web-based, cloud-based, and / or online services and content, such as those available on the Internet, on other devices, and / or on various computing systems. As another example, the companion device 12 may be utilized to access applications, such as an ST application, that provide one or more operational functions of the STTM system 10, such as communication with one or more location elements comprising one or more of the management system 30, one or more tracking modules 11, one or more management devices, and / or the location network 14, and / or the global satellite communications infrastructure 15.

[0132] In certain embodiments, the companion device 12 may be used by a scorer to control one or more operational functions of the STTM system 10. The scorer may be a human, such as a dedicated user or player, a passive robot, an active robot, a humanoid, a program, a computer, any type of user, or a combination thereof. The companion device 12 may include a memory containing instructions and a processor that executes the instructions from the memory to perform various operations performed by the companion device 12. In certain embodiments, the processor may be hardware, software, or a combination thereof. The companion device 12 may also include an interface 12a (e.g., a screen, monitor, graphical user interface, etc.) that may enable the scorer to interact with various applications, such as ST applications, running on the companion device 12 and to interact with the STTM system 10, e.g., one or both of the score tracking system 20 or the management system 30. In particular embodiments, companion device 12 may be and / or include a computer, any type of sensor, a laptop, a set-top box, a tablet device, a phablet, a server, a mobile device, a smartphone, a smartwatch, and / or any other type of computing device. Illustratively, companion device 12 is shown in FIG. 1 as a smartphone or tablet device.

[0133] The management device 13 is utilized by an administrative user in connection with the functions of the management system 30 and can receive and transmit signals requesting various types of content, services, and data provided by and / or accessible through the communications network 17 or other networks with which the STTM system 10 communicates. In further embodiments, the administrative user may be a robot, a computer, a humanoid, an animal, any type of user, or any combination thereof. The management device 13 may include a memory containing instructions and a processor that executes the instructions from the memory to perform various operations performed by the management device 13. In particular embodiments, the processor may be hardware, software, or a combination thereof. The management device 13 may also include an interface (e.g., a screen, a monitor, a graphical user interface, etc.) that may enable a user to interact with various applications (e.g., management applications) running on the management device 13 and with the devices, elements, and systems of the STTM system 10. In particular embodiments, the management device 13 may be a computer, a laptop, a set-top box, a tablet device, a phablet, a server, a mobile device, a smartphone, a smartwatch, and / or any other type of computing device. The management device 13 may be local or remote with respect to the venue. The management device 13 may be cloud-based or web-based.

[0134] In certain embodiments, companion device 12, tracking module 11, management device 13, and / or location network 14 can have any number of software applications and / or application services stored thereon and / or accessible thereto. For example, companion device 12, tracking module 11, management device 13, and / or location network 14 can include applications for controlling the operational features and functions of STTM system 10 and / or score tracking system 20 or its management system, applications for controlling any system devices, cloud-based applications, VoIP applications, cellular applications, other telephone-based applications, location and / or accessibility applications and / or application services, other types of telephone-based applications, position and / or location applications, media streaming applications, content-based applications, media editing applications, database applications, Internet-based applications, browser applications, mobile applications, service-based applications, productivity applications, video applications, other types of applications, any type of application service, or combinations thereof. In certain embodiments, the software applications can support the functionality provided by STTM system 10, such as score tracking system 20 or its management system 30, and methods described in this disclosure. In certain embodiments, the software applications and services may include one or more graphical user interfaces to allow users (e.g., scorers, players, system administrators) to easily interact with the software applications.The software applications and services may also be utilized by a user to interact with any device within the STTM system 10, any network of the STTM system 10, or any network utilized by the STTM system 10 (e.g., a location network or global satellite communications infrastructure), or any combination thereof. In particular embodiments, the companion device 12, tracking module 11, and / or management device 13 may include an associated device identification ID or other identifier to uniquely identify the particular companion device 12, tracking module 11, and / or management device 13.

[0135] Communications network 17 may be configured to link each of the STTM system devices, components, and elements and may include any number of networks, including location network 14 in one embodiment. For example, a communications network may be utilized by companion device 12 to connect with other devices within or outside communications network 17. In various embodiments, companion device 12, tracking module 11, management device 13, and / or location network 14 may belong to and / or form part of communications network 17. In particular embodiments, communications network 17 may be a local, mesh, or other network that enables and / or facilitates various aspects of the functionality of STTM system 10. In particular embodiments, communications network 17 may be formed between or among various user devices, such as management device 13, companion device 12, tracking module 11, database 18, or combinations thereof, through the use of any type of wireless or other protocol and / or technology. For example, user devices may communicate with each other in communications network 17 by utilizing any protocol and / or wireless technology, satellite, fiber, or any combination thereof. In particular, communication network 17 may be communicatively linked to and / or configured to communicate with other networks of STTM system 10 and / or networks external to STTM system 10. In various embodiments, tracking module 11 may be configured to communicate directly with one or more components and / or location elements of management system 30. Communication network 17 may be configured to transmit, generate, and receive any information and data traversing STTM system 10. In particular embodiments, communication network 17 may include any number of servers, databases, or other components.Communications network 17 may also include or be connected to a mesh network, a local area network, a cloud computing network, an IMS network, a VoIP network, a security network, a VoLTE network, a wireless network, an Ethernet network, a satellite network, a broadband network, a cellular network, a private network, a cable network, the Internet, an intranet, an Internet Protocol network, an MPLS network, a content delivery network, a near field communication network, or any combination thereof. Illustratively, management device 13 is depicted as a representative server and is depicted as being included within or utilizing communications network 171. As described above and elsewhere herein, management device 13 typically configures a user interface that allows a user to perform scoring and / or tournament competition management operations described herein. In certain embodiments, communications network 17 may be part of a single autonomous system located in a particular geographic region or may be part of multiple autonomous systems spanning multiple geographic regions.

[0136] The functionality of STTM system 10 may be supported and performed using any combination of servers. The servers may reside within communications network 17 or its environment, although in certain embodiments, the servers may reside outside communications network 17. The servers may provide and serve server services that perform the various operations and functions provided by STTM system 10. In certain embodiments, management device 13 may comprise one or more network servers, routers, gateways, switches, media distribution hubs, signal transfer points, service control points, service switching points, firewalls, routers, edge devices, nodes, computers, mobile devices, or any other suitable computing devices, or any combination thereof.

[0137] The STTM system 10 may include or utilize a database 18 to store and relay information traversing the STTM system 10, cache content traversing the STTM system 10, store data about each device in the STTM system 10, and perform other typical functions of a database 18. Additionally, the database 18 may include or be connected to a processor and memory for performing various operations related to the database 18. In particular embodiments, the database 18 may be connected to a server, a companion device 12, a management device 13, a tracking module 11, any device in the STTM system 10, any process in the STTM system 10, any program in the STTM system 10, any other device, system, element, any network, or any combination thereof. The database 18 may be comprised of multiple databases 18. The database 18 may be local or remote. The database may be cloud-based.

[0138] The STTM system 10 may further include or transmit competition-related data generated by the STTM system 10 to one or more data platforms 19. The data platforms 19 may comprise hardware, software, servers, computers, programs, applications, etc. configured to view, manipulate, analyze, store, or otherwise consume the generated data. In some embodiments, the data platforms 17 comprise competition data viewers and analysis platforms available to players, coaches, administrators, fans, members of media organizations, broadcasters, or any other person. In further embodiments, the data platforms 17 comprise client platforms for data consumption and may include competition data viewer or analysis platforms. In the illustrated example, the data platforms 19 are shown as communicating via a web- or cloud-based portion of the communications network 17. However, in various embodiments, the competition-related data may be transmitted via other portions of the network, for example, locally.

[0139] While this disclosure may refer to particular applications executing on one or more electronic user devices, it should be understood that such applications, including any application services, may be provided within a single application, program, or platform, or may be split, virtualized, distributed, or combined across or among any number of executable platforms and resources.

[0140] Various interface components are referred to herein. Interface components include interface elements configured to interface an operation, such as selecting a data value or data element, to a user, display elements configured to interface a display to a user, data elements, etc. Indicators, operators, options, etc. described herein with respect to interfaces may include buttons, toggles, switches, slide bars, swipe buttons / bars / fields, sidebars, or other interface elements. Such interface elements may be configured as hard or soft interfaces. Similarly, interaction terms such as pressing, tapping, selecting, etc. may be performed using a human body, a stylus or other instrument, a peripheral device such as a mouse or keyboard, or other suitable user interaction.

[0141] With continued reference to FIG. 2 , the score tracking system 20 may be configured to track scores related to the play of multiple competitive players, such as golfers, competing in a competition. While the competition is described herein as a golf tournament, those skilled in the art will understand, after reading this disclosure, that the systems and methods described herein can be applied to other competitions and other environments. Score tracking may also include tracking the location of stroke events. As introduced above and described in more detail below, the score tracking system 20 may include a tracking module 11 configured to be carried by or associated with a player. In some embodiments, for example, as shown in FIG. 2 , the score tracking system 20 may also include or be configured to incorporate a companion device 12. The companion device 12 may be configured to receive score-related inputs, such as stroke event inputs, from a scorer and transmit score-related data to the management system 30. Tracking module 11 may be configured with location identification, positioning, and / or proximity technologies that may be used by tracking module 11 and / or another device, such as companion device 12, managing device 13, location network 14, and / or location system 80, to track the location of tracking module 11, as introduced above and described in more detail below. Using companion device 12, a scorer may record events, such as stroke events, related to play. Recording an event may result in the generation and recording of an associated timestamp and / or the retrieval, identification, calculation, and / or transmission of location data from tracking module 11 corresponding to the recorded event, such as when the player addressed or struck the ball.The location data, or chronological synchronization of the tracking module 11's location and timestamp, may be used by the location system 70 as a proxy for the player's ball position following a previous hit or the starting position of the player's ball before striking the ball. A notable advantage of this score tracking method is that a single scorer, typically accompanying a group of golfers, can record both scores and location data in an unobtrusive manner. As described in more detail below, in various embodiments, the tracking module 11 is configured to be compatible with multiple location service technologies, thereby providing flexibility with respect to tracking the location of the tracking module 11, for example, by utilizing available infrastructure on the course as needed. The score tracking system 20 and / or STTM system 10 may include or incorporate location services such as one or more of the global satellite communications infrastructure 15 or location network 14. Location network 14 is typically a local location network for the golf course where the tournament is being held and may include radio receivers, transmitters, transceivers, antennas, UWB antennas, anchors, initiators, responders, cell towers, Wi-Fi access points, beacons, geobeacons, BLE gateways, etc. In some embodiments, location network 14 includes external location / signal networks utilizing short-range or long-range location technologies, which may include signals of opportunity.

[0142] In various embodiments, the tracking module 11 is configured to communicate with the companion device 12 and is operable to obtain calculated location data or location signaling parameters from the tracking module 11, which can be used by the companion device 12, the managing device 13, and / or a location system to calculate the position of the tracking module 11 at a given time, a time range, or continuously. However, in some embodiments, the tracking module 11 may not be in communication with the companion device 12 for location tracking operations; for example, another device may calculate or receive the position of the tracking module 11. For example, a timestamp set by the companion device 12 may be transmitted to another device before or after transmission to the managing device 13 for chronological pairing with the position of the tracking model 11, or the managing device 13 may be in communication with the tracking module 11 and the companion device 12 to receive location data for pairing with the timestamp.

[0143] In one example, the tracking module 11 obtains GPS coordinates via communication with the global satellite communications infrastructure 15 and transmits the coordinates to the management system 30. The companion device 12 can also transmit stroke events with associated timestamps to the management system 30. The location system 80 pairs the timestamps with the corresponding location coordinates.

[0144] In one example, the tracking module 11 obtains its position, which may include location coordinates, through location signaling with a location network 14, such as a UWB or other location network described herein. In one configuration, the tracking module 11 calculates its position as described herein and transmits the position to the management system 30. In another configuration, the location network 14 calculates the position of the tracking module 11 and transmits the position to the management system 30 or the companion device 12, which then transmits the position and / or the position paired with a corresponding timestamp to the management system 30. The companion device 12 may also transmit a stroke event with an associated timestamp to the management system 30. The location system 80 can then pair the timestamp with the corresponding location coordinates.

[0145] In one embodiment, the management system 30 includes a device management system 40 configured to manage multiple tracking modules 11 and assign them to players. The device management system 40 can execute on one or more management devices 13. In one configuration, the device management system 40 communicates with the tracking modules 11 during play to track their locations. When a companion device 12 sets a timestamp regarding the location of a tracking module 11 for an assigned player, the device management system 40 receives the timestamp and pairs it with the location of the tracking module 11 at the time set by the timestamp. This location information can be provided to the data management system 40 for review and / or made available for transmission or use by the operation of the STTM system 10 or the data platform 19. As noted above and elsewhere herein, the location calculations and / or the combination of location coordinates and timestamps can be performed by a location system 80 and made available to other systems in the management system 30, or the functionality of the location system 80 can be provided by other systems in the management system 30. The location calculations can be perceptually instantaneous or otherwise real-time. In one embodiment, the companion device 12, tracking module 11, management device 13, location network 14, and / or location system 80 may track the location of the tracking module 11 continuously or near-continuously. Such continuous or near-continuous tracking can be used to address location tracking / network delays. For example, if a scorer records a stroke event that sets a timestamp when the ball is struck, in nearly all cases, the most recent location calculated within five seconds of the timestamp provides the accurate location of the ball at the time of strike. In one embodiment, the scorer sets a timestamp for location purposes at address.

[0146] In various embodiments, the management system 30 includes one or more of a round management system 60 configured to manage the rounds and groupings of players playing in an event, a data management system 60 configured to review and edit scoring data recorded by the score tracking system 20, or a verification system 70 configured to provide streamlined verification of a player's official scorecard against scores collected by the score tracking system 20. In these or other embodiments, the management system 30 may include a location system 80. The location system 80 may be configured to process the tracking module 11's location data, calculation of location data from the positioning data, pairing of timestamps with location data, zone determination, and / or comparison of zone determination with scoring data zone identification. In one embodiment, the companion device 12 may transmit scoring data to the management system 30. The tracking module may also transmit location data or positioning data, directly or indirectly, to the management system 30. Stroke events and corresponding timestamps may be available to the location system 80 for pairing with the tracking module's location. Location system 80 may share data and / or functionality with various systems of management system 30. For example, a device management system and / or a data management system may perform or access one or more of the above-described location determination functions instead of or in addition to location system 80. In various embodiments, location system 80 includes or communicates with one or more location networks. As described in more detail herein, location networks may include GPS, Wi-Fi, RFID, BLE, UWB, NFC, cellular, etc.

[0147] As introduced above, the companion device 12 may be configured to execute or run an ST application. The ST application may comprise a mobile app, a web app, a cloud-based app, or other application format and may include instructions operable to perform the score-collection functionality described herein with respect to the companion device 12. If the companion device 12 is configured to communicate with the tracking module 11, the ST application may be configured to provide a communication protocol between the companion device 12 and the tracking module 11. For example, the ST application may configure the companion device 12 to communicate with the tracking module 11, provide updates, receive data for storage, provide processing operations, send alarm initiation commands, obtain battery level or charge status, receive location data for the tracking module 11, initiate location data events, relay data received from the tracking module 11 to storage or another computing device, perform proxy services for the tracking module 11, or perform other operations described herein. Additionally or alternatively, the ST application may configure the companion device 12 for communication with the managed device 13 of the management system 30. For example, the ST application may be configured to receive and import grouping assignments, round information, tee times, etc. from the round management system 60 .In the above or another example, the ST application may be configured to receive player and tracking module 11 assignments from the device management system 40, incorporate the player and tracking module 11 assignments into the collected scoring data (stroke event data, location data, timestamps, club selection, etc.), transmit the stroke event data including the associated timestamps to the STTM system 10, e.g., the location system 80, the device management system 40, the data management system 50, and / or the verification system 70, and / or communicate with the tracking modules 11 to pair them with their assigned players. However, in some embodiments, the assignments are maintained by the management system 30, and the companion device 12 may be accompanied by stroke event timestamps or location data with identifiers for the respective tracking modules 11 that the management system 30, e.g., the data management system 60 or the location system 80, uses to pair the tracking modules 11's positions at the timestamps with the players assigned to the tracking modules 11. In the above or another embodiment, the ST application may be configured to transmit the collected scoring data recorded by the companion device 12 to a management system 30, such as a data management system 60, a verification system 70, and / or a location system 80.

[0148] In one embodiment, tracking module 11 is comprised of a compact housing that can be easily carried or worn by an individual. FIGS. 4A-4D provide diagrams of an exemplary tracking module 11. In the illustrated example, tracking module 11 includes a housing 110 that is generally smaller than a deck of playing cards, although larger tracking modules 11 may be used. In one example, housing 110 may include a clip for clipping to a belt, pocket, or other surface. In one embodiment, a wearable receptacle may be provided that can be carried or worn by an individual to receive tracking module 11. In one example, the receptacle may include a clip for clipping to a belt or pocket, or may include or be attached to a wearable band. Numerous variations may be implemented. For example, tracking module 11 may be integrated into or embedded in clothing, such as a belt, belt buckle, hat, bracelet, or the like. In some embodiments, tracking module 11 may be integrated into a tablet, laptop, smart device such as a phone or PDA, or other portable electronic device. In various embodiments, the housing 110 may be configured to be openable for maintenance, part replacement, upgrades, or other desired purposes. For example, the housing 110 may include removable panels or may have a clamshell design. In one embodiment, the housing 110 may be waterproof or water-resistant with respect to the interior of the housing 110. For example, the panels or clamshell may be provided over a gasket.

[0149] 4D is a semi-schematic view of the interior of tracking module 11, showing components that may be included in various embodiments of tracking module 11. In some embodiments, tracking module 11 includes a wired data communication port 111. Port 111 may be provided or accessible from the exterior of housing 110, or may be accessible by removal of a panel or clamshell thereof. Wired data communication port 111 may be utilized for programming, downloading, or other data communication needs as an alternative or backup to wireless data communication.

[0150] The tracking module 11 may include one or more batteries 113 configured to power the operation of the tracking module 11. A variety of standard and custom-sized batteries 113 may be used, such as AA, CR123A, 23A, or coin cells such as CR2032. While a compact size is preferred, larger batteries 113 may also be used. By way of example, a user may wear or carry a separate battery pack or power supply that powers the tracking module 11 via a wired or wireless connection. Any suitable type of battery 113 sufficient to power the tracking module 11 may be used. For example, the battery 113 may include lithium, alkaline, silver oxide, zinc carbon, zinc air, lithium ion, NiCD, or NiMH. Various tracking module 11 configurations may include or be configured to operate with a rechargeable battery 113, such as a lithium ion, NiCD, or NiMH. In one embodiment, the tracking module 11 includes a rechargeable battery 113, such as a rechargeable lithium polymer 2300 mAh battery.

[0151] Some configurations of the tracking module 11 may include a charging port 112 operable to receive a supply of power to charge the battery 113. The charging port 112 may include a female or male connector. The port 112 may be configured to be waterproof or water-resistant to prevent water ingress into the charging port 112. For example, the charging port 112 may be separated from the interior of the housing by a gasket. In a further example, access to the charging port 112 is provided by removing a panel seated on the gasket or by inserting an external charging interface connector through a slit in the water-blocking material. In another example, a removable plug may be mounted in or on the charging port interface to prevent water ingress. In one embodiment, the tracking module 11 is configured to be charged wirelessly. In one embodiment, the tracking module 11 is configured with a charging port for recharging the battery while within the housing. For example, the housing may include a wired or wireless charging port. A magnetic wireless charging port, USB (e.g., A, B, Mini A / B, Micro A / B, C), Thunderbolt, a DC power connector, or other suitable power delivery interface technology may be used. A custom charging interface may also be used. In some embodiments, charging port 112 is similarly configured to be operable for use as wired data communication port 111. In one embodiment, charging port 112 comprises a USB C connection. In the above or another example, the housing may include a charging interface configured to be plugged into a charger having multiple charging ports for simultaneous charging of multiple tracking modules 11.

[0152] In various embodiments, the tracking module 11 may be configured with a wireless communication port 114 including one or more radio receivers, transmitters, and / or transceivers. The wireless communication port 114 may be configured to transmit and / or receive wireless data communications, e.g., signals, via any wireless communication medium or protocol, such as those including or incorporating radio waves, cellular, Wi-Fi, short-range radio, Bluetooth, or other suitable wireless communication technologies. The wireless communication port 114 may be configured for multi-band operation. For example, the wireless communication port 114 may be configured for communication in multiple frequency bands. The multiple frequency bands may include cellular networks (4G, LTE-M, NBIot, 2G, etc.) and / or other frequency bands. The wireless communication port 114 may be configured to transmit and / or receive data, such as location data and / or positioning data, from a location network, a global satellite communications infrastructure, etc. The wireless communication port 114 may be configured to transmit and / or receive positioning data, such as parameters for calculating a position. The wireless communication port 114 may be configured to operate as a beacon, as described in more detail below. The tracking module 11 may be configured with a location alarm. The location alarm may be remotely activated wirelessly via wireless communication from one or more of a remote command center, a management device, or a companion device equipped with an appropriate wired or wireless transmitter or transceiver for transmitting an alarm activation signal to the wireless communication port 114 of the tracking module 11, which may include communication through an intermediate wired network of the communication network. For example, the alarm activation signal may be transmitted and / or received via Wi-Fi, cellular, short-range radio, Bluetooth, or other suitable wireless communication technology.

[0153] In one embodiment, a companion device to the managing device, such as a managing device in a device management system, may be configured to transmit, e.g., via an application, an alarm activation signal that, when received by the wireless communication port 114 of the tracking module 11, causes the tracking module 11 to output an alarm. The alarm may include activation of a vibration device, such as an ERM motor or LRA, housed in the housing and operable to generate vibrations in response to receiving the alarm signal. Additionally or alternatively, the alarm signal may trigger an audible alarm that is output from a speaker 116 or other noise-generating device within or associated with the housing. Additionally or alternatively, the alarm signal may trigger activation of a light, such as an LED, or a lighted display, such as an LCD.

[0154] The tracking module 11 may include a memory 119a and a processor 119b that executes instructions stored or otherwise received in the memory 119a to perform the operations of the tracking module 11. In some configurations, the housing 110 includes a memory expansion port or slot for connecting additional memory storage. The expansion slot may be configured to accommodate an expansion memory device, such as a microSD card, or may receive a plug for a wired connection to the expansion memory device. The memory 119a may be used to store collected data, such as location data and time data. Such data may be transmitted to a storage device, receiving device, or processing device continuously, periodically, daily, or on demand.

[0155] The tracking module 11 may include an accelerometer 1100. The accelerometer 1100 may be utilized for movement detection. Movement detection may be utilized in combination with positioning and tracking, determining, or obtaining position; for example, movement detection may initiate transmission of location signals and / or listening for the same. Movement detection may initiate transmission of tracked, determined, or obtained location or position data, for example, to a companion device, a location network, or an STTM system device. In some embodiments, the accelerometer 1100 may be configured for movement detection related to detection of a swing by a player. Detection of movement corresponding to a swing may be used in addition to or instead of scorer input of a swing or "shot hit," as described below. The accelerometer 1100 may also be configured to detect an address corresponding to a time period accompanied by a cessation of movement prior to detection of movement corresponding to a swing, for example.

[0156] Tracking module 11 may include a user interface 11a for interfacing operation and / or status with a user. In various embodiments, user interface 11a includes a display 118 for displaying information. Any suitable display 118, such as an OLED screen, may be used. The information may include battery capacity, battery life or status, and operating mode, such as awake, sleep, ready to receive instructions, and operating. In some embodiments, display 118 may present data regarding current operation or assignment. For example, the display may be configured to display the group number and / or player to which tracking module 11 has been assigned for data collection.

[0157] In one embodiment, the user interface 11 a includes one or more indicator lights that can be used to indicate an operational state, such as powered on, processing data, uploading data, downloading data such as instructions, assignments, or updates, receiving and / or acquiring position / location data, receiving instructions, transmitting data, an operation in progress, an operation completed, etc.

[0158] In one embodiment, the tracking module 11 includes a speaker 116 operable to output sound. The speaker 116 can be used to output audible alarms for location purposes, battery life, confirmation of user interaction or receipt of communication, initiation of wake-up mode and / or sleep mode, communication of instructions received from the companion device 12, or any other desired use.

[0159] In various embodiments, as introduced above, the tracking module 11 includes location, positioning, and / or proximity technologies to assist in locating a misplaced tracking module 11 and / or determining the precise location of the tracking module 11. For example, the tracking module 11 may be configured to output directional or omnidirectional location signals, such as packets, blinks, requests, responses, etc., that may be used by a companion device, location network, management system, and / or location system to locate and / or determine the location / location of the tracking module 11, e.g., based on signal strength, signal parameters, and / or signal characteristics. Additionally or alternatively, an STTM system that may include the location elements described herein may be configured to locate the tracking module 11 using other technologies, as described below.

[0160] The STTM system or its score tracking system may include a location network configured to provide location tracking functions and / or services. The location tracking network (see FIG. 2) may include multiple location signaling devices. The location signaling devices may include receivers, transmitters, transceivers, gateways, beacons, UWB antennas, anchors, initiators, responders, real-time kinematic (RTK) base stations, and the like configured to determine outdoor positions / locations. The location signaling devices may be configured to utilize radio waves such as UHF, NFC, Wi-Fi, Bluetooth Low-Energy, and / or UWB. The location signaling devices may be positioned around the playing course and configured to communicate location signals with multiple tracking modules 11. The location network may be configured for device-side location calculation and / or network-side location calculation. The location network and / or tracking module 11 may utilize various localization techniques such as RSSI, RSSI-fingerprinting, and / or Time of Flight (ToF), Time Difference of Arrival (TDPA), and / or Angle of Arrival (AoA).

[0161] Tracking module 11 may include one or more short-range communication devices, such as Wi-Fi, Bluetooth, BLE, NFC, and / or ultra-wideband chips, configured to provide short-range position signaling, location location, proximity determination, and / or ranging. While FIG. 4D shows wireless communication port 115 configured for ultra-wideband, other short-range communication protocols and / or signaling may be utilized. Wireless communication port 115 may be in addition to or instead of wireless communication port 114. In some embodiments, wireless communication port 115 is comprised of a Wi-Fi, BLE, LTE, and ultra-wideband chip, and wireless communication port 114 is comprised of a cellular chip. Depending on the configuration, location services may be utilized by tracking module 11, a location signaling device of a location network, and / or any device appropriately configured to receive location or location signals and utilize the signals and associated data to identify and / or determine the location / position of tracking module 11.

[0162] Additionally or alternatively, the tracking module 11 may be configured to receive location signals from location signaling devices, which may be used to determine the position / location of the tracking module 11, either by the tracking module 11, a companion device, a location network, a location system, or otherwise. For example, beacon signals may be used to determine the position / location of the tracking module 11. As introduced above, the location signals may be output using near-field communication technologies. In various embodiments, the location signals may be transmitted via radio waves, such as UHF, NFC, Wi-Fi, Bluetooth Low-Energy, or ultra-wideband. For example, the tracking module 11 may be configured to receive location signals, such as beacon packets or UWB anchors. In a device-side use case, the tracking module 11 may use the received location signals to calculate its position or relay the location signal / packet data and / or associated reception parameters to another device, such as a companion device or a management device, for direct or indirect processing (e.g., via an API). For example, if a beacon is present, the tracking module 11 may receive beacon packets that can be used by the tracking module 11 or a companion or management device in communication with the tracking module 11 for position / location determination, e.g., via RSSI, RSSI-fingerprinting, and / or ToF techniques. In a network-side position calculation use case, the tracking module 11 may continuously output signals, send position response signals to position signals received from location signaling devices, or send polling signals that may be used by a location network or other STTM system components, such as a location system, to calculate the position of the tracking module 11, e.g., via TDPA, ToF, and / or AoA.In one embodiment, the location network includes multiple location signaling devices, e.g., beacons or anchors, positioned around a playing area, such as a green, fairway, rough, and / or tee box. Tracking module 11 can receive the transmitted signals for location / position determination. In a further example, tracking module 11 may transmit a responsive location signal. In these or other examples, three or more beacons or anchors may be used, for example, around a green, for precision and accuracy.

[0163] In one embodiment, the tracking module 11 may be configured for UWB position / location determination in conjunction with a location network. For example, the tracking module 11 may include multiple antennas to directly or indirectly utilize AoA / phase difference. The tracking module 11 may be configured for single-sided, two-sided, or multi-sided ranging as an initiator and / or responder. The tracking module 11 may be configured to operate as an initiator in a time difference of arrival model with synchronous anchors in a location tracking network deployed around a golf course, achieving precise positioning and accuracy, for example, down to 1 cm. In one embodiment, multiple positioning technologies may be utilized to enhance positioning, such as Wi-Fi, BLE, and / or UWB. In further embodiments, one or more of these positioning technologies may be utilized in conjunction with one or more global satellite communications. In some embodiments, the location system includes a UWB positioning system including multiple anchors that receive positioning signals from the tracking module 11. The anchors may utilize time difference of arrival (TDoA) or other suitable techniques to determine the coordinates of the tracking module 11. It will be appreciated that in such a network or other location network, a location system may receive and / or collect positioning or location data. The location system may calculate a position from the positioning data. The location system may further constitute all or part of the location network.

[0164] The tracking module 11 may be configured to utilize one or more global satellite communications for precise position determination and positioning. Illustratively, FIG. 4D illustrates the inclusion of a GPS chip or receiver 117 configured to receive GPS location coordinate data. While GPS is generally referred to herein, those skilled in the art will understand that such references equally apply to other global navigation satellite systems (GNSS), such as GLONASS, BeiDou, Galileo, or other current or future GNSS. GPS location may be augmented with WAAS (Wide Area Augmentation System), DGPS (Differential GPS), e.g., GDGPS (Global Differential GPS), RTK (Real Time Kinematic), CORS (Continuous Operating Reference Point), SOP (Signal of Opportunity)-based or augmented navigation, UWB, LTE, cellular, radio, television, Wi-Fi, other satellite signals, and the like. In some embodiments, a location network may be used in place of or hybrid with one or more global communications coordinate systems. The location network can utilize location signals and methodologies including, but not limited to, RTK, CORS, SOP-based, UWB, LTE, cellular, wireless, or Wi-Fi. In one example, tracking module 11 is configured to utilize any or all of the available global satellite communications (GPS, GLONASS, BEIDOU, GALILEO, and QZSS) to provide precise positioning outdoors with an accuracy of 0.5-5 m typical or better. In one embodiment, tracking module 11 transmits its coordinate location to a management system via a cellular network.

[0165] In one embodiment, the communication network includes a Low Power Wide Area Network (LPWAN) through which the tracking module 11 transmits location data directly or indirectly to the management system. In one example, the LPWAN includes a LoRa network. Companion devices can similarly transmit stroke event data over such networks. Unlike current score tracking methodologies, the score tracking system architecture utilizes a low data load suitable for transmitting small data packets over low-power, long-range networks while still maintaining a steady stream of accurate data.

[0166] As introduced above, STTM systems can utilize UWB positioning / location networks for all or part of their location services. GPS or other location services can also be used simultaneously, in a hybrid configuration, or as separately selectable options or settings for system devices.

[0167] In various embodiments, tracking module 11 may be configured to continuously output location or locating signals or to output location signals upon receiving an instruction to do so. For example, an ST application or location tracking network may be operable to address one or more tracking modules 11 to begin outputting location signals. In one embodiment, tracking module 11 is configured to determine location coordinates every n seconds and transmit all or a portion of the coordinates every n+x seconds. For example, tracking module 11 may be configured to collect location coordinates at any predetermined time interval and transmit the collected location coordinates at any time interval.

[0168] In one embodiment, the tournament course and / or its surrounding grounds may be mapped and divided into geolocation zones. Location data from tracking module 11, which may include position identification data, may be transmitted to a management system, such as a management device, to determine a current geolocation zone corresponding to the tracking module's location. The current zone may be transmitted to tracking module 11 and trigger an action by the tracking module. In one embodiment, tracking module 11 is programmed to identify the current zone, and identifying the current zone may trigger an action. In some embodiments, tracking module 11 may transmit coordinates through an API containing the geolocation zone to a management device that returns the current zone for the corresponding coordinate to the tracking module. Actions that may be triggered include alerts, API calls, database entries, alarms, etc., based on entering, leaving, or being in a particular zone.

[0169] FIG. 3 illustrates an example of geolocation zoning of a golf hole. The zones include a green zone 31, a fringe zone 32, a fairway zone 33, a first cut zone 34, a hazard zone 35, a rough zone 36, a natural area zone 37, and a tee box zone 38. Each zone includes coordinates corresponding to the respective zone. As described above, other or additional zones may be included. In various embodiments, the entire hole is zoned. As introduced above and described in more detail below, geolocation zoning can be used for various operations of the STTM system. For example, a companion device, score tracking system, or management system can mark or record a group of players as being on the green when the tracking module assigned to the first player in the group crosses the green zone 31. As described above, a location system can collect or receive location data regarding the tracking modules. The location system may use this location data to determine the location of the tracking modules. Location coordinates may be applied to predefined coordinate ranges corresponding to the defined zones to determine which zone the tracking module is currently located in. This zone determination may be performed in real time, for example, within 10 seconds, 5 seconds, or less. The location system may use the most recent set of location coordinates or interval of location coordinates to determine the current location and / or zone in which each tracking module 11 is located in order to track the location of the tracking modules 11. Similarly, a group may be marked or recorded as having completed a hole when the tracking module assigned to the last player in the group crosses the green zone 31 after the group has been marked or recorded as being in the green zone 31. The group is marked or recorded as having entered the tee box when the tracking module 11 assigned to the player who first entered the tee box zone 38 is detected.As described in more detail below, user input to the ST application on the companion device may additionally or alternately be used to mark or record locations. In one embodiment, a group marked or recorded as being on a tee box may advance the ST application to the hole associated with the tee box. In another embodiment, when the scorer enters "in hole" into the companion device for the last player in the group to hole out, the ST application automatically advances to the next hole. In another embodiment, the ST application does not advance to the next hole until "in hole" has been entered for all players on the preceding hole and the players have entered the tee box for that hole.

[0170] As introduced above, tracking module 11 may be configured to collect location coordinates at any predetermined time interval and transmit the collected location coordinates at any time interval. In one example, tracking module 11 may be configured to obtain location coordinates, e.g., GPS positions, every second and transmit the obtained location coordinates to the location system every five seconds. However, tracking module 11 may be configured to collect location data and transmit the collected location data at any desired time interval.

[0171] In one embodiment, the location of tracking module 11 is tracked continuously, for example, at one-second intervals or other programmatic intervals. In one embodiment, a timestamp is paired with a location so that location coordinates collected around the time corresponding to the timestamp can be analyzed to identify the most likely location.

[0172] As will be described in more detail below, a scorer using a companion device can also input a ball location or "starting location." Such a location may correspond to a defined zone of the hole. Using the zone determination from the tracking module coordinates, the location system can compare the determined zone with the input zone and identify any discrepancies. For example, the determined zone may be a fairway, but the input zone may be a bunker or hazard. In such a case, the location system may be configured to accept the zone location as the bunker or hazard. In one embodiment, the location coordinates may be adjusted to the bunker or hazard. In another embodiment, the location coordinates are retained, and only the zone location corresponding to the "starting location" is changed to correspond to that input by the scorer.

[0173] The companion device may record a timestamp of the address and / or shot hit. The location network may apply an algorithm that analyzes the location before and after the timestamp. The lookback and forward times may be adjustable in the location system. As an example, the lookback and forward times may be 30 seconds. In one embodiment, the lookback time may be longer than the forward time. The location system may examine the locations closest in time to the timestamp to identify the most accurate location. Identifying the most accurate location may involve determining a period of 5 to 10 seconds or more during which the location changes little. As described above, the tracking module may detect when the swing was made. Such data may be provided to the location system to confirm or enhance analysis of the timestamp. For example, the location system may pair the location at the time of the swing and match it with the location obtained by the scorer provided in the timestamp. In some embodiments, if the location is unknown or does not correlate to the expected location, for example, if the coordinates correspond to a different hole, the location is not recorded.

[0174] In one embodiment, the tracking module 11 is configured with an operating window. For example, location data, which may include position identification data, is not stored or transmitted outside of the defined time of the operating window. Such an operating window may be registered with each tracking module 11. In this or another example, if the tracking module 11 is not registered with a player in a tournament, no location or position identification data is stored or transmitted. In either of the above or another example, the tracking module 11 may not transmit location or position identification data if the acquired coordinates are not those of the course hosting the tournament. Thus, in some embodiments, the tracking module 11 may be programmed with allowable coordinates associated with a tournament. Such restrictions may enhance privacy for users of the tracking module 11. In some embodiments, the operating window registration, player registration, and / or coordinate restrictions may be overridden by the STTM system 10, for example, to locate a lost or missing tracking module 11.

[0175] In one embodiment, the STTM system 10 may be configured to pass a notification to the tracking module 11 registered with a player who is out of position or playing too slowly. For example, the tracking module 11 may output a text notification (if equipped), an audible and / or visual alarm, or a vibration. Additionally or alternatively, a companion device assigned to a group that includes a player who is out of position or playing too slowly may receive such a notification via the ST application. In a further example, the notification may include instructions on how to correct the problem, such as arriving at a specific location on time or asking the player to pick up the pace.

[0176] As introduced above, and with particular reference to FIGS. 5A-5C , the STTM system can include a device management system 40 configured to assign tracking modules 11 to players. The device management system 40 can provide device administrator data and / or device management operations locally, remotely, and / or from any location via a management device. In some configurations, the device management system 40 is configured to assign tracking modules to groups, which are then assigned to players in turn. Tracking modules are assigned to players in turn; for example, the tracking module software is typically temporarily programmed into the player so that location data, localization data, or other data transmitted from the tracking module includes an identification of the assigned player. The location data includes a timestamp corresponding to the time the location data was collected or is otherwise associated with the location of the tracking module. In some embodiments, the tracking module is player agnostic, but an identification number or other unique identifier associated with the tracking module is established in the STTM system so that communication from the tracking module pairs the identifier with the assigned player. In various embodiments, a companion device, whether programmed or agnostic, may be configured to associate a tracking module with an assigned player. For example, the ST application may be programmed by a device management system or scorer to associate the tracking module with an assigned player for display on the companion device. In some embodiments, the companion device may transmit the tracking module identifier and / or player name to an STTM system, such as a location system, device management system 40, data management system, or verification system, upon entry of a stroke event associated with a location timestamp.

[0177] The device management system 40 may be configured to import and group tracking modules for tournament operation. In one example, the device management system 40 may be configured to store and / or present tracking module management data. In certain embodiments, the device management system 40 is configured to load or import new tracking modules and create new devices. Importing a new tracking module may include uploading a file, such as a CSV file, containing a tracking module profile or a list of tracking module profiles to manage. The tracking module profile may include specific tracking module management data, such as identifiers and / or other tracking module data. The device management system 40 may be configured to save the tracking module profile in a location and store the associated loaded tracking modules and the tracking module locations. The device management system 40 may be configured to receive specific device-related management data directly or indirectly from the loaded tracking modules and present at least a portion of this data on a user interface display. Figures 5A-5B illustrate an embodiment of a user interface that presents device management data and allows a user to perform device management operations.

[0178] FIG. 5A provides a device management overview presentation 400 including a device list 401 of tracking modules and their associated locations 402 loaded into the device management system 40 according to various embodiments. The device management system 40 is configured to allow a user to create locations and delete locations. In one embodiment, when a user deletes a location, a warning prompt may be generated to notify the user of the deletion upon user confirmation. The locations 402 may be places associated with listed tracking modules. The locations 402 may refer to geographic locations by coordinates, landmarks, or location references (e.g., 9th hall, volunteer meeting area, gear locker, equipment room, geolocation zone, etc.). Additionally or alternatively, the locations 402 may refer to physical containers containing respective tracking modules (e.g., container 681). In one example, the locations 402 refer to containers containing storage devices configured to function as charging stations for charging tracking modules and / or storage stations for storing tracking modules. In one example, location 402 refers to the physical container containing the tracking module and the geographic location of the container, which may be coordinates, a zone determined by the geolocation corresponding to the listed tracking module, or a location defined by device management system 40. Locations 402 and devices included in device list 401 may be imported into device management system 40 prior to assignment. In one configuration, the number of devices per location may be predefined in device management system 40 at the time of import.

[0179] FIG. 5B illustrates an exemplary user interface 403 generated by the device management system 40 to provide tracking module management functions and present device management data for loaded tracking modules. The data elements included in the tracking module device management data or profile shown in the illustrated embodiment include, for each tracking module, (a) capabilities 404, (b) device name 405, (c) device ID 406, (d) accuracy 407, (e) location 408, (f) signal strength 409, and (g) battery level 410. In other embodiments, fewer or additional device data elements may be presented. A location element 411, corresponding to the location 402 provided in the overview presentation 400, may be provided at the top of the hierarchy. Loaded and saved tracking modules and associated device data elements are stored in the identified location 411 and presented below the location 411 element. In one configuration, the device management system 40 may be configured to allow a user to move the location and associated device management data to change their order in the presentation. In this or another configuration, a user can collapse or expand tracking module data for a selected location by, for example, interacting with the location 411 field. In this or another configuration, the presentation includes a location labeled "Storage" 412 that stores tracking modules that have been loaded but are not currently in use. In one example, this location label is fixed and cannot be deleted. As described above, the device management system 40 can communicate directly or indirectly with loaded tracking modules to receive data associated with one or more device data elements. In various embodiments, the presentation may be configured to automatically update at predetermined time intervals, such as every 30 seconds, or upon the occurrence of an event, such as a device data element being received outside a predetermined tolerance or threshold.In some configurations, the presentation may include a manual update option to cause the values ​​of the device data elements to be updated immediately.

[0180] "Active" is specified in the Active 404 data element if the respective tracking module is transmitting a location signal, such as GPS information / coordinates, polling signal, response signal, location signal parameters, location data, positioning signal, etc.

[0181] The device name 405 may be a unique name associated with the device. The device ID 406 may be a manufacturing ID number assigned to the GPS or other location technology. The accuracy 407 may refer to the measurement accuracy of the device's location as a distance. The location 408 may refer to the device's current location. Depending on the configuration and location technology used, the location values ​​may be provided in latitude / longitude, grid coordinates, or other suitable location coordinate designations. In various embodiments, the device management system 40 may perform one or more location operations related to the location system. For example, the device management system 40 may receive location data transmitted from a tracking module during play. The device management system 40 may provide such location data to the location system continuously, on demand, or at predetermined intervals. As one example, the location system receives a timestamp from the ST application corresponding to a location event entered into the companion device. The location system can provide the timestamp to the device management system 40 and pair it with the corresponding location of the tracking module specified by the timestamp. In another example, the companion device may send a location information event to the device management system 40 for location pairing. Any suitable data handling and flow may be used to perform such location operations during play. For example, the tracking module may send location and / or position identification data to the location system, and the companion device may send location events to the location system for timestamp and location pairing with the tracking module.

[0182] Signal strength 409 may be the current signal strength of the location signal received by and / or transmitted by each tracking module. For example, signal strength 409 may refer to wireless signal strength, such as cell, Wi-Fi, UWB, etc., and may be queried by device management system 40 to measure the health of the tracking module with respect to its ability to share location information or other data, such as swing. In one embodiment, signal strength 409 may refer to the accuracy of location-based coordinates. Battery life 410 provides a value related to the life of the tracking module's battery. For example, the battery life element data value may be presented as a percentage of battery life remaining, or as a time or duration until the battery will be completely depleted or depleted to a threshold level.

[0183] In some embodiments, communication between the device management system 40 and the tracking module may be bidirectional. For example, the device management system 40 may be configured to address the tracking module. In one such configuration, deleting or transferring a tracking module from location 402 / 411 by operation of the device management system 40 may cause the deleted tracking module to send a communication. This communication causes the tracking module to update its location to “unassigned,” “storage,” or possibly a new location. In one example, the tracking module may include a user interface (e.g., see FIG. 4C ) that allows a user to view device data elements associated with the tracking module. In the above or another example, the communication may cause the tracking module to output a notification that it will no longer be used, will no longer be associated with the location, or will be moved to another location. The notification may include a sound, a text display, a light, or other indication that provides the desired notification when perceived by the user. In one example, the tracking module includes a notification button that, when pressed by the user, triggers an output notification associated with the tracking module. In some embodiments, the tracking module is not configured to store an indication of the assigned location.

[0184] In one embodiment, the device management system 40 is configured to allow a user to assign tracking modules to players. Tracking module assignment may be based, for example, on player grouping for a round. Referring to FIG. 5C , the device management system 40 may be configured to generate a device assignment user interface 420 that allows a user to perform device assignment operations. In various embodiments, the device assignment user interface 420 and the device management overview 400 may be provided in a tabbed format so that a user can perform device management or device assignment operations from either interface simply by selecting the desired tab. In one embodiment, the device assignment user interface 420 can receive groupings from a grouping engine and automatically assign tracking modules to groups and players from a device list.

[0185] The device assignment user interface 400 may include various device assignment elements. For example, the device assignment may include an element selected from one or more of: (a) device list 421, (b) device setup list 422, (c) save device setup 423, (d) menu 424, (e) event 425, (f) round 426, or (g) group presentation 427. The group presentation 427 element may display the group for device assignment along with the players associated with the group, if available. For example, the group presentation 427 may include one or more of: (a) group number 428, (b) player name 429, (c) device name 430, or (d) device status 431.

[0186] The device list 412 may include a list of devices that are not assigned to a group number. The device settings list 423 may include saved settings of device assignments to group layouts. In certain embodiments, save device setup 423 may be provided as an option operable by an operator to save device setups for a set of groups. The menu 424 may include one or more additional options that are not displayed for quick selection on the main panel. The event 425 may identify the event in a golf tournament or other event at which device assignments for each group are reviewed and managed. The round 426 may identify the round of the event at which device assignments are reviewed and managed.

[0187] As introduced above, the device assignment element may include a menu 424 with additional options to assist a user in setting up a device assignment. In one example, the menu 424 may include a "Location Selection" option that allows a user to select or specify a location for one or more devices to be used in the device assignment. In the above or another example, the menu may include a "Tournament" option that allows a user to select a tournament. A tournament option or another option may be available to specify the tour to which the tournament is associated. It will be understood that the assignment element may be provided in any suitable presentation format, and that elements referenced with respect to the menu 424 may be provided on the main device assignment user interface 420 display.

[0188] In one embodiment, the device management system 40 may be configured to load a group number and a shell for devices assigned to that group. In various embodiments, each assignment within a group may be in sequential order. The order may be static as long as the device is assigned to a group and not reassigned. As introduced above, the device list may include a list of all tracking modules that are not assigned to a group and are therefore available for assignment. The device management system 40 may be configured to allow a user to assign devices in the device list to a group. The user may further assign devices in a specific order within the group. Once devices are assigned to a group, the user may save the assignment via the save device settings operator.

[0189] The group presentation provided in the device assignment user interface 420 may be configured to provide a group number and the devices associated with that group. If there are players in the selected round, the group presentation may display each of the players associated with the group in teeing order. For example, when a round is selected from the round 246 element, the group presentation may automatically fill in the players in the grouping. The group number 428 includes a number associated with the grouping for that round, which may also be assigned to each tracking module assigned to the group for deployment. The player name 429 may include the name of each player assigned to the group and may be presented in teeing order. The device name 430 may include the name of the device. The device status 431 may include details of the device's current hardware capabilities, such as battery life and signal strength.

[0190] In one embodiment, assigning a tracking module to a player associates a tracking module identification number with the player in the STTM system backend, associates the identification number with data obtained from and / or recorded by the tracking module, and the STTM system component receiving the data, e.g., companion device, location system, verification system, data management system, device management system 40, and / or data platform, associates the identification number with the assigned player. Such STTM system components can receive the player and tracking module identification number assignments set by the device management system 40 for such purposes. In one example, the companion device receives the player and tracking module identification number assignments set by the device management system 40 and associates the tracking module data with the player during scoring, e.g., stores and / or transmits it to the same STTM system component. As introduced above, the STTM system can include a location network configured for device-side and / or network-side location tracking, e.g., utilizing a UWB anchor network. In a network-side location tracking use case, the device-player assignment is sent to a system component configured to calculate a location from data collected by the network-side location network, or is subsequently used to associate the tracking module's calculated location data with that of the assigned player.

[0191] As introduced above and with reference to FIGS. 6A-6G , the STTM system may include a round management system 60 configured to manage rounds and groupings of players playing in an event. The round management system may provide data manager data access to round management operations locally, remotely, and / or from any location via a management device. In various embodiments, groupings may be managed by a grouping engine 500 configured to record one or more of saving tee times, adjusting to pre-published tee times, or player ordering within each tee time group. In some embodiments, the grouping engine 500 may be configured to automatically generate groupings for future rounds based on scoring rules. Rounds may be managed by a round engine 501 configured to manage one or both of round status and round cuts.

[0192] The grouping engine 500 may be configured to manage groupings. Managing groupings includes creating groupings of players. In one example, the grouping engine 500 may be configured to allow a user to define and manipulate groupings for every round of every event. FIG. 6A illustrates a user interface for the grouping engine 500, including a grouping management panel 503 configured to interface various operations of the grouping engine 500 to a user.In various embodiments, the grouping management panel 503 can be configured to provide one or more elements, such as interface elements, display elements, or related operational elements, including: (a) a grouping presentation element 504 consisting of a list of groups with associated tee times for each segment; (b) a display by segments element 505 operable to allow a user to view each segment, a defined portion of a segment, or all segments at once; (c) a player list element 506 identifying players who are ungrouped or available for grouping; (d) a segment list element 507 identifying segments created for a particular round; (e) a round selection element 508 operable to allow a user to select a round in order to review and edit the groupings associated with that round; (f) a segment profile selection element 509 operable to load a previously created profile with segment information; and (g) a segment selection element 509 for creating or modifying segments for a round. (h) an edit element 510, (i) a create grouping element 511 configured to generate groupings based on predefined and / or definable round segment rules, (ii) a delete player element 512 configured to remove players in the grouping presentation component while preserving tee time data, (iii) a create shell element 513 configured to generate groupings that do not include players but have groupings based on round segment rules, (iv) a clear grouping element 514 configured to remove player and tee time data from the grouping presentation component, (v) a grouping state element 515 including a selectable list of grouping states, (vi) a revision element 516 for accessing revision editor operations operable to adjust groupings and flag rounds as having revised groupings, or (vii) a player status element 517 providing access to player status editor operations operable to change the status of players for rounds in the event.

[0193] 6B , the grouping engine 500 may be configured to display a grouping presentation 518. The grouping presentation 518 may be displayed in whole or in part or may be accessible via interaction with the grouping presentation element 504 ( FIG. 6A ). In the illustrated embodiment, the grouping presentation 518 includes grouping data elements provided in rows, with each row representing a group of players with a tee time. For each group, one or more of the following grouping data elements may be provided: (a) segment number 519, which provides a segment number associated with the group; (b) group number 520, which is associated with the group of players for a particular tee time; (c) tee time 521, which provides the current time created for the group; (d) tee time data 522, which provides the date of the tee time created for the group; (e) course 523, which provides the course the group will play for the specified tee time; and (f) player 524, which provides the names of the players assigned to each group, which may be presented in order of play.

[0194] As will be explained in more detail below, various grouping and / or round data may be subject to revision. In the illustrated display, grouping data that has been subject to revision from its original value is labeled with an (R) in this example to indicate a revision of the original tee time.

[0195] In various embodiments, the grouping engine 500 can provide various display and / or editing options for the groupings and associated data elements within a grouping presentation. For example, the grouping engine 500 can provide interface elements that allow a user to sort columns of data, for example, numerically, alphabetically, chronologically, or by other suitable data point characteristics. In one example, an interface element can be provided that allows a user to cause the grouping engine 500 to selectively present groupings by segment number or by all segments at once. In the above or another example, the grouping engine may be configured to allow a user to edit the data points of a row of data. For example, editing functionality can be provided along with or separate from the displayed data. In one embodiment, the displayed data elements referenced in FIG. 6B can comprise interface elements that display respective data point values ​​and are configured for user interaction to optionally edit the data point values. The grouping engine 500 may provide editing functionality for grouping data elements selected from the following: (a) a segment number editor containing a list of available segments created or loaded from a profile; (b) a group number editor operable to allow a user to change the group number value (typically a positive integer); (c) a tee time editor operable to allow a user to change the tee time (e.g., hour:minute); (d) a tee time date editor operable to allow a user to change the tee time date (e.g., month:day:year); (e) a course editor operable to allow a user to change the course (which may include a selectable list of courses available for the selected tournament and event); (f) a player editor operable to allow a user to change the player (e.g., selecting a player provides a field to enter another player or displays a list of selectable players, which may include drag and drop or other selectable methodologies); or (g) a combination thereof.As noted above, the display elements in the grouping presentation 518 may be composed of interface elements. In one embodiment, interaction with such interface elements may result in the editor operations described above. In one configuration, the grouping engine 500 is operable to allow a user to selectively add rows, remove rows, or both.

[0196] 6A , player list element 506 may selectively display, or be configured to display, a list of all players in the field for a selected event who are not placed in or assigned to a group in grouping presentation 518. In various embodiments, a user may assign players to tee times via interaction with player list element 506 or via another interface element in grouping presentation 518. In one embodiment, player list element 506 is configured to display the player's name and the player's event score total relative to par.

[0197] The grouping engine 500 may utilize segments and segment profiles. A segment may include a block of tee times representing the beginning stages of a round. For example, two segments of a group may include one starting on the first hole and the other starting on the tenth hole. A segment profile may include a set of segment rules that the grouping engine 500 uses to assist in generating groupings. The grouping engine 500 may include or have access to one or more segment profiles. Segment profiles may be loaded and / or created using a segment data manager. In various embodiments, the grouping engine 500 may be configured to automatically apply one or more segment profiles to a round. For example, a user may define, save, load, or delete one or more profiles that the grouping engine 500 applies to an event or its round. In one embodiment, the grouping engine 500 is configured to allow the current user to search for other users that include related segment profiles, such as segment profiles and / or user profiles, or segment profiles created by or previously used by other users. In one example, a user can select a segment profile and import the selected profile into a current event or their profile, or export the segment profile into another user's profile.

[0198] 6C illustrates a segment profile management interface 525, including example elements of a segment profile along with definitions of options for editing the data elements or creating a new segment. The example elements and definitions of options for editing may be available to a segment data manager for creating a new segment profile. The elements may include one or more data elements selected from the following: (a) segment number selection 526, including a list of segments created for the selected round; (b) segment priority 527, consisting of a non-overlapping positive integer value set to another segment associated with the round so that a particular segment can exist in the system once per round; (c) courses 528, including a list of courses associated with the selected event; (d) date 529, identifying the date a tee time begins play; (e) tee time 530, identifying the first tee time for a start or finish; (f) tee time (start / finish) 531, including an option to flag a tee time as a start tee time or an end tee time; and (g) the time between the start or finish time set in tee time (above) and tee time (start / finish) (above). (h) if set, Groups in Interval 533, identifying the number of groups that will be in an interval while the remaining groups are in a different interval, as applied using First Interval (below) and Remaining Interval (below); (i) First Interval 534, representing the number of groups defined in Groups in Interval (above); (j) Remaining Interval 535, representing the time interval for groups not defined in Groups in Interval (above); (k) Best Score Last / First 536, identifying whether the best scoring player is set to the first or last tee time; (l) Starting Hole 537 for all tee times in the segment; (m) Players per Group 538, identifying the maximum number of players assigned to a group; (n) Number of Groups 539, identifying the initial number of groups for the segment; or (o) a combination thereof.The segment list panel 540 may be configured to display all data elements for each segment of the segment profiles loaded into the segment profile management interface 525 .

[0199] In some configurations, the grouping engine 500 is configured to allow a user to create or delete segments. For example, elements of a segment profile may be editable through interaction with elements in a display, where options for editing the elements comprise interface elements the user uses to edit data elements or other aspects of the segment profile. For example, to delete a segment, a user can select Delete Segment 541 from the segment profile management interface 525. To create a new segment, a user can select Create New Segment 542 from the segment profile management interface 525. Upon selection, the user is presented with default data elements, such as the next sequential number from the current segment in the profile, the next sequential number from the current segment in the profile, the currently selected course, or a predefined time interval. In various embodiments, additional data elements can be set to other default values ​​or left blank to be further specified by the user.

[0200] When loading an existing segment profile, the number of groups per segment may default to the round field size divided by the number of segments. When editing a segment after the number of players has been updated, the number of groups in each segment is updated based on the round field size divided by the total number of segments. In one configuration, if a multi-segment profile has an uneven number of groups, odd groups may automatically be placed at the highest even segment priority by default.

[0201] After editing or creating a new segment profile, the user can save the segment profile 543. In one example, the user may be asked to provide a name for the profile, which may be a new name for the profile. The user can also save the profile and overwrite the current segment profile with the updated profile.

[0202] 6A , the grouping engine 500 may be configured to generate groupings. In one embodiment, a user can interact with the grouping generation element 511 to generate groupings for an event, a round, or a segment thereof. For example, when an option in the grouping generation element 511 is activated, the grouping engine 500 can generate groupings utilizing the current segment profile. Tee times can be generated based on the configuration of each segment in the segment profile.

[0203] When generating groupings, a player slot may be identified for each player based on the number of players per group, as defined in the segment configuration, with the slot representing the order in which each player plays. The slot referenced as 1 is the player who will play first, the slot referenced as 2 is the player who will play second, and so on. If multiple segments are part of a round's segment profile, the grouping engine 500 may automatically begin assigning players with the segment set as priority 1 and make player assignments sequentially as each segment completes its player assignments. If Best Score Last / First 536 is set to Last, player assignments may begin with the last tee time of the segment and work backward from there. If Best Score Last / First 536 is set to First, player assignments may begin with the first tee time of the segment and work forward from there. With regard to player selection and slotting when Best Score Last / First 536 is set, the grouping engine 500 may assign players to the player with the highest tournament score to the first slot, the player with the second best score to the second slot, and so on until each slot within a tee time has been assigned a player before moving on to the next tee time. In some embodiments, a segment profile can tie multiple players together. In one example, if multiple players are tied, the grouping engine 500 can apply the following ordering rules to determine the next player's assignment: (a) earliest tee time from the previous round, (b) highest segment priority from the previous round, highest first, (c) lowest slot number, lowest first, and (d) highest priority course, highest first.

[0204] The grouping engine 500 may be configured to utilize elements of the segment profile for a selected round to create a grouping shell or for grouping automation. For example, when the grouping generation component 511 is invoked, the grouping engine 500 is configured to create groupings using the currently selected profile for that round. Tee times may be generated based on the configuration of each segment in the segment profile, as described above. When the shell generation component is invoked, the grouping engine may be configured to suggest slots based on the number of players assigned to each group for each segment and generate a grouping shell.

[0205] Each round is associated with a grouping state. The grouping state may be editable via the grouping state element 515. In one embodiment, the grouping state may be selected from one or more of: (a) draft, (b) to review, (c) reviewed, (d) official, or (e) a combination thereof. The "draft" state may be utilized by a user while they are working to create the groupings needed for a round. In one embodiment, the "draft" state may be set as the default state when initially creating the groupings. The "to review" state may be set when a defined set of groupings is ready for review. The "reviewed" state may be set when a defined set of groupings has been reviewed and the review determines that they are ready to move to the "official" state. The "official" state may be set when a set of groupings has been reviewed, approved, and is ready for distribution.

[0206] In various embodiments, the grouping engine 500 may be configured to apply one or more grouping state rules. For example, the grouping engine 500 may restrict the setting of a grouping state that progresses toward formal skipping the grouping state. In one example, a "reviewed" grouping state cannot be set until a "to be reviewed" grouping state is set, and an "formal" grouping state cannot be set until a "reviewed" grouping state is set. In various embodiments, the grouping engine 500 is configured to log all grouping states with a timestamp of the user's selection. The user who made the grouping state selection may also be logged and associated with the selection.

[0207] In some embodiments, the grouping draft is saved for subsequent review by the grouping engine 500. In one example, the saved grouping draft is not distributed to other STTM system components. In some embodiments, a review may be performed to modify the grouping, for example, to create hot groups, to prevent players from being in early groups multiple weeks in a row, to separate players who are known to play slower, to separate players who do not stay alone, etc. In one example, once the grouping data is in a state for review, an administrative user can review the data and then, once signed off, set the grouping date to an “approved” state. Once the grouping data is approved and the associated state is set to “approved,” the grouping data becomes available to other STTM systems.

[0208] As introduced above, the grouping engine 500 can include a revision editor. In the illustrated embodiment, the revision editor operation may be initiated by interacting with the Revision element 516 of the grouping management panel 503. Revision states can be designated by various states. For example, revision states include “To Be Revisioned,” “Revision,” and “Revised.” The “To Be Revisioned” state may be set as a default state that is set before a revision occurs, after a grouping becomes official and before the revision process begins. The “Revision” state is displayed when a user utilizing the revision editor is in the process of revising a grouping that already has its state set to “Official.” The “Revised” state may be displayed when the grouping review process is complete and there is a change from the original grouping that was set as the official grouping state. In one embodiment, any changes made to the grouping or data elements updated by the revision editor may automatically set the revision state to “Revision,” and the grouping state may restart from the “To Be Reviewed” state. In further or alternative embodiments, the "revision" state may be set any time after the original grouping is set to the "official" grouping state, upon completion of the grouping validation process.

[0209] The revision editor may include various operations that a user can use to adjust tee times from the current grouping tee times. For example, FIG. 6D illustrates an interface for a revision editor 545 configured to adjust tee times using a revise based on an offset element 546 or a revise using the methodology of a reference time element 547. Revise based on an offset element 546 may cause the revision editor 545 to apply a revise based on an offset technique utilizing start and end groups. The start and end groups may be predefined or may be set by the user, for example, by interacting with a start and end group element 548, and represent the start and end groups for which the tee times are adjusted. A time-based revise element 547 may cause the revision editor 545 to apply a revise based on an offset technique, which, in one embodiment, may also include a time adjustment, which may be specified via interaction with an adjust time (+ / -) element 549 in the illustrated interface, consisting of an amount of time applied to the original tee times of the groups identified by the settings in the start and end group steps. The start and end group and / or adjustment time (+ / -) elements 548, 549 may include interface elements including fields for entering text, selectable lists of groups and / or time differences, or other suitable interface elements. Revising using the base time approach may allow the user to utilize a new base tee time that replaces the original base tee time via interaction with the new base time element 550, with the remaining tee time adjustments then being generated based on the data elements defined in the round's segment profile. In various embodiments, once a revision is utilized and applied, the round state is set to "revision" and the grouping engine 500 begins the grouping validation process.

[0210] As introduced above, the player list element 506 may include or provide access to a list of all players in the field for the event. In some embodiments, player status for an event and / or round may be associated with a player's name, e.g., displayed. In some embodiments, the grouping engine 500 may include a player status editor configured to change a player's status. For example, in one configuration, a user may highlight a player in the player list and select the player status component to access the player status editor and change the player status of the selected player. Referring to FIG. 6E , which illustrates an example interface for a player status editor 560, a status options list 561 may be provided that a user can use to set the player status of a selected player. A status setting operator 562 may be provided to enable a user to set the status of a selected player. Various player status options may be provided, which may include one or more of the following: (a) uncut—a status identifying a player who is eligible to play in the event; (b) cut—a status identifying a player who has been flagged for cut, which, as described in more detail below, can be set manually or updated automatically after a cut rule has been implemented; (c) dropped—a status identifying a player who has dropped out of a round; (d) disqualified—a status identifying a player who has been disqualified from a round; or (e) cut but did not finish—a status identifying a player who will be paid official money but will not continue playing in the remaining rounds. In various embodiments, the player list 563 is automatically updated upon setting the player status. The player status editor 560 may be configured to provide additional options for further defining player status.For example, the player status editor 560 may provide the user with an option to define whether a player status entered by the user as "withdrawn" will also be set for future rounds for that player. If a player's status is set to "withdrawn," "disqualified," "cut," or "cut but did not finish," the player may be removed from the grouping presentation 504 for the specified round and from the player list 506 of the grouping management panel 503.

[0211] As introduced above, the round management system may include a round engine configured to allow a user to define round states different from the round states defined in connection with the various grouping creation processes described above with respect to Figures 6A-6E. In some embodiments, the round engine is also operable to allow a user to create and execute player cuts on a round. In one example, the round engine may be configured to provide playoff management operations in conjunction with round states and / or cuts.

[0212] 6F illustrates a user interface for round engine 501, including a round management panel 570 configured to interface a user with various operations of round engine 501. In various embodiments, round management panel 570 may be configured to provide one or more elements, such as interface elements, display elements, or related operational elements. In the illustrated embodiment, the elements include one or more round selection elements selected from (a) round selection element 571, (b) round status element 572, (c) suspend type element 573, and (d) suspend round element 574.

[0213] The round selection element 571 may be operable to select a round for control. The round selection element 571 may or may not consist of a selectable list of rounds available at the event that are presented for user selection.

[0214] The round state element 572 may be operable to select a round state, and may comprise a selectable list of available round states or may be presented for user selection. In some embodiments, one or more round states may be automatically set by the round engine 501. In various embodiments, the round state may include the following states: (a) not started—the default state before a grouping is made official; (b) grouping official—a state corresponding to and only available when the respective grouping for the round is made as “official,” as described above; (c) in progress—a state that is automatically set when the first stroke or score of the round is made, and in some embodiments, may additionally or alternatively be set manually; (d) suspended—a state that is set when the round is suspended due to weather or other circumstances; (e) played—a state that is automatically set when the final score of the round is made, and in some embodiments, may additionally or alternatively be set manually; (f) official—a state that is set when no further changes to the round data, such as changes to stroke information or scores, are required; (g) canceled—a state that is set when the round is canceled and the remaining time of the event is not played; or (h) combinations thereof.

[0215] In various embodiments, when the round state is set to "suspended," the user can select a suspension type using the suspension type element 573. In one example, the round engine 501 can request or prompt the user to select a suspension type when setting the round state to "suspended." In various embodiments, the suspension type element 573 can include or be operable to cause a selectable list of suspension types to be presented for user selection. Exemplary suspension types can include one or more of delayed, canceled, suspended, or end of day.

[0216] In various embodiments, when the round state is set to “suspended,” the user can select a suspension reason using the suspension reason element 574. In one example, the round engine 501 can request or prompt the user to select a suspension reason when setting the round state to “suspended.” In various embodiments, the suspension reason element 574 can include or be operable to cause a selectable list of suspension reasons to be presented for user selection. Exemplary suspension reasons can include weather or environmental reasons. In one configuration, the suspension reason can include one or more of darkness, rain, thunder, fog, wind, or frost. In a further configuration, the suspension reason can include a text field for entering a custom reason for suspension, such as, for example, a tornado warning, equipment issues, or course maintenance.

[0217] The round management panel 570 may also include one or more elements configured to interface a user with the operation of the round engine 501 regarding the management of a cut in a round. While certain elements are depicted on a single or the same panel, it will be understood that such elements may be provided in many different ways, including on different panels and / or in different combinations. With regard to the cut management elements, in the illustrated embodiment, two selectable lists are available: a non-cut (uncut) player list element 575 and a cut player list element 576. The non-cut player list element 575 includes or is operable to present a selectable list of all players in the round who have not been flagged as cut. The cut player list element 576 includes or is operable to present a selectable list of all players who have been cut for that round. The cut management elements also include a run cut element 577 and an uncut all element 578. The run cut element 578 is configured to execute cut rules based on selected settings, as described below, and set defined players to a cut player status. The uncut all element 578 is configured to remove cut player status.

[0218] With respect to the cut rule, selectable settings may include the number to cut 579, the number to cut and play 580, the maximum number of strokes from the lead 581, the target cut 582, include amateur 583, or a combination thereof. The number to cut 579 corresponds to the number of players who make the cut based on their score and whose player status remains uncut, while all other players set to uncut have their player status set to "cut." The number to cut and play 580 corresponds to the number of players who make the cut based on their score and continue playing the round. If set, the difference between the number to cut 579 and the number to cut and play 580 set above may include players whose player status is set to "cut but did not finish." All other players may have their player status set to "cut." The maximum number of strokes from the lead 581 may correspond to the number of players who make the cut that is a number of strokes from the lead relative to par. The target cut 582 may correspond to the number of players who make the cut closest to the set value, regardless of whether they are above or below that value. If the player values ​​are the same above and below, all players above the value are considered "uncut" and all remaining players have a player status of "cut." Include Amateurs 583 can correspond to whether or not to include amateurs as part of the cut rule. If set, participating amateurs are part of the cut rule. If not set, the cut rule does not include amateurs. Include Amateurs 583 can be selected in addition to other cut rule components. It will be understood that if selectable settings are included, different and / or additional settings may be provided.

[0219] The round management panel 570 may also include a save round information element 585 that provides the user with the option to save or cancel changes made to the round state and / or cut configuration. In one embodiment, once the cut rule definitions are saved for a round, the cut rules may be used for live projected cut presentations in the STTM system. However, the round engine 501 may be configured not to set player status as defined above until the user executes the cut rule option.

[0220] The round management panel 570 may also include one or more elements configured to interface a user with operation of the round engine 501 related to a playoff round creator. For example, the round management panel 570 includes a playoff creator component operable to provide access to a playoff round creator configured to create playoffs for a selected round. Figure 6G illustrates an example user interface of the round engine 501 configured to interface a user with various operations of the playoff round creator 586.

[0221] The playoff round creator 586 may include various elements for defining a playoff round. For example, the playoff round creator 586 may include one or more definable elements selected from (a) playoff type 587, (b) playoff number 588, (c) determined position 589, (d) starting hole sequence 590, (e) repeating hole pattern 591, (f) player list 592, (g) save playoff 593, (h) start playoff 594, or (h) set winner 595.

[0222] The playoff creator 586 may be configured to include multiple selectable playoff types for selection via the playoff type element 587, such as one or more playoff types selected from "Sudden Death," "Number of Holes," and "Number of Holes / Sudden Death." "Sudden Death" corresponds to a playoff format in which, starting with the first playoff hole, a player participating in the playoff plays until he or she has a better stroke score than the other players participating in the playoff. If two or more players are playing, the player with a higher score than the best score on that hole is eliminated. "Number of Holes" corresponds to a playoff format in which all players participating in the playoff play a number of holes defined by the starting hole order below. If a player has the best score, that player wins and the playoff ends. In the event of a tie after the set number of holes, the playoff repeats for the set number of holes. This process continues until a player has a better score than the other players in the playoff. In this playoff type, multiple players may be eliminated if they do not have a better score than the best score. "Number of Holes / Sudden Death" corresponds to a playoff format where the playoff begins with all players participating in the playoff playing a defined number of holes in the starting hole order below. If a player has the best score, that player wins and the playoff ends. If there is a tie after the defined number of holes, the playoff goes into sudden death as defined above.

[0223] A playoff number element 588 sets or is operable to set a playoff number, which allows a user to store multiple playoffs for a round. A determined position element 589 defines or is operable to define the position of a player who will play in a playoff. For example, a determined playoff position may include position 1 if multiple players are tied for first place, or position 3 if multiple players are tied for third place.

[0224] The starting hole sequence element 590 may define, or be operable to define, the hole on which the playoff will be played first. In the case of a "number of holes" playoff format, the starting hole sequence element 590 provides the holes defined for that format. The repeating hole pattern element 591 may define, or be operable to define, a repeating hole pattern for a "sudden death" playoff format in instances where a winner has not been identified after the holes of the starting hole sequence are completed.

[0225] The save playoff component 593 may be operable to save the playoff settings. In some embodiments, the playoff settings may be saved without starting the playoff.

[0226] The playoff initiation element 594 may be operable to initiate a playoff. In one embodiment, a playoff may not be initiated in the round generator until play is completed in a selected round. In one example, a playoff may require verification that a previous round is complete. In another embodiment, a playoff may be initiated before the previous round is completed.

[0227] Once play is complete in the selected round, a player list 592 is imported into a playoff round creator 586 by analyzing the scores according to the playoff number 588 and / or determined position 589 settings. The playoff round creator 586 can then be configured to apply the remaining playoff settings to create a new round according to the rules. Players who qualify for a playoff round may be placed into groupings, which may automatically include up to four players per group, as described above, although in some embodiments, manual group placement may be used. In some embodiments, the groupings for the playoffs may be configured to be reviewable via a grouping presentation. In another or further embodiment, the round status may be automatically set to "grouped official."

[0228] As introduced above, companion devices can be used by scorers to perform scoring functions. Scorers may include caddies, players, or other individuals observing play. The companion devices can run the ST application. The companion devices may include a wireless data communication transceiver configured to wirelessly transmit score data, which may include event data, to STTM system components. During play, each group can have an assigned companion device that the scorer uses to collect score data. The score data is transmitted to a management system, which is configured to process data received from multiple companion devices during play. Companion devices can be configured with various wireless communication technologies, such as those described above, which may include short-range and / or long-range communication with devices in the STTM system. Companion devices can be configured to communicate with the tracking module to trigger and / or define data collection events that can be used to officially score players' rounds. For example, companion devices can be carried by a scorer accompanying a group of players or observing play. In various embodiments, a companion device may not be configured to communicate with a tracking module, and the companion device may transmit location and / or location data to a location system, location element, and / or other STTM system components. The companion device may similarly transmit collected score data and / or event data to a location system, location element, and / or other STTM system components.

[0229] In various embodiments, the companion device may be configured to wake up the tracking module and initiate event capture, such as collecting event data (e.g., event capture, position / location determination, or related data for processing and determination of same by the companion device or another processing device). In one embodiment, the tracking module may be configured to receive instructions for event capture. The instructions may be sent by the companion device or the managing device. For example, the companion device and / or the managing device may be networked with or otherwise operable to provide instructions to and / or receive instructions or data from multiple tracking modules. It should be understood that the managing device may include or provide data to the location system.

[0230] While scorers using companion devices typically accompany the players they are tracking, in some embodiments, scorers can view players remotely via live or delayed feeds. If the scorer is also entering events that set the address timestamp or when the ball was hit, these can be paired with the tracking module's location to provide a proxy for the ball's location following the previous shot and the ball's starting position for the current shot; the feed should be live or with a precisely known delay to accurately link the player's location to the ball's location. In remote viewing use cases, the tracking module can be configured to communicate with the managing device or intermediate relay device via an appropriate communication protocol, which may include a short-range or long-range communication protocol, depending on the proximity of the managing device or intermediate relay device, to provide its location data or calculation parameters. In configurations where the tracking module's location is subject to network-side calculation by other devices, the other devices can communicate directly or indirectly with the managing device.

[0231] The ST application or a companion device (which may be local, remote, web-based, or cloud-based) running and / or accessing the ST application may be utilized by a scorer to score one or more rounds of golf, representing a golf tournament event. Collected scoring data may be stored or transmitted by the companion device, as discussed in more detail elsewhere herein. References to transmission of scoring data from the companion device and / or tracking module, which may include event data and / or location data, may include indirect or direct transmission to one or more location systems, management systems, and / or data platforms. For example, scoring data may be immediately or subsequently transmitted to a location system and / or one or more management systems for applications configured to perform further data management, data review, data correction, score verification, data analysis, data storage, location identification, location calculation, zone identification, or other STTM system operations. A data viewing platform may refer to distribution to a subscription service or platform, such as a downstream client, a business or consumer-level platform, a private or public network for fan consumption alone or with other data, a surface web platform, or the like. In various embodiments, the scoring data may be distributed or made available for use or integration with web apps, mobile apps, or other applications for public or private viewing, analysis, or archiving.

[0232] The ST application may be configured for multiple selectable score-level operations, such as stroke-level operations, where a scorer may utilize the ST application to record strokes as they occur without utilizing the position functionality of the tracking module or utilizing and / or incorporating a tracking module as described herein.

[0233] When using a tracking module to obtain location information, the ST application or other STTM system applications or services can combine the location information with stroke-level data. In laser-operator-level scoring, scorers may use the ST application to record strokes without additional location information, or they may track player locations via a tracking module for use in combination with laser position tracking, either via a manual laser pointing device like those used by PGA Tour laser operators or through operation of an automated laser system that tracks or continuously tracks the ball's location throughout a round. Laser information can be output or converted to a coordinate grid system based on mapping such as course surveying or GPS. In a combined-use configuration, location data obtained from different technologies may be used for separate end uses, combined for analysis to achieve greater accuracy, or one location technology may be used as a backup or reference for another location technology. In one embodiment, the companion device and ST application can be configured to allow one scorer to collect stroke-level data for all players in a group.

[0234] In one embodiment, the companion device may be pre-loaded with or configured to access, via the ST application, specific event data such as one or more of: (a) par values ​​for a particular course; (b) hole sequence for the course (which may be associated with par values); (c) pre-defined starting locations (which may include location indicators, not just from locations selectable in a "Starting Location" screen); (d) score levels for the event (stroke recording only or utilizing and / or incorporating location tracking, e.g., GPS, UWB, BLE, Wi-Fi, cellular, etc., rangefinders, laser operators, or combinations thereof); (e) course name; (f) player group data for assigned groups, multiple groups, or all player groups for the event, such as player names within a group, player numbers within a group, player images, e.g., headshots, or the like; or (g) combinations thereof. In one example, the ST application runs, at least in part, in a cloud-based environment, and the event data is automatically provided to the companion device, such as upon startup. If the event is conducted on multiple courses, course data for a particular course or courses may be provided or selectable by the scorer, for example, via a user interface. Course names and course numbers may be provided. The companion device may automatically be provided with round details, including group updates, group assignments, event changes, event notifications, or other round details.

[0235] In one embodiment, using the ST application, the companion device can be configured to receive group location data. The scorer may interface with the companion device's user interface to enter group location data by any suitable method, such as by entering it into a provided field, selecting from a displayed list of options, etc. In one example, the scorer enters or selects "Tee" when the group's players are at the tee box. In yet another example, the scorer can enter or select "Fairway" when the first caddie or player in the group arrives at the player's ball in the fairway. In yet another example, the scorer can enter or select "Green" when the first caddie or player in the group arrives at the player's ball around the green.

[0236] The output of the data management system, device management system, round management system, grouping engine, and / or round engine may be sent to the ST application to adapt the operation of the ST application to the output. For example, a grouping output may be sent to the ST application to input one or more groups to which companion devices are assigned.

[0237] As introduced above with respect to FIG. 3, in various embodiments, the location of a group and / or player can be automatically tracked via location tracking technologies and associated location networks, such as GPS, Wi-Fi, RFID, BLE, UWB, NFC, cellular, etc. For example, an ST application can incorporate geofencing that triggers a group's repositioning within predefined boundaries. Geofencing may also be applied by other STTM system applications by tracking the location of companion devices and / or tracking modules.

[0238] To track a player's hits, the companion device can present a selectable list of players from which the scorer can choose. When tracking a player's hits, the companion device may be configured to present a selectable list of locations from which the player can take a shot. Examples of locations include the tee, the fairway, the primary rough of the green, a bunker, a sandy area, the fringe, a waste area, or a native or natural area. In one configuration, a "starting location" should be set for a player at any time and remain "fixed" for the next shot. In other words, the scorer can set a player's "starting location" as soon as the location is known and have that value persist until the scorer changes the location or indicates that the ball has been hit.

[0239] In one example, the scorer can also input when a player addresses the ball. This can be input as an event, such as when the player first addresses the ball, or as a toggle. In the case of a toggle, the companion device user interface can include an "address" button that the scorer presses when the player is facing the ball. The scorer can then press a "shot hit" button or otherwise indicate that the ball has been hit. "address" may be interpreted by the ST application as remaining down until the scorer presses or taps the "shot hit" button or other indicator, at which point both the address and hit events are transmitted or recorded. In another configuration, the scorer maintains contact with the "address" button until the ball is hit. When the scorer releases the "address" button, the ball is interpreted as being hit. In some embodiments, the interaction with the address button is transmitted in real time before indicating that the ball has been hit. In other embodiments, the interaction may be transmitted in real time together after the shot is taken or may be stored locally for later transmission. When collecting location data, such as location coordinate data, for shots utilizing a tracking module, the ST application may be configured to associate a tracking module assigned to a player with the player's name. When the scorer indicates that the ball has been hit, the location of the tracking module is captured and recorded as described elsewhere herein. In some configurations, capturing the tracking module's location may be triggered via interaction with an "address" button.

[0240] The companion device may also be configured to score various stroke types, such as drops, penalties, and provisionals. For example, the companion device may query the scorer or request input of the shot type, if applicable. If the scorer selects "drop," the companion device may prompt the scorer to indicate whether there was a penalty. If the scorer selects "penalty," the companion device may prompt the scorer to indicate whether there was a drop. If the scorer selects "provisional," the companion device may prompt the scorer on the next stroke to indicate whether a provisional is being used. If yes, and the shot location was "off the tee," a penalty stroke may be automatically added to the player's score. If not, and the shot location was "off the tee," the companion device may prompt the scorer to indicate whether there was a drop, and if so, a penalty stroke is automatically added to the player's score.

[0241] As introduced above, the user interface can present a "shot hit" button or other indicator that the scorer can interact with to indicate that the ball has been hit. In one example, the "shot hit" indicator is a button that the scorer taps when the ball is hit. In another example, the "shot hit" indicator is a button that the scorer holds down until the ball is hit, and rather than "pressing," releasing the button indicates that the ball has been hit. In yet another example, a multi-stage "shot hit" indicator or multiple indicators can be used to indicate at least two of the following: address, location timestamp, and shot hit. For example, a two-stage "shot hit" indicator can be used, with a first stage indicating address and / or location and a second stage indicating location and / or shot hit. In one configuration, the scorer can press a two-stage indicator button when the player is at address and release the indicator button when the ball is hit, with the press setting a location timestamp and the release interpreted as a ball being hit.

[0242] In some embodiments, after the scorer indicates that the ball has been hit, the scorer may be prompted to indicate whether the ball is in the hole. The interface may present a button, swipe bar, field, or the like with which the user can interact to indicate whether the ball is in the hole. In one example, the scorer is presented with a two-way swipe field, and the scorer indicates "yes" or "no" by swiping the field in the desired indicated direction. In one embodiment, if the scorer fails to interact with the associated indicator within a predetermined number of seconds to indicate that the ball is "in the hole," an "in the hole" prompt may be displayed, and the ST application may accept the lack of an indication as a null response with a value indicating that the ball is not in the hole. In another configuration, the ST application may be configured to similarly interpret the lack of an indication as indicating that the ball is in the hole. The scorer may have the option of indicating a null response or allowing a timeout. For example, the scorer may swipe right for in the hole, left for out of the hole, and time out for in the hole. After indicating that the ball has been hit or that the ball is not in the hole, the user interface automatically returns to the group page, from which the scorer can select the same player or the next player to record the same shot. Once the scorer indicates that all players are in the hole, the scorer can be prompted or have available a button or other indicator to advance to the next hole. In another example, once the scorer indicates that all players are in the hole, the ST application can automatically advance to the next hole.

[0243] As described above, scoring data may be collected in real time, stored locally, or transmitted immediately upon the occurrence of an event such as the collection of additional scoring data or when one or all players finish a hole or group of holes, periodically, at scheduled intervals, when the companion device is in proximity to a managing device (which may include a network access point or node), when a predetermined amount of data has been collected, or based on remaining available data storage.

[0244] 7A-7V, which illustrate various user interfaces of the ST application 700 according to various embodiments, a scorer can interface with a companion device to provide a player description. The interface can include various data entry screens through which the scorer can input data. The screens can include predefined, selectable options presented, for example, via list boxes, check boxes, drop-downs, input steppers, text entry fields, etc. The ST application 700 can be preprogrammed to present one or more descriptive categories, each category including multiple descriptive choices from which the scorer can select regarding a selected or identified player. In some embodiments, the ST application 700 can include a field through which the scorer can input a text description. The description can be entered into one or more predefined descriptive categories selected by the scorer. In some configurations, the scorer can enter descriptive information or define descriptive categories by voice or text. Providing a field for descriptive entry can be in addition to or instead of one or more predefined descriptive categories and / or multiple options within such descriptive categories. In one embodiment, the ST application 700 can include or incorporate a photo application or otherwise be configured to input images of players. The ST application 700 can associate an image with the player. In yet another embodiment, the ST application 700 is configured to perform image analysis to analyze the image of the player and extract descriptive attributes, such as the color of clothing worn by the player. In this or another example, the ST application 700 can display an image of the player captured by the companion device or another device that directly or indirectly transmits the image to the companion device.

[0245] FIG. 7A illustrates a user interface of an ST application 700 that provides a menu 701 of selectable options, according to one embodiment. Using the user interface, a scorer can select a player description button 702 from the menu 701. Selecting the player description button 702 can cause the user interface to display a player description screen 703, which provides options for entering one or more player descriptions, as shown, for example, in FIG. 7B. In some configurations, the ST application 700 can pre-populate player names, such as players within a group that the scorer should track. In these or other configurations, the ST application 700 can provide a field for the scorer to manually enter player names or provide a selectable list of groups or players.

[0246] Referring again to FIG. 7B, the scorer can select the description button 704 to provide a description of the player Vincent Johnson.

[0247] Selecting the description button can cause the ST application 700 to display one or more description categories 705. In the example shown in FIG. 7C, the user interface displays a context box containing multiple descriptive categories 705 for the scorer to choose from. The scorer can select a descriptive category from available options and be presented with multiple selectable descriptions. For example, in FIG. 7C, the scorer is presented with three descriptive categories 705 related to clothing: "Player Shirt," "Player Pants," and "Player Cap." Selecting "Player Shirt" displays multiple descriptive characteristics 706 related to the player's shirt from which the scorer can choose. The scorer can select a descriptive category that allows the player to easily distinguish between them. For example, the scorer can select one or more pieces of clothing worn by a player that distinguishes them from other players, allowing the scorer to distinguish which player is taking a shot from a distance. If further clarification is needed, a suitable description can be provided. In FIG. 7D, the descriptive characteristics relate to color. In this example, the descriptive characteristics also include additional characteristics, identified as options in this example, from which the scorer can further define the player's shirt. In the illustrated interface, the scorer has selected green as the player shirt color and light as the optional description. In some embodiments, such as the illustration in FIG. 7D , the user interface may require the scorer to confirm the selection with a confirm button 707. The selectable descriptive features within the "player pants" and / or "player cap" may be similar to or different from those within the "player shirt" descriptive category. While the descriptive categories relate to articles of clothing in the illustrated embodiment, in some examples, different descriptive categories or descriptive features may be provided in addition to or instead of articles of clothing, such as shoes, clubs, bags, brands of articles, etc.

[0248] In various embodiments, the ST application 700 may be configured to receive descriptive input for one or more descriptive categories. The number of descriptive categories defined by the scorer may be predetermined or specified in the ST application 700, or may be left to the scorer. As shown in the summary player detail view 708 depicted in FIG. 7E, the scorer has also entered "black" for Vincent Johnson's second descriptive category (player pants) in a manner similar to that described above with respect to FIGS. 7B-7D. FIG. 7E also shows that the scorer has entered descriptive characteristics for two descriptive categories (player pants, player cap) for Mahindra Latchman and one descriptive category (player shirt) for Jared Garcia.

[0249] The ST application 700 may include a scoring function that allows the scorer to input multiple details about the play, including club type, shot location, strokes, penalties, scoring, lie, etc.

[0250] Referring to FIG. 7F , in some embodiments, the ST application 700 may be configured to generate a club selection feature on the user interface that a scorer can use to identify the club a player is currently using to strike the golf ball and / or set up during play. For example, on a group screen 710, the scorer may select a “Club Selection” button 709 associated with the player. For example, while on the tee, the scorer may select the “Club Selection” button 709 and be presented with a club selection 711, as depicted in FIG. 7G . The club selection may include any number of clubs, such as the player's entire bag or an exhaustive list of potential clubs. In one embodiment, the club selection is programmed to correspond to clubs the player is likely to use at a particular location on the course. For example, using the location of a companion device and / or a tracking module carried by the player, the ST application 700 can determine a club selection to present that corresponds to what the player will use in that or similar situation and / or location on the course. In some embodiments, the location and / or situation may include, for example, a zone determination, as described with respect to FIG. 3 . For example, the location system may determine the location of the tracking module from location data provided to the location system, where the location coordinates are applied to predefined coordinate ranges corresponding to defined zones to determine in which zone the tracking module is currently located. In FIG. 7G, the scorer selects the "Iron" button, indicating that the player is teeing off with an iron on the par-3 second hole. In one embodiment, the companion device 12 will not respond to the selection of a player name unless the scorer first enters a club. Club selection can occur before the player arrives at the ball and / or before the player hits the ball. While it is preferable for the scorer to enter the club before the player hits the ball, in some embodiments, club selection may be entered after the player hits the ball.

[0251] The companion device 12 running the ST application 700 may be configured to receive input from the player accurately hitting the ball. In some embodiments, a "Shot Hit" button 712 may be provided that the scorer can tap at the exact moment the player hits the ball. To display the "Shot Hit" button 712, the scorer can select the name of the player to indicate the "Shot Hit" from the group screen 710 ( FIG. 7F ). Referring to FIG. 7H , the user interface includes the "Shot Hit" button 712, which the scorer uses to indicate the shot by holding down their finger on the button before the ball is hit and releasing their finger the instant the ball stops moving. For example, when the player addresses the ball and is ready to take the shot, the scorer holds down the "Shot Hit" button 712. Then, at the exact moment the player hits the shot, the scorer releases the button to indicate the shot has been hit. This action signals the system to record the location of the tracking module at that instant, which corresponds to the player's location. This location information may also be associated with the player's club selection. This data may be stored in the tracking module, companion device, or associated memory, or may be transmitted to the managing device immediately when the scorer indicates that a player or group has completed a hole, or periodically, at scheduled intervals, based on the proximity of the tracking module or companion device to the managing device, or based on its storage capacity. As described in more detail elsewhere herein, the location information may be input to an application configured to render a graphical display of a digital stroke trail detailing the shots taken in the round.

[0252] In some embodiments, when the scorer releases the "Shot Hit" button 712, the scorer will then input the ball's landing location relative to the golf course (e.g., fairway, rough, green, out of bounds, sand, hazard, ground under repair, cart path, hole). The companion device 12 may be configured to automatically display location options when the scorer releases the "Shot Hit" button 712, or the user interface may provide location buttons that the scorer can use to select from multiple locations or to enter a location in a provided field. In the embodiment shown in FIG. 7I, when the "Shot Hit" button 712 is released, the user interface displays an "In Hole" prompt 713, allowing the scorer to indicate whether the ball is in the hole or not. As shown, the interface for the In Hole prompt 713 requires a directional swipe, with left being "No" and right being "Yes." However, other interface buttons or methods may be used. 7J, after the scorer indicates whether the ball went into the hole, the user interface may return to the group screen 710 displaying the recorded shots. The group screen 710 may also include a notification or indicator 714 indicating that a player is currently playing a hole. As shown, the text below the player's name has changed to "Starting Location," indicating that the player is between shots on the hole. This indicator 714 may also act as a button to trigger the tracking module to collect location information when the player takes their next shot, in a manner similar to that described for the first shot.

[0253] 7K and 7L, to record a player's second shot, the scorer may select a "Starting Location Button" 715 within indicator 714 from group screen 710. This selection may present a "Starting Location" screen 716 containing multiple locations the scorer can select to indicate where the player is hitting their shot. As shown, the scorer may select fairway bunker, fairway, first cut, natural area, deep rough, pond, greenside bunker, fringe, other, or green. Because the player has not yet hit their first shot, the option to select "Tee" is unavailable in this embodiment. However, selecting "Provisional" or "Penalty Drop" allows the player to select "Tee."

[0254] In some embodiments, the course may be mapped before or after play, and the recorded location positions of the tracking modules corresponding to the player and ball may be overlaid on a map, or the STTM system may determine a relative location to the golf course based on the recorded positions relative to the map. The course may be mapped using any coordinate or grid system and may utilize surveying techniques, global satellite communication systems (GPS, GLONASS, BEIDOU, GALILEO & QZSS), LIDAR, or other suitable methodologies. The recorded location information may be collected or converted to such coordinate or grid systems, directly or indirectly, and / or utilize overlay techniques.

[0255] After entering the starting location on the "Starting Location" screen 716, the user interface may display the group screen 710. As shown in Figures 7M and 7N, the location indicator 714 may change to the scorer's selection, e.g., the fairway. The scorer then selects a player name and displays a "Shot Hit" button, which allows the scorer to indicate the moment the ball was hit by the player and then whether the ball went into the hole, e.g., in a manner similar to that described above.

[0256] Recording the time and location of each player's putt can be done in a similar manner as described above for other shots. In various embodiments, when the ball reaches the green and the scorer selects "Green" from the "Starting Location" screen, the location indicator 714 on the group screen 710 may remain at "Green" until the ball is holed. In another embodiment, the user interface may allow the user to select a different location after a subsequent shot that may not be holed and, for example, roll off the green. FIG. 7O shows the group page 710 with the first two players holed and a third player on the green. When it is the third player's turn to putt, the scorer can select the player's name, press and hold the displayed "Shot Hit" button as the player is about to putt, and release it when the player putts the ball, recording the time and location of the putt via the location of the tracking module as described with respect to FIG. 7H. The user interface may then display an "In Hole" prompt that the scorer can use to record whether the ball was holed, which may be similar to that described with respect to FIG. 7I. If the ball is not holed, the scorer records the next putt as before. If the ball goes into the hole, the ST application 700 records the player as having completed the hole, and the scoring process begins again from the next tee box. In one example, after the scorer records that all players in the group have their balls in the hole, a location indicator 714 on the group is displayed. The location indicator 714 on the group page 710 may automatically return to "Select Club." In another example, the user interface may indicate to the scorer that the hole is complete and prompt them to move on to the next hole.

[0257] 7P-7V illustrate PDP scoring according to various embodiments. In these examples, the scorer records in a "Starting Location" screen 716 the "starting location" where the next shot will be hit, rather than where the original shot landed. However, in some embodiments, the ST application 700 or system may additionally provide for input of the landing location of the previous shot by entering it into a text field, by selecting from a list of areas around the hole, such as "ponds," provided on the "Starting Location" screen 716, or by displaying a map and allowing the scorer to indicate the ball's landing location on the screen.

[0258] 7P illustrates recording a second shot from a tee that was recorded as provisional. Using the "Starting Location" screen 716, the scorer selects "Provisional" and then selects the starting location, which in this example is "Tee." The display then returns to the group screen 710, with "Provisional" displayed as the location indicator. The scorer can then select the player's name and score the shot as described above.

[0259] Referring to FIG. 7Q, once a provisional shot is recorded, "Tentative" may remain in the position indicator 714 below the player's name until the scorer selects the player's name to record the position of the next shot. FIG. 7R shows a prompt 720 that appears after selecting a player's name, requesting the scorer to indicate whether the player is using a provisional shot. If the scorer indicates that the player is not using a provisional shot, scoring proceeds normally. If the scorer indicates that the player is using a provisional shot, a penalty stroke is awarded and displayed on the group screen 710, as shown in FIG. 7S.

[0260] FIG. 7T illustrates recording a penalty drop. In some embodiments, when recording a penalty drop, the ST application 700 prompts the scorer to indicate that the ball for the penalty drop is in play. For example, from the "Starting Location" screen 716, the scorer selects "Penalty Drop" and then selects a starting location, which in this example is "Deep Rough." The display then returns to the group screen 710, as in FIG. 7U, with "Penalty Drop" displayed as a location indicator 714 below the player's name. The scorer can then select a player's name before the player drops the ball. For example, referring to FIG. 7V, the scorer is presented with a penalty drop prompt 721 that provides a "Ball in Play" button 722 that the scorer uses to indicate when the player drops or retakes the ball. This allows the penalty stroke to be assessed, and the location and time of the shot continue to be recorded as described above.

[0261] Free drops can be recorded in a similar manner to recording penalty drops, except that "Penalty Drops" is selected from the "Starting Location" screen and no penalties are accessed.

[0262] 8A-8G, in various embodiments, the STTM system includes a data management system 50 configured to review and edit scoring data recorded by the score tracking system. The data management system 50 can provide data administrators with data access locally, remotely, and / or for management operations from any location via a management device.

[0263] The data management system 50 may include a data management tool 800 including interface, display, or related operational elements selected from one or more elements, such as (a) an event selector 801, (b) a round selector 802, (c) a course selector 803, (d) an edit mode notification 804, (e) a data discrepancy panel 805, (f) a hole graphic display 806, (g) a group scorecard 807, (h) team player stroke details 808, or (i) a full group presentation 809. FIG. 8A illustrates an exemplary user interface of a data management tool 800 for use with the data management system 50 that provides the above-listed elements in presentation blocks. In various embodiments, the page layout of elements is configured to allow connections to be created between blocks and / or data elements therein. For example, selecting an element in a block may establish a connection to other blocks. In a further example, the other blocks to which connections have been established may be updated with the appropriate presentation, as described in more detail below. However, it will be understood that the elements operable to provide operation of data management system 50 and associated components and its data may be provided in many formats, and the present disclosure is not limited to the particular arrangements and combinations of elements and user interface components depicted herein.

[0264] The event selector 801 may include a selectable list of one or more events available for viewing and managing associated data. In one example, the event selector 801 includes a drop-down list of all events available for viewing. Selection of an event causes or is operable to cause a presentation block to present associated data for that event.

[0265] The round selector 802 may include a selectable list of one or more rounds of an event available for viewing and managing associated data. In one example, the round selector 802 comprises a drop-down list of all available rounds of the event selected with respect to the event selector component. In a further example, selecting a round causes or is operable to cause the presentation block to present data for the round of the selected event. In a further example, the round selector 802 and / or the presentation block may default to the most recent round in progress. If no round is in progress, the default may be the earliest round having a "grouped official" round status, as described in more detail with respect to the round management system 60.

[0266] The course selector 803 may include a selectable list of one or more courses available for viewing and managing associated data for a selected event and round. In one example, the course selector 803 comprises a drop-down list of all courses available for the selected event and round. Selecting a course may cause the presentation block to present or be operable to present data for the course for the selected event and round. In one example, if multiple courses are being played in the event and round, a default course may be set to the host course. In another or further example, the course selector 803 may include a selectable option for selecting all courses. In one such example, selecting all courses causes data for all courses in the presentation block to be presented in a single combined presentation.

[0267] The edit mode notification 804 may include display elements that constitute a notification that is presented when edits are made in any of the presentation blocks in which scoring data is edited. The edit mode notification 804 may be selectively programmable to provide a notification for any desired edits. For example, in some embodiments, no notification is displayed if changes are made only to the play management blocks described below. In one example, a notification is output when a data element value is above or below a predefined threshold, or within or outside a predefined range. The notification may be interactive, such that the user can interact with the notification and accept the changes, such as by selecting all or part of the notification. In one embodiment, a separate interface element is provided that the user can interact with to accept the changes. In some configurations, the notification may be operable to display or present a summary or identification of the change that caused the notification.

[0268] In various embodiments, when a user changes or enters data in a presentation block, the data management tool 800 may automatically enter edit mode. While in edit mode, data may not be transmitted to downstream clients or their data viewing platforms. However, once the user accepts all current edits, edit mode may be turned off and data, including changes made during edit mode, may be transmitted to downstream clients, including their data viewing platforms.

[0269] The hole graphic display 806 may be provided in 2D graphics (although more advanced graphics, such as 3D, may also be used). The hole graphic display 806 may include various navigation features. For example, the hole graphic display 806 may include one or more of a zoom feature that allows a user to selectively zoom in and out on the graphic, a graphic rotation feature that allows a user to selectively rotate the graphic on a horizontal, vertical, and / or other axis, and / or a variable centering feature that allows a user to move the center of the graphic within a presentation panel. In one example of a zoom feature, a quick zoom is provided to zoom in on the green and zoom out to view the entire hole and / or zoom out to view the entire course. In one example, the graphic is oriented in a manner that allows maximum visibility from tee to green, such as an overhead view, tee view, or green view. The hole graphic display may include various display distances for the hole. For example, one or both of the scorecard yardage distances or the actual yardage distances between the tee and the pin set for the round may be displayed. In one configuration, hole setup information may be displayed on the hole graphic. For example, current hole information may be displayed for each round, such as one or more of the tee locations, pin locations, and / or fairway center points for holes on the course. In one embodiment, the graphical display may be configured to display all players in a group at once upon request from a user, for example, via interaction with a "Show all group players" element.

[0270] Stroke or ball location coordinates, such as those collected through operation of the tracking module and companion device, may be plotted on a hole graphical display 806. For example, the hole graphical display 806 may include a plot of the ball location relative to the hole. For example, the ball location may be plotted on the graphical display to indicate the ending locations of team players' strokes. For consecutive strokes that include location coordinates, lines may be displayed between the plotted points to depict the stroke trajectory. Since the starting point is the tee and the ending point is the pin, the data management tool 800 may generate lines from these points to the coordinates of the player's stroke on the hole or stroke with the ending point. In one example, the plotted ball location distance from the tee, distance from the last stroke, and / or distance to the pin may be displayed or provided as defined, selectable formatting options.

[0271] Additional functionality may be provided for managing stroke coordinates, such as allowing the user to enter the location of a received stroke, move an existing location assigned to a stroke, create a stroke along with its location, display all GPS or other location coordinates collected for team players, and / or delete a stroke along with its location, etc. In one example of the functionality described above where breadcrumbs are present, hole graphical display 806 may be configured to allow the user to "lock" a stroke to the breadcrumb.

[0272] In one embodiment, the functionality includes displaying all GPS and / or other coordinates collected for team players, including those not related to strokes, e.g., breadcrumbs. By displaying all coordinates, the hole graphic display 806 can be configured to associate a location with a player's stroke.

[0273] In various embodiments, selecting a group from the full group presentation 809 may cause the group scorecard 807 to be populated with data related to the group. In one example, the hole graphical display 806 may similarly populate with shot and / or ball location data related to the group. In one example, selecting a particular hole for a group via the group scorecard 807 causes the hole graphical display 806 to zoom to the selected hole and display plotted ball positions and shot trajectories of the team players in the group.

[0274] 8B shows an example interface 810 for a group scorecard 807 presented by or accessible through interaction with the group scorecard data management tool 800, all or a portion of which may be available in each presentation block view. Various elements of the group scorecard 807 may be viewable and / or editable through the operations and functionality of the group scorecard 807, as described in detail below with respect to each element. The group scorecard 807 may include various data elements such as one or more of: (a) team player names 811, (b) stroke events 812, (c) stroke count 813, (d) total 814, (e) total 815, (f) today 816, (g) front 9 holes by hole score 817, (h) score out 818, (i) back 9 holes by hole score 819, (j) score in 820, (k) stroke total, or (l) strokes official 821.

[0275] Team player names 811 may list the team players in a group. For example, players may be presented by last name, first name. In one configuration, team player names 811 may not be edited via the group scorecard component of data management tool 800.

[0276] Stroke event 812, if flagged, may represent the last stroke event received from a score tracking system or, in one example, a verification system. Various stroke events may be represented, such as club selection, address to ball, shot hit, provisional, preliminary, final, in hole, etc. In one configuration, stroke event 812 may not be edited via the group scorecard component of data management tool 800.

[0277] The stroke count 813 may represent the strokes currently recorded for the hole the player is on. If a team player has not started the round, the stroke count may default to display the starting tee time. In one configuration, the stroke count 813 may not be edited via the group scorecard component of the data management tool 800.

[0278] The total 814 may present the total par relative score for the event. In one configuration, the total 814 may not be directly edited via the group scorecard component of the data management tool 800.

[0279] Today 815 may present a par relative score for that round. In one configuration, Today 815 may not be edited via the Group Scorecard component of the data management tool.

[0280] The front 9 holes by hole score 816 may present a list of the scores for each hole of the first 9 holes. In some embodiments, depending on the configuration, column or row headers may be provided to indicate the hole number for greater clarity. In one configuration, the front 9 holes by hole score 816 may be edited via the group scorecard component of the administration tool 800 by entering an integer or deleting a score from the hole score field.

[0281] The scoreout 817 may present the stroke totals of the scores entered on the front nine. In one configuration, the scoreout 817 may not be edited directly via the group scorecard component of the data management tool 800.

[0282] Back 9 holes by hole score 818 may present a list of scores for each hole in the back 9 holes. In some embodiments, depending on the configuration, column or row headers may be provided to indicate the hole number to improve clarity. In one configuration, back 9 holes by hole score 818 may be configured to be edited via the group scorecard component of administration tool 800 by entering an integer or deleting a score from the hole score field.

[0283] Score In 819 may present the stroke total of the score entered on the back nine. In one configuration, the score in 819 may not be edited directly via the group scorecard component of data management tool 800.

[0284] Stroke total 820 may display the stroke total for the round. In one example, stroke total 820 may only be displayed if data has been entered in score out 817 and score in 819. In one configuration, score total 820 may not be edited directly via the group scorecard component of data management tool 800.

[0285] Official Strokes 821 may present the strokes received for team players on all holes flagged as official. In one configuration, this element may be edited by the user to indicate that no further edits should be made to any strokes on any hole for the player.

[0286] FIG. 8C illustrates an exemplary interface for team player stroke details 808 of data management tool 800, configured to interface its operation to a user. The interface is presented or accessible through interaction with the team player stroke details 808 element of the respective presentation block view of FIG. 8A. The team player stroke details 808 elements may be displayed. In operation of team player stroke details 808, a user may edit various elements. In some embodiments, selecting a player in the group scorecard 807 or full group presentation 809 populates the team player stroke details 808 interface with the respective data elements for the selected group.

[0287] When selecting a team player for presentation and / or stroke editing using team player stroke details 808, hole graphical display 806 may default to display the course view, current hole, next hole, first hole completed, last hole completed, or full course view. In one embodiment, by selecting a particular hole from group scorecard 807, e.g., selecting a hole from the front 9 holes by hole 816 or front 9 holes by hole 818 ( FIG. 8B ) data element view, team player stroke details 808 presents the player's stroke details for the particular hole. In this manner, data management tool 800 may be configured to allow a user to selectively view strokes by hole using group scorecard 807 or view stroke details for a hole via interaction with team player stroke details 808.

[0288] In one example, hole graphic display 806 presents a representation of a hole by viewing team player stroke details for the hole via team player stroke details 808. The graphic may be oriented from left to right, with the tee location on the left and the green on the right. Functionality such as zooming in and out of the graphic may be provided, as described above. As an example, a quick zoom operator may be provided to allow a user to quickly zoom to various areas of the hole, such as the tee box, fairway, hazards, green area, or a specific selected shot. Functionality may also include moving the graphic to change the longitude and latitude of the view within a static display area, e.g., within any zoom value. Yardage may also be displayed relative to the tee and pin setup locations. Other yardages may be selectively displayed within or relative to the graphic, as described above.

[0289] The data elements of team player stroke details 808 may include various informational and scoring data elements, such as one or more of: (a) team player name 822, (b) stroke number 823, (c) stroke accessed 824, (d) stroke event 825, (e) timestamp 826, (f) stroke type 827, (g) location 828, (h) club 829, (i) provisional 830, or (j) in hole 831. The data elements may correspond to those collected by the ST application via operation of the companion device described herein. Such data elements may be received by data management system 50 for viewing and / or editing.

[0290] Team player names 822 may include a list of all team players in a group. For example, selecting a group from the all group presentation 809 or group scorecard 807 may populate team player names 822 with the team players for that group. The presentation may display data about a single player, which may default to any player, such as the last player to have a stroke event recorded or complete a hole, the first player in a predefined order of teeing off, etc. In one configuration, team player names 822 may not be edited via team player stroke details 808.

[0291] The stroke number 823 can correspond to the received stroke. In one configuration, the stroke number 823 is editable via the team player stroke details 808, allowing the user to enter an integer number.

[0292] The accessed strokes 824 may correspond to the number of strokes that will be counted in the hole score of the team player who received the stroke. In one configuration, the accessed strokes 824 may be editable via the team player's stroke details 808, allowing the user to enter an integer number, for example.

[0293] In one embodiment, a user can create strokes before or after other strokes. When a stroke is created, the data management tool 800 may be configured to automatically set the stroke number as the number after the previous stroke. If a stroke is created between two other strokes, the other strokes following the created stroke may be automatically renumbered, starting from the created stroke. The data management tool 800 may also edit the timestamp 826 to set it to either the time after the previous stroke or the time before the upcoming stroke. In one example, when a stroke is created, the default stroke accessed is 1.

[0294] In one embodiment, a user can delete strokes. When a stroke is deleted, the data management tool 800 may be configured to automatically renumber the remaining strokes sequentially. If a stroke is deleted and it is not a stroke within the flagged hole 831 but is a stroke with an available “in hole” flag, the data management tool 800 may recalculate the score with a new total of accessed strokes. When a stroke with an “in hole” flag is deleted, the data management tool 800 may be configured to clear the calculated score. As described below, the “in hole” flag may be set or cleared by the user. After deleting a stroke with an “in hole” flag, the user can set the “in hole” flag for another stroke for which a revised score will be calculated by the data management tool 800. In one example, upon deletion of a stroke flagged as “in hole,” the user may be prompted to flag a stroke with an “in hole” flag.

[0295] The stroke event 825 may correspond to the most recent stroke event received. The stroke event 825 may allow a user to identify the stroke event. Thus, in one configuration, the stroke event 825 is editable via the team player stroke details 808. Editable options may be provided, and the editable options may include one or more event types selected from club selection, address to ball, shot hit, preliminary, final, or in-hole, corresponding to such events collected by the ST application via the companion device and tracking module.

[0296] The timestamp 826 can correspond to that of the stroke event 825, such as the most recent stroke event 825. In one configuration, the timestamp is editable via the team player stroke details 808, allowing the user to edit the fields in the form of hour and day inputs.

[0297] Stroke type 827 may correspond to a stroke type identifier, such as stroke, penalty, or drop, corresponding to such stroke type collected by the ST application via the companion device. In one configuration, stroke type 827 is editable by data management tool 800 to change or add stroke types from a list. In one example, interacting with stroke type 827 displays a dropdown containing a list of available stroke types, allowing the user to select one of the stroke types to configure. In various embodiments, data management tool 800 may automatically apply various rules to editing stroke types. For example, if the created stroke type is “drop,” the accessed stroke 824 may be zero. If the created stroke type is “drop,” the stroke number 823 may be the same as the previous stroke or penalty type. If the created stroke type is “penalty,” the accessed stroke 824 may default to one. If the created stroke type is “penalty,” the stroke number 823 may increment by the amount identified for the accessed stroke 824.

[0298] Location 828 may correspond to the graphical location of the stroke as determined by a location methodology described herein, such as a tracking module, a location system, manual input via operation of a rangefinder, indication of the ball's location against a displayed map, or other location methodology used by the STTM scoring system. In one configuration, location 828 is editable to change the location from an available list of location descriptions of the golf course being played, such as tee box, fairway, rough, first cut, hazard, pond, out of bounds, green, etc. In one example, interacting with the location data element may display a dropdown containing a list of available locations on the golf course that can be set to the location.

[0299] Provisional 830 can be used to identify whether the stroke is provisional or not. In one configuration, the Provisional field is editable with a "Yes" or "No" value option as to whether the stroke is a provisional stroke.

[0300] In Hole 831 is used to identify whether a specified stroke resulted in the ball being in the hole. In one configuration, a user can set or remove a flag when a stroke is considered in the hole. The data management tool 800 may automatically apply various rules to the "in hole" flag. For example, if the last stroke with the highest stroke number is flagged as "in hole," a score may be calculated and stored based on the sum of all strokes accessed. If a non-last stroke with the highest stroke number is flagged as "in hole," that stroke is set as the highest stroke number, and all other strokes are renumbered sequentially.

[0301] Referring to FIG. 8D , in various embodiments, a stroke event review viewer 832 may be provided. For example, each stroke in the player's stroke details 808 may be operable to optionally expand to display additional associated stroke events. In the illustrated viewer, stroke events for a stroke are entered in the stroke events 823 element. As shown, stroke events for a stroke number include club selection, address, shot hit, preliminary, and final. Thus, the stroke resulted in the player not holding the ball. In various embodiments, stroke details received from a companion device are marked as "preliminary" and are subject to review via operation of the data management tool 800 or a verification system, described below. If the review is successful, the stroke details can be set to "final." In one configuration, fields in the stroke event review viewer 832 are not editable, except for the timestamp field. The stroke event review viewer 832 may be configured to allow a user to reorder or rearrange stroke events. The stroke event review viewer 832 may be configured to allow a user to collapse the review of stroke events, such as to present only the most recent stroke event.

[0302] 8E illustrates an exemplary interface for the full group presentation 806 of the data management tool 800, configured to interface with a user and its operation. All or a portion of the interface may be presented in the respective presentation block views of FIG. 8A or may be accessible through interaction with the full group presentation 806 provided therein. Various elements of the interface may be viewable and / or editable through operation of the full group presentation 806.

[0303] The all group presentation 809 may be configured to display a selected round or may include displaying only the selected round. In one example, the all group presentation 809 is configured to display information for a selected course, or, if selected, all courses in the tournament. In some configurations, the display may be scrollable and / or each column of data may be sorted in either ascending or descending order based on the information available in the column. In some configurations, none of the fields in the all group presentation 809 may be directly edited via the all group presentation 809. In one embodiment, the presentation of the all group presentation 809 may include a notification regarding the names of team players if their scorecards are flagged as “official,” for example, via a verification system described in more detail elsewhere herein.

[0304] The full group presentation 809 includes: (a) group number 832—corresponding to the number assigned to the group; (b) course 833—corresponding to the course the group number is playing; (c) starting hole 834—corresponding to the first hole the group started on based on their grouping for the round; (d) tee time 835—corresponding to the group's starting tee time; (e) rank 836—corresponding to the player's projected position in the progression of play during the ongoing round; and (f) team player name 837. (g) Total 838 - corresponds to the current par relative score total for the event; (h) Today 839 - corresponds to the par relative score for the round; (i) Front 9 Holes by Hole Score 840 - corresponds to a listing of the scores by hole for the first 9 holes; (j) Score Out 841 - corresponds to the stroke totals for the scores entered for the front 9; (k) Back 9 Holes by Hole Score 842 - corresponds to a listing of the scores by hole for the back 9 holes; (l) Score In 843 - corresponds to the stroke totals for the scores entered for the back 9; or (m) Stroke Total 844 - corresponds to the stroke total for the round and is displayed if Score Out 841 and Score In 843 data are available.

[0305] 8F illustrates an example interface for a data mismatch panel 805 of the data management tool 800, which is configured to interface its operation to a user. All or a portion of the interface may be presented in the respective presentation block diagram of FIG. 8A or may be accessible through interaction with the data mismatch panel component provided therein. Various elements of the interface may be viewable and / or editable through operation of the data mismatch panel 805.

[0306] The data mismatch panel 805 can include two sub-elements: an error message panel 850 and a warning message panel 851. In one embodiment, the sub-elements can be configured to function independently.

[0307] In various embodiments, the data discrepancy panel 805 can be manipulated to improve user experience and efficiency. For example, rows of data may be scrollable. Also, columns of data may be sortable in either ascending or descending order based on the information available in the column. In one configuration, the data discrepancy panel 805 can provide interface elements operable to flag warnings as reviewed and remove warnings from the presentation. In one example, the data discrepancy panel 805 can allow a user to review all warnings flagged as reviewed, review errors and warnings by group, hole, or team player, reset and display all errors and warnings if any were set as reviewed and removed, scroll through all messages by panel if some messages cannot be displayed in the initial view, or turn rules on or off for all or selected error and / or warning message rules. In one example, none of the fields may be editable.

[0308] In various embodiments, the error and warning messages 853 and 854 may identify various identifying elements regarding the player, time, and / or location to which the message pertains. In the illustrated embodiment, the following data elements are presented: team player name 855, hole number 856, and group number 857. The data management tool 800 may be configured to analyze the scoring and / or location data and associated procedures and automatically generate error and / or warning messages 853, 854 when anomalies are identified.

[0309] Error messages 853 relate to missing data and / or procedural anomalies regarding the recorded score and / or location data and are displayed in the error message 853 element associated with the identification information. Various error messages may include, for example, one or more of missing location information, missing stroke coordinates, missing scores (e.g., missing scores that may appear when there is a gap in the score between holes), total accessed strokes does not match recorded score, score recorded but missing strokes, provisionally flagged stroke with no penalty recorded and accessed stroke equal to 1, timestamps of stroke trajectory from hole to hole not consecutive, first stroke not from tee position, stroke not flagged final after next stroke taken, and team player not officially marked for stroke after team player completes round.

[0310] The warning message 854 may relate to an event or lack thereof detected by the data management tool 800 that may not yet be an error or cannot yet be confirmed to be an error based on available data, but is anomalous compared to the expected behavior of a scoring system, which may include a location system. The warning message 854 may be displayed with associated identifying information. Various warning messages 854 may be included, such as one or more of the following: one or more of the tracked players being out of sync with the strokes of other team players in the group; multiple consecutive drops by a team player; a drop without a penalty in a team player's stroke path; stroke coordinates not closer to the pin location than the coordinates of the previous stroke; a gap of more than 10 minutes between team player strokes; multiple strokes including positions from the tee; an atypical score for a team player, such as a double bogey, a worst, or an eagle or better; five minutes have passed but no coordinates have been received for a stroke; a team player is on the green but appears to be off the green; a driving distance outside the normal range of distances for a par 4 or par 5, such as less than 180 yards or more than 380 yards; a stroke flagged as being on a hole that is 30 yards or more distant; the pin not being set and a team player stroke being received on the hole; or the tee not being set and a team player stroke being received on the hole.

[0311] 8G, in various embodiments, the presentation blocks and / or one or more associated components thereof of the data management tool 800 described above with respect to FIGS. 8A-8F may be configured to create connections therebetween. For example, a presentation block layout may be configured to create connections between block views of component elements. For example, when selecting or otherwise interacting with, e.g., making a selection, an element in one block view, e.g., with respect to an associated element, a connection is established to one or more other blocks, thereby updating the appropriate presentation within the respective blocks.

[0312] The presentation block may be configured to apply connectivity rules for the entire group presentation 809. In one embodiment, selecting a team player's name causes the group scorecard 807 to present the group to which the team player belongs, the hole graphical display 807 to present the current hole that the team player has not completed, the team player stroke details 808 to present the strokes taken on the current hole that the team player has not completed, and the data discrepancy panel 805 to present all errors and warnings for the selected team player on all holes. In the above or another embodiment, selecting a group number may cause the group scorecard 807 to present the selected group, the hole graphical display 806 to present the current hole and default to the top team player in the group and the current hole that the team player has not completed, the team player stroke details 808 to display the strokes taken on the current hole that the top team player in the group has not completed, or the data discrepancy panel 805 to present all errors and warnings for the selected group. In any of the above or other embodiments, selecting a hole for a team player may cause the group scorecard 807 to present the group to which the team player belongs, the hole graphical display 806 to present the selected team player and the selected hole, the team player stroke details 808 to present the strokes taken on the selected hole and team player, or the data discrepancy panel 805 to present all errors and warnings for that hole and team player, which may include warnings that have been flagged as reviewed.

[0313] In any one of the above embodiments or in another embodiment, interaction with the group scorecard 807 may result in connectivity with one or more other components of the data management system 50. For example, selecting a team player's name may cause one or more of the following: hole graphical display 806 presents the current hole that the team player has not completed; team player stroke details 808 presents the strokes taken on the current hole that the team player has not completed; data discrepancy panel 805 presents all errors and warnings for the selected team player on all holes; or full group presentation 809 presents the group or team player at the top of the presentation. In yet another example, selecting a team player's hole may cause the hole graphical display 806 to present the selected team player and the selected hole; team player stroke details 808 presents the strokes taken on the selected hole and team player; data discrepancy panel 805 presents all errors and warnings for that hole and team player, which may include warnings flagged as reviewed; or full group presentation 809 presents the group or team player at the top of the presentation.

[0314] In any one of the above embodiments or another embodiment, a team player's interaction with stroke details 808 may cause a connection with one or more other components of data management system 50. For example, selecting a stroke may present location coordinates within hole graphical display 806 for the stroke, if coordinates exist.

[0315] In any one of the above embodiments or other embodiments, interaction with the hole graphic display 806 may cause a connection with one or more other components of the data management system 50. For example, selecting a location coordinate assigned to a stroke may cause the selected stroke to be highlighted in the team player stroke details component.

[0316] In any one of the above embodiments or in another embodiment, interaction with the data discrepancy panel 805 may result in a connection with one or more other elements of the data management system 50. For example, selecting an error or warning to review may update the presentation of the group scorecard 807 based on the team player and group identified in the error or warning message. In another or further example, selecting an error or warning to review may update the presentation of the hole graphic display 806 and / or the team player stroke details 808 based on the team player identified in the error or warning message.

[0317] In various embodiments, the STTM system includes a verification system 70 configured to provide streamlined verification of a player's official scorecard against scores collected by the score tracking system. The verification system 70 may be configured to allow a user to make changes to scores resulting from operation of the score tracking system, if desired. Using the verification system 70, a user can also quickly identify that a scorecard has been reviewed and flagged as official. In some embodiments, this official designation can be transmitted or otherwise immediately available on one or more data platforms to inform users of the scoring data that no further score edits will be received for the respective player. In one example, the flagging of a scorecard as official is retained for storage in a database, later distribution, internal verification, compilation with additional verified scorecards, analysis, or a combination thereof.

[0318] The verification system 70 may be configured for operation in various network environments as identified herein with respect to its various STTM systems / subsystems. For example, the verification system 70 may be configured to operate in a local, remote, or distributed network-based environment. The verification system 70 may be configured to operate in a web-based, cloud-based, or other suitable network environment. In one embodiment, the verification system 70 may operate within a browser or browser-like environment. For example, the verification system 70 may include a verification application capable of running on multiple browser tabs with different settings. In a further example, the verification system 70 includes an edit tracking feature whereby the verification system 70 tracks edits made by users. These user edits are tracked as associated with the particular user who made the edits. The verification system's tracking feature may be configured to store tracked edits by user and to allow the tracked edits to be reviewed. For example, a reviewing user may access the verification system 70, view a list of users, and review details regarding the edits each user made to the scorecard. In some configurations, the verification system 70 may allow the reviewing user to view users' edits by type, such as score, stroke, location, stroke type (drop, shot, penalty), etc. In this or another configuration, the verification system 70 may be configured to allow a reviewing user to view one or more types of edits by one, more, or all users within a particular time period or event.

[0319] 9A-9B, in one embodiment, the verification system 70 may be configured to generate two functional verification tools for scorecard verification. Each verification tool may be provided in one or more tabs, screens, pages, windows, or any suitable displayable arrangement having the functionality described herein. The verification tools may be displayed in whole or in part separately or together. In one example, a first tool panel may be configured to input scoring data from a player's scorecard and compare it with a second score collection methodology, such as an automatic or semi-automatic scoring methodology. The operation of the first tool may be referred to herein as blind verification. The second score collection methodology according to various embodiments is described below with reference to a tracking system methodology, but it will be understood that variations of this score collection methodology or other score collection methodologies may be similarly applied to the operation of the verification system. Thus, the first verification tool may be configured for blind verification, allowing a user to input scores from a player's scorecard, which are then automatically compared with scoring data recorded by the score tracking system. The second validation tool may output the overall scores of players in a particular group, all groups, all players, or any desired combination thereof, along with the player rankings. In various embodiments, the validation tools may be located in selectable tabs, with each tab including a validation tool within a panel.

[0320] FIG. 9A shows an example of a first verification tool 901 configured for blind verification.

[0321] An event selector 902 may be provided to allow a user to select an event that the verification system 50 will use to verify a player's scorecard. The event selector 902 may include a list of selectable events. Interfacing with the event selector 902 may invoke a dropdown, list, or other selectable form of event for selection.

[0322] A round selector 903 can be provided to allow a user to select a round that the verification system will use to verify a player's scorecard. In some embodiments, selection of an event may be a prerequisite for round selection. For example, if the event is static, known, or not otherwise entered, the verification tool 901 may not allow the user to interact with the round selector 903. Interaction with the round selector 903 may present available rounds of the event for selection in a manner similar to that described with respect to the event selector 902. In one example, after a user selects an event, the verification tool 901 generates a selectable list of available rounds of the event in the event selector 902.

[0323] A cutline 904 may be provided so that the user can view a display of current, real-time cut data. In some embodiments, the cutline 904 is displayed only if the selected round is a cut round. Viewing the cutline 904 can provide the user with insight into what changes may be made to the cut. For example, changing one player's score may cause multiple other players to make or miss the cut.

[0324] A group selector 905 can be provided to allow the user to select a group containing the player for scorecard verification.

[0325] A player selector 906 may be provided that includes a list of selectable players within a selected group. In one embodiment, the player selector 906 is provided without the group selector 905, and a list of participating players is provided from which the user can select.

[0326] The name of the player currently being reviewed for scorecard verification may be displayed in the Player Name 907 field. In some configurations, an image, such as a headshot of the player, may also be displayed.

[0327] A score entry may be provided for entering a player's score from the player's scorecard. The score entry may include a hole field 910, such as an 18-hole field, for entering scores for all holes in a round. The hole field 910 may be configured for manual entry. In one example, the hole field 910 includes a drop-down, toggle field, or other suitable entry method for each hole with selectable scores. In the illustrated embodiment, the score entry includes hole fields 910 that require the user to make each field available for entry, for example, using the enter key or tab to select the hole field 910 with mouse navigation. As described below, scores recorded by the score tracking system and received by the verification system 70 may be absent or otherwise hidden from view so that manual score entry and subsequent comparison with the score tracking system scores are blind from the user's perspective.

[0328] System-received scores, such as scores received from a score tracking system, can be imported into the verification system 70. In some embodiments, importing of score tracking system scores may occur automatically upon receipt of the scores or may occur after a delay. Score data and associated player data may be imported into the verification system after each hole is completed, periodically, after a predetermined number of holes, upon receipt, or when a player or group completes a round, which may be indicated by a scorer via a companion device. For example, when a scorer indicates that a player or group has completed a hole or round, the calculated score and the player name or player number associated with the data may be transmitted directly or indirectly to the verification system. In the illustrated embodiment, if a selected player is not officially flagged on the scorecard, the system-received scores are hidden or blank while the user enters their scores for blind verification purposes.

[0329] In the illustrated example, the first verification tool 901 includes a comparison trigger 912 for triggering a comparison between scores. For example, with respect to blind verification, a user can interact with the comparison trigger 912 to initiate a comparison between the player scorecard and the system-received scores to be verified. Prior to initiating the comparison, the first verification tool 901 may not display the system-received scores. In some embodiments, the comparison may be initiated upon entry of one or all scores or upon aggregation of the system-received scores, which may be provided as a button or other interactive trigger.

[0330] As a result of the comparison operation, the system-received score may be entered in a hole field 914 juxtaposed to the corresponding hole field 910. A validity notification may be displayed for the hole or associated score to indicate a score match, a score discrepancy, or both. For example, when an option to compare the blind entry score with the system score is triggered, the system score may be displayed and a validity notification of what matches and what does not match may be displayed. In the illustrated embodiment, a solid arrow 918 between the blind score hole field 910 and the system-received score hole field 914 indicates a score match, and a dashed arrow 920 indicates a discrepancy. The validity notification may be provided by any suitable indication. For example, matches and / or discrepancies may be indicated by different colors, shading, text, outlines, boxes, symbols, or other suitable perceptible indications.

[0331] The first verification tool 901 may include an official marker 922 that allows a user to flag a scorecard as official. For example, if blind verification indicates that all scores match, the user may interact with the official marker 922 to mark the scorecard as official. In another example, if all scores match, the verification system 70 may automatically flag the scores as official.

[0332] In some embodiments, scores may be editable by the user to resolve discrepancies. In some configurations, the discrepant or edited score is submitted or saved for additional review. As described above, marking a scorecard as official may send the scorecard, score, or a false flag to a database for storage and / or distribution to one or more data platforms, along with an indication that the score is official. In some embodiments, scores recorded by a score tracking system may be submitted to one or more data platforms as non-official scores, and verification is sent to the data platform to indicate that the score is now official by flagging the score as official via a verification system.

[0333] In one embodiment, after the blind comparison is triggered, the user is given the ability to edit any scores in the system's scorecard. In this or another example, the ability to mark a player's scorecard as official is blocked until all score discrepancies are resolved. In this or another example, when a player's scorecard associated with the verification system 70 is marked official, a notification may be displayed against the player's scorecard, and the notification will remain on the player's scorecard even if the user navigates back to the player.

[0334] 9B, the second verification tool 830 may present scoring data for one or more groups. The presentation may be configured to display scores from a selected event and / or round, as selected with respect to the first verification tool 901. The presented scores may include informal tracking scores and official scores. As described elsewhere herein, various score transmission timing schemes may be used. In various embodiments, tracking scores may be entered as they are transmitted to the companion device 12, such as after each shot hit entry or when a player or group completes a hole.

[0335] Scoring data can be arranged in a variety of formats. In the illustrated embodiment, the scoring data is arranged so that each column of data is sorted in either ascending or descending order based on the information available in the respective column. Fields are typically not editable from a basic user perspective. The display may be scrollable to view groups other than the initially displayed group. In one example, selecting a player or group populates information for that player or group from a second validation tool. Thus, a user can select a player or group and view additional details about that player or group's score. In one example, if no manual score entry has been entered or processed by validation, selecting a player or group populates the group selector and / or player selector fields for the selected player or group. In one embodiment, players with scores marked as official are marked with a visual indicia as a notification of this.

[0336] The presented scoring data may include various data points about the players and their scores, such as one or more of the following: (a) Group Number 931—corresponding to the group number assigned to the group of players; (b) Course of Play 932—corresponding to the course on which the scoring data was collected; (c) Starting Hole 933—corresponding to the first hole on which the group started based on their grouping for that round; (d) Tee Time 934—corresponding to the starting tee time for that group; (e) Rank 935—the player's predicted rank in the progress of play during the ongoing round; and (f) Team Player Name 936—the name of each team player in that group. (g) Total 937—corresponding to the player's first and last name, (g) Total 937—corresponding to the current total par relative score for the competition, (h) Today 938—corresponding to the par relative score for the round, (i) Front 9 Holes by Hole Score 939—corresponding to a listing of the scores for each hole in the first nine holes, (j) Score Out 940—corresponding to the stroke totals for the scores entered for the front nine, (k) Back 9 Holes by Hole Score 941—corresponding to a listing of the scores for each hole in the back nine holes, (l) Score In 942—corresponding to the stroke totals for the scores entered for the back nine, (m) Stroke Total 943—corresponding to the stroke total for the round, or (n) any combination thereof. In various embodiments, Stroke Total 943 is displayed only if Score Out 940 and Score In 942 have data.

[0337] According to various embodiments, a round management system can be utilized to manage the rounds and groupings of players participating in a golf tournament. For example, a grouping engine can create player groupings for participating players. The round management system can also input the groupings into the ST application, from which a scorer using a companion device can identify assigned groups and / or players and track scores during competition.

[0338] The grouped players are automatically entered into the device assignment element of the device management system. Once the groups are defined, the device management system can assign tracking modules to various groups and players from a device list. In one example, a companion device or an ST application running thereon is assigned or programmed to a particular group, and the tracking module assigned to the group is entered into the companion device via the ST application for specific identification by a scorer who links scoring data to the tracking module. In one variation, a scorer assigned to a group enters credentials or otherwise logs on to the ST application, which enters group information for the scorer's assigned group into the ST application. In another configuration, entering a player's name into the ST application identifies the player for scoring data transmission, and one or more of a location system, data management system, or verification system are configured to access the tracking module assignment and pair the scoring data with the tracking module data.

[0339] During a round, scorers can collect scoring data by entering various stroke events and other data into a companion device described herein. Stroke events may be associated with timestamps. The companion device may transmit the scoring data to a management system. The tracking module can automatically collect location or localization data continuously, at defined intervals, or upon the occurrence of defined events. In one example, the tracking module is configured to continuously acquire GPS coordinates corresponding to its location, for example, every second. The tracking module can automatically transmit the acquired coordinates to the management system continuously, at defined intervals, or upon the occurrence of defined events. In one example, the tracking module transmits the collected location or localization data to the management system every five seconds. As described above, other location information techniques can be used instead of, in addition to, or in combination with GPS. For example, an STTM system can include or incorporate a location network consisting of an UWB location network. The location or localization data may be transmitted to the management system directly or indirectly from the tracking module, the location network, or another device.

[0340] The location system can access the tracking module assignments and pair the timestamp with the assigned tracking module location. The data management system can access the scoring data and review and edit it as needed using a data management tool. A verification system then compares the score from the score tracking system with each player's scorecard. For example, the verification system may apply blind verification. The verification system then reconciles the score from the score tracking system with the player's scorecard. The verification system marks the reconciled system scores as "official." The "official" designation is entered into the data management tool interface to indicate that no additional scores or score corrections will be entered for that player. The official scores and related data collected by the companion devices and tracking modules during play may then be stored in a database and / or distributed to a data platform for viewing, analysis, etc.

[0341] In various embodiments, the score tracking system may utilize additional location tracking technologies, which may act as primary, secondary, backup, or alternative position determination techniques with respect to the use of the tracking module.

[0342] In one embodiment, the companion device or other electronic device includes a laser rangefinder and is operated by, for example, a scorer, such as a human or robot. The rangefinder is used to measure the distance of objects, such as a player or a ball, from the device. The device may also include direction sensors, such as magnetic field sensors and / or gravity field sensors, to combine distance and direction relative to a map of the course. To further enhance position determination, the device's location may be known because the device is placed at a known location, or the device's location, e.g., coordinates, may be combined with the angle and distance of an object from the device to determine the device's location by the device or another device. For example, a device in a mobile use case may acquire GPS (or other global constellation coordinates), which may be augmented, as described herein, with, for example, Wide Area Augmentation System (WAAS), Differential GPS (DGPS), e.g., Global Differential GPS (GDGPS), Continuously Operating Reference Stations (CORS), Signals of Opportunity (SOP)-based or augmented navigation, UWB, LTE, cellular, radio, television, Wi-Fi, other satellite signals, etc. The location of the device may also be determined using any location network technology as described herein, such as UHF, NFC, Wi-Fi, Bluetooth Low-Energy, or UWB. The coordinates of the object may be determined and overlaid or mapped onto the golf course to determine the object's position relative to the golf course. In one embodiment, the device is a real-time kinematic (RTK)-enabled device and utilizes RTK to determine the coordinates. For example, an RTK base station or network may be utilized to determine the device's location in combination with the direction and distance of an object targeted with a laser rangefinder to determine the object's position.In particular, as described elsewhere herein, the tracking module may also be an RTK-enabled device, and the location network may include an RTK base station or an RTK network.

[0343] In one embodiment, a camera system is positioned around the golf course. One or more cameras can track movement and determine distance using associated lasers or rangefinders or through optical calculations. For example, each camera can calculate the distance of a ball or other object of known size by comparing the size of the optically captured object with known object sizes. Further determining the camera angle allows the object's position at distance and angle from the camera to be plotted against a map of the area around the camera. Position determination may be enhanced, for example, by utilizing multiple cameras to triangulate or otherwise determine the position of a ball or other object. As an example, a camera may utilize an optical map of an area of ​​the course from a fixed camera's field of view to determine the object's position relative to a known location within the mapped area. For example, an approximate location of the object may be determined by comparing an image of the object with surrounding features in an image of the known location. To enhance the accuracy of position determination, distance may be determined using optical calculations such as those described above. In this or another example, radar may be implemented to track objects, including position, velocity, trajectory, acceleration, or other parameters. In this or another example, the camera may be configured for optical recognition. For example, cameras may utilize facial recognition, body recognition, gait recognition, clothing recognition, ball / shape recognition, etc., used to identify participants and / or balls, thereby pairing locations with players and / or player-balls. In one embodiment, players carry or wear optical, electromagnetic, or reflective markers identifiable by cameras or associated receivers that uniquely identify the players. In one embodiment, cameras may utilize optical recognition / augmented reality (AR) to determine the location of players and / or balls. Cameras may typically be placed at known locations, although in some cases, one or more cameras may be utilized in a mobile environment, utilizing, for example, real-time kinematic base station or camera-related location determination methodologies, such as those described herein with respect to tracking module location determination.In some embodiments, a camera is used to identify motion and objects, and a laser or rangefinder associated with the camera can be targeted at such objects to determine their distance from the camera. The camera's viewing angle and distance can be combined to determine the object's location. In some embodiments, the topology of the area can be mapped or determined and added to the distance calculation. In some embodiments, such camera systems are operated by humans, robots, or fully autonomously. The camera can operate in the visual and / or optical spectrum, including one or more of the visual spectrum, ultraviolet spectrum, or infrared spectrum.

[0344] The systems and methods disclosed herein may include additional functionality and features. For example, the operational functions of the systems and methods may be configured to execute on a dedicated processor specifically configured to perform the operations provided by the systems and methods. Notably, the operational features and functions provided by the systems and methods may increase the efficiency of computing devices utilized to facilitate the functionality provided by the systems and various methods disclosed herein. For example, by training the system over time based on data and / or other information provided and / or generated in the system, the amount of computer operations that need to be performed by devices and elements within the system using the system's processor and memory may be reduced compared to traditional methodologies. In such situations, less processing power is utilized because the processor and memory do not need to be dedicated to processing. As a result, utilizing the software, techniques, and algorithms provided in this disclosure can result in substantial savings in the use of computer resources. In certain embodiments, various operational functions of the system may be configured to execute on one or more graphics processors and / or application-specific integrated processors. In some embodiments, various functions and features of the systems and methods may operate without human intervention and be implemented entirely by computing devices. In certain embodiments, for example, multiple computing devices may interact with the devices of the system to provide the functionality supported by the system. Additionally, in certain embodiments, the computing devices of the system may operate continuously without human intervention to reduce the likelihood of introducing errors into the system.

[0345] At least some of the methodologies and techniques described with respect to the exemplary embodiments may incorporate a machine, such as, but not limited to, a computer system or other computing device, where a set of instructions, when executed, can cause the machine to perform any one or more of the above-described methodologies or functions. The machine may be configured to facilitate various operations performed by the system. For example, but not limited to, the machine may be configured to assist the system by providing processing power to support the processing load experienced by the system, by providing storage capacity to store instructions or data traversing the system, or by assisting other operations performed by or within the system. As another example, a computer system may help increase the accuracy of collected scoring data collected in a reduced infrastructure environment by incorporating rules, such as error and / or warning rules, that automatically identify potential discrepancies. As another example, utilizing a tracking module that does not interfere with player performance or require player interaction to track location provides accurate tracking with significantly reduced infrastructure and human intervention compared to current methodologies.

[0346] In some embodiments, the machine may operate as a standalone device. In some embodiments, the machine may be connected (e.g., using a communications network, another network, or a combination thereof) to and assist operations performed by other machines and systems, such as tracking modules, companion devices, management devices and associated system servers, databases, other systems, programs, and / or devices, or any combination thereof. The machine may be connected to any component in the system. In a network deployment, the machine may operate as a server or a client user machine in a server-client-user network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may comprise a server computer, a client user computer, a personal computer (PC), a tablet PC, a laptop computer, a desktop computer, a control system, a network router, a switch, a bridge, or any machine capable of executing a set of instructions (whether sequential or not) that specify actions to be performed by the machine. Furthermore, while a single machine is illustrated, the term “machine” is intended to include any collection of machines individually or collectively executing a set (or sets) of instructions to perform any one or more of the methodologies discussed herein.

[0347] A computer system may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), a main memory, and a static memory, which communicate with each other via a bus. The computer system may further include a video display device, which may be, but is not limited to, a liquid crystal display (LCD), a flat panel, a solid-state display, or a cathode ray tube (CRT). The computer system may include, but is not limited to, an input device such as a keyboard, a cursor control device such as a mouse, a disk drive unit, a signal generator such as a speaker or remote control, and a network interface device. The disk drive unit may include, but is not limited to, a machine-readable medium having stored thereon one or more sets of instructions, such as software that embodies any one or more of the methodologies or functions described herein, including the methods exemplified above. Instructions may also reside, completely or at least partially, in the main memory, the static memory, the processor, or a combination thereof during execution by the computer system. The main memory and the processor may also constitute machine-readable media.

[0348] Dedicated hardware implementations, including but not limited to application-specific integrated circuits, programmable logic arrays, and other hardware devices, can also be constructed to perform the methods described herein. Applications that may include the apparatus and systems of various embodiments broadly include a variety of electronic and computer systems. Some embodiments implement functionality in two or more specific interconnected hardware modules or devices, with associated control and data signals communicated between and through the modules, or as part of an application-specific integrated circuit. Thus, the exemplary systems are applicable to software, firmware, and hardware implementations.

[0349] In accordance with various embodiments of the present disclosure, the methods described herein are intended to operate as software programs running on a computer processor. Furthermore, software implementations may include, but are not limited to, distributed processing or component / object distributed processing, parallel processing, or virtual machine processing, and may also be constructed to implement the methods described herein.

[0350] The present disclosure contemplates machine-readable media containing instructions such that a device connected to a communications network, another network, or a combination thereof can use the instructions to send or receive audio, video, or data and communicate over the communications network, another network, or a combination thereof. The instructions can also be sent or received over the communications network, another network, or a combination thereof via a network interface device. The term "machine-readable medium" should be considered to include a single medium or multiple media (e.g., centralized or distributed databases, and / or associated caches and servers) that store one or more sets of instructions. The term "machine-readable medium" should also be considered to include any medium capable of storing, encoding, or carrying a set of instructions for execution by a machine, causing the machine to perform any one or more of the methodologies of the present disclosure. The terms “machine-readable medium,” “machine-readable device,” or “computer-readable device” accordingly include, but are not limited to, memory devices; solid-state memories such as memory cards or other packages containing one or more read-only (non-volatile) memories, random-access memories, or other rewritable (volatile) memories; magneto-optical or optical media such as disks or tapes; or other self-contained information archives or sets of archives, all of which are considered distribution media equivalent to tangible storage media. A “machine-readable medium,” “machine-readable device,” or “computer-readable device” may be non-transitory and, in certain embodiments, may not include the waves or signals themselves. Accordingly, the present disclosure is considered to include any one or more of the machine-readable media or distribution media enumerated herein, including art-recognized equivalents and successor media, on which the software implementation herein may be stored.

[0351] The illustrations of the arrangements described herein are intended to provide a general understanding of the structure of various embodiments and are not intended to serve as a complete description of all elements and features of apparatus and systems that may utilize the structures described herein. Other arrangements may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of the present disclosure. Additionally, the figures are merely representative and may not be drawn to scale. Certain proportions thereof may be exaggerated, and other proportions may be minimized. Accordingly, the specification and drawings are to be regarded in an illustrative, rather than a restrictive, sense.

[0352] Thus, while particular arrangements have been illustrated and described herein, it is understood that any arrangement calculated to achieve the same purpose may be substituted for the particular arrangement illustrated. This disclosure is intended to cover any adaptations or modifications of the various embodiments and arrangements of the invention. Combinations of the above arrangements, and other arrangements not specifically described herein, will be apparent to those skilled in the art upon reviewing the above description. Therefore, this disclosure is not limited to the particular arrangement(s) disclosed as the best mode contemplated for carrying out the invention, but rather the invention is intended to include all embodiments and arrangements falling within the scope of the appended claims.

[0353] The foregoing is provided for the purposes of illustrating, explaining, and describing embodiments of the present invention. Modifications and adaptations to these embodiments will be apparent to those skilled in the art and can be made without departing from the scope or spirit of the invention. Upon reviewing the above-described embodiments, it will be apparent to those skilled in the art that said embodiments can be modified, scaled down, or enhanced without departing from the scope and spirit of the claims set forth below.

Claims

1. 1. A score tracking method, the method including: collecting or receiving, by a location system, location data corresponding to positions of tracking modules carried by players participating in a golf tournament, the location data including or used to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a designated time during play of the golf tournament; receiving an indication of the occurrence of a stroke event associated with the player, the indication being entered into the companion device by a scorer carrying a companion device and viewing the player carrying the tracking module; receiving or generating a timestamp corresponding to the time an indication of the occurrence of the stroke event was entered into or received from the companion device by the scorer; and Pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

2. The method of claim 1 , wherein the sets of location coordinates correspond to positions of the tracking module over a period of time, each set of location coordinates corresponding to a predefined time interval within the period of time.

3. 10. The method of claim 1, wherein the tracking module is configured to output location signals received by a plurality of beacons positioned around a perimeter of a golf course to calculate the location data corresponding to a position of the tracking module.

4. 10. The method of claim 1, wherein the location data is transmitted to the location system from one or more beacons positioned around the golf course that are configured to receive location signals transmitted by the tracking module to track the position of the tracking module.

5. The method of claim 1 , further comprising receiving the location data and indication of score events corresponding to a plurality of the tracking modules carried by different players participating in the golf tournament.

6. The method of claim 5 , wherein a single companion device is configured to receive indications of the scoring events associated with multiple players, each player carrying a separate tracking module.

7. 7. The method of claim 6, wherein the location data and the indication of the score event include identification data including an identification of the player carrying the tracking module or an identification number of the tracking module carried by the player, and wherein pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred includes matching the respective identification data.

8. 2. The method of claim 1, further comprising dividing holes in a golf course into zones, each zone corresponding to a range of location coordinates, and determining a current zone in which the tracking module is located from the plurality of sets of location coordinates.

9. 1. A score tracking system, the system including: a tracking module configured to be carried by a player participating in a golf tournament; an application configured to interface a scoring operation to a user via a user interface of a companion device, the companion device being separate from the tracking module, the application configured to receive input via the user interface indicating an occurrence of a stroke event, the input causing the application to set a timestamp corresponding to the occurrence of the stroke event; and 1. A location system configured to collect or receive location data, the location data including or used by the location system to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to a position of the tracking module at a specified time, and the location system configured to pair the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

10. 10. The system of claim 9, wherein the sets of location coordinates correspond to positions of the tracking module over a period of time, each set of location coordinates corresponding to a predefined time interval within the period of time.

11. 10. The system of claim 9, wherein the tracking module is configured to output location signals received by a plurality of beacons positioned around a perimeter of the golf course to calculate the location data corresponding to a position of the tracking module.

12. 10. The system of claim 9, wherein the location data is transmitted to the location system from one or more beacons positioned around the golf course configured to receive location signals transmitted by the tracking module to track the position of the tracking module.

13. 10. The system of claim 9, wherein the location system is configured to receive the location data and indications of scoring events corresponding to a plurality of the tracking modules carried by different players participating in the golf tournament.

14. The system of claim 9 , wherein a single companion device is configured to receive indications of scoring events associated with multiple players, each player carrying a separate tracking module.

15. 10. The system of claim 9, wherein the location data and indication of a score event include identification data including an identification of the player carrying the tracking module or an identification number of the tracking module carried by the player, and the location system is configured to match each of the identification data to pair the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

16. 1. A score tracking system, the system including: a tracking module configured to be carried by a player participating in a golf tournament; an application configured to interface scoring operations to a user via a user interface of a companion device, the companion device being separate from the tracking module and configured to receive input via the user interface indicating an occurrence of a stroke event, the input causing the application to set a timestamp corresponding to the occurrence of the stroke event, the stroke event including an address and a ball hit, the user interface including an indicator configured to be pressed to indicate that a player is addressing the ball and to be held until the player hits the ball to indicate that the ball has been hit; and 1. A location system configured to collect or receive location data, the location data including or used by the location system to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to a position of the tracking module at a specified time, and the location system configured to pair the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

17. 1. A score tracking method, the method including: receiving input from a companion device corresponding to a stroke event of a player competing in a golf tournament, the input including a timestamp corresponding to an occurrence of the stroke event; collecting or receiving, by a location system, location data corresponding to the position of a tracking module carried by the player, the location data including or used to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a specified time; and Pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred, wherein the companion device includes an interface configured to receive input corresponding to the stroke event, the stroke event including an address and a ball hit, and the interface includes an indicator configured to be pressed to indicate that the player is addressing the ball and to be held until the player hits the ball to indicate that the ball has been hit.

18. 20. The method of claim 17, wherein the companion device is carried by a scorer accompanying a group of players that includes the player, and the companion device receives inputs corresponding to the stroke events of all players in the group.

19. 1. A score tracking method, the method including: receiving input from a companion device corresponding to a stroke event of a player competing in a golf tournament, the input including a timestamp corresponding to an occurrence of the stroke event; collecting or receiving, by a location system, location data corresponding to the position of a tracking module carried by the player, the location data including or used to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a specified time; and A step of pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred, the stroke event being entered into the companion device by a scorer watching live video of the golf tournament.

20. 1. A score tracking method, the method including: receiving, from a companion device, input corresponding to a stroke event of a player competing in a golf tournament, the input including a timestamp corresponding to an occurrence of the stroke event; collecting or receiving, by a location system, location data corresponding to the position of a tracking module carried by the player, the location data including or used to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a specified time; and A step of pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred, the stroke event being entered into the companion device by a scorer watching a video replay of the golf tournament.

Images