Golf event management system with scoring and location tracking

Abstract

A fractional tracking system may include a tracking module, a companion device, and a location system. The tracking module may be configured to be carried by players participating in a golf tournament. The companion device may be configured to receive an input corresponding to a ball hitting event, the input including a timestamp corresponding to an occurrence of the ball hitting event. The location system may collect or receive location data, the location data including a plurality of sets of location coordinates, or the location system generates a plurality of sets of location coordinates using the location data. Each set of position coordinates may correspond to a position of the tracking module at a specified time. The location system may pair the timestamp with a set of location coordinates corresponding to the location of the tracking module at the occurrence of the ball striking event.

Description

Technical Field

[0001] The present disclosure relates to the management of golf events, including systems and methods for score and position tracking that are broadly applicable to a variety of network infrastructures. Background Art

[0002] Managing the play of a golf tournament while also providing detailed location and score tracking for each stroke requires a complex backstage dance that is even more difficult due to the variability of course locations and infrastructure. For example, before each Professional Golfers' Association TOUR (PGA TOUR) event, each golf course is mapped to create a digital image of each hole, which is used as background information to calculate the exact location and distance between any two coordinates, such as the tee and the player's first shot or shot location and the location of the hole. Using the mapped data and the ShotLink system, the PGA Tour collects the location of each ball and the score of each stroke for each round. In addition to pre-game mapping, the ShotLink system also utilizes a complex and expensive infrastructure that takes several days to set up and disassemble and must be transported between events. The successful operation of the ShotLink system also depends on a volunteer team of up to 350 volunteers per event. The game data provided by the ShotLink system has proven to be extremely valuable to both fans and players. However, the time, cost, and infrastructure required to operate the ShotLink system make the ShotLink system impractical for use in lower-level tournaments.

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

[0004] In a first aspect, a score tracking system includes one or both of a tracking module and an application or a location system. In one example, the tracking module and one or both of the application or the location tracking system can be according to any example, configuration or embodiment described herein. In one example, the tracking module can be configured to be carried by a player participating in a golf tournament. The application can be configured to dock a user with a scoring operation via a user interface of a companion device. The companion device can be separated from the tracking module and configured to receive an input indicating the occurrence of a shot event via a user interface. The input can cause the application to set a timestamp corresponding to the occurrence of the shot event. In one configuration, the shot event includes aiming and a ball hit. In the above and another configuration, the interface includes an indicator that is configured to be pressed to indicate that the player is aiming the ball and is 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 can be configured to collect or receive location data. The location data can include a plurality of location coordinate sets, or the location system can generate a plurality of location coordinate sets using the location data, wherein each location coordinate set corresponds to the location of the tracking module at a specified time. In one example, the location system can be configured to pair the timestamp with a set of location coordinates corresponding to the location of the tracking module at the occurrence of the striking event.

[0005] In any one or another of the above examples of the first aspect, the position of the tracking module at the occurrence of a stroke event may be used as a proxy for the position of the ball of the player carrying the tracking module resulting from a previous stroke.

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

[0007] In any one or another of the above examples of the first aspect, the tracking module may be configured to transmit the location data to the location system.

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

[0009] In any one or another of the above examples of the first aspect, the location data collected or received by the location system includes positioning data, and the location system calculates the location coordinates using the positioning data.

[0010] In any one or another of the above examples of the first aspect, the plurality of location coordinate sets include a Global Positioning System (GPS) coordinate set.

[0011] In any one or another of the above examples of the first aspect, the plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

[0013] In any one or another of the above examples of the first aspect, the location system may be configured to segment the holes of the golf course into regions, each region corresponding to a series of location coordinates, and wherein the location system may be configured to determine the current region in which the tracking module is located from a plurality of sets of location coordinates.

[0014] In any one or another of the above examples of the first aspect, the companion device may be configured to be carried by a scorekeeper who accompanies a group of players including the player. The companion device may be configured to receive input corresponding to a shot event for all players in the group.

[0015] In any one or another of the above examples of the first aspect, the stroke event comprises a ball strike.The position of the tracking module at the occurrence of the stroke event can be used as a proxy for the position of the ball of the player carrying the tracking module resulting from a previous stroke.

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

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

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

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

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

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

[0022] In any of the above examples of the second aspect, the companion device may be carried by a scorekeeper who accompanies a group of players including the player, and the companion device may receive input corresponding to shot events of all players in the group.

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

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

[0025] In any one or another of the above examples of the second aspect, the location data collected or received by the location system includes positioning data, and the location system calculates the location coordinates using the positioning data.

[0026] In any one or another of the above examples of the second aspect, the plurality of location coordinate sets include GPS coordinate sets.

[0027] In any one or another of the above examples of the second aspect, the plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

[0029] In any one or another of the above examples of the second aspect, the method includes segmenting a hole of a golf course into regions, each region corresponding to a series of position coordinates, and determining a current region where the tracking module may be located from a plurality of sets of position coordinates.

[0030] In any or another of the above examples of the second aspect, the stroke event comprises a ball hit, and the position of the tracking module at the occurrence of the stroke event can be used as a proxy for the position of the ball of the player carrying the tracking module resulting from a previous stroke.

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

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

[0033] In a third aspect, a score tracking method includes collecting or receiving location data by a location system. The location data may correspond to the location of a tracking module carried by a player participating in a golf tournament. The location data may include a plurality of location coordinate sets or may be used to generate a plurality of location coordinate sets, each of which may correspond to the location of the tracking module at a specified time during play of the golf tournament. In one configuration, the method may include receiving an indication of the occurrence of a shot event associated with the player, the indication being input into a companion device by a scorekeeper who carries the companion device and views the player carrying the tracking module. In one configuration, the method may also include receiving or generating a timestamp corresponding to the time at which the indication of the occurrence of the shot event was input into the companion device by the scorekeeper or received from the companion device. 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 occurrence of the shot event.

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

[0035] In an example of the third aspect or the fourth aspect, the plurality of position coordinate sets correspond to positions of the tracking module within a time period, and each position coordinate set corresponds to a predefined time interval within the time period.

[0036] In the above example or another example of the third aspect or the fourth aspect, the tracking module can be configured to receive location signals from a plurality of beacons, the plurality of beacons being positioned around the golf course. In one configuration, the location data includes parameters of the location signals, and the location system calculates a plurality of location coordinate sets using the parameters of the location signals. In one configuration, the tracking module calculates the location of the tracking module using the parameters of the location signals, and transmits the location to the location system as the location data.

[0037] In any one or another of the above examples of the third aspect or the fourth aspect, the tracking module may be configured to output a position signal, and the tracking module calculates the position data using the position signal.

[0038] In any one or another of the above examples of the third aspect or the fourth aspect, the tracking module can be configured to output a position signal for receipt by a plurality of beacons to calculate position data corresponding to the position of the tracking module, the plurality of beacons being positioned around the golf course.

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

[0040] In any one or another of the above examples of the third aspect or the fourth aspect, the timestamp corresponds to the time at which the indication of the occurrence of the hitting event is input into the companion device, and the companion device generates the timestamp and transmits the timestamp to the location system.

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

[0042] In any one or another of the above examples of the third aspect or the fourth aspect, the indication of the occurrence of the hitting event includes an identification of the player carrying the tracking module.

[0043] In any one or another of the above examples of the third aspect or the fourth aspect, the method includes or the system is configured to receive location data and indications of scoring events corresponding to a plurality of tracking modules, each of which is carried by a respective player participating in a golf tournament.

[0044] In any one or another of the above examples of the third aspect or the fourth aspect, a single companion device may be configured to receive indications of scoring events associated with multiple players, each player carrying a separate tracking module. In one configuration, the position data and the indication of the scoring event include identification data, the identification data including an identification of the player carrying the tracking module or an identification number of the tracking module carried by the player. In yet another configuration, pairing the timestamp with a set of position coordinates corresponding to the position of the tracking module at the occurrence of the hitting event includes matching the corresponding identification data.

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

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

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

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

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

[0050] In any one or another of the above examples of the third aspect or the fourth aspect, the location data collected or received by the location system includes positioning data, and the location system calculates the location coordinates using the positioning data.

[0051] In any one or another of the above examples of the third aspect or the fourth aspect, the plurality of location coordinate sets include GPS coordinate sets.

[0052] In any one or another of the above examples of the third aspect or the fourth aspect, the plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

[0053] In any one or another of the above examples of the third aspect or the fourth aspect, the tracking module can 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, wherein the second interval is greater than the first interval.

[0054] In any one or another of the above examples of the third aspect or the fourth aspect, the method may include or the system may be configured to: divide the holes of the golf course into regions, each region corresponding to a series of position coordinates, and determine the current region where the tracking module can be located from multiple sets of position coordinates.

[0055] In a fifth aspect, a 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 may be configured to receive an input corresponding to a stroke event, and the input includes a timestamp corresponding to the occurrence of the stroke event. The location system may collect or receive location data, the location data including a plurality of location coordinate sets, or the location system generates a plurality of location coordinate sets using the location data. Each location coordinate set may correspond to a location of the tracking module at a specified time. The location system may pair the timestamp with a location coordinate set corresponding to the location of the tracking module at the occurrence of the stroke event.

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

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

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

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

[0060] In any one or another of the above examples of the fifth aspect, the location data collected or received by the location system includes positioning data, and the location system calculates the location coordinates using the positioning data.

[0061] In any one or another of the above examples of the fifth aspect, the plurality of location coordinate sets include GPS coordinate sets.

[0062] In any one or another of the above examples of the fifth aspect, the plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

[0064] In any one or another of the above examples of the fifth aspect, the location system is configured to segment the holes of the golf course into regions, each region corresponding to a series of location coordinates. The location system can determine the current region where the tracking module is located from the plurality of location coordinate sets.

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

[0066] In any one or another of the above examples of the fifth aspect, the companion device is configured to be carried by a scorekeeper who accompanies a group of players including the player. The companion device may also be configured to receive input corresponding to a hitting event of all players in the group.

[0067] In a sixth aspect, a score tracking method includes: receiving input corresponding to a stroke event of a player participating in a golf tournament from a companion device, wherein the input includes a timestamp corresponding to the occurrence of the stroke event; collecting or receiving location data by a location system, wherein the location data corresponds to the location of a tracking module carried by the player, and wherein 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; and pairing the timestamp with the set of location coordinates corresponding to the location of the tracking module at the occurrence of the stroke event.

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

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

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

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

[0072] In any one or another of the above examples of the sixth aspect, the location data collected or received by the location system includes positioning data, and the location system calculates the location coordinates using the positioning data.

[0073] In any one or another of the above examples of the sixth aspect, the plurality of location coordinate sets include GPS coordinate sets.

[0074] In any one or another of the above examples of the sixth aspect, the plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

[0076] In any one or another of the above examples of the sixth aspect, the method further comprises: dividing the holes of the golf course into regions, each region corresponding to a series of position coordinates, and determining the current region where the tracking module is located from multiple sets of position coordinates.

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

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

[0079] In any one or another of the above examples of the sixth aspect, a shot event is input into the companion device by a scorer viewing a live video of a golf tournament.

[0080] In any one or another of the above examples of the sixth aspect, the shot events are entered into the companion device by a scorer viewing a video replay of a golf tournament. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0082] Figure 1 Schematically illustrates the hardware and networking features of an STTM system according to various embodiments described herein;

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

[0084] Figure 3 shows regional features for location tracking according to various embodiments described herein;

[0085] Figure 4A and Figure 4B Various views of a tracking module according to various embodiments described herein are shown, wherein Figure 4A A front view is shown, and Figure 4B A side view is shown;

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

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

[0088] Figure 5A An overview listing of tracking modules and associated locations of tracking modules that are loaded into a device management system according to various embodiments described herein is provided;

[0089] Figure 5B shows an example user interface generated by a device management system to provide tracking module management functionality and present device management data for a loaded tracking module in accordance with various embodiments described herein;

[0090] Figure 5C shows a device dispatch user interface that enables a user to perform device dispatch operations in accordance with various embodiments described herein;

[0091] Fig. 6A A grouping engine user interface is shown, the grouping engine user interface including a grouping management panel, according to various embodiments described herein;

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

[0093] Figure 6C shows a segment profile management interface including definition of example data elements of a segment profile and options to edit the data elements or create a new segment according to various embodiments described herein;

[0094] Fig.6D An interface of a revision editor according to various embodiments described herein is shown, the revision editor being configured to adjust a serve time using an "offset-based revision" method or a "revision using a base time" method;

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

[0096] Fig. 6F A round engine interface is shown according to various embodiments described herein, the round engine interface including a round management panel;

[0097] Figure 6G A round engine interface is shown for creating a tiebreaker according to various embodiments described herein;

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

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

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

[0101] Fig.7D shows a descriptive property selection screen of an ST application according to various embodiments described herein, the descriptive property selection screen being used for a selected descriptive category;

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

[0103] Figure 7F showing selection of a "Select Club" feature from a stack screen of an ST application in accordance with various embodiments described herein;

[0104] Figure 7G shows selecting "Irons" from a Select Clubs screen of the ST application in accordance with various embodiments described herein;

[0105] Figure 7H shows an interface for indicating a "club hit" using an ST application according to various embodiments described herein;

[0106] Fig.7I shows a "hole in" prompt for an ST application according to various embodiments described herein;

[0107] Figure 7J shows a set of screens that use the ST application to display a recorded shot after a score has indicated a "shot out" in accordance with various embodiments described herein;

[0108] Figure 7K shows selecting a "From Location" feature from a group screen of an ST application in accordance with various embodiments described herein;

[0109] Figure 7L illustrates a selection of available descriptive features for selection in a "From Location" screen of an ST application in accordance with various embodiments described herein;

[0110] Figure 7M and Figure 7Nshows a set of screens showing a transition from "Fairway" back to "From Position" after indicating "Club Hit" using the ST application, in accordance with various embodiments described herein;

[0111] Fig.7O shows a group page in which the first two players have completed the hole and the third player is on the green according to various embodiments described herein;

[0112] Figure 7P shows recording a second shot played from the teeing area according to various embodiments described herein, the second shot played from the teeing area being recorded as a provisional ball;

[0113] Figure 7Q to Figure 7S shows a user interface of an ST application according to various embodiments described herein, the user interface depicting a workflow for recording a provisional stroke that is ultimately used to record a penalty stroke;

[0114] Figure 7T to Figure 7V shows a user interface of an ST application depicting a workflow for recording a penalty drop and indicating that a dropped ball is in progress, according to various embodiments described herein;

[0115] Fig. 8A A presentation block user interface of a data management tool of a data management system according to various embodiments described herein is shown, the presentation block user interface including a tool component in a presentation block;

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

[0117] Figure 8C illustrates a team player shot details component of a data management tool according to various embodiments described herein;

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

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

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

[0121] Figure 8G shows a presentation tile user interface depicting connections between presentation tiles of a tool component according to various embodiments described herein;

[0122] Fig.9A A first verification user interface of a verification system according to various embodiments described herein is shown, the first verification user interface being configured for blind verification; and

[0123] Fig. 9B A second verification user interface of the verification system is shown, the second verification user interface presenting scoring data for one or more groups according to various embodiments described herein. DETAILED DESCRIPTION

[0124] This description describes various embodiments of score tracking and tournament management system, which may be referred to as STTM system in this article.STTM system may include various systems, components and modules, and various systems, components and modules are configured to provide a lightweight platform for score tracking and management for tournament data.Data collection may be unnoticeable for participating players, but data collection can provide accurate and detailed data about the competition and performance of participating players.Management functions can be provided on site, off-site or in a mixed configuration.Tournaments and score management functions before and during rounds can be automated, and customizable setting rules or configuration files are adopted, which can be adapted to various tournament structures, and greatly reduce costs and personnel hours, while also integrating multiple tournament processes, such as player grouping, serving time, score collection, position tracking, error correction and score verification.STTM system can be used to provide tournament scoring and organizational management and / or scoring system functions, and tournament scoring and organizational management and / or scoring system functions can be used to provide comprehensive data and feedback to players and other interested parties in real time or delayed.

[0125] Although some embodiments of the STTM system described herein can be combined with or utilize advanced infrastructure, the STTM system can be provided with a flexible package that is widely applicable and is configured for portability, and this flexible package that is widely applicable can utilize limited infrastructure, and the impact of the quantity, quality and accuracy of the final data product and / or the championship operation management support and function obtained via the use of the STTM system is very small. The flexible architecture of the STTM system can be scalable, retractable and / or modular, to meet the available infrastructure and resources with only the minimum change of data quality. For example, although this paper describes the various aspects of the STTM system as providing integrated functions or operations, the systems, components and modules of the STTM system are not limited to the use of combination. In fact, the systems, components and modules described herein can be utilized individually, or individually integrated with the system known or future development.

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

[0127] The STTM system may include a user device that executes an application, in combination with the user device and / or communicates with the user device to perform the operations described herein. The user device may dock the user with the operation of the STTM system. For example, the user device may be configured to access, execute, run or simulate one or more STTM system applications and / or services. Applications and services may be stored in local and / or remote memories and executed by local and / or remote processors. In some embodiments, applications, services, etc. are provided in whole or in part in a cloud computing environment, such as Software-as-a-Service (SaaS), Data Center as a Service (DCaaS), Data as a Service (DaaS), Platform as a Service (PaaS), Integration Platform as a Service (iPaaS), Infrastructure as a Service (IaaS), etc.

[0128] refer to Figure 1 and Figure 2 The STTM system 10 may include a score tracking system 20 and a management system 20, the score tracking system 20 being configured to track position and / or competition scores, such as golf tournament scores, and the management system 20 being used to manage the operation of the STTM system 10, which may include components of the STTM system 10, such as devices and elements.

[0129] The STTM system 10 may include or be combined with various devices, including one or more of a tracking module 11, a companion device 12, a management device 13, and / or a location element such as a location network 14 or a global satellite constellation infrastructure 15. The STTM system 10 may include or be combined with a communication network 17, which is configured to transmit system data to, from, or within the STTM system 10 components to perform the operations of the STTM system 10 described herein. In various embodiments, the communication network 17 may include one or more location elements, or be capable of operatively networking one or more location elements.

[0130] Tracking module 11 may include a user device that is configured to be carried by a player or otherwise positioned near a player during a match. Tracking module 11 may include a memory and a processor, the memory including instructions, and the processor executing instructions from the memory to perform various operations performed by tracking module 11. In some embodiments, the processor may be hardware, software, or a combination thereof. In some embodiments, tracking module 11 may also include an interface 11a (e.g., see Figure 4C), interface 11a can enable scorers, players and / or other users to interact with various applications, such as score tracking applications, and / or operations performed on tracking module 11, such as position signaling and / or position calculation processes, and can interact with STTM system components, devices, systems and / or their elements. The score tracking application can be referred to as an ST application. In some embodiments, tracking module 11 can be and / or include a computer, any type of sensor, a laptop, a set-top box, a tablet device, a tablet phone, a server, a mobile device, a smart phone, a smart watch and / or any other type of computing device, and / or any combination thereof. Tracking module 11 can be configured to perform various location operations. For example, tracking module 11 can be configured to track the location of tracking module 11 and / or communicate positioning information to the STTM system and / or position elements. Tracking module 11 can be configured to perform location tracking using various technologies and location schemes described herein. For example, in some embodiments, the tracking module 11 is configured to obtain Global Positioning System (GPS) coordinates corresponding to the location of the tracking module 11 and transmit these coordinates to an STTM system device or system, such as the management system 20 described herein. In these or other embodiments, the tracking module 11 can operate as a beacon in the location network 14. The tracking module 11 can be configured to communicate with various location elements, such as the location network 14 and / or location services, to transmit data including location data, which can include positioning data, which can be used to determine the location of the tracking module 11. The location data can also include a timestamp corresponding to the time associated with the location data. The tracking module 11 can be configured to communicate data, such as location and / or positioning data, through various communication networks 17, such as a mesh network, a local network, a cloud computing network, an IP Multimedia Subsystem (IMS) network, a Voice over Internet Protocol (VoIP) network, a secure network, a Voice over Long-Term Evolution (VoLTE) network, a wireless network, an Ethernet, a satellite network, a broadband network, a cellular network, a private network, a wired network, the Internet, an intranet, an Internet Protocol network, a Multi-Protocol Label Switching (MPLS) network, a content distribution network, a short-range wireless communication network, or any combination thereof.The tracking module 11 may be configured to communicate directly with a location element, such as the location network 14, the global satellite constellation infrastructure 15, via various communication networks 17, or indirectly with a location element via another STTM system device or network device. For example, in one embodiment, the tracking module 11 may transmit data directly to an STTM system 10 device, element, associated network, and / or location element via one or more communication networks 17, and / or transmit signals using a companion device 12 or a management device 13 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 can be configured to communicate, define, identify and / or organize the scoring data associated with the tracking module 11, and the scoring data may include location data. Additionally or alternatively, the companion device 12 may be used to collect and / or track other competition data. The user may utilize the companion device 12 to access data, content, services and / or perform various other tasks and functions of the STTM system 10. As an example, the user may utilize the companion device 12 to transmit signals to access various web-based, cloud-based and / or online services and content, such as those services and content that can be used on the Internet, on other devices and / or on various computing systems. As another example, the companion device 12 may be used to access an application, such as a score tracking (Score Tracking, ST) application, which provides one or more operating functions of the STTM system 10, such as communication with a management system 30, one or more tracking modules 11, one or more management devices and / or one or more location elements, and one or more location elements include one or more of a location network 14 and / or a global satellite constellation infrastructure 15.

[0132] In some embodiments, a scorekeeper may control one or more operational functions of the STTM system 10 using a companion device 12. The scorekeeper may be a human such as a dedicated user or player, a passive robot, an active robot, a simulated robot, a program, a computer, any type of user, or a combination thereof. The companion device 12 may include a memory, a processor. The memory includes instructions, and the processor executes instructions from the memory to perform various operations performed by the companion device 12. In some 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, a monitor, a graphical user interface, etc.), which may enable the scorekeeper to interact with various applications executed on the companion device 12, such as ST applications, and to interact with the STTM system 10, such as one or both of the score tracking system 20 or the management system 30. In some embodiments, the companion device 12 may be and / or may include a computer, any type of sensor, a laptop, a set-top box, a tablet device, a tablet phone, a server, a mobile device, a smart phone, a smart watch, and / or any other type of computing device. Illustratively, in Figure 1 , the companion device 12 is shown as a smart phone or tablet device.

[0133] The management user can utilize the management device 13 to receive and transmit signals regarding the functions of the management system 30 to request various types of content, services, and data, which are provided and / or accessed by the communication network 17 or any other network through which the STTM system 10 communicates. In another embodiment, the management user can be a robot, a computer, a simulated robot, an animal, any type of user, or any combination thereof. The management device 13 can include a memory and a processor, the memory including instructions, and the processor executes instructions from the memory to perform various operations performed by the management device 13. In some embodiments, the processor can be hardware, software, or a combination thereof. The management device 13 can also include an interface (e.g., a screen, a monitor, a graphical user interface, etc.) that enables a user to interact with various applications (e.g., management applications) executed on the management device 13 and to interact with the devices, elements, and systems of the STTM system 10. In some embodiments, the management device 13 can be a computer, a laptop, a set-top box, a tablet device, a tablet phone, a server, a mobile device, a smart phone, a smart watch, and / or any other type of computing device. The management device 13 can be local or remote relative to the competition location. The management device 13 may be cloud-based or web-based.

[0134] In some 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 and / or accessible on the companion device 12, tracking module 11, management device 13 and / or location network 14. For example, the companion device 12, tracking module 11, management device 13 and / or location network 14 may include applications for controlling the operating features and functions of the STTM system 10 and / or the score tracking system 20 or the management system of the score tracking system 20, applications for controlling any system devices, cloud-based applications, VoIP applications, cellular applications, 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, any other type of application, any type of application service, or a combination thereof. In some embodiments, the software application may support the functionality provided by the STTM system 10, such as the score tracking system 20 or the management system 30 of the score tracking system 20, and the methods described in the present disclosure. In some embodiments, the 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 applications. Users may also utilize the software applications and services to interact with any device in the STTM system 10, any network of the STTM system 10, or any network utilized by the STTM system 10 (e.g., a location network or a global satellite constellation infrastructure), or any combination thereof. In some embodiments, the companion device 12, tracking module 11, and / or management device 13 may include an associated device identification or any other identifier to uniquely identify a specific companion device 12, tracking module 11, and / or management device 13.

[0135] The communication network 17 can be configured to link each of the STTM system devices, components and elements, and can include any number of networks, in one embodiment, any number of networks including the location network 14. For example, the communication network can be used by the companion device 12 to connect with other devices inside or outside the communication network 17. In various embodiments, the companion device 12, the tracking module 11, the management device 13 and / or the location network 14 can belong to and / or form part of the communication network 17. In some embodiments, the communication network 17 can be a local network, a mesh network or other networks that can implement and / or promote various aspects of the functions of the STTM system 10. In some embodiments, the communication network 17 can be formed between or among various user devices, such as the management device 13, the companion device 12, the tracking module 11, the database 18 or their combination, by using any type of wireless or other protocols and / or technologies. For example, user devices can communicate with each other in the communication network 17 by utilizing any protocol and / or wireless technology, satellite, optical fiber or any combination thereof. It is noteworthy that the communication network 17 can be configured to communicate with any other network of the STTM system 10 and / or any other network outside the STTM system 10, and / or communicate with any other network of the STTM system 10 and / or any other network outside the STTM system 10. In various embodiments, the tracking module 11 can be configured to communicate directly with one or more components and / or location elements of the management system 30. The communication network 17 can be configured to transmit, generate and receive any information and data traversing the STTM system 10. In certain embodiments, the communication network 17 can include any number of servers, databases or other component parts. The communication network 17 can also include and be connected to a mesh network, a local network, a cloud computing network, an IMS network, a VoIP network, a secure network, a VoLTE network, a wireless network, an Ethernet, a satellite network, a broadband network, a cellular network, a private network, a wired network, the Internet, an intranet, an Internet protocol network, an MPLS network, a content distribution network, a short-range wireless communication network or any combination thereof. Illustratively, management device 13 is shown as a representative server and is shown as being included within or utilizing communication network 171. As described above and elsewhere herein, management device 13 will typically include a user interface that enables a user to perform the scoring and / or tournament play management operations described herein. In some embodiments, communication network 17 may be part of a single autonomous system located in a specific geographic region, or part of multiple autonomous systems spanning several geographic regions.

[0136] The functions of the STTM system 10 can be supported and executed by using any combination of servers. The server can reside in the communication network 17 or in the environment of the communication network 17, however, in some embodiments, the server can reside outside the communication network 17. The server can provide and act as a server service for performing various operations and functions provided by the STTM system 10. In some embodiments, the management device 13 may include a server, and the server includes one or more network servers, routers, gateways, switches, media distribution hubs, signal transmission 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 of the devices in the STTM system 10, and perform any other typical functions of the database 18. In addition, the database 18 may include a processor and a memory, or be connected to a processor and a memory to perform various operations associated with the database 18. In some 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 of the STTM system 10, any program of the STTM system 10, any other device, system, element, any network, or any combination thereof. The database 18 may include multiple databases 18. The database 18 may be local or remote. The database may be cloud-based.

[0138] The STTM system 10 may also include one or more data platforms 19 or transfer the competition-related data generated by the STTM system 10 to one or more data platforms 19. Data platform 19 may include hardware, software, server, computer, program, application program, etc., which are configured to view, manipulate, analyze, store or otherwise consume the generated data. In certain embodiments, data platform 17 includes a competition data viewer and an analysis platform, which can be used for players, coaches, managers, fans, members of media organizations, broadcasters or any other person. In another embodiment, data platform 17 includes a client platform for data consumption, and may include a competition data viewer and an analysis platform. In the example shown, data platform 19 is shown as part of the communication based on a web page or cloud via a communication network 17. However, in various embodiments, competition-related data may be transmitted via other parts of the network, such as locally.

[0139] Although the present disclosure may refer to specific applications executing on one or more electronic user devices, it should be understood that these applications, including any application services, may be provided within a single application, program, or platform, or may be divided, virtualized, distributed, or combined across any number of executable platforms and resources.

[0140] This description refers to various interface components. Interface components may include interface elements, display elements, data elements, etc., where the interface elements are configured to interface a user with an operation such as selecting a data value or a data element; display elements are configured to interface a user with a display. Indicators, operators, options, etc. described herein with respect to the interface may include buttons, toggle keys, switches, sliders, sliding buttons / bars / fields, sidebars, and / or other interface elements. These interface elements may be configured to be hard or soft. Similarly, interaction terms, such as pressing, tapping, selecting, etc., may be performed with a human body, a stylus or other tool, a peripheral device such as a mouse or keyboard, or other suitable user interaction.

[0141] Continue to refer Figure 2 , the score tracking system 20 can be configured to track scores for a game of multiple participating players, such as golfers, competing in a competition. The competition is described herein as a golf tournament, but a person of ordinary skill in the art will appreciate after reading this disclosure that the systems and methods described herein can be applied to other competitions and in other environments. Score tracking can also include tracking the location of a shot event. As introduced above and described in more detail below, the score tracking system 20 can include a tracking module 11 that is configured to be carried by or accompany the player. In some embodiments, for example, Figure 2As shown, 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 shot event inputs, from a scorekeeper and transmit score-related data to the management system 30. The tracking module 11 may be configured with positioning, location, and / or proximity technology, as described above and described in more detail below, and the tracking module 11 and / or another device, such as the companion device 12, the management device 13, the location network 14, and / or the location system 80, may use the positioning, location, and / or proximity technology to track the location of the tracking module 11. Using the companion device 12, the scorekeeper may record events related to the game, such as shot events. The recording of events may cause a timestamp to be generated and associated with the recording, and / or the retrieval, identification, calculation, and / or transmission of location data from the tracking module 11 corresponding to the recorded event, for example, when a player aims or hits a ball. The timing synchronization of the position data or timestamp with the position of the tracking module 11 can be used by the position system 70 as a proxy for the position of the player's ball after the previous hit or the position of the start of the player's ball before the hit. The significant benefit of this score tracking method is that a single scorekeeper who will usually accompany a group of multiple golfers can record both scores and position data in an unobtrusive manner. As described in more detail below, in various embodiments, the tracking module 11 is configured to be compatible with a variety of location service technologies, thereby providing flexibility in tracking the location of the tracking module 11, for example, by utilizing the available infrastructure about the golf course when necessary to provide flexibility in tracking the location of the tracking module 11. The score tracking system 20 and / or the STTM system 10 may include or be combined with location services, such as one or more of the global satellite constellation infrastructure 15 or the location network 14. The location network 14 will typically be a local location network for the golf course where the tournament is being played, and may include radio receivers, transmitters, transceivers, antennas, Ultra WideBand (UWB) antennas, anchors, initiators, responders, cellular towers, Wireless Fidelity (Wi-Fi) access points, beacons, geo-beacons, Bluetooth Low Energy (BLE) gateways, etc. In some embodiments, the location network 14 includes an external location / signal network that utilizes short-range or long-range location technology that may include signals of opportunity.

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

[0143] In one example, tracking module 11 obtains global positioning system GPS coordinates of tracking module 11 via communication with global satellite constellation infrastructure 15 and transmits the coordinates to management system 30. Companion device 12 may also transmit the shot event including the associated timestamp to management system 30. Location system 80 may then pair the timestamp with the corresponding location coordinates.

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

[0145] In one embodiment, the management system 30 includes an equipment management system 40, which is configured to manage multiple tracking modules 11 and assign multiple tracking modules 11 to players. The equipment management system 40 can be executed on one or more management devices 13. In one configuration, the equipment management system 40 communicates with the tracking module 11 during the game to track the location of the tracking module 11. When the companion device 12 sets a timestamp about the location of the tracking module 11 relative to the assigned player, the equipment management system 40 receives the timestamp and pairs the timestamp with the location of the tracking module 11 at the time set by the timestamp. The location information can be provided to the data management system 40 for review, and / or can be used for transmission or use by the STTM system 10 operation or data platform 19. As mentioned above and elsewhere in this article, the location calculation and / or the pairing of the location coordinates with the timestamp can be performed by the location system 80 and can be used for other systems of the management system 30, or the functions of the location system 80 can be provided by other systems of the management system 30. The location calculation can be instantaneous in perception and real-time in other cases. In one embodiment, companion device 12, tracking module 11, management device 13, location network 14, and / or location system 80 may continuously or nearly continuously track the location of tracking module 11. Such continuous or nearly continuous tracking may be used to account for location tracking / network delays. For example, when a scorer records a shot event that results in the setting of a timestamp at the time the ball was hit, in almost all cases the most recently calculated position within five seconds of the timestamp will provide the accurate location of the ball at the time of the hit. In one embodiment, the scorer will set a timestamp at the aiming point for location purposes.

[0146] In various embodiments, the management system 30 includes one or more of a round management system 60, a data management system 60, or a verification system 70, wherein the round management system 60 is configured to manage the rounds and groups of players playing in the event, the data management system 60 is configured to review and edit the scoring data recorded by the score tracking system 20, and the verification system 70 is configured to provide a simplified verification of the official scorecard of the player based on the scores collected by the score tracking system 20. In the above or another embodiment, the management system 30 may include a location system 80. The location system 80 may be configured to process the tracking module 11 location data, calculate the location data from the positioning data, pair the timestamp with the location data, make a zone determination, and / or compare the zone determination with the scoring data zone identification. In one embodiment, the companion device 12 may transmit the scoring data to the management system 30. The tracking module may also directly or indirectly transmit the location data or positioning data to the management system 30. The shot event and the corresponding timestamp can be used in the location system 80 to be paired with the tracking module location. The location system 80 may share data and / or functions with various systems of the management system 30. For example, instead of the location system 80 or in addition to the location system 80, the device management system and / or the data management system may perform or access one or more of the above location determination functions. In various embodiments, the location system 80 includes one or more location networks or communicates with one or more location networks. As described in more detail herein, the location network may include a global positioning system (GPS), wireless fidelity (Wi-Fi), radio frequency identification (RFID), Bluetooth Low Energy (BLE), ultra-wideband (UWB), near field communication (NFC), cellular, etc.

[0147] As introduced above, the companion device 12 can be configured to execute or run the ST application. The ST application can include a mobile application, a web application, a cloud-based application, or other application format, and includes instructions that are operable to perform the score collection features described herein with respect to the companion device 12. When the companion device 11 is configured to communicate with the tracking module 11, the ST application can be configured to provide a communication protocol between the companion device 12 and the tracking module 11. For example, the ST application can configure the companion device 12 to: communicate with the tracking module 11, provide updates, receive data for storage, provide processing operations, transmit alarm initiation instructions, obtain battery life or charging status, receive tracking module 11 location data, initiate location data events, relay data received from the tracking module 11 to a memory or another computing device, perform proxy services for the tracking module 11, or other operations described herein. Additionally or alternatively, the ST application can configure the companion device 12 to communicate with the management device 13 of the management system 30. For example, the ST application can be configured to receive and combine group assignments, round information, serve times, etc. from the round management system 60. In the above or another example, the ST application may be configured to: receive player and tracking module 11 assignments from the device management system 40, incorporate the player and tracking module 11 assignments into the collected scoring data (shot event data, position data, timestamps, club selection, etc.), transmit the shot event data including the associated timestamps to the STTM system 10, such as the position system 80, the device management system 40, the data management system 50 and / or the verification system 70, and / or communicate with the tracking module 11 to pair the tracking module 11 with the assigned player. However, in some embodiments, the assignments may be retained by the management system 30, and the companion device 12 may accompany the shot event timestamp or position data with an identifier of the corresponding tracking module 11, and the management system 30, such as the data management system 60 or the position system 80, uses the identifier to pair the position of the tracking module 11 at 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 the management system 30, such as the data management system 60, the verification system 70 and / or the position system 80.

[0148] In one embodiment, tracking module 11 includes a compact housing that can be easily carried or worn by an individual. FIG. 4A to FIG. 4DA view of an example tracking module 11 is provided. Although a larger tracking module 11 may be used, in the example shown, the tracking module 11 is provided with a housing 110 that is substantially smaller than a deck of cards. In one example, the housing 110 may be equipped with a clip for clipping to a belt, pocket, or other surface. In one embodiment, a wearable container for receiving the tracking module 11 may be provided, and the wearable container may be carried or worn by an individual. In one example, the container may include a clip for clipping to a belt or pocket, or may include a wearable strap or be attached to a wearable strap. Many variations may be implemented. For example, the tracking module 11 may be integrated or embedded in an article of clothing, such as a belt, belt buckle, hat, or bracelet. In some embodiments, the tracking module 11 may be integrated in a tablet computer, a laptop computer, a smart device such as a phone or a personal digital assistant (PDA), or other portable electronic device. In various embodiments, the housing 110 may be configured to be opened for maintenance, component replacement, upgrading, or other desired purposes. For example, the housing 110 may include a removable panel, or include a flip cover design. In one embodiment, the housing 110 can be waterproof or water resistant relative to the interior of the housing 110. For example, a panel or flap can rest on a gasket.

[0149] Figure 4D 1 is a semi-schematic diagram of the interior of the tracking module 11, which shows 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 exterior of the housing 110, or may be accessed by removing a panel or flap of the housing 110. The wired data communication port 111 may 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 provide power to the tracking module 11 operation. Various standard and custom sized batteries 113 may be used, such as AA, CR123A, 23A, or coin cells, such as CR2032. Although compact sizes are preferred, larger batteries 113 may also be used. In one example, a user may wear or otherwise carry a separate battery pack or power source that powers the tracking module 11 via a wired or wireless connection. Any suitable type of battery 113 sufficient to power the tracking module 11 may be used. For example, the battery 113 may include lithium, alkaline, silver oxide, carbon zinc, zinc air, lithium ion, nickel cadmium (NiCD), or nickel metal hydride (NiMH). Various tracking module 11 configurations may include a rechargeable battery 113, such as lithium ion, NiCD, or NiMH, or be configured to operate with a rechargeable battery 113. In one embodiment, tracking module 11 includes a battery 113 that is rechargeable, such as a rechargeable lithium polymer 2300 mAh battery.

[0151] Some configurations of the tracking module 11 may include a charging port 112 that is operable to receive an electrical supply to charge the battery 113. The charging port 112 may include a concave or convex 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 separated from the interior of the housing by a gasket. In yet another example, access to the charging port 112 is provided by removing a panel disposed on the gasket or by inserting an external charging interface connector through a slit in the water barrier material. In another example, a removable plug may be disposed within or above the charging port interface to prevent water intrusion. In one embodiment, the tracking module 11 is configured to be charged wirelessly. In one embodiment, the tracking module 11 is configured with a charging port to recharge the battery while in the housing. For example, the housing may include a wired or wireless charging port. A magnetic wireless charging port, a Universal Serial Bus (USB) (e.g., A, B, Mini A / B, Micro A / B, C), a Thunderbolt interface, a Direct Current (DC) electrical connector, or other suitable electrical transmission interface technology may be used. A customized charging interface may also be used. In some embodiments, the charging port 112 is configured to be similarly operable for use as a wired data communication port 111. In one embodiment, the charging port 112 includes a USB C connection. In the above or another example, the housing may be equipped with a charging interface configured to be plugged into a charger having multiple charging ports to charge multiple tracking modules 11 in bulk.

[0152] In various embodiments, the tracking module 11 may be configured with a wireless communication port 114, which includes one or more wireless receivers, transmitters and / or transceivers. The wireless communication port 114 may be configured to transmit and / or receive wireless data communications, such as signals, via any wireless communication medium or protocol, such as those including or in combination with radio waves, cellular, WiFi, short-range wireless, Bluetooth or other suitable wireless communication technologies. The wireless communication port 114 may be configured for multi-band operation. For example, the wireless communication port 114 may be configured to communicate 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 and / or positioning data, from a location network, a global satellite constellation infrastructure, etc. The wireless communication port 114 may be configured to transmit and / or receive positioning data, such as parameters for calculating a location. The wireless communication port 114 may be configured to operate as a beacon, as described in more detail below. The tracking module 11 may be configured with a location alarm. The location alarm may be remotely and wirelessly activated via wireless communication from one or more of a remote command center, a management device, or a companion device equipped with a suitable wired or wireless transmitter or transceiver for transmitting the alarm activation signal to the wireless communication port 114 of the tracking module 11, which may include communication through an intermediate wired network of the communication network. For example, the alarm activation signal may be transmitted and / or received via Wi-Fi, cellular, short-range wireless, Bluetooth, or other suitable wireless communication technology.

[0153] In one embodiment, a companion device of the management device, such as a management device of a device management system, can be configured to transmit an alarm activation signal, for example 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 eccentric rotating mass (ERM) motor or a linear resonant actuator (LRA), which may be housed in the housing and is operable to generate vibrations in response to receiving the alarm signal. Additionally or alternatively, the alarm signal may trigger an audible alarm to be output from a speaker 116 or other noise generating device within or associated with the housing. Additionally or alternatively, the alarm signal may trigger the activation of a light, such as a light-emitting diode (LED), or the activation of a liquid crystal display (LCD) or other light-emitting display.

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

[0155] Tracking module 11 can be equipped with accelerometer 1100. Accelerometer 1100 can be used for movement detection. Movement detection can be used in conjunction with positioning and position tracking, determination or acquisition, for example, movement detection can initiate the transmission of position signal and / or be used for monitoring of position signal. Movement detection can initiate the transmission of position or orientation data tracked, determined or acquired, for example, to a companion device, a location network or an STTM system device. In some embodiments, accelerometer 1100 can be configured for movement detection about detecting a player's swing. In addition to or in place of the scorer input of a swing or "bar hit" as described below, the detection of movement corresponding to the swing can be used. Accelerometer 1100 can be similarly configured to detect aiming, for example, aiming corresponding to a time period with a pause in movement before detecting a movement corresponding to the swing.

[0156] The tracking module 11 may include a user interface 11a for interfacing operations and / or status with a user. In various embodiments, the user interface 11a includes a display 118 for displaying information. Any suitable display 118 may be used, such as an organic light-emitting diode (OLED) screen. The information may include battery capacity, battery life or status, operating modes such as wake-up, sleep, ready to receive instructions, operation, etc. In some embodiments, the display 118 may present data about the current operation or assignment. For example, the display may be configured to display the group number and / or player to which the tracking module 11 is assigned regarding data collection.

[0157] In one embodiment, the user interface 11a includes one or more indicator lights. The indicator lights can be used to indicate operating status, such as power on, processing data, uploading data, downloading data such as instructions, dispatching or updating, receiving and / or acquiring position / orientation data, receiving instructions, transmitting data, operation in progress, operation completed, etc.

[0158] In one embodiment, tracking module 11 includes a speaker 116 operable to output sounds. Speaker 116 may be used to output audible alerts for positioning purposes, battery life, confirmation of receipt of user interaction or communication, initiation of wake and / or sleep mode, communication of instructions received from companion device 12, or other desired purposes.

[0159] In various embodiments, as described above, the tracking module 11 is equipped with positioning, location and / or proximity technology to assist in locating a misplaced tracking module 11 and / or determining the precise location of the tracking module 11. For example, the tracking module 11 can be configured to output positioning signals, such as packets, flashes, requests, responses, etc., directionally or omnidirectionally, and the accompanying device, location network, management system and / or location system can use the positioning signal to locate and / or determine the position / orientation of the tracking module 11, for example, based on signal strength, signal parameters and / or signal characteristics. Additionally or alternatively, the STTM system that can include the location elements described herein can be configured to locate the tracking module 11 using other technologies, such as, for example, those described below.

[0160] The STTM system or the score tracking system of the STTM system may include a location network configured to provide location tracking functions and / or services. The location tracking network (see Figure 2) may include multiple location signaling devices. The location signaling device may include a receiver, a transmitter, a transceiver, a gateway, a beacon, a UWB antenna, an anchor point, a launcher, a responder, a Real Time Kinematic (RTK) base station or a similar setting for outdoor position / orientation determination. The location signaling device may be configured to utilize radio waves, such as Ultra High Frequency (UHF), NFC, Wi-Fi, low-power Bluetooth and / or UWB. The location signaling device may be positioned around the court of the game and configured to communicate location signals with multiple tracking modules 11. The location network may be configured for device-side location calculation and / or network-side location calculation. The location network and / or tracking module 11 may utilize various positioning technologies, such as received signal strength indication (RSSI), RSSI fingerprint and / or time of flight (ToF), time difference on arrival (TDPA) and / or angle of arrival (AoA).

[0161] The tracking module 11 may include one or more short-range communication devices, such as WiFi, Bluetooth, BLE, NFC and / or ultra-wideband chips, configured to provide short-range location signaling, location search, proximity determination and / or ranging. Figure 4D A wireless communication port 115 is shown, which is configured for ultra-wideband, but other short-range communication protocols and / or signaling may be utilized. The wireless communication port 115 may be a supplement or replacement for the wireless communication port 114. In some embodiments, the wireless communication port 115 includes a Wi-Fi chip, a BLE chip, a Long Term Evolution (LTE) chip, and an ultra-wideband chip, and the wireless communication port 114 includes a cellular chip. Depending on the configuration, positioning services may be utilized by the tracking module 11, the STTM system, a location signaling device of a location network, and / or any device suitably configured to receive a location or positioning signal and utilize the signal and associated data to locate and / or determine the position / position of the tracking module 11.

[0162] Additionally or alternatively, the tracking module 11 can be configured to receive a positioning signal from a location signaling device, and the tracking module 11, a companion device, a location network, a location system, or other can use the positioning signal to determine the location / orientation of the tracking module 11. For example, a beacon signal can be used to determine the location / orientation of the tracking module 11. As introduced above, the positioning signal can be output via a short-range communication technology. In various embodiments, the positioning signal can be transmitted via radio waves, such as UHF, NFC, Wi-Fi, low-power Bluetooth, or ultra-wideband. For example, the tracking module 11 can be configured to receive a positioning signal, such as a beacon information packet or a UWB anchor point. In a device-side use case, the tracking module 11 can use the received location signal to calculate the location of the tracking module 11, or relay the location signal / information packet data and / or associated reception parameters to another device, such as a companion device or a management device, for direct or indirect processing, for example by utilizing an application programming interface (Application Programming Interface, API). For example, if there is a beacon, the tracking module 11 can receive a beacon information packet, and the tracking module 11 or a companion device or management device communicating with the tracking module 11 can use the beacon information packet to determine the position / orientation, for example, via RSSI, RSSI fingerprint and / or ToF technology. In the network-side position calculation use case, the tracking module 11 can continuously output signals, transmit a positioning response signal to a positioning signal received from a position signaling device, transmit a polling signal, etc., and the position network or other STTM system components, such as a position system, can use these signals to calculate the position of the tracking module 11, for example, via TDPA, ToF and / or AoA. In one embodiment, the position network includes multiple position signaling devices, such as beacons or anchors, and multiple position signaling devices are positioned around a playing area, such as a green, a fairway, a rough area and / or a tee. The tracking module 11 can receive the transmitted signal to determine the orientation / position. In another example, the tracking module 11 can transmit a response positioning signal. In the above or another example, three or more beacons or anchor points may be used, for example, around a putting green for precision and accuracy.

[0163] In one embodiment, the tracking module 11 can be configured for UWB position / orientation determination in conjunction with a location network. For example, the tracking module 11 can include multiple antennas, and the multiple antennas are used to directly or indirectly utilize AoA / phase difference. The tracking module 11 can be configured to perform unilateral, bilateral or multi-lateral ranging as an initiator and / or responder. The tracking module 11 can be configured to operate as an initiator in a time difference of arrival model, wherein the synchronization anchor points of the location tracking network are positioned around the golf course for precise location and accuracy, for example, an accuracy of 1 cm. In one embodiment, a variety of positioning technologies can be used to enhance positioning, such as Wi-Fi, BLE and / or UWB. In another embodiment, one or more of these positioning technologies can be used in conjunction with one or more global satellite constellations. In some embodiments, the location system includes a UWB positioning system, and the UWB positioning system includes multiple anchor points, and the multiple anchor points receive positioning signals from the tracking module 11. The anchor point can determine the coordinates of the tracking module 11 using the time difference of arrival (Time Difference of Arrival, TDoA) or other suitable technology. It should be understood that in such a network or any other location network, the location system may receive and / or collect positioning data or location data. The location system may calculate the location from the positioning data. The location system may also include all or part of the location network.

[0164] Tracking module 11 may be configured to utilize one or more global satellite constellations for accurate position determination and positioning. Figure 4DA GPS chip or receiver 117 is shown to be included, which is configured to receive GPS position coordinate data. Although the present description generally relates to GPS, it will be understood by those skilled in the art that such references are equally applicable to other Global Navigation Satellite Systems (GNSS), such as GLONASS, BeiDou, Galileo or other current or future GNSS. GPS positions can be enhanced with Wide Area Augmentation System (WAAS), Differential GPS (DGPS) such as Global Differential GPS (GDGPS), Real Time Kinematic (RTK), Continuously Operating Reference Station (CORS), Signals of Opportunity (SOP)-based or enhanced navigation, UWB, LTE, cellular, radio, TV, Wi-Fi, other satellite signals, etc. In some embodiments, a location network can be used instead of one or more global constellation coordinate systems, or a location network can be used in a mixed manner with one or more global constellation coordinate systems. The location network can utilize location signals and methods, including but not limited to RTK, CORS, SOP-based, UWB, LTE, cellular, radio or Wi-Fi. In one example, the tracking module 11 is configured to utilize any or all of the available global satellite constellations (GPS, GLONASS, Beidou, Galileo and QZSS) to achieve precise positioning, with a typical accuracy of 0.5-5m, outdoor accuracy or higher. In one embodiment, the tracking module 11 transmits the coordinate position of the tracking module 11 to the management system via a cellular network.

[0165] In one embodiment, the communication network includes a Low Power Wide Area Network (LPWAN), and the tracking module 11 transmits the location data to the management system directly or indirectly via the LPWAN. In one example, the LPWAN includes a Long Range Radio (LoRa) network. The companion device can similarly transmit the hitting event data via such a network. Unlike current score tracking methods, the configuration of the present score tracking system can utilize low data loads, which are suitable for the transmission of small data packets over low power, long distance networks, while still maintaining a large amount of accurate data.

[0166] As described above, the STTM system can utilize the UWB positioning / location network for all or part of the location services. GPS or other location services can also be used simultaneously in a hybrid configuration, or as a separate selectable option or setting relative to the system equipment.

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

[0168] In one embodiment, the championship course and / or surrounding venues may be mapped and divided into geo-location areas. The location data of the tracking module 11 may be transmitted to a management system, such as a management device, to determine the current geo-location area corresponding to the location of the tracking module, and the location data of the tracking module 11 may include positioning data. The current area may be transmitted to the tracking module 11, which may trigger an action of the tracking module. In one embodiment, the tracking module 11 is programmed to identify the current area, and the identification of the current area may trigger an action. In some embodiments, the tracking module 11 may transmit the coordinates to the management device, which passes the coordinates through an API including the geo-location area and returns the current area of ​​the coordinates corresponding to the tracking module. The actions that may be triggered include warnings, API calls, database inputs, alarms, etc. based on entering, leaving, or being in a specific area.

[0169] Figure 3The example geolocation partition of golf hole is shown.The area comprises green area 31, edge area 32, fairway area 33, first mowing area 34, obstacle area 35, rough area 36, ​​natural area area 37 and tee area 38.Each area comprises the coordinate corresponding to the corresponding area.As mentioned above, other or additional areas can be included.In various embodiments, all holes are partitioned.As introduced above and described in more detail below, geolocation partition can be used for various operations of STTM system.For example, when the tracking module assigned to the first player in the group enters the green area 31, the group mark of the player can be or recorded as being on the green by the accompanying device, score tracking system or management system.As mentioned above, the position system can collect or receive the position data about the tracking module.The position system can use this position data to determine the position of the tracking module.The position coordinate can be applied to the predefined coordinate range corresponding to the defined area to determine which area the tracking module is currently located in.The area can be determined in real time, for example, the area is determined in less than 10 seconds or 5 seconds or less. The position system can utilize the most recent position coordinate set or the interval of position coordinate to determine the current position and / or area where each tracking module 11 is located to track the position of the tracking module 11. Similarly, when the tracking module assigned to the last player in the group passes through the green area 31 after the group is marked or recorded as being in the green area 31, the group can be marked or recorded as completing the hole. When the tracking module 11 assigned to the first player is detected to enter the tee area 38, the group can be marked or recorded as being in the tee. As described in more detail below, the user input to the ST application on the companion device can be used additionally or alternatively to mark or record the position. In one embodiment, the group marked or recorded as being in the tee can advance the ST application to the hole associated with the tee. In another embodiment, the scorer who inputs the "hole in" about the last player in the group who hits the ball into the hole into the companion device automatically advances the ST application to the next hole. In another embodiment, the ST application will not advance to the next hole until "Hole-In" is entered for all players on the previous hole and the player enters the tee box for the hole.

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

[0171] In one embodiment, the location of the tracking module 11 is tracked continuously, for example, continuously at one second intervals, or continuously in other ways as programmed. In one embodiment, pairing the timestamp with the location can analyze the location coordinates collected before the time corresponding to the timestamp and after the time corresponding to the timestamp to identify the most likely location.

[0172] As described in more detail below, the scorer using the companion device can also input ball positions or "from positions". These positions can correspond to defined areas of the hole. Using the area determination from the tracking module coordinates, the position system can compare the determined area to the input area and identify the existence of any inconsistencies. For example, the determined area may be a fairway, but the input area may be a bunker or hazard. In this case, the position system can be configured to accept the area position as a bunker or hazard. In one embodiment, the position coordinates can be adjusted to a bunker or hazard. In another embodiment, the position coordinates can be retained and only the area position corresponding to the "from position" can be changed to correspond to the area position entered by the scorer.

[0173] The companion device can record the timestamp at the aiming and / or the club hitting position. The location network can apply an algorithm to analyze the position before and after the timestamp. The review time period and the look-ahead time period can be adjustable in the location system. As an example, the review time period and the look-ahead time period can be 30 seconds. In one embodiment, the review segment can be longer than the look-ahead segment. The location system can find the position closest to the timestamp in time and identify the most accurate position. The identification of the most accurate position can include the determination of a time period of 5 seconds to 10 seconds or more with almost no change in position. As described above, the tracking module can detect when a swing is made. This data can be provided to the location system to confirm or strengthen the analysis about the timestamp. For example, the location system can pair the position at the time of the swing and cross-reference the position with the position provided in the timestamp and obtained by the scorer. In some embodiments, if the position is not known or is not related to the expected position, such as the coordinates corresponding to different holes, the position is not recorded.

[0174] In one embodiment, tracking module 11 is configured with an operation window. For example, location data, which may include positioning data, will not be stored or transmitted outside the defined time of the operation window. Such an operation window can be registered to each tracking module 11. In this or another example, if tracking module 11 is not registered to a player in a tournament, location data or positioning data will not be stored or transmitted. In any one or another of the above examples, if the coordinates obtained are not the coordinates of the stadium hosting the tournament, tracking module 11 may not transmit location data or positioning data. Therefore, in some embodiments, tracking module 11 can be programmed with allowable coordinates associated with the tournament. This restriction can strengthen the privacy of users of tracking module 11. In some embodiments, STTM system 10 can cover operation window registration, player registration and / or coordinate restrictions, for example, to locate a lost or lost tracking module 11.

[0175] In one embodiment, the STTM system 10 can be configured to pass notifications to the tracking module 11 registered to the player who is not in the right position or playing too slowly. For example, the tracking module 11 can output a text notification (if so equipped), an audible and / or visual alarm or vibration. Additionally or alternatively, the companion device assigned to the group including the player who is not in the right position or playing too slowly can receive such notifications via the ST application. In another example, the notification can include instructions on how to correct the problem, for example, arriving at a specific location or requiring the player to increase speed under a time or before a time.

[0176] As described above and with specific reference to FIG. 5A to FIG. 5C, the STTM system may include an equipment management system 40, which is configured to assign tracking modules 11 to players. The equipment management system 40 can provide data and / or equipment access to equipment management operations to equipment administrators locally, remotely and / or from any location via management equipment. In some configurations, the equipment management system 40 is configured to assign tracking modules to groups, and the tracking modules will then be assigned to players. The tracking module can be actively assigned to the player, for example, the software of the tracking module can usually be temporarily programmed to the player so that the position data, positioning data or other data transmitted from the tracking module include the identification of the assigned player. The position data may include a timestamp corresponding to the time of collecting the position data, or otherwise be related to the position of the tracking module. In some embodiments, the tracking module is independent of the player, and an identification number or other unique identifier associated with the tracking module is established in the STTM system so that the communication from the tracking module pairs the identifier with the assigned player. In various embodiments, whether it is programmed or unrelated, the companion device can be configured to associate the tracking module with the assigned player. For example, the ST application can be programmed by the equipment management system or by the scorekeeper to associate the tracking module with the assigned player for display on the companion device. In some embodiments, when a shot event associated with a location timestamp is entered, the companion device can transmit the tracking module identifier and / or the player name to an STTM system, such as a location system, equipment 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 operations. In one example, the device management system 40 may be configured to store and / or present tracking module management data. In some embodiments, the device management system 40 is configured to load or import a new tracking module and create a new device. The import of a new tracking module may include uploading a file, such as a comma-separated values ​​(CSV) file, which includes a tracking module configuration file to be managed or a list of tracking module configuration files. The tracking module configuration file may include specific tracking module management data, such as an identifier and / or other tracking module data. The device management system 40 may be configured to store the tracking module configuration file to a location and save the associated tracking module loaded and the location of the tracking module. The device management system 40 may be configured to directly or indirectly receive specific device-related management data from the loaded tracking module and present at least a portion of the data on a user interface display. FIG. 5A to FIG. 5B Embodiments of user interfaces are shown that present device management data and enable a user to perform device management operations.

[0178] Figure 5AA device management overview presentation 400 is provided, which includes a device list 401 of tracking modules loaded into the device management system 40 according to various embodiments and an associated location 402 of the tracking module. The device management system 40 is configured to enable a user to create a location and delete a location. In one embodiment, when a user deletes a location, a warning prompt may be generated to notify the user of the deletion after the user confirms. The location 402 may be a location associated with a listed tracking module. The location 402 may reference a geographic location by coordinates, landmarks, or location references (e.g., the 9th hole, a volunteer meeting area, an equipment cabinet, an equipment room, a geo-location area, etc.). Additionally or alternatively, the location 402 may refer to a physical container (e.g., container 681) containing a corresponding tracking module. In one example, the location 402 refers to a container including a device that accommodates the device, and the device that accommodates the device is configured to be used as a charging station and / or a storage station, the charging station is used to charge the tracking module, and the storage station is used to store the tracking module. In one example, the location 402 refers to a physical container containing a tracking module and the geographic location of the container, which can be coordinates, a geo-location determined area corresponding to the listed tracking module, or a location defined by the device management system 40. The locations 402 and devices included in the device list 401 can be imported into the device management system 40 before dispatching. In one configuration, the number of devices per location can be predefined in the device management system 40 at the import.

[0179] Figure 5BAn example user interface 403 generated by a device management system 40 is shown to provide tracking module management functions and present device management data for loaded tracking modules. The data elements included in the tracking module device management data or configuration file displayed in the illustrated embodiment include (a) function 404, (b) device name 405, (c) device ID 406, (d) accuracy 407, (e) position 408, (f) signal strength 409, and (g) battery life 410 of each tracking module. In other embodiments, fewer or additional device data elements may be presented. A location element 411 may be provided at the top of the hierarchy, which may correspond to the location 402 provided in the overview presentation 400. Loaded and stored tracking modules and associated device data elements may be stored to the identified location 411 and may be presented below the location 411 element. In one configuration, the device management system 40 may be configured to enable a user to move locations and associated device management data to change the order in the presentation. In the above or another configuration, a user is able to collapse and expand the tracking module data for a selected location, for example by interacting with the location 411 field. In the above or another configuration, the presentation includes a location 412 labeled "Storage," which stores loaded but currently unused tracking modules. In one example, the location label is fixed and cannot be deleted. As mentioned above, the device management system 40 can communicate directly or indirectly with the loaded tracking module to receive data associated with one or more device data elements. In various embodiments, the presentation can be configured to automatically refresh at predetermined time intervals, such as once every 30 seconds, or automatically refresh when an event occurs, such as when a received device data element is outside a predetermined acceptable range or exceeds a threshold. In one configuration, the presentation can include a manual refresh option to cause the presentation to immediately update the value of the device data element.

[0180] If the corresponding tracking module is sending a location signal, such as GPS information / coordinates, a polling signal, a response signal, location signal parameters, location data, a positioning signal, etc., then the "Function" is identified in the Function 404 data element.

[0181] Device name 405 may be a unique name associated with the device. Device ID 406 may be a manufacturing identification (IDentification, ID) number assigned by GPS or other location technology. Accuracy 407 may refer to the location of the device as the measurement accuracy of the distance. Azimuth 408 may refer to the current location of the device. Depending on the configuration and location technology used, the location value may be specified in latitude / longitude, grid coordinates or other suitable location coordinates. In various embodiments, the device management system 40 may perform one or more location operations associated with the location system. For example, the device management system 40 may receive the location data transmitted from the tracking module during the game. The device management system 40 may continuously provide such location data to the location system upon request or at predetermined intervals. In one example, the location system receives a timestamp corresponding to a location event from the ST application, and the location event is input into the companion device. The location system may provide a timestamp to the device management system 40 to pair with the corresponding location of the specified tracking module at the timestamp. In another example, the companion device may transmit the location event to the device management system 40 for location pairing. Any suitable data processing and flow may be used to perform such location operations during the game. For example, the tracking module may transmit location and / or positioning data to a location system, and the companion device may transmit location events to the location system for time stamp and tracking module location pairing.

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

[0183] In some embodiments, the communication between the device management system 40 and the tracking module can be bidirectional. For example, the device management system 40 can be configured to address the tracking module. In one such configuration, removal or transfer of the tracking module from the location 402 / 411 via operation of the device management system 40 can cause the communication to be transmitted to the removed tracking module. The communication can cause the tracking module to update the location of the tracking module to "unassigned", "stored", or a new location, as appropriate. In one example, the tracking module can include a user interface (e.g., see Figure 4C), the user interface allows a user to view device data elements associated with the tracking module. In the above or another example, the communication can cause the tracking module to output a notification that the tracking module is not in use, is not associated with the location, or is about to be moved to another location. The notification may include audio, text display, light, or other indicia, which, when perceived by the user, provides the desired notification. In one example, the tracking module includes a notification button, which, when pressed by the user, causes the output notification associated with the tracking module. In some embodiments, the tracking module is not configured to store an indication of the assigned location.

[0184] In one embodiment, the equipment management system 40 is configured to enable a user to assign tracking modules to players. For example, the assignment of tracking modules may be based on the player grouping of rounds. Figure 5C , the device management system 40 can be configured to generate a device assignment user interface 420 that allows a user to perform device assignment operations. In various embodiments, the device assignment user interface 420 and the device management overview 400 can be provided in a tabbed format that allows a user to simply select a desired tab to perform device management or device assignment operations from either interface. In one embodiment, the device assignment user interface 420 can receive groups from a grouping engine and automatically assign tracking modules from a list of devices to groups and players.

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

[0186] Equipment list 412 may include a list of equipment that is not assigned to a group number. Equipment settings list 423 may include a stored configuration of equipment assignments for a group layout. In some embodiments, a save equipment settings 423 operator may be provided as an option that is operable to save equipment settings for a group set. Menu 424 may include one or more additional options that are not visible for quick selection on the main panel. Events 425 may identify events in a golf tournament or other events that will review and manage equipment assignments for each group. Rounds 426 may identify rounds of events that will review and manage equipment assignments.

[0187] As introduced above, the device dispatch element may include a menu 424, which includes additional options that assist the user to set up to perform device dispatch. In one example, the menu 424 may include a "position selection" option, which enables the user to select or specify the location of one or more devices to be used for device dispatch. In the above or another example, the menu may include a "championship" option, which enables the user to select a championship. The championship option or another option may be used to specify that the championship is an associated tour. It should be understood that the dispatch element may be provided in any suitable presentation format, and the elements cited about the menu 424 may be provided on the main device dispatch user interface 420 display.

[0188] In one embodiment, the device management system 40 can be configured to load a framework of group numbers and devices assigned to the group. In various embodiments, each assignment in the group can be sorted in order. Unless assigned and reassigned to the group, the order can be unchanged. As introduced above, the device list can contain a list of all tracking modules that have not yet been assigned to the group and can therefore be used for assignment. The device management system 40 can be configured to enable the user to assign the devices in the device list to the group. It can also enable the user to assign the devices in a specific order in the group. After the device is assigned to the group, the user can save the allocation via the save device setting operator.

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

[0190] In one embodiment, the tracking module is assigned to the player. The tracking module identification number is associated with the player at the back end of the STTM system, so that the data obtained from the tracking module and / or recorded by the tracking module is attached with the identification number, and the STTM system component receiving the data, such as the accompanying device, the position system, the verification system, the data management system, the device management system 40 and / or the data platform, associates the identification number with the assigned player. This STTM system component can receive the player and tracking module identification number assignment set by the device management system 40 for this purpose. In one example, the accompanying device receives the player and tracking module identification number assignment set by the device management system 40, and associates the tracking module data with the player when scoring, such as storing and / or transmitting to the same STTM system component. As introduced above, the STTM system can include a location network, which is configured for, for example, device-side and / or network-side location tracking using a UWB anchor network. In the network-side location tracking use case, the device and player assignment can be transmitted to the system component, which is configured to calculate the location from the data collected by the network-side location network, or is subsequently used to associate the calculated location data of the tracking module with the calculated location data of the assigned player.

[0191] As described above, and with reference to FIG. 6A to FIG. 6G , the STTM system may include a round management system 60, which is configured to manage rounds and groups of players playing in an event. The round management system can provide data access to round management operations to a data administrator locally, remotely and / or from any location via a management device. In various embodiments, grouping can be managed by a grouping engine 500, which is configured to store serving times, adjust the serving times previously announced or record one or more of the order of the players in each serving time group. In certain embodiments, grouping engine 500 can be configured to automatically generate the grouping of future rounds based on scoring rules. Rounds can be managed by a round engine 501, which is configured to manage one or both of round states or round cuts.

[0192] The grouping engine 500 may be configured to manage groups. Management of groups may include creating groups of players. In one example, the grouping engine 500 may be configured to enable a user to define and manipulate groups for any round of any event. Fig. 6AA user interface of the grouping engine 500 is shown, the user interface including a grouping management panel 503, the grouping management panel 503 being configured to interface a user with various operations of the grouping engine 500. In various embodiments, the grouping management panel 503 may be configured to provide one or more elements, such as interface elements, display elements, or associated operational elements, one or more of which are selected from the following: (a) a grouping presentation element 504 including a list of groups with associated serve times for each segment of the group; (b) a view by segment element 505 operable to enable a user to view each segment, a portion of a segment's definition, or all segments at once; (c) a player list element 506 identifying players that have not yet been grouped or otherwise available for grouping; (d) a segment list element 507 identifying segments that have been created for a particular round; (e) a round selection element 508 operable to enable a user to select a round to view and edit a grouping, wherein a segment is associated with the round; (f) a segment profile selection element 509 operable to load a previously created profile having segment information; (g) an edit segment element 508 operable to load a previously created profile having segment information; (h) a segment list element 509 ...c) a segment list element 506 operable to load a previously created profile having segment information; (d) a segment list element 507 operable to load a previously created profile having segment information; (e) a segment list element 509 operable to load a previously created profile having segment information; (f) a segment list element 509 operable to load a previously created profile having segment information; (g) a segment list element 509 operable to load a previously created profile having segment information; (h) generate grouping element 511, configured to generate grouping based on predefined and / or definable segmenting rules for a round; (i) remove player element 512, configured to remove players in the grouping presentation component while retaining serve time data; (j) generate frame element 513, configured to generate groups without players but with groups based on segmenting rules for a round; (k) clear grouping element 514, configured to remove players and serve time data from the grouping presentation component; (l) grouping state element 515, including a selectable list of grouping states; (m) revision element 516, used to access the operation of a revision editor, which can be operated to adjust the grouping and mark the round as a revised grouping; or (n) player status element 517, providing access to the operation of a player status editor, which can be operated to change the player status of a round in an event.

[0193] Further references Figure 6B , the grouping engine 500 can be configured to display the grouping presentation 518. The grouping presentation 518 can be displayed in whole or in part, or can be displayed via a grouping presentation element 504 ( Fig. 6A) for interactive access. In the illustrated embodiment, the group presentation 518 includes group data elements provided in rows, where each row represents a group of players and a tee time. For each group, one or more of the following group data elements may be provided: (a) segment number 519, providing the 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, presenting the current time created for the group; (d) tee time data 522, presenting the date of the tee time created for the group; (e) court 523, presenting the court that the group will play at the identified tee time; and (f) player 524, providing the names of the players assigned to each group, which names may be presented in the order of play.

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

[0195] In various embodiments, the grouping engine 500 can provide various viewing and / or editing options regarding the groups and related data elements in the group presentation. For example, the grouping engine 500 can provide interface elements that allow a user to sort a column of data, for example, numerically, alphabetically, chronologically, or by other suitable data point characteristics. In one example, an interface element can be provided so that a user can selectively cause the grouping engine 500 to present the groups by segment number or all segments at once. In the above or another example, the grouping engine can be configured to enable a user to edit data points in a row of data. For example, editing features can be provided with the displayed data, or can be provided separately from the displayed data. In one embodiment, in Figure 6BThe displayed data elements referenced in may include interface elements that display corresponding data point values ​​and are configured for user interaction to optionally edit the data point values. The grouping engine 500 may provide editing features for grouping data elements, the grouping data elements selected from the following: (a) a segment number editor, including a list of available segments, the list of available segments having been created or loaded from a configuration file; (b) a group number editor, operable to enable a user to change a group number value, the group number value being typically a positive integer; (c) a tee time editor, operable to enable a user to change a tee time (e.g., hours: minutes); (d) a tee time date editor, operable to enable a user to change a tee time date (e.g., month:day:year); (e) a course editor, operable to enable a user to change a course, the course editor may include a selectable list of courses available for a selected tournament or event; (f) a player editor, operable to enable a user to change a player (e.g., selecting a player may provide a field to enter another player, or may display a list of selectable players, the list of selectable players may include drag and drop or other selectable methods); or (g) a combination thereof. As noted above, the displayed elements in the grouping presentation 518 may include interface elements. In one embodiment, interaction with these interface elements may cause the above editor operations.In one configuration, the grouping engine 500 is operable to enable a user to selectively add rows, delete rows, or both add and delete rows.

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

[0197] The grouping engine 500 can utilize segmentation and segmentation profiles. Segments can include tee time blocks that present the beginning of a round. For example, the segmentation of two groups can include a segmentation of one group starting with hole 1 and a segmentation of another group starting with hole 10. The segmentation profile can include a segmentation rule set, and the grouping engine 500 uses the segmentation rule set to assist in group creation. The grouping engine 500 can include one or more segmentation profiles or access one or more segmentation profiles. The segmentation profile can be loaded and / or created using a segmentation data manager. In various embodiments, the grouping engine 500 can be configured to automatically apply one or more segmentation profiles to a round. For example, a user can define a profile, save a profile, load a profile, or delete one or more of the profiles, and the grouping engine 500 applies the profile to an event or a round of an event. In one embodiment, the grouping engine 500 is configured to allow the current user to search for a segmentation profile and / or a user profile or another user, and the other user includes an associated segmentation profile, such as a segmentation profile created by another user or a segmentation profile previously used by another user. In one example, the user can select a segmented profile and import the selected profile into a current event or user's profile, or import the segmented profile into other users' profiles.

[0198] Figure 6CA segment profile management interface 525 is shown, which includes a definition of example elements of a segment profile and options to edit data elements or create new segments. The definition of example elements to be edited and options may be used in the segment data manager to create new segment profiles. The element may include one or more data elements selected from the following: (a) Segment Number Selection 526, including a list of segments that have been created for the selected round; (b) Segment Priority 527, including a positive integer value that cannot be repeated and is set in another segment associated with the round so that a specific segment can exist once per round in the system; (c) Courts 528, including a list of courts associated with the selected event; (d) Date 529, identifying the date on which the tee time starts the match; (e) Tee Time 530, identifying the initial tee time for starting or ending; (f) Tee Time (Starting / Ending) 531, including the option to mark the tee time as a starting tee time or an ending tee time; (g) Time Interval 532, used to specify the time from the start or end time set in Tee Time (above) to the end time of the match (above). (h) Groups at intervals 533, if set, then groups at intervals 533 identifies the number of groups that will be at one interval, while the remaining groups are at different intervals applied using the (below) first interval and the (below) remaining intervals; (i) first interval 534, representing the number of groups defined in the (above) groups at intervals; (j) remaining intervals 535, representing the time intervals of groups that are not defined in the (above) groups at intervals; (k) best score last / first 536, identifying whether the player with the best score is set at the first tee time or the last tee time; (l) starting hole 537, for all tee times in the segment; (m) players per group 538, identifying the maximum number of players assigned to a group; (n) number of groups 539, identifying the initial number of groups for the segment; or (o) a combination thereof. The segment list panel 540 may include a display of all data elements for each segment of the segment profile that are loaded in the segment profile management interface 525 .

[0199] In one configuration, the grouping engine 500 is configured to enable a user to create or delete segments. For example, elements of a segment profile may be edited via interaction with an element in a display, where the options for the element to be edited include an interface element that the user may use to edit data elements or other content of the segment profile. For example, to delete a segment, the user may select to delete segment 541 from the segment profile manager interface 525. To create a new segment, the user may select to create a new segment 542 from the segment profile manager interface 525. Upon selection, a default data element may be presented to the user, the default data element having the next sequence number from the current segment in the profile, the next sequence number from the current segment in the profile, the currently selected court, 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 a pre-existing segment profile, the number of groups per segment may be defaulted to the size of the field of play divided by the number of segments. When editing a segment after the number of players has been updated, the number of groups in each segment may be updated based on the size of the field of play divided by the total number of segments. In one configuration, if there is an uneven number of groups in a multi-segment profile, the odd group may be automatically placed in the highest even segment priority by default.

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

[0202] Reference again Fig. 6A , the grouping engine 500 can be configured to generate groupings. In one embodiment, a user can interact with the generate grouping element 511 to generate groupings of events, rounds, or segments thereof. For example, when the generate grouping element 511 option is activated, the grouping engine 500 can create groups using the current segmentation profile. The serve times can be generated based on the configuration of each segment in the segmentation profile, as described above.

[0203] When generating groups, a player slot can be identified for each player based on the number of players per group defined in the segment configuration, with the slot representing the order in which each player will play. The slot referenced as 1 is the first player to play, the slot referenced as 2 is the second player, and so on. If multiple segments are part of a segment configuration file for a round, the grouping engine 500 can automatically initiate player assignments and work in sequence as player assignments are completed for each segment, starting with the segment set to priority 1. If Best Score Last / First 536 is set to Last, player assignments can start at the last serve time of the segment and operate backwards from the last serve time of the segment. If Best Score Last / First 536 is set to First, player assignments can start at the first serve time of the segment and operate forwards from the first serve time of the segment. With respect to player selection and slotting when setting best score last / first 536, the grouping engine 500 may assign the player with the best tournament score in the first slot, the player with the second best score in the second slot, and so on, until the player has been assigned to each slot at a tee time before moving to the next tee time. In some embodiments, a segmentation profile may be bound to multiple players. In one example, if multiple players are bound, the grouping engine 500 may apply the following order rules to determine the next player to assign, such as: (a) the earliest tee time from the previous round; (b) the highest segment priority from the previous round, with the highest being first; (c) the lowest slot number, with the lowest being first; and (d) the course with the highest priority, with the highest being first.

[0204] The grouping engine 500 may be configured to create a grouping framework or perform grouping automation using elements of the segmentation profile for the selected round. For example, when the generate grouping element 511 is activated, the grouping engine 500 may be configured to create groups using the profile currently selected for the round. The serve times may be generated based on the configuration of each segment in the segmentation profile, as described above. When the generate framework component is activated, the grouping engine may be configured to present slots based on the number of players assigned to each group for each segment to generate a framework for the groups.

[0205] Each round can be associated with a grouping state. The grouping state can be edited via the grouping state element 515. In one embodiment, the grouping state can be selected from one or more of (a) draft, (b) pending review, (c) reviewed, (d) official, or (e) a combination thereof. When a user is creating a grouping required for a round, the "draft" state can be utilized. In one embodiment, when a grouping is first created, the "draft" state can be set as the default state. When a defined grouping set is ready for review, the "pending review" state can be set. When a defined grouping set has been reviewed and has been reviewed to be ready to transition to the "official" state, the "reviewed" state can be set. When a grouping set has been reviewed and approved and is ready to be distributed, the "official" state can be set.

[0206] In various embodiments, the grouping engine 500 can be configured to apply one or more grouping state rules. For example, the grouping engine 500 can limit the setting of grouping states that skip grouping states and move toward official. In one example, the "reviewed grouping" state can not be set until the "pending" grouping state has been set, and the "official" grouping state can not be set until the "reviewed" grouping state has been set. In various embodiments, the grouping engine 500 is configured to record all grouping states with a timestamp selected by the user. The user who makes the grouping state selection can also be recorded and associated with the selection.

[0207] In certain embodiments, the drafted grouping is stored for subsequent review by the grouping engine 500. In one example, the drafted grouping stored is distributed to other STTM system components. In certain embodiments, review can be performed to modify the group, for example, to create an interesting feature group, ensure that the player is not in the early group for multiple weeks in a row, separate the player who is known to play slowly, separate the player who is not alone etc. In one example, when the grouping data enters the state of review, the management user can review the data, and once the signature is signed afterwards, the grouping date is set to "approved" state. Once the grouping data has been approved, and the associated state is set to "approved", the grouping data just can be used for other STTM systems.

[0208] As introduced above, the grouping engine 500 may include a revision editor. In the illustrated embodiment, the operation of the revision editor may be activated by interaction with the revision element 516 in the grouping management panel 503. The revision status may be specified in various states. For example, the revision status may include "pending revision", "revised" and "revised status". The "revised" status may be set as a default status, which is set after the grouping is official and before any revision is made before the revision process begins. The "revised" status may be displayed when a user utilizing the revision editor is in the process of revising a grouping that already has the "official" status set. The "revised" status may be displayed when the grouping review process is completed, and the "revised" status is a change to the original grouping that was set to the official grouping status. In one embodiment, when changes are made to the grouping or data element updated by the revision editor, the revision status may be automatically set to "revised", and the grouping status restarts at the "pending review" state. In yet another or another embodiment, the "revised" status may be set when the grouping verification process is completed at any time after the original grouping is set to the "official" grouping status.

[0209] The revision editor can be equipped with various operations that the user can use to adjust the tee time from the current grouped tee time. For example, Fig.6DAn interface of a revision editor 545 is shown, and the revision editor 545 is configured to adjust the service time using an offset-based revision element 546 or a revision element 547 method using a reference time. The offset-based revision element 546 can cause the revision editor 545 to apply an offset-based revision method, which utilizes a start and end group. The start and end groups can be predefined or set by a user, such as by interacting with a start and end group element 548, and represent the start group and the end group to which the service time will be adjusted. The time-based revision element 547 can cause the revision editor 545 to apply an offset-based revision method, which in one embodiment can also include an adjustment of time, which can be specified via interaction with an adjusted time (+ / -) element 549 in the shown interface, which includes the amount of time that will be applied to the original service time of the group identified by the setting of the start and end group step. The start and end groups 548 and / or adjusted time (+ / -) elements 549 may include interface elements including fields for entering text, selectable lists of groups and / or time differences, or other suitable interface elements. The revision method using the baseline time can allow a user to utilize a new baseline serve time via interaction with a new baseline time element 550, the new baseline serve time replacing the original baseline serve time, and thereafter generating adjustments to the remaining serve times based on data elements defined in the segmentation profile for the round. In various embodiments, when the revision is used and applied, the round status is set to "revised" and the grouping engine 500 begins the grouping verification process.

[0210] As introduced above, the player list element 506 can contain or provide access to a list of all players in the field of the event. In some embodiments, the player status of the event and / or round can be associated with the player's name, such as displayed with the player's name. In some embodiments, the grouping engine 500 can include a player status editor, which is configured to change the player status. For example, in one configuration, a user can highlight a player displayed in the player list and select the player status component to access the player status editor to change the player status of the selected player. Fig. 6E, depicting an example interface of a player status editor 560, a list of status options 561 may be provided, which a user may use to set a player status for a selected player. A set status operator 562 may be provided to enable a user to set a status for a selected player. Various player status options may be provided, which may include one or more of the following: (a) Not Cut - Identify the status of a player who is still eligible to play in an event; (b) Cut - Identify the status of a player marked as cut, which may be manually set or automatically updated after the cut rule has been run, as described in more detail below; (c) Withdraw - Identify the status of a player who has withdrawn from a round; (d) Disqualified - Identify the status of a player who has been disqualified from a round; or (e) Advance but Not Complete - Identify the status of a player who will receive an official bonus but does not continue to play in the remaining rounds. In various embodiments, a player list 563 may be automatically updated after a player status is set. The player status editor 560 may be configured to provide additional options to further define the player's status. For example, the player status editor 560 may provide the user with an option to define whether a player status entered by the user as "out" will also be set for the player's future rounds. When a player's status is set to "out," "disqualified," "cut," or "qualified but not completed," the player may be removed from the group presentation 504 and player list 506 in the group management panel 503 for the identified round.

[0211] As described above, the round management system may include a round engine configured to enable a user to define the rounds with respect to the above FIG. 6A to FIG. 6E The round states defined by the various grouping creation processes described above are different round states. In some embodiments, the round engine can also operate to enable users to create and run player cuts on rounds. In one example, the round engine can be configured to provide playoff management operations as well as round states and / or cuts.

[0212] Fig. 6F A user interface of the round engine 501 is shown, which includes a round management panel 570, which is configured to interface a user with various operations of the round engine 501. In various embodiments, the round management panel 570 can be configured to provide one or more elements, such as interface elements, display elements, or associated operation elements. In the illustrated embodiment, the elements include one or more round selection elements, and the one or more round selection elements are selected from (a) round selection elements 571, (b) round status elements 572, (c) pause type elements 573, and (d) pause round elements 574.

[0213] The round selection element 571 is operable to select a round to control. The round selection element 571 may include, or cause a selectable list of available rounds for the event to be presented for selection by the user.

[0214] The round state element 572 is operable to select a round state and may include or cause a selectable list of available round states to be presented for user selection. In some embodiments, one or more round states may be automatically set by the round engine 501 . In various embodiments, round states may include: (a) Unstarted - a default state before a group is set as official; (b) Official Group - a state corresponding to a corresponding group of a round that has been set as "official" and available only when the corresponding group of the round has been set as "official", as described above; (c) In Progress - a state that is automatically set when the first shot or score of the round is created, and in some embodiments, this state can be set manually in addition or alternatively; (d) Paused - a state that is set if the round is interrupted due to weather or other circumstances; (e) Play Complete - a state that a round can be automatically set when the final score for the round is created, and in some embodiments, this state can be set manually in addition or alternatively; (f) Official - a state that is set when no changes to round data, such as shot information or score changes, are required; (g) Cancelled - a state that is set if the round has been canceled and will not be played for the remainder of the event; or (h) or a combination thereof.

[0215] In various embodiments, when the round status is set to "paused", the user can select a pause type using the pause type element 573. In one example, when the round status is set to "paused", the round engine 501 can require or prompt the user to select a pause type. In various embodiments, the pause type element 573 can include a selectable list of pause types or be operable to present a selectable list of pause types for user selection. Example pause types can include one or more of delayed, canceled, paused, or completed for the day.

[0216] In various embodiments, when the round status is set to "paused", the user can use the pause reason element 574 to select a pause reason. In one example, when the round status is set to "paused", the round engine 501 can require or prompt the user to select a pause reason. In various embodiments, the pause reason element 574 may include a selectable list of pause reasons, or be operable to present a selectable list of pause reasons for the user to select. Example pause reasons may include weather or environmental reasons. In one configuration, the pause reason may include one or more of darkness, rain, lightning, fog, wind, or frost. In another configuration, the pause reason may include a text field for entering a custom reason for the pause, 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 user with the operation of the round engine 501 regarding the cut management of the round. It should be understood that although certain elements are depicted in a single or identical panel, these elements can be provided in many different ways, including 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 cause a selectable list to be presented for all players of the round that have not yet been marked as cut. The cut player list element 576 includes or is operable to cause a selectable list to be presented for all players that have been cut for the round. The cut management elements also include a run cut element 577 and an uncut all element 578. The run cut element 578 is configured to run the cut rules based on the selected settings discussed below and set the players defined by the cut player status. The uncut all component 578 is configured to remove cut player conditions.

[0218] Regarding the cut rule, the optional settings may include the number of promotions 579, the number of promotions and matches 580, the maximum number of strokes from the leader 581, the target cut 582, including amateurs 583, or a combination thereof. The number of promotions 579 may correspond to the number of players who will be promoted based on the score and have the player status remain uncut, while all other players set to uncut will be set to the player status of "cut". The number of promotions and matches 580 may correspond to the number of players who will be promoted based on the score and will continue to the next round. If this is set, the difference between the number of promotions 579 set above and the number of promotions and matches 580 may include players whose player status will be set to "promoted but not completed". All other players may be set to the player status of "cut". The maximum number of strokes from the leader 581 may correspond to the number of players who are promoted, and the number of players who are promoted is the number of relative strokes from the leader's marked club. The target cut 582 may correspond to the number of players who are promoted that is closest to the value set, whether it is higher or lower than the value. If the players' values ​​are the same above and below, all players above that value may be considered "uncut" and all remaining players will have a "cut" player status. Include amateurs 583 may correspond to whether amateurs are included as part of the cutting rules. If set, then the participating amateurs are part of the cutting rules. If not set, then the cutting rules will not include amateurs. Include amateurs 583 may be selected in addition to other cutting rule components. It should be appreciated that if a selectable setting is included, different and / or additional settings may be provided.

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

[0220] The round management panel 570 may also include one or more elements configured to interface a user with the round engine 501 regarding the operation of a tie-off round creator. For example, the round management panel 570 includes a tie-off creator component operable to provide access to a tie-off round creator configured to create a tie-off for a selected round. Figure 6G An example user interface of the round engine 501 is shown, which is configured to interface a user with various operations of the play-off 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) position determination 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 can be configured to include a plurality of selectable playoff types, to select via the playoff type element 587, such as, one or more playoff types selected from "sudden death method", "number of holes" and "number of holes / sudden death method". "Sudden death method" corresponds to the playoff system, in which, starting with the first playoff hole, the players in the playoff compete until the player has a better stroke score than the other players in the playoff. If more than two players are playing, the player with a higher score than the best score on the hole is eliminated. "Number of holes" corresponds to the playoff system, in which, the playoff starts from all players in the playoff, and all players in the playoff play several holes, as defined in the hole sequence of the beginning below. If the player has the best score, the player wins, and the playoff ends. If there is a tie after the number of holes defined, the playoff repeats the number of holes defined. Continue this process, until the player has a better score than the other players in the playoff. If the scores of multiple players in this playoff type are not better than the best score, multiple players in this playoff type may be eliminated. "Number of holes / sudden death method" corresponds to the playoff format, in which the playoff starts with all players in the playoff playing a number of holes, as defined in the starting hole sequence below. If the player has the best score, then the player wins and the playoff ends. If there is a tie after the defined holes, then the playoff adopts the sudden death method as defined above.

[0223] The playoff number element 588 may be set or operable to set the number of playoffs, thereby enabling a user to store multiple playoffs for a round. The position decision element 589 may define or be operable to define what player position will be played in the playoff. For example, the playoff position decision may include position 1 for multiple players tied for first place or position 3 for multiple players tied for third place.

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

[0225] Save tie-up element 593 can operate to save tie-up settings. In some embodiments, tie-up settings can be saved without starting a tie-up.

[0226] Start play-in element 594 can operate to start play-in. In one embodiment, play-in can be started in the round maker until the game is completed in the round selected. In one example, play-in may need to verify that the previous round has been completed. In another embodiment, play-in can start before the previous round has been completed.

[0227] When the match 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 playoff number 588 and / or the position decision 589 value set. The playoff round creator 586 can then be configured to apply the remaining playoff settings to create a new round according to the rules. The players who are eligible to participate in the playoff round can be placed in a grouping, which can automatically include, as described above, each group has a maximum of four players; however, in some embodiments, manual group placement can be used. In some embodiments, the grouping for the playoff can be configured to be able to be presented for review via the grouping. In another or yet another embodiment, the round status can be automatically set to "official grouping".

[0228] As introduced above, the scorekeeper can use the accompanying device to perform the scoring function. The scorekeeper can include caddies, players or other people who are checking the game. The accompanying device can execute or run the ST application. The accompanying device can be equipped with a wireless data communication transceiver, which is configured to transmit score data wirelessly to the STTM system components, and the score data can include event data. During the game, each group can have the accompanying device assigned, and the scorekeeper uses the accompanying device assigned to collect score data. The score data can be transmitted to the management system, and the management system can be configured to process the data received from a plurality of accompanying devices during the game. The accompanying device can be configured with various wireless communication technologies as described above, and various wireless communication technologies can include short-range and / or long-range communication with the equipment of the STTM system. The accompanying device can be configured to communicate with the tracking module, to trigger and / or define data collection events, and data collection events can be used for officially scoring the player's round. For example, the accompanying device can be carried by the group accompanying the player or the scorekeeper observing the game otherwise. In various embodiments, the companion device may not be configured to communicate with the tracking module, and the companion device may transmit the location and / or location data to the location system, location element, and / or other STTM system components. The companion device may similarly transmit the collected score data and / or event data to the location system, location element, and / or other STTM system components.

[0229] In various embodiments, the companion device can be configured to wake up the tracking module and initiate event capture, such as collection of event data, for example, event capture, location / orientation determination, or data for processing and determination thereof by the companion device or another processing device. In one embodiment, the tracking module can be configured to receive instructions for event capture. The instructions can be transmitted by the companion device or the management device. For example, the companion device and / or the management device can be networked with multiple tracking modules or otherwise operable to provide instructions and / or receive instructions or data from multiple tracking modules. It should be understood that the management device can include data or provide data to the location system.

[0230] A scorer utilizing a companion device will typically accompany the player whose score the scorer is tracking; however, in some embodiments, the scorer may remotely view the player via a real-time or delayed feed. When the scorer is also inputting events that set timestamps for aiming or when a ball is struck, the feed should be real-time or have a precisely known delay to maintain accuracy in linking the player's position relative to the position of the ball, which timestamps may be paired with the location of the tracking module to provide a proxy for the ball position after a previous stroke or the position where the ball started for the current stroke. In a remote viewing use case, the tracking module may be configured to communicate with a management device or an intermediate relay device via a suitable communication protocol to provide location data or calculation parameters for the tracking module, which may include a short-range communication protocol or a long-range communication protocol depending on the proximity of the management device or the intermediate relay device. In a configuration where the location of the tracking module is calculated network-side by another device, the other device may communicate directly or indirectly with the management device.

[0231] ST application program or the companion device of operation and / or access ST application program--ST application program can be local, remote, network-based or cloud-based--can be used by scorekeeper for one or more rounds of golf, usually golf tournament events.The scoring data collected can be stored or transmitted by the companion device, as discussed in more detail elsewhere herein.The reference to the scoring data transmitted from the companion device and / or tracking module can include being transmitted to one or more position systems, management systems and / or data platforms indirectly or directly, and the scoring data can include event data and / or position data.For example, the scoring data can be transmitted to the position system and / or one or more management systems immediately or subsequently, for further data management, data review, data correction, score verification, data analysis, data storage, position identification, position calculation, regional identification or be configured to perform other STTM system operation application programs.The data viewing platform can refer to being distributed to subscription services or platforms, such as those subscription services or platforms of downstream clients, commercial or consumer-level platforms, private or public networks, surface network platforms, etc., used for fan consumption alone or together with other data. In various embodiments, the ratings data may be distributed or made available for use or integration with a web application, mobile application, or other application for public or private viewing, analysis, or archival storage.

[0232] The ST application can be configured for a number of selectable scoring level operations. For example, in a shot level operation, a scorer can utilize the ST application to record a shot at the location where the shot occurred, without utilizing the location functionality of the tracking module or the utilization and / or integration of the tracking module as described herein.

[0233] When utilizing tracking module to obtain position information, ST application or other STTM system application or service can combine position data with shot level data.In laser operator level scoring, scorekeeper can utilize ST application to record shot without additional position information, or can also track player position via tracking module, with via manual laser pointing device, the equipment used by laser operator of PGA Tour, or be used in combination with laser position tracking via the operation of automatic laser system, the automatic laser system tracks or continuously tracks the position of ball in whole round.Can output laser information based on the survey of court or GPS or similar mapping or convert laser information into coordinate grid system.In combined use configuration, the position data obtained from different technologies can be used for different end uses, and is combined for analysis to realize higher accuracy, or a kind of position technology can be used as backup or reference of another kind of position technology.In one embodiment, accompanying device and ST application can be configured to allow single scorekeeper to collect the shot level data of all players in single group.

[0234] In one embodiment, the companion device may be preloaded with specific event data, or configured to access specific event data via the ST application, such as one or more of the following: (a) par values ​​for a particular course; (b) course hole sequence (a course hole sequence may be associated with a par value); (c) slave location predefinition (a slave location predefinition may include a location indicator and a slave location available for selection in a "from location" screen); (d) score level of the event (a score level of the event may record only shots or utilize and / or incorporate location tracking, such as GPS, UWB, BLE, Wi-Fi, cellular, etc., rangefinder, laser operator, or a combination thereof); (e) course name; (f) player group data, an assigned group, multiple groups, or all groups of players for the event, such as names of players in a group, numbers of players in a group, images of players, such as avatars; or (g) a combination thereof. In one example, the ST application is executed at least in part, such as in a cloud-based environment, and the above event data is provided to the companion device, such as automatically upon startup. If the event is conducted on multiple courses, course data for a specific course or courses may be provided or selected by the scorekeeper, for example, via a user interface. Course name and number may be provided. The companion device may be automatically provided with round details, which may include group updates, group assignments, event changes, event notifications, or other round details.

[0235] In one embodiment, using the ST application, the companion device can be configured to receive group position data. The scorekeeper can interface with the user interface of the companion device to enter the group position data by any suitable method, such as entering into a provided field, selecting from a list of displayed options, etc. In one example, when the players in the group are on the tee, the scorekeeper enters or selects "tee". In another or another example, when the first caddie or player of the group reaches the ball of the player in the fairway, the scorekeeper can enter or select "fairway". In another or another example, when the first caddie or player of the group reaches the ball of the player around the green, the scorekeeper can enter or select "green".

[0236] The output of the data management system, device management system, round management system, grouping engine and / or round engine can be transmitted to the ST application to conform the operation of the ST application to the output. For example, the grouped output can be sent to the ST application to populate one or more groups to which the companion device is assigned.

[0237] As mentioned above Figure 3 As described, in various embodiments, group and / or player locations may be automatically tracked via location tracking technologies and associated location networks, such as GPS, Wi-Fi, RFID, BLE, UWB, NFC, cellular, etc. For example, the ST application may incorporate geo-fencing, which triggers group location changes at predefined boundaries. Geofencing may also be applied by other STTM system applications by tracking the location of companion devices and / or tracking modules.

[0238] To track a player's hits, the companion device may present a selectable list of players from which the scorer may select. When tracking a player's hits, the companion device may be configured to present a selectable list of locations from which the player will hit the shot. Example locations may include a teeing ground, fairway, green rough, bunker, sand, fringe, wasteland, or native or natural area. In one configuration, a "from position" will be set for the player at any time, and will make the "from position" "sticky" for the next shot. In other words, once the position is known, the scorer may set the player's "from position" and have the value persist until the scorer changes position or indicates that the ball has been hit.

[0239] In one example, the scorer can also input when the player is aiming at the ball. For example, when the following situation occurs: when the player is aiming at the ball for the first time or as a switch, this can be input as an event. In the switching case, the user interface of the accompanying device can include a "aim" button, and when the player is aiming at the ball, the scorer presses the "aim" button. The scorer can then press the "bar hits out" button, or otherwise indicate that the ball has been hit out. The ST application can interpret "aim" as keeping the attack until the scorer presses or taps the "bar hits out" button or other indicator, sending or recording both aiming and hitting events at this time. In another configuration, the scorer maintains contact with the "aim" button until the ball is hit out. When the scorer releases the "aim" button, the release is interpreted as the ball being hit out. In certain embodiments, before indicating that the ball is hit out, the interaction of the aiming button is transmitted in real time. In other embodiments, the interaction can be transmitted in real time together after the bar is hit out, or can be stored locally to carry out subsequent transmission. When utilizing the tracking module to collect position data, such as position coordinate data, for a shot, the ST application can be configured to map the tracking module assigned to the player to the player's name. When the scorer indicates that the ball is hit, the position of the tracking module is captured and recorded as described elsewhere herein. In some configurations, the capture of the position of the tracking module can be triggered via interaction with an "aim" button.

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

[0241] As described above, the user interface may present a "shot out" button or other indicator that the scorer may interact with to indicate that the ball has been shot. In one example, the "shot out" indicator is a button that the scorer taps when the ball is shot. In another example, the "shot out" indicator is a button that the scorer presses and holds until the ball is shot, wherein the release of the button indicates when the ball is shot, rather than "pressing down". In yet another example, a multi-level "shot out" indicator or multiple indicators may be used to indicate at least two of aiming, position timestamp, and shot out. For example, a two-level "shot out" indicator may be used to indicate aiming and / or position in a first level, and position and / or shot out in a second level. In one configuration, the scorer may press a two-level indicator button when the player is in the aiming position, and release the indicator button when the ball is shot, wherein the press sets the position timestamp, and the release is interpreted as the ball being shot out.

[0242] In some embodiments, after the scorer indicates that the ball has been hit, the scorer can be prompted to indicate whether the ball has been holed. The interface can present buttons, slide bars or fields, etc., and the user can interact with buttons, slide bars or fields, etc. to indicate whether the ball has been holed. In one example, the scorer is presented with a two-way sliding field, and the scorer indicates "yes" or "no" by sliding the field in the direction of the desired indication. In one embodiment, if the scorer does not interact with the associated indicator within a predetermined number of seconds to indicate that the ball has "holed", the "holed" prompt can be displayed, and the ST application can regard the lack of indication as an empty response, and the empty response has the value that the ball has not been holed. In another configuration, the ST application can be similarly configured to regard the lack of indication as the ball being holed. The scorer can choose to indicate an empty response or allow time to expire. For example, the scorer can slide to the right for holed, slide to the left for not holed, or allow time to expire for not holed. After indicating that the ball has been hit or the ball has not been holed, the user interface can automatically return to the group page, and the scorekeeper can select the same or next player to make a stroke from the group page to record the stroke. When the scorekeeper indicates that all players have holed out, the scorekeeper can be prompted to indicate to proceed to the next hole or a button or other indicator can be used to proceed to the next hole. In another example, when the scorekeeper indicates that all players have holed out, the ST application can automatically proceed to the next hole.

[0243] As mentioned above, scoring data may be collected in real time and stored locally, either immediately, upon an event occurring, such as when another piece of scoring data is collected or when one or all players complete a hole or group of holes, periodically, at scheduled intervals, when the companion device is in proximity to a management device (which may include a network access point or node), after a predetermined amount of data has been collected, or based on the remaining available data storage for transmission.

[0244] Reference FIG. 7A to FIG. 7V , FIG. 7A to FIG. 7V Various user interfaces of ST application 700 according to various embodiments are shown, and scorers can dock with accompanying devices to provide player descriptions. The interface may include various data input screens, and scorers can enter data into various data input screens. The screen may include predefined selectable options, for example, predefined selectable options are presented in list boxes, check boxes, drop-down menus, input steppers, text input fields, etc. ST application 700 may be preprogrammed to present one or more descriptive categories, and one or more descriptive categories each include multiple descriptive selections that scorers can select about selected or identified players. In some embodiments, ST application 700 may include a field into which scorers can enter text descriptions. Descriptions may be entered into one or more predefined descriptive categories selected by scorers. In some configurations, scorers may enter descriptive information or define descriptive categories by voice or text. The provision of fields for descriptive input may be a supplement or replacement for one or more predefined descriptive categories and / or multiple options within these descriptive categories. In one embodiment, ST application 700 may include a photo application or in conjunction with a photo application, or may be otherwise configured to input images of players. The ST application 700 may associate an image with a player. In yet another or another embodiment, the ST application 700 is configured to analyze the image of the player and perform image analysis to extract descriptive attributes, such as the color of clothing worn by the player. In this or another example, the ST application 700 may display a picture of the player that was captured by the companion device or another device that directly or indirectly transmits the picture to the companion device.

[0245] Fig. 7A A user interface of an ST application 700 is depicted that provides a menu 701 of selectable options, according to one embodiment. Using the user interface, the scorer may select a player description button 702 from the menu 701. Upon selecting the player description button 702, the user interface may display a player description screen 703 that provides options for entering one or more player descriptions, such as Figure 7B In one configuration, the ST application 700 may pre-populate player names, such as those in the group that the scorer will track. In these or other configurations, the ST application 700 may provide a field into which the scorer may manually enter the player name, or may provide a selectable list of groups or players from which the scorer may select to populate the player in order to provide further descriptions.

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

[0247] Selecting the Description button causes the ST application 700 to display one or more descriptive categories 705. Figure 7C In the example shown in , the user interface displays a context box that includes multiple descriptive categories 705 for the scorer to select. The scorer can select a descriptive category from the available options and is presented with multiple selectable descriptions. For example, in Figure 7C , the scorer is presented with three descriptive categories 705 relating to clothing: "Player Shirts," "Player Pants," and "Player Hats." Selecting "Player Shirts" displays a number of descriptive properties 706 for the player shirts from which the scorer can select. The scorer can select descriptive categories that allow the players to be easily distinguished. For example, the scorer can select one or more items of clothing worn by the player that are distinct from other players, so that the scorer can distinguish which player is hitting the shot, even from a distance. For situations where additional clarity may be desired, an optimal description can be provided. In Fig.7D In the example, the descriptive characteristics are related to color. In this example, the descriptive characteristics also include additional characteristics, identified as optional in this example, from which the scorer can further define the player's shirt. In the interface shown, the scorer has selected green for the color of the player's shirt and selected light as an optional description. In some embodiments, such as in Fig.7D , the user interface may request the scorekeeper to confirm the selection with a confirmation button 707. The selectable descriptive features within the "player pants" and / or "player hat" descriptive categories may be similar or different than those within the "player shirt" descriptive category. Although the descriptive categories in the illustrated embodiment relate to clothing, in some examples, different descriptive categories or descriptive features may be provided that may be in addition to or in lieu of clothing, such as shoes, clubs, bags, brand of items, etc.

[0248] In various embodiments, ST application 700 may be configured to receive descriptive input regarding one or more descriptive categories. The number of descriptive categories to be defined by the scorer may be predetermined or specified in ST application 700, or may be left to the scorer. Fig. 7E As shown in the summary player detail view 708 depicted in FIG. FIG. 7B to FIG. 7D The same way is described for Vincent Johnson's second descriptive category (player pants) by entering "black". Fig. 7EIt is also shown that the scorekeeper has entered descriptive properties for two descriptive categories for player Mahindra Luchman (Player Pants, Player Hat) and one descriptive category for player Jared Garcia (Player Shirt).

[0249] The ST application 700 may be equipped with a scoring feature that enables the scorer to enter a number of details about the game, including club type, shot location, shots, penalty strokes, scores, rankings, etc.

[0250] refer to Figure 7F In some embodiments, the ST application 700 may be configured to generate a club selection feature on the user interface that the scorer may use to identify the club currently being used by the player to set up and / or hit the golf ball during play. For example, on the group screen 710, the scorer may select a "select club" button 709 associated with the player. For example, at the teeing ground, the scorer may select the "select club" button 709 and be presented with a selection of clubs 711, as shown in FIG. Figure 7G The club selection may include any number of clubs, such as a player's entire set of clubs or an exhaustive list of potential clubs. In one embodiment, the club selection is programmed to correspond to clubs that a player might use at a particular location on the course. For example, using the location of the companion device and / or a tracking module carried by the player, the ST application 700 may determine the club selection to present a selection of clubs that correspond to clubs used by the player in that context or similar contexts and / or locations on the course. In some embodiments, the location and / or context may include a zone determination, such as, for example, regarding a particular location on the course. Figure 3 For example, the location system can 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 area to determine which area the tracking module is currently located in. Figure 7G In the example of FIG. 1 , the scorer selects the "Irons" button to instruct the player to tee off with an iron club on the par 3 of the second hole. In one embodiment, the companion device 12 will not respond to the selection of the player's name without the scorer first entering a club. The club selection may be made before the player reaches the ball and / or before the player strikes the ball. Although it is preferred that the scorer enter the club before the player strikes the ball, in some embodiments, the club selection may be entered after the player strikes the ball.

[0251] The companion device 12 executing the ST application 700 may be configured to receive precise input of the player hitting the ball. In some embodiments, a "shot out" button 712 may be provided, which the scorer may tap at the moment the player hits the ball. To display the "shot out" button 712, the scorer may select from the group screen 710 ( Figure 7F) and the scorer will indicate "Stroke Struck" for the player's name. Figure 7H , the user interface includes a "club hit" button 712, which the scorer will use to indicate a club hit by pressing and holding the scorer's finger on the button before the ball is hit, and then removing the scorer's finger at the moment the ball is hit to indicate the club hit. For example, when the player is aiming at the ball, preparing to make a club hit, the scorer presses and holds the "club hit" button 712. Then, at the exact moment the player hits the club, the scorer releases the button to indicate that the club has been hit. This action sends a signal to the system to record the position of the tracking module at that moment, which corresponds to the position of the player. This position information can also be associated with the player's club selection selection. This data can be saved in the tracking module, the companion device, or an associated memory, or can be transmitted to the management device at the time when the scorer indicates that the player or group has completed the hole, regularly, at scheduled intervals, based on the proximity of the tracking module or companion device to the management device, or based on the storage capacity of the tracking module or companion device. As described in more detail elsewhere herein, the position information may be input into an application configured to present a graphical display of a digital shot trajectory detailing the stroke of the round.

[0252] In some embodiments, when the scorer releases the "Shot Out" button 712, the scorer will then input the landing location of the ball relative to the golf course (e.g., fairway, rough, green, out of bounds, sand, hazard, in the repair area, cart path, hole). The companion device 12 may be configured to automatically display a location selection when the scorer releases the "Shot Out" button 712, or the user interface may be provided with a location button that the scorer may use to select from a plurality of locations or enter a location into a provided field. Fig.7I In the embodiment shown in FIG. 1 , when the “Hit Out” button 712 is released, the user interface displays a “Hole In” prompt 713, through which the scorer can indicate whether the ball has entered the hole. As shown, the interface of the hole prompt 713 requires a directional slide, left for no, right for yes. However, other interface buttons and methods may be used. After the scorer indicates whether the ball has entered the hole, refer to FIG. Figure 7J , the user interface may return to the group screen 710 now displaying the recorded strokes. The group screen 710 may also include a notification or indicator 714 that the player is currently playing on the hole. As shown, the text below the player's name has changed to "From Position," indicating that the player is between strokes on the hole. This indicator 714 may also operate as a button for triggering the collection of position information by the tracking module when the player hits the player's next shot in a manner similar to that described with respect to the first shot.

[0253] refer to Figure 7K and Figure 7L , in order to record the player's second shot, the scorekeeper can select "from position button" 715 in indicator 714 from group screen 710. This selection can make "from position" screen 716 be presented, and "from position" screen 716 includes multiple positions that the scorekeeper can select to indicate the position where the player hits the shot. As shown in the figure, the scorekeeper can select fairway bunkers, fairways, first mowing areas, native areas, deep rough areas, water areas, greenside bunkers, edges, other or greens. Since the player did not hit the player's first shot, the option of selecting "teeing ground" in this embodiment is unusable. However, the selection of "tentative ball" or "penalty throw" will make "teeing ground" usable.

[0254] In some embodiments, the course can be mapped before or after the game, and the location of the recorded position of the tracking module corresponding to the player and the ball can be superimposed on the map, or the STTM system can determine the location relative to the golf course in other ways based on the recorded position relative to the map. The course can be mapped using any coordinate or grid system, and can utilize surveying technology, global satellite constellation systems (GPS, GLONASS, Beidou, Galileo and QZSS), light detection and ranging (LIght Detection And Ranging, LIDAR) or other suitable methods. The recorded position information can be collected or converted directly or indirectly to such a coordinate or grid system and / or collected or converted using superposition technology.

[0255] After entering the from location on the From Location screen 716, the user interface may display the Group screen 710. Figure 7M and Figure 7N As shown, the position indicator 714 can change to a position indicator selected by the scorer, such as a fairway. The scorer can then select the player's name and reveal a "shot" button, through which the scorer can indicate the moment the player hits the ball, and then indicate whether the ball enters the hole, for example, in a manner similar to that described above.

[0256] Recording the time and location of each player's putt may be performed in a manner similar to that described above with respect to other strokes. In various embodiments, when the ball reaches the green and the scorer selects "green" from the "from position" screen, the position indicator 714 on the group screen 710 may remain "green" until the ball is holed. In another embodiment, the user interface may allow the user to select another location after a subsequent stroke that does not enter the hole, such as a location that may roll off the green. Fig.7OA group page 710 is shown in which the first two players have completed the hole and the third player is on the green. When it is the third player's turn to putt, the scorer can select the player's name, hold down the displayed "Pitch Out" button when the player is about to putt, and release it when the player putts to record the time and location of the putt via the location of the tracking module, as described with respect to FIG. Figure 7H The user interface can then display a "hole in" cue that the scorer can use to record whether the ball is in the hole, and the "hole in" cue can be combined with information about Fig.7I The prompts described are similar. If the ball does not enter the hole, the scorer records the next putt as before. If the ball does enter the hole, the ST application 700 records the player as completing the hole, and the scoring process starts again from the next tee. In one example, after the scorer records all the players who have hit the ball into the hole in the group, the position indicator 714 on the group page 710 can automatically revert to "select club". In another example, the user interface can prompt the scorer to indicate that the hole is completed and prompt the scorer to move to the next hole.

[0257] Figure 7P to Figure 7V PDP scoring according to various embodiments is shown. In these examples, the scorer records the "from position" on the "from position" screen 716, and the next shot will be hit from this "from position", rather than the position where the original shot landed. However, in some embodiments, the ST application 700 or system can additionally provide input to the landing position of the previous shot by input into a text field, selecting from a list of areas around the hole, such as "water area" provided on the "from position" screen 716, or a map that can be displayed, and the scorer can indicate the landing position of the ball on the screen.

[0258] Figure 7P The second shot played from the teeing ground is shown recorded as the provisional ball. Using the "from position" screen 716, the scorer selects "tentative ball" and then selects the from position, which in this example is "teeing ground". The display may then return to the group screen 710 and "tentative ball" may appear as the position indicator. The scorer may then select the player's name and score the shot as described above.

[0259] Reference Figure 7Q Once a provisional stroke is recorded, the "provisional ball" 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 stroke. Figure 7R7 shows a display prompt 720 that is presented after selecting a player's name, requesting the scorer to indicate whether the player is using a provisional club. If the scorer indicates that the player is not using a provisional club, scoring will proceed as normal. If the scorer indicates that the player is using a provisional club, a penalty stroke is awarded, which may be Figure 7S The group shown is indicated on screen 710.

[0260] Figure 7T Recording a penalty drop is shown. In some embodiments, when recording a penalty drop, the ST application 700 prompts the scorer to indicate that a penalty drop is in progress. For example, from the "From Position" screen 716, the scorer selects "Penalty Drop" and then selects the from position, which in this example is "Rough". The display may then return to the group screen 710 and "Penalty Drop" may appear as a position indicator 714 below the player's name, Figure 7U The scorer can then select the player's name before the player throws the ball. For example, refer to Figure 7V , the scorer is presented with a penalty drop reminder 721, which provides a "Ball in Play" button 722, which the scorer uses to instruct the player when to drop the ball or re-tie. This evaluates the penalty stroke, and further stroke locations and times may continue to be recorded as described above.

[0261] A free drop may be recorded in a manner similar to that of a penalty drop, except that "Penalty Drop" is selected from the "From Position" screen and penalty drops are not accessed.

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

[0263] The data management system 50 may include a data management tool 800, which includes one or more elements, such as interface elements, display elements or associated operating elements, one or more elements selected from (a) event selector 801, (b) round selector 802, (c) course selector 803, (d) edit mode notification 804, (e) data difference panel 805, (f) hole graphic representation 806, (g) group scorecard 807, (h) team player shot details 808 or (i) all group presentation 809. Fig. 8ADescribe the example user interface of the data management tool 800 used for use with the data management system 50, and this example user interface provides the elements listed in the presentation block above.In various embodiments, the page layout of the element is configured to enable to create a connection between the blocks and / or data elements therein.For example, when selecting an element in a block, a connection can be established for other blocks.In another example, other blocks in which a connection is established can be updated with appropriate presentation, as described in more detail below.However, it should be understood that the elements that can operate to provide the operation of the data management system 50 and the associated components and data of the elements can be provided in many formats, and the present disclosure is not limited to the specific arrangement and combination of the elements and user interface components described herein.

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

[0265] The round selector 802 may include a selectable list of one or more rounds of an event that can be used to view and manage associated data. In one example, the round selector 802 includes a drop-down list of all available rounds of an event selected by the event selector component. In another example, the selection of a round may cause the presentation block to present or be operable to present data for the round of the selected event. In another example, the round selector 802 and / or 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 an "official grouping" round status, as described in more detail with respect to the round management system 60.

[0266] The court selector 803 may include a selectable list of one or more courts for the selected event and round, which can be used to view and manage associated data. In one example, the court selector 803 includes a drop-down list of all courts that can be used for the selected event and round. The selection of a court can cause the presentation block to present or be operable to present data for the court of the selected event and round. In one example, when multiple courts are played for an event and round, the default court can be set as the main court. In another or yet another example, the court selector 803 may include a selectable option to select all courts. In one such example, the selection of all courts causes the data for all courts to be presented in a combined presentation in the presentation block.

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

[0268] In various embodiments, when a user changes data or enters data into a presentation block, the data management tool 800 may be automatically placed in an edit mode. While in edit mode, data may not be transmitted to a downstream client or a data viewing platform of a downstream client. However, when the user accepts all current edits, the edit mode may be turned off, and data including any changes made while in edit mode may be sent to downstream clients, including the data viewing platform of the downstream client.

[0269] The hole graphic representation 806 can be provided in 2D graphics (although more advanced graphics, such as 3D, can also be used). The hole graphic representation 806 can include various navigation functions. For example, the hole graphic representation 806 can include one or more of a zoom function, a graphic rotation function, and / or a variable centering function, wherein the zoom function allows the user to selectively zoom in and out the graphics, the graphic rotation function allows the user to selectively rotate the graphics on the horizontal axis, the vertical axis, and / or other axes, and the variable centering function allows the user to move the center of the graphics in the presentation panel. In one example of the zoom function, a fast zoom can be provided to zoom in on the green, zoom out to show the entire hole, and / or zoom out to show the complete course. In one example, the graphics are oriented in a method that allows the maximum viewing from the teeing area to the green, such as a top view, a teeing area view, or a green view. The hole graphic representation can include various displayed distances about the hole. For example, it can be displayed as a scorecard yardage set for a round or one or two of the actual yardage between the teeing area and the flagpole. In one configuration, the hole setting information can be displayed on the hole graphic. For example, current hole information, such as one or more of teeing ground locations, flagstick locations, and / or fairway center points for holes of the course, may be displayed for each round. In one embodiment, the graphical presentation may be configured to display all players of a group at once upon request from a user, such as via interaction with a "show all group players" element.

[0270] Shot or ball position coordinates, such as shot or ball position coordinates collected via the operation of tracking module and adjoining device, can be drawn on hole graphic representation 806.For example, hole graphic representation 806 can include the figure of ball position relative to hole.For example, ball position can be drawn in the graphic presentation, to show the position of the end of the shot of team player.For the continuous shot that comprises position coordinates, line can be shown between the points drawn to describe the shot track.Because the point of beginning is teeing ground and the point of ending is flagpole, data management tool 800 can generate the line from these points to shot, and line has the coordinates of player's shot on hole or the position of ending.In one example, the distance of the ball position drawn from teeing ground, the distance of the last shot and / or the distance to flagpole can be displayed or provided as the selectable format option of definition.

[0271] Additional functionality may be provided for managing the coordinates of shots, such as enabling a user to: input the location of a received shot; move an existing location assigned to a shot; create a shot and the location for the shot; display all GPS or other location coordinates collected for a team player; and / or delete a shot and the location of the shot. In the example of the above functionality where breadcrumbs are present, the hole graphical representation 806 may be configured to enable a user to "pin" a shot to a breadcrumb.

[0272] In one embodiment, the functionality includes displaying all GPS and / or other coordinates collected for a team player, including coordinates not associated with a shot, such as bread crumbs. In the case of presenting all coordinates, the hole graphic representation 806 can be configured to associate a location with a player's shot.

[0273] In various embodiments, selecting a group from all group presentations 809 may cause group scorecard 807 to be populated with data associated with the group. In one example, hole graphic representations 806 may similarly be populated with stroke and / or ball position data related to the group. In one example, selecting a particular hole of a group via group scorecard 807 causes hole graphic representations 806 to zoom to the selected hole and display the plotted ball positions and stroke trajectories for the team players in the group.

[0274] Figure 8BAn example interface 810 of a group scorecard 807 is shown, which can be presented by a group scorecard data management tool 800 or can be accessed via interaction with the group scorecard data management tool 800, and all or part of the example interface 810 can be available in the corresponding presentation block view. Various elements of the group scorecard 807 can be displayed and / or edited via the operation and function of the group scorecard 807, as described in more detail below about each element. The group scorecard 807 can include various data elements, such as (a) team player names 811, (b) shot events 812, (c) shot counts 813, (d) totals 814, (e) totals 815, (f) today 816, (g) front nine hole score 817, (h) front nine hole score 818, (i) back nine hole score 819, (j) back nine hole score 820, (k) shot totals, or (l) one or more of the official shot 821.

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

[0276] If indicated, the shot events 812 may present the last shot event received from the score tracking system, or in one example, may present the last shot event received from the validation system. Various shot events may be presented, such as club selection, address ball, club hit, provisional ball, preliminary, final, and hole in. In one configuration, the shot events 812 may not be edited via the group scorecard component of the data management tool 800.

[0277] The shot count 813 may be a representation of the currently recorded shots on the hole that the player is on. If the team players have not yet started their round, the shot count may default to display the starting tee time. In one configuration, the shot count 813 may not be edited via the team scorecard component of the data management tool 800.

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

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

[0280] The front nine hole-by-hole scores 816 may present a list of scores for the front nine holes divided by hole. In some embodiments, depending on the configuration, a column or row header may be provided to display the hole number to improve clarity. In one configuration, the front nine hole-by-hole scores 816 may be edited via the group scorecard component of the management tool 800 by entering an integer or removing a score from the hole score field.

[0281] The front nine hole score 817 can present the stroke totals of the scores entered on the front nine holes. In one configuration, the front nine hole score 817 can be edited directly without passing through the group scorecard component of the data management tool 800.

[0282] Back nine hole-by-hole scores 818 can present a list of scores for the back nine holes divided by hole. In some embodiments, depending on the configuration, column or row headers can be provided to display the hole numbers to improve clarity. In one configuration, back nine hole-by-hole scores 818 can be configured to be edited via the group scorecard component of the management tool 800 by entering an integer or removing a score from the hole score field.

[0283] Back nine hole score 819 can present the stroke totals of the scores entered on the back nine holes. In one configuration, back nine hole score 819 can be edited directly without passing through the group scorecard component of data management tool 800.

[0284] The stroke totals 820 can present the stroke totals for the round. In one example, the stroke totals 820 can be displayed only when the front nine hole scores 817 and the back nine hole scores 819 have been filled with data. In one configuration, the score totals 820 can be edited directly without going through the group scorecard component of the data management tool 800.

[0285] Official strokes 821 can present the strokes received for the team players on all holes marked as official. In one configuration, the user can edit this element to indicate that any strokes on any hole of the player will no longer be edited.

[0286] Figure 8C An example interface of the team player shot details 808 of the data management tool 800 is shown, which is configured to interface the user with the operation of the team player shot details 808. The interface can be presented in Fig. 8A The team player shot details 808 element of the corresponding presentation block view of the team player shot details 808 may be accessed via interaction with the team player shot details 808 element. The elements of the team player shot details 808 may be displayed. In the operation of the team player shot details 808, the user may be enabled to edit various elements. In some embodiments, selecting a player in the group scorecard 807 or the all group presentation 809 populates the interface of the team player shot details 808 with the corresponding data elements of the selected group.

[0287] When a team player is selected for presentation and / or shot editing using team player shot details 808, the hole graphic representation 806 may default to displaying a course view, the current hole, the next hole, the first hole completed, the last hole completed, or the entire course view. In one embodiment, a specific hole is selected from the group scorecard 807, for example, by selecting from the front nine hole by hole 816 or the front nine hole by hole 818 ( Figure 8B ) data element view, the team player shot details 808 presents the shot details of the player for the specific hole. Therefore, the data management tool 800 can be configured to enable the user to selectively view the shot by hole using the group scorecard 807, or selectively view the shot details for the hole via interaction with the team player shot details 808.

[0288] In one example, checking the shot details of the team player about the hole via the team player shot details 808 makes the hole graphic representation 806 present the representation of the hole.Graphic can be oriented from left to right, wherein, the tee position is on the left side, and the green is on the right side.As mentioned above, functions such as zooming in and out of graphics can be provided.In one example, a fast zoom operator can be provided to allow the user to zoom quickly to various areas of the hole, such as tee, fairway, obstacle, green area, or zoom to the specific stroke of selection.Function can also include mobile graphics, to change the longitude and latitude of view in the static viewing area, for example, in any zoom value.Can also show yardage with respect to the setting position of tee and flagpole.Other yardages can be selectively presented in graphics as described above or selectively presented with respect to graphics.

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

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

[0291] Batting number 823 can correspond to the batting received. In one configuration, batting number 823 can be edited via team player batting details 808, allowing the user to enter an integer.

[0292] The stroke 824 accessed can correspond to the stroke number, which will be counted into the hole score of the team player on the stroke received. In one configuration, the stroke 824 accessed can be edited via the team player's stroke details 808, for example, thereby allowing the user to input an integer.

[0293] In one embodiment, a user may create a shot before or after any other shot. If a shot is created, the data management tool 800 may be configured to automatically set the shot number to the number after the previous shot. If a shot is created between two other shots, the other shots after the created shot may be automatically renumbered starting from the created shot. The data management tool 800 may edit the timestamp 826 to be set to a time after the previous shot or a time before the previous shot. In one example, when a shot is created, the default shot accessed is 1.

[0294] In one embodiment, the user can delete a shot. If a shot is deleted, the data management tool 800 can be configured to automatically renumber the remaining shots in order. If a shot is deleted, and the shot is not a shot in the marked hole 831, but a shot in which the "hole-in" mark is available, the data management tool 800 can recalculate the score using the new total of the shots accessed. If a shot with a "hole-in" mark is deleted, the data management tool 800 can be configured to clear the calculated score. As described below, the user can set or remove the "hole-in" mark. After deleting the shot including the "hole-in" mark, the user can set the "hole-in" mark for another shot, and the data management tool 800 calculates the revised score from the other shot. In one example, after deleting the shot marked as "hole-in", the user can be prompted to mark the shot with the "hole-in" mark.

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

[0296] The timestamp 826 may correspond to the timestamp of a hitting event 825, such as the latest hitting event 825. In one configuration, the timestamp can be edited via the team player hitting details 808, allowing the user to edit the field in the format of time and today input.

[0297] The shot type 827 may correspond to a shot type identifier, such as a shot, penalty stroke, or drop shot, which corresponds to such a shot type collected by the ST application via a companion device. In one configuration, the shot type 827 can be edited by the data management tool 800 to change or add a shot type from a list. In one example, interacting with the shot type 827 causes a drop-down menu to appear, which includes a list of available shot types, and the list of available shot types enables the user to select one of the shot types to set. In various embodiments, the data management tool 800 may automatically apply various rules to the editing of the shot type. For example, if the shot type created is a "drop shot", the shot 824 accessed may be zero. If the shot type created is a "drop shot", the shot number 823 may be the same as the previous shot or penalty stroke type. If the shot type created is a "penalty stroke", the shot 824 accessed may be defaulted to 1. If the type of shot created is "penalty stroke," the shot number 823 may be incremented by the amount identified for the shot 824 accessed.

[0298] Location 828 may correspond to a graphical location of a shot determined by a location method described herein, e.g., via a tracking module, a location system, a rangefinder, via manual input indicating the location of the ball relative to a displayed map, or operation of other location methods used by the STTM scoring system. In one configuration, location 828 is editable to change the location from an available list of location descriptions for the golf course being played, such as tee boxes, fairways, roughs, first cuts, hazards, water, out of bounds, greens, etc. In one example, interacting with the location data element may cause a drop-down menu to appear that includes a list of available locations for the golf course that may be set for the location.

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

[0300] Hole in 831 can be used to identify whether a specified shot is the result of a ball being holed in. In one configuration, if a shot is considered to be holed in, the user can set or remove a flag. The data management tool 800 can automatically apply various rules to the "hole in" flag. For example, if the last shot with the highest shot number is marked as "hole in", a score can be calculated and stored based on the sum of all shots accessed. If a shot that is not the last shot with the highest shot number is marked as "hole in", the shot is set to the highest shot number, and all other shots can be renumbered in sequence.

[0301] Reference Fig.8D In various embodiments, a shot event review viewer 832 may be provided. For example, each shot in the player shot details 808 may be operable to be optionally expanded to display additional associated shot events. In the viewer shown, the shot events for the shot are populated in the shot event 823 element. As shown, the shot events for the shot number include club selection, aiming, club strike, preliminary and final. Therefore, the shot did not result in the player holding the ball. In various embodiments, the shot details received from the companion device may be marked as "preliminary" and reviewed via the operation of the data management tool 800 or the verification system described below, and a successful review of the operation of the data management tool 800 or the verification system described below may set the shot details to "final". In one configuration, the fields of the shot event review viewer 832 cannot be edited except for the timestamp field. The shot event review viewer 832 may be configured to enable a user to reorder or sort the shot events in a sequence of events. The shot event review viewer 832 may be configured to enable a user to collapse the review of review events, such as presenting only the most recent shot event.

[0302] Fig. 8E An example interface of all group presentations 806 of the data management tool 800 is shown, which is configured to interface a user with the operation of all group presentations 806. All or a portion of the interface may be in Fig. 8A The corresponding presentation block view of the interface may be presented in the interface, or may be accessed via interaction with all group presentations 806 provided in the corresponding presentation block view. Various elements of the interface may be displayed and / or edited via the operation of all group presentations 806.

[0303] All groups present 809 and can be configured to show the round of selection, and this can comprise only showing the round of selection.In one example, all groups present 809 and be configured to show the information of all the courts of the court of selection or tournament, if selected.In some configurations, display can be able to scroll, and / or each data column can be sorted in ascending or descending order based on the information available in the column.In one configuration, in the field in all groups present 809, none can be directly edited via all groups present 809.In one embodiment, if the scorecard of the team player is for example marked as "official" via the verification system described in more detail in other places of this paper, the presentation of the group presentation 809 shown can comprise the notification about the name of the team player.

[0304] The all group presentation 809 may include various data elements, such as one or more of the following: (a) group number 832 - corresponding to the number assigned to the group; (b) course 833 - corresponding to the course on which the group number is playing; (c) starting hole 834 - corresponding to the first hole that the group starts based on the grouping for the round; (d) tee time 835 - corresponding to the starting tee time of the group; (e) ranking 836 - corresponding to the expected ranking of the players during the course of the match during the round in progress; (f) team player names 837 - corresponding to the identification of the players; (g) total 838 - corresponding to the current total standard of the event. 844—corresponds to the total strokes of the round, which is displayed when the front nine hole score 841 and the back nine hole score 843 have data.

[0305] Figure 8F An example interface of the data difference panel 805 of the data management tool 800 is shown, which is configured to interface a user with the operation of the data difference panel 805. All or a portion of the interface may be Fig. 8A The data difference panel 805 may be displayed in the corresponding presentation block view or may be accessed through interaction with a data difference panel component provided in the corresponding presentation block view. Various elements of the interface may be displayed and / or edited through operation of the data difference panel 805.

[0306] The data difference panel 805 may include two sub-elements, including 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 difference panel 805 can be manipulated to enhance user experience and efficiency. For example, data rows can be scrollable. Data columns can also be sorted in ascending or descending order based on the information available in the column. In one configuration, the data difference panel 805 can provide interface elements that can be operated to mark a warning as reviewed and remove the warning from presentation. In one example, the data difference panel 805 can enable a user to: review all warnings that have been marked as reviewed; review errors and warnings by group, hole, or team player; reset and display all errors and warnings in the case where any content has been set to reviewed and removed; scroll through all messages through the panel in the case where all messages are not visible in the initial display; or turn all rules on or off, or select error and / or warning message rules. In one example, none of the fields can be edited.

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

[0309] Error message 853 may be related to missing data and / or program anomalies regarding the recorded score and / or position data, which may be displayed in an error message 853 element associated with the identification information. Various error messages may be included, such as one or more of the following: missing position description; missing coordinates on a shot; missing score, for example, if there is a scoring gap between holes, a missing score may be displayed; the shot accessed does not equal the recorded score; a score was recorded, but no shot was taken; no penalty stroke was recorded for a shot marked as provisional, where the shot accessed was 1; non-contiguous timestamps for the shot trajectory from hole to hole; the first shot was not taken from the teeing position; a shot was not marked as final after the next shot was received; or a team player was not marked as an official shot after having completed a round.

[0310] Warning message 854 may be related to an event or lack of an event detected by 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 operation of a scoring system, which may include a location system. Warning message 854 may be displayed with associated identifying information. Various warning messages 854 may be included, such as one or more of the following: the tracked player's shots are out of sync with those of other team players in the group; multiple consecutive drops by a team player; drops without penalty strokes in the trajectory of a team player's shots; the coordinates of the shot are no closer to the flagpole location than the coordinates of the previous shot; more than 10 minutes between a team player's shots; multiple shots include locations from the teeing ground; an atypical score for a team player, such as double bogey or worst and eagle or better; 5 minutes have passed but the shot has not yet received coordinates; the team player is on the green and then appears to leave the green; the tee shot distance is outside the range of normal distances on par 4 and par 5, such as less than 180 yards and longer than 380 yards; the shot is marked as a hole-in with a distance greater than 30 yards; the flagpole has not yet been set and a team player's shot has been received on the hole; or, the teeing ground has not yet been set and a team player's shot has been received on the hole.

[0311] refer to Figure 8G In various embodiments, the above FIG. 8A to FIG. 8F The described presentation blocks of the data management tool 800 and / or one or more associated components of the presentation blocks of the data management tool 800 may be configured to create connections between the presentation blocks of the data management tool 800 and / or one or more associated components of the presentation blocks of the data management tool 800. For example, the 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, such as making a selection, in one block view or otherwise with respect to an associated element, a connection is established for one or more other blocks to thereby update the appropriate presentation in the corresponding block.

[0312] The presentation block may be configured to apply the connection rules for all group presentations 809. In one example, selecting the name of a team player causes one or more of the following: causing the group scorecard 807 to present the group that the team player is in; causing the hole graphic representation 807 to present the current hole that the team player has not yet completed; causing the team player shot details 808 to present the strokes received on the current hole that the team player has not yet completed; causing the data difference panel 805 to present all errors and warnings for the selected team player on all holes. In the above or another example, selecting a group number may cause one or more of the following: causing the group scorecard 807 to present the selected group; causing the hole graphic representation 806 to present the current hole to the leading team player in the group and default and present the current hole that the team player has not yet completed; causing the team player shot details 808 to display the strokes received on the current hole that the leading team player in the group has not yet completed; or causing the data difference panel 805 to present all errors and warnings for the selected group. In any one or another of the above examples, selecting a team player's hole may: cause the group scorecard 807 to present the group that the team player is in; cause the hole graphic representation 806 to present the selected team player and the selected hole; cause the team player shot details 808 to present the shots received on the hole and the selected team player; or cause the data difference panel 805 to present all errors and warnings for that hole and team player, all of which may include any warnings that have been marked as reviewed.

[0313] In any one or another of the above embodiments, interaction with the group scorecard 807 may cause connection with one or more other components of the data management system 50. For example, selecting the name of a team player may cause one or more of the following: causing the hole graphic representation 806 to present the current hole that the team player has not yet completed; causing the team player shot details 808 to present the shots received on the current hole that the team player has not yet completed; causing the data difference panel 805 to present all errors and warnings for the selected team player on all holes; or causing the all group presentation 809 to present the group or team player at the top of the presentation. In yet another or another example, selecting a hole of a team player may cause one or more of the following: causing the hole graphic representation 806 to present the selected team player and the selected hole; causing the team player shot details 808 to present the shots received on the hole and the selected team player; causing the data difference panel 805 to present all errors and warnings for the hole and the team player, all errors and warnings may include any warnings that have been marked as reviewed; or causing the all group presentation 809 to present the group or team player at the top of the presentation.

[0314] In any or another of the above embodiments, interaction with team player shot details 808 may result in connection with one or more other components of data management system 50. For example, if coordinates for the shot exist, selecting the shot may cause the location coordinates in the hole graphical representation 806 to be presented.

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

[0316] In any or another of the above embodiments, interaction with the data difference panel 805 may cause connection to one or more other elements of the data management system 50. For example, selecting an error or warning to be reviewed may cause the presentation of the group scorecard 807 to be updated based on the team players and groups identified in the error or warning message. In another or yet another example, selecting an error or warning to be reviewed may cause the presentation of the hole graphic representation 806 and / or the team player shot details 808 to 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, which is configured to provide a simplified verification of the official scorecard of the player according to the score collected by the score tracking system. If necessary, the verification system 70 can be configured to allow the user to change the score obtained from the operation of the score tracking system. Using the verification system 70, the user can also quickly identify the scorecard that has been reviewed and is marked as official. In certain embodiments, this official designation can be transmitted on one or more data platforms or otherwise immediately available on one or more data platforms, so as to no longer receive the score editing for the corresponding player to the user communication of the scoring data. In one example, the verification mark as the official scorecard is retained, for archiving in the database, propagating later, internal verification, compiling together with the additional verified scorecard, analyzing or their combination.

[0318] Verification system 70 can be configured to operate in various network environments, such as those network environments identified by the subsystems of various STTM systems / various STTM systems herein. For example, verification system 70 can be configured to operate in a local, remote or distributed network-based environment. Verification system 70 can be configured to operate in a web-based, cloud-based or other suitable network environment. In one embodiment, verification system 70 can operate in a browser or similar browser environment. For example, verification system 70 can include a verification application, which has the ability to run on multiple browser tabs with different settings. In another example, verification system 70 includes an edit tracking feature, wherein verification system 70 tracks the editing of users. These user edits are tracked as being associated with the specific user who edits. The tracking feature of verification system can be configured to store the editing of the tracking of users, and enables the editing of tracking to be reviewed. For example, review users can access verification system 70 and view the list of users, and review the details of the editing made by each user to which scorecards. In some configurations, the verification system 70 may allow a reviewing user to view a user's edits by type, such as score, stroke, position, type of shot (drop, stroke, penalty stroke), etc. In this or another configuration, the verification system 70 may be configured to allow a reviewing user to view one or more or all of a user's edits by one or more types during a specific time period or event.

[0319] refer to FIG. 9A to FIG. 9B In one embodiment, the verification system 70 can be configured to generate two functional verification tools, which are used for scorecard verification. Each verification tool can be provided in one or more tabs, screens, pages, windows, or any suitable displayable arrangement with the functions described herein. The verification tools can be displayed separately, or can be displayed together in whole or in part. In one example, the first tool panel can be configured to input player scorecard scoring data and compare with a second score collection method, such as an automatic or semi-automatic scoring method. The operation of the first tool can be referred to as blind verification in this article. The second score collection method according to various embodiments is described below with respect to the tracking system method, but it should be understood that variations of the score collection method or other score collection methods can be similarly applicable to the operation of the verification system. Therefore, the first verification tool can be configured for blind verification, which allows the user to enter a score for the player's scorecard, wherein the entered score is automatically compared with the scoring data recorded by the score tracking system. The second verification tool can generate an output of all scores and player rankings for a specific group of players, all groups, all players, or their desired combinations. In various embodiments, the verification tools can be arranged in selectable tabs, wherein each tab includes a verification tool within the panel.

[0320] Fig.9A An example first verification tool 901 is shown, which is configured for blind verification.

[0321] An event selector 902 may be provided to allow a user to select an event that the verification system 50 will use for player scorecard verification. The event selector 902 may include a list of selectable events. Interfacing with the event selector 902 may cause a drop-down menu, list, or other selectable format of events to be selected.

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

[0323] A trim line 904 may be provided to allow the user to view a display of current real-time trim data. In some embodiments, trim line 904 is presented only when the selected round is a trim round. Viewing trim line 904 may provide the user with insight into what a modification may do with respect to a trim. For example, changing the score of one player may result in several other players advancing / eliminating.

[0324] A group selector 905 may be provided to allow a user to select a group including a player for scorecard verification.

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

[0326] The name of the player currently being reviewed for scorecard validation may be displayed in the player name 907 field. In some configurations, an image of the player, such as an avatar, may be displayed.

[0327] Score input can be provided for inputting the score of the player from the scorecard of the player. Score input can include hole field 910, for example 18 hole fields, and hole field 910 is used to input the scores of all holes from round. Hole field 910 can be configured to input manually. In one example, hole field 910 includes a drop-down menu for each hole, and the drop-down menu has selectable score, switching field or other suitable input methods. In the illustrated embodiment, score input includes hole field 910, and hole field 910 requires the user to select hole field 910 and mouse navigation, for example, using input key or tab to enable each field to be used for input. As mentioned below, the score recorded by the score tracking system, received by the verification system 70 may be lacking or otherwise hidden from the visual field, so that from the user's perspective, manual score input and the comparison with the score tracking system score subsequently are blind.

[0328] The scores received by the system, such as those received from the score tracking system, can be imported into the verification system 70. In some embodiments, the import of the score tracking system score can be automatic after receiving the score, or can be delayed. The score data and the associated player data can be imported into the verification system after completing each hole, regularly, when received, after a predetermined number of holes, or when a player or group has completed a round, which can be indicated by the scorekeeper via a companion device. For example, when the scorekeeper indicates that the player or group has completed a hole or round, the calculated score and the player's name or number associated with the data can be sent directly or indirectly to the verification system. In the illustrated embodiment, if the scorecard is not yet marked official on the selected player, the score received by the system will not be visible or will be blank when the user enters the score for the purpose of blind verification.

[0329] In the example shown, the first verification tool 901 includes a comparison trigger 912 to cause a comparison between the scores. For example, with respect to blind verification, a user may interact with the comparison trigger 912 to initiate a comparison between a player's scorecard and the scores received by the system to be verified. Prior to triggering the comparison, the first verification tool 901 may not display the scores received by the system. In some embodiments, the comparison may be initiated after one or all scores are entered or after populating the scores received by the system, which may be provided as a button or other interactive trigger.

[0330] As the result of the comparison operation, the score received by the system can be filled in the hole field 914, and the hole field 914 is juxtaposed with the corresponding hole field 910. The validity notice about the hole or the associated score can be shown, to indicate the score matching, score difference or score matching and score difference. For example, when triggering the option of comparing the blind input score with the system score, the system score can occur, and can show the valid notice of what matching and what mismatching. In the illustrated embodiment, the solid arrow 918 indication score matching between the score hole field 914 received by the blind score hole field 910 and the system, and the dotted arrow 920 indication difference. The validity notice can be provided by any suitable mark. For example, matching and / or difference can be indicated by different colors, shadows, texts, outlines, frames, symbols or other suitable perceptible marks.

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

[0332] In some embodiments, the user can edit the score to resolve the difference. In one configuration, the score with the difference or the edited score is sent or saved for additional review. As mentioned above, marking the scorecard as official can transfer the scorecard, score, or official designation to a database for storage and / or dissemination to one or more data platforms, and indicate that the score is official. In some embodiments, the score recorded by the score tracking system can be transferred to one or more data platforms as an unofficial score, and the score is marked as official via a verification system so that verification is transmitted to the data platform to indicate that the score is now official.

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

[0334] refer to Fig. 9B, the second verification tool 830 can present the scoring data for one or more groups. The presentation can be configured to display the scores from the selected events and / or rounds, such as the scores from the selected events and / or rounds selected with respect to the first verification tool 901. The scores presented can include unofficial tracked scores and official scores. As described elsewhere herein, various score transmission timing schemes can be used. In various embodiments, the tracked scores can be populated when the companion device 12 transmits, such as after each shot input or when a player or group completes a hole.

[0335] Scoring data can be arranged in various formats. In the illustrated embodiment, scoring data is arranged so that each data column is sorted in ascending or descending order based on the information available in each column. From the basic user standpoint, fields will usually be unable to edit. The display can be scrollable to view groups other than those groups initially displayed. In one example, selecting a player or group will fill the player or group with respect to the second verification tool. Therefore, a user can select a player or group and view additional details about the player's or group's score. In one example, if manual score input has not yet been entered or processed by verification, selecting a player or group will fill a group selector and / or player selector field to the selected player or group. In one embodiment, a player with a score marked as official is marked with a visual mark as a notification of the score marked as official.

[0336] The scoring data presented may include various data points about the players and scores, such as one or more of the following: (a) group number 931 - corresponding to the group number of the group assigned to the player; (b) course played 932 - corresponding to the course for which the scoring data was collected; (c) starting hole 933 - corresponding to the first hole at which the group starts based on the grouping for the round; (d) tee time 934 - corresponding to the tee time for the start of the group; (e) ranking 935 - the expected ranking of the player during the ongoing round during the course of the match; (f) team player name 936 - corresponding to the first and last name of each team player in the group. ; (g) Total 937 - corresponds to the current total par relative score of the event; (h) Today 938 - corresponds to the par relative score of the round; (i) Front Nine Hole-by-Hole Score 939 - corresponds to the list of scores divided by holes for the front nine holes; (j) Front Nine Hole Score 940 - corresponds to the stroke totals of the scores entered on the front nine holes; (k) Back Nine Hole-by-Hole Score 941 - corresponds to the list of scores divided by holes for the back nine holes; (l) Back Nine Hole Score 942 - corresponds to the stroke totals of the scores entered on the back nine holes; (m) Stroke Total 943 - corresponds to the stroke totals of the round; (n) combinations thereof. In various embodiments, the stroke totals 943 will be displayed only when the front nine hole scores 940 and the back nine hole scores 942 have data.

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

[0338] The players of the group can automatically fill the equipment assignment element of the equipment management system.After the group is defined, the equipment management system can assign the tracking module from the equipment list to each group and player.In one example, the companion device or the ST application executed on the companion device is assigned or programmed to a specific group, and the tracking module assigned to the group can fill the companion device via the ST application for the scorer who links the scoring data to the tracking module for specific identification.In a variant, the scorer assigned to the group can enter their credentials or otherwise log in to the ST application, and the group information of the group assigned to the scorer thus fills the ST application.In another configuration, the player's name identification is entered in the ST application for the player for the transmission of the scoring data, and one or more of the position system, the data management system or the verification system is configured to access the tracking module assignment, so that the scoring data is paired with the tracking module data.

[0339] During the round, the scorer can collect scoring data by inputting various hitting events and other data into the accompanying device as described herein. The hitting event can be associated with a timestamp. The accompanying device can transmit the scoring data to the management system. The tracking module can automatically and continuously collect position data or positioning data at defined intervals or at the occurrence of defined events. In one example, the tracking module is configured to continuously, for example, per second, obtain GPS coordinates corresponding to the tracking module position. The tracking module can automatically transmit the obtained coordinates to the management system at defined intervals or at the occurrence of defined events. In one example, the tracking module transmits the collected position data or positioning data to the management system every five seconds. As mentioned above, instead of, for example, hybrid methods, GPS, in addition to, for example, hybrid methods, GPS, or with, for example, hybrid methods, GPS combination, other position methods can be used. For example, the STTM system can include or combine a location network, and the location network includes a UWB location network. Position data or positioning data can be directly or indirectly transmitted to the management system from the tracking module, the location network or other devices.

[0340] The location system can access the tracking module assignment and pair the timestamp with the location of the assigned tracking module. The data management system can access the scoring data, where the scoring data can be reviewed and edited using the data management tool if necessary. The verification system can then compare the score tracking system score with the scorecard of the corresponding player. For example, the verification system can apply blind verification. The verification system can then reconcile the score tracking system score with the player scorecard. The verification system can then mark the score obtained by the reconciled system as "official". The "official" designation can then populate the data management tool interface to indicate that no additional scores or score modifications will be entered for the player. The official scores and related data collected by the accompanying device and tracking module during the game 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. These techniques may operate as primary, secondary, backup, or alternative location determination methods with respect to the utilization of the tracking module.

[0342] In one embodiment, the companion device or another electronic device is equipped with a laser rangefinder, which is operated by a scorekeeper, such as a human or a robot. The rangefinder is used to determine the distance of an object, such as a player or a ball, from the device. The device may also include an orientation sensor, such as a magnetic field and / or gravity field sensor, to combine distance and orientation relative to a map of the course. To further enhance the position determination, the position of the device, such as coordinates, is combined with the angle and distance of the object from the device because the device is located at a known location or the position of the device is determined by the device or another device. For example, a device in a mobile use case can obtain the device's GPS (or other global constellation coordinates), and the device's GPS can be enhanced as described herein, for example, using a Wide Area Augmentation System (WAAS), a Differential GPS (DGPS) such as a Global Differential GPS (GDGPS), a Continuously Operating Reference Station (CORS), or enhanced navigation based on Signals of Opportunity (SOP), UWB, LTE, cellular, radio, TV, Wi-Fi, other satellite signals, etc. Any location network technology, such as those described herein, can also be used to determine the location of the device, for example, using UHF, NFC, Wi-Fi, low-power Bluetooth, or UWB to determine the location of the device. The coordinates of the object are determined, and the coordinates can be superimposed or mapped to a golf course to determine the location of the object relative to the golf course. In one embodiment, the device is a device that supports Real Time Kinematic (RTK) and uses RTK to determine the coordinates of the device. For example, an RTK base station or network can be used to determine the location of the device, which is used in combination with the direction and distance of an object aimed at with a laser rangefinder to determine the object location. It is noteworthy that, as described elsewhere herein, the tracking module can similarly be an RTK-enabled device, and the location network can include an RTK base station or RTK network.

[0343] In one embodiment, the camera system is positioned around a golf course. One or more cameras can track movement and identify distances using an associated laser or rangefinder or via optical calculations. For example, each camera can calculate the distance of a ball or other object of known size by comparing the size of the optical capture of the object with the size of the optical capture of the known size of the object. Further determination of the angle of the camera can be used to map the position of the object at the distance and angle from the camera relative to the area around the camera. Position determination can be enhanced by using multiple cameras, for example, by using multiple cameras to triangulate or otherwise determine the position of the ball or other object. In one example, the camera can use an optical map of the area of ​​the golf course from the field of view of a fixed camera to determine the position of the object relative to the known position in the mapped area. For example, by comparing the captured image of the object with the surrounding features in the image at the known position, the approximate position of the object can be determined. Optical calculations such as those described above can be used to determine the distance to enhance the accuracy of the position determination. In the above or another example, the radar can be implemented to track the object, and the object can include position, speed, trajectory, acceleration or other parameters. In the above or another example, the camera can be configured for optical recognition. For example, the camera can utilize facial recognition, body recognition, gait recognition, clothing recognition, ball / shape recognition, etc. for identifying participants and / or balls, so as to pair the position with players and / or players' balls. In one embodiment, the player carries or wears an optical, electromagnetic, or reflective marker that can be recognized by a camera or associated receiver that uniquely identifies the player. In one embodiment, the camera can locate the player and / or ball using optical recognition / augmented reality (AR). The camera can usually be located at a known location, but in some cases, one or more cameras can be utilized in a mobile environment, for example, using a real-time dynamic base station or a location method for the camera, such as those methods described herein for determining the location of the tracking module. In some embodiments, the camera can be used to identify motion and objects, and a laser or rangefinder associated with the camera can be aimed at these objects to determine the distance of the object from the camera. The camera perspective is combined with the distance to determine the position of the object. In some embodiments, the topology of the area can be mapped or determined, and the topology of the area is added to the distance calculation. In some embodiments, such a camera system is operated by humans, robots, or completely autonomously. The camera may operate in the visible spectrum and / or in the spectrum to include one or more of the visible spectrum, ultraviolet spectrum, or infrared spectrum.

[0344] The systems and methods disclosed herein may include additional functions and features. For example, the operating functions of the systems and methods may be configured to be executed on a dedicated processor, which is specifically configured to perform the operations provided by the systems and methods. It is worth noting that the operating features and functions provided by the systems and methods can increase the efficiency of computing devices, which are 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 and / or generated in the system, the devices and elements in the system may need to use the processor and memory of the system to perform a reduced amount of computer operations compared to traditional methods. In this scenario, less processing power needs to be utilized because the processor and memory do not need to be dedicated to processing. Therefore, by utilizing the software, technology and algorithms provided in this disclosure, there are a lot of savings in the use of computer resources. In some embodiments, the various operating functions of the system may be configured to be executed on one or more graphics processors and / or dedicated integrated processors. In some embodiments, the various functions and features of the systems and methods can be operated without any human intervention and can be performed entirely by computing devices. In some embodiments, for example, many computing devices can interact with the devices of the system to provide system-supported functions. Additionally, in certain embodiments, the computing devices of the system may operate continuously and without human intervention to reduce the likelihood of errors being introduced into the system.

[0345] At least a portion of the methods and techniques described with respect to exemplary embodiments may be combined with a machine, such as, but not limited to, a computer system or other computing device, within which a set of instructions, when executed, may cause the machine to perform any one or more of the methods or functions discussed above. The machine may be configured to facilitate various operations performed by the system. For example, the machine may be configured to, but not limited to, assist the system by providing processing power to assist with the processing load experienced in the system, by providing storage capacity for storing instructions or data traversing the system, or by assisting with any other operations performed by or within the system. As another example, a computer system may assist in enhancing the accuracy of the collected scoring data collected in a reduced infrastructure environment by combining rules, such as error and / or warning rules that automatically identify potential differences. As another example, using a tracking module that does not interfere with the performance of the player or does not require player interaction for tracking positions provides accurate tracking that greatly reduces infrastructure and human intervention compared to current methods.

[0346] In some embodiments, the machine can operate as a standalone device. In some embodiments, the machine can be connected to other machines and systems (e.g., using a communication network, another network, or a combination of a communication network and another network), such as but not limited to tracking modules, companion devices, management devices and associated system servers, databases, any other systems, programs and / or devices, or any combination thereof, to perform operations and assist other machines and systems to perform operations. The machine can be connected to any component in the system. In a networked deployment, the machine can operate with the performance of a server or client user machine in a server-client user network environment, or operate as a peer machine in a peer (or distributed) network environment. The machine may include a server computer, a client user computer, a personal computer (Personal Computer, PC), a tablet PC, a laptop computer, a desktop computer, a control system, a network router, a switch or a bridge, or any machine capable of (sequentially or otherwise) executing a set of instructions, which specifies the actions that the machine will take. Further, although a single machine is shown, the term "machine" should also be considered to include any collection of machines that execute a set of instructions (or multiple sets of instructions) individually or jointly to perform any one or more of the methods discussed herein.

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

[0348] Special hardware implementations can also be constructed to implement the methods described herein, including but not limited to application specific integrated circuits, programmable logic arrays, and other hardware devices. Applications that may include the apparatus and systems of various embodiments include a wide variety of electronic and computer systems. Some embodiments implement functions in two or more specific interconnected hardware modules or devices, wherein related control and data signals communicate between modules and through modules, or as part of an application specific integrated circuit. Therefore, the example system is suitable for software, firmware, and hardware implementations.

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

[0350] The present disclosure contemplates a machine-readable medium containing instructions so that a device connected to a communication network, another network, or a combination thereof can use the instructions to send or receive voice, video, or data and communicate through the communication network, another network, or a combination thereof. The instructions can also be transmitted or received through the communication network, another network, or a combination thereof via a network interface device. The term "machine-readable medium" should be deemed to include a single medium or multiple media (e.g., a centralized or distributed database and / or associated caches and servers) that stores one or more sets of instructions. The term "machine-readable medium" should also be deemed to include any medium that is capable of storing, encoding, or carrying a set of instructions executed by a machine and causing the machine to perform any one or more of the methods of the present disclosure. The terms "machine-readable medium", "machine-readable device" or "computer-readable device" shall accordingly be deemed to include, but not be limited to: a storage device, a solid-state memory such as a memory card or other package containing one or more read-only (non-volatile) memories, random access memories or other rewritable (volatile) memories; a magneto-optical or optical medium such as a disk or tape; or, other self-contained information archive or collection of archives, other self-contained information archives or collections of archives are considered to be equivalent to tangible storage media distribution media. A "machine-readable medium", "machine-readable device" or "computer-readable device" may be non-transitory and, in certain embodiments, may not itself include waves or signals. Accordingly, the present disclosure is deemed to include any one or more of a machine-readable medium or distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.

[0351] The description of the arrangement described herein is intended to provide a general understanding of the structure of various embodiments, and the description of the arrangement described herein is not intended to be used as a complete description of all elements and features of the devices and systems that may use the structure described herein. Other arrangements can be used and derived therefrom so that structural and logical replacements and changes can be made without departing from the scope of the present disclosure. The figures are also representative only and may not be drawn to scale. Certain proportions of the figures may be enlarged, while other proportions may be minimized. Therefore, the specification and drawings should be regarded as illustrative rather than restrictive.

[0352] Therefore, although specific arrangements have been shown and described herein, it should be understood that any arrangement calculated to achieve the same purpose may replace the specific arrangement shown. The present disclosure is intended to cover any and all changes or variations of the various embodiments and arrangements of the present invention. Upon review of the above description, the combination of the above arrangements and other arrangements not specifically described herein will be apparent to those of ordinary skill in the art. Therefore, it is intended that the present disclosure is not limited to the specific arrangements disclosed as the best mode contemplated for practicing the present invention, but that the present invention will include all embodiments and arrangements falling within the scope of the appended claims.

[0353] The foregoing is provided for the purpose of illustrating, explaining, and describing embodiments of the present invention. Modifications and changes to these embodiments will be apparent to those of ordinary skill in the art and may be made without departing from the scope or spirit of the present invention. Upon review of the above embodiments, it will be apparent to those of ordinary skill in the art that the embodiments may be modified, reduced, or increased without departing from the scope and spirit of the claims described below.

Claims

1. A score tracking method, the method comprising: collecting or receiving location data by a location system, wherein the location data corresponds to a location of a tracking module carried by a player participating in a golf tournament, and wherein the location data includes or is used to generate a plurality of sets of location coordinates, each set of location coordinates corresponding to a location of the tracking module at a specified time during play of the golf tournament; receiving an indication of an occurrence of a hitting event associated with a player, the indication being input into a companion device by a scorekeeper carrying the companion device and viewing the player carrying the tracking module; receiving or generating a timestamp corresponding to a time at which the indication of the occurrence of the hitting event was entered into or received from the companion device by the scorekeeper; and The timestamp is paired with a set of position coordinates corresponding to the location of the tracking module at the occurrence of the hitting event.

2. The method according to claim 1, wherein: The plurality of sets of position coordinates correspond to positions of the tracking module within a time period, and wherein each set of position coordinates corresponds to a predefined time interval within the time period.

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

4. The method according to claim 3, wherein: The position data includes parameters of the position signal, and the position system calculates the plurality of sets of position coordinates using the parameters of the position signal.

5. The method according to claim 3, wherein: The tracking module calculates the position of the tracking module using the parameters of the position signal and transmits the position to the position system as the position data.

6. The method according to claim 1, wherein: The tracking module is configured to output a position signal, and the tracking module calculates position data using the position signal.

7. The method according to claim 1, wherein: The tracking module is configured to output a position signal for receipt by a plurality of beacons to calculate the position data corresponding to the position of the tracking module, the plurality of beacons being positioned around the golf course.

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

9. The method according to claim 1, wherein: The timestamp corresponds to a time at which the indication of the occurrence of the ball striking event is input into the companion device, and wherein the companion device generates the timestamp and transmits the timestamp to the location system.

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

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

12. The method according to claim 1, further comprising: Position data corresponding to a plurality of tracking modules, each carried by a respective player participating in the golf tournament, and an indication of a scoring event are received.

13. The method according to claim 12, wherein: A single companion device is configured to receive indications of scoring events associated with a plurality of players, each player carrying a separate tracking module.

14. The method according to claim 13, wherein: The position data and the indication of the scoring event include identification data, the identification data including an identification of the player carrying the tracking module or an identification number of the tracking module carried by the player, and wherein pairing the timestamp with a set of position coordinates corresponding to the position of the tracking module at the occurrence of the hitting event includes: matching the corresponding identification data.

15. The method according to claim 1, wherein: The stroke event comprises a ball hit, and wherein the position of the tracking module at the occurrence of the stroke event serves 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 the 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 wherein 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 positioning data, and the location system uses the positioning data to calculate the location coordinates.

21. The method according to claim 1, wherein: The plurality of location coordinate sets include a Global Positioning System GPS coordinate set.

22. The method according to claim 1, wherein: The plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

24. The method of claim 1, further comprising: The holes of the golf course are divided into regions, each region corresponds to a series of position coordinates, and the current region where the tracking module is located is determined from the plurality of position coordinate sets.

25. A score tracking system, the system comprising: A tracking module configured to be carried by a player participating in a golf tournament, an application configured to interface a user with scoring operations via a user interface of a companion device, the companion device being separate from the tracking module, and configured to receive input via the user interface indicating the occurrence of a striking event, wherein the input causes the application to set a timestamp corresponding to the occurrence of the striking event; and A position system configured to collect or receive position data, wherein the position data includes a plurality of position coordinate sets, or the position system generates the plurality of position coordinate sets using the position data, wherein each position coordinate set corresponds to the position of the tracking module at a specified time, wherein the position system is configured to pair the timestamp with the position coordinate set corresponding to the position of the tracking module at the occurrence of the hitting event.

26. The system of claim 25, wherein: The plurality of sets of position coordinates correspond to positions of the tracking module within a time period, and wherein each set of position coordinates corresponds to a predefined time interval within the time period.

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

28. The system of claim 27, wherein: The position data includes parameters of the position signal, and the position system is configured to calculate the plurality of sets of position coordinates using the parameters of the position signal.

29. The system of claim 27, wherein: The tracking module is configured to calculate a position of the tracking module using parameters of the position signal and transmit the position to the position system as the position data.

30. The system of claim 25, wherein: The tracking module is configured to output a position signal, and the tracking module calculates position data using the position signal.

31. The system of claim 25, wherein: The tracking module is configured to output a position signal for receipt by a plurality of beacons to calculate the position data corresponding to the position of the tracking module, the plurality of beacons being positioned around the golf course.

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

33. The system of claim 25, wherein: The timestamp corresponds to a time at which the indication of the occurrence of the ball striking event is input into the companion device, and wherein the companion device generates the timestamp and transmits the timestamp to the location system.

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

35. The system of claim 25, wherein: The indication of the occurrence of the hitting event includes an identification of a player carrying the tracking module.

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

37. The system of claim 25, wherein: A single companion device is configured to receive indications of scoring events associated with a plurality of players, each player carrying a separate tracking module.

38. The system of claim 25, wherein: The position data and the indication of the scoring event include identification data, the identification data including an identification of the player carrying the tracking module or an identification number of the tracking module carried by the player, and wherein the position system is configured to match the corresponding identification data to pair the timestamp with a set of position coordinates corresponding to the position of the tracking module at the occurrence of the hitting event.

39. The system of claim 25, wherein: The stroke event comprises a ball hit or a player set, wherein the position of the tracking module at the occurrence of the stroke event serves as a proxy for the position of the ball of the player carrying the tracking module resulting from a previous stroke.

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

41. The system of claim 40, wherein: The location network utilizes ultra-wideband positioning.

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

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

44. The system of claim 25, wherein: The location data collected or received by the location system includes positioning data, and the location system uses the positioning data to calculate the location coordinates.

45. The system of claim 25, wherein: The plurality of location coordinate sets include a Global Positioning System GPS coordinate set.

46. ​​The system of claim 25, wherein: The plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

48. The system of claim 25, wherein: The location system is configured to segment holes of a golf course into regions, each region corresponding to a series of location coordinates, and wherein the location system is configured to determine a current region where the tracking module is located from the plurality of sets of location coordinates.

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

50. A score tracking system, the system comprising: A tracking module configured to be carried by a player participating in a golf tournament, an application configured to interface a user with scoring operations via a user interface of a companion device, the companion device being separate from the tracking module, and configured to receive input via the user interface indicating the occurrence of a stroke event, wherein the input causes the application to set a timestamp corresponding to the occurrence of the stroke event, wherein the stroke event includes an aim and a ball strike, and wherein the interface includes an indicator configured to be pressed to indicate that the player is aiming the ball and held until the player strikes the ball to indicate that the ball has been struck; and A position system configured to collect or receive position data, wherein the position data includes a plurality of position coordinate sets, or the position system generates the plurality of position coordinate sets using the position data, wherein each position coordinate set corresponds to the position of the tracking module at a specified time, wherein the position system is configured to pair the timestamp with the position coordinate set corresponding to the position of the tracking module at the occurrence of the hitting event.

51. The system of claim 50, wherein: The position of the tracking module at the occurrence of the stroke event serves as a proxy for the position of the ball of the player carrying the tracking module resulting from previous strokes.

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

53. The system of claim 52, wherein: The location network utilizes ultra-wideband positioning.

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

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

56. The system of claim 50, wherein: The location data collected or received by the location system includes positioning data, and the location system uses the positioning data to calculate the location coordinates.

57. The system of claim 50, wherein: The plurality of location coordinate sets include a Global Positioning System GPS coordinate set.

58. The system of claim 50, wherein: The plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

60. The system of claim 50, wherein: The location system is configured to segment holes of a golf course into regions, each region corresponding to a series of location coordinates, and wherein the location system is configured to determine a current region where the tracking module is located from the plurality of sets of location coordinates.

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

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

63. The method of claim 62, wherein: The companion device is carried by a scorekeeper who accompanies a group of players including the player, and wherein the companion device receives input corresponding to shot events of all players in the group.

64. A score tracking method, the method comprising: receiving, from a companion device, input corresponding to a stroke event of a player participating in a golf tournament, wherein the input includes a timestamp corresponding to an occurrence of the stroke event; collecting or receiving position data by a position system, wherein the position data corresponds to a position of a tracking module carried by the player, and wherein the position data includes or is used to generate a plurality of sets of position coordinates, each set of position coordinates corresponding to a position of the tracking module at a specified time; and The timestamp is paired with a set of location coordinates corresponding to the location of the tracking module at the occurrence of the shot event, wherein the shot event is input into the companion device by a scorer viewing a live video of the golf tournament.

65. The method of claim 64, wherein: The stroke event comprises a ball hit, and wherein the position of the tracking module at the occurrence of the stroke event serves as a proxy for the position of the ball of the player carrying the tracking module resulting from a previous stroke.

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

67. The method of claim 66, wherein: The location network utilizes ultra-wideband positioning.

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

69. The method of claim 64, wherein: The location tracking system is configured to receive the location data from a location network, and wherein 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 positioning data, and the location system uses the positioning data to calculate the location coordinates.

71. The method of claim 64, wherein: The plurality of location coordinate sets include a Global Positioning System GPS coordinate set.

72. The method of claim 64, wherein: The plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

74. The method of claim 64, further comprising: The holes of the golf course are divided into regions, each region corresponds to a series of position coordinates, and the current region where the tracking module is located is determined from the plurality of position coordinate sets.

75. A score tracking method, the method comprising: receiving, from a companion device, input corresponding to a stroke event of a player participating in a golf tournament, wherein the input includes a timestamp corresponding to an occurrence of the stroke event; collecting or receiving position data by a position system, wherein the position data corresponds to a position of a tracking module carried by a player, and wherein the position data includes or is used to generate a plurality of sets of position coordinates, each set of position coordinates corresponding to a position of the tracking module at a specified time; and The timestamp is paired with a set of position coordinates corresponding to the location of the tracking module at the occurrence of the shot event, wherein the shot event is entered into the companion device by a scorer viewing a video replay of the golf tournament.

76. The method of claim 75, wherein: The stroke event comprises a ball hit, and wherein the position of the tracking module at the occurrence of the stroke event serves as a proxy for the position of the ball of the player carrying the tracking module resulting from a previous stroke.

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

78. The method of claim 77, wherein: The location network utilizes ultra-wideband positioning.

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

80. The method of claim 75, wherein: The location tracking system is configured to receive the location data from a location network, and wherein 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 positioning data, and the location system uses the positioning data to calculate the location coordinates.

82. The method of claim 75, wherein: The plurality of location coordinate sets include a Global Positioning System GPS coordinate set.

83. The method of claim 75, wherein: The plurality of position coordinate sets include ultra-wideband positioning coordinate sets.

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

85. The method of claim 75, further comprising: The holes of the golf course are divided into regions, each region corresponds to a series of position coordinates, and the current region where the tracking module is located is determined from the plurality of position coordinate sets.

Images