Golf event management system with score and location tracking.

Abstract

A system and method for providing golf event management that offers a portable design, precise tracking operation, reduced setup time and personnel, and broadly adaptable to course conditions and infrastructure. [Solution] The tracking module 11 is carried by a player participating in a golf tournament, and the companion device 12 receives input corresponding to stroke events, the input including a timestamp corresponding to the occurrence of the stroke event. The location system can collect or receive location data. Each set of location coordinates corresponds to the position of the tracking module at a specified time. The location system can pair a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

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 behind-the-scenes transactions, which are further complicated by the diversity of course locations and infrastructures. For example, prior to each event on the PGA Tour, each golf course is mapped and digital images of each hole are created, and this image is used as background information for calculating 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 collected 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 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 embodiment, the score tracking system includes a tracking module and either an application or a location system. In one example, the tracking module and either an application or a location tracking system may be 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 scoring operations 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 inputs via the user interface that indicate the occurrence of stroke events. These inputs allow the application to set a timestamp corresponding to the occurrence of a stroke event. In one configuration, a stroke event includes addressing and ball hit (hitting the ball). In the above or other configurations, 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. Location data may include multiple sets of location coordinates, or may be used by the location system to generate multiple sets of location coordinates, each set of location coordinates corresponding to the position of the tracking module at a specified time. In one example, the location system may be configured to pair a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time a stroke event occurred.

[0005] In either the above example of the first embodiment or any other example, 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 either the above example of the first embodiment or another example, the tracking module may be configured to operate as a beacon in the location network. In a further example, the location network utilizes ultra-wideband positioning.

[0007] In either the above example of the first embodiment or any other example, the tracking module may be configured to transmit location data to the location system.

[0008] In either the above example of the first embodiment or any other example, the location system may be configured to receive location data from a location network, and the location network may be configured to calculate a set of location coordinates.

[0009] In either the above example of the first embodiment or any other example, the location data collected or received by the location system includes localization data that the location system uses to calculate location coordinates.

[0010] In either the above example of the first embodiment or any other example, the sets of location coordinates consist of sets of GPS coordinates.

[0011] In either the above example of the first embodiment or any other example, the sets of location coordinates consist of sets of ultra-broadband positioning coordinates.

[0012] In either the above example of the first embodiment or any other example, the tracking module may be configured to collect location data at a predetermined first interval and to transmit the collected location data to the location system at a predetermined second interval, wherein the second interval is greater than the first interval.

[0013] In either the above example of the first embodiment or another example, the location system may be configured to divide the holes of a golf course into zones, each zone corresponding 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 set of location coordinates.

[0014] In either the above example of the first embodiment or any other example, the companion device may be configured to be carried by a scorer accompanying a group of players, including the players. The companion device may be configured to receive input corresponding to stroke events of all players in the group.

[0015] In either the above example of the first embodiment or any other example, the stroke event includes a ball hit. The position of the tracking module at the time the stroke event occurs 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 either the above example of the first embodiment or any other example, the tracking module operates as a beacon in the location network. In one configuration, the location network utilizes ultra-broadband positioning.

[0017] In a second embodiment, the score tracking method includes receiving input from a companion device corresponding to stroke events of a player participating in a golf tournament. The input may include a timestamp corresponding to the occurrence of a stroke event. The method may 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 may include multiple sets of location coordinates or may be used to generate multiple sets of location coordinates, each set of location coordinates corresponding to the location of the tracking module at a specified time.

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

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

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

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

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

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

[0024] In any of the above or other examples of the second embodiment, 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 set of location coordinates.

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

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

[0027] In any of the above or another example 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 another example 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 another example 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 another example of the second aspect, a 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 resulting from the previous stroke.

[0031] In any of the above or another example of the second aspect, the tracking module operates as a beacon in a location network.

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

[0033] In a third embodiment, 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 or is used to generate multiple sets of location coordinates, each set of location coordinates corresponding to the location of the tracking module at a specified time during play in the golf tournament. In one configuration, the method may also include receiving instructions for the occurrence of a stroke event related to a player, which are entered into the companion device by a scorer carrying a companion device and observing the player carrying the tracking module. In one configuration, the method may also include receiving or generating a timestamp corresponding to the time the instruction for the occurrence of a stroke event was entered into or received from the companion device by the scorer. In one configuration, the method may include pairing the timestamp with a set of location coordinates corresponding to the location of the tracking module at the time the stroke event occurred.

[0034] In a fourth embodiment, the score tracking system includes a tracking module and either an application or a location system, or both. The tracking module may be configured to be carried by a player participating in a golf tournament. The application may be configured to interface scoring operations 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 inputs via a user interface that indicate the occurrence of stroke events. The inputs may cause the application to set a timestamp corresponding to the occurrence of a stroke event. The location system may be configured to collect or receive location data. The location data may include multiple sets of location coordinates, or be used by the location system to generate multiple sets of location coordinates. Each set of location coordinates corresponds to the position of the tracking module at a given time. The location system may be configured to pair a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time of the occurrence of a stroke event.

[0035] In the third or fourth embodiment, 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 that period.

[0036] In the above or other examples of the third or fourth aspect, the tracking module may be configured to receive location signals from a plurality of beacons placed around the golf course. In one configuration, the location data includes parameters of the location signals that the location system uses to calculate a set of location coordinates. In one configuration, the tracking module uses the parameters of the location signals 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 embodiment, 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 embodiment, the tracking module may be configured to output location signals received by a plurality of beacons placed around the golf course in order 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, location data may be transmitted to the location system from one or more beacons placed around the golf course, which are configured to receive location signals transmitted by the tracking module to track the location of the tracking module.

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

[0041] In any of the above or other examples of the third or fourth aspect, the instruction for the occurrence of a stroke event includes the 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 instruction for the occurrence of a stroke event includes the identification of the player carrying the tracking module.

[0043] In any of the above or other examples of the third or fourth aspect, the method includes receiving location data and score event instructions corresponding to multiple tracking modules carried by separate players participating in a golf tournament, or the system is configured to receive location data and score event instructions corresponding to multiple tracking modules carried by separate players participating in a golf tournament.

[0044] In any of the above or other examples of the third or fourth embodiment, a single companion device may be configured to receive score event instructions relating to multiple players, each carrying a separate tracking module. In one configuration, location data and score event instructions include identification data, which includes 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, matching a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred includes matching the respective identification data.

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

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

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

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

[0049] In any of the above or other examples of the third or fourth embodiment, 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 set of location coordinates.

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

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

[0052] In any of the above or other examples of the third or fourth embodiment, the sets of location coordinates consist of sets of ultra-broadband positioning coordinates.

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

[0054] In any of the above or other examples of the third or fourth embodiment, 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 set of location coordinates, or the system may be configured to divide 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 set of location coordinates.

[0055] In a fifth embodiment, the score tracking system may 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 inputs corresponding to stroke events, the inputs may include a timestamp corresponding to the occurrence of the stroke event. The location system may include multiple sets of location coordinates, or collect or receive location data used by the location system to generate multiple sets of location coordinates. Each set of location coordinates corresponds to the position of the tracking module at a given time. The location system may pair a timestamp with a set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

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

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

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

[0059] In any of the above or other examples of the fifth embodiment, the location system is configured to receive location data from a location network, and the location network is configured to compute a set of location coordinates.

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

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

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

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

[0064] In any of the above or other examples of the fifth embodiment, the location system is configured to divide the holes of the 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 a set of location coordinates.

[0065] In any of the above or other examples of the fifth embodiment, the companion device includes an interface configured to receive input corresponding to stroke events. Stroke events may include addressing and hitting the ball. The interface may 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.

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

[0067] In a sixth embodiment, the score tracking method includes the steps of: receiving input from a companion device corresponding to stroke events 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 location of a tracking module carried by the player, the location data including a plurality of sets of location coordinates or 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 a timestamp with a set of location coordinates corresponding to the location of the tracking module at the time the stroke event occurred.

[0068] In one example of the sixth embodiment, the stroke event includes a ball hit, and the position of the tracking module at the time the stroke event occurs is used as a proxy for the position of the ball of the player carrying the tracking module resulting from 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-broadband positioning.

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

[0071] In any of the above or other examples of the sixth embodiment, the location tracking system is configured to receive location data from a location network, and the location network is configured to calculate a set of location coordinates.

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

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

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

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

[0076] In any of the above or other examples of the sixth aspect, the method further includes 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 set of location coordinates.

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

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

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

[0080] In any of the above or other examples of the sixth aspect, the stroke event is entered into the companion device by a scorer viewing a video replay of the golf tournament. [Brief explanation of the drawing]

[0081] Novel features of the described embodiments are specifically described in the appended claims. However, the described embodiments, both in terms of organization and mode of operation, can be best understood by referring to the following description taken in conjunction with the appended drawings:

[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 and operating environment components of the STTM system according to the various embodiments described herein;

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

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

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

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

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

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

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

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

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

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

[0094] Figure 6D shows the interface of a revision editor configured to adjust teatime using either an "offset-based revision" methodology or a "reference time-based revision" methodology, according to various embodiments described herein;

[0095] Figure 6E shows the player status editor interface according to various embodiments described herein;

[0096] Figure 6F shows the round engine interface that constitutes the round management panel according to various embodiments described herein;

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

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

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

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

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

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

[0103] Figure 7F illustrates 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 "Irons" from the club selection screen of the ST application according to various embodiments described herein;

[0105] Figure 7H shows an interface for instructing a “shot hit” using the ST application, according to various embodiments described herein;

[0106] Figure 7I shows the “in-hole” prompt for the ST application according to various embodiments described herein;

[0107] Figure 7J shows a group screen displaying the strokes recorded after the score indicates a “shot hit” using the ST application, according to various embodiments described herein;

[0108] Figure 7K illustrates the selection of the “Starting Place” function from the group screen of the ST application in various embodiments described herein;

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

[0110] Figures 7M and 7N show group screens illustrating the transition of the "starting location" from the "fairway" back 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 in various embodiments described herein, where the first two players have finished the hole and the third player is on the green;

[0112] Figure 7P shows the recording of a provisionally recorded second shot from the tee according to various embodiments described herein;

[0113] Figures 7Q–7S show the user interface of the ST application illustrating the workflow for recording a provisional shot that will ultimately be used and result in a record of a penalty stroke, according to various embodiments described herein;

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

[0115] Figure 8A shows a presentation block user interface of a data management tool in a data management system, including tool components within a 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 components of the team player of the data management tool according to various embodiments described herein;

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

[0119] Figure 8E shows all the group presentation components of the data management tool according to the various embodiments described herein;

[0120] Figure 8F shows examples of interfaces for the data mismatch panel component of a data management tool according to various embodiments described herein;

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

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

[0123] Figure 9B shows a second validation user interface for a validation system that presents scoring data for one or more groups, according to various embodiments described herein. [Modes for carrying out the invention]

[0124] This description describes various embodiments of a score tracking and tournament management system, sometimes 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 on players' games and performance without interfering with the players' actions. Management functions can be provided in on-site, off-site, or hybrid configurations. Pre-round and in-round tournament and score management functions can be automated and adaptable to various tournament structures, significantly reducing costs and manpower, while employing customizable setup rules and profiles that integrate multiple tournament processes such as player grouping, tee time, score collection, location tracking, error correction, and score verification. The STTM system can be used to provide tournament scoring, organizational management, and / or scoring system functionality, providing thorough data and feedback to players and other stakeholders in real-time or with delay.

[0125] While some embodiments of the STTM system described herein may incorporate or utilize advanced infrastructure, the STTM system can be provided as a widely applicable, flexible package configured for portability, allowing it to utilize limited infrastructure with minimal impact on the volume, quality, accuracy, and / or functionality gained through the use of the final data product and its event management support. The flexible architecture of the STTM system may be extensible, storable, and / or modular to adapt to available infrastructure and resources with minimal variation in data quality. For example, while various aspects of the STTM system are described herein as providing integrated functionality or operation, the systems, components, and modules of the STTM system are not limited to combined use. In fact, the systems, components, and modules described herein can be used individually or integrated individually with known or future-developed systems.

[0126] The operations described herein can be performed in association with one or more electronic user devices. For example, computer-readable instructions, when stored in memory and executed by a processor, can cause a user device to perform the operations described herein. The memory and / or processor may be local or remote to the user device. A user device may include one or more tracking modules, one or more companion devices, and / or one or more management devices. A user device may include appropriate dedicated or multipurpose electronic computing devices and systems such as mainframes, servers, computers, dedicated devices, desktops, laptops, tablets, smart devices / telephones, and personal data assistants. When used for collecting live event data, companion devices are typically handheld tablets, smart devices / telephones, personal data assistants, or dedicated handheld devices.

[0127] The STTM system includes, embeds, and / or can communicate with a user device that runs an application for performing the operations described herein. The user device can interface the user with the operation 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 delivered in whole or in part in a cloud computing environment (e.g., SaaS, DCaaS, DaaS, PaaS, iPaaS, IaaS, etc.).

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

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

[0130] The tracking module 11 consists of a user device configured to be carried by a competitive player or configured to be placed near a competitive player during play. The tracking module 11 may include a memory containing instructions and a processor that executes instructions from memory to perform various operations performed by the tracking module 11. In certain embodiments, the processor may be hardware, software, or a combination thereof. In some embodiments, the tracking module 11 may also include an interface 11a (see, for example, Figure 4C) which may allow scorers, players, and / or other users to interact with various applications such as a score tracking application, which may be called an ST application, and / or operations performed on the tracking module 11, such as location signals and / or location calculation processes, and to interact with STTM system components, devices, systems, and / or elements thereof. In certain embodiments, the tracking module 11 is and / or includes 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, and / or any combination thereof. The tracking module 11 may be configured to perform various location operations. For example, the tracking module 11 may be configured to track its position and / or communicate location information to the STTM system and / or location element. The tracking module 11 may be configured for location tracking utilizing various techniques and location schemes described herein. For example, in some embodiments, the tracking module 11 is configured to acquire GPS coordinates corresponding to its position and transmit such coordinates to an STTM system device or a system such as the management system 20, as described herein.In these or other embodiments, the tracking module 11 may operate as a beacon in the location network 14. The tracking module 11 may be configured to communicate with the location network 14 and / or various location elements such as location services to transmit data constituting location data, which may include location data that can be used to determine the location of the tracking module 11. The location data may also include a timestamp corresponding to the time the location data is related to. The tracking module 11 may be configured to communicate data such as location data and / or location data over various communication networks 17, such as mesh networks, local networks, cloud computing networks, IMS networks, VoIP networks, security networks, VoLTE networks, wireless networks, Ethernet networks, satellite networks, broadband networks, cellular networks, private networks, cable networks, the Internet, intranets, Internet Protocol networks, MPLS networks, content delivery networks, near-field communication networks, or any combination thereof. The tracking module 11 may be configured to communicate directly with location elements such as the location network 14 and the global satellite communication infrastructure 15 over various communication networks 17, or to communicate indirectly over another STTM system device or network device.For example, in one embodiment, the tracking module 11 may utilize a companion device 12 or management device 13 to transmit data directly to devices, elements, associated networks and / or location elements of the STTM system 10 via one or more communication networks 17, and / or to transmit signals to access various network-based, web-based, cloud-based and / or online services and content, such as those available on the internet, on other devices and / or on various computing systems.

[0131] The companion device 12 may be configured to communicate with, define, identify, and / or organize scoring data, which may include location data, associated with the tracking module 11. Furthermore, or alternatively, the companion device 12 may be used to collect and / or track other competition data. The companion device 12 may be used by the user to access data, content, and services, and / or to perform various other tasks and functions of the STTM system 10. For 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. Another example is that the companion device 12 may be used to access applications such as ST applications that provide one or more operational functions of the STTM system 10, such as communication with one or more location elements comprising the management system 30, one or more tracking modules 11, one or more management devices, and / or the location network 14, and / or the global satellite communication infrastructure 15.

[0132] In certain embodiments, the companion device 12 may be used by a scorer to control one or more operational functions of the STTM system 10. The scorer may be a human, such as a dedicated user or player, a passive robot, an active robot, a humanoid, a program, a computer, any type of user, or a combination thereof. The companion device 12 may include a memory containing instructions and a processor that executes instructions from memory to perform various operations performed by the companion device 12. In certain embodiments, the processor may be hardware, software, or a combination thereof. The companion device 12 may also include an interface 12a (e.g., a screen, monitor, graphical user interface, etc.) that can enable the scorer to interact with various applications, such as ST applications, running on the companion device 12, and to interact with one or both of the STTM system 10, for example, the score tracking system 20 or the management system 30. In certain embodiments, the companion device 12 may be and / or 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. Exemplarily, the companion device 12 is shown as a smartphone or tablet device in Figure 1.

[0133] The management device 13 is used by the management user in relation to the functions of the management system 30 and can receive and transmit signals requesting various types of content, services, and data provided and / or accessible by the communication network 17 or other networks with which the STTM system 10 communicates. In a further embodiment, the management user may be a robot, computer, humanoid, animal, any type of user, or any combination thereof. The management device 13 may include memory containing instructions and a processor that executes instructions from memory to perform various operations performed by the management device 13. In a particular embodiment, 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 can enable the user to interact with various applications running on the management device 13 (e.g., management applications) and with the devices, elements, and systems of the STTM system 10. In a particular embodiment, 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 competition venue. The management device 13 may be cloud-based or web-based.

[0134] In certain embodiments, the companion device 12, tracking module 11, management device 13, and / or location network 14 may have any number of software applications and / or application services stored therein and / or accessible therewith. For example, the companion device 12, tracking module 11, management device 13, and / or location network 14 may include applications for controlling the operational features and functions of the STTM system 10 and / or 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 a combination thereof. In certain embodiments, the software application may support the functions provided by the STTM system 10, such as the score tracking system 20 or its management system 30 described herein, and the methods thereof. In certain embodiments, software applications and services may include one or more graphical user interfaces to enable users (e.g., scorers, players, system administrators) to easily interact with the software application.Furthermore, software applications and services may be used by users to interact with any device within the STTM system 10, any network of the STTM system 10, or any network utilized by the STTM system 10 (e.g., a location network or global satellite communications infrastructure), or any combination thereof. In certain embodiments, the companion device 12, tracking module 11, and / or management device 13 may include an associated device identification ID, or other identifiers to uniquely identify a 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, and may include any number of networks, including a location network 14 in one embodiment. For example, the communication network can be used by the companion device 12 to connect with other devices inside and outside the communication network 17. In various embodiments, the companion device 12, tracking module 11, management device 13, and / or the location network 14 may belong to and / or form part of the communication network 17. In a particular embodiment, 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 a particular embodiment, the communication network 17 may be formed between or within various user devices such as the management device 13, companion device 12, tracking module 11, database 18, or a combination thereof, through the use of any type of radio or other protocol and / or technology. For example, user devices can communicate with each other in the communication network 17 by utilizing any protocol and / or radio technology, satellite, fiber, or any combination thereof. In particular, the communication network 17 may be configured to link to and / or communicate with other networks of the STTM system 10 and / or networks outside 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 that traverses 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 and be connected to mesh networks, local networks, cloud computing networks, IMS networks, VoIP networks, security networks, VoLTE networks, wireless networks, Ethernet networks, satellite networks, broadband networks, cellular networks, private networks, cable networks, the Internet, intranets, Internet Protocol networks, MPLS networks, content delivery networks, near-field communication networks, or any combination thereof. Exemplarily, the management device 13 is shown as a representative server and is shown as being contained within or utilizing the communication network 171. As described above and elsewhere in this specification, the management device 13 typically constitutes a user interface that enables a user to perform the scoring and / or tournament competition management operations described herein. In certain embodiments, the communication network 17 may be part of a single autonomous system located in a specific geographical region or part of a plurality of autonomous systems spanning multiple geographical regions.

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

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

[0138] The STTM system 10 may further include or transmit competition-related data generated by the STTM system 10 to one or more data platforms 19. The data platform 19 may consist 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 available to players, coaches, administrators, fans, members of media organizations, broadcasters, or any other person. In further embodiments, the data platform 17 may constitute a client platform for data consumption and may include a competition data viewer 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 via other parts of the network, for example, locally.

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

[0140] This specification refers to various interface components. Interface components include interface elements configured to interface with the user for operations such as selecting data values ​​or data elements, display elements configured to interface with the user for display, data elements, and so on. Indicators, operators, options, etc., described herein in relation to interfaces may include buttons, toggles, switches, sliders, swipe buttons / bars / fields, sidebars, or other interface elements. Such interface elements can be configured in hard or soft. Similarly, interaction terms such as pressing, tapping, and selecting can be performed using the human body, styluses or other instruments, peripherals such as mice and keyboards, or other appropriate user interactions.

[0141] Continuing to refer to Figure 2, the score tracking system 20 may be configured to track the scores of multiple players, such as golfers, participating in a competition. While the competition 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 may also include tracking the location of stroke events. As introduced above and described in more detail below, the score tracking system 20 may include a tracking module 11 that is carried by the player or configured to accompany the player. In some embodiments, for example, as shown in Figure 2, the score tracking system 20 may also include a companion device 12 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 the scorer and transmit score-related data to a management system 30. The tracking module 11 may be configured using localization, positioning, and / or proximity techniques to track the location of the tracking module 11, as introduced above and described in more detail below. These techniques may be used by the tracking module 11 and / or other devices such as the companion device 12, the management device 13, the location network 14, and / or the location system 80. Using the companion device 12, the scorer can record events related to play, such as stroke events. Recording events may result in the generation and recording of associated timestamps, and / or the retrieval, identification, calculation, and / or transmission of location data from the tracking module 11 corresponding to the recorded events, such as when a player addresses the ball or hits it.Location data, or the chronological 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 a previous hit or the starting position of the player's ball before hitting it. A notable advantage of this score tracking method is that a single scorer, typically accompanying a group of golfers, can record both the score and location data in an unobtrusive manner. In various embodiments, as will be described in more detail below, the tracking module 11 is configured to be compatible with multiple location service technologies, thereby providing flexibility in tracking the location of the tracking module 11 by, for example, utilizing the infrastructure available with respect to the course as needed. The score tracking system 20 and / or STTM system 10 may include or incorporate location services such as one or more of the global satellite communications infrastructure 15 or the location network 14. Location network 14 is typically a local location network relating to a golf course where a tournament is held, and may include wireless receivers, transmitters, transceivers, antennas, UWB antennas, anchors, initiators, responders, cell towers, Wi-Fi® access points, beacons, geobeacons, BLE gateways, etc. In some embodiments, location network 14 includes an external location / signaling network that utilizes short-range or long-range location technology, which may include opportunity signaling.

[0142] In various embodiments, the tracking module 11 is configured to communicate with a companion device 12 and is operable to retrieve calculated location data or location signaling parameters from the tracking module 11, which can be used by the companion device 12, a management device 13, and / or a location system to calculate the location of the tracking module 11 over a given time, time range, or continuously. However, in some embodiments, the tracking module 11 does not need to communicate with the companion device 12 with respect to location tracking operations, and another device may calculate or receive the location of the tracking module 11, for example. For example, a timestamp set by the companion device 12 may be sent to another device before or after transmission to the management device 13 to be paired chronologically with the location of the tracking module 11, or the management device 13 may communicate with the tracking module 11 and the companion device 12 to receive location data to pair with the timestamp.

[0143] In one example, the tracking module 11 acquires 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 stroke events, including associated timestamps, to the management system 30. The location system 80 pairs the timestamps with the corresponding location coordinates.

[0144] In one example, the tracking module 11 obtains its position, which may include location coordinates, through location signaling with a location network 14, such as a UWB or other location network as 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 a companion device 12, which then transmits the position, and / or the position paired with a corresponding timestamp, to the management system 30. The companion device 12 may also transmit a stroke event, including the associated timestamp, to the management system 30. The location system 80 can then pair the timestamp with the corresponding location coordinates.

[0145] In one embodiment, the management system 30 includes a device management system 40 configured to manage a plurality of tracking modules 11 and assign them to players. The device management system 40 can run on one or more management devices 13. In one configuration, the device management system 40 communicates with the tracking modules 11 during play to track their locations. When a companion device 12 sets a timestamp regarding the location of 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 review and / or can be made available for operation of the STTM system 10 or for transmission or use by the data platform 19. As described above and elsewhere in this specification, the location calculation, and / or the combination of location coordinates and timestamps, may be performed by the location system 80 and made available by 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 location calculation may be perceptually instantaneous or otherwise real-time. In one embodiment, the companion device 12, tracking module 11, management device 13, location network 14, and / or location system 80 can track the location of the tracking module 11 continuously or nearly continuously. Such continuous or nearly continuous tracking can be used to address location tracking / network delays. For example, if a scorer records a stroke event with a timestamp set when the ball is struck, in almost all cases the most recent position calculated within 5 seconds of the timestamp will provide the exact position of the ball at the time of the strike. In one embodiment, the scorer sets a timestamp for position purposes at address.

[0146] In various embodiments, the management system 30 includes one or more of the following: a round management system 60 configured to manage rounds and groupings of players playing in an event; a data management system 60 configured to review and edit scoring data recorded by the score tracking system 20; or a verification system 70 configured to provide streamlined verification of a player's official scorecard against scores collected by the score tracking system 20. In the above or other embodiments, the management system 30 may include a location system 80. The location system 80 may be configured to handle location data from the tracking module 11, calculation of location data from localization data, pairing of timestamps with location data, zone determination, and / or comparison of zone determination with scoring data zone identification. In one embodiment, a companion device 12 may transmit scoring data to the management system 30. The tracking module may also transmit location data or localization data to the management system 30, directly or indirectly. Stroke events and corresponding timestamps may be available to the location system 80 for pairing 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 location determination functions described above on behalf 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, location networks may include GPS, Wi-Fi®, RFID, BLE, UWB, NFC, cellular, and the like.

[0147] As described above, the companion device 12 may be configured to run or execute an ST application. The ST application may consist of a mobile app, a web app, a cloud-based application, or other application format, and may include instructions that can be operated to perform the score collection functions 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 from the tracking module 11, initiate location data events, relay data received from the tracking module 11 to storage or another computing device, perform proxy services for the tracking module 11, or perform other operations described herein. Furthermore, 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 import group assignments, round information, tea time, etc., from the round management system 60.In the above or another example, the ST application may be configured to receive player and tracking module 11 assignments from the device management system 40, incorporate player and tracking module 11 assignments into collected scoring data (stroke event data, location data, timestamps, club selection, etc.), transmit stroke event data including relevant timestamps to the STTM system 10, e.g., location system 80, device management system 40, data management system 50, and / or verification system 70, and / or communicate with the tracking module 11 to pair it with the assigned player. However, in some embodiments, the assignments may be held by the management system 30, and the companion device 12 may be accompanied by stroke event timestamps or location data having identifiers for each tracking module 11, which the management system 30, e.g., data management system 60 or location system 80, use to pair the location of the tracking module 11 in the timestamp with the player assigned to the tracking module 11. In the above or another embodiment, the ST application may be configured to transmit the collected scoring data recorded by the companion device 12 to a management system 30, such as a data management system 60, a verification system 70, and / or a location system 80.

[0148] In one embodiment, the tracking module 11 consists of a compact housing that can be easily carried or worn by an individual. Figures 4A–4D provide illustrations of exemplary tracking modules 11. Larger tracking modules 11 may be used, but in the illustrated example, the tracking module 11 has a housing 110 that is generally smaller than a deck of playing cards. In one embodiment, the housing 110 may have 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 may be provided for receiving the tracking module 11. In one example, the receptacle may include a clip for clipping to a belt or pocket, or include a wearable band, or 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, or bracelet. In some embodiments, the tracking module 11 may be integrated into a smart device such as a tablet, laptop, phone or PDA, or other portable electronic device. In various embodiments, the housing 110 may be configured to be opened for maintenance, parts replacement, upgrade, or other desired purposes. For example, the housing 110 may include removable panels or constitute a clamshell design. In one embodiment, the housing 110 may be waterproof or water-resistant with respect to the interior of the housing 110. For example, the panels or clamshell may be provided on a gasket.

[0149] Figure 4D is a semi-schematic internal view of 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 it may be accessible by removing its panel or clamshell. The wired data communication port 111 can be used as an alternative or backup to wireless data communication for programming, downloading, or other data communication needs.

[0150] The tracking module 11 may include one or more batteries 113 configured to power the operation of the tracking module 11. Various standard and custom-sized 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, the user may attach or carry a separate battery pack or power supply that powers the tracking module 11 via a wired or wireless connection. Any suitable type of battery 113 sufficient to power the tracking module 11 can be used. For example, the battery 113 may include lithium, alkaline, silver oxide, zinc carbon, zinc air, lithium ion, NiCD, or NiMH. Various configurations of the tracking module 11 may include or be configured to operate on a rechargeable battery 113 such as lithium ion, NiCD, or NiMH. In one embodiment, the tracking module 11 includes a rechargeable battery 113 such as a rechargeable lithium polymer 2300mAh battery.

[0151] Some configurations of the tracking module 11 may include a charging port 112 that can operate to receive power for charging a battery 113. The charging port 112 may include a female or male connector. The port 112 may be configured to be waterproof or water-resistant to prevent water from entering the charging port 112. For example, the charging port 112 may be isolated from the inside 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 watertight material. In another example, a removable plug may be fitted inside or on the charging port interface to prevent water ingress. In one embodiment, the tracking module 11 is configured to be charged wirelessly. In one embodiment, the tracking module 11 is configured to have a charging port for recharging the battery while it is inside the housing. For example, the housing may include a wired or wireless charging port. A magnetic wireless charging port, USB (e.g., A, B, Mini A / B, Micro A / B, C), Thunderbolt, a DC power connector, or other suitable power supply interface technology can be used. A custom charging interface can also be used. In some embodiments, the charging port 112 is configured to operate as a wired data communication port 111 as well. In one embodiment, the charging port 112 is configured as a USB-C connection. In the above or other examples, the housing may include a charging interface configured to plug into a charger having multiple charging ports for simultaneous charging of multiple tracking modules 11.

[0152] In various embodiments, the tracking module 11 may be configured to include a wireless communication port 114 comprising 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, e.g., signals, over any wireless communication medium or protocol, including or incorporating radio waves, cellular, Wi-Fi®, near-field radio, Bluetooth®, or other suitable wireless communication technologies. The wireless communication port 114 may be configured for multiband operation. For example, the wireless communication port 114 may be configured for communication in multiple frequency bands. The multiple frequency bands may include cellular networks (4G, LTE-M, NBIot, 2G, etc.) and / or other frequency bands. The wireless communication port 114 may be configured to transmit and / or receive data such as location data and / or positioning data from a location network, global satellite communication infrastructure, etc. The wireless communication port 114 may be configured to transmit and / or receive positioning data such as parameters for position 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 activated wirelessly via radio communication from one or more remote command centers, management devices, or companion devices equipped with appropriate wired or wireless transmitters or transceivers 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 radio, Bluetooth®, or other appropriate wireless communication technology.

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

[0154] The tracking module 11 may include a memory 119a and a processor 119b that executes instructions stored in the memory 119a or otherwise received in order to perform the operation of the tracking module 11. In some configurations, the housing 110 may include 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 microSD 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, receiving device, or processing device continuously, periodically, daily, or on demand.

[0155] The tracking module 11 may include an accelerometer 1100. The accelerometer 1100 may be used for motion detection. Motion detection may be used in combination with positioning and location tracking, determination, or acquisition, for example, motion detection may initiate the transmission of a location signal and / or listen to the same. Motion detection may initiate the transmission of 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 accelerometer 1100 may be configured for motion detection relating to the detection of a swing by a player. Motion detection corresponding to a swing may be used in addition to, or instead of, a scorer input of a swing or "shot hit," as described later. The accelerometer 1100 may also be configured to detect an address corresponding to a time with a pause in motion prior to the detection of motion corresponding to a swing, for example.

[0156] The tracking module 11 may include a user interface 11a for interface with the user regarding operation and / or status. In various embodiments, the user interface 11a may include a display 118 for displaying information. Any suitable display 118, such as an OLED screen, may be used. The information may include battery capacity, battery life or status, and operating modes such as wakefulness, sleep, ready to receive instructions, and operating. In some embodiments, the display 118 may present data regarding the current operation or assignment. For example, the display may be configured to display the group number to which the tracking module 11 is assigned 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, processing data, uploading data, downloading data such as instructions, assignments, or updates, receiving and / or acquiring location data, receiving instructions, transmitting data, operating, or operation completed.

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

[0159] In various embodiments, as described above, the tracking module 11 includes localization, positioning, and / or proximity techniques to assist in locating a misplaced tracking module 11 and / or determining its exact location. For example, the tracking module 11 may be configured to output localization signals, such as packets, flashes, requests, and responses, in a directional or omnidirectional manner, which may be used by companion devices, location networks, management systems, and / or location systems to locate and / or determine the location of the tracking module 11, for example, based on signal strength, signal parameters, and / or signal characteristics. In addition, or alternatively, an STTM system, which may include the location elements described herein, may be configured to locate the tracking module 11 using other techniques, such as those described below.

[0160] The STTM system or its score tracking system may include a location network configured to provide location tracking functionality and / or services. The location tracking network (see Figure 2) may include multiple location signaling devices. Location signaling devices may include receivers, transmitters, transceivers, gateways, beacons, UWB antennas, anchors, initiators, responders, real-time kinematic (RTK) base stations, etc., configured to determine outdoor location / location. Location signaling devices may be configured to utilize radio waves such as UHF, NFC, Wi-Fi®, Bluetooth Low-Energy®, and / or UWB. Location signaling devices may be placed around the course of play and configured to communicate location signals with multiple tracking modules 11. The location network may be configured for device-side location calculation and / or network-side location calculation. The location network and / or tracking module 11 can utilize various localization techniques such as RSSI, RSSI-fingerprinting, and / or time of flight (ToF), time difference at arrival (TDPA), and / or angle of arrival (AoA).

[0161] The tracking module 11 may include one or more near-field communication devices such as Wi-Fi®, Bluetooth®, BLE, NFC, and / or ultra-wideband chips, configured to provide near-field location signaling, location retrieval, proximity determination, and / or ranging. Figure 4D shows a wireless communication port 115 configured for ultra-wideband, but other near-field communication protocols and / or signaling may be utilized. The wireless communication port 115 may be added to or replace the wireless communication port 114. In some embodiments, the wireless communication port 115 consists of a Wi-Fi® chip, a BLE chip, an LTE chip, and an ultra-wideband chip, while the wireless communication port 114 consists of a cellular chip. Depending on the configuration, location services may be utilized by the tracking module 11, the STTM system, location signaling devices of the location network, and / or any device appropriately configured to receive location signals or positioning signals and utilize the signals and associated data to identify and / or determine the location of the tracking module 11.

[0162] In addition, or alternatively, the tracking module 11 may be configured to receive location signals from a location signaling device that can be used to determine the location of the tracking module 11 by the tracking module 11, a companion device, a location network, a location system, or any other. For example, a beacon signal may be used to determine the location of the tracking module 11. As described above, the location signals may be output using short-range communication technology. In various embodiments, the location signals may be transmitted via radio waves such as UHF, NFC, Wi-Fi®, Bluetooth Low-Energy®, or ultra-wideband. For example, the tracking module 11 may be configured to receive location signals such as beacon packets or UWB anchors. In device-side use cases, the tracking module 11 can calculate its location using the received location signals, or relay the location signal / packet data and / or associated received parameters to another device, such as a companion device or management device, for direct or indirect processing (e.g., by using an API). For example, if a beacon is present, the tracking module 11 can receive beacon packets, which can then be used by the tracking module 11, or a companion or management device communicating with the tracking module 11, for location / location determination, for example, by RSSI, RSSI-fingerprinting, and / or ToF technology. In network-side location calculation use cases, the tracking module 11 may continuously output signals, transmit location response signals to location signals received from location signaling devices, or transmit polling signals, which may be used by location networks or other STTM system components, such as location systems, to calculate the location 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, positioned around a playing area such as the green, fairway, rough, and / or tee box. The tracking module 11 can receive signals transmitted for location / positioning. In a further example, the tracking module 11 may transmit a response positioning signal. In the above or another embodiment, three or more beacons or anchors may be used for accuracy and precision, for example, around the green.

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

[0164] The tracking module 11 may be configured to utilize one or more global satellite communications for precise positioning and location. Exemplary, Figure 4D shows a GPS chip or receiver 117 configured to receive GPS location coordinate data. While this specification generally refers to GPS, those skilled in the art will understand that such references also apply to other Global Navigation Satellite Systems (GNSS), such as GLONASS, BeiDou, Galileo, or other current or future GNSS systems. GPS location can be augmented with WAAS (Wide Area Augmentation System), DGPS (Differential GPS), e.g., GDGPS (Global Differential GPS), RTK (Real-Time Kinematic), CORS (Continuous Operating Reference Points), SOP (Skill Signal-Based) based or augmented navigation, UWB, LTE, cellular, radio, television, Wi-Fi®, and other satellite signals. In some embodiments, the location network can be used instead of, or in a hybrid with, one or more global communication coordinate systems. The location network may 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 one or all of the available global satellite communications (GPS, GLONASS, BEIDOU, GALILEO, and QZSS) to perform accurate positioning outdoors with an accuracy of 0.5–5 m typ. or better. In one embodiment, the tracking module 11 transmits its coordinate position to a management system via a cellular network.

[0165] In one embodiment, the communication network includes an 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. Companion devices can similarly transmit stroke event data over such a network. Unlike current score tracking methodologies, the configuration of this score tracking system utilizes low data load, suitable for transmitting small data packets over low-power, long-distance networks, while maintaining a stable amount of accurate data.

[0166] As described above, the STTM system can utilize UWB positioning / location networks for all or part of its location services. GPS or other location services can also be used simultaneously, in a hybrid configuration, or as individually selectable options or settings for each system device.

[0167] In various embodiments, the tracking module 11 may be configured to output a location signal or a positioning signal continuously, or it may be configured to output a location signal when it receives an instruction to output a location signal. For example, an ST application or location tracking network may be operable to address one or more tracking modules 11 in order to initiate the output of a 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 may be configured to collect location coordinates at any predetermined time interval and transmit the collected location coordinates at any predetermined time interval.

[0168] In one embodiment, the tournament course and / or surrounding grounds may be mapped and divided into geolocation zones. Location data from the tracking module 11, which may include localization data, may be sent to a management system, such as a management device, to determine the current geolocation zone corresponding to the tracking module's location. The current zone is sent to the tracking module 11 and can trigger actions 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 for the coordinates corresponding to the tracking module. Actions that can be triggered include alerts, API calls, database entries, alarms, etc., based on entering, leaving, or being in a particular zone.

[0169] Figure 3 shows an example of geolocation zoning for 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 its respective zone. As mentioned 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, score tracking system, or management system may 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 mentioned above, a location system may collect or receive location data about the tracking module. The location system may use this location data to determine the position of the tracking module. Location coordinates may be applied to a predefined coordinate range corresponding to a defined zone to determine which zone the tracking module is currently located in. This zone determination may be performed in real time, for example, within 10 seconds, 5 seconds, or less. The location system may utilize the latest set of location coordinates or the interval of location coordinates to determine the current position and / or zone to which each tracking module 11 is located in order to track the position of the tracking module 11. Similarly, when the tracking module assigned to the last player in the group crosses the green zone 31 after the group has been marked or recorded as being in the green zone 31, the group may be marked or recorded as having completed the hole. When the tracking module 11 assigned to the first player to enter 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 be used additionally or alternately to mark or record locations. In one embodiment, a group marked or recorded as being at a tee box can advance the ST application to the hole associated with that tee box. In another embodiment, when a scorer enters "In Hole" into the companion device for the last player in a group that has holed out, the ST application automatically advances to the next hole. In yet another embodiment, the ST application does not advance to the next hole until "In Hole" has been entered for all players in the preceding hole and the players have entered the tee box for that hole.

[0170] As described above, the tracking module 11 may be configured to collect location coordinates at any predetermined time interval and to transmit the collected location coordinates at any predetermined time interval. For example, the tracking module may be configured to acquire location coordinates, such as GPS position, every second and to transmit the acquired location coordinates to the location system every five seconds. However, the tracking module 11 may also be configured to collect location data at any desired time interval and to transmit the collected location data.

[0171] In one embodiment, the position of the tracking module 11 is tracked continuously, for example, at 1-second intervals or otherwise according to a program. In one embodiment, by pairing a timestamp with a 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 detailed later, scorers using the companion device can also input the ball's position or "starting location." Such a position may correspond to a defined zone on the hole. Using zone determination from the tracking module's coordinates, the location system can compare the determined zone with the input zone and identify any discrepancies. For example, the determined zone might be the fairway, while the input zone is a bunker or hazard. In such cases, the location system may be configured to accept the zone's location 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 modified to correspond to what is input by the scorer.

[0173] The companion device may record a timestamp at address and / or shot hit. The location network may apply an algorithm to analyze the position before and after the timestamp. Lookback and forward times may be adjustable in the location system. For example, the lookback and forward times may be 30 seconds. In one embodiment, the lookback time may be longer than the forward time. The location system 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 longer during which the position hardly changes. As described above, the tracking module can detect when the swing took place. Such data may be provided to the location system to verify or enhance the analysis regarding the timestamp. For example, the location system can pair the position at the time of the swing and match it with the position obtained by the scorer provided with the timestamp. In some embodiments, the position is not recorded if the position is unknown or does not correlate with the expected position, for example, if the coordinates correspond to a different hole.

[0174] In one embodiment, the tracking module 11 consists of an operation window. For example, location data, which may include localization data, is not stored or transmitted outside of the defined time of the operation window. Such an operation window can be registered with each tracking module 11. In this example or another, if the tracking module 11 is not registered with a tournament player, the location data or localization data is not stored or transmitted. In any of the above or other examples, the tracking module 11 may not transmit the location data or localization 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 acceptable coordinates related to the tournament. Such restrictions may enhance the privacy of the tracking module 11 to the user. In some embodiments, 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 to a player who is out of position or playing too slowly. For example, the tracking module 11 may output a text notification (if equipped), an audible and / or visual alarm, or vibration. In addition, or alternatively, a companion device assigned to a group including a player who is out of position or playing too slowly may receive such a notification via the ST application. In a further example, the notification may include instructions on how to correct the problem, such as arriving at a specific location on time, or asking the player to pick up the pace.

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

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

[0178] Figure 5A provides a device management overview presentation 400, which includes a device list 401 of tracking modules and their associated locations 402 loaded into the device management system 40 according to various embodiments. The device management system 40 is configured to allow users to create and delete locations. In one embodiment, when a user deletes a location, a warning prompt may be generated to notify the user of the deletion upon user confirmation. A location 402 may be a place associated with a listed tracking module. A location 402 may refer to a geographical location by coordinates, landmarks, or location references (e.g., 9th Hall, Volunteer Meeting Area, Gear Locker, Tool Room, Geolocation Zone, etc.). In addition, or alternatively, a location 402 may refer to a physical container containing each tracking module (e.g., container 681). In one example, a location 402 refers to a container containing a storage device configured to function as a charging station for charging tracking modules and / or a storage station for storing tracking modules. In one example, location 402 refers to a physical container containing a tracking module, and the geographical location of the container, which may be coordinates, a zone determined by the geolocation corresponding to the listed tracking module, or a location defined by the device management system 40. Locations 402 and devices included in the device list 401 may be imported into the device management system 40 before 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] Figure 5B shows an exemplary user interface 403 generated by the device management system 40 to provide tracking module management functionality and present device management data for loaded tracking modules. The data elements included in the tracking module device management data or profile shown in the illustrated embodiment include, for each tracking module, (a) 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 a location 402 provided in the overview presentation 400 may be provided at the top of the hierarchy. Loaded and saved tracking modules and associated device data elements are stored in the identified location 411 and presented under the location 411 element. In one configuration, the device management system 40 may be configured to allow the user to move locations and associated device management data to change the order in the presentation. In the above or other configurations, the user can collapse or expand tracking module data for a selected location, for example, by interacting with the location 411 field. In the above or other configurations, the presentation includes a location labeled “Storage” 412 that stores loaded but not currently in use 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 loaded tracking modules to receive data associated with one or more device data elements. In various embodiments, the presentation may be configured to update automatically at predetermined time intervals, such as every 30 seconds, or when an event occurs, such as when a device data element is received outside a predetermined tolerance range or exceeding a threshold.In some configurations, the presentation may include a manual update option to instantly update the values ​​of device data elements.

[0180] If each tracking module is transmitting location signals, such as GPS information / coordinates, polling signals, response signals, location signal parameters, location data, or positioning signals, then "Functioning" is identified by the Functioning 404 data element.

[0181] The device name 405 may be a unique name associated with the device. The device ID 406 may be a manufacturing ID number assigned to GPS or other location technology. The precision 407 may refer to the measurement accuracy of the device's position as distance. The position 408 may refer to the device's current position. Depending on the configuration and location technology used, the position value may be provided in latitude / longitude, grid coordinates, or other appropriate location coordinate specifications. In various embodiments, the device management system 40 may perform one or more position 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, on 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 provide the timestamp to the device management system 40 and pair it with the corresponding position of the tracking module specified by the timestamp. In another example, the companion device may send a location information event to the device management system 40 for location pairing. Any appropriate data handling and flow may be used to perform such location operations during gameplay. For example, a tracking module may send location data and / or localization data to a location system, and a companion device may send location events to the location system for timestamps and location pairing with the tracking module.

[0182] The signal strength 409 may be the current signal strength of the location signal received and / or transmitted by each tracking module. For example, the signal strength 409 may refer to the radio signal strength such as a cell, Wi-Fi®, or UWB, which may be queried by the device management system 40 to measure the health of the tracking module in relation to its ability to share location information or other data such as swing. In one embodiment, the signal strength 409 may refer to the accuracy of the position-based coordinates. The battery life 410 provides a value relating to the battery life of the tracking module. For example, the battery level element data value may be presented as a percentage of battery remaining, or as the time or period during which the battery is completely depleted or depleted to a threshold level.

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

[0184] In one embodiment, the device management system 40 is configured to allow a user to assign tracking modules to players. The assignment of tracking modules can be done, for example, based on the grouping of players in a round. Referring to Figure 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 tab format so that a user can perform a device management or device assignment operation from either interface by simply selecting the desired tab. In one embodiment, the device assignment user interface 420 can receive groupings from a grouping engine and automatically assign tracking modules to groups and players from a device list.

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

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

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

[0188] In one embodiment, the device management system 40 may be configured to load a group number and the shells of the devices assigned to that group. In various embodiments, each assignment within a group may be in a sequential order. The order may be static unless assigned to a group and then reassigned. As described above, the device list may include a list of all tracking modules that are not assigned to a group and are therefore assignable. The device management system 40 may be configured to allow a user to assign devices in the device list to groups. The user may further assign devices in a specific order within a group. Once a device is assigned to a group, the user can save the assignment via a device configuration save operator.

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

[0190] In one embodiment, by assigning a tracking module to a player, the STTM system's backend associates the tracking module identification number with the player, the identification number is attached to the data obtained from and / or recorded by the tracking module, and the STTM system components receiving the data, such as a companion device, location system, verification system, data management system, device management system 40, and / or data platform, associate the player to whom the identification number has been assigned. Such STTM system components can receive the player and tracking module identification number assignments set by the device management system 40 for this purpose. In one example, a companion device receives the player and tracking module identification number assignments set by the device management system 40, associates the tracking module data with the player during scoring, and stores and / or transmits it to the same STTM system component, for example. As described above, the STTM system may include a location network configured for device-side and / or network-side location tracking, for example, using a UWB anchor network. In network-side location tracking use cases, device and player assignments are sent to system components configured to calculate location from data collected by the network-side location network, or are subsequently used to associate the tracking module's calculated location data with that of the assigned player.

[0191] As described above, and also referring to Figures 6A-6G, the STTM system may include a round management system 60 configured to manage rounds and groupings of players playing in an event. The round management system can provide data manager data access to round management operations from local, remote, and / or any location via a management device. In various embodiments, groupings may be managed by a grouping engine 500 configured to record one or more of the following: saving tee times, adjusting to pre-announced 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. Rounds may be managed by a round engine 501 configured to manage either or both round states or round cuts.

[0192] The grouping engine 500 may be configured to manage groupings. Managing groupings includes creating groupings of players. In one example, the grouping engine 500 may be configured to allow a user to define and manipulate groupings for every round of every event. Figure 6A shows the user interface of the grouping 500 engine, including a grouping management panel 503 configured to interface various operations of the grouping engine 500 to the user.In various embodiments, the grouping management panel 503 may be configured to provide one or more elements, for example, interface elements, display elements, or associated operation elements, which include: (a) a grouping presentation element 504 consisting of a list of groups with associated teatimes for each segment; (b) a display element 505 with segments that can be operated to allow the user to view each segment, a defined portion of a segment, or all segments at once; (c) a player list element 506 identifying players who are not grouped or can be grouped; (d) a segment list element 507 identifying segments created for a particular round; (e) a round selection element 508 that can be operated to allow the user to select a round in order to review and edit the groupings associated with a segment in that round; (f) a segment profile selection element 509 that can be operated to load a previously created profile with segment information; and (g) segments for creating or modifying segments for a round. (h) a grouping generation element 511 configured to generate groupings based on predefined and / or definable round segmenting rules, (i) a player removal element 512 configured to remove players from a grouping presentation component while retaining teatime data, (j) a shell generation element 513 configured to generate groupings that do not contain players but have groupings based on round segmenting rules, (k) a grouping clear element 514 configured to remove player and teatime data from a grouping presentation component, (l) a grouping state element 515 containing a selectable list of grouping states, (m) a revision element 516 for accessing operations of a revision editor that can be operated to adjust groupings and flag rounds as revised groupings, or (n) a player status element 517 for providing access to operations of a player status editor that can be operated to change the status of players in a round in an event.

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

[0194] As will be explained in more detail later, various grouped data and / or round data may be subject to revision. In the diagram, grouped data that has been revised from the original value is labeled (R) in this example to indicate the revision of the original teatime.

[0195] In various embodiments, the grouping engine 500 can provide various display and / or editing options with respect to the grouping and associated data elements within the grouping presentation. For example, the grouping engine 500 can provide interface elements that allow the user to sort the data columns by, for example, numerical, alphabetical, chronological, or other appropriate data point characteristics. In one example, an interface element can be provided that causes the user to selectively present grouping by segment number or grouping by all segments at once. In the above or another example, the grouping engine may be configured to allow the user to edit the data points of a row of data. For example, the editing function may be provided together with or separately from the displayed data. In one embodiment, the displayed data elements referenced in Figure 6B may consist of interface elements that display the respective data point values ​​and are configured for user interaction to optionally edit the data point values. The grouping engine 500 can provide editing capabilities for grouping data elements selected from: (a) a segment number editor containing a list of available segments created or loaded from a profile; (b) a group number editor that allows the user to change a group number value (usually a positive integer); (c) a tea time editor that allows the user to change a tea time (e.g., hour:minute); (d) a tea time date editor that allows the user to change a tea time date (e.g., month:day:year); (e) a course editor that allows the user to change a course (which may include a selectable list of courses available for the selected tournament and event); (f) a player editor that allows the user to change a player (e.g., when a player is selected, a field is provided to enter another player, or a list of selectable players is displayed, which may include drag-and-drop or other selectable methodologies); or (g) a combination of these.As described above, the display elements in the grouped presentation 518 may consist of interface elements. In one embodiment, interaction with such interface elements may trigger the editor operations described above. 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 Figure 6A, the player list element 506 may selectively display, or be configured to display, a list of all players in the field of a selected event who are not placed in or assigned to a group in the grouping presentation 518. In various embodiments, the user can assign players to tee time through interaction with the player list element 506 or through another interface element in the grouping presentation 518. In one embodiment, the player list element 506 is configured to display the player's name and the player's total event score relative to par.

[0197] The grouping engine 500 can utilize segments and segment profiles. A segment may include a tee time block that indicates the starting point of a round. For example, two segments of a group may include one starting at the 1st hole and the other starting at the 10th hole. A segment profile may include a set of segment rules that the grouping engine 500 uses to assist in grouping generation. The grouping engine 500 may include or access one or more segment profiles. Segment profiles 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 may define, save, load, or delete one or more profiles that the grouping engine 500 applies to an event or round. In one embodiment, the grouping engine 500 is configured to allow the current user to find other users who include relevant segment profiles, such as segment profiles and / or user profiles, or segment profiles created by or previously used by other users. For example, a user can select a segment profile and import the selected profile into the current event or those profiles, or export the segment profile to another user's profile.

[0198] Figure 6C shows the segment profile management interface 525, which includes an example of a segment profile element along with definitions of options for editing data elements or creating new segments. The example elements and definitions of options for editing may be available to the segment data manager to create a new segment profile. An element may include one or more data elements selected from: (a) segment number selection 526, which contains a list of segments created for the selected round; (b) segment priority 527, which consists of non-repeating positive integer values ​​set for other segments associated with a round, so that a particular segment can exist in the system once per round; (c) course 528, which contains a list of courses associated with the selected event; (d) date 529, which identifies the date on which the tee time begins play; (e) tee time 530, which identifies the first tee time for start or end; (f) tee time (start / end) 531, which includes an option to flag the tee time as the start or end tee time; (g) time between the start or end time set in tee time (above) and tee time (start / end) (above). (h) A time interval 532 used to specify intervals; (h) Groups in an interval 533 that identifies the number of groups that make up an interval, while the remaining groups are in different intervals, as if set, applied using the first interval (below) and the remaining intervals (below); (i) A first interval 534 that represents the number of groups defined in the Groups in an interval (above); (j) Remaining intervals 535 that represent the time intervals for groups not defined in the Groups in an interval (above); (k) Best score last / first 536 that identifies whether the best-scoring player is set for the first tee time or the last tee time; (l) The starting hole for all tee times in the segment 537; (m) Players per group 538 that identifies the maximum number of players assigned to a group; (n) Number of groups 539 that identifies the initial number of groups in 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 to allow users to create or delete segments. For example, elements of a segment profile may be editable through interaction with elements in the display, where options for editing the elements consist of interface elements used by the user to edit data elements or other aspects of the segment profile. For example, to delete a segment, the user can select Delete Segment 541 from the segment profile management interface 525. To create a new segment, the user can select Create New Segment 542 from the segment profile management interface 525. Upon selection, the user is presented with default data elements that have the next sequential number from the current segment in the profile, the currently selected course, or a predefined time interval. In various embodiments, additional data elements may be set to other default values ​​or left blank to be further specified by the user.

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

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

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

[0203] When generating groupings, a player slot for each player can be identified based on the number of players per group, as defined in the segment configuration, and each slot represents the order in which each player plays. A slot referred to as 1 is the first player to play, a slot referred to as 2 is the second player to play, and so on. If multiple segments are part of a round's segment profile, the grouping engine 500 can automatically begin assigning players to the segment set as priority 1 and then sequentially assign players to each segment as it completes its player assignments. If Best Score Last / First 536 is set to Last, player assignments can begin from the last tee time of the segment and work backward from there. If Best Score Last / First 536 is set to First, player assignments can begin from the first tee time of the segment and work forward from there. Regarding player selection and slotting when Best Score Last / First 536 is set, the grouping engine 500 may assign the player with the best tournament score to the first slot, the player with the second-best score to the second slot, and continue assigning players until each slot in the tee time is filled before moving on to the next tee time. In some embodiments, segment profiles can link multiple players. In one example, if multiple players are tied, the grouping engine 500 can determine the next player assignment by applying the following ordering rules: (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 a segment profile for a selected round to create a grouping shell, or for automating grouping. For example, when a grouping generation element 511 is invoked, the grouping engine 500 is configured to create a grouping using the profile currently selected for that round. Teatime may be generated based on the configuration of each segment in the segment profile, as described above. When a shell generation component is invoked, the grouping engine may be configured to generate a grouping shell, presenting slots based on the number of players assigned to each group for each segment.

[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 the following: (a) Draft, (b) Scheduled for Review, (c) Reviewed, (d) Formal, or (e) a combination thereof. The "Draft" state can be available while the user is working to create the groupings required for a round. In one embodiment, the "Draft" state may be set as the default state when the groupings are first created. The "Scheduled for Review" state may be set when the defined set of groupings is ready for review. The "Reviewed" state may be set when the defined set of groupings has been reviewed and the review has determined that it is ready to move to the "Formal" state. The "Formal" state may be set when the set of groupings has been reviewed, approved, and ready for distribution.

[0206] In various embodiments, the grouping engine 500 may be configured to apply one or more grouping state rules. For example, the grouping engine 500 may restrict the setting of grouping states that progress toward formal, skipping grouping states. For example, the "Reviewed" grouping state cannot be set until the "Reviewed" 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 may be configured to log all grouping states with a timestamp of the user's selection. The user who made the grouping state selection may also be logged and associated with the selection.

[0207] In some embodiments, the grouping draft is saved for subsequent review by the grouping engine 500. In one example, the saved grouping draft is not distributed to other STTM system components. In some embodiments, reviews may be performed to modify the grouping, for example, to create a group of interest, to prevent players from being in the fast group for several weeks in a row, to separate players known to be slow players, or to separate players who are not alone. In one example, once the grouping data enters a state for review, the administrative user can review the data and then, upon signing off, set the grouping date to the "approved" state. Once the grouping data is approved and the associated state is set to "approved," the grouping data becomes available to other STTM systems.

[0208] As described above, the grouping engine 500 may include a revision editor. In the illustrated embodiment, operation of the revision editor may be initiated by interaction with the revision element 516 of the grouping management panel 503. The revision state can be specified in various states. For example, revision states include "Revision Scheduled," "Revision," and "Revised." The "Revision Scheduled" state may be set as the default state, which is set after the grouping has become formal and before the revision process starts and before the revision is performed. The "Revision" state is displayed when a user using the revision editor is in the process of revising a grouping that already has a state set to "Formal." The "Revised" state may be displayed when the grouping review process is completed and there are changes from the original grouping which was set to the formal grouping state. In one embodiment, when changes are made to a grouping or data element updated by the revision editor, the revision state may be 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 at any time after the original grouping has been set to the “formal” grouping state, when the grouping validation process is complete.

[0209] The revision editor may include various operations that the user can use to adjust the tea time from the current grouping's tea time. For example, Figure 6D shows the interface of a revision editor 545 configured to adjust the tea time using either an offset element 546-based revision or a revision using a reference time element 547 methodology. The offset element 546-based revision allows the revision editor 545 to apply an offset-based revision that utilizes start and end groups. The start and end groups may be predefined or set by the user, for example by interacting with the start and end group elements 548, and represent the start and end groups from which the tea time is adjusted. The time-based revision element 547 allows the revision editor 545 to apply an offset-based revision, which in one embodiment may also include a time adjustment that can be specified via interaction with the adjustment time (+ / -) element 549 in the illustrated interface, consisting of an amount of time applied to the original tea time of the group identified by the setting of the start and end group steps. The start and end group and / or adjustment time (+ / -) elements 548, 549 may include interface elements containing fields for entering text, selectable lists of groups and / or time differences, or other appropriate interface elements. A revision using a base time method can allow the user to utilize a new base tea time that replaces the original base tea time through interaction with a new base time element 550, and the adjustment of the remaining tea time is then generated based on the data elements defined in the round's segment profile. In various embodiments, once a revision is used and applied, the round state is set to “Revision”, and the grouping engine 500 starts the grouping validation process.

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

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

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

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

[0214] The round state element 572 may be operable to select a round state, and may constitute a selectable list of available round states or be presented for user selection. In some embodiments, one or more round states may be set automatically by the round engine 501. In various embodiments, round states may include: (a) Not Started - the default state before grouping is formally set; (b) Grouping Formal - corresponding to when each grouping of the round is set as “Formal” as described above, and only available in that case; (c) In Progress - a state that is automatically set when the first stroke or score of the round is made, and which in some embodiments may be additionally or alternatively set manually; (d) Suspended - a state that is set when the round is suspended due to weather or other circumstances; (e) Play Completed - a state that is automatically set when the last score of the round is made, and which in some embodiments may be additionally or alternatively set manually; (f) Formal - a state that is set when no further changes to the round data are needed, such as changes to stroke information or scores; (g) Cancelled - a state that is set when the round is canceled and the remaining time of the event is not played; or (h) a combination of these.

[0215] In various embodiments, when the round state is set to “suspend,” the user can select a suspension type using the suspension type element 573. In one example, the round engine 501 may request or prompt the user to select a suspension type when setting the round state to “suspend.” In various embodiments, the suspension type element 573 may include or be operable to present a selectable list of suspension types for user selection. Exemplary suspension types may include one or more of delay, cancellation, suspension, or end of day.

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

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

[0218] Regarding the cut rules, selectable settings can include 579 cuts, 580 cuts to play, 581 maximum strokes from the leader, 582 target cuts, 583 including amateurs, or a combination of these. 579 cuts corresponds to the number of players who are cut based on their score and whose player status remains uncut, while all other players set to uncut have their player status set to "cut". 580 cuts to play corresponds to the number of players who are cut based on their score and continue to play the round. If this is set, the difference between 579 cuts and 580 cuts to play may include players whose player status is set to "cut but did not finish". All other players can have their player status set to "cut". 581 maximum strokes from the leader may correspond to the number of players who are cut by a number of strokes relative to par from the leader. 582 target cuts can correspond to the number of players who are cut closest to a set value, regardless of whether it is above or below that value. If players have the same value whether above or below a certain threshold, all players with higher values ​​are considered "uncut," and all remaining players have a player status of "cut." The 583, including amateurs, can be configured to include amateurs as part of the cut rules. If configured, participating amateurs are part of the cut rules. If not configured, amateurs are not included in the cut rules. The 583, including amateurs, can be selected in addition to other components of the cut rules. If a selectable setting is included, it should be understood that different and / or additional settings may be provided.

[0219] The round management panel 570 may also include a round information storage element 585 that gives the user the option to save or cancel changes made to the round status and / or cut configuration. In one embodiment, once 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 player statuses as defined above until the user executes a cut rule option.

[0220] The round management panel 570 may 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 may include a playoff creator component that can operate to provide access to a playoff round creator configured to create playoffs for selected rounds. Figure 6G shows an exemplary user interface of the round engine 501 configured to interface with the user the various operations of the playoff round creator 586.

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

[0222] The playoff creator 586 may be configured to include multiple selectable playoff types for selection via the playoff type element 587, such as one or more playoff types selected from “Sudden Death”, “Number of Holes”, and “Number of Holes / Sudden Death”. “Sudden Death” corresponds to a playoff format in which players start from the first playoff hole and continue playing until they have a better stroke score than the other players in the playoff. If two or more players are playing, the player who scores higher than the best score on that hole is eliminated. “Number of Holes” corresponds to a playoff format in which all players in the playoff play a number of holes defined in the order of the starting holes below. If there is a player with the best score, that player wins and the playoff ends. If there is a tie score after the predetermined number of holes, the playoff repeats for the predetermined 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 be eliminated unless their score is better than the best score. "Number of Holes / Sudden Death" corresponds to a playoff format in which all players participating in the playoff play a defined number of holes in the order of the starting holes below. If a player achieves the best score, that player wins and the playoff ends. If there is a tie score after the defined holes, the playoff enters the sudden death phase as defined above.

[0223] The playoff number element 588 can set or be operable to set a playoff number, allowing the user to remember multiple playoffs for a round. The determined position element 589 can define or be operable to define the position of the players played in the playoff. For example, the determined playoff position could 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 defines, or may be operable to define, the hole on which the playoff is first played. In the case of a "number of holes" playoff format, the start hole sequence element 590 provides the holes defined for that format. The repeating hole pattern element 591 defines, or may be operable to define, a repeating hole pattern for a "sudden death" playoff format in the case where a winner has not been determined after the holes of the start hole sequence have been completed.

[0225] The playoff saving 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 initiation element 594 may be operable to initiate a playoff. In one embodiment, the playoff may not be initiated by 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 initiated before the previous round is completed.

[0227] Once 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 settings of playoff number 588 and / or determined position 589. The playoff round creator 586 can then be configured to apply the remaining playoff settings to create a new round according to the rules. Players who have qualified for the playoff round may be placed in a group, which may automatically include up to four players per group as described above, although in some embodiments manual group placement may be used. In some embodiments, the grouping for the playoff may be configured to be reviewable via a grouping presentation. In another, or further, embodiment, the round status may be automatically set to "Group Formal".

[0228] As described above, companion devices can be used by scorers to perform scoring functions. Scorers may include caddies, players, or other people observing the play. Companion devices can run ST applications. Companion devices may include wireless data communication transceivers configured to wirelessly transmit score data, which may include event data, to STTM system components. During play, each group may have an assigned companion device that a scorer uses to collect score data. The score data is transmitted to a management system, which is configured to process data received from multiple companion devices during play. Companion devices can consist of various wireless communication technologies as described above, which may include short-range and / or long-range communication with devices in the STTM system. Companion devices may be configured to communicate with a tracking module to trigger and / or define data collection events that may be used to formally score a player's round. For example, a companion device may be carried by a scorer accompanying a group of players or by 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 the location system, location elements, and / or other STTM system components. The companion device may also transmit collected score data and / or event data to the location system, location elements, and / or other STTM system components.

[0229] In various embodiments, the companion device may be configured to wake up the tracking module and initiate event capture, such as collecting event data (e.g., event capture, location / location determination, or relevant 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 instructions for event capture. Instructions may be transmitted by the companion device or the management device. For example, the companion device and / or the management device may be networked with multiple tracking modules, or otherwise, capable of providing instructions to and / or receiving instructions or data from multiple tracking modules. It should be understood that the management device may include or provide data to the location system.

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

[0231] ST applications or companion devices (which may be local, remote, web-based, or cloud-based) that run and / or access ST applications may be used by scorers 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 will be discussed in more detail elsewhere in this specification. References to transmission of scoring data from companion devices and / or tracking modules, which may include event data and / or location data, may include indirect or direct transmission to one or more location systems, management systems, and / or data platforms. For example, scoring data may be transmitted immediately or subsequently to location systems and / or one or more management systems for applications configured to perform further data management, data review, data correction, score verification, data analysis, data storage, location, location calculation, zoning, or other STTM system operations. Data viewing platforms may refer to distribution to subscription services or platforms such as downstream clients, business or consumer-level platforms, private or public networks for consumption by fans alone or in conjunction with other data, surface web platforms, etc. In various embodiments, scoring data may be distributed or made available for use or integration with web applications, mobile applications, or other applications for public or private viewing, analysis, or archiving.

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

[0233] When a tracking module is used to acquire location information, the ST application or other STTM system applications or services can combine the location information with stroke level data. In laser operator-level scoring, the scorer may use the ST application to record strokes without additional location information, or they may track the player's position via a tracking module for use in combination with laser position tracking, either via a manual laser pointing device such as those used by PGA Tour laser operators, or via the operation of an automated laser system that tracks or continuously tracks the ball's position throughout a round. The laser information can be output to or converted to a coordinate grid system based on mapping, such as course surveying or GPS. In combined use configurations, location data obtained from different technologies may be used for separate end uses, 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 ST application can be configured so that one scorer can collect stroke level data for all players in a group.

[0234] In one embodiment, the companion device may be configured to have certain event data preloaded or accessible via the ST application, such as (a) the par value of a particular course, (b) the hole sequence of the course (which may be associated with the par value), (c) a predefined starting location (which may include a location indicator, as well as locations selectable on the "Starting Location" screen), (d) the score level of the event (stroke recording only, or utilization, and / or incorporation of location tracking, e.g., GPS, UWB, BLE, Wi-Fi®, cellular, etc., rangefinder, laser operator, or a combination thereof), (e) the course name, (f) player names in a group, player numbers in a group, player images, player group data for assigned groups such as headshots, multiple groups, or all player groups in the event, or (g) a combination thereof. In one example, the ST application runs at least partially in a cloud-based environment, and the event data is automatically provided to the companion device, for example, at startup. If an event takes place across multiple courses, course data for a specific course or multiple courses may be provided or selectable by the scorer, for example, through a user interface. Course names and course numbers may be provided. The companion device may automatically provide round details, including group updates, group assignments, event changes, event notifications, or details of other rounds.

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

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

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

[0238] To track a player's hit, the companion device can present a selectable list of players that the scorer can choose from. When tracking a player's hit, the companion device may be configured to present a selectable list of locations where the player will hit their shot. Examples of locations include the teeing ground, the fairway, the primary rough on the green, bunkers, sandy areas, fringes, waste areas, or natural or habitable areas. In one configuration, the “starting location” should be set for the player at any time and “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 the location or indicates that the ball has been hit.

[0239] In one example, the scorer may also input when the player addressed the ball. This may be entered as an event, for example, when the player first addresses the ball, or as a toggle. In the case of a toggle, the companion device's user interface may include an "address" button that the scorer presses when the player is approaching the ball. The scorer can then indicate that the ball has been hit by pressing a "shot hit" button or by other means. The ST application may interpret "address" as remaining down until the scorer presses or taps the "shot hit" button or other indicator, at which point both the address and hit events are sent 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 sent in real time before indicating that the ball has been hit. In other embodiments, the interaction may be sent together in real time after the shot has been made, or it may be stored locally for subsequent transmissions. When collecting location data, such as location coordinates, for shots using a tracking module, the ST application may be configured to associate the tracking module assigned to a player with the player's name. When the scorer indicates that the ball has been hit, the tracking module's position is captured and recorded as described elsewhere in this specification. In some configurations, the capture of the tracking module's position may be triggered via interaction with the “Address” button.

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

[0241] As described above, the user interface can present a “shot hit” button or other indicator that the scorer can interact with to indicate when the ball has been hit. In one example, the “shot hit” indicator is a button that the scorer taps when the ball is hit. In another example, the “shot hit” indicator is a button that the scorer holds down until the ball is hit, and releasing the button, rather than simply “pressing,” indicates that the ball has been hit. In yet another example, a multi-stage “shot hit” indicator or multiple indicators can be used to indicate at least two of the following: address, location timestamp, and shot hit. For example, a two-stage “shot hit” indicator could be used, with the first stage showing the address and / or location, and the second stage showing the location and / or shot hit. In one configuration, the scorer can press the two-stage indicator button when the player is in the address position and release the indicator button when the ball is hit, with pressing setting the location timestamp and releasing interpreting the ball as 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 may present buttons, swipe bars, or fields, etc., that the user can interact with to indicate whether the ball is in the hole. In one example, the scorer is presented with a two-way swipe field, and the scorer indicates "yes" or "no" by swiping the field in the desired direction. 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 a lack of indication as a null response with the value that the ball is not in the hole. In another configuration, the ST application may similarly take a lack of indication as the ball is in the hole. The scorer may have the option of indicating a null response or allowing time to expire. For example, the scorer may swipe right for in, swipe left for out, and allow time to expire for in. After indicating that the ball has been hit or that the ball has not entered the hole, the user interface automatically returns to the group page, from which the scorer can select the same player or the next player to record the same shot. Once the scorer indicates that all players have entered the hole, the scorer can be prompted to show or make available a button or other indicator to proceed to the next hole. In another example, once 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 may be collected in real time and stored locally or transmitted immediately, periodically, at scheduled intervals, when a companion device is close to a management device (which may include a network access point or node), when a predetermined amount of data has been collected, or when events occur such as the collection of other scoring data or when one or all players have completed a hole or group of holes, or based on the remaining available data storage.

[0244] Referring to Figures 7A-7V, which show various user interfaces of the ST application 700 according to various embodiments, the scorer can interface with a companion device to provide a player description. The interface may include various data input screens on which the scorer can input data. The screens may include predefined selectable options presented, for example, in the form of list boxes, checkboxes, dropdowns, input steppers, text input fields, etc. The ST application 700 may be pre-programmed to present one or more descriptive categories, each category containing multiple descriptive options that the scorer can select with respect to a selected or identified player. In some embodiments, the ST application 700 may include a field on which the scorer can input a text description. The description can be entered into one or more predefined descriptive categories selected by the scorer. In some configurations, the scorer may input descriptive information or define descriptive categories by voice or text. The provision of fields for descriptive input may be in addition to, or instead of, one or more predefined descriptive categories and / or multiple options within such descriptive categories. In one embodiment, the ST application 700 may include or incorporate a photo application or otherwise be configured to input an image of the player. The ST application 700 can associate an image with a player. In yet another embodiment, the ST application 700 is configured to perform image analysis to analyze the player's image and extract descriptive attributes such as the color of the clothing the player is wearing. In this example or another, the ST application 700 can display the captured player's image on a companion device, or on another device that transmits the image directly or indirectly 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 one 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, for example, in Figure 7B. In one configuration, the ST application 700 can pre-enter player names, such as players in a group that the scorer should track. In these or other configurations, the ST application 700 may provide a field for the scorer to manually enter player names, or it may provide a selectable list of groups or players.

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

[0247] By selecting the description button, the ST application 700 can display one or more description categories 705. In the example shown in Figure 7C, the user interface displays a context box containing multiple descriptive categories 705 for the scorer to select. The scorer can select a descriptive category from the available options and be presented with multiple selectable descriptions. For example, in Figure 7C, the scorer is presented with three descriptive categories 705 related to clothing: "Player Shirt," "Player Pants," and "Player Cap." If "Player Shirt" is selected, several descriptive features 706 related to the player's shirt are displayed, from which the scorer can select. The scorer can select descriptive categories that make it easy to distinguish players. For example, the scorer can select one or more garments that distinguish a player from other players so that it can be distinguished from a distance as to which player is taking a shot. If further clarification is needed, the scorer can provide the most appropriate description. In Figure 7D, the descriptive features relate to color. In this example, the descriptive features also include additional characteristics, which are identified as optional in this example, from which the scorer can further define the player shirt. In the illustrated interface, the scorer selects green as the player shirt color and light as the optional description. In some embodiments, such as the one shown in Figure 7D, the user interface may require the scorer to confirm their selection with a 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. While the description categories in the illustrated embodiments relate to clothing items, in some examples, different descriptive categories or descriptive features may be provided in addition to, or instead of, clothing items, such as shoes, clubs, bags, or brand names of items.

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

[0249] The ST Application 700 may include a scoring function that allows the scorer to input multiple details about the play, including club type, shot location, stroke, penalty, scoring, and lie.

[0250] Referring to Figure 7F, in some embodiments, the ST application 700 may be configured to generate a club selection function on the user interface that can be used by a scorer to identify the club a player is currently using to hit and / or set up a golf ball during play. For example, on the group screen 710, the scorer can select a “Club Selection” button 709 associated with a player. For example, on the teeing ground, the scorer may select the “Club Selection” button 709 and be presented with a club selection 711, as depicted in Figure 7G. The club selection can include any number of clubs, such as the entirety of a player’s bag or an exhaustive list of potential clubs. In one embodiment, the club selection is programmed to correspond to clubs that a player is likely to use at a particular location on the course. For example, using the location of a companion device and / or a tracking module carried by the player, the ST application 700 can determine which club selection to present to use that the player will 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 Figure 3. For example, the location system may determine the location of the tracking module from location data provided to the location system, where the location coordinates are applied to a predefined coordinate range corresponding to a defined zone to determine which zone the tracking module is currently located in. Figure 7G shows that the scorer has selected the "Iron" button, indicating that the player is teeing off with an iron on the second hole of a par 3. In one embodiment, the companion device 12 will not respond to the selection of the player name unless the scorer first inputs the club. Club selection can be made before the player arrives at the ball and / or before the player hits the ball. It is preferable that the scorer inputs the club before the player hits the ball, but in some embodiments, the club selection may be entered after the player hits the ball.

[0251] The companion device 12 running the ST application 700 may be configured to receive precise 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 moment the player hits the ball. To display the “Shot Hit” button 712, the scorer can select the name of the player to whom they want to “Shot Hit” from a group screen 710 (Figure 7F). Referring to Figure 7H, the user interface includes a “Shot Hit” button 712 that the scorer uses to signal a shot by pressing and holding a finger on the button before the ball is hit and releasing the finger at the moment the ball stops moving. For example, when the player addresses the ball and is ready to hit the shot, the scorer presses and holds the “Shot Hit” button 712. Then, at the exact moment the player hits the shot, the scorer releases the button to indicate that the shot has been hit. This action signals the system to record the position of the tracking module at that moment, which corresponds to the player's position. This location information may further be associated with the player's club selection. This data may be stored in the tracking module, companion device, or associated memory, or it may be transmitted to the management device at the time the scorer indicates that a player or group has completed a hole, or it may be transmitted periodically, at scheduled intervals, based on the proximity between the tracking module or companion device and the management device, or based on their storage capacity. As described in more detail elsewhere in this specification, location information can be input into an application configured to render a graphical display of a digital stroke trail showing the details of the shots in a round.

[0252] In some embodiments, when the scorer releases the "Shot Hit" button 712, the scorer then inputs the ball's landing location on 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 the user interface may have location buttons that the scorer can use to select from multiple locations or to input a location into a provided field. In the embodiment shown in Figure 7I, when the "Shot Hit" button 712 is released, the user interface displays a "In Hole" prompt 713, which allows the scorer to indicate whether the ball is in the hole or not. As shown, the interface for the In Hole prompt 713 requires a directional swipe, with left for "No" and right for "Yes". However, other interface buttons or methods may be used. Referring to Figure 7J, after the scorer indicates whether the ball has entered the hole, the user interface can return to the group screen 710, which displays the recorded shots. The group screen 710 may also include a notification or indicator 714 indicating that the player is currently playing on a hole. As shown, the text below the player's name has changed to “Starting Location,” indicating that the player is between shots on the hole. This indicator 714 can also function as a button to trigger the tracking module to collect location information when the player hits their next shot, in a similar manner to that described for the first shot.

[0253] Referring to Figures 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 the “Starting Location” screen 716, which includes several locations that the scorer can select to indicate where the player is hitting the shot. As illustrated, the scorer can select a fairway bunker, fairway, first cut, natural area, deep rough, pond, greenside bunker, fringe, other, or green. In this embodiment, the option to select “Tee” is not available because the player has not yet hit the first shot. However, selecting “Provisional” or “Penalty Drop” will enable the selection of “Tee.”

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

[0255] After the starting location is entered on the "Starting Location" screen 716, the user interface may display the group screen 710. As shown in Figures 7M and 7N, the location indicator 714 may change to what the scorer has selected, for example, the fairway. The scorer then selects a player name and displays the "Shot Hit" button, which allows the scorer to indicate the moment the ball was hit by the player, and then indicate whether the ball went into the hole, for example, in the same manner as described above.

[0256] Recording the time and location of each player's putt can be done in a similar manner to that described above for other shots. In various embodiments, once 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 may allow the user to select a different location after a subsequent shot that does not enter the hole and may, for example, roll off the green. Figure 70 shows the group page 710 with the first two players having finished the hole and the third player on the green. When it is the third player's turn to putt, the scorer can select the player's name and press and hold the "Shot Hit" button that appears when the player is about to putt, releasing it when the player putts the ball, and recording the time and location of the putt via the tracking module's location as described with respect to Figure 7H. The user interface may then display a "In Hole" prompt that the scorer can use to record whether the ball entered the hole, which may be similar to that described with respect to Figure 7I. If the ball did not enter the hole, the scorer records the next putt as before. When a ball enters a hole, the ST application 700 records that the player has finished the hole, and the scoring process restarts from the next tee box. In one example, after the scorer has recorded that all players in the group have entered a hole, a location indicator 714 appears on the group. The location indicator 714 on the group page 710 may automatically return to "Select Club". In another example, the user interface may indicate to the scorer that a hole has been completed and prompt them to move to the next hole.

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

[0258] Figure 7P shows how to record a second shot from a tee that has been recorded as provisional. Using the "Starting Location" screen 716, the scorer selects "Provisional" and then the starting location, which in this example is the "Tee". The display then returns to the group screen 710, where "Provisional" is displayed as the location indicator. The scorer can then 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 at the position indicator 714 below the player's name until the scorer selects the player's name to record the position of the next shot. Figure 7R shows the prompt 720 that appears after the player's name has been selected, which asks the scorer to indicate whether the player is using a provisional shot. If the scorer indicates that the player is not using a provisional shot, scoring proceeds as usual. If the scorer indicates that the player is using a provisional shot, a penalty stroke is awarded and displayed on the group screen 710, as shown in 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 selects the starting location, which in this example is “Deep Rough.” The display then returns to the group screen 710, as shown in Figure 7U, with “Penalty Drop” displayed as a location indicator 714 below the player's name. The scorer can then select the player's name before the player drops the ball. Referring to Figure 7V, for example, the scorer is presented with a penalty drop prompt 721 that provides the scorer with a “Ball in Play” button 722 to use to indicate when the player has dropped or retrieved the ball. This allows the penalty stroke to be evaluated, and the position and time of the shot continue to be recorded as described above.

[0261] Free drops can be recorded in the same way as penalty drops, 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 the score tracking system. The data management system 50 can provide data administrators with local, remote, and / or management device access to management operations from any location.

[0263] The data management system 50 may include a data management tool 800 which includes an interface element, display element, or associated operation element selected from one or more elements, for example, (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 scorecard 807, (h) a team player stroke details 808, or (i) a full group presentation 809. Figure 8A shows an exemplary user interface of the data management tool 800 for use with the data management system 50 which provides the elements listed above in a presentation block. In various embodiments, the page layout of the elements is configured to create connections between blocks and / or data elements within it. For example, selecting an element in one block may establish a connection to other blocks. In further examples, the other blocks with which connections have been established may be updated with appropriate presentations, as will be described in more detail below. However, it will be understood that the elements and related components and their data that can operate to provide the operation of the data management system 50 may be provided in many formats, and this disclosure is not limited to the specific arrangement and combination of elements and user interface components described herein.

[0264] The event selector 801 can contain a selectable list of one or more events available for viewing and managing related data. For example, the event selector 801 contains a dropdown list of all viewable events. Selecting an event can cause or enable a presentation block to display the related data for that event.

[0265] The round selector 802 may contain a selectable list of one or more rounds of an event available for viewing and managing related data. In one example, the round selector 802 consists of a dropdown list of all available rounds of an event selected with respect to an event selector component. In a further example, the selection of a round may cause a presentation block to present, or be prompted to present, the round data for the selected event. In a further example, the round selector 802 and / or the presentation block may default to the most recent round in progress. If no round is in progress, the default may be the earliest round with a “Grouped Formal” round status, as described in more detail with respect to the round management system 60.

[0266] The course selector 803 may include a selectable list of one or more courses available for viewing and managing related data for selected events and rounds. In one example, the course selector 803 consists of a dropdown list of all courses available for the selected events and rounds. Course selection can cause or enable a presentation block to present course data for the selected events and rounds. In one example, if multiple courses are played in an event and round, the default course may be set to the host course. In another example, or further examples, the course selector 803 may include a selectable option to select all courses. In such an example, selecting all courses would present data for all courses in the presentation block in a single combined presentation.

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

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

[0269] The hole graphic display 806 may be provided with 2D graphics (although more advanced graphics such as 3D may also be used). The hole graphic display 806 may include various navigation functions. For example, the hole graphic display 806 may include one or more of the following: a zoom function that allows the user to selectively zoom in and zoom out of the graphic; a graphic rotation function that allows the user to selectively rotate the graphic along 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, which can zoom in on the green, zoom out to view the entire hole, and / or zoom out to view the entire course. In one embodiment, the graphic is oriented in a way that allows for maximum visibility from tee to green, such as an overhead view, tee view, and green view. The hole graphic display may include various display distances to the hole. For example, either or both of the scorecard yardage distance or the actual yardage distance between the tee and 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 may be displayed for each round, such as the tee position, pin position, and / or one or more fairway center points of the course. In one embodiment, the graphic display may be configured to display all players in a group at once, upon request from the user, for example, through interaction with a “Show 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 plotting 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 that include location coordinates, lines may be displayed between the plotted points to depict the stroke trajectory. Since the starting point is the tee and the ending point is the pin, the data management tool 800 may generate lines from these points to the coordinates of the player's stroke on the hole or to the stroke having the ending point. In one example, the distance from the tee to the plotted ball position, 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 allowing the user to input the location of a received stroke, move existing locations assigned to strokes, create strokes with their locations, display all collected GPS or other location coordinates for team players, and / or delete strokes along with their locations. In the example of the above features where breadcrumbs are present, the hole graphic display 806 may be configured to allow the user to "lock" strokes to the breadcrumbs.

[0272] In one embodiment, the above function includes displaying all GPS coordinates and / or other coordinates collected for the team players, including those not related to strokes, such as breadcrumbs. 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 the entire group presentation 809 may cause the group scorecard 807 to populate data related to the group. 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 specific hole in 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] Figure 8B shows an exemplary interface 810 of a group scorecard 807 that is presented by or accessible through interaction with the group scorecard data management tool 800, all or part of which may be available in the respective presentation block views. Various elements of the group scorecard 807 may be viewable and / or editable through the operation and functionality of the group scorecard 807, as will be described in detail below with respect to each element. The group scorecard 807 may include various data elements such as one or more of the following: (a) team player names 811, (b) stroke events 812, (c) stroke count 813, (d) total 814, (e) total 815, (f) today 816, (g) front nine holes by hole score 817, (h) score out 818, (i) back nine holes by hole score 819, (j) score in 820, (k) total strokes, or (l) stroke official 821.

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

[0276] Stroke event 812, if flagged, can present the last stroke event received from the score tracking system or, in one instance, the verification system. Various stroke events may be presented, such as club selection, addressing the ball, shot hit, provisional, reserve, final, and in-hole. In one configuration, stroke event 812 may not be edited via the group scorecard component of the data management tool 800.

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

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

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

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

[0281] ScoreOut 817 can display the total strokes of the score entered in the front nine. In one configuration, ScoreOut 817 may not be directly editable via the group scorecard component of the data management tool 800.

[0282] The Back 9 Holes with Hole Score 818 can present a list of hole-by-hole scores for the back nine holes. In some embodiments, depending on the configuration, column or row headers may be provided to indicate the hole number for improved clarity. In one configuration, the Back 9 Holes with Hole Score 818 may be configured to be edited via the Group Scorecard component of the Management Tool 800 by entering integers or by deleting scores from the hole score field.

[0283] ScoreIn 819 may display the total strokes of the score entered for the back nine. In one configuration, the 819 score may not be directly edited via the group scorecard component of the data management tool 800.

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

[0285] Official Stroke 821 can display the strokes received for the team player on all holes that have been flagged as official. In some configurations, this element can be edited by the user to indicate that no further edits will be made to any stroke on any hole for any player.

[0286] Figure 8C shows an exemplary interface for the Team Player Stroke Details 808 of the data management tool 800, which is configured to interface its operation to the user. The interface can be presented through interaction with the Team Player Stroke Details 808 elements in each presentation block view of Figure 8A, or it can be accessed through interaction with the Team Player Stroke Details 808 elements. The elements of the Team Player Stroke Details 808 may be displayed. In the operation of the Team Player Stroke Details 808, the user can edit various elements. In some embodiments, when a player is selected in the group scorecard 807 or the whole group presentation 809, the data elements for each selected group are populated into the Team Player Stroke Details 808 interface.

[0287] When a team player is selected for presentation and / or stroke editing using the team player stroke details 808, the hole graphic display 806 may be set to default 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 scorecard 807, for example, by selecting a hole from the hole 816 from the front nine holes by hole or the front nine holes 818 (Figure 8B) data element view, the team player stroke details 808 presents the stroke details of the player for that specific hole. Thus, the data management tool 800 may be configured to allow the user to selectively view hole-by-hole strokes using the group scorecard 807 or to view hole stroke details through interaction with the team player stroke details 808.

[0288] In one example, the hole graphic display 806 presents a representation of the hole by viewing the stroke details of a team player for that hole via the team player stroke details 808. 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. Functionality such as zooming in and zooming out of the graphic may be provided, as described above. For example, a quick zoom operator may be provided so that the user can quickly zoom to different areas of the hole, such as the tee box, fairway, hazards, green area, or a specific selected shot. Functionality may also include moving the graphic within a static display area, for example, within any zoom value, to change the longitude and latitude of the view. Yard distances may also be displayed relative to the set positions of the tee and pin. Other yardages may be displayed within or against the graphic, as described above.

[0289] The data elements of the Team Player Stroke Details 808 may include a variety of informational and scoring data elements, such as (a) Team Player Name 822, (b) Stroke Number 823, (c) Stroke Accessed 824, (d) Stroke Event 825, (e) Timestamp 826, (f) Stroke Type 827, (g) Location 828, (h) Club 829, (i) Provisional 830, or (j) In Hole 831. The data elements may correspond to those collected by the ST application through 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] Team Player Name 822 can contain a list of all team players in a group. For example, if you select a group from the All Group Presentation 809 or Group Scorecard 807, the team players in that group may be entered into Team Player Name 822. The presentation may also display data about a single player, which may be set to any player, such as the last player whose stroke event was recorded or who completed a hole, or the first player in a predefined tee-off order. In one configuration, Team Player Name 822 may not be edited via Team Player Stroke Details 808.

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

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

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

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

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

[0296] The time stamp 826 can correspond to those of the stroke events 825, such as the latest stroke event 825. In one configuration, the time stamp 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 be set. In various embodiments, the data management tool 800 can automatically apply various rules to the editing of the stroke type. For example, when the created stroke type is "drop", the accessed stroke 824 may be zero. When the created stroke type is "drop", the stroke number 823 may be the same as the previous stroke or penalty type. When the created stroke type is "penalty", the accessed stroke 824 may default to 1. When the created stroke type is "penalty", the stroke number 823 may be incremented 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, a location system, the operation of a rangefinder, manual input via an indication of the ball position relative to a displayed map, or other location methodologies used by an STTM scoring system. In one configuration, Location 828 can be editable to change the location from a list of available descriptions of locations on the golf course being played, such as a tee box, fairway, rough, first cut, hazard, pond, out of bounds, green, etc. In one example, interaction with the location data element may display a drop-down including a list of available locations on 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 editable 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 if the 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 accessed strokes. 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 Figure 8D, in various embodiments, a stroke event review viewer 832 may be provided. For example, each stroke in the player's stroke details 808 can be optionally expanded to display additional related stroke events. In the illustrated viewer, stroke events for a stroke are entered into the stroke event 823 element. As shown, the stroke event for stroke number includes club selection, address, shot hit, pre-shot, and final. Thus, as a result of the stroke, the player did not hold the ball. In various embodiments, the stroke details received from the companion device are marked as "pre-shot" and are subject to review via the operation of the data management tool 800 or validation system described later, and if the review is successful, the stroke details can be set to "final". In one configuration, the fields of the stroke event review viewer 832 are not editable except for the timestamp field. The stroke event review viewer 832 may be configured to allow the user to rearrange or reorder the stroke events. The stroke event review viewer 832 may be configured to allow the user to collapse the review of stroke events, such as presenting only the most recent stroke events.

[0302] Figure 8E shows an exemplary interface of the data management tool 800 for the entire group presentation 806, configured to interface with the user and its operations. All or part of the interface may be presented in each presentation block view in Figure 8A, or accessible through interaction with the entire group presentation 806 provided therein. Various elements of the interface may be viewable and / or editable through operations on the entire group presentation 806.

[0303] The All Group Presentation 809 may be configured to display a selected round, or to display only the selected round. In one example, the All Group Presentation 809 is configured to display information for a selected course, or, if selected, for all courses in the tournament. In one configuration, the display may be scrollable, and / or each column of data may be sorted in either ascending or descending order based on the information available in the column. In one configuration, none of the fields of the All Group Presentation 809 may be editable directly through the All Group Presentation 809. In one embodiment, the presentation of the All Group Presentation 809 may include a notification regarding the names of team players if the team players' scorecards have been flagged as “official” through a verification system, for example, which is described in more detail elsewhere in this Specification.

[0304] The entire group presentation 809 includes: (a) Group number 832 - corresponding to the number assigned to the group; (b) Course 833 - corresponding to the course the group is playing on; (c) Starting hole 834 - corresponding to the first hole the group started on, based on the round grouping; (d) Tee time 835 - corresponding to the group's starting tee time; (e) Rank 836 - corresponding to the expected ranking of the players in play during the ongoing round; (f) Team player name 837 It may include one or more of the following data elements: (g) Total 838 - corresponding to player identification, (h) Today 839 - corresponding to the par relative score of the round, (i) Front 9 Holes by Hole Score 840 - corresponding to a list of hole-by-hole scores for the first 9 holes, (j) Score Out 841 - corresponding to the total strokes of the scores entered for the front 9, (k) Back 9 Holes by Hole Score 842 - corresponding to a list of hole-by-hole scores for the back 9 holes, (l) Score In 843 - corresponding to the total strokes of the scores entered for the back 9, or (m) Total Strokes 844 - corresponding to the total strokes of the round, displayed if data for Score Out 841 and Score In 843 is available.

[0305] Figure 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 Figure 8A, or may be accessible through interaction with the data mismatch panel components provided therein. Various elements of the interface may be viewable and / or editable through operation of the data mismatch panel 805.

[0306] The data mismatch panel 805 may include two sub-elements: 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 mismatch panel 805 can be manipulated to improve user experience and efficiency. For example, data rows may be scrollable. Data columns may also be sortable in either ascending or descending order based on the information available in the columns. In one configuration, the data mismatch panel 805 can provide an interface element that can be manipulated to flag warnings as reviewed and remove warnings from the presentation. In one example, the data mismatch panel 805 may allow the user to review all warnings flagged as reviewed, review errors and warnings by group, hall, or team player, reset and display all errors and warnings if any have been set as reviewed and removed, scroll through all messages per panel if some messages cannot be displayed in the initial display, or turn on or off rules for all or selected error and / or warning message rules. In one example, no fields may be editable.

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

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

[0310] Warning message 854 may relate to an event or absence detected by the data management tool 800 that may not yet be an error, or cannot yet be confirmed as an error based on available data, but is abnormal compared to the expected behavior of a scoring system, which may include a location system. Warning message 854 may be displayed with relevant identification information. Warning message 854 may include a variety of issues, such as: one or more tracked players not being synchronized with the strokes of other team players in the group; multiple consecutive drops by a team player; a drop without penalty in a team player's stroke trajectory; a stroke's coordinates not being closer to the pin than the coordinates of the previous stroke; more than 10 minutes between a team player's strokes; multiple strokes including positions from the teeing ground; an unusual score by a team player, such as a double bogey, worst score, eagle or better; 5 minutes have passed but coordinates for a stroke have not been received; a team player was on the green but appears to be off the green; a driving distance outside the normal distance range for a par 4 or par 5, such as less than 180 yards or more than 380 yards; a stroke being flagged as being on a hole more than 30 yards away; the pin not being set and a team player's stroke being received on that hole; or the tee not being set and a team player's stroke being received on that hole.

[0311] Referring to Figure 8G, in various embodiments, the presentation blocks and / or one or more related components of the data management tool 800 described with respect to Figures 8A-8F may be configured to create connections between them. For example, a presentation block layout may be configured to create connections between block views of component elements. For example, when an element is selected or otherwise interacted with in one block view, etc., with respect to related elements, 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 to all group presentations 809. In one embodiment, selecting a team player's name may cause one or more of the following to occur: the group scorecard 807 to display the group to which the team player belongs; the hole graphic display 807 to display the current hole that the team player has not completed; the team player stroke details 808 to display the strokes taken by the team player on the current hole that the team player has not completed; or the data mismatch panel 805 to display all errors and warnings for the selected team player on all holes. In the above or another embodiment, selecting a group number may cause one or more of the following to occur: the group scorecard 807 to display the selected group; the hole graphic display 806 to display the current hole, defaulting to the top team player in the group and the current hole that the team player has not completed; the team player stroke details 808 to display the strokes taken by the top team player in the group on the current hole that the team player has not completed; or the data mismatch panel 805 to display all errors and warnings for the selected group. In either of the above embodiments or any other embodiment, selecting a hole for a team player can cause the group scorecard 807 to display the group to which the team player belongs, the hole graphic display 806 to display the selected team player and the selected hole, the team player stroke details 808 to display the strokes taken by the selected hole and team player, or the data mismatch panel 805 to display 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, interaction with the group scorecard 807 may result in connections with one or more other components of the data management system 50. For example, selecting a team player's name may cause one or more of the following to occur: the hole graphic display 806 presents the current hole that the team player has not completed; the team player stroke details 808 presents the strokes taken by the team player on the current hole that the team player has not completed; the data mismatch panel 805 presents all errors and warnings for the selected team player on all holes; or the all-group presentation 809 presents the group or team player at the top of the presentation. In yet another example, selecting a team player's hole may cause the hole graphic display 806 to present the selected team player and the selected hole; the team player stroke details 808 presents the strokes taken by the selected hole and the team player; the data mismatch panel 805 presents all errors and warnings for that hole and team player, which may include warnings flagged as reviewed; or the all-group presentation 809 presents the group or team player at the top of the presentation.

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

[0315] In any of the embodiments described above or any other embodiment, interaction with the hall graphic display 806 may result in connections with one or more other components of the data management system 50. For example, by selecting location coordinates assigned to a stroke, the selected stroke may be highlighted in the team player's stroke details component.

[0316] In any one or another embodiment of the above embodiments, interaction with the data mismatch panel 805 may trigger connections with one or more other elements of the data management system 50. For example, by selecting an error or warning to review, the presentation of the group scorecard 807 may be updated based on the team players and groups identified in the error or warning message. In another or further example, by selecting an error or warning to review, the presentation of the hole graphic display 806 and / or the team player's stroke details 808 may be updated based on the team players identified in the error or warning message.

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

[0318] The verification system 70 may be configured to operate in various network environments as specified herein with respect to its various STTM systems / subsystems. For example, the verification system 70 may be configured to operate in a local, remote, or distributed network-based environment. The verification system 70 may be configured to operate in a web-based, cloud-based, or other suitable network environment. In one embodiment, the verification system 70 may operate within a browser or a browser-like environment. For example, the verification system 70 may include a verification application that has the ability to run on multiple browser tabs with different settings. In a further example, the verification system 70 includes an edit tracking function in which the verification system 70 tracks edits made by users. These user edits are tracked as being associated with the specific user who made the edit. The tracking function of the verification system may be configured to store the tracked edits by 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 about the edits each user made to the scorecard. In some configurations, the verification system 70 may allow a reviewing user to view user edits by type, such as score, stroke, location, and stroke type (drop, shot, penalty). In this configuration or another, the verification system 70 may be configured to allow the reviewing user to view edits of one or more types made by one, more, or all users within a specific 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 scorecard 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 scorecard and compare it with a second score collection method such as an automatic or semi-automatic scoring method. In this specification, the operation of the first tool may sometimes 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 equally apply to the operation of the verification system. Accordingly, the first verification tool may be configured for blind verification that allows a user to input the score of a player's scorecard, 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 rankings of the players. In various embodiments, the verification tools can be arranged in selectable tabs, and each tab includes 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 scorecard. The event selector 902 can include a list of selectable events. By interfacing with the event selector 902, a dropdown, list, or other selectable form of an event for selection can be triggered.

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

[0323] The cut line 904 may be provided so that the user can view a display of the current real-time cut data. In some embodiments, the cut line 904 is displayed only when the selected round is a cut round. By viewing the cut line 904, the user can gain insight into what changes are possible to the cut. For example, changing the score of one player may cause several other players to either be on or off the cut.

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

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

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

[0327] A score entry system may be provided for entering a player's score from the player's scorecard. The score entry system may include a hole field 910 for entering scores for all holes of a round, for example, an 18-hole field. The hole field 910 may be configured for manual entry. In one example, the hole field 910 includes a dropdown, toggle field, or other suitable input method for each hole with selectable scores. In the illustrated embodiment, the score entry includes a hole field 910 that requires the user to make each field editable by using the Enter key or Tab to select the hole field 910, for example, along with mouse navigation. As will be discussed later, scores recorded by the score tracking system and received by the verification system 70 may be absent or otherwise hidden from view so as to be blind to the user's perspective when comparing manual score entry with subsequent score tracking system scores.

[0328] System-received scores, such as scores received from the score tracking system, can be imported into the verification system 70. In some embodiments, the import of score tracking system scores may be performed automatically upon receipt of the scores or with a delay. Score data and associated player data may be imported into the verification system periodically after each hole is completed, after a predetermined number of holes, or when a player or group completes 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 completed a hole or 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 a player selected on the scorecard is not officially flagged, the system-received score is either invisible or blank while the user enters the score for the purpose of blind verification.

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

[0330] As a result of the comparison operation, the system-received score may be entered into a Hall field 914 juxtaposed with the corresponding Hall field 910. Validity notifications may be displayed for the Hall or related score to indicate a match, a mismatch, or both. For example, when the option to compare a blind entry score with the system score is triggered, the system score may be displayed, along with validity notifications indicating what matches and what does not. In the illustrated embodiment, a solid arrow 918 between the blind score Hall field 910 and the system-received score Hall field 914 indicates a match, and a dashed arrow 920 indicates a mismatch. Validity notifications may be provided by any appropriate display. For example, matches and / or mismatches may be indicated by different colors, shading, text, outlines, boxes, symbols, or other appropriate perceptible displays.

[0331] The first verification tool 901 may include a formality marker 922 that allows the user to flag a scorecard as official. For example, if blind verification shows that all scores match, the user can interact with the formality 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, scores may be editable by the user to resolve discrepancies. In some configurations, discrepant or edited scores are submitted or saved for further review. As described above, marking a scorecard as official means that the scorecard, score, or acknowledgment flag, along with an indication that the score is official, can be sent to a database for storage and / or distribution to one or more data platforms. 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 platform to indicate that the score is now official by flagging the score as official via a verification system.

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

[0334] Referring to Figure 9B, the second validation tool 830 may present scoring data for one or more groups. The presentation may be configured to display scores from selected events and / or rounds, as selected with respect to the first validation tool 901. The presented scores may include informal tracking scores and formal scores. Various score transmission timing schemes may be used, as described elsewhere in this specification. In various embodiments, tracking scores may be entered when transmitted to the companion device 12, such as after each shot hit entry or when a player or group completes a hole.

[0335] Scoring data can be arranged in various formats. In the illustrated embodiment, the scoring data is arranged so that each column of data is sorted in either ascending or descending order based on the information available in that column. Fields are typically not editable from the basic user's perspective. 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 about that player or group from a second validation tool is populated. Thus, the user can select a player or group and see additional details about that player or group's score. In one example, if manual score entry has not been entered or processed by validation, selecting a player or group populates the group selector and / or player selector fields for the selected player or group. In one embodiment, players with scores marked as official are marked with a visual indicator as a notification.

[0336] The presented scoring data may include various data points about players and their scores, such as one or more of the following: (a) Group number 931 - corresponding to the group number assigned to the group of players; (b) Course played 932 - corresponding to the course from which the scoring data was collected; (c) Starting hole 933 - corresponding to the first hole from which the group started based on the grouping of the round; (d) Tee time 934 - corresponding to the group's starting tee time; (e) Rank 935 - the predicted rank of the player in play during the ongoing round; (f) Team player name 936 - each team player in the group. (g) Total 937 - Corresponding to the player's last and first name, (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 hole-by-hole scores for the first 9 holes, (j) Score Out 940 - Corresponding to the total strokes of the scores entered for the front 9, (k) Back 9 Holes by Hole Score 941 - Corresponding to a list of hole-by-hole scores for the back 9 holes, (l) Score In 942 - Corresponding to the total strokes of the scores entered for the back 9, (m) Total Strokes 943 - Corresponding to the total strokes of the round, or (n) a combination thereof. In various embodiments, Total Strokes 943 is displayed only if there is data in Score Out 940 and Score In 942.

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

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

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

[0340] The location system can access the assignment of tracking modules and pair timestamps with the locations of the assigned tracking modules. The data management system can access the scoring data and review and edit it as needed using data management tools. Next, the verification system compares the scores from the score tracking system with each player's scorecard. For example, the verification system may apply blind verification. The verification system then matches the scores from the score tracking system with the players' scorecards. The verification system marks the matched system scores 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 devices and tracking modules 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 may utilize additional location tracking techniques. Such techniques may act as primary, secondary, backup, or alternative location determination methods with respect to the use of the tracking module.

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

[0343] In one embodiment, a camera system is positioned around a golf course. One or more cameras can track motion and determine distance using associated lasers or rangefinders, or through optical calculations. For example, each camera can calculate the distance to a ball or other object of known size by comparing the size of an optically captured object to the size of a known object. By further determining the camera angles, the position of an object at distance and angle from the camera can be plotted on a map of the area around the camera. Positioning may be enhanced by 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 the course area from the field of view of a fixed camera can be used by the camera to determine the position of an object relative to a known location in the mapped area. For example, the approximate position of an object can be determined by comparing an image of the object with surrounding features in an image of a known location. To improve the accuracy of positioning, distance may be determined using optical calculations as described above. In the above or other embodiments, radar may be implemented to track an object, including its position, velocity, trajectory, acceleration, or other parameters. In the above or other embodiments, the cameras may be configured for optical recognition. For example, the camera may utilize facial recognition, body recognition, gait recognition, clothing recognition, ball / shape recognition, etc., used to identify participants and / or the ball, thereby pairing locations with players and / or player balls. In one embodiment, players carry or wear optical, electromagnetic, or reflective makers identifiable by a camera or associated receiver that uniquely identifies the player. In one embodiment, the camera may utilize optical recognition / augmented reality (AR) to locate the player and / or ball. The cameras may typically be placed in known locations, but in some cases, one or more cameras may be used in a mobile environment utilizing a real-time kinematic base station or camera positioning methodology, such as those described herein with respect to tracking module positioning.In some embodiments, the camera is used to identify motion and objects, and a laser or rangefinder associated with the camera may target such objects to determine their distance from the camera. The camera's field of view and distance can be combined to determine the object's position. In some embodiments, the topology of a region can be mapped or determined and incorporated into distance calculations. In some embodiments, such a camera system is operated by a human, a robot, or fully autonomously. The camera may operate in a visual spectrum and / or optical spectrum, including one or more of the visual spectrum, the ultraviolet spectrum, or the infrared spectrum.

[0344] The systems and methods disclosed herein may include further functionalities and features. For example, the operational functions of the systems and methods may be configured to run on a dedicated processor specifically configured to perform the operations provided by the systems and methods. Notably, the operational features and functions provided by the systems and methods may enhance the efficiency of computing devices used to facilitate the functions provided by the systems and various methods disclosed herein. For example, by training the system over time based on data and / or other information provided in the system, the amount of computer operations that need to be performed by devices and elements within the system using the system's processor and memory may be reduced compared to conventional methodologies. In such situations, less processing power is required because the processor and memory do not need to be dedicated to processing. As a result, using the software, techniques, and algorithms provided herein results in substantial savings in the use of computing resources. In certain embodiments, various operational functions of the system may be configured to run on one or more graphics processors and / or application-specific integrated processors. In some embodiments, various functions and features of the systems and methods may operate without human intervention and be fully implemented by computing devices. 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. Furthermore, in certain embodiments, the computing devices of the system may operate continuously without human intervention to reduce the possibility of errors being introduced into the system.

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

[0346] In some embodiments, the machine may operate as a standalone device. In some embodiments, the machine may be connected to and assist in operations performed by other machines and systems (e.g., using a communication network, another network, or a combination thereof), such as tracking modules, companion devices, management devices, and associated system servers, databases, other systems, programs, and / or devices, or any combination thereof. The machine may be connected to any component within a 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 consist of a server computer, a client user computer, a personal computer (PC), a tablet PC, a laptop computer, a desktop computer, a control system, a network router, a switch, a bridge, or any machine capable of executing a set of instructions (whether sequential or not) that specify the actions to be performed by that machine. Furthermore, although a single machine is illustrated, the term “machine” also includes any set of machines individually or collectively executing a set (or set of) instructions to perform one or more of the methodologies discussed herein.

[0347] A computer system may include a processor (e.g., a central processing unit (CPU), a graphics processing unit (GPU), or both), main memory, and static memory, which communicate with each other via a bus. The computer system may further include a video display device, which may be, but is not limited to, a liquid crystal display (LCD), a flat panel, a solid-state display, or a cathode ray tube (CRT). The computer system may also include, but is not limited to, input devices such as a keyboard, cursor control devices such as a mouse, a disk drive unit, signal generators such as speakers or remote controls, and network interface devices. The disk drive unit may include, but is not limited to, 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 those illustrated above. Instructions may also reside entirely or at least partially in main memory, static memory, within the processor, or a combination thereof, during execution by the computer system. Main memory and the processor may also constitute machine-readable media.

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

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

[0350] This disclosure envisions a machine-readable medium containing instructions that enables a device connected to a communication network, another network, or a combination thereof to use the instructions to transmit or receive voice, video, or data and to communicate over the communication network, another network, or a combination thereof. Instructions may further be transmitted or received over the communication network, another network, or a combination thereof via a network interface device. The term “machine-readable medium” should be understood to include a single or multiple mediums (e.g., a centralized or distributed database, and / or associated caches and servers) that store one or more sets of instructions. The term “machine-readable medium” should also be understood to include any medium capable of storing, encoding, or carrying a set of instructions for machine execution, which enables a machine to execute one or more of the methodologies of this disclosure. The terms “machine-readable medium,” “machine-readable device,” or “computer-readable device” are, accordingly, considered equivalent distribution media to tangible storage media, but are not limited to solid memory such as memory devices, memory cards or other packages containing one or more read-only (non-volatile) memories, random-access memories, or other rewritable (volatile) memories, magneto-optical media or optical media such as disks or tapes, or other self-contained information archives or sets of archives. “Machine-readable medium,” “machine-readable device,” or “computer-readable device” may be non-transient and, in particular embodiments, may not include waves or signals themselves. Accordingly, this disclosure is considered to include one or more machine-readable media or distribution media, including equivalents and successor media recognized in the art, which are enumerated herein and on which software implementations herein are stored.

[0351] The examples of configurations described herein are intended to provide a general understanding of the structures of various embodiments and are not intended to serve as a complete description of all elements and features of devices and systems that may utilize the configurations described herein. Other configurations can be utilized and derived therefrom, allowing for structural and logical substitutions and modifications without departing from the scope of this disclosure. Furthermore, the figures are representative only and may not be drawn to scale. Certain proportions may be exaggerated, and others may be minimized. Thus, this specification and the drawings are to be considered illustrative rather than restrictive.

[0352] Therefore, while specific configurations have been illustrated and described herein, it should be understood that any configuration calculated to achieve the same objective can be substituted for the specific configurations illustrated. This disclosure is intended to cover all adaptations or variations of various embodiments and configurations of the present invention. Combinations of the above configurations, and other configurations not specifically described herein, will be apparent to those skilled in the art upon consideration of the above description. Thus, this disclosure is not limited to any specific configuration(s) disclosed as the best mode contemplated for carrying out the present invention, and the present invention is intended to include all embodiments and configurations belonging to the appended claims.

[0353] The above is provided for the purpose of illustrating, describing, and illustrating embodiments of the present invention. Modifications and adaptations to these embodiments will be obvious to those skilled in the art and can be made without departing from the scope or spirit of the invention. By examining the embodiments described above, it will be apparent to those skilled in the art that the embodiments can be modified, narrowed, or enhanced without departing from the claims and spirit described below.

Claims

1. A score tracking method, the method including: A step of collecting or receiving location data by a location system, wherein the location data corresponds to the location of a tracking module carried by a player participating in a golf tournament, and the location data includes a plurality of sets of location coordinates or is 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; A step of receiving instructions for the occurrence of a stroke event related to the player, wherein the instructions are input into the companion device by a scorer who is carrying a companion device and observing the player who is carrying the tracking module; The steps include receiving or generating a timestamp corresponding to the time when the instruction for the occurrence of the stroke event was input to or received from the companion device by the scorer; and The step of pairing the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

2. The method according to claim 1, wherein the set of location coordinates corresponds to the position of the tracking module over a certain period of time, and each set of location coordinates corresponds to a predetermined time interval within the certain period of time.

3. The method according to claim 1, wherein the tracking module is configured to receive location signals from a plurality of beacons arranged around a golf course.

4. The method according to claim 3, wherein the location data includes parameters of the location signal used by the location system to calculate the set of location coordinates.

5. The method according to claim 3, wherein the tracking module uses the parameters of the location signal to calculate its position and transmits the position to the location system as location data.

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 location signals received by a plurality of beacons arranged around a golf course in order to calculate the location data corresponding to the position 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 positioned around a golf course, which are configured to receive location signals transmitted by the tracking module to track the position of the tracking module.

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

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

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

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

13. The method according to claim 12, wherein a single companion device is configured to receive instructions for the score event relating to a plurality of players, each carrying a separate tracking module.

14. The method of claim 13, wherein the location data and the score event instruction 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 the matching of the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurs includes matching the respective identification data.

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

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 the 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.

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

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

22. The method according to claim 1, wherein the plurality of sets of location coordinates consists 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 predetermined first interval and to transmit the collected location data to the location system at a predetermined second interval, wherein the second interval is greater than the first interval.

24. The method according to claim 1, further comprising 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 the plurality of sets of location coordinates.

25. A score tracking system, the system includes the following: A tracking module designed to be carried by players participating in golf tournaments; An application configured to interface scoring operations to a user via the user interface of a companion device, wherein the companion device is separate from the tracking module and is configured to receive input via the user interface that instructs the occurrence of a stroke event, the input causing the application to set a timestamp corresponding to the occurrence of the stroke event; 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 time the stroke event occurred.

26. The system according to claim 25, wherein the set of location coordinates corresponds to the position of the tracking module over a certain period of time, and each set of location coordinates corresponds to a predetermined time interval within the certain period of time.

27. The system according to claim 25, wherein the tracking module is configured to receive location signals from a plurality of beacons placed around a golf course.

28. The system according to claim 27, wherein the location data includes parameters of a location signal configured for the location system to use to calculate the set of location coordinates.

29. The system according to claim 27, wherein the tracking module is configured to use the parameters of the location signal to calculate its position and transmit that position to the location system as location data.

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 location signals received by a plurality of beacons arranged around a golf course in order to calculate the location data corresponding to the position of the tracking module.

32. The system according to claim 25, wherein the location data is transmitted to the location system from one or more beacons positioned around a golf course, which are configured to receive location signals transmitted by the tracking module in order to track the position of the tracking module.

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

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

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

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

37. The system according to claim 25, wherein a single companion device is configured to receive instructions for score events relating to a plurality of players, each carrying a separate tracking module.

38. The system according to claim 25, wherein 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, and the location system is configured to match the respective identification data to the timestamp with the set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred.

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

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

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

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

43. The system according to claim 25, 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.

44. The system according to claim 25, 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.

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

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

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

48. The system according to claim 25, wherein the location system is configured to divide the holes of a golf course into zones, each zone corresponding to a range of 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 location coordinates.

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

50. A score tracking system, the system includes the following: A tracking module designed to be carried by players participating in golf tournaments; An application configured to interface scoring operations to a user via a user interface of a companion device, wherein the companion device is separate from the tracking module and is configured to receive input via the user interface that indicates 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 includes an indicator configured to be pressed to indicate that a player is addressing the ball and held until the player hits the ball to indicate that the ball has been hit; 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 time the stroke event occurred.

51. The system according to claim 50, wherein the position of the tracking module at the time of the stroke event is used as a proxy for the position of the ball of the player carrying the tracking module due to the previous stroke.

52. The system according to claim 50, wherein the tracking module operates as a beacon in the 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 consist of a set of GPS coordinates.

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

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

60. The system according to claim 50, wherein the location system is configured to divide the holes of a golf course into zones, each zone corresponding to a range of 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 location coordinates.

61. The system according to claim 50, wherein the companion device is configured to be carried by a scorer accompanying a group of players, including the player, and the companion device is configured to receive input corresponding to the stroke events of all players in the group.

62. A score tracking method, the method including: A step of receiving input from a companion device corresponding to a stroke event of a player participating in a golf tournament, wherein the input includes a timestamp corresponding to the occurrence of the stroke event; A step of collecting or receiving location data by a location system, wherein the location data corresponds to the position of a tracking module carried by the player, and the location data includes a plurality of sets of location coordinates, or is 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 A step of pairing the timestamp with a set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurs, wherein the companion device includes an interface configured to receive input corresponding to the stroke event, the stroke event includes an address and a ball hit, and the interface includes an indicator configured to be pressed to indicate that the player is addressing the ball and 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 input corresponding to the stroke events of all players in the group.

64. A score tracking method, the method including: A step of receiving input from a companion device corresponding to a stroke event of a player participating in a golf tournament, wherein the input includes a timestamp corresponding to the occurrence of the stroke event; A step of collecting or receiving location data by a location system, wherein the location data corresponds to the position of a tracking module carried by the player, and the location data includes a plurality of sets of location coordinates, or is 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 A step of pairing the timestamp with a set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred, wherein the stroke event is input to the companion device by a scorer viewing live video of the golf tournament.

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

66. The method according to claim 64, wherein the tracking module operates as a beacon in the 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 the 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.

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

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

72. The method according to claim 64, wherein the plurality of sets of 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 predetermined first interval and to transmit the collected location data to the location system at a predetermined second interval, the second interval being greater than the first interval.

74. The method according to claim 64, further comprising 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 the plurality of sets of location coordinates.

75. A score tracking method, the method including: A step of receiving an input from a companion device corresponding to a stroke event of a player participating in a golf tournament, wherein the input includes a timestamp corresponding to the occurrence of the stroke event; A step of collecting or receiving location data by a location system, wherein the location data corresponds to the position of a tracking module carried by the player, and the location data includes a plurality of sets of location coordinates, or is 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 A step of pairing the timestamp with a set of location coordinates corresponding to the position of the tracking module at the time the stroke event occurred, wherein the stroke event is 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 the stroke event is used as a proxy for the position of the ball of the player carrying the tracking module resulting from a 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 the 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 of claim 75, wherein the location data collected or received by the location system includes location identification data used by the location system to calculate the location coordinates.

82. The method according to claim 75, wherein the plurality of sets of location coordinates consists of a set of GPS coordinates.

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

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

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 location coordinates, and determining the current zone in which the tracking module is located from the plurality of sets of location coordinates.

Images