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 the management of golf events, including systems and methods for score and location (position) tracking that are widely applicable to multiple network infrastructures. Background

[0002] Managing the play of a golf tournament while tracking the detailed locations and scores of all shots requires complex backstage transactions, which are further complicated by the diversity of course locations and infrastructures. For example, before each event on the PGA Tour, each golf course is mapped and digital images of each hole are created, which are used as background information to calculate the exact position and distance between two coordinates (e.g., the tee box and the player's first shot, or the position of the shot and the position of the hole). On the PGA Tour, by using this mapping data in conjunction with its ShotLink system, it has been collecting the positions and scores of all balls for all shots for all rounds. In addition to the pre-tournament mapping, the ShotLink system also utilizes a complex and costly infrastructure that takes days to set up and tear down and must be transported between events. Also, the successful operation of the ShotLink system depends on a volunteer workforce of up to 350 people per event. The tournament data provided by the ShotLink system has proven to be valuable for both fans and players. However, considering the time, cost, and infrastructure required for the operation of the ShotLink system, it is not practical to use it for low-level tournaments.

[0003] What is needed is a system and method for golf event management that provides accurate tracking operations with a portable design, reduces setup time and personnel, and is widely adaptable to course conditions and infrastructures.

Summary of the Invention

[0004] In a first aspect, a score tracking system includes a tracking module and one or both of an application or a location system. In one example, the tracking module and one or both of the application or the 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 is separate from the tracking module and may be configured to receive an input that indicates the occurrence of a stroke event via the user interface. Based on this input, the application can set a timestamp corresponding to the occurrence of the stroke event. In one configuration, a stroke event includes an address and a ball hit (hitting the ball). 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 held until the player hits the ball to indicate that the ball has been hit. In an example including a location system, the location system may be configured to collect or receive location data. The location data may include a plurality of sets of location coordinates or may be used by the location system to generate a plurality of sets of location coordinates, and each set of location coordinates corresponds 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 occurrence of a stroke event.

[0005] In any of the above examples or alternative 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 resulting from the previous stroke.

[0006] In any of the above examples or alternative 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 examples or alternative examples of the first aspect, the tracking module can be configured to transmit location data to a location system.

[0008] In any of the above examples or alternative 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 a plurality of sets of location coordinates.

[0009] In any of the above examples or alternative examples of the first aspect, the location data collected or received by the location system includes location identification data used by the location system to calculate location coordinates.

[0010] In any of the above examples or alternative examples of the first aspect, the plurality of sets of location coordinates consists of a set of GPS coordinates.

[0011] In any of the above examples or alternative examples of the first aspect, the plurality of sets of location coordinates consists of a set of ultra-wide band positioning coordinates.

[0012] In any of the above or alternative examples of the first aspect, the tracking module may be 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, where the second interval is greater than the first interval.

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

[0014] In any of the above or alternative examples of the first aspect, the companion device may be configured to be carried by a scorer who accompanies a group of players including the player. 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 alternative examples of the first aspect, the stroke event includes a ball hit. The position of the tracking module at the time of occurrence of the stroke event can be used as a proxy for the position of the ball of the player carrying the tracking module resulting from the previous stroke.

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

[0017] In a second aspect, the score tracking method includes receiving, from a companion device, an input corresponding to a stroke event 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 may correspond to the location of a tracking module carried by the player. The location data can include a plurality of sets of location coordinates or can be used to generate a plurality of sets of location coordinates, and each set of location coordinates corresponds 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 location of the tracking module at the time of occurrence of the stroke event. The companion device may include an interface configured to receive an input corresponding to the 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 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 location of the tracking module at the time of occurrence of the stroke event, and the stroke event can be input into the companion device by a scorer viewing a live video of the golf tournament.

[0020] In one example, the 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 stroke event. The stroke event can be input into the companion device by a scorer viewing a video replay of a 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 traveling with a group of players including the player, and the companion device can receive inputs corresponding to the stroke events of all players within the group.

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

[0024] In any of the above or another example 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 a plurality of sets of location coordinates.

[0025] In any of the above or another example of the second aspect, the location data collected or received by the location system includes location identification data used by the location system to calculate location coordinates.

[0026] In any of the above or another example of the second aspect, the plurality of sets of location coordinates consists of a set of GPS coordinates.

[0027] In any of the above or alternative examples of the second aspect, the plurality of sets of location coordinates consists of a set of ultra-wideband positioning coordinates.

[0028] In any of the above or alternative examples of the second aspect, the tracking module may be 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, where the second interval is greater than the first interval.

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

[0030] In any of the above or alternative examples of the second aspect, the stroke event includes a ball hit, and the position of the tracking module at the occurrence of the stroke event 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 alternative examples of the second aspect, the tracking module operates as a beacon in the location network.

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

[0033] In a third aspect, the 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 includes a plurality of sets of location coordinates or is used to generate a plurality of sets of location coordinates, and each set of location coordinates corresponds to the location of the tracking module at a specified time during play of the golf tournament. In one configuration, the method includes receiving an indication of the occurrence of a stroke event associated with a player, the indication being input into the companion device by a scorer viewing a player carrying the companion device and 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 input into or received from the companion device by the scorer. In one configuration, the method can include pairing the timestamp with a set of location coordinates corresponding to the location of the tracking module at the time of the occurrence of the stroke event.

[0034] In a fourth aspect, the score tracking system includes a tracking module and one or both of an application or 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 is separate from the tracking module and may be configured to receive an input that indicates the occurrence of a stroke event via the user interface. 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 a plurality of sets of location coordinates or may be used by the location system to 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 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 occurrence of the stroke event.

[0035] In an example of the third or fourth aspect, the set of location coordinates corresponds to the position of the tracking module over a period of time, and each set of location coordinates corresponds 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 a location signal from a plurality of beacons disposed around the golf course. In one configuration, the location data includes parameters of the location signal that the location system uses to calculate a set of location coordinates. In one configuration, the tracking module utilizes the parameters of the location signal to calculate its position and transmits its position to the location system as location data.

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

[0038] In any of the above or other examples of the third or fourth aspect, the tracking module may be configured to output a location signal received by a plurality of beacons arranged 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 aspect, the location data may be transmitted from one or more beacons arranged around the golf course configured to receive a location signal transmitted by the tracking module to track the position of the tracking module to the location system.

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

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

[0042] In any of the above or other examples of the third or fourth aspect, 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 alternative examples of the third or fourth aspect, the method includes receiving location data and score event instructions corresponding to a plurality of tracking modules respectively carried by separate players participating in a golf tournament, or the system is configured to receive location data and score event instructions corresponding to a plurality of tracking modules respectively carried by separate players participating in a golf tournament.

[0044] In any of the above or alternative examples of the third or fourth aspect, a single companion device may be configured to receive score event instructions related to a plurality of players each carrying a separate tracking module. In one configuration, the location data and score event instructions include identification data including the identification of the player carrying the tracking module or the identification number of the tracking module carried by the player. In a further configuration, pairing a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time of occurrence of a stroke event includes collating the respective identification data.

[0045] In any of the above or alternative examples of the third or fourth aspect, the stroke event includes a ball hit, and the position of the tracking module at the time of occurrence of the stroke event is used as a proxy for the position of the ball of the player carrying the tracking module resulting from the previous stroke.

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

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

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

[0049] In any of the above or alternative examples of the third or fourth 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 a plurality of sets of location coordinates.

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

[0051] In any of the above or alternative examples of the third or fourth aspect, the plurality of sets of location coordinates consists of sets of GPS coordinates.

[0052] In any of the above or alternative examples of the third or fourth aspect, the plurality of sets of location coordinates consists of sets of ultra-wideband positioning coordinates.

[0053] In any of the above or alternative examples of the third or fourth aspect, the tracking module may be configured to collect location data at a predefined first interval and send the collected location data to the location system at a predefined second interval, where the second interval is greater than the first interval.

[0054] In any of the above or alternative examples of the third or fourth aspect, the method may include dividing the holes of a golf course into zones, each zone corresponding to a range of location coordinates, and determining the current zone in which the tracking module is located from a plurality of sets of location coordinates, or the system is configured to divide the holes of a golf course into zones, each zone corresponding to a range of location coordinates, and determine the current zone in which the tracking module is located from a plurality of 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 may be configured to be carried by a player participating in a golf tournament. The companion device is configured to receive an input corresponding to a stroke event, and the input may include a timestamp corresponding to the occurrence of the stroke event. The location system can include a plurality of sets of location coordinates or collect or receive location data used by the location system to 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 occurrence of the stroke event.

[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 of occurrence of the stroke event is used as a proxy for the position of the ball of the player carrying the tracking module resulting from the previous stroke.

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

[0058] In any of the above or another example of the fifth aspect, the tracking module is configured to send location data to a location system.

[0059] In any of the above or another example 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 another example of the fifth aspect, the location data collected or received by the location system includes location-specific data that the location system uses to calculate location coordinates.

[0061] In any of the above or another example of the fifth aspect, the plurality of sets of location coordinates consists of a set of GPS coordinates.

[0062] In any of the above or another example of the fifth aspect, the plurality of sets of location coordinates consists of a set of ultra-wideband positioning coordinates.

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

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

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

[0066] In any of the above or another example of the fifth aspect, the companion device is configured to be carried by a scorer who accompanies a group of players including the player. The companion device may be further configured to receive an input corresponding to a stroke event of all players within the group.

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

[0068] In one example of the sixth aspect, the stroke event includes a ball hit, and the location of the tracking module at the time of occurrence of the stroke event is used as a proxy for the location 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 the location network. In one configuration, the location network utilizes ultra-wideband positioning.

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

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

[0072] In any of the above or another example of the sixth aspect, the location data collected or received by the location system includes location identification data used by the location system to calculate location coordinates.

[0073] In any of the above or another example of the sixth aspect, the plurality of sets of location coordinates consists of a set of GPS coordinates.

[0074] In any of the above or another example of the sixth aspect, the plurality of sets of location coordinates consists of a set of ultra-wideband positioning coordinates.

[0075] In any of the above or another example of the sixth 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 may be greater than the first interval.

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

[0077] In any of the above or another example of the sixth aspect, the companion device can include an interface configured to receive an 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 held until the player hits the ball to indicate that the ball has been hit.

[0078] In any of the above or another example of the sixth aspect, the companion device is carried by a scorer who accompanies a group of players including the player, and the companion device receives an input corresponding to the stroke events of all players in the group.

[0079] In any of the above or another example of the sixth aspect, the stroke event is input to the companion device by a scorer watching a live video of a golf tournament.

[0080] In any of the above or another example of the sixth aspect, the stroke event is input to the companion device by a scorer watching a video replay of a golf tournament.

Brief Description of the Drawings

[0081] The novel features of the described embodiments are specifically recited in the appended claims. However, the described embodiments may be best understood by reference to the following description taken in conjunction with the accompanying drawings, both as to organization and manner of operation:

[0082] Figure 1 schematically shows the hardware and network functions of the STTM system according to various embodiments described herein;

[0083] Figure 2 schematically shows various elements of the STTM system and operating environment components according to various embodiments described herein;

[0084] Figure 3 shows the zone function for location tracking according to various embodiments described herein;

[0085] Figures 4A and 4B show various views of the tracking module according to various embodiments described herein, Figure 4A shows a face-on view, and Figure 4B shows a side view;

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

[0087] Figure 4D shows various components of the tracking module according to various embodiments described herein;

[0088] Figure 5A provides an overview list of the tracking module loaded into the device management system and its associated locations according to various embodiments described herein;

[0089] Figure 5B shows an exemplary user interface generated by the device management system to provide a tracking module management function and present device management data of the loaded tracking module according to various embodiments described herein;

[0090] Figure 5C shows a device assignment user interface that enables a user to perform a device assignment operation according to various embodiments described herein;

[0091] Figure 6A shows a grouped engine user interface including a grouping management panel according to various embodiments described herein;

[0092] Figure 6B shows a grouped presentation by segments according to various embodiments described herein;

[0093] Figure 6C shows a segment profile management interface including examples of data elements of a segment profile along with the definition of options for editing data elements or creating new segments according to various embodiments described herein;

[0094] Figure 6D is a diagram showing an interface of a revision editor 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] Figure 6E shows a player status editor interface according to various embodiments described herein;

[0096] Figure 6F shows a round engine interface constituting a round management panel according to various embodiments described herein;

[0097] Figure 6G shows a round engine interface for creating a playoff according to various embodiments described herein;

[0098] Figure 7A shows a menu screen of an ST application according to various embodiments described herein;

[0099] Figure 7B shows a player description selection screen of an ST application according to various embodiments described herein;

[0100] Figure 7C shows a description category selection screen of an ST application according to various embodiments described herein;

[0101] Figure 7D shows a description property selection screen for a selected description category of the ST application according to various embodiments described herein;

[0102] Figure 7E shows a summary player detail screen of the ST application according to various embodiments described herein;

[0103] Figure 7F shows the selection of the "Select Club" function from the group screen of the ST application according to various embodiments described herein;

[0104] Figure 7G shows the selection of "Iron" from the club selection screen of the ST application according to various embodiments described herein;

[0105] Figure 7H shows an interface for instructing "Shot Hit" using the ST application according to various embodiments described herein;

[0106] Figure 7I shows the "In Hole" prompt of the ST application according to various embodiments described herein;

[0107] Figure 7J shows a group screen that displays the strokes recorded after the score indicates "Shot Hit" using the ST application according to various embodiments described herein;

[0108] Figure 7K shows the selection of the "Starting Location" function from the group screen of the ST application according to various embodiments described herein;

[0109] Figure 7L shows the selection of available description properties for selection on the "Starting Location" screen of the ST application according to various embodiments described herein;

[0110] Figures 7M and 7N show a group screen that depicts the transition of the "starting location" returning from the "fairway" to the "starting location" after instructing a "shot hit" using the ST application, according to various embodiments described herein;

[0111] Figure 7O shows a group page where the first two players have finished the hole and the third player is on the green, according to various embodiments described herein;

[0112] Figure 7P shows recording a second shot from a provisional tee, according to various embodiments described herein;

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

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

[0115] Figure 8A shows the presentation block user interface of the data management tool of a data management system that includes tool components within the presentation block, according to various embodiments described herein;

[0116] Figure 8B shows the group scorecard interface of the data management tool, according to various embodiments described herein;

[0117] Figure 8C shows the stroke detail component of the team players of the data management tool, according to various embodiments described herein;

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

[0119] FIG. 8E shows an all-group presentation component of a data management tool according to various embodiments described herein;

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

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

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

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

[0124] This description will explain various embodiments of a score tracking (score tracing) and tournament management system, which may be referred to herein as the 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 provide accurate and detailed data regarding a player's game and performance while not interfering with the participating players. The management functions can be provided in an on-site, off-site, or hybrid configuration. The pre-round, in-round tournament and score management functions can be automated and adaptable to various tournament structures, significantly reducing costs and personnel time while integrating multiple tournament processes such as player grouping, tee times, score collection, location tracking, error correction, score verification, etc., and can adopt customizable setup rules and profiles. The STTM system can be utilized to provide thorough data and feedback to players and other stakeholders in real-time or with a delay, and can be utilized to provide the functionality of a tournament scoring, organization management, and / or scoring system.

[0125] Some embodiments of the STTM systems described herein may incorporate or utilize advanced infrastructure, but the STTM systems can be provided in a widely applicable, flexible package configured for portability to utilize limited infrastructure with little impact on the amount, quality, accuracy, and / or functionality obtained through the end data product and the tournament operations management support and its use. The flexible architecture of the STTM systems may be extensible, storable, and / or modular to conform to the available infrastructure and resources with minimal variation to the data quality. For example, while various aspects of the STTM systems are described herein as providing integrated functions or operations, the systems, components, and modules of the STTM systems are not limited to combined use. In fact, the systems, components, and modules described herein can be utilized individually or integrated individually with known systems or systems to be developed in the future.

[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 memory and executed by a processor, can cause a 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 (tracking modules), one or more companion devices (companion devices) 12, and / or one or more management devices. The user device can include suitable dedicated or multi-purpose electronic computing devices and systems such as mainframes, servers, computers, dedicated devices, desktops, laptops, tablets, smart devices / phones, personal data assistants, etc. When utilized for collecting live event data, the companion device is typically a handheld tablet, smart device / phone, personal data assistant, or dedicated handheld device.

[0127] The STTM system can include, incorporate, and / or communicate with a user device that executes an application for performing the operations described herein. The user device can interface the user with the operations of the STTM system. For example, the user device can be configured to access, execute, run, or emulate one or more applications and / or services of the STTM system. 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] Referring to FIGS. 1 and 2, the STTM system 10 can include a score tracking system 20 configured to track the scoring of a competition, such as the location (position) and / or the scoring of a golf tournament, and a management system 20 that manages the operation of the STTM system 10, which can include its components, such as devices and elements.

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

[0130] The tracking module 11 is composed of a user device configured to be carried by a competitive player, or is configured to be placed near the competitive player during play. The tracking module 11 can include a memory containing instructions and a processor that executes instructions from the memory to perform various operations executed 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, e.g., FIG. 4C) that enables a scorer, a player, and / or other users to interact with various applications such as a score tracking application that may be referred to as an ST application, and / or location signals, and / or operations executed on the tracking module 11 such as location calculation processes, and to interact with STTM system components, devices, systems, and / or their elements. In certain embodiments, the tracking module 11 is 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, and / or can include them. The tracking module 11 can be configured to perform various location operations. For example, the tracking module 11 may be configured to track its location and / or communicate location information to the STTM system and / or location elements. The tracking module 11 may be configured for location tracking using various techniques and location schemes described herein. For example, in some embodiments, the 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 a management system 20 as described herein.In these embodiments 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 a location service to send data that constitutes location data, which may include location-specific data that can be utilized to determine the position of the tracking module 11. The location data may also include a timestamp corresponding to the time to which the location data relates. The tracking module 11 may be configured to communicate data such as location data and / or location-specific data via 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 short-range wireless 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 communication infrastructure 15, etc. via various communication networks 17, or may be configured to communicate indirectly via another STTM system device or a network device.For example, in one embodiment, the tracking module 11 may transmit data directly to devices, elements, related networks, and / or location elements of the STTM system 10 via one or more communication networks 17 and / or may 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. The companion device 12 or the management device 13 may be utilized for this purpose.

[0131] The companion device 12 may be configured to communicate with, define, identify, and / or organize scoring data that may include location data related to the tracking module 11. Further, or alternatively, the companion device 12 may be utilized to collect and / or track other competitive data. The companion device 12 may be used by a user to access data, content, services, and / or perform various other tasks and functions of the STTM system 10. As an example, the user may use 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 an application, such as an ST application, that provides one or more operating functions of the STTM system 10, such as communication with one or more of the management systems 30, one or more tracking modules 11, one or more management devices, and / or location elements that make up one or more of the location networks 14 and / or the global satellite communication infrastructure 15.

[0132] In certain embodiments, the companion device 12 may be used by a scorer to control one or more operating 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 can include a memory containing instructions and a processor that executes the instructions from the memory to perform various operations executed 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 (such as a screen, monitor, graphical user interface, etc.) that enables the scorer to interact with various applications such as ST applications executed on the companion device 12 and to interact with one or both of the STTM system 10, such as the score tracking system 20 or the management system 30. In certain embodiments, the companion device 12 may be, and / or may include, a computer, any type of sensor, laptop, set-top box, tablet device, phablet, server, mobile device, smartphone, smartwatch, and / or any other type of computing device. Illustratively, the companion device 12 is shown as a smartphone or tablet device in FIG. 1.

[0133] The management device 13 is utilized by a management user with respect to 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 via the communication network 17 or other network with which the STTM system 10 communicates. In further embodiments, the management user may be a robot, computer, humanoid, animal, any type of user, or any combination thereof. The management device 13 can include a memory containing instructions and a processor that executes instructions from the memory to perform various operations executed by the management device 13. In certain embodiments, the processor may be hardware, software, or a combination thereof. The management device 13 may also include an interface (e.g., a screen, monitor, graphical user interface, etc.) that enables the user to interact with various applications (e.g., management applications) executed on the management device 13 and to interact with the devices, elements, and systems of the STTM system 10. In certain embodiments, the management device 13 may be a computer, laptop, set-top box, tablet device, phablet, server, mobile device, smartphone, smartwatch, and / or any other type of computing device. The management device 13 may be local or remote with respect to the arena location. The management device 13 may be cloud-based or web-based.

[0134] In certain embodiments, the companion device 12, the tracking module 11, the management device 13, and / or the location network 14 can have any number of software applications and / or application services stored thereon and / or accessible therefrom. For example, the companion device 12, the tracking module 11, the management device 13, and / or the location network 14 can include applications for controlling the operational features and functions of the STTM system 10 and / or the score tracking system 20 or its management system, applications for controlling any system device, cloud-based applications, VoIP applications, cellular applications, other phone-based applications, location and / or accessible applications, and / or application services, other types of phone-based applications, location and / or positioning 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 STTM system 10, such as the score tracking system 20 or its management system 30, described in the present disclosure, and the functions provided by the methods. In certain embodiments, the software applications and services can include one or more graphical user interfaces to enable a user (e.g., a scorer, a player, a system administrator) to easily interact with the software applications.In addition, software applications and services may 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 a global satellite communication infrastructure), or any combination thereof. In certain embodiments, the companion device 12, the tracking module 11, and / or the management device 13 may include a related device identification ID, or other identifier for uniquely identifying the particular companion device 12, tracking module 11, and / or management device 13.

[0135] The communication network 17 may be configured to link each of the STTM system devices, components, and elements, may include any number of networks, and in one embodiment includes the location network 14. For example, the communication network can be utilized by the companion device 12 to connect to other devices inside and outside the communication network 17. In various embodiments, the companion device 12, the tracking module 11, the management device 13, and / or the location network 14 may belong to the communication network 17 and / or form part of the communication network 17. In certain embodiments, the communication network 17 may be a local, mesh, or other network that enables and / or facilitates various aspects of the functionality of the STTM system 10. In certain embodiments, the communication network 17 may be formed between and / or among various user devices such as the management device 13, the companion device 12, the tracking module 11, the database 18, or combinations thereof through the use of any type of wireless or other protocol and / or technology. For example, the user devices may communicate with each other in the communication network 17 by utilizing any protocol and / or wireless technology, satellite, fiber, or any combination thereof. In particular, the communication network 17 may be configured to communicatively link and / or communicate with other networks of the STTM system 10 and / or networks external to the STTM system 10. In various embodiments, the tracking module 11 may be configured to communicate directly with one or more components and / or location elements of the management system 30. The communication network 17 may be configured to transmit, generate, and receive any information and data traversing the STTM system 10. In certain embodiments, the communication network 17 may include any number of servers, databases, or other components.The communication network 17 may also include 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 short-range wireless communication network, or any combination thereof, and may be connected thereto. Exemplarily, the management device 13 is shown as a representative server and may be included within or shown as utilizing the communication network 171. As described above and elsewhere in this specification, the management device 13 typically comprises a user interface that enables a user to perform the scoring and / or tournament management operations described herein. In certain embodiments, the communication network 17 may be part of a single autonomous system located in a particular geographic region or part of multiple autonomous systems spanning multiple geographic regions.

[0136] The functions of the STTM system 10 can be supported and executed by using any combination of servers. The servers may exist in the communication network 17 or its environment, but in certain embodiments, the servers may exist outside the communication network 17. The servers can provide server services that execute various operations and functions provided by the STTM system 10 and play their roles. In certain embodiments, the management device 13 may be composed of a server including 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 device, or any combination thereof.

[0137] The STTM system 10 can 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 regarding each device within the STTM system 10, and perform other typical functions of a database 18. Further, the database 18 can include or be connected to a processor and memory to perform various operations associated with the database 18. In certain embodiments, the database 18 can be connected to a server, companion device 12, management device 13, tracking module 11, any device of the STTM system 10, any process of the STTM system 10, any program of the STTM system 10, any other device, system, element, any network, or any combination thereof. The database 18 can be composed of multiple databases 18. The database 18 can be local or remote. The database can be cloud-based.

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

[0139] This disclosure can refer to specific applications executed on one or more electronic user devices, but it should be understood that such applications, including any application services, may be provided within a single application, program, or platform, or may be divided, virtualized, distributed, or combined across any number of executable platforms and resources or among them.

[0140] This specification refers to various interface components. Interface components include interface elements configured to interface operations such as the selection of data values or data elements to the user, display elements configured to interface displays to the user, data elements, and the like. Indicators, operators, options, etc. described in this specification regarding the interface may include buttons, toggles, switches, sliders, swipe buttons / bars / fields, sidebars, or other interface elements. Such interface elements can be configured either hard or soft. Similarly, interaction terms such as press, tap, select, etc. can be performed using the human body, a stylus or other instrument, peripheral devices such as a mouse or keyboard, or other appropriate user interactions.

[0141] Continuing to refer to FIG. 2, the score tracking system 20 can be configured to track scores related to the play of a plurality of competing players, such as golfers participating in a tournament. Although the tournament is described herein as a golf tournament, those skilled in the art will understand, upon reading this disclosure, that the systems and methods described herein can be applied to other competitions and other environments. Score tracking can also include tracking the location of stroke events. As introduced above and described in more detail below, the score tracking system 20 can 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 the score-related data to a management system 30. The tracking module 11 can be configured using location identification, positioning, and / or proximity technologies that can be used by the tracking module 11, and / or the companion device 12, the management device 13, the location network 14, and / or another device, such as the location system 80, to track the location of the tracking module 11, as introduced above and described in more detail below. Using the companion device 12, a scorer can record events, such as stroke events related to the play. Recording the 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 the tracking module 11 corresponding to the recorded event, such as when the player addressed or hit the ball.The location data, or the time-series synchronization of the position and timestamp of the tracking module 11, may be used by the location system 70 as a proxy for the position of the player's ball following the previous hit or the starting position of the player's ball before hitting the ball. A notable advantage of this score tracking method is that typically a single scorer who accompanies a group of multiple golfers can record both the score and the location data in a conservative manner. As will be explained in more detail below, in various embodiments, the tracking module 11 is configured to be compatible with a plurality of location service technologies, thereby providing flexibility with respect to tracking the location of the tracking module 11, for example, by utilizing the infrastructure available with respect to the course as needed. The score tracking system 20 and / or the STTM system 10 may include or incorporate location services such as one or more of the global satellite communication infrastructure 15 or the location network 14. The location network 14 is typically a local location network with respect to the golf course where the tournament is being held and may include wireless receivers, transmitters, transceivers, antennas, UWB antennas, anchors, initiators, responders, cell towers, Wi-Fi® access points, beacons, geobeacons, BLE gateways, and the like. In some embodiments, the location network 14 includes an external location / signal network that utilizes short-range or long-range location technologies, which may include opportunistic signals.

[0142] In various embodiments, the tracking module 11 is configured to communicate with the companion device 12, and the calculated location data or location signaling parameters that can be used to calculate the location of the tracking module 11 at a given time, time range, or continuously by the companion device 12, the management device 13, and / or the location system are operable to be obtained from the tracking module 11. However, in some embodiments, the tracking module 11 may not communicate with the companion device 12 regarding the location tracking operation. For example, another device may calculate or receive the location of the tracking module 11. For example, the timestamp set by the companion device 12 may be sent to another device to be paired with the location of the tracking module 11 in time series before or after being sent to the management device 13, or the management device 13 may communicate 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 communication infrastructure 15 and transmits those coordinates to the management system 30. The companion device 12 can also transmit a stroke event including the associated timestamp to the management system 30. The location system 80 pairs the timestamp with the corresponding location coordinates.

[0144] In one example, the tracking module 11 obtains its position, which may include location coordinates, by location signaling with a location network 14 such as the UWB or other location network described herein. In one configuration, the tracking module 11 calculates its position as described herein and transmits its 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, and the companion device 12 then transmits the position, and / or the position paired with the corresponding timestamp, to the management system 30. The companion device 12 may also transmit a stroke event including the associated timestamp to the management system 30. Next, the location system 80 may 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 a plurality of tracking modules 11 and assign them to players. The device management system 40 can be executed on one or more management devices 13. In one configuration, the device management system 40 communicates with the tracking module 11 during play to track the location of the tracking module 11. When the companion device 12 sets a timestamp regarding the location of the tracking module 11 for the 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 is provided to the data management system 40 for consideration and / or can be made available for use by the operation of the STTM system 10 or transmission or use by the data platform 19. As described above and elsewhere in this specification, the position calculation and / or the combination of location coordinates and timestamps may be performed by the location system 80 and made available to other systems of the management system 30, or the functionality of the location system 80 may be provided by other systems of the management system 30. The position calculation may be perceptually instantaneous or otherwise real-time. In one embodiment, the companion device 12, the tracking module 11, the management device 13, the location network 14, and / or the location system 80 can track the location of the tracking module 11 continuously or in a near-continuous state. Such continuous or nearly continuous tracking can be used to address location tracking / network latency. For example, when a scorer records a stroke event that sets a timestamp when the ball is struck, in almost all cases, the most recent position calculated within 5 seconds of the timestamp provides the exact position of the ball when it was struck. In one embodiment, the scorer sets a timestamp for location purposes at address time.

[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 a rationalized verification of a player's official scorecard against scores collected by the score tracking system 20. In the above or another embodiment, the management system 30 can include a location system 80. The location system 80 may be configured to process location data of the tracking module 11, calculation of location data from location-specific data, pairing of timestamps and location data, determination of zones, 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 location-specific data directly or indirectly to the management system 30. The location system 80 may be available to pair (associate) stroke events and corresponding timestamps with the location of the tracking module. The location system 80 may share data and / or functions with various systems of the 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 location determination functions instead of, or in addition to, the location system 80. In various embodiments, the location system 80 includes or communicates with one or more location networks. As described in more detail herein, the location networks can include GPS, Wi-Fi®, RFID, BLE, UWB, NFC, cellular, and the like.

[0147] As introduced above, the companion device 12 may be configured to execute or run an ST application. The ST application may be composed of a mobile application, a web application, a cloud-based, or other application formats, and may include instructions operable to perform the score collection function described herein with respect to the companion device 12. If the companion device 11 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 start commands, obtain battery level or charge status, receive location data of the tracking module 11, initiate location data events, relay data received from the tracking module 11 to storage or another computing device, execute a proxy service of the tracking module 11, or perform other operations described herein. Further, or alternatively, the ST application may configure the companion device 12 for communication with the management device 13 of the management system 30. For example, the ST application may be configured to receive and incorporate group assignment, round information, tee time, etc. from the round management system 60.In the above or another example, the ST application receives the assignment of the player and tracking module 11 from the device management system 40, incorporates the assignment of the player and tracking module 11 into the collected scoring data (stroke event data, location data, timestamp, club selection, etc.), and transmits the stroke event data including the relevant timestamp to the STTM system 10, such as the location system 80, the device management system 40, the data management system 50, and / or the verification system 70, and / or may be configured to communicate with the tracking module 11 to pair the tracking module 11 with the assigned player. However, in some embodiments, the assignment is maintained by the management system 30, and the companion device 12 may be accompanied by stroke event timestamps or location data having the identifier of each tracking module 11 that the management system 30, such as the data management system 60 or the location system 80, uses to pair the position of the tracking module 11 at the timestamp with the assigned player. 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 the management system 30, such as the data management system 60, the verification system 70, and / or the location system 80.

[0148] In one embodiment, the tracking module 11 is composed 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. Although a larger tracking module 11 may be used, in the illustrated example, the tracking module 11 generally includes a housing 110 that is smaller than a deck of playing cards. In one example, the housing 110 may include a clip for clipping to a belt, pocket, or other surface. In one embodiment, a wearable receptacle that can be carried or worn by an individual for receiving the tracking module 11 may be provided. In one example, the receptacle may include a clip for clipping to a belt or pocket, or may include a wearable band, or can be attached to a wearable band. Numerous variations may be implemented. For example, the tracking module 11 may be integrated into or embedded in clothing such as a belt, belt buckle, hat, bracelet, etc. In some embodiments, the tracking module 11 may be integrated into a smart device such as a tablet, laptop, phone, PDA, or other portable electronic device. In various embodiments, the housing 110 may be configured to be opened for maintenance, component replacement, upgrade, or other desired purposes. For example, the housing 110 may include a removable panel or may be configured with a clam shell design. In one embodiment, the housing 110 may have waterproof or water-resistant properties with respect to the interior of the housing 110. For example, the panel or clam shell can be provided over a gasket.

[0149] Figure 4D is a semi-schematic diagram inside the tracking module 11 showing components that may be included in various embodiments of the tracking module 11. In some embodiments, the tracking module 11 includes a wired data communication port 111. The port 111 may be provided or accessible from the outside of the housing 110, or may be accessible by removing its panel or clam shell. The wired data communication port 111 can be used for programming, downloading, or other data communication needs as an alternative or backup to wireless data communication.

[0150] The tracking module 11 can include one or more batteries (cells) 113 configured to power the operation of the tracking module 11. Various standard and custom size batteries 113 can be used, such as coin cells like AA, CR123A, 23A, or CR2032. A compact size is preferred, but larger batteries 113 can also be used. As an example, a user can attach or carry a separate battery pack or power source 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 can be used. For example, the battery 113 can include lithium, alkaline, silver oxide, carbon zinc, air zinc, lithium ion, NiCD, or NiMH. Various configurations of the tracking module 11 may include a rechargeable battery 113 such as a lithium ion, NiCD, or NiMH, or may be configured to operate with a rechargeable battery 113. 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 can include a charging port 112 that is operable to receive a supply of power to charge the battery 113. The charging port 112 can include a female connector or a 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 a water-blocking material. In another example, a removable plug may be mounted within or on the charging port interface to prevent water ingress. In one embodiment, the tracking module 11 is configured to be wirelessly charged. In one embodiment, the tracking module 11 is configured to have a charging port for recharging the battery while within the housing. For example, the housing can 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, DC power connector, or other suitable power supply interface technology can be used. A custom charging interface can also be used. In some embodiments, the charging port 112 is also operably configured to be used as a wired data communication port 111. In one embodiment, the charging port 112 is configured with 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 a plurality of charging ports for bulk charging of a plurality of tracking modules 11.

[0152] In various embodiments, the tracking module 11 may be configured to include a wireless communication port 114 that includes one or more wireless receivers, transmitters, and / or transceivers. The wireless communication port 114 may be configured to transmit and / or receive wireless data communications, such as signals, via any wireless communication medium or protocol, including, or incorporated with, radio waves, cellular, Wi-Fi®, short-range wireless, 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 (such as 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 communication infrastructure, etc. The wireless communication port 114 may be configured to transmit and / or receive positioning data, such as parameters for location calculation. The wireless communication port 114 may be configured to operate as a beacon, as detailed below. The tracking module 11 may be configured to have a location alarm. The location alarm may be remotely wirelessly activated via wireless communication from one or more of a remote command center, a management device, or a companion device equipped with a suitable 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 via 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 wireless, Bluetooth®, or other suitable wireless communication technologies.

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

[0154] The tracking module 11 can include a memory 119a and a processor 119b that executes instructions stored in the memory 119a or received in other ways to execute the operation of the tracking module 11. In some configurations, the housing 110 includes a memory expansion port or slot for connecting to additional memory storage. The expansion slot may be configured to accommodate an expansion memory device such as a micro SD card and 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 can be transmitted to a storage device, a receiving device, and a processing device continuously, periodically, daily, or upon request.

[0155] Tracking module 11 may include an accelerometer 1100. The accelerometer 1100 may be used for motion detection. The motion detection may be used in combination with positioning and location tracking, determination, or acquisition. For example, the motion detection may start transmitting a location signal and / or may listen for the same. The motion detection may start transmitting the tracked, determined, or acquired location or position data to, for example, a companion device, a location network, or an STTM system device. In some embodiments, the acceleration sensor 1100 may be configured for motion detection related to the detection of a swing by a player. The detection of motion corresponding to a swing may be used in addition to or instead of the score input for a swing or "shot hit" as described below. The acceleration sensor 1100 may similarly be configured to detect an address corresponding to a time with a pause in motion, for example, prior to the detection of motion corresponding to a swing.

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

[0157] In one embodiment, the user interface 11a includes one or more indicator lights. The indicator lights can be used to indicate operational states such as power on, data processing, data uploading, data downloading such as instructions, assignments, or updates, receiving and / or acquiring location / location data, receiving instructions, sending data, in operation, operation completed, and the like.

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

[0159] In various embodiments, as introduced above, the tracking module 11 is equipped with location identification, positioning, and / or proximity technologies to assist in identifying the location of the misplaced tracking module 11 and / or determining the exact location of the tracking module 11. For example, the tracking module 11 can be configured to output location identification signals such as packets, blinks, requests, responses, etc., which can be used by a companion device, a location network, a management system, and / or a location system to identify and / or determine the location / location of the tracking module 11 based on, for example, signal strength, signal parameters, and / or signal characteristics, either directionally or omnidirectionally. Additionally, or alternatively, an STTM system that may include the location elements described herein can be configured to identify the location of the tracking module 11 using other techniques as described below.

[0160] The STTM system or its score tracking system may include a location network configured to provide a location tracking function and / or service. The location tracking network (see Figure 2) may include a plurality of location signaling devices. The location signaling devices can include those set for determining outdoor positions / places, such as receivers, transmitters, transceivers, gateways, beacons, UWB antennas, anchors, initiators, responders, real-time kinematic (RTK) base stations, etc. The location signaling devices can be configured to utilize radio waves such as UHF, NFC, Wi-Fi (registered trademark), Bluetooth Low-Energy (registered trademark), and / or UWB. The location signaling devices may be arranged around the pre-course and configured to communicate with a plurality of 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 the tracking module 11 can utilize various localization technologies such as RSSI, RSSI-fingerprinting, and / or time of flight (ToF), time difference of arrival (TDPA), and / or angle of arrival (AoA).

[0161] The tracking module 11 can 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, position search, proximity determination, and / or ranging. FIG. 4D shows a wireless communication port 115 configured for ultra-wideband, although other short-range communication protocols and / or signaling may be utilized. The wireless communication port 115 may be in addition to, or instead of, the wireless communication port 114. In some embodiments, the wireless communication port 115 is composed of a Wi-Fi® chip, a BLE chip, an LTE chip, and an ultra-wideband chip, and the wireless communication port 114 is composed of a cellular chip. Depending on the configuration, location services may be utilized by the tracking module 11, the STTM system, a location signaling device of the location network, and / or any device suitably configured to receive a location signal or position identification signal and utilize the signal and associated data to identify and / or determine the location / position of the tracking module 11.

[0162] Additionally, or alternatively, the tracking module 11 may be configured to receive a location - specific signal from a location - signaling device that can be used to determine the position / location of the tracking module 11 by the tracking module 11, a companion device, a location network, a location system, or any of the others. For example, a beacon signal may be used to determine the position / location of the tracking module 11. As introduced above, the location - specific signal may be output using short - range communication technology. In various embodiments, the location - specific signal 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 - specific signals such as beacon packets or UWB anchors. In a device - side use case, the tracking module 11 may use the received location signal to calculate its position or relay the location signal / packet data and / or related received parameters to another device such as a companion device or a management device for direct or indirect processing (e.g., via the use of an API). For example, when a beacon is present, the tracking module 11 can receive the beacon packet, and the beacon packet can be used for position / location determination by the tracking module 11, or a companion device or management device communicating with the tracking module 11, for example, by RSSI, RSSI - fingerprinting, and / or ToF technology. In a network - side position - calculation use case, the tracking module 11 may continuously output signals, transmit location - specific response signals to location - specific signals received from a location - signaling device, or transmit polling signals, and these signals may be used by other STTM system components such as a location network or a location system to calculate the position of the tracking module 11, for example, via TDPA, ToF, and / or AoA.In one embodiment, the location network includes a plurality of location signaling devices, such as beacons or anchors, disposed around a play area such as a green, fairway, rough, and / or tee box. The tracking module 11 can receive signals transmitted for location / determination. In a further example, the tracking module 11 may transmit a response location identification signal. In the above or another embodiment, three or more beacons or anchors may be used, for example, around the green, for accuracy and precision.

[0163] In one embodiment, the tracking module 11 may be configured to cooperate with a location network for UWB position / location determination. For example, the tracking module 11 can include a plurality of antennas for directly or indirectly utilizing AoA / difference in phase. The tracking module 11 may be configured as an initiator and / or responder for single-sided, two-sided, or multi-sided ranging. The tracking module 11 is configured to operate as an initiator in a time difference of arrival model with synchronization anchors of a location tracking network arranged around a golf course and can achieve precise positions and accuracies up to, for example, 1 cm. In one embodiment, multiple positioning technologies can be utilized to enhance positioning such as Wi-Fi®, BLE, and / or UWB. In a further embodiment, 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 a plurality of anchors that receive location-specific signals from the tracking module 11. The anchors can utilize time difference of arrival (TDoA) or other suitable techniques to determine the coordinates of the tracking module 11. It will be understood that in such a network or other location network, the location system may receive and / or collect location-specific data or location data. The location system may calculate a position from the location-specific 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 accurate positioning and location determination. Exemplarily, FIG. 4D shows including a GPS chip or receiver 117 configured to receive GPS location coordinate data. Although generally referred to herein as GPS, those skilled in the art will understand that such reference applies equally to other global navigation satellite systems (GNSS) such as GLONASS, BeiDou, Galileo, or other current or future GNSS. The GPS location can be enhanced with WAAS (Wide Area Augmentation System), DGPS (Differential GPS), e.g., GDGPS (Global Differential GPS), RTK (Real Time Kinematic), CORS (Continuous Operating Reference Station), SOP (Signal of Opportunity) - based or enhanced navigation, UWB, LTE, cellular, radio, television, Wi-Fi®, other satellite signals, etc. In some embodiments, the location network can be used instead of or in hybrid with one or more global communication 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, the tracking module 11 is configured to utilize any or all of the available global satellite communications (GPS, GLONASS, BEIDOU, GALILEO, and QZSS) and perform accurate positioning outdoors with an accuracy of 0.5 - 5m typ. or better. In one embodiment, the tracking module 11 transmits its coordinate position to the management system via the cellular network.

[0165] In one embodiment, the communication network includes a LPWAN (Low Power Wide Area Network) 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. Similarly, the companion device can transmit stroke event data via such a network. Different from the current score tracking methodology, the configuration of this score tracking system utilizes a low data load suitable for transmitting small data packets over a low power, long distance network and can still maintain a stable amount of accurate data.

[0166] As introduced above, the STTM system can utilize a UWB positioning / location network for all or part of the location service. GPS or other location services can also be used simultaneously, either in a hybrid configuration or as an option or setting that can be individually selected for system devices.

[0167] In various embodiments, the tracking module 11 may be configured to continuously output a location signal or a positioning signal, or may be configured to output a location signal when receiving an instruction to output a location signal. For example, the ST application or the location tracking network may be operable to address one or more tracking modules 11 to start the output of the location signal. In one embodiment, the tracking module 11 is configured to determine location coordinates every n seconds and transmit all or part of the coordinates every n + x seconds. For example, the tracking module 11 can be configured to collect location coordinates at any predetermined time interval and transmit the location coordinates collected at any time interval.

[0168] In one embodiment, the tournament course and / or the site around it may be mapped and divided into geolocation zones. The location data of the tracking module 11, which may include location-specific data, may be sent to a management system, such as a management device, to determine the current geolocation zone corresponding to the location of the tracking module. The current zone may be sent to the tracking module 11 and can trigger an action by the tracking module. In one embodiment, the tracking module 11 is programmed to identify the current zone, and the identification of the current zone may trigger an action. In some embodiments, the tracking module 11 may pass coordinates via an API that includes geolocation zones and send the coordinates to a management device that returns the current zone of the coordinates corresponding to the tracking module. Actions that can be triggered include alerts, API calls, database entries, alarms, etc. based on entering, exiting, or being in a specific zone.

[0169] Figure 3 shows 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 that zone. As described above, other zones or additional zones may be included. In various embodiments, all holes are 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, a score tracking system, or a management system can mark or record that a group of players is on the green when a tracking module assigned to the first player in the group crosses the green zone 31. As described above, the location system can collect or receive location data regarding the tracking module. The location system may use this location data to determine the location of the tracking module. The location coordinates may be applied to a predefined coordinate range corresponding to the defined zones to determine which zone the tracking module is currently located in. This determination of the zone may be performed in real time, for example, within 10 seconds, within 5 seconds, or within fewer seconds. The location system may utilize the most recent set of location coordinates or an interval of location coordinates to track the location of each tracking module 11 and / or to determine the current location and / or zone in which each tracking module 11 is located. Similarly, when a 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 may be marked or recorded as having completed the hole. When a tracking module 11 assigned to the player who first entered the tee box zone 38 is detected, the group is marked or recorded as having entered the tee box.As will be described in more detail below, user input to the ST application on the companion device may additionally or alternatively be used to mark or record locations. In one embodiment, a group marked or recorded as being at the tee box can advance the ST application to the hole associated with the tee box. In another embodiment, when a scorer enters "in the hole" into the companion device with respect to the last player of a holed-out group, the ST application automatically advances to the next hole. In another embodiment, the ST application does not advance to the next hole until "in the hole" has been entered for all players of the previous hole and the player enters the tee box of that hole.

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

[0171] In one embodiment, the position of the tracking module 11 is continuously tracked, for example, at one-second intervals or as otherwise programmed. In one embodiment, by pairing a timestamp with the position, the location coordinates collected before and after the time corresponding to the timestamp can be analyzed to identify the most likely position.

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

[0173] The companion device may record an address and / or a timestamp at the time of the shot. The location network may apply an algorithm that analyzes the positions before and after the timestamp. The look-back time and the forward time may be adjustable in the location system. As an example, the look-back time and the forward time can be 30 seconds. In one embodiment, the look-back time may be longer than the forward time. The location system can examine the location closest in time to the timestamp and 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 position changes little. As described above, the tracking module can detect when the swing was made. Such data may be provided to the location system to confirm or enhance the analysis regarding the timestamp. For example, the location system can pair the position at the time of the swing and compare it with the position obtained by the scorer provided with the timestamp. In some embodiments, if the position is unknown or does not correlate with the expected position, for example, if the coordinates correspond to a different hole, the position is not recorded.

[0174] In one embodiment, the tracking module 11 is composed of an operation window. For example, location data that may include location-specific data is not saved or transmitted outside the defined time of the operation window. Such an operation window can be registered with each tracking module 11. In this example or another example, if the tracking module 11 is not registered with a tournament player, the location data or location-specific data is not saved or transmitted. In any of the above or other examples, the tracking module 11 may not transmit the location data or location-specific data if the acquired coordinates are not the coordinates of the course hosting the tournament. Thus, in some embodiments, the tracking module 11 may be programmed with allowable coordinates related to the tournament. Such restrictions may enhance the privacy for the users of the tracking module 11. In some embodiments, the operation window registration, player registration, and / or coordinate restrictions may be overridden by the STTM system 10, for example, to find a lost or missing tracking module 11.

[0175] In one embodiment, the STTM system 10 may be configured to pass a notification to a tracking module 11 registered with a player whose position is off or whose play is too slow. For example, the tracking module 11 can 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 whose position is off or whose play is too slow can receive such a notification via the ST application. In a further example, the notification can 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 particularly with reference to FIGS. 5A - 5C, the STTM system can include a device management system 40 configured to assign a tracking module 11 to a player. The device management system 40 can provide device administrator data and / or device access to device management operations locally, remotely, and / or from anywhere via a management device. In some configurations, the device management system 40 is configured to assign tracking modules to groups, and the tracking modules are in turn assigned to players. The tracking modules are assigned to players in order, for example, the software of the tracking module is typically temporarily programmed into the player such that the location data, location - specific data, or other data transmitted from the tracking module includes the identification of the assigned player. The location data includes a timestamp corresponding to the time when the location data was collected or is otherwise associated with respect to the location of the tracking module. In some embodiments, the tracking module is agnostic to the player, but an identification number or other unique identifier associated with the tracking module is established in the STTM system such that communications from the tracking module pair an identifier with the assigned player. In various embodiments, whether programmed or agnostic, the companion device may be configured to associate the tracking module with the assigned player. For example, the ST application may be programmed by the device management system or a scorer to associate the tracking module with the assigned player for display on the companion device. In some embodiments, the companion device can 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 when a stroke event related to the location timestamp is input.

[0177] The device management system 40 may be configured to import and group a tracking module 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 a new tracking module and create a new device. Importing the 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 be managed. The tracking module profile may include specific tracking module management data such as an identifier and / or other tracking module data. The device management system 40 may be configured to store the tracking module profile in a location and store the location of the loaded related tracking module and the tracking module. The device management system 40 may be configured to receive specific device-related management data directly or indirectly from the loaded tracking module and present at least a portion of this data on a user interface display. FIGS. 5A-5B show embodiments of a user interface that presents device management data and enables a user to perform device management operations.

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

[0179] FIG. 5B is a diagram showing an exemplary user interface 403 generated by the device management system 40 to provide a tracking module management function and present device management data for the loaded tracking module. The data elements included in the tracking module device management data or profile shown in the illustrated embodiment are, for each tracking module, (a) function 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. The loaded and saved tracking modules and related device data elements are saved in the specified location 411 and presented below the location 411 element. In one configuration, the device management system 40 may be configured to allow the user to move the location and related device management data to change the order in the presentation. In the above or another configuration, the user may be able to collapse or expand the tracking module data for the selected location, for example, by interacting with the location 411 field. In the above or another configuration, the presentation includes a location labeled "Storage" 412 for saving loaded but currently unused tracking modules. 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 the loaded tracking module to receive data associated with one or more device data elements. In various embodiments, the presentation may be configured to be automatically updated at a predetermined time interval, such as every 30 seconds, or when an event occurs, such as when a device data element is received outside a predetermined tolerance or exceeds a threshold.In one configuration, the presentation can include a manual update option for immediately updating the values of the device data elements.

[0180] When each tracking module is transmitting a location signal, such as GPS information / coordinates, a polling signal, a response signal, location signal parameters, location data, a location identification signal, etc., "in operation" is identified by the in-operation 404 data element.

[0181] Device name 405 may be a unique name associated with the device. Device ID 406 may be a manufacturing ID number assigned to GPS or other location technologies. Accuracy 407 may refer to the measurement accuracy of the device's position as a distance. Location 408 may refer to the current location of the device. Depending on the configuration and location technology used, the location value may be provided in latitude / longitude, grid coordinates, or other appropriate 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 the tracking module during play. The device management system 40 may provide such location data to the location system continuously, in response to a request, or at predetermined intervals. As an 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 pair the timestamp with the corresponding position of the tracking module specified by that timestamp and provide it to the device management system 40. In another example, the companion device may send a location information event to the device management system 40 for location pairing. Any appropriate data handling and flow may be used to perform such location operations during play. For example, the tracking module may send location data and / or location-specific data to the location system, and the companion device may send a location event to the location system for location pairing of the timestamp and the tracking module.

[0182] The signal strength 409 may be the current signal strength of the location signals received by and / or transmitted by each tracking module. For example, the signal strength 409 may refer to the wireless signal strength such as cell, Wi-Fi (registered trademark), UWB, etc., and may be queried by the device management system 40 to measure the soundness of the tracking module regarding the ability to share location information or other data such as swings. In one embodiment, the signal strength 409 may refer to the accuracy of location-based coordinates. The battery life 410 provides a value regarding the life of the battery of the tracking module. For example, the battery remaining element data value is presented as a percentage of the remaining battery, or the time or period until the battery is completely depleted or depleted to a threshold level.

[0183] In some embodiments, the 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 the tracking module from location 402 / 411 by operation of the device management system 40 may cause a communication to be sent to the deleted tracking module. By this communication, the tracking module may update its location to "unassigned", "storage", or in some cases a new location. In one example, the tracking module may include a user interface (see, e.g., FIG. 4C) that enables a user to view device data elements associated with the tracking module. In the foregoing or another example, the communication may cause the tracking module to output a notification of being unused, not associated with its location, or being moved to another location. The notification may include an audio, text display, light, or other display that provides a desired notification when perceived by the user. In one example, the tracking module includes a notification button that, when pressed by the user, causes an output notification associated with the tracking module. In some embodiments, the tracking module is not configured to save a display of the assigned location.

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

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

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

[0187] As introduced above, the device assignment element can include a menu 424 that includes additional options to assist the user in the setup of the device assignment. In one example, the menu 424 can include a "Location Selection" option that enables the user to select or specify a location for one or more devices used in the device assignment. In the above or another example, the menu can include a "Tournament" option that enables the user to select a tournament. The tournament option or another option may be available to specify the tour associated with the tournament. The assignment element may be provided in any suitable presentation format, and it will be understood that the elements referred to in 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 the group number and the shell of the devices assigned to that group. In various embodiments, each assignment within a group may be in sequential order. The order may be static, assigned to the group and not re-assigned unless re-assigned. As introduced above, the device list is not assigned to a group and may thus include a list of all tracking modules that can be assigned. The device management system 40 may be configured such that a user can assign the devices in the device list to a group. The user may further assign the devices in a specific order within the group. When a device is assigned to a group, the user can save the assignment via the device settings save operator.

[0189] The group presentation provided to the device assignment user interface 420 may be configured to provide the 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 tee order. For example, when a round is selected from the 246 elements of round 2, the grouped players may be automatically filled into the group presentation. The group number 428 includes the number associated with the grouping of that round, which can 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 tee order. The device name 430 may include the name of the device. The device status 431 may include details of the current hardware functions of the device, such as battery level and signal strength.

[0190] In one embodiment, by assigning a tracking module to a player, a tracking module identification number is associated with the player in the backend of the STTM system, and an identification number is attached to the data obtained from the tracking module and / or the data recorded by the tracking module. An STTM system component that receives the data, such as a companion device, a location system, a verification system, a data management system, a device management system 40, and / or a data platform, associates it with the player to whom the identification number is assigned. Such an STTM system component can receive the assignment of the identification numbers of the player and the tracking module set by the device management system 40 for such purposes. In one example, the companion device receives the assignment of the identification numbers of the player and the tracking module set by the device management system 40, and associates the tracking module data with the player during scoring, for example, saving and / or transmitting 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, for example, using a UWB anchor network. In a network-side location tracking use case, the assignment of the device to the player is sent to a system component configured to calculate a location from the data collected by the network-side location network, or is subsequently used to associate the calculated location data of the tracking module with that of the assigned player.

[0191] As introduced above, and referring also to FIGS. 6A-6G, the STTM system can include a round management system 60 configured to manage the rounds and groupings of players playing in an event. The round management system can provide data manager data access to round management operations from local, remote, and / or anywhere via a management device. In various embodiments, the grouping can be managed by a grouping engine 500 configured to record one or more of the preservation of tee times, the adjustment to pre-published tee times, or the order of players 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. The rounds may be managed by a round engine 501 configured to manage one or both of a round state or a round cut.

[0192] The grouping engine 500 may be configured to manage grouping. Managing grouping 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 shows a user interface of the grouping engine 500 that includes 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 operation elements, which include: (a) a grouping presentation element 504 consisting of a list of groups with associated tee times for each segment; (b) a display element 505 by segments that is operable to enable a user to view each segment, a defined portion of a segment, or all segments at once; (c) a player list element 506 that identifies players that are not grouped or can be grouped; (d) a segment list element 507 that identifies segments created for a specific round; (e) a round selection element 508 that is operable to enable a user to select a round for the user to review and edit the grouping in which segments are associated with that round; (f) a segment profile selection element 509 that is operable to load a previously created profile with segment information; (g) a segment editing element 510 for creating or changing segments for a round; (h) a grouping generation element 511 configured to generate a grouping based on predefined and / or definable segment rules for a round; (i) a player deletion element 512 configured to delete players within a grouping presentation component while retaining tee time data; (j) a shell generation element 513 configured to generate a grouping that does not include players but has a grouping based on segment rules for a round; (k) a grouping clear element 514 configured to delete players and tee time data from a grouping presentation component; (l) a grouping status element 515 that includes a selectable list of grouping statuses; (m) a revision element 516 for accessing the operation of a revision editor that is operable to adjust a grouping and flag a round as having been revised; or (n) a player status element 517 that provides access to the operation of a player status editor that is operable to change the status of players in a round in an event.

[0193] Referring further to FIG. 6B, the grouping engine 500 may be configured to display a grouping presentation 518. The grouping presentation 518 may be wholly or partially displayed or accessible via interaction with the grouping presentation elements 504 (FIG. 6A). In the illustrated embodiment, the grouping presentation 518 includes grouping data elements provided in rows each 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) a segment number 519 that provides a segment number associated with the group, (b) a group number 520 associated with the group of players for a particular tee time, (c) a tee time 521 that presents the current time created for the group, (d) tee time data 522 that presents the date of the tee time created for the group, (e) a course 523 that presents the course on which the group plays for the specified tee time, and (f) a player 524 that provides the name of the player assigned to each group that may be presented in play order.

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

[0195] In various embodiments, the grouping engine 500 can provide various display and / or editing options with respect to the grouping within the grouping presentation and associated data elements. For example, the grouping engine 500 can provide interface elements that allow a user to sort columns of data by, for example, numerical value, alphabetical order, chronological order, or other appropriate data point characteristics. In one example, the grouping engine 500 can provide interface elements such that a user can selectively present, at one time, grouping by segment number or grouping by all segments. In the foregoing or another example, the grouping engine may be configured such that a user can edit data points of a row of data. For example, the editing functionality can be provided with the displayed data or separately from the displayed data. In one embodiment, the displayed data elements, as referenced in FIG. 6B, may consist of interface elements that display respective data point values and are configured for user interaction to arbitrarily edit the data point values. The grouping engine 500 can provide an editing function for grouping data elements selected from the following: (a) a segment number editor that includes a list of available segments created or loaded from a profile, (b) a group number editor that is operable such that a user can change a group number value (usually a positive integer), (c) a tee time editor that is operable such that a user can change the tee time (e.g., hours:minutes), (d) a tee time date editor that is operable such that a user can change the date of the tee time (e.g., month:day:year), (e) a course editor that is operable such that a user can change the course (which may include a selectable list of courses available for a selected tournament and event), (f) a player editor that is operable such that a user can change the player (e.g., when a player is selected, a field for entering another player is provided or a list of selectable players is displayed, which may include drag-and-drop or other selectable methodologies), or (g) combinations thereof.As described above, the display elements in the grouped presentation 518 may be composed of interface elements. In one embodiment, the above-described editor operations may be caused by interaction with such interface elements. In one configuration, the grouping engine 500 is operable to allow the user to selectively add rows, delete rows, or both.

[0196] Referring again to FIG. 6A, the player list element 506 may be configured to selectively display or display a list of all players within the field of the selected event that are not placed in the grouped presentation 518 or not assigned to a group. In various embodiments, the user can assign players to a tee time via interaction with the player list element 506 or via another interface element within the grouped presentation 518. In one embodiment, the player list element 506 is configured to display the player name and the total player event score relative to the par.

[0197] The grouping engine 500 can utilize segments and segment profiles. A segment can include a block of tee times presenting the start stage of a round. For example, two segments of a group can include one starting at hole 1 and the other starting at hole 10. A segment profile can include a set of segment rules used by the grouping engine 500 to assist in grouping generation. The grouping engine 500 can include or have access to one or more segment profiles. The segment profile can 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 can 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 such that the current user can search for other users including related segment profiles such as segment profiles created by or previously used by other users, or segment profiles and / or user profiles of other users. In one example, a user can select a segment profile and import the selected profile into the current event or their profiles, or export the segment profile to the profiles of other users.

[0198] FIG. 6C shows a segment profile management interface 525 that includes an example of elements of a segment profile along with definitions of options for editing data elements or creating new segments. The example elements and definitions of options for editing may be used by the segment data manager to create a new segment profile. The elements can include one or more data elements selected from the following: (a) a segment number selection 526 that includes a list of segments created for a selected round, (b) a segment priority 527 consisting of non - duplicable positive integer values set in another segment associated with the round so that a particular segment can exist in the system once per round, (c) a course 528 that includes a list of courses associated with a selected event, (d) a date 529 that identifies the date on which the tee - time starts play, (e) a tee - time 530 that identifies the first tee - time for start or end, (f) a tee - time (start / end) 531 that includes an option to flag a tee - time as a start tee - time or an end tee - time, (g) a time interval 532 used to specify the time interval between the start or end time set at the tee - time (above) and the tee - time (start / end) (above), (h) a group in interval 533 that, if set, identifies the number of groups that fall into an interval while the remaining groups are in different intervals, such that the first interval (below) and the remaining intervals (below) are applied, (i) a first interval 534 that represents the number of groups defined by the group in interval (above), (j) a remaining interval 535 that represents the time intervals of groups not defined by the group in interval (above), (k) a best score last / first 536 that identifies whether the player with the best score is set at the first tee - time or the last tee - time, (l) a start hole of all tee - times of the segment 537, (m) a player per group 538 that identifies the maximum number of players assigned to a group, (n) a group number 539 that identifies the initial number of groups of the segment, or (o) a combination thereof.The segment list panel 540 can be configured to display all data elements for each segment of the segment profile loaded into the segment profile management interface 525.

[0199] In one configuration, the grouping engine 500 is configured such that a user can create or delete segments. For example, elements of a segment profile may be editable through interaction with elements within a display, where the options for editing the elements include interface elements that a user uses to edit data elements of the segment profile or others. For example, to delete a segment, the user can select segment deletion 541 from the segment profile management interface 525. To create a new segment, the user can select new segment creation 542 from the segment profile management interface 525. Upon selection, the user is presented with the next consecutive number from the current segments within the profile, the next consecutive number from the current segments within the profile, the currently selected course, or default data elements with a predefined time interval. In various embodiments, additional data elements can be left blank to be set to other default values or further specified by the user.

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

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

[0202] Referring again to FIG. 6A, the grouping engine 500 may be configured to generate groupings. In one embodiment, the user can interact with the grouping generation element 511 to generate groupings for events, rounds, or segments thereof. For example, when the options of the grouping generation element 511 are activated, the grouping engine 500 can generate groupings using the current segment profile. Tea time can be generated based on the configuration of each segment of the segment profile described above.

[0203] When generating the grouping, as defined in the segment configuration, the player slot of each player can be identified based on the number of players in each group, and the slot represents the order in which each player plays. The slot referred to as 1 is the player who plays first, the slot referred to as 2 is the player who plays second, and so on. When multiple segments are part of the segment profile of a round, the grouping engine 500 can automatically start the assignment of players from the segment set as priority 1, and as each segment completes the assignment of players, the assignment of players can be sequentially performed. When the best score last / first 536 is set to last, the assignment of players can start from the last tee time of the segment and operate in reverse from there. When the best score last / first 536 is set to first, the assignment of players can start from the first tee time of the segment and operate forward from there. Regarding the selection and slotting of players when the best score last / first 536 is set, the grouping engine 500 can assign the player with the highest tournament score to the first slot, the player with the second best score to the second slot, and assign players to each slot within the tee time until players are assigned to all slots within the tee time before moving to the next tee time. In some embodiments, the segment profile can tie together multiple players. In one example, when multiple players have the same score, the grouping engine 500 can apply the following order rules to determine the assignment of the next player: (a) the earliest tee time from the previous round, (b) the highest segment priority from the previous round, with the highest first, (c) the lowest slot number, with the lowest first, and (d) the highest priority course, with the highest first.

[0204] The grouping engine 500 may be configured to utilize elements of the segment profile for a selected round for creating a grouping shell or for the automation of grouping. For example, when the grouping generation element 511 is activated, the grouping engine 500 is configured to create a grouping using the profile currently selected for that round. The tea time may be generated based on the configuration of each segment within the segment profile as described above. When the shell generation component is activated, the grouping engine may be configured to present 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) review scheduled, (c) reviewed, (d) official, or (e) combinations thereof. The "draft" state can be utilized by the user during the work of creating the grouping required for the round. In one embodiment, the "draft" state can be set as the default state when initially creating a grouping. The "review scheduled" state can be set when a defined set of groupings is ready for review. The "reviewed" state can be set when a defined set of groupings has been reviewed and is determined to be ready to transition to the "official" state upon review. The "official" state can 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 can limit the setting of a grouping state that formally progresses by skipping a grouping state. In one example, the "reviewed" grouping state cannot be set until the "scheduled for review" grouping state is set, and the "formal" grouping state cannot be set until the "reviewed" grouping state is set. In various embodiments, the grouping engine 500 is configured to log all grouping states with time stamps of user selections. The user who made the grouping state selection may also be logged and associated with the selection.

[0207] In some embodiments, the grouped draft is saved for subsequent review by the grouping engine 500. In one example, the saved grouped 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 a group of interest, to prevent a player from continuously entering early groups for weeks, to separate players known to be slow, to separate players who do not play alone, etc. In one example, when the grouped data enters a state for review, the administrative user reviews the data and can then set the grouping date to the "approved" state when signed off. When the grouped data is approved and the associated state is set to "approved", the grouped data becomes available in other STTM systems.

[0208] As introduced above, the grouping engine 500 can include a revision editor. In the illustrated embodiment, the operation of the revision editor may be initiated by interacting with the revision element 516 of the grouping management panel 503. The revision state can be specified in various states. For example, the revision states include "scheduled revision", "revision", and "revised state". The "scheduled revision" state may be set as the default state that is set before the revision process is started and before the revision is made after the grouping becomes official. The "revision" state is displayed when the user using the revision editor is in the process of revising a grouping that already has a "formal" set state. The "revised" state may be displayed when the grouping review process is completed and the changes are from the original grouping that was set to the formal grouping state. In one embodiment, when changes are made to the grouping or data element updated by the revision editor, the revision state is automatically set to "revision", and the grouping state may restart from the "review scheduled" state. In a further, or alternative, embodiment, the "revision" state may be set when the grouping verification process is completed at any time after the original grouping is set to the "formal" grouping state.

[0209] The revision editor can be provided with various operations that a user can use to adjust the tee times from the current grouped tee times. For example, FIG. 6D shows an interface of a revision editor 545 configured to adjust tee times using a revision based on an offset element 546 or a methodology of a reference time element 547. A revision based on the offset element 546 can cause the revision editor 545 to apply a revision based on an offset technique that utilizes start and end groups. The start and end groups may be pre-defined or may be set by the user, for example, by interacting with start and end group elements 548, and represent the start and end groups for which the tee times are adjusted. The time-based revision element 547 may cause the revision editor 545 to apply a revision based on an offset technique, which in one embodiment may also include an adjustment of time that can be specified via interaction with an adjustment time (+ / -) element 549 within the illustrated interface, and consists of the amount of time applied to the original tee times of the groups identified by the setting of the start and end group steps. The start and end groups and / or the adjustment time (+ / -) elements 548, 549 can include interface elements that include fields for entering text, selectable lists of groups and / or time differences, or other suitable interface elements. A revision using the base time methodology can enable a user to utilize a new base tee time that replaces the original base tee time via interaction with a new base time element 550, and the adjustment of the remaining tee times is then generated based on data elements defined in the segment profile of the round. In various embodiments, when a revision is used and applied, the round state is set to "revision" and the grouping engine 500 starts a grouping verification process.

[0210] As introduced above, the player list element 506 can include, or provide access to, a list of all players in the event's field. In some embodiments, the player status for an event and / or round may be associated with a player's name and may be displayed, for example. In some embodiments, the grouping engine 500 can include a player status editor configured to change a player's status. For example, in one configuration, a user can highlight a player in the player list, select a player status component to access the player status editor, and change the player status of the selected player. Referring to FIG. 6E, which shows an example interface of the player status editor 560, a list of status options 561 that a user can use to set the player status of the selected player may be provided. A status setting operator 562 may be provided to enable the user to set the status of the selected player. Various player status options may be provided, and they may include one or more of the following: (a) Uncut - a status that identifies players eligible to play in an event, (b) Cut - a status that identifies players with a cut flag, which can be set manually or updated automatically after the cut rules are executed, as will be described in more detail later, (c) Withdrawn - a status that identifies players who have withdrawn from a round, (d) Disqualified - a status that identifies players who have been disqualified from a round, or (e) Cut but did not finish - a status that identifies players who have been cut but do not continue to play in the remaining rounds, although official money is paid. In various embodiments, the player list 563 is automatically updated when a player status is set. The player status editor 560 may be configured to provide additional options for further defining the player status.For example, the player status editor 560 can provide the user with an option to define whether the player status entered by the user as "withdrawal" is also set for the player's future rounds. If the player's status is set to "withdrawal", "disqualification", "cut", or "cut but did not finish", the player may be removed from the player list 506 of the grouped presentation 504 and the grouped management panel 503 for the specified round.

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

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

[0213] The round selection element 571 may be operable to select a round for control. The round selection element 571 may be composed of, or may be, a selectable list of rounds available for an event presented for user selection.

[0214] The round state element 572 may be operable to select a round state, may constitute 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 grouping is formally set; (b) Grouping Formal - corresponding to the case where each grouping of the round is set as "formal" as described above, and is only available in that case; (c) In Progress - a state that is automatically set when the first stroke or score of the round is created and can additionally or alternatively be set manually in some embodiments; (d) Interrupted - a state that is set when the round is interrupted due to weather or other circumstances; (e) Play Complete - a state that is automatically set when the last score of the round is created and may additionally or alternatively be set manually depending on the embodiment; (f) Formal - a state that is set when no further changes to the round data, such as stroke information or score changes, are required; (g) Cancelled - a state that is set when the round is cancelled 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 "Interrupted", the user may use the suspension type element 573 to select a suspension type. In one example, the round engine 501 may request or prompt the user to select a suspension type when setting the round state to "Interrupted". In various embodiments, the suspension type element 573 may include presenting a selectable list of suspension types for user selection or may be operable. Exemplary suspension types may include one or more of delay, cancel, interrupt, or end of day.

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

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

[0218] Regarding the cut rule, the selectable settings can 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, including amateurs 583, or combinations thereof. The number to cut 579 corresponds to the number of players whose cut is based on the score and whose player status remains uncut, and all other players set to uncut will have their player status set to "cut". The number to cut and play 580 corresponds to the number of players who are cut based on the score and continue to play the round. If this is 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 can set their player status to "cut". The maximum number of strokes from the lead 581 may correspond to the number of players who make a cut that is the number of strokes relative to par from the lead. The target cut 582 can correspond to the number of players who make a cut closest to the set value, whether above or below that value. If the player values are the same, whether above or below, all players above the value are considered "uncut" and all the remaining players have the player status of "cut". Including amateurs 583 can correspond to whether to include amateurs as part of the cut rule. If set, the participating amateurs become part of the cut rule. If not set, amateurs are not included in the cut rule. Including amateurs 583 can be selected in addition to other components of the cut rule. It will be understood that if selectable settings are included, different and / or additional settings may be provided.

[0219] The round management panel 570 can also include a round information saving element 585 that gives the user the option to save or cancel changes made to the round state and / or cut configuration. In one embodiment, when a cut rule definition is saved for a round, the cut rule may be used for a live projection cut presentation in the STTM system. However, the round engine 501 may be configured not to set the player status as defined above until the user executes a cut rule option.

[0220] The round management panel 570 can also include one or more elements configured to interface with the user the operation of the round engine 501 regarding the 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 a playoff for a selected round. FIG. 6G shows an exemplary user interface of the round engine 501 configured to interface with the user various operations of the playoff round creator 586.

[0221] The playoff round creator 586 can include various elements for defining a playoff round. For example, the playoff round creator 586 can include one or more definable elements selected from (a) playoff type 587, (b) playoff number 588, (c) determined position 589, (d) start 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 can be configured to include a plurality of selectable playoff types for selection via a playoff type element 587, such as one or more playoff types selected from "sudden death", "number of holes", and "holes / sudden death". "Sudden death" corresponds to a playoff format that starts from the first playoff hole and is played until a player participating in the playoff has a better stroke score than the other players participating in the playoff. When two or more players are playing, the player who scores higher than the best score of that hole drops out. "Number of holes" corresponds to a playoff format in which all players participating in the playoff play the number of holes defined in the following starting hole order. If there is a player with the best score, that player wins and the playoff ends. If the same score is reached after the determined number of holes, the playoff repeats the determined number of holes. This process continues until a player has a better score than the other players in the playoff. In this type of playoff, multiple players may drop out if they do not score better than the best score. "Holes / sudden death" corresponds to a playoff format in which all players participating in the playoff start a playoff in which they play the number of holes defined in the following starting hole order. If there is a player with the best score, that player wins and the playoff ends. If there is the same score after the defined holes, the playoff enters sudden death as defined above.

[0223] The playoff number element 588 is operable to set or be set to a playoff number that enables the user to remember multiple playoffs for a round. The determined position element 589 is operable to define or be set to define the position of the player playing in the playoff. For example, the determined playoff position can include position 1 when multiple players are tied for first place or position 3 when multiple players are tied for third place.

[0224] The start hole sequence element 590 may define or be operable to define the hole at which the playoff is first played. In the case of the playoff format of "number of holes", the start 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 the "sudden death" playoff format in cases where a winner is not identified after the holes of the start hole sequence are completed.

[0225] The playoff save element 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 start element 594 may be operable to start the playoff. In one embodiment, the playoff may not be started in the round generator until play is completed in the selected round. In one example, the playoff may require verification that the previous round has been completed. In another embodiment, the playoff may be started before the previous round is completed.

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

[0228] As introduced above, the companion device can be used by a scorer to perform the scoring function. The scorer may include a caddy, a player, or another person watching the play. The companion device can run the ST application. The companion device may comprise a wireless data communication transceiver configured to wirelessly transmit score data, which may include event data, to the STTM system component. During play, each group can have an assigned companion device that the scorer uses to collect score data. The score data is transmitted to the management system, which is configured to process data received from multiple companion devices during play. The companion device can be configured with various wireless communication technologies as described above, including short-range and / or long-range communication with devices of the STTM system. The companion device can be configured to communicate with a tracking module to trigger and / or define data collection events that can be used to officially score a player's round. For example, the companion device can be carried by a scorer accompanying a group of players or a scorer observing the play. In various embodiments, the companion device may not be configured to communicate with the 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 can 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 the collection of event data (e.g., event capture, location / place determination, or related data for processing and determination of the same by the companion device or another processing device). In one embodiment, the tracking module may be configured to receive an instruction for event capture. The instruction may be sent by the companion device or the management device. For example, the companion device and / or the management device may be operable to be network-connected to a plurality of tracking modules or, if not, provide an instruction to the plurality of tracking modules and / or receive an instruction or data from the plurality of tracking modules. It should be understood that the management device may include data to or provide data to the location system.

[0230] A scorer using a companion device typically accompanies the player whose score the scorer is tracking. However, in some embodiments, the scorer can view the player remotely via a live or delayed feed. If the scorer is also inputting events that set a timestamp for an address or when the ball was hit, it can be paired with the position of the tracking module to provide a proxy for the position of the ball following a previous shot or the starting position of the ball for the current shot. The feed should be live or have an accurately known delay to accurately link the position of the player to the position of the ball. In a remote viewing use case, the tracking module can be configured to communicate with a management device or an intermediate relay device via an appropriate communication protocol that may include a short-range or long-range communication protocol depending on the proximity of the management device or intermediate relay device to provide its location data or calculation parameters. In a configuration where the position of the tracking module is subject to network-side calculations by other devices, the other devices can communicate with the management device directly or indirectly.

[0231] An ST application or a companion device (which may be local, remote, web-based, or cloud-based) that runs and / or accesses the ST application may be utilized by a scorer to score one or more rounds of golf representing a golf tournament event. The collected scoring data may be stored or transmitted by the companion device as discussed in more detail elsewhere in this specification. References to the 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, the scoring data may be transmitted immediately or subsequently to a location system and / or one or more management systems for an application 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. The 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 fans to consume alone or with other data, a surface web platform, etc. In various embodiments, the scoring data may be distributed or made available for use or integration with a web app, mobile app, or other application for public or private viewing, analysis, or archival storage.

[0232] The ST application may be configured for multiple selectable score level operations. For example, in a stroke level operation, the scorer can record a stroke using the ST application when the stroke occurs without using the location function of the tracking module or without performing the utilization and / or incorporation of the tracking module described herein.

[0233] When using the tracking module to obtain location information, the ST application or other STTM system applications and services can combine the location information with stroke level data. In laser operator level scoring, the scorer may use the ST application to record a stroke without additional location information, or through a manual laser pointing device such as those used by PGA Tour laser operators, or through the operation of an automatic laser system that tracks or continuously tracks the position of the ball throughout the round, the position of the player may be tracked through the tracking module for use in combination with laser position tracking. The 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, may be combined for analysis to achieve higher accuracy, or one location technology may be used as a backup or reference for another location technology. In one embodiment, the companion device and the ST application can be configured such that one scorer can collect stroke level data for all players in one group.

[0234] In one embodiment, the companion device, via the ST application, may have specific event data such as (a) par values for a specific course, (b) hole sequences of the course (which may be associated with par values), (c) predefined starting locations (not only selectable locations on the "starting location" screen, but may also include location indicators), (d) score levels of events (only recording strokes, or utilization and / or incorporation of location tracking, e.g., GPS, UWB, BLE, Wi-Fi®, cellular, etc., distance meters, laser operators, or combinations thereof), (e) course names, (f) player names within a group, player numbers within a group, player images, assigned groups such as headshots, multiple groups, or player group data for all player groups of an event, or (g) combinations thereof, pre-loaded or configured to be accessible. In one example, the ST application is at least partially executed in, for example, a cloud-based environment, and the above event data is automatically provided to the companion device at startup or the like. If the event is implemented on multiple courses, the course data for a specific course or multiple 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 be automatically provided with round details, including group updates, group assignments, event changes, event notifications, or details of other rounds.

[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 user interface of the companion device to input group location data in any suitable way, such as input to a provided field, selection from a list of displayed options, etc. In one example, when the players of a group are at the tee box, the scorer inputs or selects "tee". In yet another example, when the first caddie or player of a group arrives at the ball of a player on the fairway, the scorer can input or select "fairway". In yet another example, when the first caddie or player of a group arrives at the ball of a player around the green, the scorer can input or select "green".

[0236] The outputs 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, the grouping output may be sent to the ST application for input into one or more groups to which the companion device is assigned.

[0237] As introduced above with respect to FIG. 3, in various embodiments, the locations of groups and / or players can be automatically tracked via location tracking technologies and related location networks, such as GPS, Wi-Fi®, RFID, BLE, UWB, NFC, cellular, etc. For example, the ST application can incorporate geofencing to trigger changes in the location of a group at a pre-defined boundary. Geofencing may also be applied by other STTM system applications by tracking the location of the companion device and / or tracking module.

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

[0239] In one example, the scorer can also input when the player addressed the ball. This can be input as an event, for example, when it occurs when the player first addresses the ball, or it can be input as a toggle. In the case of a toggle, the user interface of the companion device can include an "Address" button that the scorer presses when the player is facing the ball. The scorer can then press the "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 indicating part, 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, it is interpreted that the ball has been 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 together in real time after the shot has been taken, or may be stored locally for later transmission. For a shot using a tracking module, when collecting location data such as location coordinate data, the ST application may be configured to associate the tracking module assigned to the player with the player's name. When the scorer indicates that the ball has been hit, the position of the tracking module is captured and recorded as described elsewhere in this specification. In some configurations, the capture of the position of the tracking module may be triggered via interaction with the "Address" button.

[0240] In addition, the companion device may be configured to score various stroke types such as drops, penalties, provisional, etc. For example, the companion device can query the scorer or request shot type input if applicable. If the scorer selects "drop", the companion device can prompt the scorer to indicate whether there was a penalty. If the scorer selects "penalty", the companion device can prompt the scorer to indicate whether there was a drop. If the scorer selects "provisional", the companion device can prompt the scorer to indicate whether the provisional was used on the next stroke. If so (yes) and the shot location was "from the tee", a penalty stroke may be automatically added to the player's score. If not (no) and the shot location was "from the tee", the companion device can prompt the scorer for an indication of 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 a 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 continues to press until the ball is hit, and releasing the button, rather than "pushing" it, 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 an address, a location timestamp, and a shot hit. For example, a two-stage "Shot Hit" indicator can be used to indicate an address and / or a location in a first stage and a location and / or a shot hit in a second stage. In one configuration, the scorer can press a two-stage indicator button when the player is at the address position and release the indicator button when the ball is hit, with pressing setting the location timestamp and releasing being interpreted as the ball having been 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 can present buttons, swipe bars, fields, etc. that the user can interact with to indicate whether the ball is in the hole. In one example, a two-way swipe field is presented to the scorer, and the scorer indicates "yes" or "no" by swiping the field in the desired direction of indication. In one embodiment, if the scorer fails to interact with the relevant indicator within a predetermined number of seconds to indicate that the ball is "in the hole", a "in the hole" prompt may be displayed, and the ST application may receive the lack of indication as a null response having a value that the ball is not in the hole. In another configuration, the ST application may similarly be configured to take the lack of indication as an indication that the ball is in the hole. The scorer can have the option of indicating a null response or allowing a time-out. For example, the scorer can set a right swipe as in the hole, a left swipe as out of the hole, and a time-out as 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 where the scorer can select the same player or the next player to record the same shot. When the scorer indicates that all players are in the hole, the scorer can be prompted to show a button or other indicator to proceed to the next hole or made available. In another example, when the scorer indicates that all players are in the hole, the ST application can automatically proceed to the next hole.

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

[0244] Referring to FIGS. 7A - 7V showing various user interfaces of the ST application 700 according to various embodiments, the scorer can interface with a companion device to provide an explanation of the player. The interface can include various data input screens where the scorer can enter data. The screens can include pre - defined selectable options presented, for example, in a list box, checkbox, dropdown, input stepper, text input field, etc. The ST application 700 may be pre - programmed to present one or more descriptive categories, and each category includes a plurality of descriptive options that the scorer can select regarding a selected or identified player. In some embodiments, the ST application 700 can include a field where the scorer can enter a text explanation. The explanation can be entered into one or more of the pre - defined descriptive categories selected by the scorer. In some configurations, the scorer can input descriptive information or define descriptive categories either by voice or text. The provision of fields for descriptive input can be done in addition to, or instead of, one or more pre - defined descriptive categories and / or a plurality of options within such descriptive categories. In one embodiment, the ST application 700 may include, incorporate, or otherwise be configured to input an image of the player, such as a photo application. The ST application 700 can associate the 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 the clothes the player is wearing. In this or another example, the ST application 700 can display the captured image of the player by the companion device or another device that directly or indirectly transmits the image to the companion device.

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

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

[0247] By selecting the description button, the ST application 700 can display one or more description categories 705. In the example shown in FIG. 7C, the user interface displays a context box that includes a plurality of descriptive categories 705 for the scorer to select from. The scorer can select a descriptive category from the available options and present multiple selectable descriptions. For example, in FIG. 7C, the scorer is presented with three descriptive categories 705 related to clothing: "Player Shirt", "Player Pants", "Player Cap". When "Player Shirt" is selected, a plurality of descriptive features 706 related to the player's shirt are displayed, from which the scorer can select. The scorer can select a descriptive category that can easily distinguish the player. For example, the scorer can select one or more pieces of clothing that the player wears distinctively from other players so that it is possible to distinguish which player is taking a shot even from a distance. If further clarification is needed, optimal descriptions can be made. In FIG. 7D, the descriptive features relate to color. In this example, the descriptive features also include additional characteristics that are identified as optional in this example, from which the scorer can further define the player shirt. In the illustrated interface, the scorer has selected green as the color of the player shirt and light as the optional description. In some embodiments such as the illustration in FIG. 7D, the user interface can require the scorer to confirm the selection with the confirmation button 707. The selectable descriptive features within "Player Pants" and / or "Player Cap" may be similar to or different from those within the "Player Shirt" description category. The description categories relate to clothing items in the illustrated embodiment, but in some examples, different description categories or descriptive features may be provided in addition to or instead of clothing items, such as shoes, clubs, bags, brands of items, etc.

[0248] In various embodiments, the ST application 700 may be configured to receive descriptive input regarding 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 the second descriptive category (player pants) of Vincent Johnson in the same manner as described above with respect to FIGS. 7B-7D. FIG. 7E also shows that the scorer has entered descriptive features for two descriptive categories (player pants, player cap) of player Mahindra Ratchman and one descriptive category (player shirt) of player Jared Garcia.

[0249] The ST application 700 may include a scoring function that enables the scorer to enter a plurality of details regarding a play including club type, shot position, stroke, penalty, scoring, lie, and the like.

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

[0251] Companion device 12 that executes ST application 700 may be configured to receive accurate input from the player hitting the ball. In some embodiments, a "Shot Hit" button 712 may be provided that the scorer can tap at the instant the player hits the ball. To display the "Shot Hit" button 712, the scorer can select the name of the player indicating "Shot Hit" from the group screen 710 (FIG. 7F). Referring to FIG. 7H, the user interface includes a "Shot Hit" button 712 that the scorer uses to indicate a shot by keeping a finger pressed on the button before the ball is hit and releasing the finger at the instant the ball stops moving. For example, when the player addresses the ball and is ready to take a shot, the scorer keeps the "Shot Hit" button 712 pressed. Then, at the exact instant the player takes the shot, the scorer releases the button to indicate that the shot has been taken. This action sends a signal to the system to record the position of the tracking module at that instant, which corresponds to the position of the player. This location information may further be associated with the player's club selection. This data may be stored in the tracking module, the companion device, or associated memory, or may be sent to the management device at that time when the scorer indicates that the player or group has completed the hole, periodically, at scheduled intervals, based on the proximity of the tracking module or companion device to the management device, or based on its storage capacity. As described in more detail elsewhere in this specification, the location information can be input into an application configured to render a graphical display of a digital stroke trail indicating the details of the shots of a round.

[0252] In some embodiments, when the scorer releases the "Shot Hit" button 712, the scorer will then be required to enter the landing position of the ball relative to the golf course (e.g., fairway, rough, green, out of bounds, sand, hazard, repair area, 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 alternatively, the user interface may be provided with location buttons that the scorer uses to select from a plurality of locations or to enter a location into a provided field. In the embodiment shown in FIG. 7I, when the "Shot Hit" button 712 is released, the user interface displays a "In the Hole" prompt 713, whereby the scorer can indicate whether the ball is in the hole. As shown, the interface of the in-the-hole prompt 713 requires a directional swipe, left for "No" and right for "Yes". However, other interface buttons or methods may be used. Referring to FIG. 7J, after the scorer indicates whether the ball has gone into the hole, the user interface can return to the group screen 710 that displays the recorded shots. The group screen 710 can also include a notification or indicator 714 indicating that the player is currently playing on the hole. As shown, the text under the player name has changed to "Starting Location" indicating that the player is in the middle of a shot on the hole. This indicator 714 can also act as a button to trigger the collection of location information by the tracking module when the player takes the next shot, in a manner similar to that described for the first shot.

[0253] Referring to FIGS. 7K and 7L, to record the player's second shot, the scorer may select the "starting location button" 715 within the indicator 714 from the group screen 710. This selection may present a "starting location" screen 716 that includes a plurality of locations that the scorer can select to indicate where the player is hitting the shot. As shown, the scorer can select fairway bunker, fairway, first cut, natural area, deep rough, pond, greenside bunker, fringe, other, or green. Since the player has not taken the first shot, the option to select "tee" is not available in this embodiment. However, selecting "provisional" or "penalty drop" enables the selection of "tee".

[0254] In some embodiments, the course may be mapped before or after play, the recorded location of the tracking module corresponding to the player and the ball may be overlaid on a map, or the STTM system may determine the relative position 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 surveying techniques, global satellite communication systems (GPS, GLONASS, BEIDOU, GALILEO & QZSS), LIDAR, or other suitable methodologies may be utilized. The recorded location information may be collected or converted directly or indirectly into such a coordinate or grid system, and / or overlay techniques may be utilized.

[0255] After entering the starting location on the "Starting Location" screen 716, the user interface may display the group screen 710. As shown in FIGS. 7M and 7N, the location indicator 714 may change to what the scorer has selected, for example, the fairway. Next, the scorer selects the player name, displays the "Shot Hit" button, thereby indicating to the player the moment the ball is hit, and then, for example, in the same manner as described above, can indicate whether the ball has gone into the hole.

[0256] Recording the time and position 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 "Green" until the ball enters the hole. In another embodiment, the user interface can allow the user to select a different location after a subsequent shot, for example, rolling off the green, without entering the hole. FIG. 7O shows a group page 710 where the first two players have finished the hole and the third player is on the green. When it is the third player's turn to putt, the scorer selects the player's name and continues to press the "Shot Hit" button displayed when the player is attempting to putt, releasing it when the player has putted the ball, and recording the time and position of the putt through the position of the tracking module as described with respect to FIG. 7H. Thereafter, the user interface may display a "In the Hole" prompt that can be used by the scorer to record whether the ball has entered the hole, which may be similar to that described with respect to FIG. 7I. If the ball does not enter the hole, the scorer records the next putt as before. If the ball enters the hole, the ST application 700 records that the player has finished the hole and the scoring process is restarted from the next tee box. In one example, after the scorer has recorded that all players in the group have put the ball into the hole, the 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 can indicate to the scorer that the hole is finished and prompt the scorer to move to the next hole.

[0257] Figures 7P through 7V show PDP scoring according to various embodiments. In these examples, the scorer records, on the "starting location" screen 716, not the location where the original shot landed, but the "starting location" where the next shot will be taken. However, in some embodiments, the ST application 700 or system may additionally provide for input of the landing position of the previous shot by input into a text field, selection from a list of areas around the hole such as the "pond" provided on the "starting location" screen 716, or display of a map where the scorer indicates the landing position of the ball on the screen.

[0258] Figure 7P shows recording of a second shot from a tee recorded as provisional. Using the "starting location" screen 716, the scorer selects "provisional" and then, in this example, selects the starting location which is the "tee". Thereafter, the display returns to the group screen 710 and "provisional" is displayed as a location indicator. Thereafter, the scorer can select the player's name and score the shot as described above.

[0259] Referring to Figure 7Q, when a provisional shot is recorded, "provisional" may remain in the position of the position indicator 714 under the player's name until the scorer selects the player's name to record the position of the next shot. Figure 7R shows a prompt 720 displayed after the player's name is selected, which asks the scorer to indicate whether the player is using the provisional shot. If the scorer indicates that the player is not using the provisional shot, scoring proceeds as normal. If the scorer indicates that the player is using the provisional shot, a penalty stroke is given and is displayed on the group screen 710 as shown in Figure 7S.

[0260] Figure 7T shows the recording of 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, in this example, selects the starting location which is "Deep Rough". Thereafter, as shown in Figure 7U, the display returns to the group screen 710 and "Penalty Drop" is displayed as the location indicator 714 under the player's name. Thereafter, the scorer can select the player's name before the player drops the ball. For example, referring to Figure 7V, the scorer is presented with a penalty drop prompt 721 that provides a "Ball in Play" button 722 for the scorer to use to indicate when the player drops or retires the ball. Thereby, the penalty stroke is evaluated and further the position and time of the shot continue to be recorded as described above.

[0261] A free drop can be recorded in a manner similar to recording a penalty drop, except that "Penalty Drop" is selected from the "Starting Location" screen and the penalty is not accessed.

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

[0263] The data management system 50 can include a data management tool 800 that includes interface elements, display elements, or related operating 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 mismatch panel 805, (f) a hole graphic display 806, (g) a group score card 807, (h) stroke details of team players 808, or (i) an all-group presentation 809. FIG. 8A shows an exemplary user interface of a data management tool 800 for use with a data management system 50 that provides the elements listed above in a presentation block. In various embodiments, the page layout of the elements is configured to create connections between the blocks and / or data elements therein. For example, selecting an element within a block may establish a connection to another block. In a further example, the other blocks with established connections may be updated in an appropriate presentation, as will be described in more detail below. However, it will be understood that the elements, related components, and their data that are operable to provide the operation of the data management system 50 may be provided in many formats, and the present disclosure is not limited to the specific arrangements and combinations of the elements and user interface components depicted herein.

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

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

[0266] The course selector 803 can include a selectable list of one or more courses available for viewing and managing related data for the selected event and round. In one example, the course selector 803 consists of a drop-down list of all courses available for the selected event and round. The selection of a course can be operable to cause the presentation block to present or cause the presentation of the data of the course of the selected event and round. In one example, when multiple courses are being played for an event and round, the default course may be set to the host course. In another or further example, the course selector 803 can include a selectable option for selecting all courses. In such an example, by selecting all courses, the data of all courses within the presentation block is presented in one combined presentation.

[0267] The editing mode notification 804 can include display elements that constitute a notification presented when editing is performed in any of the presentation blocks in which the scoring data has been edited. The editing mode notification 804 may be selectively programmable to provide a notification for any desired edit. For example, in some embodiments, the notification is not displayed if changes are made only to the play management block described later. In one example, the notification is output when the data element value exceeds or falls below a predefined threshold, or is within or outside a predefined range. This notification may be interactive such that the user can interact with the notification, such as by selecting all or part of the notification, and accept the changes. In one embodiment, a separate interface element is provided through which the user can interact 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 the user changes or inputs data to a presentation block, the data management tool 800 may automatically enter the editing mode. While in the editing mode, the data may not be sent to the downstream client or its data viewing platform. However, when the user accepts all current edits, the editing mode is turned off, and the data including the changes made during the editing mode may be sent to the downstream client including the data viewing platform.

[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 can include various navigation functions. For example, the hole graphic display 806 can include one or more of a zoom function that allows the user to selectively zoom in and out of the graphic, a graphic rotation function that allows the user to selectively rotate the graphic about the horizontal axis, vertical axis, and / or other axes, and / or a variable centering function that allows the user to move the center of the graphic within the presentation panel. In one example of the zoom function, a quick zoom is provided that can zoom in green, zoom out to display the entire hole, and / or zoom out to display the entire course. In one embodiment, the graphic is oriented in a way that allows maximum visibility from the tee to the green, such as an overhead view, a tee view, a green view, etc. The hole graphic display can include various display distances to the hole. For example, one or both of the yardage distance of the scorecard or the actual yardage distance between the tee and the pin set for the round may be displayed. In one configuration, hole setting information may be displayed on the hole graphic. For example, current hole information for each round, such as one or more of the tee position, pin position, and / or fairway center point of the holes of the course, may be displayed. In one embodiment, the graphic display may be configured to display all players of a group at once in response to a request from the user, for example, via interaction with an "display all group players" element.

[0270] Stroke or ball location coordinates, such as those collected through the operation of the tracking module and companion device, may be plotted on the hole graphic display 806. For example, the hole graphic display 806 may include a plot of the ball position relative to the hole. For example, the ball position may be plotted on the graphic display to indicate the end position of a team player's stroke. For consecutive strokes including location coordinates, a line 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 a line from these points to the coordinates of the player's stroke on the hole or to a stroke having an end point. In one example, the distance of the plotted ball position from the tee, the distance from the last stroke, and / or the distance to the pin may be displayed or provided as defined selectable format options.

[0271] Additional features may be provided for managing stroke coordinates, such as entering the position of a received stroke by the user, moving an existing position assigned to a stroke, creating a stroke along with its position, displaying all GPS or other location coordinates collected for a team player, and / or deleting a stroke along with its position. In one example of the above features where a pan is present, the hole graphic display 806 may be configured such that the user can "lock" a stroke relative to the pan.

[0272] In one embodiment, the above features include displaying all GPS coordinates and / or other coordinates collected for a team player that are not related to a stroke, such as a pan. By displaying all coordinates, the hole graphic display 806 can be configured to associate one location with a player's stroke.

[0273] In various embodiments, selecting a group from all group presentations 809 may cause data related to the group to be entered into the group scorecard 807. In one example, the hole graphic display 806 may similarly pop up with shot data and / or ball location data related to the group. In one embodiment, when a particular hole of a group is selected via the group scorecard 807, the hole graphic display 806 zooms in on the selected hole and displays the plotted ball positions and shot trajectories of the team players within the group.

[0274] FIG. 8B shows an exemplary interface 810 of the group scorecard 807 presented by interaction with the group scorecard data management tool 800 or accessible via interaction with the group scorecard data management tool 800, all or part of which may be available in the respective presentation block view. Various elements of the group scorecard 807 may be displayable and / or editable via the operation and functionality of the group scorecard 807, as will be described in detail below for each element. The group scorecard 807 may include various data elements such as one or more of (a) team player name 811, (b) stroke event 812, (c) number of strokes 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) total strokes, or (l) official strokes 821.

[0275] The team player name 811 can list the team players within the group. For example, the player may be presented by surname, given name. In one configuration, the team player name 811 may not be editable via the group scorecard component of the data management tool 800.

[0276] When the flag is set, the stroke event 812 can present the last stroke event received from a score tracking system or, in one example, a verification system. Various stroke events may be presented, such as club selection, address to the ball, shot hit, provisional, practice, final, within the hole, etc. In one configuration, the stroke event 812 may not be edited via the group score card component of the data management tool 800.

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

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

[0279] Today 815 can present the par - relative score for that round. In one configuration, today 815 may not be edited via the group score card component of the data management tool.

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

[0281] Score Out 817 can present the total strokes of the scores entered at the front 9. In one configuration, Score Out 817 may not be directly edited via the group score card component of data management tool 800.

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

[0283] Score In 819 may present the total strokes of the scores entered at the back 9. In one configuration, the scores of 819 may not be directly edited via the group score card component of data management tool 800.

[0284] Stroke Total 820 can display the total strokes of the round. In one example, Stroke Total 820 may be displayed only when data is entered into Score Out 817 and Score In 819. In one configuration, Score Total 820 may not be directly edited via the group score card component of data management tool 800.

[0285] Official Strokes 821 can present the strokes received for the team players at all holes that are officially flagged. In one configuration, this element can be edited by the user to indicate that no further editing will be done for any stroke of any hole of the player.

[0286] FIG. 8C shows an exemplary interface of the stroke details 808 of a team player of the data management tool 800, and the interface is configured to interface its operation to the user. The interface is presented via interaction with the stroke details 808 element of each presentation block view of FIG. 8A or can be accessed via interaction with the stroke details 808 element of the team player. The elements of the stroke details 808 of the team player may be displayed. In the operation of the stroke details 808 of the team player, the user can edit various elements. In some embodiments, when a player is selected in the group score card 807 or the full group presentation 809, the data elements of each selected group are input into the interface of the team player stroke details 808.

[0287] When selecting a team player for presentation and / or stroke editing using the stroke details 808 of the team player, the hole graphic display 806 may be default set to display a course view, the current hole, the next hole, the first completed hole, the last completed hole, or a full course view. In one embodiment, by selecting a specific hole from the group score card 807, for example, hole 816 from the front 9 holes by hole or hole 818 of the front 9 holes by hole (FIG. 8B) from the data element view of the hole, the stroke details 808 of the team player presents the stroke details of the player for the specific hole. Thus, the data management tool 800 can be configured to enable the user to selectively view the strokes hole by hole using the group score card 807 or view the stroke details of the hole via interaction with the team player stroke details 808.

[0288] In one example, by viewing the team player's stroke details 808 for the hole, the hole graphic display 806 presents the display of the hole. The graphic may be oriented from left to right such that the tee position is on the left and the green is on the right. As described above, functionality such as zooming in and out of the graphic may be provided. As an example, a quick zoom operator may be provided so that the user can quickly zoom to various areas of the hole, such as the tee box, fairway, hazard, green area, or a particular selected shot. The functionality may also include moving the graphic within a static display area, e.g., within any zoom value, to change the longitude and latitude of the view. Yardage can also be displayed with respect to the set positions of the tee and the pin. Other yardages can be selectively displayed within or relative to the graphic, as described above.

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

[0290] The team player name 822 can include a list of all team players within a group. For example, when selecting a group from the full group presentation 809 or the group score card 807, the team players of that group may be input into the team player name 822. The presentation may display data regarding a single player, which may be defaulted to any player, such as the last player for whom a stroke event was recorded or completed the hole, or the first player in a predefined order of tee-off. In one configuration, the team player name 822 may not be editable via the 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's stroke details 808, enabling the user to input an integer.

[0292] The accessed stroke 824 can correspond to the number of strokes that are counted towards the hole score of the team player who received that stroke. In one configuration, the accessed stroke 824 is editable via the team player's stroke details 808, for example, enabling the user to input an integer.

[0293] In one embodiment, the user can create a stroke 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. When 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 edit the timestamp 826 to set it either to the time after the previous stroke or the time before the proceeding stroke. In one example, when a stroke is created, the default stroke accessed is 1.

[0294] In one embodiment, the user can delete a stroke. When a stroke is deleted, the data management tool 800 may be configured to automatically re-number the remaining strokes sequentially. If the stroke is deleted and it is a stroke within the available strokes where the "within hole" flag is available rather than a stroke within the flagged hole 831, the data management tool 800 may recalculate the score with the new total of the accessed strokes. When a stroke with the "within hole" flag is deleted, the data management tool 800 may be configured to clear the calculated score. As will be described later, the "within hole" flag may be set or deleted by the user. After deleting a stroke that includes the "within hole" flag, the user can set the "within hole" flag for another stroke for which the score corrected by the data management tool 800 is calculated. In one example, when deleting a stroke flagged as "within hole", the user may be prompted to flag a stroke with the "within hole" flag.

[0295] The stroke event 825 may correspond to the latest received stroke event. The stroke event 825 may enable the 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 the ball, shot hit, preliminary, final, or within hole corresponding to such events collected by the ST application via the companion device and the tracking module.

[0296] The timestamp 826 can correspond to those of the stroke events 825, such as the latest stroke event 825. In one configuration, the timestamp is editable via the stroke details 808 of the team player, enabling the user to edit the field in the time and date input format.

[0297] The stroke type 827 can correspond to stroke type identifiers such as strokes, penalties, or drops, which correspond to such stroke types collected by the ST application via the companion device. In one configuration, the stroke type 827 is editable by the data management tool 800 to change or add stroke types from a list. In one example, by interacting with the stroke type 827, a drop-down including a list of available stroke types is displayed, allowing the user to select one of the stroke types to set. In various embodiments, the data management tool 800 can automatically apply various rules to the editing of the stroke type. 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 1. If the created stroke type is "penalty", the stroke number 823 may increment up to the amount identified for the accessed stroke 824.

[0298] Location 828 can correspond to the graphic location of a stroke determined by the location methodologies described herein, such as a tracking module, location system, operation of a rangefinder, manual input via indication of ball position relative to a displayed map, or other location methodologies used by an STTM scoring system. In one configuration, Location 828 can be edited to change the location from a list of available descriptions of the location of the golf course being played, such as tee box, fairway, rough, first cut, hazard, pond, out of bounds, green, etc. In one example, interaction with a location data element may display a drop-down including a list of available locations of the golf course that can be set for the location.

[0299] Provisional 830 can be used to identify whether a stroke is provisional. In one configuration, the provisional field can be edited with "yes" or "no" value options regarding whether the stroke is a provisional stroke.

[0300] In-Hole 831 is used to identify whether the ball has gone into the hole as a result of a specified stroke. In one configuration, the user can set or remove a flag when a stroke is considered in-hole. Data management tool 800 may automatically apply various rules to the "in-hole" flag. For example, if the "in-hole" flag is attached to the last stroke with the largest stroke number, the score may be calculated and stored based on the sum of all strokes accessed. If the "in-hole" flag is attached to a stroke that is not the last stroke with the highest stroke number, that stroke is set as the highest stroke number and the numbers of all other strokes are sequentially changed.

[0301] Referring to FIG. 8D, in various embodiments, a stroke event review viewer 832 may be provided. For example, each stroke of the player's stroke details 808 is operable to optionally expand to display additional related stroke events. In the illustrated viewer, stroke events for a stroke are input into the stroke event 823 element. As shown, the stroke events for the stroke number include club selection, address, shot hit, setup, and finish. Thus, as a result of the stroke, the player did not hold the ball. In various embodiments, the stroke details received from a companion device are marked as "setup" and are subject to review via the operation of the data management tool 800 or verification system described below, and upon successful review, the stroke details can be set to "finish". In one configuration, the fields of the stroke event review viewer 832 cannot be edited except for the timestamp field. The stroke event review viewer 832 may be configured such that the user can reorder or rearrange the order of the stroke events. The stroke event review viewer 832 may be configured such that the user can collapse the review of the stroke events, such as presenting only the latest stroke event.

[0302] FIG. 8E shows an exemplary interface of the full group presentation 806 of the data management tool 800, which is configured to interface with the user and their operations. All or part of the interface may be presented in each presentation block view of FIG. 8A, or may be accessible via interaction with the full group presentation 806 provided therein. Various elements of the interface may be displayable and / or editable via the operation of the full group presentation 806.

[0303] The full group presentation 809 may be configured to display the selected round and may include displaying only the selected round. In one example, the full group presentation 809 is configured to display information for the selected course, or if selected, all courses of the tournament. In one configuration, the display may be scrollable and / or each column of data may be sorted either in ascending or descending order based on the information available in the column. In one configuration, none of the fields of the full group presentation 809 may be directly edited via the full group presentation 809. In one embodiment, the presentation of the full group presentation 809 may include a notification regarding the name of a team player if the team player's scorecard has been flagged as "official" via a verification system, for example, described in more detail elsewhere in this specification.

[0304] The full group presentation 809 corresponds to (a) the group number 832 - the number assigned to the group, (b) the course 833 - the course on which the group number is playing, (c) the starting hole 834 - corresponding to the first hole from which the group started based on the grouping of the round, (d) the tee time 835 - corresponding to the starting tee time of the group, (e) the rank 836 - corresponding to the expected ranking of the players in progress during the play of the ongoing round, (f) the team player name 837 - corresponding to the identification of the player, (g) the total 838 - corresponding to the total of the current par relative scores of that event, (h) today 839 - corresponding to the par relative score of that round, (i) the front 9 holes by hole score 840 - corresponding to a list of hole-by-hole scores for the first 9 holes, (j) the score out 841 - corresponding to the total strokes of the scores entered for the front 9, (k) the back 9 holes by hole score 842 - corresponding to a list of hole-by-hole scores for the back 9 holes, (l) the score in 843 - corresponding to the total strokes of the scores entered for the back 9, or (m) the total strokes 844 - corresponding to the total strokes of the round and is displayed if there is data for score out 841 and score in 843, and can include various data elements such as one or more of the above.

[0305] FIG. 8F shows an exemplary interface of the data mismatch panel 805 of the data management tool 800, which is configured to interface its operation to the user. All or part of the interface may be presented in the respective presentation block diagrams of FIG. 8A or may be accessible via interaction with the data mismatch panel components provided therein. Various elements of the interface may be displayable and / or editable via the operation of the data mismatch panel 805.

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

[0307] In various embodiments, the data inconsistency panel 805 can be operated to improve the user experience and efficiency. For example, the rows of data may be scrollable. Also, the columns of data may be sortable either in ascending or descending order based on the information available in the column. In one configuration, the data inconsistency panel 805 can provide an interface element that can flag a warning as reviewed and operate to remove the warning from the presentation. In one example, the data inconsistency panel 805 enables the user to review all warnings flagged as reviewed, review errors and warnings for each group, hall, or team player, reset and display all errors and warnings if any have been set as reviewed and deleted, scroll through all messages for each panel if there are messages that cannot be displayed in the initial view, or turn on or off the rules for all or selected error and / or warning message rules. In one example, some fields may not be editable.

[0308] In various embodiments, the error message 853 and warning message 854 can identify various identifying elements with respect to the player, time, and / or location to which the message pertains. In the illustrated embodiment, data elements of team player name 855, hall number 856, and group number 857 are presented. The data management tool 800 may be configured to analyze scoring data and / or location data and related procedures and automatically generate error and / or warning messages 853, 854 when an anomaly is identified.

[0309] Error message 853 relates to data loss and / or procedural anomalies regarding the recorded score and / or location data and is displayed in the error message 853 element associated with the identification information. There may be various error messages, for example, lack of location information, lack of stroke coordinates, lack of score, lack of score that may be displayed if there is a score gap between holes, the total of the accessed strokes does not match the recorded score, the score is recorded but there is no stroke, no penalty is recorded for the stroke with the provisional flag, the accessed stroke is 1, the time stamps of the stroke trajectory from hole to hole are not continuous, the first stroke is not from the tee position, after receiving the next stroke, the stroke is not marked with the final flag, after the team player completes the round, the team player is not marked with the official stroke mark, and one or more of the like.

[0310] Warning message 854 may be related to an event or lack thereof that is abnormal compared to the expected operation of a scoring system that may include a location system, detected by data management tool 800, and that may not yet be an error or whose error status cannot yet be confirmed based on available data. Warning message 854 may be displayed along with associated identification information. There may be various warning messages 854, for example, one or more of the tracked players are not synchronized with the strokes of other team players in the group, multiple consecutive drops by a team player, a drop without a penalty in the stroke trajectory of a team player, the coordinates of the stroke are not closer to the pin position than the coordinates of the previous stroke, there is a gap of more than 10 minutes between the strokes of a team player, multiple strokes include a position from the tee ground, an atypical score of a team player such as a double bogey or worse, an eagle or better, 5 minutes have elapsed but a certain stroke has not received coordinates, a team player was on the green but appears to be outside the green, the driving distance is less than 180 yards, more than 380 yards, etc., outside the normal distance range for par 4 or par 5, the stroke is flagged as being on a hole with a distance of more than 30 yards, the pin is not set and a team player's stroke on that hole is received, or the tee is not set and a team player's stroke on that hole is received, etc.

[0311] Referring to FIG. 8G, in various embodiments, the presentation blocks of the data management tool 800 described above with respect to FIGS. 8A-8F and / or one or more of its associated components may be configured to create connections therebetween. For example, the presentation block layout may be configured to create connections between block views of component elements. For example, with respect to related elements, when an element is selected, such as in one block view, or otherwise interacted with, such as when a selection is made, a connection is established to one or more other blocks, thereby updating the appropriate presentation within each block.

[0312] The presentation block may be configured to apply connection rules for the entire group presentation 809. In one embodiment, selecting the name of a team player causes one or more of the following: the group score card 807 to present the group to which the team player belongs, the hole graphic display 807 to present the current hole that the team player has not completed, the team player stroke detail 808 to present the strokes received at the current hole that the team player has not completed, and the data mismatch panel 805 to present all errors and warnings for the selected team player at all holes. In the above or another embodiment, selecting a group number may cause one or more of the following: the group score card 807 to present the selected group, the hole graphic display 806 to present the current hole, with the top team player in the group and the current hole that the team player has not completed as the default, the team player stroke detail 808 to display the strokes received at the current hole that the top team player in the group has not completed, or the data mismatch panel 805 to present all errors and warnings for the selected group. In any of the above embodiments or another embodiment, selecting a team player's hole can cause the group score card 807 to present the group to which the team player belongs, the hole graphic display 806 to present the selected team player and the selected hole, the team player stroke detail 808 to present the selected hole and the strokes received by the team player, or the data mismatch panel 805 to present all errors and warnings for that hole and team player, which may include warnings flagged as reviewed.

[0313] In any one or another embodiment of the above embodiments, when interacting with the group score card 807, connections with one or more other components of the data management system 50 may occur. For example, when selecting the name of a team player, the hole graphic display 806 may present the current hole that the team player has not completed, the team player stroke details 808 may present the strokes received at the current hole that the team player has not completed, the data mismatch panel 805 may present all errors and warnings for all team players selected at all holes, or the all-group presentation 809 may present the group or team player at the top of the presentation, and one or more of these may be caused. In yet another example, when selecting the hole of a team player, the hole graphic display 806 may present the selected team player and the selected hole, the team player stroke details 808 may present the strokes received at the selected hole by the team player, the data mismatch panel 805 may present all errors and warnings for that hole and the team player, which may include warnings flagged as reviewed, or the all-group presentation 809 may present the group or team player at the top of the presentation.

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

[0315] In any one of the above embodiments or another embodiment, the 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, by selecting the location coordinates assigned to the stroke, the selected stroke in the team player stroke detail component may be highlighted.

[0316] In any one of the above embodiments or another embodiment, the interaction with the data mismatch panel 805 may cause a connection with one or more other elements of the data management system 50. For example, by selecting an error or warning to be reviewed, the presentation of the group score card 807 may be updated based on the team players and groups identified in the error or warning message. In another example 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 a rationalized verification of a player's official scorecard against scores collected by a score tracking system. The verification system 70 may be configured to allow a user to modify the scores obtained from the operation of the score tracking system, if necessary. Also, by using the verification system 70, a user can quickly identify that the scorecard has been reviewed and officially flagged. In some embodiments, this official designation is sent or otherwise made immediately available on one or more data platforms, communicating to users of the scoring data that no further score editing will be received for each player. In one example, the fact that a scorecard has been officially flagged is retained for storage in a database, later distribution, internal verification, compilation with additional verified scorecards, analysis, or combinations thereof.

[0318] The verification system 70 may be configured for operation in various network environments as specified herein with respect to its various STTM systems / subsystems. For example, the verification system 70 can 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 an environment such as a browser or like a browser. For example, the verification system 70 can include a verification application having the ability to execute on multiple browser tabs with different settings. In a further example, the verification system 70 includes an edit tracking function that tracks edits made by the user to the verification system 70. These user edits are tracked as being associated with the particular user who made the edit. The tracking function of the verification system can be configured to save the edits tracked per user and make the tracked edits reviewable. For example, a reviewing user can access the verification system 70, view a list of users, and review details regarding the edits made by each user to the scorecard. In some configurations, the verification system 70 can enable the reviewing user to view the user's 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 enable the reviewing user to view edits by one or more types made by one or more or all users within a particular period or event.

[0319] Referring to FIGS. 9A - 9B, in one embodiment, the verification system 70 may be configured to generate two functional verification tools for score card verification. Each verification tool may be provided in one or more tabs, screens, pages, windows, or any suitable displayable arrangement having the functions described herein. The verification tools may be displayed separately or together, in whole or in part. In one example, the first tool panel may be configured to input the scoring data of the player's score card and compare it with a second score collection method such as an automatic or semi - automatic scoring method. Herein, the operation of the first tool may be referred to as blind verification. The second score collection methodology according to various embodiments will be described below with respect to the tracking system methodology, but it will be understood that this score collection methodology or variations of 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 that allows a user to input the score of a player's score card, and the input score is automatically compared with the scoring data recorded by the score tracking system. The second verification tool can output the total scores of players in a particular group, all groups, all players, or a desired combination thereof, along with the player rankings. In various embodiments, the verification tools can be placed in selectable tabs, and each tab contains a verification tool within the 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 uses for verifying a player's score card. The event selector 902 can include a list of selectable events. Interfacing with the event selector 902 can trigger a dropdown, list, or other selectable form of events for selection.

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

[0323] The cut line 904 may be provided to allow the user to view the current real-time cut data display. In some embodiments, the cut line 904 is only displayed if the selected round is the cut round. Viewing the cut line 904 can provide the user with insight into what changes are possible with respect to the cut. For example, changing the score of one player can cause multiple other players to either make the cut or not make the cut.

[0324] The group selector 905 can be provided to allow the user to select a group containing players for score card verification.

[0325] A player selector 906 may be provided that includes a list of selectable players within the 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 player's headshot may also be displayed.

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

[0328] System received scores such as scores received from a score tracking system, like the system received score, can be imported into the verification system 70. In some embodiments, the import of the score tracking system score may be performed automatically when the score is received, or may be performed later. The score data and related player data may be imported into the verification system periodically after each hole is completed, after a predetermined number of holes, when received, or when a player or group finishes a round, which may be instructed by the scorer via a companion device. For example, when the scorer indicates that a player or group has finished a hole or a round, the calculated score and the player name or player number associated with the data may be sent directly or indirectly to the verification system. In the illustrated embodiment, if the player selected on the score card is not flagged as official, for the purpose of blind verification, the system received score may be hidden or blank while the user enters the score.

[0329] In the example shown, the first verification tool 901 includes a comparison trigger 912 for causing a comparison between scores. For example, for blind verification, the user can interact with the comparison trigger 912 to initiate a comparison between the player score card and the system received score being verified. Before starting the comparison, the first verification tool 901 may not display the system received score. In some embodiments, the comparison may be initiated when one or all scores are entered, or when the system received scores are aggregated, 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 input into the hole field 914 juxtaposed to the corresponding hole field 910. Validity notifications may be displayed regarding the hole or associated scores to indicate score match, score mismatch, or both. For example, when an option to compare the score of a blind entry with the system score is triggered, the system score may be displayed and a valid notification of what matches and what does not may be displayed. In the illustrated embodiment, the solid arrow 918 between the blind score hole field 910 and the system received score hole field 914 indicates that the scores match, and the dashed arrow 920 indicates a mismatch. The validity notification may be provided by any suitable display. For example, the match and / or mismatch may be indicated by different colors, shades, text, outlines, boxes, symbols, or other suitable perceptible displays.

[0331] The first verification tool 901 can include an official marker 922 that enables the user to flag the scorecard officially. For example, if all scores are shown to match in a blind verification, the user can interact with the official marker 922 and mark the scorecard as official. In another example, if all scores match, the verification system 70 can automatically flag the scores as official.

[0332] In some embodiments, the score may be editable by the user to resolve discrepancies. In one configuration, discrepant or edited scores are sent or saved for additional review. As described above, marking a scorecard as official can be done by sending to a database for storage and / or distribution to one or more data platforms, along with an indication that the scorecard, score, or consent flag is official. In some embodiments, scores recorded by a score tracking system may be sent to one or more data platforms as unofficial scores, and verification is sent to the data platforms to flag the score as official to indicate that the score is currently official by flagging the score through a verification system.

[0333] In one embodiment, after a blind comparison is triggered, the user is given the ability to edit any score within 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 the above or another example, a notification may be displayed for a player's scorecard when it is marked as official, associated with the verification system 70, and that notification remains on the player's scorecard even if the user navigates away and returns to the player.

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

[0335] Scoring data can be arranged in various formats. In the illustrated embodiment, the scoring data is arranged such that each column of data is sorted either in ascending or descending order based on the information available in that column. The fields are typically not editable from the perspective of a basic user. The display may be scrollable to view groups other than the initially displayed group. In one example, when a player or group is selected, information regarding a second verification tool is input for that player or group. Thus, the user can select a player or group and view additional details regarding the score of that player or group. In one instance, if no manual score input has been entered or if it has not been processed by verification, selecting a player or group will result in the input of a group selector and / or player selector field for the selected player or group. In one embodiment, players with officially marked scores are marked with a visual indication as such.

[0336] The scored data presented can include various data points regarding players and scores, such as one or more of the following: (a) group number 931 - corresponding to the group number assigned to the player's group, (b) pre-course 932 - corresponding to the course on which the scored data was collected, (c) starting hole 933 - corresponding to the first hole at which the group started based on the grouping of that round, (d) tee time 934 - corresponding to the start tee time of that group, (e) rank 935 - the predicted rank of the player during play in the ongoing round, (f) team player name 936 - corresponding to the surname and given name of each team player in that group, (g) total 937 - corresponding to the current total par relative score of that tournament, (h) today 938 - corresponding to the par relative score of that round, (i) front 9 holes by hole score 939 - corresponding to a list of scores for each of the first 9 holes, (j) score out 940 - corresponding to the stroke total of the scores entered for the front 9, (k) back 9 holes by hole score 941 - corresponding to a list of scores for each of the back 9 holes, (l) score in 942 - corresponding to the stroke total of the scores entered for the back 9, (m) stroke total 943 - corresponding to the stroke total of the round, or (n) combinations thereof. In various embodiments, the stroke total 943 is displayed only if there is data for score out 940 and score in 942.

[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 groupings of players for the participating players. The round management system may also input the grouping into an ST application, from which a scorer using a companion device can identify the assigned group and / or players and track scores during the tournament.

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

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

[0340] The location system can access the assignment of the tracking module and pair a timestamp with the location of the assigned tracking module. The data management system can access the scoring data and perform reviews and edits as needed using data management tools. Next, the verification system compares the score of the score tracking system with the scorecard of each player. For example, the verification system may apply blind verification. Next, the verification system collates the score of the score tracking system with the player's scorecard. The verification system marks the collated score of the system as "official". The "official" designation is entered into the interface of the data management tool and indicates that no additional scores or score corrections will be entered for that player. The official scores and related data collected by the companion device and the tracking module during play can 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 can utilize additional location tracking technologies. Such technologies may operate as primary, secondary, backup, or alternative positioning methods 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 a scorer such as a human or a robot. The rangefinder is used to measure the distance from the device to objects such as players and balls. The device can also include a direction sensor such as a magnetic field sensor and / or a gravity field sensor to combine the distance and direction with respect to the map of the course. To further enhance the positioning, the position of the device may be known because the device is placed at a known location, or the position of the device, such as coordinates, may be determined by the device or another device by combining with the angle and distance of the object from the device. For example, a device in a mobile use case can obtain GPS (or other global constellation coordinates), which can be enhanced with, for example, WAAS (Wide Area Augmentation System), differential GPS (DGPS), such as GDGPS (Global Differential GPS), CORS (Continuously Operating Reference Stations), SOP (Signals of Opportunity)-based or augmented navigation, UWB, LTE, cellular, radio, television, Wi-Fi®, other satellite signals, etc., as described herein. The position of the device can 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 can be determined and overlaid or mapped onto the golf course to determine the position of the object relative to the golf course. In one embodiment, the device is a real-time kinematic (RTK)-compatible device and uses RTK to determine coordinates. For example, an RTK base station or network can be used to determine the position of the device in combination with the direction and distance of an object targeted by a laser rangefinder to determine the position of the object.In particular, as described elsewhere in this specification, the tracking module may likewise be an RTK-compatible device, and the location network may include an RTK base station or an RTK network.

[0343] In one embodiment, a camera system is arranged around a golf course. One or more cameras can track movement and determine distance using an associated laser or rangefinder, or via optical calculations. For example, each camera can calculate the distance to a ball or other object of known size by comparing the size of the optically captured object to the size of a known object. By further determining the angle of the camera, the position of the object at the distance and angle from the camera can be plotted against a map of the area around the camera. Position determination may be enhanced using multiple cameras, for example, to determine the position of a ball or other object by triangulation or other methods. As an example, an optical map of an area of the course can be utilized by the camera from the field of view of a fixed camera, and the position of an object relative to a known position within the mapped area can be determined. For example, the approximate position of an object can be determined by comparing an image of the object to surrounding features within an image of a known position. To increase the accuracy of position determination, the distance may be determined using optical calculations as described above. In the above or another embodiment, radar may be implemented to track an object including position, velocity, trajectory, acceleration, or other parameters. In the above or another embodiment, the camera may be configured for optical recognition. For example, the camera utilizes face 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, a player carries or wears an optical, electromagnetic, or reflective marker that can be identified by a camera or associated receiver that uniquely identifies the player. In one embodiment, the camera can utilize optical recognition / augmented reality (AR) to identify the position of players and / or balls. The camera may typically be arranged in a known location, but in some cases, one or more cameras may be utilized in a mobile environment that utilizes a real-time kinematic base station or a positioning methodology for cameras as described herein with respect to the positioning of the tracking module.In some embodiments, the camera is used to identify movement and objects, and a laser or rangefinder associated with the camera can be targeted at such objects to determine the distance from the camera to the object. By combining the camera's field of view angle and the distance, the position of the object can be determined. In some embodiments, the topology of the area can be mapped or determined and added to the distance calculation. In some embodiments, such a camera system is operated by a human, a robot, or completely autonomously. The camera can operate in the visual spectrum and / or optical spectrum, including one or more of the visual spectrum, ultraviolet spectrum, or infrared spectrum.

[0344] The systems and methods disclosed herein can include additional functionality and features. For example, the operating functionality of the systems and methods may be configured to execute on a dedicated processor specially configured to perform the operations provided by the systems and methods. Notably, the operational characteristics and functions provided by the systems and methods can potentially enhance the efficiency of computing devices utilized to facilitate the functions provided by the systems and methods disclosed herein. For example, by training the system over time based on data and / or other information provided in and / or generated by 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 can be reduced compared to conventional methodologies. In such a situation, since there is no need to dedicate the processor and memory for processing, less processing power needs to be utilized. As a result, using the software, techniques, and algorithms provided in this disclosure results in substantial savings in the use of computer resources. In certain embodiments, the various operating functions of the system can be configured to execute on one or more graphics processors and / or application-specific integrated processors. In some embodiments, the various functions and features of the systems and methods may operate without human intervention and may be fully implemented by a computing device. In certain embodiments, for example, a number of computing devices may interact with the devices of the system to provide the functions supported by the system. Further, in certain embodiments, the computing devices of the system may operate continuously without human intervention to reduce the likelihood of errors being introduced into the system.

[0345] At least some of the methodologies and techniques described with respect to the illustrative embodiments can be incorporated into a machine, such as a computer system or other computing device, but are not limited thereto, and when a set of instructions is executed, one or more of the methodologies or functions described above can be caused to be executed by the machine. The machine may be configured to facilitate the various operations performed by the system. For example, the machine may assist the system by providing processing power to assist the processing load experienced in 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, but is not limited thereto. As another example, a computer system can assist in increasing the accuracy of the 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, accurate tracking is provided that significantly reduces infrastructure and human intervention compared to current methodologies by utilizing a tracking module that does not interfere with the player's performance or require player interaction to track position.

[0346] In some embodiments, the machine may operate as a stand-alone device. In some embodiments, the machine may be connected to and assisted by other machines and systems, such as a tracking module, a companion device, a management device and associated system servers, databases, other systems, programs, and / or devices, or any combination thereof (e.g., using a communication network, another network, or a combination thereof). The machine may be connected to any component within the system. In a network deployment, the machine may operate as a server or 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 be 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 (sequential or otherwise) that specify actions to be taken by that machine. Further, although a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.

[0347] A computer system can 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 can 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 generating device such as a speaker or a remote control, and a network interface device. The disk drive unit can include a machine-readable medium storing one or more instruction sets, such as software, that embody any one or more of the methodologies or functions described herein, including the methods illustrated above. The instructions can also be present, fully or at least partially, in the main memory, the static memory, within the processor, or in a combination thereof, during execution by the computer system. The main memory and the processor can also constitute a machine-readable medium.

[0348] Dedicated hardware implementations, including, but not limited to, application specific integrated circuits, programmable logic arrays, and other hardware devices, can likewise be constructed to implement the methods described herein. Applications that may include the apparatus and systems of various embodiments can broadly include a variety of electronic and computer systems. Some embodiments implement functionality in two or more specific interconnected hardware modules or devices having related control and data signals that are communicated between and through the modules, or as portions of application specific integrated circuits. Thus, the illustrative 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 executed on a computer processor. Further, the software implementation can include, but is not limited to, distributed processing or component / object distributed processing, parallel processing, or virtual machine processing, and can also be constructed to implement the methods described herein.

[0350] The present disclosure contemplates a machine-readable medium including instructions that enable a device connected to a communication network, another network, or a combination thereof to transmit or receive voice, video, or data using the instructions and communicate via the communication network, another network, or a combination thereof. The instructions can further be transmitted or received via a network interface device via a communication network, another network, or a combination thereof. The term "machine-readable medium" should be regarded as including a single medium or multiple media (e.g., a centralized or distributed database and / or associated cache and server) that store one or more sets of instructions. Also, the term "machine-readable medium" should be regarded as including any medium that can store, encode, or carry a set of instructions for machine execution and cause a machine to execute any one or more of the methodologies of the present disclosure. The terms "machine-readable medium", "machine-readable device", or "computer-readable device" shall accordingly be regarded as including, but not limited to, solid-state memories such as memory cards or other packages that house a memory device, 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, which are regarded as equivalent distribution media to tangible storage media. The "machine-readable medium", "machine-readable device", or "computer-readable device" may be non-transitory and, in certain embodiments, may not include a wave or signal per se. Accordingly, the present disclosure is considered to include any one or more of a machine-readable medium or distribution media, including equivalents and successor media recognized in the art, listed herein and in which software implementations herein are stored.

[0351] The exemplary arrangements described herein are intended to provide a general understanding of the structures of various embodiments and are not intended to function as a complete description of all elements and features of the devices and systems that may utilize the structures described herein. Other arrangements can be utilized and derived from them, without departing from the scope of the present disclosure, so that structural and logical substitutions and changes can be made. Also, the figures are merely representative and may not be drawn to scale. The specific ratios may be exaggerated, and other ratios may be minimized. Accordingly, the present specification and the drawings are to be regarded in an illustrative rather than a restrictive sense.

[0352] Therefore, although a particular arrangement has been illustrated and described herein, it should be understood that any arrangement calculated to achieve the same purpose may be substituted for the particular arrangement illustrated. The present disclosure is intended to cover any adaptations or variations of the various embodiments and arrangements of the present invention. Combinations of the above arrangements and other arrangements not specifically described herein will be apparent to those skilled in the art upon consideration of the above description. Accordingly, the present disclosure is not limited to the particular arrangement(s) disclosed as the best mode contemplated for carrying out the present invention, and the present invention is intended to include all embodiments and arrangements falling within the scope of the appended claims.

[0353] The foregoing is provided for purposes of exemplifying, explaining, and describing embodiments of the present invention. Changes 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 present invention. Upon consideration of the foregoing embodiments, it will be apparent to those skilled in the art that the embodiments can be modified, reduced, or enhanced without departing from the scope and spirit of the claims and description set forth below.

Claims

Claim 1 A score tracking method, the method comprising: collecting or receiving location data by a location system, the location data corresponding to the location of a tracking module carried by a player participating in a golf tournament, the location data including a plurality of sets of location coordinates or being used to generate the plurality of 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; receiving an indication of the occurrence of a stroke event related to the player, the indication being input into the companion device by a scorer who carries the companion device and views the player carrying the tracking module; receiving or generating a timestamp corresponding to the time when the indication of the occurrence of the stroke event is input into or received from the companion device by the scorer; and pairing the timestamp with the set of location coordinates corresponding to the location of the tracking module at the time of the occurrence of the stroke event. Claim 2 The method according to claim 1, wherein the set of location coordinates corresponds to the location of the tracking module over a certain period, and each set of location coordinates corresponds to a predefined time interval within the certain period. Claim 3 The method according to claim 1, wherein the tracking module is configured to receive location signals from a plurality of beacons arranged around the golf course. Claim 4 The method according to claim 3, wherein the location data includes parameters of the location signals used by the location system to calculate the set of location coordinates. Claim 5 The method according to claim 3, wherein the tracking module utilizes the parameters of the location signals to calculate its location and transmits its location as the location data to the location system. Claim 6 The method according to claim 1, wherein the tracking module is configured to output a location signal used by the tracking module to calculate the location data.

7. The method according to claim 1, wherein the tracking module is configured to output a location signal received by a plurality of beacons arranged around the golf course to calculate the location data corresponding to the location of the tracking module.

8. The method according to claim 1, wherein the location data is transmitted to the location system from one or more beacons arranged around the golf course configured to receive a location signal transmitted by the tracking module to track the location of the tracking module.

9. The method according to claim 1, wherein the timestamp corresponds to the time when an indication of the occurrence of the stroke event is input to the companion device, and the companion device generates the timestamp and transmits the timestamp to the location system.

10. The method according to claim 1, wherein the indication of the occurrence of the stroke event includes an identification of the tracking module assigned to the player.

11. The method according to claim 1, wherein the indication of the occurrence of the stroke event includes an identification of the player carrying the tracking module.

12. The method according to claim 1, further comprising receiving location data and an indication of a score event corresponding to a plurality of the tracking modules each carried by a separate player participating in the golf tournament.

13. The method according to claim 12, wherein a single companion device is configured to receive an indication of a score event related to a plurality of players each carrying a separate tracking module.

14. The location data and the indication of the score event include identification data including the identification of the player carrying the tracking module or the identification number of the tracking module carried by the player, and pairing the time stamp with the set of location coordinates corresponding to the position of the tracking module at the time of occurrence of the stroke event includes collating each said identification data, the method according to claim 13.

15. The stroke event includes a ball hit, and the position of the tracking module at the time of occurrence 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, the method according to claim 1.

16. The method according to claim 1, wherein the tracking module operates as a beacon in a location network.

17. The method according to claim 16, wherein the location network utilizes ultra-wideband positioning.

18. The method according to claim 1, wherein the tracking module is configured to transmit the location data to the location system.

19. The method according to claim 1, wherein a location tracking system is configured to receive the location data from a location network, and the location network is configured to calculate the plurality of sets of the location coordinates.

20. The method according to claim 1, wherein the location data collected or received by the location system includes location-specific data used by the location system to calculate the location coordinates.

21. The method according to claim 1, wherein the plurality of sets of the location coordinates consist of a set of GPS coordinates.

22. The method according to claim 1, wherein the plurality of sets of the location coordinates consist of a set of ultra-wideband positioning coordinates.

23. The method according to claim 1, wherein the tracking module is configured to collect the location data at a predefined first interval and transmit the collected location data to the location system at a predefined second interval, and the second interval is greater than the first interval. Claim 24 The method of claim 1, further comprising dividing the holes of a golf course into zones, each zone corresponding to a range of the location coordinates, and determining a current zone in which the tracking module is located from the plurality of sets of the location coordinates. Claim 25 A score tracking system, the system comprising: 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 and configured to receive an input for instructing the occurrence of a stroke event via the user interface, the input causing the application to set a time stamp corresponding to the occurrence of the stroke event; and A location system configured to collect or receive location data, the location data including a plurality of sets of location coordinates or used by the location system to generate the plurality of sets of location coordinates, each set of location coordinates corresponding to the location of the tracking module at a specified time, the location system being configured to pair the time stamp with the set of location coordinates corresponding to the location of the tracking module at the time of occurrence of the stroke event. Claim 26 The system of claim 25, wherein the set of the location coordinates corresponds to the location of the tracking module over a certain period, and each set of the location coordinates corresponds to a predefined time interval within the certain period. Claim 27 The system of claim 25, wherein the tracking module is configured to receive location signals from a plurality of beacons arranged around a golf course. Claim 28 The system of claim 27, wherein the location data includes parameters of location signals configured to be used by the location system to calculate the set of the location coordinates. Claim 29 The system according to claim 27, wherein the tracking module is configured to use parameters of the location signal to calculate its location and transmit the location as the location data to the location system.

30. The system according to claim 25, wherein the tracking module is configured to output a location signal used by the tracking module to calculate the location data.

31. The system according to claim 25, wherein the tracking module is configured to output a location signal received by a plurality of beacons arranged around the golf course to calculate the location data corresponding to the location of the tracking module.

32. The system according to claim 25, wherein the location data is transmitted from one or more beacons arranged around the golf course configured to receive the location signal transmitted by the tracking module to track the location of the tracking module to the location system.

33. The system according to claim 25, wherein the timestamp corresponds to the time when an indication of the occurrence of the stroke event is input to the companion device, and the companion device generates the timestamp and transmits the timestamp to the location system.

34. The system according to claim 25, wherein the indication of the occurrence of the stroke event includes an identification of the tracking module assigned to the player.

35. The system according to claim 25, wherein the indication of the occurrence of the stroke event includes an identification of the player carrying the tracking module.

36. The system according to claim 25, wherein the location system is configured to receive the location data and an indication of a score event corresponding to a plurality of the tracking modules each carried by a separate player participating in the golf tournament.

37. The system according to claim 25, wherein a single companion device is configured to receive an indication of a score event related to a plurality of players each carrying a separate tracking module.

38. The indication of the location data and the score event includes identification data including the identification of the player carrying the tracking module or the identification number of the tracking module carried by the player, and the location system is configured to collate the respective identification data to pair the time stamp with a set of the location coordinates corresponding to the position of the tracking module at the time of occurrence of the stroke event. The system according to claim 25.

39. The stroke event includes a ball hit or a player setup, and the position of the tracking module at the time of occurrence of the stroke event is used as a proxy for the position of the ball of the player carrying the tracking module resulting from the previous stroke. The system according to claim 25.

40. The tracking module operates as a beacon in a location network. The system according to claim 25.

41. The location network utilizes ultra-wideband positioning. The system according to claim 40.

42. The tracking module is configured to transmit the location data to the location system. The system according to claim 25.

43. The location system is configured to receive the location data from a location network, and the location network is configured to calculate the plurality of sets of the location coordinates. The system according to claim 25.

44. The location data collected or received by the location system includes location-specific data used by the location system to calculate the location coordinates. The system according to claim 25.

45. The plurality of sets of the location coordinates consist of a set of GPS coordinates. The system according to claim 25.

46. The plurality of sets of the location coordinates consist of a set of ultra-wideband positioning coordinates. The system according to claim 25.

47. The tracking module is configured to collect the location data at a predefined first interval and transmit the collected location data to the location system at a predefined second interval, wherein the second interval is greater than the first interval, the system according to claim 25.

48. The location system is configured to divide the holes of a golf course into zones, each zone corresponding to a range of the location coordinates, and the location system is configured to determine the current zone in which the tracking module is located from the plurality of sets of the location coordinates, the system according to claim 25.

49. The companion device is configured to be carried by a scorer who accompanies a group of players including the player, and the companion device is configured to receive an input corresponding to the stroke event of all players in the group, the system according to claim 25.

50. A score tracking system, the system comprising: 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 user interface being configured to receive an input indicating the 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, and the user interface including an indicator configured to be pressed to indicate that the player is addressing the ball and held until the player hits the ball to indicate that the ball has been hit, application; and, A location system configured to collect or receive location data, wherein the location data includes a plurality of sets of location coordinates or is used by the location system to generate the plurality of sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a specified time, and the location system is configured to pair the timestamp with the set of location coordinates corresponding to the position of the tracking module at the occurrence of the stroke event.

51. The system according to claim 50, wherein the position of the tracking module at the occurrence 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.

52. The system according to claim 50, wherein the tracking module operates as a beacon in a location network.

53. The system according to claim 52, wherein the location network utilizes ultra-wideband positioning.

54. The system according to claim 50, wherein the tracking module is configured to transmit the location data to the location system.

55. The system according to claim 50, wherein the location system is configured to receive the location data from a location network, and the location network is configured to calculate the plurality of sets of location coordinates.

56. The system according to claim 50, wherein the location data collected or received by the location system includes location-specific data used by the location system to calculate the location coordinates.

57. The system according to claim 50, wherein the plurality of sets of location coordinates consists of sets of GPS coordinates.

58. The system according to claim 50, wherein the plurality of sets of location coordinates consists of sets of ultra-wideband positioning coordinates.

59. The tracking module is configured to collect the 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, the system according to claim 50.

60. The location system is configured to divide the holes of a golf course into zones, each zone corresponding to a range of the location coordinates, and the location system is configured to determine the current zone in which the tracking module is located from the plurality of sets of the location coordinates, the system according to claim 50.

61. The companion device is configured to be carried by a scorer who accompanies a group of players including the player, and the companion device is configured to receive an input corresponding to the stroke event of all players within the group, the system according to claim 50.

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

63. The method according to claim 62, wherein the companion device is carried by a scorer accompanying a group of players including the player, and the companion device receives an input corresponding to the stroke event of all players within the group.

64. A score tracking method, the method including: Receiving, from a companion device, an 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 location data by a location system, the location data corresponding to the position of a tracking module carried by the player, the location data including a plurality of sets of location coordinates or being used to generate the 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 a set of location coordinates corresponding to the position of the tracking module at the time of occurrence of the stroke event, the stroke event being input to the companion device by a scorer watching a live video of the golf tournament.

65. The stroke event includes a ball hit, and the position of the tracking module at the time of occurrence 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, the method according to claim 64.

66. The method according to claim 64, wherein the tracking module operates as a beacon in a location network.

67. The method according to claim 66, wherein the location network utilizes ultra-wideband positioning.

68. The method according to claim 64, wherein the tracking module is configured to transmit the location data to the location system.

69. The method according to claim 64, wherein a location tracking system is configured to receive the location data from a location network, and the location network is configured to calculate the plurality of sets of the location coordinates.

70. The method according to claim 64, wherein the location data collected or received by the location system includes location-specific data used by the location system to calculate the location coordinates.

71. The method according to claim 64, wherein the plurality of sets of the location coordinates consist of a set of GPS coordinates.

72. The method according to claim 64, wherein the plurality of sets of the location coordinates consist of a set of ultra-wideband positioning coordinates.

73. The method according to claim 64, wherein the tracking module is configured to collect the location data at a predefined first interval and transmit the collected location data to the location system at a predefined second interval, and the second interval is greater than the first interval.

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

75. A score tracking method, the method comprising the following: Receiving, from a companion device, an 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 location data by a location system, the location data corresponding to the position of a tracking module carried by the player, the location data including a plurality of sets of location coordinates or being used to generate the 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 a set of location coordinates corresponding to the position of the tracking module at the time of occurrence of the stroke event, the stroke event being input to the companion device by a scorer viewing a video replay of the golf tournament.

76. The method according to claim 75, wherein the stroke event includes a ball hit, and the position of the tracking module at the time of occurrence of the stroke event is used as a proxy for the position of the ball of the player carrying the tracking module resulting from the previous stroke.

77. The method according to claim 75, wherein the tracking module operates as a beacon in a location network.

78. The method according to claim 77, wherein the location network utilizes ultra-wideband positioning.

79. The method according to claim 75, wherein the tracking module is configured to transmit the location data to the location system.

80. The method according to claim 75, wherein a location tracking system is configured to receive the location data from a location network, and the location network is configured to calculate the plurality of sets of location coordinates.

81. The method according to claim 75, wherein the location data collected or received by the location system includes location-specific data used by the location system to calculate the location coordinates. Claim 82 The method according to claim 75, wherein the plurality of sets of the location coordinates consist of sets of GPS coordinates. Claim 83 The method according to claim 75, wherein the plurality of sets of the location coordinates consist of sets of ultra-wideband positioning coordinates. Claim 84 The method according to claim 75, wherein the tracking module is configured to collect the location data at a predefined first interval and transmit the collected location data to the location system at a predefined second interval, and the second interval is greater than the first interval. Claim 85 The method according to claim 75, further comprising dividing the holes of a golf course into zones, each zone corresponding to a range of the location coordinates, and determining the current zone in which the tracking module is located from the plurality of sets of the location coordinates.

Images